- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Tue, 26 Aug 2014 09:59:35 -0700
- To: Mark Nottingham <mnot@mnot.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On Aug 26, 2014, at 9:44 AM, Roy T. Fielding wrote: > 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." Er, probably easier to be generic to all directives that control freshness: "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 cache directives that would normally indicate that the response is immediately stale." ....Roy
Received on Tuesday, 26 August 2014 16:59:58 UTC