Changeset 1400 for draft-ietf-httpbis
- Timestamp:
- 22/08/11 07:53:05 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1396 r1400 362 362 } 363 363 @bottom-center { 364 content: "Expires February 10, 2012";364 content: "Expires February 23, 2012"; 365 365 } 366 366 @bottom-right { … … 408 408 <meta name="dct.creator" content="Reschke, J. F."> 409 409 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-08- 09">410 <meta name="dct.issued" scheme="ISO8601" content="2011-08-22"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 412 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: February 10, 2012</td>436 <td class="left">Expires: February 23, 2012</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 495 495 <tr> 496 496 <td class="left"></td> 497 <td class="right">August 9, 2011</td>497 <td class="right">August 22, 2011</td> 498 498 </tr> 499 499 </tbody> … … 525 525 in progress”. 526 526 </p> 527 <p>This Internet-Draft will expire on February 10, 2012.</p>527 <p>This Internet-Draft will expire on February 23, 2012.</p> 528 528 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 529 529 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1359 1359 </pre><div id="rfc.figure.u.14"></div> 1360 1360 <p>For example</p> <pre class="text"> Expires: Thu, 01 Dec 1994 16:00:00 GMT 1361 </pre><div class="note" id="rfc.section.3.3.p.6"> 1361 </pre><p id="rfc.section.3.3.p.6">A cache <em class="bcp14">MUST</em> treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired"). 1362 </p> 1363 <div class="note" id="rfc.section.3.3.p.7"> 1362 1364 <p> <b>Note:</b> If a response includes a Cache-Control field with the max-age directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.2</a>), that directive overrides the Expires field. Likewise, the s-maxage directive overrides Expires in shared caches. 1363 1365 </p> 1364 1366 </div> 1365 <p id="rfc.section.3.3.p.7">A server <em class="bcp14">SHOULD NOT</em> send Expires dates more than one year in the future. 1366 </p> 1367 <p id="rfc.section.3.3.p.8">A cache <em class="bcp14">MUST</em> treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired"). 1367 <p id="rfc.section.3.3.p.8">Historically, HTTP required the Expires field-value to be no more than a year in the future. While longer freshness lifetimes 1368 are no longer prohibited, extremely large values have been demonstrated to cause problems (e.g., clock overflows due to use 1369 of 32-bit integers for time values), and most caches will evict a response far sooner than that. Therefore, senders ought 1370 not produce them. 1368 1371 </p> 1369 1372 <div id="rfc.iref.p.5"></div> … … 2041 2044 </ul> 2042 2045 <h2 id="rfc.section.C.17"><a href="#rfc.section.C.17">C.17</a> <a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p6-cache-15</a></h2> 2043 <p id="rfc.section.C.17.p.1">None yet.</p> 2046 <p id="rfc.section.C.17.p.1">Closed issues: </p> 2047 <ul> 2048 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/290">http://tools.ietf.org/wg/httpbis/trac/ticket/290</a>>: "Motivate one-year limit for Expires" 2049 </li> 2050 </ul> 2044 2051 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2045 2052 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a> -
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.