Changeset 1675 for draft-ietf-httpbis
- Timestamp:
- 11/06/12 13:29:02 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1667 r1675 452 452 } 453 453 @bottom-center { 454 content: "Expires December 3, 2012";454 content: "Expires December 13, 2012"; 455 455 } 456 456 @bottom-right { … … 494 494 <meta name="dct.creator" content="Reschke, J. F."> 495 495 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 496 <meta name="dct.issued" scheme="ISO8601" content="2012-06- 01">496 <meta name="dct.issued" scheme="ISO8601" content="2012-06-11"> 497 497 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 498 498 <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."> … … 520 520 </tr> 521 521 <tr> 522 <td class="left">Expires: December 3, 2012</td>522 <td class="left">Expires: December 13, 2012</td> 523 523 <td class="right">M. Nottingham, Editor</td> 524 524 </tr> … … 537 537 <tr> 538 538 <td class="left"></td> 539 <td class="right">June 1 , 2012</td>539 <td class="right">June 11, 2012</td> 540 540 </tr> 541 541 </tbody> … … 567 567 in progress”. 568 568 </p> 569 <p>This Internet-Draft will expire on December 3, 2012.</p>569 <p>This Internet-Draft will expire on December 13, 2012.</p> 570 570 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 571 571 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1112 1112 </p> 1113 1113 <p id="rfc.section.2.5.p.3">If the Content-Length, ETag and Last-Modified values of a HEAD response (when present) are the same as that in a selected 1114 GET response (as per <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.8</a>), the cache SHOULDupdate the remaining headers in the stored response using the following rules:1114 GET response (as per <a href="#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.8</a>), the cache <em class="bcp14">SHOULD</em> update the remaining headers in the stored response using the following rules: 1115 1115 </p> 1116 1116 <ul> … … 1338 1338 stale responses. 1339 1339 </li> 1340 <li>If the no-cache response directive specifies one or more field-names, then a cache MAY use the response to satisfy a subsequent 1341 request, subject to any other restrictions on caching. However, any header fields in the response that have the field-name(s) 1342 listed <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin 1340 <li>If the no-cache response directive specifies one or more field-names, then a cache <em class="bcp14">MAY</em> use the response to satisfy a subsequent request, subject to any other restrictions on caching. However, any header fields 1341 in the response that have the field-name(s) listed <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful revalidation with the origin server. This allows an origin 1343 1342 server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response. 1344 1343 </li> -
draft-ietf-httpbis/latest/p6-cache.xml
r1667 r1675 986 986 If the Content-Length, ETag and Last-Modified values of a HEAD response 987 987 (when present) are the same as that in a selected GET response (as per 988 <xref target="caching.negotiated.responses"/>), the cache SHOULDupdate the988 <xref target="caching.negotiated.responses"/>), the cache &SHOULD; update the 989 989 remaining headers in the stored response using the following rules: 990 990 <list style="symbols"> … … 1399 1399 have been configured to return stale responses.</t> 1400 1400 <t>If the no-cache response directive specifies one or more field-names, 1401 then a cache MAYuse the response to satisfy a subsequent request,1401 then a cache &MAY; use the response to satisfy a subsequent request, 1402 1402 subject to any other restrictions on caching. However, any header fields 1403 1403 in the response that have the field-name(s) listed &MUST-NOT; be sent
Note: See TracChangeset
for help on using the changeset viewer.