Network.http.pipelining

From MozillaZine Knowledge Base

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

This article describes the preference network.http.pipelining. 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
- 2.1 true
- 2.2 false
3 Caveats
4 Recommended settings
5 First checked in
6 Has an effect in
7 Related bugs
8 Related preferences
9 See also
10 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. Pipelining reduces network load and can reduce page loading times over high-latency connections, but not all servers support it. Some servers may even behave incorrectly if they receive pipelined requests. If a proxy server is not configured, this preference controls whether to attempt to use pipelining.

[edit]

Possible values and their effects

[edit]

true

Attempt to use pipelining in HTTP 1.1 connections.

[edit]

false

Never use pipelining. (Default)

[edit]

Caveats

This preference has an effect only if you are not using a proxy. If you are using a proxy, see network.http.proxy.pipelining.
network.http.keep-alive must be set to true for pipelining to work.
network.http.version must be set to 1.1 for pipelining to work.
Although this preference may improve performance, it may cause problems loading pages from some servers.

[edit]