Network.http.pipelining.maxrequests: Difference between revisions
From MozillaZine Knowledge Base
Jump to navigationJump to search
m (→Possible values and their effects: 1 = no pipelining) |
|||
Line 5: | Line 5: | ||
==Possible values and their effects== | ==Possible values and their effects== | ||
Any integer from 1 to 8 inclusive, determining the maximum number of requests to pipeline at once. A value of 1 effectively means "do not pipeline". (Default: | Any integer from 1 to 8 inclusive, determining the maximum number of requests to pipeline at once. A value of 1 effectively means "do not pipeline". (Default: 30) | ||
==Caveats== | ==Caveats== |
Revision as of 22:37, 5 January 2006
Background
HTTP is the application-layer protocol that most web pages are transferred with. In HTTP 1.1, multiple requests can be sent before any responses are received. This is known as pipelining. This preference specifies the maximum number of requests to pipeline at once.
Possible values and their effects
Any integer from 1 to 8 inclusive, determining the maximum number of requests to pipeline at once. A value of 1 effectively means "do not pipeline". (Default: 30)
Caveats
- network.http.pipelining or network.http.proxy.pipelining (depending on whether you use a proxy) must be set to true for this preference to take effect.
Recommended settings
Higher values will cause a delay before the first request completes but will make the last request complete sooner. Higher values will also cause more of a delay if a connection fails.
First checked in
Has an effect in
- Netscape (all versions since 6.1)
- Mozilla Suite (all versions since 0.9)
- Mozilla Phoenix (all versions)
- Mozilla Firebird (all versions)
- Mozilla Firefox (all versions)
- SeaMonkey (all versions)
- Camino (all versions)
- Minimo (all versions)