RE: [squid-users] Problem with attachment updates

 
>
> All,
>
> Found an interesting "problem" which we can replicate and can't find a
> solution. We are running Squid2.5 (Stable 5 on a Solaris 9 server) and
> have a web site on IIS. The html page on the web server is basically a
> link to a Word document on the web server (the page which showed this
> error in the first place is more complex - this small site is for
> testing purposes). When we click on the link, as expected,
> the document
> opens.
>
> The problem we have is that when we replace the document with a newer
> version (same name) and try and access the file again the old
> version of
> the file is returned. In the access.log and store.log it is being
> treated as if the file has not been updated, and the cached version is
> being returned. We have tried clearing out the local browser
> cache to no
> avail. We have tried different browsers to no avail. We are running a
> default installation (not much changed in the Squid.conf file
> in regards
> to cache settings). These attachments change on a frequent
> interval, so
> we need the latest always returned.
>
> We have also tested this on a 2.5 Stable 3 implementation as well with
> the same result. This tends to indicate it is a "feature", not a
> "problem". Is this true? We are investigating looking at
> denying caching
> DOC, XLS, HLP files etc. from the cache, but is this
> necessary? Is this
> normal for this type of site?
>
> Any assistance/questions/links to answers would be appreciated.
>
 
  Caching behavior depends (also) on "freshness" info about objects
returned by the remote webserver. Check with :

       http://www.ircache.net/cgi-bin/cacheability.py

for your document(s)/url(s).
When an object get's updated and or changed the webserver must 'reflect' this
info towards webcache(s).

M.
Received on Mon Jun 07 2004 - 23:32:13 MDT