source: draft-ietf-httpbis/00/p5-range.html @ 308

Last change on this file since 308 was 230, checked in by julian.reschke@…, 13 years ago

Update to xml2rfc 1.33 (only affects Makefiles), update to latest version of rfc2629.xslt, change Makefile to allow Saxon to keep line numbers from source files.

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 65.2 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://www.w3.org/2006/03/hcard">
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}
32dd {
33  margin-right: 2em;
34}
35dl {
36  margin-left: 2em;
37}
38
39dl.empty dd {
40  margin-top: .5em;
41}
42dl p {
43  margin-left: 0em;
44}
45dt {
46  margin-top: .5em;
47}
48h1 {
49  font-size: 14pt;
50  line-height: 21pt;
51  page-break-after: avoid;
52}
53h1.np {
54  page-break-before: always;
55}
56h1 a {
57  color: #333333;
58}
59h2 {
60  font-size: 12pt;
61  line-height: 15pt;
62  page-break-after: avoid;
63}
64h2 a {
65  color: black;
66}
67h3 {
68  font-size: 10pt;
69  page-break-after: avoid;
70}
71h3 a {
72  color: black;
73}
74h4 {
75  font-size: 10pt;
76  page-break-after: avoid;
77}
78h4 a {
79  color: black;
80}
81h5 {
82  font-size: 10pt;
83  page-break-after: avoid;
84}
85h5 a {
86  color: black;
87}
88img {
89  margin-left: 3em;
90}
91li {
92  margin-left: 2em;
93  margin-right: 2em;
94}
95ol {
96  margin-left: 2em;
97  margin-right: 2em;
98}
99ol p {
100  margin-left: 0em;
101}
102p {
103  margin-left: 2em;
104  margin-right: 2em;
105}
106pre {
107  margin-left: 3em;
108  background-color: lightyellow;
109  padding: .25em;
110}
111pre.text2 {
112  border-style: dotted;
113  border-width: 1px;
114  background-color: #f0f0f0;
115  width: 69em;
116}
117pre.inline {
118  background-color: white;
119  padding: 0em;
120}
121pre.text {
122  border-style: dotted;
123  border-width: 1px;
124  background-color: #f8f8f8;
125  width: 69em;
126}
127pre.drawing {
128  border-style: solid;
129  border-width: 1px;
130  background-color: #f8f8f8;
131  padding: 2em;
132}
133table {
134  margin-left: 2em;
135}
136table.header {
137  width: 95%;
138  font-size: 10pt;
139  color: white;
140}
141td.top {
142  vertical-align: top;
143}
144td.topnowrap {
145  vertical-align: top;
146  white-space: nowrap;
147}
148td.header {
149  background-color: gray;
150  width: 50%;
151}
152td.header a {
153  color: white;
154}
155td.reference {
156  vertical-align: top;
157  white-space: nowrap;
158  padding-right: 1em;
159}
160thead {
161  display:table-header-group;
162}
163ul.toc {
164  list-style: none;
165  margin-left: 1.5em;
166  margin-right: 0em;
167  padding-left: 0em;
168}
169li.tocline0 {
170  line-height: 150%;
171  font-weight: bold;
172  font-size: 10pt;
173  margin-left: 0em;
174  margin-right: 0em;
175}
176li.tocline1 {
177  line-height: normal;
178  font-weight: normal;
179  font-size: 9pt;
180  margin-left: 0em;
181  margin-right: 0em;
182}
183li.tocline2 {
184  font-size: 0pt;
185}
186ul p {
187  margin-left: 0em;
188}
189ul.ind {
190  list-style: none;
191  margin-left: 1.5em;
192  margin-right: 0em;
193  padding-left: 0em;
194}
195li.indline0 {
196  font-weight: bold;
197  line-height: 200%;
198  margin-left: 0em;
199  margin-right: 0em;
200}
201li.indline1 {
202  font-weight: normal;
203  line-height: 150%;
204  margin-left: 0em;
205  margin-right: 0em;
206}
207.bcp14 {
208  font-style: normal;
209  text-transform: lowercase;
210  font-variant: small-caps;
211}
212.comment {
213  background-color: yellow;
214}
215.center {
216  text-align: center;
217}
218.error {
219  color: red;
220  font-style: italic;
221  font-weight: bold;
222}
223.figure {
224  font-weight: bold;
225  text-align: center;
226  font-size: 9pt;
227}
228.filename {
229  color: #333333;
230  font-weight: bold;
231  font-size: 12pt;
232  line-height: 21pt;
233  text-align: center;
234}
235.fn {
236  font-weight: bold;
237}
238.hidden {
239  display: none;
240}
241.left {
242  text-align: left;
243}
244.right {
245  text-align: right;
246}
247.title {
248  color: #990000;
249  font-size: 18pt;
250  line-height: 18pt;
251  font-weight: bold;
252  text-align: center;
253  margin-top: 36pt;
254}
255.vcardline {
256  display: block;
257}
258.warning {
259  font-size: 14pt;
260  background-color: yellow;
261}
262
263
264@media print {
265  .noprint {
266    display: none;
267  }
268 
269  a {
270    color: black;
271    text-decoration: none;
272  }
273
274  table.header {
275    width: 90%;
276  }
277
278  td.header {
279    width: 50%;
280    color: black;
281    background-color: white;
282    vertical-align: top;
283    font-size: 12pt;
284  }
285
286  ul.toc a::after {
287    content: leader('.') target-counter(attr(href), page);
288  }
289 
290  a.iref {
291    content: target-counter(attr(href), page);
292  }
293 
294  .print2col {
295    column-count: 2;
296    -moz-column-count: 2;
297    column-fill: auto;
298  }
299}
300
301@page {
302  @top-left {
303       content: "INTERNET DRAFT";
304  }
305  @top-right {
306       content: "December 2007";
307  }
308  @top-center {
309       content: "HTTP/1.1";
310  }
311  @bottom-left {
312       content: "Fielding, et al.";
313  }
314  @bottom-center {
315       content: "Standards Track";
316  }
317  @bottom-right {
318       content: "[Page " counter(page) "]";
319  }
320}
321
322@page:first {
323    @top-left {
324      content: normal;
325    }
326    @top-right {
327      content: normal;
328    }
329    @top-center {
330      content: normal;
331    }
332}
333</style><link rel="Contents" href="#rfc.toc">
334      <link rel="Author" href="#rfc.authors">
335      <link rel="Copyright" href="#rfc.copyright">
336      <link rel="Index" href="#rfc.index">
337      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
338      <link rel="Chapter" title="2 Range Units" href="#rfc.section.2">
339      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
340      <link rel="Chapter" title="4 Combining Byte Ranges" href="#rfc.section.4">
341      <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5">
342      <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6">
343      <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7">
344      <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8">
345      <link rel="Chapter" href="#rfc.section.9" title="9 References">
346      <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
347      <link rel="Appendix" title="B Changes from RFC 2068" href="#rfc.section.B">
348      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.365, 2008-03-07 07:17:25, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
349      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
350      <meta name="DC.Creator" content="Fielding, R.">
351      <meta name="DC.Creator" content="Gettys, J.">
352      <meta name="DC.Creator" content="Mogul, J.">
353      <meta name="DC.Creator" content="Frystyk, H.">
354      <meta name="DC.Creator" content="Masinter, L.">
355      <meta name="DC.Creator" content="Leach, P.">
356      <meta name="DC.Creator" content="Berners-Lee, T.">
357      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-00">
358      <meta name="DC.Date.Issued" scheme="ISO8601" content="2007-12">
359      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068">
360      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
361      <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.">
362   </head>
363   <body>
364      <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
365         <tr>
366            <td class="header left">Network Working Group</td>
367            <td class="header right">R. Fielding, Editor</td>
368         </tr>
369         <tr>
370            <td class="header left">Internet Draft</td>
371            <td class="header right">Day Software</td>
372         </tr>
373         <tr>
374            <td class="header left">
375               &lt;draft-ietf-httpbis-p5-range-00&gt;
376               
377            </td>
378            <td class="header right">J. Gettys</td>
379         </tr>
380         <tr>
381            <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>,
382               <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
383            </td>
384            <td class="header right">One Laptop per Child</td>
385         </tr>
386         <tr>
387            <td class="header left">Intended status: Standards Track</td>
388            <td class="header right">J. Mogul</td>
389         </tr>
390         <tr>
391            <td class="header left">Expires: June 2008</td>
392            <td class="header right">HP</td>
393         </tr>
394         <tr>
395            <td class="header left"></td>
396            <td class="header right">H. Frystyk</td>
397         </tr>
398         <tr>
399            <td class="header left"></td>
400            <td class="header right">Microsoft</td>
401         </tr>
402         <tr>
403            <td class="header left"></td>
404            <td class="header right">L. Masinter</td>
405         </tr>
406         <tr>
407            <td class="header left"></td>
408            <td class="header right">Adobe Systems</td>
409         </tr>
410         <tr>
411            <td class="header left"></td>
412            <td class="header right">P. Leach</td>
413         </tr>
414         <tr>
415            <td class="header left"></td>
416            <td class="header right">Microsoft</td>
417         </tr>
418         <tr>
419            <td class="header left"></td>
420            <td class="header right">T. Berners-Lee</td>
421         </tr>
422         <tr>
423            <td class="header left"></td>
424            <td class="header right">W3C/MIT</td>
425         </tr>
426         <tr>
427            <td class="header left"></td>
428            <td class="header right">December 20, 2007</td>
429         </tr>
430      </table>
431      <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-00</span></p>
432      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
433      <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
434         is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
435         6 of BCP 79.
436      </p>
437      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
438         that other groups may also distribute working documents as Internet-Drafts.
439      </p>
440      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
441         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
442         in progress”.
443      </p>
444      <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;.
445      </p>
446      <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;.
447      </p>
448      <p>This Internet-Draft will expire in June 2008.</p>
449      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
450      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
451         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the
452         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
453         5 defines range-specific requests and the rules for constructing and combining responses to those requests.
454      </p>
455      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
456      <p>This version of the HTTP specification contains only minimal editorial changes from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a> (abstract, introductory paragraph, and authors' addresses). All other changes are due to partitioning the original into seven
457         mostly independent parts. The intent is for readers of future drafts to able to use draft 00 as the basis for comparison when
458         the WG makes later changes to the specification text. This draft will shortly be followed by draft 01 (containing the first
459         round of changes that have already been agreed to on the mailing list). There is no point in reviewing this draft other than
460         to verify that the partitioning has been done correctly. Roy T. Fielding, Yves Lafon, and Julian Reschke will be the editors
461         after draft 00 is submitted.
462      </p> 
463      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
464         list is at &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/report/11">http://www3.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/">http://www3.tools.ietf.org/wg/httpbis/</a>&gt;.
465      </p>
466      <hr class="noprint">
467      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
468      <ul class="toc">
469         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
470         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
471         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul class="toc">
472               <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
473               <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
474            </ul>
475         </li>
476         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Byte Ranges</a></li>
477         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
478               <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
479               <li class="tocline1">5.2&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
480               <li class="tocline1">5.3&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
481               <li class="tocline1">5.4&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul class="toc">
482                     <li class="tocline1">5.4.1&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
483                     <li class="tocline1">5.4.2&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
484                  </ul>
485               </li>
486            </ul>
487         </li>
488         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
489         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
490         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
491         <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
492         <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
493         <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
494         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
495         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
496         <li class="tocline0"><a href="#rfc.index">Index</a></li>
497      </ul>
498      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
499      <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to range requests, partial responses, and the multipart/byteranges media
500         type. Right now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">[RFC2616]</cite> without edit.
501      </p>
502      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
503      <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
504         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.
505      </p>
506      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>   range-unit       = bytes-unit | other-range-unit
507   bytes-unit       = "bytes"
508   other-range-unit = token
509</pre><p id="rfc.section.2.p.3">The only range unit defined by HTTP/1.1 is "bytes". HTTP/1.1 implementations <em class="bcp14">MAY</em> ignore ranges specified using other units.
510      </p>
511      <p id="rfc.section.2.p.4">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges.</p>
512      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
513      </h1>
514      <div id="rfc.iref.3"></div>
515      <div id="rfc.iref.s.1"></div>
516      <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>
517      <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.2" 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.
518      </p>
519      <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
520      </p>
521      <ul>
522         <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
523            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.
524         </li>
525         <li>Date</li>
526         <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
527         <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
528            variant
529         </li>
530      </ul>
531      <p id="rfc.section.3.1.p.3">If the 206 response is the result of an If-Range request that used a strong cache validator (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.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>), the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response <em class="bcp14">MUST NOT</em> include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the
532         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.
533      </p>
534      <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 Byte Ranges">4</a>.
535      </p>
536      <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) responses.
537      </p>
538      <div id="rfc.iref.4"></div>
539      <div id="rfc.iref.s.2"></div>
540      <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>
541      <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.3" title="Range">Section&nbsp;5.4</a>), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request
542         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
543         values were greater than the current length of the selected resource.)
544      </p>
545      <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.
546      </p>
547      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Byte Ranges</a></h1>
548      <p id="rfc.section.4.p.1">A response might transfer only a subrange of the bytes of an entity-body, either because the request included one or more
549         Range specifications, or because a connection was broken prematurely. After several such transfers, a cache might have received
550         several ranges of the same entity-body.
551      </p>
552      <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
553         cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met:
554      </p>
555      <ul>
556         <li>Both the incoming response and the cache entry have a cache validator.</li>
557         <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>).
558         </li>
559      </ul>
560      <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
561         response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information.
562      </p>
563      <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>
564      <p id="rfc.section.5.p.1">This section defines the syntax and semantics of all standard HTTP/1.1 header fields. For entity-header fields, both sender
565         and recipient refer to either the client or the server, depending on who sends and who receives the entity.
566      </p>
567      <div id="rfc.iref.a.1"></div>
568      <div id="rfc.iref.h.1"></div>
569      <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>
570      <p id="rfc.section.5.1.p.1">The Accept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource:</p>
571      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>       Accept-Ranges     = "Accept-Ranges" ":" acceptable-ranges
572       acceptable-ranges = 1#range-unit | "none"
573</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
574      </p>
575      <div id="rfc.figure.u.3"></div><pre class="text">       Accept-Ranges: bytes
576</pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate byte-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>.
577      </p>
578      <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
579      </p>
580      <div id="rfc.figure.u.4"></div><pre class="text">       Accept-Ranges: none
581</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
582      <div id="rfc.iref.c.1"></div>
583      <div id="rfc.iref.h.2"></div>
584      <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>
585      <p id="rfc.section.5.2.p.1">The Content-Range entity-header is sent with a partial entity-body to specify where in the full entity-body the partial body
586         should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
587      </p>
588      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>    Content-Range = "Content-Range" ":" content-range-spec
589
590    content-range-spec      = byte-content-range-spec
591    byte-content-range-spec = bytes-unit SP
592                              byte-range-resp-spec "/"
593                              ( instance-length | "*" )
594
595    byte-range-resp-spec = (first-byte-pos "-" last-byte-pos)
596                                   | "*"
597    instance-length           = 1*DIGIT
598</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 "*"
599         character means that the instance-length is unknown at the time when the response was generated.
600      </p>
601      <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.
602      </p>
603      <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
604         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.
605      </p>
606      <p id="rfc.section.5.2.p.6">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
607         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 "*".
608      </p>
609      <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>
610      <ul>
611         <li>The first 500 bytes:
612            <div id="rfc.figure.u.6"></div><pre class="text">   bytes 0-499/1234
613</pre> </li>
614         <li>The second 500 bytes:
615            <div id="rfc.figure.u.7"></div><pre class="text">   bytes 500-999/1234
616</pre> </li>
617         <li>All except for the first 500 bytes:
618            <div id="rfc.figure.u.8"></div><pre class="text">   bytes 500-1233/1234
619</pre> </li>
620         <li>The last 500 bytes:
621            <div id="rfc.figure.u.9"></div><pre class="text">   bytes 734-1233/1234
622</pre> </li>
623      </ul>
624      <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
625         a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and
626         a Content-Length header showing the number of bytes actually transferred. For example,
627      </p>
628      <div id="rfc.figure.u.10"></div><pre class="text">    HTTP/1.1 206 Partial content
629    Date: Wed, 15 Nov 1995 06:25:24 GMT
630    Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
631    Content-Range: bytes 21010-47021/47022
632    Content-Length: 26012
633    Content-Type: image/gif
634</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
635         ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges"
636         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</a> for a compatibility issue.
637      </p>
638      <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 byte-ranges in a single request.
639      </p>
640      <p id="rfc.section.5.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
641      </p>
642      <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
643         the full entity).
644      </p>
645      <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
646         field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
647         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>).
648      </p>
649      <dl class="empty">
650         <dd> <b>Note:</b> clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
651            an unsatisfiable Range request-header, since not all servers implement this request-header.
652         </dd>
653      </dl>
654      <div id="rfc.iref.i.1"></div>
655      <div id="rfc.iref.h.3"></div>
656      <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>
657      <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
658         cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.)
659         However, if the condition fails because the entity has been modified, the client would then have to make a second request
660         to obtain the entire current entity-body.
661      </p>
662      <p id="rfc.section.5.3.p.2">The If-Range header allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity is unchanged,
663         send me the part(s) that I am missing; otherwise, send me the entire new entity'.
664      </p>
665      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.11"></span>     If-Range = "If-Range" ":" ( entity-tag | HTTP-date )
666</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
667         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.
668      </p>
669      <p id="rfc.section.5.3.p.5">If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial content) response. If the entity tag does not match, then
670         the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response.
671      </p>
672      <div id="rfc.iref.r.1"></div>
673      <div id="rfc.iref.h.4"></div>
674      <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>
675      <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>
676      <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
677         for any HTTP entity. (However, not all clients and servers need to support byte-range operations.)
678      </p>
679      <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>
680      <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.
681      </p>
682      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>    ranges-specifier = byte-ranges-specifier
683    byte-ranges-specifier = bytes-unit "=" byte-range-set
684    byte-range-set  = 1#( byte-range-spec | suffix-byte-range-spec )
685    byte-range-spec = first-byte-pos "-" [last-byte-pos]
686    first-byte-pos  = 1*DIGIT
687    last-byte-pos   = 1*DIGIT
688</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
689         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
690         at zero.
691      </p>
692      <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
693         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.
694      </p>
695      <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
696         is taken to be equal to one less than the current length of the entity-body in bytes.
697      </p>
698      <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>
699      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>    suffix-byte-range-spec = "-" suffix-length
700    suffix-length = 1*DIGIT
701</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
702         is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
703         entire entity-body is used.
704      </p>
705      <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
706         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
707         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.
708      </p>
709      <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p>
710      <ul>
711         <li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li>
712         <li>The second 500 bytes (byte offsets 500-999, inclusive): bytes=500-999</li>
713         <li>The final 500 bytes (byte offsets 9500-9999, inclusive): bytes=-500</li>
714         <li>Or bytes=9500-</li>
715         <li>The first and last bytes only (bytes 0 and 9999): bytes=0-0,-1</li>
716         <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): <br> bytes=500-600,601-999<br> bytes=500-700,601-999
717         </li>
718      </ul>
719      <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>
720      <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
721         to the entity returned as the result of the request:
722      </p>
723      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.20"></span>   Range = "Range" ":" ranges-specifier
724</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,
725         since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
726         entities.
727      </p>
728      <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>
729      <ul>
730         <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other
731            words, the response carries a status code of 206 (Partial Content) instead of 200 (OK).
732         </li>
733         <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
734            one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition
735            is true. It does not affect the 304 (Not Modified) response returned if the conditional is false.
736         </li>
737      </ul>
738      <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.
739      </p>
740      <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
741         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.
742      </p>
743      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
744      <p id="rfc.section.6.p.1">TBD.</p>
745      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
746      <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.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
747      </p>
748      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
749      <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
750         from Steve Zilles.
751      </p>
752      <p id="rfc.section.8.p.2">Based on an XML translation of RFC 2616 by Julian Reschke.</p>
753      <h1 id="rfc.references"><a href="#rfc.section.9" id="rfc.section.9">9.</a> References
754      </h1>
755      <table summary="References">       
756         <tr>
757            <td class="reference"><b id="Part1">[Part1]</b></td>
758            <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>, and <a title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-00">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-00 (work in progress), December&nbsp;2007.
759            </td>
760         </tr>
761         <tr>
762            <td class="reference"><b id="Part4">[Part4]</b></td>
763            <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>, and <a title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-00">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-00 (work in progress), December&nbsp;2007.
764            </td>
765         </tr>
766         <tr>
767            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
768            <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.
769            </td>
770         </tr>
771         <tr>
772            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
773            <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.
774            </td>
775         </tr>
776      </table>
777      <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
778      <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
779            (editor)
780            <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>
781      <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>
782      <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>
783      <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>
784      <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>
785      <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>
786      <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>
787      <div id="rfc.iref.m.1"></div>
788      <div id="rfc.iref.m.2"></div>
789      <h1 id="rfc.section.A"><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>
790      <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
791         non-overlapping ranges), these are transmitted as a multipart message-body. The media type for this purpose is called "multipart/byteranges".
792      </p>
793      <p id="rfc.section.A.p.2">The multipart/byteranges media type includes two or more parts, each with its own Content-Type and Content-Range fields. The
794         required boundary parameter specifies the boundary string used to separate each body-part.
795      </p>
796      <p id="rfc.section.A.p.3"> </p>
797      <dl>
798         <dt>Media Type name:</dt>
799         <dd>multipart</dd>
800         <dt>Media subtype name:</dt>
801         <dd>byteranges</dd>
802         <dt>Required parameters:</dt>
803         <dd>boundary</dd>
804         <dt>Optional parameters:</dt>
805         <dd>none</dd>
806         <dt>Encoding considerations:</dt>
807         <dd>only "7bit", "8bit", or "binary" are permitted</dd>
808         <dt>Security considerations:</dt>
809         <dd>none</dd>
810      </dl>
811      <div id="rfc.figure.u.15"></div>
812      <p>For example:</p><pre class="text">   HTTP/1.1 206 Partial Content
813   Date: Wed, 15 Nov 1995 06:25:24 GMT
814   Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
815   Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
816
817   --THIS_STRING_SEPARATES
818   Content-type: application/pdf
819   Content-range: bytes 500-999/8000
820
821   ...the first range...
822   --THIS_STRING_SEPARATES
823   Content-type: application/pdf
824   Content-range: bytes 7000-7999/8000
825
826   ...the second range
827   --THIS_STRING_SEPARATES--
828</pre><p id="rfc.section.A.p.5">Notes: </p>
829      <ol>
830         <li>Additional CRLFs may precede the first boundary string in the entity.</li>
831         <li>Although RFC 2046 <a href="#RFC2046" id="rfc.xref.RFC2046.1"><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.
832         </li>
833         <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.
834         </li>
835      </ol>
836      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h1>
837      <p id="rfc.section.B.p.1">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving
838         a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length
839         of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>)
840      </p>
841      <p id="rfc.section.B.p.2">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send
842         needed headers in a 206 response, this problem can be avoided.
843      </p>
844      <p id="rfc.section.B.p.3">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document.
845         The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside
846         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.5" title="Content-Range">5.2</a>)
847      </p>
848      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
849      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
850         authors retain all their rights.
851      </p>
852      <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
853         HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
854         DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
855         WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
856      </p>
857      <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
858      <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
859         be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
860         license under such rights might or might not be available; nor does it represent that it has made any independent effort to
861         identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
862         BCP 79.
863      </p>
864      <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
865         of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
866         of this specification can be obtained from the IETF on-line IPR repository at &lt;<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>&gt;.
867      </p>
868      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
869         rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
870         at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
871      </p>
872      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
873      <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>
874      </p>
875      <div class="print2col">
876         <ul class="ind">
877            <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind">
878                  <li class="indline1">206 Partial Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.3"><b>3.1</b></a></li>
879               </ul>
880            </li>
881            <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind">
882                  <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</a></li>
883               </ul>
884            </li>
885            <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
886                  <li class="indline1">Accept-Ranges header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>5.1</b></a></li>
887               </ul>
888            </li>
889            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
890                  <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">B</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B</a></li>
891               </ul>
892            </li>
893            <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
894                  <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
895                     <ul class="ind">
896                        <li class="indline1"><tt>Accept-Ranges</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>5.1</b></a></li>
897                        <li class="indline1"><tt>acceptable-ranges</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>5.1</b></a></li>
898                        <li class="indline1"><tt>byte-content-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>5.2</b></a></li>
899                        <li class="indline1"><tt>byte-range-resp-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>5.2</b></a></li>
900                        <li class="indline1"><tt>byte-range-set</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>5.4.1</b></a></li>
901                        <li class="indline1"><tt>byte-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>5.4.1</b></a></li>
902                        <li class="indline1"><tt>byte-ranges-specifier</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>5.4.1</b></a></li>
903                        <li class="indline1"><tt>bytes-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>2</b></a></li>
904                        <li class="indline1"><tt>Content-Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>5.2</b></a></li>
905                        <li class="indline1"><tt>content-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>5.2</b></a></li>
906                        <li class="indline1"><tt>first-byte-pos</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>5.4.1</b></a></li>
907                        <li class="indline1"><tt>If-Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>5.3</b></a></li>
908                        <li class="indline1"><tt>instance-length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>5.2</b></a></li>
909                        <li class="indline1"><tt>last-byte-pos</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>5.4.1</b></a></li>
910                        <li class="indline1"><tt>other-range-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>2</b></a></li>
911                        <li class="indline1"><tt>Range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>5.4.2</b></a></li>
912                        <li class="indline1"><tt>range-unit</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>2</b></a></li>
913                        <li class="indline1"><tt>ranges-specifier</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>5.4.1</b></a></li>
914                        <li class="indline1"><tt>suffix-byte-range-spec</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>5.4.1</b></a></li>
915                        <li class="indline1"><tt>suffix-length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>5.4.1</b></a></li>
916                     </ul>
917                  </li>
918               </ul>
919            </li>
920            <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
921                  <li class="indline1">Headers&nbsp;&nbsp;
922                     <ul class="ind">
923                        <li class="indline1">Accept-Ranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a></li>
924                        <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">B</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B</a></li>
925                        <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></li>
926                        <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">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a></li>
927                     </ul>
928                  </li>
929               </ul>
930            </li>
931            <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
932                  <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></li>
933               </ul>
934            </li>
935            <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">
936                  <li class="indline1">Media Type&nbsp;&nbsp;
937                     <ul class="ind">
938                        <li class="indline1">multipart/byteranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.1"><b>A</b></a></li>
939                        <li class="indline1">multipart/x-byteranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.4">A</a></li>
940                     </ul>
941                  </li>
942                  <li class="indline1">multipart/byteranges Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.2"><b>A</b></a></li>
943                  <li class="indline1">multipart/x-byteranges Media Type&nbsp;&nbsp;<a class="iref" href="#rfc.iref.m.3">A</a></li>
944               </ul>
945            </li>
946            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
947                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">7</a>, <a class="iref" href="#Part1"><b>9</b></a></li>
948                  <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">3.1</a>, <a class="iref" href="#rfc.xref.Part4.2">4</a>, <a class="iref" href="#Part4"><b>9</b></a><ul class="ind">
949                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">3.1</a>, <a class="iref" href="#rfc.xref.Part4.2">4</a></li>
950                     </ul>
951                  </li>
952               </ul>
953            </li>
954            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
955                  <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">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>5.4</b></a></li>
956                  <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#RFC2046"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a></li>
957                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>9</b></a></li>
958               </ul>
959            </li>
960            <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
961                  <li class="indline1">Status Codes&nbsp;&nbsp;
962                     <ul class="ind">
963                        <li class="indline1">206 Partial Content&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a></li>
964                        <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</a></li>
965                     </ul>
966                  </li>
967               </ul>
968            </li>
969         </ul>
970      </div>
971   </body>
972</html>
Note: See TracBrowser for help on using the repository browser.