Re: Code updates

Mark Swanson wrote:

> Our emails crossed paths and we took 2 different approaches. You are 
> forcing
> Vary: on all responses, and I'm only sending it when people access it 
> via the
> extra_html_header (which needed patching).
>
> Perhaps the perfect patch would be another proc entry to 
> enable/disable the
> Vary: header.
>
> What you have done or what I have done work well enough for me and I'm 
> happy
> to leave it at that.
>
> Last thought: If squid _ever_ caches a response with no Vary it will not
> replace it with a new response containing Vary - nor obey the Vary 
> semantics.
> So, perhaps it is simply better to always enable Vary: so this confusing
> scenario can never occur.


Squid 2.5.STABLE1 does support Vary headers, and obeys them...so if you 
send a vary header, older Squids won't cache it, new Squids will cache 
it correctly.  (I think.  Henrik wrote the code, and Robert spent some 
time on the mod_gzip/Squid-Dev lists hashing out what happens when.  I 
can't seem to get any search results from the squid-dev list right now, 
so I don't have a link to point to---but it is definitely in the archives.)
-- 
Joe Cooper <[email protected]>
Web caching appliances and support.
http://www.swelltech.com