Changeset 827
- Timestamp:
- 07/06/10 11:29:53 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r826 r827 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-06-0 2">404 <meta name="dct.issued" scheme="ISO8601" content="2010-06-07"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. 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."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: December 4, 2010</td>430 <td class="left">Expires: December 9, 2010</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">June 2, 2010</td>491 <td class="right">June 7, 2010</td> 492 492 </tr> 493 493 </tbody> … … 515 515 in progress”. 516 516 </p> 517 <p>This Internet-Draft will expire in December 4, 2010.</p>517 <p>This Internet-Draft will expire in December 9, 2010.</p> 518 518 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 519 519 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1030 1030 <div id="rfc.iref.h.3"></div> 1031 1031 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="header.cache-control" href="#header.cache-control">Cache-Control</a></h2> 1032 <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives that <em class="bcp14">MUST</em> be obeyed by all caches along the request/response chain. Such cache directives are unidirectional in that the presence of 1033 a directive in a request does not imply that the same directive is to be given in the response. 1034 </p> 1035 <div class="note" id="rfc.section.3.2.p.2"> 1032 <p id="rfc.section.3.2.p.1">The "Cache-Control" general-header field is used to specify directives for caches along the request/response chain. Such cache 1033 directives are unidirectional in that the presence of a directive in a request does not imply that the same directive is to 1034 be given in the response. 1035 </p> 1036 <p id="rfc.section.3.2.p.2">HTTP/1.1 caches <em class="bcp14">MUST</em> obey the requirements of the Cache-Control directives defined in this section. See <a href="#cache.control.extensions" title="Cache Control Extensions">Section 3.2.3</a> for information about how Cache-Control directives defined elsewhere are handled. 1037 </p> 1038 <div class="note" id="rfc.section.3.2.p.3"> 1036 1039 <p> <b>Note:</b> HTTP/1.0 caches might not implement Cache-Control and might only implement Pragma: no-cache (see <a href="#header.pragma" id="rfc.xref.header.pragma.2" title="Pragma">Section 3.4</a>). 1037 1040 </p> 1038 1041 </div> 1039 <p id="rfc.section.3.2.p. 3">Cache directives <em class="bcp14">MUST</em> be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives1042 <p id="rfc.section.3.2.p.4">Cache directives <em class="bcp14">MUST</em> be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives 1040 1043 might be applicable to all recipients along the request/response chain. It is not possible to target a directive to a specific 1041 1044 cache. … … 1883 1886 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/29">http://tools.ietf.org/wg/httpbis/trac/ticket/29</a>>: "Age calculation" 1884 1887 </li> 1888 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/168">http://tools.ietf.org/wg/httpbis/trac/ticket/168</a>>: "Clarify differences between / requirements for request and response CC directives" 1889 </li> 1885 1890 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/208">http://tools.ietf.org/wg/httpbis/trac/ticket/208</a>>: "IANA registry for cache-control directives" 1886 1891 </li> -
draft-ietf-httpbis/latest/p6-cache.xml
r826 r827 977 977 <x:anchor-alias value="cache-response-directive"/> 978 978 <t> 979 The "Cache-Control" general-header field is used to specify directives that 980 &MUST; be obeyed by all caches along the request/response chain. Such cache 981 directives are unidirectional in that the presence of a directive in a 982 request does not imply that the same directive is to be given in the 983 response. 979 The "Cache-Control" general-header field is used to specify directives for 980 caches along the request/response chain. Such cache directives are 981 unidirectional in that the presence of a directive in a request does not 982 imply that the same directive is to be given in the response. 983 </t> 984 <t> 985 HTTP/1.1 caches &MUST; obey the requirements of the Cache-Control directives 986 defined in this section. See <xref target="cache.control.extensions"/> for 987 information about how Cache-Control directives defined elsewhere are handled. 984 988 </t> 985 989 <x:note> … … 2463 2467 </t> 2464 2468 <t> 2469 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/168" />: 2470 "Clarify differences between / requirements for request and response CC directives" 2471 </t> 2472 <t> 2465 2473 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/208" />: 2466 2474 "IANA registry for cache-control directives"
Note: See TracChangeset
for help on using the changeset viewer.