Changeset 576 for draft-ietf-httpbis


Ignore:
Timestamp:
May 6, 2009, 12:11:26 AM (11 years ago)
Author:
julian.reschke@…
Message:

Make spec consistent in not stating "decimal" when it's already clear from the ABNF (related to #161)

Location:
draft-ietf-httpbis/latest
Files:
6 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r574 r576  
    471471         <tr>
    472472            <td class="header left"></td>
    473             <td class="header right">May 3, 2009</td>
     473            <td class="header right">May 6, 2009</td>
    474474         </tr>
    475475      </table>
     
    12631263         </li>
    12641264         <li>
    1265             <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
    1266                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
     1265            <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
    12671266               with both a Transfer-Encoding header field and a Content-Length header field, the latter <em class="bcp14">MUST</em> be ignored.
    12681267            </p>
     
    16531652      <div id="rfc.iref.h.4"></div>
    16541653      <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>
    1655       <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
     1654      <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
    16561655         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.
    16571656      </p>
     
    30013000      <p id="rfc.section.E.8.p.1">Closed issues: </p>
    30023001      <ul>
     3002         <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"
     3003         </li>
    30033004         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/162">http://tools.ietf.org/wg/httpbis/trac/ticket/162</a>&gt;: "comment ABNF"
    30043005         </li>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r574 r576  
    14011401    <x:lt><t>
    14021402     If a Content-Length header field (<xref target="header.content-length"/>) is present, its
    1403      decimal value in OCTETs represents both the entity-length and the
     1403     value in OCTETs represents both the entity-length and the
    14041404     transfer-length. The Content-Length header field &MUST-NOT; be sent
    14051405     if these two lengths are different (i.e., if a Transfer-Encoding
     
    22432243<t>
    22442244   The entity-header field "Content-Length" indicates the size of the
    2245    entity-body, in decimal number of OCTETs, sent to the recipient or,
     2245   entity-body, in number of OCTETs, sent to the recipient or,
    22462246   in the case of the HEAD method, the size of the entity-body that
    22472247   would have been sent had the request been a GET.
     
    49104910  <list style="symbols">
    49114911    <t>
     4912      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/161"/>:
     4913      "base for numeric protocol elements"
     4914    </t>
     4915    <t>
    49124916      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/162"/>:
    49134917      "comment ABNF"
  • draft-ietf-httpbis/latest/p5-range.html

    r573 r576  
    467467         <tr>
    468468            <td class="header left"></td>
    469             <td class="header right">May 1, 2009</td>
     469            <td class="header right">May 6, 2009</td>
    470470         </tr>
    471471      </table>
     
    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>
     
    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
     
    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
     
    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>
  • draft-ietf-httpbis/latest/p5-range.xml

    r573 r576  
    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>
     
    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>
     
    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
     
    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>
  • draft-ietf-httpbis/latest/p6-cache.html

    r575 r576  
    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>
     
    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>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r575 r576  
    895895<t anchor="rule.delta-seconds">
    896896  <x:anchor-alias value="delta-seconds" />
    897   Age field-values are non-negative decimal integers, representing time in seconds.
     897  Age field-values are non-negative integers, representing time in seconds.
    898898</t>
    899899<figure><artwork type="abnf2616"><iref item="Grammar" primary="true" subitem="delta-seconds" />
     
    23082308<section anchor="changes.since.06" title="Since draft-ietf-httpbis-p6-cache-06">
    23092309<t>
     2310  Closed issues:
     2311  <list style="symbols">
     2312    <t>
     2313      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/161"/>:
     2314      "base for numeric protocol elements"
     2315    </t>
     2316  </list>
    23102317</t>
    23112318</section>
Note: See TracChangeset for help on using the changeset viewer.