Heya,
Tollef Fog Heen wrote:
> it's been a while, we should meet up one of those days. :-)
definitely!
> | It seems that the "Accept-encoding" header the client sends (or doesn't
> | send in curl's case) to Varnish is the crucial bit, but of course I'm
> | not sure. It _does_ influence the curl result though, setting it to the
> | same as what Iceweasel sends to Varnish messes up the results (only
> | garble comes back).
>
> I'd start by turning off Content-Encoding: gzip and see if that helps.
Excactly where do you mean I should turn this off?
Turning off Apache mod_deflate solves the problem. However, it's
probably not the "ultimate" solution as I wager the customer wants to
still use the deflate module. Setting
# Make sure proxies don't deliver the wrong content
Header append Vary User-Agent env=!dont-vary
in Apache's site configuration doesn't seem to help when mod_deflate is
active. I assume the remedy is playing around with more Apache options,
I'm grateful any input here.
Cheers,
-Torstein
--
Torstein Krause Johansen
System Architect
mobile: +47 97 01 76 04
web: http://www.escenic.com/
Escenic - platform for innovation
_______________________________________________
varnish-misc mailing list
[email protected]
http://projects.linpro.no/mailman/listinfo/varnish-misc
