Ignore:
Timestamp:
25/09/13 13:01:17 (7 years ago)
Author:
julian.reschke@…
Message:

Update to latest version of rfc2629.xslt

File:
1 edited

Legend:

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

    r2414 r2418  
    106106body {
    107107  color: black;
    108   font-family: verdana, helvetica, arial, sans-serif;
    109   font-size: 10pt;
     108  font-family: cambria, helvetica, arial, sans-serif;
     109  font-size: 11pt;
    110110  margin-right: 2em;
    111111}
     
    132132}
    133133h1 {
    134   font-size: 14pt;
     134  font-size: 130%;
    135135  line-height: 21pt;
    136136  page-break-after: avoid;
     
    139139  page-break-before: always;
    140140}
    141 h1 a {
    142   color: #333333;
    143 }
    144141h2 {
    145   font-size: 12pt;
     142  font-size: 120%;
    146143  line-height: 15pt;
    147144  page-break-after: avoid;
    148145}
    149146h3, h4, h5, h6 {
    150   font-size: 10pt;
     147  font-size: 110%;
    151148  page-break-after: avoid;
    152149}
    153 h2 a, h3 a, h4 a, h5 a, h6 a {
     150h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    154151  color: black;
    155152}
     
    248245  caption-side: bottom;
    249246  font-weight: bold;
    250   font-size: 9pt;
     247  font-size: 10pt;
    251248  margin-top: .5em;
    252249}
     
    255252  border-spacing: 1px;
    256253  width: 95%;
    257   font-size: 10pt;
     254  font-size: 11pt;
    258255  color: white;
    259256}
     
    288285  line-height: 150%;
    289286  font-weight: bold;
    290   font-size: 10pt;
    291287  margin-left: 0em;
    292288}
     
    294290  line-height: normal;
    295291  font-weight: normal;
    296   font-size: 9pt;
     292  font-size: 10pt;
    297293  margin-left: 0em;
    298294}
     
    302298ul p {
    303299  margin-left: 0em;
     300}
     301.title, .filename, h1, h2, h3, h4 {
     302  font-family: candara, helvetica, arial, sans-serif;
     303}
     304samp, tt, code, pre {
     305  font: consolas, monospace;
    304306}
    305307ul.ind, ul.ind ul {
     
    341343  font-weight: bold;
    342344  text-align: center;
    343   font-size: 9pt;
     345  font-size: 10pt;
    344346}
    345347.filename {
    346348  color: #333333;
     349  font-size: 75%;
    347350  font-weight: bold;
    348   font-size: 12pt;
    349351  line-height: 21pt;
    350352  text-align: center;
     
    360362}
    361363.title {
    362   color: #990000;
    363   font-size: 18pt;
     364  color: green;
     365  font-size: 150%;
    364366  line-height: 18pt;
    365367  font-weight: bold;
     
    367369  margin-top: 36pt;
    368370}
    369 .vcardline {
    370   display: block;
    371 }
    372371.warning {
    373   font-size: 14pt;
     372  font-size: 130%;
    374373  background-color: yellow;
    375374}
     
    414413    background-color: white;
    415414    vertical-align: top;
    416     font-size: 12pt;
     415    font-size: 110%;
    417416  }
    418417
     
    446445  }
    447446  @bottom-center {
    448        content: "Expires March 28, 2014";
     447       content: "Expires March 29, 2014";
    449448  }
    450449  @bottom-right {
     
    483482      <link href="p4-conditional.html" rel="prev">
    484483      <link href="p6-cache.html" rel="next">
    485       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.599, 2013/08/29 10:34:28, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     484      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.603, 2013/09/18 20:22:25, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    486485      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    487486      <meta name="dct.creator" content="Fielding, R.">
     
    489488      <meta name="dct.creator" content="Reschke, J. F.">
    490489      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    491       <meta name="dct.issued" scheme="ISO8601" content="2013-09-24">
     490      <meta name="dct.issued" scheme="ISO8601" content="2013-09-25">
    492491      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    493492      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
     
    515514            </tr>
    516515            <tr>
    517                <td class="left">Expires: March 28, 2014</td>
     516               <td class="left">Expires: March 29, 2014</td>
    518517               <td class="right">J. Reschke, Editor</td>
    519518            </tr>
     
    524523            <tr>
    525524               <td class="left"></td>
    526                <td class="right">September 24, 2013</td>
     525               <td class="right">September 25, 2013</td>
    527526            </tr>
    528527         </tbody>
     
    540539      <p>The changes in this draft are summarized in <a href="#changes.since.24" title="Since draft-ietf-httpbis-p5-range-24">Appendix&nbsp;E.6</a>.
    541540      </p>
    542       <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    543       <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
    544       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
    545          working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
    546       </p>
    547       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    548          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    549          in progress”.
    550       </p>
    551       <p>This Internet-Draft will expire on March 28, 2014.</p>
    552       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    553       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    554       <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
    555          and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
    556          text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
    557          BSD License.
    558       </p>
    559       <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
    560          10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
    561          allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
    562          controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
    563          works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
    564          it into languages other than English.
    565       </p>
     541      <div id="rfc.status">
     542         <h1><a href="#rfc.status">Status of This Memo</a></h1>
     543         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     544         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
     545            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
     546         </p>
     547         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     548            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     549            in progress”.
     550         </p>
     551         <p>This Internet-Draft will expire on March 29, 2014.</p>
     552      </div>
     553      <div id="rfc.copyrightnotice">
     554         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     555         <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     556         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
     557            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     558            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
     559            BSD License.
     560         </p>
     561         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     562            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     563            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     564            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     565            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     566            it into languages other than English.
     567         </p>
     568      </div>
    566569      <hr class="noprint">
    567570      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
     
    626629         <li><a href="#rfc.index">Index</a></li>
    627630      </ul>
    628       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    629       <p id="rfc.section.1.p.1">Hypertext Transfer Protocol (HTTP) clients often encounter interrupted data transfers as a result of canceled requests or
    630          dropped connections. When a client has stored a partial representation, it is desirable to request the remainder of that representation
    631          in a subsequent request rather than transfer the entire representation. Likewise, devices with limited local storage might
    632          benefit from being able to request only a subset of a larger representation, such as a single page of a very large document,
    633          or the dimensions of an embedded image.
    634       </p>
    635       <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type. Range requests
    636          are an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so that recipients not implementing this feature (or not supporting it for the target resource)
    637          can respond as if it is a normal GET request without impacting interoperability. Partial responses are indicated by a distinct
    638          status code to not be mistaken for full responses by caches that might not implement the feature.
    639       </p>
    640       <p id="rfc.section.1.p.3">Although the range request mechanism is designed to allow for extensible range types, this specification only defines requests
    641          for byte ranges.
    642       </p>
    643       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="conformance" href="#conformance">Conformance and Error Handling</a></h2>
    644       <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
    645          in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    646       </p>
    647       <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    648       </p>
    649       <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    650       <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;C</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF with the list rule expanded.
    651       </p>
    652       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
    653       <p id="rfc.section.2.p.1">A representation can be partitioned into subranges according to various structural units, depending on the structure inherent
    654          in the representation's media type. This "<dfn>range unit</dfn>" is used in the <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> (<a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;2.3</a>) response header field to advertise support for range requests, the <a href="#header.range" class="smpl">Range</a> (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;3.1</a>) request header field to delineate the parts of a representation that are requested, and the <a href="#header.content-range" class="smpl">Content-Range</a> (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;4.2</a>) payload header field to describe which part of a representation is being transferred.
    655       </p>
    656       <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#range.units" class="smpl">range-unit</a>       = <a href="#byte.ranges" class="smpl">bytes-unit</a> / <a href="#range.units.other" class="smpl">other-range-unit</a>
    657 </pre><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h2>
    658       <p id="rfc.section.2.1.p.1">Since representation data is transferred in payloads as a sequence of octets, a byte range is a meaningful substructure for
    659          any representation transferable over HTTP (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). We define the "bytes" range unit for expressing subranges of the data's octet sequence.
    660       </p>
    661       <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#byte.ranges" class="smpl">bytes-unit</a>       = "bytes"
     631      <div id="introduction">
     632         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     633         <p id="rfc.section.1.p.1">Hypertext Transfer Protocol (HTTP) clients often encounter interrupted data transfers as a result of canceled requests or
     634            dropped connections. When a client has stored a partial representation, it is desirable to request the remainder of that representation
     635            in a subsequent request rather than transfer the entire representation. Likewise, devices with limited local storage might
     636            benefit from being able to request only a subset of a larger representation, such as a single page of a very large document,
     637            or the dimensions of an embedded image.
     638         </p>
     639         <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type. Range requests
     640            are an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so that recipients not implementing this feature (or not supporting it for the target resource)
     641            can respond as if it is a normal GET request without impacting interoperability. Partial responses are indicated by a distinct
     642            status code to not be mistaken for full responses by caches that might not implement the feature.
     643         </p>
     644         <p id="rfc.section.1.p.3">Although the range request mechanism is designed to allow for extensible range types, this specification only defines requests
     645            for byte ranges.
     646         </p>
     647         <div id="conformance">
     648            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#conformance">Conformance and Error Handling</a></h2>
     649            <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
     650               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
     651            </p>
     652            <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     653            </p>
     654         </div>
     655         <div id="notation">
     656            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     657            <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 7</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;C</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF with the list rule expanded.
     658            </p>
     659         </div>
     660      </div>
     661      <div id="range.units">
     662         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#range.units">Range Units</a></h1>
     663         <p id="rfc.section.2.p.1">A representation can be partitioned into subranges according to various structural units, depending on the structure inherent
     664            in the representation's media type. This "<dfn>range unit</dfn>" is used in the <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> (<a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;2.3</a>) response header field to advertise support for range requests, the <a href="#header.range" class="smpl">Range</a> (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;3.1</a>) request header field to delineate the parts of a representation that are requested, and the <a href="#header.content-range" class="smpl">Content-Range</a> (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;4.2</a>) payload header field to describe which part of a representation is being transferred.
     665         </p>
     666         <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#range.units" class="smpl">range-unit</a>       = <a href="#byte.ranges" class="smpl">bytes-unit</a> / <a href="#range.units.other" class="smpl">other-range-unit</a>
     667</pre><div id="byte.ranges">
     668            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#byte.ranges">Byte Ranges</a></h2>
     669            <p id="rfc.section.2.1.p.1">Since representation data is transferred in payloads as a sequence of octets, a byte range is a meaningful substructure for
     670               any representation transferable over HTTP (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). We define the "bytes" range unit for expressing subranges of the data's octet sequence.
     671            </p>
     672            <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#byte.ranges" class="smpl">bytes-unit</a>       = "bytes"
    662673</pre><div id="rule.ranges-specifier">
    663          <p id="rfc.section.2.1.p.3">        A byte range request can specify a single range of bytes, or a set of ranges within a single representation.</p>
    664       </div>
    665       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#byte.ranges" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
     674               <p id="rfc.section.2.1.p.3">        A byte range request can specify a single range of bytes, or a set of ranges within a single representation.</p>
     675            </div>
     676            <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#byte.ranges" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
    666677  <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>  = 1#( <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> / <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> )
    667678  <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" [ <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> ]
     
    669680  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    670681</pre><p id="rfc.section.2.1.p.5">The <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value in a <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> gives the byte-offset of the first byte in a range. The <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets
    671          start at zero.
    672       </p>
    673       <p id="rfc.section.2.1.p.6">Examples of <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> values:
    674       </p>
    675       <ul>
    676          <li>The first 500 bytes (byte offsets 0-499, inclusive):
    677             <div id="rfc.figure.u.4"></div><pre class="text">  bytes=0-499
     682               start at zero.
     683            </p>
     684            <p id="rfc.section.2.1.p.6">Examples of <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> values:
     685            </p>
     686            <ul>
     687               <li>The first 500 bytes (byte offsets 0-499, inclusive):
     688                  <div id="rfc.figure.u.4"></div><pre class="text">  bytes=0-499
    678689</pre> </li>
    679          <li>The second 500 bytes (byte offsets 500-999, inclusive):
    680             <div id="rfc.figure.u.5"></div><pre class="text">  bytes=500-999
     690               <li>The second 500 bytes (byte offsets 500-999, inclusive):
     691                  <div id="rfc.figure.u.5"></div><pre class="text">  bytes=500-999
    681692</pre> </li>
    682       </ul>
    683       <p id="rfc.section.2.1.p.7">A <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> is invalid if the <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value is present and less than the <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>.
    684       </p>
    685       <p id="rfc.section.2.1.p.8">A client can limit the number of bytes requested without knowing the size of the selected representation. If the <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value is absent, or if the value is greater than or equal to the current length of the representation data, the byte range
    686          is interpreted as the remainder of the representation (i.e., the server replaces the value of <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> with a value that is one less than the current length of the selected representation).
    687       </p>
    688       <p id="rfc.section.2.1.p.9">A client can request the last N bytes of the selected representation using a <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a>.
    689       </p>
    690       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
     693            </ul>
     694            <p id="rfc.section.2.1.p.7">A <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> is invalid if the <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value is present and less than the <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>.
     695            </p>
     696            <p id="rfc.section.2.1.p.8">A client can limit the number of bytes requested without knowing the size of the selected representation. If the <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value is absent, or if the value is greater than or equal to the current length of the representation data, the byte range
     697               is interpreted as the remainder of the representation (i.e., the server replaces the value of <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> with a value that is one less than the current length of the selected representation).
     698            </p>
     699            <p id="rfc.section.2.1.p.9">A client can request the last N bytes of the selected representation using a <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a>.
     700            </p>
     701            <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
    691702  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    692703</pre><p id="rfc.section.2.1.p.11">If the selected representation is shorter than the specified <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, the entire representation is used.
    693       </p>
    694       <p id="rfc.section.2.1.p.12">Additional examples, assuming a representation of length 10000: </p>
    695       <ul>
    696          <li>The final 500 bytes (byte offsets 9500-9999, inclusive):
    697             <div id="rfc.figure.u.7"></div><pre class="text">  bytes=-500
     704            </p>
     705            <p id="rfc.section.2.1.p.12">Additional examples, assuming a representation of length 10000: </p>
     706            <ul>
     707               <li>The final 500 bytes (byte offsets 9500-9999, inclusive):
     708                  <div id="rfc.figure.u.7"></div><pre class="text">  bytes=-500
    698709</pre> Or: <div id="rfc.figure.u.8"></div><pre class="text">  bytes=9500-
    699710</pre> </li>
    700          <li>The first and last bytes only (bytes 0 and 9999):
    701             <div id="rfc.figure.u.9"></div><pre class="text">  bytes=0-0,-1
     711               <li>The first and last bytes only (bytes 0 and 9999):
     712                  <div id="rfc.figure.u.9"></div><pre class="text">  bytes=0-0,-1
    702713</pre> </li>
    703          <li>Other valid (but not canonical) specifications of the second 500 bytes (byte offsets 500-999, inclusive):
    704             <div id="rfc.figure.u.10"></div><pre class="text">  bytes=500-600,601-999
     714               <li>Other valid (but not canonical) specifications of the second 500 bytes (byte offsets 500-999, inclusive):
     715                  <div id="rfc.figure.u.10"></div><pre class="text">  bytes=500-600,601-999
    705716  bytes=500-700,601-999
    706717</pre> </li>
    707       </ul>
    708       <p id="rfc.section.2.1.p.13">If a valid <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> includes at least one <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> with a <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> that is less than the current length of the representation, or at least one <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> with a non-zero <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, then the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is satisfiable. Otherwise, the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is unsatisfiable.
    709       </p>
    710       <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought
    711          to anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
    712       </p>
    713       <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="range.units.other" href="#range.units.other">Other Range Units</a></h2>
    714       <p id="rfc.section.2.2.p.1">Range units are intended to be extensible. New range units ought to be registered with IANA, as defined in <a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;5.1</a>.
    715       </p>
    716       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.13"></span>  <a href="#range.units.other" class="smpl">other-range-unit</a> = <a href="#imported.abnf" class="smpl">token</a>
    717 </pre><div id="rfc.iref.a.1"></div>
    718       <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2>
    719       <p id="rfc.section.2.3.p.1">The "Accept-Ranges" header field allows a server to indicate that it supports range requests for the target resource.</p>
    720       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
     718            </ul>
     719            <p id="rfc.section.2.1.p.13">If a valid <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> includes at least one <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> with a <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> that is less than the current length of the representation, or at least one <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> with a non-zero <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, then the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is satisfiable. Otherwise, the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is unsatisfiable.
     720            </p>
     721            <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought
     722               to anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
     723            </p>
     724         </div>
     725         <div id="range.units.other">
     726            <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#range.units.other">Other Range Units</a></h2>
     727            <p id="rfc.section.2.2.p.1">Range units are intended to be extensible. New range units ought to be registered with IANA, as defined in <a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;5.1</a>.
     728            </p>
     729            <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.13"></span>  <a href="#range.units.other" class="smpl">other-range-unit</a> = <a href="#imported.abnf" class="smpl">token</a>
     730</pre></div>
     731         <div id="header.accept-ranges">
     732            <div id="rfc.iref.a.1"></div>
     733            <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></h2>
     734            <p id="rfc.section.2.3.p.1">The "Accept-Ranges" header field allows a server to indicate that it supports range requests for the target resource.</p>
     735            <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
    721736  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
    722737</pre><p id="rfc.section.2.3.p.3">An origin server that supports byte-range requests for a given target resource <em class="bcp14">MAY</em> send
    723       </p>
    724       <div id="rfc.figure.u.13"></div><pre class="text">  Accept-Ranges: bytes
     738            </p>
     739            <div id="rfc.figure.u.13"></div><pre class="text">  Accept-Ranges: bytes
    725740</pre><p id="rfc.section.2.3.p.5">to indicate what range units are supported. A client <em class="bcp14">MAY</em> generate range requests without having received this header field for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
    726       </p>
    727       <p id="rfc.section.2.3.p.6">A server that does not support any kind of range request for the target resource resource <em class="bcp14">MAY</em> send
    728       </p>
    729       <div id="rfc.figure.u.14"></div><pre class="text">  Accept-Ranges: none
     741            </p>
     742            <p id="rfc.section.2.3.p.6">A server that does not support any kind of range request for the target resource resource <em class="bcp14">MAY</em> send
     743            </p>
     744            <div id="rfc.figure.u.14"></div><pre class="text">  Accept-Ranges: none
    730745</pre><p id="rfc.section.2.3.p.8">to advise the client not to attempt a range request.</p>
    731       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="range.requests" href="#range.requests">Range Requests</a></h1>
    732       <div id="rfc.iref.r.1"></div>
    733       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.range" href="#header.range">Range</a></h2>
    734       <p id="rfc.section.3.1.p.1">The "Range" header field on a GET request modifies the method semantics to request transfer of only one or more subranges
    735          of the selected representation data, rather than the entire selected representation data.
    736       </p>
    737       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  <a href="#header.range" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#header.range" class="smpl">other-ranges-specifier</a>
     746         </div>
     747      </div>
     748      <div id="range.requests">
     749         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#range.requests">Range Requests</a></h1>
     750         <div id="header.range">
     751            <div id="rfc.iref.r.1"></div>
     752            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.range">Range</a></h2>
     753            <p id="rfc.section.3.1.p.1">The "Range" header field on a GET request modifies the method semantics to request transfer of only one or more subranges
     754               of the selected representation data, rather than the entire selected representation data.
     755            </p>
     756            <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  <a href="#header.range" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#header.range" class="smpl">other-ranges-specifier</a>
    738757  <a href="#header.range" class="smpl">other-ranges-specifier</a> = <a href="#range.units.other" class="smpl">other-range-unit</a> "=" <a href="#header.range" class="smpl">other-range-set</a>
    739758  <a href="#header.range" class="smpl">other-range-set</a> = 1*<a href="#imported.abnf" class="smpl">CHAR</a>
    740759</pre><p id="rfc.section.3.1.p.3">A server <em class="bcp14">MAY</em> ignore the Range header field. However, origin servers and intermediate caches ought to support byte ranges when possible,
    741          since Range supports efficient recovery from partially failed transfers and partial retrieval of large representations. A
    742          server <em class="bcp14">MUST</em> ignore a Range header field received with a request method other than GET.
    743       </p>
    744       <p id="rfc.section.3.1.p.4">An origin server <em class="bcp14">MUST</em> ignore a Range header field that contains a range unit it does not understand. A proxy <em class="bcp14">MAY</em> discard a Range header field that contains a range unit it does not understand.
    745       </p>
    746       <p id="rfc.section.3.1.p.5">A server that supports range requests <em class="bcp14">MAY</em> ignore or reject a <a href="#header.range" class="smpl">Range</a> header field that consists of more than two overlapping ranges, or a set of many small ranges that are not listed in ascending
    747          order, since both are indications of either a broken client or a deliberate denial of service attack (<a href="#overlapping.ranges" title="Denial of Service Attacks using Range">Section&nbsp;6.1</a>). A client <em class="bcp14">SHOULD NOT</em> request multiple ranges that are inherently less efficient to process and transfer than a single range that encompasses the
    748          same data.
    749       </p>
    750       <p id="rfc.section.3.1.p.6">A client that is requesting multiple ranges <em class="bcp14">SHOULD</em> list those ranges in ascending order (the order in which they would typically be received in a complete representation) unless
    751          there is a specific need to request a later part earlier. For example, a user agent processing a large representation with
    752          an internal catalog of parts might need to request later parts first, particularly if the representation consists of pages
    753          stored in reverse order and the user agent wishes to transfer one page at a time.
    754       </p>
    755       <p id="rfc.section.3.1.p.7">The Range header field is evaluated after evaluating the precondition header fields defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, and only if the result in absence of the Range header field would be a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. In other words, Range is ignored when a conditional GET would result in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response.
    756       </p>
    757       <p id="rfc.section.3.1.p.8">The If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;3.2</a>) can be used as a precondition to applying the Range header field.
    758       </p>
    759       <p id="rfc.section.3.1.p.9">If all of the preconditions are true, the server supports the Range header field for the target resource, and the specified
    760          range(s) are valid and satisfiable (as defined in <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;2.1</a>), the server <em class="bcp14">SHOULD</em> send a <a href="#status.206" class="smpl">206 (Partial Content)</a> response with a payload containing one or more partial representations that correspond to the satisfiable ranges requested,
    761          as defined in <a href="#range.response" title="Responses to a Range Request">Section&nbsp;4</a>.
    762       </p>
    763       <p id="rfc.section.3.1.p.10">If all of the preconditions are true, the server supports the Range header field for the target resource, and the specified
    764          range(s) are invalid or unsatisfiable, the server <em class="bcp14">SHOULD</em> send a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response.
    765       </p>
    766       <div id="rfc.iref.i.1"></div>
    767       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.if-range" href="#header.if-range">If-Range</a></h2>
    768       <p id="rfc.section.3.2.p.1">If a client has a partial copy of a representation and wishes to have an up-to-date copy of the entire representation, it
    769          could use the <a href="#header.range" class="smpl">Range</a> header field with a conditional GET (using either or both of <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> and <a href="p4-conditional.html#header.if-match" class="smpl">If-Match</a>.) However, if the precondition fails because the representation has been modified, the client would then have to make a second
    770          request to obtain the entire current representation.
    771       </p>
    772       <p id="rfc.section.3.2.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is: if the representation
    773          is unchanged, send me the part(s) that I am requesting in Range; otherwise, send me the entire representation.
    774       </p>
    775       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#imported.abnf" class="smpl">entity-tag</a> / <a href="#imported.abnf" class="smpl">HTTP-date</a>
     760               since Range supports efficient recovery from partially failed transfers and partial retrieval of large representations. A
     761               server <em class="bcp14">MUST</em> ignore a Range header field received with a request method other than GET.
     762            </p>
     763            <p id="rfc.section.3.1.p.4">An origin server <em class="bcp14">MUST</em> ignore a Range header field that contains a range unit it does not understand. A proxy <em class="bcp14">MAY</em> discard a Range header field that contains a range unit it does not understand.
     764            </p>
     765            <p id="rfc.section.3.1.p.5">A server that supports range requests <em class="bcp14">MAY</em> ignore or reject a <a href="#header.range" class="smpl">Range</a> header field that consists of more than two overlapping ranges, or a set of many small ranges that are not listed in ascending
     766               order, since both are indications of either a broken client or a deliberate denial of service attack (<a href="#overlapping.ranges" title="Denial of Service Attacks using Range">Section&nbsp;6.1</a>). A client <em class="bcp14">SHOULD NOT</em> request multiple ranges that are inherently less efficient to process and transfer than a single range that encompasses the
     767               same data.
     768            </p>
     769            <p id="rfc.section.3.1.p.6">A client that is requesting multiple ranges <em class="bcp14">SHOULD</em> list those ranges in ascending order (the order in which they would typically be received in a complete representation) unless
     770               there is a specific need to request a later part earlier. For example, a user agent processing a large representation with
     771               an internal catalog of parts might need to request later parts first, particularly if the representation consists of pages
     772               stored in reverse order and the user agent wishes to transfer one page at a time.
     773            </p>
     774            <p id="rfc.section.3.1.p.7">The Range header field is evaluated after evaluating the precondition header fields defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, and only if the result in absence of the Range header field would be a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. In other words, Range is ignored when a conditional GET would result in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response.
     775            </p>
     776            <p id="rfc.section.3.1.p.8">The If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;3.2</a>) can be used as a precondition to applying the Range header field.
     777            </p>
     778            <p id="rfc.section.3.1.p.9">If all of the preconditions are true, the server supports the Range header field for the target resource, and the specified
     779               range(s) are valid and satisfiable (as defined in <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;2.1</a>), the server <em class="bcp14">SHOULD</em> send a <a href="#status.206" class="smpl">206 (Partial Content)</a> response with a payload containing one or more partial representations that correspond to the satisfiable ranges requested,
     780               as defined in <a href="#range.response" title="Responses to a Range Request">Section&nbsp;4</a>.
     781            </p>
     782            <p id="rfc.section.3.1.p.10">If all of the preconditions are true, the server supports the Range header field for the target resource, and the specified
     783               range(s) are invalid or unsatisfiable, the server <em class="bcp14">SHOULD</em> send a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response.
     784            </p>
     785         </div>
     786         <div id="header.if-range">
     787            <div id="rfc.iref.i.1"></div>
     788            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.if-range">If-Range</a></h2>
     789            <p id="rfc.section.3.2.p.1">If a client has a partial copy of a representation and wishes to have an up-to-date copy of the entire representation, it
     790               could use the <a href="#header.range" class="smpl">Range</a> header field with a conditional GET (using either or both of <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> and <a href="p4-conditional.html#header.if-match" class="smpl">If-Match</a>.) However, if the precondition fails because the representation has been modified, the client would then have to make a second
     791               request to obtain the entire current representation.
     792            </p>
     793            <p id="rfc.section.3.2.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is: if the representation
     794               is unchanged, send me the part(s) that I am requesting in Range; otherwise, send me the entire representation.
     795            </p>
     796            <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#imported.abnf" class="smpl">entity-tag</a> / <a href="#imported.abnf" class="smpl">HTTP-date</a>
    776797</pre><p id="rfc.section.3.2.p.4">A client <em class="bcp14">MUST NOT</em> generate an If-Range header field in a request that does not contain a <a href="#header.range" class="smpl">Range</a> header field. A server <em class="bcp14">MUST</em> ignore an If-Range header field received in a request that does not contain a <a href="#header.range" class="smpl">Range</a> header field. An origin server <em class="bcp14">MUST</em> ignore an If-Range header field received in a request for a target resource that does not support Range requests.
    777       </p>
    778       <p id="rfc.section.3.2.p.5">A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an entity-tag that is marked as weak. A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an <a href="#imported.abnf" class="smpl">HTTP-date</a> unless the client has no entity-tag for the corresponding representation and the date is a strong validator in the sense defined
    779          by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.
    780       </p>
    781       <p id="rfc.section.3.2.p.6">A server that evaluates an If-Range precondition <em class="bcp14">MUST</em> use the strong comparison function when comparing entity-tags (<a href="p4-conditional.html#entity.tag.comparison" title="Comparison">Section 2.3.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) and <em class="bcp14">MUST</em> evaluate the condition as false if an <a href="#imported.abnf" class="smpl">HTTP-date</a> validator is provided that is not a strong validator in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>. (A server can distinguish between a valid <a href="#imported.abnf" class="smpl">HTTP-date</a> and any form of entity-tag by examining the first two characters.)
    782       </p>
    783       <p id="rfc.section.3.2.p.7">If the validator given in the If-Range header field matches the current validator for the selected representation of the target
    784          resource, then the server <em class="bcp14">SHOULD</em> process the <a href="#header.range" class="smpl">Range</a> header field as requested. If the validator does not match, the server <em class="bcp14">MUST</em> ignore the <a href="#header.range" class="smpl">Range</a> header field.
    785       </p>
    786       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="range.response" href="#range.response">Responses to a Range Request</a></h1>
    787       <div id="rfc.iref.20"></div>
    788       <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h2>
    789       <p id="rfc.section.4.1.p.1">The <dfn>206 (Partial Content)</dfn> status code indicates that the server is successfully fulfilling a range request for the target resource by transferring one
    790          or more parts of the selected representation that correspond to the satisfiable ranges found in the request's <a href="#header.range" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;3.1</a>).
    791       </p>
    792       <p id="rfc.section.4.1.p.2">If a single part is being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field, describing what range of the selected representation is enclosed, and a payload consisting of the range. For
    793          example:
    794       </p>
    795       <div id="rfc.figure.u.17"></div><pre class="text">HTTP/1.1 206 Partial Content
     798            </p>
     799            <p id="rfc.section.3.2.p.5">A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an entity-tag that is marked as weak. A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an <a href="#imported.abnf" class="smpl">HTTP-date</a> unless the client has no entity-tag for the corresponding representation and the date is a strong validator in the sense defined
     800               by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.
     801            </p>
     802            <p id="rfc.section.3.2.p.6">A server that evaluates an If-Range precondition <em class="bcp14">MUST</em> use the strong comparison function when comparing entity-tags (<a href="p4-conditional.html#entity.tag.comparison" title="Comparison">Section 2.3.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) and <em class="bcp14">MUST</em> evaluate the condition as false if an <a href="#imported.abnf" class="smpl">HTTP-date</a> validator is provided that is not a strong validator in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>. (A server can distinguish between a valid <a href="#imported.abnf" class="smpl">HTTP-date</a> and any form of entity-tag by examining the first two characters.)
     803            </p>
     804            <p id="rfc.section.3.2.p.7">If the validator given in the If-Range header field matches the current validator for the selected representation of the target
     805               resource, then the server <em class="bcp14">SHOULD</em> process the <a href="#header.range" class="smpl">Range</a> header field as requested. If the validator does not match, the server <em class="bcp14">MUST</em> ignore the <a href="#header.range" class="smpl">Range</a> header field.
     806            </p>
     807         </div>
     808      </div>
     809      <div id="range.response">
     810         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#range.response">Responses to a Range Request</a></h1>
     811         <div id="status.206">
     812            <div id="rfc.iref.20"></div>
     813            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#status.206">206 Partial Content</a></h2>
     814            <p id="rfc.section.4.1.p.1">The <dfn>206 (Partial Content)</dfn> status code indicates that the server is successfully fulfilling a range request for the target resource by transferring one
     815               or more parts of the selected representation that correspond to the satisfiable ranges found in the request's <a href="#header.range" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;3.1</a>).
     816            </p>
     817            <p id="rfc.section.4.1.p.2">If a single part is being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field, describing what range of the selected representation is enclosed, and a payload consisting of the range. For
     818               example:
     819            </p>
     820            <div id="rfc.figure.u.17"></div><pre class="text">HTTP/1.1 206 Partial Content
    796821Date: Wed, 15 Nov 1995 06:25:24 GMT
    797822Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    802827... 26012 bytes of partial image data ...
    803828</pre><p id="rfc.section.4.1.p.4">If multiple parts are being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a "multipart/byteranges" payload, as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>, and a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field containing the multipart/byteranges media type and its required boundary parameter. To avoid confusion with single
    804          part responses, a server <em class="bcp14">MUST NOT</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field in the HTTP header section of a multiple part response (this field will be sent in each part instead).
    805       </p>
    806       <p id="rfc.section.4.1.p.5">Within the header area of each body part in the multipart payload, the server <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field corresponding to the range being enclosed in that body part. If the selected representation would have had a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, the server <em class="bcp14">SHOULD</em> generate that same <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> field in the header area of each body part. For example:
    807       </p>
    808       <div id="rfc.figure.u.18"></div><pre class="text">HTTP/1.1 206 Partial Content
     829               part responses, a server <em class="bcp14">MUST NOT</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field in the HTTP header section of a multiple part response (this field will be sent in each part instead).
     830            </p>
     831            <p id="rfc.section.4.1.p.5">Within the header area of each body part in the multipart payload, the server <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field corresponding to the range being enclosed in that body part. If the selected representation would have had a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, the server <em class="bcp14">SHOULD</em> generate that same <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> field in the header area of each body part. For example:
     832            </p>
     833            <div id="rfc.figure.u.18"></div><pre class="text">HTTP/1.1 206 Partial Content
    809834Date: Wed, 15 Nov 1995 06:25:24 GMT
    810835Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    824849--THIS_STRING_SEPARATES--
    825850</pre><p id="rfc.section.4.1.p.7">When multiple ranges are requested, a server <em class="bcp14">MAY</em> coalesce any of the ranges that overlap or that are separated by a gap that is smaller than the overhead of sending multiple
    826          parts, regardless of the order in which the corresponding byte-range-spec appeared in the received <a href="#header.range" class="smpl">Range</a> header field. Since the typical overhead between parts of a multipart/byteranges payload is around 80 bytes, depending on
    827          the selected representation's media type and the chosen boundary parameter length, it can be less efficient to transfer many
    828          small disjoint parts than it is to transfer the entire selected representation.
    829       </p>
    830       <p id="rfc.section.4.1.p.8">A server <em class="bcp14">MUST NOT</em> generate a multipart response to a request for a single range, since a client that does not request multiple parts might not
    831          support multipart responses. However, a server <em class="bcp14">MAY</em> generate a multipart/byteranges payload with only a single body part if multiple ranges were requested and only one range
    832          was found to be satisfiable or only one range remained after coalescing. A client that cannot process a multipart/byteranges
    833          response <em class="bcp14">MUST NOT</em> generate a request that asks for multiple ranges.
    834       </p>
    835       <p id="rfc.section.4.1.p.9">When a multipart response payload is generated, the server <em class="bcp14">SHOULD</em> send the parts in the same order that the corresponding byte-range-spec appeared in the received <a href="#header.range" class="smpl">Range</a> header field, excluding those ranges that were deemed unsatisfiable or that were coalesced into other ranges. A client that
    836          receives a multipart response <em class="bcp14">MUST</em> inspect the <a href="#header.content-range" class="smpl">Content-Range</a> header field present in each body part in order to determine which range is contained in that body part; a client cannot rely
    837          on receiving the same ranges that it requested, nor the same order that it requested.
    838       </p>
    839       <p id="rfc.section.4.1.p.10">When a 206 response is generated, the server <em class="bcp14">MUST</em> generate the following header fields, in addition to those required above, if the field would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request: <a href="p2-semantics.html#header.date" class="smpl">Date</a>, <a href="p6-cache.html#header.cache-control" class="smpl">Cache-Control</a>, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a>, <a href="p6-cache.html#header.expires" class="smpl">Expires</a>, <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a>, and <a href="p2-semantics.html#header.vary" class="smpl">Vary</a>.
    840       </p>
    841       <p id="rfc.section.4.1.p.11">If a 206 is generated in response to a request with an <a href="#header.if-range" class="smpl">If-Range</a> header field, the sender <em class="bcp14">SHOULD NOT</em> generate other representation header fields beyond those required above, because the client is understood to already have
    842          a prior response containing those header fields. Otherwise, the sender <em class="bcp14">MUST</em> generate all of the representation header fields that would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request.
    843       </p>
    844       <p id="rfc.section.4.1.p.12">A 206 response is cacheable unless otherwise indicated by explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
    845       </p>
    846       <div id="rfc.iref.c.1"></div>
    847       <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="header.content-range" href="#header.content-range">Content-Range</a></h2>
    848       <p id="rfc.section.4.2.p.1">The "Content-Range" header field is sent in a single part <a href="#status.206" class="smpl">206 (Partial Content)</a> response to indicate the partial range of the selected representation enclosed as the message payload, sent in each part of
    849          a multipart 206 response to indicate the range enclosed within each body part, and sent in <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> responses to provide information about the selected representation.
    850       </p>
    851       <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.content-range" class="smpl">Content-Range</a>       = <a href="#header.content-range" class="smpl">byte-content-range</a>
     851               parts, regardless of the order in which the corresponding byte-range-spec appeared in the received <a href="#header.range" class="smpl">Range</a> header field. Since the typical overhead between parts of a multipart/byteranges payload is around 80 bytes, depending on
     852               the selected representation's media type and the chosen boundary parameter length, it can be less efficient to transfer many
     853               small disjoint parts than it is to transfer the entire selected representation.
     854            </p>
     855            <p id="rfc.section.4.1.p.8">A server <em class="bcp14">MUST NOT</em> generate a multipart response to a request for a single range, since a client that does not request multiple parts might not
     856               support multipart responses. However, a server <em class="bcp14">MAY</em> generate a multipart/byteranges payload with only a single body part if multiple ranges were requested and only one range
     857               was found to be satisfiable or only one range remained after coalescing. A client that cannot process a multipart/byteranges
     858               response <em class="bcp14">MUST NOT</em> generate a request that asks for multiple ranges.
     859            </p>
     860            <p id="rfc.section.4.1.p.9">When a multipart response payload is generated, the server <em class="bcp14">SHOULD</em> send the parts in the same order that the corresponding byte-range-spec appeared in the received <a href="#header.range" class="smpl">Range</a> header field, excluding those ranges that were deemed unsatisfiable or that were coalesced into other ranges. A client that
     861               receives a multipart response <em class="bcp14">MUST</em> inspect the <a href="#header.content-range" class="smpl">Content-Range</a> header field present in each body part in order to determine which range is contained in that body part; a client cannot rely
     862               on receiving the same ranges that it requested, nor the same order that it requested.
     863            </p>
     864            <p id="rfc.section.4.1.p.10">When a 206 response is generated, the server <em class="bcp14">MUST</em> generate the following header fields, in addition to those required above, if the field would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request: <a href="p2-semantics.html#header.date" class="smpl">Date</a>, <a href="p6-cache.html#header.cache-control" class="smpl">Cache-Control</a>, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a>, <a href="p6-cache.html#header.expires" class="smpl">Expires</a>, <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a>, and <a href="p2-semantics.html#header.vary" class="smpl">Vary</a>.
     865            </p>
     866            <p id="rfc.section.4.1.p.11">If a 206 is generated in response to a request with an <a href="#header.if-range" class="smpl">If-Range</a> header field, the sender <em class="bcp14">SHOULD NOT</em> generate other representation header fields beyond those required above, because the client is understood to already have
     867               a prior response containing those header fields. Otherwise, the sender <em class="bcp14">MUST</em> generate all of the representation header fields that would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request.
     868            </p>
     869            <p id="rfc.section.4.1.p.12">A 206 response is cacheable unless otherwise indicated by explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
     870            </p>
     871         </div>
     872         <div id="header.content-range">
     873            <div id="rfc.iref.c.1"></div>
     874            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#header.content-range">Content-Range</a></h2>
     875            <p id="rfc.section.4.2.p.1">The "Content-Range" header field is sent in a single part <a href="#status.206" class="smpl">206 (Partial Content)</a> response to indicate the partial range of the selected representation enclosed as the message payload, sent in each part of
     876               a multipart 206 response to indicate the range enclosed within each body part, and sent in <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> responses to provide information about the selected representation.
     877            </p>
     878            <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.content-range" class="smpl">Content-Range</a>       = <a href="#header.content-range" class="smpl">byte-content-range</a>
    852879                      / <a href="#header.content-range" class="smpl">other-content-range</a>
    853880                         
     
    864891  <a href="#header.content-range" class="smpl">other-range-resp</a>    = *<a href="#imported.abnf" class="smpl">CHAR</a>
    865892</pre><p id="rfc.section.4.2.p.3">If a <a href="#status.206" class="smpl">206 (Partial Content)</a> response contains a <a href="#header.content-range" class="smpl">Content-Range</a> header field with a <a href="#range.units" class="smpl">range unit</a> (<a href="#range.units" title="Range Units">Section&nbsp;2</a>) that the recipient does not understand, the recipient <em class="bcp14">MUST NOT</em> attempt to recombine it with a stored representation. A proxy that receives such a message <em class="bcp14">SHOULD</em> forward it downstream.
    866       </p>
    867       <p id="rfc.section.4.2.p.4">For byte ranges, a sender <em class="bcp14">SHOULD</em> indicate the complete length of the representation from which the range has been extracted, unless the complete length is
    868          unknown or difficult to determine. An asterisk character ("*") in place of the complete-length indicates that the representation
    869          length was unknown when the header field was generated.
    870       </p>
    871       <p id="rfc.section.4.2.p.5">The following example illustrates when the complete length of the selected representation is known by the sender to be 1234
    872          bytes:
    873       </p>
    874       <div id="rfc.figure.u.20"></div><pre class="text">  Content-Range: bytes 42-1233/1234
     893            </p>
     894            <p id="rfc.section.4.2.p.4">For byte ranges, a sender <em class="bcp14">SHOULD</em> indicate the complete length of the representation from which the range has been extracted, unless the complete length is
     895               unknown or difficult to determine. An asterisk character ("*") in place of the complete-length indicates that the representation
     896               length was unknown when the header field was generated.
     897            </p>
     898            <p id="rfc.section.4.2.p.5">The following example illustrates when the complete length of the selected representation is known by the sender to be 1234
     899               bytes:
     900            </p>
     901            <div id="rfc.figure.u.20"></div><pre class="text">  Content-Range: bytes 42-1233/1234
    875902</pre><p id="rfc.section.4.2.p.7">and this second example illustrates when the complete length is unknown:</p>
    876       <div id="rfc.figure.u.21"></div><pre class="text">  Content-Range: bytes 42-1233/*
     903            <div id="rfc.figure.u.21"></div><pre class="text">  Content-Range: bytes 42-1233/*
    877904</pre><p id="rfc.section.4.2.p.9">A Content-Range field value is invalid if it contains a <a href="#header.content-range" class="smpl">byte-range-resp</a> that has a <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value less than its <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value, or a <a href="#header.content-range" class="smpl">complete-length</a> value less than or equal to its <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value. The recipient of an invalid <a href="#header.content-range" class="smpl">Content-Range</a> <em class="bcp14">MUST NOT</em> attempt to recombine the received content with a stored representation.
    878       </p>
    879       <p id="rfc.section.4.2.p.10">A server generating a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response to a byte range request <em class="bcp14">SHOULD</em> send a Content-Range header field with an <a href="#header.content-range" class="smpl">unsatisfied-range</a> value, as in the following example:
    880       </p>
    881       <div id="rfc.figure.u.22"></div><pre class="text">  Content-Range: bytes */1234
     905            </p>
     906            <p id="rfc.section.4.2.p.10">A server generating a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response to a byte range request <em class="bcp14">SHOULD</em> send a Content-Range header field with an <a href="#header.content-range" class="smpl">unsatisfied-range</a> value, as in the following example:
     907            </p>
     908            <div id="rfc.figure.u.22"></div><pre class="text">  Content-Range: bytes */1234
    882909</pre><p id="rfc.section.4.2.p.12">The complete-length in a 416 response indicates the current length of the selected representation.</p>
    883       <p id="rfc.section.4.2.p.13">The "Content-Range" header field has no meaning for status codes that do not explicitly describe its semantic. For this specification,
    884          only the <a href="#status.206" class="smpl">206 (Partial Content)</a> and <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> status codes describe a meaning for Content-Range.
    885       </p>
    886       <p id="rfc.section.4.2.p.14">The following are examples of Content-Range values in which the selected representation contains a total of 1234 bytes: </p>
    887       <ul>
    888          <li>The first 500 bytes:
    889             <div id="rfc.figure.u.23"></div><pre class="text">  Content-Range: bytes 0-499/1234
     910            <p id="rfc.section.4.2.p.13">The "Content-Range" header field has no meaning for status codes that do not explicitly describe its semantic. For this specification,
     911               only the <a href="#status.206" class="smpl">206 (Partial Content)</a> and <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> status codes describe a meaning for Content-Range.
     912            </p>
     913            <p id="rfc.section.4.2.p.14">The following are examples of Content-Range values in which the selected representation contains a total of 1234 bytes: </p>
     914            <ul>
     915               <li>The first 500 bytes:
     916                  <div id="rfc.figure.u.23"></div><pre class="text">  Content-Range: bytes 0-499/1234
    890917</pre> </li>
    891          <li>The second 500 bytes:
    892             <div id="rfc.figure.u.24"></div><pre class="text">  Content-Range: bytes 500-999/1234
     918               <li>The second 500 bytes:
     919                  <div id="rfc.figure.u.24"></div><pre class="text">  Content-Range: bytes 500-999/1234
    893920</pre> </li>
    894          <li>All except for the first 500 bytes:
    895             <div id="rfc.figure.u.25"></div><pre class="text">  Content-Range: bytes 500-1233/1234
     921               <li>All except for the first 500 bytes:
     922                  <div id="rfc.figure.u.25"></div><pre class="text">  Content-Range: bytes 500-1233/1234
    896923</pre> </li>
    897          <li>The last 500 bytes:
    898             <div id="rfc.figure.u.26"></div><pre class="text">  Content-Range: bytes 734-1233/1234
     924               <li>The last 500 bytes:
     925                  <div id="rfc.figure.u.26"></div><pre class="text">  Content-Range: bytes 734-1233/1234
    899926</pre> </li>
    900       </ul>
    901       <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Ranges</a></h2>
    902       <p id="rfc.section.4.3.p.1">A response might transfer only a subrange of a representation if the connection closed prematurely or if the request used
    903          one or more Range specifications. After several such transfers, a client might have received several ranges of the same representation.
    904          These ranges can only be safely combined if they all have in common the same strong validator (<a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.1</a> of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>).
    905       </p>
    906       <p id="rfc.section.4.3.p.2">A client that has received multiple partial responses to GET requests on a target resource <em class="bcp14">MAY</em> combine those responses into a larger continuous range if they share the same strong validator.
    907       </p>
    908       <p id="rfc.section.4.3.p.3">If the most recent response is an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, then the header fields of that response are used for any combined response and replace those of the matching stored
    909          responses.
    910       </p>
    911       <p id="rfc.section.4.3.p.4">If the most recent response is a <a href="#status.206" class="smpl">206 (Partial Content)</a> response and at least one of the matching stored responses is a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, then the combined response header fields consist of the most recent 200 response's header fields. If all of the matching
    912          stored responses are 206 responses, then the stored response with the most recent header fields is used as the source of header
    913          fields for the combined response, except that the client <em class="bcp14">MUST</em> use other header fields provided in the new response, aside from <a href="#header.content-range" class="smpl">Content-Range</a>, to replace all instances of the corresponding header fields in the stored response.
    914       </p>
    915       <p id="rfc.section.4.3.p.5">The combined response message body consists of the union of partial content ranges in the new response and each of the selected
    916          responses. If the union consists of the entire range of the representation, then the client <em class="bcp14">MUST</em> process the combined response as if it were a complete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, including a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field that reflects the complete length. Otherwise, the client <em class="bcp14">MUST</em> process the set of continuous ranges as one of the following: an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response if the combined response is a prefix of the representation, a single <a href="#status.206" class="smpl">206 (Partial Content)</a> response containing a multipart/byteranges body, or multiple <a href="#status.206" class="smpl">206 (Partial Content)</a> responses, each with one continuous range that is indicated by a <a href="#header.content-range" class="smpl">Content-Range</a> header field.
    917       </p>
    918       <div id="rfc.iref.29"></div>
    919       <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a id="status.416" href="#status.416">416 Range Not Satisfiable</a></h2>
    920       <p id="rfc.section.4.4.p.1">The <dfn>416 (Range Not Satisfiable)</dfn> status code indicates that none of the ranges in the request's <a href="#header.range" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;3.1</a>) overlap the current extent of the selected resource or that the set of ranges requested has been rejected due to invalid
    921          ranges or an excessive request of small or overlapping ranges.
    922       </p>
    923       <p id="rfc.section.4.4.p.2">For byte ranges, failing to overlap the current extent means that the <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> of all of the <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> values were greater than the current length of the selected representation. When this status code is generated in response
    924          to a byte range request, the sender <em class="bcp14">SHOULD</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field specifying the current length of the selected representation (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;4.2</a>).
    925       </p>
    926       <div id="rfc.figure.u.27"></div>
    927       <p>For example:</p><pre class="text">HTTP/1.1 416 Range Not Satisfiable
     927            </ul>
     928         </div>
     929         <div id="combining.byte.ranges">
     930            <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></h2>
     931            <p id="rfc.section.4.3.p.1">A response might transfer only a subrange of a representation if the connection closed prematurely or if the request used
     932               one or more Range specifications. After several such transfers, a client might have received several ranges of the same representation.
     933               These ranges can only be safely combined if they all have in common the same strong validator (<a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.1</a> of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>).
     934            </p>
     935            <p id="rfc.section.4.3.p.2">A client that has received multiple partial responses to GET requests on a target resource <em class="bcp14">MAY</em> combine those responses into a larger continuous range if they share the same strong validator.
     936            </p>
     937            <p id="rfc.section.4.3.p.3">If the most recent response is an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, then the header fields of that response are used for any combined response and replace those of the matching stored
     938               responses.
     939            </p>
     940            <p id="rfc.section.4.3.p.4">If the most recent response is a <a href="#status.206" class="smpl">206 (Partial Content)</a> response and at least one of the matching stored responses is a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, then the combined response header fields consist of the most recent 200 response's header fields. If all of the matching
     941               stored responses are 206 responses, then the stored response with the most recent header fields is used as the source of header
     942               fields for the combined response, except that the client <em class="bcp14">MUST</em> use other header fields provided in the new response, aside from <a href="#header.content-range" class="smpl">Content-Range</a>, to replace all instances of the corresponding header fields in the stored response.
     943            </p>
     944            <p id="rfc.section.4.3.p.5">The combined response message body consists of the union of partial content ranges in the new response and each of the selected
     945               responses. If the union consists of the entire range of the representation, then the client <em class="bcp14">MUST</em> process the combined response as if it were a complete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, including a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field that reflects the complete length. Otherwise, the client <em class="bcp14">MUST</em> process the set of continuous ranges as one of the following: an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response if the combined response is a prefix of the representation, a single <a href="#status.206" class="smpl">206 (Partial Content)</a> response containing a multipart/byteranges body, or multiple <a href="#status.206" class="smpl">206 (Partial Content)</a> responses, each with one continuous range that is indicated by a <a href="#header.content-range" class="smpl">Content-Range</a> header field.
     946            </p>
     947         </div>
     948         <div id="status.416">
     949            <div id="rfc.iref.29"></div>
     950            <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#status.416">416 Range Not Satisfiable</a></h2>
     951            <p id="rfc.section.4.4.p.1">The <dfn>416 (Range Not Satisfiable)</dfn> status code indicates that none of the ranges in the request's <a href="#header.range" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;3.1</a>) overlap the current extent of the selected resource or that the set of ranges requested has been rejected due to invalid
     952               ranges or an excessive request of small or overlapping ranges.
     953            </p>
     954            <p id="rfc.section.4.4.p.2">For byte ranges, failing to overlap the current extent means that the <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> of all of the <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> values were greater than the current length of the selected representation. When this status code is generated in response
     955               to a byte range request, the sender <em class="bcp14">SHOULD</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field specifying the current length of the selected representation (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;4.2</a>).
     956            </p>
     957            <div id="rfc.figure.u.27"></div>
     958            <p>For example:</p><pre class="text">HTTP/1.1 416 Range Not Satisfiable
    928959Date: Fri, 20 Jan 2012 15:41:54 GMT
    929960Content-Range: bytes */47022
    930961</pre><div class="note" id="rfc.section.4.4.p.4">
    931          <p><b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. That is partly because most clients are prepared to receive a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request
    932             until they have received a complete representation. Thus, clients cannot depend on receiving a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response even when it is most appropriate.
    933          </p>
     962               <p><b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. That is partly because most clients are prepared to receive a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request
     963                  until they have received a complete representation. Thus, clients cannot depend on receiving a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response even when it is most appropriate.
     964               </p>
     965            </div>
     966         </div>
    934967      </div>
    935       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    936       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="range.unit.registry" href="#range.unit.registry">Range Unit Registry</a></h2>
    937       <p id="rfc.section.5.1.p.1">The HTTP Range Unit Registry defines the name space for the range unit names and refers to their corresponding specifications.
    938          The registry will be created and maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    939       </p>
    940       <h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a id="range.unit.registry.procedure" href="#range.unit.registry.procedure">Procedure</a></h3>
    941       <p id="rfc.section.5.1.1.p.1">Registration of an HTTP Range Unit <em class="bcp14">MUST</em> include the following fields:
    942       </p>
    943       <ul>
    944          <li>Name</li>
    945          <li>Description</li>
    946          <li>Pointer to specification text</li>
    947       </ul>
    948       <p id="rfc.section.5.1.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    949       </p>
    950       <h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a id="range.unit.registration" href="#range.unit.registration">Registrations</a></h3>
    951       <p id="rfc.section.5.1.2.p.1">The initial HTTP Range Unit Registry shall contain the registrations below:</p>
    952       <div id="rfc.table.1">
    953          <div id="iana.range.units.table"></div>
    954          <table class="tt full left" cellpadding="3" cellspacing="0">
    955             <thead>
    956                <tr>
    957                   <th>Range Unit Name</th>
    958                   <th>Description</th>
    959                   <th>Reference</th>
    960                </tr>
    961             </thead>
    962             <tbody>
    963                <tr>
    964                   <td class="left">bytes</td>
    965                   <td class="left">a range of octets</td>
    966                   <td class="left"><a href="#byte.ranges" title="Byte Ranges">Section&nbsp;2.1</a></td>
    967                </tr>
    968                <tr>
    969                   <td class="left">none</td>
    970                   <td class="left">reserved as keyword, indicating no ranges are supported</td>
    971                   <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.2" title="Accept-Ranges">Section&nbsp;2.3</a></td>
    972                </tr>
    973             </tbody>
    974          </table>
     968      <div id="IANA.considerations">
     969         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     970         <div id="range.unit.registry">
     971            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#range.unit.registry">Range Unit Registry</a></h2>
     972            <p id="rfc.section.5.1.p.1">The HTTP Range Unit Registry defines the name space for the range unit names and refers to their corresponding specifications.
     973               The registry will be created and maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
     974            </p>
     975            <div id="range.unit.registry.procedure">
     976               <h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a href="#range.unit.registry.procedure">Procedure</a></h3>
     977               <p id="rfc.section.5.1.1.p.1">Registration of an HTTP Range Unit <em class="bcp14">MUST</em> include the following fields:
     978               </p>
     979               <ul>
     980                  <li>Name</li>
     981                  <li>Description</li>
     982                  <li>Pointer to specification text</li>
     983               </ul>
     984               <p id="rfc.section.5.1.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     985               </p>
     986            </div>
     987            <div id="range.unit.registration">
     988               <h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a href="#range.unit.registration">Registrations</a></h3>
     989               <p id="rfc.section.5.1.2.p.1">The initial HTTP Range Unit Registry shall contain the registrations below:</p>
     990               <div id="rfc.table.1">
     991                  <div id="iana.range.units.table"></div>
     992                  <table class="tt full left" cellpadding="3" cellspacing="0">
     993                     <thead>
     994                        <tr>
     995                           <th>Range Unit Name</th>
     996                           <th>Description</th>
     997                           <th>Reference</th>
     998                        </tr>
     999                     </thead>
     1000                     <tbody>
     1001                        <tr>
     1002                           <td class="left">bytes</td>
     1003                           <td class="left">a range of octets</td>
     1004                           <td class="left"><a href="#byte.ranges" title="Byte Ranges">Section&nbsp;2.1</a></td>
     1005                        </tr>
     1006                        <tr>
     1007                           <td class="left">none</td>
     1008                           <td class="left">reserved as keyword, indicating no ranges are supported</td>
     1009                           <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.2" title="Accept-Ranges">Section&nbsp;2.3</a></td>
     1010                        </tr>
     1011                     </tbody>
     1012                  </table>
     1013               </div>
     1014               <p id="rfc.section.5.1.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1015            </div>
     1016         </div>
     1017         <div id="status.code.registration">
     1018            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h2>
     1019            <p id="rfc.section.5.2.p.1">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
     1020            </p>
     1021            <div id="rfc.table.2">
     1022               <div id="iana.status.code.registration.table"></div>
     1023               <table class="tt full left" cellpadding="3" cellspacing="0">
     1024                  <thead>
     1025                     <tr>
     1026                        <th>Value</th>
     1027                        <th>Description</th>
     1028                        <th>Reference</th>
     1029                     </tr>
     1030                  </thead>
     1031                  <tbody>
     1032                     <tr>
     1033                        <td class="left">206</td>
     1034                        <td class="left">Partial Content</td>
     1035                        <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;4.1</a>
     1036                        </td>
     1037                     </tr>
     1038                     <tr>
     1039                        <td class="left">416</td>
     1040                        <td class="left">Range Not Satisfiable</td>
     1041                        <td class="left"><a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;4.4</a>
     1042                        </td>
     1043                     </tr>
     1044                  </tbody>
     1045               </table>
     1046            </div>
     1047         </div>
     1048         <div id="header.field.registration">
     1049            <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
     1050            <p id="rfc.section.5.3.p.1">HTTP header fields are registered within the Message Header Field Registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;.
     1051            </p>
     1052            <p id="rfc.section.5.3.p.2">This document defines the following HTTP header fields, so their associated registry entries shall be updated according to
     1053               the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
     1054            </p>
     1055            <div id="rfc.table.3">
     1056               <div id="iana.header.registration.table"></div>
     1057               <table class="tt full left" cellpadding="3" cellspacing="0">
     1058                  <thead>
     1059                     <tr>
     1060                        <th>Header Field Name</th>
     1061                        <th>Protocol</th>
     1062                        <th>Status</th>
     1063                        <th>Reference</th>
     1064                     </tr>
     1065                  </thead>
     1066                  <tbody>
     1067                     <tr>
     1068                        <td class="left">Accept-Ranges</td>
     1069                        <td class="left">http</td>
     1070                        <td class="left">standard</td>
     1071                        <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section&nbsp;2.3</a>
     1072                        </td>
     1073                     </tr>
     1074                     <tr>
     1075                        <td class="left">Content-Range</td>
     1076                        <td class="left">http</td>
     1077                        <td class="left">standard</td>
     1078                        <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;4.2</a>
     1079                        </td>
     1080                     </tr>
     1081                     <tr>
     1082                        <td class="left">If-Range</td>
     1083                        <td class="left">http</td>
     1084                        <td class="left">standard</td>
     1085                        <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;3.2</a>
     1086                        </td>
     1087                     </tr>
     1088                     <tr>
     1089                        <td class="left">Range</td>
     1090                        <td class="left">http</td>
     1091                        <td class="left">standard</td>
     1092                        <td class="left"><a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;3.1</a>
     1093                        </td>
     1094                     </tr>
     1095                  </tbody>
     1096               </table>
     1097            </div>
     1098            <p id="rfc.section.5.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1099         </div>
    9751100      </div>
    976       <p id="rfc.section.5.1.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    977       <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2>
    978       <p id="rfc.section.5.2.p.1">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
    979       </p>
    980       <div id="rfc.table.2">
    981          <div id="iana.status.code.registration.table"></div>
    982          <table class="tt full left" cellpadding="3" cellspacing="0">
    983             <thead>
    984                <tr>
    985                   <th>Value</th>
    986                   <th>Description</th>
    987                   <th>Reference</th>
    988                </tr>
    989             </thead>
    990             <tbody>
    991                <tr>
    992                   <td class="left">206</td>
    993                   <td class="left">Partial Content</td>
    994                   <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;4.1</a>
    995                   </td>
    996                </tr>
    997                <tr>
    998                   <td class="left">416</td>
    999                   <td class="left">Range Not Satisfiable</td>
    1000                   <td class="left"><a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;4.4</a>
    1001                   </td>
    1002                </tr>
    1003             </tbody>
    1004          </table>
     1101      <div id="security.considerations">
     1102         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     1103         <p id="rfc.section.6.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP/1.1
     1104            range request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
     1105         </p>
     1106         <div id="overlapping.ranges">
     1107            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#overlapping.ranges">Denial of Service Attacks using Range</a></h2>
     1108            <p id="rfc.section.6.1.p.1">Unconstrained multiple range requests are susceptible to denial of service attacks because the effort required to request
     1109               many overlapping ranges of the same data is tiny compared to the time, memory, and bandwidth consumed by attempting to serve
     1110               the requested data in many parts. Servers ought to ignore, coalesce, or reject egregious range requests, such as requests
     1111               for more than two overlapping ranges or for many small ranges in a single set, particularly when the ranges are requested
     1112               out of order for no apparent reason. Multipart range requests are not designed to support random access.
     1113            </p>
     1114         </div>
    10051115      </div>
    1006       <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    1007       <p id="rfc.section.5.3.p.1">HTTP header fields are registered within the Message Header Field Registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;.
    1008       </p>
    1009       <p id="rfc.section.5.3.p.2">This document defines the following HTTP header fields, so their associated registry entries shall be updated according to
    1010          the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
    1011       </p>
    1012       <div id="rfc.table.3">
    1013          <div id="iana.header.registration.table"></div>
    1014          <table class="tt full left" cellpadding="3" cellspacing="0">
    1015             <thead>
    1016                <tr>
    1017                   <th>Header Field Name</th>
    1018                   <th>Protocol</th>
    1019                   <th>Status</th>
    1020                   <th>Reference</th>
    1021                </tr>
    1022             </thead>
    1023             <tbody>
    1024                <tr>
    1025                   <td class="left">Accept-Ranges</td>
    1026                   <td class="left">http</td>
    1027                   <td class="left">standard</td>
    1028                   <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section&nbsp;2.3</a>
    1029                   </td>
    1030                </tr>
    1031                <tr>
    1032                   <td class="left">Content-Range</td>
    1033                   <td class="left">http</td>
    1034                   <td class="left">standard</td>
    1035                   <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;4.2</a>
    1036                   </td>
    1037                </tr>
    1038                <tr>
    1039                   <td class="left">If-Range</td>
    1040                   <td class="left">http</td>
    1041                   <td class="left">standard</td>
    1042                   <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;3.2</a>
    1043                   </td>
    1044                </tr>
    1045                <tr>
    1046                   <td class="left">Range</td>
    1047                   <td class="left">http</td>
    1048                   <td class="left">standard</td>
    1049                   <td class="left"><a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;3.1</a>
    1050                   </td>
    1051                </tr>
    1052             </tbody>
    1053          </table>
     1116      <div id="acks">
     1117         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
     1118         <p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     1119         </p>
    10541120      </div>
    1055       <p id="rfc.section.5.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    1056       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    1057       <p id="rfc.section.6.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP/1.1
    1058          range request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
    1059       </p>
    1060       <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="overlapping.ranges" href="#overlapping.ranges">Denial of Service Attacks using Range</a></h2>
    1061       <p id="rfc.section.6.1.p.1">Unconstrained multiple range requests are susceptible to denial of service attacks because the effort required to request
    1062          many overlapping ranges of the same data is tiny compared to the time, memory, and bandwidth consumed by attempting to serve
    1063          the requested data in many parts. Servers ought to ignore, coalesce, or reject egregious range requests, such as requests
    1064          for more than two overlapping ranges or for many small ranges in a single set, particularly when the ranges are requested
    1065          out of order for no apparent reason. Multipart range requests are not designed to support random access.
    1066       </p>
    1067       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    1068       <p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    1069       </p>
    10701121      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
    10711122      </h1>
     
    11351186      <div class="avoidbreak">
    11361187         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    1137          <address><span class="vcardline"><b>Roy T. Fielding</b>
    1138                (editor)
    1139                </span><span class="vcardline">Adobe Systems Incorporated</span><span class="vcardline">345 Park Ave</span><span class="vcardline">San Jose, CA&nbsp;95110</span><span class="vcardline">USA</span><span class="vcardline">Email: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></span></address>
    1140          <address><span class="vcardline"><b>Yves Lafon</b>
    1141                (editor)
    1142                </span><span class="vcardline">World Wide Web Consortium</span><span class="vcardline">W3C / ERCIM</span><span class="vcardline">2004, rte des Lucioles</span><span class="vcardline">Sophia-Antipolis, AM&nbsp;06902</span><span class="vcardline">France</span><span class="vcardline">Email: <a href="mailto:ylafon@w3.org">ylafon@w3.org</a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></span></address>
    1143          <address><span class="vcardline"><b>Julian F. Reschke</b>
    1144                (editor)
    1145                </span><span class="vcardline">greenbytes GmbH</span><span class="vcardline">Hafenweg 16</span><span class="vcardline">Muenster, NW&nbsp;48155</span><span class="vcardline">Germany</span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></span></address>
     1188         <p><b>Roy T. Fielding</b>
     1189            (editor)
     1190            <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
     1191         <p><b>Yves Lafon</b>
     1192            (editor)
     1193            <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM&nbsp;06902<br>France<br>Email: <a href="mailto:ylafon@w3.org">ylafon@w3.org</a><br>URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></p>
     1194         <p><b>Julian F. Reschke</b>
     1195            (editor)
     1196            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Email: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
    11461197      </div>
    1147       <div id="rfc.iref.m.1"></div>
    1148       <div id="rfc.iref.m.2"></div>
    1149       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="internet.media.type.multipart.byteranges" href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></h1>
    1150       <p id="rfc.section.A.p.1">When a <a href="#status.206" class="smpl">206 (Partial Content)</a> response message includes the content of multiple ranges, they are transmitted as body parts in 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>) with the media type of "multipart/byteranges". The following definition is to be registered with IANA <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a>.
    1151       </p>
    1152       <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more body parts, each with its own <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-range" class="smpl">Content-Range</a> fields. The required boundary parameter specifies the boundary string used to separate each body part.
    1153       </p>
    1154       <p id="rfc.section.A.p.3"></p>
    1155       <dl>
    1156          <dt>Type name:</dt>
    1157          <dd>multipart</dd>
    1158          <dt>Subtype name:</dt>
    1159          <dd>byteranges</dd>
    1160          <dt>Required parameters:</dt>
    1161          <dd>boundary</dd>
    1162          <dt>Optional parameters:</dt>
    1163          <dd>none</dd>
    1164          <dt>Encoding considerations:</dt>
    1165          <dd>only "7bit", "8bit", or "binary" are permitted</dd>
    1166          <dt>Security considerations:</dt>
    1167          <dd>none</dd>
    1168          <dt>Interoperability considerations:</dt>
    1169          <dd>none</dd>
    1170          <dt>Published specification:</dt>
    1171          <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
    1172          </dd>
    1173          <dt>Applications that use this media type:</dt>
    1174          <dd>HTTP components supporting multiple ranges in a single request.</dd>
    1175          <dt>Additional information:</dt>
    1176          <dd>
    1177             <dl>
    1178                <dt>Magic number(s):</dt>
    1179                <dd>none</dd>
    1180                <dt>File extension(s):</dt>
    1181                <dd>none</dd>
    1182                <dt>Macintosh file type code(s):</dt>
    1183                <dd>none</dd>
    1184             </dl>
    1185          </dd>
    1186          <dt>Person and email address to contact for further information:</dt>
    1187          <dd>See Authors Section.</dd>
    1188          <dt>Intended usage:</dt>
    1189          <dd>COMMON</dd>
    1190          <dt>Restrictions on usage:</dt>
    1191          <dd>none</dd>
    1192          <dt>Author:</dt>
    1193          <dd>See Authors Section.</dd>
    1194          <dt>Change controller:</dt>
    1195          <dd>IESG</dd>
    1196       </dl>
    1197       <p id="rfc.section.A.p.4">Implementation Notes: </p>
    1198       <ol>
    1199          <li>Additional CRLFs might precede the first boundary string in the body.</li>
    1200          <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> permits the boundary string to be quoted, some existing implementations handle a quoted boundary string incorrectly.
    1201          </li>
    1202          <li>A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of multipart/x-byteranges<span id="rfc.iref.m.3"></span><span id="rfc.iref.m.4"></span>, which is almost (but not quite) compatible with this type.
    1203          </li>
    1204       </ol>
    1205       <p id="rfc.section.A.p.5">Despite the name, the "multipart/byteranges" media type is not limited to byte ranges. The following example uses an "exampleunit"
    1206          range unit:
    1207       </p>
    1208       <div id="rfc.figure.u.28"></div><pre class="text">HTTP/1.1 206 Partial Content
     1198      <div id="internet.media.type.multipart.byteranges">
     1199         <div id="rfc.iref.m.1"></div>
     1200         <div id="rfc.iref.m.2"></div>
     1201         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></h1>
     1202         <p id="rfc.section.A.p.1">When a <a href="#status.206" class="smpl">206 (Partial Content)</a> response message includes the content of multiple ranges, they are transmitted as body parts in 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>) with the media type of "multipart/byteranges". The following definition is to be registered with IANA <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a>.
     1203         </p>
     1204         <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more body parts, each with its own <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-range" class="smpl">Content-Range</a> fields. The required boundary parameter specifies the boundary string used to separate each body part.
     1205         </p>
     1206         <p id="rfc.section.A.p.3"></p>
     1207         <dl>
     1208            <dt>Type name:</dt>
     1209            <dd>multipart</dd>
     1210            <dt>Subtype name:</dt>
     1211            <dd>byteranges</dd>
     1212            <dt>Required parameters:</dt>
     1213            <dd>boundary</dd>
     1214            <dt>Optional parameters:</dt>
     1215            <dd>none</dd>
     1216            <dt>Encoding considerations:</dt>
     1217            <dd>only "7bit", "8bit", or "binary" are permitted</dd>
     1218            <dt>Security considerations:</dt>
     1219            <dd>none</dd>
     1220            <dt>Interoperability considerations:</dt>
     1221            <dd>none</dd>
     1222            <dt>Published specification:</dt>
     1223            <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
     1224            </dd>
     1225            <dt>Applications that use this media type:</dt>
     1226            <dd>HTTP components supporting multiple ranges in a single request.</dd>
     1227            <dt>Additional information:</dt>
     1228            <dd>
     1229               <dl>
     1230                  <dt>Magic number(s):</dt>
     1231                  <dd>none</dd>
     1232                  <dt>File extension(s):</dt>
     1233                  <dd>none</dd>
     1234                  <dt>Macintosh file type code(s):</dt>
     1235                  <dd>none</dd>
     1236               </dl>
     1237            </dd>
     1238            <dt>Person and email address to contact for further information:</dt>
     1239            <dd>See Authors Section.</dd>
     1240            <dt>Intended usage:</dt>
     1241            <dd>COMMON</dd>
     1242            <dt>Restrictions on usage:</dt>
     1243            <dd>none</dd>
     1244            <dt>Author:</dt>
     1245            <dd>See Authors Section.</dd>
     1246            <dt>Change controller:</dt>
     1247            <dd>IESG</dd>
     1248         </dl>
     1249         <p id="rfc.section.A.p.4">Implementation Notes: </p>
     1250         <ol>
     1251            <li>Additional CRLFs might precede the first boundary string in the body.</li>
     1252            <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> permits the boundary string to be quoted, some existing implementations handle a quoted boundary string incorrectly.
     1253            </li>
     1254            <li>A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of multipart/x-byteranges<span id="rfc.iref.m.3"></span><span id="rfc.iref.m.4"></span>, which is almost (but not quite) compatible with this type.
     1255            </li>
     1256         </ol>
     1257         <p id="rfc.section.A.p.5">Despite the name, the "multipart/byteranges" media type is not limited to byte ranges. The following example uses an "exampleunit"
     1258            range unit:
     1259         </p>
     1260         <div id="rfc.figure.u.28"></div><pre class="text">HTTP/1.1 206 Partial Content
    12091261Date: Tue, 14 Nov 1995 06:25:24 GMT
    12101262Last-Modified: Tue, 14 July 04:58:08 GMT
     
    12231275...the second range
    12241276--THIS_STRING_SEPARATES--
    1225 </pre><h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
    1226       <p id="rfc.section.B.p.1">Servers are given more leeway in how they respond to a range request, in order to mitigate abuse by malicious (or just greedy)
    1227          clients. (<a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;3.1</a>)
    1228       </p>
    1229       <p id="rfc.section.B.p.2">A weak validator cannot be used in a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;4.1</a>)
    1230       </p>
    1231       <p id="rfc.section.B.p.3">The Content-Range header field only has meaning when the status code explicitly defines its use. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;4.2</a>)
    1232       </p>
    1233       <p id="rfc.section.B.p.4">This specification introduces a Range Unit Registry. (<a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;5.1</a>)
    1234       </p>
    1235       <p id="rfc.section.B.p.5">multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
    1236       </p>
    1237       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
    1238       <p id="rfc.section.C.p.1">The following core rules are included by reference, as defined in <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a> of <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    1239          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
    1240          character).
    1241       </p>
    1242       <p id="rfc.section.C.p.2">Note that all rules derived from <a href="#imported.abnf" class="smpl">token</a> are to be compared case-insensitively, like <a href="#range.units" class="smpl">range-unit</a> and <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>.
    1243       </p>
    1244       <p id="rfc.section.C.p.3">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:
    1245       </p>
    1246       <div id="rfc.figure.u.29"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>        = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
     1277</pre></div>
     1278      <div id="changes.from.rfc.2616">
     1279         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
     1280         <p id="rfc.section.B.p.1">Servers are given more leeway in how they respond to a range request, in order to mitigate abuse by malicious (or just greedy)
     1281            clients. (<a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;3.1</a>)
     1282         </p>
     1283         <p id="rfc.section.B.p.2">A weak validator cannot be used in a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;4.1</a>)
     1284         </p>
     1285         <p id="rfc.section.B.p.3">The Content-Range header field only has meaning when the status code explicitly defines its use. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;4.2</a>)
     1286         </p>
     1287         <p id="rfc.section.B.p.4">This specification introduces a Range Unit Registry. (<a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;5.1</a>)
     1288         </p>
     1289         <p id="rfc.section.B.p.5">multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
     1290         </p>
     1291      </div>
     1292      <div id="imported.abnf">
     1293         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#imported.abnf">Imported ABNF</a></h1>
     1294         <p id="rfc.section.C.p.1">The following core rules are included by reference, as defined in <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a> of <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     1295            (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
     1296            character).
     1297         </p>
     1298         <p id="rfc.section.C.p.2">Note that all rules derived from <a href="#imported.abnf" class="smpl">token</a> are to be compared case-insensitively, like <a href="#range.units" class="smpl">range-unit</a> and <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>.
     1299         </p>
     1300         <p id="rfc.section.C.p.3">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:
     1301         </p>
     1302         <div id="rfc.figure.u.29"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>        = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
    12471303  <a href="#imported.abnf" class="smpl">token</a>      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
    12481304</pre><p id="rfc.section.C.p.5">The rules below are defined in other parts:</p>
    1249       <div id="rfc.figure.u.30"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
     1305         <div id="rfc.figure.u.30"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
    12501306  <a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>&gt;
    1251 </pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1252       <p id="rfc.section.D.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    1253       </p>
    1254       <div id="rfc.figure.u.31"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
     1307</pre></div>
     1308      <div id="collected.abnf">
     1309         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     1310         <p id="rfc.section.D.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     1311         </p>
     1312         <div id="rfc.figure.u.31"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
    12551313
    12561314<a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range / other-content-range
     
    13001358
    13011359<a href="#header.content-range" class="smpl">unsatisfied-range</a> = "*/" complete-length
    1302 </pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    1303       <p id="rfc.section.E.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D">http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D</a>&gt;.
    1304       </p>
    1305       <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p5-range-19</a></h2>
    1306       <p id="rfc.section.E.1.p.1">Closed issues: </p>
    1307       <ul>
    1308          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>&gt;: "ABNF list expansion code problem"
    1309          </li>
    1310          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
    1311          </li>
    1312          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/367">http://tools.ietf.org/wg/httpbis/trac/ticket/367</a>&gt;: "reserve 'none' as byte range unit"
    1313          </li>
    1314          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
    1315          </li>
    1316          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>&gt;: "range units vs leading zeroes vs size"
    1317          </li>
    1318       </ul>
    1319       <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;<a id="changes.since.20" href="#changes.since.20">Since draft-ietf-httpbis-p5-range-20</a></h2>
    1320       <p id="rfc.section.E.2.p.1"></p>
    1321       <ul>
    1322          <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li>
    1323       </ul>
    1324       <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;<a id="changes.since.21" href="#changes.since.21">Since draft-ietf-httpbis-p5-range-21</a></h2>
    1325       <p id="rfc.section.E.3.p.1">Closed issues: </p>
    1326       <ul>
    1327          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/175">http://tools.ietf.org/wg/httpbis/trac/ticket/175</a>&gt;: "Security consideration: range flooding"
    1328          </li>
    1329          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
    1330          </li>
    1331          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/311">http://tools.ietf.org/wg/httpbis/trac/ticket/311</a>&gt;: "Add limitations to Range to reduce its use as a denial-of-service tool"
    1332          </li>
    1333          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/407">http://tools.ietf.org/wg/httpbis/trac/ticket/407</a>&gt;: "416 and multipart/byteranges"
    1334          </li>
    1335       </ul>
    1336       <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;<a id="changes.since.22" href="#changes.since.22">Since draft-ietf-httpbis-p5-range-22</a></h2>
    1337       <p id="rfc.section.E.4.p.1">Closed issues: </p>
    1338       <ul>
    1339          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
    1340          </li>
    1341          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>&gt;: "incorrect example dates"
    1342          </li>
    1343          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
    1344          </li>
    1345          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/462">http://tools.ietf.org/wg/httpbis/trac/ticket/462</a>&gt;: "Editorial suggestions"
    1346          </li>
    1347          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/485">http://tools.ietf.org/wg/httpbis/trac/ticket/485</a>&gt;: "MUSTs and other feedback"
    1348          </li>
    1349       </ul>
    1350       <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a id="changes.since.23" href="#changes.since.23">Since draft-ietf-httpbis-p5-range-23</a></h2>
    1351       <p id="rfc.section.E.5.p.1">Closed issues: </p>
    1352       <ul>
    1353          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/489">http://tools.ietf.org/wg/httpbis/trac/ticket/489</a>&gt;: "is P5's definition of strong validator consistent with P4?"
    1354          </li>
    1355          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/490">http://tools.ietf.org/wg/httpbis/trac/ticket/490</a>&gt;: "p5 editorial comments"
    1356          </li>
    1357       </ul>
    1358       <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a id="changes.since.24" href="#changes.since.24">Since draft-ietf-httpbis-p5-range-24</a></h2>
    1359       <p id="rfc.section.E.6.p.1">None yet.</p>
     1360</pre></div>
     1361      <div id="change.log">
     1362         <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     1363         <p id="rfc.section.E.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D">http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D</a>&gt;.
     1364         </p>
     1365         <div id="changes.since.19">
     1366            <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p5-range-19</a></h2>
     1367            <p id="rfc.section.E.1.p.1">Closed issues: </p>
     1368            <ul>
     1369               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>&gt;: "ABNF list expansion code problem"
     1370               </li>
     1371               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
     1372               </li>
     1373               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/367">http://tools.ietf.org/wg/httpbis/trac/ticket/367</a>&gt;: "reserve 'none' as byte range unit"
     1374               </li>
     1375               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
     1376               </li>
     1377               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>&gt;: "range units vs leading zeroes vs size"
     1378               </li>
     1379            </ul>
     1380         </div>
     1381         <div id="changes.since.20">
     1382            <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;<a href="#changes.since.20">Since draft-ietf-httpbis-p5-range-20</a></h2>
     1383            <p id="rfc.section.E.2.p.1"></p>
     1384            <ul>
     1385               <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li>
     1386            </ul>
     1387         </div>
     1388         <div id="changes.since.21">
     1389            <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;<a href="#changes.since.21">Since draft-ietf-httpbis-p5-range-21</a></h2>
     1390            <p id="rfc.section.E.3.p.1">Closed issues: </p>
     1391            <ul>
     1392               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/175">http://tools.ietf.org/wg/httpbis/trac/ticket/175</a>&gt;: "Security consideration: range flooding"
     1393               </li>
     1394               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>&gt;: "Allowing heuristic caching for new status codes"
     1395               </li>
     1396               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/311">http://tools.ietf.org/wg/httpbis/trac/ticket/311</a>&gt;: "Add limitations to Range to reduce its use as a denial-of-service tool"
     1397               </li>
     1398               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/407">http://tools.ietf.org/wg/httpbis/trac/ticket/407</a>&gt;: "416 and multipart/byteranges"
     1399               </li>
     1400            </ul>
     1401         </div>
     1402         <div id="changes.since.22">
     1403            <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;<a href="#changes.since.22">Since draft-ietf-httpbis-p5-range-22</a></h2>
     1404            <p id="rfc.section.E.4.p.1">Closed issues: </p>
     1405            <ul>
     1406               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices"
     1407               </li>
     1408               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>&gt;: "incorrect example dates"
     1409               </li>
     1410               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
     1411               </li>
     1412               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/462">http://tools.ietf.org/wg/httpbis/trac/ticket/462</a>&gt;: "Editorial suggestions"
     1413               </li>
     1414               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/485">http://tools.ietf.org/wg/httpbis/trac/ticket/485</a>&gt;: "MUSTs and other feedback"
     1415               </li>
     1416            </ul>
     1417         </div>
     1418         <div id="changes.since.23">
     1419            <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;<a href="#changes.since.23">Since draft-ietf-httpbis-p5-range-23</a></h2>
     1420            <p id="rfc.section.E.5.p.1">Closed issues: </p>
     1421            <ul>
     1422               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/489">http://tools.ietf.org/wg/httpbis/trac/ticket/489</a>&gt;: "is P5's definition of strong validator consistent with P4?"
     1423               </li>
     1424               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/490">http://tools.ietf.org/wg/httpbis/trac/ticket/490</a>&gt;: "p5 editorial comments"
     1425               </li>
     1426            </ul>
     1427         </div>
     1428         <div id="changes.since.24">
     1429            <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a href="#changes.since.24">Since draft-ietf-httpbis-p5-range-24</a></h2>
     1430            <p id="rfc.section.E.6.p.1">None yet.</p>
     1431         </div>
     1432      </div>
    13601433      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    13611434      <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a>
Note: See TracChangeset for help on using the changeset viewer.