Closed Bug 194934 Opened 22 years ago Closed 22 years ago

Mozilla's HTTP Pipelining doesn't interact well with VersionTracker.com

Categories

(Core :: Networking: HTTP, defect)

defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 195746
mozilla1.4alpha

People

(Reporter: joe, Assigned: darin.moz)

References

()

Details

(Whiteboard: [pipelining])

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021104 Chimera/0.6 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021104 Chimera/0.6 I noticed this for several weeks now but am just getting around to posting the bug. When visiting the ever-popular Mac site VersionTracker, often the pages do not render correctly. The images will appear mangled or misaligned, and hitting Reload only makes it progressively worse. Sometimes the style sheet doesn't seem to load, and clicking on linked images will sometimes yield just the same GIF image that was clicked instead of the intended page. This is one of the few sites where I have to switch to another browser to make use of it. Reproducible: Sometimes Steps to Reproduce: 1. go to http://www.versiontracker.com/macosx/ 2. Sometimes page does not render correctly 3. Sometimes links yield single gif images instead of the intended page Actual Results: broken layout, strange image behavior Expected Results: render page correctly
Joe, VersionTracker.com doesn't interact well with Mozilla's (and Chimera's) experimental HTTP Pipelining feature. By any chance, did you enable that by editing your prefs.js or user.js file?
Greg, I think this is it. I opened up prefs.js and saw that pipelining was enabled. Turned it off and Versiontracker works just fine now. Thanks for pointing that out! -Joe
Reassigning to Browser/Networking: HTTP.
Assignee: bryner → darin
Status: UNCONFIRMED → NEW
Component: Page Layout → Networking: HTTP
Ever confirmed: true
Product: Chimera → Browser
QA Contact: winnie → httpqa
Summary: Layout elements on VersionTracker.com not rendering correctly → Mozilla's HTTP Pipelining doesn't interact well with VersionTracker.com
Version: unspecified → Trunk
May I suggest that the bug gets a new description line to describe the underlaying problem? I found several sites which also exhibit this problem (and keep on searching): http://www.portazul.nl/ http://sibyl-archive.org/siteadmin/ (after redirection and login.. sorry) but maybe you can figure out which server (brand and version) is causing the trouble? --> this one is quite well reproducible
can anyone repro these problems using a 1.3 beta build or recent trunk build? the testcases seem ok to me w/ linux trunk 2003022608.
Yes. Using FizzillaMach/2003022803 with pipelining enabled, versiontracker.com loads very slowly and the images are mixed up.
The results I get (see comment 4) are using 1.3beta. Sorry for not mentioning before.
Just remembered that there is a great way to get higher reproducibility: When going to a site which exhibits this behaviour, click on a site-internal link while the page is still loading the images. Most of the time, I get an image instead of the page which the link referred to.
erik says via email that he can repro this on linux. can someone please capture a HTTP log demonstrating this problem? here's the steps (for linux w/ bash shell): $ export NSPR_LOG_MODULES=nsHttp:5 $ export NSPR_LOG_FILE=/tmp/http.log $ mozilla now, just repro the bug, exit mozilla, and then upload /tmp/http.log to this bug report. thx!
Status: NEW → ASSIGNED
OS: MacOS X → All
Hardware: Macintosh → All
Whiteboard: [pipelining]
actually, following the advice of comment #8, i can now repro this as well. very unusual behavior.
Target Milestone: --- → mozilla1.4alpha
Severity: normal → major
Netcraft says VT's running Apache/1.3.24 (Unix) mod_fastcgi/2.2.12 on an unknown platform.
*** Bug 192771 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 195746 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.