Changeset 1400 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 22/08/11 07:53:05 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r1399 r1400 1603 1603 Expires: Thu, 01 Dec 1994 16:00:00 GMT 1604 1604 </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> 1605 1610 <x:note> 1606 1611 <t> … … 1612 1617 </x:note> 1613 1618 <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. 1621 1625 </t> 1622 1626 </section> … … 2857 2861 <section title="Since draft-ietf-httpbis-p6-cache-15" anchor="changes.since.15"> 2858 2862 <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> 2860 2870 </t> 2861 2871 </section>
Note: See TracChangeset
for help on using the changeset viewer.