Network.http.proxy.pipelining: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
(clarifications, Wikipedia links, and copyediting)
Line 5: Line 5:


==Possible values and their effects==
==Possible values and their effects==
===true===
Set "network.http.pipelining" to "true"
Attempt to use pipelining in HTTP 1.1 connections to the proxy server.


===<!-- 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. -->===
===<!-- 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. -->===

Revision as of 06:33, 6 May 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

Set "network.http.pipelining" to "true"

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