Ignore:
Timestamp:
Oct 27, 2011, 1:13:52 PM (8 years ago)
Author:
ylafon@…
Message:

regen after [1459]

File:
1 edited

Legend:

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

    r1457 r1460  
    790790         selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
    791791      </p>
    792       <p id="rfc.section.5.2.p.8">Examples of byte-content-range-spec values, assuming that the representation contains a total of 1234 bytes: </p>
     792      <p id="rfc.section.5.2.p.8">The "Content-Range" header field has no meaning for status codes that does not explicitly describe its semantic. Currently,
     793         only status codes 206 (Partial Content) and 416 (Requested range not satisfiable) describe the meaning of this header field.
     794      </p>
     795      <p id="rfc.section.5.2.p.9">Examples of byte-content-range-spec values, assuming that the representation contains a total of 1234 bytes: </p>
    793796      <ul>
    794797         <li>The first 500 bytes:
     
    805808</pre> </li>
    806809      </ul>
    807       <p id="rfc.section.5.2.p.9">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
     810      <p id="rfc.section.5.2.p.10">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
    808811         a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header field,
    809812         and a Content-Length header field showing the number of bytes actually transferred. For example,
     
    815818  Content-Length: 26012
    816819  Content-Type: image/gif
    817 </pre><p id="rfc.section.5.2.p.11">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
     820</pre><p id="rfc.section.5.2.p.12">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
    818821         ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
    819822         as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
    820823      </p>
    821       <p id="rfc.section.5.2.p.12">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
    822       </p>
    823       <p id="rfc.section.5.2.p.13">When a client requests multiple ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
    824       </p>
    825       <p id="rfc.section.5.2.p.14">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
     824      <p id="rfc.section.5.2.p.13">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
     825      </p>
     826      <p id="rfc.section.5.2.p.14">When a client requests multiple ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
     827      </p>
     828      <p id="rfc.section.5.2.p.15">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
    826829         the full representation).
    827830      </p>
    828       <p id="rfc.section.5.2.p.15">If the server receives a request (other than one including an If-Range header field) with an unsatisfiable Range header field
     831      <p id="rfc.section.5.2.p.16">If the server receives a request (other than one including an If-Range header field) with an unsatisfiable Range header field
    829832         (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
    830833         resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>).
    831834      </p>
    832       <div class="note" id="rfc.section.5.2.p.16">
     835      <div class="note" id="rfc.section.5.2.p.17">
    833836         <p> <b>Note:</b> Clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
    834837            an unsatisfiable Range header field, since not all servers implement this header field.
     
    14251428         </li>
    14261429         <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/319">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/319</a>&gt;: "case sensitivity of ranges in p5"
     1430         </li>
     1431         <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/301">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/301</a>&gt;: "Content-Range on responses other than 206"
    14271432         </li>
    14281433      </ul>
Note: See TracChangeset for help on using the changeset viewer.