3 ms·
Actually, the reason is that the browser uncompresses components before caching them, so compression has no effect on cacheability. The generated data are actu
by rgrove 16y ago
Actually, the reason is that the browser uncompresses components before caching them, so compression has no effect on cacheability.
The generated data are actually a series of newline-delimited MD5 hashes of pseudorandom numbers, which makes them fairly compressible. For example, 32KB of data gzips down to about 18.9KB, which seems to me like a pretty reasonable representation of typical web content.
I didn't conclude that gzip "doesn't work", just that it has no effect on cacheability. Gzip is certainly good for reducing the number of bytes on the wire, though.