- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Wed, 03 Apr 2013 22:27:08 +1300
- To: Mark Nottingham <mnot@mnot.net>
- CC: ietf-http-wg@w3.org
On 3/04/2013 5:32 p.m., Mark Nottingham wrote: > 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. How? and which ones? I would think upgrading it to MUST would make things non-conformant but SHOULD is not absolute. Amos
Received on Wednesday, 3 April 2013 09:28:27 UTC