![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 2006
- Timestamp:
- 28/11/12 12:24:43 (8 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
-
p1-messaging.html (modified) (3 diffs)
-
p1-messaging.xml (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2005 r2006 2827 2827 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>) 2828 2828 </p> 2829 <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 2829 <p id="rfc.section.A.2.p.2">Take over the definition of "HTTPS" URI scheme, previously defined in <a href="http://tools.ietf.org/html/rfc2818#section-2.4">Section 2.4</a> of <a href="#RFC2818" id="rfc.xref.RFC2818.3"><cite title="HTTP Over TLS">[RFC2818]</cite></a>. (<a href="#https.uri" title="https URI scheme">Section 2.7.2</a>) 2830 </p> 2831 <p id="rfc.section.A.2.p.3">Require that invalid whitespace around field-names be rejected. Change ABNF productions for header fields to only define the 2830 2832 field value. (<a href="#header.fields" title="Header Fields">Section 3.2</a>) 2831 2833 </p> 2832 <p id="rfc.section.A.2.p. 3">Rules about implicit linear whitespace between certain grammar productions have been removed; now whitespace is only allowed2834 <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 2833 2835 where specifically defined in the ABNF. (<a href="#whitespace" title="Whitespace">Section 3.2.1</a>) 2834 2836 </p> 2835 <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 control2837 <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 control 2836 2838 characters other than HTAB. Non-ASCII content in header fields and reason phrase has been obsoleted and made opaque (the TEXT 2837 2839 rule was removed). (<a href="#field.components" title="Field value components">Section 3.2.4</a>) 2838 2840 </p> 2839 <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="#header.content-length" id="rfc.xref.header.content-length.2" title="Content-Length">Section 3.3.2</a>)2840 </p> 2841 <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>)2842 </p> 2843 <p id="rfc.section.A.2.p. 7">Remove special-case for "multipart/byteranges" in message body length detection; add CONNECT as special case. (<a href="#message.body.length" title="Message Body Length">Section 3.3.3</a>)2844 </p> 2845 <p id="rfc.section.A.2.p. 8">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. Furthermore2841 <p id="rfc.section.A.2.p.6">Require recipients to handle bogus "<a href="#header.content-length" class="smpl">Content-Length</a>" header fields as errors. (<a href="#header.content-length" id="rfc.xref.header.content-length.2" title="Content-Length">Section 3.3.2</a>) 2842 </p> 2843 <p id="rfc.section.A.2.p.7">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>) 2844 </p> 2845 <p id="rfc.section.A.2.p.8">Remove special-case for "multipart/byteranges" in message body length detection; add CONNECT as special case. (<a href="#message.body.length" title="Message Body Length">Section 3.3.3</a>) 2846 </p> 2847 <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 2846 2848 disallowed line folding in chunk extensions, and deprecate their use. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a>) 2847 2849 </p> 2848 <p id="rfc.section.A.2.p. 9">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk2850 <p id="rfc.section.A.2.p.10">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk 2849 2851 form is allowed for the OPTIONS request method only. (<a href="#request-target" title="Request Target">Section 5.3</a>) 2850 2852 </p> 2851 <p id="rfc.section.A.2.p.1 0">Clarify exactly when "close" connection options have to be sent; drop notion of header fields being "hop-by-hop" without being2853 <p id="rfc.section.A.2.p.11">Clarify exactly when "close" connection options have to be sent; drop notion of header fields being "hop-by-hop" without being 2852 2854 listed in the Connection header field. (<a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section 6.1</a>) 2853 2855 </p> 2854 <p id="rfc.section.A.2.p.1 1">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent.2856 <p id="rfc.section.A.2.p.12">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent. 2855 2857 Remove requirements about when servers are allowed to close connections prematurely. (<a href="#persistent.connections" title="Persistent Connections">Section 6.2</a>) 2856 2858 </p> 2857 <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>)2858 </p> 2859 <p id="rfc.section.A.2.p.1 3">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.3" title="Upgrade">Section 6.3</a>)2860 </p> 2861 <p id="rfc.section.A.2.p.1 4">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section 7.4</a>)2862 </p> 2863 <p id="rfc.section.A.2.p.1 5">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>)2864 </p> 2865 <p id="rfc.section.A.2.p.1 6">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix B</a>)2859 <p id="rfc.section.A.2.p.13">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>) 2860 </p> 2861 <p id="rfc.section.A.2.p.14">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.3" title="Upgrade">Section 6.3</a>) 2862 </p> 2863 <p id="rfc.section.A.2.p.15">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section 7.4</a>) 2864 </p> 2865 <p id="rfc.section.A.2.p.16">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>) 2866 </p> 2867 <p id="rfc.section.A.2.p.17">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix B</a>) 2866 2868 </p> 2867 2869 <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> … … 3021 3023 </p> 3022 3024 <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> <a id="changes.since.21" href="#changes.since.21">Since draft-ietf-httpbis-p1-messaging-21</a></h2> 3023 <p id="rfc.section.D.2.p.1">None yet.</p> 3025 <p id="rfc.section.D.2.p.1">Closed issues: </p> 3026 <ul> 3027 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/128">http://tools.ietf.org/wg/httpbis/trac/ticket/128</a>>: "Cite HTTPS URI scheme definition" (the spec now includes the HTTPs scheme definition and thus updates RFC 2818) 3028 </li> 3029 </ul> 3024 3030 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 3025 3031 <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</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.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</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> <a href="#rfc.index.V">V</a> … … 3284 3290 </ul> 3285 3291 </li> 3286 <li><em>RFC2818</em> <a href="#rfc.xref.RFC2818.1">1</a>, <a href="#rfc.xref.RFC2818.2">2.7.2</a>, <a href="#RFC2818"><b>10.2</b></a></li> 3292 <li><em>RFC2818</em> <a href="#rfc.xref.RFC2818.1">1</a>, <a href="#rfc.xref.RFC2818.2">2.7.2</a>, <a href="#RFC2818"><b>10.2</b></a>, <a href="#rfc.xref.RFC2818.3">A.2</a><ul> 3293 <li><em>Section 2.4</em> <a href="#rfc.xref.RFC2818.3">A.2</a></li> 3294 </ul> 3295 </li> 3287 3296 <li><em>RFC3040</em> <a href="#rfc.xref.RFC3040.1">2.3</a>, <a href="#RFC3040"><b>10.2</b></a></li> 3288 3297 <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1">7.1</a>, <a href="#RFC3864"><b>10.2</b></a></li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2005 r2006 4726 4726 </t> 4727 4727 <t> 4728 Take over the definition of "HTTPS" URI scheme, previously defined in 4729 <xref target="RFC2818" x:fmt="of" x:sec="2.4"/>. 4730 (<xref target="https.uri"/>) 4731 </t> 4732 <t> 4728 4733 Require that invalid whitespace around field-names be rejected. 4729 4734 Change ABNF productions for header fields to only define the field value. … … 5017 5022 <section title="Since draft-ietf-httpbis-p1-messaging-21" anchor="changes.since.21"> 5018 5023 <t> 5019 None yet. 5024 Closed issues: 5025 <list style="symbols"> 5026 <t> 5027 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/128"/>: 5028 "Cite HTTPS URI scheme definition" (the spec now includes the HTTPs 5029 scheme definition and thus updates RFC 2818) 5030 </t> 5031 </list> 5020 5032 </t> 5021 5033 </section>
Note: See TracChangeset
for help on using the changeset viewer.
