Ignore:
Timestamp:
Jul 4, 2012, 2:24:20 AM (7 years ago)
Author:
julian.reschke@…
Message:

Fix missing ABNF import after p2/p3 merge (see #351)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1710 r1712  
    884884  <a href="#abnf.dependencies" class="smpl">comment</a>       = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    885885  <a href="#abnf.dependencies" class="smpl">partial-URI</a>   = &lt;partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    886   <a href="#abnf.dependencies" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
     886  <a href="#abnf.dependencies" class="smpl">qvalue</a>        = &lt;qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a>&gt;
     887  <a href="#abnf.dependencies" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    887888</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="methods" href="#methods">Methods</a></h1>
    888       <p id="rfc.section.2.p.1">The method token indicates the request method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The method is case-sensitive.
     889      <p id="rfc.section.2.p.1">The method token indicates the request method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The method is case-sensitive.
    889890      </p>
    890891      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#methods" class="smpl">method</a>         = <a href="#core.rules" class="smpl">token</a>
     
    936937         to a single application, so that this is clear.
    937938      </p>
    938       <p id="rfc.section.2.2.1.p.3">Due to the parsing rules defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, definitions of HTTP methods cannot prohibit the presence of a message body on either the request or the response message
     939      <p id="rfc.section.2.2.1.p.3">Due to the parsing rules defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, definitions of HTTP methods cannot prohibit the presence of a message body on either the request or the response message
    939940         (with responses to HEAD requests being the single exception). Definitions of new methods cannot change this rule, but they
    940941         can specify that only zero-length bodies (as opposed to absent bodies) are allowed.
     
    956957         to HTTP might use the OPTIONS body to make more detailed queries on the server.
    957958      </p>
    958       <p id="rfc.section.2.3.1.p.4">If the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to a specific resource.
     959      <p id="rfc.section.2.3.1.p.4">If the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to a specific resource.
    959960         Since a server's communication options typically depend on the resource, the "*" request is only useful as a "ping" or "no-op"
    960961         type of method; it does nothing beyond allowing the client to test the capabilities of the server. For example, this can be
     
    11191120      </p>
    11201121      <p id="rfc.section.2.3.7.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing
    1121          or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the
     1122         or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the
    11221123         client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an
    11231124         infinite loop.
    11241125      </p>
    1125       <p id="rfc.section.2.3.7.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 7.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and contain a message body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
     1126      <p id="rfc.section.2.3.7.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 7.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and contain a message body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
    11261127      </p>
    11271128      <div id="rfc.iref.c.2"></div>
     
    11311132         its behavior to blind forwarding of packets until the connection is closed.
    11321133      </p>
    1133       <p id="rfc.section.2.3.8.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
     1134      <p id="rfc.section.2.3.8.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
    11341135         For example,
    11351136      </p>
     
    11671168      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Fields</a></h1>
    11681169      <p id="rfc.section.3.p.1">Header fields are key value pairs that can be used to communicate data about the message, its payload, the target resource,
    1169          or about the connection itself (i.e., control data). See <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for a general definition of their syntax.
     1170         or about the connection itself (i.e., control data). See <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for a general definition of their syntax.
    11701171      </p>
    11711172      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="considerations.for.creating.header.fields" href="#considerations.for.creating.header.fields">Considerations for Creating Header Fields</a></h2>
     
    11751176         with "X-" if they are to be registered (either immediately or in the future).
    11761177      </p>
    1177       <p id="rfc.section.3.1.p.3">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 3.2.5</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
     1178      <p id="rfc.section.3.1.p.3">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Section 3.2.5</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
    11781179         can use an encoding such as the one defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>.
    11791180      </p>
    11801181      <p id="rfc.section.3.1.p.4">Because commas (",") are used as a generic delimiter between field-values, they need to be treated with care if they are allowed
    11811182         in the field-value's payload. Typically, components that might contain a comma are protected with double-quotes using the
    1182          quoted-string ABNF production (<a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     1183         quoted-string ABNF production (<a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    11831184      </p>
    11841185      <p id="rfc.section.3.1.p.5">For example, a textual date and a URI (either of which might contain a comma) could be safely carried in field-values like
     
    11981199      <ul>
    11991200         <li>
    1200             <p>Whether the field is a single value, or whether it can be a list (delimited by commas; see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     1201            <p>Whether the field is a single value, or whether it can be a list (delimited by commas; see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    12011202            </p>
    12021203            <p>If it does not use the list syntax, document how to treat messages where the header field occurs multiple times (a sensible
     
    12141215         </li>
    12151216         <li>
    1216             <p>Whether it is appropriate to list the field-name in the Connection header (i.e., if the header is to be hop-by-hop, see <a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     1217            <p>Whether it is appropriate to list the field-name in the Connection header (i.e., if the header is to be hop-by-hop, see <a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    12171218            </p>
    12181219         </li>
     
    12251226         </li>
    12261227         <li>
    1227             <p>Whether the header field is useful or allowable in trailers (see <a href="p1-messaging.html#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     1228            <p>Whether the header field is useful or allowable in trailers (see <a href="p1-messaging.html#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    12281229            </p>
    12291230         </li>
     
    12761277               <tr>
    12771278                  <td class="left">Host</td>
    1278                   <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 5.4</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
     1279                  <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 5.4</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
    12791280               </tr>
    12801281               <tr>
     
    13161317               <tr>
    13171318                  <td class="left">TE</td>
    1318                   <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
     1319                  <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
    13191320               </tr>
    13201321               <tr>
     
    13271328      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h2>
    13281329      <p id="rfc.section.3.3.p.1">The response header fields allow the server to pass additional information about the response which cannot be placed in the
    1329          status-line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     1330         status-line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    13301331      </p>
    13311332      <div id="rfc.table.u.2">
     
    16691670      <p id="rfc.section.4.3.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been
    16701671         received and has not yet been rejected by the server. The client <em class="bcp14">SHOULD</em> continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The
    1671          server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
     1672         server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
    16721673      </p>
    16731674      <div id="rfc.iref.22"></div>
    16741675      <div id="rfc.iref.s.4"></div>
    16751676      <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    1676       <p id="rfc.section.4.3.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     1677      <p id="rfc.section.4.3.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
    16771678         by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    16781679      </p>
     
    17271728      <div id="rfc.iref.s.8"></div>
    17281729      <h3 id="rfc.section.4.4.4"><a href="#rfc.section.4.4.4">4.4.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    1729       <p id="rfc.section.4.4.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1730      <p id="rfc.section.4.4.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    17301731      </p>
    17311732      <p id="rfc.section.4.4.4.p.2">This status code is only appropriate when the response status code would have been 200 (OK) otherwise. When the status code
     
    17621763         another input action.
    17631764      </p>
    1764       <p id="rfc.section.4.4.6.p.2">The message body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     1765      <p id="rfc.section.4.4.6.p.2">The message body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    17651766      </p>
    17661767      <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
     
    20232024      <div id="rfc.iref.s.32"></div>
    20242025      <h3 id="rfc.section.4.6.15"><a href="#rfc.section.4.6.15">4.6.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
    2025       <p id="rfc.section.4.6.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an Upgrade header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) specifying the required protocols.
     2026      <p id="rfc.section.4.6.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an Upgrade header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) specifying the required protocols.
    20262027      </p>
    20272028      <div id="rfc.figure.u.7"></div>
     
    20842085      <p id="rfc.section.4.7.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
    20852086         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    2086          in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server.
     2087         in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.6</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server.
    20872088      </p>
    20882089      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
     
    22152216      </p>
    22162217      <ul class="empty">
    2217          <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     2218         <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    22182219         </li>
    22192220      </ul>
     
    22212222      </p>
    22222223      <ul class="empty">
    2223          <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     2224         <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    22242225         </li>
    22252226      </ul>
     
    22272228      </p>
    22282229      <ul class="empty">
    2229          <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     2230         <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    22302231         </li>
    22312232      </ul>
     
    22392240         <li>Pointer to specification text</li>
    22402241      </ul>
    2241       <p id="rfc.section.5.4.1.p.3">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: URIs, Connections, and Message Parsing">[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: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     2242      <p id="rfc.section.5.4.1.p.3">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.41"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[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.42"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    22422243      </p>
    22432244      <p id="rfc.section.5.4.1.p.4">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.
     
    23392340               <tr>
    23402341                  <td class="left">Content-Length</td>
    2341                   <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
     2342                  <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
    23422343               </tr>
    23432344               <tr>
     
    23492350      </div>
    23502351      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
    2351       <p id="rfc.section.6.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any Transfer-Encoding that might have been applied to ensure
     2352      <p id="rfc.section.6.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any Transfer-Encoding that might have been applied to ensure
    23522353         safe and proper transfer of the message.
    23532354      </p>
     
    23712372         in an HTTP message, it is referred to as the payload of the message.
    23722373      </p>
    2373       <p id="rfc.section.7.p.4">A representation body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The representation body is obtained from the message body by decoding any Transfer-Encoding that might have been applied
     2374      <p id="rfc.section.7.p.4">A representation body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.45"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The representation body is obtained from the message body by decoding any Transfer-Encoding that might have been applied
    23742375         to ensure safe and proper transfer of the message.
    23752376      </p>
     
    23772378      <p id="rfc.section.7.1.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p>
    23782379      <p id="rfc.section.7.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p>
    2379       <p id="rfc.section.7.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.45"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
     2380      <p id="rfc.section.7.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.46"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
    23802381         rules are used (with the first applicable one being selected):
    23812382      </p>
     
    25372538         that doesn't conform to them is better than sending a 406 (Not Acceptable) response.
    25382539      </p>
    2539       <p id="rfc.section.8.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.46"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information.
     2540      <p id="rfc.section.8.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.47"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for more information.
    25402541      </p>
    25412542      <p id="rfc.section.8.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities
     
    25922593      <p id="rfc.section.9.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first
    25932594         "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user
    2594          agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.47"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.
     2595         agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.48"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The default value is q=1.
    25952596      </p>
    25962597      <div class="note" id="rfc.section.9.1.p.5">
     
    27222723         </li>
    27232724         <li>If the representation's content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable
    2724             unless it is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.48"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)
     2725            unless it is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.49"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)
    27252726         </li>
    27262727         <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
     
    28492850      </p>
    28502851      <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.43"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    2851 </pre><p id="rfc.section.9.8.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.49"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
     2852</pre><p id="rfc.section.9.8.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.50"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
    28522853         body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
    28532854      </p>
     
    29432944      </p>
    29442945      <ul class="empty">
    2945          <li>The "100-continue" expectation is defined <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.50"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. It does not support any expect-params.
     2946         <li>The "100-continue" expectation is defined <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.51"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. It does not support any expect-params.
    29462947         </li>
    29472948      </ul>
     
    30553056      <h2 id="rfc.section.9.17"><a href="#rfc.section.9.17">9.17</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
    30563057      <p id="rfc.section.9.17.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
    3057       <p id="rfc.section.9.17.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;5.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.51"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
     3058      <p id="rfc.section.9.17.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;5.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.52"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
    30583059         identifying the application.
    30593060      </p>
     
    30613062</pre><p id="rfc.section.9.17.p.4">Example:</p>
    30623063      <div id="rfc.figure.u.60"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    3063 </pre><p id="rfc.section.9.17.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server header field. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.52"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
     3064</pre><p id="rfc.section.9.17.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server header field. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.53"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    30643065      </p>
    30653066      <div class="note" id="rfc.section.9.17.p.7">
     
    30773078         user agent limitations.
    30783079      </p>
    3079       <p id="rfc.section.9.18.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;5.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.53"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
     3080      <p id="rfc.section.9.18.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;5.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.54"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
    30803081         for identifying the application.
    30813082      </p>
     
    35653566                  <td class="left">compress</td>
    35663567                  <td class="left">UNIX "compress" program method</td>
    3567                   <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.54"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     3568                  <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.55"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    35683569                  </td>
    35693570               </tr>
     
    35723573                  <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>)
    35733574                  </td>
    3574                   <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.55"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     3575                  <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.56"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    35753576                  </td>
    35763577               </tr>
     
    35783579                  <td class="left">gzip</td>
    35793580                  <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>
    3580                   <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.56"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
     3581                  <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.57"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>
    35813582                  </td>
    35823583               </tr>
     
    36733674      </p>
    36743675      <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    3675       <p id="rfc.section.12.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.57"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     3676      <p id="rfc.section.12.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.58"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    36763677      </p>
    36773678      <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References
     
    39303931      </p>
    39313932      <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2>
    3932       <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.58"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.
     3933      <p id="rfc.section.A.6.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.59"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.
    39333934      </p>
    39343935      <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a>&nbsp;<a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2>
     
    39853986      </p>
    39863987      <p id="rfc.section.C.p.16">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated
    3987          correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.59"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;9.17</a>)
     3988         correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.60"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;9.17</a>)
    39883989      </p>
    39893990      <p id="rfc.section.C.p.17">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;5.3</a>)
     
    40444045
    40454046<a href="#mime-version" class="smpl">MIME-Version</a> = 1*DIGIT "." 1*DIGIT
    4046 
    40474047<a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*DIGIT
    40484048
     
    40504050
    40514051<a href="#core.rules" class="smpl">RWS</a> = &lt;RWS, defined in [Part1], Section 3.2.1&gt;
    4052 
    40534052<a href="#header.referer" class="smpl">Referer</a> = absolute-URI / partial-URI
    40544053<a href="#header.retry-after" class="smpl">Retry-After</a> = HTTP-date / delta-seconds
     
    40574056
    40584057<a href="#abnf.dependencies" class="smpl">URI-reference</a> = &lt;URI-reference, defined in [Part1], Section 2.7&gt;
    4059 
    40604058<a href="#header.user-agent" class="smpl">User-Agent</a> = product *( RWS ( product / comment ) )
    40614059
    40624060<a href="#abnf.dependencies" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;
    4063 
    40644061<a href="#header.accept" class="smpl">accept-ext</a> = OWS ";" OWS token [ "=" word ]
    40654062<a href="#header.accept" class="smpl">accept-params</a> = OWS ";" OWS "q=" qvalue *accept-ext
     
    40684065
    40694066<a href="#rule.charset" class="smpl">charset</a> = token
    4070 
    40714067<a href="#header.accept-encoding" class="smpl">codings</a> = content-coding / "identity" / "*"
    40724068<a href="#abnf.dependencies" class="smpl">comment</a> = &lt;comment, defined in [Part1], Section 3.2.4&gt;
     
    40744070
    40754071<a href="#obsolete.date.formats" class="smpl">date1</a> = day SP month SP year
    4076 
    40774072<a href="#obsolete.date.formats" class="smpl">date2</a> = day "-" month "-" 2DIGIT
    40784073<a href="#obsolete.date.formats" class="smpl">date3</a> = month SP ( 2DIGIT / ( SP DIGIT ) )
     
    40954090
    40964091<a href="#header.expect" class="smpl">expect-name</a> = token
    4097 
    40984092<a href="#header.expect" class="smpl">expect-param</a> = expect-name [ BWS "=" BWS expect-value ]
    40994093<a href="#header.expect" class="smpl">expect-value</a> = token / quoted-string
     
    41044098
    41054099<a href="#header.accept-language" class="smpl">language-range</a> = &lt;language-range, defined in [RFC4647], Section 2.1&gt;
    4106 
    41074100<a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in [RFC5646], Section 2.1&gt;
    41084101
    41094102<a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in [RFC5322], Section 3.4&gt;
    4110 
    41114103<a href="#header.accept" class="smpl">media-range</a> = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
    41124104 ";" OWS parameter )
     
    41284120
    41294121<a href="#obsolete.date.formats" class="smpl">obs-date</a> = rfc850-date / asctime-date
    4130 
    41314122<a href="#core.rules" class="smpl">obs-text</a> = &lt;obs-text, defined in [Part1], Section 3.2.4&gt;
    41324123
    41334124<a href="#rule.parameter" class="smpl">parameter</a> = attribute "=" value
    4134 
    41354125<a href="#abnf.dependencies" class="smpl">partial-URI</a> = &lt;partial-URI, defined in [Part1], Section 2.7&gt;
    41364126<a href="#product.tokens" class="smpl">product</a> = token [ "/" product-version ]
     
    41384128
    41394129<a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
     4130<a href="#abnf.dependencies" class="smpl">qvalue</a> = &lt;qvalue, defined in [Part1], Section 4.3.1&gt;
    41404131
    41414132<a href="#preferred.date.format" class="smpl">rfc1123-date</a> = day-name "," SP date1 SP time-of-day SP GMT
    4142 
    41434133<a href="#obsolete.date.formats" class="smpl">rfc850-date</a> = day-name-l "," SP date2 SP time-of-day SP GMT
    41444134
    41454135<a href="#preferred.date.format" class="smpl">second</a> = 2DIGIT
    4146 
    41474136<a href="#media.types" class="smpl">subtype</a> = token
    41484137
    41494138<a href="#preferred.date.format" class="smpl">time-of-day</a> = hour ":" minute ":" second
    4150 
    41514139<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
    41524140<a href="#media.types" class="smpl">type</a> = token
     
    41584146<a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT
    41594147</pre> <div id="rfc.figure.u.65"></div>
    4160       <p>ABNF diagnostics:</p><pre class="inline">; qvalue UNDEFINED
    4161 ; Accept defined but not used
     4148      <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used
    41624149; Accept-Charset defined but not used
    41634150; Accept-Encoding defined but not used
     
    47324719         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/312">http://tools.ietf.org/wg/httpbis/trac/ticket/312</a>&gt;: "should there be a permanent variant of 307"
    47334720         </li>
     4721         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/347">http://tools.ietf.org/wg/httpbis/trac/ticket/347</a>&gt;: "clarify that 201 can imply *multiple* resources were created"
     4722         </li>
     4723         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/351">http://tools.ietf.org/wg/httpbis/trac/ticket/351</a>&gt;: "merge P2 and P3"
     4724         </li>
    47344725         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
    4735          </li>
    4736          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/347">http://tools.ietf.org/wg/httpbis/trac/ticket/347</a>&gt;: "clarify that 201 can imply *multiple* resources were created"
    47374726         </li>
    47384727      </ul>
     
    49644953            </li>
    49654954            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    4966                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.3</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a>, <a href="#rfc.xref.Part1.7">1.3.1</a>, <a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.1</a>, <a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.15">1.3.2</a>, <a href="#rfc.xref.Part1.16">2</a>, <a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.8</a>, <a href="#rfc.xref.Part1.22">3</a>, <a href="#rfc.xref.Part1.23">3.1</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.1</a>, <a href="#rfc.xref.Part1.28">3.2</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.3</a>, <a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.33">4.4.4</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.35">4.6.15</a>, <a href="#rfc.xref.Part1.36">4.7.6</a>, <a href="#rfc.xref.Part1.37">5.4</a>, <a href="#rfc.xref.Part1.38">5.4</a>, <a href="#rfc.xref.Part1.39">5.4</a>, <a href="#rfc.xref.Part1.40">5.4.1</a>, <a href="#rfc.xref.Part1.41">5.4.1</a>, <a href="#rfc.xref.Part1.42">6.1</a>, <a href="#rfc.xref.Part1.43">6.2</a>, <a href="#rfc.xref.Part1.44">7</a>, <a href="#rfc.xref.Part1.45">7.1</a>, <a href="#rfc.xref.Part1.46">8.1</a>, <a href="#rfc.xref.Part1.47">9.1</a>, <a href="#rfc.xref.Part1.48">9.3</a>, <a href="#rfc.xref.Part1.49">9.8</a>, <a href="#rfc.xref.Part1.50">9.11</a>, <a href="#rfc.xref.Part1.51">9.17</a>, <a href="#rfc.xref.Part1.52">9.17</a>, <a href="#rfc.xref.Part1.53">9.18</a>, <a href="#rfc.xref.Part1.54">10.4</a>, <a href="#rfc.xref.Part1.55">10.4</a>, <a href="#rfc.xref.Part1.56">10.4</a>, <a href="#rfc.xref.Part1.57">12</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.58">A.6</a>, <a href="#rfc.xref.Part1.59">C</a><ul>
     4955                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.3</a>, <a href="#rfc.xref.Part1.4">1.3.1</a>, <a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a>, <a href="#rfc.xref.Part1.7">1.3.1</a>, <a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.1</a>, <a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.15">1.3.2</a>, <a href="#rfc.xref.Part1.16">1.3.2</a>, <a href="#rfc.xref.Part1.17">2</a>, <a href="#rfc.xref.Part1.18">2.2.1</a>, <a href="#rfc.xref.Part1.19">2.3.1</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.7</a>, <a href="#rfc.xref.Part1.22">2.3.8</a>, <a href="#rfc.xref.Part1.23">3</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.1</a>, <a href="#rfc.xref.Part1.28">3.1</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.2</a>, <a href="#rfc.xref.Part1.31">3.3</a>, <a href="#rfc.xref.Part1.32">4.3.1</a>, <a href="#rfc.xref.Part1.33">4.3.2</a>, <a href="#rfc.xref.Part1.34">4.4.4</a>, <a href="#rfc.xref.Part1.35">4.4.6</a>, <a href="#rfc.xref.Part1.36">4.6.15</a>, <a href="#rfc.xref.Part1.37">4.7.6</a>, <a href="#rfc.xref.Part1.38">5.4</a>, <a href="#rfc.xref.Part1.39">5.4</a>, <a href="#rfc.xref.Part1.40">5.4</a>, <a href="#rfc.xref.Part1.41">5.4.1</a>, <a href="#rfc.xref.Part1.42">5.4.1</a>, <a href="#rfc.xref.Part1.43">6.1</a>, <a href="#rfc.xref.Part1.44">6.2</a>, <a href="#rfc.xref.Part1.45">7</a>, <a href="#rfc.xref.Part1.46">7.1</a>, <a href="#rfc.xref.Part1.47">8.1</a>, <a href="#rfc.xref.Part1.48">9.1</a>, <a href="#rfc.xref.Part1.49">9.3</a>, <a href="#rfc.xref.Part1.50">9.8</a>, <a href="#rfc.xref.Part1.51">9.11</a>, <a href="#rfc.xref.Part1.52">9.17</a>, <a href="#rfc.xref.Part1.53">9.17</a>, <a href="#rfc.xref.Part1.54">9.18</a>, <a href="#rfc.xref.Part1.55">10.4</a>, <a href="#rfc.xref.Part1.56">10.4</a>, <a href="#rfc.xref.Part1.57">10.4</a>, <a href="#rfc.xref.Part1.58">12</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.59">A.6</a>, <a href="#rfc.xref.Part1.60">C</a><ul>
    49674956                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.3</a></li>
    49684957                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
    4969                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.33">4.4.4</a></li>
    4970                         <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.36">4.7.6</a></li>
    4971                         <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.15">1.3.2</a></li>
     4958                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.34">4.4.4</a></li>
     4959                        <li><em>Section 2.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.37">4.7.6</a></li>
     4960                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">1.3.2</a>, <a href="#rfc.xref.Part1.14">1.3.2</a>, <a href="#rfc.xref.Part1.16">1.3.2</a></li>
    49724961                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.3.1</a>, <a href="#rfc.xref.Part1.6">1.3.1</a>, <a href="#rfc.xref.Part1.7">1.3.1</a></li>
    4973                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">3</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.51">9.17</a>, <a href="#rfc.xref.Part1.53">9.18</a></li>
    4974                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.1</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.24">3.1</a></li>
    4975                         <li><em>Section 3.2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">3.1</a></li>
    4976                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.43">6.2</a>, <a href="#rfc.xref.Part1.44">7</a></li>
    4977                         <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.58">A.6</a></li>
    4978                         <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">6.1</a></li>
    4979                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.40">5.4.1</a></li>
    4980                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.27">3.1</a></li>
    4981                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.37">5.4</a>, <a href="#rfc.xref.Part1.54">10.4</a></li>
    4982                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.41">5.4.1</a></li>
    4983                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.38">5.4</a>, <a href="#rfc.xref.Part1.55">10.4</a></li>
    4984                         <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.39">5.4</a>, <a href="#rfc.xref.Part1.56">10.4</a></li>
    4985                         <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">3.2</a></li>
    4986                         <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.46">8.1</a>, <a href="#rfc.xref.Part1.47">9.1</a>, <a href="#rfc.xref.Part1.48">9.3</a></li>
    4987                         <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.21">2.3.8</a></li>
    4988                         <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.28">3.2</a></li>
    4989                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">2</a>, <a href="#rfc.xref.Part1.30">3.3</a>, <a href="#rfc.xref.Part1.45">7.1</a>, <a href="#rfc.xref.Part1.49">9.8</a></li>
    4990                         <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">3.1</a></li>
    4991                         <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.52">9.17</a>, <a href="#rfc.xref.Part1.59">C</a></li>
    4992                         <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.50">9.11</a></li>
    4993                         <li><em>Section 6.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.35">4.6.15</a></li>
    4994                         <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">2.3.7</a></li>
    4995                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.57">12</a></li>
     4962                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">3</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.52">9.17</a>, <a href="#rfc.xref.Part1.54">9.18</a></li>
     4963                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.3.1</a>, <a href="#rfc.xref.Part1.9">1.3.1</a>, <a href="#rfc.xref.Part1.10">1.3.1</a>, <a href="#rfc.xref.Part1.11">1.3.1</a>, <a href="#rfc.xref.Part1.13">1.3.2</a>, <a href="#rfc.xref.Part1.25">3.1</a></li>
     4964                        <li><em>Section 3.2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.24">3.1</a></li>
     4965                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">2.2.1</a>, <a href="#rfc.xref.Part1.35">4.4.6</a>, <a href="#rfc.xref.Part1.44">6.2</a>, <a href="#rfc.xref.Part1.45">7</a></li>
     4966                        <li><em>Section 3.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.59">A.6</a></li>
     4967                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.43">6.1</a></li>
     4968                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.41">5.4.1</a></li>
     4969                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.28">3.1</a></li>
     4970                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.38">5.4</a>, <a href="#rfc.xref.Part1.55">10.4</a></li>
     4971                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">5.4.1</a></li>
     4972                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.39">5.4</a>, <a href="#rfc.xref.Part1.56">10.4</a></li>
     4973                        <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.40">5.4</a>, <a href="#rfc.xref.Part1.57">10.4</a></li>
     4974                        <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">1.3.2</a>, <a href="#rfc.xref.Part1.47">8.1</a>, <a href="#rfc.xref.Part1.48">9.1</a>, <a href="#rfc.xref.Part1.49">9.3</a></li>
     4975                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.30">3.2</a></li>
     4976                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">2.3.1</a>, <a href="#rfc.xref.Part1.22">2.3.8</a></li>
     4977                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">3.2</a></li>
     4978                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">2</a>, <a href="#rfc.xref.Part1.31">3.3</a>, <a href="#rfc.xref.Part1.46">7.1</a>, <a href="#rfc.xref.Part1.50">9.8</a></li>
     4979                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.27">3.1</a></li>
     4980                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.53">9.17</a>, <a href="#rfc.xref.Part1.60">C</a></li>
     4981                        <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">4.3.1</a>, <a href="#rfc.xref.Part1.51">9.11</a></li>
     4982                        <li><em>Section 6.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.33">4.3.2</a>, <a href="#rfc.xref.Part1.36">4.6.15</a></li>
     4983                        <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">2.3.7</a></li>
     4984                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.58">12</a></li>
    49964985                     </ul>
    49974986                  </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1710 r1712  
    370370  <x:ref>comment</x:ref>       = &lt;comment, defined in &field-components;&gt;
    371371  <x:ref>partial-URI</x:ref>   = &lt;partial-URI, defined in &uri;&gt;
     372  <x:ref>qvalue</x:ref>        = &lt;qvalue, defined in &qvalue;&gt;
    372373  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in &uri;&gt;
    373374</artwork></figure>
     
    55435544
    55445545<x:ref>MIME-Version</x:ref> = 1*DIGIT "." 1*DIGIT
    5545 
    55465546<x:ref>Max-Forwards</x:ref> = 1*DIGIT
    55475547
     
    55495549
    55505550<x:ref>RWS</x:ref> = &lt;RWS, defined in [Part1], Section 3.2.1&gt;
    5551 
    55525551<x:ref>Referer</x:ref> = absolute-URI / partial-URI
    55535552<x:ref>Retry-After</x:ref> = HTTP-date / delta-seconds
     
    55565555
    55575556<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [Part1], Section 2.7&gt;
    5558 
    55595557<x:ref>User-Agent</x:ref> = product *( RWS ( product / comment ) )
    55605558
    55615559<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;
    5562 
    55635560<x:ref>accept-ext</x:ref> = OWS ";" OWS token [ "=" word ]
    55645561<x:ref>accept-params</x:ref> = OWS ";" OWS "q=" qvalue *accept-ext
     
    55675564
    55685565<x:ref>charset</x:ref> = token
    5569 
    55705566<x:ref>codings</x:ref> = content-coding / "identity" / "*"
    55715567<x:ref>comment</x:ref> = &lt;comment, defined in [Part1], Section 3.2.4&gt;
     
    55735569
    55745570<x:ref>date1</x:ref> = day SP month SP year
    5575 
    55765571<x:ref>date2</x:ref> = day "-" month "-" 2DIGIT
    55775572<x:ref>date3</x:ref> = month SP ( 2DIGIT / ( SP DIGIT ) )
     
    55945589
    55955590<x:ref>expect-name</x:ref> = token
    5596 
    55975591<x:ref>expect-param</x:ref> = expect-name [ BWS "=" BWS expect-value ]
    55985592<x:ref>expect-value</x:ref> = token / quoted-string
     
    56035597
    56045598<x:ref>language-range</x:ref> = &lt;language-range, defined in [RFC4647], Section 2.1&gt;
    5605 
    56065599<x:ref>language-tag</x:ref> = &lt;Language-Tag, defined in [RFC5646], Section 2.1&gt;
    56075600
    56085601<x:ref>mailbox</x:ref> = &lt;mailbox, defined in [RFC5322], Section 3.4&gt;
    5609 
    56105602<x:ref>media-range</x:ref> = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
    56115603 ";" OWS parameter )
     
    56275619
    56285620<x:ref>obs-date</x:ref> = rfc850-date / asctime-date
    5629 
    56305621<x:ref>obs-text</x:ref> = &lt;obs-text, defined in [Part1], Section 3.2.4&gt;
    56315622
    56325623<x:ref>parameter</x:ref> = attribute "=" value
    5633 
    56345624<x:ref>partial-URI</x:ref> = &lt;partial-URI, defined in [Part1], Section 2.7&gt;
    56355625<x:ref>product</x:ref> = token [ "/" product-version ]
     
    56375627
    56385628<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
     5629<x:ref>qvalue</x:ref> = &lt;qvalue, defined in [Part1], Section 4.3.1&gt;
    56395630
    56405631<x:ref>rfc1123-date</x:ref> = day-name "," SP date1 SP time-of-day SP GMT
    5641 
    56425632<x:ref>rfc850-date</x:ref> = day-name-l "," SP date2 SP time-of-day SP GMT
    56435633
    56445634<x:ref>second</x:ref> = 2DIGIT
    5645 
    56465635<x:ref>subtype</x:ref> = token
    56475636
    56485637<x:ref>time-of-day</x:ref> = hour ":" minute ":" second
    5649 
    56505638<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 3.2.4&gt;
    56515639<x:ref>type</x:ref> = token
     
    56595647</figure>
    56605648<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
    5661 ; qvalue UNDEFINED
    56625649; Accept defined but not used
    56635650; Accept-Charset defined but not used
     
    67806767    </t>
    67816768    <t>
     6769      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/347"/>:
     6770      "clarify that 201 can imply *multiple* resources were created"
     6771    </t>
     6772    <t>
     6773      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/351"/>:
     6774      "merge P2 and P3"
     6775    </t>
     6776    <t>
    67826777      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
    67836778      "ABNF requirements for recipients"
    67846779    </t>
    6785     <t>
    6786       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/347"/>:
    6787       "clarify that 201 can imply *multiple* resources were created"
    6788     </t>
    67896780  </list>
    67906781</t>
Note: See TracChangeset for help on using the changeset viewer.