Changeset 1617 for draft-ietf-httpbis/latest/p2-semantics.html

Timestamp:

Mar 26, 2012, 6:49:01 AM (8 years ago)

Author:

julian.reschke@…

Message:

re-org sections

File:

• draft-ietf-httpbis/latest/p2-semantics.html (modified) (58 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -489 +489 @@
       <link rel="Chapter" title="6 Method Definitions" href="#rfc.section.6">
       <link rel="Chapter" title="7 Status Code Definitions" href="#rfc.section.7">
-      <link rel="Chapter" title="8 Date/Time Formats" href="#rfc.section.8">
-      <link rel="Chapter" title="9 Product Tokens" href="#rfc.section.9">
-      <link rel="Chapter" title="10 Header Field Definitions" href="#rfc.section.10">
-      <link rel="Chapter" title="11 IANA Considerations" href="#rfc.section.11">
-      <link rel="Chapter" title="12 Security Considerations" href="#rfc.section.12">
-      <link rel="Chapter" title="13 Acknowledgments" href="#rfc.section.13">
-      <link rel="Chapter" href="#rfc.section.14" title="14 References">
+      <link rel="Chapter" title="8 Common Protocol Parameters" href="#rfc.section.8">
+      <link rel="Chapter" title="9 Header Field Definitions" href="#rfc.section.9">
+      <link rel="Chapter" title="10 IANA Considerations" href="#rfc.section.10">
+      <link rel="Chapter" title="11 Security Considerations" href="#rfc.section.11">
+      <link rel="Chapter" title="12 Acknowledgments" href="#rfc.section.12">
+      <link rel="Chapter" href="#rfc.section.13" title="13 References">
       <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
       <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
@@ -696 +695 @@
             </ul>
          </li>
-         <li>8.&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
-         <li>9.&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
-         <li>10.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
-               <li>10.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
-               <li>10.2&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
-               <li>10.3&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
-               <li>10.4&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
-               <li>10.5&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
-               <li>10.6&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
-               <li>10.7&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
-               <li>10.8&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
-               <li>10.9&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
-               <li>10.10&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
+         <li>8.&nbsp;&nbsp;&nbsp;<a href="#common.protocol.parameters">Common Protocol Parameters</a><ul>
+               <li>8.1&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
+               <li>8.2&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
             </ul>
          </li>
-         <li>11.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
-               <li>11.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
-               <li>11.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
-               <li>11.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
+         <li>9.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
+               <li>9.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
+               <li>9.2&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
+               <li>9.3&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
+               <li>9.4&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
+               <li>9.5&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
+               <li>9.6&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
+               <li>9.7&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
+               <li>9.8&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
+               <li>9.9&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
+               <li>9.10&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
             </ul>
          </li>
-         <li>12.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
-               <li>12.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
-               <li>12.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
-               <li>12.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li>
-               <li>12.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.12.4">Security Considerations for CONNECT</a></li>
+         <li>10.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
+               <li>10.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
+               <li>10.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
+               <li>10.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
             </ul>
          </li>
-         <li>13.&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
-         <li>14.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
-               <li>14.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
-               <li>14.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
+         <li>11.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
+               <li>11.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
+               <li>11.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
+               <li>11.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></li>
+               <li>11.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.11.4">Security Considerations for CONNECT</a></li>
+            </ul>
+         </li>
+         <li>12.&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
+         <li>13.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
+               <li>13.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
+               <li>13.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
             </ul>
          </li>
@@ -815 +817 @@
       </p>
       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#method" class="smpl">method</a>         = <a href="#core.rules" class="smpl">token</a>
-</pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;10.1</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the
+</pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;9.1</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the
          set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> respond with the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the
          resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
@@ -1001 +1003 @@
                <tr>
                   <td class="left">Expect</td>
-                  <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;10.3</a></td>
+                  <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;9.3</a></td>
                </tr>
                <tr>
                   <td class="left">From</td>
-                  <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;10.4</a></td>
+                  <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;9.4</a></td>
                </tr>
                <tr>
@@ -1033 +1035 @@
                <tr>
                   <td class="left">Max-Forwards</td>
-                  <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;10.6</a></td>
+                  <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;9.6</a></td>
                </tr>
                <tr>
@@ -1045 +1047 @@
                <tr>
                   <td class="left">Referer</td>
-                  <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;10.7</a></td>
+                  <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;9.7</a></td>
                </tr>
                <tr>
@@ -1053 +1055 @@
                <tr>
                   <td class="left">User-Agent</td>
-                  <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;10.10</a></td>
+                  <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;9.10</a></td>
                </tr>
             </tbody>
@@ -1081 +1083 @@
                <tr>
                   <td class="left">Allow</td>
-                  <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;10.1</a></td>
+                  <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;9.1</a></td>
                </tr>
                <tr>
                   <td class="left">Date</td>
-                  <td class="left"><a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;10.2</a></td>
+                  <td class="left"><a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;9.2</a></td>
                </tr>
                <tr>
@@ -1093 +1095 @@
                <tr>
                   <td class="left">Location</td>
-                  <td class="left"><a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;10.5</a></td>
+                  <td class="left"><a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;9.5</a></td>
                </tr>
                <tr>
@@ -1101 +1103 @@
                <tr>
                   <td class="left">Retry-After</td>
-                  <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;10.8</a></td>
+                  <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;9.8</a></td>
                </tr>
                <tr>
                   <td class="left">Server</td>
-                  <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;10.9</a></td>
+                  <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;9.9</a></td>
                </tr>
                <tr>
@@ -1458 +1460 @@
          but might be defined by future extensions to HTTP. Content negotiation <em class="bcp14">MAY</em> be used to select the appropriate response format. If no response body is included, the response <em class="bcp14">MUST</em> include a Content-Length field with a field-value of "0".
       </p>
-      <p id="rfc.section.6.2.p.7">The Max-Forwards header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;10.6</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
+      <p id="rfc.section.6.2.p.7">The Max-Forwards header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;9.6</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
       </p>
       <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="GET" href="#GET">GET</a></h2>
@@ -1482 +1484 @@
       <p id="rfc.section.6.3.p.6">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
       </p>
-      <p id="rfc.section.6.3.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;12.2</a> for security considerations when used for forms.
+      <p id="rfc.section.6.3.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations when used for forms.
       </p>
       <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h2>
@@ -1516 +1518 @@
       </p>
       <p id="rfc.section.6.5.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be 201 (Created) and contain a representation which describes the status of the request and refers to the new resource, and
-         a Location header field (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;10.5</a>).
+         a Location header field (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;9.5</a>).
       </p>
       <p id="rfc.section.6.5.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a Content-Location header field (see <a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
@@ -1606 +1608 @@
       <div id="rfc.iref.m.7"></div>
       <p id="rfc.section.6.8.p.1">The TRACE method requests a remote, application-layer loop-back of the request message. The final recipient of the request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message body of a 200 (OK) response. The final recipient is either
-         the origin server or the first proxy to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;10.6</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
+         the origin server or the first proxy to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;9.6</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message body.
       </p>
       <p id="rfc.section.6.8.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
@@ -1818 +1820 @@
          </p> 
       </div>
-      <p id="rfc.section.7.3.p.4">A Location header field on a 3xx response indicates that a client <em class="bcp14">MAY</em> automatically redirect to the URI provided; see <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;10.5</a>.
+      <p id="rfc.section.7.3.p.4">A Location header field on a 3xx response indicates that a client <em class="bcp14">MAY</em> automatically redirect to the URI provided; see <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;9.5</a>.
       </p>
       <p id="rfc.section.7.3.p.5">Note that for methods not known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;6.1.1</a>, automatic redirection needs to done with care, since the redirect might change the conditions under which the request was
@@ -2034 +2036 @@
       <div id="rfc.iref.s.30"></div>
       <h3 id="rfc.section.7.4.14"><a href="#rfc.section.7.4.14">7.4.14</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
-      <p id="rfc.section.7.4.14.p.1">The expectation given in an Expect header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;10.3</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
+      <p id="rfc.section.7.4.14.p.1">The expectation given in an Expect header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;9.3</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
          not be met by the next-hop server.
       </p>
@@ -2079 +2081 @@
       <p id="rfc.section.7.5.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.</p>
       <p id="rfc.section.7.5.4.p.2">The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the
-         delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;10.8</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
+         delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field (<a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;9.8</a>). If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
       </p>
       <div class="note" id="rfc.section.7.5.4.p.3"> 
@@ -2103 +2105 @@
          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.
       </p>
-      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="http.date" href="#http.date">Date/Time Formats</a></h1>
-      <p id="rfc.section.8.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is
+      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="common.protocol.parameters" href="#common.protocol.parameters">Common Protocol Parameters</a></h1>
+      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="http.date" href="#http.date">Date/Time Formats</a></h2>
+      <p id="rfc.section.8.1.p.1">HTTP applications have historically allowed three different formats for date/time stamps. However, the preferred format is
          a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>:
       </p>
       <div id="rfc.figure.u.9"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
-</pre><p id="rfc.section.8.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
+</pre><p id="rfc.section.8.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
       <div id="rfc.figure.u.10"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
 Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
-</pre><p id="rfc.section.8.p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields.
-      </p>
-      <p id="rfc.section.8.p.6">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
+</pre><p id="rfc.section.8.1.p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields.
+      </p>
+      <p id="rfc.section.8.1.p.6">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
          Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for
          time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional whitespace beyond that specifically included as SP in the grammar.
@@ -2119 +2122 @@
       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#http.date" class="smpl">HTTP-date</a>    = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>
 </pre><div id="preferred.date.format">
-         <p id="rfc.section.8.p.8">                    Preferred format:</p>
+         <p id="rfc.section.8.1.p.8">                    Preferred format:</p>
       </div>
       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#notation" class="smpl">SP</a> date1 <a href="#notation" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#notation" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
@@ -2159 +2162 @@
   <a href="#preferred.date.format" class="smpl">minute</a>       = 2<a href="#notation" class="smpl">DIGIT</a>               
   <a href="#preferred.date.format" class="smpl">second</a>       = 2<a href="#notation" class="smpl">DIGIT</a>               
-</pre><p id="rfc.section.8.p.10">The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined for the RFC 5322 constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
+</pre><p id="rfc.section.8.1.p.10">The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined for the RFC 5322 constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
       </p>
       <div id="obsolete.date.formats">
-         <p id="rfc.section.8.p.11">                Obsolete formats:</p>
+         <p id="rfc.section.8.1.p.11">                Obsolete formats:</p>
       </div>
       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.19"></span>  <a href="#obsolete.date.formats" class="smpl">obs-date</a>     = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a> 
@@ -2179 +2182 @@
   <a href="#obsolete.date.formats" class="smpl">date3</a>        = <a href="#preferred.date.format" class="smpl">month</a> <a href="#notation" class="smpl">SP</a> ( 2<a href="#notation" class="smpl">DIGIT</a> / ( <a href="#notation" class="smpl">SP</a> 1<a href="#notation" class="smpl">DIGIT</a> ))
                  ; month day (e.g., Jun  2)
-</pre><div class="note" id="rfc.section.8.p.15"> 
+</pre><div class="note" id="rfc.section.8.1.p.15"> 
          <p> <b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that might have been sent by non-HTTP applications,
             as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP.
          </p> 
       </div>
-      <div class="note" id="rfc.section.8.p.16"> 
+      <div class="note" id="rfc.section.8.1.p.16"> 
          <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers
             are not required to use these formats for user presentation, request logging, etc.
          </p> 
       </div>
-      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h1>
-      <p id="rfc.section.9.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
+      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h2>
+      <p id="rfc.section.8.2.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
          using product tokens also allow sub-products which form a significant part of the application to be listed, separated by whitespace.
          By convention, the products are listed in order of their significance for identifying the application.
@@ -2196 +2199 @@
       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#core.rules" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
   <a href="#product.tokens" class="smpl">product-version</a> = <a href="#core.rules" class="smpl">token</a>
-</pre><p id="rfc.section.9.p.3">Examples:</p>
+</pre><p id="rfc.section.8.2.p.3">Examples:</p>
       <div id="rfc.figure.u.17"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
   Server: Apache/0.8.4
-</pre><p id="rfc.section.9.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
-      </p>
-      <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
-      <p id="rfc.section.10.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>
+</pre><p id="rfc.section.8.2.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
+      </p>
+      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
+      <p id="rfc.section.9.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>
       <div id="rfc.iref.a.1"></div>
       <div id="rfc.iref.h.2"></div>
-      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
-      <p id="rfc.section.10.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
+      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
+      <p id="rfc.section.9.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
          is strictly to inform the recipient of valid request methods associated with the resource.
       </p>
       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.24"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#method" class="smpl">method</a>
-</pre><p id="rfc.section.10.1.p.3">Example of use:</p>
+</pre><p id="rfc.section.9.1.p.3">Example of use:</p>
       <div id="rfc.figure.u.19"></div><pre class="text">  Allow: GET, HEAD, PUT
-</pre><p id="rfc.section.10.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
-      <p id="rfc.section.10.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according
+</pre><p id="rfc.section.9.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
+      <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according
          to the generic message handling rules.
       </p>
       <div id="rfc.iref.d.2"></div>
       <div id="rfc.iref.h.3"></div>
-      <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h2>
-      <p id="rfc.section.10.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
-         Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;8</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
+      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h2>
+      <p id="rfc.section.9.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
+         Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;8.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
       </p>
       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.25"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
-</pre><p id="rfc.section.10.2.p.3">An example is</p>
+</pre><p id="rfc.section.9.2.p.3">An example is</p>
       <div id="rfc.figure.u.21"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
-</pre><p id="rfc.section.10.2.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases: 
+</pre><p id="rfc.section.9.2.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases: 
       </p>
       <ol>
@@ -2236 +2239 @@
          </li>
       </ol>
-      <p id="rfc.section.10.2.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient.
-      </p>
-      <p id="rfc.section.10.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it
+      <p id="rfc.section.9.2.p.6">A received message that does not have a Date header field <em class="bcp14">MUST</em> be assigned one by the recipient if the message will be cached by that recipient.
+      </p>
+      <p id="rfc.section.9.2.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it
          when it doesn't convey any useful information (as is usually the case for requests that do not contain a payload).
       </p>
-      <p id="rfc.section.10.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means
+      <p id="rfc.section.9.2.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means
          of generating a reasonably accurate date and time. In theory, the date ought to represent the moment just before the payload
          is generated. In practice, the date can be generated at any time during the message origination without affecting its semantic
@@ -2248 +2251 @@
       <div id="rfc.iref.e.1"></div>
       <div id="rfc.iref.h.4"></div>
-      <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
-      <p id="rfc.section.10.3.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
+      <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
+      <p id="rfc.section.9.3.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.expect" class="smpl">Expect</a>       = 1#<a href="#header.expect" class="smpl">expectation</a>
   
@@ -2258 +2261 @@
   <a href="#header.expect" class="smpl">expect-name</a>  = <a href="#core.rules" class="smpl">token</a>
   <a href="#header.expect" class="smpl">expect-value</a> = <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a>
-</pre><p id="rfc.section.10.3.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
+</pre><p id="rfc.section.9.3.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
          or cannot comply with, the recipient <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status code. A recipient of a syntactically invalid Expectation header field <em class="bcp14">MUST</em> respond with a 4xx status code other than 417.
       </p>
-      <p id="rfc.section.10.3.p.4">The only expectation defined by this specification is:</p>
-      <p id="rfc.section.10.3.p.5"><span id="rfc.iref.89"></span><span id="rfc.iref.e.2"></span> 100-continue 
+      <p id="rfc.section.9.3.p.4">The only expectation defined by this specification is:</p>
+      <p id="rfc.section.9.3.p.5"><span id="rfc.iref.89"></span><span id="rfc.iref.e.2"></span> 100-continue 
       </p>
       <ul class="empty">
@@ -2268 +2271 @@
          </li>
       </ul>
-      <p id="rfc.section.10.3.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>
-      <p id="rfc.section.10.3.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header
+      <p id="rfc.section.9.3.p.6">Comparison is case-insensitive for names (expect-name), and case-sensitive for values (expect-value).</p>
+      <p id="rfc.section.9.3.p.7">The Expect mechanism is hop-by-hop: the above requirements apply to any server, including proxies. However, the Expect header
          field itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
       </p>
-      <p id="rfc.section.10.3.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
+      <p id="rfc.section.9.3.p.8">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
       <div id="rfc.iref.f.1"></div>
       <div id="rfc.iref.h.5"></div>
-      <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
-      <p id="rfc.section.10.4.p.1">The "From" header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>:
+      <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
+      <p id="rfc.section.9.4.p.1">The "From" header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>:
       </p>
       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  <a href="#header.from" class="smpl">From</a>    = <a href="#header.from" class="smpl">mailbox</a>
   
   <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
-</pre><p id="rfc.section.10.4.p.3">An example is:</p>
+</pre><p id="rfc.section.9.4.p.3">An example is:</p>
       <div id="rfc.figure.u.24"></div><pre class="text">  From: webmaster@example.org
-</pre><p id="rfc.section.10.4.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed
+</pre><p id="rfc.section.9.4.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed
          on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header field so that the person responsible for running the robot can be contacted if problems occur on the receiving
          end.
       </p>
-      <p id="rfc.section.10.4.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original
+      <p id="rfc.section.9.4.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original
          issuer's address <em class="bcp14">SHOULD</em> be used.
       </p>
-      <p id="rfc.section.10.4.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's
+      <p id="rfc.section.9.4.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's
          security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
          any time prior to a request.
@@ -2296 +2299 @@
       <div id="rfc.iref.l.1"></div>
       <div id="rfc.iref.h.6"></div>
-      <h2 id="rfc.section.10.5"><a href="#rfc.section.10.5">10.5</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
-      <p id="rfc.section.10.5.p.1">The "Location" header field <em class="bcp14">MAY</em> be sent in responses to refer to a specific resource in accordance with the semantics of the status code.
+      <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
+      <p id="rfc.section.9.5.p.1">The "Location" header field <em class="bcp14">MAY</em> be sent in responses to refer to a specific resource in accordance with the semantics of the status code.
       </p>
       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#abnf.dependencies" class="smpl">URI-reference</a>
-</pre><p id="rfc.section.10.5.p.3">For 201 (Created) responses, the Location is the URI of the new resource which was created by the request. For 3xx responses,
+</pre><p id="rfc.section.9.5.p.3">For 201 (Created) responses, the Location is the URI of the new resource which was created by the request. For 3xx responses,
          the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
       </p>
-      <p id="rfc.section.10.5.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not,
+      <p id="rfc.section.9.5.p.4">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>). If the original URI, as navigated to by the user agent, did contain a fragment identifier, and the final value does not,
          then the original URI's fragment identifier is added to the final value.
       </p>
