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

Last change on this file since 834 was 832, checked in by julian.reschke@…, 9 years ago

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

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