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

Last change on this file since 1589 was 1586, checked in by fielding@…, 8 years ago

trim the authors list to just the current editors

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