Akamai Customer Care Reporter
	Description • 19 years ago

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

To reproduce this ensure you send in your Web server gzipped content and that you include 2 times the header: "Content-Encoding: gzip".

For example:
---clip---
$ curl -I -s -H "Accept-encoding: gzip" http://test.test.com/reg/javascript/wmd_hilfe1.js
HTTP/1.1 200 OK
Server: Apache
ETag: "4ca47d8c5928dfb227a789d3d70dc3aa:1132831582"
Last-Modified: Thu, 24 Nov 2005 11:26:27 GMT
Accept-Ranges: bytes
Content-Length: 467
Content-Type: application/x-javascript
Content-Encoding: gzip
Content-Encoding: gzip
Vary: Accept-Encoding
Date: Thu, 08 Dec 2005 12:33:46 GMT
---clap---

That page was unreadable in Firefox but showed fine in Internet Explorer.

When tracing the headers for Firefox, I observed Firefox kind of added the headers and it was showing in this way:
Content-Encoding: gzip,gzip

Reproducible: Always

Steps to Reproduce:
1. Make a request to a gzipped object and ensure the Web server returns 2 times Content-Encoding: gzip
2. The page will not render properly


Actual Results:  
Firefox is unable to display the gzipped objects (empty document)
Load the same URL in IE and it will show fine

Expected Results:  
The second header should have been ignored and the page should have been rendered correctly

	Elmar Ludwig
	Comment 1 • 19 years ago

*** This bug has been marked as a duplicate of 205156 ***