Changeset 2491


Ignore:
Timestamp:
Nov 12, 2013, 2:46:28 AM (6 years ago)
Author:
fielding@…
Message:

revert [2488]; see #512

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r2488 r2491  
    448448  }
    449449  @bottom-center {
    450        content: "Expires May 15, 2014";
     450       content: "Expires May 16, 2014";
    451451  }
    452452  @bottom-right {
     
    492492      <meta name="dct.creator" content="Reschke, J. F.">
    493493      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    494       <meta name="dct.issued" scheme="ISO8601" content="2013-11-11">
     494      <meta name="dct.issued" scheme="ISO8601" content="2013-11-12">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    496496      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    518518            </tr>
    519519            <tr>
    520                <td class="left">Expires: May 15, 2014</td>
     520               <td class="left">Expires: May 16, 2014</td>
    521521               <td class="right">J. Reschke, Editor</td>
    522522            </tr>
     
    527527            <tr>
    528528               <td class="left"></td>
    529                <td class="right">November 11, 2013</td>
     529               <td class="right">November 12, 2013</td>
    530530            </tr>
    531531         </tbody>
     
    554554            in progress”.
    555555         </p>
    556          <p>This Internet-Draft will expire on May 15, 2014.</p>
     556         <p>This Internet-Draft will expire on May 16, 2014.</p>
    557557      </div>
    558558      <div id="rfc.copyrightnotice">
     
    723723               <p id="rfc.section.1.2.1.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
    724724               <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    725 </pre><p id="rfc.section.1.2.1.p.3">A recipient parsing a delta-seconds value ought to use an arithmetic type of at least 32 bits of signed integer range. A sender <em class="bcp14">MUST NOT</em> generate a delta-seconds value greater than 2147483647 (32bit INT_MAX, or 2<sup>31</sup> - 1).
    726                </p>
    727                <p id="rfc.section.1.2.1.p.4">If a cache receives a delta-seconds value larger than the largest positive integer it can represent, or if any of its subsequent
    728                   calculations overflows, the cache <em class="bcp14">MUST</em> consider the value to be the largest positive integer it can represent.
     725</pre><p id="rfc.section.1.2.1.p.3">If a cache receives a delta-seconds value larger than the largest positive integer it can represent, or if any of its subsequent
     726                  calculations overflows, the cache <em class="bcp14">MUST</em> consider the value to be 2147483648 (2<sup>31</sup>). A recipient parsing a delta-seconds value <em class="bcp14">MUST</em> use an arithmetic type of at least 31 bits of range, and a sender <em class="bcp14">MUST NOT</em> generate delta-seconds with a value greater than 2147483648.
     727               </p>
     728               <p id="rfc.section.1.2.1.p.4">Note that this value (2147483648) might cause implementation issues on some platforms (in particular, those that represent
     729                  MAX_INT as 2<sup>31</sup>-1), and therefore ought to be handled carefullly.
    729730               </p>
    730731            </div>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2488 r2491  
    213213</artwork></figure>
    214214<t>
    215    A recipient parsing a delta-seconds value ought to use an arithmetic type
    216    of at least 32 bits of signed integer range. A sender &MUST-NOT; generate a
    217    delta-seconds value greater than 2147483647 (32bit INT_MAX, or
    218    2<x:sup>31</x:sup> - 1).
    219 </t>
    220 <t>
    221215   If a cache receives a delta-seconds value larger than the largest
    222216   positive integer it can represent, or if any of its subsequent calculations
    223    overflows, the cache &MUST; consider the value to be the largest positive
    224    integer it can represent.
     217   overflows, the cache &MUST; consider the value to be 2147483648
     218   (2<x:sup>31</x:sup>). A recipient parsing a delta-seconds value &MUST; use
     219   an arithmetic type of at least 31 bits of range, and a sender &MUST-NOT;
     220   generate delta-seconds with a value greater than 2147483648.
     221</t>
     222<t>
     223   Note that this value (2147483648) might cause implementation issues on some
     224   platforms (in particular, those that represent MAX_INT as
     225   2<x:sup>31</x:sup>-1), and therefore ought to be handled carefullly.
    225226</t>
    226227</section>
Note: See TracChangeset for help on using the changeset viewer.