Don't hash on Accept-Encoding; Varnish natively supports compression

Varnish 3 natively supports gzip. If a client supports gzip then the Accept-Encoding header is automatically normalized. Varnish will even request gzip'd content from the back-end even if a client doesn't support it and then decompress the content before sending it back to the client.

This allows Varnish to store a single compressed copy of the content for all clients, making the hash on Accept-Encoding unnecessary.


https://www.varnish-cache.org/docs/3.0/tutorial/compression.html

https://www.varnish-cache.org/docs/3.0/phk/gzip.html