Changeset 1684 for draft-ietf-httpbis/latest/p6-cache.html
- Timestamp:
- 22/06/12 07:12:17 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r1682 r1684 452 452 } 453 453 @bottom-center { 454 content: "Expires December 2 3, 2012";454 content: "Expires December 24, 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-2 1">496 <meta name="dct.issued" scheme="ISO8601" content="2012-06-22"> 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 2 3, 2012</td>522 <td class="left">Expires: December 24, 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 2 1, 2012</td>539 <td class="right">June 22, 2012</td> 540 540 </tr> 541 541 </tbody> … … 567 567 in progress”. 568 568 </p> 569 <p>This Internet-Draft will expire on December 2 3, 2012.</p>569 <p>This Internet-Draft will expire on December 24, 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> … … 774 774 <p id="rfc.section.1.3.p.5">Unless noted otherwise, Recipients <em class="bcp14">MUST</em> be able to parse all protocol elements matching the ABNF rules defined for them and <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling 775 775 mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require 776 different error handling strategies; for example, a Web browser m ay wish to transparently recover from a response where the777 Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type of778 error recovery could lead to dangerous consequences.776 different error handling strategies; for example, a Web browser might wish to transparently recover from a response where 777 the Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type 778 of error recovery could lead to dangerous consequences. 779 779 </p> 780 780 <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a> <a id="notation" href="#notation">Syntax Notation</a></h2>
Note: See TracChangeset
for help on using the changeset viewer.