Closed Bug 340418 Opened 19 years ago Closed 10 years ago

network.http.max-connections-per-server has no effect

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: bugzilla, Unassigned)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4 I have included detailed information on the web page listed as the test case, in summary the network.http.max-connections-per-server setting has no effect on the number of simultaneous connections firefox makes to a target web server. The test case script attempts to make 10 simultaneous connections to the web server, each request pausing 5 seconds before completing. Initialize IE's behavior is the same however changing MaxConnectionsPerServer to 16 for IE causes all 10 requests to complete in 6 seconds. This is the expected case for Firefox by changing the above settings and it has no effect. Reproducible: Always Steps to Reproduce: 1. Change your network.http.max-connections-per-server settings to 16 2. Make 10 simultaneous connections to a web server Actual Results: Connections are not made simultaneously Expected Results: Connections should be made simultaneously and complete in under 6 seconds (given the test case) Please do go to the test case url, it has clearly written code which demonstrates the issue.
Just to be clear, the test case url is: http://dev.epitunes.com/code/test.simul_connect.php
I have additionally found that this is only the case for GET statements, if you use all POST requests they will all execute simultaneously. I've updated the test case to show this as well.
Component: General → Networking: HTTP
Product: Firefox → Core
QA Contact: general → networking.http
Version: unspecified → Trunk
Try getting a log using the LiveHTTPHeaders extension? The "gGnerator" tab with all boxes checked looks promising.
try also setting network.http.max-persistent-connections-per-server?
It has been tested with that as well, same results.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.