Changeset 2480 for draft-ietf-httpbis


Ignore:
Timestamp:
07/11/13 15:28:22 (7 years ago)
Author:
julian.reschke@…
Message:

clarify integer parsing requirement (see #507)

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

Legend:

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

    r2477 r2480  
    445445  }
    446446  @bottom-center {
    447        content: "Expires May 9, 2014";
     447       content: "Expires May 11, 2014";
    448448  }
    449449  @bottom-right {
     
    487487      <meta name="dct.creator" content="Reschke, J. F.">
    488488      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    489       <meta name="dct.issued" scheme="ISO8601" content="2013-11-05">
     489      <meta name="dct.issued" scheme="ISO8601" content="2013-11-07">
    490490      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    491491      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    516516            <tr>
    517517               <td class="left">Intended status: Standards Track</td>
    518                <td class="right">November 5, 2013</td>
     518               <td class="right">November 7, 2013</td>
    519519            </tr>
    520520            <tr>
    521                <td class="left">Expires: May 9, 2014</td>
     521               <td class="left">Expires: May 11, 2014</td>
    522522               <td class="right"></td>
    523523            </tr>
     
    548548            in progress”.
    549549         </p>
    550          <p>This Internet-Draft will expire on May 9, 2014.</p>
     550         <p>This Internet-Draft will expire on May 11, 2014.</p>
    551551      </div>
    552552      <div id="rfc.copyrightnotice">
     
    15141514               </p>
    15151515               <p id="rfc.section.3.3.2.p.11">Any Content-Length field value greater than or equal to zero is valid. Since there is no predefined limit to the length of
    1516                   a payload, a recipient <em class="bcp14">SHOULD</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows (<a href="#attack.protocol.element.size.overflows" title="Buffer Overflows">Section&nbsp;9.3</a>).
     1516                  a payload, a recipient <em class="bcp14">MUST</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows (<a href="#attack.protocol.element.size.overflows" title="Buffer Overflows">Section&nbsp;9.3</a>).
    15171517               </p>
    15181518               <p id="rfc.section.3.3.2.p.12">If a message is received that has multiple Content-Length header fields with field-values consisting of the same decimal value,
     
    34273427            <ul>
    34283428               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/502">http://tools.ietf.org/wg/httpbis/trac/ticket/502</a>&gt;: "APPSDIR review of draft-ietf-httpbis-p1-messaging-24"
     3429               </li>
     3430               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/507">http://tools.ietf.org/wg/httpbis/trac/ticket/507</a>&gt;: "integer value parsing"
    34293431               </li>
    34303432               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/517">http://tools.ietf.org/wg/httpbis/trac/ticket/517</a>&gt;: "move IANA registrations to correct draft"
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2477 r2480  
    17111711   Any Content-Length field value greater than or equal to zero is valid.
    17121712   Since there is no predefined limit to the length of a payload, a
    1713    recipient &SHOULD; anticipate potentially large decimal numerals and
     1713   recipient &MUST; anticipate potentially large decimal numerals and
    17141714   prevent parsing errors due to integer conversion overflows
    17151715   (<xref target="attack.protocol.element.size.overflows"/>).
     
    54145414    </t>
    54155415    <t>
     5416      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/507"/>:
     5417      "integer value parsing"
     5418    </t>
     5419    <t>
    54165420      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/517"/>:
    54175421      "move IANA registrations to correct draft"
  • draft-ietf-httpbis/latest/p5-range.html

    r2477 r2480  
    445445  }
    446446  @bottom-center {
    447        content: "Expires May 9, 2014";
     447       content: "Expires May 11, 2014";
    448448  }
    449449  @bottom-right {
     
    488488      <meta name="dct.creator" content="Reschke, J. F.">
    489489      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    490       <meta name="dct.issued" scheme="ISO8601" content="2013-11-05">
     490      <meta name="dct.issued" scheme="ISO8601" content="2013-11-07">
    491491      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    492492      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
     
    514514            </tr>
    515515            <tr>
    516                <td class="left">Expires: May 9, 2014</td>
     516               <td class="left">Expires: May 11, 2014</td>
    517517               <td class="right">J. Reschke, Editor</td>
    518518            </tr>
     
    523523            <tr>
    524524               <td class="left"></td>
    525                <td class="right">November 5, 2013</td>
     525               <td class="right">November 7, 2013</td>
    526526            </tr>
    527527         </tbody>
     
    549549            in progress”.
    550550         </p>
    551          <p>This Internet-Draft will expire on May 9, 2014.</p>
     551         <p>This Internet-Draft will expire on May 11, 2014.</p>
    552552      </div>
    553553      <div id="rfc.copyrightnotice">
     
    718718            <p id="rfc.section.2.1.p.13">If a valid <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> includes at least one <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> with a <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> that is less than the current length of the representation, or at least one <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> with a non-zero <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, then the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is satisfiable. Otherwise, the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is unsatisfiable.
    719719            </p>
    720             <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought
    721                to anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
     720            <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients <em class="bcp14">MUST</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
    722721            </p>
    723722         </div>
     
    13801379            <ul>
    13811380               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/506">http://tools.ietf.org/wg/httpbis/trac/ticket/506</a>&gt;: "APPSDIR review of draft-ietf-httpbis-p5-range-24"
     1381               </li>
     1382               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/507">http://tools.ietf.org/wg/httpbis/trac/ticket/507</a>&gt;: "integer value parsing"
    13821383               </li>
    13831384               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/508">http://tools.ietf.org/wg/httpbis/trac/ticket/508</a>&gt;: "broken sentence in description of 206"
  • draft-ietf-httpbis/latest/p5-range.xml

    r2477 r2480  
    314314   <x:ref>last-byte-pos</x:ref>, and <x:ref>suffix-length</x:ref> are
    315315   expressed as decimal number of octets. Since there is no predefined limit
    316    to the length of a payload, recipients ought to anticipate potentially
     316   to the length of a payload, recipients &MUST; anticipate potentially
    317317   large decimal numerals and prevent parsing errors due to integer conversion
    318318   overflows.
     
    15141514    </t>
    15151515    <t>
     1516      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/507"/>:
     1517      "integer value parsing"
     1518    </t>
     1519    <t>
    15161520      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/508"/>:
    15171521      "broken sentence in description of 206"
Note: See TracChangeset for help on using the changeset viewer.