Source: https://trac.ietf.org/trac/httpbis/browser/draft-ietf-httpbis/latest/p5-range.html?rev=459
Timestamp: 2020-01-19 07:56:12
Document Index: 779463539

Matched Legal Cases: ['art1', 'art1', 'art 1', 'art1', 'art1', 'art1', 'art 1', 'art1', 'art1']

source: draft-ietf-httpbis/latest/p5-range.html @ 459
Last change on this file since 459 was 454, checked in by julian.reschke@…, 11 years ago
fix line wrap in ABNF prose problem; update XSLT for collected ABNF to move diagnostics into separate figure
<meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.424, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
&lt;draft-ietf-httpbis-p5-range-latest&gt;
<p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
<div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.2.1</a>&gt;
<p id="rfc.section.5.1.p.1">The response-header "Accept-Ranges" field allows the server to indicate its acceptance of range requests for a resource:</p>
<p id="rfc.section.5.2.p.1">The entity-header "Content-Range" is sent with a partial entity-body to specify where in the full entity-body the partial
selected resource as a decimal number. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".
<p id="rfc.section.5.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request.
<p id="rfc.section.5.3.p.2">The request header "If-Range" allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity
is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity'.
<p id="rfc.section.5.3.p.5">If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial Content) response. If the entity tag does not match, then
gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets are
decimal and start at zero.
</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the decimal suffix-length
value. (That is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length,
the entire entity-body is used.
<p id="rfc.section.5.4.2.p.1">HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies
<div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.23"></span> <a href="#range.retrieval.requests" class="smpl">Range</a> = "Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
/ <a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a>
<a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a> = 1*<a href="#notation" class="smpl">CHAR</a>
<td>Accept-Ranges</td>
<td> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
<td>Content-Range</td>
<td> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>
<td>If-Range</td>
<td> <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section&nbsp;5.3</a>
<td> <a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;5.4</a>
<p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
needed headers in a 206 response, this problem can be avoided. (Section <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">3.1</a> and <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">5.3</a>)
of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">3.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.7" title="Content-Range">5.2</a>)
<p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;3.1</a>)
<div id="rfc.figure.u.19"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = "Accept-Ranges:" OWS Accept-Ranges-v
<a href="#rule.ranges-specifier" class="smpl">other-ranges-specifier</a> = 1*CHAR
<p id="rfc.section.D.7.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
<li class="indline1">206 Partial Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.3"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.2</a></li>
<li class="indline1">416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.4"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li>
<li class="indline1">Accept-Ranges header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">6.1</a></li>
<li class="indline1">Content-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">6.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li>
<li class="indline1">Accept-Ranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a>, <a class="iref" href="#rfc.xref.header.accept-ranges.1">6.1</a></li>
<li class="indline1">Content-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">6.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.7">B.1</a></li>
<li class="indline1">If-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">6.1</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li>
<li class="indline1">Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">2</a>, <a class="iref" href="#rfc.xref.header.range.3">3.1</a>, <a class="iref" href="#rfc.xref.header.range.4">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">6.1</a></li>
<li class="indline1">If-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a>, <a class="iref" href="#rfc.xref.header.if-range.3">6.1</a>, <a class="iref" href="#rfc.xref.header.if-range.4">B.1</a></li>
<li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li>
<li class="indline1">Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">2</a>, <a class="iref" href="#rfc.xref.header.range.3">3.1</a>, <a class="iref" href="#rfc.xref.header.range.4">3.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>5.4</b></a>, <a class="iref" href="#rfc.xref.header.range.5">6.1</a></li>
<li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.2</a>, <a class="iref" href="#RFC5234"><b>9.1</b></a><ul class="ind">
<li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.1">1.2</a></li>
<li class="indline1">206 Partial Content&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.1</a>, <a class="iref" href="#rfc.xref.status.206.2">B.2</a></li>
<li class="indline1">416 Requested Range Not Satisfiable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li>