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: Roy T. Fielding <fielding@kiwi.ICS.UCI.EDU>
Date: Wed, 26 Mar 1997 15:41:33 -0800
To: "Kolics Bertold, University of Veszprem" <bertold@tohotom.vein.hu>
Cc: http-wg@cuckoo.hpl.hp.com
Message-Id: <9703261541.aa26783@paris.ics.uci.edu>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2921
>>    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)?

Yes, but not independent of other parts of Cache-Control (like private).

>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?

It should return Expires = Date and Cache-Control: no-cache
The first is for HTTP/1.0 caches and the second id for HTTP/1.1 caches.
Note that max-age=0 means "cachable, but treat as stale on future requests".

Received on Wednesday, 26 March 1997 16:01:33 UTC

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