On Mon, 2003-07-21 at 13:41, [EMAIL PROTECTED] wrote: > there's only one problemm with that idea (which i might add is a good one). > the browser has no idea about any compression of any kind (as far as i > know). you'd need an appl on your browsing machine to undo the compression > and feed it to the browser. > > sounds like a complicated setup.
HTTP/1.1 defines two routes for compressed content: Content Encoding (CE) and Transfer Encoding(TE). Transfer Encoding is appropriate for squid, and is able to compress data at any point during the transmission steps - server->squid, squid->squid, or squid->client. Content Encoding is /only/ end-to-end, and therefore not appropriate for squid to do. Both CE and TE are HTTP features in the RFC, and minimal support is a pre-requisite for browsers. Cheers, Rob -- GPG key available at: <http://members.aardvark.net.au/lifeless/keys.txt>.
signature.asc
Description: This is a digitally signed message part
