Network.http.pipelining: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
m (reverting)
m (tweaking)
Line 53: Line 53:


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

Revision as of 01:34, 12 June 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. 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 not configured, this preference controls whether to attempt to use pipelining.

Possible values and their effects

true

Attempt to use pipelining in HTTP 1.1 connections.

false

Never use pipelining. (Default)

Caveats

  • This preference only has an effect 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.
  • While this preference will improve performance, it may cause problems loading pages from some servers.

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