Ian Hickson wrote:
[EMAIL PROTECTED]">On Tue, 24 Apr 2001, Steve Morrison wrote:- images (such as banner ads) that give the current time (and sometimes
even times in the past?) as an expiration date are cached. These
probably should not be.
Well, we have to cache some version of every image just so that we don't
hit the server again when the user hits "back" to return to a page that
contained images which were generated on the fly and will be different
each time we ask the server. If you see what I mean.
Of course that might be totally irrelevant to this discussion, in which
case sorry! :-)
this is a real bug... servers often send an Expires header with a time in the past, which means that the response should not be reused without first validating it. when browsing via history, we don't care about cache validation, and in fact because of history, we do put everything in the cache. so, if a user browses to a page and hits cached content with an Expires header in the past, we should treat the cached response as if it came with a "Cache-Control: must-revalidate" header. i believe i own a bug on this already.
darin
