Changeset 1844 for draft-ietf-httpbis
- Timestamp:
- 01/09/12 07:03:26 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1843 r1844 449 449 } 450 450 @bottom-center { 451 content: "Expires March 4,2013";451 content: "Expires February 2013"; 452 452 } 453 453 @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-p2-semantics-latest"> 501 <meta name="dct.issued" scheme="ISO8601" content="2012-08 -31">501 <meta name="dct.issued" scheme="ISO8601" content="2012-08"> 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 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."> … … 530 530 </tr> 531 531 <tr> 532 <td class="left">Expires: March 4,2013</td>532 <td class="left">Expires: February 2013</td> 533 533 <td class="right">greenbytes</td> 534 534 </tr> 535 535 <tr> 536 536 <td class="left"></td> 537 <td class="right">August 31,2012</td>537 <td class="right">August 2012</td> 538 538 </tr> 539 539 </tbody> … … 562 562 in progress”. 563 563 </p> 564 <p>This Internet-Draft will expire on March 4,2013.</p>564 <p>This Internet-Draft will expire in February 2013.</p> 565 565 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 566 566 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 3095 3095 </pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 3096 3096 <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a> <a id="method.registry" href="#method.registry">Method Registry</a></h2> 3097 <p id="rfc.section.11.1.p.1">The HTTP Method Registry defines the name space for the method token in the Request line of an HTTP request.</p> 3097 <p id="rfc.section.11.1.p.1">The HTTP Method Registry defines the name space for the request method token (<a href="#methods" title="Request Methods">Section 3</a>). The method registry is maintained at <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>>. 3098 </p> 3098 3099 <h3 id="rfc.section.11.1.1"><a href="#rfc.section.11.1.1">11.1.1</a> <a id="method.procedure" href="#method.procedure">Procedure</a></h3> 3099 <p id="rfc.section.11.1.1.p.1"> Registrations <em class="bcp14">MUST</em> include the following fields:3100 <p id="rfc.section.11.1.1.p.1">HTTP method registrations <em class="bcp14">MUST</em> include the following fields: 3100 3101 </p> 3101 3102 <ul> … … 3109 3110 </ul> 3110 3111 <p id="rfc.section.11.1.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 3111 </p>3112 <p id="rfc.section.11.1.1.p.3">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>>.3113 3112 </p> 3114 3113 <h3 id="rfc.section.11.1.2"><a href="#rfc.section.11.1.2">11.1.2</a> <a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3> … … 3122 3121 a Content-Length header field with a value of "0". 3123 3122 </p> 3124 <p id="rfc.section.11.1.2.p.3">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section 3.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section 3.2.2</a>), orcacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section 3.2.3</a>), and what semantics are to be associated with the request body if any is present in the request. If a method is cacheable,3123 <p id="rfc.section.11.1.2.p.3">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section 3.2.1</a>), idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section 3.2.2</a>), cacheable (<a href="#cacheable.methods" title="Cacheable Methods">Section 3.2.3</a>), and what semantics are to be associated with the request body if any is present in the request. If a method is cacheable, 3125 3124 the method definition ought to describe how, and under what conditions, a cache can store a response and use it to satisfy 3126 3125 a subsequent request. 3127 3126 </p> 3128 3127 <h3 id="rfc.section.11.1.3"><a href="#rfc.section.11.1.3">11.1.3</a> <a id="method.registration" href="#method.registration">Registrations</a></h3> 3129 <p id="rfc.section.11.1.3.p.1">The HTTP Method Registry shall be created at <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>> and be populated with the registrations below: 3130 </p> 3128 <p id="rfc.section.11.1.3.p.1">The HTTP Method Registry shall be populated with the registrations below:</p> 3131 3129 <div id="rfc.table.2"> 3132 3130 <div id="iana.method.registration.table"></div> … … 3201 3199 </div> 3202 3200 <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a> <a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2> 3203 <p id="rfc.section.11.2.p.1">The HTTP Status Code Registry defines the name space for the status-code token in the status-line of an HTTP response (<a href="#status.codes" title="Response Status Codes">Section 5</a>). 3201 <p id="rfc.section.11.2.p.1">The HTTP Status Code Registry defines the name space for the response status-code token (<a href="#status.codes" title="Response Status Codes">Section 5</a>). The status code registry is maintained at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>>. 3202 </p> 3203 <p id="rfc.section.11.2.p.2">This section replaces the registration procedure for HTTP Status Codes 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.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. 3204 3204 </p> 3205 3205 <h3 id="rfc.section.11.2.1"><a href="#rfc.section.11.2.1">11.2.1</a> <a id="status.code.procedure" href="#status.code.procedure">Procedure</a></h3> 3206 <p id="rfc.section.11.2.1.p.1">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 3207 </p> 3208 <p id="rfc.section.11.2.1.p.2">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>>. 3206 <p id="rfc.section.11.2.1.p.1">Values to be added to the HTTP status code name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 3209 3207 </p> 3210 3208 <h3 id="rfc.section.11.2.2"><a href="#rfc.section.11.2.2">11.2.2</a> <a id="considerations.for.new.status.codes" href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h3> … … 3226 3224 </p> 3227 3225 <h3 id="rfc.section.11.2.3"><a href="#rfc.section.11.2.3">11.2.3</a> <a id="status.code.registration" href="#status.code.registration">Registrations</a></h3> 3228 <p id="rfc.section.11.2.3.p.1">The registration procedure for HTTP Status Codes — 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.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> — is now defined by <a href="#status.code.registry" title="Status Code Registry">Section 11.2</a> of this document. 3229 </p> 3230 <p id="rfc.section.11.2.3.p.2">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below: 3231 </p> 3226 <p id="rfc.section.11.2.3.p.1">The HTTP Status Code Registry shall be updated with the registrations below:</p> 3232 3227 <div id="rfc.table.3"> 3233 3228 <div id="iana.status.code.registration.table"></div> … … 3461 3456 </div> 3462 3457 <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a> <a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2> 3463 <p id="rfc.section.11.3.p.1"> The Message Header Field Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.3"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):3458 <p id="rfc.section.11.3.p.1">HTTP header fields are registered within the Message Header Field Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> (see <a href="#RFC3864" id="rfc.xref.RFC3864.3"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>). The Message Header Field Registry shall be updated with the permanent registrations below: 3464 3459 </p> 3465 3460 <div id="rfc.table.4"> … … 3611 3606 </table> 3612 3607 </div> 3613 <p id="rfc.section.11.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>3608 <p id="rfc.section.11.3.p.2">The change controller for the above registrations is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 3614 3609 <h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a> <a id="content.coding.registry" href="#content.coding.registry">Content Coding Registry</a></h2> 3615 <p id="rfc.section.11.4.p.1">The HTTP Content Coding Registry defines the name space for the content coding names.</p> 3610 <p id="rfc.section.11.4.p.1">The HTTP Content Coding Registry defines the name space for content coding names (<a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>). The content coding registry is maintained at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>. 3611 </p> 3616 3612 <h3 id="rfc.section.11.4.1"><a href="#rfc.section.11.4.1">11.4.1</a> <a id="content.coding.procedure" href="#content.coding.procedure">Procedure</a></h3> 3617 <p id="rfc.section.11.4.1.p.1"> Registrations <em class="bcp14">MUST</em> include the following fields:3613 <p id="rfc.section.11.4.1.p.1">Content Coding registrations <em class="bcp14">MUST</em> include the following fields: 3618 3614 </p> 3619 3615 <ul> … … 3622 3618 <li>Pointer to specification text</li> 3623 3619 </ul> 3624 <p id="rfc.section.11.4.1.p.2">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1. 39"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>).3620 <p id="rfc.section.11.4.1.p.2">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>). 3625 3621 </p> 3626 3622 <p id="rfc.section.11.4.1.p.3">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section. 3627 3623 </p> 3628 <p id="rfc.section.11.4.1.p.4">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>.3629 </p>3630 3624 <h3 id="rfc.section.11.4.2"><a href="#rfc.section.11.4.2">11.4.2</a> <a id="content.coding.registration" href="#content.coding.registration">Registrations</a></h3> 3631 <p id="rfc.section.11.4.2.p.1">The registration procedure for HTTP Content Codings is now defined by <a href="#content.coding.registry" title="Content Coding Registry">Section 11.4</a> of this document. 3632 </p> 3633 <p id="rfc.section.11.4.2.p.2">The HTTP Content Codings Registry located at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>> shall be updated with the registration below: 3634 </p> 3625 <p id="rfc.section.11.4.2.p.1">The HTTP Content Codings Registry shall be updated with the registrations below:</p> 3635 3626 <div id="rfc.table.5"> 3636 3627 <div id="iana.content.coding.registration.table"></div> … … 3647 3638 <td class="left">compress</td> 3648 3639 <td class="left">UNIX "compress" program method</td> 3649 <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.4 1"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>3640 <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a> 3650 3641 </td> 3651 3642 </tr> … … 3654 3645 <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>) 3655 3646 </td> 3656 <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.4 2"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>3647 <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a> 3657 3648 </td> 3658 3649 </tr> … … 3660 3651 <td class="left">gzip</td> 3661 3652 <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td> 3662 <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.4 3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>3653 <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a> 3663 3654 </td> 3664 3655 </tr> … … 3752 3743 </p> 3753 3744 <h1 id="rfc.section.13"><a href="#rfc.section.13">13.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 3754 <p id="rfc.section.13.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.4 4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>.3745 <p id="rfc.section.13.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.45"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>. 3755 3746 </p> 3756 3747 <h1 id="rfc.references"><a id="rfc.section.14" href="#rfc.section.14">14.</a> References … … 4065 4056 <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 10.15</a>) 4066 4057 </p> 4067 <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.4 5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 10.17</a>)4058 <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.46"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 10.17</a>) 4068 4059 </p> 4069 4060 <p id="rfc.section.C.p.18">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section 6.3</a>) … … 4093 4084 (any visible US-ASCII character). 4094 4085 </p> 4095 <p id="rfc.section.D.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.4 6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>:4096 </p> 4097 <div id="rfc.figure.u.63"></div><pre class="inline"> <a href="#imported.abnf" class="smpl">BWS</a> = <BWS, defined in <a href="#Part1" id="rfc.xref.Part1.4 7"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>>4098 <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.4 8"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>>4099 <a href="#imported.abnf" class="smpl">RWS</a> = <RWS, defined in <a href="#Part1" id="rfc.xref.Part1. 49"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>>4100 <a href="#imported.abnf" class="smpl">quoted-string</a> = <quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.5 0"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>>4101 <a href="#imported.abnf" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.5 1"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>>4102 <a href="#imported.abnf" class="smpl">word</a> = <word, defined in <a href="#Part1" id="rfc.xref.Part1.5 2"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>>4086 <p id="rfc.section.D.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.47"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>: 4087 </p> 4088 <div id="rfc.figure.u.63"></div><pre class="inline"> <a href="#imported.abnf" class="smpl">BWS</a> = <BWS, defined in <a href="#Part1" id="rfc.xref.Part1.48"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>> 4089 <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.49"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>> 4090 <a href="#imported.abnf" class="smpl">RWS</a> = <RWS, defined in <a href="#Part1" id="rfc.xref.Part1.50"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>> 4091 <a href="#imported.abnf" class="smpl">quoted-string</a> = <quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.51"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>> 4092 <a href="#imported.abnf" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.52"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>> 4093 <a href="#imported.abnf" class="smpl">word</a> = <word, defined in <a href="#Part1" id="rfc.xref.Part1.53"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>> 4103 4094 4104 <a href="#imported.abnf" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.5 3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>>4105 <a href="#imported.abnf" class="smpl">comment</a> = <comment, defined in <a href="#Part1" id="rfc.xref.Part1.5 4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>>4106 <a href="#imported.abnf" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.5 5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>>4107 <a href="#imported.abnf" class="smpl">URI-reference</a> = <URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.5 6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>>4095 <a href="#imported.abnf" class="smpl">absolute-URI</a> = <absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.54"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>> 4096 <a href="#imported.abnf" class="smpl">comment</a> = <comment, defined in <a href="#Part1" id="rfc.xref.Part1.55"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>> 4097 <a href="#imported.abnf" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.56"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>> 4098 <a href="#imported.abnf" class="smpl">URI-reference</a> = <URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.57"><cite title="HTTP/1.1, part 1: Message Routing and Syntax"">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>> 4108 4099 </pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 4109 4100 <div id="rfc.figure.u.64"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [ … … 5039 5030 </li> 5040 5031 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 5041 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">3.3.1</a>, <a href="#rfc.xref.Part1.8">3.3.7</a>, <a href="#rfc.xref.Part1.9">3.3.7</a>, <a href="#rfc.xref.Part1.10">3.3.8</a>, <a href="#rfc.xref.Part1.11">4</a>, <a href="#rfc.xref.Part1.12">4.5</a>, <a href="#rfc.xref.Part1.13">4.5</a>, <a href="#rfc.xref.Part1.14">4.5</a>, <a href="#rfc.xref.Part1.15">4.5</a>, <a href="#rfc.xref.Part1.16">4.5</a>, <a href="#rfc.xref.Part1.17">4.6</a>, <a href="#rfc.xref.Part1.18">4.6</a>, <a href="#rfc.xref.Part1.19">4.7</a>, <a href="#rfc.xref.Part1.20">5.2.1</a>, <a href="#rfc.xref.Part1.21">5.2.2</a>, <a href="#rfc.xref.Part1.22">5.3.4</a>, <a href="#rfc.xref.Part1.23">5.3.6</a>, <a href="#rfc.xref.Part1.24">5.5.15</a>, <a href="#rfc.xref.Part1.25">5.6.6</a>, <a href="#rfc.xref.Part1.26">6.4</a>, <a href="#rfc.xref.Part1.27">6.4</a>, <a href="#rfc.xref.Part1.28">6.4</a>, <a href="#rfc.xref.Part1.29">7.1</a>, <a href="#rfc.xref.Part1.30">7.2</a>, <a href="#rfc.xref.Part1.31">8</a>, <a href="#rfc.xref.Part1.32">8.1</a>, <a href="#rfc.xref.Part1.33">10.8</a>, <a href="#rfc.xref.Part1.34">10.11</a>, <a href="#rfc.xref.Part1.35">10.17</a>, <a href="#rfc.xref.Part1.36">10.17</a>, <a href="#rfc.xref.Part1.37">10.18</a>, <a href="#rfc.xref.Part1.38">11.1.2</a>, <a href="#rfc.xref.Part1.39">11.4 .1</a>, <a href="#rfc.xref.Part1.40">11.4.1</a>, <a href="#rfc.xref.Part1.41">11.4.2</a>, <a href="#rfc.xref.Part1.42">11.4.2</a>, <a href="#rfc.xref.Part1.43">11.4.2</a>, <a href="#rfc.xref.Part1.44">13</a>, <a href="#Part1"><b>14.1</b></a>, <a href="#rfc.xref.Part1.45">C</a>, <a href="#rfc.xref.Part1.46">D</a>, <a href="#rfc.xref.Part1.47">D</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.55">D</a>, <a href="#rfc.xref.Part1.56">D</a><ul>5032 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">3.3.1</a>, <a href="#rfc.xref.Part1.8">3.3.7</a>, <a href="#rfc.xref.Part1.9">3.3.7</a>, <a href="#rfc.xref.Part1.10">3.3.8</a>, <a href="#rfc.xref.Part1.11">4</a>, <a href="#rfc.xref.Part1.12">4.5</a>, <a href="#rfc.xref.Part1.13">4.5</a>, <a href="#rfc.xref.Part1.14">4.5</a>, <a href="#rfc.xref.Part1.15">4.5</a>, <a href="#rfc.xref.Part1.16">4.5</a>, <a href="#rfc.xref.Part1.17">4.6</a>, <a href="#rfc.xref.Part1.18">4.6</a>, <a href="#rfc.xref.Part1.19">4.7</a>, <a href="#rfc.xref.Part1.20">5.2.1</a>, <a href="#rfc.xref.Part1.21">5.2.2</a>, <a href="#rfc.xref.Part1.22">5.3.4</a>, <a href="#rfc.xref.Part1.23">5.3.6</a>, <a href="#rfc.xref.Part1.24">5.5.15</a>, <a href="#rfc.xref.Part1.25">5.6.6</a>, <a href="#rfc.xref.Part1.26">6.4</a>, <a href="#rfc.xref.Part1.27">6.4</a>, <a href="#rfc.xref.Part1.28">6.4</a>, <a href="#rfc.xref.Part1.29">7.1</a>, <a href="#rfc.xref.Part1.30">7.2</a>, <a href="#rfc.xref.Part1.31">8</a>, <a href="#rfc.xref.Part1.32">8.1</a>, <a href="#rfc.xref.Part1.33">10.8</a>, <a href="#rfc.xref.Part1.34">10.11</a>, <a href="#rfc.xref.Part1.35">10.17</a>, <a href="#rfc.xref.Part1.36">10.17</a>, <a href="#rfc.xref.Part1.37">10.18</a>, <a href="#rfc.xref.Part1.38">11.1.2</a>, <a href="#rfc.xref.Part1.39">11.4</a>, <a href="#rfc.xref.Part1.40">11.4.1</a>, <a href="#rfc.xref.Part1.41">11.4.1</a>, <a href="#rfc.xref.Part1.42">11.4.2</a>, <a href="#rfc.xref.Part1.43">11.4.2</a>, <a href="#rfc.xref.Part1.44">11.4.2</a>, <a href="#rfc.xref.Part1.45">13</a>, <a href="#Part1"><b>14.1</b></a>, <a href="#rfc.xref.Part1.46">C</a>, <a href="#rfc.xref.Part1.47">D</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.55">D</a>, <a href="#rfc.xref.Part1.56">D</a>, <a href="#rfc.xref.Part1.57">D</a><ul> 5042 5033 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.3">1.2</a></li> 5043 5034 <li><em>Section 2.3</em> <a href="#rfc.xref.Part1.22">5.3.4</a></li> 5044 5035 <li><em>Section 2.5</em> <a href="#rfc.xref.Part1.2">1.1</a></li> 5045 5036 <li><em>Section 2.6</em> <a href="#rfc.xref.Part1.25">5.6.6</a></li> 5046 <li><em>Section 2.7</em> <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5 3">D</a>, <a href="#rfc.xref.Part1.55">D</a>, <a href="#rfc.xref.Part1.56">D</a></li>5037 <li><em>Section 2.7</em> <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.56">D</a>, <a href="#rfc.xref.Part1.57">D</a></li> 5047 5038 <li><em>Section 3.2</em> <a href="#rfc.xref.Part1.11">4</a>, <a href="#rfc.xref.Part1.14">4.5</a>, <a href="#rfc.xref.Part1.35">10.17</a>, <a href="#rfc.xref.Part1.37">10.18</a></li> 5048 <li><em>Section 3.2.1</em> <a href="#rfc.xref.Part1.4 7">D</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a></li>5049 <li><em>Section 3.2.4</em> <a href="#rfc.xref.Part1.13">4.5</a>, <a href="#rfc.xref.Part1.5 0">D</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.54">D</a></li>5039 <li><em>Section 3.2.1</em> <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a></li> 5040 <li><em>Section 3.2.4</em> <a href="#rfc.xref.Part1.13">4.5</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.55">D</a></li> 5050 5041 <li><em>Section 3.3</em> <a href="#rfc.xref.Part1.23">5.3.6</a>, <a href="#rfc.xref.Part1.30">7.2</a>, <a href="#rfc.xref.Part1.31">8</a>, <a href="#rfc.xref.Part1.38">11.1.2</a></li> 5051 5042 <li><em>Section 3.3.2</em> <a href="#rfc.xref.Part1.29">7.1</a></li> 5052 <li><em>Section 4</em> <a href="#rfc.xref.Part1. 39">11.4.1</a></li>5043 <li><em>Section 4</em> <a href="#rfc.xref.Part1.40">11.4.1</a></li> 5053 5044 <li><em>Section 4.1</em> <a href="#rfc.xref.Part1.16">4.5</a></li> 5054 <li><em>Section 4.2.1</em> <a href="#rfc.xref.Part1.26">6.4</a>, <a href="#rfc.xref.Part1.4 1">11.4.2</a></li>5055 <li><em>Section 4.2</em> <a href="#rfc.xref.Part1. 40">11.4.1</a></li>5056 <li><em>Section 4.2.2</em> <a href="#rfc.xref.Part1.27">6.4</a>, <a href="#rfc.xref.Part1.4 2">11.4.2</a></li>5057 <li><em>Section 4.2.3</em> <a href="#rfc.xref.Part1.28">6.4</a>, <a href="#rfc.xref.Part1.4 3">11.4.2</a></li>5045 <li><em>Section 4.2.1</em> <a href="#rfc.xref.Part1.26">6.4</a>, <a href="#rfc.xref.Part1.42">11.4.2</a></li> 5046 <li><em>Section 4.2</em> <a href="#rfc.xref.Part1.39">11.4</a>, <a href="#rfc.xref.Part1.41">11.4.1</a></li> 5047 <li><em>Section 4.2.2</em> <a href="#rfc.xref.Part1.27">6.4</a>, <a href="#rfc.xref.Part1.43">11.4.2</a></li> 5048 <li><em>Section 4.2.3</em> <a href="#rfc.xref.Part1.28">6.4</a>, <a href="#rfc.xref.Part1.44">11.4.2</a></li> 5058 5049 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.18">4.6</a></li> 5059 5050 <li><em>Section 5.3</em> <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.7">3.3.1</a>, <a href="#rfc.xref.Part1.10">3.3.8</a></li> 5060 5051 <li><em>Section 5.4</em> <a href="#rfc.xref.Part1.17">4.6</a></li> 5061 5052 <li><em>Section 5.5</em> <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.19">4.7</a>, <a href="#rfc.xref.Part1.32">8.1</a>, <a href="#rfc.xref.Part1.33">10.8</a></li> 5062 <li><em>Section 5.7</em> <a href="#rfc.xref.Part1.8">3.3.7</a>, <a href="#rfc.xref.Part1.36">10.17</a>, <a href="#rfc.xref.Part1.4 5">C</a></li>5053 <li><em>Section 5.7</em> <a href="#rfc.xref.Part1.8">3.3.7</a>, <a href="#rfc.xref.Part1.36">10.17</a>, <a href="#rfc.xref.Part1.46">C</a></li> 5063 5054 <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.15">4.5</a></li> 5064 5055 <li><em>Section 6.3</em> <a href="#rfc.xref.Part1.20">5.2.1</a>, <a href="#rfc.xref.Part1.34">10.11</a></li> 5065 5056 <li><em>Section 6.4</em> <a href="#rfc.xref.Part1.21">5.2.2</a>, <a href="#rfc.xref.Part1.24">5.5.15</a></li> 5066 5057 <li><em>Section 7.3.1</em> <a href="#rfc.xref.Part1.9">3.3.7</a></li> 5067 <li><em>Section 9</em> <a href="#rfc.xref.Part1.4 4">13</a></li>5058 <li><em>Section 9</em> <a href="#rfc.xref.Part1.45">13</a></li> 5068 5059 <li><em>Appendix B</em> <a href="#rfc.xref.Part1.12">4.5</a></li> 5069 5060 </ul> … … 5163 5154 </ul> 5164 5155 </li> 5165 <li><em>RFC2817</em> <a href="#rfc.xref.RFC2817.1">11.2 .3</a>, <a href="#RFC2817"><b>14.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>5166 <li><em>Section 7.1</em> <a href="#rfc.xref.RFC2817.1">11.2 .3</a>, <a href="#rfc.xref.RFC2817.3">C</a></li>5156 <li><em>RFC2817</em> <a href="#rfc.xref.RFC2817.1">11.2</a>, <a href="#RFC2817"><b>14.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> 5157 <li><em>Section 7.1</em> <a href="#rfc.xref.RFC2817.1">11.2</a>, <a href="#rfc.xref.RFC2817.3">C</a></li> 5167 5158 </ul> 5168 5159 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1843 r1844 3944 3944 <section title="Method Registry" anchor="method.registry"> 3945 3945 <t> 3946 The HTTP Method Registry defines the name space for the method token in the 3947 Request line of an HTTP request. 3948 </t> 3946 The HTTP Method Registry defines the name space for the request method 3947 token (<xref target="methods"/>). 3948 The method registry is maintained at 3949 <eref target="http://www.iana.org/assignments/http-methods"/>. 3950 </t> 3951 3949 3952 <section title="Procedure" anchor="method.procedure"> 3950 3953 <t> 3951 Registrations &MUST; include the following fields:3954 HTTP method registrations &MUST; include the following fields: 3952 3955 <list style="symbols"> 3953 3956 <t>Method Name (see <xref target="methods"/>)</t> … … 3960 3963 Values to be added to this name space require IETF Review 3961 3964 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 3962 </t>3963 <t>3964 The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-methods"/>.3965 3965 </t> 3966 3966 </section> … … 3986 3986 New method definitions need to indicate whether they are safe (<xref 3987 3987 target="safe.methods"/>), idempotent (<xref target="idempotent.methods"/>), 3988 orcacheable (<xref target="cacheable.methods"/>), and what3988 cacheable (<xref target="cacheable.methods"/>), and what 3989 3989 semantics are to be associated with the request body if any is present 3990 3990 in the request. If a method is cacheable, the method definition ought … … 3996 3996 <section title="Registrations" anchor="method.registration"> 3997 3997 <t> 3998 The HTTP Method Registry shall be created at <eref target="http://www.iana.org/assignments/http-methods"/> 3999 and be populated with the registrations below: 3998 The HTTP Method Registry shall be populated with the registrations below: 4000 3999 </t> 4001 4000 <?BEGININC p2-semantics.iana-methods ?> … … 4062 4061 <section title="Status Code Registry" anchor="status.code.registry"> 4063 4062 <t> 4064 The HTTP Status Code Registry defines the name space for the status-code 4065 token in the status-line of an HTTP response (<xref target="status.codes"/>). 4063 The HTTP Status Code Registry defines the name space for the response 4064 status-code token (<xref target="status.codes"/>). 4065 The status code registry is maintained at 4066 <eref target="http://www.iana.org/assignments/http-status-codes"/>. 4067 </t> 4068 <t> 4069 This section replaces the registration procedure for HTTP Status Codes 4070 previously defined in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/>. 4066 4071 </t> 4067 4072 4068 4073 <section title="Procedure" anchor="status.code.procedure"> 4069 4074 <t> 4070 Values to be added to this name space require IETF Review 4071 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 4072 </t> 4073 <t> 4074 The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>. 4075 Values to be added to the HTTP status code name space require IETF Review 4076 (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 4075 4077 </t> 4076 4078 </section> … … 4115 4117 <section title="Registrations" anchor="status.code.registration"> 4116 4118 <t> 4117 The registration procedure for HTTP Status Codes — previously defined 4118 in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/> — is now defined 4119 by <xref target="status.code.registry"/> of this document. 4120 </t> 4121 <t> 4122 The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/> 4123 shall be updated with the registrations below: 4119 The HTTP Status Code Registry shall be updated with the registrations below: 4124 4120 </t> 4125 4121 <?BEGININC p2-semantics.iana-status-codes ?> … … 4317 4313 <section title="Header Field Registration" anchor="header.field.registration"> 4318 4314 <t> 4319 The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated 4320 with the permanent registrations below (see <xref target="RFC3864"/>): 4315 HTTP header fields are registered within the Message Header Field Registry 4316 located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> 4317 (see <xref target="RFC3864"/>). The Message Header Field Registry 4318 shall be updated with the permanent registrations below: 4321 4319 </t> 4322 4320 <?BEGININC p2-semantics.iana-headers ?> … … 4446 4444 <?ENDINC p2-semantics.iana-headers ?> 4447 4445 <t> 4448 The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force". 4446 The change controller for the above registrations is: 4447 "IETF (iesg@ietf.org) - Internet Engineering Task Force". 4449 4448 </t> 4450 4449 </section> … … 4452 4451 <section title="Content Coding Registry" anchor="content.coding.registry"> 4453 4452 <t> 4454 The HTTP Content Coding Registry defines the name space for the content 4455 coding names. 4453 The HTTP Content Coding Registry defines the name space for content 4454 coding names (&compression-codings;). 4455 The content coding registry is maintained at 4456 <eref target="http://www.iana.org/assignments/http-parameters"/>. 4456 4457 </t> 4457 4458 4458 4459 <section title="Procedure" anchor="content.coding.procedure"> 4459 4460 <t> 4460 Registrations &MUST; include the following fields:4461 Content Coding registrations &MUST; include the following fields: 4461 4462 <list style="symbols"> 4462 4463 <t>Name</t> … … 4476 4477 conform to the purpose of content coding defined in this section. 4477 4478 </t> 4478 <t>4479 The registry itself is maintained at4480 <eref target="http://www.iana.org/assignments/http-parameters"/>.4481 </t>4482 4479 </section> 4483 4480 4484 4481 <section title="Registrations" anchor="content.coding.registration"> 4485 4482 <t> 4486 The registration procedure for HTTP Content Codings is now defined 4487 by <xref target="content.coding.registry"/> of this document. 4488 </t> 4489 <t> 4490 The HTTP Content Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/> 4491 shall be updated with the registration below: 4483 The HTTP Content Codings Registry shall be updated with the registrations 4484 below: 4492 4485 </t> 4493 4486 <texttable align="left" suppress-title="true" anchor="iana.content.coding.registration.table">
Note: See TracChangeset
for help on using the changeset viewer.