On 22/05/2014 11:15 p.m., Amos Jeffries wrote: > On 22/05/2014 9:50 p.m., Tom Holder wrote: >> Hi Amos, >> >> Indeed it does, but the proxy is for a custom server/browse setup and >> it's essential the browser doesn't cache, however, the server behind >> squid is performing expensive operations so I want squid to cache it. >> >> Basically, I would cache in the browser, but I don't have granular >> enough control to cache content in the way I need. site1.com might >> look one way 1 second and then immediately serve completely different >> content based on what a user does (a different header is sent). >> Essentially the browser is getting confused and bleeding content >> between these two (what it believes are identical, but aren't) sites. > > So the server (or your config of Squid?) is violating HTTP protocol, and > your users are getting visible effects of the violation. > > The "fix" you asked for is this: > > acl site1 dstdomain site1.com > http_reply_access Cache-Control deny site1 > http_reply_replace Cache-Control no-store Oops. That should have been: reply_header_access Cache-Control deny site1 reply_header_replace Cache-Control no-store (thank Eliezer for the reminder). Amos
