Re: change 14.21 Expires

• From: Roy T. Fielding <fielding@liege.ICS.UCI.EDU>
• Date: Fri, 07 Jun 1996 16:06:10 -0700
• To: Paul Leach <paulle@microsoft.com>
• Cc: "'jg@w3.org'" <jg@w3.org>, "'http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com'" <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>
• Message-Id: <9606071606.aa10137@paris.ics.uci.edu>

minor twiddling ...

> Add the following paragraph to the end of 14.21:
> 
> 	The presence of an Expires header on an response that otherwise would
> by default
> 	be non-cacheable overrides the default and makes it cacheable.

would be better phrased as

   The presence of an Expires header field with a date value of some time
   in the future indicates that the response is cachable, unless indicated
   otherwise by a Cache-Control header field (section 14.9).

.....Roy

Received on Friday, 7 June 1996 17:09:27 UTC