Changeset 1287
- Timestamp:
- 20/05/11 07:06:38 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1283 r1287 359 359 } 360 360 @bottom-center { 361 content: "Expires November 2 0, 2011";361 content: "Expires November 21, 2011"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-05- 19">411 <meta name="dct.issued" scheme="ISO8601" content="2011-05-20"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 413 413 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields."> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: November 2 0, 2011</td>442 <td class="left">Expires: November 21, 2011</td> 443 443 <td class="right">HP</td> 444 444 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">May 19, 2011</td>495 <td class="right">May 20, 2011</td> 496 496 </tr> 497 497 </tbody> … … 522 522 in progress”. 523 523 </p> 524 <p>This Internet-Draft will expire on November 2 0, 2011.</p>524 <p>This Internet-Draft will expire on November 21, 2011.</p> 525 525 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 526 526 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p6-cache.html
r1284 r1287 837 837 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>. 838 838 </p> 839 <p id="rfc.section.2.3.p.8"> <span class="comment" id="ISSUE-no-req-for-directives">[<a href="#ISSUE-no-req-for-directives" class="smpl">ISSUE-no-req-for-directives</a>: there are not requirements directly applying to cache-request-directives and freshness.]</span> 840 </p> 841 <p id="rfc.section.2.3.p.9">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload 839 <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 842 840 a resource. See <a href="#history.lists" title="History Lists">Section 4</a> for an explanation of the difference between caches and history mechanisms. 843 841 </p> … … 1266 1264 it will also see and understand the private directive and thus default to the safe behavior. 1267 1265 </p> 1268 <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> beignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache1266 <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache 1269 1267 will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain 1270 1268 minimally correct even if the cache does not understand the extension(s). … … 1324 1322 Cache-Control: max-age=30 1325 1323 Pragma: no-cache 1324 1326 1325 </pre> <p id="rfc.section.3.4.p.7">will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while precluding implementations that do not 1327 1326 understand Cache-Control from serving a cached response. 1328 1327 </p> 1329 1328 <div class="note" id="rfc.section.3.4.p.8"> 1330 <p> Note: Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement1331 for "Cache-Control:no-cache" in them.1329 <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control: 1330 no-cache" in them. 1332 1331 </p> 1333 1332 </div> -
draft-ietf-httpbis/latest/p6-cache.xml
r1286 r1287 1498 1498 <x:anchor-alias value="pragma-directive"/> 1499 1499 <t> 1500 1500 The "Pragma" header field allows backwards compatibility with HTTP/1.0 1501 1501 caches, so that clients can specify a "no-cache" request that they will 1502 1502 understand (as Cache-Control was not defined until HTTP/1.1). When the … … 1505 1505 </t> 1506 1506 <t> 1507 1507 In HTTP/1.0, Pragma was defined as an extensible field for 1508 1508 implementation-specified directives for recipients. This specification 1509 1509 deprecates such extensions to improve interoperability. … … 1515 1515 </artwork></figure> 1516 1516 <t> 1517 1517 When the Cache-Control header is not present in a request, the no-cache 1518 1518 request pragma-directive &MUST; have the same effect on caches as if 1519 1519 "Cache-Control: no-cache" were present (see <xref … … 1527 1527 </t> 1528 1528 <figure> 1529 <artwork type=" code">1529 <artwork type="message/http; msgtype="response"" x:indent-with=" "> 1530 1530 GET / HTTP/1.1 1531 1531 Host: www.example.com 1532 1532 Cache-Control: max-age=30 1533 1533 Pragma: no-cache 1534 1534 1535 </artwork> 1535 1536 </figure> … … 1541 1542 <x:note> 1542 1543 <t> 1543 Note:Because the meaning of "Pragma: no-cache" in responses is not1544 <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" in responses is not 1544 1545 specified, it does not provide a reliable replacement for 1545 1546 "Cache-Control: no-cache" in them. 1546 1547 </t> 1547 1548 </x:note> 1548 1549 </section> … … 2601 2602 "Clarify differences between / requirements for request and response CC directives" 2602 2603 </t> 2603 2604 2605 2606 2604 <t> 2605 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/174" />: 2606 "Caching authenticated responses" 2607 </t> 2607 2608 <t> 2608 2609 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/208" />: … … 2696 2697 <t> 2697 2698 Closed issues: 2698 2699 2700 2701 2702 2703 2699 <list style="symbols"> 2700 <t> 2701 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/292"/>: 2702 "Pragma" 2703 </t> 2704 </list> 2704 2705 </t> 2705 2706 </section>
Note: See TracChangeset
for help on using the changeset viewer.