Changeset 884

Timestamp:

23/07/10 12:29:48 (13 years ago)

Author:

mnot@…

Message:

Add heuristic freshness requirements to status codes (see #199).

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (11 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -74 +74 @@
   <!ENTITY p5-status-codes            "<xref target='Part5' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY p7-status-codes            "<xref target='Part7' x:rel='#status.code.definitions' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY p6-heuristic               "<xref target='Part6' x:rel='#heuristic.freshness'
+xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
 ]>
 <?rfc toc="yes" ?>
@@ -1181 +1183 @@
   </list>
 </t>
+<t>
+        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine 
+        freshness for 200 responses.
+</t>
 </section>
 
@@ -1241 +1247 @@
    response would otherwise be 200 (OK).
 </t>
+<t>
+        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine 
+        freshness for 203 responses.
+</t>
+
 </section>
 
@@ -1294 +1305 @@
    and the enclosed payload is a partial representation as defined in &status-206;.
 </t>
+<t>
+        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine 
+        freshness for 206 responses.
+</t>
 </section>
 </section>
@@ -1340 +1355 @@
    include the specific URI for that representation in the Location
    field; user agents &MAY; use the Location field value for automatic
-   redirection. This response is cacheable unless indicated otherwise.
-</t>
+   redirection. 
+</t>
+<t>
+        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine 
+        freshness for 300 responses.
+</t>
+
 </section>
 
@@ -1352 +1372 @@
    URIs.  Clients with link editing capabilities ought to automatically
    re-link references to the Effective Request URI to one or more of the new
-   references returned by the server, where possible. This response is
-   cacheable unless indicated otherwise.
+   references returned by the server, where possible.
+</t>
+<t>
+        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine 
+        freshness for 301 responses.
 </t>
 <t>
@@ -1384 +1407 @@
    The requested resource resides temporarily under a different URI.
    Since the redirection might be altered on occasion, the client &SHOULD;
-   continue to use the Effectice Request URI for future requests.  This response
-   is only cacheable if indicated by a Cache-Control or Expires header
-   field.
+   continue to use the Effectice Request URI for future requests.
 </t>
 <t>
@@ -1454 +1475 @@
 </t>
 <t>
-   A 303 response &SHOULD-NOT; be cached unless it is indicated as
-   cacheable by Cache-Control or Expires header fields.  Except for
-   responses to a HEAD request, the representation of a 303 response &SHOULD;
-   contain a short hypertext note with a hyperlink to the Location URI.
+   Except for responses to a HEAD request, the representation of a 303 
+   response &SHOULD; contain a short hypertext note with a hyperlink 
+   to the Location URI.
 </t>
 </section>
@@ -1497 +1517 @@
    The requested resource resides temporarily under a different URI.
    Since the redirection &MAY; be altered on occasion, the client &SHOULD;
-   continue to use the Effective Request URI for future requests.  This response
-   is only cacheable if indicated by a Cache-Control or Expires header
-   field.
+   continue to use the Effective Request URI for future requests.
 </t>
 <t>
@@ -1697 +1715 @@
    server does not know, or has no facility to determine, whether or not
    the condition is permanent, the status code 404 (Not Found) &SHOULD; be
-   used instead. This response is cacheable unless indicated otherwise.
+   used instead.
 </t>
 <t>
@@ -1710 +1728 @@
    discretion of the server owner.
 </t>
+<t>
+        Caches &MAY; use a heuristic (see &p6-heuristic;) to determine freshness 
+        for 410 responses.
+</t>
+
 </section>