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

Roy T. Fielding (fielding@kiwi.ICS.UCI.EDU)
Mon, 31 Mar 1997 17:46:48 -0800

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Jeffrey Mogul: "Re: Age Header Field in HTTP/1.1"
Previous message: Roy T. Fielding: "Re: HTTP/1.1 Issue: max-age in responses not defined"
In reply to: Jeffrey Mogul: "Re: HTTP/1.1 Issue: max-age in responses not defined"
Next in thread: Roy T. Fielding: "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

Next message: Jeffrey Mogul: "Re: Age Header Field in HTTP/1.1"
Previous message: Roy T. Fielding: "Re: HTTP/1.1 Issue: max-age in responses not defined"
In reply to: Jeffrey Mogul: "Re: HTTP/1.1 Issue: max-age in responses not defined"
Next in thread: Roy T. Fielding: "Re: HTTP/1.1 Issue: max-age in responses not defined"