Ignore:
Timestamp:
14/06/14 11:20:37 (6 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

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

    r1099 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 {
    3031  font-style: normal;
    3132}
    32 dd {
    33   margin-right: 2em;
    34 }
    3533dl {
    3634  margin-left: 2em;
    3735}
    38 
    3936ul.empty {
    4037  list-style-type: none;
     
    5047}
    5148h1 {
    52   font-size: 14pt;
     49  font-size: 130%;
    5350  line-height: 21pt;
    5451  page-break-after: avoid;
     
    5754  page-break-before: always;
    5855}
    59 h1 a {
    60   color: #333333;
    61 }
    6256h2 {
    63   font-size: 12pt;
     57  font-size: 120%;
    6458  line-height: 15pt;
    6559  page-break-after: avoid;
    6660}
    67 h3, h4, h5, h6 {
    68   font-size: 10pt;
     61h3 {
     62  font-size: 110%;
    6963  page-break-after: avoid;
    7064}
    71 h2 a, h3 a, h4 a, h5 a, h6 a {
     65h4, h5, h6 {
     66  page-break-after: avoid;
     67}
     68h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    7269  color: black;
    7370}
     
    7774li {
    7875  margin-left: 2em;
    79   margin-right: 2em;
    8076}
    8177ol {
    8278  margin-left: 2em;
    83   margin-right: 2em;
     79}
     80ol.la {
     81  list-style-type: lower-alpha;
     82}
     83ol.ua {
     84  list-style-type: upper-alpha;
    8485}
    8586ol p {
     
    8889p {
    8990  margin-left: 2em;
    90   margin-right: 2em;
    9191}
    9292pre {
     
    9494  background-color: lightyellow;
    9595  padding: .25em;
     96  page-break-inside: avoid;
    9697}
    9798pre.text2 {
     
    122123table.tt {
    123124  vertical-align: top;
     125  border-color: gray;
     126}
     127table.tt th {
     128  border-color: gray;
     129}
     130table.tt td {
     131  border-color: gray;
     132}
     133table.all {
     134  border-style: solid;
     135  border-width: 2px;
    124136}
    125137table.full {
    126   border-style: outset;
    127   border-width: 1px;
    128 }
    129 table.headers {
    130   border-style: outset;
    131   border-width: 1px;
     138  border-style: solid;
     139  border-width: 2px;
    132140}
    133141table.tt td {
    134142  vertical-align: top;
    135143}
     144table.all td {
     145  border-style: solid;
     146  border-width: 1px;
     147}
    136148table.full td {
    137   border-style: inset;
     149  border-style: none solid;
    138150  border-width: 1px;
    139151}
     
    141153  vertical-align: top;
    142154}
     155table.all th {
     156  border-style: solid;
     157  border-width: 1px;
     158}
    143159table.full th {
    144   border-style: inset;
    145   border-width: 1px;
     160  border-style: solid;
     161  border-width: 1px 1px 2px 1px;
    146162}
    147163table.headers th {
    148   border-style: none none inset none;
    149   border-width: 1px;
     164  border-style: none none solid none;
     165  border-width: 2px;
    150166}
    151167table.left {
     
    162178  caption-side: bottom;
    163179  font-weight: bold;
    164   font-size: 9pt;
     180  font-size: 10pt;
    165181  margin-top: .5em;
    166182}
     
    169185  border-spacing: 1px;
    170186  width: 95%;
    171   font-size: 10pt;
     187  font-size: 11pt;
    172188  color: white;
    173189}
     
    177193td.topnowrap {
    178194  vertical-align: top;
    179   white-space: nowrap; 
     195  white-space: nowrap;
    180196}
    181197table.header td {
     
    197213  list-style: none;
    198214  margin-left: 1.5em;
    199   margin-right: 0em;
    200215  padding-left: 0em;
    201216}
     
    203218  line-height: 150%;
    204219  font-weight: bold;
    205   font-size: 10pt;
    206220  margin-left: 0em;
    207   margin-right: 0em;
    208221}
    209222ul.toc li li {
    210223  line-height: normal;
    211224  font-weight: normal;
    212   font-size: 9pt;
     225  font-size: 10pt;
    213226  margin-left: 0em;
    214   margin-right: 0em;
    215227}
    216228li.excluded {
     
    219231ul p {
    220232  margin-left: 0em;
     233}
     234.title, .filename, h1, h2, h3, h4 {
     235  font-family: candara, helvetica, arial, sans-serif;
     236}
     237samp, tt, code, pre {
     238  font: consolas, monospace;
    221239}
    222240ul.ind, ul.ind ul {
    223241  list-style: none;
    224242  margin-left: 1.5em;
    225   margin-right: 0em;
    226243  padding-left: 0em;
    227244  page-break-before: avoid;
     
    231248  line-height: 200%;
    232249  margin-left: 0em;
    233   margin-right: 0em;
    234250}
    235251ul.ind li li {
     
    237253  line-height: 150%;
    238254  margin-left: 0em;
    239   margin-right: 0em;
    240255}
    241256.avoidbreak {
     
    261276  font-weight: bold;
    262277  text-align: center;
    263   font-size: 9pt;
     278  font-size: 10pt;
    264279}
    265280.filename {
    266281  color: #333333;
     282  font-size: 75%;
    267283  font-weight: bold;
    268   font-size: 12pt;
    269284  line-height: 21pt;
    270285  text-align: center;
     
    273288  font-weight: bold;
    274289}
    275 .hidden {
    276   display: none;
    277 }
    278290.left {
    279291  text-align: left;
     
    283295}
    284296.title {
    285   color: #990000;
    286   font-size: 18pt;
     297  color: green;
     298  font-size: 150%;
    287299  line-height: 18pt;
    288300  font-weight: bold;
     
    290302  margin-top: 36pt;
    291303}
    292 .vcardline {
    293   display: block;
    294 }
    295304.warning {
    296   font-size: 14pt;
     305  font-size: 130%;
    297306  background-color: yellow;
    298307}
     
    303312    display: none;
    304313  }
    305  
     314
    306315  a {
    307316    color: black;
     
    318327    background-color: white;
    319328    vertical-align: top;
    320     font-size: 12pt;
     329    font-size: 110%;
    321330  }
    322331
    323   ul.toc a::after {
     332  ul.toc a:nth-child(2)::after {
    324333    content: leader('.') target-counter(attr(href), page);
    325334  }
    326  
     335
    327336  ul.ind li li a {
    328337    content: target-counter(attr(href), page);
    329338  }
    330  
     339
    331340  .print2col {
    332341    column-count: 2;
     
    338347@page {
    339348  @top-left {
    340        content: "Internet-Draft"; 
    341   } 
     349       content: "Internet-Draft";
     350  }
    342351  @top-right {
    343        content: "March 2009"; 
    344   } 
     352       content: "March 2009";
     353  }
    345354  @top-center {
    346        content: "HTTP/1.1, Part 5"; 
    347   } 
     355       content: "HTTP/1.1, Part 5";
     356  }
    348357  @bottom-left {
    349        content: "Fielding, et al."; 
    350   } 
     358       content: "Fielding, et al.";
     359  }
    351360  @bottom-center {
    352        content: "Standards Track";
    353   } 
     361       content: "Expires September 10, 2009";
     362  }
    354363  @bottom-right {
    355        content: "[Page " counter(page) "]"; 
    356   } 
    357 }
    358 
    359 @page:first { 
     364       content: "[Page " counter(page) "]";
     365  }
     366}
     367
     368@page:first {
    360369    @top-left {
    361370      content: normal;
     
    385394      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
    386395      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    387       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.537, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     396      <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/">
    388397      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    389398      <meta name="dct.creator" content="Fielding, R.">
     
    414423            </tr>
    415424            <tr>
    416                <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     425               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    417426               </td>
    418427               <td class="right">J. Gettys</td>
     
    485494      </table>
    486495      <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-06</span></p>
    487       <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    488       <p>This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain
    489          material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s)
    490          controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of
    491          such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the
    492          copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of
    493          it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it
    494          into languages other than English.
    495       </p>
    496       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
    497          that other groups may also distribute working documents as Internet-Drafts.
    498       </p>
    499       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    500          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    501          in progress”.
    502       </p>
    503       <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
    504       </p>
    505       <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
    506       </p>
    507       <p>This Internet-Draft will expire on September 10, 2009.</p>
    508       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    509       <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    510       <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date
    511          of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
    512       </p>
    513       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
     496      <div id="rfc.status">
     497         <h1><a href="#rfc.status">Status of this Memo</a></h1>
     498         <p>This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain
     499            material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s)
     500            controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of
     501            such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the
     502            copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of
     503            it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it
     504            into languages other than English.
     505         </p>
     506         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
     507            that other groups may also distribute working documents as Internet-Drafts.
     508         </p>
     509         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     510            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     511            in progress”.
     512         </p>
     513         <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
     514         </p>
     515         <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
     516         </p>
     517         <p>This Internet-Draft will expire on September 10, 2009.</p>
     518      </div>
     519      <div id="rfc.copyrightnotice">
     520         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     521         <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     522         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date
     523            of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
     524         </p>
     525      </div>
     526      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    514527      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    515528         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
    516529         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
    517530         5 defines range-specific requests and the rules for constructing and combining responses to those requests.
    518       </p> 
    519       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
     531      </p>
     532      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    520533      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    521534         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</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;.
    522       </p> 
     535      </p>
    523536      <p>The changes in this draft are summarized in <a href="#changes.since.05" title="Since draft-ietf-httpbis-p5-range-05">Appendix&nbsp;D.7</a>.
    524       </p> 
     537      </p>
    525538      <hr class="noprint">
    526539      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    527540      <ul class="toc">
    528          <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    529                <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    530                <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
    531                      <li>1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    532                      <li>1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     541         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     542               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     543               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     544                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     545                     <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>
    533546                  </ul>
    534547               </li>
    535548            </ul>
    536549         </li>
    537          <li>2.&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
    538          <li>3.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul>
    539                <li>3.1&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    540                <li>3.2&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
     550         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
     551         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul>
     552               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
     553               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
    541554            </ul>
    542555         </li>
    543          <li>4.&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
    544          <li>5.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
    545                <li>5.1&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
    546                <li>5.2&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
    547                <li>5.3&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
    548                <li>5.4&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
    549                      <li>5.4.1&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
    550                      <li>5.4.2&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
     556         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
     557         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     558               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
     559               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
     560               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
     561               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
     562                     <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
     563                     <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>
    551564                  </ul>
    552565               </li>
    553566            </ul>
    554567         </li>
    555          <li>6.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    556                <li>6.1&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
     568         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     569               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
    557570            </ul>
    558571         </li>
    559          <li>7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
    560          <li>8.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    561          <li>9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    562                <li>9.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    563                <li>9.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     572         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
     573         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     574         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     575               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     576               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    564577            </ul>
    565578         </li>
    566          <li><a href="#rfc.authors">Authors' Addresses</a></li>
    567          <li>A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
    568          <li>B.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
    569                <li>B.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
    570                <li>B.2&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     579         <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>
     580         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
     581               <li><a href="#rfc.section.B.1">B.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
     582               <li><a href="#rfc.section.B.2">B.2</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    571583            </ul>
    572584         </li>
    573          <li>C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    574          <li>D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    575                <li>D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC2616</a></li>
    576                <li>D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p5-range-00</a></li>
    577                <li>D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p5-range-01</a></li>
    578                <li>D.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></li>
    579                <li>D.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></li>
    580                <li>D.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></li>
    581                <li>D.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></li>
     585         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     586         <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>
     587               <li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC2616</a></li>
     588               <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>
     589               <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>
     590               <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>
     591               <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>
     592               <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>
     593               <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>
    582594            </ul>
    583595         </li>
    584596         <li><a href="#rfc.index">Index</a></li>
     597         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    585598      </ul>
    586       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    587       <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
    588          has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
    589          rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
    590          request only a subset of a larger representation, such as a single page of a very large document or only part of an image
    591          to be rendered by a device with limited local storage.
    592       </p>
    593       <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
    594          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
    595          request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
    596          full responses by intermediate caches that might not implement the feature.
    597       </p>
    598       <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
    599          requests for byte ranges.
    600       </p>
    601       <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>
    602       <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"
    603          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>.
    604       </p>
    605       <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
    606       </p>
    607       <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>
    608       <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.
    609       </p>
    610       <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
    611          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
    612          and WSP (whitespace).
    613       </p>
    614       <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>
    615       <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>:
    616       </p>
    617       <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;
     599      <div id="introduction">
     600         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     601         <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
     602            has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
     603            rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
     604            request only a subset of a larger representation, such as a single page of a very large document or only part of an image
     605            to be rendered by a device with limited local storage.
     606         </p>
     607         <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
     608            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
     609            request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
     610            full responses by intermediate caches that might not implement the feature.
     611         </p>
     612         <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
     613            requests for byte ranges.
     614         </p>
     615         <div id="intro.requirements">
     616            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     617            <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"
     618               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>.
     619            </p>
     620            <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
     621            </p>
     622         </div>
     623         <div id="notation">
     624            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     625            <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.
     626            </p>
     627            <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
     628               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
     629               and WSP (whitespace).
     630            </p>
     631            <div id="core.rules">
     632               <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>
     633               <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>:
     634               </p>
     635               <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;
    618636  <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;
    619 </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>
    620       <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
    621       <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#full.date" title="Full Date">Section 3.2.1</a>&gt;
     637</pre></div>
     638            <div id="abnf.dependencies">
     639               <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>
     640               <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
     641               <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#full.date" title="Full Date">Section 3.2.1</a>&gt;
    622642</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;
    623 </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>
    624       <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1
    625          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. An entity can be broken down into subranges according to various structural units.
    626       </p>
    627       <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>
     643</pre></div>
     644         </div>
     645      </div>
     646      <div id="range.units">
     647         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#range.units">Range Units</a></h1>
     648         <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1
     649            uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;5.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;5.2</a>) header fields. An entity can be broken down into subranges according to various structural units.
     650         </p>
     651         <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#range.units" class="smpl">range-unit</a>       = <a href="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a>
    628652  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
    629653  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a>
    630654</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
    631          unit defined by HTTP/1.1 is "bytes".
    632       </p>
    633       <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.
    634       </p>
    635       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
    636       </h1>
    637       <div id="rfc.iref.3"></div>
    638       <div id="rfc.iref.s.1"></div>
    639       <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>
    640       <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.
    641       </p>
    642       <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
    643       </p>
    644       <ul>
    645          <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
    646             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.
    647          </li>
    648          <li>Date</li>
    649          <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
    650          <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
    651             variant
    652          </li>
    653       </ul>
    654       <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 entity-headers. Otherwise, the response <em class="bcp14">MUST</em> include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
    655       </p>
    656       <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>.
    657       </p>
    658       <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
    659          it <em class="bcp14">MUST NOT</em> be cached either.
    660       </p>
    661       <div id="rfc.iref.4"></div>
    662       <div id="rfc.iref.s.2"></div>
    663       <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>
    664       <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
    665          did not include an If-Range request-header field. (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec
    666          values were greater than the current length of the selected resource.)
    667       </p>
    668       <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 entity-header field specifying the current length of the selected resource (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.
    669       </p>
    670       <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>
    671       <p id="rfc.section.4.p.1">A response might transfer only a subrange of an entity-body, either the request included one or more Range specifications,
    672          or because a connection was broken prematurely. After several such transfers, a cache might have received several ranges of
    673          the same entity-body.
    674       </p>
    675       <p id="rfc.section.4.p.2">If a cache has a stored non-empty set of subranges for an entity, and an incoming response transfers another subrange, the
    676          cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
    677       </p>
    678       <ul>
    679          <li>Both the incoming response and the cache entry have a cache validator.</li>
    680          <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>).
    681          </li>
    682       </ul>
    683       <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
    684          response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
    685       </p>
    686       <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>
    687       <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>
    688       <p id="rfc.section.5.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
    689          receives the entity.
    690       </p>
    691       <div id="rfc.iref.a.1"></div>
    692       <div id="rfc.iref.h.1"></div>
    693       <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>
    694       <p id="rfc.section.5.1.p.1">The response-header "Accept-Ranges" field allows the server to indicate its acceptance of range requests for a resource:</p>
    695       <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>
     655            unit defined by HTTP/1.1 is "bytes".
     656         </p>
     657         <p id="rfc.section.2.p.4">If a range unit is not understood in a request, a server <em class="bcp14">MUST</em> ignore the whole Range header (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;5.4</a>). If a range unit is not understood in a response, an intermediary <em class="bcp14">SHOULD</em> pass the response to the client; a client <em class="bcp14">MUST</em> fail.
     658         </p>
     659      </div>
     660      <div>
     661         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
     662         </h1>
     663         <div id="status.206">
     664            <div id="rfc.iref.2.1"></div>
     665            <div id="rfc.iref.s.1"></div>
     666            <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>
     667            <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.
     668            </p>
     669            <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
     670            </p>
     671            <ul>
     672               <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
     673                  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.
     674               </li>
     675               <li>Date</li>
     676               <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
     677               <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
     678                  variant
     679               </li>
     680            </ul>
     681            <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 entity-headers. Otherwise, the response <em class="bcp14">MUST</em> include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
     682            </p>
     683            <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>.
     684            </p>
     685            <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
     686               it <em class="bcp14">MUST NOT</em> be cached either.
     687            </p>
     688         </div>
     689         <div id="status.416">
     690            <div id="rfc.iref.4.1"></div>
     691            <div id="rfc.iref.s.2"></div>
     692            <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>
     693            <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
     694               did not include an If-Range request-header field. (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec
     695               values were greater than the current length of the selected resource.)
     696            </p>
     697            <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 entity-header field specifying the current length of the selected resource (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.
     698            </p>
     699         </div>
     700      </div>
     701      <div id="combining.byte.ranges">
     702         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></h1>
     703         <p id="rfc.section.4.p.1">A response might transfer only a subrange of an entity-body, either the request included one or more Range specifications,
     704            or because a connection was broken prematurely. After several such transfers, a cache might have received several ranges of
     705            the same entity-body.
     706         </p>
     707         <p id="rfc.section.4.p.2">If a cache has a stored non-empty set of subranges for an entity, and an incoming response transfers another subrange, the
     708            cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
     709         </p>
     710         <ul>
     711            <li>Both the incoming response and the cache entry have a cache validator.</li>
     712            <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>).
     713            </li>
     714         </ul>
     715         <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
     716            response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
     717         </p>
     718      </div>
     719      <div id="header.fields">
     720         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     721         <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>
     722         <p id="rfc.section.5.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
     723            receives the entity.
     724         </p>
     725         <div id="header.accept-ranges">
     726            <div id="rfc.iref.a.1"></div>
     727            <div id="rfc.iref.h.1"></div>
     728            <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>
     729            <p id="rfc.section.5.1.p.1">The response-header "Accept-Ranges" field allows the server to indicate its acceptance of range requests for a resource:</p>
     730            <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>
    696731  <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>   = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
    697732  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
    698733</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
    699       </p>
    700       <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: bytes
     734            </p>
     735            <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: bytes
    701736</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>.
    702       </p>
    703       <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
    704       </p>
    705       <div id="rfc.figure.u.7"></div><pre class="text">  Accept-Ranges: none
     737            </p>
     738            <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
     739            </p>
     740            <div id="rfc.figure.u.7"></div><pre class="text">  Accept-Ranges: none
    706741</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
    707       <div id="rfc.iref.c.1"></div>
    708       <div id="rfc.iref.h.2"></div>
    709       <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>
    710       <p id="rfc.section.5.2.p.1">The entity-header "Content-Range" is sent with a partial entity-body to specify where in the full entity-body the partial
    711          body should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
    712       </p>
    713       <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>
     742         </div>
     743         <div id="header.content-range">
     744            <div id="rfc.iref.c.1"></div>
     745            <div id="rfc.iref.h.2"></div>
     746            <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>
     747            <p id="rfc.section.5.2.p.1">The entity-header "Content-Range" is sent with a partial entity-body to specify where in the full entity-body the partial
     748               body should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
     749            </p>
     750            <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>
    714751  <a href="#header.content-range" class="smpl">Content-Range-v</a> = <a href="#header.content-range" class="smpl">content-range-spec</a>
    715752 
     
    729766  <a href="#header.content-range" class="smpl">other-range-resp-spec</a>    = *<a href="#notation" class="smpl">CHAR</a>
    730767</pre><p id="rfc.section.5.2.p.3">The header <em class="bcp14">SHOULD</em> indicate the total length of the full entity-body, unless this length is unknown or difficult to determine. The asterisk "*"
    731          character means that the instance-length is unknown at the time when the response was generated.
    732       </p>
    733       <p id="rfc.section.5.2.p.4">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.
    734       </p>
    735       <p id="rfc.section.5.2.p.5">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
    736          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.
    737       </p>
    738       <p id="rfc.section.5.2.p.6">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
    739          selected resource as a decimal number. 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 "*".
    740       </p>
    741       <p id="rfc.section.5.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p>
    742       <ul>
    743          <li>The first 500 bytes:
    744             <div id="rfc.figure.u.9"></div><pre class="text">   bytes 0-499/1234
     768               character means that the instance-length is unknown at the time when the response was generated.
     769            </p>
     770            <p id="rfc.section.5.2.p.4">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.
     771            </p>
     772            <p id="rfc.section.5.2.p.5">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
     773               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.
     774            </p>
     775            <p id="rfc.section.5.2.p.6">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
     776               selected resource as a decimal number. 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 "*".
     777            </p>
     778            <p id="rfc.section.5.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p>
     779            <ul>
     780               <li>The first 500 bytes: <span id="rfc.figure.u.9"></span><pre class="text">   bytes 0-499/1234
    745781</pre> </li>
    746          <li>The second 500 bytes:
    747             <div id="rfc.figure.u.10"></div><pre class="text">   bytes 500-999/1234
     782               <li>The second 500 bytes: <span id="rfc.figure.u.10"></span><pre class="text">   bytes 500-999/1234
    748783</pre> </li>
    749          <li>All except for the first 500 bytes:
    750             <div id="rfc.figure.u.11"></div><pre class="text">   bytes 500-1233/1234
     784               <li>All except for the first 500 bytes: <span id="rfc.figure.u.11"></span><pre class="text">   bytes 500-1233/1234
    751785</pre> </li>
    752          <li>The last 500 bytes:
    753             <div id="rfc.figure.u.12"></div><pre class="text">   bytes 734-1233/1234
     786               <li>The last 500 bytes: <span id="rfc.figure.u.12"></span><pre class="text">   bytes 734-1233/1234
    754787</pre> </li>
    755       </ul>
    756       <p id="rfc.section.5.2.p.8">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
    757          a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
    758          a Content-Length header showing the number of bytes actually transferred. For example,
    759       </p>
    760       <div id="rfc.figure.u.13"></div><pre class="text">  HTTP/1.1 206 Partial Content
     788            </ul>
     789            <p id="rfc.section.5.2.p.8">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
     790               a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
     791               a Content-Length header showing the number of bytes actually transferred. For example,
     792            </p>
     793            <div id="rfc.figure.u.13"></div><pre class="text">  HTTP/1.1 206 Partial Content
    761794  Date: Wed, 15 Nov 1995 06:25:24 GMT
    762795  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    765798  Content-Type: image/gif
    766799</pre><p id="rfc.section.5.2.p.10">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
    767          ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
    768          as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>. See <a href="#changes.from.rfc.2068" title="Changes from RFC 2068">Appendix&nbsp;B.1</a> for a compatibility issue.
    769       </p>
    770       <p id="rfc.section.5.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
    771       </p>
    772       <p id="rfc.section.5.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
    773       </p>
    774       <p id="rfc.section.5.2.p.13">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
    775          the full entity).
    776       </p>
    777       <p id="rfc.section.5.2.p.14">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header
    778          field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
    779          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>).
    780       </p>
    781       <ul class="empty">
    782          <li> <b>Note:</b> clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
    783             an unsatisfiable Range request-header, since not all servers implement this request-header.
    784          </li>
    785       </ul>
    786       <div id="rfc.iref.i.1"></div>
    787       <div id="rfc.iref.h.3"></div>
    788       <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>
    789       <p id="rfc.section.5.3.p.1">If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its
    790          cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.)
    791          However, if the condition fails because the entity has been modified, the client would then have to make a second request
    792          to obtain the entire current entity-body.
    793       </p>
    794       <p id="rfc.section.5.3.p.2">The request header "If-Range" allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity
    795          is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity'.
    796       </p>
    797       <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>
     800               ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
     801               as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>. See <a href="#changes.from.rfc.2068" title="Changes from RFC 2068">Appendix&nbsp;B.1</a> for a compatibility issue.
     802            </p>
     803            <p id="rfc.section.5.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
     804            </p>
     805            <p id="rfc.section.5.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
     806            </p>
     807            <p id="rfc.section.5.2.p.13">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
     808               the full entity).
     809            </p>
     810            <p id="rfc.section.5.2.p.14">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header
     811               field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
     812               resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>).
     813            </p>
     814            <ul class="empty">
     815               <li><b>Note:</b> clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
     816                  an unsatisfiable Range request-header, since not all servers implement this request-header.
     817               </li>
     818            </ul>
     819         </div>
     820         <div id="header.if-range">
     821            <div id="rfc.iref.i.1"></div>
     822            <div id="rfc.iref.h.3"></div>
     823            <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>
     824            <p id="rfc.section.5.3.p.1">If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its
     825               cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.)
     826               However, if the condition fails because the entity has been modified, the client would then have to make a second request
     827               to obtain the entire current entity-body.
     828            </p>
     829            <p id="rfc.section.5.3.p.2">The request header "If-Range" allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity
     830               is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity'.
     831            </p>
     832            <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>
    798833  <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>
    799834</pre><p id="rfc.section.5.3.p.4">If the client has no entity tag for an entity, 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
    800          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.
    801       </p>
    802       <p id="rfc.section.5.3.p.5">If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial Content) response. If the entity tag does not match, then
    803          the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response.
    804       </p>
    805       <div id="rfc.iref.r.1"></div>
    806       <div id="rfc.iref.h.4"></div>
    807       <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>
    808       <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>
    809       <p id="rfc.section.5.4.1.p.1">Since all HTTP entities are represented in HTTP messages as sequences of bytes, the concept of a byte range is meaningful
    810          for any HTTP entity. (However, not all clients and servers need to support byte-range operations.)
    811       </p>
    812       <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the entity-body (not necessarily the same as the message-body).</p>
    813       <div id="rule.ranges-specifier">
    814          <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 entity.
    815          </p>
    816       </div>
    817       <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>
     835               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.
     836            </p>
     837            <p id="rfc.section.5.3.p.5">If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial Content) response. If the entity tag does not match, then
     838               the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response.
     839            </p>
     840         </div>
     841         <div id="header.range">
     842            <div id="rfc.iref.r.1"></div>
     843            <div id="rfc.iref.h.4"></div>
     844            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.range">Range</a></h2>
     845            <div id="byte.ranges">
     846               <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>
     847               <p id="rfc.section.5.4.1.p.1">Since all HTTP entities are represented in HTTP messages as sequences of bytes, the concept of a byte range is meaningful
     848                  for any HTTP entity. (However, not all clients and servers need to support byte-range operations.)
     849               </p>
     850               <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the entity-body (not necessarily the same as the message-body).</p>
     851               <div id="rule.ranges-specifier">
     852                  <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 entity.
     853                  </p>
     854               </div>
     855               <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>
    818856  <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> )
    819857  <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> ]
     
    821859  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
    822860</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
    823          gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets are
    824          decimal and start at zero.
    825       </p>
    826       <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
    827          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.
    828       </p>
    829       <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 entity-body, last-byte-pos
    830          is taken to be equal to one less than the current length of the entity-body in bytes.
    831       </p>
    832       <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 entity.</p>
    833       <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>
     861                  gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets are
     862                  decimal and start at zero.
     863               </p>
     864               <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
     865                  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.
     866               </p>
     867               <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 entity-body, last-byte-pos
     868                  is taken to be equal to one less than the current length of the entity-body in bytes.
     869               </p>
     870               <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 entity.</p>
     871               <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>
    834872  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    835873</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the decimal suffix-length
    836          value. (That is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length,
    837          the entire entity-body is used.
    838       </p>
    839       <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
    840          length of the entity-body, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is
    841          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 status of 416 (Requested range not satisfiable). Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a status of 206 (Partial Content) containing the satisfiable ranges of the entity-body.
    842       </p>
    843       <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
    844       <ul>
    845          <li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li>
    846          <li>The second 500 bytes (byte offsets 500-999, inclusive): bytes=500-999</li>
    847          <li>The final 500 bytes (byte offsets 9500-9999, inclusive): bytes=-500</li>
    848          <li>Or bytes=9500-</li>
    849          <li>The first and last bytes only (bytes 0 and 9999): bytes=0-0,-1</li>
    850          <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): <br> bytes=500-600,601-999<br> bytes=500-700,601-999
    851          </li>
    852       </ul>
    853       <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>
    854       <p id="rfc.section.5.4.2.p.1">HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies
    855          to the entity returned as the result of the request:
    856       </p>
    857       <div id="rfc.figure.u.17"></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>
     874                  value. (That is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length,
     875                  the entire entity-body is used.
     876               </p>
     877               <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
     878                  length of the entity-body, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is
     879                  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 status of 416 (Requested range not satisfiable). Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a status of 206 (Partial Content) containing the satisfiable ranges of the entity-body.
     880               </p>
     881               <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
     882               <ul>
     883                  <li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li>
     884                  <li>The second 500 bytes (byte offsets 500-999, inclusive): bytes=500-999</li>
     885                  <li>The final 500 bytes (byte offsets 9500-9999, inclusive): bytes=-500</li>
     886                  <li>Or bytes=9500-</li>
     887                  <li>The first and last bytes only (bytes 0 and 9999): bytes=0-0,-1</li>
     888                  <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): <br> bytes=500-600,601-999<br> bytes=500-700,601-999
     889                  </li>
     890               </ul>
     891            </div>
     892            <div id="range.retrieval.requests">
     893               <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>
     894               <p id="rfc.section.5.4.2.p.1">HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies
     895                  to the entity returned as the result of the request:
     896               </p>
     897               <div id="rfc.figure.u.17"></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>
    858898  <a href="#range.retrieval.requests" class="smpl">Range-v</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a>
    859899          / <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a>
    860900  <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a> = 1*<a href="#notation" class="smpl">CHAR</a>
    861901</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,
    862          since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
    863          entities.
    864       </p>
    865       <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 entity: </p>
    866       <ul>
    867          <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
    868             words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
    869          </li>
    870          <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
    871             one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
    872             is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
    873          </li>
    874       </ul>
    875       <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.2" title="If-Range">Section&nbsp;5.3</a>) in addition to the Range header.
    876       </p>
    877       <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
    878          entity 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.
    879       </p>
    880       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    881       <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>
    882       <p id="rfc.section.6.1.p.1">The Message Header 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; should 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>):
    883       </p>
    884       <div id="rfc.table.1">
    885          <div id="iana.header.registration.table"></div>
    886          <table class="tt full left" cellpadding="3" cellspacing="0">
    887             <thead>
    888                <tr>
    889                   <th>Header Field Name</th>
    890                   <th>Protocol</th>
    891                   <th>Status</th>
    892                   <th>Reference</th>
    893                </tr>
    894             </thead>
    895             <tbody>
    896                <tr>
    897                   <td class="left">Accept-Ranges</td>
    898                   <td class="left">http</td>
    899                   <td class="left">standard</td>
    900                   <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
    901                   </td>
    902                </tr>
    903                <tr>
    904                   <td class="left">Content-Range</td>
    905                   <td class="left">http</td>
    906                   <td class="left">standard</td>
    907                   <td class="left"> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
    908                   </td>
    909                </tr>
    910                <tr>
    911                   <td class="left">If-Range</td>
    912                   <td class="left">http</td>
    913                   <td class="left">standard</td>
    914                   <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section&nbsp;5.3</a>
    915                   </td>
    916                </tr>
    917                <tr>
    918                   <td class="left">Range</td>
    919                   <td class="left">http</td>
    920                   <td class="left">standard</td>
    921                   <td class="left"> <a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a>
    922                   </td>
    923                </tr>
    924             </tbody>
    925          </table>
     902                  since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
     903                  entities.
     904               </p>
     905               <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 entity: </p>
     906               <ul>
     907                  <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
     908                     words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
     909                  </li>
     910                  <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
     911                     one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
     912                     is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
     913                  </li>
     914               </ul>
     915               <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.2" title="If-Range">Section&nbsp;5.3</a>) in addition to the Range header.
     916               </p>
     917               <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
     918                  entity 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.
     919               </p>
     920            </div>
     921         </div>
    926922      </div>
    927       <p id="rfc.section.6.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    928       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    929       <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>.
    930       </p>
    931       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    932       <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
    933          from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
    934          Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
    935       </p>
     923      <div id="IANA.considerations">
     924         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     925         <div id="message.header.registration">
     926            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#message.header.registration">Message Header Registration</a></h2>
     927            <p id="rfc.section.6.1.p.1">The Message Header 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; should 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>):
     928            </p>
     929            <div id="rfc.table.1">
     930               <div id="iana.header.registration.table"></div>
     931               <table class="tt full left" cellpadding="3" cellspacing="0">
     932                  <thead>
     933                     <tr>
     934                        <th>Header Field Name</th>
     935                        <th>Protocol</th>
     936                        <th>Status</th>
     937                        <th>Reference</th>
     938                     </tr>
     939                  </thead>
     940                  <tbody>
     941                     <tr>
     942                        <td class="left">Accept-Ranges</td>
     943                        <td class="left">http</td>
     944                        <td class="left">standard</td>
     945                        <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
     946                        </td>
     947                     </tr>
     948                     <tr>
     949                        <td class="left">Content-Range</td>
     950                        <td class="left">http</td>
     951                        <td class="left">standard</td>
     952                        <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
     953                        </td>
     954                     </tr>
     955                     <tr>
     956                        <td class="left">If-Range</td>
     957                        <td class="left">http</td>
     958                        <td class="left">standard</td>
     959                        <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section&nbsp;5.3</a>
     960                        </td>
     961                     </tr>
     962                     <tr>
     963                        <td class="left">Range</td>
     964                        <td class="left">http</td>
     965                        <td class="left">standard</td>
     966                        <td class="left"><a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a>
     967                        </td>
     968                     </tr>
     969                  </tbody>
     970               </table>
     971            </div>
     972            <p id="rfc.section.6.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     973         </div>
     974      </div>
     975      <div id="security.considerations">
     976         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     977         <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>.
     978         </p>
     979      </div>
     980      <div id="ack">
     981         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     982         <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
     983            from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
     984            Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
     985         </p>
     986      </div>
    936987      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
    937988      </h1>
    938989      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
    939990      </h2>
    940       <table>             
     991      <table>
    941992         <tr>
    942993            <td class="reference"><b id="Part1">[Part1]</b></td>
    943             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-06">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-06 (work in progress), March&nbsp;2009.
     994            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-06">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-06 (work in progress), March&nbsp;2009.
    944995            </td>
    945996         </tr>
    946997         <tr>
    947998            <td class="reference"><b id="Part3">[Part3]</b></td>
    948             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-p3-payload-06">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-06 (work in progress), March&nbsp;2009.
     999            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-p3-payload-06">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-06 (work in progress), March&nbsp;2009.
    9491000            </td>
    9501001         </tr>
    9511002         <tr>
    9521003            <td class="reference"><b id="Part4">[Part4]</b></td>
    953             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-06">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-06 (work in progress), March&nbsp;2009.
     1004            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-06">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-06 (work in progress), March&nbsp;2009.
    9541005            </td>
    9551006         </tr>
    9561007         <tr>
    9571008            <td class="reference"><b id="Part6">[Part6]</b></td>
    958             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-p6-cache-06">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-06 (work in progress), March&nbsp;2009.
     1009            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-p6-cache-06">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-06 (work in progress), March&nbsp;2009.
    9591010            </td>
    9601011         </tr>
    9611012         <tr>
    9621013            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    963             <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.
     1014            <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.
    9641015            </td>
    9651016         </tr>
    9661017         <tr>
    9671018            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    968             <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.
     1019            <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.
    9691020            </td>
    9701021         </tr>
    9711022         <tr>
    9721023            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    973             <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.
     1024            <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.
    9741025            </td>
    9751026         </tr>
     
    9771028      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
    9781029      </h2>
    979       <table>     
     1030      <table>
    9801031         <tr>
    9811032            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    982             <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.
     1033            <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.
    9831034            </td>
    9841035         </tr>
    9851036         <tr>
    9861037            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    987             <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.
     1038            <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.
    9881039            </td>
    9891040         </tr>
    9901041         <tr>
    9911042            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
    992             <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.
     1043            <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.
    9931044            </td>
    9941045         </tr>
    9951046      </table>
    996       <div class="avoidbreak">
    997          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    998          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    999                (editor)
    1000                <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>
    1001          <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">One Laptop per Child</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@laptop.org"><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
    1002          <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>
    1003          <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>
    1004          <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>
    1005          <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>
    1006          <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>
    1007          <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
    1008                (editor)
    1009                <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>
    1010          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
    1011                (editor)
    1012                <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>
    1013       </div>
    1014       <div id="rfc.iref.m.1"></div>
    1015       <div id="rfc.iref.m.2"></div>
    1016       <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>
    1017       <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
    1018          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>.
    1019       </p>
    1020       <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
    1021          required boundary parameter specifies the boundary string used to separate each body-part.
    1022       </p>
    1023       <p id="rfc.section.A.p.3"> </p>
    1024       <dl>
    1025          <dt>Type name:</dt>
    1026          <dd>multipart</dd>
    1027          <dt>Subtype name:</dt>
    1028          <dd>byteranges</dd>
    1029          <dt>Required parameters:</dt>
    1030          <dd>boundary</dd>
    1031          <dt>Optional parameters:</dt>
    1032          <dd>none</dd>
    1033          <dt>Encoding considerations:</dt>
    1034          <dd>only "7bit", "8bit", or "binary" are permitted</dd>
    1035          <dt>Security considerations:</dt>
    1036          <dd>none</dd>
    1037          <dt>Interoperability considerations:</dt>
    1038          <dd>none</dd>
    1039          <dt>Published specification:</dt>
    1040          <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
    1041          </dd>
    1042          <dt>Applications that use this media type:</dt>
    1043          <dt>Additional information:</dt>
    1044          <dd>
    1045             <dl>
    1046                <dt>Magic number(s):</dt>
    1047                <dd>none</dd>
    1048                <dt>File extension(s):</dt>
    1049                <dd>none</dd>
    1050                <dt>Macintosh file type code(s):</dt>
    1051                <dd>none</dd>
    1052             </dl>
    1053          </dd>
    1054          <dt>Person and email address to contact for further information:</dt>
    1055          <dd>See Authors Section.</dd>
    1056          <dt>Intended usage:</dt>
    1057          <dd>COMMON</dd>
    1058          <dt>Restrictions on usage:</dt>
    1059          <dd>none</dd>
    1060          <dt>Author/Change controller:</dt>
    1061          <dd>IESG</dd>
    1062       </dl>
    1063       <div id="rfc.figure.u.18"></div>
    1064       <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
     1047      <div id="internet.media.type.multipart.byteranges">
     1048         <div id="rfc.iref.m.1"></div>
     1049         <div id="rfc.iref.m.2"></div>
     1050         <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>
     1051         <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
     1052            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>.
     1053         </p>
     1054         <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
     1055            required boundary parameter specifies the boundary string used to separate each body-part.
     1056         </p>
     1057         <p id="rfc.section.A.p.3"></p>
     1058         <dl>
     1059            <dt>Type name:</dt>
     1060            <dd>multipart</dd>
     1061            <dt>Subtype name:</dt>
     1062            <dd>byteranges</dd>
     1063            <dt>Required parameters:</dt>
     1064            <dd>boundary</dd>
     1065            <dt>Optional parameters:</dt>
     1066            <dd>none</dd>
     1067            <dt>Encoding considerations:</dt>
     1068            <dd>only "7bit", "8bit", or "binary" are permitted</dd>
     1069            <dt>Security considerations:</dt>
     1070            <dd>none</dd>
     1071            <dt>Interoperability considerations:</dt>
     1072            <dd>none</dd>
     1073            <dt>Published specification:</dt>
     1074            <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
     1075            </dd>
     1076            <dt>Applications that use this media type:</dt>
     1077            <dt>Additional information:</dt>
     1078            <dd>
     1079               <dl>
     1080                  <dt>Magic number(s):</dt>
     1081                  <dd>none</dd>
     1082                  <dt>File extension(s):</dt>
     1083                  <dd>none</dd>
     1084                  <dt>Macintosh file type code(s):</dt>
     1085                  <dd>none</dd>
     1086               </dl>
     1087            </dd>
     1088            <dt>Person and email address to contact for further information:</dt>
     1089            <dd>See Authors Section.</dd>
     1090            <dt>Intended usage:</dt>
     1091            <dd>COMMON</dd>
     1092            <dt>Restrictions on usage:</dt>
     1093            <dd>none</dd>
     1094            <dt>Author/Change controller:</dt>
     1095            <dd>IESG</dd>
     1096         </dl>
     1097         <div id="rfc.figure.u.18"></div>
     1098         <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
    10651099  Date: Wed, 15 Nov 1995 06:25:24 GMT
    10661100  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    10791113  --THIS_STRING_SEPARATES--
    10801114</pre><p id="rfc.section.A.p.5">Notes: </p>
    1081       <ol>
    1082          <li>Additional CRLFs may precede the first boundary string in the entity.</li>
    1083          <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.
    1084          </li>
    1085          <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.
    1086          </li>
    1087       </ol>
    1088       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    1089       <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
    1090       <p id="rfc.section.B.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
    1091          for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
    1092          computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
    1093       </p>
    1094       <p id="rfc.section.B.1.p.2">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving
    1095          a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length
    1096          of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">Section&nbsp;5.2</a>)
    1097       </p>
    1098       <p id="rfc.section.B.1.p.3">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send
    1099          needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">3.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">5.3</a>)
    1100       </p>
    1101       <p id="rfc.section.B.1.p.4">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document.
    1102          The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside
    1103          of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">3.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.7" title="Content-Range">5.2</a>)
    1104       </p>
    1105       <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    1106       <p id="rfc.section.B.2.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>)
    1107       </p>
    1108       <p id="rfc.section.B.2.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>)
    1109       </p>
    1110       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1111       <div id="rfc.figure.u.19"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
     1115         <ol>
     1116            <li>Additional CRLFs may precede the first boundary string in the entity.</li>
     1117            <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.
     1118            </li>
     1119            <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.
     1120            </li>
     1121         </ol>
     1122      </div>
     1123      <div id="compatibility">
     1124         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
     1125         <div id="changes.from.rfc.2068">
     1126            <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
     1127            <p id="rfc.section.B.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
     1128               for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
     1129               computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
     1130            </p>
     1131            <p id="rfc.section.B.1.p.2">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving
     1132               a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length
     1133               of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">Section&nbsp;5.2</a>)
     1134            </p>
     1135            <p id="rfc.section.B.1.p.3">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send
     1136               needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">3.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">5.3</a>)
     1137            </p>
     1138            <p id="rfc.section.B.1.p.4">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document.
     1139               The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside
     1140               of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">3.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.7" title="Content-Range">5.2</a>)
     1141            </p>
     1142         </div>
     1143         <div id="changes.from.rfc.2616">
     1144            <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     1145            <p id="rfc.section.B.2.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>)
     1146            </p>
     1147            <p id="rfc.section.B.2.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>)
     1148            </p>
     1149         </div>
     1150      </div>
     1151      <div id="collected.abnf">
     1152         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     1153         <div id="rfc.figure.u.19"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
    11121154<a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> = acceptable-ranges
    11131155
     
    11621204
    11631205
    1164 </pre> <div id="rfc.figure.u.20"></div>
    1165       <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
     1206</pre><div id="rfc.figure.u.20"></div>
     1207         <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
    11661208; Content-Range defined but not used
    11671209; If-Range defined but not used
    11681210; Range defined but not used
    1169 </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>
    1170       <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
    1171       </h2>
    1172       <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>.
    1173       </p>
    1174       <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
    1175       </h2>
    1176       <p id="rfc.section.D.2.p.1">Closed issues: </p>
    1177       <ul>
    1178          <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;)
    1179          </li>
    1180          <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"
    1181          </li>
    1182          <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"
    1183          </li>
    1184       </ul>
    1185       <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
    1186       </h2>
    1187       <p id="rfc.section.D.3.p.1">Closed issues: </p>
    1188       <ul>
    1189          <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"
    1190          </li>
    1191       </ul>
    1192       <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;):
    1193       </p>
    1194       <ul>
    1195          <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    1196       </ul>
    1197       <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>
    1198       <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;):
    1199       </p>
    1200       <ul>
    1201          <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
    1202       </ul>
    1203       <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>
    1204       <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>
    1205       <p id="rfc.section.D.6.p.1">Closed issues: </p>
    1206       <ul>
    1207          <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"
    1208          </li>
    1209       </ul>
    1210       <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;):
    1211       </p>
    1212       <ul>
    1213          <li>Use "/" instead of "|" for alternatives.</li>
    1214          <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
    1215          <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
    1216       </ul>
    1217       <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>
    1218       <p id="rfc.section.D.7.p.1">Closed issues: </p>
    1219       <ul>
    1220          <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"
    1221          </li>
    1222       </ul>
    1223       <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;):
    1224       </p>
    1225       <ul>
    1226          <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
    1227       </ul>
    1228       <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;):
    1229       </p>
    1230       <ul>
    1231          <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    1232       </ul>
     1211</pre></div>
     1212      <div id="change.log">
     1213         <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>
     1214         <div>
     1215            <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
     1216            </h2>
     1217            <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>.
     1218            </p>
     1219         </div>
     1220         <div>
     1221            <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
     1222            </h2>
     1223            <p id="rfc.section.D.2.p.1">Closed issues: </p>
     1224            <ul>
     1225               <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;)
     1226               </li>
     1227               <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"
     1228               </li>
     1229               <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"
     1230               </li>
     1231            </ul>
     1232         </div>
     1233         <div>
     1234            <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
     1235            </h2>
     1236            <p id="rfc.section.D.3.p.1">Closed issues: </p>
     1237            <ul>
     1238               <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"
     1239               </li>
     1240            </ul>
     1241            <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;):
     1242            </p>
     1243            <ul>
     1244               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
     1245            </ul>
     1246         </div>
     1247         <div id="changes.since.02">
     1248            <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>
     1249            <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;):
     1250            </p>
     1251            <ul>
     1252               <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
     1253            </ul>
     1254         </div>
     1255         <div id="changes.since.03">
     1256            <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>
     1257         </div>
     1258         <div id="changes.since.04">
     1259            <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>
     1260            <p id="rfc.section.D.6.p.1">Closed issues: </p>
     1261            <ul>
     1262               <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"
     1263               </li>
     1264            </ul>
     1265            <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;):
     1266            </p>
     1267            <ul>
     1268               <li>Use "/" instead of "|" for alternatives.</li>
     1269               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
     1270               <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
     1271            </ul>
     1272         </div>
     1273         <div id="changes.since.05">
     1274            <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>
     1275            <p id="rfc.section.D.7.p.1">Closed issues: </p>
     1276            <ul>
     1277               <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"
     1278               </li>
     1279            </ul>
     1280            <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;):
     1281            </p>
     1282            <ul>
     1283               <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
     1284            </ul>
     1285            <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;):
     1286            </p>
     1287            <ul>
     1288               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
     1289            </ul>
     1290         </div>
     1291      </div>
    12331292      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    12341293      <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>
     
    12371296         <ul class="ind">
    12381297            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    1239                   <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">B.1</a>, <a href="#rfc.xref.status.206.2">B.2</a></li>
     1298                  <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">B.1</a>, <a href="#rfc.xref.status.206.2">B.2</a></li>
    12401299               </ul>
    12411300            </li>
    12421301            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    1243                   <li>416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.4"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">5.2</a>, <a href="#rfc.xref.status.416.2">B.1</a></li>
     1302                  <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">B.1</a></li>
    12441303               </ul>
    12451304            </li>
     
    13511410         </ul>
    13521411      </div>
     1412      <div class="avoidbreak">
     1413         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     1414         <p><b>Roy T. Fielding</b>
     1415            (editor)
     1416            <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>
     1417         <p><b>Jim Gettys</b><br>One Laptop per Child<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>EMail: <a href="mailto:jg@laptop.org">jg@laptop.org</a><br>URI: <a href="http://www.laptop.org/">http://www.laptop.org/</a></p>
     1418         <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>
     1419         <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>
     1420         <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>
     1421         <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>
     1422         <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>
     1423         <p><b>Yves Lafon</b>
     1424            (editor)
     1425            <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>
     1426         <p><b>Julian F. Reschke</b>
     1427            (editor)
     1428            <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>
     1429      </div>
    13531430   </body>
    13541431</html>
Note: See TracChangeset for help on using the changeset viewer.