Network.http.max-connections-per-server

From MozillaZine Knowledge Base

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

This article describes the preference network.http.max-connections-per-server. 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. The total number of HTTP connections the application can make to a single server 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 connections Mozilla can have open at once. (Minimo default: 2. All others default: 8. Firefox 3: 15)

[edit]

Caveats

If you are using a proxy, the proxy server - not the server the content is coming from - is the server affected, so this effectively limits the maximum number of total connections. The maximum number of connections to all servers is controlled by network.http.max-connections.

[edit]

Recommended settings

If you experience problems not being able to download multiple files from a site, 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]

First checked in

2001-05-11 by Darin Fisher

[edit]

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)

[edit]