Changes between Initial Version and Version 2 of Ticket #23755


Ignore:
Timestamp:
11/26/2014 05:28:58 PM (5 years ago)
Author:
Tim Graham
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #23755

    • Property Cc wgordonw1@… added
    • Property Component changed from Uncategorized to Core (Cache system)
    • Property Version changed from 1.7 to master
    • Property Type changed from Uncategorized to New feature
    • Property Triage Stage changed from Unreviewed to Accepted
  • Ticket #23755 – Description

    initial v2  
    11From my cursory reading of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html, it looks like patch_cache_control needs to special case "no-cache".
    22
    3 
    4 {{{
    5 no-cache
    6 If the no-cache directive does not specify a field-name, then a cache MUST NOT use the response to satisfy a subsequent request without successful revalidation with the origin server. This allows an origin server to prevent caching even by caches that have been configured to return stale responses to client requests.
    7 If the no-cache directive does specify one or more field-names, then a cache MAY use the response to satisfy a subsequent request, subject to any other restrictions on caching. However, the specified field-name(s) MUST NOT be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
    8 }}}
    9 
     3 no-cache
     4 If the no-cache directive does not specify a field-name, then a cache MUST NOT use the response to satisfy a subsequent request without successful revalidation with the origin server. This allows an origin server to prevent caching even by caches that have been configured to return stale responses to client requests.
     5 If the no-cache directive does specify one or more field-names, then a cache MAY use the response to satisfy a subsequent request, subject to any other restrictions on caching. However, the specified field-name(s) MUST NOT be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
    106
    117For example, to integrate a site that uses "Vary: Cookie" with AWS CloudFront, one must use 'Cache-Control: no-cache="Set-Cookie"' if a response does not vary by cookie.  (I've confirmed this with AWS support as of 10/31/2014).
Back to Top