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

Re: HTTP/1.1 #223: Allowing heuristic caching for new status codes

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 18 Feb 2013 11:01:06 +1100
Message-Id: <70525D6C-5EA0-42B4-A7C9-4EB56B5F5776@mnot.net>
To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
I haven't seen any feedback on this, so I'm closing as incorporated.


On 11/02/2013, at 5:27 PM, Mark Nottingham <mnot@mnot.net> wrote:

> <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/223>
> 
> After some discussion with Roy, we've come to the conclusion that the edits I did when I re-wrote the caching part unnecessarily introduced a new aspect of status codes -- whether or not responses carrying it can have a heuristic applied to determine freshness.
> 
> We're currently working through the drafts to pull that back, so that any status code defined as "cacheable" can have a heuristic applied.
> 
> We'll review those edits as part of our next round of drafts; just wanted to give people a heads-up. In parallel, I'm going to open another issue regarding *what* status codes are cacheable by default; this came out of the discussion of #223.
> 
> Cheers,
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
> 
> 

--
Mark Nottingham   http://www.mnot.net/
Received on Monday, 18 February 2013 00:01:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 18 February 2013 00:01:36 GMT