Changeset 1563 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 06/03/12 01:40:47 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1560 r1563 463 463 } 464 464 @bottom-center { 465 content: "Expires September 5, 2012";465 content: "Expires September 7, 2012"; 466 466 } 467 467 @bottom-right { … … 498 498 <link href="p5-range.html" rel="prev"> 499 499 <link href="p7-auth.html" rel="next"> 500 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.570, 2012-02-13 19:17:35, XSLT vendor: SAXON 8.9from Saxonica http://www.saxonica.com/">500 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.570, 2012-02-13 19:17:35, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/"> 501 501 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 502 502 <meta name="dct.creator" content="Fielding, R."> … … 511 511 <meta name="dct.creator" content="Reschke, J. F."> 512 512 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 513 <meta name="dct.issued" scheme="ISO8601" content="2012-03-0 4">513 <meta name="dct.issued" scheme="ISO8601" content="2012-03-06"> 514 514 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 515 515 <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."> … … 537 537 </tr> 538 538 <tr> 539 <td class="left">Expires: September 5, 2012</td>539 <td class="left">Expires: September 7, 2012</td> 540 540 <td class="right">J. Mogul</td> 541 541 </tr> … … 602 602 <tr> 603 603 <td class="left"></td> 604 <td class="right">March 4, 2012</td>604 <td class="right">March 6, 2012</td> 605 605 </tr> 606 606 </tbody> … … 632 632 in progress”. 633 633 </p> 634 <p>This Internet-Draft will expire on September 5, 2012.</p>634 <p>This Internet-Draft will expire on September 7, 2012.</p> 635 635 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 636 636 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1419 1419 stale responses. 1420 1420 </li> 1421 <li>If the no-cache response directive specifies one or more field-names, th is requirement is limited to the field-values associated1422 with the listed response header fields. That is, a cache <em class="bcp14">MUST NOT</em> send the specified field-name(s) in the response to a subsequent request without successful validation on the origin server.1423 This allows an origin server to prevent the re-use of certain header fields in a response, while still allowing caching of1424 the rest of the response.1421 <li>If the no-cache response directive specifies one or more field-names, then a cache MAY use the response to satisfy a subsequent 1422 request, subject to any other restrictions on caching. However, any header fields in the response that have the field-name(s) 1423 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 1424 server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response. 1425 1425 </li> 1426 1426 <li> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
Note: See TracChangeset
for help on using the changeset viewer.