Ignore:
Timestamp:
Jun 14, 2014, 4:20:37 AM (5 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/11/p5-range.html

    r973 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;
     82}
     83ol.la {
     84  list-style-type: lower-alpha;
     85}
     86ol.ua {
     87  list-style-type: upper-alpha;
    8788}
    8889ol p {
     
    9192p {
    9293  margin-left: 2em;
    93   margin-right: 2em;
    9494}
    9595pre {
     
    9797  background-color: lightyellow;
    9898  padding: .25em;
     99  page-break-inside: avoid;
    99100}
    100101pre.text2 {
     
    125126table.tt {
    126127  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;
    127139}
    128140table.full {
    129   border-style: outset;
    130   border-width: 1px;
    131 }
    132 table.headers {
    133   border-style: outset;
    134   border-width: 1px;
     141  border-style: solid;
     142  border-width: 2px;
    135143}
    136144table.tt td {
    137145  vertical-align: top;
    138146}
     147table.all td {
     148  border-style: solid;
     149  border-width: 1px;
     150}
    139151table.full td {
    140   border-style: inset;
     152  border-style: none solid;
    141153  border-width: 1px;
    142154}
     
    144156  vertical-align: top;
    145157}
     158table.all th {
     159  border-style: solid;
     160  border-width: 1px;
     161}
    146162table.full th {
    147   border-style: inset;
    148   border-width: 1px;
     163  border-style: solid;
     164  border-width: 1px 1px 2px 1px;
    149165}
    150166table.headers th {
    151   border-style: none none inset none;
    152   border-width: 1px;
     167  border-style: none none solid none;
     168  border-width: 2px;
    153169}
    154170table.left {
     
    165181  caption-side: bottom;
    166182  font-weight: bold;
    167   font-size: 9pt;
     183  font-size: 10pt;
    168184  margin-top: .5em;
    169185}
     
    172188  border-spacing: 1px;
    173189  width: 95%;
    174   font-size: 10pt;
     190  font-size: 11pt;
    175191  color: white;
    176192}
     
    180196td.topnowrap {
    181197  vertical-align: top;
    182   white-space: nowrap; 
     198  white-space: nowrap;
    183199}
    184200table.header td {
     
    197213  display:table-header-group;
    198214}
    199 ul.toc {
     215ul.toc, ul.toc ul {
    200216  list-style: none;
    201217  margin-left: 1.5em;
    202   margin-right: 0em;
    203218  padding-left: 0em;
    204219}
    205 li.tocline0 {
     220ul.toc li {
    206221  line-height: 150%;
    207222  font-weight: bold;
     223  margin-left: 0em;
     224}
     225ul.toc li li {
     226  line-height: normal;
     227  font-weight: normal;
    208228  font-size: 10pt;
    209229  margin-left: 0em;
    210   margin-right: 0em;
    211 }
    212 li.tocline1 {
    213   line-height: normal;
    214   font-weight: normal;
    215   font-size: 9pt;
    216   margin-left: 0em;
    217   margin-right: 0em;
    218 }
    219 li.tocline2 {
     230}
     231li.excluded {
    220232  font-size: 0pt;
    221233}
     
    223235  margin-left: 0em;
    224236}
    225 ul.ind {
     237.title, .filename, h1, h2, h3, h4 {
     238  font-family: candara, helvetica, arial, sans-serif;
     239}
     240samp, tt, code, pre {
     241  font: consolas, monospace;
     242}
     243ul.ind, ul.ind ul {
    226244  list-style: none;
    227245  margin-left: 1.5em;
    228   margin-right: 0em;
    229246  padding-left: 0em;
    230247  page-break-before: avoid;
    231248}
    232 li.indline0 {
     249ul.ind li {
    233250  font-weight: bold;
    234251  line-height: 200%;
    235252  margin-left: 0em;
    236   margin-right: 0em;
    237 }
    238 li.indline1 {
     253}
     254ul.ind li li {
    239255  font-weight: normal;
    240256  line-height: 150%;
    241257  margin-left: 0em;
    242   margin-right: 0em;
    243258}
    244259.avoidbreak {
     
    264279  font-weight: bold;
    265280  text-align: center;
    266   font-size: 9pt;
     281  font-size: 10pt;
    267282}
    268283.filename {
    269284  color: #333333;
     285  font-size: 75%;
    270286  font-weight: bold;
    271   font-size: 12pt;
    272287  line-height: 21pt;
    273288  text-align: center;
     
    276291  font-weight: bold;
    277292}
    278 .hidden {
    279   display: none;
    280 }
    281293.left {
    282294  text-align: left;
     
    286298}
    287299.title {
    288   color: #990000;
    289   font-size: 18pt;
     300  color: green;
     301  font-size: 150%;
    290302  line-height: 18pt;
    291303  font-weight: bold;
     
    293305  margin-top: 36pt;
    294306}
    295 .vcardline {
    296   display: block;
    297 }
    298307.warning {
    299   font-size: 14pt;
     308  font-size: 130%;
    300309  background-color: yellow;
    301310}
     
    306315    display: none;
    307316  }
    308  
     317
    309318  a {
    310319    color: black;
     
    321330    background-color: white;
    322331    vertical-align: top;
    323     font-size: 12pt;
     332    font-size: 110%;
    324333  }
    325334
    326   ul.toc a::after {
     335  ul.toc a:nth-child(2)::after {
    327336    content: leader('.') target-counter(attr(href), page);
    328337  }
    329  
    330   a.iref {
     338
     339  ul.ind li li a {
    331340    content: target-counter(attr(href), page);
    332341  }
    333  
     342
    334343  .print2col {
    335344    column-count: 2;
     
    341350@page {
    342351  @top-left {
    343        content: "Internet-Draft"; 
    344   } 
     352       content: "Internet-Draft";
     353  }
    345354  @top-right {
    346        content: "August 2010"; 
    347   } 
     355       content: "August 2010";
     356  }
    348357  @top-center {
    349        content: "HTTP/1.1, Part 5"; 
    350   } 
     358       content: "HTTP/1.1, Part 5";
     359  }
    351360  @bottom-left {
    352        content: "Fielding, et al."; 
    353   } 
     361       content: "Fielding, et al.";
     362  }
    354363  @bottom-center {
    355        content: "Standards Track";
    356   } 
     364       content: "Expires February 5, 2011";
     365  }
    357366  @bottom-right {
    358        content: "[Page " counter(page) "]"; 
    359   } 
    360 }
    361 
    362 @page:first { 
     367       content: "[Page " counter(page) "]";
     368  }
     369}
     370
     371@page:first {
    363372    @top-left {
    364373      content: normal;
     
    388397      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
    389398      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    390       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.520, 2010-07-14 12:36:35, 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/">
    391400      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    392401      <meta name="dct.creator" content="Fielding, R.">
     
    417426            </tr>
    418427            <tr>
    419                <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)
    420429               </td>
    421430               <td class="right">J. Gettys</td>
     
    488497      </table>
    489498      <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-11</span></p>
    490       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
     499      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    491500      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    492501         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
    493502         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
    494503         5 defines range-specific requests and the rules for constructing and combining responses to those requests.
    495       </p> 
    496       <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>
    497506      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    498507         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;.
    499       </p> 
     508      </p>
    500509      <p>The changes in this draft are summarized in <a href="#changes.since.10" title="Since draft-ietf-httpbis-p5-range-10">Appendix&nbsp;D.12</a>.
    501       </p>
    502       <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    503       <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
    504       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
    505          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>.
    506510      </p>
    507       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    508          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    509          in progress”.
    510       </p>
    511       <p>This Internet-Draft will expire on February 5, 2011.</p>
    512       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    513       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    514       <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
    515          and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
    516          text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
    517          BSD License.
    518       </p>
    519       <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
    520          10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
    521          allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
    522          controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
    523          works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
    524          it into languages other than English.
    525       </p>
     511      <div id="rfc.status">
     512         <h1><a href="#rfc.status">Status of This Memo</a></h1>
     513         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     514         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
     515            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>.
     516         </p>
     517         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     518            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     519            in progress”.
     520         </p>
     521         <p>This Internet-Draft will expire on February 5, 2011.</p>
     522      </div>
     523      <div id="rfc.copyrightnotice">
     524         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     525         <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     526         <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
     527            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     528            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
     529            BSD License.
     530         </p>
     531         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     532            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     533            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     534            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     535            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     536            it into languages other than English.
     537         </p>
     538      </div>
    526539      <hr class="noprint">
    527540      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    528541      <ul class="toc">
    529          <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
    530                <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    531                <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul class="toc">
    532                      <li class="tocline1">1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    533                      <li class="tocline1">1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     542         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     543               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     544               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     545                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     546                     <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>
    534547                  </ul>
    535548               </li>
    536549            </ul>
    537550         </li>
    538          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a><ul class="toc">
    539                <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registry">Range Specifier Registry</a></li>
     551         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a><ul>
     552               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registry">Range Specifier Registry</a></li>
    540553            </ul>
    541554         </li>
    542          <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul class="toc">
    543                <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    544                <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
     555         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
     556               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
     557               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
    545558            </ul>
    546559         </li>
    547          <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
    548          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
    549                <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
    550                <li class="tocline1">5.2&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
    551                <li class="tocline1">5.3&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
    552                <li class="tocline1">5.4&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul class="toc">
    553                      <li class="tocline1">5.4.1&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
    554                      <li class="tocline1">5.4.2&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
     560         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
     561         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     562               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
     563               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
     564               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
     565               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
     566                     <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
     567                     <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>
    555568                  </ul>
    556569               </li>
    557570            </ul>
    558571         </li>
    559          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
    560                <li class="tocline1">6.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
    561                <li class="tocline1">6.2&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    562                <li class="tocline1">6.3&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registration">Range Specifier Registration</a></li>
     572         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     573               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
     574               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
     575               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registration">Range Specifier Registration</a></li>
    563576            </ul>
    564577         </li>
    565          <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
    566          <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    567          <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
    568                <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    569                <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     578         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
     579         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     580         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     581               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     582               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    570583            </ul>
    571584         </li>
    572          <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
    573          <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
    574          <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">
    575                <li class="tocline1">B.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     585         <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>
     586         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
     587               <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>
    576588            </ul>
    577589         </li>
    578          <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    579          <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
    580                <li class="tocline1">D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC2616</a></li>
    581                <li class="tocline1">D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p5-range-00</a></li>
    582                <li class="tocline1">D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p5-range-01</a></li>
    583                <li class="tocline1">D.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></li>
    584                <li class="tocline1">D.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></li>
    585                <li class="tocline1">D.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></li>
    586                <li class="tocline1">D.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></li>
    587                <li class="tocline1">D.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></li>
    588                <li class="tocline1">D.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></li>
    589                <li class="tocline1">D.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></li>
    590                <li class="tocline1">D.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></li>
    591                <li class="tocline1">D.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></li>
     590         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     591         <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>
     592               <li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC2616</a></li>
     593               <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>
     594               <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>
     595               <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>
     596               <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>
     597               <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>
     598               <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>
     599               <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>
     600               <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>
     601               <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>
     602               <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>
     603               <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>
    592604            </ul>
    593605         </li>
    594          <li class="tocline0"><a href="#rfc.index">Index</a></li>
     606         <li><a href="#rfc.index">Index</a></li>
     607         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    595608      </ul>
    596       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    597       <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
    598          has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
    599          rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
    600          request only a subset of a larger representation, such as a single page of a very large document or only part of an image
    601          to be rendered by a device with limited local storage.
    602       </p>
    603       <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
    604          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
    605          request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
    606          full responses by intermediate caches that might not implement the feature.
    607       </p>
    608       <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
    609          requests for byte ranges.
    610       </p>
    611       <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>
    612       <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"
    613          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>.
    614       </p>
    615       <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
    616          protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
    617          for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
    618          all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    619       </p>
    620       <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>
    621       <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.
    622       </p>
    623       <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
    624          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
    625          and WSP (whitespace).
    626       </p>
    627       <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>
    628       <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>:
    629       </p>
    630       <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;
     609      <div id="introduction">
     610         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     611         <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
     612            has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
     613            rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
     614            request only a subset of a larger representation, such as a single page of a very large document or only part of an image
     615            to be rendered by a device with limited local storage.
     616         </p>
     617         <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
     618            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
     619            request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
     620            full responses by intermediate caches that might not implement the feature.
     621         </p>
     622         <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
     623            requests for byte ranges.
     624         </p>
     625         <div id="intro.requirements">
     626            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     627            <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"
     628               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>.
     629            </p>
     630            <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
     631               protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     632               for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     633               all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
     634            </p>
     635         </div>
     636         <div id="notation">
     637            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     638            <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.
     639            </p>
     640            <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
     641               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
     642               and WSP (whitespace).
     643            </p>
     644            <div id="core.rules">
     645               <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>
     646               <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>:
     647               </p>
     648               <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;
    631649  <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;
    632 </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>
    633       <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
    634       <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;
     650</pre></div>
     651            <div id="abnf.dependencies">
     652               <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>
     653               <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
     654               <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;
    635655</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#entity.tags" title="Entity-Tags">Section 2</a>&gt;
    636 </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>
    637       <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
    638          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.
    639       </p>
    640       <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>
     656</pre></div>
     657         </div>
     658      </div>
     659      <div id="range.units">
     660         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#range.units">Range Units</a></h1>
     661         <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
     662            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.
     663         </p>
     664         <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>
    641665  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
    642666  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a>
    643667</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
    644          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>.
    645       </p>
    646       <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 (<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.
    647       </p>
    648       <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>
    649       <p id="rfc.section.2.1.p.1">The HTTP Ranger Specifier Registry defines the name space for the range specifier names.</p>
    650       <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    651       </p>
    652       <ul>
    653          <li>Name</li>
    654          <li>Description</li>
    655          <li>Pointer to specification text</li>
    656       </ul>
    657       <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>).
    658       </p>
    659       <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;.
    660       </p>
    661       <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>
    662       <div id="rfc.iref.3"></div>
    663       <div id="rfc.iref.s.1"></div>
    664       <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>
    665       <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.
    666       </p>
    667       <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
    668       </p>
    669       <ul>
    670          <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
    671             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.
    672          </li>
    673          <li>Date</li>
    674          <li>Cache-Control, ETag, Expires, Content-Location, Last-Modified, and/or Vary, if the header field would have been sent in a
    675             200 response to the same request
    676          </li>
    677       </ul>
    678       <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.
    679       </p>
    680       <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 headers do not match exactly, see <a href="#combining.byte.ranges" title="Combining Ranges">Section&nbsp;4</a>.
    681       </p>
    682       <p id="rfc.section.3.1.p.5">A cache that does not support the Range and Content-Range headers <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
    683          it <em class="bcp14">MUST NOT</em> be cached either.
    684       </p>
    685       <div id="rfc.iref.4"></div>
    686       <div id="rfc.iref.s.2"></div>
    687       <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>
    688       <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 request-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
    689          did not include an If-Range request-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
    690          length of the selected resource.)
    691       </p>
    692       <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.
    693       </p>
    694       <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>
    695       <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,
    696          or because a connection closed prematurely. After several such transfers, a cache might have received several ranges of the
    697          same representation.
    698       </p>
    699       <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,
    700          the cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
    701       </p>
    702       <ul>
    703          <li>Both the incoming response and the cache entry have a cache validator.</li>
    704          <li>The two cache validators match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak and Strong Validators">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    705          </li>
    706       </ul>
    707       <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
    708          response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
    709       </p>
    710       <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>
    711       <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>
    712       <div id="rfc.iref.a.1"></div>
    713       <div id="rfc.iref.h.1"></div>
    714       <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>
    715       <p id="rfc.section.5.1.p.1">The "Accept-Ranges" response-header field allows a resource to indicate its acceptance of range requests.</p>
    716       <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = "Accept-Ranges" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>
     668            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>.
     669         </p>
     670         <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 (<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.
     671         </p>
     672         <div id="range.specifier.registry">
     673            <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>
     674            <p id="rfc.section.2.1.p.1">The HTTP Ranger Specifier Registry defines the name space for the range specifier names.</p>
     675            <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     676            </p>
     677            <ul>
     678               <li>Name</li>
     679               <li>Description</li>
     680               <li>Pointer to specification text</li>
     681            </ul>
     682            <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>).
     683            </p>
     684            <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;.
     685            </p>
     686         </div>
     687      </div>
     688      <div id="status.code.definitions">
     689         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#status.code.definitions">Status Code Definitions</a></h1>
     690         <div id="status.206">
     691            <div id="rfc.iref.2.1"></div>
     692            <div id="rfc.iref.s.1"></div>
     693            <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>
     694            <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.
     695            </p>
     696            <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
     697            </p>
     698            <ul>
     699               <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
     700                  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.
     701               </li>
     702               <li>Date</li>
     703               <li>Cache-Control, ETag, Expires, Content-Location, Last-Modified, and/or Vary, if the header field would have been sent in a
     704                  200 response to the same request
     705               </li>
     706            </ul>
     707            <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.
     708            </p>
     709            <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 headers do not match exactly, see <a href="#combining.byte.ranges" title="Combining Ranges">Section&nbsp;4</a>.
     710            </p>
     711            <p id="rfc.section.3.1.p.5">A cache that does not support the Range and Content-Range headers <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
     712               it <em class="bcp14">MUST NOT</em> be cached either.
     713            </p>
     714         </div>
     715         <div id="status.416">
     716            <div id="rfc.iref.4.1"></div>
     717            <div id="rfc.iref.s.2"></div>
     718            <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>
     719            <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 request-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
     720               did not include an If-Range request-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
     721               length of the selected resource.)
     722            </p>
     723            <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.
     724            </p>
     725         </div>
     726      </div>
     727      <div id="combining.byte.ranges">
     728         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></h1>
     729         <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,
     730            or because a connection closed prematurely. After several such transfers, a cache might have received several ranges of the
     731            same representation.
     732         </p>
     733         <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,
     734            the cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
     735         </p>
     736         <ul>
     737            <li>Both the incoming response and the cache entry have a cache validator.</li>
     738            <li>The two cache validators match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak and Strong Validators">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
     739            </li>
     740         </ul>
     741         <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
     742            response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
     743         </p>
     744      </div>
     745      <div id="header.fields">
     746         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     747         <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>
     748         <div id="header.accept-ranges">
     749            <div id="rfc.iref.a.1"></div>
     750            <div id="rfc.iref.h.1"></div>
     751            <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>
     752            <p id="rfc.section.5.1.p.1">The "Accept-Ranges" response-header field allows a resource to indicate its acceptance of range requests.</p>
     753            <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = "Accept-Ranges" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>
    717754  <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>   = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
    718755  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
    719756</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
    720       </p>
    721       <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: bytes
     757            </p>
     758            <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: bytes
    722759</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 for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
    723       </p>
    724       <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
    725       </p>
    726       <div id="rfc.figure.u.7"></div><pre class="text">  Accept-Ranges: none
     760            </p>
     761            <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
     762            </p>
     763            <div id="rfc.figure.u.7"></div><pre class="text">  Accept-Ranges: none
    727764</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
    728       <div id="rfc.iref.c.1"></div>
    729       <div id="rfc.iref.h.2"></div>
    730       <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>
    731       <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
    732          body is intended to be applied.
    733       </p>
    734       <p id="rfc.section.5.2.p.2">Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
    735       </p>
    736       <div id="rfc.figure.u.8"></div><pre class="inline"><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><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-range" class="smpl">Content-Range-v</a>
     765         </div>
     766         <div id="header.content-range">
     767            <div id="rfc.iref.c.1"></div>
     768            <div id="rfc.iref.h.2"></div>
     769            <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>
     770            <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
     771               body is intended to be applied.
     772            </p>
     773            <p id="rfc.section.5.2.p.2">Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
     774            </p>
     775            <div id="rfc.figure.u.8"></div><pre class="inline"><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><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-range" class="smpl">Content-Range-v</a>
    737776  <a href="#header.content-range" class="smpl">Content-Range-v</a> = <a href="#header.content-range" class="smpl">content-range-spec</a>
    738777 
     
    752791  <a href="#header.content-range" class="smpl">other-range-resp-spec</a>    = *<a href="#notation" class="smpl">CHAR</a>
    753792</pre><p id="rfc.section.5.2.p.4">The header <em class="bcp14">SHOULD</em> indicate the total length of the full representation, unless this length is unknown or difficult to determine. The asterisk
    754          "*" character means that the instance-length is unknown at the time when the response was generated.
    755       </p>
    756       <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.
    757       </p>
    758       <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
    759          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.
    760       </p>
    761       <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
    762          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 "*".
    763       </p>
    764       <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>
    765       <ul>
    766          <li>The first 500 bytes:
    767             <div id="rfc.figure.u.9"></div><pre class="text">  bytes 0-499/1234
     793               "*" character means that the instance-length is unknown at the time when the response was generated.
     794            </p>
     795            <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.
     796            </p>
     797            <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
     798               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.
     799            </p>
     800            <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
     801               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 "*".
     802            </p>
     803            <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>
     804            <ul>
     805               <li>The first 500 bytes: <span id="rfc.figure.u.9"></span><pre class="text">  bytes 0-499/1234
    768806</pre> </li>
    769          <li>The second 500 bytes:
    770             <div id="rfc.figure.u.10"></div><pre class="text">  bytes 500-999/1234
     807               <li>The second 500 bytes: <span id="rfc.figure.u.10"></span><pre class="text">  bytes 500-999/1234
    771808</pre> </li>
    772          <li>All except for the first 500 bytes:
    773             <div id="rfc.figure.u.11"></div><pre class="text">  bytes 500-1233/1234
     809               <li>All except for the first 500 bytes: <span id="rfc.figure.u.11"></span><pre class="text">  bytes 500-1233/1234
    774810</pre> </li>
    775          <li>The last 500 bytes:
    776             <div id="rfc.figure.u.12"></div><pre class="text">  bytes 734-1233/1234
     811               <li>The last 500 bytes: <span id="rfc.figure.u.12"></span><pre class="text">  bytes 734-1233/1234
    777812</pre> </li>
    778       </ul>
    779       <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
    780          a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
    781          a Content-Length header showing the number of bytes actually transferred. For example,
    782       </p>
    783       <div id="rfc.figure.u.13"></div><pre class="text">  HTTP/1.1 206 Partial Content
     813            </ul>
     814            <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
     815               a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
     816               a Content-Length header showing the number of bytes actually transferred. For example,
     817            </p>
     818            <div id="rfc.figure.u.13"></div><pre class="text">  HTTP/1.1 206 Partial Content
    784819  Date: Wed, 15 Nov 1995 06:25:24 GMT
    785820  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    788823  Content-Type: image/gif
    789824</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
    790          ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
    791          as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
    792       </p>
    793       <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.
    794       </p>
    795       <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.
    796       </p>
    797       <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
    798          the full representation).
    799       </p>
    800       <p id="rfc.section.5.2.p.15">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header
    801          field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
    802          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>).
    803       </p>
    804       <div class="note" id="rfc.section.5.2.p.16">
    805          <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
    806             an unsatisfiable Range request-header, since not all servers implement this request-header.
    807          </p>
    808       </div>
    809       <div id="rfc.iref.i.1"></div>
    810       <div id="rfc.iref.h.3"></div>
    811       <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>
    812       <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
    813          in its cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and
    814          If-Match.) However, if the condition fails because the representation has been modified, the client would then have to make
    815          a second request to obtain the entire current representation.
    816       </p>
    817       <p id="rfc.section.5.3.p.2">The "If-Range" request-header field allows a client to "short-circuit" the second request. Informally, its meaning is "if
    818          the representation is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation".
    819       </p>
    820       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.if-range" class="smpl">If-Range</a>   = "If-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a>
     825               ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
     826               as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
     827            </p>
     828            <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.
     829            </p>
     830            <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.
     831            </p>
     832            <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
     833               the full representation).
     834            </p>
     835            <p id="rfc.section.5.2.p.15">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header
     836               field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
     837               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>).
     838            </p>
     839            <div class="note" id="rfc.section.5.2.p.16">
     840               <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
     841                  an unsatisfiable Range request-header, since not all servers implement this request-header.
     842               </p>
     843            </div>
     844         </div>
     845         <div id="header.if-range">
     846            <div id="rfc.iref.i.1"></div>
     847            <div id="rfc.iref.h.3"></div>
     848            <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>
     849            <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
     850               in its cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and
     851               If-Match.) However, if the condition fails because the representation has been modified, the client would then have to make
     852               a second request to obtain the entire current representation.
     853            </p>
     854            <p id="rfc.section.5.3.p.2">The "If-Range" request-header field allows a client to "short-circuit" the second request. Informally, its meaning is "if
     855               the representation is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation".
     856            </p>
     857            <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.if-range" class="smpl">If-Range</a>   = "If-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a>
    821858  <a href="#header.if-range" class="smpl">If-Range-v</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
    822859</pre><p id="rfc.section.5.3.p.4">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. (The server can distinguish between a valid HTTP-date and any form of entity-tag by examining
    823          no more than two characters.) The If-Range header <em class="bcp14">SHOULD</em> only be used together with a Range header, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header, or if the server does not support the sub-range operation.
    824       </p>
    825       <p id="rfc.section.5.3.p.5">If the entity-tag given in the If-Range header matches the current cache validator for the representation, then the 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
    826          not match, then the server <em class="bcp14">SHOULD</em> return the entire representation using a 200 (OK) response.
    827       </p>
    828       <div id="rfc.iref.r.1"></div>
    829       <div id="rfc.iref.h.4"></div>
    830       <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>
    831       <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>
    832       <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
    833          representation. (However, not all clients and servers need to support byte-range operations.)
    834       </p>
    835       <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
    836          message-body).
    837       </p>
    838       <div id="rule.ranges-specifier">
    839          <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.
    840          </p>
    841       </div>
    842       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></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>
     860               no more than two characters.) The If-Range header <em class="bcp14">SHOULD</em> only be used together with a Range header, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header, or if the server does not support the sub-range operation.
     861            </p>
     862            <p id="rfc.section.5.3.p.5">If the entity-tag given in the If-Range header matches the current cache validator for the representation, then the 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
     863               not match, then the server <em class="bcp14">SHOULD</em> return the entire representation using a 200 (OK) response.
     864            </p>
     865         </div>
     866         <div id="header.range">
     867            <div id="rfc.iref.r.1"></div>
     868            <div id="rfc.iref.h.4"></div>
     869            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.range">Range</a></h2>
     870            <div id="byte.ranges">
     871               <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>
     872               <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
     873                  representation. (However, not all clients and servers need to support byte-range operations.)
     874               </p>
     875               <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
     876                  message-body).
     877               </p>
     878               <div id="rule.ranges-specifier">
     879                  <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.
     880                  </p>
     881               </div>
     882               <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></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>
    843883  <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> )
    844884  <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> ]
     
    846886  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
    847887</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
    848          gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
    849          at zero.
    850       </p>
    851       <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
    852          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.
    853       </p>
    854       <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
    855          body, last-byte-pos is taken to be equal to one less than the current length of the representation in bytes.
    856       </p>
    857       <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>
    858       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
     888                  gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
     889                  at zero.
     890               </p>
     891               <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
     892                  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.
     893               </p>
     894               <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
     895                  body, last-byte-pos is taken to be equal to one less than the current length of the representation in bytes.
     896               </p>
     897               <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>
     898               <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
    859899  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    860900</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
    861          value. (That is, this form specifies the last N bytes of a representation.) If the representation is shorter than the specified
    862          suffix-length, the entire representation is used.
    863       </p>
    864       <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
    865          length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set
    866          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.
    867       </p>
    868       <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p>
    869       <ul>
    870          <li>The first 500 bytes (byte offsets 0-499, inclusive):
    871             <div id="rfc.figure.u.17"></div><pre class="text">  bytes=0-499
     901                  value. (That is, this form specifies the last N bytes of a representation.) If the representation is shorter than the specified
     902                  suffix-length, the entire representation is used.
     903               </p>
     904               <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
     905                  length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set
     906                  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.
     907               </p>
     908               <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p>
     909               <ul>
     910                  <li>The first 500 bytes (byte offsets 0-499, inclusive): <span id="rfc.figure.u.17"></span><pre class="text">  bytes=0-499
    872911</pre> </li>
    873          <li>The second 500 bytes (byte offsets 500-999, inclusive):
    874             <div id="rfc.figure.u.18"></div><pre class="text">  bytes=500-999
     912                  <li>The second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.18"></span><pre class="text">  bytes=500-999
    875913</pre> </li>
    876          <li>The final 500 bytes (byte offsets 9500-9999, inclusive):
    877             <div id="rfc.figure.u.19"></div><pre class="text">  bytes=-500
    878 </pre> Or: <div id="rfc.figure.u.20"></div><pre class="text">  bytes=9500-
     914                  <li>The final 500 bytes (byte offsets 9500-9999, inclusive): <span id="rfc.figure.u.19"></span><pre class="text">  bytes=-500
     915</pre> Or: <span id="rfc.figure.u.20"></span><pre class="text">  bytes=9500-
    879916</pre> </li>
    880          <li>The first and last bytes only (bytes 0 and 9999):
    881             <div id="rfc.figure.u.21"></div><pre class="text">  bytes=0-0,-1
     917                  <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
    882918</pre> </li>
    883          <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive):
    884             <div id="rfc.figure.u.22"></div><pre class="text">  bytes=500-600,601-999
     919                  <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
    885920  bytes=500-700,601-999
    886921</pre> </li>
    887       </ul>
    888       <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>
    889       <p id="rfc.section.5.4.2.p.1">The "Range" request-header field defines the GET method (conditional or not) to request one or more sub-ranges of the response
    890          representation body, instead of the entire representation body.
    891       </p>
    892       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a>   = "Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
     922               </ul>
     923            </div>
     924            <div id="range.retrieval.requests">
     925               <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>
     926               <p id="rfc.section.5.4.2.p.1">The "Range" request-header field defines the GET method (conditional or not) to request one or more sub-ranges of the response
     927                  representation body, instead of the entire representation body.
     928               </p>
     929               <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a>   = "Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
    893930  <a href="#range.retrieval.requests" class="smpl">Range-v</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a>
    894931          / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
     
    896933  <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#notation" class="smpl">CHAR</a>
    897934</pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when possible,
    898          since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
    899          representations.
    900       </p>
    901       <p id="rfc.section.5.4.2.p.4">If the server supports the Range header and the specified range or ranges are appropriate for the representation: </p>
    902       <ul>
    903          <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
    904             words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
    905          </li>
    906          <li>The presence of a Range header in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match, or
    907             one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
    908             is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
    909          </li>
    910       </ul>
    911       <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (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.
    912       </p>
    913       <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
    914          representation in reply, it <em class="bcp14">SHOULD</em> only return the requested range to its client. It <em class="bcp14">SHOULD</em> store the entire received response in its cache if that is consistent with its cache allocation policies.
    915       </p>
    916       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    917       <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>
    918       <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:
    919       </p>
    920       <div id="rfc.table.1">
    921          <div id="iana.status.code.registration.table"></div>
    922          <table class="tt full left" cellpadding="3" cellspacing="0">
    923             <thead>
    924                <tr>
    925                   <th>Value</th>
    926                   <th>Description</th>
    927                   <th>Reference</th>
    928                </tr>
    929             </thead>
    930             <tbody>
    931                <tr>
    932                   <td class="left">206</td>
    933                   <td class="left">Partial Content</td>
    934                   <td class="left"> <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;3.1</a>
    935                   </td>
    936                </tr>
    937                <tr>
    938                   <td class="left">416</td>
    939                   <td class="left">Requested Range Not Satisfiable</td>
    940                   <td class="left"> <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>
    941                   </td>
    942                </tr>
    943             </tbody>
    944          </table>
     935                  since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
     936                  representations.
     937               </p>
     938               <p id="rfc.section.5.4.2.p.4">If the server supports the Range header and the specified range or ranges are appropriate for the representation: </p>
     939               <ul>
     940                  <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
     941                     words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
     942                  </li>
     943                  <li>The presence of a Range header in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match, or
     944                     one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
     945                     is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
     946                  </li>
     947               </ul>
     948               <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (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.
     949               </p>
     950               <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
     951                  representation in reply, it <em class="bcp14">SHOULD</em> only return the requested range to its client. It <em class="bcp14">SHOULD</em> store the entire received response in its cache if that is consistent with its cache allocation policies.
     952               </p>
     953            </div>
     954         </div>
    945955      </div>
    946       <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>
    947       <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>):
    948       </p>
    949       <div id="rfc.table.2">
    950          <div id="iana.header.registration.table"></div>
    951          <table class="tt full left" cellpadding="3" cellspacing="0">
    952             <thead>
    953                <tr>
    954                   <th>Header Field Name</th>
    955                   <th>Protocol</th>
    956                   <th>Status</th>
    957                   <th>Reference</th>
    958                </tr>
    959             </thead>
    960             <tbody>
    961                <tr>
    962                   <td class="left">Accept-Ranges</td>
    963                   <td class="left">http</td>
    964                   <td class="left">standard</td>
    965                   <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
    966                   </td>
    967                </tr>
    968                <tr>
    969                   <td class="left">Content-Range</td>
    970                   <td class="left">http</td>
    971                   <td class="left">standard</td>
    972                   <td class="left"> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
    973                   </td>
    974                </tr>
    975                <tr>
    976                   <td class="left">If-Range</td>
    977                   <td class="left">http</td>
    978                   <td class="left">standard</td>
    979                   <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">Section&nbsp;5.3</a>
    980                   </td>
    981                </tr>
    982                <tr>
    983                   <td class="left">Range</td>
    984                   <td class="left">http</td>
    985                   <td class="left">standard</td>
    986                   <td class="left"> <a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a>
    987                   </td>
    988                </tr>
    989             </tbody>
    990          </table>
     956      <div id="IANA.considerations">
     957         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     958         <div id="status.code.registration">
     959            <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>
     960            <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:
     961            </p>
     962            <div id="rfc.table.1">
     963               <div id="iana.status.code.registration.table"></div>
     964               <table class="tt full left" cellpadding="3" cellspacing="0">
     965                  <thead>
     966                     <tr>
     967                        <th>Value</th>
     968                        <th>Description</th>
     969                        <th>Reference</th>
     970                     </tr>
     971                  </thead>
     972                  <tbody>
     973                     <tr>
     974                        <td class="left">206</td>
     975                        <td class="left">Partial Content</td>
     976                        <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;3.1</a>
     977                        </td>
     978                     </tr>
     979                     <tr>
     980                        <td class="left">416</td>
     981                        <td class="left">Requested Range Not Satisfiable</td>
     982                        <td class="left"><a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>
     983                        </td>
     984                     </tr>
     985                  </tbody>
     986               </table>
     987            </div>
     988         </div>
     989         <div id="header.field.registration">
     990            <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>
     991            <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>):
     992            </p>
     993            <div id="rfc.table.2">
     994               <div id="iana.header.registration.table"></div>
     995               <table class="tt full left" cellpadding="3" cellspacing="0">
     996                  <thead>
     997                     <tr>
     998                        <th>Header Field Name</th>
     999                        <th>Protocol</th>
     1000                        <th>Status</th>
     1001                        <th>Reference</th>
     1002                     </tr>
     1003                  </thead>
     1004                  <tbody>
     1005                     <tr>
     1006                        <td class="left">Accept-Ranges</td>
     1007                        <td class="left">http</td>
     1008                        <td class="left">standard</td>
     1009                        <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
     1010                        </td>
     1011                     </tr>
     1012                     <tr>
     1013                        <td class="left">Content-Range</td>
     1014                        <td class="left">http</td>
     1015                        <td class="left">standard</td>
     1016                        <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
     1017                        </td>
     1018                     </tr>
     1019                     <tr>
     1020                        <td class="left">If-Range</td>
     1021                        <td class="left">http</td>
     1022                        <td class="left">standard</td>
     1023                        <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">Section&nbsp;5.3</a>
     1024                        </td>
     1025                     </tr>
     1026                     <tr>
     1027                        <td class="left">Range</td>
     1028                        <td class="left">http</td>
     1029                        <td class="left">standard</td>
     1030                        <td class="left"><a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a>
     1031                        </td>
     1032                     </tr>
     1033                  </tbody>
     1034               </table>
     1035            </div>
     1036            <p id="rfc.section.6.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1037         </div>
     1038         <div id="range.specifier.registration">
     1039            <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>
     1040            <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.
     1041            </p>
     1042            <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:
     1043            </p>
     1044            <div id="rfc.table.3">
     1045               <div id="iana.range.specifiers.table"></div>
     1046               <table class="tt full left" cellpadding="3" cellspacing="0">
     1047                  <thead>
     1048                     <tr>
     1049                        <th>Range Specifier Name</th>
     1050                        <th>Description</th>
     1051                        <th>Reference</th>
     1052                     </tr>
     1053                  </thead>
     1054                  <tbody>
     1055                     <tr>
     1056                        <td class="left">bytes</td>
     1057                        <td class="left">a range of octets</td>
     1058                        <td class="left">(this specification)</td>
     1059                     </tr>
     1060                  </tbody>
     1061               </table>
     1062            </div>
     1063            <p id="rfc.section.6.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1064         </div>
    9911065      </div>
    992       <p id="rfc.section.6.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    993       <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>
    994       <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.
    995       </p>
    996       <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:
    997       </p>
    998       <div id="rfc.table.3">
    999          <div id="iana.range.specifiers.table"></div>
    1000          <table class="tt full left" cellpadding="3" cellspacing="0">
    1001             <thead>
    1002                <tr>
    1003                   <th>Range Specifier Name</th>
    1004                   <th>Description</th>
    1005                   <th>Reference</th>
    1006                </tr>
    1007             </thead>
    1008             <tbody>
    1009                <tr>
    1010                   <td class="left">bytes</td>
    1011                   <td class="left">a range of octets</td>
    1012                   <td class="left">(this specification)</td>
    1013                </tr>
    1014             </tbody>
    1015          </table>
     1066      <div id="security.considerations">
     1067         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     1068         <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>.
     1069         </p>
    10161070      </div>
    1017       <p id="rfc.section.6.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    1018       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    1019       <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>.
    1020       </p>
    1021       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    1022       <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
    1023          from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
    1024          Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
    1025       </p>
     1071      <div id="ack">
     1072         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     1073         <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
     1074            from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
     1075            Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
     1076         </p>
     1077      </div>
    10261078      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
    10271079      </h1>
    10281080      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
    10291081      </h2>
    1030       <table>         
     1082      <table>
    10311083         <tr>
    10321084            <td class="reference"><b id="Part1">[Part1]</b></td>
    1033             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">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-11">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-11 (work in progress), August&nbsp;2010.
     1085            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">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-11">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-11 (work in progress), August&nbsp;2010.
    10341086            </td>
    10351087         </tr>
    10361088         <tr>
    10371089            <td class="reference"><b id="Part4">[Part4]</b></td>
    1038             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">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-11">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-11 (work in progress), August&nbsp;2010.
     1090            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">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-11">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-11 (work in progress), August&nbsp;2010.
    10391091            </td>
    10401092         </tr>
    10411093         <tr>
    10421094            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    1043             <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.
     1095            <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.
    10441096            </td>
    10451097         </tr>
    10461098         <tr>
    10471099            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    1048             <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.
     1100            <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.
    10491101            </td>
    10501102         </tr>
    10511103         <tr>
    10521104            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    1053             <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.
     1105            <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.
    10541106            </td>
    10551107         </tr>
     
    10571109      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
    10581110      </h2>
    1059       <table>       
     1111      <table>
    10601112         <tr>
    10611113            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    1062             <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.
     1114            <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.
    10631115            </td>
    10641116         </tr>
    10651117         <tr>
    10661118            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    1067             <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.
     1119            <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.
    10681120            </td>
    10691121         </tr>
    10701122         <tr>
    10711123            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
    1072             <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.
     1124            <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.
    10731125            </td>
    10741126         </tr>
    10751127         <tr>
    10761128            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
    1077             <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.
     1129            <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.
    10781130            </td>
    10791131         </tr>
    10801132      </table>
    1081       <div class="avoidbreak">
    1082          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    1083          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    1084                (editor)
    1085                <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></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>
    1086          <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>
    1087          <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>
    1088          <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>
    1089          <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>
    1090          <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>
    1091          <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>
    1092          <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
    1093                (editor)
    1094                <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>
    1095          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
    1096                (editor)
    1097                <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>
    1098       </div>
    1099       <div id="rfc.iref.m.1"></div>
    1100       <div id="rfc.iref.m.2"></div>
    1101       <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>
    1102       <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
    1103          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>.
    1104       </p>
    1105       <div class="note" id="rfc.section.A.p.2">
    1106          <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
    1107          </p>
    1108       </div>
    1109       <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
    1110          required boundary parameter specifies the boundary string used to separate each body-part.
    1111       </p>
    1112       <p id="rfc.section.A.p.4"> </p>
    1113       <dl>
    1114          <dt>Type name:</dt>
    1115          <dd>multipart</dd>
    1116          <dt>Subtype name:</dt>
    1117          <dd>byteranges</dd>
    1118          <dt>Required parameters:</dt>
    1119          <dd>boundary</dd>
    1120          <dt>Optional parameters:</dt>
    1121          <dd>none</dd>
    1122          <dt>Encoding considerations:</dt>
    1123          <dd>only "7bit", "8bit", or "binary" are permitted</dd>
    1124          <dt>Security considerations:</dt>
    1125          <dd>none</dd>
    1126          <dt>Interoperability considerations:</dt>
    1127          <dd>none</dd>
    1128          <dt>Published specification:</dt>
    1129          <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
    1130          </dd>
    1131          <dt>Applications that use this media type:</dt>
    1132          <dt>Additional information:</dt>
    1133          <dd>
    1134             <dl>
    1135                <dt>Magic number(s):</dt>
    1136                <dd>none</dd>
    1137                <dt>File extension(s):</dt>
    1138                <dd>none</dd>
    1139                <dt>Macintosh file type code(s):</dt>
    1140                <dd>none</dd>
    1141             </dl>
    1142          </dd>
    1143          <dt>Person and email address to contact for further information:</dt>
    1144          <dd>See Authors Section.</dd>
    1145          <dt>Intended usage:</dt>
    1146          <dd>COMMON</dd>
    1147          <dt>Restrictions on usage:</dt>
    1148          <dd>none</dd>
    1149          <dt>Author/Change controller:</dt>
    1150          <dd>IESG</dd>
    1151       </dl>
    1152       <div id="rfc.figure.u.24"></div>
    1153       <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
     1133      <div id="internet.media.type.multipart.byteranges">
     1134         <div id="rfc.iref.m.1"></div>
     1135         <div id="rfc.iref.m.2"></div>
     1136         <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>
     1137         <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
     1138            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>.
     1139         </p>
     1140         <div class="note" id="rfc.section.A.p.2">
     1141            <p><b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
     1142            </p>
     1143         </div>
     1144         <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
     1145            required boundary parameter specifies the boundary string used to separate each body-part.
     1146         </p>
     1147         <p id="rfc.section.A.p.4"></p>
     1148         <dl>
     1149            <dt>Type name:</dt>
     1150            <dd>multipart</dd>
     1151            <dt>Subtype name:</dt>
     1152            <dd>byteranges</dd>
     1153            <dt>Required parameters:</dt>
     1154            <dd>boundary</dd>
     1155            <dt>Optional parameters:</dt>
     1156            <dd>none</dd>
     1157            <dt>Encoding considerations:</dt>
     1158            <dd>only "7bit", "8bit", or "binary" are permitted</dd>
     1159            <dt>Security considerations:</dt>
     1160            <dd>none</dd>
     1161            <dt>Interoperability considerations:</dt>
     1162            <dd>none</dd>
     1163            <dt>Published specification:</dt>
     1164            <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
     1165            </dd>
     1166            <dt>Applications that use this media type:</dt>
     1167            <dt>Additional information:</dt>
     1168            <dd>
     1169               <dl>
     1170                  <dt>Magic number(s):</dt>
     1171                  <dd>none</dd>
     1172                  <dt>File extension(s):</dt>
     1173                  <dd>none</dd>
     1174                  <dt>Macintosh file type code(s):</dt>
     1175                  <dd>none</dd>
     1176               </dl>
     1177            </dd>
     1178            <dt>Person and email address to contact for further information:</dt>
     1179            <dd>See Authors Section.</dd>
     1180            <dt>Intended usage:</dt>
     1181            <dd>COMMON</dd>
     1182            <dt>Restrictions on usage:</dt>
     1183            <dd>none</dd>
     1184            <dt>Author/Change controller:</dt>
     1185            <dd>IESG</dd>
     1186         </dl>
     1187         <div id="rfc.figure.u.24"></div>
     1188         <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
    11541189  Date: Wed, 15 Nov 1995 06:25:24 GMT
    11551190  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    11681203  --THIS_STRING_SEPARATES--
    11691204</pre><div id="rfc.figure.u.25"></div>
    1170       <p>Other example:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
     1205         <p>Other example:</p><pre class="text">  HTTP/1.1 206 Partial Content
    11711206  Date: Tue, 14 Nov 1995 06:25:24 GMT
    11721207  Last-Modified: Tue, 14 July 04:58:08 GMT
     
    11841219  ...the second range
    11851220  --THIS_STRING_SEPARATES--
    1186 </pre> <p id="rfc.section.A.p.7">Notes: </p>
    1187       <ol>
    1188          <li>Additional CRLFs <em class="bcp14">MAY</em> precede the first boundary string in the body.
    1189          </li>
    1190          <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.
    1191          </li>
    1192          <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.
    1193          </li>
    1194       </ol>
    1195       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    1196       <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>
    1197       <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>)
    1198       </p>
    1199       <p id="rfc.section.B.1.p.2">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>)
    1200       </p>
    1201       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1202       <div id="rfc.figure.u.26"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
     1221</pre><p id="rfc.section.A.p.7">Notes: </p>
     1222         <ol>
     1223            <li>Additional CRLFs <em class="bcp14">MAY</em> precede the first boundary string in the body.
     1224            </li>
     1225            <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.
     1226            </li>
     1227            <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.
     1228            </li>
     1229         </ol>
     1230      </div>
     1231      <div id="compatibility">
     1232         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
     1233         <div id="changes.from.rfc.2616">
     1234            <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>
     1235            <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>)
     1236            </p>
     1237            <p id="rfc.section.B.1.p.2">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>)
     1238            </p>
     1239         </div>
     1240      </div>
     1241      <div id="collected.abnf">
     1242         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     1243         <div id="rfc.figure.u.26"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
    12031244<a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> = acceptable-ranges
    12041245
     
    12221263 instance-length / "*" )
    12231264<a href="#header.content-range" class="smpl">byte-range-resp-spec</a> = ( first-byte-pos "-" last-byte-pos ) / "*"
    1224 <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = ( *( "," OWS ) byte-range-spec ) / (
    1225  suffix-byte-range-spec *( OWS "," [ ( OWS byte-range-spec ) /
    1226  suffix-byte-range-spec ] ) )
     1265<a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = *( "," OWS ) ( byte-range-spec /
     1266 suffix-byte-range-spec ) *( OWS "," [ OWS ( byte-range-spec /
     1267 suffix-byte-range-spec ) ] )
    12271268<a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ]
    12281269<a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set
     
    12521293
    12531294<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
    1254 </pre> <div id="rfc.figure.u.27"></div>
    1255       <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
     1295</pre><div id="rfc.figure.u.27"></div>
     1296         <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
    12561297; Content-Range defined but not used
    12571298; If-Range defined but not used
    12581299; Range defined but not used
    1259 </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>
    1260       <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
    1261       </h2>
    1262       <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>.
    1263       </p>
    1264       <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
    1265       </h2>
    1266       <p id="rfc.section.D.2.p.1">Closed issues: </p>
    1267       <ul>
    1268          <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;)
    1269          </li>
    1270          <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"
    1271          </li>
    1272          <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"
    1273          </li>
    1274       </ul>
    1275       <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
    1276       </h2>
    1277       <p id="rfc.section.D.3.p.1">Closed issues: </p>
    1278       <ul>
    1279          <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"
    1280          </li>
    1281       </ul>
    1282       <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;):
    1283       </p>
    1284       <ul>
    1285          <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    1286       </ul>
    1287       <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>
    1288       <p id="rfc.section.D.4.p.1">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    1289       </p>
    1290       <ul>
    1291          <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
    1292       </ul>
    1293       <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>
    1294       <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>
    1295       <p id="rfc.section.D.6.p.1">Closed issues: </p>
    1296       <ul>
    1297          <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"
    1298          </li>
    1299       </ul>
    1300       <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;):
    1301       </p>
    1302       <ul>
    1303          <li>Use "/" instead of "|" for alternatives.</li>
    1304          <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
    1305          <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
    1306       </ul>
    1307       <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>
    1308       <p id="rfc.section.D.7.p.1">Closed issues: </p>
    1309       <ul>
    1310          <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"
    1311          </li>
    1312       </ul>
    1313       <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;):
    1314       </p>
    1315       <ul>
    1316          <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
    1317       </ul>
    1318       <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;):
    1319       </p>
    1320       <ul>
    1321          <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    1322       </ul>
    1323       <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>
    1324       <p id="rfc.section.D.8.p.1">Closed issues: </p>
    1325       <ul>
    1326          <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"
    1327          </li>
    1328       </ul>
    1329       <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>
    1330       <p id="rfc.section.D.9.p.1">Closed issues: </p>
    1331       <ul>
    1332          <li>Fixed discrepancy in the If-Range definition about allowed validators.</li>
    1333          <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"
    1334          </li>
    1335          <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"
    1336          </li>
    1337          <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"
    1338          </li>
    1339       </ul>
    1340       <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>
    1341       <p id="rfc.section.D.10.p.1">No significant changes.</p>
    1342       <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>
    1343       <p id="rfc.section.D.11.p.1">No significant changes.</p>
    1344       <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>
    1345       <p id="rfc.section.D.12.p.1">Closed issues: </p>
    1346       <ul>
    1347          <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'"
    1348          </li>
    1349          <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"
    1350          </li>
    1351          <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"
    1352          </li>
    1353       </ul>
    1354       <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;):
    1355       </p>
    1356       <ul>
    1357          <li>Add IANA registry.</li>
    1358       </ul>
     1300</pre></div>
     1301      <div id="change.log">
     1302         <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>
     1303         <div>
     1304            <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
     1305            </h2>
     1306            <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>.
     1307            </p>
     1308         </div>
     1309         <div>
     1310            <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
     1311            </h2>
     1312            <p id="rfc.section.D.2.p.1">Closed issues: </p>
     1313            <ul>
     1314               <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;)
     1315               </li>
     1316               <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"
     1317               </li>
     1318               <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"
     1319               </li>
     1320            </ul>
     1321         </div>
     1322         <div>
     1323            <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
     1324            </h2>
     1325            <p id="rfc.section.D.3.p.1">Closed issues: </p>
     1326            <ul>
     1327               <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"
     1328               </li>
     1329            </ul>
     1330            <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;):
     1331            </p>
     1332            <ul>
     1333               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
     1334            </ul>
     1335         </div>
     1336         <div id="changes.since.02">
     1337            <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>
     1338            <p id="rfc.section.D.4.p.1">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     1339            </p>
     1340            <ul>
     1341               <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
     1342            </ul>
     1343         </div>
     1344         <div id="changes.since.03">
     1345            <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>
     1346         </div>
     1347         <div id="changes.since.04">
     1348            <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>
     1349            <p id="rfc.section.D.6.p.1">Closed issues: </p>
     1350            <ul>
     1351               <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"
     1352               </li>
     1353            </ul>
     1354            <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;):
     1355            </p>
     1356            <ul>
     1357               <li>Use "/" instead of "|" for alternatives.</li>
     1358               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
     1359               <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
     1360            </ul>
     1361         </div>
     1362         <div id="changes.since.05">
     1363            <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>
     1364            <p id="rfc.section.D.7.p.1">Closed issues: </p>
     1365            <ul>
     1366               <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"
     1367               </li>
     1368            </ul>
     1369            <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;):
     1370            </p>
     1371            <ul>
     1372               <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
     1373            </ul>
     1374            <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;):
     1375            </p>
     1376            <ul>
     1377               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
     1378            </ul>
     1379         </div>
     1380         <div id="changes.since.06">
     1381            <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>
     1382            <p id="rfc.section.D.8.p.1">Closed issues: </p>
     1383            <ul>
     1384               <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"
     1385               </li>
     1386            </ul>
     1387         </div>
     1388         <div id="changes.since.07">
     1389            <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>
     1390            <p id="rfc.section.D.9.p.1">Closed issues: </p>
     1391            <ul>
     1392               <li>Fixed discrepancy in the If-Range definition about allowed validators.</li>
     1393               <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"
     1394               </li>
     1395               <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"
     1396               </li>
     1397               <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"
     1398               </li>
     1399            </ul>
     1400         </div>
     1401         <div id="changes.since.08">
     1402            <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>
     1403            <p id="rfc.section.D.10.p.1">No significant changes.</p>
     1404         </div>
     1405         <div id="changes.since.09">
     1406            <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>
     1407            <p id="rfc.section.D.11.p.1">No significant changes.</p>
     1408         </div>
     1409         <div id="changes.since.10">
     1410            <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>
     1411            <p id="rfc.section.D.12.p.1">Closed issues: </p>
     1412            <ul>
     1413               <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'"
     1414               </li>
     1415               <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"
     1416               </li>
     1417               <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"
     1418               </li>
     1419            </ul>
     1420            <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;):
     1421            </p>
     1422            <ul>
     1423               <li>Add IANA registry.</li>
     1424            </ul>
     1425         </div>
     1426      </div>
    13591427      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    13601428      <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>
     
    13621430      <div class="print2col">
    13631431         <ul class="ind">
    1364             <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind">
    1365                   <li class="indline1">206 Partial Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.3"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">6.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.1</a></li>
     1432            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
     1433                  <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>
    13661434               </ul>
    13671435            </li>
    1368             <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind">
    1369                   <li class="indline1">416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.4"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">6.1</a></li>
     1436            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
     1437                  <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>
    13701438               </ul>
    13711439            </li>
    1372             <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
    1373                   <li class="indline1">Accept-Ranges header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">6.2</a></li>
     1440            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
     1441                  <li>Accept-Ranges header&nbsp;&nbsp;<a href="#rfc.iref.a.1"><b>5.1</b></a>, <a href="#rfc.xref.header.accept-ranges.1">6.2</a></li>
    13741442               </ul>
    13751443            </li>
    1376             <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    1377                   <li class="indline1">Content-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">6.2</a></li>
     1444            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
     1445                  <li>Content-Range header&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.c.1"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a></li>
    13781446               </ul>
    13791447            </li>
    1380             <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
    1381                   <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
    1382                      <ul class="ind">
    1383                         <li class="indline1"><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>5.1</b></a></li>
    1384                         <li class="indline1"><tt>Accept-Ranges-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>5.1</b></a></li>
    1385                         <li class="indline1"><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>5.1</b></a></li>
    1386                         <li class="indline1"><tt>byte-content-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>5.2</b></a></li>
    1387                         <li class="indline1"><tt>byte-range-resp-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>5.2</b></a></li>
    1388                         <li class="indline1"><tt>byte-range-set</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>5.4.1</b></a></li>
    1389                         <li class="indline1"><tt>byte-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>5.4.1</b></a></li>
    1390                         <li class="indline1"><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>5.4.1</b></a></li>
    1391                         <li class="indline1"><tt>bytes-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>2</b></a></li>
    1392                         <li class="indline1"><tt>Content-Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>5.2</b></a></li>
    1393                         <li class="indline1"><tt>content-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>5.2</b></a></li>
    1394                         <li class="indline1"><tt>Content-Range-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>5.2</b></a></li>
    1395                         <li class="indline1"><tt>first-byte-pos</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>5.4.1</b></a></li>
    1396                         <li class="indline1"><tt>If-Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>5.3</b></a></li>
    1397                         <li class="indline1"><tt>If-Range-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>5.3</b></a></li>
    1398                         <li class="indline1"><tt>instance-length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>5.2</b></a></li>
    1399                         <li class="indline1"><tt>last-byte-pos</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>5.4.1</b></a></li>
    1400                         <li class="indline1"><tt>other-range-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>2</b></a></li>
    1401                         <li class="indline1"><tt>Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>5.4.2</b></a></li>
    1402                         <li class="indline1"><tt>range-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>2</b></a></li>
    1403                         <li class="indline1"><tt>ranges-specifier</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>5.4.1</b></a></li>
    1404                         <li class="indline1"><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>5.4.1</b></a></li>
    1405                         <li class="indline1"><tt>suffix-length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>5.4.1</b></a></li>
     1448            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
     1449                  <li><tt>Grammar</tt>&nbsp;&nbsp;
     1450                     <ul>
     1451                        <li><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>5.1</b></a></li>
     1452                        <li><tt>Accept-Ranges-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>5.1</b></a></li>
     1453                        <li><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>5.1</b></a></li>
     1454                        <li><tt>byte-content-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>5.2</b></a></li>
     1455                        <li><tt>byte-range-resp-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>5.2</b></a></li>
     1456                        <li><tt>byte-range-set</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>5.4.1</b></a></li>
     1457                        <li><tt>byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>5.4.1</b></a></li>
     1458                        <li><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>5.4.1</b></a></li>
     1459                        <li><tt>bytes-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2</b></a></li>
     1460                        <li><tt>Content-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>5.2</b></a></li>
     1461                        <li><tt>content-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>5.2</b></a></li>
     1462                        <li><tt>Content-Range-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>5.2</b></a></li>
     1463                        <li><tt>first-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>5.4.1</b></a></li>
     1464                        <li><tt>If-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>5.3</b></a></li>
     1465                        <li><tt>If-Range-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>5.3</b></a></li>
     1466                        <li><tt>instance-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>5.2</b></a></li>
     1467                        <li><tt>last-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>5.4.1</b></a></li>
     1468                        <li><tt>other-range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>2</b></a></li>
     1469                        <li><tt>Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>5.4.2</b></a></li>
     1470                        <li><tt>range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
     1471                        <li><tt>ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>5.4.1</b></a></li>
     1472                        <li><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>5.4.1</b></a></li>
     1473                        <li><tt>suffix-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>5.4.1</b></a></li>
    14061474                     </ul>
    14071475                  </li>
    14081476               </ul>
    14091477            </li>
    1410             <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
    1411                   <li class="indline1">Headers&nbsp;&nbsp;
    1412                      <ul class="ind">
    1413                         <li class="indline1">Accept-Ranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">6.2</a></li>
    1414                         <li class="indline1">Content-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">6.2</a></li>
    1415                         <li class="indline1">If-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.xref.header.if-range.2">3.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.3">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.4">6.2</a></li>
    1416                         <li class="indline1">Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">2</a>, <a class="iref" href="#rfc.xref.header.range.3">3.1</a>, <a class="iref" href="#rfc.xref.header.range.4">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">6.2</a></li>
     1478            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
     1479                  <li>Headers&nbsp;&nbsp;
     1480                     <ul>
     1481                        <li>Accept-Ranges&nbsp;&nbsp;<a href="#rfc.iref.h.1"><b>5.1</b></a>, <a href="#rfc.xref.header.accept-ranges.1">6.2</a></li>
     1482                        <li>Content-Range&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.h.2"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a></li>
     1483                        <li>If-Range&nbsp;&nbsp;<a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.xref.header.if-range.2">3.2</a>, <a href="#rfc.iref.h.3"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.3">5.4.2</a>, <a href="#rfc.xref.header.if-range.4">6.2</a></li>
     1484                        <li>Range&nbsp;&nbsp;<a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.xref.header.range.2">2</a>, <a href="#rfc.xref.header.range.3">3.1</a>, <a href="#rfc.xref.header.range.4">3.2</a>, <a href="#rfc.iref.h.4"><b>5.4</b></a>, <a href="#rfc.xref.header.range.5">6.2</a></li>
    14171485                     </ul>
    14181486                  </li>
    14191487               </ul>
    14201488            </li>
    1421             <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
    1422                   <li class="indline1">If-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.xref.header.if-range.2">3.2</a>, <a class="iref" href="#rfc.iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.3">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.4">6.2</a></li>
     1489            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
     1490                  <li>If-Range header&nbsp;&nbsp;<a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.xref.header.if-range.2">3.2</a>, <a href="#rfc.iref.i.1"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.3">5.4.2</a>, <a href="#rfc.xref.header.if-range.4">6.2</a></li>
    14231491               </ul>
    14241492            </li>
    1425             <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">
    1426                   <li class="indline1">Media Type&nbsp;&nbsp;
    1427                      <ul class="ind">
    1428                         <li class="indline1">multipart/byteranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.1"><b>A</b></a></li>
    1429                         <li class="indline1">multipart/x-byteranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.4">A</a></li>
     1493            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
     1494                  <li>Media Type&nbsp;&nbsp;
     1495                     <ul>
     1496                        <li>multipart/byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>A</b></a></li>
     1497                        <li>multipart/x-byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.4">A</a></li>
    14301498                     </ul>
    14311499                  </li>
    1432                   <li class="indline1">multipart/byteranges Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>A</b></a></li>
    1433                   <li class="indline1">multipart/x-byteranges Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3">A</a></li>
     1500                  <li>multipart/byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>A</b></a></li>
     1501                  <li>multipart/x-byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.3">A</a></li>
    14341502               </ul>
    14351503            </li>
    1436             <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    1437                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.2</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.6">7</a>, <a class="iref" href="#Part1"><b>9.1</b></a><ul class="ind">
    1438                         <li class="indline1"><em>Section 1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.2</a></li>
    1439                         <li class="indline1"><em>Section 1.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a></li>
    1440                         <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li>
     1504            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
     1505                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.2</a>, <a href="#rfc.xref.Part1.6">7</a>, <a href="#Part1"><b>9.1</b></a><ul>
     1506                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a></li>
     1507                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a></li>
     1508                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2.2</a></li>
    14411509                     </ul>
    14421510                  </li>
    1443                   <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.2">4</a>, <a class="iref" href="#Part4"><b>9.1</b></a><ul class="ind">
    1444                         <li class="indline1"><em>Section 2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.2.2</a></li>
    1445                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.2">4</a></li>
     1511                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2.2</a>, <a href="#rfc.xref.Part4.2">4</a>, <a href="#Part4"><b>9.1</b></a><ul>
     1512                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2.2</a></li>
     1513                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">4</a></li>
    14461514                     </ul>
    14471515                  </li>
    14481516               </ul>
    14491517            </li>
    1450             <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    1451                   <li class="indline1">Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">2</a>, <a class="iref" href="#rfc.xref.header.range.3">3.1</a>, <a class="iref" href="#rfc.xref.header.range.4">3.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">6.2</a></li>
    1452                   <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a>, <a class="iref" href="#rfc.xref.RFC2046.2">A</a><ul class="ind">
    1453                         <li class="indline1"><em>Section 5.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.1">A</a></li>
     1518            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
     1519                  <li>Range header&nbsp;&nbsp;<a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.xref.header.range.2">2</a>, <a href="#rfc.xref.header.range.3">3.1</a>, <a href="#rfc.xref.header.range.4">3.2</a>, <a href="#rfc.iref.r.1"><b>5.4</b></a>, <a href="#rfc.xref.header.range.5">6.2</a></li>
     1520                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#RFC2046"><b>9.1</b></a>, <a href="#rfc.xref.RFC2046.1">A</a>, <a href="#rfc.xref.RFC2046.2">A</a><ul>
     1521                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">A</a></li>
    14541522                     </ul>
    14551523                  </li>
    1456                   <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>
    1457                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li>
    1458                   <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">6.2</a>, <a class="iref" href="#RFC3864"><b>9.2</b></a></li>
    1459                   <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#RFC4288"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>
    1460                   <li class="indline1"><em>RFC5226</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.1</a>, <a class="iref" href="#RFC5226"><b>9.2</b></a><ul class="ind">
    1461                         <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.1</a></li>
     1524                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>9.1</b></a></li>
     1525                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#RFC2616"><b>9.2</b></a>, <a href="#rfc.xref.RFC2616.1">D.1</a></li>
     1526                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">6.2</a>, <a href="#RFC3864"><b>9.2</b></a></li>
     1527                  <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#RFC4288"><b>9.2</b></a>, <a href="#rfc.xref.RFC4288.1">A</a></li>
     1528                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a>, <a href="#RFC5226"><b>9.2</b></a><ul>
     1529                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a></li>
    14621530                     </ul>
    14631531                  </li>
    1464                   <li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.2</a>, <a class="iref" href="#rfc.xref.RFC5234.2">1.2</a>, <a class="iref" href="#RFC5234"><b>9.1</b></a><ul class="ind">
    1465                         <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.2">1.2</a></li>
     1532                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#RFC5234"><b>9.1</b></a><ul>
     1533                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
    14661534                     </ul>
    14671535                  </li>
    14681536               </ul>
    14691537            </li>
    1470             <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
    1471                   <li class="indline1">Status Codes&nbsp;&nbsp;
    1472                      <ul class="ind">
    1473                         <li class="indline1">206 Partial Content&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">6.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.1</a></li>
    1474                         <li class="indline1">416 Requested Range Not Satisfiable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">6.1</a></li>
     1538            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
     1539                  <li>Status Codes&nbsp;&nbsp;
     1540                     <ul>
     1541                        <li>206 Partial Content&nbsp;&nbsp;<a href="#rfc.iref.s.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>
     1542                        <li>416 Requested Range Not Satisfiable&nbsp;&nbsp;<a href="#rfc.iref.s.2"><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>
    14751543                     </ul>
    14761544                  </li>
     
    14791547         </ul>
    14801548      </div>
     1549      <div class="avoidbreak">
     1550         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     1551         <p><b>Roy T. Fielding</b>
     1552            (editor)
     1553            <br>Day Software<br>23 Corporate Plaza DR, Suite 280<br>Newport Beach, CA&nbsp;92660<br>USA<br>Phone: <a href="tel:+1-949-706-5300">+1-949-706-5300</a><br>Fax: <a href="fax:+1-949-706-5305">+1-949-706-5305</a><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>
     1554         <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>
     1555         <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>
     1556         <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>
     1557         <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>
     1558         <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>
     1559         <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>
     1560         <p><b>Yves Lafon</b>
     1561            (editor)
     1562            <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>
     1563         <p><b>Julian F. Reschke</b>
     1564            (editor)
     1565            <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>
     1566      </div>
    14811567   </body>
    14821568</html>
Note: See TracChangeset for help on using the changeset viewer.