Network.http.connect.timeout
From MozillaZine Knowledge Base
Jump to navigationJump to search
Background
This preference was one of several added to allow low-level tweaking of the HTTP networking code. After a portion of the same code was significantly rewritten in 2001, the preference ceased to have any effect (as noted in all.js as early as September 2001).
Currently, the timeout is determined by the system-level connection establishment timeout. Adding a way to configure this value is considered low-priority.
Possible values and their effects
This integer preference specified the number of seconds to wait after firing off an HTTP request before considering it “timed out”. It was originally set to 30 by default. This preference no longer has an effect.
Caveats
- This preference was an entry in all.js for over four years after the code stopped using it. This was recently rectified, and it no longer appears in the default about:config listing.
First checked in
Has an effect in
- Netscape (all versions from 6 to 6.2)
- Mozilla Suite (all versions from M11 to 0.9.*)
Related bugs
- Bug 76866 - http spews many “private” events before any real data events
- Bug 83526 - http should use fewer connections per server per page
- Bug 92224 - 8.2.4 Client Behavior if Server Prematurely Closes Connection
- Bug 142326 - Conn: configurable http timeout in UI
- Bug 205140 - Prefs: remove “network.http.*.timeout”