Ignore:
Timestamp:
Nov 13, 2008, 10:53:12 AM (11 years ago)
Author:
julian.reschke@…
Message:

Rewrite header ABNFs to spell out whitespace rules, factor out value format definitions. (related to #36)

File:
1 edited

Legend:

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

    r363 r366  
    666666      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2>
    667667      <p id="rfc.section.6.1.p.1">The response-header "Accept-Ranges" field allows the server to indicate its acceptance of range requests for a resource:</p>
    668       <div id="rfc.figure.u.6"></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="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>
     668      <div id="rfc.figure.u.6"></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="#notation" class="smpl">OWS</a> <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>
    669669  <a href="#header.accept-ranges" class="smpl">Accept-Ranges-v</a>   = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
    670670  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
     
    684684         body should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;3</a>.
    685685      </p>
    686       <div id="rfc.figure.u.9"></div><pre class="inline"><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><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.content-range" class="smpl">Content-Range-v</a>
     686      <div id="rfc.figure.u.9"></div><pre class="inline"><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><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#header.content-range" class="smpl">Content-Range</a> = "Content-Range" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.content-range" class="smpl">Content-Range-v</a>
    687687  <a href="#header.content-range" class="smpl">Content-Range-v</a> = <a href="#header.content-range" class="smpl">content-range-spec</a>
    688688 
     
    763763         is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity'.
    764764      </p>
    765       <div id="rfc.figure.u.15"></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="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a>
     765      <div id="rfc.figure.u.15"></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="#notation" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a>
    766766  <a href="#header.if-range" class="smpl">If-Range-v</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
    767767</pre><p id="rfc.section.6.3.p.4">If the client has no entity tag for an entity, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header. (The server can distinguish between a valid HTTP-date and any form of entity-tag by examining
     
    824824         to the entity returned as the result of the request:
    825825      </p>
    826       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a>   = "Range" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
     826      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a>   = "Range" ":" <a href="#notation" class="smpl">OWS</a> <a href="#range.retrieval.requests" class="smpl">Range-v</a>
    827827  <a href="#range.retrieval.requests" class="smpl">Range-v</a> = <a href="#rule.ranges-specifier" class="smpl">ranges-specifier</a>
    828828</pre><p id="rfc.section.6.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when possible,
Note: See TracChangeset for help on using the changeset viewer.