Changeset 481

Timestamp:

04/03/09 03:55:21 (13 years ago)

Author:

mnot@…

Message:

clean up / compact validation text.

File:

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

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

@@ -619 +619 @@
           <t>A "stale" response is one that either has explicit expiry information, or is allowed to
             have heuristic expiry calculated, but is not fresh according to the calculations in
-              <xref target="expiration.model" />. </t>
+              <xref target="expiration.model" />.</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
@@ -642 +642 @@
       <section anchor="validation.model" title="Validation Model">
         <t>When a cache has a stale response that it would like to use, it &SHOULD; first check
-          with the origin server (or possibly an intermediate cache with a fresh response) to see if
+          with the origin server (or possibly an intermediate cache) to see if
           it is still usable. This is called "validating" or "revalidating" the stored response.</t>
         <t>HTTP's conditional request mechanism, defined in &conditional;, is used to avoid
@@ -648 +648 @@
           response includes one or more "cache validators", such as the field values of an ETag or
           Last-Modified header field, then a validating GET request &SHOULD; be made conditional
-          to those field values. The server checks the conditional request's validator against the
-          current state of the requested resource and, if they match, the server responds with a 304
-          (Not Modified) status code to indicate that the stored response can be refreshed and
-          reused without retransmitting the response payload. If the validator does not match the
-          current state of the requested resource, then the server returns a full response,
-          including payload, so that the request can be satisfied and the stored response supplanted
-          without the need for an additional network round-trip.</t>
-        <t>See <xref target="combining.headers" /> regarding combining cached headers with those in
-          a 304 response.</t>
+          to those field values; a 304 (Not Modified) response status code indicates that the stored 
+          response can be updated and reused; see <xref target="combining.headers"/>.
+        <t>If the cache receives a full response (i.e., one with payload), it is used to satisfy the
+        request and replace the stored response.</t>
         <t>If a cache receives a 5xx response while attempting to validate a response, it &MAY;
           either forward this response to the requesting client, or act as if the server failed to
-          respond. In the latter case, it &MAY; return a previously received response unless the
+          respond. In the latter case, it &MAY; return a previously stored response unless the
           stored response includes the "must-revalidate" cache directive (see <xref
             target="cache-response-directive" />).</t>