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

Re: Server push limited to cache priming?

From: David Krauss <potswa@gmail.com>
Date: Fri, 21 Mar 2014 07:49:29 +0800
Cc: (wrong string) ι™ˆζ™Ίζ˜Œ)" <willchan@chromium.org>, Daniel Sommermann <dcsommer@fb.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <5531F31F-84AF-41F5-BBFE-DD422A6CC85E@gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>

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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:25 UTC