Changeset 1682 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 21/06/12 09:01:49 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1680 r1682 449 449 } 450 450 @bottom-center { 451 content: "Expires December 2 2, 2012";451 content: "Expires December 23, 2012"; 452 452 } 453 453 @bottom-right { … … 497 497 <meta name="dct.creator" content="Reschke, J. F."> 498 498 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 499 <meta name="dct.issued" scheme="ISO8601" content="2012-06-2 0">499 <meta name="dct.issued" scheme="ISO8601" content="2012-06-21"> 500 500 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 501 501 <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 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. Furthermore, it defines HTTP message content, metadata, and content negotiation."> … … 528 528 </tr> 529 529 <tr> 530 <td class="left">Expires: December 2 2, 2012</td>530 <td class="left">Expires: December 23, 2012</td> 531 531 <td class="right">greenbytes</td> 532 532 </tr> 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">June 2 0, 2012</td>535 <td class="right">June 21, 2012</td> 536 536 </tr> 537 537 </tbody> … … 552 552 <p>The current issues list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. 553 553 </p> 554 <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p2-semantics-19 ">Appendix E.40</a>.554 <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p2-semantics-19 and draft-ietf-httpbis-p3-payload-19">Appendix E.40</a>. 555 555 </p> 556 556 <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1> … … 563 563 in progress”. 564 564 </p> 565 <p>This Internet-Draft will expire on December 2 2, 2012.</p>565 <p>This Internet-Draft will expire on December 23, 2012.</p> 566 566 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 567 567 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 807 807 <li>E.38 <a href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></li> 808 808 <li>E.39 <a href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></li> 809 <li>E.40 <a href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19</a></li> 810 <li>E.41 <a href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></li> 809 <li>E.40 <a href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19 and draft-ietf-httpbis-p3-payload-19</a></li> 811 810 </ul> 812 811 </li> … … 857 856 <p id="rfc.section.1.2.p.4">This document also uses ABNF to define valid protocol elements (<a href="#notation" title="Syntax Notation">Section 1.3</a>). In addition to the prose requirements placed upon them, Senders <em class="bcp14">MUST NOT</em> generate protocol elements that are invalid. 858 857 </p> 859 <p id="rfc.section.1.2.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 handling858 <p id="rfc.section.1.2.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 860 859 mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require 861 860 different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the … … 4729 4728 </li> 4730 4729 </ul> 4731 <h2 id="rfc.section.E.40"><a href="#rfc.section.E.40">E.40</a> <a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19 </a></h2>4730 <h2 id="rfc.section.E.40"><a href="#rfc.section.E.40">E.40</a> <a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19 and draft-ietf-httpbis-p3-payload-19</a></h2> 4732 4731 <p id="rfc.section.E.40.p.1">Closed issues: </p> 4733 4732 <ul> 4734 4733 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/312">http://tools.ietf.org/wg/httpbis/trac/ticket/312</a>>: "should there be a permanent variant of 307" 4735 4734 </li> 4736 </ul>4737 <h2 id="rfc.section.E.41"><a href="#rfc.section.E.41">E.41</a> <a id="changes.3.since.19" href="#changes.3.since.19">Since draft-ietf-httpbis-p3-payload-19</a></h2>4738 < p id="rfc.section.E.41.p.1">None yet.</p>4735 <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" 4736 </li> 4737 </ul> 4739 4738 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 4740 4739 <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</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.O">O</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.T">T</a> <a href="#rfc.index.U">U</a>
Note: See TracChangeset
for help on using the changeset viewer.