[squid-users] Question about the reponse body content geted by ecap-adapter

Amos Jeffries squid3 at treenet.co.nz
Fri Oct 31 07:43:33 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31/10/2014 8:00 p.m., DongMing Huang wrote:
> Hi.
> 
> As we know, the reponse body content may be encoded by web server,
> for example gzip.
> 
> Before, I think the reponse body content geted by ecap-adapter
> from squid has been decoded by squid.
> 
> But, Now I‘m not sure about this.
> 
> So, What is the really answer ?

There are two forms of encoding HTTP messages. Content-Encoding and
Transfer-Encoding.

Transfer-Encoding gets removed before processing by Squid, and added
to messages output as they get delivered to clients/servers.

Content-Encoding is supposed to be end-to-end and is not touched by
Squid. eCAP adapters should expect content passed to them to match the
Content-Encoding header of the message.

Amos

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUUz2kAAoJELJo5wb/XPRjOmoIAIqCPJJ4p3JfLcFZ+S4O6Mfg
hLemGvuTcyhUwZ6ArIs8VeiQK3izKvZPq8LLNHJk7L2HduyDY74RZeAd6czO9Cv7
1yciiuk03b4+HF5yNbsYrdDejBm1ejRHndvYqAGij8VL3CezE+SfExdeJpeuZW6I
HJ8o830zGcrgfGaK/Bka87eg0R9+RyOxsGc5150+1hBSBTGZjgQMWLz/IWgGVUie
aVtIxK6AsxjGOAYAetOhoEUFaBV1dixFTVy8GVsQ5hiOFZ/oVN4qgaZmIf4KcUxS
eMDXj0U/dIDqhIBpOyeegQvZlQyuMw0SfTT++9+cxvcxnppQxPJyUdtD282Lkfk=
=kgvr
-----END PGP SIGNATURE-----


More information about the squid-users mailing list