Ignore:
Timestamp:
Mar 10, 2011, 10:45:43 PM (9 years ago)
Author:
fielding@…
Message:

update generated HTML

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.html

    r1162 r1164  
    695695      <div id="rfc.iref.s.2"></div>
    696696      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h2>
    697       <p id="rfc.section.3.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range request-header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;5.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request
    698          did not include an If-Range request-header field (<a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>). (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current
     697      <p id="rfc.section.3.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;5.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request
     698         did not include an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section&nbsp;5.3</a>). (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current
    699699         length of the selected resource.)
    700700      </p>
     
    722722      <div id="rfc.iref.h.1"></div>
    723723      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2>
    724       <p id="rfc.section.5.1.p.1">The "Accept-Ranges" response-header field allows a resource to indicate its acceptance of range requests.</p>
     724      <p id="rfc.section.5.1.p.1">The "Accept-Ranges" header field allows a resource to indicate its acceptance of range requests.</p>
    725725      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = "Accept-Ranges" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>
    726726  <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>   = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
     
    807807         the full representation).
    808808      </p>
    809       <p id="rfc.section.5.2.p.15">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header
    810          field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
     809      <p id="rfc.section.5.2.p.15">If the server receives a request (other than one including an If-Range header field) with an unsatisfiable Range header field
     810         (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected
    811811         resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;3.2</a>).
    812812      </p>
    813813      <div class="note" id="rfc.section.5.2.p.16">
    814814         <p> <b>Note:</b> Clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for
    815             an unsatisfiable Range request-header field, since not all servers implement this request-header field.
     815            an unsatisfiable Range header field, since not all servers implement this header field.
    816816         </p>
    817817      </div>
     
    820820      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="header.if-range" href="#header.if-range">If-Range</a></h2>
    821821      <p id="rfc.section.5.3.p.1">If a client has a partial copy of a representation in its cache, and wishes to have an up-to-date copy of the entire representation
    822          in its cache, it could use the Range request-header field with a conditional GET (using either or both of If-Unmodified-Since
    823          and If-Match.) However, if the condition fails because the representation has been modified, the client would then have to
    824          make a second request to obtain the entire current representation.
    825       </p>
    826       <p id="rfc.section.5.3.p.2">The "If-Range" request-header field allows a client to "short-circuit" the second request. Informally, its meaning is "if
    827          the representation is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation".
     822         in its cache, it could use the Range header field with a conditional GET (using either or both of If-Unmodified-Since and
     823         If-Match.) However, if the condition fails because the representation has been modified, the client would then have to make
     824         a second request to obtain the entire current representation.
     825      </p>
     826      <p id="rfc.section.5.3.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is "if the representation
     827         is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation".
    828828      </p>
    829829      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.if-range" class="smpl">If-Range</a>   = "If-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a>
     
    897897      </ul>
    898898      <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a>&nbsp;<a id="range.retrieval.requests" href="#range.retrieval.requests">Range Retrieval Requests</a></h3>
    899       <p id="rfc.section.5.4.2.p.1">The "Range" request-header field defines the GET method (conditional or not) to request one or more sub-ranges of the response
    900          representation body, instead of the entire representation body.
     899      <p id="rfc.section.5.4.2.p.1">The "Range" header field defines the GET method (conditional or not) to request one or more sub-ranges of the response representation
     900         body, instead of the entire representation body.
    901901      </p>
    902902      <div id="rfc.figure.u.23"></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>
Note: See TracChangeset for help on using the changeset viewer.