- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 17 Jan 2013 17:38:16 +1100
- To: "Adrien W. de Croy" <adrien@qbik.com>
- Cc: "HTTP Working Group" <ietf-http-wg@w3.org>
On 17/01/2013, at 12:23 PM, Adrien W. de Croy <adrien@qbik.com> wrote: > >> The original intent was to leave this open, AIUI, precisely because most content on the Web doesn't provide any freshness information. > There's something a bit disturbing about that. > > If most web content doesn't provide freshness information (which actually is what we also see), then heuristic freshness calculations are arguably the most important part of caching. > > Having the most important part left unspecified and open seems like a bit of a problem for interop. > > Where can a web author or cache implementor go to see what to expect the behaviour would be? Maybe we need a BCP? Well, an algorithm could be suggested in a separate document, but we can't require people to follow it. Lots of effort has gone into tweaking heuristics over the years by various caches, and it's often left up to the administrator (e.g., see refresh_pattern in Squid). I understand your concern; on the other hand, it's worked so far... -- Mark Nottingham http://www.mnot.net/
Received on Thursday, 17 January 2013 06:39:02 UTC