- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 21 Mar 2014 10:59:50 +1100
- To: David Krauss <potswa@gmail.com>
- Cc: Martin Thomson <martin.thomson@gmail.com>, "William Chan (???)" <willchan@chromium.org>, Daniel Sommermann <dcsommer@fb.com>, HTTP Working Group <ietf-http-wg@w3.org>
That's interesting. Probably just a Cache-Control directive, e.g., Cache-Control: max-age=60, once Like you say, just a hint. On 21 Mar 2014, at 10:49 am, David Krauss <potswa@gmail.com> wrote: > > On 2014–03–20, at 1:30 AM, Martin Thomson <martin.thomson@gmail.com> wrote: > >> The reason, as I understand it, relates to the ability of a client to >> act upon a response when it is received. If you push a response that >> is not expected and it's not cacheable, then - absent some sort of >> eventing API - it has to be discarded. > > It sounds like it would be useful to have a header to specify that a resource should be evicted from the cache once retrieved. > > Safe to ignore, but if used it would avoid a form of cache pollution that currently does not exist. > > -- Mark Nottingham http://www.mnot.net/
Received on Friday, 21 March 2014 00:00:35 UTC