Network.http.request.max-start-delay
Background
HTTP is the application-layer protocol that most web pages are transferred with. HTTP keep-alive connections can be re-used for multiple requests, as opposed to non-keep-alive connections, which are limited to one request. The preferences network.http.max-persistent-connections-per-server and network.http.max-persistent-connections-per-proxy define the maximum number of keep-alive connections that can be open at one time. This can cause a problem - if the keep-alive connections made are long-lived connections (large downloads), then short-lived connections won't be allowed to connect because the maximum number has already been reached. The solution is to allow the maximum number of keep-alive connections to be exceeded after a certain period of time. This preference controls that amount of time.
Possible values and their effects
Number of seconds keep-alive connections must wait before they are allowed to exceed the maximum. (Default: 10)
Caveats
- Even though this preference allows the maximum number of keep-alive connections to be exceeded, it doesn't allow exceeding the maximum number of connections of any type to a particular server or in total.
- network.http.keep-alive (if you don't have a proxy) or network.http.proxy.keep-alive (if you have a proxy) must be set to true for this preference to take effect.
First checked in
Has an effect in
- Netscape (all versions since 7.0)
- Mozilla Suite (all versions since 0.9.4)
- Mozilla Phoenix (all versions)
- Mozilla Firebird (all versions)
- Mozilla Firefox (all versions)
- SeaMonkey (all versions)
- Camino (all versions)
- Minimo (all versions)
