Ignore:
Timestamp:
20/01/13 14:57:02 (8 years ago)
Author:
fielding@…
Message:

(editorial) move status codes to where they are used; no text changes

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r2142 r2143  
    475475
    476476
    477 <section title="Status Code Definitions" anchor="status.code.definitions">
     477<section title="Responses to a Range Request" anchor="range.response">
     478<section title="Response to a Single and Multiple Ranges Request">
     479<t>
     480   When an HTTP message includes the content of a single range (for
     481   example, a response to a request for a single range, or to a request
     482   for a set of ranges that overlap without any holes), this content is
     483   transmitted with a <x:ref>Content-Range</x:ref> header field, and a
     484   <x:ref>Content-Length</x:ref> header field showing the number of bytes
     485   actually transferred. For example,
     486</t>
     487<figure><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
     488HTTP/1.1 206 Partial Content
     489Date: Wed, 15 Nov 1995 06:25:24 GMT
     490Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     491Content-Range: bytes 21010-47021/47022
     492Content-Length: 26012
     493Content-Type: image/gif
     494</artwork></figure>
     495<t>
     496   When an HTTP message includes the content of multiple ranges (for
     497   example, a response to a request for multiple non-overlapping
     498   ranges), these are transmitted as a multipart message. The multipart
     499   media type used for this purpose is "multipart/byteranges" as defined
     500   in <xref target="internet.media.type.multipart.byteranges"/>.
     501</t>
     502<t>
     503   A server &MAY; combine requested ranges when those ranges are overlapping
     504   (see <xref target="overlapping.ranges"/>).
     505</t>
     506<t>
     507   A response to a request for a single range &MUST-NOT; be sent using the
     508   multipart/byteranges media type.  A response to a request for
     509   multiple ranges, whose result is a single range, &MAY; be sent as a
     510   multipart/byteranges media type with one part. A client that cannot
     511   decode a multipart/byteranges message &MUST-NOT; ask for multiple
     512   ranges in a single request.
     513</t>
     514<t>
     515   When a client asks for multiple ranges in one request, the
     516   server &SHOULD; send them in the order that they appeared in the
     517   request.
     518</t>
     519</section>
     520
    478521<section title="206 Partial Content" anchor="status.206">
    479522  <iref primary="true" item="206 Partial Content (status code)" x:for-anchor=""/>
     
    562605  </t>
    563606</x:note>
    564 </section>
    565 </section>
    566 
    567 <section title="Responses to a Range Request" anchor="range.response">
    568 <section title="Response to a Single and Multiple Ranges Request">
    569 <t>
    570    When an HTTP message includes the content of a single range (for
    571    example, a response to a request for a single range, or to a request
    572    for a set of ranges that overlap without any holes), this content is
    573    transmitted with a <x:ref>Content-Range</x:ref> header field, and a
    574    <x:ref>Content-Length</x:ref> header field showing the number of bytes
    575    actually transferred. For example,
    576 </t>
    577 <figure><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
    578 HTTP/1.1 206 Partial Content
    579 Date: Wed, 15 Nov 1995 06:25:24 GMT
    580 Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
    581 Content-Range: bytes 21010-47021/47022
    582 Content-Length: 26012
    583 Content-Type: image/gif
    584 </artwork></figure>
    585 <t>
    586    When an HTTP message includes the content of multiple ranges (for
    587    example, a response to a request for multiple non-overlapping
    588    ranges), these are transmitted as a multipart message. The multipart
    589    media type used for this purpose is "multipart/byteranges" as defined
    590    in <xref target="internet.media.type.multipart.byteranges"/>.
    591 </t>
    592 <t>
    593    A server &MAY; combine requested ranges when those ranges are overlapping
    594    (see <xref target="overlapping.ranges"/>).
    595 </t>
    596 <t>
    597    A response to a request for a single range &MUST-NOT; be sent using the
    598    multipart/byteranges media type.  A response to a request for
    599    multiple ranges, whose result is a single range, &MAY; be sent as a
    600    multipart/byteranges media type with one part. A client that cannot
    601    decode a multipart/byteranges message &MUST-NOT; ask for multiple
    602    ranges in a single request.
    603 </t>
    604 <t>
    605    When a client asks for multiple ranges in one request, the
    606    server &SHOULD; send them in the order that they appeared in the
    607    request.
    608 </t>
    609607</section>
    610608
Note: See TracChangeset for help on using the changeset viewer.