W3C home > Mailing lists > Public > http-caching-historical@w3.org > February 1996

Re: backward compatibility of non-cachable headers

From: Roy T. Fielding <fielding@avron.ICS.UCI.EDU>
Date: Sun, 18 Feb 1996 00:20:02 -0800
To: Koen Holtman <koen@win.tue.nl>
Cc: http-caching@pa.dec.com, state@xent.w3.org
Message-Id: <9602180020.aa01815@paris.ics.uci.edu>
> I thought up the `Cache-Control always overrides Expires in 1.1, even
> if Expires gives a shorter lifetime' idea in the context of Vary
> headers and negotiable resources. ...

Ummm, that should be in draft 00......oops, I guess I forgot it.
Max-age needs to override expires simply because we don't want servers
to have to calculate the HTTP-date in expires if they understand max-age.

Received on Sunday, 18 February 1996 08:41:52 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:55:57 UTC