- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 27 May 2011 13:49:09 +1000
- To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
I haven't heard any objections to the proposal below; incorporating in <http://trac.tools.ietf.org/wg/httpbis/trac/changeset/1289>. On 27/04/2011, at 6:29 PM, Mark Nottingham wrote: > Reopening #38 to track. > > <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/38> > > > On 27/04/2011, at 6:19 PM, Poul-Henning Kamp wrote: > >> In message <12278CD3-2800-4C1A-992C-75F814EF7146@mnot.net>, Mark Nottingham wri >> tes: >> >>> Vary isn't ordering-dependent, so Obj3 and Obj4 are equivalent, and the >>> latest one should be used as per this requirement in p6 2.2: >>> >>> A cache MUST use the most recent response (as determined by the Date >>> header field) when more than one suitable response is stored. >> >> Ok, I hadn't connected that requirement to the Vary case, but >> it obviously settles the issue. >> >>> What about something like >>> >>> """ >>> If multiple selected responses are available, the most recent response >>> (as determined by the Date header field) is used (see [section 2.2]). >>> """ >> >> Works for me. >> >> -- >> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 >> phk@FreeBSD.ORG | TCP/IP since RFC 956 >> FreeBSD committer | BSD since 4.3-tahoe >> Never attribute to malice what can adequately be explained by incompetence. > > -- > Mark Nottingham http://www.mnot.net/ > > > > -- Mark Nottingham http://www.mnot.net/
Received on Friday, 27 May 2011 03:49:35 UTC