@@ -2312 +2315 @@
       <p>An original URI "http://www.example.org/index.html#larry", combined with a field value given as:</p>  <pre class="text">  Location: http://www.example.net/index.html
 </pre>  <p>would result in a final value of "http://www.example.net/index.html#larry", preserving the original fragment identifier.</p> 
-      <div class="note" id="rfc.section.10.5.p.7"> 
+      <div class="note" id="rfc.section.9.5.p.7"> 
          <p> <b>Note:</b> Some recipients attempt to recover from Location fields that are not valid URI references. This specification does not mandate
             or define such processing, but does allow it (see <a href="#intro.conformance.and.error.handling" title="Conformance and Error Handling">Section&nbsp;1.1</a>).
          </p> 
       </div>
-      <p id="rfc.section.10.5.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
+      <p id="rfc.section.9.5.p.8">There are circumstances in which a fragment identifier in a Location URI would not be appropriate. For instance, when it appears
          in a 201 Created response, where the Location header field specifies the URI for the entire created resource.
       </p>
-      <div class="note" id="rfc.section.10.5.p.9"> 
+      <div class="note" id="rfc.section.9.5.p.9"> 
          <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
             It is therefore possible for a response to contain header fields for both Location and Content-Location.
@@ -2327 +2330 @@
       <div id="rfc.iref.m.9"></div>
       <div id="rfc.iref.h.7"></div>
-      <h2 id="rfc.section.10.6"><a href="#rfc.section.10.6">10.6</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
-      <p id="rfc.section.10.6.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;6.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;6.2</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
+      <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
+      <p id="rfc.section.9.6.p.1">The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;6.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;6.2</a>) methods to limit the number of times that the request is forwarded by proxies. This can be useful when the client is attempting
          to trace a request which appears to be failing or looping mid-chain.
       </p>
       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
-</pre><p id="rfc.section.10.6.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
-      <p id="rfc.section.10.6.p.4">Each recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
-      </p>
-      <p id="rfc.section.10.6.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
+</pre><p id="rfc.section.9.6.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
+      <p id="rfc.section.9.6.p.4">Each recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
+      </p>
+      <p id="rfc.section.9.6.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other request methods.
       </p>
       <div id="rfc.iref.r.1"></div>
       <div id="rfc.iref.h.8"></div>
-      <h2 id="rfc.section.10.7"><a href="#rfc.section.10.7">10.7</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
-      <p id="rfc.section.10.7.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained
+      <h2 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
+      <p id="rfc.section.9.7.p.1">The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained
          (the "referrer", although the header field is misspelled.).
       </p>
-      <p id="rfc.section.10.7.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
+      <p id="rfc.section.9.7.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
          etc. It also allows obsolete or mistyped links to be traced for maintenance. Some servers use Referer as a means of controlling
          where they allow links from (so-called "deep linking"), but legitimate requests do not always contain a Referer header field.
       </p>
-      <p id="rfc.section.10.7.p.3">If the target URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the Referer
+      <p id="rfc.section.9.7.p.3">If the target URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the Referer
          field <em class="bcp14">MUST</em> either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not apply to sources with
          non-HTTP URIs (e.g., FTP).
       </p>
       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.34"></span>  <a href="#header.referer" class="smpl">Referer</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
-</pre><p id="rfc.section.10.7.p.5">Example:</p>
+</pre><p id="rfc.section.9.7.p.5">Example:</p>
       <div id="rfc.figure.u.30"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
-</pre><p id="rfc.section.10.7.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;12.2</a> for security considerations.
+</pre><p id="rfc.section.9.7.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations.
       </p>
       <div id="rfc.iref.r.2"></div>
       <div id="rfc.iref.h.9"></div>
-      <h2 id="rfc.section.10.8"><a href="#rfc.section.10.8">10.8</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
-      <p id="rfc.section.10.8.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected
+      <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
+      <p id="rfc.section.9.8.p.1">The header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected
          to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked to wait before issuing
          the redirected request.
       </p>
