source: draft-ietf-httpbis/07/p5-range.html

Last change on this file 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: 98.6 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: "July 2009";
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 January 14, 2010";
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-07">
411      <meta name="dct.issued" scheme="ISO8601" content="2009-07-13">
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">Day Software</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">One Laptop per Child</td>
435            </tr>
436            <tr>
437               <td class="left">Expires: January 14, 2010</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 Systems</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">July 13, 2009</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-07</span></p>
499      <div id="rfc.status">
500         <h1><a href="#rfc.status">Status of this Memo</a></h1>
501         <p>This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain
502            material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s)
503            controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of
504            such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the
505            copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of
506            it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it
507            into languages other than English.
508         </p>
509         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
510            that other groups may also distribute working documents as Internet-Drafts.
511         </p>
512         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
513            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
514            in progress”.
515         </p>
516         <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
517         </p>
518         <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
519         </p>
520         <p>This Internet-Draft will expire on January 14, 2010.</p>
521      </div>
522      <div id="rfc.copyrightnotice">
523         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
524         <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
525         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date
526            of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
527         </p>
528      </div>
529      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
530      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
531         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
532         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
533         5 defines range-specific requests and the rules for constructing and combining responses to those requests.
534      </p>
535      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
536      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
537         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
538      </p>
539      <p>The changes in this draft are summarized in <a href="#changes.since.06" title="Since draft-ietf-httpbis-p5-range-06">Appendix&nbsp;D.8</a>.
540      </p>
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></li>
554         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul>
555               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
556               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
557            </ul>
558         </li>
559         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
560         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
561               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
562               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
563               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
564               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
565                     <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
566                     <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>
567                  </ul>
568               </li>
569            </ul>
570         </li>
571         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
572               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
573            </ul>
574         </li>
575         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
576         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
577         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
578               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
579               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
580            </ul>
581         </li>
582         <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>
583         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
584               <li><a href="#rfc.section.B.1">B.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
585               <li><a href="#rfc.section.B.2">B.2</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
586            </ul>
587         </li>
588         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
589         <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>
590               <li><a href="#rfc.section.D.1">D.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC2616</a></li>
591               <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>
592               <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>
593               <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>
594               <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>
595               <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>
596               <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>
597               <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>
598            </ul>
599         </li>
600         <li><a href="#rfc.index">Index</a></li>
601         <li><a href="#rfc.authors">Authors' Addresses</a></li>
602      </ul>
603      <div id="introduction">
604         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
605         <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
606            has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
607            rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
608            request only a subset of a larger representation, such as a single page of a very large document or only part of an image
609            to be rendered by a device with limited local storage.
610         </p>
611         <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
612            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
613            request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
614            full responses by intermediate caches that might not implement the feature.
615         </p>
616         <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
617            requests for byte ranges.
618         </p>
619         <div id="intro.requirements">
620            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
621            <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"
622               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>.
623            </p>
624            <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
625            </p>
626         </div>
627         <div id="notation">
628            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
629            <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.
630            </p>
631            <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
632               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
633               and WSP (whitespace).
634            </p>
635            <div id="core.rules">
636               <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>
637               <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>:
638               </p>
639               <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;
640  <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;
641</pre></div>
642            <div id="abnf.dependencies">
643               <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>
644               <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
645               <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 3.2</a>&gt;
646</pre><div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#entity.tags" title="Entity Tags">Section 2</a>&gt;
647</pre></div>
648         </div>
649      </div>
650      <div id="range.units">
651         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#range.units">Range Units</a></h1>
652         <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1
653            uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;5.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;5.2</a>) header fields. An entity can be broken down into subranges according to various structural units.
654         </p>
655         <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>
656  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
657  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a>
658</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
659            unit defined by HTTP/1.1 is "bytes".
660         </p>
661         <p id="rfc.section.2.p.4">If a range unit is not understood in a request, a server <em class="bcp14">MUST</em> ignore the whole Range header (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;5.4</a>). If a range unit is not understood in a response, an intermediary <em class="bcp14">SHOULD</em> pass the response to the client; a client <em class="bcp14">MUST</em> fail.
662         </p>
663      </div>
664      <div>
665         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
666         </h1>
667         <div id="status.206">
668            <div id="rfc.iref.2.1"></div>
669            <div id="rfc.iref.s.1"></div>
670            <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>
671            <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.
672            </p>
673            <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
674            </p>
675            <ul>
676               <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
677                  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.
678               </li>
679               <li>Date</li>
680               <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
681               <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
682                  variant
683               </li>
684            </ul>
685            <p id="rfc.section.3.1.p.3">If the 206 response is the result of an If-Range request, the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. Otherwise, the response <em class="bcp14">MUST</em> include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
686            </p>
687            <p id="rfc.section.3.1.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see <a href="#combining.byte.ranges" title="Combining Ranges">Section&nbsp;4</a>.
688            </p>
689            <p id="rfc.section.3.1.p.5">A cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> cache 206 (Partial Content) responses. Furthermore, if a response uses a range unit that is not understood by the cache, then
690               it <em class="bcp14">MUST NOT</em> be cached either.
691            </p>
692         </div>
693         <div id="status.416">
694            <div id="rfc.iref.4.1"></div>
695            <div id="rfc.iref.s.2"></div>
696            <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>
697            <p id="rfc.section.3.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range request-header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;5.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request
698               did not include an If-Range request-header field. (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec
699               values were greater than the current length of the selected resource.)
700            </p>
701            <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range entity-header field specifying the current length of the selected resource (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.
702            </p>
703         </div>
704      </div>
705      <div id="combining.byte.ranges">
706         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></h1>
707         <p id="rfc.section.4.p.1">A response might transfer only a subrange of an entity-body, either the request included one or more Range specifications,
708            or because a connection was broken prematurely. After several such transfers, a cache might have received several ranges of
709            the same entity-body.
710         </p>
711         <p id="rfc.section.4.p.2">If a cache has a stored non-empty set of subranges for an entity, and an incoming response transfers another subrange, the
712            cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
713         </p>
714         <ul>
715            <li>Both the incoming response and the cache entry have a cache validator.</li>
716            <li>The two cache validators match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak and Strong Validators">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
717            </li>
718         </ul>
719         <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
720            response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
721         </p>
722      </div>
723      <div id="header.fields">
724         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
725         <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>
726         <p id="rfc.section.5.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
727            receives the entity.
728         </p>
729         <div id="header.accept-ranges">
730            <div id="rfc.iref.a.1"></div>
731            <div id="rfc.iref.h.1"></div>
732            <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>
733            <p id="rfc.section.5.1.p.1">The response-header "Accept-Ranges" field allows the server to indicate its acceptance of range requests for a resource:</p>
734            <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = "Accept-Ranges" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>
735  <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>   = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
736  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
737</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
738            </p>
739            <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: bytes
740</pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate range requests without having received this header for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
741            </p>
742            <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
743            </p>
744            <div id="rfc.figure.u.7"></div><pre class="text">  Accept-Ranges: none
745</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
746         </div>
747         <div id="header.content-range">
748            <div id="rfc.iref.c.1"></div>
749            <div id="rfc.iref.h.2"></div>
750            <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>
751            <p id="rfc.section.5.2.p.1">The entity-header "Content-Range" is sent with a partial entity-body to specify where in the full entity-body the partial
752               body should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
753            </p>
754            <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-range" class="smpl">Content-Range-v</a>
755  <a href="#header.content-range" class="smpl">Content-Range-v</a> = <a href="#header.content-range" class="smpl">content-range-spec</a>
756 
757  <a href="#header.content-range" class="smpl">content-range-spec</a>      = <a href="#header.content-range" class="smpl">byte-content-range-spec</a>
758                          / <a href="#header.content-range" class="smpl">other-content-range-spec</a>
759  <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>
760                            <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> "/"
761                            ( <a href="#header.content-range" class="smpl">instance-length</a> / "*" )
762 
763  <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>)
764                          / "*"
765                         
766  <a href="#header.content-range" class="smpl">instance-length</a>         = 1*<a href="#notation" class="smpl">DIGIT</a>
767 
768  <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>
769                             <a href="#header.content-range" class="smpl">other-range-resp-spec</a>
770  <a href="#header.content-range" class="smpl">other-range-resp-spec</a>    = *<a href="#notation" class="smpl">CHAR</a>
771</pre><p id="rfc.section.5.2.p.3">The header <em class="bcp14">SHOULD</em> indicate the total length of the full entity-body, unless this length is unknown or difficult to determine. The asterisk "*"
772               character means that the instance-length is unknown at the time when the response was generated.
773            </p>
774            <p id="rfc.section.5.2.p.4">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;5.4.1</a>), a byte-range-resp-spec <em class="bcp14">MUST</em> only specify one range, and <em class="bcp14">MUST</em> contain absolute byte positions for both the first and last byte of the range.
775            </p>
776            <p id="rfc.section.5.2.p.5">A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos value is less than its first-byte-pos value, or
777               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.
778            </p>
779            <p id="rfc.section.5.2.p.6">In the case of a byte range request: A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
780               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 "*".
781            </p>
782            <p id="rfc.section.5.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p>
783            <ul>
784               <li>The first 500 bytes: <span id="rfc.figure.u.9"></span><pre class="text">  bytes 0-499/1234
785</pre> </li>
786               <li>The second 500 bytes: <span id="rfc.figure.u.10"></span><pre class="text">  bytes 500-999/1234
787</pre> </li>
788               <li>All except for the first 500 bytes: <span id="rfc.figure.u.11"></span><pre class="text">  bytes 500-1233/1234
789</pre> </li>
790               <li>The last 500 bytes: <span id="rfc.figure.u.12"></span><pre class="text">  bytes 734-1233/1234
791</pre> </li>
792            </ul>
793            <p id="rfc.section.5.2.p.8">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
794               a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
795               a Content-Length header showing the number of bytes actually transferred. For example,
796            </p>
797            <div id="rfc.figure.u.13"></div><pre class="text">  HTTP/1.1 206 Partial Content
798  Date: Wed, 15 Nov 1995 06:25:24 GMT
799  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
800  Content-Range: bytes 21010-47021/47022
801  Content-Length: 26012
802  Content-Type: image/gif
803</pre><p id="rfc.section.5.2.p.10">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
804               ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
805               as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>. See <a href="#changes.from.rfc.2068" title="Changes from RFC 2068">Appendix&nbsp;B.1</a> for a compatibility issue.
806            </p>
807            <p id="rfc.section.5.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
808            </p>
809            <p id="rfc.section.5.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
810            </p>
811            <p id="rfc.section.5.2.p.13">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
812               the full entity).
813            </p>
814            <p id="rfc.section.5.2.p.14">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header
815               field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
816               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>).
817            </p>
818            <div class="note" id="rfc.section.5.2.p.15">
819               <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
820                  an unsatisfiable Range request-header, since not all servers implement this request-header.
821               </p>
822            </div>
823         </div>
824         <div id="header.if-range">
825            <div id="rfc.iref.i.1"></div>
826            <div id="rfc.iref.h.3"></div>
827            <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>
828            <p id="rfc.section.5.3.p.1">If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its
829               cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.)
830               However, if the condition fails because the entity has been modified, the client would then have to make a second request
831               to obtain the entire current entity-body.
832            </p>
833            <p id="rfc.section.5.3.p.2">The request header "If-Range" allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity
834               is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity'.
835            </p>
836            <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.if-range" class="smpl">If-Range</a>   = "If-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a>
837  <a href="#header.if-range" class="smpl">If-Range-v</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
838</pre><p id="rfc.section.5.3.p.4">If the client has no entity tag for an entity, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header. (The server can distinguish between a valid HTTP-date and any form of entity-tag by examining
839               no more than two characters.) The If-Range header <em class="bcp14">SHOULD</em> only be used together with a Range header, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header, or if the server does not support the sub-range operation.
840            </p>
841            <p id="rfc.section.5.3.p.5">If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial Content) response. If the entity tag does not match, then
842               the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response.
843            </p>
844         </div>
845         <div id="header.range">
846            <div id="rfc.iref.r.1"></div>
847            <div id="rfc.iref.h.4"></div>
848            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.range">Range</a></h2>
849            <div id="byte.ranges">
850               <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>
851               <p id="rfc.section.5.4.1.p.1">Since all HTTP entities are represented in HTTP messages as sequences of bytes, the concept of a byte range is meaningful
852                  for any HTTP entity. (However, not all clients and servers need to support byte-range operations.)
853               </p>
854               <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the entity-body (not necessarily the same as the message-body).</p>
855               <div id="rule.ranges-specifier">
856                  <p id="rfc.section.5.4.1.p.3">        A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single entity.
857                  </p>
858               </div>
859               <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
860  <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> )
861  <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> ]
862  <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
863  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
864</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
865                  gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
866                  at zero.
867               </p>
868               <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
869                  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.
870               </p>
871               <p id="rfc.section.5.4.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the entity-body, last-byte-pos
872                  is taken to be equal to one less than the current length of the entity-body in bytes.
873               </p>
874               <p id="rfc.section.5.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the entity.</p>
875               <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
876  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
877</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the suffix-length value. (That
878                  is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
879                  entire entity-body is used.
880               </p>
881               <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
882                  length of the entity-body, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is
883                  satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> return a response with a status of 416 (Requested range not satisfiable). Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a status of 206 (Partial Content) containing the satisfiable ranges of the entity-body.
884               </p>
885               <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
886               <ul>
887                  <li>The first 500 bytes (byte offsets 0-499, inclusive): <span id="rfc.figure.u.17"></span><pre class="text">  bytes=0-499
888</pre> </li>
889                  <li>The second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.18"></span><pre class="text">  bytes=500-999
890</pre> </li>
891                  <li>The final 500 bytes (byte offsets 9500-9999, inclusive): <span id="rfc.figure.u.19"></span><pre class="text">  bytes=-500
892</pre> Or: <span id="rfc.figure.u.20"></span><pre class="text">  bytes=9500-
893</pre> </li>
894                  <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
895</pre> </li>
896                  <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
897  bytes=500-700,601-999
898</pre> </li>
899               </ul>
900            </div>
901            <div id="range.retrieval.requests">
902               <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>
903               <p id="rfc.section.5.4.2.p.1">HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies
904                  to the entity returned as the result of the request:
905               </p>
906               <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a>   = "Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
907  <a href="#range.retrieval.requests" class="smpl">Range-v</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a>
908          / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
909  <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = 1*<a href="#notation" class="smpl">CHAR</a>
910</pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when possible,
911                  since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
912                  entities.
913               </p>
914               <p id="rfc.section.5.4.2.p.4">If the server supports the Range header and the specified range or ranges are appropriate for the entity: </p>
915               <ul>
916                  <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
917                     words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
918                  </li>
919                  <li>The presence of a Range header in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match, or
920                     one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
921                     is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
922                  </li>
923               </ul>
924               <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (see <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>) in addition to the Range header.
925               </p>
926               <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
927                  entity in reply, it <em class="bcp14">SHOULD</em> only return the requested range to its client. It <em class="bcp14">SHOULD</em> store the entire received response in its cache if that is consistent with its cache allocation policies.
928               </p>
929            </div>
930         </div>
931      </div>
932      <div id="IANA.considerations">
933         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
934         <div id="message.header.registration">
935            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#message.header.registration">Message Header Registration</a></h2>
936            <p id="rfc.section.6.1.p.1">The Message Header Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
937            </p>
938            <div id="rfc.table.1">
939               <div id="iana.header.registration.table"></div>
940               <table class="tt full left" cellpadding="3" cellspacing="0">
941                  <thead>
942                     <tr>
943                        <th>Header Field Name</th>
944                        <th>Protocol</th>
945                        <th>Status</th>
946                        <th>Reference</th>
947                     </tr>
948                  </thead>
949                  <tbody>
950                     <tr>
951                        <td class="left">Accept-Ranges</td>
952                        <td class="left">http</td>
953                        <td class="left">standard</td>
954                        <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
955                        </td>
956                     </tr>
957                     <tr>
958                        <td class="left">Content-Range</td>
959                        <td class="left">http</td>
960                        <td class="left">standard</td>
961                        <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
962                        </td>
963                     </tr>
964                     <tr>
965                        <td class="left">If-Range</td>
966                        <td class="left">http</td>
967                        <td class="left">standard</td>
968                        <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section&nbsp;5.3</a>
969                        </td>
970                     </tr>
971                     <tr>
972                        <td class="left">Range</td>
973                        <td class="left">http</td>
974                        <td class="left">standard</td>
975                        <td class="left"><a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a>
976                        </td>
977                     </tr>
978                  </tbody>
979               </table>
980            </div>
981            <p id="rfc.section.6.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
982         </div>
983      </div>
984      <div id="security.considerations">
985         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
986         <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>.
987         </p>
988      </div>
989      <div id="ack">
990         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
991         <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
992            from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
993            Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
994         </p>
995      </div>
996      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
997      </h1>
998      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
999      </h2>
1000      <table>
1001         <tr>
1002            <td class="reference"><b id="Part1">[Part1]</b></td>
1003            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-07">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-07 (work in progress), July&nbsp;2009.
1004            </td>
1005         </tr>
1006         <tr>
1007            <td class="reference"><b id="Part3">[Part3]</b></td>
1008            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-07">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-07 (work in progress), July&nbsp;2009.
1009            </td>
1010         </tr>
1011         <tr>
1012            <td class="reference"><b id="Part4">[Part4]</b></td>
1013            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-07">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-07 (work in progress), July&nbsp;2009.
1014            </td>
1015         </tr>
1016         <tr>
1017            <td class="reference"><b id="Part6">[Part6]</b></td>
1018            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-07">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-07 (work in progress), July&nbsp;2009.
1019            </td>
1020         </tr>
1021         <tr>
1022            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
1023            <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.
1024            </td>
1025         </tr>
1026         <tr>
1027            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1028            <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.
1029            </td>
1030         </tr>
1031         <tr>
1032            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1033            <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.
1034            </td>
1035         </tr>
1036      </table>
1037      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
1038      </h2>
1039      <table>
1040         <tr>
1041            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1042            <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.
1043            </td>
1044         </tr>
1045         <tr>
1046            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1047            <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.
1048            </td>
1049         </tr>
1050         <tr>
1051            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
1052            <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.
1053            </td>
1054         </tr>
1055      </table>
1056      <div id="internet.media.type.multipart.byteranges">
1057         <div id="rfc.iref.m.1"></div>
1058         <div id="rfc.iref.m.2"></div>
1059         <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>
1060         <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
1061            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>.
1062         </p>
1063         <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
1064            required boundary parameter specifies the boundary string used to separate each body-part.
1065         </p>
1066         <p id="rfc.section.A.p.3"></p>
1067         <dl>
1068            <dt>Type name:</dt>
1069            <dd>multipart</dd>
1070            <dt>Subtype name:</dt>
1071            <dd>byteranges</dd>
1072            <dt>Required parameters:</dt>
1073            <dd>boundary</dd>
1074            <dt>Optional parameters:</dt>
1075            <dd>none</dd>
1076            <dt>Encoding considerations:</dt>
1077            <dd>only "7bit", "8bit", or "binary" are permitted</dd>
1078            <dt>Security considerations:</dt>
1079            <dd>none</dd>
1080            <dt>Interoperability considerations:</dt>
1081            <dd>none</dd>
1082            <dt>Published specification:</dt>
1083            <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
1084            </dd>
1085            <dt>Applications that use this media type:</dt>
1086            <dt>Additional information:</dt>
1087            <dd>
1088               <dl>
1089                  <dt>Magic number(s):</dt>
1090                  <dd>none</dd>
1091                  <dt>File extension(s):</dt>
1092                  <dd>none</dd>
1093                  <dt>Macintosh file type code(s):</dt>
1094                  <dd>none</dd>
1095               </dl>
1096            </dd>
1097            <dt>Person and email address to contact for further information:</dt>
1098            <dd>See Authors Section.</dd>
1099            <dt>Intended usage:</dt>
1100            <dd>COMMON</dd>
1101            <dt>Restrictions on usage:</dt>
1102            <dd>none</dd>
1103            <dt>Author/Change controller:</dt>
1104            <dd>IESG</dd>
1105         </dl>
1106         <div id="rfc.figure.u.24"></div>
1107         <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
1108  Date: Wed, 15 Nov 1995 06:25:24 GMT
1109  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
1110  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1111 
1112  --THIS_STRING_SEPARATES
1113  Content-type: application/pdf
1114  Content-range: bytes 500-999/8000
1115 
1116  ...the first range...
1117  --THIS_STRING_SEPARATES
1118  Content-type: application/pdf
1119  Content-range: bytes 7000-7999/8000
1120 
1121  ...the second range
1122  --THIS_STRING_SEPARATES--
1123</pre><p id="rfc.section.A.p.5">Notes: </p>
1124         <ol>
1125            <li>Additional CRLFs may precede the first boundary string in the entity.</li>
1126            <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.
1127            </li>
1128            <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.
1129            </li>
1130         </ol>
1131      </div>
1132      <div id="compatibility">
1133         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
1134         <div id="changes.from.rfc.2068">
1135            <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
1136            <p id="rfc.section.B.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
1137               for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
1138               computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
1139            </p>
1140            <p id="rfc.section.B.1.p.2">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving
1141               a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length
1142               of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">Section&nbsp;5.2</a>)
1143            </p>
1144            <p id="rfc.section.B.1.p.3">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send
1145               needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">3.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">5.3</a>)
1146            </p>
1147            <p id="rfc.section.B.1.p.4">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document.
1148               The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside
1149               of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">3.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.7" title="Content-Range">5.2</a>)
1150            </p>
1151         </div>
1152         <div id="changes.from.rfc.2616">
1153            <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
1154            <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
1155            </p>
1156            <p id="rfc.section.B.2.p.2">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
1157            </p>
1158         </div>
1159      </div>
1160      <div id="collected.abnf">
1161         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
1162         <div id="rfc.figure.u.25"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
1163<a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> = acceptable-ranges
1164
1165<a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range:" OWS Content-Range-v
1166<a href="#header.content-range" class="smpl">Content-Range-v</a> = content-range-spec
1167
1168<a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part1], Section 3.2&gt;
1169
1170<a href="#header.if-range" class="smpl">If-Range</a> = "If-Range:" OWS If-Range-v
1171<a href="#header.if-range" class="smpl">If-Range-v</a> = entity-tag / HTTP-date
1172
1173<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
1174
1175<a href="#range.retrieval.requests" class="smpl">Range</a> = "Range:" OWS Range-v
1176<a href="#range.retrieval.requests" class="smpl">Range-v</a> = byte-ranges-specifier / other-ranges-specifier
1177
1178<a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = ( *( "," OWS ) range-unit *( OWS "," [ OWS
1179 range-unit ] ) ) / "none"
1180
1181<a href="#header.content-range" class="smpl">byte-content-range-spec</a> = bytes-unit SP byte-range-resp-spec "/" (
1182 instance-length / "*" )
1183<a href="#header.content-range" class="smpl">byte-range-resp-spec</a> = ( first-byte-pos "-" last-byte-pos ) / "*"
1184<a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = ( *( "," OWS ) byte-range-spec ) / (
1185 suffix-byte-range-spec *( OWS "," [ ( OWS byte-range-spec ) /
1186 suffix-byte-range-spec ] ) )
1187<a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ]
1188<a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set
1189<a href="#range.units" class="smpl">bytes-unit</a> = "bytes"
1190
1191<a href="#header.content-range" class="smpl">content-range-spec</a> = byte-content-range-spec /
1192 other-content-range-spec
1193
1194<a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in [Part4], Section 2&gt;
1195
1196<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT
1197
1198<a href="#header.content-range" class="smpl">instance-length</a> = 1*DIGIT
1199
1200<a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*DIGIT
1201
1202<a href="#header.content-range" class="smpl">other-content-range-spec</a> = other-range-unit SP other-range-resp-spec
1203<a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *CHAR
1204<a href="#range.units" class="smpl">other-range-unit</a> = token
1205<a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = 1*CHAR
1206
1207<a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit
1208
1209<a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" suffix-length
1210<a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT
1211
1212<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
1213
1214
1215</pre><div id="rfc.figure.u.26"></div>
1216         <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
1217; Content-Range defined but not used
1218; If-Range defined but not used
1219; Range defined but not used
1220</pre></div>
1221      <div id="change.log">
1222         <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>
1223         <div>
1224            <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
1225            </h2>
1226            <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>.
1227            </p>
1228         </div>
1229         <div>
1230            <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
1231            </h2>
1232            <p id="rfc.section.D.2.p.1">Closed issues: </p>
1233            <ul>
1234               <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;)
1235               </li>
1236               <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"
1237               </li>
1238               <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"
1239               </li>
1240            </ul>
1241         </div>
1242         <div>
1243            <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
1244            </h2>
1245            <p id="rfc.section.D.3.p.1">Closed issues: </p>
1246            <ul>
1247               <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"
1248               </li>
1249            </ul>
1250            <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;):
1251            </p>
1252            <ul>
1253               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1254            </ul>
1255         </div>
1256         <div id="changes.since.02">
1257            <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>
1258            <p id="rfc.section.D.4.p.1">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
1259            </p>
1260            <ul>
1261               <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
1262            </ul>
1263         </div>
1264         <div id="changes.since.03">
1265            <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>
1266         </div>
1267         <div id="changes.since.04">
1268            <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>
1269            <p id="rfc.section.D.6.p.1">Closed issues: </p>
1270            <ul>
1271               <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"
1272               </li>
1273            </ul>
1274            <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;):
1275            </p>
1276            <ul>
1277               <li>Use "/" instead of "|" for alternatives.</li>
1278               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1279               <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
1280            </ul>
1281         </div>
1282         <div id="changes.since.05">
1283            <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>
1284            <p id="rfc.section.D.7.p.1">Closed issues: </p>
1285            <ul>
1286               <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"
1287               </li>
1288            </ul>
1289            <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;):
1290            </p>
1291            <ul>
1292               <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
1293            </ul>
1294            <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;):
1295            </p>
1296            <ul>
1297               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
1298            </ul>
1299         </div>
1300         <div id="changes.since.06">
1301            <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>
1302            <p id="rfc.section.D.8.p.1">Closed issues: </p>
1303            <ul>
1304               <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"
1305               </li>
1306            </ul>
1307         </div>
1308      </div>
1309      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1310      <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>
1311      </p>
1312      <div class="print2col">
1313         <ul class="ind">
1314            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
1315                  <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.2.1"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">B.1</a>, <a href="#rfc.xref.status.206.2">B.2</a></li>
1316               </ul>
1317            </li>
1318            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1319                  <li>416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">5.2</a>, <a href="#rfc.xref.status.416.2">B.1</a></li>
1320               </ul>
1321            </li>
1322            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1323                  <li>Accept-Ranges header&nbsp;&nbsp;<a href="#rfc.iref.a.1"><b>5.1</b></a>, <a href="#rfc.xref.header.accept-ranges.1">6.1</a></li>
1324               </ul>
1325            </li>
1326            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1327                  <li>Content-Range header&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.1</a>, <a href="#rfc.xref.header.content-range.5">B.1</a>, <a href="#rfc.xref.header.content-range.6">B.1</a>, <a href="#rfc.xref.header.content-range.7">B.1</a></li>
1328               </ul>
1329            </li>
1330            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1331                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1332                     <ul>
1333                        <li><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>5.1</b></a></li>
1334                        <li><tt>Accept-Ranges-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>5.1</b></a></li>
1335                        <li><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>5.1</b></a></li>
1336                        <li><tt>byte-content-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>5.2</b></a></li>
1337                        <li><tt>byte-range-resp-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>5.2</b></a></li>
1338                        <li><tt>byte-range-set</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>5.4.1</b></a></li>
1339                        <li><tt>byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>5.4.1</b></a></li>
1340                        <li><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>5.4.1</b></a></li>
1341                        <li><tt>bytes-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2</b></a></li>
1342                        <li><tt>Content-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>5.2</b></a></li>
1343                        <li><tt>content-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>5.2</b></a></li>
1344                        <li><tt>Content-Range-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>5.2</b></a></li>
1345                        <li><tt>first-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>5.4.1</b></a></li>
1346                        <li><tt>If-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>5.3</b></a></li>
1347                        <li><tt>If-Range-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>5.3</b></a></li>
1348                        <li><tt>instance-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>5.2</b></a></li>
1349                        <li><tt>last-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>5.4.1</b></a></li>
1350                        <li><tt>other-range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>2</b></a></li>
1351                        <li><tt>Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>5.4.2</b></a></li>
1352                        <li><tt>range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
1353                        <li><tt>ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>5.4.1</b></a></li>
1354                        <li><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>5.4.1</b></a></li>
1355                        <li><tt>suffix-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>5.4.1</b></a></li>
1356                     </ul>
1357                  </li>
1358               </ul>
1359            </li>
1360            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1361                  <li>Headers&nbsp;&nbsp;
1362                     <ul>
1363                        <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.1</a></li>
1364                        <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.1</a>, <a href="#rfc.xref.header.content-range.5">B.1</a>, <a href="#rfc.xref.header.content-range.6">B.1</a>, <a href="#rfc.xref.header.content-range.7">B.1</a></li>
1365                        <li>If-Range&nbsp;&nbsp;<a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.iref.h.3"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.2">5.4.2</a>, <a href="#rfc.xref.header.if-range.3">6.1</a>, <a href="#rfc.xref.header.if-range.4">B.1</a></li>
1366                        <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.1</a></li>
1367                     </ul>
1368                  </li>
1369               </ul>
1370            </li>
1371            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
1372                  <li>If-Range header&nbsp;&nbsp;<a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.iref.i.1"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.2">5.4.2</a>, <a href="#rfc.xref.header.if-range.3">6.1</a>, <a href="#rfc.xref.header.if-range.4">B.1</a></li>
1373               </ul>
1374            </li>
1375            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
1376                  <li>Media Type&nbsp;&nbsp;
1377                     <ul>
1378                        <li>multipart/byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>A</b></a></li>
1379                        <li>multipart/x-byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.4">A</a></li>
1380                     </ul>
1381                  </li>
1382                  <li>multipart/byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>A</b></a></li>
1383                  <li>multipart/x-byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.3">A</a></li>
1384               </ul>
1385            </li>
1386            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1387                  <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>, <a href="#rfc.xref.Part1.7">B.1</a><ul>
1388                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a></li>
1389                        <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>
1390                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2.2</a></li>
1391                     </ul>
1392                  </li>
1393                  <li><em>Part3</em>&nbsp;&nbsp;<a href="#Part3"><b>9.1</b></a>, <a href="#rfc.xref.Part3.1">B.1</a></li>
1394                  <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="#Part4"><b>9.1</b></a><ul>
1395                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2.2</a></li>
1396                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">4</a></li>
1397                     </ul>
1398                  </li>
1399                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#Part6"><b>9.1</b></a>, <a href="#rfc.xref.Part6.1">B.1</a></li>
1400               </ul>
1401            </li>
1402            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1403                  <li>Range header&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.1</a></li>
1404                  <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>
1405                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">A</a></li>
1406                     </ul>
1407                  </li>
1408                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>9.1</b></a></li>
1409                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#RFC2616"><b>9.2</b></a>, <a href="#rfc.xref.RFC2616.1">D.1</a></li>
1410                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">6.1</a>, <a href="#RFC3864"><b>9.2</b></a></li>
1411                  <li><em>RFC4288</em>&nbsp;&nbsp;<a href="#RFC4288"><b>9.2</b></a>, <a href="#rfc.xref.RFC4288.1">A</a></li>
1412                  <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>
1413                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
1414                     </ul>
1415                  </li>
1416               </ul>
1417            </li>
1418            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
1419                  <li>Status Codes&nbsp;&nbsp;
1420                     <ul>
1421                        <li>206 Partial Content&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">B.1</a>, <a href="#rfc.xref.status.206.2">B.2</a></li>
1422                        <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">B.1</a></li>
1423                     </ul>
1424                  </li>
1425               </ul>
1426            </li>
1427         </ul>
1428      </div>
1429      <div class="avoidbreak">
1430         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1431         <p><b>Roy T. Fielding</b>
1432            (editor)
1433            <br>Day Software<br>23 Corporate Plaza DR, Suite 280<br>Newport Beach, CA&nbsp;92660<br>USA<br>Phone: <a href="tel:+1-949-706-5300">+1-949-706-5300</a><br>Fax: <a href="fax:+1-949-706-5305">+1-949-706-5305</a><br>EMail: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
1434         <p><b>Jim Gettys</b><br>One Laptop per Child<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>EMail: <a href="mailto:jg@laptop.org">jg@laptop.org</a><br>URI: <a href="http://www.laptop.org/">http://www.laptop.org/</a></p>
1435         <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>
1436         <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>
1437         <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>
1438         <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>
1439         <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>
1440         <p><b>Yves Lafon</b>
1441            (editor)
1442            <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>
1443         <p><b>Julian F. Reschke</b>
1444            (editor)
1445            <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>
1446      </div>
1447   </body>
1448</html>
Note: See TracBrowser for help on using the repository browser.