Ignore:
Timestamp:
Aug 22, 2011, 12:53:05 AM (8 years ago)
Author:
mnot@…
Message:

Clarify one-year limit on Expires; addresses #290

File:
1 edited

Legend:

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

    r1399 r1400  
    16031603  Expires: Thu, 01 Dec 1994 16:00:00 GMT
    16041604</artwork></figure>
     1605<t>
     1606   A cache &MUST; treat other invalid date formats,
     1607   especially including the value "0", as in the past (i.e., "already
     1608   expired").
     1609</t>
    16051610<x:note>
    16061611   <t>
     
    16121617</x:note>
    16131618<t>
    1614    A server &SHOULD-NOT; send Expires dates more than one year in the
    1615    future.
    1616 </t>
    1617 <t>
    1618    A cache &MUST; treat other invalid date formats,
    1619    especially including the value "0", as in the past (i.e., "already
    1620    expired").
     1619   Historically, HTTP required the Expires field-value to be no more than a
     1620   year in the future. While longer freshness lifetimes are no longer
     1621   prohibited, extremely large values have been demonstrated to cause
     1622   problems (e.g., clock overflows due to use of 32-bit integers for
     1623   time values), and most caches will evict a response far sooner than
     1624   that. Therefore, senders ought not produce them.
    16211625</t>
    16221626</section>
     
    28572861<section title="Since draft-ietf-httpbis-p6-cache-15" anchor="changes.since.15">
    28582862<t>
    2859   None yet.
     2863  Closed issues:
     2864  <list style="symbols">
     2865    <t>
     2866      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/290"/>:
     2867      "Motivate one-year limit for Expires"
     2868    </t>
     2869  </list>
    28602870</t>
    28612871</section>
Note: See TracChangeset for help on using the changeset viewer.