- From: Koen Holtman <koen@win.tue.nl>
- Date: Tue, 23 Jan 1996 22:04:43 +0100 (MET)
- To: mogul@pa.dec.com (Jeffrey Mogul)
- Cc: http-caching@pa.dec.com
Jeffrey Mogul: [...] > (3) The description of Expires: in draft-ietf-http-v11-spec-01.txt > says "Applications must not cache this entity beyond the date > given," whereas we seem to have some agreement that both > "fresh" and "stale" entities can be stored in a cache (but > a "stale" entity must be validated with the origin server > before being used as a response). I read the "cache" in the 1.1 draft quote above not as "store" but as "store and use without validation". This at least is current practice for proxy caches as far as I know. [...] >(3) specification wording regarding "must not cache" > I believe that we can safely reword section 10.19 of > Roy's 1.1 draft from: > Applications must not cache this entity beyond the date given > to: > Applications must not return this entity from their cache > after the date given, without first validating it with > the origin server. Yes, I think this would be safe. It would in fact be a much clearer description of current practice. >-Jeff Koen.
Received on Tuesday, 23 January 1996 22:20:17 UTC