Changeset 914 for draft-ietf-httpbis/latest

Timestamp:

24/07/10 10:44:07 (10 years ago)

Author:

mnot@…

Message:

Allow new status codes to define whether they allow heuristic freshness (see #223).

File:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (2 diffs)

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

@@ -32 +32 @@
   <!ENTITY safe-methods                "<xref target='Part2' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY weak-and-strong             "<xref target='Part4' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY status-codes                "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
 ]>
 <?rfc toc="yes" ?>
@@ -596 +597 @@
 <t>
   If no explicit expiration time is present in a stored response that has a status code
-  of 200, 203, 206, 300, 301 or 410, a heuristic expiration time can be
-  calculated. Heuristics &MUST-NOT; be used for other response status codes.
+  whose definition allows heuristic freshness to be used (including the following
+  in &status-codes;: 200, 203, 206, 300, 301 and 410), a heuristic expiration time &MAY; be
+  calculated. Heuristics &MUST-NOT; be used for response status codes that do not explicitly
+  allow it.
 </t>
 <t>