Network.http.pipelining.maxrequests

From MozillaZine Knowledge Base

The title given to this article is incorrect due to technical limitations. The correct title is network.http.pipelining.maxrequests.

This article describes the preference network.http.pipelining.maxrequests. To add, delete, or modify this preference, you will need to edit your configuration — do not edit this article.

1 Background 2 Possible values and their effects 3 Caveats 4 Recommended settings 5 First checked in 6 Has an effect in 7 Related bugs 8 Related preferences 9 External links

[edit]

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 when pipelining is enabled.

[edit]

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)

[edit]

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.

[edit]

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.

[edit]

First checked in

2001-05-11 by Darin Fisher

[edit]

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)

[edit]