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

Timestamp:

23/10/13 01:11:09 (9 years ago)

Author:

mnot@…

Message:

Adjust language around "cacheable by default", ref to p2

File:

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

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

@@ -52 +52 @@
   <!ENTITY lastmod-comparison          "<xref target='Part4' x:rel='#lastmod.comparison' 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'/>">
+  <!ENTITY status-overview             "<xref target='Part2' x:rel='#overview.of.status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status.2xx                  "<xref target='Part2' x:rel='#status.2xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY transformations             "<xref target='Part1' x:rel='#message.transformations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -294 +295 @@
             target="cache.control.extensions" />) that allows it to be cached,
             or</t>
-            <t>has a status code that is defined as cacheable
+            <t>has a status code that is defined as cacheable by default
             (see <xref target="heuristic.freshness" />), or</t>
             <t>contains a public response cache directive (see <xref
@@ -662 +663 @@
    requirements in <xref target="response.cacheability"/>, this means that,
    effectively, heuristics can only be used on responses without explicit
-   freshness whose status codes are defined as cacheable, and responses
-   without explicit freshness that have been marked as explicitly cacheable
-   (e.g., with a "public" response cache directive).
+   freshness whose status codes are defined as cacheable by default (see
+   &status-overview;), and those responses without explicit freshness that have
+   been marked as explicitly cacheable (e.g., with a "public" response cache
+   directive).
 </t>
 <t>
@@ -1424 +1426 @@
    response, even if the response would normally be non-cacheable or cacheable
    only within a private cache. (See <xref
-   target="caching.authenticated.responses"/> for additional details related
-   to the use of public in response to a request containing
-   <x:ref>Authorization</x:ref>, and <xref target="response.cacheability"/>
-   for details of how public affects responses that would normally not be
-   stored, due to their status codes not being defined as cacheable.)
+   target="caching.authenticated.responses"/> for additional details related to
+   the use of public in response to a request containing
+   <x:ref>Authorization</x:ref>, and <xref target="response.cacheability"/> for
+   details of how public affects responses that would normally not be stored,
+   due to their status codes not being defined as cacheable by default; see
+   <xref target="heuristic.freshness"/>.)
 </t>
 </section>