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

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

Clarify case insensitivity of ABNF rues derived from token or string. Addresses 319

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