Expires and 'non-cacheable'

• From: Nottingham, Mark (Australia) <mark_nottingham@exchange.au.ml.com>
• Date: Wed, 21 Jul 1999 15:09:35 +1000
• To: http-wg@hplb.hpl.hp.com
• Message-ID: <D900F0C3D524D111971F00805F0D50E1022F4A75@sv-meexch-01.au.ml.com>

In 14.9.3,
[...]
Many HTTP/1.0 cache implementations will treat an Expires value that is less
than or equal to the response Date value as being equivalent to the
Cache-Control response directive 'no-cache'. If an HTTP/1.1 cache receives
such a response, and the response does not include a Cache-Control header
field, it SHOULD consider the response to be non-cacheable in order to
retain compatibility with HTTP/1.0 servers.

Would it be safe to assume 'non-cacheable' can be interpreted as 'stale'
here? (everything else says it is)



Mark Nottingham
Internet Project Manager
Merrill Lynch Australasia (Melbourne)

Received on Tuesday, 20 July 1999 22:13:53 UTC