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

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Dave Kristol: "Re: Section 10.1.1 Combining Set-Cookie and Set-Cookie2"
• Previous message: Roy T. Fielding: "Age Header Field in HTTP/1.1"
• In reply to: Roy T. Fielding: "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"
• Reply: Roy T. Fielding: "Re: HTTP/1.1 Issue: max-age in responses not defined"

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?

Yours,
Bertold

==-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==
 Kolics, Bertold                             E-Mail: bertold@tohotom.vein.hu
 University of Veszprem, Hungary        W3: http://tohotom.vein.hu/~bertold/
 Information Engineering Course
==-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==

• Next message: Dave Kristol: "Re: Section 10.1.1 Combining Set-Cookie and Set-Cookie2"
• Previous message: Roy T. Fielding: "Age Header Field in HTTP/1.1"
• In reply to: Roy T. Fielding: "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"
• Reply: Roy T. Fielding: "Re: HTTP/1.1 Issue: max-age in responses not defined"