Network.http.pipelining.ssl
From MozillaZine Knowledge Base
Jump to navigationJump to search
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.
Many problems with pipelining are related to broken proxy servers sitting between the user and the destination web site. Since this is not a problem with SSL, it is possible to turn on pipelining for SSL websites only. This preference controls whether to use pipelining for secure websites, regardless of network.http.pipelining.
Possible values and their effects
True
Use HTTP pipelining for secure websites
False
Do not use HTTP pipelining for secure websites, unless network.http.pipelining is true (Default)
Caveats
- This preference is meant to override network.http.pipelining for one specific case—secure websites. If this preference is false and network.http.pipelining is true, pipelining will still be used for secure websites.
First checked in
Has an effect in
- Firefox (nightly builds since 2008-02-06)
Related bugs
- Bug 414477 - SSL should run with pipelining
- Bug 422978 - pipelining breaks secure Internet banking websites
