Change Details

It seems we could be hurting on cache efficiency due to MW commonly sending Vary:Accept-Encoding and us not sanitizing the client's Accept-Encoding per the example in https://www.varnish-cache.org/docs/3.0/tutorial/vary.html . On a quick check of varnish logs, I see examples of both MW backend sending that Vary header, and of various clients sending us all kinds of variations (e.g. "gzip, deflate" vs "gzip,deflate" vs "gzip, deflate, sdch" (chrome))...