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/p5-range.xml

    r2046 r2052  
    273273   header field, it &SHOULD-NOT; include other representation header fields.
    274274   Otherwise, the response &MUST; include all of the representation header
    275    fields that would have been returned with a <x:ref>200 (OK)</x:ref> response
     275   fields that would have been sent with a <x:ref>200 (OK)</x:ref> response
    276276   to the same request.
    277277</t>
     
    286286  <x:anchor-alias value="416 (Requested Range Not Satisfiable)"/>
    287287<t>
    288    A server &SHOULD; return a response with this status code if a request
     288   A server &SHOULD; send a response with this status code if a request
    289289   included a <x:ref>Range</x:ref> header field (<xref target="header.range"/>),
    290290   and none of the ranges-specifier values in this field overlap the current
     
    296296</t>
    297297<t>
    298    When this status code is returned for a byte-range request, the
     298   When this status code is sent for a byte-range request, the
    299299   response &SHOULD; include a <x:ref>Content-Range</x:ref> header field
    300300   specifying the current length of the representation (see <xref target="header.content-range"/>).
     
    359359<t>
    360360   When a client asks for multiple ranges in one request, the
    361    server &SHOULD; return them in the order that they appeared in the
     361   server &SHOULD; send them in the order that they appeared in the
    362362   request.
    363363</t>
     
    558558   syntactically invalid, or if it might be seen as a denial-of-service
    559559   attack), the server &SHOULD; treat the request as if the invalid <x:ref>Range</x:ref>
    560    header field did not exist. (Normally, this means return a <x:ref>200 (OK)</x:ref>
     560   header field did not exist. (Normally, this means send a <x:ref>200 (OK)</x:ref>
    561561   response containing the full representation).
    562562</t>
     
    690690   suffix-length, then the byte-range-set is satisfiable.
    691691   Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set
    692    is unsatisfiable, the server &SHOULD; return a response with a
     692   is unsatisfiable, the server &SHOULD; send a response with a
    693693   <x:ref>416 (Requested Range Not Satisfiable)</x:ref> status code. Otherwise, the server
    694    &SHOULD; return a response with a <x:ref>206 (Partial Content)</x:ref> status code
     694   &SHOULD; send a response with a <x:ref>206 (Partial Content)</x:ref> status code
    695695   containing the satisfiable ranges of the representation.
    696696</t>
     
    768768  <list style="symbols">
    769769     <t>The presence of a Range header field in an unconditional GET modifies
    770         what is returned if the GET is otherwise successful. In other
     770        what is sent if the GET is otherwise successful. In other
    771771        words, the response carries a status code of <x:ref>206 (Partial Content)</x:ref>
    772772        instead of <x:ref>200 (OK)</x:ref>.</t>
     
    776776        <x:ref>If-None-Match</x:ref>, or one or both of
    777777        <x:ref>If-Unmodified-Since</x:ref> and <x:ref>If-Match</x:ref>) modifies
    778         what is returned if the GET is otherwise successful and the
     778        what is sent if the GET is otherwise successful and the
    779779        condition is true. It does not affect the <x:ref>304 (Not Modified)</x:ref>
    780         response returned if the conditional is false.</t>
     780        response sent if the conditional is false.</t>
    781781  </list>
    782782</t>
     
    789789   If a proxy that supports ranges receives a Range request, forwards
    790790   the request to an inbound server, and receives an entire representation in
    791    reply, it &MAY; only return the requested range to its client.
     791   reply, it &MAY; only send the requested range to its client.
    792792</t>
    793793</section>
     
    13071307</t>
    13081308<t>
    1309   Servers are given more leeway in what they return to a range request,
     1309  Servers are given more leeway in what they send to a range request,
    13101310  in order to mitigate malicious (or just greedy) clients.
    13111311</t>
     
    13711371<x:ref>Content-Range</x:ref> = byte-content-range-spec / other-content-range-spec
    13721372
    1373 <x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 8.1.1.1&gt;
     1373<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
    13741374
    13751375<x:ref>If-Range</x:ref> = entity-tag / HTTP-date
Note: See TracChangeset for help on using the changeset viewer.