Changeset 1891 for draft-ietf-httpbis/latest
- Timestamp:
- 13/09/12 11:44:49 (8 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 12 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1888 r1891 449 449 } 450 450 @bottom-center { 451 content: "Expires March 1 6, 2013";451 content: "Expires March 17, 2013"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2012-09-1 2">494 <meta name="dct.issued" scheme="ISO8601" content="2012-09-13"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 496 496 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: March 1 6, 2013</td>526 <td class="left">Expires: March 17, 2013</td> 527 527 <td class="right">greenbytes</td> 528 528 </tr> 529 529 <tr> 530 530 <td class="left"></td> 531 <td class="right">September 1 2, 2012</td>531 <td class="right">September 13, 2012</td> 532 532 </tr> 533 533 </tbody> … … 556 556 in progress”. 557 557 </p> 558 <p>This Internet-Draft will expire on March 1 6, 2013.</p>558 <p>This Internet-Draft will expire on March 17, 2013.</p> 559 559 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 560 560 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2860 2860 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>) 2861 2861 </p> 2862 <p id="rfc.section.A.2.p.2">Update use of abs_path production from RFC 1808 to the path-absolute + query components of RFC 3986. State that the asterisk 2863 form is allowed for the OPTIONS request method only. (<a href="#request-target" title="Request Target">Section 5.3</a>) 2864 </p> 2865 <p id="rfc.section.A.2.p.3">Require that invalid whitespace around field-names be rejected. (<a href="#header.fields" title="Header Fields">Section 3.2</a>) 2866 </p> 2867 <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 2862 <p id="rfc.section.A.2.p.2">Require that invalid whitespace around field-names be rejected. Change ABNF productions for header fields to only define the 2863 field value. (<a href="#header.fields" title="Header Fields">Section 3.2</a>) 2864 </p> 2865 <p id="rfc.section.A.2.p.3">Rules about implicit linear whitespace between certain grammar productions have been removed; now whitespace is only allowed 2868 2866 where specifically defined in the ABNF. (<a href="#whitespace" title="Whitespace">Section 3.2.1</a>) 2869 2867 </p> 2870 <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 control2868 <p id="rfc.section.A.2.p.4">The NUL octet is no longer allowed in comment and quoted-string text. The quoted-pair rule no longer allows escaping control 2871 2869 characters other than HTAB. Non-ASCII content in header fields and reason phrase has been obsoleted and made opaque (the TEXT 2872 2870 rule was removed). (<a href="#field.components" title="Field value components">Section 3.2.4</a>) 2873 2871 </p> 2874 <p id="rfc.section.A.2.p.6">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix B</a>) 2875 </p> 2876 <p id="rfc.section.A.2.p.7">Require recipients to handle bogus <a href="#header.content-length" class="smpl">Content-Length</a> header fields as errors. (<a href="#message.body" title="Message Body">Section 3.3</a>) 2877 </p> 2878 <p id="rfc.section.A.2.p.8">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>) 2879 </p> 2880 <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 2872 <p id="rfc.section.A.2.p.5">Require recipients to handle bogus "<a href="#header.content-length" class="smpl">Content-Length</a>" header fields as errors. (<a href="#message.body" title="Message Body">Section 3.3</a>) 2873 </p> 2874 <p id="rfc.section.A.2.p.6">Remove reference to non-existent identity transfer-coding value tokens. (Sections <a href="#message.body" title="Message Body">3.3</a> and <a href="#transfer.codings" title="Transfer Codings">4</a>) 2875 </p> 2876 <p id="rfc.section.A.2.p.7">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. Furthermore 2881 2877 disallowed line folding in chunk extensions, and deprecate their use. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a>) 2882 2878 </p> 2883 <p id="rfc.section.A.2.p.10">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section 7.4</a>) 2884 </p> 2885 <p id="rfc.section.A.2.p.11">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent. 2879 <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 2880 form is allowed for the OPTIONS request method only. (<a href="#request-target" title="Request Target">Section 5.3</a>) 2881 </p> 2882 <p id="rfc.section.A.2.p.9">Clarify exactly when "close" connection options have to be sent; drop notion of header fields being "hop-by-hop" without being 2883 listed in the Connection header field. (<a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section 6.1</a>) 2884 </p> 2885 <p id="rfc.section.A.2.p.10">Remove hard limit of two connections per server. Remove requirement to retry a sequence of requests as long it was idempotent. 2886 2886 Remove requirements about when servers are allowed to close connections prematurely. (<a href="#persistent.connections" title="Persistent Connections">Section 6.2</a>) 2887 2887 </p> 2888 <p id="rfc.section.A.2.p.1 2">Remove requirement to retry requests under certain circumstances when the server prematurely closes the connection. (<a href="#persistent.reuse" title="Reuse">Section 6.2.2</a>)2889 </p> 2890 <p id="rfc.section.A.2.p.1 3">Change ABNF productions for header fields to only define the field value.</p>2891 < p id="rfc.section.A.2.p.14">Clarify exactly when "close" connection options have to be sent; drop notion of header fields being "hop-by-hop" without being2892 listed in the Connection header field. (<a href="#header.connection" id="rfc.xref.header.connection.10" title="Connection">Section 6.1</a>)2893 </p> 2894 <p id="rfc.section.A.2.p.1 5">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.2" title="Upgrade">Section 6.3</a>)2895 </p> 2896 <p id="rfc.section.A.2.p.1 6">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>)2888 <p id="rfc.section.A.2.p.11">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>) 2889 </p> 2890 <p id="rfc.section.A.2.p.12">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.2" title="Upgrade">Section 6.3</a>) 2891 </p> 2892 <p id="rfc.section.A.2.p.13">Registration of Transfer Codings now requires IETF Review (<a href="#transfer.coding.registry" title="Transfer Coding Registry">Section 7.4</a>) 2893 </p> 2894 <p id="rfc.section.A.2.p.14">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>) 2895 </p> 2896 <p id="rfc.section.A.2.p.15">Empty list elements in list productions have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix B</a>) 2897 2897 </p> 2898 2898 <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> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1888 r1891 4758 4758 </t> 4759 4759 <t> 4760 Update use of abs_path production from RFC 1808 to the path-absolute + query4761 components of RFC 3986. State that the asterisk form is allowed for the OPTIONS4762 request method only.4763 (<xref target="request-target"/>)4764 </t>4765 <t>4766 4760 Require that invalid whitespace around field-names be rejected. 4761 Change ABNF productions for header fields to only define the field value. 4767 4762 (<xref target="header.fields"/>) 4768 4763 </t> … … 4781 4776 </t> 4782 4777 <t> 4783 Empty list elements in list productions have been deprecated. 4784 (<xref target="abnf.extension"/>) 4785 </t> 4786 <t> 4787 Require recipients to handle bogus <x:ref>Content-Length</x:ref> header 4778 Require recipients to handle bogus "<x:ref>Content-Length</x:ref>" header 4788 4779 fields as errors. 4789 4780 (<xref target="message.body"/>) … … 4801 4792 </t> 4802 4793 <t> 4803 Registration of Transfer Codings now requires IETF Review 4804 (<xref target="transfer.coding.registry"/>) 4794 Update use of abs_path production from RFC 1808 to the path-absolute + query 4795 components of RFC 3986. State that the asterisk form is allowed for the OPTIONS 4796 request method only. 4797 (<xref target="request-target"/>) 4798 </t> 4799 <t> 4800 Clarify exactly when "close" connection options have to be sent; drop 4801 notion of header fields being "hop-by-hop" without being listed in the 4802 Connection header field. 4803 (<xref target="header.connection"/>) 4805 4804 </t> 4806 4805 <t> … … 4817 4816 </t> 4818 4817 <t> 4819 Change ABNF productions for header fields to only define the field value.4820 </t>4821 <t>4822 Clarify exactly when "close" connection options have to be sent; drop4823 notion of header fields being "hop-by-hop" without being listed in the4824 Connection header field.4825 (<xref target="header.connection"/>)4826 </t>4827 <t>4828 4818 Define the semantics of the <x:ref>Upgrade</x:ref> header field in responses 4829 4819 other than 101 (this was incorporated from <xref target="RFC2817"/>). … … 4831 4821 </t> 4832 4822 <t> 4823 Registration of Transfer Codings now requires IETF Review 4824 (<xref target="transfer.coding.registry"/>) 4825 </t> 4826 <t> 4833 4827 Take over the Upgrade Token Registry, previously defined in 4834 4828 <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>. 4835 4829 (<xref target="upgrade.token.registry"/>) 4830 </t> 4831 <t> 4832 Empty list elements in list productions have been deprecated. 4833 (<xref target="abnf.extension"/>) 4836 4834 </t> 4837 4835 </section> -
draft-ietf-httpbis/latest/p2-semantics.html
r1890 r1891 449 449 } 450 450 @bottom-center { 451 content: "Expires March 1 6, 2013";451 content: "Expires March 17, 2013"; 452 452 } 453 453 @bottom-right { … … 498 498 <meta name="dct.creator" content="Reschke, J. F."> 499 499 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 500 <meta name="dct.issued" scheme="ISO8601" content="2012-09-1 2">500 <meta name="dct.issued" scheme="ISO8601" content="2012-09-13"> 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 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."> … … 529 529 </tr> 530 530 <tr> 531 <td class="left">Expires: March 1 6, 2013</td>531 <td class="left">Expires: March 17, 2013</td> 532 532 <td class="right">greenbytes</td> 533 533 </tr> 534 534 <tr> 535 535 <td class="left"></td> 536 <td class="right">September 1 2, 2012</td>536 <td class="right">September 13, 2012</td> 537 537 </tr> 538 538 </tbody> … … 561 561 in progress”. 562 562 </p> 563 <p>This Internet-Draft will expire on March 1 6, 2013.</p>563 <p>This Internet-Draft will expire on March 17, 2013.</p> 564 564 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 565 565 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 4215 4215 </p> 4216 4216 <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> 4217 <p id="rfc.section.C.p.1">Introduce Method Registry. (<a href="#method.registry" title="Method Registry">Section 10.1</a>) 4217 <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, 4218 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.2.4</a>) 4218 4219 </p> 4219 4220 <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>) … … 4223 4224 <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>) 4224 4225 </p> 4225 <p id="rfc.section.C.p.5">Take over the Status Code Registry, previously 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.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section 10.2</a>) 4226 </p> 4227 <p id="rfc.section.C.p.6">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>) 4228 </p> 4229 <p id="rfc.section.C.p.7">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>) 4230 </p> 4231 <p id="rfc.section.C.p.8">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the 4226 <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>) 4227 </p> 4228 <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 4229 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>) 4230 </p> 4231 <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>) 4232 </p> 4233 <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>) 4234 </p> 4235 <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>) 4236 </p> 4237 <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>) 4238 </p> 4239 <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 4232 4240 user agent is able to make that determination based on the request method semantics. Furthermore, allow user agents to rewrite 4233 4241 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>) 4234 4242 </p> 4235 <p id="rfc.section.C.p. 9">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 through4243 <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 4236 4244 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. 4237 4245 (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section 7.4.5</a>) 4238 4246 </p> 4239 <p id="rfc.section.C.p.10">Define status <a href="#status.426" class="smpl">426 (Upgrade Required)</a> (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><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>) 4240 </p> 4241 <p id="rfc.section.C.p.11">Change ABNF productions for header fields to only define the field value.</p> 4242 <p id="rfc.section.C.p.12">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 4247 <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>) 4248 </p> 4249 <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 4250 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.1</a>) 4251 </p> 4252 <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 4243 4253 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>) 4244 4254 </p> 4245 <p id="rfc.section.C.p.13">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 4246 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>) 4247 </p> 4248 <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 4249 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.1</a>) 4250 </p> 4251 <p id="rfc.section.C.p.15">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>) 4252 </p> 4253 <p id="rfc.section.C.p.16">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>) 4254 </p> 4255 <p id="rfc.section.C.p.17">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 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>) 4256 </p> 4257 <p id="rfc.section.C.p.18">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section 9.3</a>) 4255 <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 4256 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>) 4257 </p> 4258 <p id="rfc.section.C.p.17">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section 9.3</a>) 4259 </p> 4260 <p id="rfc.section.C.p.18">Remove the default character encoding of "ISO-8859-1" for text media types; the default now is whatever the media type definition 4261 says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 9.5.1</a>) 4258 4262 </p> 4259 4263 <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 10.4</a>) 4260 4264 </p> 4261 <p id="rfc.section.C.p.20">Remove the default character encoding of "ISO-8859-1" for text media types; the default now is whatever the media type definition 4262 says. (<a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 9.5.1</a>) 4263 </p> 4264 <p id="rfc.section.C.p.21">Change ABNF productions for header fields to only define the field value.</p> 4265 <p id="rfc.section.C.p.22">Remove definition of Content-MD5 header field because it was inconsistently implemented with respect to partial responses, 4265 <p id="rfc.section.C.p.20">Remove definition of "Content-MD5 header" field because it was inconsistently implemented with respect to partial responses, 4266 4266 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). 4267 4267 </p> 4268 <p id="rfc.section.C.p.23">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>) 4269 </p> 4270 <p id="rfc.section.C.p.24">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, 4271 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.2.4</a>) 4272 </p> 4273 <p id="rfc.section.C.p.25">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>) 4274 </p> 4275 <p id="rfc.section.C.p.26">Remove discussion of Content-Disposition header field, it 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>) 4268 <p id="rfc.section.C.p.21">Introduce Method Registry. (<a href="#method.registry" title="Method Registry">Section 10.1</a>) 4269 </p> 4270 <p id="rfc.section.C.p.22">Take over the Status Code Registry, previously 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 10.2</a>) 4271 </p> 4272 <p id="rfc.section.C.p.23">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>) 4273 </p> 4274 <p id="rfc.section.C.p.24">Remove discussion of Content-Disposition header field, it 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>) 4276 4275 </p> 4277 4276 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1> … … 5387 5386 </li> 5388 5387 <li><em>RFC2817</em> <a href="#rfc.xref.RFC2817.1">10.2</a>, <a href="#RFC2817"><b>13.2</b></a>, <a href="#rfc.xref.RFC2817.2">C</a>, <a href="#rfc.xref.RFC2817.3">C</a>, <a href="#rfc.xref.RFC2817.4">C</a><ul> 5389 <li><em>Section 7.1</em> <a href="#rfc.xref.RFC2817.1">10.2</a>, <a href="#rfc.xref.RFC2817. 3">C</a></li>5388 <li><em>Section 7.1</em> <a href="#rfc.xref.RFC2817.1">10.2</a>, <a href="#rfc.xref.RFC2817.4">C</a></li> 5390 5389 </ul> 5391 5390 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1890 r1891 5785 5785 <section title="Changes from RFC 2616" anchor="changes.from.rfc.2616"> 5786 5786 <t> 5787 Introduce Method Registry. 5788 (<xref target="method.registry"/>) 5787 Remove base URI setting semantics for "<x:ref>Content-Location</x:ref>" due to 5788 poor implementation support, which was caused by too many broken servers emitting 5789 bogus Content-Location header fields, and also the potentially undesirable effect 5790 of potentially breaking relative links in content-negotiated resources. 5791 (<xref target="header.content-location"/>) 5789 5792 </t> 5790 5793 <t> … … 5802 5805 </t> 5803 5806 <t> 5804 Take over the Status Code Registry, previously defined in 5805 <xref target="RFC2817" x:fmt="of" x:sec="7.1"/>. 5806 (<xref target="status.code.registry"/>) 5807 Restrict "<x:ref>Max-Forwards</x:ref>" header field to OPTIONS and TRACE 5808 (previously, extension methods could have used it as well). 5809 (<xref target="header.max-forwards"/>) 5810 </t> 5811 <t> 5812 The ABNF for the "<x:ref>Expect</x:ref>" header field has been both fixed 5813 (allowing parameters for value-less expectations as well) and simplified 5814 (allowing trailing semicolons after "100-continue" when they were invalid 5815 before). 5816 (<xref target="header.expect"/>) 5817 </t> 5818 <t> 5819 Remove ISO-8859-1 special-casing in <x:ref>Accept-Charset</x:ref>. 5820 (<xref target="header.accept-charset"/>) 5821 </t> 5822 <t> 5823 Allow "<x:ref>Referer</x:ref>" field value of "about:blank" as alternative to 5824 not specifying it. 5825 (<xref target="header.referer"/>) 5807 5826 </t> 5808 5827 <t> … … 5840 5859 </t> 5841 5860 <t> 5842 Change ABNF productions for header fields to only define the field value. 5861 Correct syntax of "<x:ref>Location</x:ref>" header field to allow URI 5862 references (including relative references and fragments), as referred symbol 5863 "absoluteURI" wasn't what was expected, and add some clarifications as to 5864 when use of fragments would not be appropriate. 5865 (<xref target="header.location"/>) 5843 5866 </t> 5844 5867 <t> … … 5850 5873 </t> 5851 5874 <t> 5852 The ABNF for the <x:ref>Expect</x:ref> header field has been both fixed 5853 (allowing parameters for value-less expectations as well) and simplified 5854 (allowing trailing semicolons after "100-continue" when they were invalid 5855 before). 5856 (<xref target="header.expect"/>) 5857 </t> 5858 <t> 5859 Correct syntax of <x:ref>Location</x:ref> header field to allow URI 5860 references (including relative references and fragments), as referred symbol 5861 "absoluteURI" wasn't what was expected, and add some clarifications as to 5862 when use of fragments would not be appropriate. 5863 (<xref target="header.location"/>) 5864 </t> 5865 <t> 5866 Restrict <x:ref>Max-Forwards</x:ref> header field to OPTIONS and TRACE 5867 (previously, extension methods could have used it as well). 5868 (<xref target="header.max-forwards"/>) 5869 </t> 5870 <t> 5871 Allow <x:ref>Referer</x:ref> field value of "about:blank" as alternative to 5872 not specifying it. 5873 (<xref target="header.referer"/>) 5874 </t> 5875 <t> 5876 In the description of the <x:ref>Server</x:ref> header field, the 5877 <x:ref>Via</x:ref> field was described as a SHOULD. The requirement was and 5875 In the description of the "<x:ref>Server</x:ref>" header field, the 5876 "<x:ref>Via</x:ref>" field was described as a SHOULD. The requirement was and 5878 5877 is stated correctly in the description of the Via header field in 5879 5878 &header-via;. … … 5885 5884 </t> 5886 5885 <t> 5887 Registration of Content Codings now requires IETF Review5888 (<xref target="content.coding.registry"/>)5889 </t>5890 <t>5891 5886 Remove the default character encoding of "ISO-8859-1" for text media types; the 5892 5887 default now is whatever the media type definition says. … … 5894 5889 </t> 5895 5890 <t> 5896 Change ABNF productions for header fields to only define the field value. 5897 </t> 5898 <t> 5899 Remove definition of Content-MD5 header field because it was inconsistently 5891 Registration of Content Codings now requires IETF Review 5892 (<xref target="content.coding.registry"/>) 5893 </t> 5894 <t> 5895 Remove definition of "Content-MD5 header" field because it was inconsistently 5900 5896 implemented with respect to partial responses, and also because of known 5901 5897 deficiencies in the hash algorithm itself (see <xref target="RFC6151"/> for details). 5902 5898 </t> 5903 5899 <t> 5904 Remove ISO-8859-1 special-casing in <x:ref>Accept-Charset</x:ref>. 5905 (<xref target="header.accept-charset"/>) 5906 </t> 5907 <t> 5908 Remove base URI setting semantics for <x:ref>Content-Location</x:ref> due to 5909 poor implementation support, which was caused by too many broken servers emitting 5910 bogus Content-Location header fields, and also the potentially undesirable effect 5911 of potentially breaking relative links in content-negotiated resources. 5912 (<xref target="header.content-location"/>) 5900 Introduce Method Registry. 5901 (<xref target="method.registry"/>) 5902 </t> 5903 <t> 5904 Take over the Status Code Registry, previously defined in 5905 <xref target="RFC2817" x:fmt="of" x:sec="7.1"/>. 5906 (<xref target="status.code.registry"/>) 5913 5907 </t> 5914 5908 <t> -
draft-ietf-httpbis/latest/p4-conditional.html
r1889 r1891 449 449 } 450 450 @bottom-center { 451 content: "Expires March 1 6, 2013";451 content: "Expires March 17, 2013"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2012-09-1 2">494 <meta name="dct.issued" scheme="ISO8601" content="2012-09-13"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 496 496 <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."> … … 518 518 </tr> 519 519 <tr> 520 <td class="left">Expires: March 1 6, 2013</td>520 <td class="left">Expires: March 17, 2013</td> 521 521 <td class="right">J. Reschke, Editor</td> 522 522 </tr> … … 527 527 <tr> 528 528 <td class="left"></td> 529 <td class="right">September 1 2, 2012</td>529 <td class="right">September 13, 2012</td> 530 530 </tr> 531 531 </tbody> … … 554 554 in progress”. 555 555 </p> 556 <p>This Internet-Draft will expire on March 1 6, 2013.</p>556 <p>This Internet-Draft will expire on March 17, 2013.</p> 557 557 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 558 558 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1315 1315 <p id="rfc.section.A.p.1">Allow weak entity-tags 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>). 1316 1316 </p> 1317 <p id="rfc.section.A.p.2">Change <a href="#header.etag" class="smpl">ETag</a> header field ABNF not to use quoted-string, thus avoiding escaping issues. (<a href="#header.etag" id="rfc.xref.header.etag.3" title="ETag">Section 2.3</a>) 1318 </p> 1319 <p id="rfc.section.A.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Precondition Header Fields">Section 3</a>) 1317 <p id="rfc.section.A.p.2">Change "<a href="#header.etag" class="smpl">ETag</a>" header field ABNF not to use quoted-string, thus avoiding escaping issues. (<a href="#header.etag" id="rfc.xref.header.etag.3" title="ETag">Section 2.3</a>) 1320 1318 </p> 1321 1319 <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/p4-conditional.xml
r1889 r1891 1407 1407 </t> 1408 1408 <t> 1409 Change <x:ref>ETag</x:ref>header field ABNF not to use quoted-string, thus1409 Change "<x:ref>ETag</x:ref>" header field ABNF not to use quoted-string, thus 1410 1410 avoiding escaping issues. 1411 1411 (<xref target="header.etag"/>) 1412 </t>1413 <t>1414 Change ABNF productions for header fields to only define the field value.1415 (<xref target="header.field.definitions"/>)1416 1412 </t> 1417 1413 </section> -
draft-ietf-httpbis/latest/p5-range.html
r1889 r1891 449 449 } 450 450 @bottom-center { 451 content: "Expires March 1 6, 2013";451 content: "Expires March 17, 2013"; 452 452 } 453 453 @bottom-right { … … 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-09-1 2">495 <meta name="dct.issued" scheme="ISO8601" content="2012-09-13"> 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: March 1 6, 2013</td>521 <td class="left">Expires: March 17, 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">September 1 2, 2012</td>530 <td class="right">September 13, 2012</td> 531 531 </tr> 532 532 </tbody> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on March 1 6, 2013.</p>555 <p>This Internet-Draft will expire on March 17, 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> … … 1237 1237 <p id="rfc.section.B.p.2">Clarify that it is not ok to use a weak validator 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>) 1238 1238 </p> 1239 <p id="rfc.section.B.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 5</a>) 1240 </p> 1241 <p id="rfc.section.B.p.4">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>) 1239 <p id="rfc.section.B.p.3">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>) 1242 1240 </p> 1243 1241 <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/p5-range.xml
r1889 r1891 1324 1324 </t> 1325 1325 <t> 1326 Change ABNF productions for header fields to only define the field value.1327 (<xref target="header.field.definitions"/>)1328 </t>1329 <t>1330 1326 Clarify that multipart/byteranges can consist of a single part. 1331 1327 (<xref target="internet.media.type.multipart.byteranges"/>) -
draft-ietf-httpbis/latest/p6-cache.html
r1889 r1891 452 452 } 453 453 @bottom-center { 454 content: "Expires March 1 6, 2013";454 content: "Expires March 17, 2013"; 455 455 } 456 456 @bottom-right { … … 499 499 <meta name="dct.creator" content="Reschke, J. F."> 500 500 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 501 <meta name="dct.issued" scheme="ISO8601" content="2012-09-1 2">501 <meta name="dct.issued" scheme="ISO8601" content="2012-09-13"> 502 502 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 503 503 <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."> … … 525 525 </tr> 526 526 <tr> 527 <td class="left">Expires: March 1 6, 2013</td>527 <td class="left">Expires: March 17, 2013</td> 528 528 <td class="right">M. Nottingham, Editor</td> 529 529 </tr> … … 538 538 <tr> 539 539 <td class="left"></td> 540 <td class="right">September 1 2, 2012</td>540 <td class="right">September 13, 2012</td> 541 541 </tr> 542 542 </tbody> … … 564 564 in progress”. 565 565 </p> 566 <p>This Internet-Draft will expire on March 1 6, 2013.</p>566 <p>This Internet-Draft will expire on March 17, 2013.</p> 567 567 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 568 568 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1925 1925 <p id="rfc.section.A.p.1">Make the specified age calculation algorithm less conservative. (<a href="#age.calculations" title="Calculating Age">Section 4.1.3</a>) 1926 1926 </p> 1927 <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 order to determine the appropriate response to use. (<a href="#validation.model" title="Validation Model">Section 4.2</a>)1927 <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 order to determine the appropriate response to use. (<a href="#validation.model" title="Validation Model">Section 4.2</a>) 1928 1928 </p> 1929 1929 <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>) 1930 1930 </p> 1931 <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 7</a>) 1932 </p> 1933 <p id="rfc.section.A.p.5">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 were implemented. (<a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">Section 7.5</a>) 1934 </p> 1935 <p id="rfc.section.A.p.6">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>) 1931 <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 were implemented. (<a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">Section 7.5</a>) 1932 </p> 1933 <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>) 1936 1934 </p> 1937 1935 <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/p6-cache.xml
r1889 r1891 2462 2462 </t> 2463 2463 <t> 2464 Remove requirement to consider <x:ref>Content-Location</x:ref>in successful2464 Remove requirement to consider "<x:ref>Content-Location</x:ref>" in successful 2465 2465 responses in order to determine the appropriate response to use. 2466 2466 (<xref target="validation.model" />) … … 2471 2471 </t> 2472 2472 <t> 2473 Change ABNF productions for header fields to only define the field value. 2474 (<xref target="header.field.definitions"/>) 2475 </t> 2476 <t> 2477 Do not mention RFC 2047 encoding and multiple languages in <x:ref>Warning</x:ref> 2473 Do not mention RFC 2047 encoding and multiple languages in "<x:ref>Warning</x:ref>" 2478 2474 header fields anymore, as these aspects never were implemented. 2479 2475 (<xref target="header.warning" />) -
draft-ietf-httpbis/latest/p7-auth.html
r1889 r1891 449 449 } 450 450 @bottom-center { 451 content: "Expires March 1 6, 2013";451 content: "Expires March 17, 2013"; 452 452 } 453 453 @bottom-right { … … 490 490 <meta name="dct.creator" content="Reschke, J. F."> 491 491 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 492 <meta name="dct.issued" scheme="ISO8601" content="2012-09-1 2">492 <meta name="dct.issued" scheme="ISO8601" content="2012-09-13"> 493 493 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 494 494 <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."> … … 521 521 </tr> 522 522 <tr> 523 <td class="left">Expires: March 1 6, 2013</td>523 <td class="left">Expires: March 17, 2013</td> 524 524 <td class="right">greenbytes</td> 525 525 </tr> 526 526 <tr> 527 527 <td class="left"></td> 528 <td class="right">September 1 2, 2012</td>528 <td class="right">September 13, 2012</td> 529 529 </tr> 530 530 </tbody> … … 551 551 in progress”. 552 552 </p> 553 <p>This Internet-Draft will expire on March 1 6, 2013.</p>553 <p>This Internet-Draft will expire on March 17, 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> … … 1076 1076 </p> 1077 1077 <p id="rfc.section.A.p.3">Introduce Authentication Scheme Registry. (<a href="#authentication.scheme.registry" title="Authentication Scheme Registry">Section 2.3</a>) 1078 </p>1079 <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section 4</a>)1080 1078 </p> 1081 1079 <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.xml
r1889 r1891 1069 1069 (<xref target="authentication.scheme.registry"/>) 1070 1070 </t> 1071 <t>1072 Change ABNF productions for header fields to only define the field value.1073 (<xref target="header.field.definitions"/>)1074 </t>1075 1071 </section> 1076 1072
Note: See TracChangeset
for help on using the changeset viewer.