Network.http.pipelining.maxrequests: Difference between revisions
From MozillaZine Knowledge Base
Jump to navigationJump to search
m (→Possible values and their effects: For grammar, umbrage) |
(→External links: Linking to LXR source that clamps this value) |
||
| Line 34: | Line 34: | ||
==External links== | ==External links== | ||
* [[http://lxr.mozilla.org/mozilla/source/netwerk/protocol/http/src/nsHttpHandler.cpp nsHttpHandler.cpp source file where the value is clamped to 8]] | |||
* [http://www.mozilla.org/projects/netlib/http/pipelining-faq.html HTTP/1.1 Pipelining FAQ] | * [http://www.mozilla.org/projects/netlib/http/pipelining-faq.html HTTP/1.1 Pipelining FAQ] | ||
[[Category:Preferences]] | [[Category:Preferences]] | ||
[[Category:Tweaking preferences]] | [[Category:Tweaking preferences]] | ||
Revision as of 13:49, 30 October 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 determines the maximum number of requests to pipeline at once. A value of 1 disables pipelining. (Default: 4)
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)
