Changeset 1891 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 13/09/12 11:44:49 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1888 r1891 449 449 } 450 450 @bottom-center { 451 content: "Expires March 1 6, 2013";451 content: "Expires March 17, 2013"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2012-09-1 2">494 <meta name="dct.issued" scheme="ISO8601" content="2012-09-13"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 496 496 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: March 1 6, 2013</td>526 <td class="left">Expires: March 17, 2013</td> 527 527 <td class="right">greenbytes</td> 528 528 </tr> 529 529 <tr> 530 530 <td class="left"></td> 531 <td class="right">September 1 2, 2012</td>531 <td class="right">September 13, 2012</td> 532 532 </tr> 533 533 </tbody> … … 556 556 in progress”. 557 557 </p> 558 <p>This Internet-Draft will expire on March 1 6, 2013.</p>558 <p>This Internet-Draft will expire on March 17, 2013.</p> 559 559 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 560 560 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2860 2860 digits due to the fact that implementations are known to handle multi-digit version numbers incorrectly. (<a href="#http.version" title="Protocol Versioning">Section 2.6</a>) 2861 2861 </p> 2862 <p id="rfc.section.A.2.p.2">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk 2863 form is allowed for the OPTIONS request method only. (<a href="#request-target" title="Request Target">Section 5.3</a>) 2864 </p> 2865 <p id="rfc.section.A.2.p.3">Require that invalid whitespace around field-names be rejected. (<a href="#header.fields" title="Header Fields">Section 3.2</a>) 2866 </p> 2867 <p id="rfc.section.A.2.p.4">Rules about implicit linear whitespace between certain grammar productions have been removed; now whitespace is only allowed 2862 <p id="rfc.section.A.2.p.2">Require that invalid whitespace around field-names be rejected. Change ABNF productions for header fields to only define the 2863 field value. (<a href="#header.fields" title="Header Fields">Section 3.2</a>) 2864 </p> 2865 <p id="rfc.section.A.2.p.3">Rules about implicit linear whitespace between certain grammar productions have been removed; now whitespace is only allowed 2868 2866 where specifically defined in the ABNF. (<a href="#whitespace" title="Whitespace">Section 3.2.1</a>) 2869 2867 </p> 2870 <p id="rfc.section.A.2.p. 5">The NUL octet is no longer allowed in comment and quoted-string text. The quoted-pair rule no longer allows escaping control2868 <p id="rfc.section.A.2.p.4">The NUL octet is no longer allowed in comment and quoted-string text. The quoted-pair rule no longer allows escaping control 2871 2869 characters other than HTAB. Non-ASCII content in header fields and reason phrase has been obsoleted and made opaque (the TEXT 2872 2870 rule was removed). (<a href="#field.components" title="Field value components">Section 3.2.4</a>) 2873 2871 </p> 2874 <p id="rfc.section.A.2.p.6">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix B</a>) 2875 </p> 2876 <p id="rfc.section.A.2.p.7">Require recipients to handle bogus <a href="#header.content-length" class="smpl">Content-Length</a> header fields as errors. (<a href="#message.body" title="Message Body">Section 3.3</a>) 2877 </p> 2878 <p id="rfc.section.A.2.p.8">Remove reference to non-existent identity transfer-coding value tokens. (Sections <a href="#message.body" title="Message Body">3.3</a> and <a href="#transfer.codings" title="Transfer Codings">4</a>) 2879 </p> 2880 <p id="rfc.section.A.2.p.9">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. Furthermore 2872 <p id="rfc.section.A.2.p.5">Require recipients to handle bogus "<a href="#header.content-length" class="smpl">Content-Length</a>" header fields as errors. (<a href="#message.body" title="Message Body">Section 3.3</a>) 2873 </p> 2874 <p id="rfc.section.A.2.p.6">Remove reference to non-existent identity transfer-coding value tokens. (Sections <a href="#message.body" title="Message Body">3.3</a> and <a href="#transfer.codings" title="Transfer Codings">4</a>) 2875 </p> 2876 <p id="rfc.section.A.2.p.7">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. Furthermore 2881 2877 disallowed line folding in chunk extensions, and deprecate their use. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a>) 2882 2878 </p> 2883 <p id="rfc.section.A.2.p.10">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section 7.4</a>) 2884 </p> 2885 <p id="rfc.section.A.2.p.11">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent. 2879 <p id="rfc.section.A.2.p.8">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk 2880 form is allowed for the OPTIONS request method only. (<a href="#request-target" title="Request Target">Section 5.3</a>) 2881 </p> 2882 <p id="rfc.section.A.2.p.9">Clarify exactly when "close" connection options have to be sent; drop notion of header fields being "hop-by-hop" without being 2883 listed in the Connection header field. (<a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section 6.1</a>) 2884 </p> 2885 <p id="rfc.section.A.2.p.10">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent. 2886 2886 Remove requirements about when servers are allowed to close connections prematurely. (<a href="#persistent.connections" title="Persistent Connections">Section 6.2</a>) 2887 2887 </p> 2888 <p id="rfc.section.A.2.p.1 2">Remove requirement to retry requests under certain circumstances when the server prematurely closes the connection. (<a href="#persistent.reuse" title="Reuse">Section 6.2.2</a>)2889 </p> 2890 <p id="rfc.section.A.2.p.1 3">Change ABNF productions for header fields to only define the field value.</p>2891 < p id="rfc.section.A.2.p.14">Clarify exactly when "close" connection options have to be sent; drop notion of header fields being "hop-by-hop" without being2892 listed in the Connection header field. (<a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section 6.1</a>)2893 </p> 2894 <p id="rfc.section.A.2.p.1 5">Define the semantics of the <a href="#header.upgrade" class="smpl">Upgrade</a> header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section 6.3</a>)2895 </p> 2896 <p id="rfc.section.A.2.p.1 6">Take over the Upgrade Token Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.2">Section 7.2</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#upgrade.token.registry" title="Upgrade Token Registry">Section 7.6</a>)2888 <p id="rfc.section.A.2.p.11">Remove requirement to retry requests under certain circumstances when the server prematurely closes the connection. (<a href="#persistent.reuse" title="Reuse">Section 6.2.2</a>) 2889 </p> 2890 <p id="rfc.section.A.2.p.12">Define the semantics of the <a href="#header.upgrade" class="smpl">Upgrade</a> header field in responses other than 101 (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section 6.3</a>) 2891 </p> 2892 <p id="rfc.section.A.2.p.13">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section 7.4</a>) 2893 </p> 2894 <p id="rfc.section.A.2.p.14">Take over the Upgrade Token Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.2">Section 7.2</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#upgrade.token.registry" title="Upgrade Token Registry">Section 7.6</a>) 2895 </p> 2896 <p id="rfc.section.A.2.p.15">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix B</a>) 2897 2897 </p> 2898 2898 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="abnf.extension" href="#abnf.extension">ABNF list extension: #rule</a></h1>
Note: See TracChangeset
for help on using the changeset viewer.