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

Last change on this file since 2726 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: 104.8 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>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title><script>
7var buttonsAdded = false;
8
9function initFeedback() {
10  var fb = document.createElement("div");
11  fb.className = "feedback noprint";
12  fb.setAttribute("onclick", "feedback();");
13  fb.appendChild(document.createTextNode("feedback"));
14
15  var bodyl = document.getElementsByTagName("body");
16  bodyl.item(0).appendChild(fb);
17}
18
19function feedback() {
20  toggleButtonsToElementsByName("h1");
21  toggleButtonsToElementsByName("h2");
22  toggleButtonsToElementsByName("h3");
23  toggleButtonsToElementsByName("h4");
24
25  buttonsAdded = !buttonsAdded;
26}
27
28function toggleButtonsToElementsByName(name) {
29  var list = document.getElementsByTagName(name);
30  for (var i = 0; i < list.length; i++) {
31    toggleButton(list.item(i));
32  }
33}
34
35function toggleButton(node) {
36  if (! buttonsAdded) {
37
38    // docname
39    var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:";
40
41    var id = node.getAttribute("id");
42    // better id available?
43    var titlelinks = node.getElementsByTagName("a");
44    for (var i = 0; i < titlelinks.length; i++) {
45      var tl = titlelinks.item(i);
46      if (tl.getAttribute("id")) {
47        id = tl.getAttribute("id");
48      }
49    }
50
51    // ref
52    var ref = window.location.toString();
53    var hash = ref.indexOf("#");
54    if (hash != -1) {
55      ref = ref.substring(0, hash);
56    }
57    if (id != "") {
58      ref += "#" + id;
59    }
60
61    // docname
62    var docname = "draft-ietf-httpbis-p5-range-latest";
63
64    // section
65    var section = node.textContent;
66    section = section.replace("\u00a0", " ");
67
68    // build URI from template
69    var uri = template.replace("{docname}", encodeURIComponent(docname));
70    uri = uri.replace("{section}", encodeURIComponent(section));
71    uri = uri.replace("{ref}", encodeURIComponent(ref));
72
73    var button = document.createElement("a");
74    button.className = "fbbutton noprint";
75    button.setAttribute("href", uri);
76    button.appendChild(document.createTextNode("send feedback"));
77    node.appendChild(button);
78  }
79  else {
80    var buttons = node.getElementsByTagName("a");
81    for (var i = 0; i < buttons.length; i++) {
82      var b = buttons.item(i);
83      if (b.className == "fbbutton noprint") {
84        node.removeChild(b);
85      }
86    }
87  }
88}</script><style type="text/css" title="Xml2Rfc (sans serif)">
89a {
90  text-decoration: none;
91}
92a.smpl {
93  color: black;
94}
95a:hover {
96  text-decoration: underline;
97}
98a:active {
99  text-decoration: underline;
100}
101address {
102  margin-top: 1em;
103  margin-left: 2em;
104  font-style: normal;
105}
106body {
107  color: black;
108  font-family: cambria, helvetica, arial, sans-serif;
109  font-size: 11pt;
110  margin-right: 2em;
111}
112cite {
113  font-style: normal;
114}
115div.note {
116  margin-left: 2em;
117}
118dl {
119  margin-left: 2em;
120}
121ul.empty {
122  list-style-type: none;
123}
124ul.empty li {
125  margin-top: .5em;
126}
127dl p {
128  margin-left: 0em;
129}
130dt {
131  margin-top: .5em;
132}
133h1 {
134  font-size: 130%;
135  line-height: 21pt;
136  page-break-after: avoid;
137}
138h1.np {
139  page-break-before: always;
140}
141h2 {
142  font-size: 120%;
143  line-height: 15pt;
144  page-break-after: avoid;
145}
146h3 {
147  font-size: 110%;
148  page-break-after: avoid;
149}
150h4, h5, h6 {
151  page-break-after: avoid;
152}
153h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
154  color: black;
155}
156img {
157  margin-left: 3em;
158}
159li {
160  margin-left: 2em;
161}
162ol {
163  margin-left: 2em;
164}
165ol.la {
166  list-style-type: lower-alpha;
167}
168ol.ua {
169  list-style-type: upper-alpha;
170}
171ol p {
172  margin-left: 0em;
173}
174p {
175  margin-left: 2em;
176}
177pre {
178  margin-left: 3em;
179  background-color: lightyellow;
180  padding: .25em;
181  page-break-inside: avoid;
182}
183pre.text2 {
184  border-style: dotted;
185  border-width: 1px;
186  background-color: #f0f0f0;
187  width: 69em;
188}
189pre.inline {
190  background-color: white;
191  padding: 0em;
192}
193pre.text {
194  border-style: dotted;
195  border-width: 1px;
196  background-color: #f8f8f8;
197  width: 69em;
198}
199pre.drawing {
200  border-style: solid;
201  border-width: 1px;
202  background-color: #f8f8f8;
203  padding: 2em;
204}
205table {
206  margin-left: 2em;
207}
208table.tt {
209  vertical-align: top;
210  border-color: gray;
211}
212table.tt th {
213  border-color: gray;
214}
215table.tt td {
216  border-color: gray;
217}
218table.all {
219  border-style: solid;
220  border-width: 2px;
221}
222table.full {
223  border-style: solid;
224  border-width: 2px;
225}
226table.tt td {
227  vertical-align: top;
228}
229table.all td {
230  border-style: solid;
231  border-width: 1px;
232}
233table.full td {
234  border-style: none solid;
235  border-width: 1px;
236}
237table.tt th {
238  vertical-align: top;
239}
240table.all th {
241  border-style: solid;
242  border-width: 1px;
243}
244table.full th {
245  border-style: solid;
246  border-width: 1px 1px 2px 1px;
247}
248table.headers th {
249  border-style: none none solid none;
250  border-width: 2px;
251}
252table.left {
253  margin-right: auto;
254}
255table.right {
256  margin-left: auto;
257}
258table.center {
259  margin-left: auto;
260  margin-right: auto;
261}
262caption {
263  caption-side: bottom;
264  font-weight: bold;
265  font-size: 10pt;
266  margin-top: .5em;
267}
268
269table.header {
270  border-spacing: 1px;
271  width: 95%;
272  font-size: 11pt;
273  color: white;
274}
275td.top {
276  vertical-align: top;
277}
278td.topnowrap {
279  vertical-align: top;
280  white-space: nowrap;
281}
282table.header td {
283  background-color: gray;
284  width: 50%;
285}
286table.header a {
287  color: white;
288}
289td.reference {
290  vertical-align: top;
291  white-space: nowrap;
292  padding-right: 1em;
293}
294thead {
295  display:table-header-group;
296}
297ul.toc, ul.toc ul {
298  list-style: none;
299  margin-left: 1.5em;
300  padding-left: 0em;
301}
302ul.toc li {
303  line-height: 150%;
304  font-weight: bold;
305  margin-left: 0em;
306}
307ul.toc li li {
308  line-height: normal;
309  font-weight: normal;
310  font-size: 10pt;
311  margin-left: 0em;
312}
313li.excluded {
314  font-size: 0pt;
315}
316ul p {
317  margin-left: 0em;
318}
319.title, .filename, h1, h2, h3, h4 {
320  font-family: candara, helvetica, arial, sans-serif;
321}
322samp, tt, code, pre {
323  font: consolas, monospace;
324}
325ul.ind, ul.ind ul {
326  list-style: none;
327  margin-left: 1.5em;
328  padding-left: 0em;
329  page-break-before: avoid;
330}
331ul.ind li {
332  font-weight: bold;
333  line-height: 200%;
334  margin-left: 0em;
335}
336ul.ind li li {
337  font-weight: normal;
338  line-height: 150%;
339  margin-left: 0em;
340}
341.avoidbreak {
342  page-break-inside: avoid;
343}
344.bcp14 {
345  font-style: normal;
346  text-transform: lowercase;
347  font-variant: small-caps;
348}
349.comment {
350  background-color: yellow;
351}
352.center {
353  text-align: center;
354}
355.error {
356  color: red;
357  font-style: italic;
358  font-weight: bold;
359}
360.figure {
361  font-weight: bold;
362  text-align: center;
363  font-size: 10pt;
364}
365.filename {
366  color: #333333;
367  font-size: 75%;
368  font-weight: bold;
369  line-height: 21pt;
370  text-align: center;
371}
372.fn {
373  font-weight: bold;
374}
375.left {
376  text-align: left;
377}
378.right {
379  text-align: right;
380}
381.title {
382  color: green;
383  font-size: 150%;
384  line-height: 18pt;
385  font-weight: bold;
386  text-align: center;
387  margin-top: 36pt;
388}
389.warning {
390  font-size: 130%;
391  background-color: yellow;
392}
393.feedback {
394  position: fixed;
395  bottom: 1%;
396  right: 1%;
397  padding: 3px 5px;
398  color: white;
399  border-radius: 5px;
400  background: #a00000;
401  border: 1px solid silver;
402}
403.fbbutton {
404  margin-left: 1em;
405  color: #303030;
406  font-size: small;
407  font-weight: normal;
408  background: #d0d000;
409  padding: 1px 4px;
410  border: 1px solid silver;
411  border-radius: 5px;
412}
413
414@media print {
415  .noprint {
416    display: none;
417  }
418
419  a {
420    color: black;
421    text-decoration: none;
422  }
423
424  table.header {
425    width: 90%;
426  }
427
428  td.header {
429    width: 50%;
430    color: black;
431    background-color: white;
432    vertical-align: top;
433    font-size: 110%;
434  }
435
436  ul.toc a:nth-child(2)::after {
437    content: leader('.') target-counter(attr(href), page);
438  }
439
440  ul.ind li li a {
441    content: target-counter(attr(href), page);
442  }
443
444  .print2col {
445    column-count: 2;
446    -moz-column-count: 2;
447    column-fill: auto;
448  }
449}
450
451@page {
452  @top-left {
453       content: "Internet-Draft";
454  }
455  @top-right {
456       content: "June 2014";
457  }
458  @top-center {
459       content: "HTTP/1.1 Range Requests";
460  }
461  @bottom-left {
462       content: "Fielding, et al.";
463  }
464  @bottom-center {
465       content: "Expires December 16, 2014";
466  }
467  @bottom-right {
468       content: "[Page " counter(page) "]";
469  }
470}
471
472@page:first {
473    @top-left {
474      content: normal;
475    }
476    @top-right {
477      content: normal;
478    }
479    @top-center {
480      content: normal;
481    }
482}
483</style><link rel="Contents" href="#rfc.toc">
484      <link rel="Author" href="#rfc.authors">
485      <link rel="Copyright" href="#rfc.copyrightnotice">
486      <link rel="Index" href="#rfc.index">
487      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
488      <link rel="Chapter" title="2 Range Units" href="#rfc.section.2">
489      <link rel="Chapter" title="3 Range Requests" href="#rfc.section.3">
490      <link rel="Chapter" title="4 Responses to a Range Request" href="#rfc.section.4">
491      <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5">
492      <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6">
493      <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7">
494      <link rel="Chapter" href="#rfc.section.8" title="8 References">
495      <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
496      <link rel="Appendix" title="B Changes from RFC 2616" href="#rfc.section.B">
497      <link rel="Appendix" title="C Imported ABNF" href="#rfc.section.C">
498      <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
499      <link rel="Alternate" title="RFC7233" href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7233.html">
500      <link href="p4-conditional.html" rel="prev">
501      <link href="p6-cache.html" rel="next">
502      <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/">
503      <meta name="keywords" content="Hypertext Transfer Protocol, HTTP, HTTP Range Requests">
504      <link rel="schema.dct" href="http://purl.org/dc/terms/">
505      <meta name="dct.creator" content="Fielding, R.">
506      <meta name="dct.creator" content="Lafon, Y.">
507      <meta name="dct.creator" content="Reschke, J. F.">
508      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
509      <meta name="dct.issued" scheme="ISO8601" content="2014-06-14">
510      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
511      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
512      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
513   </head>
514   <body onload="initFeedback();">
515      <table class="header">
516         <tbody>
517            <tr>
518               <td class="left">HTTPbis Working Group</td>
519               <td class="right">R. Fielding, Editor</td>
520            </tr>
521            <tr>
522               <td class="left">Internet-Draft</td>
523               <td class="right">Adobe</td>
524            </tr>
525            <tr>
526               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
527               </td>
528               <td class="right">Y. Lafon, Editor</td>
529            </tr>
530            <tr>
531               <td class="left">Intended status: Standards Track</td>
532               <td class="right">W3C</td>
533            </tr>
534            <tr>
535               <td class="left">Expires: December 16, 2014</td>
536               <td class="right">J. Reschke, Editor</td>
537            </tr>
538            <tr>
539               <td class="left"></td>
540               <td class="right">greenbytes</td>
541            </tr>
542            <tr>
543               <td class="left"></td>
544               <td class="right">June 14, 2014</td>
545            </tr>
546         </tbody>
547      </table>
548      <p class="title">Hypertext Transfer Protocol (HTTP/1.1): Range Requests<br><span class="filename">draft-ietf-httpbis-p5-range-latest</span></p>
549      <p style="color: green; text-align: center; font-size: 14pt; background-color: yellow;"><b>Note:</b> a later version of this document has been published as <a href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7233.html">RFC7233</a>.
550         
551      </p>
552      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
553      <p>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext
554         information systems. This document defines range requests and the rules for constructing and combining responses to those
555         requests.
556      </p>
557      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
558      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
559      </p>
560      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
561      </p>
562      <p><em>This is a temporary document for the purpose of tracking the editorial changes made during the AUTH48 (RFC publication) phase.</em>
563      </p>
564      <div id="rfc.status">
565         <h1><a href="#rfc.status">Status of This Memo</a></h1>
566         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
567         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
568            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
569         </p>
570         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
571            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
572            in progress”.
573         </p>
574         <p>This Internet-Draft will expire on December 16, 2014.</p>
575      </div>
576      <div id="rfc.copyrightnotice">
577         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
578         <p>Copyright © 2014 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
579         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
580            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
581            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
582            BSD License.
583         </p>
584         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
585            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
586            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
587            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
588            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
589            it into languages other than English.
590         </p>
591      </div>
592      <hr class="noprint">
593      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
594      <ul class="toc">
595         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
596               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#conformance">Conformance and Error Handling</a></li>
597               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a></li>
598            </ul>
599         </li>
600         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a><ul>
601               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
602               <li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#range.units.other">Other Range Units</a></li>
603               <li><a href="#rfc.section.2.3">2.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
604            </ul>
605         </li>
606         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#range.requests">Range Requests</a><ul>
607               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a></li>
608               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
609            </ul>
610         </li>
611         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#range.response">Responses to a Range Request</a><ul>
612               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
613               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
614               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
615               <li><a href="#rfc.section.4.4">4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Range Not Satisfiable</a></li>
616            </ul>
617         </li>
618         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
619               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.unit.registry">Range Unit Registry</a><ul>
620                     <li><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.unit.registry.procedure">Procedure</a></li>
621                     <li><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#range.unit.registration">Registrations</a></li>
622                  </ul>
623               </li>
624               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
625               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
626               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.http">Internet Media Type Registration</a><ul>
627                     <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges.reg">Internet Media Type multipart/byteranges</a></li>
628                  </ul>
629               </li>
630            </ul>
631         </li>
632         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
633               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#overlapping.ranges">Denial-of-Service Attacks Using Range</a></li>
634            </ul>
635         </li>
636         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
637         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
638               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
639               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
640            </ul>
641         </li>
642         <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>
643         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
644         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
645         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
646         <li><a href="#rfc.index">Index</a></li>
647         <li><a href="#rfc.authors">Authors' Addresses</a></li>
648      </ul>
649      <div id="introduction">
650         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
651         <p id="rfc.section.1.p.1">Hypertext Transfer Protocol (HTTP) clients often encounter interrupted data transfers as a result of canceled requests or
652            dropped connections. When a client has stored a partial representation, it is desirable to request the remainder of that representation
653            in a subsequent request rather than transfer the entire representation. Likewise, devices with limited local storage might
654            benefit from being able to request only a subset of a larger representation, such as a single page of a very large document,
655            or the dimensions of an embedded image.
656         </p>
657         <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type. Range requests
658            are an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so that recipients not implementing this feature (or not supporting it for the target resource)
659            can respond as if it is a normal GET request without impacting interoperability. Partial responses are indicated by a distinct
660            status code to not be mistaken for full responses by caches that might not implement the feature.
661         </p>
662         <p id="rfc.section.1.p.3">Although the range request mechanism is designed to allow for extensible range types, this specification only defines requests
663            for byte ranges.
664         </p>
665         <div id="conformance">
666            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#conformance">Conformance and Error Handling</a></h2>
667            <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"
668               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>.
669            </p>
670            <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
671            </p>
672         </div>
673         <div id="notation">
674            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
675            <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF List Extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator (similar to how the '*' operator indicates
676               repetition). <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;C</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected grammar with all list operators expanded to standard ABNF notation.
677            </p>
678         </div>
679      </div>
680      <div id="range.units">
681         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#range.units">Range Units</a></h1>
682         <p id="rfc.section.2.p.1">A representation can be partitioned into subranges according to various structural units, depending on the structure inherent
683            in the representation's media type. This "<dfn>range unit</dfn>" is used in the <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> (<a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;2.3</a>) response header field to advertise support for range requests, the <a href="#header.range" class="smpl">Range</a> (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;3.1</a>) request header field to delineate the parts of a representation that are requested, and the <a href="#header.content-range" class="smpl">Content-Range</a> (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;4.2</a>) payload header field to describe which part of a representation is being transferred.
684         </p>
685         <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#range.units" class="smpl">range-unit</a>       = <a href="#byte.ranges" class="smpl">bytes-unit</a> / <a href="#range.units.other" class="smpl">other-range-unit</a>
686</pre><div id="byte.ranges">
687            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#byte.ranges">Byte Ranges</a></h2>
688            <p id="rfc.section.2.1.p.1">Since representation data is transferred in payloads as a sequence of octets, a byte range is a meaningful substructure for
689               any representation transferable over HTTP (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). The "bytes" range unit is defined for expressing subranges of the data's octet sequence.
690            </p>
691            <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#byte.ranges" class="smpl">bytes-unit</a>       = "bytes"
692</pre><div id="rule.ranges-specifier">
693               <p id="rfc.section.2.1.p.3">        A byte-range request can specify a single range of bytes or a set of ranges within a single representation.</p>
694            </div>
695            <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#byte.ranges" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
696  <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> )
697  <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> ]
698  <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
699  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
700</pre><p id="rfc.section.2.1.p.5">The <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value in a <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> gives the byte-offset of the first byte in a range. The <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets
701               start at zero.
702            </p>
703            <p id="rfc.section.2.1.p.6">Examples of <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> values:
704            </p>
705            <ul>
706               <li>The first 500 bytes (byte offsets 0-499, inclusive): <span id="rfc.figure.u.4"></span><pre class="text">  bytes=0-499
707</pre> </li>
708               <li>The second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.5"></span><pre class="text">  bytes=500-999
709</pre> </li>
710            </ul>
711            <p id="rfc.section.2.1.p.7">A <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> is invalid if the <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value is present and less than the <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>.
712            </p>
713            <p id="rfc.section.2.1.p.8">A client can limit the number of bytes requested without knowing the size of the selected representation. If the <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value is absent, or if the value is greater than or equal to the current length of the representation data, the byte range
714               is interpreted as the remainder of the representation (i.e., the server replaces the value of <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> with a value that is one less than the current length of the selected representation).
715            </p>
716            <p id="rfc.section.2.1.p.9">A client can request the last N bytes of the selected representation using a <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a>.
717            </p>
718            <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
719  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
720</pre><p id="rfc.section.2.1.p.11">If the selected representation is shorter than the specified <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, the entire representation is used.
721            </p>
722            <p id="rfc.section.2.1.p.12">Additional examples, assuming a representation of length 10000: </p>
723            <ul>
724               <li>The final 500 bytes (byte offsets 9500-9999, inclusive): <span id="rfc.figure.u.7"></span><pre class="text">  bytes=-500
725</pre> Or: <span id="rfc.figure.u.8"></span><pre class="text">  bytes=9500-
726</pre> </li>
727               <li>The first and last bytes only (bytes 0 and 9999): <span id="rfc.figure.u.9"></span><pre class="text">  bytes=0-0,-1
728</pre> </li>
729               <li>Other valid (but not canonical) specifications of the second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.10"></span><pre class="text">  bytes=500-600,601-999
730  bytes=500-700,601-999
731</pre> </li>
732            </ul>
733            <p id="rfc.section.2.1.p.13">If a valid <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> includes at least one <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> with a <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> that is less than the current length of the representation, or at least one <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> with a non-zero <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, then the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is satisfiable. Otherwise, the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is unsatisfiable.
734            </p>
735            <p id="rfc.section.2.1.p.14">In the byte-range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients <em class="bcp14">MUST</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
736            </p>
737         </div>
738         <div id="range.units.other">
739            <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#range.units.other">Other Range Units</a></h2>
740            <p id="rfc.section.2.2.p.1">Range units are intended to be extensible. New range units ought to be registered with IANA, as defined in <a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;5.1</a>.
741            </p>
742            <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.13"></span>  <a href="#range.units.other" class="smpl">other-range-unit</a> = <a href="#imported.abnf" class="smpl">token</a>
743</pre></div>
744         <div id="header.accept-ranges">
745            <div id="rfc.iref.a.1"></div>
746            <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></h2>
747            <p id="rfc.section.2.3.p.1">The "Accept-Ranges" header field allows a server to indicate that it supports range requests for the target resource.</p>
748            <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
749  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
750</pre><p id="rfc.section.2.3.p.3">An origin server that supports byte-range requests for a given target resource <em class="bcp14">MAY</em> send
751            </p>
752            <div id="rfc.figure.u.13"></div><pre class="text">  Accept-Ranges: bytes
753</pre><p id="rfc.section.2.3.p.5">to indicate what range units are supported. A client <em class="bcp14">MAY</em> generate range requests without having received this header field for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
754            </p>
755            <p id="rfc.section.2.3.p.6">A server that does not support any kind of range request for the target resource <em class="bcp14">MAY</em> send
756            </p>
757            <div id="rfc.figure.u.14"></div><pre class="text">  Accept-Ranges: none
758</pre><p id="rfc.section.2.3.p.8">to advise the client not to attempt a range request.</p>
759         </div>
760      </div>
761      <div id="range.requests">
762         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#range.requests">Range Requests</a></h1>
763         <div id="header.range">
764            <div id="rfc.iref.r.1"></div>
765            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.range">Range</a></h2>
766            <p id="rfc.section.3.1.p.1">The "Range" header field on a GET request modifies the method semantics to request transfer of only one or more subranges
767               of the selected representation data, rather than the entire selected representation data.
768            </p>
769            <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  <a href="#header.range" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#header.range" class="smpl">other-ranges-specifier</a>
770  <a href="#header.range" class="smpl">other-ranges-specifier</a> = <a href="#range.units.other" class="smpl">other-range-unit</a> "=" <a href="#header.range" class="smpl">other-range-set</a>
771  <a href="#header.range" class="smpl">other-range-set</a> = 1*<a href="#imported.abnf" class="smpl">VCHAR</a>
772</pre><p id="rfc.section.3.1.p.3">A server <em class="bcp14">MAY</em> ignore the Range header field. However, origin servers and intermediate caches ought to support byte ranges when possible,
773               since Range supports efficient recovery from partially failed transfers and partial retrieval of large representations. A
774               server <em class="bcp14">MUST</em> ignore a Range header field received with a request method other than GET.
775            </p>
776            <p id="rfc.section.3.1.p.4">An origin server <em class="bcp14">MUST</em> ignore a Range header field that contains a range unit it does not understand. A proxy <em class="bcp14">MAY</em> discard a Range header field that contains a range unit it does not understand.
777            </p>
778            <p id="rfc.section.3.1.p.5">A server that supports range requests <em class="bcp14">MAY</em> ignore or reject a <a href="#header.range" class="smpl">Range</a> header field that consists of more than two overlapping ranges, or a set of many small ranges that are not listed in ascending
779               order, since both are indications of either a broken client or a deliberate denial-of-service attack (<a href="#overlapping.ranges" title="Denial-of-Service Attacks Using Range">Section&nbsp;6.1</a>). A client <em class="bcp14">SHOULD NOT</em> request multiple ranges that are inherently less efficient to process and transfer than a single range that encompasses the
780               same data.
781            </p>
782            <p id="rfc.section.3.1.p.6">A client that is requesting multiple ranges <em class="bcp14">SHOULD</em> list those ranges in ascending order (the order in which they would typically be received in a complete representation) unless
783               there is a specific need to request a later part earlier. For example, a user agent processing a large representation with
784               an internal catalog of parts might need to request later parts first, particularly if the representation consists of pages
785               stored in reverse order and the user agent wishes to transfer one page at a time.
786            </p>
787            <p id="rfc.section.3.1.p.7">The Range header field is evaluated after evaluating the precondition header fields defined in <a href="#RFC7232" id="rfc.xref.RFC7232.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>, and only if the result in absence of the Range header field would be a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. In other words, Range is ignored when a conditional GET would result in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response.
788            </p>
789            <p id="rfc.section.3.1.p.8">The If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;3.2</a>) can be used as a precondition to applying the Range header field.
790            </p>
791            <p id="rfc.section.3.1.p.9">If all of the preconditions are true, the server supports the Range header field for the target resource, and the specified
792               range(s) are valid and satisfiable (as defined in <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;2.1</a>), the server <em class="bcp14">SHOULD</em> send a <a href="#status.206" class="smpl">206 (Partial Content)</a> response with a payload containing one or more partial representations that correspond to the satisfiable ranges requested,
793               as defined in <a href="#range.response" title="Responses to a Range Request">Section&nbsp;4</a>.
794            </p>
795            <p id="rfc.section.3.1.p.10">If all of the preconditions are true, the server supports the Range header field for the target resource, and the specified
796               range(s) are invalid or unsatisfiable, the server <em class="bcp14">SHOULD</em> send a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response.
797            </p>
798         </div>
799         <div id="header.if-range">
800            <div id="rfc.iref.i.1"></div>
801            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.if-range">If-Range</a></h2>
802            <p id="rfc.section.3.2.p.1">If a client has a partial copy of a representation and wishes to have an up-to-date copy of the entire representation, it
803               could use the <a href="#header.range" class="smpl">Range</a> header field with a conditional GET (using either or both of <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> and <a href="p4-conditional.html#header.if-match" class="smpl">If-Match</a>.) However, if the precondition fails because the representation has been modified, the client would then have to make a second
804               request to obtain the entire current representation.
805            </p>
806            <p id="rfc.section.3.2.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is as follows:
807               if the representation is unchanged, send me the part(s) that I am requesting in Range; otherwise, send me the entire representation.
808            </p>
809            <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#imported.abnf" class="smpl">entity-tag</a> / <a href="#imported.abnf" class="smpl">HTTP-date</a>
810</pre><p id="rfc.section.3.2.p.4">A client <em class="bcp14">MUST NOT</em> generate an If-Range header field in a request that does not contain a <a href="#header.range" class="smpl">Range</a> header field. A server <em class="bcp14">MUST</em> ignore an If-Range header field received in a request that does not contain a <a href="#header.range" class="smpl">Range</a> header field. An origin server <em class="bcp14">MUST</em> ignore an If-Range header field received in a request for a target resource that does not support Range requests.
811            </p>
812            <p id="rfc.section.3.2.p.5">A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an entity-tag that is marked as weak. A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an <a href="#imported.abnf" class="smpl">HTTP-date</a> unless the client has no entity-tag for the corresponding representation and the date is a strong validator in the sense defined
813               by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>.
814            </p>
815            <p id="rfc.section.3.2.p.6">A server that evaluates an If-Range precondition <em class="bcp14">MUST</em> use the strong comparison function when comparing entity-tags (<a href="p4-conditional.html#entity.tag.comparison" title="Comparison">Section 2.3.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>) and <em class="bcp14">MUST</em> evaluate the condition as false if an <a href="#imported.abnf" class="smpl">HTTP-date</a> validator is provided that is not a strong validator in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>. A valid <a href="#imported.abnf" class="smpl">entity-tag</a> can be distinguished from a valid <a href="#imported.abnf" class="smpl">HTTP-date</a> by examining the first two characters for a DQUOTE.
816            </p>
817            <p id="rfc.section.3.2.p.7">If the validator given in the If-Range header field matches the current validator for the selected representation of the target
818               resource, then the server <em class="bcp14">SHOULD</em> process the <a href="#header.range" class="smpl">Range</a> header field as requested. If the validator does not match, the server <em class="bcp14">MUST</em> ignore the <a href="#header.range" class="smpl">Range</a> header field. Note that this comparison by exact match, including when the validator is an <a href="#imported.abnf" class="smpl">HTTP-date</a>, differs from the "earlier than or equal to" comparison used when evaluating an <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> conditional.
819            </p>
820         </div>
821      </div>
822      <div id="range.response">
823         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#range.response">Responses to a Range Request</a></h1>
824         <div id="status.206">
825            <div id="rfc.iref.2.1"></div>
826            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#status.206">206 Partial Content</a></h2>
827            <p id="rfc.section.4.1.p.1">The <dfn>206 (Partial Content)</dfn> status code indicates that the server is successfully fulfilling a range request for the target resource by transferring one
828               or more parts of the selected representation that correspond to the satisfiable ranges found in the request's <a href="#header.range" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;3.1</a>).
829            </p>
830            <p id="rfc.section.4.1.p.2">If a single part is being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field, describing what range of the selected representation is enclosed, and a payload consisting of the range. For
831               example:
832            </p>
833            <div id="rfc.figure.u.17"></div><pre class="text">HTTP/1.1 206 Partial Content
834Date: Wed, 15 Nov 1995 06:25:24 GMT
835Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
836Content-Range: bytes 21010-47021/47022
837Content-Length: 26012
838Content-Type: image/gif
839
840... 26012 bytes of partial image data ...
841</pre><p id="rfc.section.4.1.p.4">If multiple parts are being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a "multipart/byteranges" payload, as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>, and a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field containing the multipart/byteranges media type and its required boundary parameter. To avoid confusion with single-part
842               responses, a server <em class="bcp14">MUST NOT</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field in the HTTP header section of a multiple part response (this field will be sent in each part instead).
843            </p>
844            <p id="rfc.section.4.1.p.5">Within the header area of each body part in the multipart payload, the server <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field corresponding to the range being enclosed in that body part. If the selected representation would have had a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, the server <em class="bcp14">SHOULD</em> generate that same <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> field in the header area of each body part. For example:
845            </p>
846            <div id="rfc.figure.u.18"></div><pre class="text">HTTP/1.1 206 Partial Content
847Date: Wed, 15 Nov 1995 06:25:24 GMT
848Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
849Content-Length: 1741
850Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
851
852--THIS_STRING_SEPARATES
853Content-Type: application/pdf
854Content-Range: bytes 500-999/8000
855
856...the first range...
857--THIS_STRING_SEPARATES
858Content-Type: application/pdf
859Content-Range: bytes 7000-7999/8000
860
861...the second range
862--THIS_STRING_SEPARATES--
863</pre><p id="rfc.section.4.1.p.7">When multiple ranges are requested, a server <em class="bcp14">MAY</em> coalesce any of the ranges that overlap, or that are separated by a gap that is smaller than the overhead of sending multiple
864               parts, regardless of the order in which the corresponding byte-range-spec appeared in the received <a href="#header.range" class="smpl">Range</a> header field. Since the typical overhead between parts of a multipart/byteranges payload is around 80 bytes, depending on
865               the selected representation's media type and the chosen boundary parameter length, it can be less efficient to transfer many
866               small disjoint parts than it is to transfer the entire selected representation.
867            </p>
868            <p id="rfc.section.4.1.p.8">A server <em class="bcp14">MUST NOT</em> generate a multipart response to a request for a single range, since a client that does not request multiple parts might not
869               support multipart responses. However, a server <em class="bcp14">MAY</em> generate a multipart/byteranges payload with only a single body part if multiple ranges were requested and only one range
870               was found to be satisfiable or only one range remained after coalescing. A client that cannot process a multipart/byteranges
871               response <em class="bcp14">MUST NOT</em> generate a request that asks for multiple ranges.
872            </p>
873            <p id="rfc.section.4.1.p.9">When a multipart response payload is generated, the server <em class="bcp14">SHOULD</em> send the parts in the same order that the corresponding byte-range-spec appeared in the received <a href="#header.range" class="smpl">Range</a> header field, excluding those ranges that were deemed unsatisfiable or that were coalesced into other ranges. A client that
874               receives a multipart response <em class="bcp14">MUST</em> inspect the <a href="#header.content-range" class="smpl">Content-Range</a> header field present in each body part in order to determine which range is contained in that body part; a client cannot rely
875               on receiving the same ranges that it requested, nor the same order that it requested.
876            </p>
877            <p id="rfc.section.4.1.p.10">When a 206 response is generated, the server <em class="bcp14">MUST</em> generate the following header fields, in addition to those required above, if the field would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request: <a href="p2-semantics.html#header.date" class="smpl">Date</a>, <a href="p6-cache.html#header.cache-control" class="smpl">Cache-Control</a>, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a>, <a href="p6-cache.html#header.expires" class="smpl">Expires</a>, <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a>, and <a href="p2-semantics.html#header.vary" class="smpl">Vary</a>.
878            </p>
879            <p id="rfc.section.4.1.p.11">If a 206 is generated in response to a request with an <a href="#header.if-range" class="smpl">If-Range</a> header field, the sender <em class="bcp14">SHOULD NOT</em> generate other representation header fields beyond those required above, because the client is understood to already have
880               a prior response containing those header fields. Otherwise, the sender <em class="bcp14">MUST</em> generate all of the representation header fields that would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request.
881            </p>
882            <p id="rfc.section.4.1.p.12">A 206 response is cacheable by default; i.e., unless otherwise indicated by explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>).
883            </p>
884         </div>
885         <div id="header.content-range">
886            <div id="rfc.iref.c.1"></div>
887            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#header.content-range">Content-Range</a></h2>
888            <p id="rfc.section.4.2.p.1">The "Content-Range" header field is sent in a single part <a href="#status.206" class="smpl">206 (Partial Content)</a> response to indicate the partial range of the selected representation enclosed as the message payload, sent in each part of
889               a multipart 206 response to indicate the range enclosed within each body part, and sent in <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> responses to provide information about the selected representation.
890            </p>
891            <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.content-range" class="smpl">Content-Range</a>       = <a href="#header.content-range" class="smpl">byte-content-range</a>
892                      / <a href="#header.content-range" class="smpl">other-content-range</a>
893                         
894  <a href="#header.content-range" class="smpl">byte-content-range</a>  = <a href="#byte.ranges" class="smpl">bytes-unit</a> <a href="#imported.abnf" class="smpl">SP</a>
895                        ( <a href="#header.content-range" class="smpl">byte-range-resp</a> / <a href="#header.content-range" class="smpl">unsatisfied-range</a> )
896
897  <a href="#header.content-range" class="smpl">byte-range-resp</a>     = <a href="#header.content-range" class="smpl">byte-range</a> "/" ( <a href="#header.content-range" class="smpl">complete-length</a> / "*" )
898  <a href="#header.content-range" class="smpl">byte-range</a>          = <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>
899  <a href="#header.content-range" class="smpl">unsatisfied-range</a>   = "*/" <a href="#header.content-range" class="smpl">complete-length</a>
900                         
901  <a href="#header.content-range" class="smpl">complete-length</a>     = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
902 
903  <a href="#header.content-range" class="smpl">other-content-range</a> = <a href="#range.units.other" class="smpl">other-range-unit</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.content-range" class="smpl">other-range-resp</a>
904  <a href="#header.content-range" class="smpl">other-range-resp</a>    = *<a href="#imported.abnf" class="smpl">CHAR</a>
905</pre><p id="rfc.section.4.2.p.3">If a <a href="#status.206" class="smpl">206 (Partial Content)</a> response contains a <a href="#header.content-range" class="smpl">Content-Range</a> header field with a <a href="#range.units" class="smpl">range unit</a> (<a href="#range.units" title="Range Units">Section&nbsp;2</a>) that the recipient does not understand, the recipient <em class="bcp14">MUST NOT</em> attempt to recombine it with a stored representation. A proxy that receives such a message <em class="bcp14">SHOULD</em> forward it downstream.
906            </p>
907            <p id="rfc.section.4.2.p.4">For byte ranges, a sender <em class="bcp14">SHOULD</em> indicate the complete length of the representation from which the range has been extracted, unless the complete length is
908               unknown or difficult to determine. An asterisk character ("*") in place of the complete-length indicates that the representation
909               length was unknown when the header field was generated.
910            </p>
911            <p id="rfc.section.4.2.p.5">The following example illustrates when the complete length of the selected representation is known by the sender to be 1234
912               bytes:
913            </p>
914            <div id="rfc.figure.u.20"></div><pre class="text">  Content-Range: bytes 42-1233/1234
915</pre><p id="rfc.section.4.2.p.7">and this second example illustrates when the complete length is unknown:</p>
916            <div id="rfc.figure.u.21"></div><pre class="text">  Content-Range: bytes 42-1233/*
917</pre><p id="rfc.section.4.2.p.9">A Content-Range field value is invalid if it contains a <a href="#header.content-range" class="smpl">byte-range-resp</a> that has a <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value less than its <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value, or a <a href="#header.content-range" class="smpl">complete-length</a> value less than or equal to its <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value. The recipient of an invalid <a href="#header.content-range" class="smpl">Content-Range</a> <em class="bcp14">MUST NOT</em> attempt to recombine the received content with a stored representation.
918            </p>
919            <p id="rfc.section.4.2.p.10">A server generating a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response to a byte-range request <em class="bcp14">SHOULD</em> send a Content-Range header field with an <a href="#header.content-range" class="smpl">unsatisfied-range</a> value, as in the following example:
920            </p>
921            <div id="rfc.figure.u.22"></div><pre class="text">  Content-Range: bytes */1234
922</pre><p id="rfc.section.4.2.p.12">The complete-length in a 416 response indicates the current length of the selected representation.</p>
923            <p id="rfc.section.4.2.p.13">The Content-Range header field has no meaning for status codes that do not explicitly describe its semantic. For this specification,
924               only the <a href="#status.206" class="smpl">206 (Partial Content)</a> and <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> status codes describe a meaning for Content-Range.
925            </p>
926            <p id="rfc.section.4.2.p.14">The following are examples of Content-Range values in which the selected representation contains a total of 1234 bytes: </p>
927            <ul>
928               <li>The first 500 bytes: <span id="rfc.figure.u.23"></span><pre class="text">  Content-Range: bytes 0-499/1234
929</pre> </li>
930               <li>The second 500 bytes: <span id="rfc.figure.u.24"></span><pre class="text">  Content-Range: bytes 500-999/1234
931</pre> </li>
932               <li>All except for the first 500 bytes: <span id="rfc.figure.u.25"></span><pre class="text">  Content-Range: bytes 500-1233/1234
933</pre> </li>
934               <li>The last 500 bytes: <span id="rfc.figure.u.26"></span><pre class="text">  Content-Range: bytes 734-1233/1234
935</pre> </li>
936            </ul>
937         </div>
938         <div id="combining.byte.ranges">
939            <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></h2>
940            <p id="rfc.section.4.3.p.1">A response might transfer only a subrange of a representation if the connection closed prematurely or if the request used
941               one or more Range specifications. After several such transfers, a client might have received several ranges of the same representation.
942               These ranges can only be safely combined if they all have in common the same strong validator (<a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.1</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>).
943            </p>
944            <p id="rfc.section.4.3.p.2">A client that has received multiple partial responses to GET requests on a target resource <em class="bcp14">MAY</em> combine those responses into a larger continuous range if they share the same strong validator.
945            </p>
946            <p id="rfc.section.4.3.p.3">If the most recent response is an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, then the header fields of that response are used for any combined response and replace those of the matching stored
947               responses.
948            </p>
949            <p id="rfc.section.4.3.p.4">If the most recent response is a <a href="#status.206" class="smpl">206 (Partial Content)</a> response and at least one of the matching stored responses is a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, then the combined response header fields consist of the most recent 200 response's header fields. If all of the matching
950               stored responses are 206 responses, then the stored response with the most recent header fields is used as the source of header
951               fields for the combined response, except that the client <em class="bcp14">MUST</em> use other header fields provided in the new response, aside from <a href="#header.content-range" class="smpl">Content-Range</a>, to replace all instances of the corresponding header fields in the stored response.
952            </p>
953            <p id="rfc.section.4.3.p.5">The combined response message body consists of the union of partial content ranges in the new response and each of the selected
954               responses. If the union consists of the entire range of the representation, then the client <em class="bcp14">MUST</em> process the combined response as if it were a complete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, including a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field that reflects the complete length. Otherwise, the client <em class="bcp14">MUST</em> process the set of continuous ranges as one of the following: an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response if the combined response is a prefix of the representation, a single <a href="#status.206" class="smpl">206 (Partial Content)</a> response containing a multipart/byteranges body, or multiple <a href="#status.206" class="smpl">206 (Partial Content)</a> responses, each with one continuous range that is indicated by a <a href="#header.content-range" class="smpl">Content-Range</a> header field.
955            </p>
956         </div>
957         <div id="status.416">
958            <div id="rfc.iref.4.1"></div>
959            <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#status.416">416 Range Not Satisfiable</a></h2>
960            <p id="rfc.section.4.4.p.1">The <dfn>416 (Range Not Satisfiable)</dfn> status code indicates that none of the ranges in the request's <a href="#header.range" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;3.1</a>) overlap the current extent of the selected resource or that the set of ranges requested has been rejected due to invalid
961               ranges or an excessive request of small or overlapping ranges.
962            </p>
963            <p id="rfc.section.4.4.p.2">For byte ranges, failing to overlap the current extent means that the <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> of all of the <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> values were greater than the current length of the selected representation. When this status code is generated in response
964               to a byte-range request, the sender <em class="bcp14">SHOULD</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field specifying the current length of the selected representation (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;4.2</a>).
965            </p>
966            <div id="rfc.figure.u.27"></div>
967            <p>For example:</p><pre class="text">HTTP/1.1 416 Range Not Satisfiable
968Date: Fri, 20 Jan 2012 15:41:54 GMT
969Content-Range: bytes */47022
970</pre><div class="note" id="rfc.section.4.4.p.4">
971               <p><b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. That is partly because most clients are prepared to receive a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request
972                  until they have received a complete representation. Thus, clients cannot depend on receiving a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response even when it is most appropriate.
973               </p>
974            </div>
975         </div>
976      </div>
977      <div id="IANA.considerations">
978         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
979         <div id="range.unit.registry">
980            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#range.unit.registry">Range Unit Registry</a></h2>
981            <p id="rfc.section.5.1.p.1">The "HTTP Range Unit Registry" defines the namespace for the range unit names and refers to their corresponding specifications.
982               The registry has been created and is now maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
983            </p>
984            <div id="range.unit.registry.procedure">
985               <h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a href="#range.unit.registry.procedure">Procedure</a></h3>
986               <p id="rfc.section.5.1.1.p.1">Registration of an HTTP Range Unit <em class="bcp14">MUST</em> include the following fields:
987               </p>
988               <ul>
989                  <li>Name</li>
990                  <li>Description</li>
991                  <li>Pointer to specification text</li>
992               </ul>
993               <p id="rfc.section.5.1.1.p.2">Values to be added to this namespace require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
994               </p>
995            </div>
996            <div id="range.unit.registration">
997               <h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a href="#range.unit.registration">Registrations</a></h3>
998               <p id="rfc.section.5.1.2.p.1">The initial range unit registry contains the registrations below:</p>
999               <div id="rfc.table.1">
1000                  <div id="iana.range.units.table"></div>
1001                  <table class="tt full left" cellpadding="3" cellspacing="0">
1002                     <thead>
1003                        <tr>
1004                           <th>Range Unit Name</th>
1005                           <th>Description</th>
1006                           <th>Reference</th>
1007                        </tr>
1008                     </thead>
1009                     <tbody>
1010                        <tr>
1011                           <td class="left">bytes</td>
1012                           <td class="left">a range of octets</td>
1013                           <td class="left"><a href="#byte.ranges" title="Byte Ranges">Section&nbsp;2.1</a></td>
1014                        </tr>
1015                        <tr>
1016                           <td class="left">none</td>
1017                           <td class="left">reserved as keyword, indicating no ranges are supported</td>
1018                           <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.2" title="Accept-Ranges">Section&nbsp;2.3</a></td>
1019                        </tr>
1020                     </tbody>
1021                  </table>
1022               </div>
1023               <p id="rfc.section.5.1.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
1024            </div>
1025         </div>
1026         <div id="status.code.registration">
1027            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h2>
1028            <p id="rfc.section.5.2.p.1">The "Hypertext Transfer Protocol (HTTP) Status Code Registry" located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; has been updated to include the registrations below:
1029            </p>
1030            <div id="rfc.table.2">
1031               <div id="iana.status.code.registration.table"></div>
1032               <table class="tt full left" cellpadding="3" cellspacing="0">
1033                  <thead>
1034                     <tr>
1035                        <th>Value</th>
1036                        <th>Description</th>
1037                        <th>Reference</th>
1038                     </tr>
1039                  </thead>
1040                  <tbody>
1041                     <tr>
1042                        <td class="left">206</td>
1043                        <td class="left">Partial Content</td>
1044                        <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;4.1</a>
1045                        </td>
1046                     </tr>
1047                     <tr>
1048                        <td class="left">416</td>
1049                        <td class="left">Range Not Satisfiable</td>
1050                        <td class="left"><a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;4.4</a>
1051                        </td>
1052                     </tr>
1053                  </tbody>
1054               </table>
1055            </div>
1056         </div>
1057         <div id="header.field.registration">
1058            <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
1059            <p id="rfc.section.5.3.p.1">HTTP header fields are registered within the "Message Headers" registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers/">http://www.iana.org/assignments/message-headers/</a>&gt;.
1060            </p>
1061            <p id="rfc.section.5.3.p.2">This document defines the following HTTP header fields, so their associated registry entries have been updated according to
1062               the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
1063            </p>
1064            <div id="rfc.table.3">
1065               <div id="iana.header.registration.table"></div>
1066               <table class="tt full left" cellpadding="3" cellspacing="0">
1067                  <thead>
1068                     <tr>
1069                        <th>Header Field Name</th>
1070                        <th>Protocol</th>
1071                        <th>Status</th>
1072                        <th>Reference</th>
1073                     </tr>
1074                  </thead>
1075                  <tbody>
1076                     <tr>
1077                        <td class="left">Accept-Ranges</td>
1078                        <td class="left">http</td>
1079                        <td class="left">standard</td>
1080                        <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section&nbsp;2.3</a>
1081                        </td>
1082                     </tr>
1083                     <tr>
1084                        <td class="left">Content-Range</td>
1085                        <td class="left">http</td>
1086                        <td class="left">standard</td>
1087                        <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;4.2</a>
1088                        </td>
1089                     </tr>
1090                     <tr>
1091                        <td class="left">If-Range</td>
1092                        <td class="left">http</td>
1093                        <td class="left">standard</td>
1094                        <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;3.2</a>
1095                        </td>
1096                     </tr>
1097                     <tr>
1098                        <td class="left">Range</td>
1099                        <td class="left">http</td>
1100                        <td class="left">standard</td>
1101                        <td class="left"><a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;3.1</a>
1102                        </td>
1103                     </tr>
1104                  </tbody>
1105               </table>
1106            </div>
1107            <p id="rfc.section.5.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
1108         </div>
1109         <div id="internet.media.type.http">
1110            <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#internet.media.type.http">Internet Media Type Registration</a></h2>
1111            <p id="rfc.section.5.4.p.1">IANA maintains the registry of Internet media types <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a> at &lt;<a href="http://www.iana.org/assignments/media-types">http://www.iana.org/assignments/media-types</a>&gt;.
1112            </p>
1113            <p id="rfc.section.5.4.p.2">This document serves as the specification for the Internet media type "multipart/byteranges". The following has been registered
1114               with IANA.
1115            </p>
1116            <div id="internet.media.type.multipart.byteranges.reg">
1117               <div id="rfc.iref.m.1"></div>
1118               <div id="rfc.iref.m.2"></div>
1119               <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a href="#internet.media.type.multipart.byteranges.reg">Internet Media Type multipart/byteranges</a></h3>
1120               <p id="rfc.section.5.4.1.p.1"></p>
1121               <dl>
1122                  <dt>Type name:</dt>
1123                  <dd>multipart</dd>
1124                  <dt>Subtype name:</dt>
1125                  <dd>byteranges</dd>
1126                  <dt>Required parameters:</dt>
1127                  <dd>boundary</dd>
1128                  <dt>Optional parameters:</dt>
1129                  <dd>N/A</dd>
1130                  <dt>Encoding considerations:</dt>
1131                  <dd>only "7bit", "8bit", or "binary" are permitted</dd>
1132                  <dt>Security considerations:</dt>
1133                  <dd>see <a href="#security.considerations" title="Security Considerations">Section&nbsp;6</a>
1134                  </dd>
1135                  <dt>Interoperability considerations:</dt>
1136                  <dd>N/A</dd>
1137                  <dt>Published specification:</dt>
1138                  <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
1139                  </dd>
1140                  <dt>Applications that use this media type:</dt>
1141                  <dd>HTTP components supporting multiple ranges in a single request.</dd>
1142                  <dt>Fragment identifier considerations:</dt>
1143                  <dd>N/A</dd>
1144                  <dt>Additional information:</dt>
1145                  <dd>
1146                     <dl>
1147                        <dt>Deprecated alias names for this type:</dt>
1148                        <dd>N/A</dd>
1149                        <dt>Magic number(s):</dt>
1150                        <dd>N/A</dd>
1151                        <dt>File extension(s):</dt>
1152                        <dd>N/A</dd>
1153                        <dt>Macintosh file type code(s):</dt>
1154                        <dd>N/A</dd>
1155                     </dl>
1156                  </dd>
1157                  <dt>Person and email address to contact for further information:</dt>
1158                  <dd>See Authors' Addresses section.</dd>
1159                  <dt>Intended usage:</dt>
1160                  <dd>COMMON</dd>
1161                  <dt>Restrictions on usage:</dt>
1162                  <dd>N/A</dd>
1163                  <dt>Author:</dt>
1164                  <dd>See Authors' Addresses section.</dd>
1165                  <dt>Change controller:</dt>
1166                  <dd>IESG</dd>
1167               </dl>
1168            </div>
1169         </div>
1170      </div>
1171      <div id="security.considerations">
1172         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
1173         <p id="rfc.section.6.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP
1174            range request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> and semantics <a href="#RFC7231" id="rfc.xref.RFC7231.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>.
1175         </p>
1176         <div id="overlapping.ranges">
1177            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#overlapping.ranges">Denial-of-Service Attacks Using Range</a></h2>
1178            <p id="rfc.section.6.1.p.1">Unconstrained multiple range requests are susceptible to denial-of-service attacks because the effort required to request
1179               many overlapping ranges of the same data is tiny compared to the time, memory, and bandwidth consumed by attempting to serve
1180               the requested data in many parts. Servers ought to ignore, coalesce, or reject egregious range requests, such as requests
1181               for more than two overlapping ranges or for many small ranges in a single set, particularly when the ranges are requested
1182               out of order for no apparent reason. Multipart range requests are not designed to support random access.
1183            </p>
1184         </div>
1185      </div>
1186      <div id="acks">
1187         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
1188         <p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
1189         </p>
1190      </div>
1191      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
1192      </h1>
1193      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
1194      </h2>
1195      <table>
1196         <tr>
1197            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
1198            <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.
1199            </td>
1200         </tr>
1201         <tr>
1202            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1203            <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.
1204            </td>
1205         </tr>
1206         <tr>
1207            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1208            <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.
1209            </td>
1210         </tr>
1211         <tr>
1212            <td class="reference"><b id="RFC7230">[RFC7230]</b></td>
1213            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., 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-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2014.
1214            </td>
1215         </tr>
1216         <tr>
1217            <td class="reference"><b id="RFC7231">[RFC7231]</b></td>
1218            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., 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-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2014.
1219            </td>
1220         </tr>
1221         <tr>
1222            <td class="reference"><b id="RFC7232">[RFC7232]</b></td>
1223            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., 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-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2014.
1224            </td>
1225         </tr>
1226         <tr>
1227            <td class="reference"><b id="RFC7234">[RFC7234]</b></td>
1228            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">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-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2014.
1229            </td>
1230         </tr>
1231      </table>
1232      <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References
1233      </h2>
1234      <table>
1235         <tr>
1236            <td class="reference"><b id="BCP13">[BCP13]</b></td>
1237            <td class="top"><a href="mailto:ned+ietf@mrochek.com" title="Oracle">Freed, N.</a>, <a href="mailto:john+ietf@jck.com">Klensin, J.</a>, and <a href="mailto:tony+mtsuffix@maillennium.att.com" title="AT&amp;T Laboratories">T. Hansen</a>, “<a href="https://tools.ietf.org/html/rfc6838">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;6838, January&nbsp;2013.
1238            </td>
1239         </tr>
1240         <tr>
1241            <td class="reference"><b id="BCP90">[BCP90]</b></td>
1242            <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.
1243            </td>
1244         </tr>
1245         <tr>
1246            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1247            <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.
1248            </td>
1249         </tr>
1250         <tr>
1251            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
1252            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
1253            </td>
1254         </tr>
1255      </table>
1256      <div id="internet.media.type.multipart.byteranges">
1257         <div id="rfc.iref.m.3"></div>
1258         <div id="rfc.iref.m.4"></div>
1259         <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>
1260         <p id="rfc.section.A.p.1">When a <a href="#status.206" class="smpl">206 (Partial Content)</a> response message includes the content of multiple ranges, they are transmitted as body parts in 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>) with the media type of "multipart/byteranges".
1261         </p>
1262         <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more body parts, each with its own <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-range" class="smpl">Content-Range</a> fields. The required boundary parameter specifies the boundary string used to separate each body part.
1263         </p>
1264         <p id="rfc.section.A.p.3">Implementation Notes: </p>
1265         <ol>
1266            <li>Additional CRLFs might precede the first boundary string in the body.</li>
1267            <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> permits the boundary string to be quoted, some existing implementations handle a quoted boundary string incorrectly.
1268            </li>
1269            <li>A number of clients and servers were coded to an early draft of the byteranges specification that used a media type of multipart/x-byteranges<span id="rfc.iref.m.5"></span><span id="rfc.iref.m.6"></span>, which is almost (but not quite) compatible with this type.
1270            </li>
1271         </ol>
1272         <p id="rfc.section.A.p.4">Despite the name, the "multipart/byteranges" media type is not limited to byte ranges. The following example uses an "exampleunit"
1273            range unit:
1274         </p>
1275         <div id="rfc.figure.u.28"></div><pre class="text">HTTP/1.1 206 Partial Content
1276Date: Tue, 14 Nov 1995 06:25:24 GMT
1277Last-Modified: Tue, 14 July 04:58:08 GMT
1278Content-Length: 2331785
1279Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1280
1281--THIS_STRING_SEPARATES
1282Content-Type: video/example
1283Content-Range: exampleunit 1.2-4.3/25
1284
1285...the first range...
1286--THIS_STRING_SEPARATES
1287Content-Type: video/example
1288Content-Range: exampleunit 11.2-14.3/25
1289
1290...the second range
1291--THIS_STRING_SEPARATES--
1292</pre></div>
1293      <div id="changes.from.rfc.2616">
1294         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
1295         <p id="rfc.section.B.p.1">Servers are given more leeway in how they respond to a range request, in order to mitigate abuse by malicious (or just greedy)
1296            clients. (<a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;3.1</a>)
1297         </p>
1298         <p id="rfc.section.B.p.2">A weak validator cannot be used in a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;4.1</a>)
1299         </p>
1300         <p id="rfc.section.B.p.3">The Content-Range header field only has meaning when the status code explicitly defines its use. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;4.2</a>)
1301         </p>
1302         <p id="rfc.section.B.p.4">This specification introduces a Range Unit Registry. (<a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;5.1</a>)
1303         </p>
1304         <p id="rfc.section.B.p.5">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>)
1305         </p>
1306      </div>
1307      <div id="imported.abnf">
1308         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#imported.abnf">Imported ABNF</a></h1>
1309         <p id="rfc.section.C.p.1">The following core rules are included by reference, as defined in <a href="https://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a> of <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
1310            (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
1311            character).
1312         </p>
1313         <p id="rfc.section.C.p.2">Note that all rules derived from <a href="#imported.abnf" class="smpl">token</a> are to be compared case-insensitively, like <a href="#range.units" class="smpl">range-unit</a> and <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>.
1314         </p>
1315         <p id="rfc.section.C.p.3">The rules below are defined in <a href="#RFC7230" id="rfc.xref.RFC7230.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>:
1316         </p>
1317         <div id="rfc.figure.u.29"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>        = &lt;OWS, see <a href="#RFC7230" id="rfc.xref.RFC7230.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
1318  <a href="#imported.abnf" class="smpl">token</a>      = &lt;token, see <a href="#RFC7230" id="rfc.xref.RFC7230.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field Value Components">Section 3.2.6</a>&gt;
1319</pre><p id="rfc.section.C.p.5">The rules below are defined in other parts:</p>
1320         <div id="rfc.figure.u.30"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>  = &lt;HTTP-date, see <a href="#RFC7231" id="rfc.xref.RFC7231.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
1321  <a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, see <a href="#RFC7232" id="rfc.xref.RFC7232.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>&gt;
1322</pre></div>
1323      <div id="collected.abnf">
1324         <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
1325         <p id="rfc.section.D.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
1326         </p>
1327         <div id="rfc.figure.u.31"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
1328
1329<a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range / other-content-range
1330
1331<a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, see [RFC7231], Section 7.1.1.1&gt;
1332
1333<a href="#header.if-range" class="smpl">If-Range</a> = entity-tag / HTTP-date
1334
1335<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, see [RFC7230], Section 3.2.3&gt;
1336
1337<a href="#header.range" class="smpl">Range</a> = byte-ranges-specifier / other-ranges-specifier
1338
1339<a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = ( *( "," OWS ) range-unit *( OWS "," [ OWS
1340 range-unit ] ) ) / "none"
1341
1342<a href="#header.content-range" class="smpl">byte-content-range</a> = bytes-unit SP ( byte-range-resp /
1343 unsatisfied-range )
1344<a href="#header.content-range" class="smpl">byte-range</a> = first-byte-pos "-" last-byte-pos
1345<a href="#header.content-range" class="smpl">byte-range-resp</a> = byte-range "/" ( complete-length / "*" )
1346<a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = *( "," OWS ) ( byte-range-spec /
1347 suffix-byte-range-spec ) *( OWS "," [ OWS ( byte-range-spec /
1348 suffix-byte-range-spec ) ] )
1349<a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ]
1350<a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set
1351<a href="#byte.ranges" class="smpl">bytes-unit</a> = "bytes"
1352
1353<a href="#header.content-range" class="smpl">complete-length</a> = 1*DIGIT
1354
1355<a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, see [RFC7232], Section 2.3&gt;
1356
1357<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT
1358
1359<a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*DIGIT
1360
1361<a href="#header.content-range" class="smpl">other-content-range</a> = other-range-unit SP other-range-resp
1362<a href="#header.content-range" class="smpl">other-range-resp</a> = *CHAR
1363<a href="#header.range" class="smpl">other-range-set</a> = 1*VCHAR
1364<a href="#range.units.other" class="smpl">other-range-unit</a> = token
1365<a href="#header.range" class="smpl">other-ranges-specifier</a> = other-range-unit "=" other-range-set
1366
1367<a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit
1368
1369<a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" suffix-length
1370<a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT
1371
1372<a href="#imported.abnf" class="smpl">token</a> = &lt;token, see [RFC7230], Section 3.2.6&gt;
1373
1374<a href="#header.content-range" class="smpl">unsatisfied-range</a> = "*/" complete-length
1375</pre></div>
1376      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1377      <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.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.R">R</a>
1378      </p>
1379      <div class="print2col">
1380         <ul class="ind">
1381            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
1382                  <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.2.1"><b>4.1</b></a>, <a href="#rfc.xref.status.206.1">5.2</a>, <a href="#rfc.xref.status.206.2">B</a></li>
1383               </ul>
1384            </li>
1385            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1386                  <li>416 Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>4.4</b></a>, <a href="#rfc.xref.status.416.1">5.2</a></li>
1387               </ul>
1388            </li>
1389            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1390                  <li>Accept-Ranges header field&nbsp;&nbsp;<a href="#rfc.xref.header.accept-ranges.1">2</a>, <a href="#rfc.iref.a.1"><b>2.3</b></a>, <a href="#rfc.xref.header.accept-ranges.2">5.1.2</a>, <a href="#rfc.xref.header.accept-ranges.3">5.3</a></li>
1391               </ul>
1392            </li>
1393            <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul>
1394                  <li><em>BCP13</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP13.1">5.4</a>, <a href="#BCP13"><b>8.2</b></a></li>
1395                  <li><em>BCP90</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP90.1">5.3</a>, <a href="#BCP90"><b>8.2</b></a></li>
1396               </ul>
1397            </li>
1398            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1399                  <li>Content-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.iref.c.1"><b>4.2</b></a>, <a href="#rfc.xref.header.content-range.2">4.4</a>, <a href="#rfc.xref.header.content-range.3">5.3</a>, <a href="#rfc.xref.header.content-range.4">B</a></li>
1400               </ul>
1401            </li>
1402            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1403                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1404                     <ul>
1405                        <li><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>2.3</b></a></li>
1406                        <li><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>2.3</b></a></li>
1407                        <li><tt>byte-content-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>4.2</b></a></li>
1408                        <li><tt>byte-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>4.2</b></a></li>
1409                        <li><tt>byte-range-resp</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>4.2</b></a></li>
1410                        <li><tt>byte-range-set</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>2.1</b></a></li>
1411                        <li><tt>byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>2.1</b></a></li>
1412                        <li><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>2.1</b></a></li>
1413                        <li><tt>bytes-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2">2</a>, <a href="#rfc.iref.g.4"><b>2.1</b></a></li>
1414                        <li><tt>complete-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>4.2</b></a></li>
1415                        <li><tt>Content-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>4.2</b></a></li>
1416                        <li><tt>first-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>2.1</b></a></li>
1417                        <li><tt>If-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>3.2</b></a></li>
1418                        <li><tt>last-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>2.1</b></a></li>
1419                        <li><tt>other-content-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>4.2</b></a></li>
1420                        <li><tt>other-range-resp</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>4.2</b></a></li>
1421                        <li><tt>other-range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3">2</a>, <a href="#rfc.iref.g.13"><b>2.2</b></a></li>
1422                        <li><tt>Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>3.1</b></a></li>
1423                        <li><tt>range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
1424                        <li><tt>ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>2.1</b></a></li>
1425                        <li><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>2.1</b></a></li>
1426                        <li><tt>suffix-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>2.1</b></a></li>
1427                        <li><tt>unsatisfied-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>4.2</b></a></li>
1428                     </ul>
1429                  </li>
1430               </ul>
1431            </li>
1432            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
1433                  <li>If-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.iref.i.1"><b>3.2</b></a>, <a href="#rfc.xref.header.if-range.2">5.3</a></li>
1434               </ul>
1435            </li>
1436            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
1437                  <li>Media Type&nbsp;&nbsp;
1438                     <ul>
1439                        <li>multipart/byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>5.4.1</b></a>, <a href="#rfc.iref.m.3"><b>A</b></a></li>
1440                        <li>multipart/x-byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.6">A</a></li>
1441                     </ul>
1442                  </li>
1443                  <li>multipart/byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>5.4.1</b></a>, <a href="#rfc.iref.m.4"><b>A</b></a></li>
1444                  <li>multipart/x-byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.5">A</a></li>
1445               </ul>
1446            </li>
1447            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1448                  <li>Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.iref.r.1"><b>3.1</b></a>, <a href="#rfc.xref.header.range.2">4.1</a>, <a href="#rfc.xref.header.range.3">4.4</a>, <a href="#rfc.xref.header.range.4">5.3</a>, <a href="#rfc.xref.header.range.5">B</a></li>
1449                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#RFC2046"><b>8.1</b></a>, <a href="#rfc.xref.RFC2046.1">A</a>, <a href="#rfc.xref.RFC2046.2">A</a><ul>
1450                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">A</a></li>
1451                     </ul>
1452                  </li>
1453                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>8.1</b></a></li>
1454                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#RFC2616"><b>8.2</b></a></li>
1455                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">5.1.1</a>, <a href="#RFC5226"><b>8.2</b></a><ul>
1456                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">5.1.1</a></li>
1457                     </ul>
1458                  </li>
1459                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#RFC5234"><b>8.1</b></a>, <a href="#rfc.xref.RFC5234.2">C</a><ul>
1460                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">C</a></li>
1461                     </ul>
1462                  </li>
1463                  <li><em>RFC7230</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.1">1.1</a>, <a href="#rfc.xref.RFC7230.2">1.2</a>, <a href="#rfc.xref.RFC7230.3">6</a>, <a href="#rfc.xref.RFC7230.4">7</a>, <a href="#RFC7230"><b>8.1</b></a>, <a href="#rfc.xref.RFC7230.5">C</a>, <a href="#rfc.xref.RFC7230.6">C</a>, <a href="#rfc.xref.RFC7230.7">C</a>, <a href="#rfc.xref.RFC7230.8">D</a><ul>
1464                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.8">D</a></li>
1465                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.1">1.1</a></li>
1466                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.6">C</a></li>
1467                        <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.7">C</a></li>
1468                        <li><em>Section 7</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.2">1.2</a></li>
1469                        <li><em>Section 10</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7230.4">7</a></li>
1470                     </ul>
1471                  </li>
1472                  <li><em>RFC7231</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.1">2.1</a>, <a href="#rfc.xref.RFC7231.2">6</a>, <a href="#RFC7231"><b>8.1</b></a>, <a href="#rfc.xref.RFC7231.3">C</a><ul>
1473                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.1">2.1</a></li>
1474                        <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7231.3">C</a></li>
1475                     </ul>
1476                  </li>
1477                  <li><em>RFC7232</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.1">3.1</a>, <a href="#rfc.xref.RFC7232.2">3.2</a>, <a href="#rfc.xref.RFC7232.3">3.2</a>, <a href="#rfc.xref.RFC7232.4">3.2</a>, <a href="#rfc.xref.RFC7232.5">4.3</a>, <a href="#RFC7232"><b>8.1</b></a>, <a href="#rfc.xref.RFC7232.6">C</a><ul>
1478                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.5">4.3</a></li>
1479                        <li><em>Section 2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.2">3.2</a>, <a href="#rfc.xref.RFC7232.4">3.2</a></li>
1480                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.6">C</a></li>
1481                        <li><em>Section 2.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7232.3">3.2</a></li>
1482                     </ul>
1483                  </li>
1484                  <li><em>RFC7234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.1">4.1</a>, <a href="#RFC7234"><b>8.1</b></a><ul>
1485                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC7234.1">4.1</a></li>
1486                     </ul>
1487                  </li>
1488               </ul>
1489            </li>
1490         </ul>
1491      </div>
1492      <div class="avoidbreak">
1493         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1494         <p><b>Roy T. Fielding</b>
1495            (editor)
1496            <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
1497         <p><b>Yves Lafon</b>
1498            (editor)
1499            <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>
1500         <p><b>Julian F. Reschke</b>
1501            (editor)
1502            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<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>
1503      </div>
1504   </body>
1505</html>
Note: See TracBrowser for help on using the repository browser.