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

Timestamp:

16/12/12 03:46:23 (9 years ago)

Author:

fielding@…

Message:

editorial fixes in methods; use send instead of return, sent instead of returned; partly addresses #419

File:

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

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

@@ -211 +211 @@
    <list>
       <t>The time at which the origin server intends that a representation
-      no longer be returned by a cache without further validation.</t>
+      no longer be sent by a cache without further validation.</t>
    </list>
 </t>
@@ -471 +471 @@
    title="Constructing Responses from Caches">
 <t>
-   For a presented request, a cache &MUST-NOT; return a stored response,
+   For a presented request, a cache &MUST-NOT; send a stored response,
    unless:
    <list style="symbols">
@@ -796 +796 @@
 </t>
 <t>
-   A cache &MUST-NOT; return a stale response if it is prohibited by an
+   A cache &MUST-NOT; send 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 "must-revalidate" cache-response-directive, or an applicable
@@ -803 +803 @@
 </t>
 <t>
-   A cache &MUST-NOT; return stale responses unless it is disconnected
+   A cache &MUST-NOT; send stale responses unless it is disconnected
    (i.e., it cannot contact the origin server or otherwise find a forward
    path) or doing so is explicitly allowed (e.g., by the max-stale request
@@ -872 +872 @@
          response while attempting to validate a response, it can either
          forward this response to the requesting client, or act as if the
-         server failed to respond. In the latter case, it can return a
+         server failed to respond. In the latter case, it can send a
          previously stored response (see <xref
          target="serving.stale.responses" />).
@@ -1073 +1073 @@
    the cache will either remove all stored responses related to the effective
    request URI, or will mark these as "invalid" and in need of a mandatory
-   validation before they can be returned in response to a subsequent request.
+   validation before they can be sent in response to a subsequent request.
 </t>
 <t>
@@ -1362 +1362 @@
    the origin server. This allows an origin server to prevent a cache from
    using it to satisfy a request without contacting it, even by caches that
-   have been configured to return stale responses.
+   have been configured to send stale responses.
 </t>
 <t>
@@ -1757 +1757 @@
       rectified by a validation (for example, a lossy compression of the
       representation) and &MUST-NOT; be deleted by a cache after validation,
-      unless a full response is returned, in which case they &MUST; be.</t>
+      unless a full response is sent, in which case they &MUST; be.</t>
    </list>
 </t>
@@ -1783 +1783 @@
   <iref primary="true" item="110 Response is Stale (warn code)" x:for-anchor=""/>
 <t>
-   A cache &SHOULD; include this whenever the returned response is stale.
+   A cache &SHOULD; include this whenever the sent response is stale.
 </t>
 </section>
@@ -1790 +1790 @@
   <iref primary="true" item="111 Revalidation Failed (warn code)" x:for-anchor=""/>
 <t>
-   A cache &SHOULD; include this when returning a stale response because an
+   A cache &SHOULD; include this when sending a stale response because an
    attempt to validate the response failed, due to an inability to reach
    the server.
@@ -2559 +2559 @@
 <x:ref>Expires</x:ref> = HTTP-date
 
-<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 8.1.1.1&gt;
+<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
 
 <x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;