sk.random2 at gmail
Aug 31, 2011, 3:40 PM
Post #1 of 2
As per the issue I've created at
File download fails with gzip compression enabled on SSL
http://code.google.com/p/cherokee/issues/detail?id=1243 , I believe I've
found a bug in Cherokee when having Gzip compression enabled for a SSL
As far as I've experienced using Cherokee 1.2.98, when I attempt a file
download from a system I have a HTTP reverse proxy handler in for in
Cherokee, the resource doesn't get delivered correctly to the browser. As
per the issue description at the above link, if I attempt to load something
like a 15MB image in my browser (SSL+gzip on in Cherokee), the image starts
to load and after about 1 or 2 lines of pixels, a "Content Encoding Error --
The page you are trying to view cannot be shown because it uses an invalid
or unsupported form of compression." is seen.
Trying to load the same resource via HTTP only with Gzip compression through
Cherokee is completely fine, so my current work-around for this issue is to
disable Gzip compression against SSL connections. The back-end system is a
CMS (Plone, specifically) but interestingly, no download issues are seen for
etc), so this leads me to think perhaps its something to do with the size of
the content, but that's a stab in the dark.
Again, as I mention in my bug report, there's no issue downloading the
resources on HTTPS with things like wget or curl, but presumably this is
because neither client send any 'Accept-Encoding' headers to request
compression. I may have to try sending these headers and see what happens.
Has anyone experienced the same issue? The workaround is fine for now, but
I'd like to be able to use Gzip on SSL (and not have to have 2 separate
rules for working around this).