Mailing List Archive: Content-encoding: gzip

In message <73096a160610041506w374b315fy32ea1ba4f6826c5 at mail.gmail.com>, "Joseph Mc
Donald" writes:
>Hi,
>
>my backend does gzip compression for clients that support it. However
>it appears that varnish caches and sends out whatever it got first.
>That is, if a client supports gzip, than it caches the gzip version.
>If the next client does not support gzip, varnish still sends out the
>gzip version. and vice versa.
>
>Do I need to configure something for varnish to respect the
>Content-encoding header?

We havn't implemented the Vary: header yet, so we are not able
to do this trick yet.

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.