![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1398 for draft-ietf-httpbis/latest/p5-range.html
- Timestamp:
- Aug 9, 2011, 8:03:32 AM (8 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p5-range.html (modified) (8 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p5-range.html
r1397 r1398 752 752 <p id="rfc.section.5.2.p.2">Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>. 753 753 </p> 754 <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#header.content-range" class="smpl">Content-Range</a> = <a href="#header.content-range" class="smpl">content-range-spec</a> 755 756 <a href="#header.content-range" class="smpl">content-range-spec</a> = <a href="#header.content-range" class="smpl">byte-content-range-spec</a> 754 <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span> <a href="#header.content-range" class="smpl">Content-Range</a> = <a href="#header.content-range" class="smpl">byte-content-range-spec</a> 757 755 / <a href="#header.content-range" class="smpl">other-content-range-spec</a> 756 758 757 <a href="#header.content-range" class="smpl">byte-content-range-spec</a> = <a href="#range.units" class="smpl">bytes-unit</a> <a href="#notation" class="smpl">SP</a> 759 758 <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> "/" … … 835 834 is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation". 836 835 </p> 837 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.1 1"></span> <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#core.rules" class="smpl">HTTP-date</a>836 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.10"></span> <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#core.rules" class="smpl">HTTP-date</a> 838 837 </pre><p id="rfc.section.5.3.p.4">Clients <em class="bcp14">MUST NOT</em> use an entity-tag marked as weak in an If-Range field value and <em class="bcp14">MUST NOT</em> use a Last-Modified date in an If-Range field value unless it has no entity-tag for the representation and the Last-Modified 839 838 date it does have for the representation is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. … … 862 861 </p> 863 862 </div> 864 <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.1 2"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>863 <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span> <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> 865 864 <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = 1#( <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> / <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> ) 866 865 <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" [ <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> ] … … 878 877 </p> 879 878 <p id="rfc.section.5.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the representation.</p> 880 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.1 8"></span><span id="rfc.iref.g.19"></span> <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>879 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span> <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> 881 880 <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 882 881 </pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the representation body, of a length given by the suffix-length … … 912 911 body, instead of the entire representation body. 913 912 </p> 914 <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g. 20"></span> <a href="#range.retrieval.requests" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>913 <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.19"></span> <a href="#range.retrieval.requests" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> 915 914 <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = <a href="#range.units" class="smpl">other-range-unit</a> "=" <a href="#range.retrieval.requests" class="smpl">other-range-set</a> 916 915 <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#notation" class="smpl">CHAR</a> … … 1228 1227 <div id="rfc.figure.u.25"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges 1229 1228 1230 <a href="#header.content-range" class="smpl">Content-Range</a> = content-range-spec1229 <a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range-spec / other-content-range-spec 1231 1230 1232 1231 <a href="#core.rules" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> … … 1250 1249 <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set 1251 1250 <a href="#range.units" class="smpl">bytes-unit</a> = "bytes" 1252 1253 <a href="#header.content-range" class="smpl">content-range-spec</a> = byte-content-range-spec /1254 other-content-range-spec1255 1251 1256 1252 <a href="#abnf.dependencies" class="smpl">entity-tag</a> = <entity-tag, defined in [Part4], Section 2.3> … … 1432 1428 <li><tt>Accept-Ranges</tt> <a href="#rfc.iref.g.4"><b>5.1</b></a></li> 1433 1429 <li><tt>acceptable-ranges</tt> <a href="#rfc.iref.g.5"><b>5.1</b></a></li> 1434 <li><tt>byte-content-range-spec</tt> <a href="#rfc.iref.g. 8"><b>5.2</b></a></li>1435 <li><tt>byte-range-resp-spec</tt> <a href="#rfc.iref.g. 9"><b>5.2</b></a></li>1436 <li><tt>byte-range-set</tt> <a href="#rfc.iref.g.1 4"><b>5.4.1</b></a></li>1437 <li><tt>byte-range-spec</tt> <a href="#rfc.iref.g.1 5"><b>5.4.1</b></a></li>1438 <li><tt>byte-ranges-specifier</tt> <a href="#rfc.iref.g.1 3"><b>5.4.1</b></a></li>1430 <li><tt>byte-content-range-spec</tt> <a href="#rfc.iref.g.7"><b>5.2</b></a></li> 1431 <li><tt>byte-range-resp-spec</tt> <a href="#rfc.iref.g.8"><b>5.2</b></a></li> 1432 <li><tt>byte-range-set</tt> <a href="#rfc.iref.g.13"><b>5.4.1</b></a></li> 1433 <li><tt>byte-range-spec</tt> <a href="#rfc.iref.g.14"><b>5.4.1</b></a></li> 1434 <li><tt>byte-ranges-specifier</tt> <a href="#rfc.iref.g.12"><b>5.4.1</b></a></li> 1439 1435 <li><tt>bytes-unit</tt> <a href="#rfc.iref.g.2"><b>2</b></a></li> 1440 1436 <li><tt>Content-Range</tt> <a href="#rfc.iref.g.6"><b>5.2</b></a></li> 1441 <li><tt>content-range-spec</tt> <a href="#rfc.iref.g.7"><b>5.2</b></a></li> 1442 <li><tt>first-byte-pos</tt> <a href="#rfc.iref.g.16"><b>5.4.1</b></a></li> 1443 <li><tt>If-Range</tt> <a href="#rfc.iref.g.11"><b>5.3</b></a></li> 1444 <li><tt>instance-length</tt> <a href="#rfc.iref.g.10"><b>5.2</b></a></li> 1445 <li><tt>last-byte-pos</tt> <a href="#rfc.iref.g.17"><b>5.4.1</b></a></li> 1437 <li><tt>first-byte-pos</tt> <a href="#rfc.iref.g.15"><b>5.4.1</b></a></li> 1438 <li><tt>If-Range</tt> <a href="#rfc.iref.g.10"><b>5.3</b></a></li> 1439 <li><tt>instance-length</tt> <a href="#rfc.iref.g.9"><b>5.2</b></a></li> 1440 <li><tt>last-byte-pos</tt> <a href="#rfc.iref.g.16"><b>5.4.1</b></a></li> 1446 1441 <li><tt>other-range-unit</tt> <a href="#rfc.iref.g.3"><b>2</b></a></li> 1447 <li><tt>Range</tt> <a href="#rfc.iref.g. 20"><b>5.4.2</b></a></li>1442 <li><tt>Range</tt> <a href="#rfc.iref.g.19"><b>5.4.2</b></a></li> 1448 1443 <li><tt>range-unit</tt> <a href="#rfc.iref.g.1"><b>2</b></a></li> 1449 <li><tt>ranges-specifier</tt> <a href="#rfc.iref.g.1 2"><b>5.4.1</b></a></li>1450 <li><tt>suffix-byte-range-spec</tt> <a href="#rfc.iref.g.1 8"><b>5.4.1</b></a></li>1451 <li><tt>suffix-length</tt> <a href="#rfc.iref.g.1 9"><b>5.4.1</b></a></li>1444 <li><tt>ranges-specifier</tt> <a href="#rfc.iref.g.11"><b>5.4.1</b></a></li> 1445 <li><tt>suffix-byte-range-spec</tt> <a href="#rfc.iref.g.17"><b>5.4.1</b></a></li> 1446 <li><tt>suffix-length</tt> <a href="#rfc.iref.g.18"><b>5.4.1</b></a></li> 1452 1447 </ul> 1453 1448 </li>
Note: See TracChangeset
for help on using the changeset viewer.
