Closed Bug 164833 Opened 22 years ago Closed 22 years ago

Mozilla displays HTTP request response(s) and binary data of other requests when pipelining is on

Categories

(Core :: Networking: HTTP, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

VERIFIED DUPLICATE of bug 140107

People

(Reporter: xenite, Assigned: darin.moz)

References

()

Details

(Whiteboard: [pipelining])

Attachments

(2 files)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 Sometimes when I load that page Mozilla at the top displays some binary code of files that were requested on the same page and HTTP request responses from the server ( Apache 1.3.12 Cobalt(Unix) ) at the start of the page. After scrolling down the rest of the page can be seen and the background image is displayed correctly (!). Reloading fixes the problem. Reproducible: Sometimes Steps to Reproduce: 1. Clean the cache, enable pipelining and go to the URL 2. 3.
Attached image Top of the page
Attached image Page scrolled down
Do you have pipelining turned on?
Yes, pipelining is turned on.
Summary: Mozilla displays HTTP request response(s) and binary data of other requests → Mozilla displays HTTP request response(s) and binary data of other requests when pipelining is on
Whiteboard: DUPEME
try disabling pipelining... and let us know if that fixes the problem. thx!
I have seen this and a similar error on other pages as well in the past, though it doesn't happen often and it seems that it only happens when pipelining is enabled. On one discussion forum (I think it was hosted on disc.server.com) Mozilla once even suddently used one of the images on that page as the background image! On reloading Mozilla used a different one as the background image. I had to reload the page a couple of times until Mozilla used the right file as the background image. So far I haven't been able to reproduce that particular bug.
well, if you can tell me the link to the problematic page, i might be able to determine what's going wrong. in most case having to do with pipelining-only bugs, it is the server that is at fault. why? because no other popular browsers besides mozilla support pipelining, so few people test their server software's pipelining abilities. nevermind the fact that the standard for HTTP/1.1 requires servers to support it ;-)
Whiteboard: DUPEME → DUPEME [pipelining]
this would be 140107 *** This bug has been marked as a duplicate of 140107 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME [pipelining] → [pipelining]
verified duplicate
Status: RESOLVED → VERIFIED
QA Contact: httpqa → tever
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: