Ignore:
Timestamp:
Jan 27, 2013, 2:46:43 AM (7 years ago)
Author:
fielding@…
Message:

Indicate certain status codes as cacheable by default instead of heuristics allowed; Use requirement on heuristics to allow them to be used only when cacheable by default or indicated as cacheable via public directive; Addresses #223

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2109 r2166  
    621621<section anchor="heuristic.freshness" title="Calculating Heuristic Freshness">
    622622<t>
    623    If no explicit expiration time is present in a stored response that has a
    624    status code whose definition allows heuristic freshness to be used
    625    (including the following in &status-codes;: <x:ref>200 (OK)</x:ref>,
    626    <x:ref>203 (Non-Authoritative Information)</x:ref>, <x:ref>206 (Partial
    627    Content)</x:ref>, <x:ref>300 (Multiple Choices)</x:ref>, <x:ref>301 (Moved
    628    Permanently)</x:ref> and <x:ref>410 (Gone)</x:ref>), a cache &MAY;
    629    calculate a heuristic expiration time. A cache &MUST-NOT; use heuristics to
    630    determine freshness for responses with status codes that do not explicitly
    631    allow it.
     623   A cache &MUST-NOT; use heuristics to determine freshness unless no explicit
     624   expiration time is present in a stored response and either the status code
     625   is defined as cacheable by default (including the following in
     626   &status-codes;: <x:ref>200 (OK)</x:ref>, <x:ref>203 (Non-Authoritative
     627   Information)</x:ref>, <x:ref>206 (Partial Content)</x:ref>, <x:ref>300
     628   (Multiple Choices)</x:ref>, <x:ref>301 (Moved Permanently)</x:ref> and
     629   <x:ref>410 (Gone)</x:ref>) or the response has been explicitly marked as
     630   cacheable (e.g., by using the public directive without a max-age).
    632631</t>
    633632<t>
Note: See TracChangeset for help on using the changeset viewer.