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/01/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 {
     
    123124  border-spacing: 1px;
    124125  width: 95%;
    125   font-size: 10pt;
     126  font-size: 11pt;
    126127  color: white;
    127128}
     
    131132td.topnowrap {
    132133  vertical-align: top;
    133   white-space: nowrap; 
     134  white-space: nowrap;
    134135}
    135136table.header td {
     
    151152  list-style: none;
    152153  margin-left: 1.5em;
    153   margin-right: 0em;
    154154  padding-left: 0em;
    155155}
     
    157157  line-height: 150%;
    158158  font-weight: bold;
    159   font-size: 10pt;
    160159  margin-left: 0em;
    161   margin-right: 0em;
    162160}
    163161ul.toc li li {
    164162  line-height: normal;
    165163  font-weight: normal;
    166   font-size: 9pt;
     164  font-size: 10pt;
    167165  margin-left: 0em;
    168   margin-right: 0em;
    169166}
    170167li.excluded {
     
    173170ul p {
    174171  margin-left: 0em;
     172}
     173.title, .filename, h1, h2, h3, h4 {
     174  font-family: candara, helvetica, arial, sans-serif;
     175}
     176samp, tt, code, pre {
     177  font: consolas, monospace;
    175178}
    176179ul.ind, ul.ind ul {
    177180  list-style: none;
    178181  margin-left: 1.5em;
    179   margin-right: 0em;
    180182  padding-left: 0em;
    181183  page-break-before: avoid;
     
    185187  line-height: 200%;
    186188  margin-left: 0em;
    187   margin-right: 0em;
    188189}
    189190ul.ind li li {
     
    191192  line-height: 150%;
    192193  margin-left: 0em;
    193   margin-right: 0em;
    194194}
    195195.avoidbreak {
     
    215215  font-weight: bold;
    216216  text-align: center;
    217   font-size: 9pt;
     217  font-size: 10pt;
    218218}
    219219.filename {
    220220  color: #333333;
     221  font-size: 75%;
    221222  font-weight: bold;
    222   font-size: 12pt;
    223223  line-height: 21pt;
    224224  text-align: center;
     
    227227  font-weight: bold;
    228228}
    229 .hidden {
    230   display: none;
    231 }
    232229.left {
    233230  text-align: left;
     
    237234}
    238235.title {
    239   color: #990000;
    240   font-size: 18pt;
     236  color: green;
     237  font-size: 150%;
    241238  line-height: 18pt;
    242239  font-weight: bold;
     
    244241  margin-top: 36pt;
    245242}
    246 .vcardline {
    247   display: block;
    248 }
    249243.warning {
    250   font-size: 14pt;
     244  font-size: 130%;
    251245  background-color: yellow;
    252246}
     
    257251    display: none;
    258252  }
    259  
     253
    260254  a {
    261255    color: black;
     
    272266    background-color: white;
    273267    vertical-align: top;
    274     font-size: 12pt;
    275   }
    276 
    277   ul.toc a::after {
     268    font-size: 110%;
     269  }
     270
     271  ul.toc a:nth-child(2)::after {
    278272    content: leader('.') target-counter(attr(href), page);
    279273  }
    280  
     274
    281275  ul.ind li li a {
    282276    content: target-counter(attr(href), page);
    283277  }
    284  
     278
    285279  .print2col {
    286280    column-count: 2;
     
    292286@page {
    293287  @top-left {
    294        content: "Internet-Draft"; 
    295   } 
     288       content: "Internet-Draft";
     289  }
    296290  @top-right {
    297        content: "January 2008"; 
    298   } 
     291       content: "January 2008";
     292  }
    299293  @top-center {
    300        content: "HTTP/1.1, Part 5"; 
    301   } 
     294       content: "HTTP/1.1, Part 5";
     295  }
    302296  @bottom-left {
    303        content: "Fielding, et al."; 
    304   } 
     297       content: "Fielding, et al.";
     298  }
    305299  @bottom-center {
    306        content: "Standards Track";
    307   } 
     300       content: "Expires July 15, 2008";
     301  }
    308302  @bottom-right {
    309        content: "[Page " counter(page) "]"; 
    310   } 
    311 }
    312 
    313 @page:first { 
     303       content: "[Page " counter(page) "]";
     304  }
     305}
     306
     307@page:first {
    314308    @top-left {
    315309      content: normal;
     
    338332      <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B">
    339333      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    340       <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/">
     334      <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/">
    341335      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    342336      <meta name="dct.creator" content="Fielding, R.">
     
    367361            </tr>
    368362            <tr>
    369                <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     363               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    370364               </td>
    371365               <td class="right">J. Gettys</td>
     
    438432      </table>
    439433      <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-01</span></p>
    440       <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    441       <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
    442          is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
    443          6 of BCP 79.
    444       </p>
    445       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
    446          that other groups may also distribute working documents as Internet-Drafts.
    447       </p>
    448       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    449          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    450          in progress”.
    451       </p>
    452       <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>.
    453       </p>
    454       <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>.
    455       </p>
    456       <p>This Internet-Draft will expire on July 15, 2008.</p>
    457       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
     434      <div id="rfc.status">
     435         <h1><a href="#rfc.status">Status of this Memo</a></h1>
     436         <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
     437            is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
     438            6 of BCP 79.
     439         </p>
     440         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
     441            that other groups may also distribute working documents as Internet-Drafts.
     442         </p>
     443         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     444            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     445            in progress”.
     446         </p>
     447         <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>.
     448         </p>
     449         <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>.
     450         </p>
     451         <p>This Internet-Draft will expire on July 15, 2008.</p>
     452      </div>
     453      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    458454      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    459455         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
    460456         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
    461457         5 defines range-specific requests and the rules for constructing and combining responses to those requests.
    462       </p> 
    463       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
     458      </p>
     459      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    464460      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    465461         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
    466       </p> 
     462      </p>
    467463      <p>This draft incorporates those issue resolutions that were either collected in the original RFC2616 errata list (&lt;<a href="http://purl.org/NET/http-errata">http://purl.org/NET/http-errata</a>&gt;), or which were agreed upon on the mailing list between October 2006 and November 2007 (as published in "draft-lafon-rfc2616bis-03").
    468       </p> 
     464      </p>
    469465      <hr class="noprint">
    470466      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    471467      <ul class="toc">
    472          <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    473                <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     468         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     469               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    474470            </ul>
    475471         </li>
    476          <li>2.&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
    477          <li>3.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul>
    478                <li>3.1&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    479                <li>3.2&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
     472         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
     473         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul>
     474               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
     475               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
    480476            </ul>
    481477         </li>
    482          <li>4.&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Byte Ranges</a></li>
    483          <li>5.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
    484                <li>5.1&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
    485                <li>5.2&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
    486                <li>5.3&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
    487                <li>5.4&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
    488                      <li>5.4.1&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
    489                      <li>5.4.2&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
     478         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Byte Ranges</a></li>
     479         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     480               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
     481               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
     482               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
     483               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
     484                     <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
     485                     <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>
    490486                  </ul>
    491487               </li>
    492488            </ul>
    493489         </li>
    494          <li>6.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
    495          <li>7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
    496          <li>8.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    497          <li>9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    498                <li>9.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    499                <li>9.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     490         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
     491         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
     492         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     493         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     494               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     495               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    500496            </ul>
    501497         </li>
    502          <li><a href="#rfc.authors">Authors' Addresses</a></li>
    503          <li>A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
    504          <li>B.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
    505                <li>B.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
    506                <li>B.2&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     498         <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>
     499         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
     500               <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>
     501               <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>
    507502            </ul>
    508503         </li>
    509          <li>C.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C">Change Log (to be removed by RFC Editor before publication)</a><ul>
    510                <li>C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
    511                <li>C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p5-range-00</a></li>
     504         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C">Change Log (to be removed by RFC Editor before publication)</a><ul>
     505               <li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
     506               <li><a href="#rfc.section.C.2">C.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p5-range-00</a></li>
    512507            </ul>
    513508         </li>
    514509         <li><a href="#rfc.index">Index</a></li>
     510         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    515511         <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    516512      </ul>
    517       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    518       <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
    519          has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
    520          rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
    521          request only a subset of a larger representation, such as a single page of a very large document or only part of an image
    522          to be rendered by a device with limited local storage.
    523       </p>
    524       <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
    525          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
    526          request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
    527          full responses by intermediate caches that might not implement the feature.
    528       </p>
    529       <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
    530          requests for byte ranges.
    531       </p>
    532       <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>
    533       <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"
    534          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>.
    535       </p>
    536       <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."
    537       </p>
    538       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
    539       <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
    540          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.
    541       </p>
    542       <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  range-unit       = bytes-unit | other-range-unit
     513      <div id="introduction">
     514         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     515         <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
     516            has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
     517            rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
     518            request only a subset of a larger representation, such as a single page of a very large document or only part of an image
     519            to be rendered by a device with limited local storage.
     520         </p>
     521         <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
     522            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
     523            request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
     524            full responses by intermediate caches that might not implement the feature.
     525         </p>
     526         <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
     527            requests for byte ranges.
     528         </p>
     529         <div id="intro.requirements">
     530            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     531            <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"
     532               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>.
     533            </p>
     534            <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."
     535            </p>
     536         </div>
     537      </div>
     538      <div id="range.units">
     539         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#range.units">Range Units</a></h1>
     540         <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
     541            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.
     542         </p>
     543         <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  range-unit       = bytes-unit | other-range-unit
    543544  bytes-unit       = "bytes"
    544545  other-range-unit = token
    545546</pre><p id="rfc.section.2.p.3">The only range unit defined by HTTP/1.1 is "bytes". HTTP/1.1 implementations <em class="bcp14">MAY</em> ignore ranges specified using other units.
    546       </p>
    547       <p id="rfc.section.2.p.4">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges.</p>
    548       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
    549       </h1>
    550       <div id="rfc.iref.3"></div>
    551       <div id="rfc.iref.s.1"></div>
    552       <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>
    553       <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.2" 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.
    554       </p>
    555       <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
    556       </p>
    557       <ul>
    558          <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
    559             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.
    560          </li>
    561          <li>Date</li>
    562          <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
    563          <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
    564             variant
    565          </li>
    566       </ul>
    567       <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.
    568       </p>
    569       <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 Byte Ranges">Section&nbsp;4</a>.
    570       </p>
    571       <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.
    572       </p>
    573       <div id="rfc.iref.4"></div>
    574       <div id="rfc.iref.s.2"></div>
    575       <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>
    576       <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.3" title="Range">Section&nbsp;5.4</a>), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request
    577          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
    578          values were greater than the current length of the selected resource.)
    579       </p>
    580       <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.
    581       </p>
    582       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Byte Ranges</a></h1>
    583       <p id="rfc.section.4.p.1">A response might transfer only a subrange of the bytes of an entity-body, either because the request included one or more
    584          Range specifications, or because a connection was broken prematurely. After several such transfers, a cache might have received
    585          several ranges of the same entity-body.
    586       </p>
    587       <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
    588          cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
    589       </p>
    590       <ul>
    591          <li>Both the incoming response and the cache entry have a cache validator.</li>
    592          <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.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    593          </li>
    594       </ul>
    595       <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
    596          response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
    597       </p>
    598       <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>
    599       <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>
    600       <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
    601          receives the entity.
    602       </p>
    603       <div id="rfc.iref.a.1"></div>
    604       <div id="rfc.iref.h.1"></div>
    605       <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>
    606       <p id="rfc.section.5.1.p.1">The Accept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource:</p>
    607       <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  Accept-Ranges     = "Accept-Ranges" ":" acceptable-ranges
     547         </p>
     548         <p id="rfc.section.2.p.4">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges.</p>
     549      </div>
     550      <div>
     551         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
     552         </h1>
     553         <div id="status.206">
     554            <div id="rfc.iref.2.1"></div>
     555            <div id="rfc.iref.s.1"></div>
     556            <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>
     557            <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.2" 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.
     558            </p>
     559            <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
     560            </p>
     561            <ul>
     562               <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
     563                  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.
     564               </li>
     565               <li>Date</li>
     566               <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
     567               <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
     568                  variant
     569               </li>
     570            </ul>
     571            <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.
     572            </p>
     573            <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 Byte Ranges">Section&nbsp;4</a>.
     574            </p>
     575            <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.
     576            </p>
     577         </div>
     578         <div id="status.416">
     579            <div id="rfc.iref.4.1"></div>
     580            <div id="rfc.iref.s.2"></div>
     581            <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>
     582            <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.3" title="Range">Section&nbsp;5.4</a>), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request
     583               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
     584               values were greater than the current length of the selected resource.)
     585            </p>
     586            <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.
     587            </p>
     588         </div>
     589      </div>
     590      <div id="combining.byte.ranges">
     591         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#combining.byte.ranges">Combining Byte Ranges</a></h1>
     592         <p id="rfc.section.4.p.1">A response might transfer only a subrange of the bytes of an entity-body, either because the request included one or more
     593            Range specifications, or because a connection was broken prematurely. After several such transfers, a cache might have received
     594            several ranges of the same entity-body.
     595         </p>
     596         <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
     597            cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
     598         </p>
     599         <ul>
     600            <li>Both the incoming response and the cache entry have a cache validator.</li>
     601            <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.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
     602            </li>
     603         </ul>
     604         <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
     605            response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
     606         </p>
     607      </div>
     608      <div id="header.fields">
     609         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     610         <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>
     611         <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
     612            receives the entity.
     613         </p>
     614         <div id="header.accept-ranges">
     615            <div id="rfc.iref.a.1"></div>
     616            <div id="rfc.iref.h.1"></div>
     617            <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>
     618            <p id="rfc.section.5.1.p.1">The Accept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource:</p>
     619            <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  Accept-Ranges     = "Accept-Ranges" ":" acceptable-ranges
    608620  acceptable-ranges = 1#range-unit | "none"
    609621</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
    610       </p>
    611       <div id="rfc.figure.u.3"></div><pre class="text">       Accept-Ranges: bytes
     622            </p>
     623            <div id="rfc.figure.u.3"></div><pre class="text">       Accept-Ranges: bytes
    612624</pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate byte-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>.
    613       </p>
    614       <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
    615       </p>
    616       <div id="rfc.figure.u.4"></div><pre class="text">       Accept-Ranges: none
     625            </p>
     626            <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
     627            </p>
     628            <div id="rfc.figure.u.4"></div><pre class="text">       Accept-Ranges: none
    617629</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
    618       <div id="rfc.iref.c.1"></div>
    619       <div id="rfc.iref.h.2"></div>
    620       <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>
    621       <p id="rfc.section.5.2.p.1">The Content-Range entity-header is sent with a partial entity-body to specify where in the full entity-body the partial body
    622          should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
    623       </p>
    624       <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  Content-Range = "Content-Range" ":" content-range-spec
     630         </div>
     631         <div id="header.content-range">
     632            <div id="rfc.iref.c.1"></div>
     633            <div id="rfc.iref.h.2"></div>
     634            <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>
     635            <p id="rfc.section.5.2.p.1">The Content-Range entity-header is sent with a partial entity-body to specify where in the full entity-body the partial body
     636               should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
     637            </p>
     638            <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  Content-Range = "Content-Range" ":" content-range-spec
    625639 
    626640  content-range-spec      = byte-content-range-spec
     
    633647  instance-length           = 1*DIGIT
    634648</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 "*"
    635          character means that the instance-length is unknown at the time when the response was generated.
    636       </p>
    637       <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.
    638       </p>
    639       <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
    640          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.
    641       </p>
    642       <p id="rfc.section.5.2.p.6">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
    643          selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
    644       </p>
    645       <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>
    646       <ul>
    647          <li>The first 500 bytes:
    648             <div id="rfc.figure.u.6"></div><pre class="text">   bytes 0-499/1234
     649               character means that the instance-length is unknown at the time when the response was generated.
     650            </p>
     651            <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.
     652            </p>
     653            <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
     654               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.
     655            </p>
     656            <p id="rfc.section.5.2.p.6">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
     657               selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
     658            </p>
     659            <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>
     660            <ul>
     661               <li>The first 500 bytes: <span id="rfc.figure.u.6"></span><pre class="text">   bytes 0-499/1234
    649662</pre> </li>
    650          <li>The second 500 bytes:
    651             <div id="rfc.figure.u.7"></div><pre class="text">   bytes 500-999/1234
     663               <li>The second 500 bytes: <span id="rfc.figure.u.7"></span><pre class="text">   bytes 500-999/1234
    652664</pre> </li>
    653          <li>All except for the first 500 bytes:
    654             <div id="rfc.figure.u.8"></div><pre class="text">   bytes 500-1233/1234
     665               <li>All except for the first 500 bytes: <span id="rfc.figure.u.8"></span><pre class="text">   bytes 500-1233/1234
    655666</pre> </li>
    656          <li>The last 500 bytes:
    657             <div id="rfc.figure.u.9"></div><pre class="text">   bytes 734-1233/1234
     667               <li>The last 500 bytes: <span id="rfc.figure.u.9"></span><pre class="text">   bytes 734-1233/1234
    658668</pre> </li>
    659       </ul>
    660       <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
    661          a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
    662          a Content-Length header showing the number of bytes actually transferred. For example,
    663       </p>
    664       <div id="rfc.figure.u.10"></div><pre class="text">    HTTP/1.1 206 Partial Content
     669            </ul>
     670            <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
     671               a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
     672               a Content-Length header showing the number of bytes actually transferred. For example,
     673            </p>
     674            <div id="rfc.figure.u.10"></div><pre class="text">    HTTP/1.1 206 Partial Content
    665675    Date: Wed, 15 Nov 1995 06:25:24 GMT
    666676    Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    669679    Content-Type: image/gif
    670680</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
    671          ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
    672          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.
    673       </p>
    674       <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 byte-ranges in a single request.
    675       </p>
    676       <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.
    677       </p>
    678       <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
    679          the full entity).
    680       </p>
    681       <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
    682          field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
    683          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>).
    684       </p>
    685       <ul class="empty">
    686          <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
    687             an unsatisfiable Range request-header, since not all servers implement this request-header.
    688          </li>
    689       </ul>
    690       <div id="rfc.iref.i.1"></div>
    691       <div id="rfc.iref.h.3"></div>
    692       <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>
    693       <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
    694          cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.)
    695          However, if the condition fails because the entity has been modified, the client would then have to make a second request
    696          to obtain the entire current entity-body.
    697       </p>
    698       <p id="rfc.section.5.3.p.2">The If-Range header allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity is unchanged,
    699          send me the part(s) that I am missing; otherwise, send me the entire new entity'.
    700       </p>
    701       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  If-Range = "If-Range" ":" ( entity-tag | HTTP-date )
     681               ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
     682               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.
     683            </p>
     684            <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 byte-ranges in a single request.
     685            </p>
     686            <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.
     687            </p>
     688            <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
     689               the full entity).
     690            </p>
     691            <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
     692               field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
     693               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>).
     694            </p>
     695            <ul class="empty">
     696               <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
     697                  an unsatisfiable Range request-header, since not all servers implement this request-header.
     698               </li>
     699            </ul>
     700         </div>
     701         <div id="header.if-range">
     702            <div id="rfc.iref.i.1"></div>
     703            <div id="rfc.iref.h.3"></div>
     704            <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>
     705            <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
     706               cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.)
     707               However, if the condition fails because the entity has been modified, the client would then have to make a second request
     708               to obtain the entire current entity-body.
     709            </p>
     710            <p id="rfc.section.5.3.p.2">The If-Range header allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity is unchanged,
     711               send me the part(s) that I am missing; otherwise, send me the entire new entity'.
     712            </p>
     713            <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  If-Range = "If-Range" ":" ( entity-tag | HTTP-date )
    702714</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
    703          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.
    704       </p>
    705       <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
    706          the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response.
    707       </p>
    708       <div id="rfc.iref.r.1"></div>
    709       <div id="rfc.iref.h.4"></div>
    710       <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>
    711       <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>
    712       <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
    713          for any HTTP entity. (However, not all clients and servers need to support byte-range operations.)
    714       </p>
    715       <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>
    716       <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.
    717       </p>
    718       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  ranges-specifier = byte-ranges-specifier
     715               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.
     716            </p>
     717            <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
     718               the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response.
     719            </p>
     720         </div>
     721         <div id="header.range">
     722            <div id="rfc.iref.r.1"></div>
     723            <div id="rfc.iref.h.4"></div>
     724            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.range">Range</a></h2>
     725            <div id="byte.ranges">
     726               <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>
     727               <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
     728                  for any HTTP entity. (However, not all clients and servers need to support byte-range operations.)
     729               </p>
     730               <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>
     731               <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.
     732               </p>
     733               <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  ranges-specifier = byte-ranges-specifier
    719734  byte-ranges-specifier = bytes-unit "=" byte-range-set
    720735  byte-range-set  = 1#( byte-range-spec | suffix-byte-range-spec )
     
    723738  last-byte-pos   = 1*DIGIT
    724739</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
    725          gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
    726          at zero.
    727       </p>
    728       <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
    729          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.
    730       </p>
    731       <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
    732          is taken to be equal to one less than the current length of the entity-body in bytes.
    733       </p>
    734       <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>
    735       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  suffix-byte-range-spec = "-" suffix-length
     740                  gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
     741                  at zero.
     742               </p>
     743               <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
     744                  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.
     745               </p>
     746               <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
     747                  is taken to be equal to one less than the current length of the entity-body in bytes.
     748               </p>
     749               <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>
     750               <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  suffix-byte-range-spec = "-" suffix-length
    736751  suffix-length = 1*DIGIT
    737752</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 suffix-length value. (That
    738          is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
    739          entire entity-body is used.
    740       </p>
    741       <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
    742          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
    743          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.
    744       </p>
    745       <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
    746       <ul>
    747          <li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li>
    748          <li>The second 500 bytes (byte offsets 500-999, inclusive): bytes=500-999</li>
    749          <li>The final 500 bytes (byte offsets 9500-9999, inclusive): bytes=-500</li>
    750          <li>Or bytes=9500-</li>
    751          <li>The first and last bytes only (bytes 0 and 9999): bytes=0-0,-1</li>
    752          <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
    753          </li>
    754       </ul>
    755       <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>
    756       <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
    757          to the entity returned as the result of the request:
    758       </p>
    759       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  Range = "Range" ":" ranges-specifier
     753                  is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
     754                  entire entity-body is used.
     755               </p>
     756               <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
     757                  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
     758                  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.
     759               </p>
     760               <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
     761               <ul>
     762                  <li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li>
     763                  <li>The second 500 bytes (byte offsets 500-999, inclusive): bytes=500-999</li>
     764                  <li>The final 500 bytes (byte offsets 9500-9999, inclusive): bytes=-500</li>
     765                  <li>Or bytes=9500-</li>
     766                  <li>The first and last bytes only (bytes 0 and 9999): bytes=0-0,-1</li>
     767                  <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
     768                  </li>
     769               </ul>
     770            </div>
     771            <div id="range.retrieval.requests">
     772               <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>
     773               <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
     774                  to the entity returned as the result of the request:
     775               </p>
     776               <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  Range = "Range" ":" ranges-specifier
    760777</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,
    761          since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
    762          entities.
    763       </p>
    764       <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>
    765       <ul>
    766          <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
    767             words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
    768          </li>
    769          <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
    770             one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
    771             is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
    772          </li>
    773       </ul>
    774       <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.
    775       </p>
    776       <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
    777          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.
    778       </p>
    779       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    780       <p id="rfc.section.6.p.1">TBD.</p>
    781       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    782       <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.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    783       </p>
    784       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
    785       <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
    786          from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
    787          Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
    788       </p>
     778                  since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
     779                  entities.
     780               </p>
     781               <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>
     782               <ul>
     783                  <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
     784                     words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
     785                  </li>
     786                  <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
     787                     one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
     788                     is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
     789                  </li>
     790               </ul>
     791               <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.
     792               </p>
     793               <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
     794                  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.
     795               </p>
     796            </div>
     797         </div>
     798      </div>
     799      <div id="IANA.considerations">
     800         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     801         <p id="rfc.section.6.p.1">TBD.</p>
     802      </div>
     803      <div id="security.considerations">
     804         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     805         <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.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     806         </p>
     807      </div>
     808      <div id="ack">
     809         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     810         <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
     811            from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
     812            Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
     813         </p>
     814      </div>
    789815      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
    790816      </h1>
    791817      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
    792818      </h2>
    793       <table>           
     819      <table>
    794820         <tr>
    795821            <td class="reference"><b id="Part1">[Part1]</b></td>
    796             <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-01">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-01 (work in progress), January&nbsp;2008.
     822            <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-01">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-01 (work in progress), January&nbsp;2008.
    797823            </td>
    798824         </tr>
    799825         <tr>
    800826            <td class="reference"><b id="Part3">[Part3]</b></td>
    801             <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-01">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-01 (work in progress), January&nbsp;2008.
     827            <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-01">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-01 (work in progress), January&nbsp;2008.
    802828            </td>
    803829         </tr>
    804830         <tr>
    805831            <td class="reference"><b id="Part4">[Part4]</b></td>
    806             <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-01">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-01 (work in progress), January&nbsp;2008.
     832            <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-01">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-01 (work in progress), January&nbsp;2008.
    807833            </td>
    808834         </tr>
    809835         <tr>
    810836            <td class="reference"><b id="Part6">[Part6]</b></td>
    811             <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-01">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-01 (work in progress), January&nbsp;2008.
     837            <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-01">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-01 (work in progress), January&nbsp;2008.
    812838            </td>
    813839         </tr>
    814840         <tr>
    815841            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    816             <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.
     842            <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.
    817843            </td>
    818844         </tr>
    819845         <tr>
    820846            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    821             <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.
     847            <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.
    822848            </td>
    823849         </tr>
     
    825851      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
    826852      </h2>
    827       <table> 
     853      <table>
    828854         <tr>
    829855            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    830             <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.
     856            <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.
    831857            </td>
    832858         </tr>
    833859      </table>
    834       <div class="avoidbreak">
    835          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    836          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    837                (editor)
    838                <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>
    839          <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>
    840          <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>
    841          <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>
    842          <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>
    843          <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>
    844          <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>
    845          <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
    846                (editor)
    847                <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>
    848          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
    849                (editor)
    850                <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>
    851       </div>
    852       <div id="rfc.iref.m.1"></div>
    853       <div id="rfc.iref.m.2"></div>
    854       <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>
    855       <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
    856          non-overlapping ranges), these are transmitted as a multipart message-body. The media type for this purpose is called "multipart/byteranges".
    857       </p>
    858       <p id="rfc.section.A.p.2">The multipart/byteranges media type includes two or more parts, each with its own Content-Type and Content-Range fields. The
    859          required boundary parameter specifies the boundary string used to separate each body-part.
    860       </p>
    861       <p id="rfc.section.A.p.3"> </p>
    862       <dl>
    863          <dt>Media Type name:</dt>
    864          <dd>multipart</dd>
    865          <dt>Media subtype name:</dt>
    866          <dd>byteranges</dd>
    867          <dt>Required parameters:</dt>
    868          <dd>boundary</dd>
    869          <dt>Optional parameters:</dt>
    870          <dd>none</dd>
    871          <dt>Encoding considerations:</dt>
    872          <dd>only "7bit", "8bit", or "binary" are permitted</dd>
    873          <dt>Security considerations:</dt>
    874          <dd>none</dd>
    875       </dl>
    876       <div id="rfc.figure.u.15"></div>
    877       <p>For example:</p><pre class="text">   HTTP/1.1 206 Partial Content
     860      <div id="internet.media.type.multipart.byteranges">
     861         <div id="rfc.iref.m.1"></div>
     862         <div id="rfc.iref.m.2"></div>
     863         <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>
     864         <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
     865            non-overlapping ranges), these are transmitted as a multipart message-body. The media type for this purpose is called "multipart/byteranges".
     866         </p>
     867         <p id="rfc.section.A.p.2">The multipart/byteranges media type includes two or more parts, each with its own Content-Type and Content-Range fields. The
     868            required boundary parameter specifies the boundary string used to separate each body-part.
     869         </p>
     870         <p id="rfc.section.A.p.3"></p>
     871         <dl>
     872            <dt>Media Type name:</dt>
     873            <dd>multipart</dd>
     874            <dt>Media subtype name:</dt>
     875            <dd>byteranges</dd>
     876            <dt>Required parameters:</dt>
     877            <dd>boundary</dd>
     878            <dt>Optional parameters:</dt>
     879            <dd>none</dd>
     880            <dt>Encoding considerations:</dt>
     881            <dd>only "7bit", "8bit", or "binary" are permitted</dd>
     882            <dt>Security considerations:</dt>
     883            <dd>none</dd>
     884         </dl>
     885         <div id="rfc.figure.u.15"></div>
     886         <p>For example:</p><pre class="text">   HTTP/1.1 206 Partial Content
    878887   Date: Wed, 15 Nov 1995 06:25:24 GMT
    879888   Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
     
    892901   --THIS_STRING_SEPARATES--
    893902</pre><p id="rfc.section.A.p.5">Notes: </p>
    894       <ol>
    895          <li>Additional CRLFs may precede the first boundary string in the entity.</li>
    896          <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.1"><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.
    897          </li>
    898          <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.
    899          </li>
    900       </ol>
    901       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    902       <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>
    903       <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
    904          for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
    905          computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.2"><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>)
    906       </p>
    907       <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
    908          a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length
    909          of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>)
    910       </p>
    911       <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
    912          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.3" title="If-Range">5.3</a>)
    913       </p>
    914       <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.
    915          The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside
    916          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.6" title="Content-Range">5.2</a>)
    917       </p>
    918       <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>
    919       <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>)
    920       </p>
    921       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
    922       </h1>
    923       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
    924       </h2>
    925       <p id="rfc.section.C.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>.
    926       </p>
    927       <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
    928       </h2>
    929       <p id="rfc.section.C.2.p.1">Closed issues: </p>
    930       <ul>
    931          <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/18">http://www3.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;)
    932          </li>
    933          <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
    934          </li>
    935          <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
    936          </li>
    937       </ul>
     903         <ol>
     904            <li>Additional CRLFs may precede the first boundary string in the entity.</li>
     905            <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.1"><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.
     906            </li>
     907            <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.
     908            </li>
     909         </ol>
     910      </div>
     911      <div id="compatibility">
     912         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
     913         <div id="changes.from.rfc.2068">
     914            <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>
     915            <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
     916               for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
     917               computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.2"><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>)
     918            </p>
     919            <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
     920               a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length
     921               of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>)
     922            </p>
     923            <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
     924               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.3" title="If-Range">5.3</a>)
     925            </p>
     926            <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.
     927               The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside
     928               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.6" title="Content-Range">5.2</a>)
     929            </p>
     930         </div>
     931         <div id="changes.from.rfc.2616">
     932            <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>
     933            <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>)
     934            </p>
     935         </div>
     936      </div>
     937      <div>
     938         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
     939         </h1>
     940         <div>
     941            <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
     942            </h2>
     943            <p id="rfc.section.C.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>.
     944            </p>
     945         </div>
     946         <div>
     947            <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
     948            </h2>
     949            <p id="rfc.section.C.2.p.1">Closed issues: </p>
     950            <ul>
     951               <li>&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/18">http://www3.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;)
     952               </li>
     953               <li>&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
     954               </li>
     955               <li>&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
     956               </li>
     957            </ul>
     958         </div>
     959      </div>
    938960      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    939961      <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>
     
    942964         <ul class="ind">
    943965            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    944                   <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>
     966                  <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>
    945967               </ul>
    946968            </li>
    947969            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    948                   <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>
     970                  <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>
    949971               </ul>
    950972            </li>
     
    10381060         </ul>
    10391061      </div>
    1040       <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    1041       <p>Copyright © The IETF Trust (2008).</p>
    1042       <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
    1043          authors retain all their rights.
    1044       </p>
    1045       <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
    1046          HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
    1047          DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
    1048          WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
    1049       </p>
    1050       <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
    1051       <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
    1052          be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
    1053          license under such rights might or might not be available; nor does it represent that it has made any independent effort to
    1054          identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
    1055          BCP 79.
    1056       </p>
    1057       <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
    1058          of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
    1059          of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
    1060       </p>
    1061       <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
    1062          rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
    1063          at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
    1064       </p>
     1062      <div class="avoidbreak">
     1063         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     1064         <p><b>Roy T. Fielding</b>
     1065            (editor)
     1066            <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>
     1067         <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>
     1068         <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>
     1069         <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>
     1070         <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>
     1071         <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>
     1072         <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>
     1073         <p><b>Yves Lafon</b>
     1074            (editor)
     1075            <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>
     1076         <p><b>Julian F. Reschke</b>
     1077            (editor)
     1078            <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>
     1079      </div>
     1080      <div id="rfc.copyright">
     1081         <h1><a href="#rfc.copyright">Full Copyright Statement</a></h1>
     1082         <p>Copyright © The IETF Trust (2008).</p>
     1083         <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
     1084            authors retain all their rights.
     1085         </p>
     1086         <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
     1087            HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
     1088            DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
     1089            WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
     1090         </p>
     1091      </div>
     1092      <div id="rfc.ipr">
     1093         <h1><a href="#rfc.ipr">Intellectual Property</a></h1>
     1094         <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
     1095            be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
     1096            license under such rights might or might not be available; nor does it represent that it has made any independent effort to
     1097            identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
     1098            BCP 79.
     1099         </p>
     1100         <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
     1101            of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
     1102            of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
     1103         </p>
     1104         <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
     1105            rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
     1106            at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
     1107         </p>
     1108      </div>
    10651109   </body>
    10661110</html>
Note: See TracChangeset for help on using the changeset viewer.