Home/ Questions/Q 329067
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T09:33:13+00:00

I’m attempting to serve static resources (css and javascript) as cached gzipped files for

  • 0

I’m attempting to serve static resources (css and javascript) as cached gzipped files for performance reasons.

The pages look gzipped when rendered, the Content-Encoding is correctly set to gzip according to LiveHTTPHeaders, and most importantly, the gzipped content is passing the GIDZipTest page (http://www.gidnetwork.com/tools/gzip-test.php) just fine. Here’s an example of the output from the test:

Web page compressed? Yes

Compression type? gzip

Size, Markup (bytes) 18,286

Size Compressed (bytes) 4,427

Compression % 75.8 

----

ResponseHeaders

status HTTP/1.0 200 OK

pragma no-cache cache-control
private, max-age=86500

expires Mon, 24 Aug 2009 04:34:14 GMT

x-amz-acl public-read

content-type text/css

content-md5 hqJaTBS3OzDFet/QHsd+ Qg==

content-encoding gzip

date Wed, 19 Aug 2009 04:34:14 GMT

server — my server —

content-length 4427

The content-encoding header is in bold, and all the other headers are as expected.

The test page also shows the uncompressed page source, and it’s always exactly as I’d expect it to be uncompressed, and I’ve even tried copying and pasting it to be rendered by the browser, and it works, so the problem must be in the actual step of recognizing that the page is gzipped and unzipping it.

And this isn’t browser-specific. In FF, Webkit, and IE, these gzipped files are not being unzipped correctly. I’ve tried everything I can think of, but am genuinely stumped.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Maybe you have something else gzipping the file a second time, but only for http 1.1 clients that list it in accept-encoding, like most browsers. GIDZipTest is sending http 1.0 requests, and gzipping to 1.0 clients is risky because http 1.0 doesn’t have an accept-encoding field for clients to indicate which encodings they support, so it’d make sense for the second compressor (if there is one) to not gzip to 1.0 clients. If that’s the case, GIDZipTest would get a single-gzipped response while browsers would get a double-gzipped (bad) response. That’s just one possibility though. Rare, but it happens.

    If that’s not it, you really should give more information, like a url to a page exhibiting the problem.

    • 0