source: draft-ietf-httpbis/14/p5-range.html @ 2734

Last change on this file since 2734 was 2726, checked in by julian.reschke@…, 6 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: 105.2 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
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;
9}
10a.smpl {
11  color: black;
12}
13a:hover {
14  text-decoration: underline;
15}
16a:active {
17  text-decoration: underline;
18}
19address {
20  margin-top: 1em;
21  margin-left: 2em;
22  font-style: normal;
23}
24body {
25  color: black;
26  font-family: cambria, helvetica, arial, sans-serif;
27  font-size: 11pt;
28  margin-right: 2em;
29}
30cite {
31  font-style: normal;
32}
33div.note {
34  margin-left: 2em;
35}
36dl {
37  margin-left: 2em;
38}
39ul.empty {
40  list-style-type: none;
41}
42ul.empty li {
43  margin-top: .5em;
44}
45dl p {
46  margin-left: 0em;
47}
48dt {
49  margin-top: .5em;
50}
51h1 {
52  font-size: 130%;
53  line-height: 21pt;
54  page-break-after: avoid;
55}
56h1.np {
57  page-break-before: always;
58}
59h2 {
60  font-size: 120%;
61  line-height: 15pt;
62  page-break-after: avoid;
63}
64h3 {
65  font-size: 110%;
66  page-break-after: avoid;
67}
68h4, h5, h6 {
69  page-break-after: avoid;
70}
71h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
72  color: black;
73}
74img {
75  margin-left: 3em;
76}
77li {
78  margin-left: 2em;
79}
80ol {
81  margin-left: 2em;
82}
83ol.la {
84  list-style-type: lower-alpha;
85}
86ol.ua {
87  list-style-type: upper-alpha;
88}
89ol p {
90  margin-left: 0em;
91}
92p {
93  margin-left: 2em;
94}
95pre {
96  margin-left: 3em;
97  background-color: lightyellow;
98  padding: .25em;
99  page-break-inside: avoid;
100}
101pre.text2 {
102  border-style: dotted;
103  border-width: 1px;
104  background-color: #f0f0f0;
105  width: 69em;
106}
107pre.inline {
108  background-color: white;
109  padding: 0em;
110}
111pre.text {
112  border-style: dotted;
113  border-width: 1px;
114  background-color: #f8f8f8;
115  width: 69em;
116}
117pre.drawing {
118  border-style: solid;
119  border-width: 1px;
120  background-color: #f8f8f8;
121  padding: 2em;
122}
123table {
124  margin-left: 2em;
125}
126table.tt {
127  vertical-align: top;
128  border-color: gray;
129}
130table.tt th {
131  border-color: gray;
132}
133table.tt td {
134  border-color: gray;
135}
136table.all {
137  border-style: solid;
138  border-width: 2px;
139}
140table.full {
141  border-style: solid;
142  border-width: 2px;
143}
144table.tt td {
145  vertical-align: top;
146}
147table.all td {
148  border-style: solid;
149  border-width: 1px;
150}
151table.full td {
152  border-style: none solid;
153  border-width: 1px;
154}
155table.tt th {
156  vertical-align: top;
157}
158table.all th {
159  border-style: solid;
160  border-width: 1px;
161}
162table.full th {
163  border-style: solid;
164  border-width: 1px 1px 2px 1px;
165}
166table.headers th {
167  border-style: none none solid none;
168  border-width: 2px;
169}
170table.left {
171  margin-right: auto;
172}
173table.right {
174  margin-left: auto;
175}
176table.center {
177  margin-left: auto;
178  margin-right: auto;
179}
180caption {
181  caption-side: bottom;
182  font-weight: bold;
183  font-size: 10pt;
184  margin-top: .5em;
185}
186
187table.header {
188  border-spacing: 1px;
189  width: 95%;
190  font-size: 11pt;
191  color: white;
192}
193td.top {
194  vertical-align: top;
195}
196td.topnowrap {
197  vertical-align: top;
198  white-space: nowrap;
199}
200table.header td {
201  background-color: gray;
202  width: 50%;
203}
204table.header a {
205  color: white;
206}
207td.reference {
208  vertical-align: top;
209  white-space: nowrap;
210  padding-right: 1em;
211}
212thead {
213  display:table-header-group;
214}
215ul.toc, ul.toc ul {
216  list-style: none;
217  margin-left: 1.5em;
218  padding-left: 0em;
219}
220ul.toc li {
221  line-height: 150%;
222  font-weight: bold;
223  margin-left: 0em;
224}
225ul.toc li li {
226  line-height: normal;
227  font-weight: normal;
228  font-size: 10pt;
229  margin-left: 0em;
230}
231li.excluded {
232  font-size: 0pt;
233}
234ul p {
235  margin-left: 0em;
236}
237.title, .filename, h1, h2, h3, h4 {
238  font-family: candara, helvetica, arial, sans-serif;
239}
240samp, tt, code, pre {
241  font: consolas, monospace;
242}
243ul.ind, ul.ind ul {
244  list-style: none;
245  margin-left: 1.5em;
246  padding-left: 0em;
247  page-break-before: avoid;
248}
249ul.ind li {
250  font-weight: bold;
251  line-height: 200%;
252  margin-left: 0em;
253}
254ul.ind li li {
255  font-weight: normal;
256  line-height: 150%;
257  margin-left: 0em;
258}
259.avoidbreak {
260  page-break-inside: avoid;
261}
262.bcp14 {
263  font-style: normal;
264  text-transform: lowercase;
265  font-variant: small-caps;
266}
267.comment {
268  background-color: yellow;
269}
270.center {
271  text-align: center;
272}
273.error {
274  color: red;
275  font-style: italic;
276  font-weight: bold;
277}
278.figure {
279  font-weight: bold;
280  text-align: center;
281  font-size: 10pt;
282}
283.filename {
284  color: #333333;
285  font-size: 75%;
286  font-weight: bold;
287  line-height: 21pt;
288  text-align: center;
289}
290.fn {
291  font-weight: bold;
292}
293.left {
294  text-align: left;
295}
296.right {
297  text-align: right;
298}
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;
306}
307.warning {
308  font-size: 130%;
309  background-color: yellow;
310}
311
312
313@media print {
314  .noprint {
315    display: none;
316  }
317
318  a {
319    color: black;
320    text-decoration: none;
321  }
322
323  table.header {
324    width: 90%;
325  }
326
327  td.header {
328    width: 50%;
329    color: black;
330    background-color: white;
331    vertical-align: top;
332    font-size: 110%;
333  }
334
335  ul.toc a:nth-child(2)::after {
336    content: leader('.') target-counter(attr(href), page);
337  }
338
339  ul.ind li li a {
340    content: target-counter(attr(href), page);
341  }
342
343  .print2col {
344    column-count: 2;
345    -moz-column-count: 2;
346    column-fill: auto;
347  }
348}
349
350@page {
351  @top-left {
352       content: "Internet-Draft";
353  }
354  @top-right {
355       content: "April 2011";
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 October 20, 2011";
365  }
366  @bottom-right {
367       content: "[Page " counter(page) "]";
368  }
369}
370
371@page:first {
372    @top-left {
373      content: normal;
374    }
375    @top-right {
376      content: normal;
377    }
378    @top-center {
379      content: normal;
380    }
381}
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      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
400      <link rel="schema.dct" href="http://purl.org/dc/terms/">
401      <meta name="dct.creator" content="Fielding, R.">
402      <meta name="dct.creator" content="Gettys, J.">
403      <meta name="dct.creator" content="Mogul, J.">
404      <meta name="dct.creator" content="Frystyk, H.">
405      <meta name="dct.creator" content="Masinter, L.">
406      <meta name="dct.creator" content="Leach, P.">
407      <meta name="dct.creator" content="Berners-Lee, T.">
408      <meta name="dct.creator" content="Lafon, Y.">
409      <meta name="dct.creator" content="Reschke, J. F.">
410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-14">
411      <meta name="dct.issued" scheme="ISO8601" content="2011-04-18">
412      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
413      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia 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.">
414      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia 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.">
415   </head>
416   <body>
417      <table class="header">
418         <tbody>
419            <tr>
420               <td class="left">HTTPbis Working Group</td>
421               <td class="right">R. Fielding, Editor</td>
422            </tr>
423            <tr>
424               <td class="left">Internet-Draft</td>
425               <td class="right">Adobe</td>
426            </tr>
427            <tr>
428               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
429               </td>
430               <td class="right">J. Gettys</td>
431            </tr>
432            <tr>
433               <td class="left">Intended status: Standards Track</td>
434               <td class="right">Alcatel-Lucent</td>
435            </tr>
436            <tr>
437               <td class="left">Expires: October 20, 2011</td>
438               <td class="right">J. Mogul</td>
439            </tr>
440            <tr>
441               <td class="left"></td>
442               <td class="right">HP</td>
443            </tr>
444            <tr>
445               <td class="left"></td>
446               <td class="right">H. Frystyk</td>
447            </tr>
448            <tr>
449               <td class="left"></td>
450               <td class="right">Microsoft</td>
451            </tr>
452            <tr>
453               <td class="left"></td>
454               <td class="right">L. Masinter</td>
455            </tr>
456            <tr>
457               <td class="left"></td>
458               <td class="right">Adobe</td>
459            </tr>
460            <tr>
461               <td class="left"></td>
462               <td class="right">P. Leach</td>
463            </tr>
464            <tr>
465               <td class="left"></td>
466               <td class="right">Microsoft</td>
467            </tr>
468            <tr>
469               <td class="left"></td>
470               <td class="right">T. Berners-Lee</td>
471            </tr>
472            <tr>
473               <td class="left"></td>
474               <td class="right">W3C/MIT</td>
475            </tr>
476            <tr>
477               <td class="left"></td>
478               <td class="right">Y. Lafon, Editor</td>
479            </tr>
480            <tr>
481               <td class="left"></td>
482               <td class="right">W3C</td>
483            </tr>
484            <tr>
485               <td class="left"></td>
486               <td class="right">J. Reschke, Editor</td>
487            </tr>
488            <tr>
489               <td class="left"></td>
490               <td class="right">greenbytes</td>
491            </tr>
492            <tr>
493               <td class="left"></td>
494               <td class="right">April 18, 2011</td>
495            </tr>
496         </tbody>
497      </table>
498      <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-14</span></p>
499      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
500      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
501         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
502         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
503         5 defines range-specific requests and the rules for constructing and combining responses to those requests.
504      </p>
505      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
506      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived
507         at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
508      </p>
509      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
510      </p>
511      <p>The changes in this draft are summarized in <a href="#changes.since.13" title="Since draft-ietf-httpbis-p5-range-13">Appendix&nbsp;D.15</a>.
512      </p>
513      <div id="rfc.status">
514         <h1><a href="#rfc.status">Status of This Memo</a></h1>
515         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
516         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
517            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
518         </p>
519         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
520            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
521            in progress”.
522         </p>
523         <p>This Internet-Draft will expire on October 20, 2011.</p>
524      </div>
525      <div id="rfc.copyrightnotice">
526         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
527         <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
528         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
529            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
530            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
531            BSD License.
532         </p>
533         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
534            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
535            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
536            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
537            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
538            it into languages other than English.
539         </p>
540      </div>
541      <hr class="noprint">
542      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
543      <ul class="toc">
544         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
545               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
546               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
547                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
548                     <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>
549                  </ul>
550               </li>
551            </ul>
552         </li>
553         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a><ul>
554               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registry">Range Specifier Registry</a></li>
555            </ul>
556         </li>
557         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
558               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
559               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
560            </ul>
561         </li>
562         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
563         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
564               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
565               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
566               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
567               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
568                     <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
569                     <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>
570                  </ul>
571               </li>
572            </ul>
573         </li>
574         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
575               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
576               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
577               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registration">Range Specifier Registration</a></li>
578            </ul>
579         </li>
580         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
581         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
582         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
583               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
584               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
585            </ul>
586         </li>
587         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
588         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
589               <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>
590            </ul>
591         </li>
592         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
593         <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>
594               <li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC 2616</a></li>
595               <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>
596               <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>
597               <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>
598               <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>
599               <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>
600               <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>
601               <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>
602               <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>
603               <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>
604               <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>
605               <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>
606               <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>
607               <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>
608               <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>
609            </ul>
610         </li>
611         <li><a href="#rfc.index">Index</a></li>
612         <li><a href="#rfc.authors">Authors' Addresses</a></li>
613      </ul>
614      <div id="introduction">
615         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
616         <p id="rfc.section.1.p.1">HTTP clients often encounter interrupted data transfers as a result of cancelled requests or dropped connections. When a cache
617            has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
618            rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
619            request only a subset of a larger representation, such as a single page of a very large document or only part of an image
620            to be rendered by a device with limited local storage.
621         </p>
622         <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
623            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
624            request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
625            full responses by intermediate caches that might not implement the feature.
626         </p>
627         <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
628            requests for byte ranges.
629         </p>
630         <div id="intro.requirements">
631            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
632            <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"
633               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>.
634            </p>
635            <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
636               protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
637               for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
638               all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
639            </p>
640         </div>
641         <div id="notation">
642            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
643            <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF, with the list rule expanded.
644            </p>
645            <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="https://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
646               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
647               and WSP (whitespace).
648            </p>
649            <div id="core.rules">
650               <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>
651               <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
652               </p>
653               <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">token</a>      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
654  <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;
655</pre></div>
656            <div id="abnf.dependencies">
657               <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>
658               <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
659               <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>&gt;
660</pre><div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.2</a>&gt;
661</pre></div>
662         </div>
663      </div>
664      <div id="range.units">
665         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#range.units">Range Units</a></h1>
666         <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
667            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.
668         </p>
669         <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#range.units" class="smpl">range-unit</a>       = <a href="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a>
670  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
671  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a>
672</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
673            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>.
674         </p>
675         <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.
676         </p>
677         <div id="range.specifier.registry">
678            <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>
679            <p id="rfc.section.2.1.p.1">The HTTP Range Specifier Registry defines the name space for the range specifier names.</p>
680            <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
681            </p>
682            <ul>
683               <li>Name</li>
684               <li>Description</li>
685               <li>Pointer to specification text</li>
686            </ul>
687            <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
688            </p>
689            <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt;.
690            </p>
691         </div>
692      </div>
693      <div id="status.code.definitions">
694         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#status.code.definitions">Status Code Definitions</a></h1>
695         <div id="status.206">
696            <div id="rfc.iref.2.1"></div>
697            <div id="rfc.iref.s.1"></div>
698            <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>
699            <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.
700            </p>
701            <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
702            </p>
703            <ul>
704               <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
705                  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.
706               </li>
707               <li>Date</li>
708               <li>Cache-Control, ETag, Expires, Content-Location, Last-Modified, and/or Vary, if the header field would have been sent in a
709                  200 response to the same request
710               </li>
711            </ul>
712            <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.
713            </p>
714            <p id="rfc.section.3.1.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified header fields do not match exactly,
715               see <a href="#combining.byte.ranges" title="Combining Ranges">Section&nbsp;4</a>.
716            </p>
717            <p id="rfc.section.3.1.p.5">A cache that does not support the Range and Content-Range header fields <em class="bcp14">MUST NOT</em> cache 206 (Partial Content) responses. Furthermore, if a response uses a range unit that is not understood by the cache, then
718               it <em class="bcp14">MUST NOT</em> be cached either.
719            </p>
720         </div>
721         <div id="status.416">
722            <div id="rfc.iref.4.1"></div>
723            <div id="rfc.iref.s.2"></div>
724            <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>
725            <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
726               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
727               length of the selected resource.)
728            </p>
729            <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.
730            </p>
731         </div>
732      </div>
733      <div id="combining.byte.ranges">
734         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></h1>
735         <p id="rfc.section.4.p.1">A response might transfer only a subrange of a representation, either because the request included one or more Range specifications,
736            or because a connection closed prematurely. After several such transfers, a cache might have received several ranges of the
737            same representation.
738         </p>
739         <p id="rfc.section.4.p.2">If a cache has a stored non-empty set of subranges for a representation, and an incoming response transfers another subrange,
740            the cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
741         </p>
742         <ul>
743            <li>Both the incoming response and the cache entry have a cache validator.</li>
744            <li>The two cache validators match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
745            </li>
746         </ul>
747         <p id="rfc.section.4.p.3">If either requirement is not met, the cache <em class="bcp14">MUST</em> use only the most recent partial response (based on the Date values transmitted with every response, and using the incoming
748            response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
749         </p>
750      </div>
751      <div id="header.fields">
752         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
753         <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>
754         <div id="header.accept-ranges">
755            <div id="rfc.iref.a.1"></div>
756            <div id="rfc.iref.h.1"></div>
757            <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>
758            <p id="rfc.section.5.1.p.1">The "Accept-Ranges" header field allows a resource to indicate its acceptance of range requests.</p>
759            <div id="rfc.figure.u.5"></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>
760  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
761</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
762            </p>
763            <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: bytes
764</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>.
765            </p>
766            <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
767            </p>
768            <div id="rfc.figure.u.7"></div><pre class="text">  Accept-Ranges: none
769</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
770         </div>
771         <div id="header.content-range">
772            <div id="rfc.iref.c.1"></div>
773            <div id="rfc.iref.h.2"></div>
774            <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>
775            <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
776               body is intended to be applied.
777            </p>
778            <p id="rfc.section.5.2.p.2">Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
779            </p>
780            <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#header.content-range" class="smpl">Content-Range</a> = <a href="#header.content-range" class="smpl">content-range-spec</a>
781 
782  <a href="#header.content-range" class="smpl">content-range-spec</a>      = <a href="#header.content-range" class="smpl">byte-content-range-spec</a>
783                          / <a href="#header.content-range" class="smpl">other-content-range-spec</a>
784  <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>
785                            <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> "/"
786                            ( <a href="#header.content-range" class="smpl">instance-length</a> / "*" )
787 
788  <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>)
789                          / "*"
790                         
791  <a href="#header.content-range" class="smpl">instance-length</a>         = 1*<a href="#notation" class="smpl">DIGIT</a>
792 
793  <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>
794                             <a href="#header.content-range" class="smpl">other-range-resp-spec</a>
795  <a href="#header.content-range" class="smpl">other-range-resp-spec</a>    = *<a href="#notation" class="smpl">CHAR</a>
796</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
797               "*" character means that the instance-length is unknown at the time when the response was generated.
798            </p>
799            <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.
800            </p>
801            <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
802               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.
803            </p>
804            <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
805               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 "*".
806            </p>
807            <p id="rfc.section.5.2.p.8">Examples of byte-content-range-spec values, assuming that the representation contains a total of 1234 bytes: </p>
808            <ul>
809               <li>The first 500 bytes: <span id="rfc.figure.u.9"></span><pre class="text">  bytes 0-499/1234
810</pre> </li>
811               <li>The second 500 bytes: <span id="rfc.figure.u.10"></span><pre class="text">  bytes 500-999/1234
812</pre> </li>
813               <li>All except for the first 500 bytes: <span id="rfc.figure.u.11"></span><pre class="text">  bytes 500-1233/1234
814</pre> </li>
815               <li>The last 500 bytes: <span id="rfc.figure.u.12"></span><pre class="text">  bytes 734-1233/1234
816</pre> </li>
817            </ul>
818            <p id="rfc.section.5.2.p.9">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
819               a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header field,
820               and a Content-Length header field showing the number of bytes actually transferred. For example,
821            </p>
822            <div id="rfc.figure.u.13"></div><pre class="text">  HTTP/1.1 206 Partial Content
823  Date: Wed, 15 Nov 1995 06:25:24 GMT
824  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
825  Content-Range: bytes 21010-47021/47022
826  Content-Length: 26012
827  Content-Type: image/gif
828</pre><p id="rfc.section.5.2.p.11">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
829               ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
830               as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
831            </p>
832            <p id="rfc.section.5.2.p.12">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
833            </p>
834            <p id="rfc.section.5.2.p.13">When a client requests multiple ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
835            </p>
836            <p id="rfc.section.5.2.p.14">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
837               the full representation).
838            </p>
839            <p id="rfc.section.5.2.p.15">If the server receives a request (other than one including an If-Range header field) with an unsatisfiable Range header field
840               (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
841               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>).
842            </p>
843            <div class="note" id="rfc.section.5.2.p.16">
844               <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
845                  an unsatisfiable Range header field, since not all servers implement this header field.
846               </p>
847            </div>
848         </div>
849         <div id="header.if-range">
850            <div id="rfc.iref.i.1"></div>
851            <div id="rfc.iref.h.3"></div>
852            <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>
853            <p id="rfc.section.5.3.p.1">If a client has a partial copy of a representation in its cache, and wishes to have an up-to-date copy of the entire representation
854               in its cache, it could use the Range header field with a conditional GET (using either or both of If-Unmodified-Since and
855               If-Match.) However, if the condition fails because the representation has been modified, the client would then have to make
856               a second request to obtain the entire current representation.
857            </p>
858            <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
859               is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation".
860            </p>
861            <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.11"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
862</pre><p id="rfc.section.5.3.p.4">Only a strong validator (<a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">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>) is usable for range retrieval, since otherwise the client might end up with an internally inconsistent representation. Clients <em class="bcp14">MUST NOT</em> use weak validators in range requests. A cache or origin server receiving a conditional range request <em class="bcp14">MUST</em> use the strong comparison function to evaluate the condition.
863            </p>
864            <p id="rfc.section.5.3.p.5">If the client has no entity-tag for a representation, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header field. (The server can distinguish between a valid HTTP-date and any form of entity-tag
865               by examining no more than two characters.) The If-Range header field <em class="bcp14">SHOULD</em> only be used together with a Range header field, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header field, or if the server does not support the sub-range operation.
866            </p>
867            <p id="rfc.section.5.3.p.6">If a client wishes to perform a sub-range retrieval on a value for which it has only a Last-Modified time and no opaque validator,
868               it <em class="bcp14">MAY</em> do this only if the Last-Modified time is strong in the sense described in <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.1.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
869            </p>
870            <p id="rfc.section.5.3.p.7">If the entity-tag given in the If-Range header field matches the current cache validator for the representation, then the
871               server <em class="bcp14">SHOULD</em> provide the specified sub-range of the representation using a 206 (Partial Content) response. If the cache validator does
872               not match, then the server <em class="bcp14">SHOULD</em> return the entire representation using a 200 (OK) response.
873            </p>
874         </div>
875         <div id="header.range">
876            <div id="rfc.iref.r.1"></div>
877            <div id="rfc.iref.h.4"></div>
878            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.range">Range</a></h2>
879            <div id="byte.ranges">
880               <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>
881               <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
882                  representation. (However, not all clients and servers need to support byte-range operations.)
883               </p>
884               <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
885                  message-body).
886               </p>
887               <div id="rule.ranges-specifier">
888                  <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.
889                  </p>
890               </div>
891               <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <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>
892  <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> )
893  <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> ]
894  <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
895  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
896</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
897                  gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
898                  at zero.
899               </p>
900               <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
901                  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.
902               </p>
903               <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
904                  body, last-byte-pos is taken to be equal to one less than the current length of the representation in bytes.
905               </p>
906               <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>
907               <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
908  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
909</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
910                  value. (That is, this form specifies the last N bytes of a representation.) If the representation is shorter than the specified
911                  suffix-length, the entire representation is used.
912               </p>
913               <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
914                  length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set
915                  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.
916               </p>
917               <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p>
918               <ul>
919                  <li>The first 500 bytes (byte offsets 0-499, inclusive): <span id="rfc.figure.u.17"></span><pre class="text">  bytes=0-499
920</pre> </li>
921                  <li>The second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.18"></span><pre class="text">  bytes=500-999
922</pre> </li>
923                  <li>The final 500 bytes (byte offsets 9500-9999, inclusive): <span id="rfc.figure.u.19"></span><pre class="text">  bytes=-500
924</pre> Or: <span id="rfc.figure.u.20"></span><pre class="text">  bytes=9500-
925</pre> </li>
926                  <li>The first and last bytes only (bytes 0 and 9999): <span id="rfc.figure.u.21"></span><pre class="text">  bytes=0-0,-1
927</pre> </li>
928                  <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.22"></span><pre class="text">  bytes=500-600,601-999
929  bytes=500-700,601-999
930</pre> </li>
931               </ul>
932            </div>
933            <div id="range.retrieval.requests">
934               <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>
935               <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
936                  body, instead of the entire representation body.
937               </p>
938               <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.20"></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>
939  <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>
940  <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#notation" class="smpl">CHAR</a>
941</pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header field. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when
942                  possible, since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval
943                  of large representations.
944               </p>
945               <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>
946               <ul>
947                  <li>The presence of a Range header field in an unconditional GET modifies what is returned if the GET is otherwise successful.
948                     In other words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
949                  </li>
950                  <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,
951                     or one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
952                     is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
953                  </li>
954               </ul>
955               <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.
956               </p>
957               <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
958                  representation in reply, it <em class="bcp14">MAY</em> only return the requested range to its client.
959               </p>
960            </div>
961         </div>
962      </div>
963      <div id="IANA.considerations">
964         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
965         <div id="status.code.registration">
966            <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>
967            <p id="rfc.section.6.1.p.1">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
968            </p>
969            <div id="rfc.table.1">
970               <div id="iana.status.code.registration.table"></div>
971               <table class="tt full left" cellpadding="3" cellspacing="0">
972                  <thead>
973                     <tr>
974                        <th>Value</th>
975                        <th>Description</th>
976                        <th>Reference</th>
977                     </tr>
978                  </thead>
979                  <tbody>
980                     <tr>
981                        <td class="left">206</td>
982                        <td class="left">Partial Content</td>
983                        <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;3.1</a>
984                        </td>
985                     </tr>
986                     <tr>
987                        <td class="left">416</td>
988                        <td class="left">Requested Range Not Satisfiable</td>
989                        <td class="left"><a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>
990                        </td>
991                     </tr>
992                  </tbody>
993               </table>
994            </div>
995         </div>
996         <div id="header.field.registration">
997            <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>
998            <p id="rfc.section.6.2.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
999            </p>
1000            <div id="rfc.table.2">
1001               <div id="iana.header.registration.table"></div>
1002               <table class="tt full left" cellpadding="3" cellspacing="0">
1003                  <thead>
1004                     <tr>
1005                        <th>Header Field Name</th>
1006                        <th>Protocol</th>
1007                        <th>Status</th>
1008                        <th>Reference</th>
1009                     </tr>
1010                  </thead>
1011                  <tbody>
1012                     <tr>
1013                        <td class="left">Accept-Ranges</td>
1014                        <td class="left">http</td>
1015                        <td class="left">standard</td>
1016                        <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
1017                        </td>
1018                     </tr>
1019                     <tr>
1020                        <td class="left">Content-Range</td>
1021                        <td class="left">http</td>
1022                        <td class="left">standard</td>
1023                        <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
1024                        </td>
1025                     </tr>
1026                     <tr>
1027                        <td class="left">If-Range</td>
1028                        <td class="left">http</td>
1029                        <td class="left">standard</td>
1030                        <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">Section&nbsp;5.3</a>
1031                        </td>
1032                     </tr>
1033                     <tr>
1034                        <td class="left">Range</td>
1035                        <td class="left">http</td>
1036                        <td class="left">standard</td>
1037                        <td class="left"><a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a>
1038                        </td>
1039                     </tr>
1040                  </tbody>
1041               </table>
1042            </div>
1043            <p id="rfc.section.6.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
1044         </div>
1045         <div id="range.specifier.registration">
1046            <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>
1047            <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.
1048            </p>
1049            <p id="rfc.section.6.3.p.2">The HTTP Range Specifier Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt; and be populated with the registrations below:
1050            </p>
1051            <div id="rfc.table.3">
1052               <div id="iana.range.specifiers.table"></div>
1053               <table class="tt full left" cellpadding="3" cellspacing="0">
1054                  <thead>
1055                     <tr>
1056                        <th>Range Specifier Name</th>
1057                        <th>Description</th>
1058                        <th>Reference</th>
1059                     </tr>
1060                  </thead>
1061                  <tbody>
1062                     <tr>
1063                        <td class="left">bytes</td>
1064                        <td class="left">a range of octets</td>
1065                        <td class="left">(this specification)</td>
1066                     </tr>
1067                  </tbody>
1068               </table>
1069            </div>
1070            <p id="rfc.section.6.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
1071         </div>
1072      </div>
1073      <div id="security.considerations">
1074         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
1075         <p id="rfc.section.7.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
1076         </p>
1077      </div>
1078      <div id="ack">
1079         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
1080         <p id="rfc.section.8.p.1">Most of the specification of ranges is based on work originally done by Ari Luotonen and John Franks, with additional input
1081            from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
1082            Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
1083         </p>
1084      </div>
1085      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
1086      </h1>
1087      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
1088      </h2>
1089      <table>
1090         <tr>
1091            <td class="reference"><b id="Part1">[Part1]</b></td>
1092            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-14">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-14 (work in progress), April&nbsp;2011.
1093            </td>
1094         </tr>
1095         <tr>
1096            <td class="reference"><b id="Part4">[Part4]</b></td>
1097            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-14">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-14 (work in progress), April&nbsp;2011.
1098            </td>
1099         </tr>
1100         <tr>
1101            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
1102            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="https://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
1103            </td>
1104         </tr>
1105         <tr>
1106            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1107            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
1108            </td>
1109         </tr>
1110         <tr>
1111            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1112            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
1113            </td>
1114         </tr>
1115      </table>
1116      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
1117      </h2>
1118      <table>
1119         <tr>
1120            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1121            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
1122            </td>
1123         </tr>
1124         <tr>
1125            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1126            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
1127            </td>
1128         </tr>
1129         <tr>
1130            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
1131            <td class="top"><a href="mailto:ned.freed@mrochek.com" title="Sun Microsystems">Freed, N.</a> and <a href="mailto:klensin+ietf@jck.com">J. Klensin</a>, “<a href="https://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
1132            </td>
1133         </tr>
1134         <tr>
1135            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
1136            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
1137            </td>
1138         </tr>
1139      </table>
1140      <div id="internet.media.type.multipart.byteranges">
1141         <div id="rfc.iref.m.1"></div>
1142         <div id="rfc.iref.m.2"></div>
1143         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></h1>
1144         <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
1145            non-overlapping ranges), these are transmitted as a multipart message-body (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="https://tools.ietf.org/html/rfc2046#section-5.1">Section 5.1</a>). The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
1146         </p>
1147         <div class="note" id="rfc.section.A.p.2">
1148            <p><b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
1149            </p>
1150         </div>
1151         <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
1152            required boundary parameter specifies the boundary string used to separate each body-part.
1153         </p>
1154         <p id="rfc.section.A.p.4"></p>
1155         <dl>
1156            <dt>Type name:</dt>
1157            <dd>multipart</dd>
1158            <dt>Subtype name:</dt>
1159            <dd>byteranges</dd>
1160            <dt>Required parameters:</dt>
1161            <dd>boundary</dd>
1162            <dt>Optional parameters:</dt>
1163            <dd>none</dd>
1164            <dt>Encoding considerations:</dt>
1165            <dd>only "7bit", "8bit", or "binary" are permitted</dd>
1166            <dt>Security considerations:</dt>
1167            <dd>none</dd>
1168            <dt>Interoperability considerations:</dt>
1169            <dd>none</dd>
1170            <dt>Published specification:</dt>
1171            <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
1172            </dd>
1173            <dt>Applications that use this media type:</dt>
1174            <dt>Additional information:</dt>
1175            <dd>
1176               <dl>
1177                  <dt>Magic number(s):</dt>
1178                  <dd>none</dd>
1179                  <dt>File extension(s):</dt>
1180                  <dd>none</dd>
1181                  <dt>Macintosh file type code(s):</dt>
1182                  <dd>none</dd>
1183               </dl>
1184            </dd>
1185            <dt>Person and email address to contact for further information:</dt>
1186            <dd>See Authors Section.</dd>
1187            <dt>Intended usage:</dt>
1188            <dd>COMMON</dd>
1189            <dt>Restrictions on usage:</dt>
1190            <dd>none</dd>
1191            <dt>Author/Change controller:</dt>
1192            <dd>IESG</dd>
1193         </dl>
1194         <div id="rfc.figure.u.24"></div>
1195         <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
1196  Date: Wed, 15 Nov 1995 06:25:24 GMT
1197  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
1198  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1199 
1200  --THIS_STRING_SEPARATES
1201  Content-type: application/pdf
1202  Content-range: bytes 500-999/8000
1203 
1204  ...the first range...
1205  --THIS_STRING_SEPARATES
1206  Content-type: application/pdf
1207  Content-range: bytes 7000-7999/8000
1208 
1209  ...the second range
1210  --THIS_STRING_SEPARATES--
1211</pre><div id="rfc.figure.u.25"></div>
1212         <p>Other example:</p><pre class="text">  HTTP/1.1 206 Partial Content
1213  Date: Tue, 14 Nov 1995 06:25:24 GMT
1214  Last-Modified: Tue, 14 July 04:58:08 GMT
1215  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1216 
1217  --THIS_STRING_SEPARATES
1218  Content-type: video/example
1219  Content-range: exampleunit 1.2-4.3/25
1220 
1221  ...the first range...
1222  --THIS_STRING_SEPARATES
1223  Content-type: video/example
1224  Content-range: exampleunit 11.2-14.3/25
1225 
1226  ...the second range
1227  --THIS_STRING_SEPARATES--
1228</pre><p id="rfc.section.A.p.7">Notes: </p>
1229         <ol>
1230            <li>Additional CRLFs <em class="bcp14">MAY</em> precede the first boundary string in the body.
1231            </li>
1232            <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.
1233            </li>
1234            <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.
1235            </li>
1236         </ol>
1237      </div>
1238      <div id="compatibility">
1239         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
1240         <div id="changes.from.rfc.2616">
1241            <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>
1242            <p id="rfc.section.B.1.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
1243            </p>
1244            <p id="rfc.section.B.1.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section&nbsp;5</a>)
1245            </p>
1246            <p id="rfc.section.B.1.p.3">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
1247            </p>
1248         </div>
1249      </div>
1250      <div id="collected.abnf">
1251         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
1252         <div id="rfc.figure.u.26"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
1253
1254<a href="#header.content-range" class="smpl">Content-Range</a> = content-range-spec
1255
1256<a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part1], Section 6.1&gt;
1257
1258<a href="#header.if-range" class="smpl">If-Range</a> = entity-tag / HTTP-date
1259
1260<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
1261
1262<a href="#range.retrieval.requests" class="smpl">Range</a> = byte-ranges-specifier / other-ranges-specifier
1263
1264<a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = ( *( "," OWS ) range-unit *( OWS "," [ OWS
1265 range-unit ] ) ) / "none"
1266
1267<a href="#header.content-range" class="smpl">byte-content-range-spec</a> = bytes-unit SP byte-range-resp-spec "/" (
1268 instance-length / "*" )
1269<a href="#header.content-range" class="smpl">byte-range-resp-spec</a> = ( first-byte-pos "-" last-byte-pos ) / "*"
1270<a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = *( "," OWS ) ( byte-range-spec /
1271 suffix-byte-range-spec ) *( OWS "," [ OWS ( byte-range-spec /
1272 suffix-byte-range-spec ) ] )
1273<a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ]
1274<a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set
1275<a href="#range.units" class="smpl">bytes-unit</a> = "bytes"
1276
1277<a href="#header.content-range" class="smpl">content-range-spec</a> = byte-content-range-spec /
1278 other-content-range-spec
1279
1280<a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in [Part4], Section 2.2&gt;
1281
1282<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT
1283
1284<a href="#header.content-range" class="smpl">instance-length</a> = 1*DIGIT
1285
1286<a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*DIGIT
1287
1288<a href="#header.content-range" class="smpl">other-content-range-spec</a> = other-range-unit SP other-range-resp-spec
1289<a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *CHAR
1290<a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*CHAR
1291<a href="#range.units" class="smpl">other-range-unit</a> = token
1292<a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = other-range-unit "=" other-range-set
1293
1294<a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit
1295
1296<a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" suffix-length
1297<a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT
1298
1299<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
1300</pre><div id="rfc.figure.u.27"></div>
1301         <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
1302; Content-Range defined but not used
1303; If-Range defined but not used
1304; Range defined but not used
1305</pre></div>
1306      <div id="change.log">
1307         <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>
1308         <div>
1309            <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC 2616
1310            </h2>
1311            <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>.
1312            </p>
1313         </div>
1314         <div>
1315            <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
1316            </h2>
1317            <p id="rfc.section.D.2.p.1">Closed issues: </p>
1318            <ul>
1319               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/18">http://tools.ietf.org/wg/httpbis/trac/ticket/18</a>&gt;: "Cache validators in 206 responses" (&lt;<a href="http://purl.org/NET/http-errata#ifrange206">http://purl.org/NET/http-errata#ifrange206</a>&gt;)
1320               </li>
1321               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
1322               </li>
1323               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/86">http://tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
1324               </li>
1325            </ul>
1326         </div>
1327         <div>
1328            <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
1329            </h2>
1330            <p id="rfc.section.D.3.p.1">Closed issues: </p>
1331            <ul>
1332               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/55">http://tools.ietf.org/wg/httpbis/trac/ticket/55</a>&gt;: "Updating to RFC4288"
1333               </li>
1334            </ul>
1335            <p id="rfc.section.D.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
1336            </p>
1337            <ul>
1338               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1339            </ul>
1340         </div>
1341         <div id="changes.since.02">
1342            <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>
1343            <p id="rfc.section.D.4.p.1">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
1344            </p>
1345            <ul>
1346               <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
1347            </ul>
1348         </div>
1349         <div id="changes.since.03">
1350            <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>
1351            <p id="rfc.section.D.5.p.1">None.</p>
1352         </div>
1353         <div id="changes.since.04">
1354            <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>
1355            <p id="rfc.section.D.6.p.1">Closed issues: </p>
1356            <ul>
1357               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/133">http://tools.ietf.org/wg/httpbis/trac/ticket/133</a>&gt;: "multipart/byteranges minimum number of parts"
1358               </li>
1359            </ul>
1360            <p id="rfc.section.D.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
1361            </p>
1362            <ul>
1363               <li>Use "/" instead of "|" for alternatives.</li>
1364               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1365               <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
1366            </ul>
1367         </div>
1368         <div id="changes.since.05">
1369            <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>
1370            <p id="rfc.section.D.7.p.1">Closed issues: </p>
1371            <ul>
1372               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/142">http://tools.ietf.org/wg/httpbis/trac/ticket/142</a>&gt;: "State base for *-byte-pos and suffix-length"
1373               </li>
1374            </ul>
1375            <p id="rfc.section.D.7.p.2">Ongoing work on Custom Ranges (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>&gt;):
1376            </p>
1377            <ul>
1378               <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
1379            </ul>
1380            <p id="rfc.section.D.7.p.3">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
1381            </p>
1382            <ul>
1383               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
1384            </ul>
1385         </div>
1386         <div id="changes.since.06">
1387            <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>
1388            <p id="rfc.section.D.8.p.1">Closed issues: </p>
1389            <ul>
1390               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
1391               </li>
1392            </ul>
1393         </div>
1394         <div id="changes.since.07">
1395            <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>
1396            <p id="rfc.section.D.9.p.1">Closed issues: </p>
1397            <ul>
1398               <li>Fixed discrepancy in the If-Range definition about allowed validators.</li>
1399               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/150">http://tools.ietf.org/wg/httpbis/trac/ticket/150</a>&gt;: "multipart/byteranges for custom range units"
1400               </li>
1401               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/151">http://tools.ietf.org/wg/httpbis/trac/ticket/151</a>&gt;: "range unit missing from other-ranges-specifier in Range header"
1402               </li>
1403               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/198">http://tools.ietf.org/wg/httpbis/trac/ticket/198</a>&gt;: "move IANA registrations for optional status codes"
1404               </li>
1405            </ul>
1406         </div>
1407         <div id="changes.since.08">
1408            <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>
1409            <p id="rfc.section.D.10.p.1">No significant changes.</p>
1410         </div>
1411         <div id="changes.since.09">
1412            <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>
1413            <p id="rfc.section.D.11.p.1">No significant changes.</p>
1414         </div>
1415         <div id="changes.since.10">
1416            <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>
1417            <p id="rfc.section.D.12.p.1">Closed issues: </p>
1418            <ul>
1419               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
1420               </li>
1421               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
1422               </li>
1423               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
1424               </li>
1425            </ul>
1426            <p id="rfc.section.D.12.p.2">Ongoing work on Custom Ranges (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>&gt;):
1427            </p>
1428            <ul>
1429               <li>Add IANA registry.</li>
1430            </ul>
1431         </div>
1432         <div id="changes.since.11">
1433            <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>
1434            <p id="rfc.section.D.13.p.1">Closed issues: </p>
1435            <ul>
1436               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/217">http://tools.ietf.org/wg/httpbis/trac/ticket/217</a>&gt;: "Caches can't be required to serve ranges"
1437               </li>
1438            </ul>
1439         </div>
1440         <div id="changes.since.12">
1441            <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>
1442            <p id="rfc.section.D.14.p.1">Closed issues: </p>
1443            <ul>
1444               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
1445               </li>
1446            </ul>
1447         </div>
1448         <div id="changes.since.13">
1449            <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>
1450            <p id="rfc.section.D.15.p.1">Closed issues: </p>
1451            <ul>
1452               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
1453               </li>
1454            </ul>
1455         </div>
1456      </div>
1457      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1458      <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>
1459      </p>
1460      <div class="print2col">
1461         <ul class="ind">
1462            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
1463                  <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>
1464               </ul>
1465            </li>
1466            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1467                  <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>
1468               </ul>
1469            </li>
1470            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1471                  <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>
1472               </ul>
1473            </li>
1474            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1475                  <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>
1476               </ul>
1477            </li>
1478            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1479                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1480                     <ul>
1481                        <li><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>5.1</b></a></li>
1482                        <li><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>5.1</b></a></li>
1483                        <li><tt>byte-content-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>5.2</b></a></li>
1484                        <li><tt>byte-range-resp-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>5.2</b></a></li>
1485                        <li><tt>byte-range-set</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>5.4.1</b></a></li>
1486                        <li><tt>byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>5.4.1</b></a></li>
1487                        <li><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>5.4.1</b></a></li>
1488                        <li><tt>bytes-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2</b></a></li>
1489                        <li><tt>Content-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>5.2</b></a></li>
1490                        <li><tt>content-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>5.2</b></a></li>
1491                        <li><tt>first-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>5.4.1</b></a></li>
1492                        <li><tt>If-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>5.3</b></a></li>
1493                        <li><tt>instance-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>5.2</b></a></li>
1494                        <li><tt>last-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>5.4.1</b></a></li>
1495                        <li><tt>other-range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>2</b></a></li>
1496                        <li><tt>Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>5.4.2</b></a></li>
1497                        <li><tt>range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
1498                        <li><tt>ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>5.4.1</b></a></li>
1499                        <li><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>5.4.1</b></a></li>
1500                        <li><tt>suffix-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>5.4.1</b></a></li>
1501                     </ul>
1502                  </li>
1503               </ul>
1504            </li>
1505            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1506                  <li>Header Fields&nbsp;&nbsp;
1507                     <ul>
1508                        <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>
1509                        <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>
1510                        <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>
1511                        <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>
1512                     </ul>
1513                  </li>
1514               </ul>
1515            </li>
1516            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
1517                  <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>
1518               </ul>
1519            </li>
1520            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
1521                  <li>Media Type&nbsp;&nbsp;
1522                     <ul>
1523                        <li>multipart/byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>A</b></a></li>
1524                        <li>multipart/x-byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.4">A</a></li>
1525                     </ul>
1526                  </li>
1527                  <li>multipart/byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>A</b></a></li>
1528                  <li>multipart/x-byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.3">A</a></li>
1529               </ul>
1530            </li>
1531            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1532                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.2</a>, <a href="#rfc.xref.Part1.6">7</a>, <a href="#Part1"><b>9.1</b></a><ul>
1533                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a></li>
1534                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a></li>
1535                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2.2</a></li>
1536                     </ul>
1537                  </li>
1538                  <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">5.3</a>, <a href="#rfc.xref.Part4.4">5.3</a>, <a href="#Part4"><b>9.1</b></a><ul>
1539                        <li><em>Section 2.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.4">5.3</a></li>
1540                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2.2</a></li>
1541                        <li><em>Section 2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">4</a>, <a href="#rfc.xref.Part4.3">5.3</a></li>
1542                     </ul>
1543                  </li>
1544               </ul>
1545            </li>
1546            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1547                  <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>
1548                  <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>
1549                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">A</a></li>
1550                     </ul>
1551                  </li>
1552                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>9.1</b></a></li>
1553                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#RFC2616"><b>9.2</b></a>, <a href="#rfc.xref.RFC2616.1">D.1</a></li>
1554                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">6.2</a>, <a href="#RFC3864"><b>9.2</b></a></li>
1555                  <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#RFC4288"><b>9.2</b></a>, <a href="#rfc.xref.RFC4288.1">A</a></li>
1556                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a>, <a href="#RFC5226"><b>9.2</b></a><ul>
1557                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a></li>
1558                     </ul>
1559                  </li>
1560                  <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>
1561                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
1562                     </ul>
1563                  </li>
1564               </ul>
1565            </li>
1566            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
1567                  <li>Status Codes&nbsp;&nbsp;
1568                     <ul>
1569                        <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>
1570                        <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>
1571                     </ul>
1572                  </li>
1573               </ul>
1574            </li>
1575         </ul>
1576      </div>
1577      <div class="avoidbreak">
1578         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1579         <p><b>Roy T. Fielding</b>
1580            (editor)
1581            <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
1582         <p><b>Jim Gettys</b><br>Alcatel-Lucent Bell Labs<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>Email: <a href="mailto:jg@freedesktop.org">jg@freedesktop.org</a><br>URI: <a href="http://gettys.wordpress.com/">http://gettys.wordpress.com/</a></p>
1583         <p><b>Jeffrey C. Mogul</b><br>Hewlett-Packard Company<br>HP Labs, Large Scale Systems Group<br>1501 Page Mill Road, MS 1177<br>Palo Alto, CA&nbsp;94304<br>USA<br>Email: <a href="mailto:JeffMogul@acm.org">JeffMogul@acm.org</a></p>
1584         <p><b>Henrik Frystyk Nielsen</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>USA<br>Email: <a href="mailto:henrikn@microsoft.com">henrikn@microsoft.com</a></p>
1585         <p><b>Larry Masinter</b><br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:LMM@acm.org">LMM@acm.org</a><br>URI: <a href="http://larry.masinter.net/">http://larry.masinter.net/</a></p>
1586         <p><b>Paul J. Leach</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>Email: <a href="mailto:paulle@microsoft.com">paulle@microsoft.com</a></p>
1587         <p><b>Tim Berners-Lee</b><br>World Wide Web Consortium<br>MIT Computer Science and Artificial Intelligence Laboratory<br>The Stata Center, Building 32<br>32 Vassar Street<br>Cambridge, MA&nbsp;02139<br>USA<br>Email: <a href="mailto:timbl@w3.org">timbl@w3.org</a><br>URI: <a href="http://www.w3.org/People/Berners-Lee/">http://www.w3.org/People/Berners-Lee/</a></p>
1588         <p><b>Yves Lafon</b>
1589            (editor)
1590            <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM&nbsp;06902<br>France<br>Email: <a href="mailto:ylafon@w3.org">ylafon@w3.org</a><br>URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></p>
1591         <p><b>Julian F. Reschke</b>
1592            (editor)
1593            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Phone: <a href="tel:+492512807760">+49 251 2807760</a><br>Fax: <a href="fax:+492512807761">+49 251 2807761</a><br>Email: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
1594      </div>
1595   </body>
1596</html>
Note: See TracBrowser for help on using the repository browser.