Paul Fee wrote:
Could someone point out a reason for the different behaviour in the
request and response path?
Cookies.
Cookie headers cannot be compressed as the RFC says they should be, so
proxy works around this by not compressing headers.
How about making the behaviour configurable so that it's consistent
in both directions and if necessary the headers can be left in
their original uncompressed form?
In theory, the idea that it be consistent in both directions is not
unreasonable - it follows the principle of "be lenient in what we accept".
Regards,
Graham
--
