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

clarify integer parsing requirement (see #507)

File:
1 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"
Note: See TracChangeset for help on using the changeset viewer.