-      <p id="rfc.section.10.8.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
+      <p id="rfc.section.9.8.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
       <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.35"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a> = <a href="#http.date" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
 </pre><div id="rule.delta-seconds">
-         <p id="rfc.section.10.8.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
+         <p id="rfc.section.9.8.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
       </div>
       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.36"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
-</pre><p id="rfc.section.10.8.p.6">Two examples of its use are</p>
+</pre><p id="rfc.section.9.8.p.6">Two examples of its use are</p>
       <div id="rfc.figure.u.33"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
   Retry-After: 120
-</pre><p id="rfc.section.10.8.p.8">In the latter example, the delay is 2 minutes.</p>
+</pre><p id="rfc.section.9.8.p.8">In the latter example, the delay is 2 minutes.</p>
       <div id="rfc.iref.s.38"></div>
       <div id="rfc.iref.h.10"></div>
-      <h2 id="rfc.section.10.9"><a href="#rfc.section.10.9">10.9</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
-      <p id="rfc.section.10.9.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
-      <p id="rfc.section.10.9.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;9</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.39"><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
+      <h2 id="rfc.section.9.9"><a href="#rfc.section.9.9">9.9</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
+      <p id="rfc.section.9.9.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
+      <p id="rfc.section.9.9.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;8.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.39"><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
          identifying the application.
       </p>
       <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.37"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
-</pre><p id="rfc.section.10.9.p.4">Example:</p>
+</pre><p id="rfc.section.9.9.p.4">Example:</p>
       <div id="rfc.figure.u.35"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
-</pre><p id="rfc.section.10.9.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.40"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
-      </p>
-      <div class="note" id="rfc.section.10.9.p.7"> 
+</pre><p id="rfc.section.9.9.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.40"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
+      </p>
+      <div class="note" id="rfc.section.9.9.p.7"> 
          <p> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
             against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable
@@ -2393 +2396 @@
       <div id="rfc.iref.u.1"></div>
       <div id="rfc.iref.h.11"></div>
-      <h2 id="rfc.section.10.10"><a href="#rfc.section.10.10">10.10</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>
-      <p id="rfc.section.10.10.p.1">The "User-Agent" header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests.
-      </p>
-      <p id="rfc.section.10.10.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
+      <h2 id="rfc.section.9.10"><a href="#rfc.section.9.10">9.10</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>
+      <p id="rfc.section.9.10.p.1">The "User-Agent" header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests.
+      </p>
+      <p id="rfc.section.9.10.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
          user agent limitations.
       </p>
-      <p id="rfc.section.10.10.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;9</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.41"><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
+      <p id="rfc.section.9.10.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;8.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.41"><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
          for identifying the application.
       </p>
-      <p id="rfc.section.10.10.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
+      <p id="rfc.section.9.10.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
          fine-grained detail, and to limit (or even prohibit) the addition of subproducts by third parties. Overly long and detailed
          User-Agent field values make requests larger and can also be used to identify ("fingerprint") the user against their wishes.
       </p>
-      <p id="rfc.section.10.10.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
+      <p id="rfc.section.9.10.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
          with them, as this circumvents the purpose of the field. Finally, they are encouraged not to use comments to identify products;
          doing so makes the field value more difficult to parse.
       </p>
       <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.38"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
-</pre><p id="rfc.section.10.10.p.7">Example:</p>
+</pre><p id="rfc.section.9.10.p.7">Example:</p>
       <div id="rfc.figure.u.37"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
-</pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
-      <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
-      <p id="rfc.section.11.1.p.1">The registration procedure for HTTP request methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.2</a> of this document.
-      </p>
-      <p id="rfc.section.11.1.p.2">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
+</pre><h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
+      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
+      <p id="rfc.section.10.1.p.1">The registration procedure for HTTP request methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.2</a> of this document.
+      </p>
+      <p id="rfc.section.10.1.p.2">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
       </p>
       <div id="rfc.table.1">
@@ -2481 +2484 @@
          </table>
       </div>
-      <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
-      <p id="rfc.section.11.2.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&nbsp;4.2</a> of this document.
-      </p>
-      <p id="rfc.section.11.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
+      <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
+      <p id="rfc.section.10.2.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&nbsp;4.2</a> of this document.
+      </p>
+      <p id="rfc.section.10.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
       </p>
       <div id="rfc.table.2">
@@ -2716 +2719 @@
          </table>
       </div>
-      <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
-      <p id="rfc.section.11.3.p.1">The Message Header Field Registry located at &lt;<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>&gt; 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>):
+      <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
+      <p id="rfc.section.10.3.p.1">The Message Header Field Registry located at &lt;<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>&gt; 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>):
       </p>
       <div id="rfc.table.3">
@@ -2735 +2738 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;10.1</a> 
+                  <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;9.1</a> 
                   </td>
                </tr>
@@ -2742 +2745 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section&nbsp;10.2</a> 
+                  <td class="left"> <a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section&nbsp;9.2</a> 
                   </td>
                </tr>
@@ -2749 +2752 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;10.3</a> 
+                  <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;9.3</a> 
                   </td>
                </tr>
@@ -2756 +2759 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;10.4</a> 
+                  <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;9.4</a> 
                   </td>
                </tr>
@@ -2763 +2766 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;10.5</a> 
+                  <td class="left"> <a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.5</a> 
                   </td>
                </tr>
@@ -2770 +2773 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;10.6</a> 
+                  <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;9.6</a> 
                   </td>
                </tr>
@@ -2777 +2780 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;10.7</a> 
+                  <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;9.7</a> 
                   </td>
                </tr>
@@ -2784 +2787 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;10.8</a> 
+                  <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.3" title="Retry-After">Section&nbsp;9.8</a> 
                   </td>
                </tr>
@@ -2791 +2794 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;10.9</a> 
+                  <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;9.9</a> 
                   </td>
                </tr>
@@ -2798 +2801 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;10.10</a> 
+                  <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;9.10</a> 
                   </td>
                </tr>
@@ -2804 +2807 @@
          </table>
       </div>
-      <p id="rfc.section.11.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
-      <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
-      <p id="rfc.section.12.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
+      <p id="rfc.section.10.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
+      <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
+      <p id="rfc.section.11.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
          as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
          make some suggestions for reducing security risks.
       </p>
-      <h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
-      <p id="rfc.section.12.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
+      <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
+      <p id="rfc.section.11.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
          a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
          Therefore, applications <em class="bcp14">SHOULD</em> supply as much control over this information as possible to the provider of that information. Four header fields are worth
          special mention in this context: Server, Via, Referer and From.
       </p>
-      <p id="rfc.section.12.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
+      <p id="rfc.section.11.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
          against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option.
       </p>
-      <p id="rfc.section.12.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
+      <p id="rfc.section.11.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
          they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall.
       </p>
-      <p id="rfc.section.12.1.p.4">The Referer header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its
+      <p id="rfc.section.11.1.p.4">The Referer header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its
          power can be abused if user details are not separated from the information contained in the Referer. Even when the personal
          information has been removed, the Referer header field might indicate a private document's URI whose publication would be
          inappropriate.
       </p>
-      <p id="rfc.section.12.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and
+      <p id="rfc.section.11.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and
          hence it <em class="bcp14">SHOULD NOT</em> be transmitted without the user being able to disable, enable, and modify the contents of the field. The user <em class="bcp14">MUST</em> be able to set the contents of this field within a user preference or application defaults configuration.
       </p>
-      <p id="rfc.section.12.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
+      <p id="rfc.section.11.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
          of From and Referer information.
       </p>
-      <p id="rfc.section.12.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;10.10</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;10.9</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might
+      <p id="rfc.section.11.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;9.10</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;9.9</a>) header fields can sometimes be used to determine that a specific client or server has a particular security hole which might
          be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently has
          no better mechanism.
       </p>
-      <p id="rfc.section.12.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,
+      <p id="rfc.section.11.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,
          to uniquely identify the user.
       </p>
-      <p id="rfc.section.12.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;6.8</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used
+      <p id="rfc.section.11.1.p.9">Some request methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;6.8</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials, and other header fields that might be used
          to collect data from the client.
       </p>
-      <h2 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
-      <p id="rfc.section.12.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
+      <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
+      <p id="rfc.section.11.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
          recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could
          have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From
          information.
       </p>
-      <p id="rfc.section.12.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
-      </p>
-      <p id="rfc.section.12.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing
+      <p id="rfc.section.11.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
+      </p>
+      <p id="rfc.section.11.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing
          servers, proxies, and user agents log or display the request-target in places where it might be visible to third parties.
          Such services can use POST-based form submission instead.
       </p>
-      <h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a>&nbsp;<a id="location.spoofing-leakage" href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></h2>
-      <p id="rfc.section.12.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location header fields in responses that are generated under control of said organizations
+      <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a id="location.spoofing-leakage" href="#location.spoofing-leakage">Location Header Fields: Spoofing and Information Leakage</a></h2>
+      <p id="rfc.section.11.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location header fields in responses that are generated under control of said organizations
          to make sure that they do not attempt to invalidate resources over which they have no authority.
       </p>
-      <p id="rfc.section.12.3.p.2">Furthermore, appending the fragment identifier from one URI to another one obtained from a Location header field might leak
+      <p id="rfc.section.11.3.p.2">Furthermore, appending the fragment identifier from one URI to another one obtained from a Location header field might leak
          confidential information to the target server — although the fragment identifier is not transmitted in the final request,
          it might be visible to the user agent through other means, such as scripting.
       </p>
-      <h2 id="rfc.section.12.4"><a href="#rfc.section.12.4">12.4</a>&nbsp;Security Considerations for CONNECT
+      <h2 id="rfc.section.11.4"><a href="#rfc.section.11.4">11.4</a>&nbsp;Security Considerations for CONNECT
       </h2>
-      <p id="rfc.section.12.4.p.1">Since tunneled data is opaque to the proxy, there are additional risks to tunneling to other well-known or reserved ports.
+      <p id="rfc.section.11.4.p.1">Since tunneled data is opaque to the proxy, there are additional risks to tunneling to other well-known or reserved ports.
          A HTTP client CONNECTing to port 25 could relay spam via SMTP, for example. As such, proxies <em class="bcp14">SHOULD</em> restrict CONNECT access to a small number of known ports.
       </p>
-      <h1 id="rfc.section.13"><a href="#rfc.section.13">13.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
-      <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.42"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
-      </p>
-      <h1 id="rfc.references"><a id="rfc.section.14" href="#rfc.section.14">14.</a> References
+      <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
+      <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.42"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
+      </p>
+      <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References
       </h1>
-      <h2 id="rfc.references.1"><a href="#rfc.section.14.1" id="rfc.section.14.1">14.1</a> Normative References
+      <h2 id="rfc.references.1"><a href="#rfc.section.13.1" id="rfc.section.13.1">13.1</a> Normative References
       </h2>
       <table>                  
@@ -2922 +2925 @@
          </tr>
       </table>
-      <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References
+      <h2 id="rfc.references.2"><a href="#rfc.section.13.2" id="rfc.section.13.2">13.2</a> Informative References
       </h2>
       <table>                      
@@ -3016 +3019 @@
       <p id="rfc.section.A.p.9">Define status 426 (Upgrade Required) (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section&nbsp;7.4.15</a>)
       </p>
