Network.http.max-persistent-connections-per-proxy

From MozillaZine Knowledge Base

The title given to this article is incorrect due to technical limitations. The correct title is network.http.max-persistent-connections-per-proxy.

This article describes the preference network.http.max-persistent-connections-per-proxy. 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
3 Caveats
4 Recommended settings
5 First checked in
6 Has an effect in
7 Related bugs
8 Related preferences
9 External links

[edit]

Background

HTTP is the application-layer protocol that most web pages are transferred with. HTTP keep-alive connections can be re-used for multiple requests, as opposed to non-keep-alive connections, which are limited to one request. Using keep-alive connections improves performance. If a proxy server is configured, the total number of HTTP keep-alive connections the application can make to it is limited by this preference. If more connections are needed, they are queued until a connection "slot" is available.

[edit]

Possible values and their effects

This preference takes values between 1 and 255 inclusive, directly corresponding to the maximum number of HTTP keep-alive connections the application can have open at once to the proxy server. (Minimo default: 2. Firefox 3: 8. All others default: 4.)

[edit]

Caveats

This preference only has an effect if you are using a proxy. If you are not using a proxy, see network.http.max-persistent-connections-per-server.
When using a proxy, the maximum number of connections of any type is controlled by network.http.max-connections and network.http.max-connections-per-server.

[edit]

Recommended settings

If you are using a proxy and experience problems not being able to download multiple files, you can raise this value. It is, however, considered poor etiquette to make too many connections to a server and may lead to you being banned from that server.

[edit]