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)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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>
Note: See TracChangeset for help on using the changeset viewer.