Ignore:
Timestamp:
Nov 28, 2012, 6:03:06 PM (7 years ago)
Author:
mnot@…
Message:

Regenerate HTML

File:
1 edited

Legend:

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

    r2007 r2018  
    449449  }
    450450  @bottom-center {
    451        content: "Expires June 1, 2013";
     451       content: "Expires June 2, 2013";
    452452  }
    453453  @bottom-right {
     
    486486      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    487487      <link href="p2-semantics.html" rel="next">
    488       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.588, 2012-08-25 12:28:24, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     488      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.588, 2012-08-25 12:28:24, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
    489489      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    490490      <meta name="dct.creator" content="Fielding, R.">
    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-28">
     493      <meta name="dct.issued" scheme="ISO8601" content="2012-11-29">
    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 28, 2012</td>
     522               <td class="right">November 29, 2012</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: June 1, 2013</td>
     525               <td class="left">Expires: June 2, 2013</td>
    526526               <td class="right"></td>
    527527            </tr>
     
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on June 1, 2013.</p>
     553      <p>This Internet-Draft will expire on June 2, 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">Clarify that the string "HTTP" in the HTTP-version ABNF production is case sensitive. Restrict the version numbers to be single
    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&nbsp;2.6</a>)
    2828       </p>
    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&nbsp;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
    2832          field value. (<a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>)
    2833       </p>
    2834       <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
     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
     2827         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>)
     2828      </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.
     2832         (<a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>)
     2833      </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
    28352837         where specifically defined in the ABNF. (<a href="#whitespace" title="Whitespace">Section&nbsp;3.2.1</a>)
    28362838      </p>
    2837       <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
    2838          characters other than HTAB. Non-ASCII content in header fields and reason phrase has been obsoleted and made opaque (the TEXT
    2839          rule was removed). (<a href="#field.components" title="Field value components">Section&nbsp;3.2.4</a>)
    2840       </p>
    2841       <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&nbsp;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&nbsp;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
    2848          disallowed line folding in chunk extensions, and deprecate their use. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;4.1</a>)
    2849       </p>
    2850       <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
    2851          form is allowed for the OPTIONS request method only. (<a href="#request-target" title="Request Target">Section&nbsp;5.3</a>)
    2852       </p>
    2853       <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
    2854          listed in the Connection header field. (<a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section&nbsp;6.1</a>)
    2855       </p>
    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.
    2857          Remove requirements about when servers are allowed to close connections prematurely. (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;6.2</a>)
    2858       </p>
    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&nbsp;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&nbsp;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&nbsp;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&nbsp;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&nbsp;B</a>)
     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
     2858         1808. (<a href="#request-target" title="Request Target">Section&nbsp;5.3</a>)
     2859      </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
     2865         in this specification doesn't exempt them. (<a href="#header.connection" id="rfc.xref.header.connection.11" title="Connection">Section&nbsp;6.1</a>)
     2866      </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.
     2872         (<a href="#persistent.reuse" title="Reuse">Section&nbsp;6.2.2</a>)
     2873      </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>)
    28682883      </p>
    28692884      <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>
     
    30533068                  <li>chunked (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.7">4.1</a></li>
    30543069                  <li>client&nbsp;&nbsp;<a href="#rfc.iref.c.1"><b>2.1</b></a></li>
    3055                   <li>close&nbsp;&nbsp;<a href="#rfc.xref.header.connection.1">2.3</a>, <a href="#rfc.xref.header.connection.2">2.6</a>, <a href="#rfc.xref.header.connection.3">3.2</a>, <a href="#rfc.xref.header.connection.4">4.3</a>, <a href="#rfc.xref.header.connection.5">5.6</a>, <a href="#rfc.iref.c.10"><b>6.1</b></a>, <a href="#rfc.xref.persistent.tear-down.1">6.1</a>, <a href="#rfc.iref.c.12">6.2.5</a>, <a href="#rfc.xref.header.connection.6">6.2.5</a>, <a href="#rfc.xref.header.connection.7">6.3</a>, <a href="#rfc.xref.header.connection.8">7.1</a>, <a href="#rfc.xref.header.connection.9">7.1</a>, <a href="#rfc.xref.header.connection.10">A.2</a></li>
     3070                  <li>close&nbsp;&nbsp;<a href="#rfc.xref.header.connection.1">2.3</a>, <a href="#rfc.xref.header.connection.2">2.6</a>, <a href="#rfc.xref.header.connection.3">3.2</a>, <a href="#rfc.xref.header.connection.4">4.3</a>, <a href="#rfc.xref.header.connection.5">5.6</a>, <a href="#rfc.iref.c.10"><b>6.1</b></a>, <a href="#rfc.xref.persistent.tear-down.1">6.1</a>, <a href="#rfc.iref.c.12">6.2.5</a>, <a href="#rfc.xref.header.connection.6">6.2.5</a>, <a href="#rfc.xref.header.connection.7">6.3</a>, <a href="#rfc.xref.header.connection.8">7.1</a>, <a href="#rfc.xref.header.connection.9">7.1</a>, <a href="#rfc.xref.header.connection.10">A.2</a>, <a href="#rfc.xref.header.connection.11">A.2</a></li>
    30563071                  <li>compress (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.c.8">4.2.1</a></li>
    30573072                  <li>connection&nbsp;&nbsp;<a href="#rfc.iref.c.2"><b>2.1</b></a></li>
    3058                   <li>Connection header field&nbsp;&nbsp;<a href="#rfc.xref.header.connection.1">2.3</a>, <a href="#rfc.xref.header.connection.2">2.6</a>, <a href="#rfc.xref.header.connection.3">3.2</a>, <a href="#rfc.xref.header.connection.4">4.3</a>, <a href="#rfc.xref.header.connection.5">5.6</a>, <a href="#rfc.iref.c.9"><b>6.1</b></a>, <a href="#rfc.xref.persistent.tear-down.1">6.1</a>, <a href="#rfc.iref.c.11">6.2.5</a>, <a href="#rfc.xref.header.connection.6">6.2.5</a>, <a href="#rfc.xref.header.connection.7">6.3</a>, <a href="#rfc.xref.header.connection.8">7.1</a>, <a href="#rfc.xref.header.connection.9">7.1</a>, <a href="#rfc.xref.header.connection.10">A.2</a></li>
     3073                  <li>Connection header field&nbsp;&nbsp;<a href="#rfc.xref.header.connection.1">2.3</a>, <a href="#rfc.xref.header.connection.2">2.6</a>, <a href="#rfc.xref.header.connection.3">3.2</a>, <a href="#rfc.xref.header.connection.4">4.3</a>, <a href="#rfc.xref.header.connection.5">5.6</a>, <a href="#rfc.iref.c.9"><b>6.1</b></a>, <a href="#rfc.xref.persistent.tear-down.1">6.1</a>, <a href="#rfc.iref.c.11">6.2.5</a>, <a href="#rfc.xref.header.connection.6">6.2.5</a>, <a href="#rfc.xref.header.connection.7">6.3</a>, <a href="#rfc.xref.header.connection.8">7.1</a>, <a href="#rfc.xref.header.connection.9">7.1</a>, <a href="#rfc.xref.header.connection.10">A.2</a>, <a href="#rfc.xref.header.connection.11">A.2</a></li>
    30593074                  <li>Content-Length header field&nbsp;&nbsp;<a href="#rfc.iref.c.6"><b>3.3.2</b></a>, <a href="#rfc.xref.header.content-length.1">7.1</a>, <a href="#rfc.xref.header.content-length.2">A.2</a></li>
    30603075               </ul>
Note: See TracChangeset for help on using the changeset viewer.