source: draft-ietf-httpbis/latest/p5-range.xml @ 334

Last change on this file since 334 was 334, checked in by julian.reschke@…, 11 years ago

use "/" instead of "|" for alternatives (related to #36)

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