- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 24 Jul 2009 10:09:11 +1000
- To: Henrik Nordstrom <henrik@henriknordstrom.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
The term was added because it was needed in 2.4; > When a cache has one or more stored responses for a requested URI, > but cannot serve any of them (e.g., because they are not fresh, or > one cannot be selected... > When sending such a conditional request, the cache SHOULD add an If- > Modified-Since header whose value is that of the Last-Modified > header from the selected (see Section 2.6) stored response, if > available. On 24/07/2009, at 9:24 AM, Henrik Nordstrom wrote: > fre 2009-07-24 klockan 08:17 +1000 skrev Mark Nottingham: > >> * What p6 2.6 currently calls the "selected response", although I >> suspect that may eventually need to change if we're to properly >> address the terminology issue. > > for now I would probably remove selected response from p6 2.6 as > follows: > > from: > > The stored response with matching selecting request-headers is > known as the selected response. > > If no selected response is available, the cache MAY forward the > presented request to the origin server in a conditional > request; > see Section 2.4. > > To: > > If no response with matching selecting request-headers is > available, the cache MAY forward the presented request to the > origin server in a conditional request; see Section 2.4. > > > unless there is plans to actually define "selected response" as a term > and use it elsewhere as well. > > > Regards > Henrik > -- Mark Nottingham http://www.mnot.net/
Received on Friday, 24 July 2009 00:09:53 UTC