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

Last change on this file since 969 was 969, checked in by fielding@…, 9 years ago

Replace lowercase should with less normative words, where possible.

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