On Sat, 12 Feb 2005, Tomasz Chmielewski wrote:
As far as I know, Squid doesn't support gzip/deflate.
Correct. Squid can not gzip/deflate content on the fly.
But there is obviously no problem for Squid to forward gzipped content from the web server.
I thought it can't request compressed content, but I was wrong. A nice surprise I'd say! :)
So to sum up: nowadays Squid would be 99% effective as regards to compression, as most web browsers do support compression?
Other things Squid won't do:
- request and download a compressed content and then forward it uncompressed to a program that don't support gzip/deflate (e.g. wget),
- when serving from a cache, it will not compress content when client requests it - but it would not matter on LAN anyway (it would only matter when Squid and the client are connected via a slow link).
The pages saved in Squid cache were not compressed, though, but this is not an issue.
Squid caches the compressed version if allowed by the web server.
What will happen if Squid caches some compressed html document (because the web server allowed to), and then this same page would be requested by a gzip/deflate-uncompatible browser?
Squid will have to download this document once again, right?
Tomek
