- From: David Krauss <potswa@gmail.com>
- Date: Fri, 21 Mar 2014 07:49:29 +0800
- To: Martin Thomson <martin.thomson@gmail.com>
- Cc: "William Chan (???)" <willchan@chromium.org>, Daniel Sommermann <dcsommer@fb.com>, HTTP Working Group <ietf-http-wg@w3.org>
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.
Received on Thursday, 20 March 2014 23:50:14 UTC