Re: More IMS

On Tue, 20 Apr 2004, Leeann BENT wrote:

>
> When an object in Squid's cache expires, it emits an IMS request to the
> server for this object. However, it seems to me that the cached object is
> not updated with the new cacheability information (at least assuming the
> 304 response has no Last-Modified header to compare with the old in
> httpReplyValidatorsMatch).

The object headers is not updated, but the date when we "got" this object
should be (and expires, if set). This is then what is used in freshness
calculations.

> This means that, once an object expires in cache, the cache will
> continue issuing IMS requests to the origin server on every request to
> this object, at least until the object changes on the server and a new
> 200 response comes back.

Should not be the case.

> Also, in response to the last IMS question, it looks like I'm seeing two
> requests (in Ethereal and in the squid logs)

What does the Squid logs say?

Is this two requests initiated by Squid, or two requests initiated by the
client?

Regards
Henrik
Received on Wed Apr 21 2004 - 12:04:33 MDT