W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Re: p6: Returning the freshest response

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 3 Apr 2013 15:32:39 +1100
Cc: ietf-http-wg@w3.org
Message-Id: <F3BC48ED-ACF6-4CA4-A0EE-089BBCD98069@mnot.net>
To: Amos Jeffries <squid3@treenet.co.nz>

On 31/03/2013, at 11:30 AM, Amos Jeffries <squid3@treenet.co.nz> wrote:

> Perhapse this is a bit better?
> "
> If multiple selected responses are available, the cache will need to choose one to use. When a selecting header has a known mechanism for doing so (e.g., qvalues on Accept and similar request headers), that mechanism SHOULD be used to eliminate unwanted responses; of the remainder, the most recent response (as determined by the Date header field) is used, as per Section 4.
> "
> Making it clear that Date mechanism still applies, but only after the negotiation filtering has been done. AFAIK that is how it always gets done in practice anyway.

I'm OK with your intent, but upgrading the MAY to a SHOULD is going to make implementations non-conformant. 

Mark Nottingham   http://www.mnot.net/
Received on Wednesday, 3 April 2013 04:33:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:10 UTC