-      <p id="rfc.section.A.p.10">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;10</a>)
+      <p id="rfc.section.A.p.10">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;9</a>)
       </p>
       <p id="rfc.section.A.p.11">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement
-         on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;10.1</a>)
+         on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;9.1</a>)
       </p>
       <p id="rfc.section.A.p.12">The ABNF for the Expect header field has been both fixed (allowing parameters for value-less expectations as well) and simplified
-         (allowing trailing semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section&nbsp;10.3</a>)
+         (allowing trailing semicolons after "100-continue" when they were invalid before). (<a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section&nbsp;9.3</a>)
       </p>
       <p id="rfc.section.A.p.13">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
          symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate.
-         (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section&nbsp;10.5</a>)
-      </p>
-      <p id="rfc.section.A.p.14">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section&nbsp;10.6</a>)
-      </p>
-      <p id="rfc.section.A.p.15">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;10.7</a>)
+         (<a href="#header.location" id="rfc.xref.header.location.5" title="Location">Section&nbsp;9.5</a>)
+      </p>
+      <p id="rfc.section.A.p.14">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section&nbsp;9.6</a>)
+      </p>
+      <p id="rfc.section.A.p.15">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.7</a>)
       </p>
       <p id="rfc.section.A.p.16">In the description of the Server header field, the Via 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 6.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>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;10.9</a>)
+         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.43"><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.9</a>)
       </p>
       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
@@ -3476 +3479 @@
          <ul class="ind">
             <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
-                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.22"><b>7.1.1</b></a>, <a href="#rfc.xref.status.100.2">11.2</a></li>
-                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.89"><b>10.3</b></a></li>
-                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.23"><b>7.1.2</b></a>, <a href="#rfc.xref.status.101.2">11.2</a></li>
+                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.22"><b>7.1.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li>
+                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.89"><b>9.3</b></a></li>
+                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.23"><b>7.1.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
-                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.24"><b>7.2.1</b></a>, <a href="#rfc.xref.status.200.2">11.2</a></li>
-                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.25"><b>7.2.2</b></a>, <a href="#rfc.xref.status.201.2">11.2</a></li>
-                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.26"><b>7.2.3</b></a>, <a href="#rfc.xref.status.202.2">11.2</a></li>
-                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.27"><b>7.2.4</b></a>, <a href="#rfc.xref.status.203.2">11.2</a>, <a href="#rfc.xref.status.203.3">A</a></li>
-                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.28"><b>7.2.5</b></a>, <a href="#rfc.xref.status.204.2">11.2</a></li>
-                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.29"><b>7.2.6</b></a>, <a href="#rfc.xref.status.205.2">11.2</a></li>
+                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.24"><b>7.2.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li>
+                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.25"><b>7.2.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li>
+                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.26"><b>7.2.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li>
+                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.27"><b>7.2.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a>, <a href="#rfc.xref.status.203.3">A</a></li>
+                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.28"><b>7.2.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li>
+                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.29"><b>7.2.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
-                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.30"><b>7.3.1</b></a>, <a href="#rfc.xref.status.300.2">11.2</a></li>
-                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.31"><b>7.3.2</b></a>, <a href="#rfc.xref.status.301.2">11.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>
-                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.32"><b>7.3.3</b></a>, <a href="#rfc.xref.status.302.2">11.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>
-                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.33"><b>7.3.4</b></a>, <a href="#rfc.xref.status.303.2">11.2</a></li>
-                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.34"><b>7.3.5</b></a>, <a href="#rfc.xref.status.305.2">11.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>
-                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.35"><b>7.3.6</b></a>, <a href="#rfc.xref.status.306.1">11.2</a></li>
-                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.36"><b>7.3.7</b></a>, <a href="#rfc.xref.status.307.2">11.2</a>, <a href="#rfc.xref.status.307.3">A</a></li>
+                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.30"><b>7.3.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li>
+                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.31"><b>7.3.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>
+                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.32"><b>7.3.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>
+                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.33"><b>7.3.4</b></a>, <a href="#rfc.xref.status.303.2">10.2</a></li>
+                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.34"><b>7.3.5</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>
+                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.35"><b>7.3.6</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li>
+                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.36"><b>7.3.7</b></a>, <a href="#rfc.xref.status.307.2">10.2</a>, <a href="#rfc.xref.status.307.3">A</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
-                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.37"><b>7.4.1</b></a>, <a href="#rfc.xref.status.400.2">11.2</a></li>
-                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.38"><b>7.4.2</b></a>, <a href="#rfc.xref.status.402.2">11.2</a></li>
-                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.39"><b>7.4.3</b></a>, <a href="#rfc.xref.status.403.2">11.2</a></li>
-                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.40"><b>7.4.4</b></a>, <a href="#rfc.xref.status.404.2">11.2</a></li>
-                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.41"><b>7.4.5</b></a>, <a href="#rfc.xref.status.405.2">11.2</a></li>
-                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.42"><b>7.4.6</b></a>, <a href="#rfc.xref.status.406.2">11.2</a></li>
-                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.43"><b>7.4.7</b></a>, <a href="#rfc.xref.status.408.2">11.2</a></li>
-                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.44"><b>7.4.8</b></a>, <a href="#rfc.xref.status.409.2">11.2</a></li>
-                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.45"><b>7.4.9</b></a>, <a href="#rfc.xref.status.410.2">11.2</a></li>
-                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.46"><b>7.4.10</b></a>, <a href="#rfc.xref.status.411.2">11.2</a></li>
-                  <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.47"><b>7.4.11</b></a>, <a href="#rfc.xref.status.413.2">11.2</a></li>
-                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.48"><b>7.4.12</b></a>, <a href="#rfc.xref.status.414.2">11.2</a></li>
-                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.49"><b>7.4.13</b></a>, <a href="#rfc.xref.status.415.2">11.2</a></li>
-                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.50"><b>7.4.14</b></a>, <a href="#rfc.xref.status.417.2">11.2</a></li>
-                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.51"><b>7.4.15</b></a>, <a href="#rfc.xref.status.426.2">11.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>
+                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.37"><b>7.4.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li>
+                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.38"><b>7.4.2</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li>
+                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.39"><b>7.4.3</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li>
+                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.40"><b>7.4.4</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li>
+                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.41"><b>7.4.5</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li>
+                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.42"><b>7.4.6</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li>
+                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.43"><b>7.4.7</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li>
+                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.44"><b>7.4.8</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li>
+                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.45"><b>7.4.9</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li>
+                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.46"><b>7.4.10</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li>
+                  <li>413 Request Representation Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.47"><b>7.4.11</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li>
+                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.48"><b>7.4.12</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li>
+                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.49"><b>7.4.13</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li>
+                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.50"><b>7.4.14</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li>
+                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.51"><b>7.4.15</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
-                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.52"><b>7.5.1</b></a>, <a href="#rfc.xref.status.500.2">11.2</a></li>
-                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.53"><b>7.5.2</b></a>, <a href="#rfc.xref.status.501.2">11.2</a></li>
-                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.54"><b>7.5.3</b></a>, <a href="#rfc.xref.status.502.2">11.2</a></li>
-                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.55"><b>7.5.4</b></a>, <a href="#rfc.xref.status.503.2">11.2</a></li>
-                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.56"><b>7.5.5</b></a>, <a href="#rfc.xref.status.504.2">11.2</a></li>
-                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.57"><b>7.5.6</b></a>, <a href="#rfc.xref.status.505.2">11.2</a></li>
+                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.52"><b>7.5.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li>
+                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.53"><b>7.5.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li>
+                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.54"><b>7.5.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li>
+                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.55"><b>7.5.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li>
+                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.56"><b>7.5.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li>
+                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.57"><b>7.5.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
-                  <li>Allow header field&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.a.1"><b>10.1</b></a>, <a href="#rfc.xref.header.allow.3">11.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li>
+                  <li>Allow header field&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.a.1"><b>9.1</b></a>, <a href="#rfc.xref.header.allow.3">10.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
-                  <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">2.1</a>, <a href="#rfc.iref.c.1"><b>6.9</b></a>, <a href="#rfc.xref.CONNECT.2">11.1</a>, <a href="#rfc.xref.CONNECT.3">A</a></li>
+                  <li>CONNECT method&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">2.1</a>, <a href="#rfc.iref.c.1"><b>6.9</b></a>, <a href="#rfc.xref.CONNECT.2">10.1</a>, <a href="#rfc.xref.CONNECT.3">A</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul>
-                  <li>Date header field&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.d.2"><b>10.2</b></a>, <a href="#rfc.xref.header.date.2">11.3</a></li>
-                  <li>DELETE method&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">2.1</a>, <a href="#rfc.iref.d.1"><b>6.7</b></a>, <a href="#rfc.xref.DELETE.2">11.1</a></li>
-                  <li><em>draft-reschke-http-status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.draft-reschke-http-status-308.1">7.3.7</a>, <a href="#draft-reschke-http-status-308"><b>14.2</b></a></li>
+                  <li>Date header field&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.d.2"><b>9.2</b></a>, <a href="#rfc.xref.header.date.2">10.3</a></li>
+                  <li>DELETE method&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">2.1</a>, <a href="#rfc.iref.d.1"><b>6.7</b></a>, <a href="#rfc.xref.DELETE.2">10.1</a></li>
+                  <li><em>draft-reschke-http-status-308</em>&nbsp;&nbsp;<a href="#rfc.xref.draft-reschke-http-status-308.1">7.3.7</a>, <a href="#draft-reschke-http-status-308"><b>13.2</b></a></li>
                </ul>
             </li>
             <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
-                  <li>Expect header field&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">7.4.14</a>, <a href="#rfc.iref.e.1"><b>10.3</b></a>, <a href="#rfc.xref.header.expect.3">11.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li>
+                  <li>Expect header field&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">7.4.14</a>, <a href="#rfc.iref.e.1"><b>9.3</b></a>, <a href="#rfc.xref.header.expect.3">10.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li>
                   <li>Expect Values&nbsp;&nbsp;
                      <ul>
-                        <li>100-continue&nbsp;&nbsp;<a href="#rfc.iref.e.2"><b>10.3</b></a></li>
+                        <li>100-continue&nbsp;&nbsp;<a href="#rfc.iref.e.2"><b>9.3</b></a></li>
                      </ul>
                   </li>
@@ -3551 +3554 @@
             </li>
             <li><a id="rfc.index.F" href="#rfc.index.F"><b>F</b></a><ul>
-                  <li>From header field&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.f.1"><b>10.4</b></a>, <a href="#rfc.xref.header.from.2">11.3</a></li>
+                  <li>From header field&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.f.1"><b>9.4</b></a>, <a href="#rfc.xref.header.from.2">10.3</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
-                  <li>GET method&nbsp;&nbsp;<a href="#rfc.xref.GET.1">2.1</a>, <a href="#rfc.iref.g.5"><b>6.3</b></a>, <a href="#rfc.xref.GET.2">11.1</a></li>
+                  <li>GET method&nbsp;&nbsp;<a href="#rfc.xref.GET.1">2.1</a>, <a href="#rfc.iref.g.5"><b>6.3</b></a>, <a href="#rfc.xref.GET.2">10.1</a></li>
                   <li><tt>Grammar</tt>&nbsp;&nbsp;
                      <ul>
