Ignore:
Timestamp:
Jun 14, 2014, 4:20:37 AM (6 years ago)
Author:
julian.reschke@…
Message:

update to latest version of rfc2629.xslt, regen all HTML

File:
1 edited

Legend:

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

    r1271 r2726  
    22  PUBLIC "-//W3C//DTD HTML 4.01//EN">
    33<html lang="en">
    4    <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
     4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    66      <title>HTTP/1.1, part 5: Range Requests and Partial Responses</title><style type="text/css" title="Xml2Rfc (sans serif)">
     
    2424body {
    2525  color: black;
    26   font-family: verdana, helvetica, arial, sans-serif;
    27   font-size: 10pt;
     26  font-family: cambria, helvetica, arial, sans-serif;
     27  font-size: 11pt;
     28  margin-right: 2em;
    2829}
    2930cite {
     
    3334  margin-left: 2em;
    3435}
    35 dd {
    36   margin-right: 2em;
    37 }
    3836dl {
    3937  margin-left: 2em;
    4038}
    41 
    4239ul.empty {
    4340  list-style-type: none;
     
    5350}
    5451h1 {
    55   font-size: 14pt;
     52  font-size: 130%;
    5653  line-height: 21pt;
    5754  page-break-after: avoid;
     
    6057  page-break-before: always;
    6158}
    62 h1 a {
    63   color: #333333;
    64 }
    6559h2 {
    66   font-size: 12pt;
     60  font-size: 120%;
    6761  line-height: 15pt;
    6862  page-break-after: avoid;
    6963}
    70 h3, h4, h5, h6 {
    71   font-size: 10pt;
     64h3 {
     65  font-size: 110%;
    7266  page-break-after: avoid;
    7367}
    74 h2 a, h3 a, h4 a, h5 a, h6 a {
     68h4, h5, h6 {
     69  page-break-after: avoid;
     70}
     71h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    7572  color: black;
    7673}
     
    8077li {
    8178  margin-left: 2em;
    82   margin-right: 2em;
    8379}
    8480ol {
    8581  margin-left: 2em;
    86   margin-right: 2em;
    8782}
    8883ol.la {
     
    9792p {
    9893  margin-left: 2em;
    99   margin-right: 2em;
    10094}
    10195pre {
     
    10397  background-color: lightyellow;
    10498  padding: .25em;
     99  page-break-inside: avoid;
    105100}
    106101pre.text2 {
     
    131126table.tt {
    132127  vertical-align: top;
     128  border-color: gray;
     129}
     130table.tt th {
     131  border-color: gray;
     132}
     133table.tt td {
     134  border-color: gray;
     135}
     136table.all {
     137  border-style: solid;
     138  border-width: 2px;
    133139}
    134140table.full {
    135   border-style: outset;
    136   border-width: 1px;
    137 }
    138 table.headers {
    139   border-style: outset;
    140   border-width: 1px;
     141  border-style: solid;
     142  border-width: 2px;
    141143}
    142144table.tt td {
    143145  vertical-align: top;
    144146}
     147table.all td {
     148  border-style: solid;
     149  border-width: 1px;
     150}
    145151table.full td {
    146   border-style: inset;
     152  border-style: none solid;
    147153  border-width: 1px;
    148154}
     
    150156  vertical-align: top;
    151157}
     158table.all th {
     159  border-style: solid;
     160  border-width: 1px;
     161}
    152162table.full th {
    153   border-style: inset;
    154   border-width: 1px;
     163  border-style: solid;
     164  border-width: 1px 1px 2px 1px;
    155165}
    156166table.headers th {
    157   border-style: none none inset none;
    158   border-width: 1px;
     167  border-style: none none solid none;
     168  border-width: 2px;
    159169}
    160170table.left {
     
    171181  caption-side: bottom;
    172182  font-weight: bold;
    173   font-size: 9pt;
     183  font-size: 10pt;
    174184  margin-top: .5em;
    175185}
     
    178188  border-spacing: 1px;
    179189  width: 95%;
    180   font-size: 10pt;
     190  font-size: 11pt;
    181191  color: white;
    182192}
     
    186196td.topnowrap {
    187197  vertical-align: top;
    188   white-space: nowrap; 
     198  white-space: nowrap;
    189199}
    190200table.header td {
     
    206216  list-style: none;
    207217  margin-left: 1.5em;
    208   margin-right: 0em;
    209218  padding-left: 0em;
    210219}
     
    212221  line-height: 150%;
    213222  font-weight: bold;
    214   font-size: 10pt;
    215223  margin-left: 0em;
    216   margin-right: 0em;
    217224}
    218225ul.toc li li {
    219226  line-height: normal;
    220227  font-weight: normal;
    221   font-size: 9pt;
     228  font-size: 10pt;
    222229  margin-left: 0em;
    223   margin-right: 0em;
    224230}
    225231li.excluded {
     
    228234ul p {
    229235  margin-left: 0em;
     236}
     237.title, .filename, h1, h2, h3, h4 {
     238  font-family: candara, helvetica, arial, sans-serif;
     239}
     240samp, tt, code, pre {
     241  font: consolas, monospace;
    230242}
    231243ul.ind, ul.ind ul {
    232244  list-style: none;
    233245  margin-left: 1.5em;
    234   margin-right: 0em;
    235246  padding-left: 0em;
    236247  page-break-before: avoid;
     
    240251  line-height: 200%;
    241252  margin-left: 0em;
    242   margin-right: 0em;
    243253}
    244254ul.ind li li {
     
    246256  line-height: 150%;
    247257  margin-left: 0em;
    248   margin-right: 0em;
    249258}
    250259.avoidbreak {
     
    270279  font-weight: bold;
    271280  text-align: center;
    272   font-size: 9pt;
     281  font-size: 10pt;
    273282}
    274283.filename {
    275284  color: #333333;
     285  font-size: 75%;
    276286  font-weight: bold;
    277   font-size: 12pt;
    278287  line-height: 21pt;
    279288  text-align: center;
     
    282291  font-weight: bold;
    283292}
    284 .hidden {
    285   display: none;
    286 }
    287293.left {
    288294  text-align: left;
     
    292298}
    293299.title {
    294   color: #990000;
    295   font-size: 18pt;
     300  color: green;
     301  font-size: 150%;
    296302  line-height: 18pt;
    297303  font-weight: bold;
     
    299305  margin-top: 36pt;
    300306}
    301 .vcardline {
    302   display: block;
    303 }
    304307.warning {
    305   font-size: 14pt;
     308  font-size: 130%;
    306309  background-color: yellow;
    307310}
     
    312315    display: none;
    313316  }
    314  
     317
    315318  a {
    316319    color: black;
     
    327330    background-color: white;
    328331    vertical-align: top;
    329     font-size: 12pt;
     332    font-size: 110%;
    330333  }
    331334
    332   ul.toc a::after {
     335  ul.toc a:nth-child(2)::after {
    333336    content: leader('.') target-counter(attr(href), page);
    334337  }
    335  
     338
    336339  ul.ind li li a {
    337340    content: target-counter(attr(href), page);
    338341  }
    339  
     342
    340343  .print2col {
    341344    column-count: 2;
     
    347350@page {
    348351  @top-left {
    349        content: "Internet-Draft"; 
    350   } 
     352       content: "Internet-Draft";
     353  }
    351354  @top-right {
    352        content: "April 2011"; 
    353   } 
     355       content: "April 2011";
     356  }
    354357  @top-center {
    355        content: "HTTP/1.1, Part 5"; 
    356   } 
     358       content: "HTTP/1.1, Part 5";
     359  }
    357360  @bottom-left {
    358        content: "Fielding, et al."; 
    359   } 
     361       content: "Fielding, et al.";
     362  }
    360363  @bottom-center {
    361        content: "Expires October 20, 2011"; 
    362   } 
     364       content: "Expires October 20, 2011";
     365  }
    363366  @bottom-right {
    364        content: "[Page " counter(page) "]"; 
    365   } 
    366 }
    367 
    368 @page:first { 
     367       content: "[Page " counter(page) "]";
     368  }
     369}
     370
     371@page:first {
    369372    @top-left {
    370373      content: normal;
     
    394397      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
    395398      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    396       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.543, 2011-02-18 21:03:40, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     399      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    397400      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    398401      <meta name="dct.creator" content="Fielding, R.">
     
    423426            </tr>
    424427            <tr>
    425                <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     428               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    426429               </td>
    427430               <td class="right">J. Gettys</td>
     
    494497      </table>
    495498      <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-14</span></p>
    496       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
     499      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    497500      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    498501         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
    499502         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
    500503         5 defines range-specific requests and the rules for constructing and combining responses to those requests.
    501       </p> 
    502       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
     504      </p>
     505      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    503506      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived
    504507         at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
    505       </p> 
     508      </p>
    506509      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    507       </p> 
     510      </p>
    508511      <p>The changes in this draft are summarized in <a href="#changes.since.13" title="Since draft-ietf-httpbis-p5-range-13">Appendix&nbsp;D.15</a>.
    509       </p>
    510       <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    511       <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
    512       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
    513          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>.
    514512      </p>
    515       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    516          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    517          in progress”.
    518       </p>
    519       <p>This Internet-Draft will expire on October 20, 2011.</p>
    520       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    521       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    522       <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
    523          and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
    524          text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
    525          BSD License.
    526       </p>
    527       <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
    528          10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
    529          allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
    530          controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
    531          works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
    532          it into languages other than English.
    533       </p>
     513      <div id="rfc.status">
     514         <h1><a href="#rfc.status">Status of This Memo</a></h1>
     515         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     516         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
     517            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>.
     518         </p>
     519         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     520            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     521            in progress”.
     522         </p>
     523         <p>This Internet-Draft will expire on October 20, 2011.</p>
     524      </div>
     525      <div id="rfc.copyrightnotice">
     526         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     527         <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     528         <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
     529            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     530            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
     531            BSD License.
     532         </p>
     533         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     534            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     535            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     536            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     537            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     538            it into languages other than English.
     539         </p>
     540      </div>
    534541      <hr class="noprint">
    535542      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    536543      <ul class="toc">
    537          <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    538                <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    539                <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
    540                      <li>1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    541                      <li>1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     544         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     545               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     546               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     547                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     548                     <li><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    542549                  </ul>
    543550               </li>
    544551            </ul>
    545552         </li>
    546          <li>2.&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a><ul>
    547                <li>2.1&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registry">Range Specifier Registry</a></li>
     553         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a><ul>
     554               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registry">Range Specifier Registry</a></li>
    548555            </ul>
    549556         </li>
    550          <li>3.&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
    551                <li>3.1&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    552                <li>3.2&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
     557         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
     558               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
     559               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
    553560            </ul>
    554561         </li>
    555          <li>4.&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
    556          <li>5.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
    557                <li>5.1&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
    558                <li>5.2&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
    559                <li>5.3&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
    560                <li>5.4&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
    561                      <li>5.4.1&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
    562                      <li>5.4.2&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
     562         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
     563         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     564               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
     565               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
     566               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
     567               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
     568                     <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
     569                     <li><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
    563570                  </ul>
    564571               </li>
    565572            </ul>
    566573         </li>
    567          <li>6.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    568                <li>6.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
    569                <li>6.2&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    570                <li>6.3&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registration">Range Specifier Registration</a></li>
     574         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     575               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
     576               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
     577               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registration">Range Specifier Registration</a></li>
    571578            </ul>
    572579         </li>
    573          <li>7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
    574          <li>8.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    575          <li>9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    576                <li>9.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    577                <li>9.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     580         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
     581         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     582         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     583               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     584               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    578585            </ul>
    579586         </li>
    580          <li><a href="#rfc.authors">Authors' Addresses</a></li>
    581          <li>A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
    582          <li>B.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
    583                <li>B.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     587         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
     588         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
     589               <li><a href="#rfc.section.B.1">B.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    584590            </ul>
    585591         </li>
    586          <li>C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    587          <li>D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    588                <li>D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC 2616</a></li>
    589                <li>D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p5-range-00</a></li>
    590                <li>D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p5-range-01</a></li>
    591                <li>D.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></li>
    592                <li>D.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></li>
    593                <li>D.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></li>
    594                <li>D.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></li>
    595                <li>D.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></li>
    596                <li>D.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></li>
    597                <li>D.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></li>
    598                <li>D.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></li>
    599                <li>D.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></li>
    600                <li>D.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></li>
    601                <li>D.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p5-range-12</a></li>
    602                <li>D.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p5-range-13</a></li>
     592         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     593         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     594               <li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC 2616</a></li>
     595               <li><a href="#rfc.section.D.2">D.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p5-range-00</a></li>
     596               <li><a href="#rfc.section.D.3">D.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p5-range-01</a></li>
     597               <li><a href="#rfc.section.D.4">D.4</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></li>
     598               <li><a href="#rfc.section.D.5">D.5</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></li>
     599               <li><a href="#rfc.section.D.6">D.6</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></li>
     600               <li><a href="#rfc.section.D.7">D.7</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></li>
     601               <li><a href="#rfc.section.D.8">D.8</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></li>
     602               <li><a href="#rfc.section.D.9">D.9</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></li>
     603               <li><a href="#rfc.section.D.10">D.10</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></li>
     604               <li><a href="#rfc.section.D.11">D.11</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></li>
     605               <li><a href="#rfc.section.D.12">D.12</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></li>
     606               <li><a href="#rfc.section.D.13">D.13</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></li>
     607               <li><a href="#rfc.section.D.14">D.14</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p5-range-12</a></li>
     608               <li><a href="#rfc.section.D.15">D.15</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p5-range-13</a></li>
    603609            </ul>
    604610         </li>
    605611         <li><a href="#rfc.index">Index</a></li>
     612         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    606613      </ul>
    607       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    608       <p id="rfc.section.1.p.1">HTTP clients often encounter interrupted data transfers as a result of cancelled requests or dropped connections. When a cache
    609          has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
    610          rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
    611          request only a subset of a larger representation, such as a single page of a very large document or only part of an image
    612          to be rendered by a device with limited local storage.
    613       </p>
    614       <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type. The protocol for
    615          range requests is an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so resources or recipients that do not implement this feature can respond as if it is a normal GET
    616          request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
    617          full responses by intermediate caches that might not implement the feature.
    618       </p>
    619       <p id="rfc.section.1.p.3">Although the HTTP range request mechanism is designed to allow for extensible range types, this specification only defines
    620          requests for byte ranges.
    621       </p>
    622       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    623       <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"
    624          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>.
    625       </p>
    626       <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
    627          protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
    628          for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
    629          all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    630       </p>
    631       <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>
    632       <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF, with the list rule expanded.
    633       </p>
    634       <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    635          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
    636          and WSP (whitespace).
    637       </p>
    638       <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    639       <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
    640       </p>
    641       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">token</a>      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     614      <div id="introduction">
     615         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     616         <p id="rfc.section.1.p.1">HTTP clients often encounter interrupted data transfers as a result of cancelled requests or dropped connections. When a cache
     617            has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
     618            rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
     619            request only a subset of a larger representation, such as a single page of a very large document or only part of an image
     620            to be rendered by a device with limited local storage.
     621         </p>
     622         <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type. The protocol for
     623            range requests is an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so resources or recipients that do not implement this feature can respond as if it is a normal GET
     624            request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
     625            full responses by intermediate caches that might not implement the feature.
     626         </p>
     627         <p id="rfc.section.1.p.3">Although the HTTP range request mechanism is designed to allow for extensible range types, this specification only defines
     628            requests for byte ranges.
     629         </p>
     630         <div id="intro.requirements">
     631            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     632            <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"
     633               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>.
     634            </p>
     635            <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
     636               protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     637               for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     638               all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
     639            </p>
     640         </div>
     641         <div id="notation">
     642            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     643            <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF, with the list rule expanded.
     644            </p>
     645            <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="https://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     646               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
     647               and WSP (whitespace).
     648            </p>
     649            <div id="core.rules">
     650               <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a href="#core.rules">Core Rules</a></h3>
     651               <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
     652               </p>
     653               <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">token</a>      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    642654  <a href="#core.rules" class="smpl">OWS</a>        = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    643 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    644       <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
    645       <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>&gt;
     655</pre></div>
     656            <div id="abnf.dependencies">
     657               <h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
     658               <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
     659               <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>&gt;
    646660</pre><div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.2</a>&gt;
    647 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
    648       <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range) of the representation be included within the response. HTTP/1.1
    649          uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;5.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;5.2</a>) header fields. A representation can be broken down into subranges according to various structural units.
    650       </p>
    651       <div id="rfc.figure.u.4"></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="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a>
     661</pre></div>
     662         </div>
     663      </div>
     664      <div id="range.units">
     665         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#range.units">Range Units</a></h1>
     666         <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range) of the representation be included within the response. HTTP/1.1
     667            uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;5.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;5.2</a>) header fields. A representation can be broken down into subranges according to various structural units.
     668         </p>
     669         <div id="rfc.figure.u.4"></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="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a>
    652670  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
    653671  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a>
    654672</pre><p id="rfc.section.2.p.3">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges. The only range
    655          unit defined by HTTP/1.1 is "bytes". Additional specifiers can be defined as described in <a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a>.
    656       </p>
    657       <p id="rfc.section.2.p.4">If a range unit is not understood in a request, a server <em class="bcp14">MUST</em> ignore the whole Range header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;5.4</a>). If a range unit is not understood in a response, an intermediary <em class="bcp14">SHOULD</em> pass the response to the client; a client <em class="bcp14">MUST</em> fail.
    658       </p>
    659       <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="range.specifier.registry" href="#range.specifier.registry">Range Specifier Registry</a></h2>
    660       <p id="rfc.section.2.1.p.1">The HTTP Range Specifier Registry defines the name space for the range specifier names.</p>
    661       <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    662       </p>
    663       <ul>
    664          <li>Name</li>
    665          <li>Description</li>
    666          <li>Pointer to specification text</li>
    667       </ul>
    668       <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<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>).
    669       </p>
    670       <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt;.
    671       </p>
    672       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="status.code.definitions" href="#status.code.definitions">Status Code Definitions</a></h1>
    673       <div id="rfc.iref.3"></div>
    674       <div id="rfc.iref.s.1"></div>
    675       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h2>
    676       <p id="rfc.section.3.1.p.1">The server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a Range header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;5.4</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;5.3</a>) to make the request conditional.
    677       </p>
    678       <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
    679       </p>
    680       <ul>
    681          <li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;5.2</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields
    682             for each part. If a Content-Length header field is present in the response, its value <em class="bcp14">MUST</em> match the actual number of octets transmitted in the message-body.
    683          </li>
    684          <li>Date</li>
    685          <li>Cache-Control, ETag, Expires, Content-Location, Last-Modified, and/or Vary, if the header field would have been sent in a
    686             200 response to the same request
    687          </li>
    688       </ul>
    689       <p id="rfc.section.3.1.p.3">If the 206 response is the result of an If-Range request, the response <em class="bcp14">SHOULD NOT</em> include other representation header fields. Otherwise, the response <em class="bcp14">MUST</em> include all of the representation header fields that would have been returned with a 200 (OK) response to the same request.
    690       </p>
    691       <p id="rfc.section.3.1.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified header fields do not match exactly,
    692          see <a href="#combining.byte.ranges" title="Combining Ranges">Section&nbsp;4</a>.
    693       </p>
    694       <p id="rfc.section.3.1.p.5">A cache that does not support the Range and Content-Range header fields <em class="bcp14">MUST NOT</em> cache 206 (Partial Content) responses. Furthermore, if a response uses a range unit that is not understood by the cache, then
    695          it <em class="bcp14">MUST NOT</em> be cached either.
    696       </p>
    697       <div id="rfc.iref.4"></div>
    698       <div id="rfc.iref.s.2"></div>
    699       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h2>
    700       <p id="rfc.section.3.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;5.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request
    701          did not include an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>). (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current
    702          length of the selected resource.)
    703       </p>
    704       <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range header field specifying the current length of the representation (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.
    705       </p>
    706       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Ranges</a></h1>
    707       <p id="rfc.section.4.p.1">A response might transfer only a subrange of a representation, either because the request included one or more Range specifications,
    708          or because a connection closed prematurely. After several such transfers, a cache might have received several ranges of the
    709          same representation.
    710       </p>
    711       <p id="rfc.section.4.p.2">If a cache has a stored non-empty set of subranges for a representation, and an incoming response transfers another subrange,
    712          the cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
    713       </p>
    714       <ul>
    715          <li>Both the incoming response and the cache entry have a cache validator.</li>
    716          <li>The two cache validators match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    717          </li>
    718       </ul>
    719       <p id="rfc.section.4.p.3">If either requirement is not met, the cache <em class="bcp14">MUST</em> use only the most recent partial response (based on the Date values transmitted with every response, and using the incoming
    720          response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
    721       </p>
    722       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
    723       <p id="rfc.section.5.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to range requests and partial responses.</p>
    724       <div id="rfc.iref.a.1"></div>
    725       <div id="rfc.iref.h.1"></div>
    726       <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2>
    727       <p id="rfc.section.5.1.p.1">The "Accept-Ranges" header field allows a resource to indicate its acceptance of range requests.</p>
    728       <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
     673            unit defined by HTTP/1.1 is "bytes". Additional specifiers can be defined as described in <a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a>.
     674         </p>
     675         <p id="rfc.section.2.p.4">If a range unit is not understood in a request, a server <em class="bcp14">MUST</em> ignore the whole Range header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;5.4</a>). If a range unit is not understood in a response, an intermediary <em class="bcp14">SHOULD</em> pass the response to the client; a client <em class="bcp14">MUST</em> fail.
     676         </p>
     677         <div id="range.specifier.registry">
     678            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#range.specifier.registry">Range Specifier Registry</a></h2>
     679            <p id="rfc.section.2.1.p.1">The HTTP Range Specifier Registry defines the name space for the range specifier names.</p>
     680            <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     681            </p>
     682            <ul>
     683               <li>Name</li>
     684               <li>Description</li>
     685               <li>Pointer to specification text</li>
     686            </ul>
     687            <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     688            </p>
     689            <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt;.
     690            </p>
     691         </div>
     692      </div>
     693      <div id="status.code.definitions">
     694         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#status.code.definitions">Status Code Definitions</a></h1>
     695         <div id="status.206">
     696            <div id="rfc.iref.2.1"></div>
     697            <div id="rfc.iref.s.1"></div>
     698            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#status.206">206 Partial Content</a></h2>
     699            <p id="rfc.section.3.1.p.1">The server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a Range header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;5.4</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;5.3</a>) to make the request conditional.
     700            </p>
     701            <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
     702            </p>
     703            <ul>
     704               <li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;5.2</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields
     705                  for each part. If a Content-Length header field is present in the response, its value <em class="bcp14">MUST</em> match the actual number of octets transmitted in the message-body.
     706               </li>
     707               <li>Date</li>
     708               <li>Cache-Control, ETag, Expires, Content-Location, Last-Modified, and/or Vary, if the header field would have been sent in a
     709                  200 response to the same request
     710               </li>
     711            </ul>
     712            <p id="rfc.section.3.1.p.3">If the 206 response is the result of an If-Range request, the response <em class="bcp14">SHOULD NOT</em> include other representation header fields. Otherwise, the response <em class="bcp14">MUST</em> include all of the representation header fields that would have been returned with a 200 (OK) response to the same request.
     713            </p>
     714            <p id="rfc.section.3.1.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified header fields do not match exactly,
     715               see <a href="#combining.byte.ranges" title="Combining Ranges">Section&nbsp;4</a>.
     716            </p>
     717            <p id="rfc.section.3.1.p.5">A cache that does not support the Range and Content-Range header fields <em class="bcp14">MUST NOT</em> cache 206 (Partial Content) responses. Furthermore, if a response uses a range unit that is not understood by the cache, then
     718               it <em class="bcp14">MUST NOT</em> be cached either.
     719            </p>
     720         </div>
     721         <div id="status.416">
     722            <div id="rfc.iref.4.1"></div>
     723            <div id="rfc.iref.s.2"></div>
     724            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></h2>
     725            <p id="rfc.section.3.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;5.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request
     726               did not include an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>). (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current
     727               length of the selected resource.)
     728            </p>
     729            <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range header field specifying the current length of the representation (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.
     730            </p>
     731         </div>
     732      </div>
     733      <div id="combining.byte.ranges">
     734         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></h1>
     735         <p id="rfc.section.4.p.1">A response might transfer only a subrange of a representation, either because the request included one or more Range specifications,
     736            or because a connection closed prematurely. After several such transfers, a cache might have received several ranges of the
     737            same representation.
     738         </p>
     739         <p id="rfc.section.4.p.2">If a cache has a stored non-empty set of subranges for a representation, and an incoming response transfers another subrange,
     740            the cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
     741         </p>
     742         <ul>
     743            <li>Both the incoming response and the cache entry have a cache validator.</li>
     744            <li>The two cache validators match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
     745            </li>
     746         </ul>
     747         <p id="rfc.section.4.p.3">If either requirement is not met, the cache <em class="bcp14">MUST</em> use only the most recent partial response (based on the Date values transmitted with every response, and using the incoming
     748            response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
     749         </p>
     750      </div>
     751      <div id="header.fields">
     752         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     753         <p id="rfc.section.5.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to range requests and partial responses.</p>
     754         <div id="header.accept-ranges">
     755            <div id="rfc.iref.a.1"></div>
     756            <div id="rfc.iref.h.1"></div>
     757            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></h2>
     758            <p id="rfc.section.5.1.p.1">The "Accept-Ranges" header field allows a resource to indicate its acceptance of range requests.</p>
     759            <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
    729760  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
    730761</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
    731       </p>
    732       <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: bytes
     762            </p>
     763            <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: bytes
    733764</pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <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>.
    734       </p>
    735       <p id="rfc.section.5.1.p.6">Servers that do not accept any kind of range request for a resource <em class="bcp14">MAY</em> send
    736       </p>
    737       <div id="rfc.figure.u.7"></div><pre class="text">  Accept-Ranges: none
     765            </p>
     766            <p id="rfc.section.5.1.p.6">Servers that do not accept any kind of range request for a resource <em class="bcp14">MAY</em> send
     767            </p>
     768            <div id="rfc.figure.u.7"></div><pre class="text">  Accept-Ranges: none
    738769</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
    739       <div id="rfc.iref.c.1"></div>
    740       <div id="rfc.iref.h.2"></div>
    741       <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="header.content-range" href="#header.content-range">Content-Range</a></h2>
    742       <p id="rfc.section.5.2.p.1">The "Content-Range" header field is sent with a partial representation to specify where in the full representation the payload
    743          body is intended to be applied.
    744       </p>
    745       <p id="rfc.section.5.2.p.2">Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
    746       </p>
    747       <div id="rfc.figure.u.8"></div><pre class="inline"><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="#header.content-range" class="smpl">Content-Range</a> = <a href="#header.content-range" class="smpl">content-range-spec</a>
     770         </div>
     771         <div id="header.content-range">
     772            <div id="rfc.iref.c.1"></div>
     773            <div id="rfc.iref.h.2"></div>
     774            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#header.content-range">Content-Range</a></h2>
     775            <p id="rfc.section.5.2.p.1">The "Content-Range" header field is sent with a partial representation to specify where in the full representation the payload
     776               body is intended to be applied.
     777            </p>
     778            <p id="rfc.section.5.2.p.2">Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
     779            </p>
     780            <div id="rfc.figure.u.8"></div><pre class="inline"><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="#header.content-range" class="smpl">Content-Range</a> = <a href="#header.content-range" class="smpl">content-range-spec</a>
    748781 
    749782  <a href="#header.content-range" class="smpl">content-range-spec</a>      = <a href="#header.content-range" class="smpl">byte-content-range-spec</a>
     
    762795  <a href="#header.content-range" class="smpl">other-range-resp-spec</a>    = *<a href="#notation" class="smpl">CHAR</a>
    763796</pre><p id="rfc.section.5.2.p.4">The header field <em class="bcp14">SHOULD</em> indicate the total length of the full representation, unless this length is unknown or difficult to determine. The asterisk
    764          "*" character means that the instance-length is unknown at the time when the response was generated.
    765       </p>
    766       <p id="rfc.section.5.2.p.5">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;5.4.1</a>), a byte-range-resp-spec <em class="bcp14">MUST</em> only specify one range, and <em class="bcp14">MUST</em> contain absolute byte positions for both the first and last byte of the range.
    767       </p>
    768       <p id="rfc.section.5.2.p.6">A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos value is less than its first-byte-pos value, or
    769          whose instance-length value is less than or equal to its last-byte-pos value, is invalid. The recipient of an invalid byte-content-range-spec <em class="bcp14">MUST</em> ignore it and any content transferred along with it.
    770       </p>
    771       <p id="rfc.section.5.2.p.7">In the case of a byte range request: A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
    772          selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
    773       </p>
    774       <p id="rfc.section.5.2.p.8">Examples of byte-content-range-spec values, assuming that the representation contains a total of 1234 bytes: </p>
    775       <ul>
    776          <li>The first 500 bytes:
    777             <div id="rfc.figure.u.9"></div><pre class="text">  bytes 0-499/1234
     797               "*" character means that the instance-length is unknown at the time when the response was generated.
     798            </p>
     799            <p id="rfc.section.5.2.p.5">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;5.4.1</a>), a byte-range-resp-spec <em class="bcp14">MUST</em> only specify one range, and <em class="bcp14">MUST</em> contain absolute byte positions for both the first and last byte of the range.
     800            </p>
     801            <p id="rfc.section.5.2.p.6">A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos value is less than its first-byte-pos value, or
     802               whose instance-length value is less than or equal to its last-byte-pos value, is invalid. The recipient of an invalid byte-content-range-spec <em class="bcp14">MUST</em> ignore it and any content transferred along with it.
     803            </p>
     804            <p id="rfc.section.5.2.p.7">In the case of a byte range request: A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
     805               selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
     806            </p>
     807            <p id="rfc.section.5.2.p.8">Examples of byte-content-range-spec values, assuming that the representation contains a total of 1234 bytes: </p>
     808            <ul>
     809               <li>The first 500 bytes: <span id="rfc.figure.u.9"></span><pre class="text">  bytes 0-499/1234
    778810</pre> </li>
    779          <li>The second 500 bytes:
    780             <div id="rfc.figure.u.10"></div><pre class="text">  bytes 500-999/1234
     811               <li>The second 500 bytes: <span id="rfc.figure.u.10"></span><pre class="text">  bytes 500-999/1234
    781812</pre> </li>
    782          <li>All except for the first 500 bytes:
    783             <div id="rfc.figure.u.11"></div><pre class="text">  bytes 500-1233/1234
     813               <li>All except for the first 500 bytes: <span id="rfc.figure.u.11"></span><pre class="text">  bytes 500-1233/1234
    784814</pre> </li>
    785          <li>The last 500 bytes:
    786             <div id="rfc.figure.u.12"></div><pre class="text">  bytes 734-1233/1234
     815               <li>The last 500 bytes: <span id="rfc.figure.u.12"></span><pre class="text">  bytes 734-1233/1234
    787816</pre> </li>
    788       </ul>
    789       <p id="rfc.section.5.2.p.9">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
    790          a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header field,
    791          and a Content-Length header field showing the number of bytes actually transferred. For example,
    792       </p>
    793       <div id="rfc.figure.u.13"></div><pre class="text">  HTTP/1.1 206 Partial Content
     817            </ul>
     818            <p id="rfc.section.5.2.p.9">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
     819               a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header field,
     820               and a Content-Length header field showing the number of bytes actually transferred. For example,
     821            </p>
     822            <div id="rfc.figure.u.13"></div><pre class="text">  HTTP/1.1 206 Partial Content
    794823  Date: Wed, 15 Nov 1995 06:25:24 GMT
    795824  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    798827  Content-Type: image/gif
    799828</pre><p id="rfc.section.5.2.p.11">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
    800          ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
    801          as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
    802       </p>
    803       <p id="rfc.section.5.2.p.12">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
    804       </p>
    805       <p id="rfc.section.5.2.p.13">When a client requests multiple ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
    806       </p>
    807       <p id="rfc.section.5.2.p.14">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
    808          the full representation).
    809       </p>
    810       <p id="rfc.section.5.2.p.15">If the server receives a request (other than one including an If-Range header field) with an unsatisfiable Range header field
    811          (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
    812          resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>).
    813       </p>
    814       <div class="note" id="rfc.section.5.2.p.16">
    815          <p> <b>Note:</b> Clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
    816             an unsatisfiable Range header field, since not all servers implement this header field.
    817          </p>
    818       </div>
    819       <div id="rfc.iref.i.1"></div>
    820       <div id="rfc.iref.h.3"></div>
    821       <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="header.if-range" href="#header.if-range">If-Range</a></h2>
    822       <p id="rfc.section.5.3.p.1">If a client has a partial copy of a representation in its cache, and wishes to have an up-to-date copy of the entire representation
    823          in its cache, it could use the Range header field with a conditional GET (using either or both of If-Unmodified-Since and
    824          If-Match.) However, if the condition fails because the representation has been modified, the client would then have to make
    825          a second request to obtain the entire current representation.
    826       </p>
    827       <p id="rfc.section.5.3.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is "if the representation
    828          is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation".
    829       </p>
    830       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
     829               ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
     830               as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
     831            </p>
     832            <p id="rfc.section.5.2.p.12">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
     833            </p>
     834            <p id="rfc.section.5.2.p.13">When a client requests multiple ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
     835            </p>
     836            <p id="rfc.section.5.2.p.14">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
     837               the full representation).
     838            </p>
     839            <p id="rfc.section.5.2.p.15">If the server receives a request (other than one including an If-Range header field) with an unsatisfiable Range header field
     840               (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
     841               resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>).
     842            </p>
     843            <div class="note" id="rfc.section.5.2.p.16">
     844               <p><b>Note:</b> Clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
     845                  an unsatisfiable Range header field, since not all servers implement this header field.
     846               </p>
     847            </div>
     848         </div>
     849         <div id="header.if-range">
     850            <div id="rfc.iref.i.1"></div>
     851            <div id="rfc.iref.h.3"></div>
     852            <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#header.if-range">If-Range</a></h2>
     853            <p id="rfc.section.5.3.p.1">If a client has a partial copy of a representation in its cache, and wishes to have an up-to-date copy of the entire representation
     854               in its cache, it could use the Range header field with a conditional GET (using either or both of If-Unmodified-Since and
     855               If-Match.) However, if the condition fails because the representation has been modified, the client would then have to make
     856               a second request to obtain the entire current representation.
     857            </p>
     858            <p id="rfc.section.5.3.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is "if the representation
     859               is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation".
     860            </p>
     861            <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
    831862</pre><p id="rfc.section.5.3.p.4">Only a strong validator (<a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>) is usable for range retrieval, since otherwise the client might end up with an internally inconsistent representation. Clients <em class="bcp14">MUST NOT</em> use weak validators in range requests. A cache or origin server receiving a conditional range request <em class="bcp14">MUST</em> use the strong comparison function to evaluate the condition.
    832       </p>
    833       <p id="rfc.section.5.3.p.5">If the client has no entity-tag for a representation, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header field. (The server can distinguish between a valid HTTP-date and any form of entity-tag
    834          by examining no more than two characters.) The If-Range header field <em class="bcp14">SHOULD</em> only be used together with a Range header field, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header field, or if the server does not support the sub-range operation.
    835       </p>
    836       <p id="rfc.section.5.3.p.6">If a client wishes to perform a sub-range retrieval on a value for which it has only a Last-Modified time and no opaque validator,
    837          it <em class="bcp14">MAY</em> do this only if the Last-Modified time is strong in the sense described in <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.1.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    838       </p>
    839       <p id="rfc.section.5.3.p.7">If the entity-tag given in the If-Range header field matches the current cache validator for the representation, then the
    840          server <em class="bcp14">SHOULD</em> provide the specified sub-range of the representation using a 206 (Partial Content) response. If the cache validator does
    841          not match, then the server <em class="bcp14">SHOULD</em> return the entire representation using a 200 (OK) response.
    842       </p>
    843       <div id="rfc.iref.r.1"></div>
    844       <div id="rfc.iref.h.4"></div>
    845       <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="header.range" href="#header.range">Range</a></h2>
    846       <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h3>
    847       <p id="rfc.section.5.4.1.p.1">Since all HTTP representations are transferred as sequences of bytes, the concept of a byte range is meaningful for any HTTP
    848          representation. (However, not all clients and servers need to support byte-range operations.)
    849       </p>
    850       <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the representation body (not necessarily the same as the
    851          message-body).
    852       </p>
    853       <div id="rule.ranges-specifier">
    854          <p id="rfc.section.5.4.1.p.3">                A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single representation.
    855          </p>
    856       </div>
    857       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
     863            </p>
     864            <p id="rfc.section.5.3.p.5">If the client has no entity-tag for a representation, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header field. (The server can distinguish between a valid HTTP-date and any form of entity-tag
     865               by examining no more than two characters.) The If-Range header field <em class="bcp14">SHOULD</em> only be used together with a Range header field, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header field, or if the server does not support the sub-range operation.
     866            </p>
     867            <p id="rfc.section.5.3.p.6">If a client wishes to perform a sub-range retrieval on a value for which it has only a Last-Modified time and no opaque validator,
     868               it <em class="bcp14">MAY</em> do this only if the Last-Modified time is strong in the sense described in <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.1.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
     869            </p>
     870            <p id="rfc.section.5.3.p.7">If the entity-tag given in the If-Range header field matches the current cache validator for the representation, then the
     871               server <em class="bcp14">SHOULD</em> provide the specified sub-range of the representation using a 206 (Partial Content) response. If the cache validator does
     872               not match, then the server <em class="bcp14">SHOULD</em> return the entire representation using a 200 (OK) response.
     873            </p>
     874         </div>
     875         <div id="header.range">
     876            <div id="rfc.iref.r.1"></div>
     877            <div id="rfc.iref.h.4"></div>
     878            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.range">Range</a></h2>
     879            <div id="byte.ranges">
     880               <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a href="#byte.ranges">Byte Ranges</a></h3>
     881               <p id="rfc.section.5.4.1.p.1">Since all HTTP representations are transferred as sequences of bytes, the concept of a byte range is meaningful for any HTTP
     882                  representation. (However, not all clients and servers need to support byte-range operations.)
     883               </p>
     884               <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the representation body (not necessarily the same as the
     885                  message-body).
     886               </p>
     887               <div id="rule.ranges-specifier">
     888                  <p id="rfc.section.5.4.1.p.3">        A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single representation.
     889                  </p>
     890               </div>
     891               <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
    858892  <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> )
    859893  <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> ]
     
    861895  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
    862896</pre><p id="rfc.section.5.4.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value
    863          gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
    864          at zero.
    865       </p>
    866       <p id="rfc.section.5.4.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The
    867          recipient of a byte-range-set that includes one or more syntactically invalid byte-range-spec values <em class="bcp14">MUST</em> ignore the header field that includes that byte-range-set.
    868       </p>
    869       <p id="rfc.section.5.4.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the representation
    870          body, last-byte-pos is taken to be equal to one less than the current length of the representation in bytes.
    871       </p>
    872       <p id="rfc.section.5.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the representation.</p>
    873       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
     897                  gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
     898                  at zero.
     899               </p>
     900               <p id="rfc.section.5.4.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The
     901                  recipient of a byte-range-set that includes one or more syntactically invalid byte-range-spec values <em class="bcp14">MUST</em> ignore the header field that includes that byte-range-set.
     902               </p>
     903               <p id="rfc.section.5.4.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the representation
     904                  body, last-byte-pos is taken to be equal to one less than the current length of the representation in bytes.
     905               </p>
     906               <p id="rfc.section.5.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the representation.</p>
     907               <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
    874908  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    875909</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the representation body, of a length given by the suffix-length
    876          value. (That is, this form specifies the last N bytes of a representation.) If the representation is shorter than the specified
    877          suffix-length, the entire representation is used.
    878       </p>
    879       <p id="rfc.section.5.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current
    880          length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set
    881          is satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> return a response with a 416 (Requested range not satisfiable) status code. Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a 206 (Partial Content) status code containing the satisfiable ranges of the representation.
    882       </p>
    883       <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p>
    884       <ul>
    885          <li>The first 500 bytes (byte offsets 0-499, inclusive):
    886             <div id="rfc.figure.u.17"></div><pre class="text">  bytes=0-499
     910                  value. (That is, this form specifies the last N bytes of a representation.) If the representation is shorter than the specified
     911                  suffix-length, the entire representation is used.
     912               </p>
     913               <p id="rfc.section.5.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current
     914                  length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set
     915                  is satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> return a response with a 416 (Requested range not satisfiable) status code. Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a 206 (Partial Content) status code containing the satisfiable ranges of the representation.
     916               </p>
     917               <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p>
     918               <ul>
     919                  <li>The first 500 bytes (byte offsets 0-499, inclusive): <span id="rfc.figure.u.17"></span><pre class="text">  bytes=0-499
    887920</pre> </li>
    888          <li>The second 500 bytes (byte offsets 500-999, inclusive):
    889             <div id="rfc.figure.u.18"></div><pre class="text">  bytes=500-999
     921                  <li>The second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.18"></span><pre class="text">  bytes=500-999
    890922</pre> </li>
    891          <li>The final 500 bytes (byte offsets 9500-9999, inclusive):
    892             <div id="rfc.figure.u.19"></div><pre class="text">  bytes=-500
    893 </pre> Or: <div id="rfc.figure.u.20"></div><pre class="text">  bytes=9500-
     923                  <li>The final 500 bytes (byte offsets 9500-9999, inclusive): <span id="rfc.figure.u.19"></span><pre class="text">  bytes=-500
     924</pre> Or: <span id="rfc.figure.u.20"></span><pre class="text">  bytes=9500-
    894925</pre> </li>
    895          <li>The first and last bytes only (bytes 0 and 9999):
    896             <div id="rfc.figure.u.21"></div><pre class="text">  bytes=0-0,-1
     926                  <li>The first and last bytes only (bytes 0 and 9999): <span id="rfc.figure.u.21"></span><pre class="text">  bytes=0-0,-1
    897927</pre> </li>
    898          <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive):
    899             <div id="rfc.figure.u.22"></div><pre class="text">  bytes=500-600,601-999
     928                  <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.22"></span><pre class="text">  bytes=500-600,601-999
    900929  bytes=500-700,601-999
    901930</pre> </li>
    902       </ul>
    903       <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;<a id="range.retrieval.requests" href="#range.retrieval.requests">Range Retrieval Requests</a></h3>
    904       <p id="rfc.section.5.4.2.p.1">The "Range" header field defines the GET method (conditional or not) to request one or more sub-ranges of the response representation
    905          body, instead of the entire representation body.
    906       </p>
    907       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
     931               </ul>
     932            </div>
     933            <div id="range.retrieval.requests">
     934               <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></h3>
     935               <p id="rfc.section.5.4.2.p.1">The "Range" header field defines the GET method (conditional or not) to request one or more sub-ranges of the response representation
     936                  body, instead of the entire representation body.
     937               </p>
     938               <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
    908939  <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = <a href="#range.units" class="smpl">other-range-unit</a> "=" <a href="#range.retrieval.requests" class="smpl">other-range-set</a>
    909940  <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#notation" class="smpl">CHAR</a>
    910941</pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header field. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when
    911          possible, since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval
    912          of large representations.
    913       </p>
    914       <p id="rfc.section.5.4.2.p.4">If the server supports the Range header field and the specified range or ranges are appropriate for the representation: </p>
    915       <ul>
    916          <li>The presence of a Range header field in an unconditional GET modifies what is returned if the GET is otherwise successful.
    917             In other words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
    918          </li>
    919          <li>The presence of a Range header field in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match,
    920             or one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
    921             is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
    922          </li>
    923       </ul>
    924       <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header field (see <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section&nbsp;5.3</a>) in addition to the Range header field.
    925       </p>
    926       <p id="rfc.section.5.4.2.p.6">If a proxy that supports ranges receives a Range request, forwards the request to an inbound server, and receives an entire
    927          representation in reply, it <em class="bcp14">MAY</em> only return the requested range to its client.
    928       </p>
    929       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    930       <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2>
    931       <p id="rfc.section.6.1.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:
    932       </p>
    933       <div id="rfc.table.1">
    934          <div id="iana.status.code.registration.table"></div>
    935          <table class="tt full left" cellpadding="3" cellspacing="0">
    936             <thead>
    937                <tr>
    938                   <th>Value</th>
    939                   <th>Description</th>
    940                   <th>Reference</th>
    941                </tr>
    942             </thead>
    943             <tbody>
    944                <tr>
    945                   <td class="left">206</td>
    946                   <td class="left">Partial Content</td>
    947                   <td class="left"> <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;3.1</a>
    948                   </td>
    949                </tr>
    950                <tr>
    951                   <td class="left">416</td>
    952                   <td class="left">Requested Range Not Satisfiable</td>
    953                   <td class="left"> <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>
    954                   </td>
    955                </tr>
    956             </tbody>
    957          </table>
     942                  possible, since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval
     943                  of large representations.
     944               </p>
     945               <p id="rfc.section.5.4.2.p.4">If the server supports the Range header field and the specified range or ranges are appropriate for the representation: </p>
     946               <ul>
     947                  <li>The presence of a Range header field in an unconditional GET modifies what is returned if the GET is otherwise successful.
     948                     In other words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
     949                  </li>
     950                  <li>The presence of a Range header field in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match,
     951                     or one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
     952                     is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
     953                  </li>
     954               </ul>
     955               <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header field (see <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section&nbsp;5.3</a>) in addition to the Range header field.
     956               </p>
     957               <p id="rfc.section.5.4.2.p.6">If a proxy that supports ranges receives a Range request, forwards the request to an inbound server, and receives an entire
     958                  representation in reply, it <em class="bcp14">MAY</em> only return the requested range to its client.
     959               </p>
     960            </div>
     961         </div>
    958962      </div>
    959       <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    960       <p id="rfc.section.6.2.p.1">The Message Header Field Registry located 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; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
    961       </p>
    962       <div id="rfc.table.2">
    963          <div id="iana.header.registration.table"></div>
    964          <table class="tt full left" cellpadding="3" cellspacing="0">
    965             <thead>
    966                <tr>
    967                   <th>Header Field Name</th>
    968                   <th>Protocol</th>
    969                   <th>Status</th>
    970                   <th>Reference</th>
    971                </tr>
    972             </thead>
    973             <tbody>
    974                <tr>
    975                   <td class="left">Accept-Ranges</td>
    976                   <td class="left">http</td>
    977                   <td class="left">standard</td>
    978                   <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
    979                   </td>
    980                </tr>
    981                <tr>
    982                   <td class="left">Content-Range</td>
    983                   <td class="left">http</td>
    984                   <td class="left">standard</td>
    985                   <td class="left"> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
    986                   </td>
    987                </tr>
    988                <tr>
    989                   <td class="left">If-Range</td>
    990                   <td class="left">http</td>
    991                   <td class="left">standard</td>
    992                   <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">Section&nbsp;5.3</a>
    993                   </td>
    994                </tr>
    995                <tr>
    996                   <td class="left">Range</td>
    997                   <td class="left">http</td>
    998                   <td class="left">standard</td>
    999                   <td class="left"> <a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a>
    1000                   </td>
    1001                </tr>
    1002             </tbody>
    1003          </table>
     963      <div id="IANA.considerations">
     964         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     965         <div id="status.code.registration">
     966            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h2>
     967            <p id="rfc.section.6.1.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:
     968            </p>
     969            <div id="rfc.table.1">
     970               <div id="iana.status.code.registration.table"></div>
     971               <table class="tt full left" cellpadding="3" cellspacing="0">
     972                  <thead>
     973                     <tr>
     974                        <th>Value</th>
     975                        <th>Description</th>
     976                        <th>Reference</th>
     977                     </tr>
     978                  </thead>
     979                  <tbody>
     980                     <tr>
     981                        <td class="left">206</td>
     982                        <td class="left">Partial Content</td>
     983                        <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;3.1</a>
     984                        </td>
     985                     </tr>
     986                     <tr>
     987                        <td class="left">416</td>
     988                        <td class="left">Requested Range Not Satisfiable</td>
     989                        <td class="left"><a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>
     990                        </td>
     991                     </tr>
     992                  </tbody>
     993               </table>
     994            </div>
     995         </div>
     996         <div id="header.field.registration">
     997            <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
     998            <p id="rfc.section.6.2.p.1">The Message Header Field Registry located 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; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
     999            </p>
     1000            <div id="rfc.table.2">
     1001               <div id="iana.header.registration.table"></div>
     1002               <table class="tt full left" cellpadding="3" cellspacing="0">
     1003                  <thead>
     1004                     <tr>
     1005                        <th>Header Field Name</th>
     1006                        <th>Protocol</th>
     1007                        <th>Status</th>
     1008                        <th>Reference</th>
     1009                     </tr>
     1010                  </thead>
     1011                  <tbody>
     1012                     <tr>
     1013                        <td class="left">Accept-Ranges</td>
     1014                        <td class="left">http</td>
     1015                        <td class="left">standard</td>
     1016                        <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
     1017                        </td>
     1018                     </tr>
     1019                     <tr>
     1020                        <td class="left">Content-Range</td>
     1021                        <td class="left">http</td>
     1022                        <td class="left">standard</td>
     1023                        <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
     1024                        </td>
     1025                     </tr>
     1026                     <tr>
     1027                        <td class="left">If-Range</td>
     1028                        <td class="left">http</td>
     1029                        <td class="left">standard</td>
     1030                        <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">Section&nbsp;5.3</a>
     1031                        </td>
     1032                     </tr>
     1033                     <tr>
     1034                        <td class="left">Range</td>
     1035                        <td class="left">http</td>
     1036                        <td class="left">standard</td>
     1037                        <td class="left"><a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a>
     1038                        </td>
     1039                     </tr>
     1040                  </tbody>
     1041               </table>
     1042            </div>
     1043            <p id="rfc.section.6.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1044         </div>
     1045         <div id="range.specifier.registration">
     1046            <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a href="#range.specifier.registration">Range Specifier Registration</a></h2>
     1047            <p id="rfc.section.6.3.p.1">The registration procedure for HTTP Range Specifiers is defined by <a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a> of this document.
     1048            </p>
     1049            <p id="rfc.section.6.3.p.2">The HTTP Range Specifier Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt; and be populated with the registrations below:
     1050            </p>
     1051            <div id="rfc.table.3">
     1052               <div id="iana.range.specifiers.table"></div>
     1053               <table class="tt full left" cellpadding="3" cellspacing="0">
     1054                  <thead>
     1055                     <tr>
     1056                        <th>Range Specifier Name</th>
     1057                        <th>Description</th>
     1058                        <th>Reference</th>
     1059                     </tr>
     1060                  </thead>
     1061                  <tbody>
     1062                     <tr>
     1063                        <td class="left">bytes</td>
     1064                        <td class="left">a range of octets</td>
     1065                        <td class="left">(this specification)</td>
     1066                     </tr>
     1067                  </tbody>
     1068               </table>
     1069            </div>
     1070            <p id="rfc.section.6.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1071         </div>
    10041072      </div>
    1005       <p id="rfc.section.6.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    1006       <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="range.specifier.registration" href="#range.specifier.registration">Range Specifier Registration</a></h2>
    1007       <p id="rfc.section.6.3.p.1">The registration procedure for HTTP Range Specifiers is defined by <a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a> of this document.
    1008       </p>
    1009       <p id="rfc.section.6.3.p.2">The HTTP Range Specifier Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt; and be populated with the registrations below:
    1010       </p>
    1011       <div id="rfc.table.3">
    1012          <div id="iana.range.specifiers.table"></div>
    1013          <table class="tt full left" cellpadding="3" cellspacing="0">
    1014             <thead>
    1015                <tr>
    1016                   <th>Range Specifier Name</th>
    1017                   <th>Description</th>
    1018                   <th>Reference</th>
    1019                </tr>
    1020             </thead>
    1021             <tbody>
    1022                <tr>
    1023                   <td class="left">bytes</td>
    1024                   <td class="left">a range of octets</td>
    1025                   <td class="left">(this specification)</td>
    1026                </tr>
    1027             </tbody>
    1028          </table>
     1073      <div id="security.considerations">
     1074         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     1075         <p id="rfc.section.7.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     1076         </p>
    10291077      </div>
    1030       <p id="rfc.section.6.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    1031       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    1032       <p id="rfc.section.7.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    1033       </p>
    1034       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    1035       <p id="rfc.section.8.p.1">Most of the specification of ranges is based on work originally done by Ari Luotonen and John Franks, with additional input
    1036          from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
    1037          Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
    1038       </p>
     1078      <div id="ack">
     1079         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     1080         <p id="rfc.section.8.p.1">Most of the specification of ranges is based on work originally done by Ari Luotonen and John Franks, with additional input
     1081            from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
     1082            Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
     1083         </p>
     1084      </div>
    10391085      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
    10401086      </h1>
    10411087      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
    10421088      </h2>
    1043       <table>         
     1089      <table>
    10441090         <tr>
    10451091            <td class="reference"><b id="Part1">[Part1]</b></td>
    1046             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-14">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-14 (work in progress), April&nbsp;2011.
     1092            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-14">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-14 (work in progress), April&nbsp;2011.
    10471093            </td>
    10481094         </tr>
    10491095         <tr>
    10501096            <td class="reference"><b id="Part4">[Part4]</b></td>
    1051             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-14">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-14 (work in progress), April&nbsp;2011.
     1097            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-14">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-14 (work in progress), April&nbsp;2011.
    10521098            </td>
    10531099         </tr>
    10541100         <tr>
    10551101            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    1056             <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
     1102            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="https://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
    10571103            </td>
    10581104         </tr>
    10591105         <tr>
    10601106            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    1061             <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
     1107            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
    10621108            </td>
    10631109         </tr>
    10641110         <tr>
    10651111            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    1066             <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     1112            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
    10671113            </td>
    10681114         </tr>
     
    10701116      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
    10711117      </h2>
    1072       <table>       
     1118      <table>
    10731119         <tr>
    10741120            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    1075             <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     1121            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    10761122            </td>
    10771123         </tr>
    10781124         <tr>
    10791125            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    1080             <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
     1126            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
    10811127            </td>
    10821128         </tr>
    10831129         <tr>
    10841130            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
    1085             <td class="top"><a href="mailto:ned.freed@mrochek.com" title="Sun Microsystems">Freed, N.</a> and <a href="mailto:klensin+ietf@jck.com">J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
     1131            <td class="top"><a href="mailto:ned.freed@mrochek.com" title="Sun Microsystems">Freed, N.</a> and <a href="mailto:klensin+ietf@jck.com">J. Klensin</a>, “<a href="https://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
    10861132            </td>
    10871133         </tr>
    10881134         <tr>
    10891135            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
    1090             <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
     1136            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
    10911137            </td>
    10921138         </tr>
    10931139      </table>
    1094       <div class="avoidbreak">
    1095          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    1096          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    1097                (editor)
    1098                <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
    1099          <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">Alcatel-Lucent Bell Labs</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:jg@freedesktop.org"><span class="email">jg@freedesktop.org</span></a></span><span class="vcardline">URI: <a href="http://gettys.wordpress.com/" class="url">http://gettys.wordpress.com/</a></span></address>
    1100          <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:JeffMogul@acm.org"><span class="email">JeffMogul@acm.org</span></a></span></address>
    1101          <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:henrikn@microsoft.com"><span class="email">henrikn@microsoft.com</span></a></span></address>
    1102          <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:LMM@acm.org"><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address>
    1103          <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span></span><span class="vcardline">Email: <a href="mailto:paulle@microsoft.com"><span class="email">paulle@microsoft.com</span></a></span></address>
    1104          <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:timbl@w3.org"><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address>
    1105          <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
    1106                (editor)
    1107                <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span>&nbsp;<span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">Email: <a href="mailto:ylafon@w3.org"><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address>
    1108          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
    1109                (editor)
    1110                <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
    1111       </div>
    1112       <div id="rfc.iref.m.1"></div>
    1113       <div id="rfc.iref.m.2"></div>
    1114       <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>
    1115       <p id="rfc.section.A.p.1">When an HTTP 206 (Partial Content) response message includes the content of multiple ranges (a response to a request for multiple
    1116          non-overlapping ranges), these are transmitted as a multipart message-body (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-5.1">Section 5.1</a>). The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
    1117       </p>
    1118       <div class="note" id="rfc.section.A.p.2">
    1119          <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
    1120          </p>
    1121       </div>
    1122       <p id="rfc.section.A.p.3">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
    1123          required boundary parameter specifies the boundary string used to separate each body-part.
    1124       </p>
    1125       <p id="rfc.section.A.p.4"> </p>
    1126       <dl>
    1127          <dt>Type name:</dt>
    1128          <dd>multipart</dd>
    1129          <dt>Subtype name:</dt>
    1130          <dd>byteranges</dd>
    1131          <dt>Required parameters:</dt>
    1132          <dd>boundary</dd>
    1133          <dt>Optional parameters:</dt>
    1134          <dd>none</dd>
    1135          <dt>Encoding considerations:</dt>
    1136          <dd>only "7bit", "8bit", or "binary" are permitted</dd>
    1137          <dt>Security considerations:</dt>
    1138          <dd>none</dd>
    1139          <dt>Interoperability considerations:</dt>
    1140          <dd>none</dd>
    1141          <dt>Published specification:</dt>
    1142          <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
    1143          </dd>
    1144          <dt>Applications that use this media type:</dt>
    1145          <dt>Additional information:</dt>
    1146          <dd>
    1147             <dl>
    1148                <dt>Magic number(s):</dt>
    1149                <dd>none</dd>
    1150                <dt>File extension(s):</dt>
    1151                <dd>none</dd>
    1152                <dt>Macintosh file type code(s):</dt>
    1153                <dd>none</dd>
    1154             </dl>
    1155          </dd>
    1156          <dt>Person and email address to contact for further information:</dt>
    1157          <dd>See Authors Section.</dd>
    1158          <dt>Intended usage:</dt>
    1159          <dd>COMMON</dd>
    1160          <dt>Restrictions on usage:</dt>
    1161          <dd>none</dd>
    1162          <dt>Author/Change controller:</dt>
    1163          <dd>IESG</dd>
    1164       </dl>
    1165       <div id="rfc.figure.u.24"></div>
    1166       <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
     1140      <div id="internet.media.type.multipart.byteranges">
     1141         <div id="rfc.iref.m.1"></div>
     1142         <div id="rfc.iref.m.2"></div>
     1143         <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>
     1144         <p id="rfc.section.A.p.1">When an HTTP 206 (Partial Content) response message includes the content of multiple ranges (a response to a request for multiple
     1145            non-overlapping ranges), these are transmitted as a multipart message-body (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="https://tools.ietf.org/html/rfc2046#section-5.1">Section 5.1</a>). The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
     1146         </p>
     1147         <div class="note" id="rfc.section.A.p.2">
     1148            <p><b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
     1149            </p>
     1150         </div>
     1151         <p id="rfc.section.A.p.3">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
     1152            required boundary parameter specifies the boundary string used to separate each body-part.
     1153         </p>
     1154         <p id="rfc.section.A.p.4"></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            <dt>Additional information:</dt>
     1175            <dd>
     1176               <dl>
     1177                  <dt>Magic number(s):</dt>
     1178                  <dd>none</dd>
     1179                  <dt>File extension(s):</dt>
     1180                  <dd>none</dd>
     1181                  <dt>Macintosh file type code(s):</dt>
     1182                  <dd>none</dd>
     1183               </dl>
     1184            </dd>
     1185            <dt>Person and email address to contact for further information:</dt>
     1186            <dd>See Authors Section.</dd>
     1187            <dt>Intended usage:</dt>
     1188            <dd>COMMON</dd>
     1189            <dt>Restrictions on usage:</dt>
     1190            <dd>none</dd>
     1191            <dt>Author/Change controller:</dt>
     1192            <dd>IESG</dd>
     1193         </dl>
     1194         <div id="rfc.figure.u.24"></div>
     1195         <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
    11671196  Date: Wed, 15 Nov 1995 06:25:24 GMT
    11681197  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    11811210  --THIS_STRING_SEPARATES--
    11821211</pre><div id="rfc.figure.u.25"></div>
    1183       <p>Other example:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
     1212         <p>Other example:</p><pre class="text">  HTTP/1.1 206 Partial Content
    11841213  Date: Tue, 14 Nov 1995 06:25:24 GMT
    11851214  Last-Modified: Tue, 14 July 04:58:08 GMT
     
    11971226  ...the second range
    11981227  --THIS_STRING_SEPARATES--
    1199 </pre> <p id="rfc.section.A.p.7">Notes: </p>
    1200       <ol>
    1201          <li>Additional CRLFs <em class="bcp14">MAY</em> precede the first boundary string in the body.
    1202          </li>
    1203          <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.
    1204          </li>
    1205          <li>A number of browsers and servers were coded to an early draft of the byteranges specification to use 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 the version documented in HTTP/1.1.
    1206          </li>
    1207       </ol>
    1208       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    1209       <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    1210       <p id="rfc.section.B.1.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
    1211       </p>
    1212       <p id="rfc.section.B.1.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;5</a>)
    1213       </p>
    1214       <p id="rfc.section.B.1.p.3">Clarify that 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>)
    1215       </p>
    1216       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1217       <div id="rfc.figure.u.26"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
     1228</pre><p id="rfc.section.A.p.7">Notes: </p>
     1229         <ol>
     1230            <li>Additional CRLFs <em class="bcp14">MAY</em> precede the first boundary string in the body.
     1231            </li>
     1232            <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.
     1233            </li>
     1234            <li>A number of browsers and servers were coded to an early draft of the byteranges specification to use 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 the version documented in HTTP/1.1.
     1235            </li>
     1236         </ol>
     1237      </div>
     1238      <div id="compatibility">
     1239         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
     1240         <div id="changes.from.rfc.2616">
     1241            <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     1242            <p id="rfc.section.B.1.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
     1243            </p>
     1244            <p id="rfc.section.B.1.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;5</a>)
     1245            </p>
     1246            <p id="rfc.section.B.1.p.3">Clarify that 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>)
     1247            </p>
     1248         </div>
     1249      </div>
     1250      <div id="collected.abnf">
     1251         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     1252         <div id="rfc.figure.u.26"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
    12181253
    12191254<a href="#header.content-range" class="smpl">Content-Range</a> = content-range-spec
     
    12331268 instance-length / "*" )
    12341269<a href="#header.content-range" class="smpl">byte-range-resp-spec</a> = ( first-byte-pos "-" last-byte-pos ) / "*"
    1235 <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = ( *( "," OWS ) byte-range-spec ) / (
    1236  suffix-byte-range-spec *( OWS "," [ ( OWS byte-range-spec ) /
    1237  suffix-byte-range-spec ] ) )
     1270<a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = *( "," OWS ) ( byte-range-spec /
     1271 suffix-byte-range-spec ) *( OWS "," [ OWS ( byte-range-spec /
     1272 suffix-byte-range-spec ) ] )
    12381273<a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ]
    12391274<a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set
     
    12631298
    12641299<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
    1265 </pre> <div id="rfc.figure.u.27"></div>
    1266       <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
     1300</pre><div id="rfc.figure.u.27"></div>
     1301         <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
    12671302; Content-Range defined but not used
    12681303; If-Range defined but not used
    12691304; Range defined but not used
    1270 </pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    1271       <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC 2616
    1272       </h2>
    1273       <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    1274       </p>
    1275       <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
    1276       </h2>
    1277       <p id="rfc.section.D.2.p.1">Closed issues: </p>
    1278       <ul>
    1279          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/18">http://tools.ietf.org/wg/httpbis/trac/ticket/18</a>&gt;: "Cache validators in 206 responses" (&lt;<a href="http://purl.org/NET/http-errata#ifrange206">http://purl.org/NET/http-errata#ifrange206</a>&gt;)
    1280          </li>
    1281          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
    1282          </li>
    1283          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/86">http://tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
    1284          </li>
    1285       </ul>
    1286       <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
    1287       </h2>
    1288       <p id="rfc.section.D.3.p.1">Closed issues: </p>
    1289       <ul>
    1290          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/55">http://tools.ietf.org/wg/httpbis/trac/ticket/55</a>&gt;: "Updating to RFC4288"
    1291          </li>
    1292       </ul>
    1293       <p id="rfc.section.D.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    1294       </p>
    1295       <ul>
    1296          <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    1297       </ul>
    1298       <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></h2>
    1299       <p id="rfc.section.D.4.p.1">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    1300       </p>
    1301       <ul>
    1302          <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
    1303       </ul>
    1304       <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></h2>
    1305       <p id="rfc.section.D.5.p.1">None.</p>
    1306       <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></h2>
    1307       <p id="rfc.section.D.6.p.1">Closed issues: </p>
    1308       <ul>
    1309          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/133">http://tools.ietf.org/wg/httpbis/trac/ticket/133</a>&gt;: "multipart/byteranges minimum number of parts"
    1310          </li>
    1311       </ul>
    1312       <p id="rfc.section.D.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    1313       </p>
    1314       <ul>
    1315          <li>Use "/" instead of "|" for alternatives.</li>
    1316          <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
    1317          <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    1318       </ul>
    1319       <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></h2>
    1320       <p id="rfc.section.D.7.p.1">Closed issues: </p>
    1321       <ul>
    1322          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/142">http://tools.ietf.org/wg/httpbis/trac/ticket/142</a>&gt;: "State base for *-byte-pos and suffix-length"
    1323          </li>
    1324       </ul>
    1325       <p id="rfc.section.D.7.p.2">Ongoing work on Custom Ranges (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>&gt;):
    1326       </p>
    1327       <ul>
    1328          <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
    1329       </ul>
    1330       <p id="rfc.section.D.7.p.3">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    1331       </p>
    1332       <ul>
    1333          <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    1334       </ul>
    1335       <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></h2>
    1336       <p id="rfc.section.D.8.p.1">Closed issues: </p>
    1337       <ul>
    1338          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
    1339          </li>
    1340       </ul>
    1341       <h2 id="rfc.section.D.9"><a href="#rfc.section.D.9">D.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></h2>
    1342       <p id="rfc.section.D.9.p.1">Closed issues: </p>
    1343       <ul>
    1344          <li>Fixed discrepancy in the If-Range definition about allowed validators.</li>
    1345          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/150">http://tools.ietf.org/wg/httpbis/trac/ticket/150</a>&gt;: "multipart/byteranges for custom range units"
    1346          </li>
    1347          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/151">http://tools.ietf.org/wg/httpbis/trac/ticket/151</a>&gt;: "range unit missing from other-ranges-specifier in Range header"
    1348          </li>
    1349          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/198">http://tools.ietf.org/wg/httpbis/trac/ticket/198</a>&gt;: "move IANA registrations for optional status codes"
    1350          </li>
    1351       </ul>
    1352       <h2 id="rfc.section.D.10"><a href="#rfc.section.D.10">D.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></h2>
    1353       <p id="rfc.section.D.10.p.1">No significant changes.</p>
    1354       <h2 id="rfc.section.D.11"><a href="#rfc.section.D.11">D.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></h2>
    1355       <p id="rfc.section.D.11.p.1">No significant changes.</p>
    1356       <h2 id="rfc.section.D.12"><a href="#rfc.section.D.12">D.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></h2>
    1357       <p id="rfc.section.D.12.p.1">Closed issues: </p>
    1358       <ul>
    1359          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
    1360          </li>
    1361          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
    1362          </li>
    1363          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
    1364          </li>
    1365       </ul>
    1366       <p id="rfc.section.D.12.p.2">Ongoing work on Custom Ranges (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>&gt;):
    1367       </p>
    1368       <ul>
    1369          <li>Add IANA registry.</li>
    1370       </ul>
    1371       <h2 id="rfc.section.D.13"><a href="#rfc.section.D.13">D.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></h2>
    1372       <p id="rfc.section.D.13.p.1">Closed issues: </p>
    1373       <ul>
    1374          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/217">http://tools.ietf.org/wg/httpbis/trac/ticket/217</a>&gt;: "Caches can't be required to serve ranges"
    1375          </li>
    1376       </ul>
    1377       <h2 id="rfc.section.D.14"><a href="#rfc.section.D.14">D.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p5-range-12</a></h2>
    1378       <p id="rfc.section.D.14.p.1">Closed issues: </p>
    1379       <ul>
    1380          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
    1381          </li>
    1382       </ul>
    1383       <h2 id="rfc.section.D.15"><a href="#rfc.section.D.15">D.15</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p5-range-13</a></h2>
    1384       <p id="rfc.section.D.15.p.1">Closed issues: </p>
    1385       <ul>
    1386          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
    1387          </li>
    1388       </ul>
     1305</pre></div>
     1306      <div id="change.log">
     1307         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     1308         <div>
     1309            <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC 2616
     1310            </h2>
     1311            <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     1312            </p>
     1313         </div>
     1314         <div>
     1315            <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
     1316            </h2>
     1317            <p id="rfc.section.D.2.p.1">Closed issues: </p>
     1318            <ul>
     1319               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/18">http://tools.ietf.org/wg/httpbis/trac/ticket/18</a>&gt;: "Cache validators in 206 responses" (&lt;<a href="http://purl.org/NET/http-errata#ifrange206">http://purl.org/NET/http-errata#ifrange206</a>&gt;)
     1320               </li>
     1321               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     1322               </li>
     1323               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/86">http://tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
     1324               </li>
     1325            </ul>
     1326         </div>
     1327         <div>
     1328            <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
     1329            </h2>
     1330            <p id="rfc.section.D.3.p.1">Closed issues: </p>
     1331            <ul>
     1332               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/55">http://tools.ietf.org/wg/httpbis/trac/ticket/55</a>&gt;: "Updating to RFC4288"
     1333               </li>
     1334            </ul>
     1335            <p id="rfc.section.D.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     1336            </p>
     1337            <ul>
     1338               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
     1339            </ul>
     1340         </div>
     1341         <div id="changes.since.02">
     1342            <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></h2>
     1343            <p id="rfc.section.D.4.p.1">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     1344            </p>
     1345            <ul>
     1346               <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
     1347            </ul>
     1348         </div>
     1349         <div id="changes.since.03">
     1350            <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a>&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></h2>
     1351            <p id="rfc.section.D.5.p.1">None.</p>
     1352         </div>
     1353         <div id="changes.since.04">
     1354            <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a>&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></h2>
     1355            <p id="rfc.section.D.6.p.1">Closed issues: </p>
     1356            <ul>
     1357               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/133">http://tools.ietf.org/wg/httpbis/trac/ticket/133</a>&gt;: "multipart/byteranges minimum number of parts"
     1358               </li>
     1359            </ul>
     1360            <p id="rfc.section.D.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     1361            </p>
     1362            <ul>
     1363               <li>Use "/" instead of "|" for alternatives.</li>
     1364               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
     1365               <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
     1366            </ul>
     1367         </div>
     1368         <div id="changes.since.05">
     1369            <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a>&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></h2>
     1370            <p id="rfc.section.D.7.p.1">Closed issues: </p>
     1371            <ul>
     1372               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/142">http://tools.ietf.org/wg/httpbis/trac/ticket/142</a>&gt;: "State base for *-byte-pos and suffix-length"
     1373               </li>
     1374            </ul>
     1375            <p id="rfc.section.D.7.p.2">Ongoing work on Custom Ranges (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>&gt;):
     1376            </p>
     1377            <ul>
     1378               <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
     1379            </ul>
     1380            <p id="rfc.section.D.7.p.3">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     1381            </p>
     1382            <ul>
     1383               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
     1384            </ul>
     1385         </div>
     1386         <div id="changes.since.06">
     1387            <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a>&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></h2>
     1388            <p id="rfc.section.D.8.p.1">Closed issues: </p>
     1389            <ul>
     1390               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
     1391               </li>
     1392            </ul>
     1393         </div>
     1394         <div id="changes.since.07">
     1395            <h2 id="rfc.section.D.9"><a href="#rfc.section.D.9">D.9</a>&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></h2>
     1396            <p id="rfc.section.D.9.p.1">Closed issues: </p>
     1397            <ul>
     1398               <li>Fixed discrepancy in the If-Range definition about allowed validators.</li>
     1399               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/150">http://tools.ietf.org/wg/httpbis/trac/ticket/150</a>&gt;: "multipart/byteranges for custom range units"
     1400               </li>
     1401               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/151">http://tools.ietf.org/wg/httpbis/trac/ticket/151</a>&gt;: "range unit missing from other-ranges-specifier in Range header"
     1402               </li>
     1403               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/198">http://tools.ietf.org/wg/httpbis/trac/ticket/198</a>&gt;: "move IANA registrations for optional status codes"
     1404               </li>
     1405            </ul>
     1406         </div>
     1407         <div id="changes.since.08">
     1408            <h2 id="rfc.section.D.10"><a href="#rfc.section.D.10">D.10</a>&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></h2>
     1409            <p id="rfc.section.D.10.p.1">No significant changes.</p>
     1410         </div>
     1411         <div id="changes.since.09">
     1412            <h2 id="rfc.section.D.11"><a href="#rfc.section.D.11">D.11</a>&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></h2>
     1413            <p id="rfc.section.D.11.p.1">No significant changes.</p>
     1414         </div>
     1415         <div id="changes.since.10">
     1416            <h2 id="rfc.section.D.12"><a href="#rfc.section.D.12">D.12</a>&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></h2>
     1417            <p id="rfc.section.D.12.p.1">Closed issues: </p>
     1418            <ul>
     1419               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
     1420               </li>
     1421               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
     1422               </li>
     1423               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
     1424               </li>
     1425            </ul>
     1426            <p id="rfc.section.D.12.p.2">Ongoing work on Custom Ranges (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>&gt;):
     1427            </p>
     1428            <ul>
     1429               <li>Add IANA registry.</li>
     1430            </ul>
     1431         </div>
     1432         <div id="changes.since.11">
     1433            <h2 id="rfc.section.D.13"><a href="#rfc.section.D.13">D.13</a>&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></h2>
     1434            <p id="rfc.section.D.13.p.1">Closed issues: </p>
     1435            <ul>
     1436               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/217">http://tools.ietf.org/wg/httpbis/trac/ticket/217</a>&gt;: "Caches can't be required to serve ranges"
     1437               </li>
     1438            </ul>
     1439         </div>
     1440         <div id="changes.since.12">
     1441            <h2 id="rfc.section.D.14"><a href="#rfc.section.D.14">D.14</a>&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p5-range-12</a></h2>
     1442            <p id="rfc.section.D.14.p.1">Closed issues: </p>
     1443            <ul>
     1444               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
     1445               </li>
     1446            </ul>
     1447         </div>
     1448         <div id="changes.since.13">
     1449            <h2 id="rfc.section.D.15"><a href="#rfc.section.D.15">D.15</a>&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p5-range-13</a></h2>
     1450            <p id="rfc.section.D.15.p.1">Closed issues: </p>
     1451            <ul>
     1452               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
     1453               </li>
     1454            </ul>
     1455         </div>
     1456      </div>
    13891457      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    13901458      <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.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</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> <a href="#rfc.index.S">S</a>
     
    13931461         <ul class="ind">
    13941462            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    1395                   <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B.1</a></li>
     1463                  <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.2.1"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B.1</a></li>
    13961464               </ul>
    13971465            </li>
    13981466            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    1399                   <li>416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.4"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">5.2</a>, <a href="#rfc.xref.status.416.2">6.1</a></li>
     1467                  <li>416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">5.2</a>, <a href="#rfc.xref.status.416.2">6.1</a></li>
    14001468               </ul>
    14011469            </li>
     
    15071575         </ul>
    15081576      </div>
     1577      <div class="avoidbreak">
     1578         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     1579         <p><b>Roy T. Fielding</b>
     1580            (editor)
     1581            <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>
     1582         <p><b>Jim Gettys</b><br>Alcatel-Lucent Bell Labs<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>Email: <a href="mailto:jg@freedesktop.org">jg@freedesktop.org</a><br>URI: <a href="http://gettys.wordpress.com/">http://gettys.wordpress.com/</a></p>
     1583         <p><b>Jeffrey C. Mogul</b><br>Hewlett-Packard Company<br>HP Labs, Large Scale Systems Group<br>1501 Page Mill Road, MS 1177<br>Palo Alto, CA&nbsp;94304<br>USA<br>Email: <a href="mailto:JeffMogul@acm.org">JeffMogul@acm.org</a></p>
     1584         <p><b>Henrik Frystyk Nielsen</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>USA<br>Email: <a href="mailto:henrikn@microsoft.com">henrikn@microsoft.com</a></p>
     1585         <p><b>Larry Masinter</b><br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:LMM@acm.org">LMM@acm.org</a><br>URI: <a href="http://larry.masinter.net/">http://larry.masinter.net/</a></p>
     1586         <p><b>Paul J. Leach</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>Email: <a href="mailto:paulle@microsoft.com">paulle@microsoft.com</a></p>
     1587         <p><b>Tim Berners-Lee</b><br>World Wide Web Consortium<br>MIT Computer Science and Artificial Intelligence Laboratory<br>The Stata Center, Building 32<br>32 Vassar Street<br>Cambridge, MA&nbsp;02139<br>USA<br>Email: <a href="mailto:timbl@w3.org">timbl@w3.org</a><br>URI: <a href="http://www.w3.org/People/Berners-Lee/">http://www.w3.org/People/Berners-Lee/</a></p>
     1588         <p><b>Yves Lafon</b>
     1589            (editor)
     1590            <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>
     1591         <p><b>Julian F. Reschke</b>
     1592            (editor)
     1593            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Phone: <a href="tel:+492512807760">+49 251 2807760</a><br>Fax: <a href="fax:+492512807761">+49 251 2807761</a><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>
     1594      </div>
    15091595   </body>
    15101596</html>
Note: See TracChangeset for help on using the changeset viewer.