W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2012

Re: #227: HEAD and Caches

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Tue, 14 Feb 2012 02:31:53 +1300
Message-ID: <4F3910C9.2060001@treenet.co.nz>
To: Mark Nottingham <mnot@mnot.net>
CC: ietf-http-wg@w3.org
On 13/02/2012 5:45 p.m., Mark Nottingham wrote:
> Proposal --
>
> Old:
>
>    The response to a HEAD request is cacheable and MAY be used to satisfy a
>    subsequent HEAD request; see [Part6]. It also MAY be used to update a
>    previously cached representation from that resource; if the new field values
>    indicate that the cached representation differs from the current
>    representation (as would be indicated by a change in Content-Length, ETag or
>    Last-Modified), then the cache MUST treat the cache entry as stale.
>
> New:
>
> The response to a HEAD request is cacheable; it MAY be used to satisfy
> subsequent HEAD requests.
>
> If the Content-Length, ETag or Last-Modified value of a HEAD response differs
> from that in the selected GET response (as per [ref to p6 2.7]), the cache
> MUST consider that selected response to be stale.
>
>
>

+1.

AYJ
Received on Monday, 13 February 2012 13:32:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:56 GMT