Changeset 2179 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

11/02/13 06:10:25 (10 years ago)

Author:

mnot@…

Message:

Tidy up discussion of heuristic freshness, with follow-on effects in the
definition of 'public', the storage algorithm, and considerations for new
status codes. Addresses #223

File:

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

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

@@ -4305 +4305 @@
 </t>
 <t>
-   A definition for a new status code ought to explain the request
+   The definition of a new status code ought to explain the request
    conditions that would cause a response containing that status code (e.g.,
    combinations of request header fields and/or method(s)) along with any 
@@ -4313 +4313 @@
 </t>
 <t>
-   A response that can transfer a payload ought to specify expected cache
-   behavior (e.g., cacheability and freshness criteria, as described in
-   &caching;) and whether the payload has any implied association with an
-   identified resource (<xref target="identifying.payload"/>).
+   The definition of a new status code ought to specify whether or not it is
+   cacheable. Note that all status codes can be cached if the response they
+   occur in has explicit freshness information; however, status codes that are
+   defined as being cacheable are allowed to be cached without explicit
+   freshness information. Likewise, the definition of a status code can place
+   constraints upon cache behaviour. See &caching; for more information.
+</t>
+<t>   
+   Finally, the definition of a new status code ought to indicate whether the
+   payload has any implied association with an identified resource (<xref
+   target="identifying.payload"/>).
 </t>
 </section>