-                        <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>10.1</b></a></li>
-                        <li><tt>asctime-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>8</b></a></li>
-                        <li><tt>Date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>10.2</b></a></li>
-                        <li><tt>date1</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>8</b></a></li>
-                        <li><tt>day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>8</b></a></li>
-                        <li><tt>day-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>8</b></a></li>
-                        <li><tt>day-name-l</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>8</b></a></li>
-                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>10.8</b></a></li>
-                        <li><tt>Expect</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>10.3</b></a></li>
-                        <li><tt>expect-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>10.3</b></a></li>
-                        <li><tt>expect-param</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>10.3</b></a></li>
-                        <li><tt>expect-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>10.3</b></a></li>
-                        <li><tt>expectation</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>10.3</b></a></li>
+                        <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>9.1</b></a></li>
+                        <li><tt>asctime-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>8.1</b></a></li>
+                        <li><tt>Date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>9.2</b></a></li>
+                        <li><tt>date1</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>8.1</b></a></li>
+                        <li><tt>day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>8.1</b></a></li>
+                        <li><tt>day-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>8.1</b></a></li>
+                        <li><tt>day-name-l</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>8.1</b></a></li>
+                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>9.8</b></a></li>
+                        <li><tt>Expect</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>9.3</b></a></li>
+                        <li><tt>expect-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>9.3</b></a></li>
+                        <li><tt>expect-param</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>9.3</b></a></li>
+                        <li><tt>expect-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>9.3</b></a></li>
+                        <li><tt>expectation</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>9.3</b></a></li>
                         <li><tt>extension-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>4</b></a></li>
-                        <li><tt>From</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>10.4</b></a></li>
-                        <li><tt>GMT</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>8</b></a></li>
-                        <li><tt>hour</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>8</b></a></li>
-                        <li><tt>HTTP-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>8</b></a></li>
-                        <li><tt>Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>10.5</b></a></li>
-                        <li><tt>Max-Forwards</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>10.6</b></a></li>
+                        <li><tt>From</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>9.4</b></a></li>
+                        <li><tt>GMT</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>8.1</b></a></li>
+                        <li><tt>hour</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>8.1</b></a></li>
+                        <li><tt>HTTP-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>8.1</b></a></li>
+                        <li><tt>Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>9.5</b></a></li>
+                        <li><tt>Max-Forwards</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>9.6</b></a></li>
                         <li><tt>method</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
-                        <li><tt>minute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>8</b></a></li>
-                        <li><tt>month</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>8</b></a></li>
-                        <li><tt>obs-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>8</b></a></li>
-                        <li><tt>product</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>9</b></a></li>
-                        <li><tt>product-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>9</b></a></li>
+                        <li><tt>minute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>8.1</b></a></li>
+                        <li><tt>month</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>8.1</b></a></li>
+                        <li><tt>obs-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>8.1</b></a></li>
+                        <li><tt>product</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>8.2</b></a></li>
+                        <li><tt>product-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>8.2</b></a></li>
                         <li><tt>reason-phrase</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>4</b></a></li>
-                        <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>10.7</b></a></li>
-                        <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>10.8</b></a></li>
-                        <li><tt>rfc1123-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>8</b></a></li>
-                        <li><tt>rfc850-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>8</b></a></li>
-                        <li><tt>second</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>8</b></a></li>
-                        <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>10.9</b></a></li>
+                        <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>9.7</b></a></li>
+                        <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>9.8</b></a></li>
+                        <li><tt>rfc1123-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>8.1</b></a></li>
+                        <li><tt>rfc850-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>8.1</b></a></li>
+                        <li><tt>second</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>8.1</b></a></li>
+                        <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>9.9</b></a></li>
                         <li><tt>status-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>4</b></a></li>
-                        <li><tt>time-of-day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>8</b></a></li>
-                        <li><tt>User-Agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>10.10</b></a></li>
-                        <li><tt>year</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>8</b></a></li>
+                        <li><tt>time-of-day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>8.1</b></a></li>
+                        <li><tt>User-Agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>9.10</b></a></li>
+                        <li><tt>year</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>8.1</b></a></li>
                      </ul>
                   </li>
@@ -3600 +3603 @@
             </li>
             <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
-                  <li>HEAD method&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">2.1</a>, <a href="#rfc.iref.h.1"><b>6.4</b></a>, <a href="#rfc.xref.HEAD.2">11.1</a></li>
+                  <li>HEAD method&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">2.1</a>, <a href="#rfc.iref.h.1"><b>6.4</b></a>, <a href="#rfc.xref.HEAD.2">10.1</a></li>
                   <li>Header Fields&nbsp;&nbsp;
                      <ul>
-                        <li>Allow&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.h.2"><b>10.1</b></a>, <a href="#rfc.xref.header.allow.3">11.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li>
-                        <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.3"><b>10.2</b></a>, <a href="#rfc.xref.header.date.2">11.3</a></li>
-                        <li>Expect&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">7.4.14</a>, <a href="#rfc.iref.h.4"><b>10.3</b></a>, <a href="#rfc.xref.header.expect.3">11.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li>
-                        <li>From&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.5"><b>10.4</b></a>, <a href="#rfc.xref.header.from.2">11.3</a></li>
-                        <li>Location&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc.xref.header.location.3">7.3</a>, <a href="#rfc.iref.h.6"><b>10.5</b></a>, <a href="#rfc.xref.header.location.4">11.3</a>, <a href="#rfc.xref.header.location.5">A</a></li>
-                        <li>Max-Forwards&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">3.2</a>, <a href="#rfc.xref.header.max-forwards.2">6.2</a>, <a href="#rfc.xref.header.max-forwards.3">6.8</a>, <a href="#rfc.iref.h.7"><b>10.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li>
-                        <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.8"><b>10.7</b></a>, <a href="#rfc.xref.header.referer.2">11.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li>
-                        <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">7.5.4</a>, <a href="#rfc.iref.h.9"><b>10.8</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3</a></li>
-                        <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.10"><b>10.9</b></a>, <a href="#rfc.xref.header.server.2">11.3</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">A</a></li>
-                        <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.h.11"><b>10.10</b></a>, <a href="#rfc.xref.header.user-agent.2">11.3</a>, <a href="#rfc.xref.header.user-agent.3">12.1</a></li>
+                        <li>Allow&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">2</a>, <a href="#rfc.xref.header.allow.2">3.3</a>, <a href="#rfc.iref.h.2"><b>9.1</b></a>, <a href="#rfc.xref.header.allow.3">10.3</a>, <a href="#rfc.xref.header.allow.4">A</a></li>
+                        <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">3.3</a>, <a href="#rfc.iref.h.3"><b>9.2</b></a>, <a href="#rfc.xref.header.date.2">10.3</a></li>
+                        <li>Expect&nbsp;&nbsp;<a href="#rfc.xref.header.expect.1">3.2</a>, <a href="#rfc.xref.header.expect.2">7.4.14</a>, <a href="#rfc.iref.h.4"><b>9.3</b></a>, <a href="#rfc.xref.header.expect.3">10.3</a>, <a href="#rfc.xref.header.expect.4">A</a></li>
+                        <li>From&nbsp;&nbsp;<a href="#rfc.xref.header.from.1">3.2</a>, <a href="#rfc.iref.h.5"><b>9.4</b></a>, <a href="#rfc.xref.header.from.2">10.3</a></li>
+                        <li>Location&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc.xref.header.location.3">7.3</a>, <a href="#rfc.iref.h.6"><b>9.5</b></a>, <a href="#rfc.xref.header.location.4">10.3</a>, <a href="#rfc.xref.header.location.5">A</a></li>
+                        <li>Max-Forwards&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">3.2</a>, <a href="#rfc.xref.header.max-forwards.2">6.2</a>, <a href="#rfc.xref.header.max-forwards.3">6.8</a>, <a href="#rfc.iref.h.7"><b>9.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li>
+                        <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.h.8"><b>9.7</b></a>, <a href="#rfc.xref.header.referer.2">10.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li>
+                        <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">7.5.4</a>, <a href="#rfc.iref.h.9"><b>9.8</b></a>, <a href="#rfc.xref.header.retry-after.3">10.3</a></li>
+                        <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.h.10"><b>9.9</b></a>, <a href="#rfc.xref.header.server.2">10.3</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">A</a></li>
+                        <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.h.11"><b>9.10</b></a>, <a href="#rfc.xref.header.user-agent.2">10.3</a>, <a href="#rfc.xref.header.user-agent.3">11.1</a></li>
                      </ul>
                   </li>
@@ -3622 +3625 @@
             </li>
             <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul>
-                  <li>Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc.xref.header.location.3">7.3</a>, <a href="#rfc.iref.l.1"><b>10.5</b></a>, <a href="#rfc.xref.header.location.4">11.3</a>, <a href="#rfc.xref.header.location.5">A</a></li>
+                  <li>Location header field&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">3.3</a>, <a href="#rfc.xref.header.location.2">6.5</a>, <a href="#rfc.xref.header.location.3">7.3</a>, <a href="#rfc.iref.l.1"><b>9.5</b></a>, <a href="#rfc.xref.header.location.4">10.3</a>, <a href="#rfc.xref.header.location.5">A</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
-                  <li>Max-Forwards header field&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">3.2</a>, <a href="#rfc.xref.header.max-forwards.2">6.2</a>, <a href="#rfc.xref.header.max-forwards.3">6.8</a>, <a href="#rfc.iref.m.9"><b>10.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">11.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li>
+                  <li>Max-Forwards header field&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">3.2</a>, <a href="#rfc.xref.header.max-forwards.2">6.2</a>, <a href="#rfc.xref.header.max-forwards.3">6.8</a>, <a href="#rfc.iref.m.9"><b>9.6</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3</a>, <a href="#rfc.xref.header.max-forwards.5">A</a></li>
                   <li>Methods&nbsp;&nbsp;
                      <ul>
