Network.http.proxy.pipelining: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
(revert misguided edit by Fareds)
 
(15 intermediate revisions by 10 users not shown)
Line 2: Line 2:


==Background==
==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 page loading times, but not all servers support it. Some servers may even behave strangely if they receive pipelined requests. If a proxy server is configured, this preference controls whether to attempt to use pipelining with the proxy server.
[http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol 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 [http://en.wikipedia.org/wiki/HTTP_pipelining 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 configured, this preference controls whether to attempt to use pipelining with the proxy server.


==Possible values and their effects==
==Possible values and their effects==
Line 8: Line 8:
Attempt to use pipelining in HTTP 1.1 connections to the proxy server.
Attempt to use pipelining in HTTP 1.1 connections to the proxy server.


===true===
===<!-- If you change this text right here, absolutely nothing will happen in your browser's configuration -->false<!-- Yes, that text. Nothing will happen. Stop it. -->===
Never use pipelining. (Default)
Never use pipelining. (Default)


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


==Recommended settings==
==Recommended settings==
Line 50: Line 50:


[[Category:Preferences]]
[[Category:Preferences]]
[[Category:Tweaking preferences]]

Latest revision as of 03:28, 23 August 2010

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 configured, this preference controls whether to attempt to use pipelining with the proxy server.

Possible values and their effects

true

Attempt to use pipelining in HTTP 1.1 connections to the proxy server.

false

Never use pipelining. (Default)

Caveats

Recommended settings

Users who want better page loading speed can try setting this preference to true, keeping in mind this may break some websites.

First checked in

2001-05-11 by Darin Fisher

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)

Related bugs

Related preferences

See also

External links