Closed
Bug 282149
Opened 20 years ago
Closed 9 years ago
Provide API to disable keep-alive connections
Categories
(Core :: Networking: HTTP, enhancement)
Core
Networking: HTTP
Tracking
()
RESOLVED
FIXED
People
(Reporter: darin.moz, Unassigned)
Details
Provide API to disable keep-alive connections. Right now, the only way to affect whether or not a request asks to make a persistent connection or not is to change the global pref: network.http.keep-alive That means that consumers who know that they are making requests that result in long-lived responses have to toggle this preference before calling NewChannel. That is pretty ugly. It would be better if we either: (1) supported some kind of flag on the channel itself, or (2) honored user-set Connection headers Option 2 might be nice anyways since "Connection" is the only hop-by-hop header, and one could imagine an application wanting to define a new hop-by-hop header (i.e., a new value for the Connection header). That said, 1 is nice because it is more explicit.
| Reporter | ||
Updated•20 years ago
|
Target Milestone: --- → Future
| Reporter | ||
Comment 1•19 years ago
|
||
-> default owner
Assignee: darin → nobody
Component: Networking: HTTP → Networking
QA Contact: networking.http → networking
Target Milestone: Future → ---
-> http.
Component: Networking → Networking: HTTP
QA Contact: networking → networking.http
Comment 3•9 years ago
|
||
LOAD_FRESH_CONNECTION
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•