Changeset 1682 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 21/06/12 09:01:49 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1677 r1682 449 449 } 450 450 @bottom-center { 451 content: "Expires December 17, 2012";451 content: "Expires December 23, 2012"; 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-06- 15">493 <meta name="dct.issued" scheme="ISO8601" content="2012-06-21"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: December 17, 2012</td>525 <td class="left">Expires: December 23, 2012</td> 526 526 <td class="right">greenbytes</td> 527 527 </tr> 528 528 <tr> 529 529 <td class="left"></td> 530 <td class="right">June 15, 2012</td>530 <td class="right">June 21, 2012</td> 531 531 </tr> 532 532 </tbody> … … 561 561 in progress”. 562 562 </p> 563 <p>This Internet-Draft will expire on December 17, 2012.</p>563 <p>This Internet-Draft will expire on December 23, 2012.</p> 564 564 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 565 565 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 959 959 <p id="rfc.section.2.5.p.3">Senders <em class="bcp14">MUST NOT</em> generate protocol elements that do not match the grammar defined by the ABNF rules for those protocol elements. 960 960 </p> 961 <p id="rfc.section.2.5.p.4">Unless otherwise noted, recipients<em class="bcp14">MAY</em> attempt to recover a usable protocol element from an invalid construct. HTTP does not define specific error handling mechanisms961 <p id="rfc.section.2.5.p.4">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> attempt to recover a usable protocol element from an invalid construct. HTTP does not define specific error handling mechanisms 962 962 except when they have a direct impact on security, since different applications of the protocol require different error handling 963 963 strategies. For example, a Web browser might wish to transparently recover from a response where the Location header field … … 3530 3530 <ul> 3531 3531 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>>: "make IANA policy definitions consistent" 3532 </li> 3533 <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" 3532 3534 </li> 3533 3535 </ul>
Note: See TracChangeset
for help on using the changeset viewer.