Ignore:
Timestamp:
Dec 15, 2012, 7:46:23 PM (7 years ago)
Author:
fielding@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2046 r2052  
    211211   <list>
    212212      <t>The time at which the origin server intends that a representation
    213       no longer be returned by a cache without further validation.</t>
     213      no longer be sent by a cache without further validation.</t>
    214214   </list>
    215215</t>
     
    471471   title="Constructing Responses from Caches">
    472472<t>
    473    For a presented request, a cache &MUST-NOT; return a stored response,
     473   For a presented request, a cache &MUST-NOT; send a stored response,
    474474   unless:
    475475   <list style="symbols">
     
    796796</t>
    797797<t>
    798    A cache &MUST-NOT; return a stale response if it is prohibited by an
     798   A cache &MUST-NOT; send a stale response if it is prohibited by an
    799799   explicit in-protocol directive (e.g., by a "no-store" or "no-cache" cache
    800800   directive, a "must-revalidate" cache-response-directive, or an applicable
     
    803803</t>
    804804<t>
    805    A cache &MUST-NOT; return stale responses unless it is disconnected
     805   A cache &MUST-NOT; send stale responses unless it is disconnected
    806806   (i.e., it cannot contact the origin server or otherwise find a forward
    807807   path) or doing so is explicitly allowed (e.g., by the max-stale request
     
    872872         response while attempting to validate a response, it can either
    873873         forward this response to the requesting client, or act as if the
    874          server failed to respond. In the latter case, it can return a
     874         server failed to respond. In the latter case, it can send a
    875875         previously stored response (see <xref
    876876         target="serving.stale.responses" />).
     
    10731073   the cache will either remove all stored responses related to the effective
    10741074   request URI, or will mark these as "invalid" and in need of a mandatory
    1075    validation before they can be returned in response to a subsequent request.
     1075   validation before they can be sent in response to a subsequent request.
    10761076</t>
    10771077<t>
     
    13621362   the origin server. This allows an origin server to prevent a cache from
    13631363   using it to satisfy a request without contacting it, even by caches that
    1364    have been configured to return stale responses.
     1364   have been configured to send stale responses.
    13651365</t>
    13661366<t>
     
    17571757      rectified by a validation (for example, a lossy compression of the
    17581758      representation) and &MUST-NOT; be deleted by a cache after validation,
    1759       unless a full response is returned, in which case they &MUST; be.</t>
     1759      unless a full response is sent, in which case they &MUST; be.</t>
    17601760   </list>
    17611761</t>
     
    17831783  <iref primary="true" item="110 Response is Stale (warn code)" x:for-anchor=""/>
    17841784<t>
    1785    A cache &SHOULD; include this whenever the returned response is stale.
     1785   A cache &SHOULD; include this whenever the sent response is stale.
    17861786</t>
    17871787</section>
     
    17901790  <iref primary="true" item="111 Revalidation Failed (warn code)" x:for-anchor=""/>
    17911791<t>
    1792    A cache &SHOULD; include this when returning a stale response because an
     1792   A cache &SHOULD; include this when sending a stale response because an
    17931793   attempt to validate the response failed, due to an inability to reach
    17941794   the server.
     
    25592559<x:ref>Expires</x:ref> = HTTP-date
    25602560
    2561 <x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 8.1.1.1&gt;
     2561<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
    25622562
    25632563<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
Note: See TracChangeset for help on using the changeset viewer.