Changeset 2166 for draft-ietf-httpbis/latest/p6-cache.xml

Timestamp:

27/01/13 10:46:43 (10 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:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p6-cache.xml

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