Try configuring the webserver (IIS) such that these documents cannot be cache or have expiry period.
The task of maintaining content freshness should belongs to the webmaster and not the proxy server administrator. -----Original Message----- From: Trigge, Graham [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 08, 2004 10:19 AM To: [EMAIL PROTECTED] Subject: [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. Regards, --------------------------------- Graham Trigge Telstra Australia IT Technical Specialist Messaging Support, Northern Region W +61 2 8272 8657 M +61 409 654 434 "Time flies like an arrow, but fruit flies like a banana"
