source: draft-ietf-httpbis/18/p5-range.html @ 2726

Last change on this file since 2726 was 2726, checked in by julian.reschke@…, 9 years ago

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

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 112.5 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: cambria, helvetica, arial, sans-serif;
27  font-size: 11pt;
28  margin-right: 2em;
30cite {
31  font-style: normal;
33div.note {
34  margin-left: 2em;
36dl {
37  margin-left: 2em;
39ul.empty {
40  list-style-type: none;
42ul.empty li {
43  margin-top: .5em;
45dl p {
46  margin-left: 0em;
48dt {
49  margin-top: .5em;
51h1 {
52  font-size: 130%;
53  line-height: 21pt;
54  page-break-after: avoid;
55} {
57  page-break-before: always;
59h2 {
60  font-size: 120%;
61  line-height: 15pt;
62  page-break-after: avoid;
64h3 {
65  font-size: 110%;
66  page-break-after: avoid;
68h4, h5, h6 {
69  page-break-after: avoid;
71h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
72  color: black;
74img {
75  margin-left: 3em;
77li {
78  margin-left: 2em;
80ol {
81  margin-left: 2em;
82} {
84  list-style-type: lower-alpha;
85} {
87  list-style-type: upper-alpha;
89ol p {
90  margin-left: 0em;
92p {
93  margin-left: 2em;
95pre {
96  margin-left: 3em;
97  background-color: lightyellow;
98  padding: .25em;
99  page-break-inside: avoid;
101pre.text2 {
102  border-style: dotted;
103  border-width: 1px;
104  background-color: #f0f0f0;
105  width: 69em;
107pre.inline {
108  background-color: white;
109  padding: 0em;
111pre.text {
112  border-style: dotted;
113  border-width: 1px;
114  background-color: #f8f8f8;
115  width: 69em;
117pre.drawing {
118  border-style: solid;
119  border-width: 1px;
120  background-color: #f8f8f8;
121  padding: 2em;
123table {
124  margin-left: 2em;
125} {
127  vertical-align: top;
128  border-color: gray;
129} th {
131  border-color: gray;
132} td {
134  border-color: gray;
136table.all {
137  border-style: solid;
138  border-width: 2px;
140table.full {
141  border-style: solid;
142  border-width: 2px;
143} td {
145  vertical-align: top;
147table.all td {
148  border-style: solid;
149  border-width: 1px;
151table.full td {
152  border-style: none solid;
153  border-width: 1px;
154} th {
156  vertical-align: top;
158table.all th {
159  border-style: solid;
160  border-width: 1px;
162table.full th {
163  border-style: solid;
164  border-width: 1px 1px 2px 1px;
166table.headers th {
167  border-style: none none solid none;
168  border-width: 2px;
170table.left {
171  margin-right: auto;
173table.right {
174  margin-left: auto;
175} {
177  margin-left: auto;
178  margin-right: auto;
180caption {
181  caption-side: bottom;
182  font-weight: bold;
183  font-size: 10pt;
184  margin-top: .5em;
187table.header {
188  border-spacing: 1px;
189  width: 95%;
190  font-size: 11pt;
191  color: white;
192} {
194  vertical-align: top;
196td.topnowrap {
197  vertical-align: top;
198  white-space: nowrap;
200table.header td {
201  background-color: gray;
202  width: 50%;
204table.header a {
205  color: white;
207td.reference {
208  vertical-align: top;
209  white-space: nowrap;
210  padding-right: 1em;
212thead {
213  display:table-header-group;
215ul.toc, ul.toc ul {
216  list-style: none;
217  margin-left: 1.5em;
218  padding-left: 0em;
220ul.toc li {
221  line-height: 150%;
222  font-weight: bold;
223  margin-left: 0em;
225ul.toc li li {
226  line-height: normal;
227  font-weight: normal;
228  font-size: 10pt;
229  margin-left: 0em;
231li.excluded {
232  font-size: 0pt;
234ul p {
235  margin-left: 0em;
237.title, .filename, h1, h2, h3, h4 {
238  font-family: candara, helvetica, arial, sans-serif;
240samp, tt, code, pre {
241  font: consolas, monospace;
243ul.ind, ul.ind ul {
244  list-style: none;
245  margin-left: 1.5em;
246  padding-left: 0em;
247  page-break-before: avoid;
249ul.ind li {
250  font-weight: bold;
251  line-height: 200%;
252  margin-left: 0em;
254ul.ind li li {
255  font-weight: normal;
256  line-height: 150%;
257  margin-left: 0em;
259.avoidbreak {
260  page-break-inside: avoid;
262.bcp14 {
263  font-style: normal;
264  text-transform: lowercase;
265  font-variant: small-caps;
267.comment {
268  background-color: yellow;
269} {
271  text-align: center;
273.error {
274  color: red;
275  font-style: italic;
276  font-weight: bold;
278.figure {
279  font-weight: bold;
280  text-align: center;
281  font-size: 10pt;
283.filename {
284  color: #333333;
285  font-size: 75%;
286  font-weight: bold;
287  line-height: 21pt;
288  text-align: center;
290.fn {
291  font-weight: bold;
293.left {
294  text-align: left;
296.right {
297  text-align: right;
299.title {
300  color: green;
301  font-size: 150%;
302  line-height: 18pt;
303  font-weight: bold;
304  text-align: center;
305  margin-top: 36pt;
307.warning {
308  font-size: 130%;
309  background-color: yellow;
313@media print {
314  .noprint {
315    display: none;
316  }
318  a {
319    color: black;
320    text-decoration: none;
321  }
323  table.header {
324    width: 90%;
325  }
327  td.header {
328    width: 50%;
329    color: black;
330    background-color: white;
331    vertical-align: top;
332    font-size: 110%;
333  }
335  ul.toc a:nth-child(2)::after {
336    content: leader('.') target-counter(attr(href), page);
337  }
339  ul.ind li li a {
340    content: target-counter(attr(href), page);
341  }
343  .print2col {
344    column-count: 2;
345    -moz-column-count: 2;
346    column-fill: auto;
347  }
350@page {
351  @top-left {
352       content: "Internet-Draft";
353  }
354  @top-right {
355       content: "January 2012";
356  }
357  @top-center {
358       content: "HTTP/1.1, Part 5";
359  }
360  @bottom-left {
361       content: "Fielding, et al.";
362  }
363  @bottom-center {
364       content: "Expires July 7, 2012";
365  }
366  @bottom-right {
367       content: "[Page " counter(page) "]";
368  }
371@page:first {
372    @top-left {
373      content: normal;
374    }
375    @top-right {
376      content: normal;
377    }
378    @top-center {
379      content: normal;
380    }
382</style><link rel="Contents" href="#rfc.toc">
383      <link rel="Author" href="#rfc.authors">
384      <link rel="Copyright" href="#rfc.copyrightnotice">
385      <link rel="Index" href="#rfc.index">
386      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
387      <link rel="Chapter" title="2 Range Units" href="#rfc.section.2">
388      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
389      <link rel="Chapter" title="4 Combining Ranges" href="#rfc.section.4">
390      <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5">
391      <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6">
392      <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7">
393      <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8">
394      <link rel="Chapter" href="#rfc.section.9" title="9 References">
395      <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
396      <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B">
397      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
398      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
399      <link href="p4-conditional.html" rel="prev">
400      <link href="p6-cache.html" rel="next">
401      <meta name="generator" content=", Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica">
402      <link rel="schema.dct" href="">
403      <meta name="dct.creator" content="Fielding, R.">
404      <meta name="dct.creator" content="Gettys, J.">
405      <meta name="dct.creator" content="Mogul, J.">
406      <meta name="dct.creator" content="Frystyk, H.">
407      <meta name="dct.creator" content="Masinter, L.">
408      <meta name="dct.creator" content="Leach, P.">
409      <meta name="dct.creator" content="Berners-Lee, T.">
410      <meta name="dct.creator" content="Lafon, Y.">
411      <meta name="dct.creator" content="Reschke, J. F.">
412      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-18">
413      <meta name="dct.issued" scheme="ISO8601" content="2012-01-04">
414      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
415      <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.">
416      <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.">
417   </head>
418   <body>
419      <table class="header">
420         <tbody>
421            <tr>
422               <td class="left">HTTPbis Working Group</td>
423               <td class="right">R. Fielding, Editor</td>
424            </tr>
425            <tr>
426               <td class="left">Internet-Draft</td>
427               <td class="right">Adobe</td>
428            </tr>
429            <tr>
430               <td class="left">Obsoletes: <a href="">2616</a> (if approved)
431               </td>
432               <td class="right">J. Gettys</td>
433            </tr>
434            <tr>
435               <td class="left">Intended status: Standards Track</td>
436               <td class="right">Alcatel-Lucent</td>
437            </tr>
438            <tr>
439               <td class="left">Expires: July 7, 2012</td>
440               <td class="right">J. Mogul</td>
441            </tr>
442            <tr>
443               <td class="left"></td>
444               <td class="right">HP</td>
445            </tr>
446            <tr>
447               <td class="left"></td>
448               <td class="right">H. Frystyk</td>
449            </tr>
450            <tr>
451               <td class="left"></td>
452               <td class="right">Microsoft</td>
453            </tr>
454            <tr>
455               <td class="left"></td>
456               <td class="right">L. Masinter</td>
457            </tr>
458            <tr>
459               <td class="left"></td>
460               <td class="right">Adobe</td>
461            </tr>
462            <tr>
463               <td class="left"></td>
464               <td class="right">P. Leach</td>
465            </tr>
466            <tr>
467               <td class="left"></td>
468               <td class="right">Microsoft</td>
469            </tr>
470            <tr>
471               <td class="left"></td>
472               <td class="right">T. Berners-Lee</td>
473            </tr>
474            <tr>
475               <td class="left"></td>
476               <td class="right">W3C/MIT</td>
477            </tr>
478            <tr>
479               <td class="left"></td>
480               <td class="right">Y. Lafon, Editor</td>
481            </tr>
482            <tr>
483               <td class="left"></td>
484               <td class="right">W3C</td>
485            </tr>
486            <tr>
487               <td class="left"></td>
488               <td class="right">J. Reschke, Editor</td>
489            </tr>
490            <tr>
491               <td class="left"></td>
492               <td class="right">greenbytes</td>
493            </tr>
494            <tr>
495               <td class="left"></td>
496               <td class="right">January 4, 2012</td>
497            </tr>
498         </tbody>
499      </table>
500      <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-18</span></p>
501      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
502      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
503         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
504         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
505      </p>
506      <p>Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.</p>
507      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
508      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (, which is archived
509         at &lt;<a href=""></a>&gt;.
510      </p>
511      <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;.
512      </p>
513      <p>The changes in this draft are summarized in <a href="#changes.since.17" title="Since draft-ietf-httpbis-p5-range-17">Appendix&nbsp;D.19</a>.
514      </p>
515      <div id="rfc.status">
516         <h1><a href="#rfc.status">Status of This Memo</a></h1>
517         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
518         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
519            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href=""></a>.
520         </p>
521         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
522            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
523            in progress”.
524         </p>
525         <p>This Internet-Draft will expire on July 7, 2012.</p>
526      </div>
527      <div id="rfc.copyrightnotice">
528         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
529         <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
530         <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
531            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
532            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
533            BSD License.
534         </p>
535         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
536            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
537            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
538            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
539            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
540            it into languages other than English.
541         </p>
542      </div>
543      <hr class="noprint">
544      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
545      <ul class="toc">
546         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
547               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
548               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
549                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
550                     <li><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
551                  </ul>
552               </li>
553            </ul>
554         </li>
555         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a><ul>
556               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registry">Range Specifier Registry</a></li>
557            </ul>
558         </li>
559         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
560               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
561               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
562            </ul>
563         </li>
564         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
565         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
566               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
567               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
568               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
569               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
570                     <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
571                     <li><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
572                  </ul>
573               </li>
574            </ul>
575         </li>
576         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
577               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
578               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
579               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registration">Range Specifier Registration</a></li>
580            </ul>
581         </li>
582         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
583               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#overlapping.ranges">Overlapping Ranges</a></li>
584            </ul>
585         </li>
586         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
587         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
588               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
589               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
590            </ul>
591         </li>
592         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="">Internet Media Type multipart/byteranges</a></li>
593         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
594               <li><a href="#rfc.section.B.1">B.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
595            </ul>
596         </li>
597         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
598         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
599               <li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC 2616</a></li>
600               <li><a href="#rfc.section.D.2">D.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p5-range-00</a></li>
601               <li><a href="#rfc.section.D.3">D.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p5-range-01</a></li>
602               <li><a href="#rfc.section.D.4">D.4</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></li>
603               <li><a href="#rfc.section.D.5">D.5</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></li>
604               <li><a href="#rfc.section.D.6">D.6</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></li>
605               <li><a href="#rfc.section.D.7">D.7</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></li>
606               <li><a href="#rfc.section.D.8">D.8</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></li>
607               <li><a href="#rfc.section.D.9">D.9</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></li>
608               <li><a href="#rfc.section.D.10">D.10</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></li>
609               <li><a href="#rfc.section.D.11">D.11</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></li>
610               <li><a href="#rfc.section.D.12">D.12</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></li>
611               <li><a href="#rfc.section.D.13">D.13</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></li>
612               <li><a href="#rfc.section.D.14">D.14</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p5-range-12</a></li>
613               <li><a href="#rfc.section.D.15">D.15</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p5-range-13</a></li>
614               <li><a href="#rfc.section.D.16">D.16</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p5-range-14</a></li>
615               <li><a href="#rfc.section.D.17">D.17</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p5-range-15</a></li>
616               <li><a href="#rfc.section.D.18">D.18</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p5-range-16</a></li>
617               <li><a href="#rfc.section.D.19">D.19</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p5-range-17</a></li>
618            </ul>
619         </li>
620         <li><a href="#rfc.index">Index</a></li>
621         <li><a href="#rfc.authors">Authors' Addresses</a></li>
622      </ul>
623      <div id="introduction">
624         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
625         <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
626            has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
627            rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
628            request only a subset of a larger representation, such as a single page of a very large document or only part of an image
629            to be rendered by a device with limited local storage.
630         </p>
631         <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
632            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
633            request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
634            full responses by intermediate caches that might not implement the feature.
635         </p>
636         <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
637            requests for byte ranges.
638         </p>
639         <div id="intro.conformance.and.error.handling">
640            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></h2>
641            <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"
642               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>.
643            </p>
644            <p id="rfc.section.1.1.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
645               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.
646            </p>
647            <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
648               SHOULD-level requirements are relevant here, unless one of the documented exceptions is applicable.
649            </p>
650            <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.
651            </p>
652            <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
653               mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
654               different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
655               Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type of
656               error recovery could lead to dangerous consequences.
657            </p>
658         </div>
659         <div id="notation">
660            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
661            <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.
662            </p>
663            <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
664               (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
665               character).
666            </p>
667            <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>.
668            </p>
669            <div id="core.rules">
670               <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a href="#core.rules">Core Rules</a></h3>
671               <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>:
672               </p>
673               <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;
674  <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;
675  <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;
677            <div id="abnf.dependencies">
678               <h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
679               <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
680               <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;
682         </div>
683      </div>
684      <div id="range.units">
685         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#range.units">Range Units</a></h1>
686         <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
687            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.
688         </p>
689         <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>
690  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
691  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a>
692</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
693            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>.
694         </p>
695         <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.
696         </p>
697         <div id="range.specifier.registry">
698            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#range.specifier.registry">Range Specifier Registry</a></h2>
699            <p id="rfc.section.2.1.p.1">The HTTP Range Specifier Registry defines the name space for the range specifier names.</p>
700            <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
701            </p>
702            <ul>
703               <li>Name</li>
704               <li>Description</li>
705               <li>Pointer to specification text</li>
706            </ul>
707            <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>).
708            </p>
709            <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href=""></a>&gt;.
710            </p>
711         </div>
712      </div>
713      <div id="status.code.definitions">
714         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#status.code.definitions">Status Code Definitions</a></h1>
715         <div id="status.206">
716            <div id="rfc.iref.2.1"></div>
717            <div id="rfc.iref.s.1"></div>
718            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#status.206">206 Partial Content</a></h2>
719            <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.
720            </p>
721            <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
722            </p>
723            <ul>
724               <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
725                  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.
726               </li>
727               <li>Date</li>
728               <li>Cache-Control, ETag, Expires, Content-Location, Last-Modified, and/or Vary, if the header field would have been sent in a
729                  200 response to the same request
730               </li>
731            </ul>
732            <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.
733            </p>
734         </div>
735         <div id="status.416">
736            <div id="rfc.iref.4.1"></div>
737            <div id="rfc.iref.s.2"></div>
738            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></h2>
739            <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
740               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
741               length of the selected resource.)
742            </p>
743            <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.
744            </p>
745         </div>
746      </div>
747      <div id="combining.byte.ranges">
748         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></h1>
749         <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
750            one or more Range specifications. After several such transfers, a client might have received several ranges of the same representation.
751            These ranges can only be safely combined if they all have in common the same strong validator, where "strong validator" is
752            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>.
753         </p>
754         <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
755            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,
756            then this new response corresponds to a new representation and <em class="bcp14">MUST NOT</em> be combined with the existing stored responses.
757         </p>
758         <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
759            response and replace those of the matching stored responses.
760         </p>
761         <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
762            the combined response header fields consist of the most recent 200 response's header fields. If all of the matching stored
763            responses are 206 responses, then the stored response with the most header fields is used as the source of header fields for
764            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
765            header fields in the stored response.
766         </p>
767         <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
768            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,
769            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
770            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.
771         </p>
772      </div>
773      <div id="header.field.definitions">
774         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#header.field.definitions">Header Field Definitions</a></h1>
775         <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>
776         <div id="header.accept-ranges">
777            <div id="rfc.iref.a.1"></div>
778            <div id="rfc.iref.h.1"></div>
779            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></h2>
780            <p id="rfc.section.5.1.p.1">The "Accept-Ranges" header field allows a resource to indicate its acceptance of range requests.</p>
781            <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>
782  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
783</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
784            </p>
785            <div id="rfc.figure.u.5"></div><pre class="text">  Accept-Ranges: bytes
786</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>.
787            </p>
788            <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
789            </p>
790            <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: none
791</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
792         </div>
793         <div id="header.content-range">
794            <div id="rfc.iref.c.1"></div>
795            <div id="rfc.iref.h.2"></div>
796            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#header.content-range">Content-Range</a></h2>
797            <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
798               body is intended to be applied.
799            </p>
800            <p id="rfc.section.5.2.p.2">Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
801            </p>
802            <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>
803                          / <a href="#header.content-range" class="smpl">other-content-range-spec</a>
805  <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>
806                            <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> "/"
807                            ( <a href="#header.content-range" class="smpl">instance-length</a> / "*" )
809  <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>)
810                          / "*"
812  <a href="#header.content-range" class="smpl">instance-length</a>         = 1*<a href="#notation" class="smpl">DIGIT</a>
814  <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>
815                             <a href="#header.content-range" class="smpl">other-range-resp-spec</a>
816  <a href="#header.content-range" class="smpl">other-range-resp-spec</a>    = *<a href="#notation" class="smpl">CHAR</a>
817</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
818               "*" character means that the instance-length is unknown at the time when the response was generated.
819            </p>
820            <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.
821            </p>
822            <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
823               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.
824            </p>
825            <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
826               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 "*".
827            </p>
828            <p id="rfc.section.5.2.p.8">The "Content-Range" header field has no meaning for status codes that do not explicitly describe its semantic. Currently,
829               only status codes 206 (Partial Content) and 416 (Requested range not satisfiable) describe the meaning of this header field.
830            </p>
831            <p id="rfc.section.5.2.p.9">Examples of byte-content-range-spec values, assuming that the representation contains a total of 1234 bytes: </p>
832            <ul>
833               <li>The first 500 bytes: <span id="rfc.figure.u.8"></span><pre class="text">  bytes 0-499/1234
834</pre> </li>
835               <li>The second 500 bytes: <span id="rfc.figure.u.9"></span><pre class="text">  bytes 500-999/1234
836</pre> </li>
837               <li>All except for the first 500 bytes: <span id="rfc.figure.u.10"></span><pre class="text">  bytes 500-1233/1234
838</pre> </li>
839               <li>The last 500 bytes: <span id="rfc.figure.u.11"></span><pre class="text">  bytes 734-1233/1234
840</pre> </li>
841            </ul>
842            <p id="rfc.section.5.2.p.10">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
843               a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header field,
844               and a Content-Length header field showing the number of bytes actually transferred. For example,
845            </p>
846            <div id="rfc.figure.u.12"></div><pre class="text">  HTTP/1.1 206 Partial Content
847  Date: Wed, 15 Nov 1995 06:25:24 GMT
848  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
849  Content-Range: bytes 21010-47021/47022
850  Content-Length: 26012
851  Content-Type: image/gif
852</pre><p id="rfc.section.5.2.p.12">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
853               ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
854               as defined in <a href="" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
855            </p>
856            <p id="rfc.section.5.2.p.13">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.
857            </p>
858            <p id="rfc.section.5.2.p.14">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.
859            </p>
860            <p id="rfc.section.5.2.p.15">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
861               the full representation).
862            </p>
863            <p id="rfc.section.5.2.p.16">If the server receives a request (other than one including an If-Range header field) with an unsatisfiable Range header field
864               (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
865               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>).
866            </p>
867            <div class="note" id="rfc.section.5.2.p.17">
868               <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
869                  an unsatisfiable Range header field, since not all servers implement this header field.
870               </p>
871            </div>
872         </div>
873         <div id="header.if-range">
874            <div id="rfc.iref.i.1"></div>
875            <div id="rfc.iref.h.3"></div>
876            <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#header.if-range">If-Range</a></h2>
877            <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
878               could use the Range header field with a conditional GET (using either or both of If-Unmodified-Since and If-Match.) However,
879               if the condition fails because the representation has been modified, the client would then have to make a second request to
880               obtain the entire current representation.
881            </p>
882            <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
883               is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation".
884            </p>
885            <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>
886</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
887               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>.
888            </p>
889            <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
890               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.)
891            </p>
892            <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.
893            </p>
894            <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
895               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,
896               then the server <em class="bcp14">SHOULD</em> send the entire representation using a 200 (OK) response.
897            </p>
898         </div>
899         <div id="header.range">
900            <div id="rfc.iref.r.1"></div>
901            <div id="rfc.iref.h.4"></div>
902            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.range">Range</a></h2>
903            <div id="byte.ranges">
904               <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a href="#byte.ranges">Byte Ranges</a></h3>
905               <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
906                  representation. (However, not all clients and servers need to support byte-range operations.)
907               </p>
908               <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
909                  message-body).
910               </p>
911               <div id="rule.ranges-specifier">
912                  <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.
913                  </p>
914               </div>
915               <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>
916  <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> )
917  <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> ]
918  <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
919  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
920</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
921                  gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
922                  at zero.
923               </p>
924               <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
925                  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.
926               </p>
927               <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
928                  body, last-byte-pos is taken to be equal to one less than the current length of the representation in bytes.
929               </p>
930               <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>
931               <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>
932  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
933</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
934                  value. (That is, this form specifies the last N bytes of a representation.) If the representation is shorter than the specified
935                  suffix-length, the entire representation is used.
936               </p>
937               <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
938                  length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set
939                  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.
940               </p>
941               <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p>
942               <ul>
943                  <li>The first 500 bytes (byte offsets 0-499, inclusive): <span id="rfc.figure.u.16"></span><pre class="text">  bytes=0-499
944</pre> </li>
945                  <li>The second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.17"></span><pre class="text">  bytes=500-999
946</pre> </li>
947                  <li>The final 500 bytes (byte offsets 9500-9999, inclusive): <span id="rfc.figure.u.18"></span><pre class="text">  bytes=-500
948</pre> Or: <span id="rfc.figure.u.19"></span><pre class="text">  bytes=9500-
949</pre> </li>
950                  <li>The first and last bytes only (bytes 0 and 9999): <span id="rfc.figure.u.20"></span><pre class="text">  bytes=0-0,-1
951</pre> </li>
952                  <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.21"></span><pre class="text">  bytes=500-600,601-999
953  bytes=500-700,601-999
954</pre> </li>
955               </ul>
956            </div>
957            <div id="range.retrieval.requests">
958               <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></h3>
959               <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
960                  body, instead of the entire representation body.
961               </p>
962               <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>
963  <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>
964  <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#notation" class="smpl">CHAR</a>
965</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,
966                  since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
967                  representations.
968               </p>
969               <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>
970               <ul>
971                  <li>The presence of a Range header field in an unconditional GET modifies what is returned if the GET is otherwise successful.
972                     In other words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
973                  </li>
974                  <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,
975                     or one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
976                     is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
977                  </li>
978               </ul>
979               <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.
980               </p>
981               <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
982                  representation in reply, it <em class="bcp14">MAY</em> only return the requested range to its client.
983               </p>
984            </div>
985         </div>
986      </div>
987      <div id="IANA.considerations">
988         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
989         <div id="status.code.registration">
990            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h2>
991            <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:
992            </p>
993            <div id="rfc.table.1">
994               <div id="iana.status.code.registration.table"></div>
995               <table class="tt full left" cellpadding="3" cellspacing="0">
996                  <thead>
997                     <tr>
998                        <th>Value</th>
999                        <th>Description</th>
1000                        <th>Reference</th>
1001                     </tr>
1002                  </thead>
1003                  <tbody>
1004                     <tr>
1005                        <td class="left">206</td>
1006                        <td class="left">Partial Content</td>
1007                        <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;3.1</a>
1008                        </td>
1009                     </tr>
1010                     <tr>
1011                        <td class="left">416</td>
1012                        <td class="left">Requested Range Not Satisfiable</td>
1013                        <td class="left"><a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>
1014                        </td>
1015                     </tr>
1016                  </tbody>
1017               </table>
1018            </div>
1019         </div>
1020         <div id="header.field.registration">
1021            <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
1022            <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>):
1023            </p>
1024            <div id="rfc.table.2">
1025               <div id="iana.header.registration.table"></div>
1026               <table class="tt full left" cellpadding="3" cellspacing="0">
1027                  <thead>
1028                     <tr>
1029                        <th>Header Field Name</th>
1030                        <th>Protocol</th>
1031                        <th>Status</th>
1032                        <th>Reference</th>
1033                     </tr>
1034                  </thead>
1035                  <tbody>
1036                     <tr>
1037                        <td class="left">Accept-Ranges</td>
1038                        <td class="left">http</td>
1039                        <td class="left">standard</td>
1040                        <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
1041                        </td>
1042                     </tr>
1043                     <tr>
1044                        <td class="left">Content-Range</td>
1045                        <td class="left">http</td>
1046                        <td class="left">standard</td>
1047                        <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
1048                        </td>
1049                     </tr>
1050                     <tr>
1051                        <td class="left">If-Range</td>
1052                        <td class="left">http</td>
1053                        <td class="left">standard</td>
1054                        <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">Section&nbsp;5.3</a>
1055                        </td>
1056                     </tr>
1057                     <tr>
1058                        <td class="left">Range</td>
1059                        <td class="left">http</td>
1060                        <td class="left">standard</td>
1061                        <td class="left"><a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a>
1062                        </td>
1063                     </tr>
1064                  </tbody>
1065               </table>
1066            </div>
1067            <p id="rfc.section.6.2.p.2">The change controller is: "IETF ( - Internet Engineering Task Force".</p>
1068         </div>
1069         <div id="range.specifier.registration">
1070            <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a href="#range.specifier.registration">Range Specifier Registration</a></h2>
1071            <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.
1072            </p>
1073            <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:
1074            </p>
1075            <div id="rfc.table.3">
1076               <div id="iana.range.specifiers.table"></div>
1077               <table class="tt full left" cellpadding="3" cellspacing="0">
1078                  <thead>
1079                     <tr>
1080                        <th>Range Specifier Name</th>
1081                        <th>Description</th>
1082                        <th>Reference</th>
1083                     </tr>
1084                  </thead>
1085                  <tbody>
1086                     <tr>
1087                        <td class="left">bytes</td>
1088                        <td class="left">a range of octets</td>
1089                        <td class="left">(this specification)</td>
1090                     </tr>
1091                  </tbody>
1092               </table>
1093            </div>
1094            <p id="rfc.section.6.3.p.3">The change controller is: "IETF ( - Internet Engineering Task Force".</p>
1095         </div>
1096      </div>
1097      <div id="security.considerations">
1098         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
1099         <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
1100            as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
1101            make some suggestions for reducing security risks.
1102         </p>
1103         <div id="overlapping.ranges">
1104            <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#overlapping.ranges">Overlapping Ranges</a></h2>
1105            <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
1106               of the complete resource representation.
1107            </p>
1108         </div>
1109      </div>
1110      <div id="acks">
1111         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
1112         <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>.
1113         </p>
1114      </div>
1115      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
1116      </h1>
1117      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
1118      </h2>
1119      <table>
1120         <tr>
1121            <td class="reference"><b id="Part1">[Part1]</b></td>
1122            <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-18 (work in progress), January&nbsp;2012.
1123            </td>
1124         </tr>
1125         <tr>
1126            <td class="reference"><b id="Part2">[Part2]</b></td>
1127            <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-18 (work in progress), January&nbsp;2012.
1128            </td>
1129         </tr>
1130         <tr>
1131            <td class="reference"><b id="Part4">[Part4]</b></td>
1132            <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-18 (work in progress), January&nbsp;2012.
1133            </td>
1134         </tr>
1135         <tr>
1136            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
1137            <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.
1138            </td>
1139         </tr>
1140         <tr>
1141            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1142            <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.
1143            </td>
1144         </tr>
1145         <tr>
1146            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1147            <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.
1148            </td>
1149         </tr>
1150      </table>
1151      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
1152      </h2>
1153      <table>
1154         <tr>
1155            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1156            <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.
1157            </td>
1158         </tr>
1159         <tr>
1160            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1161            <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.
1162            </td>
1163         </tr>
1164         <tr>
1165            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
1166            <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.
1167            </td>
1168         </tr>
1169         <tr>
1170            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
1171            <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.
1172            </td>
1173         </tr>
1174      </table>
1175      <div id="">
1176         <div id="rfc.iref.m.1"></div>
1177         <div id="rfc.iref.m.2"></div>
1178         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="">Internet Media Type multipart/byteranges</a></h1>
1179         <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
1180            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>.
1181         </p>
1182         <div class="note" id="rfc.section.A.p.2">
1183            <p><b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
1184            </p>
1185         </div>
1186         <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
1187            required boundary parameter specifies the boundary string used to separate each body-part.
1188         </p>
1189         <p id="rfc.section.A.p.4"></p>
1190         <dl>
1191            <dt>Type name:</dt>
1192            <dd>multipart</dd>
1193            <dt>Subtype name:</dt>
1194            <dd>byteranges</dd>
1195            <dt>Required parameters:</dt>
1196            <dd>boundary</dd>
1197            <dt>Optional parameters:</dt>
1198            <dd>none</dd>
1199            <dt>Encoding considerations:</dt>
1200            <dd>only "7bit", "8bit", or "binary" are permitted</dd>
1201            <dt>Security considerations:</dt>
1202            <dd>none</dd>
1203            <dt>Interoperability considerations:</dt>
1204            <dd>none</dd>
1205            <dt>Published specification:</dt>
1206            <dd>This specification (see <a href="" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
1207            </dd>
1208            <dt>Applications that use this media type:</dt>
1209            <dt>Additional information:</dt>
1210            <dd>
1211               <dl>
1212                  <dt>Magic number(s):</dt>
1213                  <dd>none</dd>
1214                  <dt>File extension(s):</dt>
1215                  <dd>none</dd>
1216                  <dt>Macintosh file type code(s):</dt>
1217                  <dd>none</dd>
1218               </dl>
1219            </dd>
1220            <dt>Person and email address to contact for further information:</dt>
1221            <dd>See Authors Section.</dd>
1222            <dt>Intended usage:</dt>
1223            <dd>COMMON</dd>
1224            <dt>Restrictions on usage:</dt>
1225            <dd>none</dd>
1226            <dt>Author/Change controller:</dt>
1227            <dd>IESG</dd>
1228         </dl>
1229         <div id="rfc.figure.u.23"></div>
1230         <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
1231  Date: Wed, 15 Nov 1995 06:25:24 GMT
1232  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
1233  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1236  Content-type: application/pdf
1237  Content-range: bytes 500-999/8000
1239  ...the first range...
1241  Content-type: application/pdf
1242  Content-range: bytes 7000-7999/8000
1244  ...the second range
1246</pre><div id="rfc.figure.u.24"></div>
1247         <p>Other example:</p><pre class="text">  HTTP/1.1 206 Partial Content
1248  Date: Tue, 14 Nov 1995 06:25:24 GMT
1249  Last-Modified: Tue, 14 July 04:58:08 GMT
1250  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1253  Content-type: video/example
1254  Content-range: exampleunit 1.2-4.3/25
1256  ...the first range...
1258  Content-type: video/example
1259  Content-range: exampleunit 11.2-14.3/25
1261  ...the second range
1263</pre><p id="rfc.section.A.p.7">Notes: </p>
1264         <ol>
1265            <li>Additional CRLFs <em class="bcp14">MAY</em> precede the first boundary string in the body.
1266            </li>
1267            <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.
1268            </li>
1269            <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.
1270            </li>
1271         </ol>
1272      </div>
1273      <div id="compatibility">
1274         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
1275         <div id="changes.from.rfc.2616">
1276            <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
1277            <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>)
1278            </p>
1279            <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>)
1280            </p>
1281            <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>)
1282            </p>
1283         </div>
1284      </div>
1285      <div id="collected.abnf">
1286         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
1287         <div id="rfc.figure.u.25"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
1289<a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range-spec / other-content-range-spec
1291<a href="#core.rules" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 8&gt;
1293<a href="#header.if-range" class="smpl">If-Range</a> = entity-tag / HTTP-date
1295<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
1297<a href="#range.retrieval.requests" class="smpl">Range</a> = byte-ranges-specifier / other-ranges-specifier
1299<a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = ( *( "," OWS ) range-unit *( OWS "," [ OWS
1300 range-unit ] ) ) / "none"
1302<a href="#header.content-range" class="smpl">byte-content-range-spec</a> = bytes-unit SP byte-range-resp-spec "/" (
1303 instance-length / "*" )
1304<a href="#header.content-range" class="smpl">byte-range-resp-spec</a> = ( first-byte-pos "-" last-byte-pos ) / "*"
1305<a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = *( "," OWS ) ( byte-range-spec /
1306 suffix-byte-range-spec ) *( OWS "," [ OWS ( byte-range-spec /
1307 suffix-byte-range-spec ) ] )
1308<a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ]
1309<a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set
1310<a href="#range.units" class="smpl">bytes-unit</a> = "bytes"
1312<a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in [Part4], Section 2.3&gt;
1314<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT
1316<a href="#header.content-range" class="smpl">instance-length</a> = 1*DIGIT
1318<a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*DIGIT
1320<a href="#header.content-range" class="smpl">other-content-range-spec</a> = other-range-unit SP other-range-resp-spec
1321<a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *CHAR
1322<a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*CHAR
1323<a href="#range.units" class="smpl">other-range-unit</a> = token
1324<a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = other-range-unit "=" other-range-set
1326<a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit
1328<a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" suffix-length
1329<a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT
1331<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.3&gt;
1332</pre><div id="rfc.figure.u.26"></div>
1333         <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
1334; Content-Range defined but not used
1335; If-Range defined but not used
1336; Range defined but not used
1338      <div id="change.log">
1339         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
1340         <div>
1341            <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC 2616
1342            </h2>
1343            <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>.
1344            </p>
1345         </div>
1346         <div>
1347            <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
1348            </h2>
1349            <p id="rfc.section.D.2.p.1">Closed issues: </p>
1350            <ul>
1351               <li>&lt;<a href=""></a>&gt;: "Cache validators in 206 responses" (&lt;<a href=""></a>&gt;)
1352               </li>
1353               <li>&lt;<a href=""></a>&gt;: "Normative and Informative references"
1354               </li>
1355               <li>&lt;<a href=""></a>&gt;: "Normative up-to-date references"
1356               </li>
1357            </ul>
1358         </div>
1359         <div>
1360            <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
1361            </h2>
1362            <p id="rfc.section.D.3.p.1">Closed issues: </p>
1363            <ul>
1364               <li>&lt;<a href=""></a>&gt;: "Updating to RFC4288"
1365               </li>
1366            </ul>
1367            <p id="rfc.section.D.3.p.2">Ongoing work on ABNF conversion (&lt;<a href=""></a>&gt;):
1368            </p>
1369            <ul>
1370               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1371            </ul>
1372         </div>
1373         <div id="changes.since.02">
1374            <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></h2>
1375            <p id="rfc.section.D.4.p.1">Ongoing work on IANA Message Header Field Registration (&lt;<a href=""></a>&gt;):
1376            </p>
1377            <ul>
1378               <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
1379            </ul>
1380         </div>
1381         <div id="changes.since.03">
1382            <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a>&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></h2>
1383            <p id="rfc.section.D.5.p.1">None.</p>
1384         </div>
1385         <div id="changes.since.04">
1386            <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a>&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></h2>
1387            <p id="rfc.section.D.6.p.1">Closed issues: </p>
1388            <ul>
1389               <li>&lt;<a href=""></a>&gt;: "multipart/byteranges minimum number of parts"
1390               </li>
1391            </ul>
1392            <p id="rfc.section.D.6.p.2">Ongoing work on ABNF conversion (&lt;<a href=""></a>&gt;):
1393            </p>
1394            <ul>
1395               <li>Use "/" instead of "|" for alternatives.</li>
1396               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1397               <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
1398            </ul>
1399         </div>
1400         <div id="changes.since.05">
1401            <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a>&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></h2>
1402            <p id="rfc.section.D.7.p.1">Closed issues: </p>
1403            <ul>
1404               <li>&lt;<a href=""></a>&gt;: "State base for *-byte-pos and suffix-length"
1405               </li>
1406            </ul>
1407            <p id="rfc.section.D.7.p.2">Ongoing work on Custom Ranges (&lt;<a href=""></a>&gt;):
1408            </p>
1409            <ul>
1410               <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
1411            </ul>
1412            <p id="rfc.section.D.7.p.3">Final work on ABNF conversion (&lt;<a href=""></a>&gt;):
1413            </p>
1414            <ul>
1415               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
1416            </ul>
1417         </div>
1418         <div id="changes.since.06">
1419            <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a>&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></h2>
1420            <p id="rfc.section.D.8.p.1">Closed issues: </p>
1421            <ul>
1422               <li>&lt;<a href=""></a>&gt;: "base for numeric protocol elements"
1423               </li>
1424            </ul>
1425         </div>
1426         <div id="changes.since.07">
1427            <h2 id="rfc.section.D.9"><a href="#rfc.section.D.9">D.9</a>&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></h2>
1428            <p id="rfc.section.D.9.p.1">Closed issues: </p>
1429            <ul>
1430               <li>Fixed discrepancy in the If-Range definition about allowed validators.</li>
1431               <li>&lt;<a href=""></a>&gt;: "multipart/byteranges for custom range units"
1432               </li>
1433               <li>&lt;<a href=""></a>&gt;: "range unit missing from other-ranges-specifier in Range header"
1434               </li>
1435               <li>&lt;<a href=""></a>&gt;: "move IANA registrations for optional status codes"
1436               </li>
1437            </ul>
1438         </div>
1439         <div id="changes.since.08">
1440            <h2 id="rfc.section.D.10"><a href="#rfc.section.D.10">D.10</a>&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></h2>
1441            <p id="rfc.section.D.10.p.1">No significant changes.</p>
1442         </div>
1443         <div id="changes.since.09">
1444            <h2 id="rfc.section.D.11"><a href="#rfc.section.D.11">D.11</a>&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></h2>
1445            <p id="rfc.section.D.11.p.1">No significant changes.</p>
1446         </div>
1447         <div id="changes.since.10">
1448            <h2 id="rfc.section.D.12"><a href="#rfc.section.D.12">D.12</a>&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></h2>
1449            <p id="rfc.section.D.12.p.1">Closed issues: </p>
1450            <ul>
1451               <li>&lt;<a href=""></a>&gt;: "Clarify 'Requested Variant'"
1452               </li>
1453               <li>&lt;<a href=""></a>&gt;: "Clarify entity / representation / variant terminology"
1454               </li>
1455               <li>&lt;<a href=""></a>&gt;: "consider removing the 'changes from 2068' sections"
1456               </li>
1457            </ul>
1458            <p id="rfc.section.D.12.p.2">Ongoing work on Custom Ranges (&lt;<a href=""></a>&gt;):
1459            </p>
1460            <ul>
1461               <li>Add IANA registry.</li>
1462            </ul>
1463         </div>
1464         <div id="changes.since.11">
1465            <h2 id="rfc.section.D.13"><a href="#rfc.section.D.13">D.13</a>&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></h2>
1466            <p id="rfc.section.D.13.p.1">Closed issues: </p>
1467            <ul>
1468               <li>&lt;<a href=""></a>&gt;: "Caches can't be required to serve ranges"
1469               </li>
1470            </ul>
1471         </div>
1472         <div id="changes.since.12">
1473            <h2 id="rfc.section.D.14"><a href="#rfc.section.D.14">D.14</a>&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p5-range-12</a></h2>
1474            <p id="rfc.section.D.14.p.1">Closed issues: </p>
1475            <ul>
1476               <li>&lt;<a href=""></a>&gt;: "Header Classification"
1477               </li>
1478            </ul>
1479         </div>
1480         <div id="changes.since.13">
1481            <h2 id="rfc.section.D.15"><a href="#rfc.section.D.15">D.15</a>&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p5-range-13</a></h2>
1482            <p id="rfc.section.D.15.p.1">Closed issues: </p>
1483            <ul>
1484               <li>&lt;<a href=""></a>&gt;: "untangle ABNFs for header fields"
1485               </li>
1486            </ul>
1487         </div>
1488         <div id="changes.since.14">
1489            <h2 id="rfc.section.D.16"><a href="#rfc.section.D.16">D.16</a>&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p5-range-14</a></h2>
1490            <p id="rfc.section.D.16.p.1">None.</p>
1491         </div>
1492         <div id="changes.since.15">
1493            <h2 id="rfc.section.D.17"><a href="#rfc.section.D.17">D.17</a>&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p5-range-15</a></h2>
1494            <p id="rfc.section.D.17.p.1">Closed issues: </p>
1495            <ul>
1496               <li>&lt;<a href=""></a>&gt;: "Security consideration: range flooding"
1497               </li>
1498            </ul>
1499         </div>
1500         <div id="changes.since.16">
1501            <h2 id="rfc.section.D.18"><a href="#rfc.section.D.18">D.18</a>&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p5-range-16</a></h2>
1502            <p id="rfc.section.D.18.p.1">Closed issues: </p>
1503            <ul>
1504               <li>&lt;<a href=""></a>&gt;: "Document HTTP's error-handling philosophy"
1505               </li>
1506               <li>&lt;<a href=""></a>&gt;: "Content-Range on responses other than 206"
1507               </li>
1508               <li>&lt;<a href=""></a>&gt;: "case sensitivity of ranges in p5"
1509               </li>
1510            </ul>
1511         </div>
1512         <div id="changes.since.17">
1513            <h2 id="rfc.section.D.19"><a href="#rfc.section.D.19">D.19</a>&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p5-range-17</a></h2>
1514            <p id="rfc.section.D.19.p.1">None.</p>
1515         </div>
1516      </div>
1517      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1518      <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>
1519      </p>
1520      <div class="print2col">
1521         <ul class="ind">
1522            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
1523                  <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.2.1"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B.1</a></li>
1524               </ul>
1525            </li>
1526            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1527                  <li>416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">5.2</a>, <a href="#rfc.xref.status.416.2">6.1</a></li>
1528               </ul>
1529            </li>
1530            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1531                  <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>
1532               </ul>
1533            </li>
1534            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1535                  <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>
1536               </ul>
1537            </li>
1538            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1539                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1540                     <ul>
1541                        <li><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>5.1</b></a></li>
1542                        <li><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>5.1</b></a></li>
1543                        <li><tt>byte-content-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>5.2</b></a></li>
1544                        <li><tt>byte-range-resp-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>5.2</b></a></li>
1545                        <li><tt>byte-range-set</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>5.4.1</b></a></li>
1546                        <li><tt>byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>5.4.1</b></a></li>
1547                        <li><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>5.4.1</b></a></li>
1548                        <li><tt>bytes-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2</b></a></li>
1549                        <li><tt>Content-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>5.2</b></a></li>
1550                        <li><tt>first-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>5.4.1</b></a></li>
1551                        <li><tt>If-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>5.3</b></a></li>
1552                        <li><tt>instance-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>5.2</b></a></li>
1553                        <li><tt>last-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>5.4.1</b></a></li>
1554                        <li><tt>other-range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>2</b></a></li>
1555                        <li><tt>Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>5.4.2</b></a></li>
1556                        <li><tt>range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
1557                        <li><tt>ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>5.4.1</b></a></li>
1558                        <li><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>5.4.1</b></a></li>
1559                        <li><tt>suffix-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>5.4.1</b></a></li>
1560                     </ul>
1561                  </li>
1562               </ul>
1563            </li>
1564            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1565                  <li>Header Fields&nbsp;&nbsp;
1566                     <ul>
1567                        <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>
1568                        <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>
1569                        <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>
1570                        <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>
1571                     </ul>
1572                  </li>
1573               </ul>
1574            </li>
1575            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
1576                  <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>
1577               </ul>
1578            </li>
1579            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
1580                  <li>Media Type&nbsp;&nbsp;
1581                     <ul>
1582                        <li>multipart/byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>A</b></a></li>
1583                        <li>multipart/x-byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.4">A</a></li>
1584                     </ul>
1585                  </li>
1586                  <li>multipart/byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>A</b></a></li>
1587                  <li>multipart/x-byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.3">A</a></li>
1588               </ul>
1589            </li>
1590            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1591                  <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>
1592                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
1593                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.2.1</a></li>
1594                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a></li>
1595                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2.1</a></li>
1596                        <li><em>Section 11</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">8</a></li>
1597                     </ul>
1598                  </li>
1599                  <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>
1600                        <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">1.2.1</a></li>
1601                     </ul>
1602                  </li>
1603                  <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>
1604                        <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>
1605                        <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>
1606                     </ul>
1607                  </li>
1608               </ul>
1609            </li>
1610            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1611                  <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>
1612                  <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>
1613                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">A</a></li>
1614                     </ul>
1615                  </li>
1616                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>9.1</b></a></li>
1617                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#RFC2616"><b>9.2</b></a>, <a href="#rfc.xref.RFC2616.1">D.1</a></li>
1618                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">6.2</a>, <a href="#RFC3864"><b>9.2</b></a></li>
1619                  <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#RFC4288"><b>9.2</b></a>, <a href="#rfc.xref.RFC4288.1">A</a></li>
1620                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a>, <a href="#RFC5226"><b>9.2</b></a><ul>
1621                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a></li>
1622                     </ul>
1623                  </li>
1624                  <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>
1625                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
1626                     </ul>
1627                  </li>
1628               </ul>
1629            </li>
1630            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
1631                  <li>Status Codes&nbsp;&nbsp;
1632                     <ul>
1633                        <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>
1634                        <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>
1635                     </ul>
1636                  </li>
1637               </ul>
1638            </li>
1639         </ul>
1640      </div>
1641      <div class="avoidbreak">
1642         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1643         <p><b>Roy T. Fielding</b>
1644            (editor)
1645            <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1646         <p><b>Jim Gettys</b><br>Alcatel-Lucent Bell Labs<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1647         <p><b>Jeffrey C. Mogul</b><br>Hewlett-Packard Company<br>HP Labs, Large Scale Systems Group<br>1501 Page Mill Road, MS 1177<br>Palo Alto, CA&nbsp;94304<br>USA<br>Email: <a href=""></a></p>
1648         <p><b>Henrik Frystyk Nielsen</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>USA<br>Email: <a href=""></a></p>
1649         <p><b>Larry Masinter</b><br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1650         <p><b>Paul J. Leach</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>Email: <a href=""></a></p>
1651         <p><b>Tim Berners-Lee</b><br>World Wide Web Consortium<br>MIT Computer Science and Artificial Intelligence Laboratory<br>The Stata Center, Building 32<br>32 Vassar Street<br>Cambridge, MA&nbsp;02139<br>USA<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1652         <p><b>Yves Lafon</b>
1653            (editor)
1654            <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM&nbsp;06902<br>France<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1655         <p><b>Julian F. Reschke</b>
1656            (editor)
1657            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Phone: <a href="tel:+492512807760">+49 251 2807760</a><br>Fax: <a href="fax:+492512807761">+49 251 2807761</a><br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1658      </div>
1659   </body>
Note: See TracBrowser for help on using the repository browser.