Changeset 1396 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 09/08/11 14:11:23 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1393 r1396 359 359 } 360 360 @bottom-center { 361 content: "Expires February 9, 2012";361 content: "Expires February 10, 2012"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-08-0 8">411 <meta name="dct.issued" scheme="ISO8601" content="2011-08-09"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 413 413 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 441 441 </tr> 442 442 <tr> 443 <td class="left">Expires: February 9, 2012</td>443 <td class="left">Expires: February 10, 2012</td> 444 444 <td class="right">HP</td> 445 445 </tr> … … 494 494 <tr> 495 495 <td class="left"></td> 496 <td class="right">August 8, 2011</td>496 <td class="right">August 9, 2011</td> 497 497 </tr> 498 498 </tbody> … … 527 527 in progress”. 528 528 </p> 529 <p>This Internet-Draft will expire on February 9, 2012.</p>529 <p>This Internet-Draft will expire on February 10, 2012.</p> 530 530 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 531 531 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 807 807 <p id="rfc.section.1.2.1.p.9">For example, given these ABNF productions:</p> 808 808 <div id="rfc.figure.u.5"></div><pre class="text"> example-list = 1#example-list-elmt 809 example-list-elmt = token ; see <a href="# basic.rules" title="Basic Rules">Section 1.2.2</a>809 example-list-elmt = token ; see <a href="#field.rules" title="Common Field ABNF Rules">Section 3.2.3</a> 810 810 </pre><p id="rfc.section.1.2.1.p.11">Then these are valid values for example-list (not including the double quotes, which are present for delimitation only):</p> 811 811 <div id="rfc.figure.u.6"></div><pre class="text"> "foo,bar" … … 3085 3085 </p> 3086 3086 <p id="rfc.section.A.2.p.2">Rules about implicit linear whitespace between certain grammar productions have been removed; now it's only allowed when specifically 3087 pointed out in the ABNF. The NUL octet is no longer allowed in comment and quoted-string text. The quoted-pair rule no longer 3088 allows escaping control characters other than HTAB. Non-ASCII content in header fields and reason phrase has been obsoleted 3089 and made opaque (the TEXT rule was removed) (<a href="#basic.rules" title="Basic Rules">Section 1.2.2</a>) 3087 pointed out in the ABNF. (<a href="#basic.rules" title="Basic Rules">Section 1.2.2</a>) 3090 3088 </p> 3091 3089 <p id="rfc.section.A.2.p.3">Clarify that the string "HTTP" in the HTTP-Version ABFN production is case sensitive. Restrict the version numbers to be single … … 3094 3092 <p id="rfc.section.A.2.p.4">Require that invalid whitespace around field-names be rejected. (<a href="#header.fields" title="Header Fields">Section 3.2</a>) 3095 3093 </p> 3096 <p id="rfc.section.A.2.p.5">Require recipients to handle bogus Content-Length header fields as errors. (<a href="#message.body" title="Message Body">Section 3.3</a>) 3097 </p> 3098 <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">6.2</a>) 3099 </p> 3100 <p id="rfc.section.A.2.p.7">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk 3094 <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 3095 characters other than HTAB. Non-ASCII content in header fields and reason phrase has been obsoleted and made opaque (the TEXT 3096 rule was removed). (<a href="#field.rules" title="Common Field ABNF Rules">Section 3.2.3</a>) 3097 </p> 3098 <p id="rfc.section.A.2.p.6">Require recipients to handle bogus Content-Length header fields as errors. (<a href="#message.body" title="Message Body">Section 3.3</a>) 3099 </p> 3100 <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">6.2</a>) 3101 </p> 3102 <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 3101 3103 form is allowed for the OPTIONS request method only. (<a href="#request-target" title="request-target">Section 4.1.2</a>) 3102 3104 </p> 3103 <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. Furthermore3105 <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 3104 3106 disallowed line folding in chunk extensions. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section 6.2.1</a>) 3105 3107 </p> 3106 <p id="rfc.section.A.2.p. 9">Remove hard limit of two connections per server. (<a href="#persistent.practical" title="Practical Considerations">Section 7.1.4</a>)3107 </p> 3108 <p id="rfc.section.A.2.p.1 0">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 9</a>)3109 </p> 3110 <p id="rfc.section.A.2.p.1 1">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.13" title="Connection">Section 9.1</a>)3111 </p> 3112 <p id="rfc.section.A.2.p.1 2">Define the semantics of the "Upgrade" 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 9.8</a>)3108 <p id="rfc.section.A.2.p.10">Remove hard limit of two connections per server. (<a href="#persistent.practical" title="Practical Considerations">Section 7.1.4</a>) 3109 </p> 3110 <p id="rfc.section.A.2.p.11">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 9</a>) 3111 </p> 3112 <p id="rfc.section.A.2.p.12">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.13" title="Connection">Section 9.1</a>) 3113 </p> 3114 <p id="rfc.section.A.2.p.13">Define the semantics of the "Upgrade" 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 9.8</a>) 3113 3115 </p> 3114 3116 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
Note: See TracChangeset
for help on using the changeset viewer.