Changeset 495

Timestamp:

Mar 3, 2009, 10:46:55 PM (11 years ago)

Author:

mnot@…

Message:

rearrange serving stale responses

File:

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

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

@@ -619 +619 @@
             have heuristic expiry calculated, but is not fresh according to the calculations in
               <xref target="expiration.model" />.</t>
+          <t>Caches &MAY; return a stale response if disconnected or explicitly allowed (e.g.,
+            the max-stale request directive; see <xref target="cache-request-directive" />).</t>
+          <t>Otherwise, caches &SHOULD-NOT; return stale responses.</t>
           <t>Caches &MUST-NOT; return a stale response if it is prohibited by an explicit
             in-protocol directive (e.g., by a "no-store" or "no-cache" cache directive, a
@@ -624 +627 @@
             "proxy-revalidate" cache-response-directive; see <xref target="cache-response-directive"
              />). </t>
-          <t>Caches &MAY; return a stale response if disconnected or explicitly allowed (e.g.,
-            the max-stale request directive; see <xref target="cache-request-directive" />).</t>
-          <t>Otherwise, caches &SHOULD-NOT; return stale responses.</t>
           <t>Stale responses &SHOULD; have a Warning header with the 110 warn-code (see <xref
               target="header.warning" />).</t>