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

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

(editorial) move byte ranges definition into range unit section near start of document; no text changes

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 99.7 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://www.w3.org/2006/03/hcard 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 init() {
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: verdana, helvetica, arial, sans-serif;
109  font-size: 10pt;
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: 14pt;
135  line-height: 21pt;
136  page-break-after: avoid;
137}
138h1.np {
139  page-break-before: always;
140}
141h1 a {
142  color: #333333;
143}
144h2 {
145  font-size: 12pt;
146  line-height: 15pt;
147  page-break-after: avoid;
148}
149h3, h4, h5, h6 {
150  font-size: 10pt;
151  page-break-after: avoid;
152}
153h2 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}
211table.full {
212  border-style: outset;
213  border-width: 1px;
214}
215table.headers {
216  border-style: outset;
217  border-width: 1px;
218}
219table.tt td {
220  vertical-align: top;
221}
222table.full td {
223  border-style: inset;
224  border-width: 1px;
225}
226table.tt th {
227  vertical-align: top;
228}
229table.full th {
230  border-style: inset;
231  border-width: 1px;
232}
233table.headers th {
234  border-style: none none inset none;
235  border-width: 1px;
236}
237table.left {
238  margin-right: auto;
239}
240table.right {
241  margin-left: auto;
242}
243table.center {
244  margin-left: auto;
245  margin-right: auto;
246}
247caption {
248  caption-side: bottom;
249  font-weight: bold;
250  font-size: 9pt;
251  margin-top: .5em;
252}
253
254table.header {
255  border-spacing: 1px;
256  width: 95%;
257  font-size: 10pt;
258  color: white;
259}
260td.top {
261  vertical-align: top;
262}
263td.topnowrap {
264  vertical-align: top;
265  white-space: nowrap;
266}
267table.header td {
268  background-color: gray;
269  width: 50%;
270}
271table.header a {
272  color: white;
273}
274td.reference {
275  vertical-align: top;
276  white-space: nowrap;
277  padding-right: 1em;
278}
279thead {
280  display:table-header-group;
281}
282ul.toc, ul.toc ul {
283  list-style: none;
284  margin-left: 1.5em;
285  padding-left: 0em;
286}
287ul.toc li {
288  line-height: 150%;
289  font-weight: bold;
290  font-size: 10pt;
291  margin-left: 0em;
292}
293ul.toc li li {
294  line-height: normal;
295  font-weight: normal;
296  font-size: 9pt;
297  margin-left: 0em;
298}
299li.excluded {
300  font-size: 0pt;
301}
302ul p {
303  margin-left: 0em;
304}
305ul.ind, ul.ind ul {
306  list-style: none;
307  margin-left: 1.5em;
308  padding-left: 0em;
309  page-break-before: avoid;
310}
311ul.ind li {
312  font-weight: bold;
313  line-height: 200%;
314  margin-left: 0em;
315}
316ul.ind li li {
317  font-weight: normal;
318  line-height: 150%;
319  margin-left: 0em;
320}
321.avoidbreak {
322  page-break-inside: avoid;
323}
324.bcp14 {
325  font-style: normal;
326  text-transform: lowercase;
327  font-variant: small-caps;
328}
329.comment {
330  background-color: yellow;
331}
332.center {
333  text-align: center;
334}
335.error {
336  color: red;
337  font-style: italic;
338  font-weight: bold;
339}
340.figure {
341  font-weight: bold;
342  text-align: center;
343  font-size: 9pt;
344}
345.filename {
346  color: #333333;
347  font-weight: bold;
348  font-size: 12pt;
349  line-height: 21pt;
350  text-align: center;
351}
352.fn {
353  font-weight: bold;
354}
355.hidden {
356  display: none;
357}
358.left {
359  text-align: left;
360}
361.right {
362  text-align: right;
363}
364.title {
365  color: #990000;
366  font-size: 18pt;
367  line-height: 18pt;
368  font-weight: bold;
369  text-align: center;
370  margin-top: 36pt;
371}
372.vcardline {
373  display: block;
374}
375.warning {
376  font-size: 14pt;
377  background-color: yellow;
378}
379.feedback {
380  position: fixed;
381  bottom: 1%;
382  right: 1%;
383  padding: 3px 5px;
384  color: white;
385  border-radius: 5px;
386  background: #a00000;
387  border: 1px solid silver;
388}
389.fbbutton {
390  margin-left: 1em;
391  color: #303030;
392  font-size: small;
393  font-weight: normal;
394  background: #d0d000;
395  padding: 1px 4px;
396  border: 1px solid silver;
397  border-radius: 5px;
398}
399
400@media print {
401  .noprint {
402    display: none;
403  }
404 
405  a {
406    color: black;
407    text-decoration: none;
408  }
409
410  table.header {
411    width: 90%;
412  }
413
414  td.header {
415    width: 50%;
416    color: black;
417    background-color: white;
418    vertical-align: top;
419    font-size: 12pt;
420  }
421
422  ul.toc a:nth-child(2)::after {
423    content: leader('.') target-counter(attr(href), page);
424  }
425 
426  ul.ind li li a {
427    content: target-counter(attr(href), page);
428  }
429 
430  .print2col {
431    column-count: 2;
432    -moz-column-count: 2;
433    column-fill: auto;
434  }
435}
436
437@page {
438  @top-left {
439       content: "Internet-Draft";
440  }
441  @top-right {
442       content: "January 2013";
443  }
444  @top-center {
445       content: "HTTP/1.1 Range Requests";
446  }
447  @bottom-left {
448       content: "Fielding, et al.";
449  }
450  @bottom-center {
451       content: "Expires July 24, 2013";
452  }
453  @bottom-right {
454       content: "[Page " counter(page) "]";
455  }
456}
457
458@page:first {
459    @top-left {
460      content: normal;
461    }
462    @top-right {
463      content: normal;
464    }
465    @top-center {
466      content: normal;
467    }
468}
469</style><link rel="Contents" href="#rfc.toc">
470      <link rel="Author" href="#rfc.authors">
471      <link rel="Copyright" href="#rfc.copyrightnotice">
472      <link rel="Index" href="#rfc.index">
473      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
474      <link rel="Chapter" title="2 Range Units" href="#rfc.section.2">
475      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
476      <link rel="Chapter" title="4 Responses to a Range Request" href="#rfc.section.4">
477      <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5">
478      <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6">
479      <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7">
480      <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8">
481      <link rel="Chapter" href="#rfc.section.9" title="9 References">
482      <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
483      <link rel="Appendix" title="B Changes from RFC 2616" href="#rfc.section.B">
484      <link rel="Appendix" title="C Imported ABNF" href="#rfc.section.C">
485      <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
486      <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
487      <link href="p4-conditional.html" rel="prev">
488      <link href="p6-cache.html" rel="next">
489      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.589, 2012-11-30 14:23:31, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
490      <link rel="schema.dct" href="http://purl.org/dc/terms/">
491      <meta name="dct.creator" content="Fielding, R.">
492      <meta name="dct.creator" content="Lafon, Y.">
493      <meta name="dct.creator" content="Reschke, J. F.">
494      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
495      <meta name="dct.issued" scheme="ISO8601" content="2013-01-20">
496      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
497      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an 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.">
498      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an 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.">
499   </head>
500   <body onload="init();">
501      <table class="header">
502         <tbody>
503            <tr>
504               <td class="left">HTTPbis Working Group</td>
505               <td class="right">R. Fielding, Editor</td>
506            </tr>
507            <tr>
508               <td class="left">Internet-Draft</td>
509               <td class="right">Adobe</td>
510            </tr>
511            <tr>
512               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
513               </td>
514               <td class="right">Y. Lafon, Editor</td>
515            </tr>
516            <tr>
517               <td class="left">Intended status: Standards Track</td>
518               <td class="right">W3C</td>
519            </tr>
520            <tr>
521               <td class="left">Expires: July 24, 2013</td>
522               <td class="right">J. Reschke, Editor</td>
523            </tr>
524            <tr>
525               <td class="left"></td>
526               <td class="right">greenbytes</td>
527            </tr>
528            <tr>
529               <td class="left"></td>
530               <td class="right">January 20, 2013</td>
531            </tr>
532         </tbody>
533      </table>
534      <p class="title">Hypertext Transfer Protocol (HTTP/1.1): Range Requests<br><span class="filename">draft-ietf-httpbis-p5-range-latest</span></p>
535      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
536      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
537         systems. This document defines range requests and the rules for constructing and combining responses to those requests.
538      </p>
539      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
540      <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;.
541      </p> 
542      <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;.
543      </p> 
544      <p>The changes in this draft are summarized in <a href="#changes.since.21" title="Since draft-ietf-httpbis-p5-range-21">Appendix&nbsp;E.3</a>.
545      </p>
546      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
547      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
548      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
549         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>.
550      </p>
551      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
552         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
553         in progress”.
554      </p>
555      <p>This Internet-Draft will expire on July 24, 2013.</p>
556      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
557      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
558      <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
559         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
560         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
561         BSD License.
562      </p>
563      <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
564         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
565         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
566         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
567         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
568         it into languages other than English.
569      </p>
570      <hr class="noprint">
571      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
572      <ul class="toc">
573         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
574               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#conformance">Conformance and Error Handling</a></li>
575               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a></li>
576            </ul>
577         </li>
578         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a><ul>
579               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
580               <li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#range.units.other">Other Range Units</a></li>
581            </ul>
582         </li>
583         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
584               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
585               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Range Not Satisfiable</a></li>
586            </ul>
587         </li>
588         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#range.response">Responses to a Range Request</a><ul>
589               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.4.1">Response to a Single and Multiple Ranges Request</a></li>
590               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
591            </ul>
592         </li>
593         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
594               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
595               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
596               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
597               <li><a href="#rfc.section.5.4">5.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
598                     <li><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
599                  </ul>
600               </li>
601            </ul>
602         </li>
603         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
604               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.unit.registry">Range Unit Registry</a><ul>
605                     <li><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.unit.registry.procedure">Procedure</a></li>
606                     <li><a href="#rfc.section.6.1.2">6.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#range.unit.registration">Registrations</a></li>
607                  </ul>
608               </li>
609               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
610               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
611            </ul>
612         </li>
613         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
614               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#overlapping.ranges">Overlapping Ranges</a></li>
615            </ul>
616         </li>
617         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
618         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
619               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
620               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
621            </ul>
622         </li>
623         <li><a href="#rfc.authors">Authors' Addresses</a></li>
624         <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>
625         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
626         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
627         <li><a href="#rfc.section.D">D.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
628         <li><a href="#rfc.section.E">E.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
629               <li><a href="#rfc.section.E.1">E.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p5-range-19</a></li>
630               <li><a href="#rfc.section.E.2">E.2</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.20">Since draft-ietf-httpbis-p5-range-20</a></li>
631               <li><a href="#rfc.section.E.3">E.3</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.21">Since draft-ietf-httpbis-p5-range-21</a></li>
632            </ul>
633         </li>
634         <li><a href="#rfc.index">Index</a></li>
635      </ul>
636      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
637      <p id="rfc.section.1.p.1">HTTP clients often encounter interrupted data transfers as a result of canceled requests or dropped connections. When a client
638         has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
639         rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
640         request only a subset of a larger representation, such as a single page of a very large document or only part of an image
641         to be rendered by a device with limited local storage.
642      </p>
643      <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type. The protocol for
644         range requests is an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so resources or recipients that do not implement this feature can respond as if it is a normal GET
645         request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
646         full responses by intermediate caches that might not implement the feature.
647      </p>
648      <p id="rfc.section.1.p.3">Although the HTTP range request mechanism is designed to allow for extensible range types, this specification only defines
649         requests for byte ranges.
650      </p>
651      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="conformance" href="#conformance">Conformance and Error Handling</a></h2>
652      <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"
653         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>.
654      </p>
655      <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="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
656      </p>
657      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
658      <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 the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. <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 ABNF with the list rule expanded.
659      </p>
660      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
661      <p id="rfc.section.2.p.1">A representation can be partitioned into subranges according to various structural units, depending on the structure inherent
662         in the representation's media type. Such a <dfn>range unit</dfn> can be used in the <a href="#range.retrieval.requests" class="smpl">Range</a> (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;5.4</a>) and <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;5.2</a>) header fields to delineate the parts of a representation that are either requested or transferred, respectively.
663      </p>
664      <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="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a>
665  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
666  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#imported.abnf" class="smpl">token</a>
667</pre><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h2>
668      <p id="rfc.section.2.1.p.1">Since all HTTP representations are transferred as sequences of bytes, the concept of a byte range is meaningful for any HTTP
669         representation. (However, not all clients and servers need to support byte-range operations.)
670      </p>
671      <p id="rfc.section.2.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the representation data (not necessarily the same as the
672         message body).
673      </p>
674      <div id="rule.ranges-specifier">
675         <p id="rfc.section.2.1.p.3">                A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single representation.
676         </p>
677      </div>
678      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
679  <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> )
680  <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> ]
681  <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
682  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
683</pre><p id="rfc.section.2.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value
684         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
685         at zero.
686      </p>
687      <p id="rfc.section.2.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The
688         recipient of a byte-range-set that includes one or more syntactically invalid byte-range-spec values <em class="bcp14">MUST</em> ignore the header field that includes that byte-range-set.
689      </p>
690      <p id="rfc.section.2.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the representation
691         data, last-byte-pos is taken to be equal to one less than the current length of the representation in bytes.
692      </p>
693      <p id="rfc.section.2.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the representation.</p>
694      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
695  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
696</pre><p id="rfc.section.2.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the representation data, of a length given by the suffix-length
697         value. (That is, this form specifies the last N bytes of a representation.) If the representation is shorter than the specified
698         suffix-length, the entire representation is used.
699      </p>
700      <p id="rfc.section.2.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current
701         length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set
702         is satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> send a response with a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> status code. Otherwise, the server <em class="bcp14">SHOULD</em> send a response with a <a href="#status.206" class="smpl">206 (Partial Content)</a> status code containing the satisfiable ranges of the representation.
703      </p>
704      <p id="rfc.section.2.1.p.12">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 an HTTP payload, recipients <em class="bcp14">SHOULD</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
705      </p>
706      <p id="rfc.section.2.1.p.13">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p>
707      <ul>
708         <li>The first 500 bytes (byte offsets 0-499, inclusive):
709            <div id="rfc.figure.u.4"></div><pre class="text">  bytes=0-499
710</pre> </li>
711         <li>The second 500 bytes (byte offsets 500-999, inclusive):
712            <div id="rfc.figure.u.5"></div><pre class="text">  bytes=500-999
713</pre> </li>
714         <li>The final 500 bytes (byte offsets 9500-9999, inclusive):
715            <div id="rfc.figure.u.6"></div><pre class="text">  bytes=-500
716</pre> Or: <div id="rfc.figure.u.7"></div><pre class="text">  bytes=9500-
717</pre> </li>
718         <li>The first and last bytes only (bytes 0 and 9999):
719            <div id="rfc.figure.u.8"></div><pre class="text">  bytes=0-0,-1
720</pre> </li>
721         <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive):
722            <div id="rfc.figure.u.9"></div><pre class="text">  bytes=500-600,601-999
723  bytes=500-700,601-999
724</pre> </li>
725      </ul>
726      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="range.units.other" href="#range.units.other">Other Range Units</a></h2>
727      <p id="rfc.section.2.2.p.1">The only range unit defined by HTTP/1.1 is "bytes" (<a href="#byte.ranges" title="Byte Ranges">Section&nbsp;2.1</a>). Additional units can be defined as described in <a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;6.1</a>.
728      </p>
729      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="status.code.definitions" href="#status.code.definitions">Status Code Definitions</a></h1>
730      <div id="rfc.iref.11"></div>
731      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h2>
732      <p id="rfc.section.3.1.p.1">The <dfn>206 (Partial Content)</dfn> status code indicates that the server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a <a href="#range.retrieval.requests" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;5.4</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an <a href="#header.if-range" class="smpl">If-Range</a> header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;5.3</a>) to make the request conditional.
733      </p>
734      <p id="rfc.section.3.1.p.2">When a 206 response is generated, the sender <em class="bcp14">MUST</em> generate the following header fields:
735      </p>
736      <ul>
737         <li>Either a <a href="#header.content-range" class="smpl">Content-Range</a> header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;5.2</a>) indicating the range included with this response, or a multipart/byteranges <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> including Content-Range fields for each part. If a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field is present in the response, its value <em class="bcp14">MUST</em> match the actual number of octets transmitted in the message body.
738         </li>
739         <li>Date</li>
740         <li> <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/or <a href="p2-semantics.html#header.vary" class="smpl">Vary</a>, if the header field would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request
741         </li>
742      </ul>
743      <p id="rfc.section.3.1.p.3">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 described above. Otherwise, the sender <em class="bcp14">MUST</em> generate all of the same 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.
744      </p>
745      <p id="rfc.section.3.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 206 responses.
746      </p>
747      <div id="rfc.iref.11"></div>
748      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="status.416" href="#status.416">416 Range Not Satisfiable</a></h2>
749      <p id="rfc.section.3.2.p.1">The <dfn>416 (Range Not Satisfiable)</dfn> status code indicates that none of the ranges-specifier values in the request's <a href="#range.retrieval.requests" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;5.4</a>) overlap the current extent of the selected resource and the request did not include an <a href="#header.if-range" class="smpl">If-Range</a> header field (<a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>). (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current
750         length of the selected representation.)
751      </p>
752      <p id="rfc.section.3.2.p.2">When this status code is sent in response 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 (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>).
753      </p>
754      <div id="rfc.figure.u.10"></div>
755      <p>For example:</p>  <pre class="text">HTTP/1.1 416 Range Not Satisfiable
756Date: Mon, 20 Jan 2012 15:41:54 GMT
757Content-Range: bytes */47022
758Content-Type: image/gif
759</pre><div class="note" id="rfc.section.3.2.p.4">
760         <p> <b>Note:</b> Clients cannot depend on servers to send a <a href="#status.416" class="smpl">416 (Range Not
761               Satisfiable)</a> response instead of a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response for an unsatisfiable <a href="#range.retrieval.requests" class="smpl">Range</a> header field, since not all servers implement this header field.
762         </p>
763      </div>
764      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="range.response" href="#range.response">Responses to a Range Request</a></h1>
765      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;Response to a Single and Multiple Ranges Request
766      </h2>
767      <p id="rfc.section.4.1.p.1">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
768         a request for a set of ranges that overlap without any holes), this content is transmitted with a <a href="#header.content-range" class="smpl">Content-Range</a> header field, and a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field showing the number of bytes actually transferred. For example,
769      </p>
770      <div id="rfc.figure.u.11"></div><pre class="text">HTTP/1.1 206 Partial Content
771Date: Wed, 15 Nov 1995 06:25:24 GMT
772Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
773Content-Range: bytes 21010-47021/47022
774Content-Length: 26012
775Content-Type: image/gif
776</pre><p id="rfc.section.4.1.p.3">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
777         ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
778         as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>.
779      </p>
780      <p id="rfc.section.4.1.p.4">A server <em class="bcp14">MAY</em> combine requested ranges when those ranges are overlapping (see <a href="#overlapping.ranges" title="Overlapping Ranges">Section&nbsp;7.1</a>).
781      </p>
782      <p id="rfc.section.4.1.p.5">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
783      </p>
784      <p id="rfc.section.4.1.p.6">When a client asks for multiple ranges in one request, the server <em class="bcp14">SHOULD</em> send them in the order that they appeared in the request.
785      </p>
786      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Ranges</a></h2>
787      <p id="rfc.section.4.2.p.1">A response might transfer only a subrange of a representation if the connection closed prematurely or if the request used
788         one or more Range specifications. After several such transfers, a client might have received several ranges of the same representation.
789         These ranges can only be safely combined if they all have in common the same strong validator, where "strong validator" is
790         defined to be either an entity-tag that is not marked as weak (<a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) or, if no entity-tag is provided, a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> value that is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.
791      </p>
792      <p id="rfc.section.4.2.p.2">When a client receives an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response or a <a href="#status.206" class="smpl">206 (Partial Content)</a> response, and already has one or more partial responses for the same method and effective request URI that have the same strong
793         validator as present in the new response, the recipient <em class="bcp14">MAY</em> combine some or all of those responses into a set of continuous ranges. A client <em class="bcp14">MUST NOT</em> combine responses that differ in the strong validator or that do not have a strong validator.
794      </p>
795      <p id="rfc.section.4.2.p.3">If the new response is an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, then the header fields of that new response are used for any combined response and replace those of the matching
796         stored responses.
797      </p>
798      <p id="rfc.section.4.2.p.4">If the new 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
799         stored responses are 206 responses, then the stored response with the most recent header fields is used as the source of header
800         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.
801      </p>
802      <p id="rfc.section.4.2.p.5">The combined response message body consists of the union of partial content ranges in the new response and each of the selected
803         responses. If the union consists of the entire range of the representation, then the client <em class="bcp14">MUST</em> record 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> record 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.
804      </p>
805      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
806      <p id="rfc.section.5.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to range requests and partial responses.</p>
807      <div id="rfc.iref.a.1"></div>
808      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2>
809      <p id="rfc.section.5.1.p.1">The "Accept-Ranges" header field allows a resource to indicate its acceptance of range requests.</p>
810      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
811  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
812</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
813      </p>
814      <div id="rfc.figure.u.13"></div><pre class="text">  Accept-Ranges: bytes
815</pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate range requests without having received this header field for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
816      </p>
817      <p id="rfc.section.5.1.p.6">Servers that do not accept any kind of range request for a resource <em class="bcp14">MAY</em> send
818      </p>
819      <div id="rfc.figure.u.14"></div><pre class="text">  Accept-Ranges: none
820</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
821      <div id="rfc.iref.c.1"></div>
822      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="header.content-range" href="#header.content-range">Content-Range</a></h2>
823      <p id="rfc.section.5.2.p.1">The "Content-Range" header field is sent with a partial representation to specify where in the full representation the payload
824         body is intended to be applied.
825      </p>
826      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><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>  <a href="#header.content-range" class="smpl">Content-Range</a>       = <a href="#header.content-range" class="smpl">byte-content-range</a>
827                      / <a href="#header.content-range" class="smpl">other-content-range</a>
828                         
829  <a href="#header.content-range" class="smpl">byte-content-range</a>  = <a href="#range.units" class="smpl">bytes-unit</a> <a href="#imported.abnf" class="smpl">SP</a>
830                        ( <a href="#header.content-range" class="smpl">byte-range-resp</a> / <a href="#header.content-range" class="smpl">unsatisfied-range</a> )
831
832  <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> / "*" )
833  <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>
834  <a href="#header.content-range" class="smpl">unsatisfied-range</a>   = "*/" <a href="#header.content-range" class="smpl">complete-length</a>
835                         
836  <a href="#header.content-range" class="smpl">complete-length</a>     = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
837 
838  <a href="#header.content-range" class="smpl">other-content-range</a> = <a href="#range.units" 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>
839  <a href="#header.content-range" class="smpl">other-range-resp</a>    = *<a href="#imported.abnf" class="smpl">CHAR</a>
840</pre><p id="rfc.section.5.2.p.3">Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>. A recipient of a <a href="#status.206" class="smpl">206 (Partial Content)</a> response containing a <a href="#header.content-range" class="smpl">Content-Range</a> header field with a <a href="#range.units" class="smpl">range unit</a> that the recipient does not understand <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.
841      </p>
842      <p id="rfc.section.5.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 unknown
843         or difficult to determine. An asterisk character ("*") in place of the complete-length indicates that the representation length
844         was unknown when the header field was generated.
845      </p>
846      <p id="rfc.section.5.2.p.5">A Content-Range field value with 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, is invalid. 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.
847      </p>
848      <p id="rfc.section.5.2.p.6">A server generating a <a href="#status.206" class="smpl">206 (Partial Content)</a> response to a byte range request <em class="bcp14">MUST</em> send, in each body-part of a multipart response or in the header block of a single part response, a Content-Range header field
849         containing a <a href="#header.content-range" class="smpl">byte-range-resp</a> value that reflects the corresponding range being sent. The following example would apply when the complete length of the
850         selected representation is known by the sender to be 1234 bytes:
851      </p>
852      <div id="rfc.figure.u.16"></div><pre class="text">  Content-Range: bytes 42-1233/1234
853</pre><p id="rfc.section.5.2.p.8">or this second example would apply when the complete length is unknown:</p>
854      <div id="rfc.figure.u.17"></div><pre class="text">  Content-Range: bytes 42-1233/*
855</pre><p id="rfc.section.5.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:
856      </p>
857      <div id="rfc.figure.u.18"></div><pre class="text">  Content-Range: bytes */1234
858</pre><p id="rfc.section.5.2.p.12">The complete-length in a 416 response indicates the current length of the selected representation, which will be known by
859         the server generating the response because that is how it determined the range to be unsatisfiable.
860      </p>
861      <p id="rfc.section.5.2.p.13">The "Content-Range" header field has no meaning for status codes that do not explicitly describe its semantic. For this specification,
862         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.
863      </p>
864      <p id="rfc.section.5.2.p.14">More examples of Content-Range values, assuming that the representation contains a total of 1234 bytes: </p>
865      <ul>
866         <li>The first 500 bytes:
867            <div id="rfc.figure.u.19"></div><pre class="text">  Content-Range: bytes 0-499/1234
868</pre> </li>
869         <li>The second 500 bytes:
870            <div id="rfc.figure.u.20"></div><pre class="text">  Content-Range: bytes 500-999/1234
871</pre> </li>
872         <li>All except for the first 500 bytes:
873            <div id="rfc.figure.u.21"></div><pre class="text">  Content-Range: bytes 500-1233/1234
874</pre> </li>
875         <li>The last 500 bytes:
876            <div id="rfc.figure.u.22"></div><pre class="text">  Content-Range: bytes 734-1233/1234
877</pre> </li>
878      </ul>
879      <div id="rfc.iref.i.1"></div>
880      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="header.if-range" href="#header.if-range">If-Range</a></h2>
881      <p id="rfc.section.5.3.p.1">If a client has a partial copy of a representation and wishes to have an up-to-date copy of the entire representation, it
882         could use the <a href="#range.retrieval.requests" 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 condition fails because the representation has been modified, the client would then have to make a second
883         request to obtain the entire current representation.
884      </p>
885      <p id="rfc.section.5.3.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is: if the representation
886         is unchanged, send me the part(s) that I am requesting in Range; otherwise, send me the entire representation.
887      </p>
888      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.22"></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>
889</pre><p id="rfc.section.5.3.p.4">Clients <em class="bcp14">MUST NOT</em> use an entity-tag marked as weak in an If-Range field value and <em class="bcp14">MUST NOT</em> use a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> date in an If-Range field value unless it has no entity-tag for the representation and the Last-Modified date it does have
890         for the representation is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.
891      </p>
892      <p id="rfc.section.5.3.p.5">A server that evaluates a conditional range request that is applicable to one of its representations <em class="bcp14">MUST</em> evaluate the condition as false if the entity-tag used as a validator is marked as weak or, when an HTTP-date is used as the
893         validator, if the date value is not strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>. (A server can distinguish between a valid HTTP-date and any form of entity-tag by examining the first two characters.)
894      </p>
895      <p id="rfc.section.5.3.p.6">The If-Range header field <em class="bcp14">SHOULD</em> only be sent by clients together with a Range header field. The If-Range header field <em class="bcp14">MUST</em> be ignored if it is received in a request that does not include a Range header field. The If-Range header field <em class="bcp14">MUST</em> be ignored by a server that does not support the sub-range operation.
896      </p>
897      <p id="rfc.section.5.3.p.7">If the validator given in the If-Range header field matches the current validator for the selected representation of the target
898         resource, then the server <em class="bcp14">SHOULD</em> send the specified sub-range of the representation using a <a href="#status.206" class="smpl">206 (Partial Content)</a> response. If the validator does not match, then the server <em class="bcp14">SHOULD</em> send the entire representation using a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response.
899      </p>
900      <div id="rfc.iref.r.1"></div>
901      <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="header.range" href="#header.range">Range</a></h2>
902      <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a id="range.retrieval.requests" href="#range.retrieval.requests">Range Retrieval Requests</a></h3>
903      <p id="rfc.section.5.4.1.p.1">The "Range" header field on a GET request modifies the method semantics to request transfer of only one or more sub-ranges
904         of the selected representation data in a successful response, rather than the entire representation data.
905      </p>
906      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
907  <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = <a href="#range.units" class="smpl">other-range-unit</a> "=" <a href="#range.retrieval.requests" class="smpl">other-range-set</a>
908  <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#imported.abnf" class="smpl">CHAR</a>
909</pre><p id="rfc.section.5.4.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,
910         since Range supports efficient recovery from partially failed transfers and partial retrieval of large representations. A
911         server <em class="bcp14">MUST</em> ignore a Range header field received with a request method other than GET.
912      </p>
913      <p id="rfc.section.5.4.1.p.4">An origin server <em class="bcp14">MUST</em> ignore a <a href="#range.retrieval.requests" class="smpl">Range</a> header field that contains a range unit it does not understand. A proxy <em class="bcp14">MAY</em> either discard a <a href="#range.retrieval.requests" class="smpl">Range</a> header field that contains a range unit it does not understand or pass it to the next inbound server when forwarding the request.
914      </p>
915      <p id="rfc.section.5.4.1.p.5">The Range header field is evaluated after evaluating the preconditions of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a> and only if the result of their evaluation is leading toward 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.
916      </p>
917      <p id="rfc.section.5.4.1.p.6">The If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section&nbsp;5.3</a>) can be used as a precondition to applying the Range header field.
918      </p>
919      <p id="rfc.section.5.4.1.p.7">If all of the preconditions are true, the server supports the Range header field for the target resource, the specified range(s)
920         are syntactically correct (as defined in <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;2.1</a>), and at least one of the ranges has a non-empty intersection with the current selected representation extent, then the server <em class="bcp14">MAY</em> respond with a status code of <a href="#status.206" class="smpl">206 (Partial Content)</a> and a payload containing one or more partial representations that correspond to those requested, as defined in <a href="#range.response" title="Responses to a Range Request">Section&nbsp;4</a>.
921      </p>
922      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
923      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="range.unit.registry" href="#range.unit.registry">Range Unit Registry</a></h2>
924      <p id="rfc.section.6.1.p.1">The HTTP Range Unit Registry defines the name space for the range unit names and refers to their corresponding specifications.
925         The registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt;.
926      </p>
927      <h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a id="range.unit.registry.procedure" href="#range.unit.registry.procedure">Procedure</a></h3>
928      <p id="rfc.section.6.1.1.p.1">Registration of an HTTP Range Unit <em class="bcp14">MUST</em> include the following fields:
929      </p>
930      <ul>
931         <li>Name</li>
932         <li>Description</li>
933         <li>Pointer to specification text</li>
934      </ul>
935      <p id="rfc.section.6.1.1.p.2">Values to be added to this name space 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="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
936      </p>
937      <h3 id="rfc.section.6.1.2"><a href="#rfc.section.6.1.2">6.1.2</a>&nbsp;<a id="range.unit.registration" href="#range.unit.registration">Registrations</a></h3>
938      <p id="rfc.section.6.1.2.p.1">The initial HTTP Range Unit Registry shall contain the registrations below:</p>
939      <div id="rfc.table.1">
940         <div id="iana.range.units.table"></div>
941         <table class="tt full left" cellpadding="3" cellspacing="0">
942            <thead>
943               <tr>
944                  <th>Range Specifier Name</th>
945                  <th>Description</th>
946                  <th>Reference</th>
947               </tr>
948            </thead>
949            <tbody>
950               <tr>
951                  <td class="left">bytes</td>
952                  <td class="left">a range of octets</td>
953                  <td class="left"><a href="#range.units" title="Range Units">Section&nbsp;2</a></td>
954               </tr>
955               <tr>
956                  <td class="left">none</td>
957                  <td class="left">reserved as keyword, indicating no ranges are supported</td>
958                  <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a></td>
959               </tr>
960            </tbody>
961         </table>
962      </div>
963      <p id="rfc.section.6.1.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
964      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2>
965      <p id="rfc.section.6.2.p.1">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
966      </p>
967      <div id="rfc.table.2">
968         <div id="iana.status.code.registration.table"></div>
969         <table class="tt full left" cellpadding="3" cellspacing="0">
970            <thead>
971               <tr>
972                  <th>Value</th>
973                  <th>Description</th>
974                  <th>Reference</th>
975               </tr>
976            </thead>
977            <tbody>
978               <tr>
979                  <td class="left">206</td>
980                  <td class="left">Partial Content</td>
981                  <td class="left"> <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;3.1</a>
982                  </td>
983               </tr>
984               <tr>
985                  <td class="left">416</td>
986                  <td class="left">Range Not Satisfiable</td>
987                  <td class="left"> <a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section&nbsp;3.2</a>
988                  </td>
989               </tr>
990            </tbody>
991         </table>
992      </div>
993      <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
994      <p id="rfc.section.6.3.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
995      </p>
996      <div id="rfc.table.3">
997         <div id="iana.header.registration.table"></div>
998         <table class="tt full left" cellpadding="3" cellspacing="0">
999            <thead>
1000               <tr>
1001                  <th>Header Field Name</th>
1002                  <th>Protocol</th>
1003                  <th>Status</th>
1004                  <th>Reference</th>
1005               </tr>
1006            </thead>
1007            <tbody>
1008               <tr>
1009                  <td class="left">Accept-Ranges</td>
1010                  <td class="left">http</td>
1011                  <td class="left">standard</td>
1012                  <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.2" title="Accept-Ranges">Section&nbsp;5.1</a>
1013                  </td>
1014               </tr>
1015               <tr>
1016                  <td class="left">Content-Range</td>
1017                  <td class="left">http</td>
1018                  <td class="left">standard</td>
1019                  <td class="left"> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
1020                  </td>
1021               </tr>
1022               <tr>
1023                  <td class="left">If-Range</td>
1024                  <td class="left">http</td>
1025                  <td class="left">standard</td>
1026                  <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">Section&nbsp;5.3</a>
1027                  </td>
1028               </tr>
1029               <tr>
1030                  <td class="left">Range</td>
1031                  <td class="left">http</td>
1032                  <td class="left">standard</td>
1033                  <td class="left"> <a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;5.4</a>
1034                  </td>
1035               </tr>
1036            </tbody>
1037         </table>
1038      </div>
1039      <p id="rfc.section.6.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
1040      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
1041      <p id="rfc.section.7.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP/1.1
1042         range request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>.
1043      </p>
1044      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="overlapping.ranges" href="#overlapping.ranges">Overlapping Ranges</a></h2>
1045      <p id="rfc.section.7.1.p.1">Range requests containing overlapping ranges can lead to a situation where the server is sending far more data than the size
1046         of the complete resource representation.
1047      </p>
1048      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
1049      <p id="rfc.section.8.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
1050      </p>
1051      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
1052      </h1>
1053      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
1054      </h2>
1055      <table>             
1056         <tr>
1057            <td class="reference"><b id="Part1">[Part1]</b></td>
1058            <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="http://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), January&nbsp;2013.
1059            </td>
1060         </tr>
1061         <tr>
1062            <td class="reference"><b id="Part2">[Part2]</b></td>
1063            <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="http://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), January&nbsp;2013.
1064            </td>
1065         </tr>
1066         <tr>
1067            <td class="reference"><b id="Part4">[Part4]</b></td>
1068            <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="http://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), January&nbsp;2013.
1069            </td>
1070         </tr>
1071         <tr>
1072            <td class="reference"><b id="Part6">[Part6]</b></td>
1073            <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="http://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), January&nbsp;2013.
1074            </td>
1075         </tr>
1076         <tr>
1077            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
1078            <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="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
1079            </td>
1080         </tr>
1081         <tr>
1082            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1083            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://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.
1084            </td>
1085         </tr>
1086         <tr>
1087            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1088            <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="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
1089            </td>
1090         </tr>
1091      </table>
1092      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
1093      </h2>
1094      <table>       
1095         <tr>
1096            <td class="reference"><b id="BCP13">[BCP13]</b></td>
1097            <td class="top"><a href="mailto:ned.freed@mrochek.com" title="Sun Microsystems">Freed, N.</a> and <a href="mailto:klensin+ietf@jck.com">J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
1098            </td>
1099         </tr>
1100         <tr>
1101            <td class="reference"><b id="BCP90">[BCP90]</b></td>
1102            <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="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
1103            </td>
1104         </tr>
1105         <tr>
1106            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1107            <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="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
1108            </td>
1109         </tr>
1110         <tr>
1111            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
1112            <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="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
1113            </td>
1114         </tr>
1115      </table>
1116      <div class="avoidbreak">
1117         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1118         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
1119               (editor)
1120               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
1121         <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
1122               (editor)
1123               <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span>&nbsp;<span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">Email: <a href="mailto:ylafon@w3.org"><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address>
1124         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
1125               (editor)
1126               <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
1127      </div>
1128      <div id="rfc.iref.m.1"></div>
1129      <div id="rfc.iref.m.2"></div>
1130      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="internet.media.type.multipart.byteranges" href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></h1>
1131      <p id="rfc.section.A.p.1">When an HTTP <a href="#status.206" class="smpl">206 (Partial Content)</a> response message includes the content of multiple ranges (a response to a request for multiple non-overlapping ranges), these
1132         are transmitted as a multipart message body (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-5.1">Section 5.1</a>). The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a>.
1133      </p>
1134      <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more 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.
1135      </p>
1136      <p id="rfc.section.A.p.3"> </p>
1137      <dl>
1138         <dt>Type name:</dt>
1139         <dd>multipart</dd>
1140         <dt>Subtype name:</dt>
1141         <dd>byteranges</dd>
1142         <dt>Required parameters:</dt>
1143         <dd>boundary</dd>
1144         <dt>Optional parameters:</dt>
1145         <dd>none</dd>
1146         <dt>Encoding considerations:</dt>
1147         <dd>only "7bit", "8bit", or "binary" are permitted</dd>
1148         <dt>Security considerations:</dt>
1149         <dd>none</dd>
1150         <dt>Interoperability considerations:</dt>
1151         <dd>none</dd>
1152         <dt>Published specification:</dt>
1153         <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
1154         </dd>
1155         <dt>Applications that use this media type:</dt>
1156         <dd>HTTP components supporting multiple ranges in a single request.</dd>
1157         <dt>Additional information:</dt>
1158         <dd>
1159            <dl>
1160               <dt>Magic number(s):</dt>
1161               <dd>none</dd>
1162               <dt>File extension(s):</dt>
1163               <dd>none</dd>
1164               <dt>Macintosh file type code(s):</dt>
1165               <dd>none</dd>
1166            </dl>
1167         </dd>
1168         <dt>Person and email address to contact for further information:</dt>
1169         <dd>See Authors Section.</dd>
1170         <dt>Intended usage:</dt>
1171         <dd>COMMON</dd>
1172         <dt>Restrictions on usage:</dt>
1173         <dd>none</dd>
1174         <dt>Author/Change controller:</dt>
1175         <dd>IESG</dd>
1176      </dl>
1177      <div class="note" id="rfc.section.A.p.4">
1178         <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
1179         </p>
1180      </div>
1181      <div id="rfc.figure.u.25"></div>
1182      <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
1183  Date: Wed, 15 Nov 1995 06:25:24 GMT
1184  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
1185  Content-Length: 1741
1186  Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1187 
1188  --THIS_STRING_SEPARATES
1189  Content-Type: application/pdf
1190  Content-Range: bytes 500-999/8000
1191 
1192  ...the first range...
1193  --THIS_STRING_SEPARATES
1194  Content-Type: application/pdf
1195  Content-Range: bytes 7000-7999/8000
1196 
1197  ...the second range
1198  --THIS_STRING_SEPARATES--
1199</pre><div id="rfc.figure.u.26"></div>
1200      <p>Another example, using the "exampleunit" range unit:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
1201  Date: Tue, 14 Nov 1995 06:25:24 GMT
1202  Last-Modified: Tue, 14 July 04:58:08 GMT
1203  Content-Length: 2331785
1204  Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1205 
1206  --THIS_STRING_SEPARATES
1207  Content-Type: video/example
1208  Content-Range: exampleunit 1.2-4.3/25
1209 
1210  ...the first range...
1211  --THIS_STRING_SEPARATES
1212  Content-Type: video/example
1213  Content-Range: exampleunit 11.2-14.3/25
1214 
1215  ...the second range
1216  --THIS_STRING_SEPARATES--
1217</pre> <p id="rfc.section.A.p.7">Notes: </p>
1218      <ol>
1219         <li>Additional CRLFs <em class="bcp14">MAY</em> precede the first boundary string in the body.
1220         </li>
1221         <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.
1222         </li>
1223         <li>A number of clients and servers were coded to an early draft of the byteranges specification to use a media type of multipart/x-byteranges<span id="rfc.iref.m.3"></span><span id="rfc.iref.m.4"></span>, which is almost, but not quite compatible with the version documented in HTTP/1.1.
1224         </li>
1225      </ol>
1226      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
1227      <p id="rfc.section.B.p.1">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;3.1</a>)
1228      </p>
1229      <p id="rfc.section.B.p.2">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.5" title="Content-Range">Section&nbsp;5.2</a>)
1230      </p>
1231      <p id="rfc.section.B.p.3">Servers are given more leeway in how they respond to a range request, in order to mitigate abuse by malicious (or just greedy)
1232         clients.
1233      </p>
1234      <p id="rfc.section.B.p.4">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>)
1235      </p>
1236      <p id="rfc.section.B.p.5">This specification introduces a Range Specifier Registry. (<a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;6.1</a>)
1237      </p>
1238      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
1239      <p id="rfc.section.C.p.1">The following core rules are included by reference, as defined in <a href="http://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
1240         (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
1241         character).
1242      </p>
1243      <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>.
1244      </p>
1245      <p id="rfc.section.C.p.3">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>:
1246      </p>
1247      <div id="rfc.figure.u.27"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>        = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>&gt;
1248  <a href="#imported.abnf" class="smpl">token</a>      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>&gt;
1249</pre><p id="rfc.section.C.p.5">The rules below are defined in other parts:</p>
1250      <div id="rfc.figure.u.28"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>&gt;
1251  <a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>&gt;
1252</pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
1253      <div id="rfc.figure.u.29"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
1254
1255<a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range / other-content-range
1256
1257<a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
1258
1259<a href="#header.if-range" class="smpl">If-Range</a> = entity-tag / HTTP-date
1260
1261<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
1262
1263<a href="#range.retrieval.requests" class="smpl">Range</a> = byte-ranges-specifier / other-ranges-specifier
1264
1265<a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = ( *( "," OWS ) range-unit *( OWS "," [ OWS
1266 range-unit ] ) ) / "none"
1267
1268<a href="#header.content-range" class="smpl">byte-content-range</a> = bytes-unit SP ( byte-range-resp /
1269 unsatisfied-range )
1270<a href="#header.content-range" class="smpl">byte-range</a> = first-byte-pos "-" last-byte-pos
1271<a href="#header.content-range" class="smpl">byte-range-resp</a> = byte-range "/" ( complete-length / "*" )
1272<a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = *( "," OWS ) ( byte-range-spec /
1273 suffix-byte-range-spec ) *( OWS "," [ OWS ( byte-range-spec /
1274 suffix-byte-range-spec ) ] )
1275<a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ]
1276<a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set
1277<a href="#range.units" class="smpl">bytes-unit</a> = "bytes"
1278
1279<a href="#header.content-range" class="smpl">complete-length</a> = 1*DIGIT
1280
1281<a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, defined in [Part4], Section 2.3&gt;
1282
1283<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT
1284
1285<a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*DIGIT
1286
1287<a href="#header.content-range" class="smpl">other-content-range</a> = other-range-unit SP other-range-resp
1288<a href="#header.content-range" class="smpl">other-range-resp</a> = *CHAR
1289<a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*CHAR
1290<a href="#range.units" class="smpl">other-range-unit</a> = token
1291<a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = other-range-unit "=" other-range-set
1292
1293<a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit
1294
1295<a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" suffix-length
1296<a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT
1297
1298<a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.6&gt;
1299
1300<a href="#header.content-range" class="smpl">unsatisfied-range</a> = "*/" complete-length
1301</pre> <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
1302      <p id="rfc.section.E.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D">http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D</a>&gt;.
1303      </p>
1304      <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p5-range-19</a></h2>
1305      <p id="rfc.section.E.1.p.1">Closed issues: </p>
1306      <ul>
1307         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>&gt;: "ABNF list expansion code problem"
1308         </li>
1309         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
1310         </li>
1311         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/367">http://tools.ietf.org/wg/httpbis/trac/ticket/367</a>&gt;: "reserve 'none' as byte range unit"
1312         </li>
1313         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>&gt;: "note introduction of new IANA registries as normative changes"
1314         </li>
1315         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>&gt;: "range units vs leading zeroes vs size"
1316         </li>
1317      </ul>
1318      <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;<a id="changes.since.20" href="#changes.since.20">Since draft-ietf-httpbis-p5-range-20</a></h2>
1319      <p id="rfc.section.E.2.p.1"> </p>
1320      <ul>
1321         <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li>
1322      </ul>
1323      <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;<a id="changes.since.21" href="#changes.since.21">Since draft-ietf-httpbis-p5-range-21</a></h2>
1324      <p id="rfc.section.E.3.p.1">None yet.</p>
1325      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1326      <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.P">P</a> <a href="#rfc.index.R">R</a>
1327      </p>
1328      <div class="print2col">
1329         <ul class="ind">
1330            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
1331                  <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.11"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.2</a>, <a href="#rfc.xref.status.206.2">B</a></li>
1332               </ul>
1333            </li>
1334            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1335                  <li>416 Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.11"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">6.2</a></li>
1336               </ul>
1337            </li>
1338            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1339                  <li>Accept-Ranges header field&nbsp;&nbsp;<a href="#rfc.iref.a.1"><b>5.1</b></a>, <a href="#rfc.xref.header.accept-ranges.1">6.1.2</a>, <a href="#rfc.xref.header.accept-ranges.2">6.3</a></li>
1340               </ul>
1341            </li>
1342            <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul>
1343                  <li><em>BCP13</em>&nbsp;&nbsp;<a href="#BCP13"><b>9.2</b></a>, <a href="#rfc.xref.BCP13.1">A</a></li>
1344                  <li><em>BCP90</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP90.1">6.3</a>, <a href="#BCP90"><b>9.2</b></a></li>
1345               </ul>
1346            </li>
1347            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1348                  <li>Content-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.c.1"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.3</a>, <a href="#rfc.xref.header.content-range.5">B</a></li>
1349               </ul>
1350            </li>
1351            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1352                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1353                     <ul>
1354                        <li><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>5.1</b></a></li>
1355                        <li><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>5.1</b></a></li>
1356                        <li><tt>byte-content-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>5.2</b></a></li>
1357                        <li><tt>byte-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>5.2</b></a></li>
1358                        <li><tt>byte-range-resp</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>5.2</b></a></li>
1359                        <li><tt>byte-range-set</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>2.1</b></a></li>
1360                        <li><tt>byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>2.1</b></a></li>
1361                        <li><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>2.1</b></a></li>
1362                        <li><tt>bytes-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2</b></a></li>
1363                        <li><tt>complete-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>5.2</b></a></li>
1364                        <li><tt>Content-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>5.2</b></a></li>
1365                        <li><tt>first-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>2.1</b></a></li>
1366                        <li><tt>If-Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>5.3</b></a></li>
1367                        <li><tt>last-byte-pos</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>2.1</b></a></li>
1368                        <li><tt>other-content-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>5.2</b></a></li>
1369                        <li><tt>other-range-resp</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>5.2</b></a></li>
1370                        <li><tt>other-range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>2</b></a></li>
1371                        <li><tt>Range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>5.4.1</b></a></li>
1372                        <li><tt>range-unit</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
1373                        <li><tt>ranges-specifier</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>2.1</b></a></li>
1374                        <li><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>2.1</b></a></li>
1375                        <li><tt>suffix-length</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>2.1</b></a></li>
1376                        <li><tt>unsatisfied-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>5.2</b></a></li>
1377                     </ul>
1378                  </li>
1379               </ul>
1380            </li>
1381            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
1382                  <li>If-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.xref.header.if-range.2">3.2</a>, <a href="#rfc.iref.i.1"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.3">5.4.1</a>, <a href="#rfc.xref.header.if-range.4">6.3</a></li>
1383               </ul>
1384            </li>
1385            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
1386                  <li>Media Type&nbsp;&nbsp;
1387                     <ul>
1388                        <li>multipart/byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>A</b></a></li>
1389                        <li>multipart/x-byteranges&nbsp;&nbsp;<a href="#rfc.iref.m.4">A</a></li>
1390                     </ul>
1391                  </li>
1392                  <li>multipart/byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.2"><b>A</b></a></li>
1393                  <li>multipart/x-byteranges Media Type&nbsp;&nbsp;<a href="#rfc.iref.m.3">A</a></li>
1394               </ul>
1395            </li>
1396            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1397                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">7</a>, <a href="#rfc.xref.Part1.4">8</a>, <a href="#Part1"><b>9.1</b></a>, <a href="#rfc.xref.Part1.5">C</a>, <a href="#rfc.xref.Part1.6">C</a>, <a href="#rfc.xref.Part1.7">C</a><ul>
1398                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
1399                        <li><em>Section 2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a></li>
1400                        <li><em>Section 3.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">C</a></li>
1401                        <li><em>Section 3.2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">C</a></li>
1402                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">8</a></li>
1403                     </ul>
1404                  </li>
1405                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">7</a>, <a href="#Part2"><b>9.1</b></a>, <a href="#rfc.xref.Part2.2">C</a><ul>
1406                        <li><em>Section 7.1.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">C</a></li>
1407                     </ul>
1408                  </li>
1409                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.2</a>, <a href="#rfc.xref.Part4.2">4.2</a>, <a href="#rfc.xref.Part4.3">5.3</a>, <a href="#rfc.xref.Part4.4">5.3</a>, <a href="#rfc.xref.Part4.5">5.4.1</a>, <a href="#Part4"><b>9.1</b></a>, <a href="#rfc.xref.Part4.6">C</a><ul>
1410                        <li><em>Section 2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">4.2</a>, <a href="#rfc.xref.Part4.3">5.3</a>, <a href="#rfc.xref.Part4.4">5.3</a></li>
1411                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.2</a>, <a href="#rfc.xref.Part4.6">C</a></li>
1412                     </ul>
1413                  </li>
1414                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a>, <a href="#Part6"><b>9.1</b></a><ul>
1415                        <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a></li>
1416                     </ul>
1417                  </li>
1418               </ul>
1419            </li>
1420            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1421                  <li>Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.xref.header.range.2">3.1</a>, <a href="#rfc.xref.header.range.3">3.2</a>, <a href="#rfc.iref.r.1"><b>5.4</b></a>, <a href="#rfc.xref.header.range.4">6.3</a></li>
1422                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#RFC2046"><b>9.1</b></a>, <a href="#rfc.xref.RFC2046.1">A</a>, <a href="#rfc.xref.RFC2046.2">A</a><ul>
1423                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">A</a></li>
1424                     </ul>
1425                  </li>
1426                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>9.1</b></a></li>
1427                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#RFC2616"><b>9.2</b></a></li>
1428                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">6.1.1</a>, <a href="#RFC5226"><b>9.2</b></a><ul>
1429                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">6.1.1</a></li>
1430                     </ul>
1431                  </li>
1432                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#RFC5234"><b>9.1</b></a>, <a href="#rfc.xref.RFC5234.2">C</a><ul>
1433                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">C</a></li>
1434                     </ul>
1435                  </li>
1436               </ul>
1437            </li>
1438         </ul>
1439      </div>
1440   </body>
1441</html>
Note: See TracBrowser for help on using the repository browser.