Re: Push and Caching

• From: Roy T. Fielding <fielding@gbiv.com>
• Date: Tue, 26 Aug 2014 09:44:00 -0700
• To: Mark Nottingham <mnot@mnot.net>
• Cc: HTTP Working Group <ietf-http-wg@w3.org>
• Message-Id: <9C64D35C-49BF-47F7-8D72-EFA2DA546FEA@gbiv.com>

On Aug 25, 2014, at 11:48 PM, Mark Nottingham wrote:

> "fresh on the origin server" isn't relevant; what's relevant is whether they're fresh in the cache, and that can be determined by examining the response.
> 
> The issue at hand is whether the pushed response needs to be revalidated, as per the definition of no-cache.

"A recipient cache SHOULD consider a pushed response to be valid for the
duration of the connection (or until it is replaced during that connection)
even if the pushed response contains a "no-cache" cache directive."

....Roy

Received on Tuesday, 26 August 2014 16:44:23 UTC