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

Last change on this file since 695 was 689, checked in by julian.reschke@…, 10 years ago

Bump up document dates, update to latest version of rfc2629.xslt

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 102.4 KB
RevLine 
[52]1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
[573]4   <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
[52]5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>HTTP/1.1, part 5: Range Requests and Partial Responses</title><style type="text/css" title="Xml2Rfc (sans serif)">
7a {
8  text-decoration: none;
9}
10a.smpl {
11  color: black;
12}
13a:hover {
14  text-decoration: underline;
15}
16a:active {
17  text-decoration: underline;
18}
19address {
20  margin-top: 1em;
21  margin-left: 2em;
22  font-style: normal;
23}
24body {
25  color: black;
26  font-family: verdana, helvetica, arial, sans-serif;
27  font-size: 10pt;
28}
29cite {
30  font-style: normal;
31}
[563]32div.note {
33  margin-left: 2em;
34}
[52]35dd {
36  margin-right: 2em;
37}
38dl {
39  margin-left: 2em;
40}
41
42dl.empty dd {
43  margin-top: .5em;
44}
45dl p {
46  margin-left: 0em;
47}
48dt {
49  margin-top: .5em;
50}
51h1 {
52  font-size: 14pt;
53  line-height: 21pt;
54  page-break-after: avoid;
55}
56h1.np {
57  page-break-before: always;
58}
59h1 a {
60  color: #333333;
61}
62h2 {
63  font-size: 12pt;
64  line-height: 15pt;
65  page-break-after: avoid;
66}
[446]67h3, h4, h5, h6 {
[52]68  font-size: 10pt;
69  page-break-after: avoid;
70}
[446]71h2 a, h3 a, h4 a, h5 a, h6 a {
[52]72  color: black;
73}
74img {
75  margin-left: 3em;
76}
77li {
78  margin-left: 2em;
79  margin-right: 2em;
80}
81ol {
82  margin-left: 2em;
83  margin-right: 2em;
84}
85ol p {
86  margin-left: 0em;
87}
88p {
89  margin-left: 2em;
90  margin-right: 2em;
91}
92pre {
93  margin-left: 3em;
94  background-color: lightyellow;
95  padding: .25em;
96}
97pre.text2 {
98  border-style: dotted;
99  border-width: 1px;
100  background-color: #f0f0f0;
101  width: 69em;
102}
103pre.inline {
104  background-color: white;
105  padding: 0em;
106}
107pre.text {
108  border-style: dotted;
109  border-width: 1px;
110  background-color: #f8f8f8;
111  width: 69em;
112}
113pre.drawing {
114  border-style: solid;
115  border-width: 1px;
116  background-color: #f8f8f8;
117  padding: 2em;
118}
119table {
120  margin-left: 2em;
121}
[253]122table.tt {
123  vertical-align: top;
124}
125table.full {
126  border-style: outset;
127  border-width: 1px;
128}
129table.headers {
130  border-style: outset;
131  border-width: 1px;
132}
133table.tt td {
134  vertical-align: top;
135}
136table.full td {
137  border-style: inset;
138  border-width: 1px;
139}
140table.tt th {
141  vertical-align: top;
142}
143table.full th {
144  border-style: inset;
145  border-width: 1px;
146}
147table.headers th {
148  border-style: none none inset none;
149  border-width: 1px;
150}
[675]151table.left {
152  margin-right: auto;
153}
154table.right {
155  margin-left: auto;
156}
157table.center {
158  margin-left: auto;
159  margin-right: auto;
160}
[454]161caption {
162  caption-side: bottom;
163  font-weight: bold;
164  font-size: 9pt;
165  margin-top: .5em;
166}
167
[52]168table.header {
169  width: 95%;
170  font-size: 10pt;
171  color: white;
172}
173td.top {
174  vertical-align: top;
175}
176td.topnowrap {
177  vertical-align: top;
178  white-space: nowrap; 
179}
180td.header {
181  background-color: gray;
182  width: 50%;
183}
[227]184td.header a {
185  color: white;
186}
[52]187td.reference {
188  vertical-align: top;
189  white-space: nowrap;
190  padding-right: 1em;
191}
192thead {
193  display:table-header-group;
194}
195ul.toc {
196  list-style: none;
197  margin-left: 1.5em;
198  margin-right: 0em;
199  padding-left: 0em;
200}
201li.tocline0 {
202  line-height: 150%;
203  font-weight: bold;
204  font-size: 10pt;
205  margin-left: 0em;
206  margin-right: 0em;
207}
208li.tocline1 {
209  line-height: normal;
210  font-weight: normal;
211  font-size: 9pt;
212  margin-left: 0em;
213  margin-right: 0em;
214}
215li.tocline2 {
216  font-size: 0pt;
217}
218ul p {
219  margin-left: 0em;
220}
221ul.ind {
222  list-style: none;
223  margin-left: 1.5em;
224  margin-right: 0em;
225  padding-left: 0em;
[440]226  page-break-before: avoid;
[52]227}
228li.indline0 {
229  font-weight: bold;
230  line-height: 200%;
231  margin-left: 0em;
232  margin-right: 0em;
233}
234li.indline1 {
235  font-weight: normal;
236  line-height: 150%;
237  margin-left: 0em;
238  margin-right: 0em;
239}
[662]240.avoidbreak {
241  page-break-inside: avoid;
242}
[52]243.bcp14 {
244  font-style: normal;
245  text-transform: lowercase;
246  font-variant: small-caps;
247}
248.comment {
249  background-color: yellow;
250}
251.center {
252  text-align: center;
253}
254.error {
255  color: red;
256  font-style: italic;
257  font-weight: bold;
258}
259.figure {
260  font-weight: bold;
261  text-align: center;
262  font-size: 9pt;
263}
264.filename {
265  color: #333333;
266  font-weight: bold;
267  font-size: 12pt;
268  line-height: 21pt;
269  text-align: center;
270}
271.fn {
272  font-weight: bold;
273}
274.hidden {
275  display: none;
276}
277.left {
278  text-align: left;
279}
280.right {
281  text-align: right;
282}
283.title {
284  color: #990000;
285  font-size: 18pt;
286  line-height: 18pt;
287  font-weight: bold;
288  text-align: center;
289  margin-top: 36pt;
290}
291.vcardline {
292  display: block;
293}
294.warning {
295  font-size: 14pt;
296  background-color: yellow;
297}
298
299
300@media print {
301  .noprint {
302    display: none;
303  }
304 
305  a {
306    color: black;
307    text-decoration: none;
308  }
309
310  table.header {
311    width: 90%;
312  }
313
314  td.header {
315    width: 50%;
316    color: black;
317    background-color: white;
318    vertical-align: top;
319    font-size: 12pt;
320  }
321
322  ul.toc a::after {
323    content: leader('.') target-counter(attr(href), page);
324  }
325 
326  a.iref {
327    content: target-counter(attr(href), page);
328  }
329 
330  .print2col {
331    column-count: 2;
332    -moz-column-count: 2;
333    column-fill: auto;
334  }
335}
336
337@page {
338  @top-left {
339       content: "INTERNET DRAFT"; 
340  } 
341  @top-right {
[689]342       content: "September 2009"; 
[52]343  } 
344  @top-center {
[120]345       content: "HTTP/1.1, Part 5"; 
[52]346  } 
347  @bottom-left {
348       content: "Fielding, et al."; 
349  } 
350  @bottom-center {
351       content: "Standards Track"; 
352  } 
353  @bottom-right {
354       content: "[Page " counter(page) "]"; 
355  } 
356}
357
358@page:first { 
359    @top-left {
360      content: normal;
361    }
362    @top-right {
363      content: normal;
364    }
365    @top-center {
366      content: normal;
367    }
368}
369</style><link rel="Contents" href="#rfc.toc">
370      <link rel="Author" href="#rfc.authors">
371      <link rel="Copyright" href="#rfc.copyright">
372      <link rel="Index" href="#rfc.index">
373      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
[424]374      <link rel="Chapter" title="2 Range Units" href="#rfc.section.2">
375      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
376      <link rel="Chapter" title="4 Combining Ranges" href="#rfc.section.4">
377      <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5">
378      <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6">
379      <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7">
380      <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8">
381      <link rel="Chapter" href="#rfc.section.9" title="9 References">
[52]382      <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
[99]383      <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B">
[421]384      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
385      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
[689]386      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.451, 2009-08-28 12:08:05, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
[52]387      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
388      <meta name="DC.Creator" content="Fielding, R.">
389      <meta name="DC.Creator" content="Gettys, J.">
390      <meta name="DC.Creator" content="Mogul, J.">
391      <meta name="DC.Creator" content="Frystyk, H.">
392      <meta name="DC.Creator" content="Masinter, L.">
393      <meta name="DC.Creator" content="Leach, P.">
394      <meta name="DC.Creator" content="Berners-Lee, T.">
[95]395      <meta name="DC.Creator" content="Lafon, Y.">
396      <meta name="DC.Creator" content="Reschke, J. F.">
[52]397      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
[689]398      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-01">
[52]399      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
400      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">
[689]401      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">
[52]402   </head>
403   <body>
404      <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
405         <tr>
[440]406            <td class="header left">HTTPbis Working Group</td>
[52]407            <td class="header right">R. Fielding, Editor</td>
408         </tr>
409         <tr>
410            <td class="header left">Internet Draft</td>
411            <td class="header right">Day Software</td>
412         </tr>
413         <tr>
414            <td class="header left">
415               &lt;draft-ietf-httpbis-p5-range-latest&gt;
416               
417            </td>
418            <td class="header right">J. Gettys</td>
419         </tr>
420         <tr>
[150]421            <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
[52]422            </td>
423            <td class="header right">One Laptop per Child</td>
424         </tr>
425         <tr>
426            <td class="header left">Intended status: Standards Track</td>
427            <td class="header right">J. Mogul</td>
428         </tr>
429         <tr>
[689]430            <td class="header left">Expires: March 5, 2010</td>
[52]431            <td class="header right">HP</td>
432         </tr>
433         <tr>
434            <td class="header left"></td>
435            <td class="header right">H. Frystyk</td>
436         </tr>
437         <tr>
438            <td class="header left"></td>
439            <td class="header right">Microsoft</td>
440         </tr>
441         <tr>
442            <td class="header left"></td>
443            <td class="header right">L. Masinter</td>
444         </tr>
445         <tr>
446            <td class="header left"></td>
447            <td class="header right">Adobe Systems</td>
448         </tr>
449         <tr>
450            <td class="header left"></td>
451            <td class="header right">P. Leach</td>
452         </tr>
453         <tr>
454            <td class="header left"></td>
455            <td class="header right">Microsoft</td>
456         </tr>
457         <tr>
458            <td class="header left"></td>
459            <td class="header right">T. Berners-Lee</td>
460         </tr>
461         <tr>
462            <td class="header left"></td>
463            <td class="header right">W3C/MIT</td>
464         </tr>
465         <tr>
466            <td class="header left"></td>
[95]467            <td class="header right">Y. Lafon, Editor</td>
468         </tr>
469         <tr>
470            <td class="header left"></td>
471            <td class="header right">W3C</td>
472         </tr>
473         <tr>
474            <td class="header left"></td>
475            <td class="header right">J. F. Reschke, Editor</td>
476         </tr>
477         <tr>
478            <td class="header left"></td>
479            <td class="header right">greenbytes</td>
480         </tr>
481         <tr>
482            <td class="header left"></td>
[689]483            <td class="header right">September 1, 2009</td>
[52]484         </tr>
485      </table>
486      <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-latest</span></p>
487      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
[446]488      <p>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This
489         document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
490         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
491         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
492         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
493         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
494         it into languages other than English.
[52]495      </p>
496      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
497         that other groups may also distribute working documents as Internet-Drafts.
498      </p>
499      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
500         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
501         in progress”.
502      </p>
503      <p>The list of current Internet-Drafts can be accessed at &lt;<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>&gt;.
504      </p>
505      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
506      </p>
[689]507      <p>This Internet-Draft will expire in March 5, 2010.</p>
[446]508      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
509      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
510      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date
511         of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
512      </p>
[52]513      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
514      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
515         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
516         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
517         5 defines range-specific requests and the rules for constructing and combining responses to those requests.
518      </p> 
519      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
520      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
[324]521         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
[153]522      </p> 
[604]523      <p>The changes in this draft are summarized in <a href="#changes.since.07" title="Since draft-ietf-httpbis-p5-range-07">Appendix&nbsp;D.9</a>.
[52]524      </p> 
525      <hr class="noprint">
526      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
527      <ul class="toc">
[96]528         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
529               <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
[424]530               <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul class="toc">
531                     <li class="tocline1">1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
532                     <li class="tocline1">1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
533                  </ul>
534               </li>
[96]535            </ul>
536         </li>
[424]537         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
538         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul class="toc">
539               <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
540               <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
[52]541            </ul>
542         </li>
[424]543         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Ranges</a></li>
544         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
545               <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
546               <li class="tocline1">5.2&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
547               <li class="tocline1">5.3&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
548               <li class="tocline1">5.4&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul class="toc">
549                     <li class="tocline1">5.4.1&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
550                     <li class="tocline1">5.4.2&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
[52]551                  </ul>
552               </li>
553            </ul>
554         </li>
[424]555         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
556               <li class="tocline1">6.1&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
[253]557            </ul>
558         </li>
[424]559         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
560         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
561         <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
562               <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
563               <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
[119]564            </ul>
565         </li>
[52]566         <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
567         <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
[99]568         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">
569               <li class="tocline1">B.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
570               <li class="tocline1">B.2&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
571            </ul>
572         </li>
[421]573         <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
574         <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
575               <li class="tocline1">D.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.1">Since RFC2616</a></li>
576               <li class="tocline1">D.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.2">Since draft-ietf-httpbis-p5-range-00</a></li>
577               <li class="tocline1">D.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.D.3">Since draft-ietf-httpbis-p5-range-01</a></li>
578               <li class="tocline1">D.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></li>
579               <li class="tocline1">D.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></li>
580               <li class="tocline1">D.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></li>
581               <li class="tocline1">D.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></li>
[547]582               <li class="tocline1">D.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></li>
[604]583               <li class="tocline1">D.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></li>
[115]584            </ul>
585         </li>
[52]586         <li class="tocline0"><a href="#rfc.index">Index</a></li>
587      </ul>
588      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
[158]589      <p id="rfc.section.1.p.1">HTTP clients often encounter interrupted data transfers as a result of cancelled requests or dropped connections. When a cache
590         has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
591         rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
592         request only a subset of a larger representation, such as a single page of a very large document or only part of an image
593         to be rendered by a device with limited local storage.
[52]594      </p>
[163]595      <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
596         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
597         request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for
598         full responses by intermediate caches that might not implement the feature.
[158]599      </p>
[163]600      <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
[158]601         requests for byte ranges.
602      </p>
[96]603      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
604      <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"
605         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>.
606      </p>
607      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
608      </p>
[424]609      <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>
[543]610      <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF, with the list rule expanded.
611      </p>
612      <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
[425]613         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
614         and WSP (whitespace).
[52]615      </p>
[424]616      <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
617      <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
618      </p>
[425]619      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">token</a>      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
620  <a href="#core.rules" class="smpl">OWS</a>        = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
[424]621</pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
622      <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
[678]623      <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>&gt;
[425]624</pre><div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#entity.tags" title="Entity Tags">Section 2</a>&gt;
[424]625</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
626      <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1
627         uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;5.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;5.2</a>) header fields. An entity can be broken down into subranges according to various structural units.
[205]628      </p>
[425]629      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#range.units" class="smpl">range-unit</a>       = <a href="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a>
[229]630  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
[424]631  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a>
632</pre><p id="rfc.section.2.p.3">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges. The only range
[393]633         unit defined by HTTP/1.1 is "bytes".
[52]634      </p>
[424]635      <p id="rfc.section.2.p.4">If a range unit is not understood in a request, a server <em class="bcp14">MUST</em> ignore the whole Range header (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;5.4</a>). If a range unit is not understood in a response, an intermediary <em class="bcp14">SHOULD</em> pass the response to the client; a client <em class="bcp14">MUST</em> fail.
[393]636      </p>
[424]637      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
[52]638      </h1>
639      <div id="rfc.iref.3"></div>
640      <div id="rfc.iref.s.1"></div>
[424]641      <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>
642      <p id="rfc.section.3.1.p.1">The server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a Range header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;5.4</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;5.3</a>) to make the request conditional.
[52]643      </p>
[424]644      <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
[52]645      </p>
646      <ul>
[424]647         <li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;5.2</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields
[52]648            for each part. If a Content-Length header field is present in the response, its value <em class="bcp14">MUST</em> match the actual number of OCTETs transmitted in the message-body.
649         </li>
650         <li>Date</li>
651         <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
652         <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
653            variant
654         </li>
655      </ul>
[424]656      <p id="rfc.section.3.1.p.3">If the 206 response is the result of an If-Range request, the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. Otherwise, the response <em class="bcp14">MUST</em> include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
[52]657      </p>
[424]658      <p id="rfc.section.3.1.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see <a href="#combining.byte.ranges" title="Combining Ranges">Section&nbsp;4</a>.
[52]659      </p>
[424]660      <p id="rfc.section.3.1.p.5">A cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> cache 206 (Partial Content) responses. Furthermore, if a response uses a range unit that is not understood by the cache, then
[393]661         it <em class="bcp14">MUST NOT</em> be cached either.
[52]662      </p>
663      <div id="rfc.iref.4"></div>
664      <div id="rfc.iref.s.2"></div>
[424]665      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h2>
666      <p id="rfc.section.3.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range request-header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;5.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request
[52]667         did not include an If-Range request-header field. (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec
668         values were greater than the current length of the selected resource.)
669      </p>
[424]670      <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range entity-header field specifying the current length of the selected resource (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.
[52]671      </p>
[424]672      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Ranges</a></h1>
673      <p id="rfc.section.4.p.1">A response might transfer only a subrange of an entity-body, either the request included one or more Range specifications,
[393]674         or because a connection was broken prematurely. After several such transfers, a cache might have received several ranges of
675         the same entity-body.
[52]676      </p>
[424]677      <p id="rfc.section.4.p.2">If a cache has a stored non-empty set of subranges for an entity, and an incoming response transfers another subrange, the
[52]678         cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
679      </p>
680      <ul>
681         <li>Both the incoming response and the cache entry have a cache validator.</li>
[424]682         <li>The two cache validators match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak and Strong Validators">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
[52]683         </li>
684      </ul>
[424]685      <p id="rfc.section.4.p.3">If either requirement is not met, the cache <em class="bcp14">MUST</em> use only the most recent partial response (based on the Date values transmitted with every response, and using the incoming
[52]686         response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
687      </p>
[424]688      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
689      <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>
690      <p id="rfc.section.5.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
[117]691         receives the entity.
[52]692      </p>
693      <div id="rfc.iref.a.1"></div>
694      <div id="rfc.iref.h.1"></div>
[424]695      <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>
696      <p id="rfc.section.5.1.p.1">The response-header "Accept-Ranges" field allows the server to indicate its acceptance of range requests for a resource:</p>
[425]697      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = "Accept-Ranges" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>
[363]698  <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>   = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
[334]699  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
[424]700</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
[52]701      </p>
[425]702      <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: bytes
[424]703</pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate range requests without having received this header for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
[52]704      </p>
[424]705      <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
[52]706      </p>
[425]707      <div id="rfc.figure.u.7"></div><pre class="text">  Accept-Ranges: none
[424]708</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
[52]709      <div id="rfc.iref.c.1"></div>
710      <div id="rfc.iref.h.2"></div>
[424]711      <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>
712      <p id="rfc.section.5.2.p.1">The entity-header "Content-Range" is sent with a partial entity-body to specify where in the full entity-body the partial
713         body should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
[52]714      </p>
[425]715      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-range" class="smpl">Content-Range-v</a>
[363]716  <a href="#header.content-range" class="smpl">Content-Range-v</a> = <a href="#header.content-range" class="smpl">content-range-spec</a>
[135]717 
[229]718  <a href="#header.content-range" class="smpl">content-range-spec</a>      = <a href="#header.content-range" class="smpl">byte-content-range-spec</a>
[434]719                          / <a href="#header.content-range" class="smpl">other-content-range-spec</a>
[425]720  <a href="#header.content-range" class="smpl">byte-content-range-spec</a> = <a href="#range.units" class="smpl">bytes-unit</a> <a href="#notation" class="smpl">SP</a>
[229]721                            <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> "/"
[334]722                            ( <a href="#header.content-range" class="smpl">instance-length</a> / "*" )
[135]723 
[308]724  <a href="#header.content-range" class="smpl">byte-range-resp-spec</a>    = (<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>)
[334]725                          / "*"
[308]726                         
[425]727  <a href="#header.content-range" class="smpl">instance-length</a>         = 1*<a href="#notation" class="smpl">DIGIT</a>
[393]728 
[425]729  <a href="#header.content-range" class="smpl">other-content-range-spec</a> = <a href="#range.units" class="smpl">other-range-unit</a> <a href="#notation" class="smpl">SP</a>
[393]730                             <a href="#header.content-range" class="smpl">other-range-resp-spec</a>
[425]731  <a href="#header.content-range" class="smpl">other-range-resp-spec</a>    = *<a href="#notation" class="smpl">CHAR</a>
[424]732</pre><p id="rfc.section.5.2.p.3">The header <em class="bcp14">SHOULD</em> indicate the total length of the full entity-body, unless this length is unknown or difficult to determine. The asterisk "*"
[52]733         character means that the instance-length is unknown at the time when the response was generated.
734      </p>
[424]735      <p id="rfc.section.5.2.p.4">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section&nbsp;5.4.1</a>), a byte-range-resp-spec <em class="bcp14">MUST</em> only specify one range, and <em class="bcp14">MUST</em> contain absolute byte positions for both the first and last byte of the range.
[52]736      </p>
[424]737      <p id="rfc.section.5.2.p.5">A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos value is less than its first-byte-pos value, or
[52]738         whose instance-length value is less than or equal to its last-byte-pos value, is invalid. The recipient of an invalid byte-content-range-spec <em class="bcp14">MUST</em> ignore it and any content transferred along with it.
739      </p>
[424]740      <p id="rfc.section.5.2.p.6">In the case of a byte range request: A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
[576]741         selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
[52]742      </p>
[424]743      <p id="rfc.section.5.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p>
[52]744      <ul>
745         <li>The first 500 bytes:
[565]746            <div id="rfc.figure.u.9"></div><pre class="text">  bytes 0-499/1234
[52]747</pre> </li>
748         <li>The second 500 bytes:
[565]749            <div id="rfc.figure.u.10"></div><pre class="text">  bytes 500-999/1234
[52]750</pre> </li>
751         <li>All except for the first 500 bytes:
[565]752            <div id="rfc.figure.u.11"></div><pre class="text">  bytes 500-1233/1234
[52]753</pre> </li>
754         <li>The last 500 bytes:
[565]755            <div id="rfc.figure.u.12"></div><pre class="text">  bytes 734-1233/1234
[52]756</pre> </li>
757      </ul>
[424]758      <p id="rfc.section.5.2.p.8">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to
[52]759         a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
760         a Content-Length header showing the number of bytes actually transferred. For example,
761      </p>
[425]762      <div id="rfc.figure.u.13"></div><pre class="text">  HTTP/1.1 206 Partial Content
[363]763  Date: Wed, 15 Nov 1995 06:25:24 GMT
764  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
765  Content-Range: bytes 21010-47021/47022
766  Content-Length: 26012
767  Content-Type: image/gif
[424]768</pre><p id="rfc.section.5.2.p.10">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping
[52]769         ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
[99]770         as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>. See <a href="#changes.from.rfc.2068" title="Changes from RFC 2068">Appendix&nbsp;B.1</a> for a compatibility issue.
[52]771      </p>
[424]772      <p id="rfc.section.5.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
[52]773      </p>
[648]774      <p id="rfc.section.5.2.p.12">When a client requests multiple ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
[52]775      </p>
[424]776      <p id="rfc.section.5.2.p.13">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing
[52]777         the full entity).
778      </p>
[424]779      <p id="rfc.section.5.2.p.14">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header
[52]780         field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
[563]781         resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>).
[52]782      </p>
[563]783      <div class="note"> 
784         <p> <b>Note:</b> clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
[52]785            an unsatisfiable Range request-header, since not all servers implement this request-header.
[563]786         </p> 
787      </div>
[52]788      <div id="rfc.iref.i.1"></div>
789      <div id="rfc.iref.h.3"></div>
[424]790      <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>
791      <p id="rfc.section.5.3.p.1">If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its
[52]792         cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.)
793         However, if the condition fails because the entity has been modified, the client would then have to make a second request
794         to obtain the entire current entity-body.
795      </p>
[424]796      <p id="rfc.section.5.3.p.2">The request header "If-Range" allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity
[363]797         is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity'.
[52]798      </p>
[425]799      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.if-range" class="smpl">If-Range</a>   = "If-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a>
[363]800  <a href="#header.if-range" class="smpl">If-Range-v</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
[424]801</pre><p id="rfc.section.5.3.p.4">If the client has no entity tag for an entity, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header. (The server can distinguish between a valid HTTP-date and any form of entity-tag by examining
[52]802         no more than two characters.) The If-Range header <em class="bcp14">SHOULD</em> only be used together with a Range header, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header, or if the server does not support the sub-range operation.
803      </p>
[619]804      <p id="rfc.section.5.3.p.5">If the entity tag given in the If-Range header matches the current cache validator for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial Content) response. If the cache validator does not match,
805         then the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response.
[52]806      </p>
807      <div id="rfc.iref.r.1"></div>
808      <div id="rfc.iref.h.4"></div>
[424]809      <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>
810      <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a>&nbsp;<a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h3>
811      <p id="rfc.section.5.4.1.p.1">Since all HTTP entities are represented in HTTP messages as sequences of bytes, the concept of a byte range is meaningful
[52]812         for any HTTP entity. (However, not all clients and servers need to support byte-range operations.)
813      </p>
[424]814      <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the entity-body (not necessarily the same as the message-body).</p>
[229]815      <div id="rule.ranges-specifier">
[564]816         <p id="rfc.section.5.4.1.p.3">                A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single entity.
[229]817         </p>
818      </div>
[425]819      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
[334]820  <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> )
[434]821  <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> ]
[425]822  <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
823  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
[424]824</pre><p id="rfc.section.5.4.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value
[576]825         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
826         at zero.
[52]827      </p>
[424]828      <p id="rfc.section.5.4.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The
[52]829         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.
830      </p>
[424]831      <p id="rfc.section.5.4.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the entity-body, last-byte-pos
[52]832         is taken to be equal to one less than the current length of the entity-body in bytes.
833      </p>
[424]834      <p id="rfc.section.5.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the entity.</p>
[425]835      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
836  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
[576]837</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the suffix-length value. (That
838         is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
839         entire entity-body is used.
[52]840      </p>
[424]841      <p id="rfc.section.5.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current
[52]842         length of the entity-body, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is
843         satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> return a response with a status of 416 (Requested range not satisfiable). Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a status of 206 (Partial Content) containing the satisfiable ranges of the entity-body.
844      </p>
[424]845      <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
[52]846      <ul>
[565]847         <li>The first 500 bytes (byte offsets 0-499, inclusive):
848            <div id="rfc.figure.u.17"></div><pre class="text">  bytes=0-499
849</pre> </li>
850         <li>The second 500 bytes (byte offsets 500-999, inclusive):
851            <div id="rfc.figure.u.18"></div><pre class="text">  bytes=500-999
852</pre> </li>
853         <li>The final 500 bytes (byte offsets 9500-9999, inclusive):
854            <div id="rfc.figure.u.19"></div><pre class="text">  bytes=-500
855</pre> Or: <div id="rfc.figure.u.20"></div><pre class="text">  bytes=9500-
856</pre> </li>
857         <li>The first and last bytes only (bytes 0 and 9999):
858            <div id="rfc.figure.u.21"></div><pre class="text">  bytes=0-0,-1
859</pre> </li>
860         <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive):
861            <div id="rfc.figure.u.22"></div><pre class="text">  bytes=500-600,601-999
862  bytes=500-700,601-999
863</pre> </li>
[52]864      </ul>
[424]865      <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;<a id="range.retrieval.requests" href="#range.retrieval.requests">Range Retrieval Requests</a></h3>
866      <p id="rfc.section.5.4.2.p.1">HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies
[52]867         to the entity returned as the result of the request:
868      </p>
[565]869      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a>   = "Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
[434]870  <a href="#range.retrieval.requests" class="smpl">Range-v</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a>
[564]871          / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
[643]872  <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>
873  <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#notation" class="smpl">CHAR</a>
[424]874</pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when possible,
[52]875         since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
876         entities.
877      </p>
[424]878      <p id="rfc.section.5.4.2.p.4">If the server supports the Range header and the specified range or ranges are appropriate for the entity: </p>
[52]879      <ul>
880         <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
881            words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
882         </li>
883         <li>The presence of a Range header in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match, or
884            one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
885            is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
886         </li>
887      </ul>
[424]888      <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (see <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>) in addition to the Range header.
[52]889      </p>
[424]890      <p id="rfc.section.5.4.2.p.6">If a proxy that supports ranges receives a Range request, forwards the request to an inbound server, and receives an entire
[52]891         entity in reply, it <em class="bcp14">SHOULD</em> only return the requested range to its client. It <em class="bcp14">SHOULD</em> store the entire received response in its cache if that is consistent with its cache allocation policies.
892      </p>
[424]893      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
894      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>
895      <p id="rfc.section.6.1.p.1">The Message Header Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
[203]896      </p>
[290]897      <div id="rfc.table.1">
898         <div id="iana.header.registration.table"></div>
[675]899         <table class="tt full left" cellpadding="3" cellspacing="0">
[253]900            <thead>
901               <tr>
902                  <th>Header Field Name</th>
903                  <th>Protocol</th>
904                  <th>Status</th>
905                  <th>Reference</th>
906               </tr>
907            </thead>
908            <tbody>
909               <tr>
910                  <td>Accept-Ranges</td>
911                  <td>http</td>
912                  <td>standard</td>
[424]913                  <td> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a> 
[253]914                  </td>
915               </tr>
916               <tr>
917                  <td>Content-Range</td>
918                  <td>http</td>
919                  <td>standard</td>
[424]920                  <td> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a> 
[253]921                  </td>
922               </tr>
923               <tr>
924                  <td>If-Range</td>
925                  <td>http</td>
926                  <td>standard</td>
[424]927                  <td> <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section&nbsp;5.3</a> 
[253]928                  </td>
929               </tr>
930               <tr>
931                  <td>Range</td>
932                  <td>http</td>
933                  <td>standard</td>
[424]934                  <td> <a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a> 
[253]935                  </td>
936               </tr>
937            </tbody>
938         </table>
939      </div>
[424]940      <p id="rfc.section.6.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
941      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
[425]942      <p id="rfc.section.7.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
[52]943      </p>
[424]944      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
945      <p id="rfc.section.8.p.1">Most of the specification of ranges is based on work originally done by Ari Luotonen and John Franks, with additional input
[159]946         from Steve Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin Hamilton, Koen Holtman, Shel Kaplan, Paul Leach,
947         Alex Lopez-Ortiz, Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Rizzo, and Bill Weihl.
[52]948      </p>
[424]949      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
[52]950      </h1>
[424]951      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
[119]952      </h2>
[425]953      <table summary="Normative References">             
[52]954         <tr>
955            <td class="reference"><b id="Part1">[Part1]</b></td>
[689]956            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), September&nbsp;2009.
[52]957            </td>
958         </tr>
959         <tr>
[138]960            <td class="reference"><b id="Part3">[Part3]</b></td>
[689]961            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-latest (work in progress), September&nbsp;2009.
[138]962            </td>
963         </tr>
964         <tr>
[52]965            <td class="reference"><b id="Part4">[Part4]</b></td>
[689]966            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), September&nbsp;2009.
[52]967            </td>
968         </tr>
969         <tr>
[138]970            <td class="reference"><b id="Part6">[Part6]</b></td>
[689]971            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a>Nottingham, M., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), September&nbsp;2009.
[138]972            </td>
973         </tr>
974         <tr>
[131]975            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
976            <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a 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.
977            </td>
978         </tr>
979         <tr>
[96]980            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
981            <td class="top"><a 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.
982            </td>
983         </tr>
[425]984         <tr>
985            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
986            <td class="top"><a title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a 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.
987            </td>
988         </tr>
[119]989      </table>
[424]990      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
[119]991      </h2>
[253]992      <table summary="Informative References">     
[96]993         <tr>
[52]994            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
[119]995            <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a 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.
[52]996            </td>
997         </tr>
[196]998         <tr>
[253]999            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1000            <td class="top"><a title="Nine by Nine">Klyne, G.</a>, <a title="BEA Systems">Nottingham, M.</a>, and <a 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.
1001            </td>
1002         </tr>
1003         <tr>
[196]1004            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
1005            <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>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.
1006            </td>
1007         </tr>
[52]1008      </table>
[662]1009      <div class="avoidbreak">
1010         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1011         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
1012               (editor)
1013               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a><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>
1014         <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
1015         <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">JeffMogul@acm.org</span></a></span></address>
1016         <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">henrikn@microsoft.com</span></a></span></address>
1017         <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</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><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address>
1018         <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a><span class="email">paulle@microsoft.com</span></a></span></address>
1019         <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address>
1020         <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
1021               (editor)
1022               <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><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>
1023         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
1024               (editor)
1025               <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 tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a><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>
1026      </div>
[52]1027      <div id="rfc.iref.m.1"></div>
1028      <div id="rfc.iref.m.2"></div>
[662]1029      <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>
[52]1030      <p id="rfc.section.A.p.1">When an HTTP 206 (Partial Content) response message includes the content of multiple ranges (a response to a request for multiple
[328]1031         non-overlapping ranges), these are transmitted as a multipart message-body (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="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="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
[52]1032      </p>
[648]1033      <div class="note"> 
1034         <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
1035         </p> 
1036      </div>
1037      <p id="rfc.section.A.p.3">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
[52]1038         required boundary parameter specifies the boundary string used to separate each body-part.
1039      </p>
[648]1040      <p id="rfc.section.A.p.4"> </p>
[52]1041      <dl>
[196]1042         <dt>Type name:</dt>
[52]1043         <dd>multipart</dd>
[196]1044         <dt>Subtype name:</dt>
[52]1045         <dd>byteranges</dd>
1046         <dt>Required parameters:</dt>
1047         <dd>boundary</dd>
1048         <dt>Optional parameters:</dt>
1049         <dd>none</dd>
1050         <dt>Encoding considerations:</dt>
1051         <dd>only "7bit", "8bit", or "binary" are permitted</dd>
1052         <dt>Security considerations:</dt>
1053         <dd>none</dd>
[196]1054         <dt>Interoperability considerations:</dt>
1055         <dd>none</dd>
1056         <dt>Published specification:</dt>
1057         <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
1058         </dd>
1059         <dt>Applications that use this media type:</dt>
1060         <dt>Additional information:</dt>
1061         <dd> 
1062            <dl>
1063               <dt>Magic number(s):</dt>
1064               <dd>none</dd>
1065               <dt>File extension(s):</dt>
1066               <dd>none</dd>
1067               <dt>Macintosh file type code(s):</dt>
1068               <dd>none</dd>
1069            </dl> 
1070         </dd>
1071         <dt>Person and email address to contact for further information:</dt>
1072         <dd>See Authors Section.</dd>
1073         <dt>Intended usage:</dt>
1074         <dd>COMMON</dd>
1075         <dt>Restrictions on usage:</dt>
1076         <dd>none</dd>
1077         <dt>Author/Change controller:</dt>
1078         <dd>IESG</dd>
[52]1079      </dl>
[565]1080      <div id="rfc.figure.u.24"></div>
[435]1081      <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
1082  Date: Wed, 15 Nov 1995 06:25:24 GMT
1083  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
1084  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1085 
1086  --THIS_STRING_SEPARATES
1087  Content-type: application/pdf
1088  Content-range: bytes 500-999/8000
1089 
1090  ...the first range...
1091  --THIS_STRING_SEPARATES
1092  Content-type: application/pdf
1093  Content-range: bytes 7000-7999/8000
1094 
1095  ...the second range
1096  --THIS_STRING_SEPARATES--
[648]1097</pre><div id="rfc.figure.u.25"></div>
1098      <p>Other example:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
1099  Date: Tue, 14 Nov 1995 06:25:24 GMT
1100  Last-Modified: Tue, 14 July 04:58:08 GMT
1101  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1102 
1103  --THIS_STRING_SEPARATES
1104  Content-type: video/example
1105  Content-range: exampleunit 1.2-4.3/25
1106 
1107  ...the first range...
1108  --THIS_STRING_SEPARATES
1109  Content-type: video/example
1110  Content-range: exampleunit 11.2-14.3/25
1111 
1112  ...the second range
1113  --THIS_STRING_SEPARATES--
1114</pre> <p id="rfc.section.A.p.7">Notes: </p>
[52]1115      <ol>
1116         <li>Additional CRLFs may precede the first boundary string in the entity.</li>
[196]1117         <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.
[52]1118         </li>
1119         <li>A number of browsers and servers were coded to an early draft of the byteranges specification to use a media type of multipart/x-byteranges<span id="rfc.iref.m.3"></span><span id="rfc.iref.m.4"></span>, which is almost, but not quite compatible with the version documented in HTTP/1.1.
1120         </li>
1121      </ol>
[99]1122      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
1123      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
[138]1124      <p id="rfc.section.B.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
1125         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
[425]1126         computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
[138]1127      </p>
1128      <p id="rfc.section.B.1.p.2">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving
[52]1129         a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length
[424]1130         of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">Section&nbsp;5.2</a>)
[52]1131      </p>
[138]1132      <p id="rfc.section.B.1.p.3">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send
[424]1133         needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">3.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">5.3</a>)
[52]1134      </p>
[138]1135      <p id="rfc.section.B.1.p.4">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document.
[52]1136         The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside
[424]1137         of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">3.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.7" title="Content-Range">5.2</a>)
[52]1138      </p>
[99]1139      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
[424]1140      <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
[105]1141      </p>
[332]1142      <p id="rfc.section.B.2.p.2">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
1143      </p>
[421]1144      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
[648]1145      <div id="rfc.figure.u.26"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
[427]1146<a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a> = acceptable-ranges
1147
1148<a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range:" OWS Content-Range-v
1149<a href="#header.content-range" class="smpl">Content-Range-v</a> = content-range-spec
1150
[678]1151<a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part1], Section 6.1&gt;
[427]1152
1153<a href="#header.if-range" class="smpl">If-Range</a> = "If-Range:" OWS If-Range-v
1154<a href="#header.if-range" class="smpl">If-Range-v</a> = entity-tag / HTTP-date
1155
1156<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
1157
[434]1158<a href="#range.retrieval.requests" class="smpl">Range</a> = "Range:" OWS Range-v
1159<a href="#range.retrieval.requests" class="smpl">Range-v</a> = byte-ranges-specifier / other-ranges-specifier
[427]1160
1161<a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = ( *( "," OWS ) range-unit *( OWS "," [ OWS
[421]1162 range-unit ] ) ) / "none"
[428]1163
[427]1164<a href="#header.content-range" class="smpl">byte-content-range-spec</a> = bytes-unit SP byte-range-resp-spec "/" (
[421]1165 instance-length / "*" )
[427]1166<a href="#header.content-range" class="smpl">byte-range-resp-spec</a> = ( first-byte-pos "-" last-byte-pos ) / "*"
1167<a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = ( *( "," OWS ) byte-range-spec ) / (
[421]1168 suffix-byte-range-spec *( OWS "," [ ( OWS byte-range-spec ) /
1169 suffix-byte-range-spec ] ) )
[427]1170<a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ]
1171<a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set
1172<a href="#range.units" class="smpl">bytes-unit</a> = "bytes"
1173
1174<a href="#header.content-range" class="smpl">content-range-spec</a> = byte-content-range-spec /
[421]1175 other-content-range-spec
[428]1176
[427]1177<a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in [Part4], Section 2&gt;
1178
1179<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT
1180
1181<a href="#header.content-range" class="smpl">instance-length</a> = 1*DIGIT
1182
1183<a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*DIGIT
1184
1185<a href="#header.content-range" class="smpl">other-content-range-spec</a> = other-range-unit SP other-range-resp-spec
1186<a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *CHAR
[647]1187<a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*CHAR
[427]1188<a href="#range.units" class="smpl">other-range-unit</a> = token
[647]1189<a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = other-range-unit "=" other-range-set
[427]1190
1191<a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit
1192
1193<a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" suffix-length
1194<a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT
1195
1196<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
[648]1197</pre> <div id="rfc.figure.u.27"></div>
[454]1198      <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used
[421]1199; Content-Range defined but not used
1200; If-Range defined but not used
1201; Range defined but not used
[454]1202</pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
[421]1203      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
[115]1204      </h2>
[421]1205      <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
[115]1206      </p>
[421]1207      <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
[115]1208      </h2>
[421]1209      <p id="rfc.section.D.2.p.1">Closed issues: </p>
[116]1210      <ul>
[324]1211         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/18">http://tools.ietf.org/wg/httpbis/trac/ticket/18</a>&gt;: "Cache validators in 206 responses" (&lt;<a href="http://purl.org/NET/http-errata#ifrange206">http://purl.org/NET/http-errata#ifrange206</a>&gt;)
[116]1212         </li>
[324]1213         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
[152]1214         </li>
[324]1215         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/86">http://tools.ietf.org/wg/httpbis/trac/ticket/86</a>&gt;: "Normative up-to-date references"
[131]1216         </li>
[116]1217      </ul>
[421]1218      <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
[170]1219      </h2>
[421]1220      <p id="rfc.section.D.3.p.1">Closed issues: </p>
[200]1221      <ul>
[324]1222         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/55">http://tools.ietf.org/wg/httpbis/trac/ticket/55</a>&gt;: "Updating to RFC4288"
[200]1223         </li>
1224      </ul>
[421]1225      <p id="rfc.section.D.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
[205]1226      </p>
1227      <ul>
1228         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1229      </ul>
[421]1230      <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></h2>
1231      <p id="rfc.section.D.4.p.1">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
[253]1232      </p>
1233      <ul>
1234         <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
1235      </ul>
[421]1236      <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></h2>
1237      <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></h2>
1238      <p id="rfc.section.D.6.p.1">Closed issues: </p>
[332]1239      <ul>
1240         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/133">http://tools.ietf.org/wg/httpbis/trac/ticket/133</a>&gt;: "multipart/byteranges minimum number of parts"
1241         </li>
1242      </ul>
[421]1243      <p id="rfc.section.D.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
[334]1244      </p>
1245      <ul>
1246         <li>Use "/" instead of "|" for alternatives.</li>
[363]1247         <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1248         <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
[334]1249      </ul>
[421]1250      <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></h2>
[438]1251      <p id="rfc.section.D.7.p.1">Closed issues: </p>
1252      <ul>
1253         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/142">http://tools.ietf.org/wg/httpbis/trac/ticket/142</a>&gt;: "State base for *-byte-pos and suffix-length"
1254         </li>
1255      </ul>
1256      <p id="rfc.section.D.7.p.2">Ongoing work on Custom Ranges (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>&gt;):
[399]1257      </p>
1258      <ul>
1259         <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li>
1260      </ul>
[543]1261      <p id="rfc.section.D.7.p.3">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
[421]1262      </p>
1263      <ul>
[424]1264         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
[421]1265      </ul>
[547]1266      <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></h2>
[576]1267      <p id="rfc.section.D.8.p.1">Closed issues: </p>
1268      <ul>
1269         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
1270         </li>
1271      </ul>
[604]1272      <h2 id="rfc.section.D.9"><a href="#rfc.section.D.9">D.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></h2>
[619]1273      <p id="rfc.section.D.9.p.1">Closed issues: </p>
1274      <ul>
1275         <li>Fixed discrepancy in the If-Range definition about allowed validators.</li>
[648]1276         <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/150">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/150</a>&gt;: "multipart/byteranges for custom range units"
1277         </li>
[643]1278         <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/151">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/151</a>&gt;: "range unit missing from other-ranges-specifier in Range header"
1279         </li>
[619]1280      </ul>
[52]1281      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1282      <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> 
1283      </p>
1284      <div class="print2col">
1285         <ul class="ind">
1286            <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind">
[424]1287                  <li class="indline1">206 Partial Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.3"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.2</a></li>
[52]1288               </ul>
1289            </li>
1290            <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind">
[424]1291                  <li class="indline1">416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.4"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li>
[52]1292               </ul>
1293            </li>
1294            <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
[424]1295                  <li class="indline1">Accept-Ranges header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">6.1</a></li>
[52]1296               </ul>
1297            </li>
1298            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
[424]1299                  <li class="indline1">Content-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">6.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li>
[52]1300               </ul>
1301            </li>
1302            <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
1303                  <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
1304                     <ul class="ind">
[424]1305                        <li class="indline1"><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>5.1</b></a></li>
1306                        <li class="indline1"><tt>Accept-Ranges-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>5.1</b></a></li>
1307                        <li class="indline1"><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>5.1</b></a></li>
1308                        <li class="indline1"><tt>byte-content-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>5.2</b></a></li>
1309                        <li class="indline1"><tt>byte-range-resp-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>5.2</b></a></li>
1310                        <li class="indline1"><tt>byte-range-set</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>5.4.1</b></a></li>
1311                        <li class="indline1"><tt>byte-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>5.4.1</b></a></li>
1312                        <li class="indline1"><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>5.4.1</b></a></li>
1313                        <li class="indline1"><tt>bytes-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>2</b></a></li>
1314                        <li class="indline1"><tt>Content-Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>5.2</b></a></li>
1315                        <li class="indline1"><tt>content-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>5.2</b></a></li>
1316                        <li class="indline1"><tt>Content-Range-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>5.2</b></a></li>
1317                        <li class="indline1"><tt>first-byte-pos</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>5.4.1</b></a></li>
1318                        <li class="indline1"><tt>If-Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>5.3</b></a></li>
1319                        <li class="indline1"><tt>If-Range-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>5.3</b></a></li>
1320                        <li class="indline1"><tt>instance-length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>5.2</b></a></li>
1321                        <li class="indline1"><tt>last-byte-pos</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>5.4.1</b></a></li>
1322                        <li class="indline1"><tt>other-range-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>2</b></a></li>
1323                        <li class="indline1"><tt>Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>5.4.2</b></a></li>
1324                        <li class="indline1"><tt>range-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>2</b></a></li>
1325                        <li class="indline1"><tt>ranges-specifier</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>5.4.1</b></a></li>
1326                        <li class="indline1"><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>5.4.1</b></a></li>
1327                        <li class="indline1"><tt>suffix-length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>5.4.1</b></a></li>
[52]1328                     </ul>
1329                  </li>
1330               </ul>
1331            </li>
1332            <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
1333                  <li class="indline1">Headers&nbsp;&nbsp;
1334                     <ul class="ind">
[424]1335                        <li class="indline1">Accept-Ranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">6.1</a></li>
1336                        <li class="indline1">Content-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">6.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li>
1337                        <li class="indline1">If-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">6.1</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li>
1338                        <li class="indline1">Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">2</a>, <a class="iref" href="#rfc.xref.header.range.3">3.1</a>, <a class="iref" href="#rfc.xref.header.range.4">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">6.1</a></li>
[52]1339                     </ul>
1340                  </li>
1341               </ul>
1342            </li>
1343            <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
[424]1344                  <li class="indline1">If-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">6.1</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li>
[52]1345               </ul>
1346            </li>
1347            <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">
1348                  <li class="indline1">Media Type&nbsp;&nbsp;
1349                     <ul class="ind">
1350                        <li class="indline1">multipart/byteranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.1"><b>A</b></a></li>
1351                        <li class="indline1">multipart/x-byteranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.4">A</a></li>
1352                     </ul>
1353                  </li>
1354                  <li class="indline1">multipart/byteranges Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>A</b></a></li>
1355                  <li class="indline1">multipart/x-byteranges Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3">A</a></li>
1356               </ul>
1357            </li>
1358            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
[425]1359                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.2</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.6">7</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.7">B.1</a><ul class="ind">
[424]1360                        <li class="indline1"><em>Section 1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">1.2</a></li>
[425]1361                        <li class="indline1"><em>Section 1.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a></li>
[678]1362                        <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li>
[52]1363                     </ul>
1364                  </li>
[424]1365                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#Part3"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part3.1">B.1</a></li>
1366                  <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.2">4</a>, <a class="iref" href="#Part4"><b>9.1</b></a><ul class="ind">
1367                        <li class="indline1"><em>Section 2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">1.2.2</a></li>
1368                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.2">4</a></li>
[205]1369                     </ul>
1370                  </li>
[424]1371                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#Part6"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part6.1">B.1</a></li>
[52]1372               </ul>
1373            </li>
1374            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
[424]1375                  <li class="indline1">Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">2</a>, <a class="iref" href="#rfc.xref.header.range.3">3.1</a>, <a class="iref" href="#rfc.xref.header.range.4">3.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">6.1</a></li>
1376                  <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a>, <a class="iref" href="#rfc.xref.RFC2046.2">A</a><ul class="ind">
[328]1377                        <li class="indline1"><em>Section 5.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2046.1">A</a></li>
1378                     </ul>
1379                  </li>
[424]1380                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>
1381                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li>
1382                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">6.1</a>, <a class="iref" href="#RFC3864"><b>9.2</b></a></li>
1383                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#RFC4288"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>
[543]1384                  <li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.2</a>, <a class="iref" href="#rfc.xref.RFC5234.2">1.2</a>, <a class="iref" href="#RFC5234"><b>9.1</b></a><ul class="ind">
1385                        <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.2">1.2</a></li>
[425]1386                     </ul>
1387                  </li>
[52]1388               </ul>
1389            </li>
1390            <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
1391                  <li class="indline1">Status Codes&nbsp;&nbsp;
1392                     <ul class="ind">
[424]1393                        <li class="indline1">206 Partial Content&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.2</a></li>
1394                        <li class="indline1">416 Requested Range Not Satisfiable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li>
[52]1395                     </ul>
1396                  </li>
1397               </ul>
1398            </li>
1399         </ul>
1400      </div>
1401   </body>
1402</html>
Note: See TracBrowser for help on using the repository browser.