ansaurus

Question

Answer 1

+1 A:

Never seen an issue exactly like that, but I did have an issue once with a transparent proxy that would claim to the web server that it could handle gzip compressed content when, in fact, it received the gzipped content from the server, stripped the gzip headers without decompressing it, and sent the result to the browser. The behavior we saw was what you describe: a save/open file dialog for what should have been a normal web page. In this case the browser in question was IE.

I'm not sure if you're problem is related, but as an experiment, you could look at the requests between the proxy and Apache and see if they are gzipped, or else turn off the gzip compression for requests in Apache and see if that fixes the issue. If so, then you probably have a problem with gzip handling in your proxy.

jbourque 2009-04-10 15:08:56

I'm with jbourque on this one... it doesn't sound like a browser bug if there is content being added to the stream. Check to see if you have any gzip handlers enabled in your PHP ini, and also check to see if you have mod_deflate running on apache, and verify it's settings.

zombat 2009-04-10 17:37:48

Answer 2

+1 A:

wget doesn't request a compressed response. Try

curl --compressed <URL>.

You could also try adding a -v to print the response headers, check that a sensible Content-Type is being returned.

Dave Cheney 2009-05-04 11:50:04

ansaurus

tags:

views:

answers:

Strange http gzip issue

related questions