[squid-users] Expires header not updating

From: Simon Morley <simon@dont-contact.us>
Date: Thu, 5 Dec 2002 22:20:18 -0000

Hi,
    We are running SQUID (2.4.STABLE4) in accelerator mode front ending a
bunch of Windows 2000 IIS5 servers.

For all of our reasonably static content we have set the web servers to
issue an 1 day expirary (i.e. The Expires: header has a date one day in the
future).

This is all fine and dandy until that day has passed, after which SQUID
serves an old expires header if the object had not been updated. This has
the result that anyone, new or old, retrieving the object from our cache has
an old expires header which causes the object to immediately expire in their
cache. This means that for all subsequent requests for that object by their
browser we receive IMS get requests when we really want the object to be
served directly from the browsers local cache.

Looking through the bug database, I see that Bug ID#7 is exactly the problem
we have (http://www.squid-cache.org/bugs/show_bug.cgi?id=7).

Is this still a problem with the 2.5 series of SQUID ?

If so, does anyone know of a workaround?

This is actually quite a big problem for us as it means objects are not
being properly cache in downstream caches. Okay, yes, the full object is not
being retrieved due to the IMS get stating that the object has not changed,
but it should not have to do the IMS get at all.

Any help would be very much appreciated!

--
Simon Morley
Received on Thu Dec 05 2002 - 15:20:21 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:11:52 MST