Re: HTTP/1.1 Issue: max-age in responses not defined

>I believe what Roy meant by "non-cachable" is "not usable without
>revalidation", not "not storable".

No, I meant not "cachable" as defined by RFC 2068.  The paragraph
would not be needed if I meant "not usable without revalidation",
since the existing definitition of Expires adequately covers that.

....Roy

Received on Monday, 31 March 1997 17:50:31 UTC