Ticket #161: 161.diff

File 161.diff, 16.0 KB (added by julian.reschke@…, 13 years ago)

proposed change for parts 1, 5 and 6

  • p5-range.html

     
    466466         </tr>
    467467         <tr>
    468468            <td class="header left"></td>
    469             <td class="header right">May 1, 2009</td>
     469            <td class="header right">May 2, 2009</td>
    470470         </tr>
    471471      </table>
    472472      <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-latest</span></p>
     
    723723         whose instance-length value is less than or equal to its last-byte-pos value, is invalid. The recipient of an invalid byte-content-range-spec <em class="bcp14">MUST</em> ignore it and any content transferred along with it.
    724724      </p>
    725725      <p id="rfc.section.5.2.p.6">In the case of a byte range request: A server sending a response with status code 416 (Requested range not satisfiable) <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
    726          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 "*".
     726         selected resource. 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 "*".
    727727      </p>
    728728      <p id="rfc.section.5.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p>
    729729      <ul>
     
    807807  <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    808808  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
    809809</pre><p id="rfc.section.5.4.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value
    810          gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets are
    811          decimal and start at zero.
     810         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
     811         at zero.
    812812      </p>
    813813      <p id="rfc.section.5.4.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The
    814814         recipient of a byte-range-set that includes one or more syntactically invalid byte-range-spec values <em class="bcp14">MUST</em> ignore the header field that includes that byte-range-set.
     
    819819      <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 entity.</p>
    820820      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
    821821  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    822 </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
    823          value. (That is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length,
    824          the entire entity-body is used.
     822</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 suffix-length value. (That
     823         is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the
     824         entire entity-body is used.
    825825      </p>
    826826      <p id="rfc.section.5.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current
    827827         length of the entity-body, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is
     
    12261226         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    12271227      </ul>
    12281228      <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></h2>
     1229      <p id="rfc.section.D.8.p.1">Closed issues: </p>
     1230      <ul>
     1231         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
     1232         </li>
     1233      </ul>
    12291234      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    12301235      <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a>
    12311236      </p>
  • p6-cache.xml

     
    888888</artwork></figure>
    889889<t anchor="rule.delta-seconds">
    890890  <x:anchor-alias value="delta-seconds" />
    891   Age field-values are non-negative decimal integers, representing time in seconds.
     891  Age field-values are non-negative integers, representing time in seconds.
    892892</t>
    893893<figure><artwork type="abnf2616"><iref item="Grammar" primary="true" subitem="delta-seconds" />
    894894  <x:ref>delta-seconds</x:ref>  = 1*<x:ref>DIGIT</x:ref>
     
    22962296
    22972297<section anchor="changes.since.06" title="Since draft-ietf-httpbis-p6-cache-06">
    22982298<t>
     2299  Closed issues:
     2300  <list style="symbols">
     2301    <t>
     2302      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/161"/>:
     2303      "base for numeric protocol elements"
     2304    </t>
     2305  </list>
    22992306</t>
    23002307</section>
    23012308
  • p6-cache.html

     
    467467         </tr>
    468468         <tr>
    469469            <td class="header left"></td>
    470             <td class="header right">May 1, 2009</td>
     470            <td class="header right">May 2, 2009</td>
    471471         </tr>
    472472      </table>
    473473      <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p>
     
    964964      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  <a href="#header.age" class="smpl">Age</a>   = "Age" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.age" class="smpl">Age-v</a>
    965965  <a href="#header.age" class="smpl">Age-v</a> = <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
    966966</pre><div id="rule.delta-seconds">
    967          <p id="rfc.section.3.1.p.3">  Age field-values are non-negative decimal integers, representing time in seconds.</p>
     967         <p id="rfc.section.3.1.p.3">  Age field-values are non-negative integers, representing time in seconds.</p>
    968968      </div>
    969969      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    970970</pre><p id="rfc.section.3.1.p.5">If a cache receives a value larger than the largest positive integer it can represent, or if any of its age calculations overflows,
     
    17051705         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    17061706      </ul>
    17071707      <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p6-cache-06</a></h2>
     1708      <p id="rfc.section.C.8.p.1">Closed issues: </p>
     1709      <ul>
     1710         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
     1711         </li>
     1712      </ul>
    17081713      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    17091714      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a>
    17101715      </p>
  • p1-messaging.xml

     
    13981398    </t></x:lt>
    13991399    <x:lt><t>
    14001400     If a Content-Length header field (<xref target="header.content-length"/>) is present, its
    1401      decimal value in OCTETs represents both the entity-length and the
     1401     value in OCTETs represents both the entity-length and the
    14021402     transfer-length. The Content-Length header field &MUST-NOT; be sent
    14031403     if these two lengths are different (i.e., if a Transfer-Encoding
    14041404     header field is present). If a message is received with both a
     
    22402240  <x:anchor-alias value="Content-Length-v"/>
    22412241<t>
    22422242   The entity-header field "Content-Length" indicates the size of the
    2243    entity-body, in decimal number of OCTETs, sent to the recipient or,
     2243   entity-body, in number of OCTETs, sent to the recipient or,
    22442244   in the case of the HEAD method, the size of the entity-body that
    22452245   would have been sent had the request been a GET.
    22462246</t>
     
    49034903
    49044904<section title="Since draft-ietf-httpbis-p1-messaging-06" anchor="changes.since.06">
    49054905<t>
     4906  Closed issues:
     4907  <list style="symbols">
     4908    <t>
     4909      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/161"/>:
     4910      "base for numeric protocol elements"
     4911    </t>
     4912  </list>
    49064913</t>
    49074914</section>
    49084915
  • p1-messaging.html

     
    470470         </tr>
    471471         <tr>
    472472            <td class="header left"></td>
    473             <td class="header right">May 1, 2009</td>
     473            <td class="header right">May 2, 2009</td>
    474474         </tr>
    475475      </table>
    476476      <p class="title">HTTP/1.1, part 1: URIs, Connections, and Message Parsing<br><span class="filename">draft-ietf-httpbis-p1-messaging-latest</span></p>
     
    12601260            </p>
    12611261         </li>
    12621262         <li>
    1263             <p>If a Content-Length header field (<a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;8.2</a>) is present, its decimal value in OCTETs represents both the entity-length and the transfer-length. The Content-Length header
    1264                field <em class="bcp14">MUST NOT</em> be sent if these two lengths are different (i.e., if a Transfer-Encoding header field is present). If a message is received
     1263            <p>If a Content-Length header field (<a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;8.2</a>) is present, its value in OCTETs represents both the entity-length and the transfer-length. The Content-Length header field <em class="bcp14">MUST NOT</em> be sent if these two lengths are different (i.e., if a Transfer-Encoding header field is present). If a message is received
    12651264               with both a Transfer-Encoding header field and a Content-Length header field, the latter <em class="bcp14">MUST</em> be ignored.
    12661265            </p>
    12671266         </li>
     
    16501649      <div id="rfc.iref.c.2"></div>
    16511650      <div id="rfc.iref.h.4"></div>
    16521651      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="header.content-length" href="#header.content-length">Content-Length</a></h2>
    1653       <p id="rfc.section.8.2.p.1">The entity-header field "Content-Length" indicates the size of the entity-body, in decimal number of OCTETs, sent to the recipient
     1652      <p id="rfc.section.8.2.p.1">The entity-header field "Content-Length" indicates the size of the entity-body, in number of OCTETs, sent to the recipient
    16541653         or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET.
    16551654      </p>
    16561655      <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span>  <a href="#header.content-length" class="smpl">Content-Length</a>   = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a>
     
    29962995         </li>
    29972996      </ul>
    29982997      <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p1-messaging-06</a></h2>
     2998      <p id="rfc.section.E.8.p.1">Closed issues: </p>
     2999      <ul>
     3000         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>&gt;: "base for numeric protocol elements"
     3001         </li>
     3002      </ul>
    29993003      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    30003004      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a>
    30013005      </p>
  • p5-range.xml

     
    547547   A server sending a response with status code 416 (Requested range not
    548548   satisfiable) &SHOULD; include a Content-Range field with a byte-range-resp-spec
    549549   of "*". The instance-length specifies the current length of
    550    the selected resource as a decimal number. A response with status code 206 (Partial
     550   the selected resource. A response with status code 206 (Partial
    551551   Content) &MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*".
    552552</t>
    553553<t>
     
    720720   The first-byte-pos value in a byte-range-spec gives the byte-offset
    721721   of the first byte in a range. The last-byte-pos value gives the
    722722   byte-offset of the last byte in the range; that is, the byte
    723    positions specified are inclusive. Byte offsets are decimal and start at zero.
     723   positions specified are inclusive. Byte offsets start at zero.
    724724</t>
    725725<t>
    726726   If the last-byte-pos value is present, it &MUST; be greater than or
     
    745745</artwork></figure>
    746746<t>
    747747   A suffix-byte-range-spec is used to specify the suffix of the
    748    entity-body, of a length given by the decimal suffix-length value. (That is,
     748   entity-body, of a length given by the suffix-length value. (That is,
    749749   this form specifies the last N bytes of an entity-body.) If the
    750750   entity is shorter than the specified suffix-length, the entire
    751751   entity-body is used.
     
    15841584
    15851585<section title="Since draft-ietf-httpbis-p5-range-06" anchor="changes.since.06">
    15861586<t>
     1587  Closed issues:
     1588  <list style="symbols">
     1589    <t>
     1590      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/161"/>:
     1591      "base for numeric protocol elements"
     1592    </t>
     1593  </list>
    15871594</t>
    15881595</section>
    15891596