Henrik, Thanks for a prompt response. Unfortunatley, seems like we're still missing something: The origin server is including CacheControl: max-age=0 ETag: <etag-value> in it's response. The problems are 1) Squid is not sending If-None-Match: <etag-value> in subsequent requests (unless the browser includes this in it's request in which case squid just passes it on) 2) When the origin server return 302, squid just passes 302 back to the browser rather than serving up its cached copy of the image. Any further tips? thanks -nikita Henrik Nordstrom-5 wrote: > > On tor, 2008-10-16 at 16:12 -0700, dukehoops wrote: >> 1. With what headers should the origin server respond in 3a) and 3b)? In >> latter case, it seems like something like "Cache-Control: >> must-revalidate", >> not sure whether to use s-maxage=0 and/or maxage=0 > > You probably do not need or want must-revalidate, it's a quite hard > directive. max-age is sufficient I think. > > You only need must-revalidate (in addition to max-age) if it's > absolutely forbidden to use the last known version when/if revalidation > should fails to contact the web server for some reason. > > You only need s-maxage if you want to assign different cache criterias > to shared caches such as Squid and browsers, for example enabling > browsers to cache the image longer than Squid. > >> 2. What params should be used in squid config? > > Preferably nothing specific for this since you have control over the web > server.. > > REgards > Henrik > > > ----- ---------------- Nikita Tovstoles vside.com ---------------- -- View this message in context: http://www.nabble.com/newbie%3A-configuring-squid-to-always-check-w-origin-server-tp20018895p20037231.html Sent from the Squid - Users mailing list archive at Nabble.com.
