W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 1997

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

From: Kolics Bertold, University of Veszprem <bertold@tohotom.vein.hu>
Date: Wed, 26 Mar 1997 11:18:58 +0100 (MET)
To: "Roy T. Fielding" <fielding@kiwi.ICS.UCI.EDU>
Cc: http-wg@cuckoo.hpl.hp.com
Message-Id: <Pine.LNX.3.95.970326111003.25583B-100000@tohotom.vein.hu>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2902

On Tue, 25 Mar 1997, Roy T. Fielding wrote:
>    The max-age directive on a response implies that the
>    server believes it to be cachable.
Does it mean that: if there is a max-age in a response, it is cacheable
(independent of the value of max-age)?
So, if a server wants a response to be treated as uncacheable then should
it return a Expires = Date or max-age set to zero?


 Kolics, Bertold                             E-Mail: bertold@tohotom.vein.hu
 University of Veszprem, Hungary        W3: http://tohotom.vein.hu/~bertold/
 Information Engineering Course
Received on Wednesday, 26 March 1997 02:05:19 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:01 UTC