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

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

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 11 Feb 2013 17:27:40 +1100
Message-Id: <5EC66A14-A13C-4AA5-BB77-145D298EC1B3@mnot.net>
To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>

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.


Mark Nottingham   http://www.mnot.net/
Received on Monday, 11 February 2013 06:29:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:10 UTC