Changeset 1682 for draft-ietf-httpbis/latest/p4-conditional.html
- Timestamp:
- 21/06/12 09:01:49 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p4-conditional.html
r1667 r1682 449 449 } 450 450 @bottom-center { 451 content: "Expires December 3, 2012";451 content: "Expires December 23, 2012"; 452 452 } 453 453 @bottom-right { … … 490 490 <meta name="dct.creator" content="Reschke, J. F."> 491 491 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 492 <meta name="dct.issued" scheme="ISO8601" content="2012-06- 01">492 <meta name="dct.issued" scheme="ISO8601" content="2012-06-21"> 493 493 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 494 494 <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 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 516 516 </tr> 517 517 <tr> 518 <td class="left">Expires: December 3, 2012</td>518 <td class="left">Expires: December 23, 2012</td> 519 519 <td class="right">J. Reschke, Editor</td> 520 520 </tr> … … 525 525 <tr> 526 526 <td class="left"></td> 527 <td class="right">June 1, 2012</td>527 <td class="right">June 21, 2012</td> 528 528 </tr> 529 529 </tbody> … … 555 555 in progress”. 556 556 </p> 557 <p>This Internet-Draft will expire on December 3, 2012.</p>557 <p>This Internet-Draft will expire on December 23, 2012.</p> 558 558 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 559 559 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 658 658 <p id="rfc.section.1.1.p.4">This document also uses ABNF to define valid protocol elements (<a href="#notation" title="Syntax Notation">Section 1.2</a>). In addition to the prose requirements placed upon them, Senders <em class="bcp14">MUST NOT</em> generate protocol elements that are invalid. 659 659 </p> 660 <p id="rfc.section.1.1.p.5">Unless noted otherwise, Recipients <em class="bcp14">M AY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling660 <p id="rfc.section.1.1.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 661 661 mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require 662 662 different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the … … 1339 1339 </p> 1340 1340 <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> <a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p4-conditional-19</a></h2> 1341 <p id="rfc.section.C.1.p.1">None yet.</p> 1341 <p id="rfc.section.C.1.p.1">Closed issues: </p> 1342 <ul> 1343 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>>: "ABNF requirements for recipients" 1344 </li> 1345 </ul> 1342 1346 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1343 1347 <p class="noprint"><a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a>
Note: See TracChangeset
for help on using the changeset viewer.