Closed Bug 238475 Opened 21 years ago Closed 14 years ago

http://www.qwestwireless.com is displayed incorrectly - images stretched if pipelining enabled

Categories

(Core :: Networking, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: wayne, Unassigned)

References

()

Details

(Whiteboard: [pipelining])

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040316 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040316 Images are stretched and repeated on http://www.qwestwireless.com Reproducible: Always Steps to Reproduce: 1. Navigate to http://www.qwestwireless.com 2. Notice that "wireless-header-personal.gif" is stretched horizontally 3. Notice that other page elements are repeated
WFM, I see no difference between Moz 1.7b, FF 0.8 or IE 5.0 on WinNT4.
this seems like a pipelining issue. site is completely broken in mozilla with pipelining enabled but properly working when disabled. however, there seem to be no problems with current firefox (regardless of the pipelining-settings).
confirming pipelining breaks the site (FF 20040319 Win2k), perhaps it's worth adding Netscape Enterprise 6.0 to the black list ? http://lxr.mozilla.org/seamonkey/source/netwerk/protocol/http/src/nsHttpConnection.cpp#236
Assignee: roc → darin
Component: Layout: View Rendering → Networking: HTTP
QA Contact: ian → httpqa
OS: Windows 98 → All
Summary: http://www.qwestwireless.com is displayed incorrectly - images are stretched → http://www.qwestwireless.com is displayed incorrectly - images stretched if pipelining enabled
Umm... using 1.7b on WinXP the site looks fine even with pipelining enabled. Yes, Cache cleared and all.
mmm wfm too using FF 20040401 on Win2k (tried both pipelined and non-pipelined)
Then the issue is more difficult to trace: I don't think there were lots of network changes between 20040319 and now (Olivier once saw it, now not) and I also don't think FF does differ from Seamonkey network-wise (Christian saw it with SM, but not with FF).
I'm now seeing this also in FF (20040408) on Win2k. However, it is not always reproducable and happens most often after reloading the page (which previously displayed correctly). Anyway, I don't see it anymore with pipelining disabled.
confirming. problem is reproducible in FF 20040315 linux trunk. pipelining specific bugs are low priority right now.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [pipelining]
Target Milestone: --- → Future
-> default owner
Assignee: darin → nobody
Component: Networking: HTTP → Networking
QA Contact: networking.http → networking
Target Milestone: Future → ---
www.qwestwireless.com redirects to qwest.com, which is running Apache, and I see no problems with pipelining enabled, so this appears to be resolved. http://toolbar.netcraft.com/site_report?url=http://www.qwest.com According to the following page, Netscape Enterprise 6.0 is down to ~6000 servers (0.01%) http://www.securityspace.com/s_survey/server_graph.html?type=http&domaindir=&month=201007&serv1=TmV0c2NhcGUtRW50ZXJwcmlzZS82LjA= Many of the NES6.0 servers I found were redirects to servers running Sun-ONE-Web-Server/6.1+, Apache, etc. I don't see any problem with pipelining with these NES6.0 websites: https://argus.uwf.edu/, http://fcps.edu/, http://www.usps.com/, http://excite.co.jp/, http://cigna.com/, http://www.sunrisemedical.co.uk/, https://www.divinvest.com/, http://labavn.org/, http://tm.hilton.com/, http://www.regenthotels.com/, http://lpse.jatengprov.go.id/, http://www.sprintpcs.com/pages/dataPlanEducation.html, http://www.cengage.co.uk/ http://www.dialog.com/, http://www.scotiabank.com/, http://www.edwardjones.com/ However watching the following NES6.0 websites with Firebug shows 'Aborted' requests which are refetched OK; I'm not sure what that means. http://cibil.com/, http://www.caixalaietana.cat/, http://cuba.cu/ http://tmxmoney.com/, http://www.topamax.com/, http://www.nova.edu/, http://www.eudora.com/, http://www.tmx.com/, http://mtnlmumbai.in/, http://opel.de/ These NES6.0 websites perform very badly when pipelining is enabled, with only part of the page contents loaded initially, and the rest of the content arriving after a ~1-2 minutes delay.(probably a separate bug) http://mibcn.com/ http://www.johnhancock.com/ None of these show the originally reported bug.
John, I think C#10 is really interesting, thanks. At the very least it shows that NSES6 really doesn't benefit from pipelining (it closes the connection - that's where those aborts are coming from), so the rare versions of it on the internet could safely go into a blacklist without a downside.
Depends on: 593386
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.