On Monday 21 July 2003 05.41, mwestern@sola.com.au 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.
There is varying degrees of support for compression in most browsers
today.
The official way to do this in proxies is to use what is called
"Transfer Encoding" in HTTP/1.1.
The official way to do this in web servers is to use "Content
Encoding", but a web server may also use "Transfer Encoding".
A transforming proxy may apply new content encodings to replies, but
is not recommended unless one has a clear understanding of HTTP/1.1
ETag interactions when modifying content entities.
The main difference between "Transfer Encoding" and "Content Encoding"
is where the coding of the entity is applied. "Transfer Encoding"
recodes the data transfer on a hop-by-hop basis, leaving the data and
semantics fully intact. "Content Encoding" applies a transofrmation
to the object as such, actually resulting in a different object, and
operates end-to-end.
Both require HTTP/1.1 to operate correctly. Support for
transfer-encoding is the major obstacle for Squid to become HTTP/1.1.
-- Donations welcome if you consider my Free Squid support helpful. https://www.paypal.com/xclick/business=hno%40squid-cache.org If you need commercial Squid support or cost effective Squid or firewall appliances please refer to MARA Systems AB, Sweden http://www.marasystems.com/, info@marasystems.comReceived on Mon Jul 21 2003 - 04:24:31 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:18:13 MST