Network.http.pipelining.ssl

From MozillaZine Knowledge Base

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

This article describes the preference network.http.pipelining.ssl. 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 First checked in
5 Has an effect in
6 Related bugs
7 Related preferences
8 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.

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.

[edit]

Possible values and their effects

[edit]

True

Use HTTP pipelining for secure websites

[edit]

False

Do not use HTTP pipelining for secure websites, unless network.http.pipelining is true (Default)

[edit]

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.

[edit]