Changeset 2018
- Timestamp:
- 29/11/12 02:03:06 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2007 r2018 449 449 } 450 450 @bottom-center { 451 content: "Expires June 1, 2013";451 content: "Expires June 2, 2013"; 452 452 } 453 453 @bottom-right { … … 486 486 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 487 487 <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.9from 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/"> 489 489 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 490 490 <meta name="dct.creator" content="Fielding, R."> 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2012-11-2 8">493 <meta name="dct.issued" scheme="ISO8601" content="2012-11-29"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 520 520 <tr> 521 521 <td class="left">Intended status: Standards Track</td> 522 <td class="right">November 2 8, 2012</td>522 <td class="right">November 29, 2012</td> 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: June 1, 2013</td>525 <td class="left">Expires: June 2, 2013</td> 526 526 <td class="right"></td> 527 527 </tr> … … 551 551 in progress”. 552 552 </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> 554 554 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 555 555 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2824 2824 </p> 2825 2825 <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a> <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 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 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 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 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 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 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 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 2835 2837 where specifically defined in the ABNF. (<a href="#whitespace" title="Whitespace">Section 3.2.1</a>) 2836 2838 </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 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 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 2848 disallowed line folding in chunk extensions, and deprecate their use. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section 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 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 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 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 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>) 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 B</a>) 2868 2883 </p> 2869 2884 <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> … … 3053 3068 <li>chunked (Coding Format) <a href="#rfc.iref.c.7">4.1</a></li> 3054 3069 <li>client <a href="#rfc.iref.c.1"><b>2.1</b></a></li> 3055 <li>close <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 <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> 3056 3071 <li>compress (Coding Format) <a href="#rfc.iref.c.8">4.2.1</a></li> 3057 3072 <li>connection <a href="#rfc.iref.c.2"><b>2.1</b></a></li> 3058 <li>Connection header field <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 <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> 3059 3074 <li>Content-Length header field <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> 3060 3075 </ul> -
draft-ietf-httpbis/latest/p2-semantics.html
r2001 r2018 449 449 } 450 450 @bottom-center { 451 content: "Expires May 31, 2013";451 content: "Expires June 2, 2013"; 452 452 } 453 453 @bottom-right { … … 491 491 <link href="p1-messaging.html" rel="prev"> 492 492 <link href="p4-conditional.html" rel="next"> 493 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.588, 2012-08-25 12:28:24, XSLT vendor: SAXON 8.9from Saxonica http://www.saxonica.com/">493 <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/"> 494 494 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 495 495 <meta name="dct.creator" content="Fielding, R."> 496 496 <meta name="dct.creator" content="Reschke, J. F."> 497 497 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 498 <meta name="dct.issued" scheme="ISO8601" content="2012-11-2 7">498 <meta name="dct.issued" scheme="ISO8601" content="2012-11-29"> 499 499 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 500 500 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 524 524 <tr> 525 525 <td class="left">Intended status: Standards Track</td> 526 <td class="right">November 2 7, 2012</td>526 <td class="right">November 29, 2012</td> 527 527 </tr> 528 528 <tr> 529 <td class="left">Expires: May 31, 2013</td>529 <td class="left">Expires: June 2, 2013</td> 530 530 <td class="right"></td> 531 531 </tr> … … 555 555 in progress”. 556 556 </p> 557 <p>This Internet-Draft will expire on May 31, 2013.</p>557 <p>This Internet-Draft will expire on June 2, 2013.</p> 558 558 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 559 559 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 4087 4087 </p> 4088 4088 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 4089 <p id="rfc.section.C.p.1">Remove base URI setting semantics for "<a href="#header.content-location" class="smpl">Content-Location</a>" due to poor implementation support (which was caused by too many broken servers emitting bogus Content-Location header fields, 4090 and also the potentially undesirable effect of potentially breaking relative links in content-negotiated resources). (<a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section 3.1.4.2</a>) 4091 </p> 4092 <p id="rfc.section.C.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.4" title="POST">Section 5.3.3</a>) 4093 </p> 4094 <p id="rfc.section.C.p.3">Remove requirement to handle all Content-* header fields; ban use of <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> with PUT. (<a href="#PUT" id="rfc.xref.PUT.4" title="PUT">Section 5.3.4</a>) 4095 </p> 4096 <p id="rfc.section.C.p.4">Take over definition of CONNECT method from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.3" title="CONNECT">Section 5.3.6</a>) 4097 </p> 4098 <p id="rfc.section.C.p.5">Restrict "<a href="#header.max-forwards" class="smpl">Max-Forwards</a>" header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section 6.1.1</a>) 4099 </p> 4100 <p id="rfc.section.C.p.6">The ABNF for the "<a href="#header.expect" class="smpl">Expect</a>" header field has been both fixed (allowing parameters for value-less expectations as well) and simplified (allowing trailing 4089 <p id="rfc.section.C.p.1"> <a href="#header.content-location" class="smpl">Content-Location</a> no longer sets a base URI, due to poor implementation support (which was caused by too many broken servers emitting bogus 4090 Content-Location header fields, and also the potentially undesirable effect of potentially breaking relative links in content-negotiated 4091 resources). (<a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section 3.1.4.2</a>) 4092 </p> 4093 <p id="rfc.section.C.p.2">The definition of POST has been clarified. (<a href="#POST" id="rfc.xref.POST.4" title="POST">Section 5.3.3</a>) 4094 </p> 4095 <p id="rfc.section.C.p.3">Servers are no longer required to handle all Content-* header fields in requests. (<a href="#PUT" id="rfc.xref.PUT.4" title="PUT">Section 5.3.4</a>) 4096 </p> 4097 <p id="rfc.section.C.p.4">Use of <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> is explicitly banned on PUT requests. (<a href="#PUT" id="rfc.xref.PUT.5" title="PUT">Section 5.3.4</a>) 4098 </p> 4099 <p id="rfc.section.C.p.5">The CONNECT method is now defined by this specification, taking over from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.3" title="CONNECT">Section 5.3.6</a>) 4100 </p> 4101 <p id="rfc.section.C.p.6">The "<a href="#header.max-forwards" class="smpl">Max-Forwards</a>" header field is now restricted to the OPTIONS and TRACE methods (previously, extension methods could have used it as well). 4102 (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section 6.1.1</a>) 4103 </p> 4104 <p id="rfc.section.C.p.7">The ABNF for the "<a href="#header.expect" class="smpl">Expect</a>" header field has been both fixed (allowing parameters for value-less expectations as well) and simplified (allowing trailing 4101 4105 semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section 6.1.2</a>) 4102 4106 </p> 4103 <p id="rfc.section.C.p.7">Remove ISO-8859-1 special-casing in <a href="#header.accept-charset" class="smpl">Accept-Charset</a>. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.4" title="Accept-Charset">Section 6.3.3</a>) 4104 </p> 4105 <p id="rfc.section.C.p.8">Allow "<a href="#header.referer" class="smpl">Referer</a>" field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 6.5.2</a>) 4106 </p> 4107 <p id="rfc.section.C.p.9">Broadened the definition of <a href="#status.203" class="smpl">203 (Non-Authoritative Information)</a> to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section 7.3.4</a>) 4108 </p> 4109 <p id="rfc.section.C.p.10">Status codes <a href="#status.301" class="smpl">301</a>, <a href="#status.302" class="smpl">302</a>, and <a href="#status.307" class="smpl">307</a>: removed the normative requirements on both response payloads and user interaction. (<a href="#status.3xx" id="rfc.xref.status.3xx.1" title="Redirection 3xx">Section 7.4</a>) 4110 </p> 4111 <p id="rfc.section.C.p.11">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the 4112 user agent is able to make that determination based on the request method semantics. Furthermore, allow user agents to rewrite 4113 the method from POST to GET for status codes <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a>. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">7.4.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">7.4.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">7.4.7</a>) 4114 </p> 4115 <p id="rfc.section.C.p.12">Deprecate <a href="#status.305" class="smpl">305 (Use Proxy)</a> status code, because user agents did not implement it. It used to indicate that the target resource needs to be accessed through 4116 the proxy given by the <a href="#header.location" class="smpl">Location</a> field. The Location field gave the URI of the proxy. The recipient was expected to repeat this single request via the proxy. 4117 (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section 7.4.5</a>) 4118 </p> 4119 <p id="rfc.section.C.p.13">Define status <a href="#status.426" class="smpl">426 (Upgrade Required)</a> (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="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section 7.5.15</a>) 4120 </p> 4121 <p id="rfc.section.C.p.14">Correct syntax of "<a href="#header.location" class="smpl">Location</a>" header field to allow URI references (including relative references and fragments), as referred symbol "absoluteURI" wasn't 4122 what was expected, and add some clarifications as to when use of fragments would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section 8.1.2</a>) 4123 </p> 4124 <p id="rfc.section.C.p.15">Reclassify "<a href="#header.allow" class="smpl">Allow</a>" as response header field, removing the option to specify it in a PUT request. Relax the server requirement on the contents 4125 of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 8.4.1</a>) 4126 </p> 4127 <p id="rfc.section.C.p.16">In the description of the "<a href="#header.server" class="smpl">Server</a>" header field, the "<a href="p1-messaging.html#header.via" class="smpl">Via</a>" field was described as a SHOULD. The requirement was and is stated correctly in the description of the Via header field 4128 in <a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 8.4.2</a>) 4129 </p> 4130 <p id="rfc.section.C.p.17">Clarify contexts that charset is used in. (<a href="#charset" title="Charset">Section 3.1.1.2</a>) 4131 </p> 4132 <p id="rfc.section.C.p.18">Remove the default charset of "ISO-8859-1" for text media types; the default now is whatever the media type definition says. 4133 (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 3.1.1.3</a>) 4134 </p> 4135 <p id="rfc.section.C.p.19">Registration of Content Codings now requires IETF Review (<a href="#content.coding.registry" title="Content Coding Registry">Section 9.4</a>) 4136 </p> 4137 <p id="rfc.section.C.p.20">Remove definition of "Content-MD5 header" field because it was inconsistently implemented with respect to partial responses, 4107 <p id="rfc.section.C.p.8">Special casing for ISO-8859-1 in <a href="#header.accept-charset" class="smpl">Accept-Charset</a> has been removed. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.4" title="Accept-Charset">Section 6.3.3</a>) 4108 </p> 4109 <p id="rfc.section.C.p.9">"<a href="#header.referer" class="smpl">Referer</a>" can now hoave a field value of "about:blank" as an alternative to not sending a Referer header field. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section 6.5.2</a>) 4110 </p> 4111 <p id="rfc.section.C.p.10">The definition of <a href="#status.203" class="smpl">203 (Non-Authoritative Information)</a> has been broadened to include cases of payload transformations as well. (<a href="#status.203" id="rfc.xref.status.203.3" title="203 Non-Authoritative Information">Section 7.3.4</a>) 4112 </p> 4113 <p id="rfc.section.C.p.11">Redirect status codes <a href="#status.301" class="smpl">301</a>, <a href="#status.302" class="smpl">302</a>, and <a href="#status.307" class="smpl">307</a> no longer have normative requirements on response payloads and user interaction. (<a href="#status.3xx" id="rfc.xref.status.3xx.1" title="Redirection 3xx">Section 7.4</a>) 4114 </p> 4115 <p id="rfc.section.C.p.12">The request methods that are safe to automatically redirect is no longer a closed set; user agents are able to make that determination 4116 based upon the request method semantics. (<a href="#status.3xx" id="rfc.xref.status.3xx.2" title="Redirection 3xx">Section 7.4</a>) 4117 </p> 4118 <p id="rfc.section.C.p.13">User agents are now allowed to rewrite the method from POST to GET for status codes <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a>. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">7.4.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">7.4.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">7.4.7</a>) 4119 </p> 4120 <p id="rfc.section.C.p.14">The <a href="#status.305" class="smpl">305 (Use Proxy)</a> status code is now deprecated, because user agents did not implement it. It used to indicate that the target resource needed 4121 to be accessed through the proxy given by the <a href="#header.location" class="smpl">Location</a> field. The recipient was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section 7.4.5</a>) 4122 </p> 4123 <p id="rfc.section.C.p.15">The <a href="#status.426" class="smpl">426 (Upgrade Required)</a> status code has been incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section 7.5.15</a>) 4124 </p> 4125 <p id="rfc.section.C.p.16">The syntax of the <a href="#header.location" class="smpl">Location</a> header field has been corrected to allow URI references (including relative references and fragments), along with some clarifications 4126 as to when use of fragments would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section 8.1.2</a>) 4127 </p> 4128 <p id="rfc.section.C.p.17"> <a href="#header.allow" class="smpl">Allow</a> has been reclassified as a response header field, removing the option to specify it in a PUT request. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section 8.4.1</a>) 4129 </p> 4130 <p id="rfc.section.C.p.18">Requirements relating to the content of the Allow header have been relaxed; correspondingly, clients are not required to always 4131 trust its value. (<a href="#header.allow" id="rfc.xref.header.allow.5" title="Allow">Section 8.4.1</a>) 4132 </p> 4133 <p id="rfc.section.C.p.19">The requirement to produce a <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field has been moved from the description of the <a href="#header.server" class="smpl">Server</a> header field to <a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 8.4.2</a>) 4134 </p> 4135 <p id="rfc.section.C.p.20">The contexts that charset is used in have been clarified. (<a href="#charset" title="Charset">Section 3.1.1.2</a>) 4136 </p> 4137 <p id="rfc.section.C.p.21">The default charset of "ISO-8859-1" for text media types has been removed; the default now is whatever the media type definition 4138 says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 3.1.1.3</a>) 4139 </p> 4140 <p id="rfc.section.C.p.22">Registration of Content Codings now requires IETF Review. (<a href="#content.coding.registry" title="Content Coding Registry">Section 9.4</a>) 4141 </p> 4142 <p id="rfc.section.C.p.23">The Content-MD5 header field has been removed, because it was inconsistently implemented with respect to partial responses, 4138 4143 and also because of known deficiencies in the hash algorithm itself (see <a href="#RFC6151" id="rfc.xref.RFC6151.1"><cite title="Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms">[RFC6151]</cite></a> for details). 4139 4144 </p> 4140 <p id="rfc.section.C.p.2 1">IntroduceMethod Registry. (<a href="#method.registry" title="Method Registry">Section 9.1</a>)4141 </p> 4142 <p id="rfc.section.C.p.2 2">Take over the Status Code Registry, previouslydefined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section 9.2</a>)4143 </p> 4144 <p id="rfc.section.C.p.2 3">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix A.5</a>)4145 </p> 4146 <p id="rfc.section.C.p.2 4">Remove discussion of Content-Disposition header field, itis now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix B</a>)4145 <p id="rfc.section.C.p.24">This specification introduces a Method Registry. (<a href="#method.registry" title="Method Registry">Section 9.1</a>) 4146 </p> 4147 <p id="rfc.section.C.p.25">The Status Code Registry is now defined by this specification; previously, it was defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section 9.2</a>) 4148 </p> 4149 <p id="rfc.section.C.p.26">References to the "identity" transfer-coding value token have been removed. (<a href="#no.content-transfer-encoding" id="rfc.xref.no.content-transfer-encoding.1" title="No Content-Transfer-Encoding">Appendix A.5</a>) 4150 </p> 4151 <p id="rfc.section.C.p.27">The Content-Disposition header field is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix B</a>) 4147 4152 </p> 4148 4153 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1> … … 4343 4348 <li>306 (Unused) (status code) <a href="#rfc.iref.73"><b>7.4.6</b></a>, <a href="#rfc.xref.status.306.1">9.2.3</a></li> 4344 4349 <li>307 Temporary Redirect (status code) <a href="#rfc.xref.status.307.1">7.1</a>, <a href="#rfc.iref.73"><b>7.4.7</b></a>, <a href="#rfc.xref.status.307.2">9.2.3</a>, <a href="#rfc.xref.status.307.3">C</a></li> 4345 <li>3xx Redirection (status code class) <a href="#rfc.iref.72"><b>7.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a> </li>4350 <li>3xx Redirection (status code class) <a href="#rfc.iref.72"><b>7.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a>, <a href="#rfc.xref.status.3xx.2">C</a></li> 4346 4351 </ul> 4347 4352 </li> … … 4380 4385 <li>Accept-Encoding header field <a href="#rfc.xref.header.accept-encoding.1">3.1.2.1</a>, <a href="#rfc.xref.header.accept-encoding.2">3.4.1</a>, <a href="#rfc.xref.header.accept-encoding.3">6.3</a>, <a href="#rfc.iref.a.3"><b>6.3.4</b></a>, <a href="#rfc.xref.header.accept-encoding.4">9.3.2</a>, <a href="#rfc.xref.header.accept-encoding.5">9.4.2</a></li> 4381 4386 <li>Accept-Language header field <a href="#rfc.xref.header.accept-language.1">3.4.1</a>, <a href="#rfc.xref.header.accept-language.2">6.3</a>, <a href="#rfc.iref.a.4"><b>6.3.5</b></a>, <a href="#rfc.xref.header.accept-language.3">9.3.2</a></li> 4382 <li>Allow header field <a href="#rfc.xref.header.allow.1">5.1</a>, <a href="#rfc.xref.header.allow.2">8.4</a>, <a href="#rfc.iref.a.5"><b>8.4.1</b></a>, <a href="#rfc.xref.header.allow.3">9.3.2</a>, <a href="#rfc.xref.header.allow.4">C</a> </li>4387 <li>Allow header field <a href="#rfc.xref.header.allow.1">5.1</a>, <a href="#rfc.xref.header.allow.2">8.4</a>, <a href="#rfc.iref.a.5"><b>8.4.1</b></a>, <a href="#rfc.xref.header.allow.3">9.3.2</a>, <a href="#rfc.xref.header.allow.4">C</a>, <a href="#rfc.xref.header.allow.5">C</a></li> 4383 4388 </ul> 4384 4389 </li> … … 4582 4587 <li>payload <a href="#rfc.iref.p.1">3.3</a></li> 4583 4588 <li>POST method <a href="#rfc.xref.POST.1">3.3</a>, <a href="#rfc.xref.POST.2">5.1</a>, <a href="#rfc.iref.p.2"><b>5.3.3</b></a>, <a href="#rfc.xref.POST.3">9.1.3</a>, <a href="#rfc.xref.POST.4">C</a></li> 4584 <li>PUT method <a href="#rfc.xref.PUT.1">3.3</a>, <a href="#rfc.xref.PUT.2">5.1</a>, <a href="#rfc.iref.p.3"><b>5.3.4</b></a>, <a href="#rfc.xref.PUT.3">9.1.3</a>, <a href="#rfc.xref.PUT.4">C</a> </li>4589 <li>PUT method <a href="#rfc.xref.PUT.1">3.3</a>, <a href="#rfc.xref.PUT.2">5.1</a>, <a href="#rfc.iref.p.3"><b>5.3.4</b></a>, <a href="#rfc.xref.PUT.3">9.1.3</a>, <a href="#rfc.xref.PUT.4">C</a>, <a href="#rfc.xref.PUT.5">C</a></li> 4585 4590 </ul> 4586 4591 </li> … … 4684 4689 <li>1xx Informational <a href="#rfc.iref.s.2"><b>7.2</b></a></li> 4685 4690 <li>2xx Successful <a href="#rfc.iref.s.3"><b>7.3</b></a></li> 4686 <li>3xx Redirection <a href="#rfc.iref.s.4"><b>7.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a> </li>4691 <li>3xx Redirection <a href="#rfc.iref.s.4"><b>7.4</b></a>, <a href="#rfc.xref.status.3xx.1">C</a>, <a href="#rfc.xref.status.3xx.2">C</a></li> 4687 4692 <li>4xx Client Error <a href="#rfc.iref.s.5"><b>7.5</b></a></li> 4688 4693 <li>5xx Server Error <a href="#rfc.iref.s.6"><b>7.6</b></a></li> -
draft-ietf-httpbis/latest/p4-conditional.html
r2001 r2018 449 449 } 450 450 @bottom-center { 451 content: "Expires May 31, 2013";451 content: "Expires June 2, 2013"; 452 452 } 453 453 @bottom-right { … … 486 486 <link href="p2-semantics.html" rel="prev"> 487 487 <link href="p5-range.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.9from 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/"> 489 489 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 490 490 <meta name="dct.creator" content="Fielding, R."> 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2012-11-2 7">493 <meta name="dct.issued" scheme="ISO8601" content="2012-11-29"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 495 495 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false."> … … 517 517 </tr> 518 518 <tr> 519 <td class="left">Expires: May 31, 2013</td>520 <td class="right">November 2 7, 2012</td>519 <td class="left">Expires: June 2, 2013</td> 520 <td class="right">November 29, 2012</td> 521 521 </tr> 522 522 </tbody> … … 545 545 in progress”. 546 546 </p> 547 <p>This Internet-Draft will expire on May 31, 2013.</p>547 <p>This Internet-Draft will expire on June 2, 2013.</p> 548 548 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 549 549 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1294 1294 </div> 1295 1295 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 1296 <p id="rfc.section.A.p.1"> Allow weak entity-tagsin all requests except range requests (Sections <a href="#weak.and.strong.validators" title="Weak versus Strong">2.1</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">3.2</a>).1297 </p> 1298 <p id="rfc.section.A.p.2"> Change "<a href="#header.etag" class="smpl">ETag</a>" header field ABNF not touse quoted-string, thus avoiding escaping issues. (<a href="#header.etag" id="rfc.xref.header.etag.3" title="ETag">Section 2.3</a>)1296 <p id="rfc.section.A.p.1">Weak entity-tags are now allowed in all requests except range requests (Sections <a href="#weak.and.strong.validators" title="Weak versus Strong">2.1</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">3.2</a>). 1297 </p> 1298 <p id="rfc.section.A.p.2">The <a href="#header.etag" class="smpl">ETag</a> header field ABNF has been changed to not use quoted-string, thus avoiding escaping issues. (<a href="#header.etag" id="rfc.xref.header.etag.3" title="ETag">Section 2.3</a>) 1299 1299 </p> 1300 1300 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1> -
draft-ietf-httpbis/latest/p5-range.html
r2001 r2018 449 449 } 450 450 @bottom-center { 451 content: "Expires May 31, 2013";451 content: "Expires June 2, 2013"; 452 452 } 453 453 @bottom-right { … … 487 487 <link href="p4-conditional.html" rel="prev"> 488 488 <link href="p6-cache.html" rel="next"> 489 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.588, 2012-08-25 12:28:24, XSLT vendor: SAXON 8.9from Saxonica http://www.saxonica.com/">489 <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/"> 490 490 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 491 491 <meta name="dct.creator" content="Fielding, R."> … … 493 493 <meta name="dct.creator" content="Reschke, J. F."> 494 494 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 495 <meta name="dct.issued" scheme="ISO8601" content="2012-11-2 7">495 <meta name="dct.issued" scheme="ISO8601" content="2012-11-29"> 496 496 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 497 497 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests."> … … 519 519 </tr> 520 520 <tr> 521 <td class="left">Expires: May 31, 2013</td>521 <td class="left">Expires: June 2, 2013</td> 522 522 <td class="right">J. Reschke, Editor</td> 523 523 </tr> … … 528 528 <tr> 529 529 <td class="left"></td> 530 <td class="right">November 2 7, 2012</td>530 <td class="right">November 29, 2012</td> 531 531 </tr> 532 532 </tbody> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on May 31, 2013.</p>555 <p>This Internet-Draft will expire on June 2, 2013.</p> 556 556 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 557 557 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1229 1229 </ol> 1230 1230 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 1231 <p id="rfc.section.B.p.1"> IntroduceRange Specifier Registry. (<a href="#range.specifier.registry" title="Range Specifier Registry">Section 2.1</a>)1232 </p> 1233 <p id="rfc.section.B.p.2"> Clarify that it is not ok to use a weak validatorin a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section 3.1</a>)1234 </p> 1235 <p id="rfc.section.B.p.3"> Clarify thatmultipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>)1231 <p id="rfc.section.B.p.1">This specification introduces a Range Specifier Registry. (<a href="#range.specifier.registry" title="Range Specifier Registry">Section 2.1</a>) 1232 </p> 1233 <p id="rfc.section.B.p.2">A weak validator cannot be used in a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section 3.1</a>) 1234 </p> 1235 <p id="rfc.section.B.p.3">multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>) 1236 1236 </p> 1237 1237 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1> -
draft-ietf-httpbis/latest/p6-cache.html
r2002 r2018 452 452 } 453 453 @bottom-center { 454 content: "Expires May 31, 2013";454 content: "Expires June 2, 2013"; 455 455 } 456 456 @bottom-right { … … 492 492 <link href="p5-range.html" rel="prev"> 493 493 <link href="p7-auth.html" rel="next"> 494 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.588, 2012-08-25 12:28:24, XSLT vendor: SAXON 8.9from Saxonica http://www.saxonica.com/">494 <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/"> 495 495 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 496 496 <meta name="dct.creator" content="Fielding, R."> … … 498 498 <meta name="dct.creator" content="Reschke, J. F."> 499 499 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 500 <meta name="dct.issued" scheme="ISO8601" content="2012-11-2 7">500 <meta name="dct.issued" scheme="ISO8601" content="2012-11-29"> 501 501 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 502 502 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: May 31, 2013</td>526 <td class="left">Expires: June 2, 2013</td> 527 527 <td class="right">J. Reschke, Editor</td> 528 528 </tr> … … 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">November 2 7, 2012</td>535 <td class="right">November 29, 2012</td> 536 536 </tr> 537 537 </tbody> … … 559 559 in progress”. 560 560 </p> 561 <p>This Internet-Draft will expire on May 31, 2013.</p>561 <p>This Internet-Draft will expire on June 2, 2013.</p> 562 562 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 563 563 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1892 1892 </div> 1893 1893 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> 1894 <p id="rfc.section.A.p.1"> Make the specified age calculation algorithmless conservative. (<a href="#age.calculations" title="Calculating Age">Section 4.1.3</a>)1895 </p> 1896 <p id="rfc.section.A.p.2"> Remove requirement to consider "<a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a>" in successful responses in orderto determine the appropriate response to use. (<a href="#validation.model" title="Validation Model">Section 4.2</a>)1897 </p> 1898 <p id="rfc.section.A.p.3"> Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a>)1899 </p> 1900 <p id="rfc.section.A.p.4"> Do not mention RFC 2047 encoding and multiple languages in "<a href="#header.warning" class="smpl">Warning</a>" header fields anymore, as these aspects never wereimplemented. (<a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">Section 7.5</a>)1901 </p> 1902 <p id="rfc.section.A.p.5"> Introduce Cache Directive and Warn Code Registries. (<a href="#cache.control.extensions" title="Cache Control Extensions">Section 7.2.3</a> and <a href="#warn.code.extensions" title="Warn Code Extensions">Section 7.5.8</a>)1894 <p id="rfc.section.A.p.1">The algorithm for calculating age is now less conservative. (<a href="#age.calculations" title="Calculating Age">Section 4.1.3</a>) 1895 </p> 1896 <p id="rfc.section.A.p.2">The <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header field is no longer used to determine the appropriate response to use. (<a href="#validation.model" title="Validation Model">Section 4.2</a>) 1897 </p> 1898 <p id="rfc.section.A.p.3">Requirements regarding denial of service attack avoidance have been clarified. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a>) 1899 </p> 1900 <p id="rfc.section.A.p.4">The <a href="#header.warning" class="smpl">Warning</a> header field no longer uses RFC 2047 encoding, nor allows multiple languages, as these aspects were not implemented. (<a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">Section 7.5</a>) 1901 </p> 1902 <p id="rfc.section.A.p.5">This specification introduces the Cache Directive and Warn Code Registries. (<a href="#cache.control.extensions" title="Cache Control Extensions">Section 7.2.3</a> and <a href="#warn.code.extensions" title="Warn Code Extensions">Section 7.5.8</a>) 1903 1903 </p> 1904 1904 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1> -
draft-ietf-httpbis/latest/p7-auth.html
r2000 r2018 449 449 } 450 450 @bottom-center { 451 content: "Expires May 31, 2013";451 content: "Expires June 2, 2013"; 452 452 } 453 453 @bottom-right { … … 484 484 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 485 485 <link href="p6-cache.html" rel="prev"> 486 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.588, 2012-08-25 12:28:24, XSLT vendor: SAXON 8.9from Saxonica http://www.saxonica.com/">486 <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/"> 487 487 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 488 488 <meta name="dct.creator" content="Fielding, R."> 489 489 <meta name="dct.creator" content="Reschke, J. F."> 490 490 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 491 <meta name="dct.issued" scheme="ISO8601" content="2012-11-2 7">491 <meta name="dct.issued" scheme="ISO8601" content="2012-11-29"> 492 492 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 493 493 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework."> … … 517 517 <tr> 518 518 <td class="left">Intended status: Standards Track</td> 519 <td class="right">November 2 7, 2012</td>519 <td class="right">November 29, 2012</td> 520 520 </tr> 521 521 <tr> 522 <td class="left">Expires: May 31, 2013</td>522 <td class="left">Expires: June 2, 2013</td> 523 523 <td class="right"></td> 524 524 </tr> … … 546 546 in progress”. 547 547 </p> 548 <p>This Internet-Draft will expire on May 31, 2013.</p>548 <p>This Internet-Draft will expire on June 2, 2013.</p> 549 549 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 550 550 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1045 1045 </div> 1046 1046 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFCs 2616 and 2617</a></h1> 1047 <p id="rfc.section.A.p.1">The "realm" parameter is n't required anymore in general; consequently, the ABNF allows challenges without any auth parameters.1047 <p id="rfc.section.A.p.1">The "realm" parameter is no longer always required; consequently, the ABNF allows challenges without any auth parameters. 1048 1048 (<a href="#access.authentication.framework" title="Access Authentication Framework">Section 2</a>) 1049 1049 </p> … … 1051 1051 (<a href="#access.authentication.framework" title="Access Authentication Framework">Section 2</a>) 1052 1052 </p> 1053 <p id="rfc.section.A.p.3"> Introduce Authentication Scheme Registry. (<a href="#authentication.scheme.registry" title="Authentication Scheme Registry">Section 2.3</a>)1053 <p id="rfc.section.A.p.3">This specification introduces the Authentication Scheme Registry. (<a href="#authentication.scheme.registry" title="Authentication Scheme Registry">Section 2.3</a>) 1054 1054 </p> 1055 1055 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
Note: See TracChangeset
for help on using the changeset viewer.