Closed Bug 142103 Opened 24 years ago Closed 16 years ago

Perf Regression w/ pipelining and secure surfing

Categories

(Core :: Networking: HTTP, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: rebron, Unassigned)

References

()

Details

(Whiteboard: [pipelining])

Seeing a slow down in surfing https sites with the Enable Http Pipelining pref enabled. Using Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020502 Go to https://webbranch.technologycu.com/ and notice the performance slow down when you http pref enabled and disabled.
I can't get the site to complete loading at all .. even when using HTTP/1.0. This bug may be related to, or a DUP of, bug #140176. (using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.0+) Gecko/20020507)
if the problem doesn't go away when you enable HTTP/1.0 then this bug has nothing to do with pipelining. can you confirm?
Actually, I'm only noticing it at this url. Not so much on other secure sites. Tested at http://401k.com But there is definitely a slow down at techcu when enable pipelining pref is enabled. When it's disabled, it speeds right back up.
mass futuring of untargeted bugs
Target Milestone: --- → Future
*** Bug 147788 has been marked as a duplicate of this bug. ***
Seeing this on 2002062508 build and 1.0.0 Debian package on Linux. Can't load my bank account or my 401k at all when pipelining is enabled. Darin, in comment #2 do you mean when HTTP/1.0 is enabled _with_ pipelining? I can test again with those settings if you want. OS->All
OS: Windows 2000 → All
After seeing bug 141179, I decided to check on the two sites I mentioned and they're running Microsoft IIS/5.0 and 4.0 respectively.
did the fix for bug 144442 affect this?
hmm... if the server is IIS/4.0 then we will not pipeline any requests to it. if the server is IIS/5.0 we don't prevent pipelining. that may have to change... especially if there are sites running IIS/5.0 that don't like pipelined requests.
Whiteboard: [pipelining]
-> default owner
Assignee: darin → nobody
QA Contact: tever → networking.http
Target Milestone: Future → ---
IIS/5.0 is now on the blacklist. Can we close this bug?
I'm going to close this. The server referenced in the comments is now on the pipeline server black list and no comments updated the impact of that change. The URL is question is not up any more.. the general http page for the domain now runs apache and has a redirect to a domain parking lot. There is nothing more to learn about making pipelining safe from this bug.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.