-                        <li>CONNECT&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">2.1</a>, <a href="#rfc.iref.m.8"><b>6.9</b></a>, <a href="#rfc.xref.CONNECT.2">11.1</a>, <a href="#rfc.xref.CONNECT.3">A</a></li>
-                        <li>DELETE&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">2.1</a>, <a href="#rfc.iref.m.6"><b>6.7</b></a>, <a href="#rfc.xref.DELETE.2">11.1</a></li>
-                        <li>GET&nbsp;&nbsp;<a href="#rfc.xref.GET.1">2.1</a>, <a href="#rfc.iref.m.2"><b>6.3</b></a>, <a href="#rfc.xref.GET.2">11.1</a></li>
-                        <li>HEAD&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">2.1</a>, <a href="#rfc.iref.m.3"><b>6.4</b></a>, <a href="#rfc.xref.HEAD.2">11.1</a></li>
-                        <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">2.1</a>, <a href="#rfc.iref.m.1"><b>6.2</b></a>, <a href="#rfc.xref.OPTIONS.2">10.6</a>, <a href="#rfc.xref.OPTIONS.3">11.1</a></li>
-                        <li>POST&nbsp;&nbsp;<a href="#rfc.xref.POST.1">2.1</a>, <a href="#rfc.iref.m.4"><b>6.5</b></a>, <a href="#rfc.xref.POST.2">11.1</a>, <a href="#rfc.xref.POST.3">A</a></li>
-                        <li>PUT&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.m.5"><b>6.6</b></a>, <a href="#rfc.xref.PUT.2">11.1</a>, <a href="#rfc.xref.PUT.3">A</a></li>
-                        <li>TRACE&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">2.1</a>, <a href="#rfc.iref.m.7"><b>6.8</b></a>, <a href="#rfc.xref.TRACE.2">10.6</a>, <a href="#rfc.xref.TRACE.3">11.1</a>, <a href="#rfc.xref.TRACE.4">12.1</a></li>
+                        <li>CONNECT&nbsp;&nbsp;<a href="#rfc.xref.CONNECT.1">2.1</a>, <a href="#rfc.iref.m.8"><b>6.9</b></a>, <a href="#rfc.xref.CONNECT.2">10.1</a>, <a href="#rfc.xref.CONNECT.3">A</a></li>
+                        <li>DELETE&nbsp;&nbsp;<a href="#rfc.xref.DELETE.1">2.1</a>, <a href="#rfc.iref.m.6"><b>6.7</b></a>, <a href="#rfc.xref.DELETE.2">10.1</a></li>
+                        <li>GET&nbsp;&nbsp;<a href="#rfc.xref.GET.1">2.1</a>, <a href="#rfc.iref.m.2"><b>6.3</b></a>, <a href="#rfc.xref.GET.2">10.1</a></li>
+                        <li>HEAD&nbsp;&nbsp;<a href="#rfc.xref.HEAD.1">2.1</a>, <a href="#rfc.iref.m.3"><b>6.4</b></a>, <a href="#rfc.xref.HEAD.2">10.1</a></li>
+                        <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">2.1</a>, <a href="#rfc.iref.m.1"><b>6.2</b></a>, <a href="#rfc.xref.OPTIONS.2">9.6</a>, <a href="#rfc.xref.OPTIONS.3">10.1</a></li>
+                        <li>POST&nbsp;&nbsp;<a href="#rfc.xref.POST.1">2.1</a>, <a href="#rfc.iref.m.4"><b>6.5</b></a>, <a href="#rfc.xref.POST.2">10.1</a>, <a href="#rfc.xref.POST.3">A</a></li>
+                        <li>PUT&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.m.5"><b>6.6</b></a>, <a href="#rfc.xref.PUT.2">10.1</a>, <a href="#rfc.xref.PUT.3">A</a></li>
+                        <li>TRACE&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">2.1</a>, <a href="#rfc.iref.m.7"><b>6.8</b></a>, <a href="#rfc.xref.TRACE.2">9.6</a>, <a href="#rfc.xref.TRACE.3">10.1</a>, <a href="#rfc.xref.TRACE.4">11.1</a></li>
                      </ul>
                   </li>
@@ -3642 +3645 @@
             </li>
             <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul>
-                  <li>OPTIONS method&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">2.1</a>, <a href="#rfc.iref.o.1"><b>6.2</b></a>, <a href="#rfc.xref.OPTIONS.2">10.6</a>, <a href="#rfc.xref.OPTIONS.3">11.1</a></li>
+                  <li>OPTIONS method&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">2.1</a>, <a href="#rfc.iref.o.1"><b>6.2</b></a>, <a href="#rfc.xref.OPTIONS.2">9.6</a>, <a href="#rfc.xref.OPTIONS.3">10.1</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
-                  <li><em>Part1</em>&nbsp;&nbsp;<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">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a>, <a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.1</a>, <a href="#rfc.xref.Part1.10">1.2.1</a>, <a href="#rfc.xref.Part1.11">1.2.2</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a>, <a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.17">3</a>, <a href="#rfc.xref.Part1.18">3.1</a>, <a href="#rfc.xref.Part1.19">3.1</a>, <a href="#rfc.xref.Part1.20">3.1</a>, <a href="#rfc.xref.Part1.21">3.1</a>, <a href="#rfc.xref.Part1.22">3.1</a>, <a href="#rfc.xref.Part1.23">3.2</a>, <a href="#rfc.xref.Part1.24">3.2</a>, <a href="#rfc.xref.Part1.25">3.3</a>, <a href="#rfc.xref.Part1.26">5</a>, <a href="#rfc.xref.Part1.27">5.1</a>, <a href="#rfc.xref.Part1.28">6.2</a>, <a href="#rfc.xref.Part1.29">6.8</a>, <a href="#rfc.xref.Part1.30">6.8</a>, <a href="#rfc.xref.Part1.31">6.9</a>, <a href="#rfc.xref.Part1.32">7.1.1</a>, <a href="#rfc.xref.Part1.33">7.1.2</a>, <a href="#rfc.xref.Part1.34">7.2.4</a>, <a href="#rfc.xref.Part1.35">7.2.6</a>, <a href="#rfc.xref.Part1.36">7.4.15</a>, <a href="#rfc.xref.Part1.37">7.5.6</a>, <a href="#rfc.xref.Part1.38">10.3</a>, <a href="#rfc.xref.Part1.39">10.9</a>, <a href="#rfc.xref.Part1.40">10.9</a>, <a href="#rfc.xref.Part1.41">10.10</a>, <a href="#rfc.xref.Part1.42">13</a>, <a href="#Part1"><b>14.1</b></a>, <a href="#rfc.xref.Part1.43">A</a><ul>
+                  <li><em>Part1</em>&nbsp;&nbsp;<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">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a>, <a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.1</a>, <a href="#rfc.xref.Part1.10">1.2.1</a>, <a href="#rfc.xref.Part1.11">1.2.2</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a>, <a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.16">2.2.1</a>, <a href="#rfc.xref.Part1.17">3</a>, <a href="#rfc.xref.Part1.18">3.1</a>, <a href="#rfc.xref.Part1.19">3.1</a>, <a href="#rfc.xref.Part1.20">3.1</a>, <a href="#rfc.xref.Part1.21">3.1</a>, <a href="#rfc.xref.Part1.22">3.1</a>, <a href="#rfc.xref.Part1.23">3.2</a>, <a href="#rfc.xref.Part1.24">3.2</a>, <a href="#rfc.xref.Part1.25">3.3</a>, <a href="#rfc.xref.Part1.26">5</a>, <a href="#rfc.xref.Part1.27">5.1</a>, <a href="#rfc.xref.Part1.28">6.2</a>, <a href="#rfc.xref.Part1.29">6.8</a>, <a href="#rfc.xref.Part1.30">6.8</a>, <a href="#rfc.xref.Part1.31">6.9</a>, <a href="#rfc.xref.Part1.32">7.1.1</a>, <a href="#rfc.xref.Part1.33">7.1.2</a>, <a href="#rfc.xref.Part1.34">7.2.4</a>, <a href="#rfc.xref.Part1.35">7.2.6</a>, <a href="#rfc.xref.Part1.36">7.4.15</a>, <a href="#rfc.xref.Part1.37">7.5.6</a>, <a href="#rfc.xref.Part1.38">9.3</a>, <a href="#rfc.xref.Part1.39">9.9</a>, <a href="#rfc.xref.Part1.40">9.9</a>, <a href="#rfc.xref.Part1.41">9.10</a>, <a href="#rfc.xref.Part1.42">12</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.43">A</a><ul>
                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
                         <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
@@ -3653 +3656 @@
                         <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">1.2.2</a>, <a href="#rfc.xref.Part1.13">1.2.2</a>, <a href="#rfc.xref.Part1.14">1.2.2</a></li>
                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a></li>
-                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">3</a>, <a href="#rfc.xref.Part1.20">3.1</a>, <a href="#rfc.xref.Part1.39">10.9</a>, <a href="#rfc.xref.Part1.41">10.10</a></li>
+                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">3</a>, <a href="#rfc.xref.Part1.20">3.1</a>, <a href="#rfc.xref.Part1.39">9.9</a>, <a href="#rfc.xref.Part1.41">9.10</a></li>
                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.2.1</a>, <a href="#rfc.xref.Part1.9">1.2.1</a>, <a href="#rfc.xref.Part1.10">1.2.1</a>, <a href="#rfc.xref.Part1.12">1.2.2</a>, <a href="#rfc.xref.Part1.19">3.1</a></li>
                         <li><em>Section 3.2.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">3.1</a></li>
@@ -3663 +3666 @@
                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">2</a>, <a href="#rfc.xref.Part1.25">3.3</a>, <a href="#rfc.xref.Part1.27">5.1</a></li>
                         <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">3.1</a></li>
-                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">6.8</a>, <a href="#rfc.xref.Part1.40">10.9</a>, <a href="#rfc.xref.Part1.43">A</a></li>
-                        <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">7.1.1</a>, <a href="#rfc.xref.Part1.38">10.3</a></li>
+                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">6.8</a>, <a href="#rfc.xref.Part1.40">9.9</a>, <a href="#rfc.xref.Part1.43">A</a></li>
+                        <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">7.1.1</a>, <a href="#rfc.xref.Part1.38">9.3</a></li>
                         <li><em>Section 6.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.33">7.1.2</a>, <a href="#rfc.xref.Part1.36">7.4.15</a></li>
                         <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.30">6.8</a></li>
-                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">13</a></li>
+                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">12</a></li>
                      </ul>
                   </li>
-                  <li><em>Part3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">3.1</a>, <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.3">3.2</a>, <a href="#rfc.xref.Part3.4">3.2</a>, <a href="#rfc.xref.Part3.5">3.2</a>, <a href="#rfc.xref.Part3.6">3.2</a>, <a href="#rfc.xref.Part3.7">5</a>, <a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.9">7</a>, <a href="#rfc.xref.Part3.10">7.3</a>, <a href="#rfc.xref.Part3.11">7.3.1</a>, <a href="#rfc.xref.Part3.12">7.4.6</a>, <a href="#rfc.xref.Part3.13">10.5</a>, <a href="#Part3"><b>14.1</b></a><ul>
+                  <li><em>Part3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">3.1</a>, <a href="#rfc.xref.Part3.2">3.1</a>, <a href="#rfc.xref.Part3.3">3.2</a>, <a href="#rfc.xref.Part3.4">3.2</a>, <a href="#rfc.xref.Part3.5">3.2</a>, <a href="#rfc.xref.Part3.6">3.2</a>, <a href="#rfc.xref.Part3.7">5</a>, <a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.9">7</a>, <a href="#rfc.xref.Part3.10">7.3</a>, <a href="#rfc.xref.Part3.11">7.3.1</a>, <a href="#rfc.xref.Part3.12">7.4.6</a>, <a href="#rfc.xref.Part3.13">9.5</a>, <a href="#Part3"><b>13.1</b></a><ul>
                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.2">3.1</a></li>
                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.11">7.3.1</a></li>
@@ -3679 +3682 @@
                         <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.5">3.2</a></li>
                         <li><em>Section 6.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.6">3.2</a></li>
-                        <li><em>Section 6.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.13">10.5</a></li>
+                        <li><em>Section 6.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.8">6.5</a>, <a href="#rfc.xref.Part3.13">9.5</a></li>
                         <li><em>Section 6.8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">3.1</a>, <a href="#rfc.xref.Part3.9">7</a></li>
                      </ul>
                   </li>
-                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.4">3.2</a>, <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.6">4.1</a>, <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.8">4.1</a>, <a href="#rfc.xref.Part4.9">7.2.2</a>, <a href="#rfc.xref.Part4.10">7.3</a>, <a href="#Part4"><b>14.1</b></a>, <a href="#rfc.xref.Part4.11">C.2</a><ul>
+                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.4">3.2</a>, <a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.6">4.1</a>, <a href="#rfc.xref.Part4.7">4.1</a>, <a href="#rfc.xref.Part4.8">4.1</a>, <a href="#rfc.xref.Part4.9">7.2.2</a>, <a href="#rfc.xref.Part4.10">7.3</a>, <a href="#Part4"><b>13.1</b></a>, <a href="#rfc.xref.Part4.11">C.2</a><ul>
                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.5">3.3</a>, <a href="#rfc.xref.Part4.9">7.2.2</a></li>
                         <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">3.2</a></li>
