Changeset 732 for draft-ietf-httpbis/latest
- Timestamp:
- 07/12/09 17:46:53 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r729 r732 402 402 <meta name="DC.Creator" content="Reschke, J. F."> 403 403 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-12-0 1">404 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-12-07"> 405 405 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="DC.Description.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."> … … 435 435 </tr> 436 436 <tr> 437 <td class="left">Expires: June 4, 2010</td>437 <td class="left">Expires: June 10, 2010</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 492 492 <tr> 493 493 <td class="left"></td> 494 <td class="right">December 1, 2009</td>494 <td class="right">December 7, 2009</td> 495 495 </tr> 496 496 </tbody> … … 522 522 <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. 523 523 </p> 524 <p>This Internet-Draft will expire in June 4, 2010.</p>524 <p>This Internet-Draft will expire in June 10, 2010.</p> 525 525 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 526 526 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 771 771 <p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request, caches <em class="bcp14">MUST</em> include a single Age header field (<a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section 3.1</a>) in the response with a value equal to the stored response's current_age; see <a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>. <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: DISCUSS: this currently includes successfully validated responses.]</span> 772 772 </p> 773 <p id="rfc.section.2.2.p.4">Requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) <em class="bcp14">MUST</em> be written through the cache to the origin server; i.e., Acache must not reply to such a request before having forwarded773 <p id="rfc.section.2.2.p.4">Requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) <em class="bcp14">MUST</em> be written through the cache to the origin server; i.e., a cache must not reply to such a request before having forwarded 774 774 the request and having received a corresponding response. 775 775 </p> … … 1111 1111 <li> <b>Note:</b> This usage of the word private only controls where the response may be stored, and cannot ensure the privacy of the message 1112 1112 content. Also, private response directives with field-names are often handled by implementations as if an unqualified private 1113 directive was rec ieved; i.e., the special handling for the qualified form is not widely implemented.1113 directive was received; i.e., the special handling for the qualified form is not widely implemented. 1114 1114 </li> 1115 1115 </ul> … … 1249 1249 <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a> <a id="header.vary" href="#header.vary">Vary</a></h2> 1250 1250 <p id="rfc.section.3.5.p.1">The "Vary" response-header field conveys the set of request-header fields that were used to select the representation.</p> 1251 <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satis dy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.6</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request1251 <p id="rfc.section.3.5.p.2">Caches use this information, in part, to determine whether a stored response can be used to satisfy a given request; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.6</a>. determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request 1252 1252 without validation; see <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.6</a>. 1253 1253 </p> … … 1278 1278 </p> 1279 1279 <p id="rfc.section.3.6.p.2">Warnings can be used for other purposes, both cache-related and otherwise. The use of a warning, rather than an error status 1280 code, distinguish these responses from true failures.1280 code, distinguishes these responses from true failures. 1281 1281 </p> 1282 1282 <p id="rfc.section.3.6.p.3">Warning headers can in general be applied to any message, however some warn-codes are specific to caches and can only be applied -
draft-ietf-httpbis/latest/p6-cache.xml
r729 r732 495 495 <t> 496 496 Requests with methods that are unsafe (&safe-methods;) &MUST; be written through the cache to 497 the origin server; i.e., Acache must not reply to such a request before having forwarded the request and having received a497 the origin server; i.e., a cache must not reply to such a request before having forwarded the request and having received a 498 498 corresponding response. 499 499 </t> … … 1104 1104 be stored, and cannot ensure the privacy of the message content. 1105 1105 Also, private response directives with field-names are often handled by 1106 implementations as if an unqualified private directive was rec ieved; i.e.,1106 implementations as if an unqualified private directive was received; i.e., 1107 1107 the special handling for the qualified form is not widely implemented. 1108 1108 </t> … … 1345 1345 <t> 1346 1346 Caches use this information, in part, to determine whether a stored response 1347 can be used to satis dy a given request; see1347 can be used to satisfy a given request; see 1348 1348 <xref target="caching.negotiated.responses" />. 1349 1349 determines, while the response is fresh, whether a cache is permitted to use the … … 1403 1403 <t> 1404 1404 Warnings can be used for other purposes, both cache-related and otherwise. The use of a 1405 warning, rather than an error status code, distinguish these responses from true failures.1405 warning, rather than an error status code, distinguishes these responses from true failures. 1406 1406 </t> 1407 1407 <t>
Note: See TracChangeset
for help on using the changeset viewer.