Ignore:
Timestamp:
Jul 28, 2009, 8:37:35 AM (10 years ago)
Author:
julian.reschke@…
Message:

update collected ABNFs

File:
1 edited

Legend:

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

    r647 r648  
    371371      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
    372372      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    373       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.439, 2009-06-09 18:43:39, XSLT vendor: SAXON 8.9.0.4 from Saxonica http://www.saxonica.com/">
     373      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.439, 2009-06-09 18:43:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    374374      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    375375      <meta name="DC.Creator" content="Fielding, R.">
     
    758758      <p id="rfc.section.5.2.p.11">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.
    759759      </p>
    760       <p id="rfc.section.5.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
     760      <p id="rfc.section.5.2.p.12">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.
    761761      </p>
    762762      <p id="rfc.section.5.2.p.13">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
     
    10151015         non-overlapping ranges), these are transmitted as a multipart message-body (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-5.1">Section 5.1</a>). The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
    10161016      </p>
    1017       <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
     1017      <div class="note">
     1018         <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
     1019         </p>
     1020      </div>
     1021      <p id="rfc.section.A.p.3">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
    10181022         required boundary parameter specifies the boundary string used to separate each body-part.
    10191023      </p>
    1020       <p id="rfc.section.A.p.3"> </p>
     1024      <p id="rfc.section.A.p.4"> </p>
    10211025      <dl>
    10221026         <dt>Type name:</dt>
     
    10751079  ...the second range
    10761080  --THIS_STRING_SEPARATES--
    1077 </pre><p id="rfc.section.A.p.5">Notes: </p>
     1081</pre><div id="rfc.figure.u.25"></div>
     1082      <p>Other example:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
     1083  Date: Tue, 14 Nov 1995 06:25:24 GMT
     1084  Last-Modified: Tue, 14 July 04:58:08 GMT
     1085  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
     1086 
     1087  --THIS_STRING_SEPARATES
     1088  Content-type: video/example
     1089  Content-range: exampleunit 1.2-4.3/25
     1090 
     1091  ...the first range...
     1092  --THIS_STRING_SEPARATES
     1093  Content-type: video/example
     1094  Content-range: exampleunit 11.2-14.3/25
     1095 
     1096  ...the second range
     1097  --THIS_STRING_SEPARATES--
     1098</pre> <p id="rfc.section.A.p.7">Notes: </p>
    10781099      <ol>
    10791100         <li>Additional CRLFs may precede the first boundary string in the entity.</li>
     
    11061127      </p>
    11071128      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1108       <div id="rfc.figure.u.25"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
     1129      <div id="rfc.figure.u.26"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
    11091130<a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> = acceptable-ranges
    11101131
     
    11581179
    11591180<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
    1160 </pre> <div id="rfc.figure.u.26"></div>
     1181</pre> <div id="rfc.figure.u.27"></div>
    11611182      <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
    11621183; Content-Range defined but not used
     
    12371258      <ul>
    12381259         <li>Fixed discrepancy in the If-Range definition about allowed validators.</li>
     1260         <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/150">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/150</a>&gt;: "multipart/byteranges for custom range units"
     1261         </li>
    12391262         <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/151">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/151</a>&gt;: "range unit missing from other-ranges-specifier in Range header"
    12401263         </li>
Note: See TracChangeset for help on using the changeset viewer.