Your message dated Mon, 14 May 2007 10:29:07 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#423709: Chokes on .css/.js with Content-Encoding: gzip
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: iceweasel
Version: 2.0.0.3-1
I was testing Content-Encoding: gzip of CSS and Javascript files on my
site. Iceweasel does not handle these at all.
With gzip-encoded CSS, the page loads as if the stylesheet could not be
downloaded at all. The Error Console gives "Selector expected" and
"unclosed string" warnings for the .css file, clearly indicating that the
interpreter is parsing the compressed form of the stylesheet.
With gzip-encoded Javascript, the page loads as if it weren't there, and
the Error Console shows "Illegal character" errors in the script files to
similar effect as with the CSS.
Interestingly enough, if you click on the file links in the Error Console
to the .css/.js files in question, the Javascript files display fine---but
the CSS still shows up as binary gibberish.
The server logs confirm that the gzip-compressed versions of both types of
files were the ones downloaded.
Given that the server was correctly acting upon the Accept-Encoding request
header sent by Iceweasel, this is a pretty egregious bug. At the very
least, the header should be adjusted to accurately reflect what the browser
can/cannot handle.
--- End Message ---
--- Begin Message ---
On Mon, May 14, 2007 at 04:24:51AM -0400, Daniel Richard G. <[EMAIL PROTECTED]>
wrote:
> On Mon, 2007 May 14 08:40:22 +0200, Mike Hommey wrote:
> >
> > Could you install mozilla-livehttpheaders, open tools->live http
> > headers, and check out the headers the server sends and post them here ?
>
> Oh, f***... the server is sending "Content-Encoding: gzip, gzip", which
> apparently means that mod_gzip is compressing the already-gzipped CSS and
> Javascript content. (These live as static .css.gz/.js.gz files on the
> server, and are served using a non-mod_gzip content-negotiation mechanism.)
>
> So that's it, then. My server provider has a misconfigured mod_gzip. The
> whole problem goes away when I explicitly disable mod_gzip with
> "mod_gzip_on No".
>
> Sorry for not catching this sooner---this behavior did not show up with
> text/html (see below), nor with "lynx -head", which was what I was using to
> test the server response.
I'll close this bug, then.
Mike
--- End Message ---
