Closed
Bug 1674124
Opened 4 years ago
Closed 4 years ago
We should disable HTTP3 if NS_HTTP_ALLOW_KEEPALIVE is not set
Categories
(Core :: Networking: HTTP, task, P2)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
84 Branch
Tracking | Status | |
---|---|---|
firefox84 | --- | fixed |
People
(Reporter: dragana, Assigned: dragana)
References
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
The simple solution would be just to disable HTTP3.
We may think about allowing it in the similar way HTTP2 does it, it is allowed as the first and only Transaction and the connection is closed after that.
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Assignee: nobody → dd.mozilla
Status: NEW → ASSIGNED
Assignee | ||
Updated•4 years ago
|
Pushed by ddamjanovic@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/caca899c0ff4
Disable HTTP3 if NS_HTTP_ALLOW_KEEPALIVE is set. r=necko-reviewers,valentin
Comment 3•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox84:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•