Changeset 1483 for draft-ietf-httpbis/latest
- Timestamp:
- 05/12/11 03:17:47 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1481 r1483 362 362 } 363 363 @bottom-center { 364 content: "Expires June 3, 2012";364 content: "Expires June 7, 2012"; 365 365 } 366 366 @bottom-right { … … 410 410 <meta name="dct.creator" content="Reschke, J. F."> 411 411 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 412 <meta name="dct.issued" scheme="ISO8601" content="2011-12-0 1">412 <meta name="dct.issued" scheme="ISO8601" content="2011-12-05"> 413 413 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 414 414 <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."> … … 436 436 </tr> 437 437 <tr> 438 <td class="left">Expires: June 3, 2012</td>438 <td class="left">Expires: June 7, 2012</td> 439 439 <td class="right">J. Mogul</td> 440 440 </tr> … … 501 501 <tr> 502 502 <td class="left"></td> 503 <td class="right">December 1, 2011</td>503 <td class="right">December 5, 2011</td> 504 504 </tr> 505 505 </tbody> … … 531 531 in progress”. 532 532 </p> 533 <p>This Internet-Draft will expire on June 3, 2012.</p>533 <p>This Internet-Draft will expire on June 7, 2012.</p> 534 534 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 535 535 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 844 844 <li>selecting header fields nominated by the stored response (if any) match those presented (see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.7</a>), and 845 845 </li> 846 <li>the presented request and stored response are free from directives that would prevent its use (see <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section 3.2</a> and <a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section 3.4</a>), and 846 <li>the presented request does not contain the no-cache pragma (<a href="#header.pragma" id="rfc.xref.header.pragma.1" title="Pragma">Section 3.4</a>), nor the no-cache cache directive (<a href="#cache-request-directive" title="Request Cache-Control Directives">Section 3.2.1</a>), unless the stored response is successfully validated (<a href="#validation.model" title="Validation Model">Section 2.4</a>), and 847 </li> 848 <li>the stored response does not contain the no-cache cache directive (<a href="#cache-response-directive" title="Response Cache-Control Directives">Section 3.2.2</a>), unless it is successfully validated (<a href="#validation.model" title="Validation Model">Section 2.4</a>), and 847 849 </li> 848 850 <li>the stored response is either: … … 891 893 </pre> <p id="rfc.section.2.3.p.6">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>. 892 894 </p> 893 <p id="rfc.section.2.3.p.7">Additionally, clients might need to influence freshness calculation. They can do this using several request cache directives,894 with the effect of either increasing or loosening constraints on freshness. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section 3.2.1</a>.895 <p id="rfc.section.2.3.p.7">Additionally, clients can influence freshness calculation -- either constraining it relaxing it -- by using the max-age and 896 min-fresh request cache directives. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section 3.2.1</a> for details. 895 897 </p> 896 898 <p id="rfc.section.2.3.p.8">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload … … 1674 1676 <td class="left">http</td> 1675 1677 <td class="left">standard</td> 1676 <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control. 3" title="Cache-Control">Section 3.2</a>1678 <td class="left"> <a href="#header.cache-control" id="rfc.xref.header.cache-control.2" title="Cache-Control">Section 3.2</a> 1677 1679 </td> 1678 1680 </tr> … … 2093 2095 </ul> 2094 2096 <h2 id="rfc.section.C.19"><a href="#rfc.section.C.19">C.19</a> <a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p6-cache-17</a></h2> 2095 <p id="rfc.section.C.19.p.1">No changes yet.</p> 2097 <p id="rfc.section.C.19.p.1">Closed issues: </p> 2098 <ul> 2099 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/293">http://tools.ietf.org/wg/httpbis/trac/ticket/293</a>>: "Interaction of request and response Cache-Control" 2100 </li> 2101 </ul> 2096 2102 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2097 2103 <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> … … 2124 2130 <li>cache entry <a href="#rfc.iref.c.4">2</a></li> 2125 2131 <li>cache key <a href="#rfc.iref.c.5">2</a></li> 2126 <li>Cache-Control header field <a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc. xref.header.cache-control.2">2.2</a>, <a href="#rfc.iref.c.6"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.3">5.2</a></li>2132 <li>Cache-Control header field <a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.iref.c.6"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.2">5.2</a></li> 2127 2133 <li>cacheable <a href="#rfc.iref.c.3">1.2</a></li> 2128 2134 </ul> … … 2167 2173 <ul> 2168 2174 <li>Age <a href="#rfc.xref.header.age.1">2.2</a>, <a href="#rfc.xref.header.age.2">2.3.2</a>, <a href="#rfc.iref.h.2"><b>3.1</b></a>, <a href="#rfc.xref.header.age.3">5.2</a></li> 2169 <li>Cache-Control <a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc. xref.header.cache-control.2">2.2</a>, <a href="#rfc.iref.h.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.3">5.2</a></li>2175 <li>Cache-Control <a href="#rfc.xref.header.cache-control.1">2.1</a>, <a href="#rfc.iref.h.3"><b>3.2</b></a>, <a href="#rfc.xref.header.cache-control.2">5.2</a></li> 2170 2176 <li>Expires <a href="#rfc.xref.header.expires.1">2.1</a>, <a href="#rfc.xref.header.expires.2">2.3</a>, <a href="#rfc.xref.header.expires.3">2.3.1</a>, <a href="#rfc.iref.h.4"><b>3.3</b></a>, <a href="#rfc.xref.header.expires.4">5.2</a></li> 2171 2177 <li>Pragma <a href="#rfc.xref.header.pragma.1">2.2</a>, <a href="#rfc.xref.header.pragma.2">3.2</a>, <a href="#rfc.iref.h.5"><b>3.4</b></a>, <a href="#rfc.xref.header.pragma.3">5.2</a></li> -
draft-ietf-httpbis/latest/p6-cache.xml
r1481 r1483 627 627 match those presented (see <xref target="caching.negotiated.responses" 628 628 />), and</t> 629 <t>the presented request and stored response are free from directives 630 that would prevent its use (see <xref target="header.cache-control" /> 631 and <xref target="header.pragma"/>), and</t> 629 <t>the presented request does not contain the no-cache pragma (<xref 630 target="header.pragma"/>), nor the no-cache cache directive (<xref 631 target="cache-request-directive"/>), unless the stored response is 632 successfully validated (<xref target="validation.model"/>), and</t> 633 <t>the stored response does not contain the no-cache cache directive 634 (<xref target="cache-response-directive"/>), unless it is successfully 635 validated (<xref target="validation.model"/>), and</t> 632 636 <t>the stored response is either: 633 637 <list style="symbols"> … … 720 724 </t> 721 725 <t> 722 Additionally, clients might need to influence freshness calculation. They723 c an do this using several request cache directives, with the effect of724 either increasing or loosening constraints on freshness. See <xref725 target="cache-request-directive" />.726 Additionally, clients can influence freshness calculation -- either 727 constraining it relaxing it -- by using the max-age and min-fresh 728 request cache directives. See <xref target="cache-request-directive" /> 729 for details. 726 730 </t> 727 731 <t> … … 2928 2932 <section title="Since draft-ietf-httpbis-p6-cache-17" anchor="changes.since.17"> 2929 2933 <t> 2930 No changes yet. 2934 Closed issues: 2935 <list style="symbols"> 2936 <t> 2937 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/293"/>: 2938 "Interaction of request and response Cache-Control" 2939 </t> 2940 </list> 2931 2941 </t> 2932 2942 </section>
Note: See TracChangeset
for help on using the changeset viewer.