@@ -3694 +3697 @@
                      </ul>
                   </li>
-                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.2</a>, <a href="#rfc.xref.Part5.2">3.2</a>, <a href="#rfc.xref.Part5.3">3.3</a>, <a href="#rfc.xref.Part5.4">4.1</a>, <a href="#rfc.xref.Part5.5">4.1</a>, <a href="#rfc.xref.Part5.6">4.1</a>, <a href="#rfc.xref.Part5.7">6.3</a>, <a href="#Part5"><b>14.1</b></a><ul>
+                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.2</a>, <a href="#rfc.xref.Part5.2">3.2</a>, <a href="#rfc.xref.Part5.3">3.3</a>, <a href="#rfc.xref.Part5.4">4.1</a>, <a href="#rfc.xref.Part5.5">4.1</a>, <a href="#rfc.xref.Part5.6">4.1</a>, <a href="#rfc.xref.Part5.7">6.3</a>, <a href="#Part5"><b>13.1</b></a><ul>
                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.4">4.1</a></li>
                         <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.5">4.1</a></li>
@@ -3703 +3706 @@
                      </ul>
                   </li>
-                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">3.1</a>, <a href="#rfc.xref.Part6.3">3.3</a>, <a href="#rfc.xref.Part6.4">3.3</a>, <a href="#rfc.xref.Part6.5">4.2.1</a>, <a href="#rfc.xref.Part6.6">6.3</a>, <a href="#rfc.xref.Part6.7">6.4</a>, <a href="#rfc.xref.Part6.8">6.5</a>, <a href="#rfc.xref.Part6.9">6.6</a>, <a href="#rfc.xref.Part6.10">6.7</a>, <a href="#rfc.xref.Part6.11">7.2.1</a>, <a href="#rfc.xref.Part6.12">7.2.4</a>, <a href="#rfc.xref.Part6.13">7.2.4</a>, <a href="#rfc.xref.Part6.14">7.2.4</a>, <a href="#rfc.xref.Part6.15">7.3.1</a>, <a href="#rfc.xref.Part6.16">7.3.2</a>, <a href="#rfc.xref.Part6.17">7.4.9</a>, <a href="#Part6"><b>14.1</b></a><ul>
+                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">2.2.1</a>, <a href="#rfc.xref.Part6.2">3.1</a>, <a href="#rfc.xref.Part6.3">3.3</a>, <a href="#rfc.xref.Part6.4">3.3</a>, <a href="#rfc.xref.Part6.5">4.2.1</a>, <a href="#rfc.xref.Part6.6">6.3</a>, <a href="#rfc.xref.Part6.7">6.4</a>, <a href="#rfc.xref.Part6.8">6.5</a>, <a href="#rfc.xref.Part6.9">6.6</a>, <a href="#rfc.xref.Part6.10">6.7</a>, <a href="#rfc.xref.Part6.11">7.2.1</a>, <a href="#rfc.xref.Part6.12">7.2.4</a>, <a href="#rfc.xref.Part6.13">7.2.4</a>, <a href="#rfc.xref.Part6.14">7.2.4</a>, <a href="#rfc.xref.Part6.15">7.3.1</a>, <a href="#rfc.xref.Part6.16">7.3.2</a>, <a href="#rfc.xref.Part6.17">7.4.9</a>, <a href="#Part6"><b>13.1</b></a><ul>
                         <li><em>Section 2.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.8">6.5</a></li>
                         <li><em>Section 2.3.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.11">7.2.1</a>, <a href="#rfc.xref.Part6.14">7.2.4</a>, <a href="#rfc.xref.Part6.15">7.3.1</a>, <a href="#rfc.xref.Part6.16">7.3.2</a>, <a href="#rfc.xref.Part6.17">7.4.9</a></li>
@@ -3714 +3717 @@
                      </ul>
                   </li>
-                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3.2</a>, <a href="#rfc.xref.Part7.2">3.2</a>, <a href="#rfc.xref.Part7.3">3.3</a>, <a href="#rfc.xref.Part7.4">3.3</a>, <a href="#rfc.xref.Part7.5">4.1</a>, <a href="#rfc.xref.Part7.6">4.1</a>, <a href="#rfc.xref.Part7.7">4.1</a>, <a href="#Part7"><b>14.1</b></a><ul>
+                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">3.2</a>, <a href="#rfc.xref.Part7.2">3.2</a>, <a href="#rfc.xref.Part7.3">3.3</a>, <a href="#rfc.xref.Part7.4">3.3</a>, <a href="#rfc.xref.Part7.5">4.1</a>, <a href="#rfc.xref.Part7.6">4.1</a>, <a href="#rfc.xref.Part7.7">4.1</a>, <a href="#Part7"><b>13.1</b></a><ul>
                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.5">4.1</a></li>
                         <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.6">4.1</a></li>
@@ -3724 +3727 @@
                      </ul>
                   </li>
-                  <li>POST method&nbsp;&nbsp;<a href="#rfc.xref.POST.1">2.1</a>, <a href="#rfc.iref.p.1"><b>6.5</b></a>, <a href="#rfc.xref.POST.2">11.1</a>, <a href="#rfc.xref.POST.3">A</a></li>
-                  <li>PUT method&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.p.2"><b>6.6</b></a>, <a href="#rfc.xref.PUT.2">11.1</a>, <a href="#rfc.xref.PUT.3">A</a></li>
+                  <li>POST method&nbsp;&nbsp;<a href="#rfc.xref.POST.1">2.1</a>, <a href="#rfc.iref.p.1"><b>6.5</b></a>, <a href="#rfc.xref.POST.2">10.1</a>, <a href="#rfc.xref.POST.3">A</a></li>
+                  <li>PUT method&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.p.2"><b>6.6</b></a>, <a href="#rfc.xref.PUT.2">10.1</a>, <a href="#rfc.xref.PUT.3">A</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
-                  <li>Referer header field&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.1"><b>10.7</b></a>, <a href="#rfc.xref.header.referer.2">11.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li>
-                  <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">7.5.4</a>, <a href="#rfc.iref.r.2"><b>10.8</b></a>, <a href="#rfc.xref.header.retry-after.3">11.3</a></li>
-                  <li><em>RFC1123</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.1">8</a>, <a href="#rfc.xref.RFC1123.2">8</a>, <a href="#RFC1123"><b>14.2</b></a><ul>
-                        <li><em>Section 5.2.14</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.2">8</a></li>
+                  <li>Referer header field&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">3.2</a>, <a href="#rfc.iref.r.1"><b>9.7</b></a>, <a href="#rfc.xref.header.referer.2">10.3</a>, <a href="#rfc.xref.header.referer.3">A</a></li>
+                  <li>Retry-After header field&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">3.3</a>, <a href="#rfc.xref.header.retry-after.2">7.5.4</a>, <a href="#rfc.iref.r.2"><b>9.8</b></a>, <a href="#rfc.xref.header.retry-after.3">10.3</a></li>
+                  <li><em>RFC1123</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.1">8.1</a>, <a href="#rfc.xref.RFC1123.2">8.1</a>, <a href="#RFC1123"><b>13.2</b></a><ul>
+                        <li><em>Section 5.2.14</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.2">8.1</a></li>
                      </ul>
                   </li>
-                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">7.3</a>, <a href="#RFC1945"><b>14.2</b></a><ul>
+                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">7.3</a>, <a href="#RFC1945"><b>13.2</b></a><ul>
                         <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">7.3</a></li>
                      </ul>
                   </li>
-                  <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">7.3</a>, <a href="#rfc.xref.RFC2068.2">7.3</a>, <a href="#RFC2068"><b>14.2</b></a><ul>
+                  <li><em>RFC2068</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">7.3</a>, <a href="#rfc.xref.RFC2068.2">7.3</a>, <a href="#RFC2068"><b>13.2</b></a><ul>
                         <li><em>Section 10.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.2">7.3</a></li>
                         <li><em>Section 10.3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2068.1">7.3</a></li>
                      </ul>
                   </li>
-                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>14.1</b></a></li>
-                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">7.3</a>, <a href="#RFC2616"><b>14.2</b></a>, <a href="#rfc.xref.RFC2616.3">C.1</a><ul>
+                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>13.1</b></a></li>
+                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">7.3</a>, <a href="#RFC2616"><b>13.2</b></a>, <a href="#rfc.xref.RFC2616.3">C.1</a><ul>
                         <li><em>Section 10.3.8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">7.3</a></li>
                      </ul>
                   </li>
-                  <li><em>RFC2817</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">11.2</a>, <a href="#RFC2817"><b>14.2</b></a>, <a href="#rfc.xref.RFC2817.2">A</a>, <a href="#rfc.xref.RFC2817.3">A</a>, <a href="#rfc.xref.RFC2817.4">A</a><ul>
-                        <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">11.2</a>, <a href="#rfc.xref.RFC2817.2">A</a></li>
+                  <li><em>RFC2817</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">10.2</a>, <a href="#RFC2817"><b>13.2</b></a>, <a href="#rfc.xref.RFC2817.2">A</a>, <a href="#rfc.xref.RFC2817.3">A</a>, <a href="#rfc.xref.RFC2817.4">A</a><ul>
+                        <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">10.2</a>, <a href="#rfc.xref.RFC2817.2">A</a></li>
                      </ul>
                   </li>
-                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">3.1</a>, <a href="#rfc.xref.RFC3864.2">3.1</a>, <a href="#rfc.xref.RFC3864.3">11.3</a>, <a href="#RFC3864"><b>14.2</b></a><ul>
+                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">3.1</a>, <a href="#rfc.xref.RFC3864.2">3.1</a>, <a href="#rfc.xref.RFC3864.3">10.3</a>, <a href="#RFC3864"><b>13.2</b></a><ul>
                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.2">3.1</a></li>
                      </ul>
                   </li>
-                  <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">10.5</a>, <a href="#rfc.xref.RFC3986.2">10.5</a>, <a href="#RFC3986"><b>14.1</b></a><ul>
-                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">10.5</a></li>
-                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.2">10.5</a></li>
+                  <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">9.5</a>, <a href="#rfc.xref.RFC3986.2">9.5</a>, <a href="#RFC3986"><b>13.1</b></a><ul>
+                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">9.5</a></li>
+                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.2">9.5</a></li>
                      </ul>
                   </li>
-                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a>, <a href="#RFC5226"><b>14.2</b></a><ul>
+                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a>, <a href="#RFC5226"><b>13.2</b></a><ul>
                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.2</a>, <a href="#rfc.xref.RFC5226.2">4.2</a></li>
                      </ul>
                   </li>
-                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#rfc.xref.RFC5234.3">3.1</a>, <a href="#RFC5234"><b>14.1</b></a><ul>
+                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#rfc.xref.RFC5234.3">3.1</a>, <a href="#RFC5234"><b>13.1</b></a><ul>
                         <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
                      </ul>
                   </li>
