Ignore:
Timestamp:
Nov 29, 2012, 3:51:24 PM (7 years ago)
Author:
mnot@…
Message:

More adjustments to "Changes from RFC2616", based upon the issues list.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2018 r2024  
    449449  }
    450450  @bottom-center {
    451        content: "Expires June 2, 2013";
     451       content: "Expires June 3, 2013";
    452452  }
    453453  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2012-11-29">
     493      <meta name="dct.issued" scheme="ISO8601" content="2012-11-30">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    520520            <tr>
    521521               <td class="left">Intended status: Standards Track</td>
    522                <td class="right">November 29, 2012</td>
     522               <td class="right">November 30, 2012</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: June 2, 2013</td>
     525               <td class="left">Expires: June 3, 2013</td>
    526526               <td class="right"></td>
    527527            </tr>
     
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on June 2, 2013.</p>
     553      <p>This Internet-Draft will expire on June 3, 2013.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    28242824      </p>
    28252825      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    2826       <p id="rfc.section.A.2.p.1">The HTTP-version ABNF production has been clarified to be case-sensitive. Additionally, version numbers has been restricted
     2826      <p id="rfc.section.A.2.p.1">HTTP's approach to error handling has been explained. (<a href="#conformance" title="Conformance and Error Handling">Section&nbsp;2.5</a>)
     2827      </p>
     2828      <p id="rfc.section.A.2.p.2">The expectation to support HTTP/0.9 requests has been removed.</p>
     2829      <p id="rfc.section.A.2.p.3">The term "Effective Request URI" has been introduced. (<a href="#effective.request.uri" title="Effective Request URI">Section&nbsp;5.5</a>)
     2830      </p>
     2831      <p id="rfc.section.A.2.p.4">HTTP messages can be (and often are) buffered by implementations; despite it sometimes being available as a stream, HTTP is
     2832         fundamentally a message-oriented protocol. (<a href="#http.message" title="Message Format">Section&nbsp;3</a>)
     2833      </p>
     2834      <p id="rfc.section.A.2.p.5">Minimum supported sizes for various protocol elements have been suggested, to improve interoperability.</p>
     2835      <p id="rfc.section.A.2.p.6">Header fields that span multiple lines ("line folding") are deprecated. (<a href="#field.parsing" title="Field Parsing">Section&nbsp;3.2.2</a>)
     2836      </p>
     2837      <p id="rfc.section.A.2.p.7">The HTTP-version ABNF production has been clarified to be case-sensitive. Additionally, version numbers has been restricted
    28272838         to single digits, due to the fact that implementations are known to handle multi-digit version numbers incorrectly. (<a href="#http.version" title="Protocol Versioning">Section&nbsp;2.6</a>)
    28282839      </p>
    2829       <p id="rfc.section.A.2.p.2">The "HTTPS" URI scheme is now defined by this specification; previously, it was done 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&nbsp;2.7.2</a>)
    2830       </p>
    2831       <p id="rfc.section.A.2.p.3">Invalid whitespace around field-names is now required to be rejected, because accepting it represents a security vulnerability.
     2840      <p id="rfc.section.A.2.p.8">The HTTPS URI scheme is now defined by this specification; previously, it was done 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&nbsp;2.7.2</a>)
     2841      </p>
     2842      <p id="rfc.section.A.2.p.9">The HTTPS URI scheme implies end-to-end security. (<a href="#https.uri" title="https URI scheme">Section&nbsp;2.7.2</a>)
     2843      </p>
     2844      <p id="rfc.section.A.2.p.10">Userinfo (i.e., username and password) are now disallowed in HTTP and HTTPS URIs, because of security issues related to their
     2845         transmission on the wire. (<a href="#http.uri" title="http URI scheme">Section&nbsp;2.7.1</a>)
     2846      </p>
     2847      <p id="rfc.section.A.2.p.11">Invalid whitespace around field-names is now required to be rejected, because accepting it represents a security vulnerability.
    28322848         (<a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>)
    28332849      </p>
    2834       <p id="rfc.section.A.2.p.4">The ABNF productions defining header fields now only list the field value. (<a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>)
    2835       </p>
    2836       <p id="rfc.section.A.2.p.5">Rules about implicit linear whitespace between certain grammar productions have been removed; now whitespace is only allowed
     2850      <p id="rfc.section.A.2.p.12">The ABNF productions defining header fields now only list the field value. (<a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>)
     2851      </p>
     2852      <p id="rfc.section.A.2.p.13">Rules about implicit linear whitespace between certain grammar productions have been removed; now whitespace is only allowed
    28372853         where specifically defined in the ABNF. (<a href="#whitespace" title="Whitespace">Section&nbsp;3.2.1</a>)
    28382854      </p>
    2839       <p id="rfc.section.A.2.p.6">The NUL octet is no longer allowed in comment and quoted-string text. (<a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>)
    2840       </p>
    2841       <p id="rfc.section.A.2.p.7">The quoted-pair rule no longer allows escaping control characters other than HTAB. (<a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>)
    2842       </p>
    2843       <p id="rfc.section.A.2.p.8">Non-ASCII content in header fields and the reason phrase has been obsoleted and made opaque (the TEXT rule was removed). (<a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>)
    2844       </p>
    2845       <p id="rfc.section.A.2.p.9">Bogus "<a href="#header.content-length" class="smpl">Content-Length</a>" header fields are now required to be handled as errors by recipients. (<a href="#header.content-length" id="rfc.xref.header.content-length.2" title="Content-Length">Section&nbsp;3.3.2</a>)
    2846       </p>
    2847       <p id="rfc.section.A.2.p.10">The "identity" transfer-coding value token has been removed. (Sections <a href="#message.body" title="Message Body">3.3</a> and <a href="#transfer.codings" title="Transfer Codings">4</a>)
    2848       </p>
    2849       <p id="rfc.section.A.2.p.11">"multipart/byteranges" is no longer a way of determining message body length detection. (<a href="#message.body.length" title="Message Body Length">Section&nbsp;3.3.3</a>)
    2850       </p>
    2851       <p id="rfc.section.A.2.p.12">CONNECT is a new, special case in determining message body length. (<a href="#message.body.length" title="Message Body Length">Section&nbsp;3.3.3</a>)
    2852       </p>
    2853       <p id="rfc.section.A.2.p.13">Chunk length does not include the count of the octets in the chunk header and trailer. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>)
    2854       </p>
    2855       <p id="rfc.section.A.2.p.14">Use of chunk extensions is deprecated, and line folding in them is disallowed. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>)
    2856       </p>
    2857       <p id="rfc.section.A.2.p.15">The path-absolute + query components of RFC3986 have been used to define the request-target, instead of abs_path from RFC
     2855      <p id="rfc.section.A.2.p.14">The NUL octet is no longer allowed in comment and quoted-string text, and handling of backslash-escaping in them has been
     2856         clarified. (<a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>)
     2857      </p>
     2858      <p id="rfc.section.A.2.p.15">The quoted-pair rule no longer allows escaping control characters other than HTAB. (<a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>)
     2859      </p>
     2860      <p id="rfc.section.A.2.p.16">Non-ASCII content in header fields and the reason phrase has been obsoleted and made opaque (the TEXT rule was removed). (<a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>)
     2861      </p>
     2862      <p id="rfc.section.A.2.p.17">Bogus "<a href="#header.content-length" class="smpl">Content-Length</a>" header fields are now required to be handled as errors by recipients. (<a href="#header.content-length" id="rfc.xref.header.content-length.2" title="Content-Length">Section&nbsp;3.3.2</a>)
     2863      </p>
     2864      <p id="rfc.section.A.2.p.18">The "identity" transfer-coding value token has been removed. (Sections <a href="#message.body" title="Message Body">3.3</a> and <a href="#transfer.codings" title="Transfer Codings">4</a>)
     2865      </p>
     2866      <p id="rfc.section.A.2.p.19">The algorithm for determining the message body length has been clarified to indicate all of the special cases (e.g., driven
     2867         by methods or status codes) that affect it, and that new protocol elements cannot define such special cases. (<a href="#message.body.length" title="Message Body Length">Section&nbsp;3.3.3</a>)
     2868      </p>
     2869      <p id="rfc.section.A.2.p.20">"multipart/byteranges" is no longer a way of determining message body length detection. (<a href="#message.body.length" title="Message Body Length">Section&nbsp;3.3.3</a>)
     2870      </p>
     2871      <p id="rfc.section.A.2.p.21">CONNECT is a new, special case in determining message body length. (<a href="#message.body.length" title="Message Body Length">Section&nbsp;3.3.3</a>)
     2872      </p>
     2873      <p id="rfc.section.A.2.p.22">Chunk length does not include the count of the octets in the chunk header and trailer. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>)
     2874      </p>
     2875      <p id="rfc.section.A.2.p.23">Use of chunk extensions is deprecated, and line folding in them is disallowed. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>)
     2876      </p>
     2877      <p id="rfc.section.A.2.p.24">The path-absolute + query components of RFC3986 have been used to define the request-target, instead of abs_path from RFC
    28582878         1808. (<a href="#request-target" title="Request Target">Section&nbsp;5.3</a>)
    28592879      </p>
    2860       <p id="rfc.section.A.2.p.16">The asterisk form of the request-target is only allowed in the OPTIONS method. (<a href="#request-target" title="Request Target">Section&nbsp;5.3</a>)
    2861       </p>
    2862       <p id="rfc.section.A.2.p.17">Exactly when "close" connection options have to be sent has been clarified. (<a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section&nbsp;6.1</a>)
    2863       </p>
    2864       <p id="rfc.section.A.2.p.18">"hop-by-hop" header fields are required to appear in the Connection header field; just because they're defined as hop-by-hop
     2880      <p id="rfc.section.A.2.p.25">The asterisk form of the request-target is only allowed in the OPTIONS method. (<a href="#request-target" title="Request Target">Section&nbsp;5.3</a>)
     2881      </p>
     2882      <p id="rfc.section.A.2.p.26">Exactly when "close" connection options have to be sent has been clarified. (<a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section&nbsp;6.1</a>)
     2883      </p>
     2884      <p id="rfc.section.A.2.p.27">"hop-by-hop" header fields are required to appear in the Connection header field; just because they're defined as hop-by-hop
    28652885         in this specification doesn't exempt them. (<a href="#header.connection" id="rfc.xref.header.connection.11" title="Connection">Section&nbsp;6.1</a>)
    28662886      </p>
    2867       <p id="rfc.section.A.2.p.19">The limit of two connections per server has been removed. (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;6.2</a>)
    2868       </p>
    2869       <p id="rfc.section.A.2.p.20">An idempotent sequence of requests is no longer required to be retried. (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;6.2</a>)
    2870       </p>
    2871       <p id="rfc.section.A.2.p.21">The requirement to retry requests under certain circumstances when the server prematurely closes the connection has been removed.
     2887      <p id="rfc.section.A.2.p.28">The limit of two connections per server has been removed. (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;6.2</a>)
     2888      </p>
     2889      <p id="rfc.section.A.2.p.29">An idempotent sequence of requests is no longer required to be retried. (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;6.2</a>)
     2890      </p>
     2891      <p id="rfc.section.A.2.p.30">The requirement to retry requests under certain circumstances when the server prematurely closes the connection has been removed.
    28722892         (<a href="#persistent.reuse" title="Reuse">Section&nbsp;6.2.2</a>)
    28732893      </p>
    2874       <p id="rfc.section.A.2.p.22">Some extraneous requirements about when servers are allowed to close connections prematurely have been removed. (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;6.2</a>)
    2875       </p>
    2876       <p id="rfc.section.A.2.p.23">The semantics of the <a href="#header.upgrade" class="smpl">Upgrade</a> header field is now defined 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&nbsp;6.3</a>)
    2877       </p>
    2878       <p id="rfc.section.A.2.p.24">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section&nbsp;7.4</a>)
    2879       </p>
    2880       <p id="rfc.section.A.2.p.25">This specification now defines 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&nbsp;7.6</a>)
    2881       </p>
    2882       <p id="rfc.section.A.2.p.26">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix&nbsp;B</a>)
     2894      <p id="rfc.section.A.2.p.31">Some extraneous requirements about when servers are allowed to close connections prematurely have been removed. (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;6.2</a>)
     2895      </p>
     2896      <p id="rfc.section.A.2.p.32">The semantics of the <a href="#header.upgrade" class="smpl">Upgrade</a> header field is now defined 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&nbsp;6.3</a>)
     2897      </p>
     2898      <p id="rfc.section.A.2.p.33">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section&nbsp;7.4</a>)
     2899      </p>
     2900      <p id="rfc.section.A.2.p.34">The meaning of the "deflate" content coding has been clarified. (<a href="#deflate.coding" title="Deflate Coding">Section&nbsp;4.2.2</a>)
     2901      </p>
     2902      <p id="rfc.section.A.2.p.35">This specification now defines 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&nbsp;7.6</a>)
     2903      </p>
     2904      <p id="rfc.section.A.2.p.36">Empty list elements in list productions (e.g., a list header containing ", ,") have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix&nbsp;B</a>)
     2905      </p>
     2906      <p id="rfc.section.A.2.p.37">Issues with the Keep-Alive and Proxy-Connection headers in requests are pointed out, with use of the latter being discouraged
     2907         altogether. (<a href="#compatibility.with.http.1.0.persistent.connections" title="Keep-Alive Connections">Appendix&nbsp;A.1.2</a>)
    28832908      </p>
    28842909      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="abnf.extension" href="#abnf.extension">ABNF list extension: #rule</a></h1>
Note: See TracChangeset for help on using the changeset viewer.