Changeset 2004
- Timestamp:
- 28/11/12 08:05:31 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2003 r2004 449 449 } 450 450 @bottom-center { 451 content: "Expires May 31, 2013";451 content: "Expires June 1, 2013"; 452 452 } 453 453 @bottom-right { … … 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2012-11-2 7">493 <meta name="dct.issued" scheme="ISO8601" content="2012-11-28"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 520 520 <tr> 521 521 <td class="left">Intended status: Standards Track</td> 522 <td class="right">November 2 7, 2012</td>522 <td class="right">November 28, 2012</td> 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: May 31, 2013</td>525 <td class="left">Expires: June 1, 2013</td> 526 526 <td class="right"></td> 527 527 </tr> … … 551 551 in progress”. 552 552 </p> 553 <p>This Internet-Draft will expire on May 31, 2013.</p>553 <p>This Internet-Draft will expire on June 1, 2013.</p> 554 554 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 555 555 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 928 928 can be used for a particular request. HTTP requirements for cache behavior and cacheable responses are defined in <a href="p6-cache.html#caching.overview" title="Overview of Cache Operation">Section 2</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>. 929 929 </p> 930 <p id="rfc.section.2.4.p.5">There are a wide variety of architectures and configurations of caches and proxies deployed across the World Wide Web and931 inside large organizations. These systems include national hierarchies of proxy caches to save transoceanic bandwidth, systems932 that broadcast or multicast cache entries, organizations that distribute subsets of cached data via optical media, and so933 on.930 <p id="rfc.section.2.4.p.5">There are a wide variety of architectures and configurations of caches deployed across the World Wide Web and inside large 931 organizations. These include national hierarchies of proxy caches to save transoceanic bandwidth, collaborative systems that 932 broadcast or multicast cache entries, archives of pre-fetched cache entries for use in off-line or high-latency environments, 933 and so on. 934 934 </p> 935 935 <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a> <a id="conformance" href="#conformance">Conformance and Error Handling</a></h2> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2003 r2004 591 591 <t> 592 592 There are a wide variety of architectures and configurations 593 of caches and proxiesdeployed across the World Wide Web and594 inside large organizations. These systemsinclude national hierarchies595 of proxy caches to save transoceanic bandwidth, systems that596 broadcast or multicast cache entries, organizations that distribute597 subsets of cached data via optical media, and so on.593 of caches deployed across the World Wide Web and 594 inside large organizations. These include national hierarchies 595 of proxy caches to save transoceanic bandwidth, collaborative systems that 596 broadcast or multicast cache entries, archives of pre-fetched cache 597 entries for use in off-line or high-latency environments, and so on. 598 598 </t> 599 599 </section>
Note: See TracChangeset
for help on using the changeset viewer.