-                  <li><em>RFC5322</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">8</a>, <a href="#rfc.xref.RFC5322.2">10.2</a>, <a href="#rfc.xref.RFC5322.3">10.4</a>, <a href="#rfc.xref.RFC5322.4">10.4</a>, <a href="#RFC5322"><b>14.2</b></a><ul>
-                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">8</a></li>
-                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.3">10.4</a>, <a href="#rfc.xref.RFC5322.4">10.4</a></li>
-                        <li><em>Section 3.6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.2">10.2</a></li>
+                  <li><em>RFC5322</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">8.1</a>, <a href="#rfc.xref.RFC5322.2">9.2</a>, <a href="#rfc.xref.RFC5322.3">9.4</a>, <a href="#rfc.xref.RFC5322.4">9.4</a>, <a href="#RFC5322"><b>13.2</b></a><ul>
+                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.1">8.1</a></li>
+                        <li><em>Section 3.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.3">9.4</a>, <a href="#rfc.xref.RFC5322.4">9.4</a></li>
+                        <li><em>Section 3.6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.2">9.2</a></li>
                      </ul>
                   </li>
-                  <li><em>RFC5789</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5789.1">6.6</a>, <a href="#RFC5789"><b>14.2</b></a></li>
-                  <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#RFC5987"><b>14.2</b></a></li>
+                  <li><em>RFC5789</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5789.1">6.6</a>, <a href="#RFC5789"><b>13.2</b></a></li>
+                  <li><em>RFC5987</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5987.1">3.1</a>, <a href="#RFC5987"><b>13.2</b></a></li>
                </ul>
             </li>
             <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
                   <li>Safe Methods&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>6.1.1</b></a></li>
-                  <li>Server header field&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.38"><b>10.9</b></a>, <a href="#rfc.xref.header.server.2">11.3</a>, <a href="#rfc.xref.header.server.3">12.1</a>, <a href="#rfc.xref.header.server.4">A</a></li>
+                  <li>Server header field&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">3.3</a>, <a href="#rfc.iref.s.38"><b>9.9</b></a>, <a href="#rfc.xref.header.server.2">10.3</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">A</a></li>
                   <li>Status Codes&nbsp;&nbsp;
                      <ul>
-                        <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.2"><b>7.1.1</b></a>, <a href="#rfc.xref.status.100.2">11.2</a></li>
-                        <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.3"><b>7.1.2</b></a>, <a href="#rfc.xref.status.101.2">11.2</a></li>
-                        <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.4"><b>7.2.1</b></a>, <a href="#rfc.xref.status.200.2">11.2</a></li>
-                        <li>201 Created&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.5"><b>7.2.2</b></a>, <a href="#rfc.xref.status.201.2">11.2</a></li>
-                        <li>202 Accepted&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.6"><b>7.2.3</b></a>, <a href="#rfc.xref.status.202.2">11.2</a></li>
-                        <li>203 Non-Authoritative Information&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.7"><b>7.2.4</b></a>, <a href="#rfc.xref.status.203.2">11.2</a>, <a href="#rfc.xref.status.203.3">A</a></li>
-                        <li>204 No Content&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.8"><b>7.2.5</b></a>, <a href="#rfc.xref.status.204.2">11.2</a></li>
-                        <li>205 Reset Content&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.9"><b>7.2.6</b></a>, <a href="#rfc.xref.status.205.2">11.2</a></li>
-                        <li>300 Multiple Choices&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.10"><b>7.3.1</b></a>, <a href="#rfc.xref.status.300.2">11.2</a></li>
-                        <li>301 Moved Permanently&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.11"><b>7.3.2</b></a>, <a href="#rfc.xref.status.301.2">11.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>
-                        <li>302 Found&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.12"><b>7.3.3</b></a>, <a href="#rfc.xref.status.302.2">11.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>
-                        <li>303 See Other&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.13"><b>7.3.4</b></a>, <a href="#rfc.xref.status.303.2">11.2</a></li>
-                        <li>305 Use Proxy&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.14"><b>7.3.5</b></a>, <a href="#rfc.xref.status.305.2">11.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>
-                        <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.15"><b>7.3.6</b></a>, <a href="#rfc.xref.status.306.1">11.2</a></li>
-                        <li>307 Temporary Redirect&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.16"><b>7.3.7</b></a>, <a href="#rfc.xref.status.307.2">11.2</a>, <a href="#rfc.xref.status.307.3">A</a></li>
-                        <li>400 Bad Request&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.17"><b>7.4.1</b></a>, <a href="#rfc.xref.status.400.2">11.2</a></li>
-                        <li>402 Payment Required&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.18"><b>7.4.2</b></a>, <a href="#rfc.xref.status.402.2">11.2</a></li>
-                        <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.19"><b>7.4.3</b></a>, <a href="#rfc.xref.status.403.2">11.2</a></li>
-                        <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.20"><b>7.4.4</b></a>, <a href="#rfc.xref.status.404.2">11.2</a></li>
-                        <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.21"><b>7.4.5</b></a>, <a href="#rfc.xref.status.405.2">11.2</a></li>
-                        <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.22"><b>7.4.6</b></a>, <a href="#rfc.xref.status.406.2">11.2</a></li>
-                        <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.23"><b>7.4.7</b></a>, <a href="#rfc.xref.status.408.2">11.2</a></li>
-                        <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.24"><b>7.4.8</b></a>, <a href="#rfc.xref.status.409.2">11.2</a></li>
-                        <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.25"><b>7.4.9</b></a>, <a href="#rfc.xref.status.410.2">11.2</a></li>
-                        <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.26"><b>7.4.10</b></a>, <a href="#rfc.xref.status.411.2">11.2</a></li>
-                        <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.27"><b>7.4.11</b></a>, <a href="#rfc.xref.status.413.2">11.2</a></li>
-                        <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.28"><b>7.4.12</b></a>, <a href="#rfc.xref.status.414.2">11.2</a></li>
-                        <li>415 Unsupported Media Type&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.29"><b>7.4.13</b></a>, <a href="#rfc.xref.status.415.2">11.2</a></li>
-                        <li>417 Expectation Failed&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.30"><b>7.4.14</b></a>, <a href="#rfc.xref.status.417.2">11.2</a></li>
-                        <li>426 Upgrade Required&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.31"><b>7.4.15</b></a>, <a href="#rfc.xref.status.426.2">11.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>
-                        <li>500 Internal Server Error&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.32"><b>7.5.1</b></a>, <a href="#rfc.xref.status.500.2">11.2</a></li>
-                        <li>501 Not Implemented&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.33"><b>7.5.2</b></a>, <a href="#rfc.xref.status.501.2">11.2</a></li>
-                        <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.34"><b>7.5.3</b></a>, <a href="#rfc.xref.status.502.2">11.2</a></li>
-                        <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.35"><b>7.5.4</b></a>, <a href="#rfc.xref.status.503.2">11.2</a></li>
-                        <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.36"><b>7.5.5</b></a>, <a href="#rfc.xref.status.504.2">11.2</a></li>
-                        <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.37"><b>7.5.6</b></a>, <a href="#rfc.xref.status.505.2">11.2</a></li>
+                        <li>100 Continue&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.s.2"><b>7.1.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li>
+                        <li>101 Switching Protocols&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.s.3"><b>7.1.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li>
+                        <li>200 OK&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.s.4"><b>7.2.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li>
+                        <li>201 Created&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.s.5"><b>7.2.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li>
+                        <li>202 Accepted&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.s.6"><b>7.2.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li>
+                        <li>203 Non-Authoritative Information&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.s.7"><b>7.2.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a>, <a href="#rfc.xref.status.203.3">A</a></li>
+                        <li>204 No Content&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.s.8"><b>7.2.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li>
+                        <li>205 Reset Content&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.s.9"><b>7.2.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li>
+                        <li>300 Multiple Choices&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.s.10"><b>7.3.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li>
+                        <li>301 Moved Permanently&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.s.11"><b>7.3.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>
+                        <li>302 Found&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.s.12"><b>7.3.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>
+                        <li>303 See Other&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.iref.s.13"><b>7.3.4</b></a>, <a href="#rfc.xref.status.303.2">10.2</a></li>
+                        <li>305 Use Proxy&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.s.14"><b>7.3.5</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>
+                        <li>306 (Unused)&nbsp;&nbsp;<a href="#rfc.iref.s.15"><b>7.3.6</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li>
+                        <li>307 Temporary Redirect&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.iref.s.16"><b>7.3.7</b></a>, <a href="#rfc.xref.status.307.2">10.2</a>, <a href="#rfc.xref.status.307.3">A</a></li>
+                        <li>400 Bad Request&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.s.17"><b>7.4.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li>
+                        <li>402 Payment Required&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.s.18"><b>7.4.2</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li>
+                        <li>403 Forbidden&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.s.19"><b>7.4.3</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li>
+                        <li>404 Not Found&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.s.20"><b>7.4.4</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li>
+                        <li>405 Method Not Allowed&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.s.21"><b>7.4.5</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li>
+                        <li>406 Not Acceptable&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.s.22"><b>7.4.6</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li>
+                        <li>408 Request Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.s.23"><b>7.4.7</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li>
+                        <li>409 Conflict&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.s.24"><b>7.4.8</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li>
+                        <li>410 Gone&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.s.25"><b>7.4.9</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li>
+                        <li>411 Length Required&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.s.26"><b>7.4.10</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li>
+                        <li>413 Request Representation Too Large&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.s.27"><b>7.4.11</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li>
+                        <li>414 URI Too Long&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.s.28"><b>7.4.12</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li>
+                        <li>415 Unsupported Media Type&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.s.29"><b>7.4.13</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li>
+                        <li>417 Expectation Failed&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.s.30"><b>7.4.14</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li>
+                        <li>426 Upgrade Required&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.s.31"><b>7.4.15</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>
+                        <li>500 Internal Server Error&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.s.32"><b>7.5.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li>
+                        <li>501 Not Implemented&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.s.33"><b>7.5.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li>
+                        <li>502 Bad Gateway&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.s.34"><b>7.5.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li>
+                        <li>503 Service Unavailable&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.s.35"><b>7.5.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li>
+                        <li>504 Gateway Timeout&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.s.36"><b>7.5.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li>
+                        <li>505 HTTP Version Not Supported&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.s.37"><b>7.5.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li>
                      </ul>
                   </li>
@@ -3826 +3829 @@
             </li>
             <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul>
-                  <li>TRACE method&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">2.1</a>, <a href="#rfc.iref.t.1"><b>6.8</b></a>, <a href="#rfc.xref.TRACE.2">10.6</a>, <a href="#rfc.xref.TRACE.3">11.1</a>, <a href="#rfc.xref.TRACE.4">12.1</a></li>
+                  <li>TRACE method&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">2.1</a>, <a href="#rfc.iref.t.1"><b>6.8</b></a>, <a href="#rfc.xref.TRACE.2">9.6</a>, <a href="#rfc.xref.TRACE.3">10.1</a>, <a href="#rfc.xref.TRACE.4">11.1</a></li>
                </ul>
             </li>
             <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul>
-                  <li>User-Agent header field&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.u.1"><b>10.10</b></a>, <a href="#rfc.xref.header.user-agent.2">11.3</a>, <a href="#rfc.xref.header.user-agent.3">12.1</a></li>
+                  <li>User-Agent header field&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.2</a>, <a href="#rfc.iref.u.1"><b>9.10</b></a>, <a href="#rfc.xref.header.user-agent.2">10.3</a>, <a href="#rfc.xref.header.user-agent.3">11.1</a></li>
                </ul>
             </li>