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

Last change on this file since 1539 was 1524, checked in by julian.reschke@…, 8 years ago

remove unneeded status code descriptions (resolves #336)

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 72.4 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 "February">
16  <!ENTITY ID-YEAR "2012">
17  <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
18  <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
19  <!ENTITY abnf-extension             "<xref target='Part1' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY acks                       "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY whitespace                 "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY field-components           "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY http-date                  "<xref target='Part2' x:rel='#http.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
24  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
25  <!ENTITY entity-tags                "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26  <!ENTITY weak-and-strong-validators "<xref target='Part4' x:rel='#weak.and.strong.validators' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
27  <!ENTITY lastmod-comparison         "<xref target='Part4' x:rel='#lastmod.comparison' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
28  <!ENTITY p6-heuristic               "<xref target='Part6' x:rel='#heuristic.freshness' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
29]>
30<?rfc toc="yes" ?>
31<?rfc symrefs="yes" ?>
32<?rfc sortrefs="yes" ?>
33<?rfc compact="yes"?>
34<?rfc subcompact="no" ?>
35<?rfc linkmailto="no" ?>
36<?rfc editing="no" ?>
37<?rfc comments="yes"?>
38<?rfc inline="yes"?>
39<?rfc rfcedstyle="yes"?>
40<?rfc-ext allow-markup-in-artwork="yes" ?>
41<?rfc-ext include-references-in-index="yes" ?>
42<rfc obsoletes="2616" category="std" x:maturity-level="proposed"
43     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p5-range-&ID-VERSION;"
44     xmlns:x='http://purl.org/net/xml2rfc/ext'>
45<x:link rel="prev" basename="p4-conditional"/>
46<x:link rel="next" basename="p6-cache"/>
47<x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/>
48<front>
49
50  <title abbrev="HTTP/1.1, Part 5">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
51
52  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
53    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
54    <address>
55      <postal>
56        <street>345 Park Ave</street>
57        <city>San Jose</city>
58        <region>CA</region>
59        <code>95110</code>
60        <country>USA</country>
61      </postal>
62      <email>fielding@gbiv.com</email>
63      <uri>http://roy.gbiv.com/</uri>
64    </address>
65  </author>
66
67  <author initials="J." surname="Gettys" fullname="Jim Gettys">
68    <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
69    <address>
70      <postal>
71        <street>21 Oak Knoll Road</street>
72        <city>Carlisle</city>
73        <region>MA</region>
74        <code>01741</code>
75        <country>USA</country>
76      </postal>
77      <email>jg@freedesktop.org</email>
78      <uri>http://gettys.wordpress.com/</uri>
79    </address>
80  </author>
81 
82  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
83    <organization abbrev="HP">Hewlett-Packard Company</organization>
84    <address>
85      <postal>
86        <street>HP Labs, Large Scale Systems Group</street>
87        <street>1501 Page Mill Road, MS 1177</street>
88        <city>Palo Alto</city>
89        <region>CA</region>
90        <code>94304</code>
91        <country>USA</country>
92      </postal>
93      <email>JeffMogul@acm.org</email>
94    </address>
95  </author>
96
97  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
98    <organization abbrev="Microsoft">Microsoft Corporation</organization>
99    <address>
100      <postal>
101        <street>1 Microsoft Way</street>
102        <city>Redmond</city>
103        <region>WA</region>
104        <code>98052</code>
105        <country>USA</country>
106      </postal>
107      <email>henrikn@microsoft.com</email>
108    </address>
109  </author>
110
111  <author initials="L." surname="Masinter" fullname="Larry Masinter">
112    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
113    <address>
114      <postal>
115        <street>345 Park Ave</street>
116        <city>San Jose</city>
117        <region>CA</region>
118        <code>95110</code>
119        <country>USA</country>
120      </postal>
121      <email>LMM@acm.org</email>
122      <uri>http://larry.masinter.net/</uri>
123    </address>
124  </author>
125 
126  <author initials="P." surname="Leach" fullname="Paul J. Leach">
127    <organization abbrev="Microsoft">Microsoft Corporation</organization>
128    <address>
129      <postal>
130        <street>1 Microsoft Way</street>
131        <city>Redmond</city>
132        <region>WA</region>
133        <code>98052</code>
134      </postal>
135      <email>paulle@microsoft.com</email>
136    </address>
137  </author>
138   
139  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
140    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
141    <address>
142      <postal>
143        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
144        <street>The Stata Center, Building 32</street>
145        <street>32 Vassar Street</street>
146        <city>Cambridge</city>
147        <region>MA</region>
148        <code>02139</code>
149        <country>USA</country>
150      </postal>
151      <email>timbl@w3.org</email>
152      <uri>http://www.w3.org/People/Berners-Lee/</uri>
153    </address>
154  </author>
155
156  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
157    <organization abbrev="W3C">World Wide Web Consortium</organization>
158    <address>
159      <postal>
160        <street>W3C / ERCIM</street>
161        <street>2004, rte des Lucioles</street>
162        <city>Sophia-Antipolis</city>
163        <region>AM</region>
164        <code>06902</code>
165        <country>France</country>
166      </postal>
167      <email>ylafon@w3.org</email>
168      <uri>http://www.raubacapeu.net/people/yves/</uri>
169    </address>
170  </author>
171
172  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
173    <organization abbrev="greenbytes">greenbytes GmbH</organization>
174    <address>
175      <postal>
176        <street>Hafenweg 16</street>
177        <city>Muenster</city><region>NW</region><code>48155</code>
178        <country>Germany</country>
179      </postal>
180      <phone>+49 251 2807760</phone>
181      <facsimile>+49 251 2807761</facsimile>
182      <email>julian.reschke@greenbytes.de</email>
183      <uri>http://greenbytes.de/tech/webdav/</uri>
184    </address>
185  </author>
186
187  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
188  <workgroup>HTTPbis Working Group</workgroup>
189
190<abstract>
191<t>
192   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
193   distributed, collaborative, hypertext information systems. HTTP has been in
194   use by the World Wide Web global information initiative since 1990. This
195   document is Part 5 of the seven-part specification that defines the protocol
196   referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
197</t>
198<t>
199   Part 5 defines range-specific requests and the rules for constructing and
200   combining responses to those requests.
201</t>
202</abstract>
203
204<note title="Editorial Note (To be removed by RFC Editor)">
205  <t>
206    Discussion of this draft should take place on the HTTPBIS working group
207    mailing list (ietf-http-wg@w3.org), which is archived at
208    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
209  </t>
210  <t>
211    The current issues list is at
212    <eref target="http://tools.ietf.org/wg/httpbis/trac/report/3"/> and related
213    documents (including fancy diffs) can be found at
214    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
215  </t>
216  <t>
217    The changes in this draft are summarized in <xref target="changes.since.18"/>.
218  </t>
219</note>
220</front>
221<middle>
222<section title="Introduction" anchor="introduction">
223<t>
224   HTTP clients often encounter interrupted data transfers as a result
225   of cancelled requests or dropped connections.  When a client has stored
226   a partial representation, it is desirable to request the remainder
227   of that representation in a subsequent request rather than transfer
228   the entire representation.
229   There are also a number of Web applications that benefit from being
230   able to request only a subset of a larger representation, such as a
231   single page of a very large document or only part of an image to be
232   rendered by a device with limited local storage.
233</t>
234<t>
235   This document defines HTTP/1.1 range requests,
236   partial responses, and the multipart/byteranges media type.
237   The protocol for range requests is an &OPTIONAL; feature of HTTP,
238   designed so resources or recipients that do not implement this feature
239   can respond as if it is a normal GET request without impacting
240   interoperability.  Partial responses are indicated by a distinct status
241   code to not be mistaken for full responses by intermediate caches
242   that might not implement the feature.
243</t>
244<t>
245   Although the HTTP range request mechanism is designed to allow for
246   extensible range types, this specification only defines requests for
247   byte ranges.
248</t>
249
250<section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
251<t>
252   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
253   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
254   document are to be interpreted as described in <xref target="RFC2119"/>.
255</t>
256<t>
257   This document defines conformance criteria for several roles in HTTP
258   communication, including Senders, Recipients, Clients, Servers, User-Agents,
259   Origin Servers, Intermediaries, Proxies and Gateways. See &architecture;
260   for definitions of these terms.
261</t>
262<t>
263   An implementation is considered conformant if it complies with all of the
264   requirements associated with its role(s). Note that SHOULD-level requirements
265   are relevant here, unless one of the documented exceptions is applicable.
266</t>
267<t>
268   This document also uses ABNF to define valid protocol elements
269   (<xref target="notation"/>). In addition to the prose requirements placed
270   upon them, Senders &MUST-NOT; generate protocol elements that are invalid.
271</t>
272<t>
273   Unless noted otherwise, Recipients &MAY; take steps to recover a usable
274   protocol element from an invalid construct. However, HTTP does not define
275   specific error handling mechanisms, except in cases where it has direct
276   impact on security. This is because different uses of the protocol require
277   different error handling strategies; for example, a Web browser may wish to
278   transparently recover from a response where the Location header field
279   doesn't parse according to the ABNF, whereby in a systems control protocol
280   using HTTP, this type of error recovery could lead to dangerous consequences.
281</t>
282</section>
283
284<section title="Syntax Notation" anchor="notation">
285  <x:anchor-alias value="ALPHA"/>
286  <x:anchor-alias value="CHAR"/>
287  <x:anchor-alias value="CR"/>
288  <x:anchor-alias value="DIGIT"/>
289  <x:anchor-alias value="LF"/>
290  <x:anchor-alias value="OCTET"/>
291  <x:anchor-alias value="SP"/>
292  <x:anchor-alias value="VCHAR"/>
293<t>
294   This specification uses the Augmented Backus-Naur Form (ABNF) notation
295   of <xref target="RFC5234"/> with the list rule extension defined in
296   &notation;<xref target="collected.abnf"/> shows the collected ABNF
297   with the list rule expanded.
298</t>
299<t>
300  The following core rules are included by
301  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
302  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
303  DIGIT (decimal 0-9), DQUOTE (double quote),
304  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
305  OCTET (any 8-bit sequence of data), SP (space), and
306  VCHAR (any visible US-ASCII character).
307</t>
308
309<t>
310  Note that all rules derived from <x:ref>token</x:ref> are to
311  be compared case-insensitively, like <x:ref>range-unit</x:ref> and
312  <x:ref>acceptable-ranges</x:ref>.
313</t>
314
315<section title="Core Rules" anchor="core.rules">
316  <x:anchor-alias value="token"/>
317  <x:anchor-alias value="OWS"/>
318  <x:anchor-alias value="HTTP-date"/>
319<t>
320  The core rules below are defined in <xref target="Part1"/> and
321  <xref target="Part2"/>:
322</t>
323<figure><artwork type="abnf2616">
324  <x:ref>OWS</x:ref>        = &lt;OWS, defined in &whitespace;&gt;
325  <x:ref>token</x:ref>      = &lt;token, defined in &field-components;&gt;
326  <x:ref>HTTP-date</x:ref>  = &lt;HTTP-date, defined in &http-date;&gt;
327</artwork></figure>
328</section>
329
330<section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
331  <x:anchor-alias value="entity-tag"/>
332<t>
333  The ABNF rules below are defined in other parts:
334</t>
335<figure><!--Part4--><artwork type="abnf2616">
336  <x:ref>entity-tag</x:ref> = &lt;entity-tag, defined in &entity-tags;&gt;
337</artwork></figure>
338</section>
339
340</section>
341
342</section>
343
344
345<section title="Range Units" anchor="range.units">
346  <x:anchor-alias value="bytes-unit"/>
347  <x:anchor-alias value="other-range-unit"/>
348  <x:anchor-alias value="range-unit"/>
349<t>
350   HTTP/1.1 allows a client to request that only part (a range) of the
351   representation be included within the response. HTTP/1.1 uses range
352   units in the Range (<xref target="header.range"/>) and Content-Range (<xref target="header.content-range"/>)
353   header fields. A representation can be broken down into subranges according
354   to various structural units.
355</t>
356<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"/>
357  <x:ref>range-unit</x:ref>       = <x:ref>bytes-unit</x:ref> / <x:ref>other-range-unit</x:ref>
358  <x:ref>bytes-unit</x:ref>       = "bytes"
359  <x:ref>other-range-unit</x:ref> = <x:ref>token</x:ref>
360</artwork></figure>
361<t>
362  HTTP/1.1 has been designed to allow implementations of applications
363  that do not depend on knowledge of ranges. The only range unit defined
364  by HTTP/1.1 is "bytes". Additional specifiers can be defined as described
365  in <xref target="range.specifier.registry"/>.
366</t>
367<t>
368  If a range unit is not understood in a request, a server &MUST; ignore
369  the whole Range header field (<xref target="header.range"/>).
370  If a range unit is not understood in a response, an intermediary
371  &SHOULD; pass the response to the client; a client &MUST; fail.
372</t>
373
374<section title="Range Specifier Registry" anchor="range.specifier.registry">
375<t>
376   The HTTP Range Specifier Registry defines the name space for the range
377   specifier names.
378</t>
379<t>
380   Registrations &MUST; include the following fields:
381   <list style="symbols">
382     <t>Name</t>
383     <t>Description</t>
384     <t>Pointer to specification text</t>
385   </list>
386</t>
387<t>
388  Values to be added to this name space are subject to IETF review
389  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
390</t>
391<t>
392   The registry itself is maintained at
393   <eref target="http://www.iana.org/assignments/http-range-specifiers"/>.
394</t>
395</section>
396
397</section>
398
399<section title="Status Code Definitions" anchor="status.code.definitions">
400<section title="206 Partial Content" anchor="status.206">
401  <iref primary="true" item="206 Partial Content (status code)" x:for-anchor=""/>
402  <iref primary="true" item="Status Codes" subitem="206 Partial Content" x:for-anchor=""/>
403<t>
404   The server has fulfilled the partial GET request for the resource.
405   The request &MUST; have included a Range header field (<xref target="header.range"/>)
406   indicating the desired range, and &MAY; have included an If-Range
407   header field (<xref target="header.if-range"/>) to make the request conditional.
408</t>
409<t>
410   The response &MUST; include the following header fields:
411  <list style="symbols">
412    <t>
413        Either a Content-Range header field (<xref target="header.content-range"/>) indicating
414        the range included with this response, or a multipart/byteranges
415        Content-Type including Content-Range fields for each part. If a
416        Content-Length header field is present in the response, its
417        value &MUST; match the actual number of octets transmitted in the
418        message-body.
419    </t>
420    <t>
421        Date
422    </t>
423    <t>
424        Cache-Control, ETag, Expires, Content-Location, Last-Modified,
425        and/or Vary, if the header field would have been sent in a 200
426        response to the same request
427    </t>
428  </list>
429</t>
430<t>
431   If the 206 response is the result of an If-Range request, the response
432   &SHOULD-NOT; include other representation header fields. Otherwise, the response
433   &MUST; include all of the representation header fields that would have been returned
434   with a 200 (OK) response to the same request.
435</t>
436<t>
437   Caches &MAY; use a heuristic (see &p6-heuristic;) to determine
438   freshness for 206 responses.
439</t>
440</section>
441
442<section title="416 Requested Range Not Satisfiable" anchor="status.416">
443  <iref primary="true" item="416 Requested Range Not Satisfiable (status code)" x:for-anchor=""/>
444  <iref primary="true" item="Status Codes" subitem="416 Requested Range Not Satisfiable" x:for-anchor=""/>
445<t>
446   A server &SHOULD; return a response with this status code if a request
447   included a Range header field (<xref target="header.range"/>), and none of
448   the ranges-specifier values in this field overlap the current extent
449   of the selected resource, and the request did not include an If-Range
450   header field (<xref target="header.if-range"/>). (For byte-ranges,
451   this means that the first-byte-pos of all of the byte-range-spec values were
452   greater than the current length of the selected resource.)
453</t>
454<t>
455   When this status code is returned for a byte-range request, the
456   response &SHOULD; include a Content-Range header field
457   specifying the current length of the representation (see <xref target="header.content-range"/>).
458   This response &MUST-NOT; use the multipart/byteranges content-type.
459</t>
460</section>
461</section>
462
463<section title="Combining Ranges" anchor="combining.byte.ranges">
464<t>
465   A response might transfer only a subrange of a representation if the
466   connection closed prematurely or if the request used one or more Range
467   specifications.  After several such transfers, a client might have
468   received several ranges of the same representation.  These ranges can only
469   be safely combined if they all have in common the same strong validator,
470   where "strong validator" is defined to be either an entity-tag that is
471   not marked as weak (&entity-tags;) or, if no entity-tag is provided, a
472   Last-Modified value that is strong in the sense defined by
473   &lastmod-comparison;.
474</t>
475<t>
476   When a client receives an incomplete 200 (OK) or 206 (Partial Content)
477   response and already has one or more stored responses for the same method
478   and effective request URI, all of the stored responses with the same
479   strong validator &MAY; be combined with the partial content in this new
480   response.  If none of the stored responses contain the same strong
481   validator, then this new response corresponds to a new representation
482   and &MUST-NOT; be combined with the existing stored responses.
483</t>
484<t>
485   If the new response is an incomplete 200 (OK) response, then the header
486   fields of that new response are used for any combined response and replace
487   those of the matching stored responses.
488</t>
489<t>
490   If the new response is a 206 (Partial Content) response and at least one
491   of the matching stored responses is a 200 (OK), then the combined response
492   header fields consist of the most recent 200 response's header fields.
493   If all of the matching stored responses are 206 responses, then the
494   stored response with the most header fields is used as the source of
495   header fields for the combined response, except that the client &MUST;
496   use other header fields provided in the new response, aside from
497   Content-Range, to replace all instances of the corresponding header
498   fields in the stored response.
499</t>
500<t>
501   The combined response message-body consists of the union of partial
502   content ranges in the new response and each of the selected responses.
503   If the union consists of the entire range of the representation, then the
504   combined response &MUST; be recorded as a complete 200 (OK) response
505   with a Content-Length header field that reflects the complete length.
506   Otherwise, the combined response(s) &MUST; include a Content-Range
507   header field describing the included range(s) and be recorded as
508   incomplete.  If the union consists of a discontinuous range of the
509   representation, then the client &MAY; store it as either a multipart range
510   response or as multiple 206 responses with one continuous range each.
511</t>
512</section>
513
514<section title="Header Field Definitions" anchor="header.field.definitions">
515<t>
516   This section defines the syntax and semantics of HTTP/1.1 header fields
517   related to range requests and partial responses.
518</t>
519
520<section title="Accept-Ranges" anchor="header.accept-ranges">
521  <iref primary="true" item="Accept-Ranges header field" x:for-anchor=""/>
522  <iref primary="true" item="Header Fields" subitem="Accept-Ranges" x:for-anchor=""/>
523  <x:anchor-alias value="Accept-Ranges"/>
524  <x:anchor-alias value="acceptable-ranges"/>
525<t>
526   The "Accept-Ranges" header field allows a resource to indicate
527   its acceptance of range requests.
528</t>
529<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Ranges"/><iref primary="true" item="Grammar" subitem="acceptable-ranges"/>
530  <x:ref>Accept-Ranges</x:ref>     = <x:ref>acceptable-ranges</x:ref>
531  <x:ref>acceptable-ranges</x:ref> = 1#<x:ref>range-unit</x:ref> / "none"
532</artwork></figure>
533<t>
534      Origin servers that accept byte-range requests &MAY; send
535</t>
536<figure><artwork type="example">
537  Accept-Ranges: bytes
538</artwork></figure>
539<t>
540      but are not required to do so. Clients &MAY; generate range
541      requests without having received this header field for the resource
542      involved. Range units are defined in <xref target="range.units"/>.
543</t>
544<t>
545      Servers that do not accept any kind of range request for a
546      resource &MAY; send
547</t>
548<figure><artwork type="example">
549  Accept-Ranges: none
550</artwork></figure>
551<t>
552      to advise the client not to attempt a range request.
553</t>
554</section>
555
556<section title="Content-Range" anchor="header.content-range">
557  <iref primary="true" item="Content-Range header field" x:for-anchor=""/>
558  <iref primary="true" item="Header Fields" subitem="Content-Range" x:for-anchor=""/>
559  <x:anchor-alias value="byte-content-range-spec"/>
560  <x:anchor-alias value="byte-range-resp-spec"/>
561  <x:anchor-alias value="Content-Range"/>
562  <x:anchor-alias value="instance-length"/>
563  <x:anchor-alias value="other-content-range-spec"/>
564  <x:anchor-alias value="other-range-resp-spec"/>
565<t>
566   The "Content-Range" header field is sent with a partial representation to
567   specify where in the full representation the payload body is intended to be
568   applied.
569</t>
570<t>   
571   Range units are defined in <xref target="range.units"/>.
572</t>
573<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Range"/><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"/>
574  <x:ref>Content-Range</x:ref>           = <x:ref>byte-content-range-spec</x:ref>
575                          / <x:ref>other-content-range-spec</x:ref>
576                         
577  <x:ref>byte-content-range-spec</x:ref> = <x:ref>bytes-unit</x:ref> <x:ref>SP</x:ref>
578                            <x:ref>byte-range-resp-spec</x:ref> "/"
579                            ( <x:ref>instance-length</x:ref> / "*" )
580 
581  <x:ref>byte-range-resp-spec</x:ref>    = (<x:ref>first-byte-pos</x:ref> "-" <x:ref>last-byte-pos</x:ref>)
582                          / "*"
583                         
584  <x:ref>instance-length</x:ref>         = 1*<x:ref>DIGIT</x:ref>
585 
586  <x:ref>other-content-range-spec</x:ref> = <x:ref>other-range-unit</x:ref> <x:ref>SP</x:ref>
587                             <x:ref>other-range-resp-spec</x:ref>
588  <x:ref>other-range-resp-spec</x:ref>    = *<x:ref>CHAR</x:ref>
589</artwork></figure>
590<t>
591   The header field &SHOULD; indicate the total length of the full representation,
592   unless this length is unknown or difficult to determine. The asterisk
593   "*" character means that the instance-length is unknown at the time
594   when the response was generated.
595</t>
596<t>
597   Unlike byte-ranges-specifier values (see <xref target="byte.ranges"/>), a byte-range-resp-spec
598   &MUST; only specify one range, and &MUST; contain
599   absolute byte positions for both the first and last byte of the
600   range.
601</t>
602<t>
603   A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos
604   value is less than its first-byte-pos value, or whose
605   instance-length value is less than or equal to its last-byte-pos
606   value, is invalid. The recipient of an invalid byte-content-range-spec
607   &MUST; ignore it and any content transferred along with it.
608</t>
609<t>
610   In the case of a byte range request:
611   A server sending a response with status code 416 (Requested range not
612   satisfiable) &SHOULD; include a Content-Range field with a byte-range-resp-spec
613   of "*". The instance-length specifies the current length of
614   the selected resource. A response with status code 206 (Partial
615   Content) &MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*".
616</t>
617<t>
618  The "Content-Range" header field has no meaning for status codes that do not
619  explicitly describe its semantic. Currently, only status codes
620  206 (Partial Content) and 416 (Requested range not satisfiable) describe
621  the meaning of this header field.
622</t>
623<t>
624   Examples of byte-content-range-spec values, assuming that the representation
625   contains a total of 1234 bytes:
626   <list style="symbols">
627      <t>
628        The first 500 bytes:
629<figure><artwork type="example" x:indent-with="   ">
630  bytes 0-499/1234
631</artwork></figure>
632      </t>   
633      <t>
634        The second 500 bytes:
635<figure><artwork type="example" x:indent-with="   ">
636  bytes 500-999/1234
637</artwork></figure>
638      </t>   
639      <t>
640        All except for the first 500 bytes:
641<figure><artwork type="example" x:indent-with="   ">
642  bytes 500-1233/1234
643</artwork></figure>
644      </t>   
645      <t>
646        The last 500 bytes:
647<figure><artwork type="example" x:indent-with="   ">
648  bytes 734-1233/1234
649</artwork></figure>
650      </t>   
651   </list>
652</t>
653<t>
654   When an HTTP message includes the content of a single range (for
655   example, a response to a request for a single range, or to a request
656   for a set of ranges that overlap without any holes), this content is
657   transmitted with a Content-Range header field, and a Content-Length header
658   field showing the number of bytes actually transferred. For example,
659</t>
660<figure><artwork type="example">
661  HTTP/1.1 206 Partial Content
662  Date: Wed, 15 Nov 1995 06:25:24 GMT
663  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
664  Content-Range: bytes 21010-47021/47022
665  Content-Length: 26012
666  Content-Type: image/gif
667</artwork></figure>
668<t>
669   When an HTTP message includes the content of multiple ranges (for
670   example, a response to a request for multiple non-overlapping
671   ranges), these are transmitted as a multipart message. The multipart
672   media type used for this purpose is "multipart/byteranges" as defined
673   in <xref target="internet.media.type.multipart.byteranges"/>.
674</t>
675<t>
676   A response to a request for a single range &MUST-NOT; be sent using the
677   multipart/byteranges media type.  A response to a request for
678   multiple ranges, whose result is a single range, &MAY; be sent as a
679   multipart/byteranges media type with one part. A client that cannot
680   decode a multipart/byteranges message &MUST-NOT; ask for multiple
681   ranges in a single request.
682</t>
683<t>
684   When a client requests multiple ranges in one request, the
685   server &SHOULD; return them in the order that they appeared in the
686   request.
687</t>
688<t>
689   If the server ignores a byte-range-spec because it is syntactically
690   invalid, the server &SHOULD; treat the request as if the invalid Range
691   header field did not exist. (Normally, this means return a 200
692   response containing the full representation).
693</t>
694<t>
695   If the server receives a request (other than one including an If-Range
696   header field) with an unsatisfiable Range header
697   field (that is, all of whose byte-range-spec values have a
698   first-byte-pos value greater than the current length of the selected
699   resource), it &SHOULD; return a response code of 416 (Requested range
700   not satisfiable) (<xref target="status.416"/>).
701</t>
702<x:note>
703  <t>
704    <x:h>Note:</x:h> Clients cannot depend on servers to send a 416 (Requested
705    range not satisfiable) response instead of a 200 (OK) response for
706    an unsatisfiable Range header field, since not all servers
707    implement this header field.
708  </t>
709</x:note>
710</section>
711
712<section title="If-Range" anchor="header.if-range">
713  <iref primary="true" item="If-Range header field" x:for-anchor=""/>
714  <iref primary="true" item="Header Fields" subitem="If-Range" x:for-anchor=""/>
715  <x:anchor-alias value="If-Range"/>
716<t>
717   If a client has a partial copy of a representation and wishes
718   to have an up-to-date copy of the entire representation, it
719   could use the Range header field with a conditional GET (using
720   either or both of If-Unmodified-Since and If-Match.) However, if the
721   condition fails because the representation has been modified, the client
722   would then have to make a second request to obtain the entire current
723   representation.
724</t>
725<t>
726   The "If-Range" header field allows a client to "short-circuit" the second
727   request. Informally, its meaning is "if the representation is unchanged, send
728   me the part(s) that I am missing; otherwise, send me the entire new
729   representation".
730</t>
731<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Range"/>
732  <x:ref>If-Range</x:ref> = <x:ref>entity-tag</x:ref> / <x:ref>HTTP-date</x:ref>
733</artwork></figure>
734<t>
735   Clients &MUST-NOT; use an entity-tag marked as weak in an If-Range
736   field value and &MUST-NOT; use a Last-Modified date in an If-Range
737   field value unless it has no entity-tag for the representation and
738   the Last-Modified date it does have for the representation is strong
739   in the sense defined by &lastmod-comparison;.
740</t>
741<t>
742   A server that evaluates a conditional range request that is applicable
743   to one of its representations &MUST; evaluate the condition as false if
744   the entity-tag used as a validator is marked as weak or, when an HTTP-date
745   is used as the validator, if the date value is not strong in the sense
746   defined by &lastmod-comparison;. (A server can distinguish between a
747   valid HTTP-date and any form of entity-tag by examining the first
748   two characters.)
749</t>
750<t>
751   The If-Range header field &SHOULD; only be sent by clients together with
752   a Range header field.  The If-Range header field &MUST; be ignored if it
753   is received in a request that does not include a Range header field.
754   The If-Range header field &MUST; be ignored by a server that does not
755   support the sub-range operation.
756</t>
757<t>
758   If the validator given in the If-Range header field matches the current
759   validator for the selected representation of the target resource, then
760   the server &SHOULD; send the specified sub-range of the representation
761   using a 206 (Partial Content) response. If the validator does not match,
762   then the server &SHOULD; send the entire representation using a 200 (OK)
763   response.
764</t>
765</section>
766
767<section title="Range" anchor="header.range">
768  <iref primary="true" item="Range header field" x:for-anchor=""/>
769  <iref primary="true" item="Header Fields" subitem="Range" x:for-anchor=""/>
770
771<section title="Byte Ranges" anchor="byte.ranges">
772<t>
773   Since all HTTP representations are transferred as sequences
774   of bytes, the concept of a byte range is meaningful for any HTTP
775   representation. (However, not all clients and servers need to support byte-range
776   operations.)
777</t>
778<t>
779   Byte range specifications in HTTP apply to the sequence of bytes in
780   the representation body (not necessarily the same as the message-body).
781</t>
782<t anchor="rule.ranges-specifier">
783  <x:anchor-alias value="byte-range-set"/>
784  <x:anchor-alias value="byte-range-spec"/>
785  <x:anchor-alias value="byte-ranges-specifier"/>
786  <x:anchor-alias value="first-byte-pos"/>
787  <x:anchor-alias value="last-byte-pos"/>
788  <x:anchor-alias value="ranges-specifier"/>
789  <x:anchor-alias value="suffix-byte-range-spec"/>
790  <x:anchor-alias value="suffix-length"/>
791
792   A byte range operation &MAY; specify a single range of bytes, or a set
793   of ranges within a single representation.
794</t>
795<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"/>
796  <x:ref>byte-ranges-specifier</x:ref> = <x:ref>bytes-unit</x:ref> "=" <x:ref>byte-range-set</x:ref>
797  <x:ref>byte-range-set</x:ref>  = 1#( <x:ref>byte-range-spec</x:ref> / <x:ref>suffix-byte-range-spec</x:ref> )
798  <x:ref>byte-range-spec</x:ref> = <x:ref>first-byte-pos</x:ref> "-" [ <x:ref>last-byte-pos</x:ref> ]
799  <x:ref>first-byte-pos</x:ref>  = 1*<x:ref>DIGIT</x:ref>
800  <x:ref>last-byte-pos</x:ref>   = 1*<x:ref>DIGIT</x:ref>
801</artwork></figure>
802<t>
803   The first-byte-pos value in a byte-range-spec gives the byte-offset
804   of the first byte in a range. The last-byte-pos value gives the
805   byte-offset of the last byte in the range; that is, the byte
806   positions specified are inclusive. Byte offsets start at zero.
807</t>
808<t>
809   If the last-byte-pos value is present, it &MUST; be greater than or
810   equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec
811   is syntactically invalid. The recipient of a byte-range-set
812   that includes one or more syntactically invalid byte-range-spec
813   values &MUST; ignore the header field that includes that byte-range-set.
814</t>
815<t>
816   If the last-byte-pos value is absent, or if the value is greater than
817   or equal to the current length of the representation body, last-byte-pos is
818   taken to be equal to one less than the current length of the representation
819   in bytes.
820</t>
821<t>
822   By its choice of last-byte-pos, a client can limit the number of
823   bytes retrieved without knowing the size of the representation.
824</t>
825<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="suffix-byte-range-spec"/><iref primary="true" item="Grammar" subitem="suffix-length"/>
826  <x:ref>suffix-byte-range-spec</x:ref> = "-" <x:ref>suffix-length</x:ref>
827  <x:ref>suffix-length</x:ref> = 1*<x:ref>DIGIT</x:ref>
828</artwork></figure>
829<t>
830   A suffix-byte-range-spec is used to specify the suffix of the
831   representation body, of a length given by the suffix-length value. (That is,
832   this form specifies the last N bytes of a representation.) If the
833   representation is shorter than the specified suffix-length, the entire
834   representation is used.
835</t>
836<t>
837   If a syntactically valid byte-range-set includes at least one byte-range-spec
838   whose first-byte-pos is less than the current length of
839   the representation, or at least one suffix-byte-range-spec with a non-zero
840   suffix-length, then the byte-range-set is satisfiable.
841   Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set
842   is unsatisfiable, the server &SHOULD; return a response with a
843   416 (Requested range not satisfiable) status code. Otherwise, the server
844   &SHOULD; return a response with a 206 (Partial Content) status code
845   containing the satisfiable ranges of the representation.
846</t>
847<t>
848   Examples of byte-ranges-specifier values (assuming a representation of
849   length 10000):
850  <list style="symbols">
851     <t>The first 500 bytes (byte offsets 0-499, inclusive):
852<figure><artwork type="example" x:indent-with="   ">
853  bytes=0-499
854</artwork></figure>
855    </t>
856     <t>The second 500 bytes (byte offsets 500-999, inclusive):
857<figure><artwork type="example" x:indent-with="   ">
858  bytes=500-999
859</artwork></figure>
860    </t>
861     <t>The final 500 bytes (byte offsets 9500-9999, inclusive):
862<figure><artwork type="example" x:indent-with="   ">
863  bytes=-500
864</artwork></figure>
865    Or:
866<figure><artwork type="example" x:indent-with="   ">
867  bytes=9500-
868</artwork></figure>
869    </t>
870     <t>The first and last bytes only (bytes 0 and 9999):
871<figure><artwork type="example" x:indent-with="   ">
872  bytes=0-0,-1
873</artwork></figure>
874     </t>
875     <t>Several legal but not canonical specifications of the second 500
876        bytes (byte offsets 500-999, inclusive):
877<figure><artwork type="example" x:indent-with="   ">
878  bytes=500-600,601-999
879  bytes=500-700,601-999
880</artwork></figure>
881     </t>
882  </list>
883</t>
884</section>
885
886<section title="Range Retrieval Requests" anchor="range.retrieval.requests">
887  <x:anchor-alias value="Range"/>
888  <x:anchor-alias value="other-ranges-specifier"/>
889  <x:anchor-alias value="other-range-set"/>
890<t>
891   The "Range" header field defines the GET method (conditional or
892   not) to request one or more sub-ranges of the response representation body, instead
893   of the entire representation body.
894</t>
895<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Range"/>
896  <x:ref>Range</x:ref> = <x:ref>byte-ranges-specifier</x:ref> / <x:ref>other-ranges-specifier</x:ref>
897  <x:ref>other-ranges-specifier</x:ref> = <x:ref>other-range-unit</x:ref> "=" <x:ref>other-range-set</x:ref>
898  <x:ref>other-range-set</x:ref> = 1*<x:ref>CHAR</x:ref>
899</artwork></figure>
900<t>
901   A server &MAY; ignore the Range header field. However, origin
902   servers and intermediate caches ought to support byte ranges when
903   possible, since Range supports efficient recovery from partially
904   failed transfers, and supports efficient partial retrieval of large
905   representations.
906</t>
907<t>
908   If the server supports the Range header field and the specified range or
909   ranges are appropriate for the representation:
910  <list style="symbols">
911     <t>The presence of a Range header field in an unconditional GET modifies
912        what is returned if the GET is otherwise successful. In other
913        words, the response carries a status code of 206 (Partial
914        Content) instead of 200 (OK).</t>
915
916     <t>The presence of a Range header field in a conditional GET (a request
917        using one or both of If-Modified-Since and If-None-Match, or
918        one or both of If-Unmodified-Since and If-Match) modifies what
919        is returned if the GET is otherwise successful and the
920        condition is true. It does not affect the 304 (Not Modified)
921        response returned if the conditional is false.</t>
922  </list>
923</t>
924<t>
925   In some cases, it might be more appropriate to use the If-Range
926   header field (see <xref target="header.if-range"/>) in addition to the Range
927   header field.
928</t>
929<t>
930   If a proxy that supports ranges receives a Range request, forwards
931   the request to an inbound server, and receives an entire representation in
932   reply, it &MAY; only return the requested range to its client.
933</t>
934</section>
935</section>
936</section>
937
938<section title="IANA Considerations" anchor="IANA.considerations">
939
940<section title="Status Code Registration" anchor="status.code.registration">
941<t>
942   The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
943   shall be updated with the registrations below:
944</t>
945<?BEGININC p5-range.iana-status-codes ?>
946<!--AUTOGENERATED FROM extract-status-code-defs.xslt, do not edit manually-->
947<texttable align="left" suppress-title="true" anchor="iana.status.code.registration.table">
948   <ttcol>Value</ttcol>
949   <ttcol>Description</ttcol>
950   <ttcol>Reference</ttcol>
951   <c>206</c>
952   <c>Partial Content</c>
953   <c>
954      <xref target="status.206"/>
955   </c>
956   <c>416</c>
957   <c>Requested Range Not Satisfiable</c>
958   <c>
959      <xref target="status.416"/>
960   </c>
961</texttable>
962<!--(END)-->
963<?ENDINC p5-range.iana-status-codes ?>
964</section>
965
966<section title="Header Field Registration" anchor="header.field.registration">
967<t>
968   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
969   with the permanent registrations below (see <xref target="RFC3864"/>):
970</t>
971<?BEGININC p5-range.iana-headers ?>
972<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
973<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
974   <ttcol>Header Field Name</ttcol>
975   <ttcol>Protocol</ttcol>
976   <ttcol>Status</ttcol>
977   <ttcol>Reference</ttcol>
978
979   <c>Accept-Ranges</c>
980   <c>http</c>
981   <c>standard</c>
982   <c>
983      <xref target="header.accept-ranges"/>
984   </c>
985   <c>Content-Range</c>
986   <c>http</c>
987   <c>standard</c>
988   <c>
989      <xref target="header.content-range"/>
990   </c>
991   <c>If-Range</c>
992   <c>http</c>
993   <c>standard</c>
994   <c>
995      <xref target="header.if-range"/>
996   </c>
997   <c>Range</c>
998   <c>http</c>
999   <c>standard</c>
1000   <c>
1001      <xref target="header.range"/>
1002   </c>
1003</texttable>
1004<!--(END)-->
1005<?ENDINC p5-range.iana-headers ?>
1006<t>
1007   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
1008</t>
1009</section>
1010
1011<section title="Range Specifier Registration" anchor="range.specifier.registration">
1012<t>
1013  The registration procedure for HTTP Range Specifiers is defined by
1014  <xref target="range.specifier.registry"/> of this document.
1015</t>
1016<t>
1017   The HTTP Range Specifier Registry shall be created at <eref target="http://www.iana.org/assignments/http-range-specifiers"/>
1018   and be populated with the registrations below:
1019</t>
1020<texttable align="left" suppress-title="true" anchor="iana.range.specifiers.table">
1021   <ttcol>Range Specifier Name</ttcol>
1022   <ttcol>Description</ttcol>
1023   <ttcol>Reference</ttcol>
1024
1025   <c>bytes</c>
1026   <c>a range of octets</c>
1027   <c>(this specification)</c>
1028</texttable>
1029<t>
1030   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
1031</t>
1032</section>
1033</section>
1034
1035<section title="Security Considerations" anchor="security.considerations">
1036<t>
1037   This section is meant to inform application developers, information
1038   providers, and users of the security limitations in HTTP/1.1 as
1039   described by this document. The discussion does not include
1040   definitive solutions to the problems revealed, though it does make
1041   some suggestions for reducing security risks.
1042</t>
1043<section title="Overlapping Ranges" anchor="overlapping.ranges">
1044<t>
1045   Range requests containing overlapping ranges may lead to the situation
1046   where a server is sending far more data than the size of the complete
1047   resource representation.
1048</t>
1049</section>
1050</section>
1051
1052<section title="Acknowledgments" anchor="acks">
1053<t>
1054  See &acks;.
1055</t>
1056</section>
1057</middle>
1058<back>
1059
1060<references title="Normative References">
1061
1062<reference anchor="Part1">
1063  <front>
1064    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
1065    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1066      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1067      <address><email>fielding@gbiv.com</email></address>
1068    </author>
1069    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1070      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
1071      <address><email>jg@freedesktop.org</email></address>
1072    </author>
1073    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1074      <organization abbrev="HP">Hewlett-Packard Company</organization>
1075      <address><email>JeffMogul@acm.org</email></address>
1076    </author>
1077    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1078      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1079      <address><email>henrikn@microsoft.com</email></address>
1080    </author>
1081    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1082      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1083      <address><email>LMM@acm.org</email></address>
1084    </author>
1085    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1086      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1087      <address><email>paulle@microsoft.com</email></address>
1088    </author>
1089    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1090      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1091      <address><email>timbl@w3.org</email></address>
1092    </author>
1093    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1094      <organization abbrev="W3C">World Wide Web Consortium</organization>
1095      <address><email>ylafon@w3.org</email></address>
1096    </author>
1097    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1098      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1099      <address><email>julian.reschke@greenbytes.de</email></address>
1100    </author>
1101    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1102  </front>
1103  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
1104  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
1105</reference>
1106
1107<reference anchor="Part2">
1108  <front>
1109    <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
1110    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1111      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1112      <address><email>fielding@gbiv.com</email></address>
1113    </author>
1114    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1115      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
1116      <address><email>jg@freedesktop.org</email></address>
1117    </author>
1118    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1119      <organization abbrev="HP">Hewlett-Packard Company</organization>
1120      <address><email>JeffMogul@acm.org</email></address>
1121    </author>
1122    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1123      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1124      <address><email>henrikn@microsoft.com</email></address>
1125    </author>
1126    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1127      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1128      <address><email>LMM@acm.org</email></address>
1129    </author>
1130    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1131      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1132      <address><email>paulle@microsoft.com</email></address>
1133    </author>
1134    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1135      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1136      <address><email>timbl@w3.org</email></address>
1137    </author>
1138    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1139      <organization abbrev="W3C">World Wide Web Consortium</organization>
1140      <address><email>ylafon@w3.org</email></address>
1141    </author>
1142    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1143      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1144      <address><email>julian.reschke@greenbytes.de</email></address>
1145    </author>
1146    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1147  </front>
1148  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
1149  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
1150</reference>
1151
1152<reference anchor="Part4">
1153  <front>
1154    <title abbrev="HTTP/1.1">HTTP/1.1, part 4: Conditional Requests</title>
1155    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1156      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1157      <address><email>fielding@gbiv.com</email></address>
1158    </author>
1159    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1160      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
1161      <address><email>jg@freedesktop.org</email></address>
1162    </author>
1163    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1164      <organization abbrev="HP">Hewlett-Packard Company</organization>
1165      <address><email>JeffMogul@acm.org</email></address>
1166    </author>
1167    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1168      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1169      <address><email>henrikn@microsoft.com</email></address>
1170    </author>
1171    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1172      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1173      <address><email>LMM@acm.org</email></address>
1174    </author>
1175    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1176      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1177      <address><email>paulle@microsoft.com</email></address>
1178    </author>
1179    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1180      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1181      <address><email>timbl@w3.org</email></address>
1182    </author>
1183    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1184      <organization abbrev="W3C">World Wide Web Consortium</organization>
1185      <address><email>ylafon@w3.org</email></address>
1186    </author>
1187    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1188      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1189      <address><email>julian.reschke@greenbytes.de</email></address>
1190    </author>
1191    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1192  </front>
1193  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"/>
1194  <x:source href="p4-conditional.xml" basename="p4-conditional"/>
1195</reference>
1196
1197<reference anchor="Part6">
1198  <front>
1199    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
1200    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1201      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1202      <address><email>fielding@gbiv.com</email></address>
1203    </author>
1204    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1205      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
1206      <address><email>jg@freedesktop.org</email></address>
1207    </author>
1208    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1209      <organization abbrev="HP">Hewlett-Packard Company</organization>
1210      <address><email>JeffMogul@acm.org</email></address>
1211    </author>
1212    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1213      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1214      <address><email>henrikn@microsoft.com</email></address>
1215    </author>
1216    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1217      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1218      <address><email>LMM@acm.org</email></address>
1219    </author>
1220    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1221      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1222      <address><email>paulle@microsoft.com</email></address>
1223    </author>
1224    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1225      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1226      <address><email>timbl@w3.org</email></address>
1227    </author>
1228    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1229      <organization abbrev="W3C">World Wide Web Consortium</organization>
1230      <address><email>ylafon@w3.org</email></address>
1231    </author>
1232    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
1233      <organization>Rackspace</organization>
1234      <address><email>mnot@mnot.net</email></address>
1235    </author>
1236    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1237      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1238      <address><email>julian.reschke@greenbytes.de</email></address>
1239    </author>
1240    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1241  </front>
1242  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
1243  <x:source href="p6-cache.xml" basename="p6-cache"/>
1244</reference>
1245
1246<reference anchor="RFC2046">
1247  <front>
1248    <title abbrev="Media Types">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</title>
1249    <author initials="N." surname="Freed" fullname="Ned Freed">
1250      <organization>Innosoft International, Inc.</organization>
1251      <address><email>ned@innosoft.com</email></address>
1252    </author>
1253    <author initials="N." surname="Borenstein" fullname="Nathaniel S. Borenstein">
1254      <organization>First Virtual Holdings</organization>
1255      <address><email>nsb@nsb.fv.com</email></address>
1256    </author>
1257    <date month="November" year="1996"/>
1258  </front>
1259  <seriesInfo name="RFC" value="2046"/>
1260</reference>
1261
1262<reference anchor="RFC2119">
1263  <front>
1264    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
1265    <author initials="S." surname="Bradner" fullname="Scott Bradner">
1266      <organization>Harvard University</organization>
1267      <address><email>sob@harvard.edu</email></address>
1268    </author>
1269    <date month="March" year="1997"/>
1270  </front>
1271  <seriesInfo name="BCP" value="14"/>
1272  <seriesInfo name="RFC" value="2119"/>
1273</reference>
1274
1275<reference anchor="RFC5234">
1276  <front>
1277    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
1278    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
1279      <organization>Brandenburg InternetWorking</organization>
1280      <address>
1281        <email>dcrocker@bbiw.net</email>
1282      </address> 
1283    </author>
1284    <author initials="P." surname="Overell" fullname="Paul Overell">
1285      <organization>THUS plc.</organization>
1286      <address>
1287        <email>paul.overell@thus.net</email>
1288      </address>
1289    </author>
1290    <date month="January" year="2008"/>
1291  </front>
1292  <seriesInfo name="STD" value="68"/>
1293  <seriesInfo name="RFC" value="5234"/>
1294</reference>
1295
1296</references>
1297
1298<references title="Informative References">
1299
1300<reference anchor="RFC2616">
1301  <front>
1302    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
1303    <author initials="R." surname="Fielding" fullname="R. Fielding">
1304      <organization>University of California, Irvine</organization>
1305      <address><email>fielding@ics.uci.edu</email></address>
1306    </author>
1307    <author initials="J." surname="Gettys" fullname="J. Gettys">
1308      <organization>W3C</organization>
1309      <address><email>jg@w3.org</email></address>
1310    </author>
1311    <author initials="J." surname="Mogul" fullname="J. Mogul">
1312      <organization>Compaq Computer Corporation</organization>
1313      <address><email>mogul@wrl.dec.com</email></address>
1314    </author>
1315    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
1316      <organization>MIT Laboratory for Computer Science</organization>
1317      <address><email>frystyk@w3.org</email></address>
1318    </author>
1319    <author initials="L." surname="Masinter" fullname="L. Masinter">
1320      <organization>Xerox Corporation</organization>
1321      <address><email>masinter@parc.xerox.com</email></address>
1322    </author>
1323    <author initials="P." surname="Leach" fullname="P. Leach">
1324      <organization>Microsoft Corporation</organization>
1325      <address><email>paulle@microsoft.com</email></address>
1326    </author>
1327    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
1328      <organization>W3C</organization>
1329      <address><email>timbl@w3.org</email></address>
1330    </author>
1331    <date month="June" year="1999"/>
1332  </front>
1333  <seriesInfo name="RFC" value="2616"/>
1334</reference>
1335
1336<reference anchor='RFC3864'>
1337  <front>
1338    <title>Registration Procedures for Message Header Fields</title>
1339    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
1340      <organization>Nine by Nine</organization>
1341      <address><email>GK-IETF@ninebynine.org</email></address>
1342    </author>
1343    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
1344      <organization>BEA Systems</organization>
1345      <address><email>mnot@pobox.com</email></address>
1346    </author>
1347    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
1348      <organization>HP Labs</organization>
1349      <address><email>JeffMogul@acm.org</email></address>
1350    </author>
1351    <date year='2004' month='September' />
1352  </front>
1353  <seriesInfo name='BCP' value='90' />
1354  <seriesInfo name='RFC' value='3864' />
1355</reference>
1356
1357<reference anchor="RFC4288">
1358  <front>
1359    <title>Media Type Specifications and Registration Procedures</title>
1360    <author initials="N." surname="Freed" fullname="N. Freed">
1361      <organization>Sun Microsystems</organization>
1362      <address>
1363        <email>ned.freed@mrochek.com</email>
1364      </address>
1365    </author>
1366    <author initials="J." surname="Klensin" fullname="J. Klensin">
1367      <address>
1368        <email>klensin+ietf@jck.com</email>
1369      </address>
1370    </author>
1371    <date year="2005" month="December"/>
1372  </front>
1373  <seriesInfo name="BCP" value="13"/>
1374  <seriesInfo name="RFC" value="4288"/>
1375</reference>
1376
1377<reference anchor='RFC5226'>
1378  <front>
1379    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
1380    <author initials='T.' surname='Narten' fullname='T. Narten'>
1381      <organization>IBM</organization>
1382      <address><email>narten@us.ibm.com</email></address>
1383    </author>
1384    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
1385      <organization>Google</organization>
1386      <address><email>Harald@Alvestrand.no</email></address>
1387    </author>
1388    <date year='2008' month='May' />
1389  </front>
1390  <seriesInfo name='BCP' value='26' />
1391  <seriesInfo name='RFC' value='5226' />
1392</reference>
1393
1394</references>
1395
1396<section title="Internet Media Type multipart/byteranges" anchor="internet.media.type.multipart.byteranges">
1397<iref item="Media Type" subitem="multipart/byteranges" primary="true"/>
1398<iref item="multipart/byteranges Media Type" primary="true"/>
1399<t>
1400   When an HTTP 206 (Partial Content) response message includes the
1401   content of multiple ranges (a response to a request for multiple
1402   non-overlapping ranges), these are transmitted as a multipart
1403   message-body (<xref target="RFC2046" x:fmt="," x:sec="5.1"/>). The media type for this purpose is called
1404   "multipart/byteranges".  The following is to be registered with IANA <xref target="RFC4288"/>.
1405</t>
1406<x:note>
1407  <t>
1408    <x:h>Note:</x:h> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
1409  </t>
1410</x:note>
1411<t>
1412   The multipart/byteranges media type includes one or more parts, each
1413   with its own Content-Type and Content-Range fields. The required
1414   boundary parameter specifies the boundary string used to separate
1415   each body-part.
1416</t>
1417<t>
1418  <list style="hanging" x:indent="12em">
1419    <t hangText="Type name:">
1420      multipart
1421    </t>
1422    <t hangText="Subtype name:">
1423      byteranges
1424    </t>
1425    <t hangText="Required parameters:">
1426      boundary
1427    </t>
1428    <t hangText="Optional parameters:">
1429      none
1430    </t>
1431    <t hangText="Encoding considerations:">
1432      only "7bit", "8bit", or "binary" are permitted
1433    </t>
1434    <t hangText="Security considerations:">
1435      none
1436    </t>
1437    <t hangText="Interoperability considerations:">
1438      none
1439    </t>
1440    <t hangText="Published specification:">
1441      This specification (see <xref target="internet.media.type.multipart.byteranges"/>).
1442    </t>
1443    <t hangText="Applications that use this media type:">
1444    </t>
1445    <t hangText="Additional information:">
1446      <list style="hanging">
1447        <t hangText="Magic number(s):">none</t>
1448        <t hangText="File extension(s):">none</t>
1449        <t hangText="Macintosh file type code(s):">none</t>
1450      </list>
1451    </t>
1452    <t hangText="Person and email address to contact for further information:">
1453      See Authors Section.
1454    </t>
1455    <t hangText="Intended usage:">
1456      COMMON
1457    </t>
1458    <t hangText="Restrictions on usage:">
1459      none
1460    </t>
1461    <t hangText="Author/Change controller:">
1462      IESG
1463    </t>
1464  </list>
1465</t>
1466<figure><preamble>
1467   For example:
1468</preamble><artwork type="example">
1469  HTTP/1.1 206 Partial Content
1470  Date: Wed, 15 Nov 1995 06:25:24 GMT
1471  Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
1472  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1473 
1474  --THIS_STRING_SEPARATES
1475  Content-type: application/pdf
1476  Content-range: bytes 500-999/8000
1477 
1478  ...the first range...
1479  --THIS_STRING_SEPARATES
1480  Content-type: application/pdf
1481  Content-range: bytes 7000-7999/8000
1482 
1483  ...the second range
1484  --THIS_STRING_SEPARATES--
1485</artwork></figure>
1486<figure><preamble>
1487   Other example:
1488</preamble>
1489<artwork type="example">
1490  HTTP/1.1 206 Partial Content
1491  Date: Tue, 14 Nov 1995 06:25:24 GMT
1492  Last-Modified: Tue, 14 July 04:58:08 GMT
1493  Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES
1494 
1495  --THIS_STRING_SEPARATES
1496  Content-type: video/example
1497  Content-range: exampleunit 1.2-4.3/25
1498 
1499  ...the first range...
1500  --THIS_STRING_SEPARATES
1501  Content-type: video/example
1502  Content-range: exampleunit 11.2-14.3/25
1503 
1504  ...the second range
1505  --THIS_STRING_SEPARATES--
1506</artwork>
1507</figure>
1508<t>
1509      Notes:
1510  <list style="numbers">
1511      <t>Additional CRLFs &MAY; precede the first boundary string in the body.</t>
1512
1513      <t>Although <xref target="RFC2046"/> permits the boundary string to be
1514         quoted, some existing implementations handle a quoted boundary
1515         string incorrectly.</t>
1516
1517      <t>A number of browsers and servers were coded to an early draft
1518         of the byteranges specification to use a media type of
1519         multipart/x-byteranges<iref item="multipart/x-byteranges Media Type"/><iref item="Media Type" subitem="multipart/x-byteranges"/>, which is almost, but not quite
1520         compatible with the version documented in HTTP/1.1.</t>
1521  </list>
1522</t>
1523</section>
1524
1525<section title="Compatibility with Previous Versions" anchor="compatibility">
1526<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
1527<t>
1528  Clarify that it is not ok to use a weak validator in a 206 response.
1529  (<xref target="status.206"/>)
1530</t>
1531<t>
1532  Change ABNF productions for header fields to only define the field value.
1533  (<xref target="header.field.definitions"/>)
1534</t>
1535<t>
1536  Clarify that multipart/byteranges can consist of a single part.
1537  (<xref target="internet.media.type.multipart.byteranges"/>)
1538</t>
1539</section>
1540
1541</section>
1542
1543<?BEGININC p5-range.abnf-appendix ?>
1544<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
1545<figure>
1546<artwork type="abnf" name="p5-range.parsed-abnf">
1547<x:ref>Accept-Ranges</x:ref> = acceptable-ranges
1548
1549<x:ref>Content-Range</x:ref> = byte-content-range-spec / other-content-range-spec
1550
1551<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 8&gt;
1552
1553<x:ref>If-Range</x:ref> = entity-tag / HTTP-date
1554
1555<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
1556
1557<x:ref>Range</x:ref> = byte-ranges-specifier / other-ranges-specifier
1558
1559<x:ref>acceptable-ranges</x:ref> = ( *( "," OWS ) range-unit *( OWS "," [ OWS
1560 range-unit ] ) ) / "none"
1561
1562<x:ref>byte-content-range-spec</x:ref> = bytes-unit SP byte-range-resp-spec "/" (
1563 instance-length / "*" )
1564<x:ref>byte-range-resp-spec</x:ref> = ( first-byte-pos "-" last-byte-pos ) / "*"
1565<x:ref>byte-range-set</x:ref> = ( *( "," OWS ) byte-range-spec ) / (
1566 suffix-byte-range-spec *( OWS "," [ ( OWS byte-range-spec ) /
1567 suffix-byte-range-spec ] ) )
1568<x:ref>byte-range-spec</x:ref> = first-byte-pos "-" [ last-byte-pos ]
1569<x:ref>byte-ranges-specifier</x:ref> = bytes-unit "=" byte-range-set
1570<x:ref>bytes-unit</x:ref> = "bytes"
1571
1572<x:ref>entity-tag</x:ref> = &lt;entity-tag, defined in [Part4], Section 2.3&gt;
1573
1574<x:ref>first-byte-pos</x:ref> = 1*DIGIT
1575
1576<x:ref>instance-length</x:ref> = 1*DIGIT
1577
1578<x:ref>last-byte-pos</x:ref> = 1*DIGIT
1579
1580<x:ref>other-content-range-spec</x:ref> = other-range-unit SP other-range-resp-spec
1581<x:ref>other-range-resp-spec</x:ref> = *CHAR
1582<x:ref>other-range-set</x:ref> = 1*CHAR
1583<x:ref>other-range-unit</x:ref> = token
1584<x:ref>other-ranges-specifier</x:ref> = other-range-unit "=" other-range-set
1585
1586<x:ref>range-unit</x:ref> = bytes-unit / other-range-unit
1587
1588<x:ref>suffix-byte-range-spec</x:ref> = "-" suffix-length
1589<x:ref>suffix-length</x:ref> = 1*DIGIT
1590
1591<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 3.2.4&gt;
1592</artwork>
1593</figure>
1594<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
1595; Accept-Ranges defined but not used
1596; Content-Range defined but not used
1597; If-Range defined but not used
1598; Range defined but not used
1599</artwork></figure></section>
1600<?ENDINC p5-range.abnf-appendix ?>
1601
1602
1603<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
1604
1605<section title="Since RFC 2616">
1606<t>
1607  Extracted relevant partitions from <xref target="RFC2616"/>.
1608</t>
1609</section>
1610
1611<section title="Since draft-ietf-httpbis-p5-range-00">
1612<t>
1613  Closed issues:
1614  <list style="symbols"> 
1615    <t>
1616      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/18"/>:
1617      "Cache validators in 206 responses"
1618      (<eref target="http://purl.org/NET/http-errata#ifrange206"/>)
1619    </t>
1620    <t>
1621      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
1622      "Normative and Informative references"
1623    </t>
1624    <t>
1625      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/86"/>:
1626      "Normative up-to-date references"
1627    </t>
1628  </list>
1629</t>
1630</section>
1631
1632<section title="Since draft-ietf-httpbis-p5-range-01">
1633<t>
1634  Closed issues:
1635  <list style="symbols"> 
1636    <t>
1637      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/55"/>:
1638      "Updating to RFC4288"
1639    </t>
1640  </list>
1641</t>
1642<t>
1643  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1644  <list style="symbols"> 
1645    <t>
1646      Add explicit references to BNF syntax and rules imported from other parts of the specification.
1647    </t>
1648  </list>
1649</t>
1650</section>
1651
1652<section title="Since draft-ietf-httpbis-p5-range-02" anchor="changes.since.02">
1653<t>
1654  Ongoing work on IANA Message Header Field Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
1655  <list style="symbols"> 
1656    <t>
1657      Reference RFC 3984, and update header field registrations for headers defined
1658      in this document.
1659    </t>
1660  </list>
1661</t>
1662</section>
1663
1664<section title="Since draft-ietf-httpbis-p5-range-03" anchor="changes.since.03">
1665<t>
1666  None.
1667</t>
1668</section>
1669
1670<section title="Since draft-ietf-httpbis-p5-range-04" anchor="changes.since.04">
1671<t>
1672  Closed issues:
1673  <list style="symbols"> 
1674    <t>
1675      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/133"/>:
1676      "multipart/byteranges minimum number of parts"
1677    </t>
1678  </list>
1679</t>
1680<t>
1681  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1682  <list style="symbols"> 
1683    <t>
1684      Use "/" instead of "|" for alternatives.
1685    </t>
1686    <t>
1687      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
1688      whitespace ("OWS") and required whitespace ("RWS").
1689    </t>
1690    <t>
1691      Rewrite ABNFs to spell out whitespace rules, factor out
1692      header field value format definitions.
1693    </t>
1694  </list>
1695</t>
1696</section>
1697
1698<section title="Since draft-ietf-httpbis-p5-range-05" anchor="changes.since.05">
1699<t>
1700  Closed issues:
1701  <list style="symbols"> 
1702    <t>
1703      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/142"/>:
1704      "State base for *-byte-pos and suffix-length"
1705    </t>
1706  </list>
1707</t>
1708<t>
1709  Ongoing work on Custom Ranges (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/85"/>):
1710  <list style="symbols"> 
1711    <t>
1712      Remove bias in favor of byte ranges; allow custom ranges in ABNF.
1713    </t>
1714  </list>
1715</t>
1716<t>
1717  Final work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1718  <list style="symbols"> 
1719    <t>
1720      Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.
1721    </t>
1722  </list>
1723</t>
1724</section>
1725
1726<section title="Since draft-ietf-httpbis-p5-range-06" anchor="changes.since.06">
1727<t>
1728  Closed issues:
1729  <list style="symbols"> 
1730    <t>
1731      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/161"/>:
1732      "base for numeric protocol elements"
1733    </t>
1734  </list>
1735</t>
1736</section>
1737
1738<section title="Since draft-ietf-httpbis-p5-range-07" anchor="changes.since.07">
1739<t>
1740  Closed issues:
1741  <list style="symbols">
1742    <t>
1743      Fixed discrepancy in the If-Range definition about allowed validators.
1744    </t>
1745    <t>
1746      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/150" />: "multipart/byteranges for custom range units"
1747    </t>
1748    <t>
1749      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/151" />: "range unit missing from other-ranges-specifier in Range header"
1750    </t>
1751    <t>
1752      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/198"/>:
1753      "move IANA registrations for optional status codes"
1754    </t>
1755  </list>
1756</t>
1757</section>
1758
1759<section title="Since draft-ietf-httpbis-p5-range-08" anchor="changes.since.08">
1760<t>
1761  No significant changes.
1762</t>
1763</section>
1764
1765<section title="Since draft-ietf-httpbis-p5-range-09" anchor="changes.since.09">
1766<t>
1767 No significant changes.
1768</t>
1769</section>
1770
1771<section title="Since draft-ietf-httpbis-p5-range-10" anchor="changes.since.10">
1772<t>
1773  Closed issues:
1774  <list style="symbols"> 
1775    <t>
1776      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/69"/>:
1777      "Clarify 'Requested Variant'"
1778    </t>
1779    <t>
1780      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/109"/>:
1781      "Clarify entity / representation / variant terminology"
1782    </t>
1783    <t>
1784      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/220"/>:
1785      "consider removing the 'changes from 2068' sections"
1786    </t>
1787  </list>
1788</t>
1789<t>
1790  Ongoing work on Custom Ranges (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/85"/>):
1791  <list style="symbols"> 
1792    <t>
1793      Add IANA registry.
1794    </t>
1795  </list>
1796</t>
1797</section>
1798
1799<section title="Since draft-ietf-httpbis-p5-range-11" anchor="changes.since.11">
1800<t>
1801  Closed issues:
1802  <list style="symbols"> 
1803    <t>
1804      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/217"/>:
1805      "Caches can't be required to serve ranges"
1806    </t>
1807  </list>
1808</t>
1809</section>
1810
1811<section title="Since draft-ietf-httpbis-p5-range-12" anchor="changes.since.12">
1812<t>
1813  Closed issues:
1814  <list style="symbols"> 
1815    <t>
1816      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/224"/>:
1817      "Header Classification"
1818    </t>
1819  </list>
1820</t>
1821</section>
1822
1823<section title="Since draft-ietf-httpbis-p5-range-13" anchor="changes.since.13">
1824<t>
1825  Closed issues:
1826  <list style="symbols">
1827    <t>
1828      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/276"/>:
1829      "untangle ABNFs for header fields"
1830    </t>
1831  </list>
1832</t>
1833</section>
1834
1835<section title="Since draft-ietf-httpbis-p5-range-14" anchor="changes.since.14">
1836<t>
1837  None.
1838</t>
1839</section>
1840
1841<section title="Since draft-ietf-httpbis-p5-range-15" anchor="changes.since.15">
1842<t>
1843  Closed issues:
1844  <list style="symbols">
1845    <t>
1846      <eref target="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/175"/>:
1847      "Security consideration: range flooding"
1848    </t>
1849  </list>
1850</t>
1851</section>
1852
1853<section title="Since draft-ietf-httpbis-p5-range-16" anchor="changes.since.16">
1854<t>
1855  Closed issues:
1856  <list style="symbols"> 
1857    <t>
1858      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/186"/>:
1859      "Document HTTP's error-handling philosophy"
1860    </t>
1861    <t>
1862      <eref target="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/301"/>:
1863      "Content-Range on responses other than 206"
1864    </t>
1865    <t>
1866      <eref target="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/319"/>:
1867      "case sensitivity of ranges in p5"
1868    </t>
1869  </list>
1870</t>
1871</section>
1872
1873<section title="Since draft-ietf-httpbis-p5-range-17" anchor="changes.since.17">
1874<t>
1875  None.
1876</t>
1877</section>
1878
1879<section title="Since draft-ietf-httpbis-p5-range-18" anchor="changes.since.18">
1880<t>
1881  None yet.
1882</t>
1883</section>
1884
1885</section>
1886
1887</back>
1888</rfc>
Note: See TracBrowser for help on using the repository browser.