source: draft-ietf-httpbis/latest/p5-range.html @ 1457

Last change on this file since 1457 was 1457, checked in by ylafon@…, 8 years ago

regen after [1456]

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 110.0 KB
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>HTTP/1.1, part 5: Range Requests and Partial Responses</title><style type="text/css" title="Xml2Rfc (sans serif)">
7a {
8  text-decoration: none;
10a.smpl {
11  color: black;
13a:hover {
14  text-decoration: underline;
16a:active {
17  text-decoration: underline;
19address {
20  margin-top: 1em;
21  margin-left: 2em;
22  font-style: normal;
24body {
25  color: black;
26  font-family: verdana, helvetica, arial, sans-serif;
27  font-size: 10pt;
29cite {
30  font-style: normal;
32div.note {
33  margin-left: 2em;
35dd {
36  margin-right: 2em;
38dl {
39  margin-left: 2em;
42ul.empty {
43  list-style-type: none;
45ul.empty li {
46  margin-top: .5em;
48dl p {
49  margin-left: 0em;
51dt {
52  margin-top: .5em;
54h1 {
55  font-size: 14pt;
56  line-height: 21pt;
57  page-break-after: avoid;
58} {
60  page-break-before: always;
62h1 a {
63  color: #333333;
65h2 {
66  font-size: 12pt;
67  line-height: 15pt;
68  page-break-after: avoid;
70h3, h4, h5, h6 {
71  font-size: 10pt;
72  page-break-after: avoid;
74h2 a, h3 a, h4 a, h5 a, h6 a {
75  color: black;
77img {
78  margin-left: 3em;
80li {
81  margin-left: 2em;
82  margin-right: 2em;
84ol {
85  margin-left: 2em;
86  margin-right: 2em;
87} {
89  list-style-type: lower-alpha;
90} {
92  list-style-type: upper-alpha;
94ol p {
95  margin-left: 0em;
97p {
98  margin-left: 2em;
99  margin-right: 2em;
101pre {
102  margin-left: 3em;
103  background-color: lightyellow;
104  padding: .25em;
106pre.text2 {
107  border-style: dotted;
108  border-width: 1px;
109  background-color: #f0f0f0;
110  width: 69em;
112pre.inline {
113  background-color: white;
114  padding: 0em;
116pre.text {
117  border-style: dotted;
118  border-width: 1px;
119  background-color: #f8f8f8;
120  width: 69em;
122pre.drawing {
123  border-style: solid;
124  border-width: 1px;
125  background-color: #f8f8f8;
126  padding: 2em;
128table {
129  margin-left: 2em;
130} {
132  vertical-align: top;
134table.full {
135  border-style: outset;
136  border-width: 1px;
138table.headers {
139  border-style: outset;
140  border-width: 1px;
141} td {
143  vertical-align: top;
145table.full td {
146  border-style: inset;
147  border-width: 1px;
148} th {
150  vertical-align: top;
152table.full th {
153  border-style: inset;
154  border-width: 1px;
156table.headers th {
157  border-style: none none inset none;
158  border-width: 1px;
160table.left {
161  margin-right: auto;
163table.right {
164  margin-left: auto;
165} {
167  margin-left: auto;
168  margin-right: auto;
170caption {
171  caption-side: bottom;
172  font-weight: bold;
173  font-size: 9pt;
174  margin-top: .5em;
177table.header {
178  border-spacing: 1px;
179  width: 95%;
180  font-size: 10pt;
181  color: white;
182} {
184  vertical-align: top;
186td.topnowrap {
187  vertical-align: top;
188  white-space: nowrap; 
190table.header td {
191  background-color: gray;
192  width: 50%;
194table.header a {
195  color: white;
197td.reference {
198  vertical-align: top;
199  white-space: nowrap;
200  padding-right: 1em;
202thead {
203  display:table-header-group;
205ul.toc, ul.toc ul {
206  list-style: none;
207  margin-left: 1.5em;
208  margin-right: 0em;
209  padding-left: 0em;
211ul.toc li {
212  line-height: 150%;
213  font-weight: bold;
214  font-size: 10pt;
215  margin-left: 0em;
216  margin-right: 0em;
218ul.toc li li {
219  line-height: normal;
220  font-weight: normal;
221  font-size: 9pt;
222  margin-left: 0em;
223  margin-right: 0em;
225li.excluded {
226  font-size: 0pt;
228ul p {
229  margin-left: 0em;
231ul.ind, ul.ind ul {
232  list-style: none;
233  margin-left: 1.5em;
234  margin-right: 0em;
235  padding-left: 0em;
236  page-break-before: avoid;
238ul.ind li {
239  font-weight: bold;
240  line-height: 200%;
241  margin-left: 0em;
242  margin-right: 0em;
244ul.ind li li {
245  font-weight: normal;
246  line-height: 150%;
247  margin-left: 0em;
248  margin-right: 0em;
250.avoidbreak {
251  page-break-inside: avoid;
253.bcp14 {
254  font-style: normal;
255  text-transform: lowercase;
256  font-variant: small-caps;
258.comment {
259  background-color: yellow;
260} {
262  text-align: center;
264.error {
265  color: red;
266  font-style: italic;
267  font-weight: bold;
269.figure {
270  font-weight: bold;
271  text-align: center;
272  font-size: 9pt;
274.filename {
275  color: #333333;
276  font-weight: bold;
277  font-size: 12pt;
278  line-height: 21pt;
279  text-align: center;
281.fn {
282  font-weight: bold;
284.hidden {
285  display: none;
287.left {
288  text-align: left;
290.right {
291  text-align: right;
293.title {
294  color: #990000;
295  font-size: 18pt;
296  line-height: 18pt;
297  font-weight: bold;
298  text-align: center;
299  margin-top: 36pt;
301.vcardline {
302  display: block;
304.warning {
305  font-size: 14pt;
306  background-color: yellow;
310@media print {
311  .noprint {
312    display: none;
313  }
315  a {
316    color: black;
317    text-decoration: none;
318  }
320  table.header {
321    width: 90%;
322  }
324  td.header {
325    width: 50%;
326    color: black;
327    background-color: white;
328    vertical-align: top;
329    font-size: 12pt;
330  }
332  ul.toc a::after {
333    content: leader('.') target-counter(attr(href), page);
334  }
336  ul.ind li li a {
337    content: target-counter(attr(href), page);
338  }
340  .print2col {
341    column-count: 2;
342    -moz-column-count: 2;
343    column-fill: auto;
344  }
347@page {
348  @top-left {
349       content: "Internet-Draft"; 
350  } 
351  @top-right {
352       content: "October 2011"; 
353  } 
354  @top-center {
355       content: "HTTP/1.1, Part 5"; 
356  } 
357  @bottom-left {
358       content: "Fielding, et al."; 
359  } 
360  @bottom-center {
361       content: "Expires April 29, 2012"; 
362  } 
363  @bottom-right {
364       content: "[Page " counter(page) "]"; 
365  } 
368@page:first { 
369    @top-left {
370      content: normal;
371    }
372    @top-right {
373      content: normal;
374    }
375    @top-center {
376      content: normal;
377    }
379</style><link rel="Contents" href="#rfc.toc">
380      <link rel="Author" href="#rfc.authors">
381      <link rel="Copyright" href="#rfc.copyrightnotice">
382      <link rel="Index" href="#rfc.index">
383      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
384      <link rel="Chapter" title="2 Range Units" href="#rfc.section.2">
385      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
386      <link rel="Chapter" title="4 Combining Ranges" href="#rfc.section.4">
387      <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5">
388      <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6">
389      <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7">
390      <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8">
391      <link rel="Chapter" href="#rfc.section.9" title="9 References">
392      <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
393      <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B">
394      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
395      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
396      <meta name="generator" content=", Revision 1.556, 2011-08-28 20:30:48, XSLT vendor: SAXON 8.9 from Saxonica">
397      <link rel="schema.dct" href="">
398      <meta name="dct.creator" content="Fielding, R.">
399      <meta name="dct.creator" content="Gettys, J.">
400      <meta name="dct.creator" content="Mogul, J.">
401      <meta name="dct.creator" content="Frystyk, H.">
402      <meta name="dct.creator" content="Masinter, L.">
403      <meta name="dct.creator" content="Leach, P.">
404      <meta name="dct.creator" content="Berners-Lee, T.">
405      <meta name="dct.creator" content="Lafon, Y.">
406      <meta name="dct.creator" content="Reschke, J. F.">
407      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
408      <meta name="dct.issued" scheme="ISO8601" content="2011-10-27">
409      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
410      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">
411      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">
412   </head>
413   <body>
414      <table class="header">
415         <tbody>
416            <tr>
417               <td class="left">HTTPbis Working Group</td>
418               <td class="right">R. Fielding, Editor</td>
419            </tr>
420            <tr>
421               <td class="left">Internet-Draft</td>
422               <td class="right">Adobe</td>
423            </tr>
424            <tr>
425               <td class="left">Obsoletes: <a href="">2616</a> (if approved)
426               </td>
427               <td class="right">J. Gettys</td>
428            </tr>
429            <tr>
430               <td class="left">Intended status: Standards Track</td>
431               <td class="right">Alcatel-Lucent</td>
432            </tr>
433            <tr>
434               <td class="left">Expires: April 29, 2012</td>
435               <td class="right">J. Mogul</td>
436            </tr>
437            <tr>
438               <td class="left"></td>
439               <td class="right">HP</td>
440            </tr>
441            <tr>
442               <td class="left"></td>
443               <td class="right">H. Frystyk</td>
444            </tr>
445            <tr>
446               <td class="left"></td>
447               <td class="right">Microsoft</td>
448            </tr>
449            <tr>
450               <td class="left"></td>
451               <td class="right">L. Masinter</td>
452            </tr>
453            <tr>
454               <td class="left"></td>
455               <td class="right">Adobe</td>
456            </tr>
457            <tr>
458               <td class="left"></td>
459               <td class="right">P. Leach</td>
460            </tr>
461            <tr>
462               <td class="left"></td>
463               <td class="right">Microsoft</td>
464            </tr>
465            <tr>
466               <td class="left"></td>
467               <td class="right">T. Berners-Lee</td>
468            </tr>
469            <tr>
470               <td class="left"></td>
471               <td class="right">W3C/MIT</td>
472            </tr>
473            <tr>
474               <td class="left"></td>
475               <td class="right">Y. Lafon, Editor</td>
476            </tr>
477            <tr>
478               <td class="left"></td>
479               <td class="right">W3C</td>
480            </tr>
481            <tr>
482               <td class="left"></td>
483               <td class="right">J. Reschke, Editor</td>
484            </tr>
485            <tr>
486               <td class="left"></td>
487               <td class="right">greenbytes</td>
488            </tr>
489            <tr>
490               <td class="left"></td>
491               <td class="right">October 27, 2011</td>
492            </tr>
493         </tbody>
494      </table>
495      <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-latest</span></p>
496      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
497      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
498         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
499         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
500      </p> 
501      <p>Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.</p> 
502      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
503      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (, which is archived
504         at &lt;<a href=""></a>&gt;.
505      </p> 
506      <p>The current issues list is at &lt;<a href=""></a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href=""></a>&gt;.
507      </p> 
508      <p>The changes in this draft are summarized in <a href="#changes.since.16" title="Since draft-ietf-httpbis-p5-range-16">Appendix&nbsp;D.18</a>.
509      </p> 
510      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
511      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
512      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
513         working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href=""></a>.
514      </p>
515      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
516         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
517         in progress”.
518      </p>
519      <p>This Internet-Draft will expire on April 29, 2012.</p>
520      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
521      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
522      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href=""></a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
523         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
524         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
525         BSD License.
526      </p>
527      <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
528         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
529         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
530         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
531         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
532         it into languages other than English.
533      </p>
534      <hr class="noprint">
535      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
536      <ul class="toc">
537         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
538               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
539               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
540                     <li>1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
541                     <li>1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
542                  </ul>
543               </li>
544            </ul>
545         </li>
546         <li>2.&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a><ul>
547               <li>2.1&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registry">Range Specifier Registry</a></li>
548            </ul>
549         </li>
550         <li>3.&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
551               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
552               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
553            </ul>
554         </li>
555         <li>4.&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
556         <li>5.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
557               <li>5.1&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
558               <li>5.2&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
559               <li>5.3&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
560               <li>5.4&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
561                     <li>5.4.1&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
562                     <li>5.4.2&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
563                  </ul>
564               </li>
565            </ul>
566         </li>
567         <li>6.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
568               <li>6.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
569               <li>6.2&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
570               <li>6.3&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registration">Range Specifier Registration</a></li>
571            </ul>
572         </li>
573         <li>7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
574               <li>7.1&nbsp;&nbsp;&nbsp;<a href="#overlapping.ranges">Overlapping Ranges</a></li>
575            </ul>
576         </li>
577         <li>8.&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
578         <li>9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
579               <li>9.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
580               <li>9.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
581            </ul>
582         </li>
583         <li><a href="#rfc.authors">Authors' Addresses</a></li>
584         <li>A.&nbsp;&nbsp;&nbsp;<a href="">Internet Media Type multipart/byteranges</a></li>
585         <li>B.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
586               <li>B.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
587            </ul>
588         </li>
589         <li>C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
590         <li>D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
591               <li>D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC 2616</a></li>
592               <li>D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p5-range-00</a></li>
593               <li>D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p5-range-01</a></li>
594               <li>D.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></li>
595               <li>D.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></li>
596               <li>D.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></li>
597               <li>D.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></li>
598               <li>D.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></li>
599               <li>D.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></li>
600               <li>D.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></li>
601               <li>D.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></li>
602               <li>D.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></li>
603               <li>D.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></li>
604               <li>D.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p5-range-12</a></li>
605               <li>D.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p5-range-13</a></li>
606               <li>D.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p5-range-14</a></li>
607               <li>D.17&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p5-range-15</a></li>
608               <li>D.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p5-range-16</a></li>
609            </ul>
610         </li>
611         <li><a href="#rfc.index">Index</a></li>
612      </ul>
613      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
614      <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 client
615         has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
616         rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
617         request only a subset of a larger representation, such as a single page of a very large document or only part of an image
618         to be rendered by a device with limited local storage.
619      </p>
620      <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
621         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
622         request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
623         full responses by intermediate caches that might not implement the feature.
624      </p>
625      <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
626         requests for byte ranges.
627      </p>
628      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.conformance.and.error.handling" href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></h2>
629      <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"
630         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>.
631      </p>
632      <p id="rfc.section.1.1.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
633         Servers, User-Agents, Origin Servers, Intermediaries, Proxies and Gateways. See <a href="p1-messaging.html#architecture" title="Architecture">Section 2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for definitions of these terms.
634      </p>
635      <p id="rfc.section.1.1.p.3">An implementation is considered conformant if it complies with all of the requirements associated with its role(s). Note that
636         SHOULD-level requirements are relevant here, unless one of the documented exceptions is applicable.
637      </p>
638      <p id="rfc.section.1.1.p.4">This document also uses ABNF to define valid protocol elements (<a href="#notation" title="Syntax Notation">Section&nbsp;1.2</a>). In addition to the prose requirements placed upon them, Senders <em class="bcp14">MUST NOT</em> generate protocol elements that are invalid.
639      </p>
640      <p id="rfc.section.1.1.p.5">Unless noted otherwise, Recipients <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling
641         mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
642         different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
643         Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type of
644         error recovery could lead to dangerous consequences.
645      </p>
646      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
647      <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF, with the list rule expanded.
648      </p>
649      <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
650         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
651         character).
652      </p>
653      <p id="rfc.section.1.2.p.3">Note that all rules derived from <a href="#core.rules" class="smpl">token</a> are to be compared case-insensitively, like <a href="#range.units" class="smpl">range-unit</a> and <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>.
654      </p>
655      <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
656      <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>:
657      </p>
658      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">OWS</a>        = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
659  <a href="#core.rules" class="smpl">token</a>      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.rules" title="Common Field ABNF Rules">Section 3.2.3</a>&gt;
660  <a href="#core.rules" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="" title="Date/Time Formats">Section 8</a>&gt;
661</pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
662      <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
663      <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>&gt;
664</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
665      <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range) of the representation be included within the response. HTTP/1.1
666         uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;5.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;5.2</a>) header fields. A representation can be broken down into subranges according to various structural units.
667      </p>
668      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#range.units" class="smpl">range-unit</a>       = <a href="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a>
669  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
670  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a>
671</pre><p id="rfc.section.2.p.3">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges. The only range
672         unit defined by HTTP/1.1 is "bytes". Additional specifiers can be defined as described in <a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a>.
673      </p>
674      <p id="rfc.section.2.p.4">If a range unit is not understood in a request, a server <em class="bcp14">MUST</em> ignore the whole Range header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;5.4</a>). If a range unit is not understood in a response, an intermediary <em class="bcp14">SHOULD</em> pass the response to the client; a client <em class="bcp14">MUST</em> fail.
675      </p>
676      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="range.specifier.registry" href="#range.specifier.registry">Range Specifier Registry</a></h2>
677      <p id="rfc.section.2.1.p.1">The HTTP Range Specifier Registry defines the name space for the range specifier names.</p>
678      <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
679      </p>
680      <ul>
681         <li>Name</li>
682         <li>Description</li>
683         <li>Pointer to specification text</li>
684      </ul>
685      <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="">Section 4.1</a>).
686      </p>
687      <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href=""></a>&gt;.
688      </p>
689      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="status.code.definitions" href="#status.code.definitions">Status Code Definitions</a></h1>
690      <div id="rfc.iref.3"></div>
691      <div id="rfc.iref.s.1"></div>
692      <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>
693      <p id="rfc.section.3.1.p.1">The server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a Range header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;5.4</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;5.3</a>) to make the request conditional.
694      </p>
695      <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
696      </p>
697      <ul>
698         <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
699            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.
700         </li>
701         <li>Date</li>
702         <li>Cache-Control, ETag, Expires, Content-Location, Last-Modified, and/or Vary, if the header field would have been sent in a
703            200 response to the same request
704         </li>
705      </ul>
706      <p id="rfc.section.3.1.p.3">If the 206 response is the result of an If-Range request, the response <em class="bcp14">SHOULD NOT</em> include other representation header fields. Otherwise, the response <em class="bcp14">MUST</em> include all of the representation header fields that would have been returned with a 200 (OK) response to the same request.
707      </p>
708      <div id="rfc.iref.4"></div>
709      <div id="rfc.iref.s.2"></div>
710      <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>
711      <p id="rfc.section.3.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;5.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request
712         did not include an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>). (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current
713         length of the selected resource.)
714      </p>
715      <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range header field specifying the current length of the representation (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.
716      </p>
717      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Ranges</a></h1>
718      <p id="rfc.section.4.p.1">A response might transfer only a subrange of a representation if the connection closed prematurely or if the request used
719         one or more Range specifications. After several such transfers, a client might have received several ranges of the same representation.
720         These ranges can only be safely combined if they all have in common the same strong validator, where "strong validator" is
721         defined to be either an entity-tag that is not marked as weak (<a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>) or, if no entity-tag is provided, a Last-Modified value that is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
722      </p>
723      <p id="rfc.section.4.p.2">When a client receives an incomplete 200 (OK) or 206 (Partial Content) response and already has one or more stored responses
724         for the same method and effective request URI, all of the stored responses with the same strong validator <em class="bcp14">MAY</em> be combined with the partial content in this new response. If none of the stored responses contain the same strong validator,
725         then this new response corresponds to a new representation and <em class="bcp14">MUST NOT</em> be combined with the existing stored responses.
726      </p>
727      <p id="rfc.section.4.p.3">If the new response is an incomplete 200 (OK) response, then the header fields of that new response are used for any combined
728         response and replace those of the matching stored responses.
729      </p>
730      <p id="rfc.section.4.p.4">If the new response is a 206 (Partial Content) response and at least one of the matching stored responses is a 200 (OK), then
731         the combined response header fields consist of the most recent 200 response's header fields. If all of the matching stored
732         responses are 206 responses, then the stored response with the most header fields is used as the source of header fields for
733         the combined response, except that the client <em class="bcp14">MUST</em> use other header fields provided in the new response, aside from Content-Range, to replace all instances of the corresponding
734         header fields in the stored response.
735      </p>
736      <p id="rfc.section.4.p.5">The combined response message-body consists of the union of partial content ranges in the new response and each of the selected
737         responses. If the union consists of the entire range of the representation, then the combined response <em class="bcp14">MUST</em> be recorded as a complete 200 (OK) response with a Content-Length header field that reflects the complete length. Otherwise,
738         the combined response(s) <em class="bcp14">MUST</em> include a Content-Range header field describing the included range(s) and be recorded as incomplete. If the union consists
739         of a discontinuous range of the representation, then the client <em class="bcp14">MAY</em> store it as either a multipart range response or as multiple 206 responses with one continuous range each.
740      </p>
741      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
742      <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>
743      <div id="rfc.iref.a.1"></div>
744      <div id="rfc.iref.h.1"></div>
745      <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>
746      <p id="rfc.section.5.1.p.1">The "Accept-Ranges" header field allows a resource to indicate its acceptance of range requests.</p>
747      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
748  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
749</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
750      </p>
751      <div id="rfc.figure.u.5"></div><pre class="text">  Accept-Ranges: bytes
752</pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate range requests without having received this header field for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
753      </p>
754      <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
755      </p>
756      <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: none
757</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
758      <div id="rfc.iref.c.1"></div>
759      <div id="rfc.iref.h.2"></div>
760      <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>
761      <p id="rfc.section.5.2.p.1">The "Content-Range" header field is sent with a partial representation to specify where in the full representation the payload
762         body is intended to be applied.
763      </p>
764      <p id="rfc.section.5.2.p.2">Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
765      </p>
766      <div id="rfc.figure.u.7"></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>  <a href="#header.content-range" class="smpl">Content-Range</a>           = <a href="#header.content-range" class="smpl">byte-content-range-spec</a>
767                          / <a href="#header.content-range" class="smpl">other-content-range-spec</a>
769  <a href="#header.content-range" class="smpl">byte-content-range-spec</a> = <a href="#range.units" class="smpl">bytes-unit</a> <a href="#notation" class="smpl">SP</a>
770                            <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> "/"
771                            ( <a href="#header.content-range" class="smpl">instance-length</a> / "*" )
773  <a href="#header.content-range" class="smpl">byte-range-resp-spec</a>    = (<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>)
774                          / "*"
776  <a href="#header.content-range" class="smpl">instance-length</a>         = 1*<a href="#notation" class="smpl">DIGIT</a>
778  <a href="#header.content-range" class="smpl">other-content-range-spec</a> = <a href="#range.units" class="smpl">other-range-unit</a> <a href="#notation" class="smpl">SP</a>
779                             <a href="#header.content-range" class="smpl">other-range-resp-spec</a>
780  <a href="#header.content-range" class="smpl">other-range-resp-spec</a>    = *<a href="#notation" class="smpl">CHAR</a>
781</pre><p id="rfc.section.5.2.p.4">The header field <em class="bcp14">SHOULD</em> indicate the total length of the full representation, unless this length is unknown or difficult to determine. The asterisk
782         "*" character means that the instance-length is unknown at the time when the response was generated.
783      </p>
784      <p id="rfc.section.5.2.p.5">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;5.4.1</a>), a byte-range-resp-spec <em class="bcp14">MUST</em> only specify one range, and <em class="bcp14">MUST</em> contain absolute byte positions for both the first and last byte of the range.
785      </p>
786      <p id="rfc.section.5.2.p.6">A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos value is less than its first-byte-pos value, or
787         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.
788      </p>
789      <p id="rfc.section.5.2.p.7">In the case of a byte range request: A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
790         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 "*".
791      </p>
792      <p id="rfc.section.5.2.p.8">Examples of byte-content-range-spec values, assuming that the representation contains a total of 1234 bytes: </p>
793      <ul>
794         <li>The first 500 bytes:
795            <div id="rfc.figure.u.8"></div><pre class="text">  bytes 0-499/1234
796</pre> </li>
797         <li>The second 500 bytes:
798            <div id="rfc.figure.u.9"></div><pre class="text">  bytes 500-999/1234
799</pre> </li>
800         <li>All except for the first 500 bytes:
801            <div id="rfc.figure.u.10"></div><pre class="text">  bytes 500-1233/1234
802</pre> </li>
803         <li>The last 500 bytes:
804            <div id="rfc.figure.u.11"></div><pre class="text">  bytes 734-1233/1234
805</pre> </li>
806      </ul>
807      <p id="rfc.section.5.2.p.9">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
808         a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header field,
809         and a Content-Length header field showing the number of bytes actually transferred. For example,
810      </p>
811      <div id="rfc.figure.u.12"></div><pre class="text">  HTTP/1.1 206 Partial Content
812  Date: Wed, 15 Nov 1995 06:25:24 GMT
813  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
814  Content-Range: bytes 21010-47021/47022
815  Content-Length: 26012
816  Content-Type: image/gif
817</pre><p id="rfc.section.5.2.p.11">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
818         ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
819         as defined in <a href="" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
820      </p>
821      <p id="rfc.section.5.2.p.12">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
822      </p>
823      <p id="rfc.section.5.2.p.13">When a client requests multiple ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
824      </p>
825      <p id="rfc.section.5.2.p.14">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
826         the full representation).
827      </p>
828      <p id="rfc.section.5.2.p.15">If the server receives a request (other than one including an If-Range header field) with an unsatisfiable Range header field
829         (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
830         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>).
831      </p>
832      <div class="note" id="rfc.section.5.2.p.16"> 
833         <p> <b>Note:</b> Clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
834            an unsatisfiable Range header field, since not all servers implement this header field.
835         </p> 
836      </div>
837      <div id="rfc.iref.i.1"></div>
838      <div id="rfc.iref.h.3"></div>
839      <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>
840      <p id="rfc.section.5.3.p.1">If a client has a partial copy of a representation and wishes to have an up-to-date copy of the entire representation, it
841         could use the Range header field with a conditional GET (using either or both of If-Unmodified-Since and If-Match.) However,
842         if the condition fails because the representation has been modified, the client would then have to make a second request to
843         obtain the entire current representation.
844      </p>
845      <p id="rfc.section.5.3.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is "if the representation
846         is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation".
847      </p>
848      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#core.rules" class="smpl">HTTP-date</a>
849</pre><p id="rfc.section.5.3.p.4">Clients <em class="bcp14">MUST NOT</em> use an entity-tag marked as weak in an If-Range field value and <em class="bcp14">MUST NOT</em> use a Last-Modified date in an If-Range field value unless it has no entity-tag for the representation and the Last-Modified
850         date it does have for the representation is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
851      </p>
852      <p id="rfc.section.5.3.p.5">A server that evaluates a conditional range request that is applicable to one of its representations <em class="bcp14">MUST</em> evaluate the condition as false if the entity-tag used as a validator is marked as weak or, when an HTTP-date is used as the
853         validator, if the date value is not strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. (A server can distinguish between a valid HTTP-date and any form of entity-tag by examining the first two characters.)
854      </p>
855      <p id="rfc.section.5.3.p.6">The If-Range header field <em class="bcp14">SHOULD</em> only be sent by clients together with a Range header field. The If-Range header field <em class="bcp14">MUST</em> be ignored if it is received in a request that does not include a Range header field. The If-Range header field <em class="bcp14">MUST</em> be ignored by a server that does not support the sub-range operation.
856      </p>
857      <p id="rfc.section.5.3.p.7">If the validator given in the If-Range header field matches the current validator for the selected representation of the target
858         resource, then the server <em class="bcp14">SHOULD</em> send the specified sub-range of the representation using a 206 (Partial Content) response. If the validator does not match,
859         then the server <em class="bcp14">SHOULD</em> send the entire representation using a 200 (OK) response.
860      </p>
861      <div id="rfc.iref.r.1"></div>
862      <div id="rfc.iref.h.4"></div>
863      <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>
864      <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>
865      <p id="rfc.section.5.4.1.p.1">Since all HTTP representations are transferred as sequences of bytes, the concept of a byte range is meaningful for any HTTP
866         representation. (However, not all clients and servers need to support byte-range operations.)
867      </p>
868      <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the representation body (not necessarily the same as the
869         message-body).
870      </p>
871      <div id="rule.ranges-specifier">
872         <p id="rfc.section.5.4.1.p.3">                A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single representation.
873         </p>
874      </div>
875      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.11"></span><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>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
876  <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>  = 1#( <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> / <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> )
877  <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" [ <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> ]
878  <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
879  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
880</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
881         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
882         at zero.
883      </p>
884      <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
885         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.
886      </p>
887      <p id="rfc.section.5.4.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the representation
888         body, last-byte-pos is taken to be equal to one less than the current length of the representation in bytes.
889      </p>
890      <p id="rfc.section.5.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the representation.</p>
891      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
892  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
893</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the representation body, of a length given by the suffix-length
894         value. (That is, this form specifies the last N bytes of a representation.) If the representation is shorter than the specified
895         suffix-length, the entire representation is used.
896      </p>
897      <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
898         length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set
899         is satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> return a response with a 416 (Requested range not satisfiable) status code. Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a 206 (Partial Content) status code containing the satisfiable ranges of the representation.
900      </p>
901      <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p>
902      <ul>
903         <li>The first 500 bytes (byte offsets 0-499, inclusive):
904            <div id="rfc.figure.u.16"></div><pre class="text">  bytes=0-499
905</pre> </li>
906         <li>The second 500 bytes (byte offsets 500-999, inclusive):
907            <div id="rfc.figure.u.17"></div><pre class="text">  bytes=500-999
908</pre> </li>
909         <li>The final 500 bytes (byte offsets 9500-9999, inclusive):
910            <div id="rfc.figure.u.18"></div><pre class="text">  bytes=-500
911</pre> Or: <div id="rfc.figure.u.19"></div><pre class="text">  bytes=9500-
912</pre> </li>
913         <li>The first and last bytes only (bytes 0 and 9999):
914            <div id="rfc.figure.u.20"></div><pre class="text">  bytes=0-0,-1
915</pre> </li>
916         <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive):
917            <div id="rfc.figure.u.21"></div><pre class="text">  bytes=500-600,601-999
918  bytes=500-700,601-999
919</pre> </li>
920      </ul>
921      <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>
922      <p id="rfc.section.5.4.2.p.1">The "Range" header field defines the GET method (conditional or not) to request one or more sub-ranges of the response representation
923         body, instead of the entire representation body.
924      </p>
925      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.19"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
926  <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = <a href="#range.units" class="smpl">other-range-unit</a> "=" <a href="#range.retrieval.requests" class="smpl">other-range-set</a>
927  <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#notation" class="smpl">CHAR</a>
928</pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header field. However, origin servers and intermediate caches ought to support byte ranges when possible,
929         since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
930         representations.
931      </p>
932      <p id="rfc.section.5.4.2.p.4">If the server supports the Range header field and the specified range or ranges are appropriate for the representation: </p>
933      <ul>
934         <li>The presence of a Range header field in an unconditional GET modifies what is returned if the GET is otherwise successful.
935            In other words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
936         </li>
937         <li>The presence of a Range header field in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match,
938            or one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
939            is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
940         </li>
941      </ul>
942      <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header field (see <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section&nbsp;5.3</a>) in addition to the Range header field.
943      </p>
944      <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
945         representation in reply, it <em class="bcp14">MAY</em> only return the requested range to its client.
946      </p>
947      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
948      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2>
949      <p id="rfc.section.6.1.p.1">The HTTP Status Code Registry located at &lt;<a href=""></a>&gt; shall be updated with the registrations below:
950      </p>
951      <div id="rfc.table.1">
952         <div id="iana.status.code.registration.table"></div>
953         <table class="tt full left" cellpadding="3" cellspacing="0">
954            <thead>
955               <tr>
956                  <th>Value</th>
957                  <th>Description</th>
958                  <th>Reference</th>
959               </tr>
960            </thead>
961            <tbody>
962               <tr>
963                  <td class="left">206</td>
964                  <td class="left">Partial Content</td>
965                  <td class="left"> <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;3.1</a> 
966                  </td>
967               </tr>
968               <tr>
969                  <td class="left">416</td>
970                  <td class="left">Requested Range Not Satisfiable</td>
971                  <td class="left"> <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a> 
972                  </td>
973               </tr>
974            </tbody>
975         </table>
976      </div>
977      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
978      <p id="rfc.section.6.2.p.1">The Message Header Field Registry located at &lt;<a href=""></a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
979      </p>
980      <div id="rfc.table.2">
981         <div id="iana.header.registration.table"></div>
982         <table class="tt full left" cellpadding="3" cellspacing="0">
983            <thead>
984               <tr>
985                  <th>Header Field Name</th>
986                  <th>Protocol</th>
987                  <th>Status</th>
988                  <th>Reference</th>
989               </tr>
990            </thead>
991            <tbody>
992               <tr>
993                  <td class="left">Accept-Ranges</td>
994                  <td class="left">http</td>
995                  <td class="left">standard</td>
996                  <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a> 
997                  </td>
998               </tr>
999               <tr>
1000                  <td class="left">Content-Range</td>
1001                  <td class="left">http</td>
1002                  <td class="left">standard</td>
1003                  <td class="left"> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a> 
1004                  </td>
1005               </tr>
1006               <tr>
1007                  <td class="left">If-Range</td>
1008                  <td class="left">http</td>
1009                  <td class="left">standard</td>
1010                  <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">Section&nbsp;5.3</a> 
1011                  </td>
1012               </tr>
1013               <tr>
1014                  <td class="left">Range</td>
1015                  <td class="left">http</td>
1016                  <td class="left">standard</td>
1017                  <td class="left"> <a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a> 
1018                  </td>
1019               </tr>
1020            </tbody>
1021         </table>
1022      </div>
1023      <p id="rfc.section.6.2.p.2">The change controller is: "IETF ( - Internet Engineering Task Force".</p>
1024      <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="range.specifier.registration" href="#range.specifier.registration">Range Specifier Registration</a></h2>
1025      <p id="rfc.section.6.3.p.1">The registration procedure for HTTP Range Specifiers is defined by <a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a> of this document.
1026      </p>
1027      <p id="rfc.section.6.3.p.2">The HTTP Range Specifier Registry shall be created at &lt;<a href=""></a>&gt; and be populated with the registrations below:
1028      </p>
1029      <div id="rfc.table.3">
1030         <div id="iana.range.specifiers.table"></div>
1031         <table class="tt full left" cellpadding="3" cellspacing="0">
1032            <thead>
1033               <tr>
1034                  <th>Range Specifier Name</th>
1035                  <th>Description</th>
1036                  <th>Reference</th>
1037               </tr>
1038            </thead>
1039            <tbody>
1040               <tr>
1041                  <td class="left">bytes</td>
1042                  <td class="left">a range of octets</td>
1043                  <td class="left">(this specification)</td>
1044               </tr>
1045            </tbody>
1046         </table>
1047      </div>
1048      <p id="rfc.section.6.3.p.3">The change controller is: "IETF ( - Internet Engineering Task Force".</p>
1049      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
1050      <p id="rfc.section.7.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
1051         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
1052         make some suggestions for reducing security risks.
1053      </p>
1054      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="overlapping.ranges" href="#overlapping.ranges">Overlapping Ranges</a></h2>
1055      <p id="rfc.section.7.1.p.1">Range requests containing overlapping ranges may lead to the situation where a server is sending far more data than the size
1056         of the complete resource representation.
1057      </p>
1058      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
1059      <p id="rfc.section.8.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 11</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
1060      </p>
1061      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
1062      </h1>
1063      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
1064      </h2>
1065      <table>           
1066         <tr>
1067            <td class="reference"><b id="Part1">[Part1]</b></td>
1068            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="" title="Microsoft Corporation">Frystyk, H.</a>, <a href="" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, <a href="" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), October&nbsp;2011.
1069            </td>
1070         </tr>
1071         <tr>
1072            <td class="reference"><b id="Part2">[Part2]</b></td>
1073            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="" title="Microsoft Corporation">Frystyk, H.</a>, <a href="" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, <a href="" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), October&nbsp;2011.
1074            </td>
1075         </tr>
1076         <tr>
1077            <td class="reference"><b id="Part4">[Part4]</b></td>
1078            <td class="top"><a href="" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="" title="Microsoft Corporation">Frystyk, H.</a>, <a href="" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, <a href="" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), October&nbsp;2011.
1079            </td>
1080         </tr>
1081         <tr>
1082            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
1083            <td class="top"><a href="" title="Innosoft International, Inc.">Freed, N.</a> and <a href="" title="First Virtual Holdings">N. Borenstein</a>, “<a href="">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
1084            </td>
1085         </tr>
1086         <tr>
1087            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1088            <td class="top"><a href="" title="Harvard University">Bradner, S.</a>, “<a href="">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
1089            </td>
1090         </tr>
1091         <tr>
1092            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1093            <td class="top"><a href="" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="" title="THUS plc.">P. Overell</a>, “<a href="">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
1094            </td>
1095         </tr>
1096      </table>
1097      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
1098      </h2>
1099      <table>       
1100         <tr>
1101            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1102            <td class="top"><a href="" title="University of California, Irvine">Fielding, R.</a>, <a href="" title="W3C">Gettys, J.</a>, <a href="" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="" title="Xerox Corporation">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, and <a href="" title="W3C">T. Berners-Lee</a>, “<a href="">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
1103            </td>
1104         </tr>
1105         <tr>
1106            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1107            <td class="top"><a href="" title="Nine by Nine">Klyne, G.</a>, <a href="" title="BEA Systems">Nottingham, M.</a>, and <a href="" title="HP Labs">J. Mogul</a>, “<a href="">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
1108            </td>
1109         </tr>
1110         <tr>
1111            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
1112            <td class="top"><a href="" title="Sun Microsystems">Freed, N.</a> and <a href="">J. Klensin</a>, “<a href="">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
1113            </td>
1114         </tr>
1115         <tr>
1116            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
1117            <td class="top"><a href="" title="IBM">Narten, T.</a> and <a href="" title="Google">H. Alvestrand</a>, “<a href="">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
1118            </td>
1119         </tr>
1120      </table>
1121      <div class="avoidbreak">
1122         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1123         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
1124               (editor)
1125               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
1126         <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">Alcatel-Lucent Bell Labs</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
1127         <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=""><span class="email"></span></a></span></address>
1128         <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=""><span class="email"></span></a></span></address>
1129         <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=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
1130         <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=""><span class="email"></span></a></span></address>
1131         <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=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
1132         <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
1133               (editor)
1134               <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=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
1135         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
1136               (editor)
1137               <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=""><span class="email"></span></a></span><span class="vcardline">URI: <a href="" class="url"></a></span></address>
1138      </div>
1139      <div id="rfc.iref.m.1"></div>
1140      <div id="rfc.iref.m.2"></div>
1141      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="" href="">Internet Media Type multipart/byteranges</a></h1>
1142      <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
1143         non-overlapping ranges), these are transmitted as a multipart message-body (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="">Section 5.1</a>). The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
1144      </p>
1145      <div class="note" id="rfc.section.A.p.2"> 
1146         <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
1147         </p> 
1148      </div>
1149      <p id="rfc.section.A.p.3">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
1150         required boundary parameter specifies the boundary string used to separate each body-part.
1151      </p>
1152      <p id="rfc.section.A.p.4"> </p>
1153      <dl>
1154         <dt>Type name:</dt>
1155         <dd>multipart</dd>
1156         <dt>Subtype name:</dt>
1157         <dd>byteranges</dd>
1158         <dt>Required parameters:</dt>
1159         <dd>boundary</dd>
1160         <dt>Optional parameters:</dt>
1161         <dd>none</dd>
1162         <dt>Encoding considerations:</dt>
1163         <dd>only "7bit", "8bit", or "binary" are permitted</dd>
1164         <dt>Security considerations:</dt>
1165         <dd>none</dd>
1166         <dt>Interoperability considerations:</dt>
1167         <dd>none</dd>
1168         <dt>Published specification:</dt>
1169         <dd>This specification (see <a href="" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
1170         </dd>
1171         <dt>Applications that use this media type:</dt>
1172         <dt>Additional information:</dt>
1173         <dd> 
1174            <dl>
1175               <dt>Magic number(s):</dt>
1176               <dd>none</dd>
1177               <dt>File extension(s):</dt>
1178               <dd>none</dd>
1179               <dt>Macintosh file type code(s):</dt>
1180               <dd>none</dd>
1181            </dl> 
1182         </dd>
1183         <dt>Person and email address to contact for further information:</dt>
1184         <dd>See Authors Section.</dd>
1185         <dt>Intended usage:</dt>
1186         <dd>COMMON</dd>
1187         <dt>Restrictions on usage:</dt>
1188         <dd>none</dd>
1189         <dt>Author/Change controller:</dt>
1190         <dd>IESG</dd>
1191      </dl>
1192      <div id="rfc.figure.u.23"></div>
1193      <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
1194  Date: Wed, 15 Nov 1995 06:25:24 GMT
1195  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
1196  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1199  Content-type: application/pdf
1200  Content-range: bytes 500-999/8000
1202  ...the first range...
1204  Content-type: application/pdf
1205  Content-range: bytes 7000-7999/8000
1207  ...the second range
1209</pre><div id="rfc.figure.u.24"></div>
1210      <p>Other example:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
1211  Date: Tue, 14 Nov 1995 06:25:24 GMT
1212  Last-Modified: Tue, 14 July 04:58:08 GMT
1213  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1216  Content-type: video/example
1217  Content-range: exampleunit 1.2-4.3/25
1219  ...the first range...
1221  Content-type: video/example
1222  Content-range: exampleunit 11.2-14.3/25
1224  ...the second range
1226</pre> <p id="rfc.section.A.p.7">Notes: </p>
1227      <ol>
1228         <li>Additional CRLFs <em class="bcp14">MAY</em> precede the first boundary string in the body.
1229         </li>
1230         <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> permits the boundary string to be quoted, some existing implementations handle a quoted boundary string incorrectly.
1231         </li>
1232         <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.
1233         </li>
1234      </ol>
1235      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
1236      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
1237      <p id="rfc.section.B.1.p.1">Clarify that it is not ok to use a weak validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
1238      </p>
1239      <p id="rfc.section.B.1.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;5</a>)
1240      </p>
1241      <p id="rfc.section.B.1.p.3">Clarify that multipart/byteranges can consist of a single part. (<a href="" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
1242      </p>
1243      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
1244      <div id="rfc.figure.u.25"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
1246<a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range-spec / other-content-range-spec
1248<a href="#core.rules" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 8&gt;
1250<a href="#header.if-range" class="smpl">If-Range</a> = entity-tag / HTTP-date
1252<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
1254<a href="#range.retrieval.requests" class="smpl">Range</a> = byte-ranges-specifier / other-ranges-specifier
1256<a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = ( *( "," OWS ) range-unit *( OWS "," [ OWS
1257 range-unit ] ) ) / "none"
1259<a href="#header.content-range" class="smpl">byte-content-range-spec</a> = bytes-unit SP byte-range-resp-spec "/" (
1260 instance-length / "*" )
1261<a href="#header.content-range" class="smpl">byte-range-resp-spec</a> = ( first-byte-pos "-" last-byte-pos ) / "*"
1262<a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = ( *( "," OWS ) byte-range-spec ) / (
1263 suffix-byte-range-spec *( OWS "," [ ( OWS byte-range-spec ) /
1264 suffix-byte-range-spec ] ) )
1265<a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ]
1266<a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set
1267<a href="#range.units" class="smpl">bytes-unit</a> = "bytes"
1269<a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in [Part4], Section 2.3&gt;
1271<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT
1273<a href="#header.content-range" class="smpl">instance-length</a> = 1*DIGIT
1275<a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*DIGIT
1277<a href="#header.content-range" class="smpl">other-content-range-spec</a> = other-range-unit SP other-range-resp-spec
1278<a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *CHAR
1279<a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*CHAR
1280<a href="#range.units" class="smpl">other-range-unit</a> = token
1281<a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = other-range-unit "=" other-range-set
1283<a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit
1285<a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" suffix-length
1286<a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT
1288<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.3&gt;
1289</pre> <div id="rfc.figure.u.26"></div>
1290      <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
1291; Content-Range defined but not used
1292; If-Range defined but not used
1293; Range defined but not used
1294</pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
1295      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC 2616
1296      </h2>
1297      <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
1298      </p>
1299      <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
1300      </h2>
1301      <p id="rfc.section.D.2.p.1">Closed issues: </p>
1302      <ul>
1303         <li> &lt;<a href=""></a>&gt;: "Cache validators in 206 responses" (&lt;<a href=""></a>&gt;)
1304         </li>
1305         <li> &lt;<a href=""></a>&gt;: "Normative and Informative references"
1306         </li>
1307         <li> &lt;<a href=""></a>&gt;: "Normative up-to-date references"
1308         </li>
1309      </ul>
1310      <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
1311      </h2>
1312      <p id="rfc.section.D.3.p.1">Closed issues: </p>
1313      <ul>
1314         <li> &lt;<a href=""></a>&gt;: "Updating to RFC4288"
1315         </li>
1316      </ul>
1317      <p id="rfc.section.D.3.p.2">Ongoing work on ABNF conversion (&lt;<a href=""></a>&gt;):
1318      </p>
1319      <ul>
1320         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1321      </ul>
1322      <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></h2>
1323      <p id="rfc.section.D.4.p.1">Ongoing work on IANA Message Header Field Registration (&lt;<a href=""></a>&gt;):
1324      </p>
1325      <ul>
1326         <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
1327      </ul>
1328      <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></h2>
1329      <p id="rfc.section.D.5.p.1">None.</p>
1330      <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></h2>
1331      <p id="rfc.section.D.6.p.1">Closed issues: </p>
1332      <ul>
1333         <li> &lt;<a href=""></a>&gt;: "multipart/byteranges minimum number of parts"
1334         </li>
1335      </ul>
1336      <p id="rfc.section.D.6.p.2">Ongoing work on ABNF conversion (&lt;<a href=""></a>&gt;):
1337      </p>
1338      <ul>
1339         <li>Use "/" instead of "|" for alternatives.</li>
1340         <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1341         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
1342      </ul>
1343      <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></h2>
1344      <p id="rfc.section.D.7.p.1">Closed issues: </p>
1345      <ul>
1346         <li> &lt;<a href=""></a>&gt;: "State base for *-byte-pos and suffix-length"
1347         </li>
1348      </ul>
1349      <p id="rfc.section.D.7.p.2">Ongoing work on Custom Ranges (&lt;<a href=""></a>&gt;):
1350      </p>
1351      <ul>
1352         <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
1353      </ul>
1354      <p id="rfc.section.D.7.p.3">Final work on ABNF conversion (&lt;<a href=""></a>&gt;):
1355      </p>
1356      <ul>
1357         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
1358      </ul>
1359      <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></h2>
1360      <p id="rfc.section.D.8.p.1">Closed issues: </p>
1361      <ul>
1362         <li> &lt;<a href=""></a>&gt;: "base for numeric protocol elements"
1363         </li>
1364      </ul>
1365      <h2 id="rfc.section.D.9"><a href="#rfc.section.D.9">D.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></h2>
1366      <p id="rfc.section.D.9.p.1">Closed issues: </p>
1367      <ul>
1368         <li>Fixed discrepancy in the If-Range definition about allowed validators.</li>
1369         <li> &lt;<a href=""></a>&gt;: "multipart/byteranges for custom range units"
1370         </li>
1371         <li> &lt;<a href=""></a>&gt;: "range unit missing from other-ranges-specifier in Range header"
1372         </li>
1373         <li> &lt;<a href=""></a>&gt;: "move IANA registrations for optional status codes"
1374         </li>
1375      </ul>
1376      <h2 id="rfc.section.D.10"><a href="#rfc.section.D.10">D.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></h2>
1377      <p id="rfc.section.D.10.p.1">No significant changes.</p>
1378      <h2 id="rfc.section.D.11"><a href="#rfc.section.D.11">D.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></h2>
1379      <p id="rfc.section.D.11.p.1">No significant changes.</p>
1380      <h2 id="rfc.section.D.12"><a href="#rfc.section.D.12">D.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></h2>
1381      <p id="rfc.section.D.12.p.1">Closed issues: </p>
1382      <ul>
1383         <li> &lt;<a href=""></a>&gt;: "Clarify 'Requested Variant'"
1384         </li>
1385         <li> &lt;<a href=""></a>&gt;: "Clarify entity / representation / variant terminology"
1386         </li>
1387         <li> &lt;<a href=""></a>&gt;: "consider removing the 'changes from 2068' sections"
1388         </li>
1389      </ul>
1390      <p id="rfc.section.D.12.p.2">Ongoing work on Custom Ranges (&lt;<a href=""></a>&gt;):
1391      </p>
1392      <ul>
1393         <li>Add IANA registry.</li>
1394      </ul>
1395      <h2 id="rfc.section.D.13"><a href="#rfc.section.D.13">D.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></h2>
1396      <p id="rfc.section.D.13.p.1">Closed issues: </p>
1397      <ul>
1398         <li> &lt;<a href=""></a>&gt;: "Caches can't be required to serve ranges"
1399         </li>
1400      </ul>
1401      <h2 id="rfc.section.D.14"><a href="#rfc.section.D.14">D.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p5-range-12</a></h2>
1402      <p id="rfc.section.D.14.p.1">Closed issues: </p>
1403      <ul>
1404         <li> &lt;<a href=""></a>&gt;: "Header Classification"
1405         </li>
1406      </ul>
1407      <h2 id="rfc.section.D.15"><a href="#rfc.section.D.15">D.15</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p5-range-13</a></h2>
1408      <p id="rfc.section.D.15.p.1">Closed issues: </p>
1409      <ul>
1410         <li> &lt;<a href=""></a>&gt;: "untangle ABNFs for header fields"
1411         </li>
1412      </ul>
1413      <h2 id="rfc.section.D.16"><a href="#rfc.section.D.16">D.16</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p5-range-14</a></h2>
1414      <p id="rfc.section.D.16.p.1">None.</p>
1415      <h2 id="rfc.section.D.17"><a href="#rfc.section.D.17">D.17</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p5-range-15</a></h2>
1416      <p id="rfc.section.D.17.p.1">Closed issues: </p>
1417      <ul>
1418         <li> &lt;<a href=""></a>&gt;: "Security consideration: range flooding"
1419         </li>
1420      </ul>
1421      <h2 id="rfc.section.D.18"><a href="#rfc.section.D.18">D.18</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p5-range-16</a></h2>
1422      <p id="rfc.section.D.18.p.1">Closed issues: </p>
1423      <ul>
1424         <li> &lt;<a href=""></a>&gt;: "Document HTTP's error-handling philosophy"
1425         </li>
1426         <li> &lt;<a href=""></a>&gt;: "case sensitivity of ranges in p5"
1427         </li>
1428      </ul>
1429      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1430      <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> 
1431      </p>
1432      <div class="print2col">
1433         <ul class="ind">
1434            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
1435                  <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B.1</a></li>
1436               </ul>
1437            </li>
1438            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1439                  <li>416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.4"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">5.2</a>, <a href="#rfc.xref.status.416.2">6.1</a></li>
1440               </ul>
1441            </li>
1442            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1443                  <li>Accept-Ranges header field&nbsp;&nbsp;<a href="#rfc.iref.a.1"><b>5.1</b></a>, <a href="#rfc.xref.header.accept-ranges.1">6.2</a></li>
1444               </ul>
1445            </li>
1446            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1447                  <li>Content-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.c.1"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a></li>
1448               </ul>
1449            </li>
1450            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1451                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1452                     <ul>
1453                        <li><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>5.1</b></a></li>
1454                        <li><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>5.1</b></a></li>
1455                        <li><tt>byte-content-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>5.2</b></a></li>
1456                        <li><tt>byte-range-resp-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>5.2</b></a></li>
1457                        <li><tt>byte-range-set</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>5.4.1</b></a></li>
1458                        <li><tt>byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>5.4.1</b></a></li>
1459                        <li><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>5.4.1</b></a></li>
1460                        <li><tt>bytes-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2</b></a></li>
1461                        <li><tt>Content-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>5.2</b></a></li>
1462                        <li><tt>first-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>5.4.1</b></a></li>
1463                        <li><tt>If-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>5.3</b></a></li>
1464                        <li><tt>instance-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>5.2</b></a></li>
1465                        <li><tt>last-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>5.4.1</b></a></li>
1466                        <li><tt>other-range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>2</b></a></li>
1467                        <li><tt>Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>5.4.2</b></a></li>
1468                        <li><tt>range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
1469                        <li><tt>ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>5.4.1</b></a></li>
1470                        <li><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>5.4.1</b></a></li>
1471                        <li><tt>suffix-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>5.4.1</b></a></li>
1472                     </ul>
1473                  </li>
1474               </ul>
1475            </li>
1476            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1477                  <li>Header Fields&nbsp;&nbsp;
1478                     <ul>
1479                        <li>Accept-Ranges&nbsp;&nbsp;<a href="#rfc.iref.h.1"><b>5.1</b></a>, <a href="#rfc.xref.header.accept-ranges.1">6.2</a></li>
1480                        <li>Content-Range&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.h.2"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a></li>
1481                        <li>If-Range&nbsp;&nbsp;<a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.xref.header.if-range.2">3.2</a>, <a href="#rfc.iref.h.3"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.3">5.4.2</a>, <a href="#rfc.xref.header.if-range.4">6.2</a></li>
1482                        <li>Range&nbsp;&nbsp;<a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.xref.header.range.2">2</a>, <a href="#rfc.xref.header.range.3">3.1</a>, <a href="#rfc.xref.header.range.4">3.2</a>, <a href="#rfc.iref.h.4"><b>5.4</b></a>, <a href="#rfc.xref.header.range.5">6.2</a></li>
1483                     </ul>
1484                  </li>
1485               </ul>
1486            </li>
1487            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
1488                  <li>If-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.xref.header.if-range.2">3.2</a>, <a href="#rfc.iref.i.1"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.3">5.4.2</a>, <a href="#rfc.xref.header.if-range.4">6.2</a></li>
1489               </ul>
1490            </li>
1491            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
1492                  <li>Media Type&nbsp;&nbsp;
1493                     <ul>
1494                        <li>multipart/byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>A</b></a></li>
1495                        <li>multipart/x-byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.4">A</a></li>
1496                     </ul>
1497                  </li>
1498                  <li>multipart/byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>A</b></a></li>
1499                  <li>multipart/x-byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.3">A</a></li>
1500               </ul>
1501            </li>
1502            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1503                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">8</a>, <a href="#Part1"><b>9.1</b></a><ul>
1504                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
1505                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.2.1</a></li>
1506                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a></li>
1507                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2.1</a></li>
1508                        <li><em>Section 11</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">8</a></li>
1509                     </ul>
1510                  </li>
1511                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.2.1</a>, <a href="#rfc.xref.Part2.2">1.2.1</a>, <a href="#Part2"><b>9.1</b></a><ul>
1512                        <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">1.2.1</a></li>
1513                     </ul>
1514                  </li>
1515                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2.2</a>, <a href="#rfc.xref.Part4.2">4</a>, <a href="#rfc.xref.Part4.3">4</a>, <a href="#rfc.xref.Part4.4">5.3</a>, <a href="#rfc.xref.Part4.5">5.3</a>, <a href="#Part4"><b>9.1</b></a><ul>
1516                        <li><em>Section 2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.3">4</a>, <a href="#rfc.xref.Part4.4">5.3</a>, <a href="#rfc.xref.Part4.5">5.3</a></li>
1517                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2.2</a>, <a href="#rfc.xref.Part4.2">4</a></li>
1518                     </ul>
1519                  </li>
1520               </ul>
1521            </li>
1522            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1523                  <li>Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.xref.header.range.2">2</a>, <a href="#rfc.xref.header.range.3">3.1</a>, <a href="#rfc.xref.header.range.4">3.2</a>, <a href="#rfc.iref.r.1"><b>5.4</b></a>, <a href="#rfc.xref.header.range.5">6.2</a></li>
1524                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#RFC2046"><b>9.1</b></a>, <a href="#rfc.xref.RFC2046.1">A</a>, <a href="#rfc.xref.RFC2046.2">A</a><ul>
1525                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">A</a></li>
1526                     </ul>
1527                  </li>
1528                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>9.1</b></a></li>
1529                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#RFC2616"><b>9.2</b></a>, <a href="#rfc.xref.RFC2616.1">D.1</a></li>
1530                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">6.2</a>, <a href="#RFC3864"><b>9.2</b></a></li>
1531                  <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#RFC4288"><b>9.2</b></a>, <a href="#rfc.xref.RFC4288.1">A</a></li>
1532                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a>, <a href="#RFC5226"><b>9.2</b></a><ul>
1533                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a></li>
1534                     </ul>
1535                  </li>
1536                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#RFC5234"><b>9.1</b></a><ul>
1537                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
1538                     </ul>
1539                  </li>
1540               </ul>
1541            </li>
1542            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
1543                  <li>Status Codes&nbsp;&nbsp;
1544                     <ul>
1545                        <li>206 Partial Content&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B.1</a></li>
1546                        <li>416 Requested Range Not Satisfiable&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">5.2</a>, <a href="#rfc.xref.status.416.2">6.1</a></li>
1547                     </ul>
1548                  </li>
1549               </ul>
1550            </li>
1551         </ul>
1552      </div>
1553   </body>
Note: See TracBrowser for help on using the repository browser.