Closed Bug 160667 Opened 23 years ago Closed 23 years ago

The page is rendered as garbage. [Accept-encoding: Deflate offered but not supported]

Categories

(Core :: Networking: HTTP, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

VERIFIED DUPLICATE of bug 105292

People

(Reporter: kedar.bhise, Unassigned)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721 BuildID: 2002072104 The page http://economictimes.indiatimes.com/cms.dll/default shows up correctly in IE 6. In Mozilla 1.1b, the page shows up as a string of garbage characters. An exaample: ä=kwÚÈ’ŸwΙÿÐË}xæ¬ z ŽÍ=ãÄs�íd²³{vs©�Žõ`ô°ÃìîñOݪ– Reproducible: Always Steps to Reproduce: 1. Paste the URL in the address bar. 2. Press enter. 3. You should get the garbage Actual Results: The page is rendered as: ä=kwÚÈ’ŸwΙÿÐË}xæ¬ z ŽÍ=ãÄs�íd²³{vs©�Žõ`ô°ÃìîñOݪ– Expected Results: Rendered the page correctly. I am using the Lobpuri Flat theme
Tried to reproduce with 1.0 and 1.1b nightly. Both of them only show this behaviour when using a squid proxy. Reporter: are you also using a proxy? Maybe squid doesnt pass through the headers containing gzip-information? Just my...
he site sends us "Content-Encoding:Deflate", which I thought we explicitly did not support?
Assignee: Matti → new-network-bugs
Status: UNCONFIRMED → NEW
Component: Browser-General → Networking
Ever confirmed: true
QA Contact: asa → benc
I have to revoke my comment regarding proxies and the WFMs... But it obviously depends on the encoding... But when "Content-Encoding:Deflate" is not supported, why does my nightly send these headers?: Accept-Encoding: gzip, deflate, compress;q=0.9
*** This bug has been marked as a duplicate of 105292 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
->http
Component: Networking → Networking: HTTP
vrfy dupe
Status: RESOLVED → VERIFIED
Summary: The page is rendered as garbage. See description → The page is rendered as garbage. [Accept-encoding: Deflate offered but not supported]
You need to log in before you can comment on or make changes to this bug.