Ignore:
Timestamp:
16/07/12 14:30:03 (10 years ago)
Author:
julian.reschke@…
Message:

Move imported ABNF rules to appendix sections

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

Legend:

Unmodified
Added
Removed

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

    r1803 r1805  
    487487      <link rel="Appendix" title="B Additional Features" href="#rfc.section.B">
    488488      <link rel="Appendix" title="C Changes from RFC 2616" href="#rfc.section.C">
    489       <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
    490       <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
     489      <link rel="Appendix" title="D Imported ABNF" href="#rfc.section.D">
     490      <link rel="Appendix" title="E Collected ABNF" href="#rfc.section.E">
     491      <link rel="Appendix" title="F Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.F">
    491492      <link href="p1-messaging.html" rel="prev">
    492493      <link href="p3-payload.html" rel="next">
    … …  
    549550      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    550551      </p> 
    551       <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p2-semantics-19 and draft-ietf-httpbis-p3-payload-19">Appendix&nbsp;E.40</a>.
     552      <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p2-semantics-19 and draft-ietf-httpbis-p3-payload-19">Appendix&nbsp;F.40</a>.
    552553      </p>
    553554      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    … …  
    580581         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    581582               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
    582                <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
    583                      <li>1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    584                      <li>1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    585                   </ul>
    586                </li>
     583               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a></li>
    587584            </ul>
    588585         </li>
    … …  
    761758         <li>B.&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a></li>
    762759         <li>C.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    763          <li>D.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    764          <li>E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    765                <li>E.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.1">Since RFC 2616</a></li>
    766                <li>E.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
    767                <li>E.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.3">Since draft-ietf-httpbis-p3-payload-00</a></li>
    768                <li>E.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.4">Since draft-ietf-httpbis-p2-semantics-01</a></li>
    769                <li>E.5&nbsp;&nbsp;&nbsp;<a href="#rfc.section.E.5">Since draft-ietf-httpbis-p3-payload-01</a></li>
    770                <li>E.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
    771                <li>E.7&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li>
    772                <li>E.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
    773                <li>E.9&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li>
    774                <li>E.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
    775                <li>E.11&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li>
    776                <li>E.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
    777                <li>E.13&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li>
    778                <li>E.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li>
    779                <li>E.15&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li>
    780                <li>E.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li>
    781                <li>E.17&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li>
    782                <li>E.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></li>
    783                <li>E.19&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li>
    784                <li>E.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></li>
    785                <li>E.21&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li>
    786                <li>E.22&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></li>
    787                <li>E.23&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li>
    788                <li>E.24&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></li>
    789                <li>E.25&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li>
    790                <li>E.26&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></li>
    791                <li>E.27&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></li>
    792                <li>E.28&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></li>
    793                <li>E.29&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></li>
    794                <li>E.30&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></li>
    795                <li>E.31&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></li>
    796                <li>E.32&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></li>
    797                <li>E.33&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></li>
    798                <li>E.34&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></li>
    799                <li>E.35&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></li>
    800                <li>E.36&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></li>
    801                <li>E.37&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></li>
    802                <li>E.38&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></li>
    803                <li>E.39&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></li>
    804                <li>E.40&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19 and draft-ietf-httpbis-p3-payload-19</a></li>
     760         <li>D.&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
     761         <li>E.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     762         <li>F.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     763               <li>F.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.1">Since RFC 2616</a></li>
     764               <li>F.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
     765               <li>F.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.3">Since draft-ietf-httpbis-p3-payload-00</a></li>
     766               <li>F.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.4">Since draft-ietf-httpbis-p2-semantics-01</a></li>
     767               <li>F.5&nbsp;&nbsp;&nbsp;<a href="#rfc.section.F.5">Since draft-ietf-httpbis-p3-payload-01</a></li>
     768               <li>F.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
     769               <li>F.7&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></li>
     770               <li>F.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
     771               <li>F.9&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></li>
     772               <li>F.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
     773               <li>F.11&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></li>
     774               <li>F.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
     775               <li>F.13&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></li>
     776               <li>F.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li>
     777               <li>F.15&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></li>
     778               <li>F.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li>
     779               <li>F.17&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></li>
     780               <li>F.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></li>
     781               <li>F.19&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></li>
     782               <li>F.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></li>
     783               <li>F.21&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></li>
     784               <li>F.22&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></li>
     785               <li>F.23&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></li>
     786               <li>F.24&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></li>
     787               <li>F.25&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></li>
     788               <li>F.26&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></li>
     789               <li>F.27&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></li>
     790               <li>F.28&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></li>
     791               <li>F.29&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></li>
     792               <li>F.30&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></li>
     793               <li>F.31&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></li>
     794               <li>F.32&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></li>
     795               <li>F.33&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></li>
     796               <li>F.34&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></li>
     797               <li>F.35&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></li>
     798               <li>F.36&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></li>
     799               <li>F.37&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></li>
     800               <li>F.38&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></li>
     801               <li>F.39&nbsp;&nbsp;&nbsp;<a href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></li>
     802               <li>F.40&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19 and draft-ietf-httpbis-p3-payload-19</a></li>
    805803            </ul>
    806804         </li>
    … …  
    854852      </p>
    855853      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    856       <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF with the list rule expanded.
    857       </p>
    858       <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    859          (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR
    860          (any visible US-ASCII character).
    861       </p>
    862       <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    863       <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>:
    864       </p>
    865       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">BWS</a>           = &lt;BWS, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    866   <a href="#core.rules" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    867   <a href="#core.rules" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    868   <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    869   <a href="#core.rules" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    870   <a href="#core.rules" class="smpl">word</a>          = &lt;word, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    871 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    872       <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
    873       <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>&gt;
    874   <a href="#abnf.dependencies" class="smpl">comment</a>       = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    875   <a href="#abnf.dependencies" class="smpl">partial-URI</a>   = &lt;partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>&gt;
    876   <a href="#abnf.dependencies" class="smpl">qvalue</a>        = &lt;qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a>&gt;
    877   <a href="#abnf.dependencies" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>&gt;
    878 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="methods" href="#methods">Methods</a></h1>
    879       <p id="rfc.section.2.p.1">The method token indicates the request method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). The method is case-sensitive.
    880       </p>
    881       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#methods" class="smpl">method</a>         = <a href="#core.rules" class="smpl">token</a>
     854      <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;D</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;E</a> shows the collected ABNF with the list rule expanded.
     855      </p>
     856      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="methods" href="#methods">Methods</a></h1>
     857      <p id="rfc.section.2.p.1">The method token indicates the request method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). The method is case-sensitive.
     858      </p>
     859      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#methods" class="smpl">method</a>         = <a href="#imported.abnf" class="smpl">token</a>
    882860</pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an <a href="#header.allow" class="smpl">Allow</a> header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;9.5</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the
    883861         set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> respond with the status code <a href="#status.405" class="smpl">405 (Method Not Allowed)</a> if the method is known by the origin server but not allowed for the resource, and <a href="#status.501" class="smpl">501 (Not
    … …  
    929907         to a single application, so that this is clear.
    930908      </p>
    931       <p id="rfc.section.2.2.1.p.3">Due to the parsing rules defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, definitions of HTTP methods cannot prohibit the presence of a message body on either the request or the response message
     909      <p id="rfc.section.2.2.1.p.3">Due to the parsing rules defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, definitions of HTTP methods cannot prohibit the presence of a message body on either the request or the response message
    932910         (with responses to HEAD requests being the single exception). Definitions of new methods cannot change this rule, but they
    933911         can specify that only zero-length bodies (as opposed to absent bodies) are allowed.
    … …  
    948926         body to make more detailed queries on the server.
    949927      </p>
    950       <p id="rfc.section.2.3.1.p.4">If the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to a specific resource.
     928      <p id="rfc.section.2.3.1.p.4">If the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to a specific resource.
    951929         Since a server's communication options typically depend on the resource, the "*" request is only useful as a "ping" or "no-op"
    952930         type of method; it does nothing beyond allowing the client to test the capabilities of the server. For example, this can be
    … …  
    11041082      </p>
    11051083      <p id="rfc.section.2.3.7.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing
    1106          or diagnostic information. The value of the <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field (<a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the <a href="#header.max-forwards" class="smpl">Max-Forwards</a> header field allows the client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding
     1084         or diagnostic information. The value of the <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field (<a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the <a href="#header.max-forwards" class="smpl">Max-Forwards</a> header field allows the client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding
    11071085         messages in an infinite loop.
    11081086      </p>
    1109       <p id="rfc.section.2.3.7.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a <a href="#header.content-type" class="smpl">Content-Type</a> of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 7.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) and contain a message body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
     1087      <p id="rfc.section.2.3.7.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have a <a href="#header.content-type" class="smpl">Content-Type</a> of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 7.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) and contain a message body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
    11101088      </p>
    11111089      <div id="rfc.iref.c.2"></div>
    … …  
    11151093         its behavior to blind forwarding of packets until the connection is closed.
    11161094      </p>
    1117       <p id="rfc.section.2.3.8.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
     1095      <p id="rfc.section.2.3.8.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> use the authority form (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>); i.e., the request-target consists of only the host name and port number of the tunnel destination, separated by a colon.
    11181096         For example,
    11191097      </p>
    1120       <div id="rfc.figure.u.4"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
     1098      <div id="rfc.figure.u.2"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
    11211099Host: server.example.com:80
    11221100
    … …  
    11311109      </p>
    11321110      <p id="rfc.section.2.3.8.p.7">Proxy authentication might be used to establish the authority to create a tunnel:</p>
    1133       <div id="rfc.figure.u.5"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
     1111      <div id="rfc.figure.u.3"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
    11341112Host: server.example.com:80
    11351113Proxy-Authorization: basic aGVsbG86d29ybGQ=
    … …  
    11521130      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Fields</a></h1>
    11531131      <p id="rfc.section.3.p.1">Header fields are key value pairs that can be used to communicate data about the message, its payload, the target resource,
    1154          or about the connection itself (i.e., control data). See <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> for a general definition of their syntax.
     1132         or about the connection itself (i.e., control data). See <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> for a general definition of their syntax.
    11551133      </p>
    11561134      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="considerations.for.creating.header.fields" href="#considerations.for.creating.header.fields">Considerations for Creating Header Fields</a></h2>
    … …  
    11601138         with "X-" if they are to be registered (either immediately or in the future).
    11611139      </p>
    1162       <p id="rfc.section.3.1.p.3">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Appendix B</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
     1140      <p id="rfc.section.3.1.p.3">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF list extension: #rule">Appendix B</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
    11631141         can use an encoding such as the one defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>.
    11641142      </p>
    11651143      <p id="rfc.section.3.1.p.4">Because commas (",") are used as a generic delimiter between field-values, they need to be treated with care if they are allowed
    11661144         in the field-value's payload. Typically, components that might contain a comma are protected with double-quotes using the
    1167          quoted-string ABNF production (<a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     1145         quoted-string ABNF production (<a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    11681146      </p>
    11691147      <p id="rfc.section.3.1.p.5">For example, a textual date and a URI (either of which might contain a comma) could be safely carried in field-values like
    11701148         these:
    11711149      </p>
    1172       <div id="rfc.figure.u.6"></div><pre class="text">  Example-URI-Field: "http://example.com/a.html,foo",
     1150      <div id="rfc.figure.u.4"></div><pre class="text">  Example-URI-Field: "http://example.com/a.html,foo",
    11731151                     "http://without-a-comma.example.com/"
    11741152  Example-Date-Field: "Sat, 04 May 1996", "Wed, 14 Sep 2005"
    … …  
    11831161      <ul>
    11841162         <li>
    1185             <p>Whether the field is a single value, or whether it can be a list (delimited by commas; see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     1163            <p>Whether the field is a single value, or whether it can be a list (delimited by commas; see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    11861164            </p>
    11871165            <p>If it does not use the list syntax, document how to treat messages where the header field occurs multiple times (a sensible
    … …  
    11991177         </li>
    12001178         <li>
    1201             <p>Whether it is appropriate to list the field-name in the <a href="p1-messaging.html#header.connection" class="smpl">Connection</a> header field (i.e., if the header field is to be hop-by-hop, see <a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     1179            <p>Whether it is appropriate to list the field-name in the <a href="p1-messaging.html#header.connection" class="smpl">Connection</a> header field (i.e., if the header field is to be hop-by-hop, see <a href="p1-messaging.html#header.connection" title="Connection">Section 6.1</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    12021180            </p>
    12031181         </li>
    … …  
    12101188         </li>
    12111189         <li>
    1212             <p>Whether the header field is useful or allowable in trailers (see <a href="p1-messaging.html#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     1190            <p>Whether the header field is useful or allowable in trailers (see <a href="p1-messaging.html#chunked.encoding" title="Chunked Transfer Coding">Section 4.1</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    12131191            </p>
    12141192         </li>
    … …  
    12611239               <tr>
    12621240                  <td class="left">Host</td>
    1263                   <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 5.4</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
     1241                  <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 5.4</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
    12641242               </tr>
    12651243               <tr>
    … …  
    13011279               <tr>
    13021280                  <td class="left">TE</td>
    1303                   <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
     1281                  <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
    13041282               </tr>
    13051283               <tr>
    … …  
    13121290      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h2>
    13131291      <p id="rfc.section.3.3.p.1">The response header fields allow the server to pass additional information about the response which cannot be placed in the
    1314          status-line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     1292         status-line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    13151293      </p>
    13161294      <div id="rfc.table.u.2">
    … …  
    16601638      <p id="rfc.section.4.3.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been
    16611639         received and has not yet been rejected by the server. The client <em class="bcp14">SHOULD</em> continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The
    1662          server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
     1640         server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
    16631641      </p>
    16641642      <div id="rfc.iref.22"></div>
    16651643      <div id="rfc.iref.s.4"></div>
    16661644      <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    1667       <p id="rfc.section.4.3.2.p.1">The server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     1645      <p id="rfc.section.4.3.2.p.1">The server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> message header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
    16681646         by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    16691647      </p>
    … …  
    17201698      <div id="rfc.iref.s.9"></div>
    17211699      <h3 id="rfc.section.4.4.4"><a href="#rfc.section.4.4.4">4.4.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    1722       <p id="rfc.section.4.4.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.4</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1700      <p id="rfc.section.4.4.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.4</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    17231701      </p>
    17241702      <p id="rfc.section.4.4.4.p.2">This status code is only appropriate when the response status code would have been <a href="#status.200" class="smpl">200 (OK)</a> otherwise. When the status code before transformation would have been different, the 214 Transformation Applied warn-code
    … …  
    17551733         another input action.
    17561734      </p>
    1757       <p id="rfc.section.4.4.6.p.2">The message body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     1735      <p id="rfc.section.4.4.6.p.2">The message body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    17581736      </p>
    17591737      <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
    … …  
    20141992      <div id="rfc.iref.s.35"></div>
    20151993      <h3 id="rfc.section.4.6.15"><a href="#rfc.section.4.6.15">4.6.15</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
    2016       <p id="rfc.section.4.6.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) specifying the required protocols.
    2017       </p>
    2018       <div id="rfc.figure.u.7"></div>
     1994      <p id="rfc.section.4.6.15.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.5</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) specifying the required protocols.
     1995      </p>
     1996      <div id="rfc.figure.u.5"></div>
    20191997      <p>Example:</p>  <pre class="text">HTTP/1.1 426 Upgrade Required
    20201998Upgrade: HTTP/3.0
    … …  
    20792057      <p id="rfc.section.4.7.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
    20802058         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    2081          in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.7</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[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.
     2059         in <a href="p1-messaging.html#http.version" title="Protocol Versioning">Section 2.7</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[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.
    20822060      </p>
    20832061      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    … …  
    20862064         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>:
    20872065      </p>
    2088       <div id="rfc.figure.u.8"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
     2066      <div id="rfc.figure.u.6"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    20892067</pre><p id="rfc.section.5.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
    2090       <div id="rfc.figure.u.9"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
     2068      <div id="rfc.figure.u.7"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    20912069Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    20922070</pre><p id="rfc.section.5.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.
    … …  
    20962074         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.
    20972075      </p>
    2098       <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.3"></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>
     2076      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.3"></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>
    20992077</pre><div id="preferred.date.format">
    21002078         <p id="rfc.section.5.1.p.8">                    Preferred format:</p>
    21012079      </div>
    2102       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><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>  <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>
     2080      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><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>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
    21032081  ; fixed length subset of the format defined in
    21042082  ; <a href="http://tools.ietf.org/html/rfc1123#section-5.2.14">Section 5.2.14</a> of <a href="#RFC1123" id="rfc.xref.RFC1123.2"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>
    … …  
    21122090               / %x53.75.6E ; "Sun", case-sensitive
    21132091               
    2114   <a href="#obsolete.date.formats" class="smpl">date1</a>        = <a href="#preferred.date.format" class="smpl">day</a> <a href="#notation" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">month</a> <a href="#notation" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
     2092  <a href="#obsolete.date.formats" class="smpl">date1</a>        = <a href="#preferred.date.format" class="smpl">day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">month</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
    21152093               ; e.g., 02 Jun 1982
    21162094
    2117   <a href="#preferred.date.format" class="smpl">day</a>          = 2<a href="#notation" class="smpl">DIGIT</a>
     2095  <a href="#preferred.date.format" class="smpl">day</a>          = 2<a href="#imported.abnf" class="smpl">DIGIT</a>
    21182096  <a href="#preferred.date.format" class="smpl">month</a>        = %x4A.61.6E ; "Jan", case-sensitive
    21192097               / %x46.65.62 ; "Feb", case-sensitive
    … …  
    21282106               / %x4E.6F.76 ; "Nov", case-sensitive
    21292107               / %x44.65.63 ; "Dec", case-sensitive
    2130   <a href="#preferred.date.format" class="smpl">year</a>         = 4<a href="#notation" class="smpl">DIGIT</a>
     2108  <a href="#preferred.date.format" class="smpl">year</a>         = 4<a href="#imported.abnf" class="smpl">DIGIT</a>
    21312109
    21322110  <a href="#preferred.date.format" class="smpl">GMT</a>   = %x47.4D.54 ; "GMT", case-sensitive
    … …  
    21352113                 ; 00:00:00 - 23:59:59
    21362114                 
    2137   <a href="#preferred.date.format" class="smpl">hour</a>         = 2<a href="#notation" class="smpl">DIGIT</a>               
    2138   <a href="#preferred.date.format" class="smpl">minute</a>       = 2<a href="#notation" class="smpl">DIGIT</a>               
    2139   <a href="#preferred.date.format" class="smpl">second</a>       = 2<a href="#notation" class="smpl">DIGIT</a>               
     2115  <a href="#preferred.date.format" class="smpl">hour</a>         = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
     2116  <a href="#preferred.date.format" class="smpl">minute</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
     2117  <a href="#preferred.date.format" class="smpl">second</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
    21402118</pre><p id="rfc.section.5.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>).
    21412119      </p>
    … …  
    21432121         <p id="rfc.section.5.1.p.11">              Obsolete formats:</p>
    21442122      </div>
    2145       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.16"></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>
    2146 </pre><div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  <a href="#obsolete.date.formats" class="smpl">rfc850-date</a>  = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#notation" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <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>
    2147   <a href="#obsolete.date.formats" class="smpl">date2</a>        = <a href="#preferred.date.format" class="smpl">day</a> "-" <a href="#preferred.date.format" class="smpl">month</a> "-" 2<a href="#notation" class="smpl">DIGIT</a>
     2123      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.16"></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>
     2124</pre><div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  <a href="#obsolete.date.formats" class="smpl">rfc850-date</a>  = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     2125  <a href="#obsolete.date.formats" class="smpl">date2</a>        = <a href="#preferred.date.format" class="smpl">day</a> "-" <a href="#preferred.date.format" class="smpl">month</a> "-" 2<a href="#imported.abnf" class="smpl">DIGIT</a>
    21482126                 ; day-month-year (e.g., 02-Jun-82)
    21492127
    … …  
    21552133         / %x53.61.74.75.72.64.61.79 ; "Saturday", case-sensitive
    21562134         / %x53.75.6E.64.61.79 ; "Sunday", case-sensitive
    2157 </pre><div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.18"></span>  <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#notation" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <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">year</a>
    2158   <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> ))
     2135</pre><div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.18"></span>  <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
     2136  <a href="#obsolete.date.formats" class="smpl">date3</a>        = <a href="#preferred.date.format" class="smpl">month</a> <a href="#imported.abnf" class="smpl">SP</a> ( 2<a href="#imported.abnf" class="smpl">DIGIT</a> / ( <a href="#imported.abnf" class="smpl">SP</a> 1<a href="#imported.abnf" class="smpl">DIGIT</a> ))
    21592137                 ; month day (e.g., Jun  2)
    21602138</pre><div class="note" id="rfc.section.5.1.p.15">
    … …  
    21732151         By convention, the products are listed in order of their significance for identifying the application.
    21742152      </p>
    2175       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></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>]
    2176   <a href="#product.tokens" class="smpl">product-version</a> = <a href="#core.rules" class="smpl">token</a>
     2153      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#imported.abnf" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
     2154  <a href="#product.tokens" class="smpl">product-version</a> = <a href="#imported.abnf" class="smpl">token</a>
    21772155</pre><p id="rfc.section.5.2.p.3">Examples:</p>
    2178       <div id="rfc.figure.u.16"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     2156      <div id="rfc.figure.u.14"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    21792157  Server: Apache/0.8.4
    21802158</pre><p id="rfc.section.5.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).
    … …  
    21872165         </p>
    21882166      </div>
    2189       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.21"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a>
     2167      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.21"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#imported.abnf" class="smpl">token</a>
    21902168</pre><p id="rfc.section.5.3.p.4">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
    21912169         Character Set registry <em class="bcp14">MUST</em> represent the character encoding defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character encodings to those defined within the IANA registry.
    … …  
    22012179         directly, and only decoded by the recipient.
    22022180      </p>
    2203       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.22"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#core.rules" class="smpl">token</a>
     2181      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.22"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#imported.abnf" class="smpl">token</a>
    22042182</pre><p id="rfc.section.5.4.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;9.3</a>) and <a href="#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;9.6</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    22052183         mechanism will be required to remove the encoding.
    … …  
    22082186      </p>
    22092187      <ul class="empty">
    2210          <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     2188         <li>See <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    22112189         </li>
    22122190      </ul>
    … …  
    22142192      </p>
    22152193      <ul class="empty">
    2216          <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     2194         <li>See <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    22172195         </li>
    22182196      </ul>
    … …  
    22202198      </p>
    22212199      <ul class="empty">
    2222          <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     2200         <li>See <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    22232201         </li>
    22242202      </ul>
    … …  
    22322210         <li>Pointer to specification text</li>
    22332211      </ul>
    2234       <p id="rfc.section.5.4.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     2212      <p id="rfc.section.5.4.1.p.3">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    22352213      </p>
    22362214      <p id="rfc.section.5.4.1.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
    … …  
    22412219      <p id="rfc.section.5.5.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the <a href="#header.content-type" class="smpl">Content-Type</a> (<a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;9.9</a>) and <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;9.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
    22422220      </p>
    2243       <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span>  <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
    2244   <a href="#media.types" class="smpl">type</a>       = <a href="#core.rules" class="smpl">token</a>
    2245   <a href="#media.types" class="smpl">subtype</a>    = <a href="#core.rules" class="smpl">token</a>
     2221      <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span>  <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
     2222  <a href="#media.types" class="smpl">type</a>       = <a href="#imported.abnf" class="smpl">token</a>
     2223  <a href="#media.types" class="smpl">subtype</a>    = <a href="#imported.abnf" class="smpl">token</a>
    22462224</pre><div id="rule.parameter">
    22472225         <p id="rfc.section.5.5.p.3">      The type/subtype <em class="bcp14">MAY</em> be followed by parameters in the form of attribute/value pairs.
    22482226         </p>
    22492227      </div>
    2250       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span>  <a href="#rule.parameter" class="smpl">parameter</a>      = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a>
    2251   <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#core.rules" class="smpl">token</a>
    2252   <a href="#rule.parameter" class="smpl">value</a>          = <a href="#core.rules" class="smpl">word</a>
     2228      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span>  <a href="#rule.parameter" class="smpl">parameter</a>      = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a>
     2229  <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#imported.abnf" class="smpl">token</a>
     2230  <a href="#rule.parameter" class="smpl">value</a>          = <a href="#imported.abnf" class="smpl">word</a>
    22532231</pre><p id="rfc.section.5.5.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
    22542232         depending on the semantics of the parameter name. The presence or absence of a parameter might be significant to the processing
    22552233         of a media-type, depending on its definition within the media type registry.
    22562234      </p>
    2257       <p id="rfc.section.5.5.p.6">A parameter value that matches the <a href="#core.rules" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
     2235      <p id="rfc.section.5.5.p.6">A parameter value that matches the <a href="#imported.abnf" class="smpl">token</a> production can be transmitted as either a token or within a quoted-string. The quoted and unquoted values are equivalent.
    22582236      </p>
    22592237      <p id="rfc.section.5.5.p.7">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
    … …  
    22982276         of subtags:
    22992277      </p>
    2300       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.30"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
     2278      <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.30"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
    23012279</pre><p id="rfc.section.5.6.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered
    23022280         by the IANA (see &lt;<a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>&gt;).
    23032281      </p>
    2304       <div id="rfc.figure.u.22"></div>
     2282      <div id="rfc.figure.u.20"></div>
    23052283      <p>Example tags include:</p>  <pre class="text">  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
    23062284</pre> <p id="rfc.section.5.6.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
    … …  
    23312309               <tr>
    23322310                  <td class="left">Content-Length</td>
    2333                   <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
     2311                  <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a></td>
    23342312               </tr>
    23352313               <tr>
    … …  
    23412319      </div>
    23422320      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
    2343       <p id="rfc.section.6.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> that might have been applied to ensure safe and proper transfer of the message.
     2321      <p id="rfc.section.6.2.p.1">A payload body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.31"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. The payload body is obtained from the message body by decoding any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> that might have been applied to ensure safe and proper transfer of the message.
    23442322      </p>
    23452323      <div id="rfc.iref.r.1"></div>
    … …  
    23602338         in an HTTP message, it is referred to as the payload of the message.
    23612339      </p>
    2362       <p id="rfc.section.7.p.4">A representation body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. The representation body is obtained from the message body by decoding any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> that might have been applied to ensure safe and proper transfer of the message.
     2340      <p id="rfc.section.7.p.4">A representation body is only present in a message when a message body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. The representation body is obtained from the message body by decoding any <a href="p1-messaging.html#header.transfer-encoding" class="smpl">Transfer-Encoding</a> that might have been applied to ensure safe and proper transfer of the message.
    23632341      </p>
    23642342      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="identifying.response.associated.with.representation" href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></h2>
    23652343      <p id="rfc.section.7.1.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p>
    23662344      <p id="rfc.section.7.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p>
    2367       <p id="rfc.section.7.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.45"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
     2345      <p id="rfc.section.7.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.33"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
    23682346         rules are used (with the first applicable one being selected):
    23692347      </p>
    … …  
    24572435      <p id="rfc.section.7.3.p.2">The data type of the representation data is determined via the header fields <a href="#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-encoding" class="smpl">Content-Encoding</a>. These define a two-layer, ordered encoding model:
    24582436      </p>
    2459       <div id="rfc.figure.u.23"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
     2437      <div id="rfc.figure.u.21"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
    24602438</pre><p id="rfc.section.7.3.p.4"> <a href="#header.content-type" class="smpl">Content-Type</a> specifies the media type of the underlying data, which defines both the data format and how that data <em class="bcp14">SHOULD</em> be processed by the recipient (within the scope of the request method semantics). Any HTTP/1.1 message containing a payload
    24612439         body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of the associated representation unless that metadata is unknown
    … …  
    25262504            (Not Acceptable)</a> response.
    25272505      </p>
    2528       <p id="rfc.section.8.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.46"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> for more information.
     2506      <p id="rfc.section.8.1.p.5">Many of the mechanisms for expressing preferences use quality values to declare relative preference. See <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.34"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> for more information.
    25292507      </p>
    25302508      <p id="rfc.section.8.1.p.6">HTTP/1.1 includes the following header fields for enabling server-driven negotiation through description of user agent capabilities
    … …  
    25682546         for an in-line image.
    25692547      </p>
    2570       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span>  <a href="#header.accept" class="smpl">Accept</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] )
     2548      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span>  <a href="#header.accept" class="smpl">Accept</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] )
    25712549 
    25722550  <a href="#header.accept" class="smpl">media-range</a>    = ( "*/*"
    25732551                   / ( <a href="#media.types" class="smpl">type</a> "/" "*" )
    25742552                   / ( <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> )
    2575                    ) *( <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
    2576   <a href="#header.accept" class="smpl">accept-params</a>  = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> *( <a href="#header.accept" class="smpl">accept-ext</a> )
    2577   <a href="#header.accept" class="smpl">accept-ext</a>     = <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#core.rules" class="smpl">token</a> [ "=" <a href="#core.rules" class="smpl">word</a> ]
     2553                   ) *( <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
     2554  <a href="#header.accept" class="smpl">accept-params</a>  = <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> "q=" <a href="#imported.abnf" class="smpl">qvalue</a> *( <a href="#header.accept" class="smpl">accept-ext</a> )
     2555  <a href="#header.accept" class="smpl">accept-ext</a>     = <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> <a href="#imported.abnf" class="smpl">token</a> [ "=" <a href="#imported.abnf" class="smpl">word</a> ]
    25782556</pre><p id="rfc.section.9.1.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating
    25792557         all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range.
    … …  
    25812559      <p id="rfc.section.9.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first
    25822560         "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user
    2583          agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.47"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). The default value is q=1.
     2561         agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). The default value is q=1.
    25842562      </p>
    25852563      <div class="note" id="rfc.section.9.1.p.5">
    … …  
    25912569      </div>
    25922570      <p id="rfc.section.9.1.p.6">The example</p>
    2593       <div id="rfc.figure.u.25"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
     2571      <div id="rfc.figure.u.23"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
    25942572</pre><p id="rfc.section.9.1.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
    25952573         quality".
    … …  
    26002578      </p>
    26012579      <p id="rfc.section.9.1.p.10">A more elaborate example is</p>
    2602       <div id="rfc.figure.u.26"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
     2580      <div id="rfc.figure.u.24"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
    26032581          text/x-dvi; q=0.8, text/x-c
    26042582</pre><p id="rfc.section.9.1.p.12">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then
    … …  
    26082586         to a given type, the most specific reference has precedence. For example,
    26092587      </p>
    2610       <div id="rfc.figure.u.27"></div><pre class="text">  Accept: text/*, text/plain, text/plain;format=flowed, */*
     2588      <div id="rfc.figure.u.25"></div><pre class="text">  Accept: text/*, text/plain, text/plain;format=flowed, */*
    26112589</pre><p id="rfc.section.9.1.p.15">have the following precedence: </p>
    26122590      <ol>
    … …  
    26192597         which matches that type. For example,
    26202598      </p>
    2621       <div id="rfc.figure.u.28"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
     2599      <div id="rfc.figure.u.26"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    26222600          text/html;level=2;q=0.4, */*;q=0.5
    26232601</pre><p id="rfc.section.9.1.p.18">would cause the following values to be associated:</p>
    … …  
    26682646         that capability to a server which is capable of representing documents in those character encodings.
    26692647      </p>
    2670       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.35"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" )
    2671                          [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
     2648      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.35"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" )
     2649                         [ <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> "q=" <a href="#imported.abnf" class="smpl">qvalue</a> ] )
    26722650</pre><p id="rfc.section.9.2.p.3">Character encoding values (a.k.a., charsets) are described in <a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;5.3</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset. The default value is q=1. An
    26732651         example is
    26742652      </p>
    2675       <div id="rfc.figure.u.30"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
     2653      <div id="rfc.figure.u.28"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    26762654</pre><p id="rfc.section.9.2.p.5">The special value "*", if present in the Accept-Charset field, matches every character encoding which is not mentioned elsewhere
    26772655         in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character encodings not explicitly
    … …  
    26882666         no encoding is preferred.
    26892667      </p>
    2690       <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>  = #( <a href="#header.accept-encoding" class="smpl">codings</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
     2668      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>  = #( <a href="#header.accept-encoding" class="smpl">codings</a> [ <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> "q=" <a href="#imported.abnf" class="smpl">qvalue</a> ] )
    26912669  <a href="#header.accept-encoding" class="smpl">codings</a>          = <a href="#content.codings" class="smpl">content-coding</a> / "identity" / "*"
    26922670</pre><p id="rfc.section.9.3.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding. The default value is q=1.
    26932671      </p>
    26942672      <p id="rfc.section.9.3.p.4">For example,</p>
    2695       <div id="rfc.figure.u.32"></div><pre class="text">  Accept-Encoding: compress, gzip
     2673      <div id="rfc.figure.u.30"></div><pre class="text">  Accept-Encoding: compress, gzip
    26962674  Accept-Encoding:
    26972675  Accept-Encoding: *
    … …  
    27092687         </li>
    27102688         <li>If the representation's content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable
    2711             unless it is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.48"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)
     2689            unless it is accompanied by a qvalue of 0. (As defined in <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.36"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, a qvalue of 0 means "not acceptable".)
    27122690         </li>
    27132691         <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li>
    … …  
    27312709         in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;5.6</a>.
    27322710      </p>
    2733       <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a> =
    2734                     1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> "q=" <a href="#abnf.dependencies" class="smpl">qvalue</a> ] )
     2711      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a> =
     2712                    1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> "q=" <a href="#imported.abnf" class="smpl">qvalue</a> ] )
    27352713  <a href="#header.accept-language" class="smpl">language-range</a>  =
    27362714            &lt;language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>&gt;
    … …  
    27382716         languages specified by that range. The quality value defaults to "q=1". For example,
    27392717      </p>
    2740       <div id="rfc.figure.u.34"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
     2718      <div id="rfc.figure.u.32"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
    27412719</pre><p id="rfc.section.9.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (see also <a href="http://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>)
    27422720      </p>
    … …  
    27662744         is strictly to inform the recipient of valid request methods associated with the resource.
    27672745      </p>
    2768       <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.40"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#methods" class="smpl">method</a>
     2746      <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.40"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#methods" class="smpl">method</a>
    27692747</pre><p id="rfc.section.9.5.p.3">Example of use:</p>
    2770       <div id="rfc.figure.u.36"></div><pre class="text">  Allow: GET, HEAD, PUT
     2748      <div id="rfc.figure.u.34"></div><pre class="text">  Allow: GET, HEAD, PUT
    27712749</pre><p id="rfc.section.9.5.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    27722750      <p id="rfc.section.9.5.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
    … …  
    27802758         its underlying media type.
    27812759      </p>
    2782       <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.41"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
     2760      <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.41"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
    27832761</pre><p id="rfc.section.9.6.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;5.4</a>. An example of its use is
    27842762      </p>
    2785       <div id="rfc.figure.u.38"></div><pre class="text">  Content-Encoding: gzip
     2763      <div id="rfc.figure.u.36"></div><pre class="text">  Content-Encoding: gzip
    27862764</pre><p id="rfc.section.9.6.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding
    27872765         and is only decoded before rendering or analogous usage. However, a transforming proxy <em class="bcp14">MAY</em> modify the content-coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control
    … …  
    28072785         that this might not be equivalent to all the languages used within the representation.
    28082786      </p>
    2809       <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.42"></span>  <a href="#header.content-language" class="smpl">Content-Language</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
     2787      <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.42"></span>  <a href="#header.content-language" class="smpl">Content-Language</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
    28102788</pre><p id="rfc.section.9.7.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;5.6</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
    28112789         user's own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate
    28122790         field is
    28132791      </p>
    2814       <div id="rfc.figure.u.40"></div><pre class="text">  Content-Language: da
     2792      <div id="rfc.figure.u.38"></div><pre class="text">  Content-Language: da
    28152793</pre><p id="rfc.section.9.7.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean
    28162794         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
    … …  
    28202798         simultaneously in the original Maori and English versions, would call for
    28212799      </p>
    2822       <div id="rfc.figure.u.41"></div><pre class="text">  Content-Language: mi, en
     2800      <div id="rfc.figure.u.39"></div><pre class="text">  Content-Language: mi, en
    28232801</pre><p id="rfc.section.9.7.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple
    28242802         linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly
    … …  
    28332811         message. In other words, if one were to perform a GET on this URI at the time of this message's generation, then a <a href="#status.200" class="smpl">200 (OK)</a> response would contain the same representation that is enclosed as payload in this message.
    28342812      </p>
    2835       <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.43"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    2836 </pre><p id="rfc.section.9.8.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.49"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
     2813      <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.43"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#imported.abnf" class="smpl">absolute-URI</a> / <a href="#imported.abnf" class="smpl">partial-URI</a>
     2814</pre><p id="rfc.section.9.8.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
    28372815         body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
    28382816      </p>
    … …  
    28732851         the media type is that which would have been sent had the request been a GET.
    28742852      </p>
    2875       <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.44"></span>  <a href="#header.content-type" class="smpl">Content-Type</a> = <a href="#media.types" class="smpl">media-type</a>
     2853      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.44"></span>  <a href="#header.content-type" class="smpl">Content-Type</a> = <a href="#media.types" class="smpl">media-type</a>
    28762854</pre><p id="rfc.section.9.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;5.5</a>. An example of the field is
    28772855      </p>
    2878       <div id="rfc.figure.u.44"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
     2856      <div id="rfc.figure.u.42"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
    28792857</pre><p id="rfc.section.9.9.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section&nbsp;7.3</a>.
    28802858      </p>
    … …  
    28852863         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;5.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    28862864      </p>
    2887       <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.45"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
     2865      <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.45"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
    28882866</pre><p id="rfc.section.9.10.p.3">An example is</p>
    2889       <div id="rfc.figure.u.46"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
     2867      <div id="rfc.figure.u.44"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
    28902868</pre><p id="rfc.section.9.10.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
    28912869      </p>
    … …  
    29132891      <h2 id="rfc.section.9.11"><a href="#rfc.section.9.11">9.11</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
    29142892      <p id="rfc.section.9.11.p.1">The "Expect" header field is used to indicate that particular server behaviors are required by the client.</p>
    2915       <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span>  <a href="#header.expect" class="smpl">Expect</a>       = 1#<a href="#header.expect" class="smpl">expectation</a>
     2893      <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span>  <a href="#header.expect" class="smpl">Expect</a>       = 1#<a href="#header.expect" class="smpl">expectation</a>
    29162894 
    2917   <a href="#header.expect" class="smpl">expectation</a>  = <a href="#header.expect" class="smpl">expect-name</a> [ <a href="#core.rules" class="smpl">BWS</a> "=" <a href="#core.rules" class="smpl">BWS</a> <a href="#header.expect" class="smpl">expect-value</a> ]
    2918                              *( <a href="#core.rules" class="smpl">OWS</a> ";" [ <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expect" class="smpl">expect-param</a> ] )
    2919   <a href="#header.expect" class="smpl">expect-param</a> = <a href="#header.expect" class="smpl">expect-name</a> [ <a href="#core.rules" class="smpl">BWS</a> "=" <a href="#core.rules" class="smpl">BWS</a> <a href="#header.expect" class="smpl">expect-value</a> ]
     2895  <a href="#header.expect" class="smpl">expectation</a>  = <a href="#header.expect" class="smpl">expect-name</a> [ <a href="#imported.abnf" class="smpl">BWS</a> "=" <a href="#imported.abnf" class="smpl">BWS</a> <a href="#header.expect" class="smpl">expect-value</a> ]
     2896                             *( <a href="#imported.abnf" class="smpl">OWS</a> ";" [ <a href="#imported.abnf" class="smpl">OWS</a> <a href="#header.expect" class="smpl">expect-param</a> ] )
     2897  <a href="#header.expect" class="smpl">expect-param</a> = <a href="#header.expect" class="smpl">expect-name</a> [ <a href="#imported.abnf" class="smpl">BWS</a> "=" <a href="#imported.abnf" class="smpl">BWS</a> <a href="#header.expect" class="smpl">expect-value</a> ]
    29202898 
    2921   <a href="#header.expect" class="smpl">expect-name</a>  = <a href="#core.rules" class="smpl">token</a>
    2922   <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>
     2899  <a href="#header.expect" class="smpl">expect-name</a>  = <a href="#imported.abnf" class="smpl">token</a>
     2900  <a href="#header.expect" class="smpl">expect-value</a> = <a href="#imported.abnf" class="smpl">token</a> / <a href="#imported.abnf" class="smpl">quoted-string</a>
    29232901</pre><p id="rfc.section.9.11.p.3">If all received Expect header field(s) are syntactically valid but contain an expectation that the recipient does not understand
    29242902         or cannot comply with, the recipient <em class="bcp14">MUST</em> respond with a <a href="#status.417" class="smpl">417 (Expectation Failed)</a> status code. A recipient of a syntactically invalid Expectation header field <em class="bcp14">MUST</em> respond with a <a href="#status.4xx" class="smpl">4xx</a> status code other than 417.
    … …  
    29282906      </p>
    29292907      <ul class="empty">
    2930          <li>The "100-continue" expectation is defined <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.50"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. It does not support any expect-params.
     2908         <li>The "100-continue" expectation is defined <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 6.4.3</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. It does not support any expect-params.
    29312909         </li>
    29322910      </ul>
    … …  
    29412919      <p id="rfc.section.9.12.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>:
    29422920      </p>
    2943       <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.51"></span>  <a href="#header.from" class="smpl">From</a>    = <a href="#header.from" class="smpl">mailbox</a>
     2921      <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.51"></span>  <a href="#header.from" class="smpl">From</a>    = <a href="#header.from" class="smpl">mailbox</a>
    29442922 
    29452923  <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;
    29462924</pre><p id="rfc.section.9.12.p.3">An example is:</p>
    2947       <div id="rfc.figure.u.49"></div><pre class="text">  From: webmaster@example.org
     2925      <div id="rfc.figure.u.47"></div><pre class="text">  From: webmaster@example.org
    29482926</pre><p id="rfc.section.9.12.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
    29492927         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
    … …  
    29622940      <p id="rfc.section.9.13.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.
    29632941      </p>
    2964       <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#abnf.dependencies" class="smpl">URI-reference</a>
     2942      <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#imported.abnf" class="smpl">URI-reference</a>
    29652943</pre><p id="rfc.section.9.13.p.3">For <a href="#status.201" class="smpl">201 (Created)</a> responses, the Location is the URI of the new resource which was created by the request. For <a href="#status.3xx" class="smpl">3xx (Redirection)</a> responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
    29662944      </p>
    … …  
    29682946         then the original URI's fragment identifier is added to the final value.
    29692947      </p>
    2970       <div id="rfc.figure.u.51"></div>
     2948      <div id="rfc.figure.u.49"></div>
    29712949      <p>For example, the original URI "http://www.example.org/~tim", combined with a field value given as:</p>  <pre class="text">  Location: /pub/WWW/People.html#tim
    29722950</pre>  <p>would result in a final value of "http://www.example.org/pub/WWW/People.html#tim"</p>
    2973       <div id="rfc.figure.u.52"></div>
     2951      <div id="rfc.figure.u.50"></div>
    29742952      <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
    29752953</pre>  <p>would result in a final value of "http://www.example.net/index.html#larry", preserving the original fragment identifier.</p>
    … …  
    29942972         to trace a request which appears to be failing or looping mid-chain.
    29952973      </p>
    2996       <div id="rfc.figure.u.53"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
     2974      <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    29972975</pre><p id="rfc.section.9.14.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
    29982976      <p id="rfc.section.9.14.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).
    … …  
    30142992         non-HTTP URIs (e.g., FTP).
    30152993      </p>
    3016       <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.54"></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>
     2994      <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.54"></span>  <a href="#header.referer" class="smpl">Referer</a> = <a href="#imported.abnf" class="smpl">absolute-URI</a> / <a href="#imported.abnf" class="smpl">partial-URI</a>
    30172995</pre><p id="rfc.section.9.15.p.5">Example:</p>
    3018       <div id="rfc.figure.u.55"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
     2996      <div id="rfc.figure.u.53"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
    30192997</pre><p id="rfc.section.9.15.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.
    30202998      </p>
    … …  
    30263004      </p>
    30273005      <p id="rfc.section.9.16.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>
    3028       <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.55"></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>
     3006      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.55"></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>
    30293007</pre><div id="rule.delta-seconds">
    30303008         <p id="rfc.section.9.16.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
    30313009      </div>
    3032       <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.56"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
     3010      <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.56"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    30333011</pre><p id="rfc.section.9.16.p.6">Two examples of its use are</p>
    3034       <div id="rfc.figure.u.58"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
     3012      <div id="rfc.figure.u.56"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    30353013  Retry-After: 120
    30363014</pre><p id="rfc.section.9.16.p.8">In the latter example, the delay is 2 minutes.</p>
    … …  
    30393017      <h2 id="rfc.section.9.17"><a href="#rfc.section.9.17">9.17</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
    30403018      <p id="rfc.section.9.17.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
    3041       <p id="rfc.section.9.17.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;5.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.51"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
     3019      <p id="rfc.section.9.17.p.2">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;5.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.39"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
    30423020         identifying the application.
    30433021      </p>
    3044       <div id="rfc.figure.u.59"></div><pre class="inline"><span id="rfc.iref.g.57"></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> ) )
     3022      <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.57"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
    30453023</pre><p id="rfc.section.9.17.p.4">Example:</p>
    3046       <div id="rfc.figure.u.60"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    3047 </pre><p id="rfc.section.9.17.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the <a href="#header.server" class="smpl">Server</a> header field. Instead, it <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.via" class="smpl">Via</a> field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.52"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     3024      <div id="rfc.figure.u.58"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
     3025</pre><p id="rfc.section.9.17.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the <a href="#header.server" class="smpl">Server</a> header field. Instead, it <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.via" class="smpl">Via</a> 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: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    30483026      </p>
    30493027      <div class="note" id="rfc.section.9.17.p.7">
    … …  
    30613039         user agent limitations.
    30623040      </p>
    3063       <p id="rfc.section.9.18.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;5.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.53"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
     3041      <p id="rfc.section.9.18.p.3">The field can contain multiple product tokens (<a href="#product.tokens" title="Product Tokens">Section&nbsp;5.2</a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
    30643042         for identifying the application.
    30653043      </p>
    … …  
    30723050         doing so makes the field value more difficult to parse.
    30733051      </p>
    3074       <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.58"></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> ) )
     3052      <div id="rfc.figure.u.59"></div><pre class="inline"><span id="rfc.iref.g.58"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
    30753053</pre><p id="rfc.section.9.18.p.7">Example:</p>
    3076       <div id="rfc.figure.u.62"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     3054      <div id="rfc.figure.u.60"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    30773055</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>
    30783056      <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>
    … …  
    35583536                  <td class="left">compress</td>
    35593537                  <td class="left">UNIX "compress" program method</td>
    3560                   <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.54"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>
     3538                  <td class="left"> <a href="p1-messaging.html#compress.coding" title="Compress Coding">Section 4.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.42"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>
    35613539                  </td>
    35623540               </tr>
    … …  
    35653543                  <td class="left">"deflate" compression mechanism (<a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>) used inside the "zlib" data format (<a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a>)
    35663544                  </td>
    3567                   <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.55"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>
     3545                  <td class="left"> <a href="p1-messaging.html#deflate.coding" title="Deflate Coding">Section 4.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.43"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>
    35683546                  </td>
    35693547               </tr>
    … …  
    35713549                  <td class="left">gzip</td>
    35723550                  <td class="left">Same as GNU zip <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a></td>
    3573                   <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.56"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>
     3551                  <td class="left"> <a href="p1-messaging.html#gzip.coding" title="Gzip Coding">Section 4.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.44"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>
    35743552                  </td>
    35753553               </tr>
    … …  
    36633641      </p>
    36643642      <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    3665       <p id="rfc.section.12.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.57"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     3643      <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.45"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    36663644      </p>
    36673645      <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References
    … …  
    38843862         MIME environments.
    38853863      </p>
    3886       <div id="rfc.figure.u.63"></div><pre class="inline"><span id="rfc.iref.g.59"></span>  <a href="#mime-version" class="smpl">MIME-Version</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a>
     3864      <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.59"></span>  <a href="#mime-version" class="smpl">MIME-Version</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> "." 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    38873865</pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this
    38883866         document and not the MIME specification.
    … …  
    39713949      <p id="rfc.section.C.p.16">Allow <a href="#header.referer" class="smpl">Referer</a> field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.15</a>)
    39723950      </p>
    3973       <p id="rfc.section.C.p.17">In the description of the <a href="#header.server" class="smpl">Server</a> header field, the <a href="p1-messaging.html#header.via" class="smpl">Via</a> field was described as a SHOULD. The requirement was and is stated correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.58"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;9.17</a>)
     3951      <p id="rfc.section.C.p.17">In the description of the <a href="#header.server" class="smpl">Server</a> header field, the <a href="p1-messaging.html#header.via" class="smpl">Via</a> field was described as a SHOULD. The requirement was and is stated correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.46"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;9.17</a>)
    39743952      </p>
    39753953      <p id="rfc.section.C.p.18">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Encodings (charset)">Section&nbsp;5.3</a>)
    … …  
    39943972      <p id="rfc.section.C.p.26">Remove discussion of Content-Disposition header field, it is now defined by <a href="#RFC6266" id="rfc.xref.RFC6266.2"><cite title="Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)">[RFC6266]</cite></a>. (<a href="#additional.features" title="Additional Features">Appendix&nbsp;B</a>)
    39953973      </p>
    3996       <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    3997       <div id="rfc.figure.u.64"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
     3974      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
     3975      <p id="rfc.section.D.p.1">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     3976         (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR
     3977         (any visible US-ASCII character).
     3978      </p>
     3979      <p id="rfc.section.D.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.47"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>:
     3980      </p>
     3981      <div id="rfc.figure.u.62"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">BWS</a>           = &lt;BWS, defined in <a href="#Part1" id="rfc.xref.Part1.48"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     3982  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.49"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     3983  <a href="#imported.abnf" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#Part1" id="rfc.xref.Part1.50"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     3984  <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.51"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     3985  <a href="#imported.abnf" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.52"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     3986  <a href="#imported.abnf" class="smpl">word</a>          = &lt;word, defined in <a href="#Part1" id="rfc.xref.Part1.53"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     3987
     3988  <a href="#imported.abnf" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.54"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>&gt;
     3989  <a href="#imported.abnf" class="smpl">comment</a>       = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.55"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     3990  <a href="#imported.abnf" class="smpl">partial-URI</a>   = &lt;partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.56"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>&gt;
     3991  <a href="#imported.abnf" class="smpl">qvalue</a>        = &lt;qvalue, defined in <a href="#Part1" id="rfc.xref.Part1.57"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#quality.values" title="Quality Values">Section 4.3.1</a>&gt;
     3992  <a href="#imported.abnf" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.58"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>&gt;
     3993</pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     3994      <div id="rfc.figure.u.63"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
    39983995 OWS ( media-range [ accept-params ] ) ] ) ]
    39993996<a href="#header.accept-charset" class="smpl">Accept-Charset</a> = *( "," OWS ) ( ( charset / "*" ) [ OWS ";" OWS "q="
    … …  
    40074004<a href="#header.allow" class="smpl">Allow</a> = [ ( "," / method ) *( OWS "," [ OWS method ] ) ]
    40084005
    4009 <a href="#core.rules" class="smpl">BWS</a> = &lt;BWS, defined in [Part1], Section 3.2.1&gt;
     4006<a href="#imported.abnf" class="smpl">BWS</a> = &lt;BWS, defined in [Part1], Section 3.2.1&gt;
    40104007
    40114008<a href="#header.content-encoding" class="smpl">Content-Encoding</a> = *( "," OWS ) content-coding *( OWS "," [ OWS
    … …  
    40314028<a href="#header.max-forwards" class="smpl">Max-Forwards</a> = 1*DIGIT
    40324029
    4033 <a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
     4030<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
    40344031
    4035 <a href="#core.rules" class="smpl">RWS</a> = &lt;RWS, defined in [Part1], Section 3.2.1&gt;
     4032<a href="#imported.abnf" class="smpl">RWS</a> = &lt;RWS, defined in [Part1], Section 3.2.1&gt;
    40364033<a href="#header.referer" class="smpl">Referer</a> = absolute-URI / partial-URI
    40374034<a href="#header.retry-after" class="smpl">Retry-After</a> = HTTP-date / delta-seconds
    … …  
    40394036<a href="#header.server" class="smpl">Server</a> = product *( RWS ( product / comment ) )
    40404037
    4041 <a href="#abnf.dependencies" class="smpl">URI-reference</a> = &lt;URI-reference, defined in [Part1], Section 2.8&gt;
     4038<a href="#imported.abnf" class="smpl">URI-reference</a> = &lt;URI-reference, defined in [Part1], Section 2.8&gt;
    40424039<a href="#header.user-agent" class="smpl">User-Agent</a> = product *( RWS ( product / comment ) )
    40434040
    4044 <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [Part1], Section 2.8&gt;
     4041<a href="#imported.abnf" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [Part1], Section 2.8&gt;
    40454042<a href="#header.accept" class="smpl">accept-ext</a> = OWS ";" OWS token [ "=" word ]
    40464043<a href="#header.accept" class="smpl">accept-params</a> = OWS ";" OWS "q=" qvalue *accept-ext
    … …  
    40504047<a href="#rule.charset" class="smpl">charset</a> = token
    40514048<a href="#header.accept-encoding" class="smpl">codings</a> = content-coding / "identity" / "*"
    4052 <a href="#abnf.dependencies" class="smpl">comment</a> = &lt;comment, defined in [Part1], Section 3.2.4&gt;
     4049<a href="#imported.abnf" class="smpl">comment</a> = &lt;comment, defined in [Part1], Section 3.2.4&gt;
    40534050<a href="#content.codings" class="smpl">content-coding</a> = token
    40544051
    … …  
    41064103
    41074104<a href="#rule.parameter" class="smpl">parameter</a> = attribute "=" value
    4108 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = &lt;partial-URI, defined in [Part1], Section 2.8&gt;
     4105<a href="#imported.abnf" class="smpl">partial-URI</a> = &lt;partial-URI, defined in [Part1], Section 2.8&gt;
    41094106<a href="#product.tokens" class="smpl">product</a> = token [ "/" product-version ]
    41104107<a href="#product.tokens" class="smpl">product-version</a> = token
    41114108
    4112 <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
    4113 <a href="#abnf.dependencies" class="smpl">qvalue</a> = &lt;qvalue, defined in [Part1], Section 4.3.1&gt;
     4109<a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
     4110<a href="#imported.abnf" class="smpl">qvalue</a> = &lt;qvalue, defined in [Part1], Section 4.3.1&gt;
    41144111
    41154112<a href="#preferred.date.format" class="smpl">rfc1123-date</a> = day-name "," SP date1 SP time-of-day SP GMT
    … …  
    41204117
    41214118<a href="#preferred.date.format" class="smpl">time-of-day</a> = hour ":" minute ":" second
    4122 <a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
     4119<a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
    41234120<a href="#media.types" class="smpl">type</a> = token
    41244121
    41254122<a href="#rule.parameter" class="smpl">value</a> = word
    41264123
    4127 <a href="#core.rules" class="smpl">word</a> = &lt;word, defined in [Part1], Section 3.2.4&gt;
     4124<a href="#imported.abnf" class="smpl">word</a> = &lt;word, defined in [Part1], Section 3.2.4&gt;
    41284125
    41294126<a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT
    4130 </pre> <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    4131       <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;Since RFC 2616
     4127</pre> <h1 id="rfc.section.F"><a href="#rfc.section.F">F.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     4128      <h2 id="rfc.section.F.1"><a href="#rfc.section.F.1">F.1</a>&nbsp;Since RFC 2616
    41324129      </h2>
    4133       <p id="rfc.section.E.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    4134       </p>
    4135       <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
     4130      <p id="rfc.section.F.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     4131      </p>
     4132      <h2 id="rfc.section.F.2"><a href="#rfc.section.F.2">F.2</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
    41364133      </h2>
    4137       <p id="rfc.section.E.2.p.1">Closed issues: </p>
     4134      <p id="rfc.section.F.2.p.1">Closed issues: </p>
    41384135      <ul>
    41394136         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/5">http://tools.ietf.org/wg/httpbis/trac/ticket/5</a>&gt;: "Via is a MUST" (&lt;<a href="http://purl.org/NET/http-errata#via-must">http://purl.org/NET/http-errata#via-must</a>&gt;)
    … …  
    41544151         </li>
    41554152      </ul>
    4156       <p id="rfc.section.E.2.p.2">Other changes: </p>
     4153      <p id="rfc.section.F.2.p.2">Other changes: </p>
    41574154      <ul>
    41584155         <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.14"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>
    41594156         </li>
    41604157      </ul>
    4161       <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
     4158      <h2 id="rfc.section.F.3"><a href="#rfc.section.F.3">F.3</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
    41624159      </h2>
    4163       <p id="rfc.section.E.3.p.1">Closed issues: </p>
     4160      <p id="rfc.section.F.3.p.1">Closed issues: </p>
    41644161      <ul>
    41654162         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/8">http://tools.ietf.org/wg/httpbis/trac/ticket/8</a>&gt;: "Media Type Registrations" (&lt;<a href="http://purl.org/NET/http-errata#media-reg">http://purl.org/NET/http-errata#media-reg</a>&gt;)
    … …  
    41864183         </li>
    41874184      </ul>
    4188       <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
     4185      <h2 id="rfc.section.F.4"><a href="#rfc.section.F.4">F.4</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
    41894186      </h2>
    4190       <p id="rfc.section.E.4.p.1">Closed issues: </p>
     4187      <p id="rfc.section.F.4.p.1">Closed issues: </p>
    41914188      <ul>
    41924189         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/21">http://tools.ietf.org/wg/httpbis/trac/ticket/21</a>&gt;: "PUT side effects"
    … …  
    41954192         </li>
    41964193      </ul>
    4197       <p id="rfc.section.E.4.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4194      <p id="rfc.section.F.4.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    41984195      </p>
    41994196      <ul>
    … …  
    42024199         <li>Copy definition of delta-seconds from Part6 instead of referencing it.</li>
    42034200      </ul>
    4204       <h2 id="rfc.section.E.5"><a href="#rfc.section.E.5">E.5</a>&nbsp;Since draft-ietf-httpbis-p3-payload-01
     4201      <h2 id="rfc.section.F.5"><a href="#rfc.section.F.5">F.5</a>&nbsp;Since draft-ietf-httpbis-p3-payload-01
    42054202      </h2>
    4206       <p id="rfc.section.E.5.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4203      <p id="rfc.section.F.5.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    42074204      </p>
    42084205      <ul>
    42094206         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    42104207      </ul>
    4211       <h2 id="rfc.section.E.6"><a href="#rfc.section.E.6">E.6</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></h2>
    4212       <p id="rfc.section.E.6.p.1">Closed issues: </p>
     4208      <h2 id="rfc.section.F.6"><a href="#rfc.section.F.6">F.6</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></h2>
     4209      <p id="rfc.section.F.6.p.1">Closed issues: </p>
    42134210      <ul>
    42144211         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/24">http://tools.ietf.org/wg/httpbis/trac/ticket/24</a>&gt;: "Requiring Allow in 405 responses"
    … …  
    42274224         </li>
    42284225      </ul>
    4229       <p id="rfc.section.E.6.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     4226      <p id="rfc.section.F.6.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    42304227      </p>
    42314228      <ul>
    42324229         <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
    42334230      </ul>
    4234       <p id="rfc.section.E.6.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4231      <p id="rfc.section.F.6.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    42354232      </p>
    42364233      <ul>
    42374234         <li>Replace string literals when the string really is case-sensitive (method).</li>
    42384235      </ul>
    4239       <h2 id="rfc.section.E.7"><a href="#rfc.section.E.7">E.7</a>&nbsp;<a id="changes.3.since.02" href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h2>
    4240       <p id="rfc.section.E.7.p.1">Closed issues: </p>
     4236      <h2 id="rfc.section.F.7"><a href="#rfc.section.F.7">F.7</a>&nbsp;<a id="changes.3.since.02" href="#changes.3.since.02">Since draft-ietf-httpbis-p3-payload-02</a></h2>
     4237      <p id="rfc.section.F.7.p.1">Closed issues: </p>
    42414238      <ul>
    42424239         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
    … …  
    42474244         </li>
    42484245      </ul>
    4249       <p id="rfc.section.E.7.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
     4246      <p id="rfc.section.F.7.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    42504247      </p>
    42514248      <ul>
    42524249         <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
    42534250      </ul>
    4254       <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>
    4255       <p id="rfc.section.E.8.p.1">Closed issues: </p>
     4251      <h2 id="rfc.section.F.8"><a href="#rfc.section.F.8">F.8</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>
     4252      <p id="rfc.section.F.8.p.1">Closed issues: </p>
    42564253      <ul>
    42574254         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/98">http://tools.ietf.org/wg/httpbis/trac/ticket/98</a>&gt;: "OPTIONS request bodies"
    … …  
    42624259         </li>
    42634260      </ul>
    4264       <p id="rfc.section.E.8.p.2">Ongoing work on Method Registry (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
     4261      <p id="rfc.section.F.8.p.2">Ongoing work on Method Registry (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
    42654262      </p>
    42664263      <ul>
    42674264         <li>Added initial proposal for registration process, plus initial content (non-HTTP/1.1 methods to be added by a separate specification).</li>
    42684265      </ul>
    4269       <h2 id="rfc.section.E.9"><a href="#rfc.section.E.9">E.9</a>&nbsp;<a id="changes.3.since.03" href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></h2>
    4270       <p id="rfc.section.E.9.p.1">Closed issues: </p>
     4266      <h2 id="rfc.section.F.9"><a href="#rfc.section.F.9">F.9</a>&nbsp;<a id="changes.3.since.03" href="#changes.3.since.03">Since draft-ietf-httpbis-p3-payload-03</a></h2>
     4267      <p id="rfc.section.F.9.p.1">Closed issues: </p>
    42714268      <ul>
    42724269         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/67">http://tools.ietf.org/wg/httpbis/trac/ticket/67</a>&gt;: "Quoting Charsets"
    … …  
    42774274         </li>
    42784275      </ul>
    4279       <p id="rfc.section.E.9.p.2">Other changes: </p>
     4276      <p id="rfc.section.F.9.p.2">Other changes: </p>
    42804277      <ul>
    42814278         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/68">http://tools.ietf.org/wg/httpbis/trac/ticket/68</a>&gt;: "Encoding References Normative" — rephrase the annotation and reference BCP97.
    42824279         </li>
    42834280      </ul>
    4284       <h2 id="rfc.section.E.10"><a href="#rfc.section.E.10">E.10</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2>
    4285       <p id="rfc.section.E.10.p.1">Closed issues: </p>
     4281      <h2 id="rfc.section.F.10"><a href="#rfc.section.F.10">F.10</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2>
     4282      <p id="rfc.section.F.10.p.1">Closed issues: </p>
    42864283      <ul>
    42874284         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/103">http://tools.ietf.org/wg/httpbis/trac/ticket/103</a>&gt;: "Content-*"
    … …  
    42904287         </li>
    42914288      </ul>
    4292       <p id="rfc.section.E.10.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4289      <p id="rfc.section.F.10.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    42934290      </p>
    42944291      <ul>
    … …  
    42974294         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    42984295      </ul>
    4299       <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a id="changes.3.since.04" href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h2>
    4300       <p id="rfc.section.E.11.p.1">Closed issues: </p>
     4296      <h2 id="rfc.section.F.11"><a href="#rfc.section.F.11">F.11</a>&nbsp;<a id="changes.3.since.04" href="#changes.3.since.04">Since draft-ietf-httpbis-p3-payload-04</a></h2>
     4297      <p id="rfc.section.F.11.p.1">Closed issues: </p>
    43014298      <ul>
    43024299         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
    43034300         </li>
    43044301      </ul>
    4305       <p id="rfc.section.E.11.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4302      <p id="rfc.section.F.11.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    43064303      </p>
    43074304      <ul>
    … …  
    43104307         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    43114308      </ul>
    4312       <h2 id="rfc.section.E.12"><a href="#rfc.section.E.12">E.12</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></h2>
    4313       <p id="rfc.section.E.12.p.1">Closed issues: </p>
     4309      <h2 id="rfc.section.F.12"><a href="#rfc.section.F.12">F.12</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></h2>
     4310      <p id="rfc.section.F.12.p.1">Closed issues: </p>
    43144311      <ul>
    43154312         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/94">http://tools.ietf.org/wg/httpbis/trac/ticket/94</a>&gt;: "reason-phrase BNF"
    43164313         </li>
    43174314      </ul>
    4318       <p id="rfc.section.E.12.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4315      <p id="rfc.section.F.12.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    43194316      </p>
    43204317      <ul>
    43214318         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    43224319      </ul>
    4323       <h2 id="rfc.section.E.13"><a href="#rfc.section.E.13">E.13</a>&nbsp;<a id="changes.3.since.05" href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h2>
    4324       <p id="rfc.section.E.13.p.1">Closed issues: </p>
     4320      <h2 id="rfc.section.F.13"><a href="#rfc.section.F.13">F.13</a>&nbsp;<a id="changes.3.since.05" href="#changes.3.since.05">Since draft-ietf-httpbis-p3-payload-05</a></h2>
     4321      <p id="rfc.section.F.13.p.1">Closed issues: </p>
    43254322      <ul>
    43264323         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/118">http://tools.ietf.org/wg/httpbis/trac/ticket/118</a>&gt;: "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
    43274324         </li>
    43284325      </ul>
    4329       <p id="rfc.section.E.13.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     4326      <p id="rfc.section.F.13.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    43304327      </p>
    43314328      <ul>
    43324329         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    43334330      </ul>
    4334       <p id="rfc.section.E.13.p.3">Other changes: </p>
     4331      <p id="rfc.section.F.13.p.3">Other changes: </p>
    43354332      <ul>
    43364333         <li>Move definition of quality values into Part 1.</li>
    43374334      </ul>
    4338       <h2 id="rfc.section.E.14"><a href="#rfc.section.E.14">E.14</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></h2>
    4339       <p id="rfc.section.E.14.p.1">Closed issues: </p>
     4335      <h2 id="rfc.section.F.14"><a href="#rfc.section.F.14">F.14</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></h2>
     4336      <p id="rfc.section.F.14.p.1">Closed issues: </p>
    43404337      <ul>
    43414338         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/144">http://tools.ietf.org/wg/httpbis/trac/ticket/144</a>&gt;: "Clarify when Referer is sent"
    … …  
    43464343         </li>
    43474344      </ul>
    4348       <h2 id="rfc.section.E.15"><a href="#rfc.section.E.15">E.15</a>&nbsp;<a id="changes.3.since.06" href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h2>
    4349       <p id="rfc.section.E.15.p.1">Closed issues: </p>
     4345      <h2 id="rfc.section.F.15"><a href="#rfc.section.F.15">F.15</a>&nbsp;<a id="changes.3.since.06" href="#changes.3.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h2>
     4346      <p id="rfc.section.F.15.p.1">Closed issues: </p>
    43504347      <ul>
    43514348         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special"
    … …  
    43544351         </li>
    43554352      </ul>
    4356       <h2 id="rfc.section.E.16"><a href="#rfc.section.E.16">E.16</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></h2>
    4357       <p id="rfc.section.E.16.p.1">Closed issues: </p>
     4353      <h2 id="rfc.section.F.16"><a href="#rfc.section.F.16">F.16</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></h2>
     4354      <p id="rfc.section.F.16.p.1">Closed issues: </p>
    43584355      <ul>
    43594356         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/27">http://tools.ietf.org/wg/httpbis/trac/ticket/27</a>&gt;: "Idempotency"
    … …  
    43744371         </li>
    43754372      </ul>
    4376       <p id="rfc.section.E.16.p.2">Partly resolved issues: </p>
     4373      <p id="rfc.section.F.16.p.2">Partly resolved issues: </p>
    43774374      <ul>
    43784375         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/171">http://tools.ietf.org/wg/httpbis/trac/ticket/171</a>&gt;: "Are OPTIONS and TRACE safe?"
    43794376         </li>
    43804377      </ul>
    4381       <h2 id="rfc.section.E.17"><a href="#rfc.section.E.17">E.17</a>&nbsp;<a id="changes.3.since.07" href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></h2>
    4382       <p id="rfc.section.E.17.p.1">Closed issues: </p>
     4378      <h2 id="rfc.section.F.17"><a href="#rfc.section.F.17">F.17</a>&nbsp;<a id="changes.3.since.07" href="#changes.3.since.07">Since draft-ietf-httpbis-p3-payload-07</a></h2>
     4379      <p id="rfc.section.F.17.p.1">Closed issues: </p>
    43834380      <ul>
    43844381         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/13">http://tools.ietf.org/wg/httpbis/trac/ticket/13</a>&gt;: "Updated reference for language tags"
    … …  
    43954392         </li>
    43964393      </ul>
    4397       <p id="rfc.section.E.17.p.2">Partly resolved issues: </p>
     4394      <p id="rfc.section.F.17.p.2">Partly resolved issues: </p>
    43984395      <ul>
    43994396         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/148">http://tools.ietf.org/wg/httpbis/trac/ticket/148</a>&gt;: "update IANA requirements wrt Transfer-Coding values" (add the IANA Considerations subsection)
    … …  
    44024399         </li>
    44034400      </ul>
    4404       <h2 id="rfc.section.E.18"><a href="#rfc.section.E.18">E.18</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></h2>
    4405       <p id="rfc.section.E.18.p.1">Closed issues: </p>
     4401      <h2 id="rfc.section.F.18"><a href="#rfc.section.F.18">F.18</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></h2>
     4402      <p id="rfc.section.F.18.p.1">Closed issues: </p>
    44064403      <ul>
    44074404         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/10">http://tools.ietf.org/wg/httpbis/trac/ticket/10</a>&gt;: "Safe Methods vs Redirection" (we missed the introduction to the <a href="#status.3xx" class="smpl">3xx</a> status codes when fixing this previously)
    44084405         </li>
    44094406      </ul>
    4410       <h2 id="rfc.section.E.19"><a href="#rfc.section.E.19">E.19</a>&nbsp;<a id="changes.3.since.08" href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></h2>
    4411       <p id="rfc.section.E.19.p.1">Closed issues: </p>
     4407      <h2 id="rfc.section.F.19"><a href="#rfc.section.F.19">F.19</a>&nbsp;<a id="changes.3.since.08" href="#changes.3.since.08">Since draft-ietf-httpbis-p3-payload-08</a></h2>
     4408      <p id="rfc.section.F.19.p.1">Closed issues: </p>
    44124409      <ul>
    44134410         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/81">http://tools.ietf.org/wg/httpbis/trac/ticket/81</a>&gt;: "Content Negotiation for media types"
    … …  
    44164413         </li>
    44174414      </ul>
    4418       <h2 id="rfc.section.E.20"><a href="#rfc.section.E.20">E.20</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></h2>
    4419       <p id="rfc.section.E.20.p.1">Closed issues: </p>
     4415      <h2 id="rfc.section.F.20"><a href="#rfc.section.F.20">F.20</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></h2>
     4416      <p id="rfc.section.F.20.p.1">Closed issues: </p>
    44204417      <ul>
    44214418         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>&gt;: "Fragment combination / precedence during redirects"
    44224419         </li>
    44234420      </ul>
    4424       <p id="rfc.section.E.20.p.2">Partly resolved issues: </p>
     4421      <p id="rfc.section.F.20.p.2">Partly resolved issues: </p>
    44254422      <ul>
    44264423         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header field payload handling"
    … …  
    44294426         </li>
    44304427      </ul>
    4431       <h2 id="rfc.section.E.21"><a href="#rfc.section.E.21">E.21</a>&nbsp;<a id="changes.3.since.09" href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></h2>
    4432       <p id="rfc.section.E.21.p.1">Closed issues: </p>
     4428      <h2 id="rfc.section.F.21"><a href="#rfc.section.F.21">F.21</a>&nbsp;<a id="changes.3.since.09" href="#changes.3.since.09">Since draft-ietf-httpbis-p3-payload-09</a></h2>
     4429      <p id="rfc.section.F.21.p.1">Closed issues: </p>
    44334430      <ul>
    44344431         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/122">http://tools.ietf.org/wg/httpbis/trac/ticket/122</a>&gt;: "MIME-Version not listed in P1, general header fields"
    … …  
    44414438         </li>
    44424439      </ul>
    4443       <p id="rfc.section.E.21.p.2">Partly resolved issues: </p>
     4440      <p id="rfc.section.F.21.p.2">Partly resolved issues: </p>
    44444441      <ul>
    44454442         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
    44464443         </li>
    44474444      </ul>
    4448       <h2 id="rfc.section.E.22"><a href="#rfc.section.E.22">E.22</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></h2>
    4449       <p id="rfc.section.E.22.p.1">Closed issues: </p>
     4445      <h2 id="rfc.section.F.22"><a href="#rfc.section.F.22">F.22</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></h2>
     4446      <p id="rfc.section.F.22.p.1">Closed issues: </p>
    44504447      <ul>
    44514448         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
    … …  
    44624459         </li>
    44634460      </ul>
    4464       <h2 id="rfc.section.E.23"><a href="#rfc.section.E.23">E.23</a>&nbsp;<a id="changes.3.since.10" href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></h2>
    4465       <p id="rfc.section.E.23.p.1">Closed issues: </p>
     4461      <h2 id="rfc.section.F.23"><a href="#rfc.section.F.23">F.23</a>&nbsp;<a id="changes.3.since.10" href="#changes.3.since.10">Since draft-ietf-httpbis-p3-payload-10</a></h2>
     4462      <p id="rfc.section.F.23.p.1">Closed issues: </p>
    44664463      <ul>
    44674464         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
    … …  
    44824479         </li>
    44834480      </ul>
    4484       <p id="rfc.section.E.23.p.2">Partly resolved issues: </p>
     4481      <p id="rfc.section.F.23.p.2">Partly resolved issues: </p>
    44854482      <ul>
    44864483         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/178">http://tools.ietf.org/wg/httpbis/trac/ticket/178</a>&gt;: "Content-MD5 and partial responses"
    44874484         </li>
    44884485      </ul>
    4489       <h2 id="rfc.section.E.24"><a href="#rfc.section.E.24">E.24</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></h2>
    4490       <p id="rfc.section.E.24.p.1">Closed issues: </p>
     4486      <h2 id="rfc.section.F.24"><a href="#rfc.section.F.24">F.24</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></h2>
     4487      <p id="rfc.section.F.24.p.1">Closed issues: </p>
    44914488      <ul>
    44924489         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/229">http://tools.ietf.org/wg/httpbis/trac/ticket/229</a>&gt;: "Considerations for new status codes"
    … …  
    44974494         </li>
    44984495      </ul>
    4499       <h2 id="rfc.section.E.25"><a href="#rfc.section.E.25">E.25</a>&nbsp;<a id="changes.3.since.11" href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></h2>
    4500       <p id="rfc.section.E.25.p.1">Closed issues: </p>
     4496      <h2 id="rfc.section.F.25"><a href="#rfc.section.F.25">F.25</a>&nbsp;<a id="changes.3.since.11" href="#changes.3.since.11">Since draft-ietf-httpbis-p3-payload-11</a></h2>
     4497      <p id="rfc.section.F.25.p.1">Closed issues: </p>
    45014498      <ul>
    45024499         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/123">http://tools.ietf.org/wg/httpbis/trac/ticket/123</a>&gt;: "Factor out Content-Disposition"
    45034500         </li>
    45044501      </ul>
    4505       <h2 id="rfc.section.E.26"><a href="#rfc.section.E.26">E.26</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></h2>
    4506       <p id="rfc.section.E.26.p.1">Closed issues: </p>
     4502      <h2 id="rfc.section.F.26"><a href="#rfc.section.F.26">F.26</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p2-semantics-12</a></h2>
     4503      <p id="rfc.section.F.26.p.1">Closed issues: </p>
    45074504      <ul>
    45084505         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/43">http://tools.ietf.org/wg/httpbis/trac/ticket/43</a>&gt;: "Fragment combination / precedence during redirects" (added warning about having a fragid on the redirect might cause inconvenience
    … …  
    45464543         </li>
    45474544      </ul>
    4548       <h2 id="rfc.section.E.27"><a href="#rfc.section.E.27">E.27</a>&nbsp;<a id="changes.3.since.12" href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></h2>
    4549       <p id="rfc.section.E.27.p.1">Closed issues: </p>
     4545      <h2 id="rfc.section.F.27"><a href="#rfc.section.F.27">F.27</a>&nbsp;<a id="changes.3.since.12" href="#changes.3.since.12">Since draft-ietf-httpbis-p3-payload-12</a></h2>
     4546      <p id="rfc.section.F.27.p.1">Closed issues: </p>
    45504547      <ul>
    45514548         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Field Classification"
    … …  
    45564553         </li>
    45574554      </ul>
    4558       <h2 id="rfc.section.E.28"><a href="#rfc.section.E.28">E.28</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></h2>
    4559       <p id="rfc.section.E.28.p.1">Closed issues: </p>
     4555      <h2 id="rfc.section.F.28"><a href="#rfc.section.F.28">F.28</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p2-semantics-13</a></h2>
     4556      <p id="rfc.section.F.28.p.1">Closed issues: </p>
    45604557      <ul>
    45614558         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
    … …  
    45644561         </li>
    45654562      </ul>
    4566       <h2 id="rfc.section.E.29"><a href="#rfc.section.E.29">E.29</a>&nbsp;<a id="changes.3.since.13" href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></h2>
    4567       <p id="rfc.section.E.29.p.1">Closed issues: </p>
     4563      <h2 id="rfc.section.F.29"><a href="#rfc.section.F.29">F.29</a>&nbsp;<a id="changes.3.since.13" href="#changes.3.since.13">Since draft-ietf-httpbis-p3-payload-13</a></h2>
     4564      <p id="rfc.section.F.29.p.1">Closed issues: </p>
    45684565      <ul>
    45694566         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/20">http://tools.ietf.org/wg/httpbis/trac/ticket/20</a>&gt;: "Default charsets for text media types"
    … …  
    45764573         </li>
    45774574      </ul>
    4578       <h2 id="rfc.section.E.30"><a href="#rfc.section.E.30">E.30</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></h2>
    4579       <p id="rfc.section.E.30.p.1">Closed issues: </p>
     4575      <h2 id="rfc.section.F.30"><a href="#rfc.section.F.30">F.30</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p2-semantics-14</a></h2>
     4576      <p id="rfc.section.F.30.p.1">Closed issues: </p>
    45804577      <ul>
    45814578         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/255">http://tools.ietf.org/wg/httpbis/trac/ticket/255</a>&gt;: "Clarify status code for rate limiting"
    … …  
    45884585         </li>
    45894586      </ul>
    4590       <h2 id="rfc.section.E.31"><a href="#rfc.section.E.31">E.31</a>&nbsp;<a id="changes.3.since.14" href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></h2>
    4591       <p id="rfc.section.E.31.p.1">None.</p>
    4592       <h2 id="rfc.section.E.32"><a href="#rfc.section.E.32">E.32</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></h2>
    4593       <p id="rfc.section.E.32.p.1">Closed issues: </p>
     4587      <h2 id="rfc.section.F.31"><a href="#rfc.section.F.31">F.31</a>&nbsp;<a id="changes.3.since.14" href="#changes.3.since.14">Since draft-ietf-httpbis-p3-payload-14</a></h2>
     4588      <p id="rfc.section.F.31.p.1">None.</p>
     4589      <h2 id="rfc.section.F.32"><a href="#rfc.section.F.32">F.32</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p2-semantics-15</a></h2>
     4590      <p id="rfc.section.F.32.p.1">Closed issues: </p>
    45944591      <ul>
    45954592         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/285">http://tools.ietf.org/wg/httpbis/trac/ticket/285</a>&gt;: "Strength of requirements on Accept re: 406"
    … …  
    45984595         </li>
    45994596      </ul>
    4600       <h2 id="rfc.section.E.33"><a href="#rfc.section.E.33">E.33</a>&nbsp;<a id="changes.3.since.15" href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></h2>
    4601       <p id="rfc.section.E.33.p.1">Closed issues: </p>
     4597      <h2 id="rfc.section.F.33"><a href="#rfc.section.F.33">F.33</a>&nbsp;<a id="changes.3.since.15" href="#changes.3.since.15">Since draft-ietf-httpbis-p3-payload-15</a></h2>
     4598      <p id="rfc.section.F.33.p.1">Closed issues: </p>
    46024599      <ul>
    46034600         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/285">http://tools.ietf.org/wg/httpbis/trac/ticket/285</a>&gt;: "Strength of requirements on Accept re: 406"
    46044601         </li>
    46054602      </ul>
    4606       <h2 id="rfc.section.E.34"><a href="#rfc.section.E.34">E.34</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></h2>
    4607       <p id="rfc.section.E.34.p.1">Closed issues: </p>
     4603      <h2 id="rfc.section.F.34"><a href="#rfc.section.F.34">F.34</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p2-semantics-16</a></h2>
     4604      <p id="rfc.section.F.34.p.1">Closed issues: </p>
    46084605      <ul>
    46094606         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/160">http://tools.ietf.org/wg/httpbis/trac/ticket/160</a>&gt;: "Redirects and non-GET methods"
    … …  
    46164613         </li>
    46174614      </ul>
    4618       <h2 id="rfc.section.E.35"><a href="#rfc.section.E.35">E.35</a>&nbsp;<a id="changes.3.since.16" href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></h2>
    4619       <p id="rfc.section.E.35.p.1">Closed issues: </p>
     4615      <h2 id="rfc.section.F.35"><a href="#rfc.section.F.35">F.35</a>&nbsp;<a id="changes.3.since.16" href="#changes.3.since.16">Since draft-ietf-httpbis-p3-payload-16</a></h2>
     4616      <p id="rfc.section.F.35.p.1">Closed issues: </p>
    46204617      <ul>
    46214618         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>&gt;: "Document HTTP's error-handling philosophy"
    46224619         </li>
    46234620      </ul>
    4624       <h2 id="rfc.section.E.36"><a href="#rfc.section.E.36">E.36</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></h2>
    4625       <p id="rfc.section.E.36.p.1">Closed issues: </p>
     4621      <h2 id="rfc.section.F.36"><a href="#rfc.section.F.36">F.36</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p2-semantics-17</a></h2>
     4622      <p id="rfc.section.F.36.p.1">Closed issues: </p>
    46264623      <ul>
    46274624         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/185">http://tools.ietf.org/wg/httpbis/trac/ticket/185</a>&gt;: "Location header field payload handling"
    … …  
    46384635         </li>
    46394636      </ul>
    4640       <h2 id="rfc.section.E.37"><a href="#rfc.section.E.37">E.37</a>&nbsp;<a id="changes.3.since.17" href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></h2>
    4641       <p id="rfc.section.E.37.p.1">Closed issues: </p>
     4637      <h2 id="rfc.section.F.37"><a href="#rfc.section.F.37">F.37</a>&nbsp;<a id="changes.3.since.17" href="#changes.3.since.17">Since draft-ietf-httpbis-p3-payload-17</a></h2>
     4638      <p id="rfc.section.F.37.p.1">Closed issues: </p>
    46424639      <ul>
    46434640         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/323">http://tools.ietf.org/wg/httpbis/trac/ticket/323</a>&gt;: "intended maturity level vs normative references"
    46444641         </li>
    46454642      </ul>
    4646       <h2 id="rfc.section.E.38"><a href="#rfc.section.E.38">E.38</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></h2>
    4647       <p id="rfc.section.E.38.p.1">Closed issues: </p>
     4643      <h2 id="rfc.section.F.38"><a href="#rfc.section.F.38">F.38</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></h2>
     4644      <p id="rfc.section.F.38.p.1">Closed issues: </p>
    46484645      <ul>
    46494646         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/227">http://tools.ietf.org/wg/httpbis/trac/ticket/227</a>&gt;: "Combining HEAD responses"
    … …  
    46664663         </li>
    46674664      </ul>
    4668       <h2 id="rfc.section.E.39"><a href="#rfc.section.E.39">E.39</a>&nbsp;<a id="changes.3.since.18" href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></h2>
    4669       <p id="rfc.section.E.39.p.1">Closed issues: </p>
     4665      <h2 id="rfc.section.F.39"><a href="#rfc.section.F.39">F.39</a>&nbsp;<a id="changes.3.since.18" href="#changes.3.since.18">Since draft-ietf-httpbis-p3-payload-18</a></h2>
     4666      <p id="rfc.section.F.39.p.1">Closed issues: </p>
    46704667      <ul>
    46714668         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/330">http://tools.ietf.org/wg/httpbis/trac/ticket/330</a>&gt;: "is ETag a representation header field?"
    … …  
    46764673         </li>
    46774674      </ul>
    4678       <h2 id="rfc.section.E.40"><a href="#rfc.section.E.40">E.40</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19 and draft-ietf-httpbis-p3-payload-19</a></h2>
    4679       <p id="rfc.section.E.40.p.1">Closed issues: </p>
     4675      <h2 id="rfc.section.F.40"><a href="#rfc.section.F.40">F.40</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p2-semantics-19 and draft-ietf-httpbis-p3-payload-19</a></h2>
     4676      <p id="rfc.section.F.40.p.1">Closed issues: </p>
    46804677      <ul>
    46814678         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/312">http://tools.ietf.org/wg/httpbis/trac/ticket/312</a>&gt;: "should there be a permanent variant of 307"
    … …  
    49244921            </li>
    49254922            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    4926                   <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">1.2.2</a>, <a href="#rfc.xref.Part1.16">2</a>, <a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.20">2.3.7</a>, <a href="#rfc.xref.Part1.21">2.3.8</a>, <a href="#rfc.xref.Part1.22">3</a>, <a href="#rfc.xref.Part1.23">3.1</a>, <a href="#rfc.xref.Part1.24">3.1</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.26">3.1</a>, <a href="#rfc.xref.Part1.27">3.1</a>, <a href="#rfc.xref.Part1.28">3.2</a>, <a href="#rfc.xref.Part1.29">3.2</a>, <a href="#rfc.xref.Part1.30">3.3</a>, <a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.33">4.4.4</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.35">4.6.15</a>, <a href="#rfc.xref.Part1.36">4.7.6</a>, <a href="#rfc.xref.Part1.37">5.4</a>, <a href="#rfc.xref.Part1.38">5.4</a>, <a href="#rfc.xref.Part1.39">5.4</a>, <a href="#rfc.xref.Part1.40">5.4.1</a>, <a href="#rfc.xref.Part1.41">5.4.1</a>, <a href="#rfc.xref.Part1.42">6.1</a>, <a href="#rfc.xref.Part1.43">6.2</a>, <a href="#rfc.xref.Part1.44">7</a>, <a href="#rfc.xref.Part1.45">7.1</a>, <a href="#rfc.xref.Part1.46">8.1</a>, <a href="#rfc.xref.Part1.47">9.1</a>, <a href="#rfc.xref.Part1.48">9.3</a>, <a href="#rfc.xref.Part1.49">9.8</a>, <a href="#rfc.xref.Part1.50">9.11</a>, <a href="#rfc.xref.Part1.51">9.17</a>, <a href="#rfc.xref.Part1.52">9.17</a>, <a href="#rfc.xref.Part1.53">9.18</a>, <a href="#rfc.xref.Part1.54">10.4</a>, <a href="#rfc.xref.Part1.55">10.4</a>, <a href="#rfc.xref.Part1.56">10.4</a>, <a href="#rfc.xref.Part1.57">12</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.58">C</a><ul>
     4923                  <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">2</a>, <a href="#rfc.xref.Part1.5">2.2.1</a>, <a href="#rfc.xref.Part1.6">2.3.1</a>, <a href="#rfc.xref.Part1.7">2.3.7</a>, <a href="#rfc.xref.Part1.8">2.3.7</a>, <a href="#rfc.xref.Part1.9">2.3.8</a>, <a href="#rfc.xref.Part1.10">3</a>, <a href="#rfc.xref.Part1.11">3.1</a>, <a href="#rfc.xref.Part1.12">3.1</a>, <a href="#rfc.xref.Part1.13">3.1</a>, <a href="#rfc.xref.Part1.14">3.1</a>, <a href="#rfc.xref.Part1.15">3.1</a>, <a href="#rfc.xref.Part1.16">3.2</a>, <a href="#rfc.xref.Part1.17">3.2</a>, <a href="#rfc.xref.Part1.18">3.3</a>, <a href="#rfc.xref.Part1.19">4.3.1</a>, <a href="#rfc.xref.Part1.20">4.3.2</a>, <a href="#rfc.xref.Part1.21">4.4.4</a>, <a href="#rfc.xref.Part1.22">4.4.6</a>, <a href="#rfc.xref.Part1.23">4.6.15</a>, <a href="#rfc.xref.Part1.24">4.7.6</a>, <a href="#rfc.xref.Part1.25">5.4</a>, <a href="#rfc.xref.Part1.26">5.4</a>, <a href="#rfc.xref.Part1.27">5.4</a>, <a href="#rfc.xref.Part1.28">5.4.1</a>, <a href="#rfc.xref.Part1.29">5.4.1</a>, <a href="#rfc.xref.Part1.30">6.1</a>, <a href="#rfc.xref.Part1.31">6.2</a>, <a href="#rfc.xref.Part1.32">7</a>, <a href="#rfc.xref.Part1.33">7.1</a>, <a href="#rfc.xref.Part1.34">8.1</a>, <a href="#rfc.xref.Part1.35">9.1</a>, <a href="#rfc.xref.Part1.36">9.3</a>, <a href="#rfc.xref.Part1.37">9.8</a>, <a href="#rfc.xref.Part1.38">9.11</a>, <a href="#rfc.xref.Part1.39">9.17</a>, <a href="#rfc.xref.Part1.40">9.17</a>, <a href="#rfc.xref.Part1.41">9.18</a>, <a href="#rfc.xref.Part1.42">10.4</a>, <a href="#rfc.xref.Part1.43">10.4</a>, <a href="#rfc.xref.Part1.44">10.4</a>, <a href="#rfc.xref.Part1.45">12</a>, <a href="#Part1"><b>13.1</b></a>, <a href="#rfc.xref.Part1.46">C</a>, <a href="#rfc.xref.Part1.47">D</a>, <a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.55">D</a>, <a href="#rfc.xref.Part1.56">D</a>, <a href="#rfc.xref.Part1.57">D</a>, <a href="#rfc.xref.Part1.58">D</a><ul>
    49274924                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
    49284925                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
    4929                         <li><em>Section 2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.33">4.4.4</a></li>
    4930                         <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.36">4.7.6</a></li>
    4931                         <li><em>Section 2.8</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.15">1.2.2</a></li>
    4932                         <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>
    4933                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">3</a>, <a href="#rfc.xref.Part1.25">3.1</a>, <a href="#rfc.xref.Part1.51">9.17</a>, <a href="#rfc.xref.Part1.53">9.18</a></li>
    4934                         <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.24">3.1</a></li>
    4935                         <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">2.2.1</a>, <a href="#rfc.xref.Part1.34">4.4.6</a>, <a href="#rfc.xref.Part1.43">6.2</a>, <a href="#rfc.xref.Part1.44">7</a></li>
    4936                         <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.42">6.1</a></li>
    4937                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.40">5.4.1</a></li>
    4938                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.27">3.1</a></li>
    4939                         <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.37">5.4</a>, <a href="#rfc.xref.Part1.54">10.4</a></li>
    4940                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.41">5.4.1</a></li>
    4941                         <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.38">5.4</a>, <a href="#rfc.xref.Part1.55">10.4</a></li>
    4942                         <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.39">5.4</a>, <a href="#rfc.xref.Part1.56">10.4</a></li>
    4943                         <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">1.2.2</a>, <a href="#rfc.xref.Part1.46">8.1</a>, <a href="#rfc.xref.Part1.47">9.1</a>, <a href="#rfc.xref.Part1.48">9.3</a></li>
    4944                         <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">3.2</a></li>
    4945                         <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.18">2.3.1</a>, <a href="#rfc.xref.Part1.21">2.3.8</a></li>
    4946                         <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.28">3.2</a></li>
    4947                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">2</a>, <a href="#rfc.xref.Part1.30">3.3</a>, <a href="#rfc.xref.Part1.45">7.1</a>, <a href="#rfc.xref.Part1.49">9.8</a></li>
    4948                         <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">3.1</a></li>
    4949                         <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">2.3.7</a>, <a href="#rfc.xref.Part1.52">9.17</a>, <a href="#rfc.xref.Part1.58">C</a></li>
    4950                         <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.31">4.3.1</a>, <a href="#rfc.xref.Part1.50">9.11</a></li>
    4951                         <li><em>Section 6.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.32">4.3.2</a>, <a href="#rfc.xref.Part1.35">4.6.15</a></li>
    4952                         <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">2.3.7</a></li>
    4953                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.57">12</a></li>
    4954                         <li><em>Appendix B</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.23">3.1</a></li>
     4926                        <li><em>Section 2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.21">4.4.4</a></li>
     4927                        <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.24">4.7.6</a></li>
     4928                        <li><em>Section 2.8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.54">D</a>, <a href="#rfc.xref.Part1.56">D</a>, <a href="#rfc.xref.Part1.58">D</a></li>
     4929                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.10">3</a>, <a href="#rfc.xref.Part1.13">3.1</a>, <a href="#rfc.xref.Part1.39">9.17</a>, <a href="#rfc.xref.Part1.41">9.18</a></li>
     4930                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.48">D</a>, <a href="#rfc.xref.Part1.49">D</a>, <a href="#rfc.xref.Part1.50">D</a></li>
     4931                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">3.1</a>, <a href="#rfc.xref.Part1.51">D</a>, <a href="#rfc.xref.Part1.52">D</a>, <a href="#rfc.xref.Part1.53">D</a>, <a href="#rfc.xref.Part1.55">D</a></li>
     4932                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">2.2.1</a>, <a href="#rfc.xref.Part1.22">4.4.6</a>, <a href="#rfc.xref.Part1.31">6.2</a>, <a href="#rfc.xref.Part1.32">7</a></li>
     4933                        <li><em>Section 3.3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.30">6.1</a></li>
     4934                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.28">5.4.1</a></li>
     4935                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">3.1</a></li>
     4936                        <li><em>Section 4.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.25">5.4</a>, <a href="#rfc.xref.Part1.42">10.4</a></li>
     4937                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.29">5.4.1</a></li>
     4938                        <li><em>Section 4.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.26">5.4</a>, <a href="#rfc.xref.Part1.43">10.4</a></li>
     4939                        <li><em>Section 4.2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.27">5.4</a>, <a href="#rfc.xref.Part1.44">10.4</a></li>
     4940                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">3.2</a></li>
     4941                        <li><em>Section 4.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.34">8.1</a>, <a href="#rfc.xref.Part1.35">9.1</a>, <a href="#rfc.xref.Part1.36">9.3</a>, <a href="#rfc.xref.Part1.57">D</a></li>
     4942                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2.3.1</a>, <a href="#rfc.xref.Part1.9">2.3.8</a></li>
     4943                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">3.2</a></li>
     4944                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.18">3.3</a>, <a href="#rfc.xref.Part1.33">7.1</a>, <a href="#rfc.xref.Part1.37">9.8</a></li>
     4945                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.14">3.1</a></li>
     4946                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">2.3.7</a>, <a href="#rfc.xref.Part1.40">9.17</a>, <a href="#rfc.xref.Part1.46">C</a></li>
     4947                        <li><em>Section 6.4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">4.3.1</a>, <a href="#rfc.xref.Part1.38">9.11</a></li>
     4948                        <li><em>Section 6.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.20">4.3.2</a>, <a href="#rfc.xref.Part1.23">4.6.15</a></li>
     4949                        <li><em>Section 7.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">2.3.7</a></li>
     4950                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.45">12</a></li>
     4951                        <li><em>Appendix B</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">3.1</a></li>
    49554952                     </ul>
    49564953                  </li>
    4957                   <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">2.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.2</a>, <a href="#rfc.xref.Part4.6">3.3</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">4.1</a>, <a href="#rfc.xref.Part4.10">4.4.2</a>, <a href="#rfc.xref.Part4.11">4.5</a>, <a href="#rfc.xref.Part4.12">7.2</a>, <a href="#rfc.xref.Part4.13">7.2</a>, <a href="#Part4"><b>13.1</b></a>, <a href="#rfc.xref.Part4.14">E.2</a><ul>
     4954                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">2.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.2</a>, <a href="#rfc.xref.Part4.6">3.3</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">4.1</a>, <a href="#rfc.xref.Part4.10">4.4.2</a>, <a href="#rfc.xref.Part4.11">4.5</a>, <a href="#rfc.xref.Part4.12">7.2</a>, <a href="#rfc.xref.Part4.13">7.2</a>, <a href="#Part4"><b>13.1</b></a>, <a href="#rfc.xref.Part4.14">F.2</a><ul>
    49584955                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.13">7.2</a></li>
    49594956                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.6">3.3</a>, <a href="#rfc.xref.Part4.10">4.4.2</a>, <a href="#rfc.xref.Part4.12">7.2</a></li>
    … …  
    50435040                     </ul>
    50445041                  </li>
    5045                   <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">4.5</a>, <a href="#rfc.xref.RFC2616.3">9.4</a>, <a href="#RFC2616"><b>13.2</b></a>, <a href="#rfc.xref.RFC2616.4">E.1</a><ul>
     5042                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">4.5</a>, <a href="#rfc.xref.RFC2616.3">9.4</a>, <a href="#RFC2616"><b>13.2</b></a>, <a href="#rfc.xref.RFC2616.4">F.1</a><ul>
    50465043                        <li><em>Section 10.3.8</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.2">4.5</a></li>
    50475044                        <li><em>Section 14.4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.3">9.4</a></li>
    … …  
    50745071                     </ul>
    50755072                  </li>
    5076                   <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>
    5077                         <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
     5073                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">3.1</a>, <a href="#RFC5234"><b>13.1</b></a>, <a href="#rfc.xref.RFC5234.3">D</a><ul>
     5074                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.3">D</a></li>
    50785075                     </ul>
    50795076                  </li>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1803 r1805  
    299299
    300300<section title="Syntax Notation" anchor="notation">
    301   <x:anchor-alias value="ALPHA"/>
    302   <x:anchor-alias value="CR"/>
    303   <x:anchor-alias value="DIGIT"/>
    304   <x:anchor-alias value="LF"/>
    305   <x:anchor-alias value="OCTET"/>
    306   <x:anchor-alias value="SP"/>
    307   <x:anchor-alias value="VCHAR"/>
    308301<t>
    309302   This specification uses the Augmented Backus-Naur Form (ABNF) notation
    310303   of <xref target="RFC5234"/> with the list rule extension defined in
    311    &notation;.  <xref target="collected.abnf"/> shows the collected ABNF
     304   &notation;. <xref target="imported.abnf"/> describes rules imported from
     305   other documents. <xref target="collected.abnf"/> shows the collected ABNF
    312306   with the list rule expanded.
    313307</t>
    314 <t>
    315   The following core rules are included by
    316   reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
    317   ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
    318   DIGIT (decimal 0-9), DQUOTE (double quote),
    319   HEXDIG (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed),
    320   OCTET (any 8-bit sequence of data), SP (space), and
    321   VCHAR (any visible US-ASCII character).
    322 </t>
    323 
    324 <section title="Core Rules" anchor="core.rules">
    325   <x:anchor-alias value="quoted-string"/>
    326   <x:anchor-alias value="token"/>
    327   <x:anchor-alias value="word"/>
    328   <x:anchor-alias value="BWS"/>
    329   <x:anchor-alias value="OWS"/>
    330   <x:anchor-alias value="RWS"/>
    331 <t>
    332   The core rules below are defined in <xref target="Part1"/>:
    333 </t>
    334 <figure><artwork type="abnf2616">
    335   <x:ref>BWS</x:ref>           = &lt;BWS, defined in &whitespace;&gt;
    336   <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
    337   <x:ref>RWS</x:ref>           = &lt;RWS, defined in &whitespace;&gt;
    338   <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &field-components;&gt;
    339   <x:ref>token</x:ref>         = &lt;token, defined in &field-components;&gt;
    340   <x:ref>word</x:ref>          = &lt;word, defined in &field-components;&gt;
    341 </artwork></figure>
    342 </section>
    343 
    344 <section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
    345   <x:anchor-alias value="absolute-URI"/>
    346   <x:anchor-alias value="comment"/>
    347   <x:anchor-alias value="partial-URI"/>
    348   <x:anchor-alias value="qvalue"/>
    349   <x:anchor-alias value="URI-reference"/>
    350 <t>
    351   The ABNF rules below are defined in other parts:
    352 </t>
    353 <figure><!--Part1--><artwork type="abnf2616">
    354   <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in &uri;&gt;
    355   <x:ref>comment</x:ref>       = &lt;comment, defined in &field-components;&gt;
    356   <x:ref>partial-URI</x:ref>   = &lt;partial-URI, defined in &uri;&gt;
    357   <x:ref>qvalue</x:ref>        = &lt;qvalue, defined in &qvalue;&gt;
    358   <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in &uri;&gt;
    359 </artwork></figure>
    360 </section>
    361308</section>
    362309</section>
    … …  
    56115558</section>
    56125559
     5560<section title="Imported ABNF" anchor="imported.abnf">
     5561  <x:anchor-alias value="ALPHA"/>
     5562  <x:anchor-alias value="CR"/>
     5563  <x:anchor-alias value="DIGIT"/>
     5564  <x:anchor-alias value="LF"/>
     5565  <x:anchor-alias value="OCTET"/>
     5566  <x:anchor-alias value="SP"/>
     5567  <x:anchor-alias value="VCHAR"/>
     5568  <x:anchor-alias value="quoted-string"/>
     5569  <x:anchor-alias value="token"/>
     5570  <x:anchor-alias value="word"/>
     5571  <x:anchor-alias value="BWS"/>
     5572  <x:anchor-alias value="OWS"/>
     5573  <x:anchor-alias value="RWS"/>
     5574  <x:anchor-alias value="absolute-URI"/>
     5575  <x:anchor-alias value="comment"/>
     5576  <x:anchor-alias value="partial-URI"/>
     5577  <x:anchor-alias value="qvalue"/>
     5578  <x:anchor-alias value="URI-reference"/>
     5579<t>
     5580  The following core rules are included by
     5581  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
     5582  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
     5583  DIGIT (decimal 0-9), DQUOTE (double quote),
     5584  HEXDIG (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed),
     5585  OCTET (any 8-bit sequence of data), SP (space), and
     5586  VCHAR (any visible US-ASCII character).
     5587</t>
     5588<t>
     5589  The rules below are defined in <xref target="Part1"/>:
     5590</t>
     5591<figure><artwork type="abnf2616">
     5592  <x:ref>BWS</x:ref>           = &lt;BWS, defined in &whitespace;&gt;
     5593  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
     5594  <x:ref>RWS</x:ref>           = &lt;RWS, defined in &whitespace;&gt;
     5595  <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &field-components;&gt;
     5596  <x:ref>token</x:ref>         = &lt;token, defined in &field-components;&gt;
     5597  <x:ref>word</x:ref>          = &lt;word, defined in &field-components;&gt;
     5598
     5599  <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in &uri;&gt;
     5600  <x:ref>comment</x:ref>       = &lt;comment, defined in &field-components;&gt;
     5601  <x:ref>partial-URI</x:ref>   = &lt;partial-URI, defined in &uri;&gt;
     5602  <x:ref>qvalue</x:ref>        = &lt;qvalue, defined in &qvalue;&gt;
     5603  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in &uri;&gt;
     5604</artwork></figure>
     5605</section>
     5606
    56135607<?BEGININC p2-semantics.abnf-appendix ?>
    56145608<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">

  • draft-ietf-httpbis/latest/p4-conditional.html

    r1803 r1805  
    481481      <link rel="Chapter" href="#rfc.section.9" title="9 References">
    482482      <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
    483       <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    484       <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
     483      <link rel="Appendix" title="B Imported ABNF" href="#rfc.section.B">
     484      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
     485      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    485486      <link href="p3-payload.html" rel="prev">
    486487      <link href="p5-range.html" rel="next">
    … …  
    542543      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    543544      </p> 
    544       <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p4-conditional-19">Appendix&nbsp;C.1</a>.
     545      <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p4-conditional-19">Appendix&nbsp;D.1</a>.
    545546      </p>
    546547      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    … …  
    620621         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    621622         <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    622          <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    623          <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    624                <li>C.1&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p4-conditional-19</a></li>
     623         <li>B.&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
     624         <li>C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     625         <li>D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     626               <li>D.1&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p4-conditional-19</a></li>
    625627            </ul>
    626628         </li>
    … …  
    672674      </p>
    673675      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    674       <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF with the list rule expanded.
    675       </p>
    676       <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    677          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
    678          character).
    679       </p>
    680       <p id="rfc.section.1.2.p.3">The ABNF rules below are defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> and <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>:
    681       </p>
    682       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#notation" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    683   <a href="#notation" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    684   <a href="#notation" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a>&gt;
    685 </pre><div id="rfc.iref.m.1"></div>
     676      <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;B</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF with the list rule expanded.
     677      </p>
     678      <div id="rfc.iref.m.1"></div>
    686679      <div id="rfc.iref.v.1"></div>
    687680      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="validators" href="#validators">Validators</a></h1>
    … …  
    740733         was last modified.
    741734      </p>
    742       <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#header.last-modified" class="smpl">Last-Modified</a> = <a href="#notation" class="smpl">HTTP-date</a>
     735      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#header.last-modified" class="smpl">Last-Modified</a> = <a href="#imported.abnf" class="smpl">HTTP-date</a>
    743736</pre><p id="rfc.section.2.2.p.3">An example of its use is</p>
    744       <div id="rfc.figure.u.3"></div><pre class="text">  Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
     737      <div id="rfc.figure.u.2"></div><pre class="text">  Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
    745738</pre><h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a id="lastmod.generation" href="#lastmod.generation">Generation</a></h3>
    746739      <p id="rfc.section.2.2.1.p.1">Origin servers <em class="bcp14">SHOULD</em> send Last-Modified for any selected representation for which a last modification date can be reasonably and consistently determined,
    … …  
    802795         same time, or both. An entity-tag consists of an opaque quoted string, possibly prefixed by a weakness indicator.
    803796      </p>
    804       <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.etag" class="smpl">ETag</a>       = <a href="#header.etag" class="smpl">entity-tag</a>
     797      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.etag" class="smpl">ETag</a>       = <a href="#header.etag" class="smpl">entity-tag</a>
    805798
    806799  <a href="#header.etag" class="smpl">entity-tag</a> = [ <a href="#header.etag" class="smpl">weak</a> ] <a href="#header.etag" class="smpl">opaque-tag</a>
    807800  <a href="#header.etag" class="smpl">weak</a>       = %x57.2F ; "W/", case-sensitive
    808   <a href="#header.etag" class="smpl">opaque-tag</a> = <a href="#notation" class="smpl">DQUOTE</a> *<a href="#header.etag" class="smpl">etagc</a> <a href="#notation" class="smpl">DQUOTE</a>
    809   <a href="#header.etag" class="smpl">etagc</a>      = %x21 / %x23-7E / <a href="#notation" class="smpl">obs-text</a>
    810              ; <a href="#notation" class="smpl">VCHAR</a> except double quotes, plus obs-text
     801  <a href="#header.etag" class="smpl">opaque-tag</a> = <a href="#imported.abnf" class="smpl">DQUOTE</a> *<a href="#header.etag" class="smpl">etagc</a> <a href="#imported.abnf" class="smpl">DQUOTE</a>
     802  <a href="#header.etag" class="smpl">etagc</a>      = %x21 / %x23-7E / <a href="#imported.abnf" class="smpl">obs-text</a>
     803             ; <a href="#imported.abnf" class="smpl">VCHAR</a> except double quotes, plus obs-text
    811804</pre><div class="note" id="rfc.section.2.3.p.3">
    812805         <p> <b>Note:</b> Previously, opaque-tag was defined to be a quoted-string (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-3.11">Section 3.11</a>), thus some recipients might perform backslash unescaping. Servers therefore ought to avoid backslash characters in entity
    … …  
    818811         not consistently maintained.
    819812      </p>
    820       <div id="rfc.figure.u.5"></div>
     813      <div id="rfc.figure.u.4"></div>
    821814      <p>Examples:</p>  <pre class="text">  ETag: "xyzzy"
    822815  ETag: W/"xyzzy"
    … …  
    890883      </div>
    891884      <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a id="example.entity.tag.vs.conneg" href="#example.entity.tag.vs.conneg">Example: Entity-tags varying on Content-Negotiated Resources</a></h3>
    892       <p id="rfc.section.2.3.3.p.1">Consider a resource that is subject to content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Section 8</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>), and where the representations returned upon a GET request vary based on the <a href="p2-semantics.html#header.accept-encoding" class="smpl">Accept-Encoding</a> request header field (<a href="p2-semantics.html#header.accept-encoding" title="Accept-Encoding">Section 9.3</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>):
    893       </p>
    894       <div id="rfc.figure.u.6"></div>
     885      <p id="rfc.section.2.3.3.p.1">Consider a resource that is subject to content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Section 8</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>), and where the representations returned upon a GET request vary based on the <a href="p2-semantics.html#header.accept-encoding" class="smpl">Accept-Encoding</a> request header field (<a href="p2-semantics.html#header.accept-encoding" title="Accept-Encoding">Section 9.3</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>):
     886      </p>
     887      <div id="rfc.figure.u.5"></div>
    895888      <p>&gt;&gt; Request:</p><pre class="text2">GET /index HTTP/1.1
    896889Host: www.example.com
    … …  
    898891
    899892</pre><p id="rfc.section.2.3.3.p.3">In this case, the response might or might not use the gzip content coding. If it does not, the response might look like:</p>
    900       <div id="rfc.figure.u.7"></div>
     893      <div id="rfc.figure.u.6"></div>
    901894      <p>&gt;&gt; Response:</p><pre class="text">HTTP/1.1 200 OK
    902895Date: Thu, 26 Mar 2010 00:05:00 GMT
    … …  
    912905Hello World!
    913906</span></pre><p id="rfc.section.2.3.3.p.5">An alternative representation that does use gzip content coding would be:</p>
    914       <div id="rfc.figure.u.8"></div>
     907      <div id="rfc.figure.u.7"></div>
    915908      <p>&gt;&gt; Response:</p><pre class="text">HTTP/1.1 200 OK
    916909Date: Thu, 26 Mar 2010 00:05:00 GMT
    … …  
    924917         <p> <b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation has to be distinct
    925918            from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings
    926             (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags.
     919            (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags.
    927920         </p>
    928921      </div>
    … …  
    982975         field-value of "*" places the precondition on the existence of any current representation for the target resource.
    983976      </p>
    984       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.if-match" class="smpl">If-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a>
     977      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.if-match" class="smpl">If-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a>
    985978</pre><p id="rfc.section.3.1.p.4">The If-Match condition is met if and only if any of the entity-tags listed in the If-Match field value match the entity-tag
    986979         of the selected representation for the target resource (as per <a href="#entity.tag.comparison" title="Comparison">Section&nbsp;2.3.2</a>), or if "*" is given and any current representation exists for the target resource.
    … …  
    996989      </p>
    997990      <p id="rfc.section.3.1.p.9">Examples:</p>
    998       <div id="rfc.figure.u.10"></div><pre class="text">  If-Match: "xyzzy"
     991      <div id="rfc.figure.u.9"></div><pre class="text">  If-Match: "xyzzy"
    999992  If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
    1000993  If-Match: *
    … …  
    10151008         for the target resource.
    10161009      </p>
    1017       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#header.if-none-match" class="smpl">If-None-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a>
     1010      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#header.if-none-match" class="smpl">If-None-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a>
    10181011</pre><p id="rfc.section.3.2.p.5">The If-None-Match condition is met if and only if none of the entity-tags listed in the If-None-Match field value match the
    10191012         entity-tag of the selected representation for the target resource (as per <a href="#entity.tag.comparison" title="Comparison">Section&nbsp;2.3.2</a>), or if "*" is given and no current representation exists for that resource.
    … …  
    10281021      </p>
    10291022      <p id="rfc.section.3.2.p.9">Examples:</p>
    1030       <div id="rfc.figure.u.12"></div><pre class="text">  If-None-Match: "xyzzy"
     1023      <div id="rfc.figure.u.11"></div><pre class="text">  If-None-Match: "xyzzy"
    10311024  If-None-Match: W/"xyzzy"
    10321025  If-None-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
    … …  
    10401033         method; instead, respond as detailed below.
    10411034      </p>
    1042       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> = <a href="#notation" class="smpl">HTTP-date</a>
     1035      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> = <a href="#imported.abnf" class="smpl">HTTP-date</a>
    10431036</pre><p id="rfc.section.3.3.p.3">An example of the field is:</p>
    1044       <div id="rfc.figure.u.14"></div><pre class="text">  If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT
     1037      <div id="rfc.figure.u.13"></div><pre class="text">  If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT
    10451038</pre><p id="rfc.section.3.3.p.5">A GET method with an If-Modified-Since header field and no <a href="p5-range.html#range.retrieval.requests" class="smpl">Range</a> header field requests that the selected representation be transferred only if it has been modified since the date given by
    10461039         the If-Modified-Since header field. The algorithm for determining this includes the following cases:
    … …  
    10801073         representation has been modified since the time specified in this field, then the server <em class="bcp14">MUST NOT</em> perform the requested operation and <em class="bcp14">MUST</em> instead respond with the <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code. If the selected representation has not been modified since the time specified in this field, the server <em class="bcp14">SHOULD</em> perform the request method as if the If-Unmodified-Since header field were not present.
    10811074      </p>
    1082       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> = <a href="#notation" class="smpl">HTTP-date</a>
     1075      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> = <a href="#imported.abnf" class="smpl">HTTP-date</a>
    10831076</pre><p id="rfc.section.3.4.p.3">An example of the field is:</p>
    1084       <div id="rfc.figure.u.16"></div><pre class="text">  If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
     1077      <div id="rfc.figure.u.15"></div><pre class="text">  If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
    10851078</pre><p id="rfc.section.3.4.p.5">If a request normally (i.e., in absence of the If-Unmodified-Since header field) would result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code, the If-Unmodified-Since header field <em class="bcp14">SHOULD</em> be ignored.
    10861079      </p>
    … …  
    10991092         as if it were the payload of a 200 response. The 304 response <em class="bcp14">MUST NOT</em> contain a message-body, and thus is always terminated by the first empty line after the header fields.
    11001093      </p>
    1101       <p id="rfc.section.4.1.p.2">A 304 response <em class="bcp14">MUST</em> include a <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field (<a href="p2-semantics.html#header.date" title="Date">Section 9.10</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>) unless the origin server does not have a clock that can provide a reasonable approximation of the current time. If a <a href="p2-semantics.html#status.200" class="smpl">200
     1094      <p id="rfc.section.4.1.p.2">A 304 response <em class="bcp14">MUST</em> include a <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field (<a href="p2-semantics.html#header.date" title="Date">Section 9.10</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>) unless the origin server does not have a clock that can provide a reasonable approximation of the current time. If a <a href="p2-semantics.html#status.200" class="smpl">200
    11021095            (OK)</a> response to the same request would have included any of the header fields <a href="p6-cache.html#header.cache-control" class="smpl">Cache-Control</a>, <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a>, <a href="#header.etag" class="smpl">ETag</a>, <a href="p6-cache.html#header.expires" class="smpl">Expires</a>, or <a href="p6-cache.html#header.vary" class="smpl">Vary</a>, then those same header fields <em class="bcp14">MUST</em> be sent in a 304 response.
    11031096      </p>
    … …  
    12581251      <p id="rfc.section.6.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    12591252      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    1260       <p id="rfc.section.7.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     1253      <p id="rfc.section.7.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    12611254      </p>
    12621255      <p id="rfc.section.7.p.2">The validators defined by this specification are not intended to ensure the validity of a representation, guard against malicious
    … …  
    12661259      </p>
    12671260      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    1268       <p id="rfc.section.8.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     1261      <p id="rfc.section.8.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    12691262      </p>
    12701263      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
    … …  
    13421335      <p id="rfc.section.A.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Precondition Header Fields">Section&nbsp;3</a>)
    13431336      </p>
    1344       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1345       <div id="rfc.figure.u.17"></div> <pre class="inline"><a href="#header.etag" class="smpl">ETag</a> = entity-tag
    1346 
    1347 <a href="#notation" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 5.1&gt;
     1337      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
     1338      <p id="rfc.section.B.p.1">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     1339         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
     1340         character).
     1341      </p>
     1342      <p id="rfc.section.B.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>:
     1343      </p>
     1344      <div id="rfc.figure.u.16"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     1345  <a href="#imported.abnf" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     1346</pre><p id="rfc.section.B.p.4">The rules below are defined in other parts:</p>
     1347      <div id="rfc.figure.u.17"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a>&gt;
     1348</pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     1349      <div id="rfc.figure.u.18"></div> <pre class="inline"><a href="#header.etag" class="smpl">ETag</a> = entity-tag
     1350
     1351<a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 5.1&gt;
    13481352
    13491353<a href="#header.if-match" class="smpl">If-Match</a> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
    … …  
    13561360<a href="#header.last-modified" class="smpl">Last-Modified</a> = HTTP-date
    13571361
    1358 <a href="#notation" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
     1362<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
    13591363
    13601364<a href="#header.etag" class="smpl">entity-tag</a> = [ weak ] opaque-tag
    … …  
    13621366 / obs-text
    13631367
    1364 <a href="#notation" class="smpl">obs-text</a> = &lt;obs-text, defined in [Part1], Section 3.2.4&gt;
     1368<a href="#imported.abnf" class="smpl">obs-text</a> = &lt;obs-text, defined in [Part1], Section 3.2.4&gt;
    13651369<a href="#header.etag" class="smpl">opaque-tag</a> = DQUOTE *etagc DQUOTE
    13661370
    13671371<a href="#header.etag" class="smpl">weak</a> = %x57.2F ; W/
    1368 </pre> <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    1369       <p id="rfc.section.C.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-19#appendix-C">http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-19#appendix-C</a>&gt;.
    1370       </p>
    1371       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p4-conditional-19</a></h2>
    1372       <p id="rfc.section.C.1.p.1">Closed issues: </p>
     1372</pre> <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     1373      <p id="rfc.section.D.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-19#appendix-C">http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-19#appendix-C</a>&gt;.
     1374      </p>
     1375      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p4-conditional-19</a></h2>
     1376      <p id="rfc.section.D.1.p.1">Closed issues: </p>
    13731377      <ul>
    13741378         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/241">http://tools.ietf.org/wg/httpbis/trac/ticket/241</a>&gt;: "Need to clarify eval order/interaction of conditional headers"
    … …  
    14501454            </li>
    14511455            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    1452                   <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</a>, <a href="#rfc.xref.Part1.5">1.2</a>, <a href="#rfc.xref.Part1.6">1.2</a>, <a href="#rfc.xref.Part1.7">2.3.3</a>, <a href="#rfc.xref.Part1.8">7</a>, <a href="#rfc.xref.Part1.9">8</a>, <a href="#Part1"><b>9.1</b></a><ul>
     1456                  <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">2.3.3</a>, <a href="#rfc.xref.Part1.5">7</a>, <a href="#rfc.xref.Part1.6">8</a>, <a href="#Part1"><b>9.1</b></a>, <a href="#rfc.xref.Part1.7">B</a>, <a href="#rfc.xref.Part1.8">B</a>, <a href="#rfc.xref.Part1.9">B</a><ul>
    14531457                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">1.2</a></li>
    14541458                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.1</a></li>
    1455                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2</a></li>
    1456                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">1.2</a></li>
    1457                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">2.3.3</a></li>
    1458                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">8</a></li>
     1459                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">B</a></li>
     1460                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">B</a></li>
     1461                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">2.3.3</a></li>
     1462                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">8</a></li>
    14591463                     </ul>
    14601464                  </li>
    1461                   <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">1.2</a>, <a href="#rfc.xref.Part2.3">1.2</a>, <a href="#rfc.xref.Part2.4">2.3.3</a>, <a href="#rfc.xref.Part2.5">2.3.3</a>, <a href="#rfc.xref.Part2.6">4.1</a>, <a href="#Part2"><b>9.1</b></a><ul>
    1462                         <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">1.2</a></li>
    1463                         <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.3.3</a></li>
    1464                         <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">2.3.3</a></li>
    1465                         <li><em>Section 9.10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.6">4.1</a></li>
     1465                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">2.3.3</a>, <a href="#rfc.xref.Part2.3">2.3.3</a>, <a href="#rfc.xref.Part2.4">4.1</a>, <a href="#Part2"><b>9.1</b></a>, <a href="#rfc.xref.Part2.5">B</a><ul>
     1466                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">B</a></li>
     1467                        <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">2.3.3</a></li>
     1468                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">2.3.3</a></li>
     1469                        <li><em>Section 9.10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">4.1</a></li>
    14661470                     </ul>
    14671471                  </li>
    … …  
    14821486                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">6.2</a>, <a href="#RFC3864"><b>9.2</b></a></li>
    14831487                  <li><em>RFC4918</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4918.1">2</a>, <a href="#RFC4918"><b>9.2</b></a></li>
    1484                   <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="#RFC5234"><b>9.1</b></a><ul>
    1485                         <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
     1488                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#RFC5234"><b>9.1</b></a>, <a href="#rfc.xref.RFC5234.2">B</a><ul>
     1489                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">B</a></li>
    14861490                     </ul>
    14871491                  </li>

  • draft-ietf-httpbis/latest/p4-conditional.xml

    r1803 r1805  
    221221
    222222<section title="Syntax Notation" anchor="notation">
    223   <x:anchor-alias value="ALPHA"/>
    224   <x:anchor-alias value="CR"/>
    225   <x:anchor-alias value="DIGIT"/>
    226   <x:anchor-alias value="DQUOTE"/>
    227   <x:anchor-alias value="LF"/>
    228   <x:anchor-alias value="OCTET"/>
    229   <x:anchor-alias value="VCHAR"/>
    230   <x:anchor-alias value="core.rules"/>
    231   <x:anchor-alias value="obs-text"/>
    232   <x:anchor-alias value="OWS"/>
    233   <x:anchor-alias value="HTTP-date"/>
    234223<t>
    235224   This specification uses the Augmented Backus-Naur Form (ABNF) notation
    236225   of <xref target="RFC5234"/> with the list rule extension defined in
    237    &notation;.  <xref target="collected.abnf"/> shows the collected ABNF
     226   &notation;. <xref target="imported.abnf"/> describes rules imported from
     227   other documents. <xref target="collected.abnf"/> shows the collected ABNF
    238228   with the list rule expanded.
    239229</t>
    240 <t>
    241   The following core rules are included by
    242   reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
    243   ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
    244   DIGIT (decimal 0-9), DQUOTE (double quote),
    245   HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
    246   OCTET (any 8-bit sequence of data), SP (space), and
    247   VCHAR (any visible US-ASCII character).
    248 </t>
    249 <t>
    250   The ABNF rules below are defined in <xref target="Part1"/> and
    251   <xref target="Part2"/>:
    252 </t>
    253 <figure><artwork type="abnf2616">
    254   <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
    255   <x:ref>obs-text</x:ref>      = &lt;obs-text, defined in &field-components;&gt;
    256   <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &http-date;&gt;
    257 </artwork></figure>
    258230</section>
    259231</section>
    … …  
    14821454</section>
    14831455
     1456<section title="Imported ABNF" anchor="imported.abnf">
     1457  <x:anchor-alias value="ALPHA"/>
     1458  <x:anchor-alias value="CR"/>
     1459  <x:anchor-alias value="DIGIT"/>
     1460  <x:anchor-alias value="DQUOTE"/>
     1461  <x:anchor-alias value="LF"/>
     1462  <x:anchor-alias value="OCTET"/>
     1463  <x:anchor-alias value="VCHAR"/>
     1464  <x:anchor-alias value="core.rules"/>
     1465  <x:anchor-alias value="obs-text"/>
     1466  <x:anchor-alias value="OWS"/>
     1467  <x:anchor-alias value="HTTP-date"/>
     1468<t>
     1469  The following core rules are included by
     1470  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
     1471  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
     1472  DIGIT (decimal 0-9), DQUOTE (double quote),
     1473  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
     1474  OCTET (any 8-bit sequence of data), SP (space), and
     1475  VCHAR (any visible US-ASCII character).
     1476</t>
     1477<t>
     1478  The rules below are defined in <xref target="Part1"/>:
     1479</t>
     1480<figure><artwork type="abnf2616">
     1481  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
     1482  <x:ref>obs-text</x:ref>      = &lt;obs-text, defined in &field-components;&gt;
     1483</artwork></figure>
     1484<t>
     1485  The rules below are defined in other parts:
     1486</t>
     1487<figure><artwork type="abnf2616">
     1488  <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &http-date;&gt;
     1489</artwork></figure>
     1490</section>
     1491
    14841492<?BEGININC p4-conditional.abnf-appendix ?>
    14851493<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">

  • draft-ietf-httpbis/latest/p5-range.html

    r1804 r1805  
    482482      <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A">
    483483      <link rel="Appendix" title="B Changes from RFC 2616" href="#rfc.section.B">
    484       <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
    485       <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
     484      <link rel="Appendix" title="C Imported ABNF" href="#rfc.section.C">
     485      <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
     486      <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
    486487      <link href="p4-conditional.html" rel="prev">
    487488      <link href="p6-cache.html" rel="next">
    … …  
    543544      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    544545      </p> 
    545       <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p5-range-19">Appendix&nbsp;D.1</a>.
     546      <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p5-range-19">Appendix&nbsp;E.1</a>.
    546547      </p>
    547548      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    … …  
    574575         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    575576               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
    576                <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
    577                      <li>1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    578                      <li>1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    579                   </ul>
    580                </li>
     577               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a></li>
    581578            </ul>
    582579         </li>
    … …  
    625622         <li>A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
    626623         <li>B.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    627          <li>C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    628          <li>D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    629                <li>D.1&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p5-range-19</a></li>
     624         <li>C.&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
     625         <li>D.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     626         <li>E.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     627               <li>E.1&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p5-range-19</a></li>
    630628            </ul>
    631629         </li>
    … …  
    671669      </p>
    672670      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    673       <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF with the list rule expanded.
    674       </p>
    675       <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    676          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
    677          character).
    678       </p>
    679       <p id="rfc.section.1.2.p.3">Note that all rules derived from <a href="#core.rules" class="smpl">token</a> are to be compared case-insensitively, like <a href="#range.units" class="smpl">range-unit</a> and <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>.
    680       </p>
    681       <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    682       <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> and <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>:
    683       </p>
    684       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">OWS</a>        = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    685   <a href="#core.rules" class="smpl">token</a>      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    686   <a href="#core.rules" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a>&gt;
    687 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    688       <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
    689       <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>&gt;
    690 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
     671      <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;C</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF with the list rule expanded.
     672      </p>
     673      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h1>
    691674      <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range) of the representation be included within the response. HTTP/1.1
    692675         uses range units in the <a href="#range.retrieval.requests" class="smpl">Range</a> (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;5.4</a>) and <a href="#header.content-range" class="smpl">Content-Range</a> (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section&nbsp;5.2</a>) header fields. A representation can be broken down into subranges according to various structural units.
    693676      </p>
    694       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#range.units" class="smpl">range-unit</a>       = <a href="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a>
     677      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#range.units" class="smpl">range-unit</a>       = <a href="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a>
    695678  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
    696   <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a>
     679  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#imported.abnf" class="smpl">token</a>
    697680</pre><p id="rfc.section.2.p.3">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges. The only range
    698681         unit defined by HTTP/1.1 is "bytes". Additional specifiers can be defined as described in <a href="#range.specifier.registry" title="Range Specifier Registry">Section&nbsp;2.1</a>.
    … …  
    741724      <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a <a href="#header.content-range" class="smpl">Content-Range</a> header field specifying the current length of the representation (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type. For example,
    742725      </p>
    743       <div id="rfc.figure.u.4"></div><pre class="text">HTTP/1.1 416 Requested Range Not Satisfiable
     726      <div id="rfc.figure.u.2"></div><pre class="text">HTTP/1.1 416 Requested Range Not Satisfiable
    744727Date: Mon, 20 Jan 2012 15:41:54 GMT
    745728Content-Range: bytes */47022
    … …  
    757740         a request for a set of ranges that overlap without any holes), this content is transmitted with a <a href="#header.content-range" class="smpl">Content-Range</a> header field, and a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field showing the number of bytes actually transferred. For example,
    758741      </p>
    759       <div id="rfc.figure.u.5"></div><pre class="text">HTTP/1.1 206 Partial Content
     742      <div id="rfc.figure.u.3"></div><pre class="text">HTTP/1.1 206 Partial Content
    760743Date: Wed, 15 Nov 1995 06:25:24 GMT
    761744Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT
    … …  
    777760         one or more Range specifications. After several such transfers, a client might have received several ranges of the same representation.
    778761         These ranges can only be safely combined if they all have in common the same strong validator, where "strong validator" is
    779          defined to be either an entity-tag that is not marked as weak (<a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>) or, if no entity-tag is provided, a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> value that is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
     762         defined to be either an entity-tag that is not marked as weak (<a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>) or, if no entity-tag is provided, a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> value that is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    780763      </p>
    781764      <p id="rfc.section.4.2.p.2">When a client receives an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> or <a href="#status.206" class="smpl">206 (Partial Content)</a> response and already has one or more stored responses for the same method and effective request URI, all of the stored responses
    … …  
    800783      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2>
    801784      <p id="rfc.section.5.1.p.1">The "Accept-Ranges" header field allows a resource to indicate its acceptance of range requests.</p>
    802       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
     785      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a>     = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>
    803786  <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none"
    804787</pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send
    805788      </p>
    806       <div id="rfc.figure.u.7"></div><pre class="text">  Accept-Ranges: bytes
     789      <div id="rfc.figure.u.5"></div><pre class="text">  Accept-Ranges: bytes
    807790</pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate range requests without having received this header field for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
    808791      </p>
    809792      <p id="rfc.section.5.1.p.6">Servers that do not accept any kind of range request for a resource <em class="bcp14">MAY</em> send
    810793      </p>
    811       <div id="rfc.figure.u.8"></div><pre class="text">  Accept-Ranges: none
     794      <div id="rfc.figure.u.6"></div><pre class="text">  Accept-Ranges: none
    812795</pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p>
    813796      <div id="rfc.iref.c.1"></div>
    … …  
    819802      <p id="rfc.section.5.2.p.2">Range units are defined in <a href="#range.units" title="Range Units">Section&nbsp;2</a>.
    820803      </p>
    821       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  <a href="#header.content-range" class="smpl">Content-Range</a>           = <a href="#header.content-range" class="smpl">byte-content-range-spec</a>
     804      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  <a href="#header.content-range" class="smpl">Content-Range</a>           = <a href="#header.content-range" class="smpl">byte-content-range-spec</a>
    822805                          / <a href="#header.content-range" class="smpl">other-content-range-spec</a>
    823806                         
    824   <a href="#header.content-range" class="smpl">byte-content-range-spec</a> = <a href="#range.units" class="smpl">bytes-unit</a> <a href="#notation" class="smpl">SP</a>
     807  <a href="#header.content-range" class="smpl">byte-content-range-spec</a> = <a href="#range.units" class="smpl">bytes-unit</a> <a href="#imported.abnf" class="smpl">SP</a>
    825808                            <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> "/"
    826809                            ( <a href="#header.content-range" class="smpl">instance-length</a> / "*" )
    … …  
    829812                          / "*"
    830813                         
    831   <a href="#header.content-range" class="smpl">instance-length</a>         = 1*<a href="#notation" class="smpl">DIGIT</a>
     814  <a href="#header.content-range" class="smpl">instance-length</a>         = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    832815 
    833   <a href="#header.content-range" class="smpl">other-content-range-spec</a> = <a href="#range.units" class="smpl">other-range-unit</a> <a href="#notation" class="smpl">SP</a>
     816  <a href="#header.content-range" class="smpl">other-content-range-spec</a> = <a href="#range.units" class="smpl">other-range-unit</a> <a href="#imported.abnf" class="smpl">SP</a>
    834817                             <a href="#header.content-range" class="smpl">other-range-resp-spec</a>
    835   <a href="#header.content-range" class="smpl">other-range-resp-spec</a>    = *<a href="#notation" class="smpl">CHAR</a>
     818  <a href="#header.content-range" class="smpl">other-range-resp-spec</a>    = *<a href="#imported.abnf" class="smpl">CHAR</a>
    836819</pre><p id="rfc.section.5.2.p.4">The header field <em class="bcp14">SHOULD</em> indicate the total length of the full representation, unless this length is unknown or difficult to determine. The asterisk
    837820         "*" character means that the instance-length is unknown at the time when the response was generated.
    … …  
    852835      <ul>
    853836         <li>The first 500 bytes:
    854             <div id="rfc.figure.u.10"></div><pre class="text">  bytes 0-499/1234
     837            <div id="rfc.figure.u.8"></div><pre class="text">  bytes 0-499/1234
    855838</pre> </li>
    856839         <li>The second 500 bytes:
    857             <div id="rfc.figure.u.11"></div><pre class="text">  bytes 500-999/1234
     840            <div id="rfc.figure.u.9"></div><pre class="text">  bytes 500-999/1234
    858841</pre> </li>
    859842         <li>All except for the first 500 bytes:
    860             <div id="rfc.figure.u.12"></div><pre class="text">  bytes 500-1233/1234
     843            <div id="rfc.figure.u.10"></div><pre class="text">  bytes 500-1233/1234
    861844</pre> </li>
    862845         <li>The last 500 bytes:
    863             <div id="rfc.figure.u.13"></div><pre class="text">  bytes 734-1233/1234
     846            <div id="rfc.figure.u.11"></div><pre class="text">  bytes 734-1233/1234
    864847</pre> </li>
    865848      </ul>
    … …  
    877860         is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation".
    878861      </p>
    879       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#core.rules" class="smpl">HTTP-date</a>
     862      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#imported.abnf" class="smpl">entity-tag</a> / <a href="#imported.abnf" class="smpl">HTTP-date</a>
    880863</pre><p id="rfc.section.5.3.p.4">Clients <em class="bcp14">MUST NOT</em> use an entity-tag marked as weak in an If-Range field value and <em class="bcp14">MUST NOT</em> use a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> date in an If-Range field value unless it has no entity-tag for the representation and the Last-Modified date it does have
    881          for the representation is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
     864         for the representation is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    882865      </p>
    883866      <p id="rfc.section.5.3.p.5">A server that evaluates a conditional range request that is applicable to one of its representations <em class="bcp14">MUST</em> evaluate the condition as false if the entity-tag used as a validator is marked as weak or, when an HTTP-date is used as the
    884          validator, if the date value is not strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. (A server can distinguish between a valid HTTP-date and any form of entity-tag by examining the first two characters.)
     867         validator, if the date value is not strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. (A server can distinguish between a valid HTTP-date and any form of entity-tag by examining the first two characters.)
    885868      </p>
    886869      <p id="rfc.section.5.3.p.6">The If-Range header field <em class="bcp14">SHOULD</em> only be sent by clients together with a Range header field. The If-Range header field <em class="bcp14">MUST</em> be ignored if it is received in a request that does not include a Range header field. The If-Range header field <em class="bcp14">MUST</em> be ignored by a server that does not support the sub-range operation.
    … …  
    903886         </p>
    904887      </div>
    905       <div id="rfc.figure.u.15"></div><pre class="inline"><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>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
     888      <div id="rfc.figure.u.13"></div><pre class="inline"><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>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
    906889  <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>  = 1#( <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> / <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> )
    907890  <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" [ <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> ]
    908   <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    909   <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#notation" class="smpl">DIGIT</a>
     891  <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
     892  <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>   = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    910893</pre><p id="rfc.section.5.4.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value
    911894         gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start
    … …  
    919902      </p>
    920903      <p id="rfc.section.5.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the representation.</p>
    921       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
    922   <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
     904      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>  <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>
     905  <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    923906</pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the representation body, of a length given by the suffix-length
    924907         value. (That is, this form specifies the last N bytes of a representation.) If the representation is shorter than the specified
    … …  
    934917      <ul>
    935918         <li>The first 500 bytes (byte offsets 0-499, inclusive):
    936             <div id="rfc.figure.u.17"></div><pre class="text">  bytes=0-499
     919            <div id="rfc.figure.u.15"></div><pre class="text">  bytes=0-499
    937920</pre> </li>
    938921         <li>The second 500 bytes (byte offsets 500-999, inclusive):
    939             <div id="rfc.figure.u.18"></div><pre class="text">  bytes=500-999
     922            <div id="rfc.figure.u.16"></div><pre class="text">  bytes=500-999
    940923</pre> </li>
    941924         <li>The final 500 bytes (byte offsets 9500-9999, inclusive):
    942             <div id="rfc.figure.u.19"></div><pre class="text">  bytes=-500
    943 </pre> Or: <div id="rfc.figure.u.20"></div><pre class="text">  bytes=9500-
     925            <div id="rfc.figure.u.17"></div><pre class="text">  bytes=-500
     926</pre> Or: <div id="rfc.figure.u.18"></div><pre class="text">  bytes=9500-
    944927</pre> </li>
    945928         <li>The first and last bytes only (bytes 0 and 9999):
    946             <div id="rfc.figure.u.21"></div><pre class="text">  bytes=0-0,-1
     929            <div id="rfc.figure.u.19"></div><pre class="text">  bytes=0-0,-1
    947930</pre> </li>
    948931         <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive):
    949             <div id="rfc.figure.u.22"></div><pre class="text">  bytes=500-600,601-999
     932            <div id="rfc.figure.u.20"></div><pre class="text">  bytes=500-600,601-999
    950933  bytes=500-700,601-999
    951934</pre> </li>
    … …  
    955938         body, instead of the entire representation body.
    956939      </p>
    957       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.19"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
     940      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.19"></span>  <a href="#range.retrieval.requests" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a>
    958941  <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = <a href="#range.units" class="smpl">other-range-unit</a> "=" <a href="#range.retrieval.requests" class="smpl">other-range-set</a>
    959   <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#notation" class="smpl">CHAR</a>
     942  <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#imported.abnf" class="smpl">CHAR</a>
    960943</pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header field. However, origin servers and intermediate caches ought to support byte ranges when possible,
    961944         since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large
    … …  
    10921075      </p>
    10931076      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    1094       <p id="rfc.section.8.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     1077      <p id="rfc.section.8.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    10951078      </p>
    10961079      <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References
    … …  
    12241207         </p>
    12251208      </div>
    1226       <div id="rfc.figure.u.24"></div>
     1209      <div id="rfc.figure.u.22"></div>
    12271210      <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
    12281211  Date: Wed, 15 Nov 1995 06:25:24 GMT
    … …  
    12411224  ...the second range
    12421225  --THIS_STRING_SEPARATES--
    1243 </pre><div id="rfc.figure.u.25"></div>
     1226</pre><div id="rfc.figure.u.23"></div>
    12441227      <p>Another example, using the "exampleunit" range unit:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
    12451228  Date: Tue, 14 Nov 1995 06:25:24 GMT
    … …  
    12761259      <p id="rfc.section.B.p.4">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
    12771260      </p>
    1278       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     1261      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
     1262      <p id="rfc.section.C.p.1">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     1263         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
     1264         character).
     1265      </p>
     1266      <p id="rfc.section.C.p.2">Note that all rules derived from <a href="#imported.abnf" class="smpl">token</a> are to be compared case-insensitively, like <a href="#range.units" class="smpl">range-unit</a> and <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>.
     1267      </p>
     1268      <p id="rfc.section.C.p.3">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>:
     1269      </p>
     1270      <div id="rfc.figure.u.24"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>        = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     1271  <a href="#imported.abnf" class="smpl">token</a>      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     1272</pre><p id="rfc.section.C.p.5">The rules below are defined in other parts:</p>
     1273      <div id="rfc.figure.u.25"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>  = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a>&gt;
     1274  <a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>&gt;
     1275</pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    12791276      <div id="rfc.figure.u.26"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges
    12801277
    12811278<a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range-spec / other-content-range-spec
    12821279
    1283 <a href="#core.rules" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 5.1&gt;
     1280<a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 5.1&gt;
    12841281
    12851282<a href="#header.if-range" class="smpl">If-Range</a> = entity-tag / HTTP-date
    12861283
    1287 <a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
     1284<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
    12881285
    12891286<a href="#range.retrieval.requests" class="smpl">Range</a> = byte-ranges-specifier / other-ranges-specifier
    … …  
    13021299<a href="#range.units" class="smpl">bytes-unit</a> = "bytes"
    13031300
    1304 <a href="#abnf.dependencies" class="smpl">entity-tag</a> = &lt;entity-tag, defined in [Part4], Section 2.3&gt;
     1301<a href="#imported.abnf" class="smpl">entity-tag</a> = &lt;entity-tag, defined in [Part4], Section 2.3&gt;
    13051302
    13061303<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT
    … …  
    13211318<a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT
    13221319
    1323 <a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
    1324 </pre> <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    1325       <p id="rfc.section.D.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D">http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D</a>&gt;.
    1326       </p>
    1327       <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p5-range-19</a></h2>
    1328       <p id="rfc.section.D.1.p.1">Closed issues: </p>
     1320<a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
     1321</pre> <h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     1322      <p id="rfc.section.E.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D">http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D</a>&gt;.
     1323      </p>
     1324      <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p5-range-19</a></h2>
     1325      <p id="rfc.section.E.1.p.1">Closed issues: </p>
    13291326      <ul>
    13301327         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>&gt;: "ABNF list expansion code problem"
    … …  
    14131410            </li>
    14141411            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    1415                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2.1</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">8</a>, <a href="#Part1"><b>9.1</b></a><ul>
     1412                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">8</a>, <a href="#Part1"><b>9.1</b></a>, <a href="#rfc.xref.Part1.4">C</a>, <a href="#rfc.xref.Part1.5">C</a>, <a href="#rfc.xref.Part1.6">C</a><ul>
    14161413                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
    14171414                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a></li>
    1418                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.2.1</a></li>
    1419                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2.1</a></li>
    1420                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">8</a></li>
     1415                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">C</a></li>
     1416                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">C</a></li>
     1417                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">8</a></li>
    14211418                     </ul>
    14221419                  </li>
    1423                   <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.2.1</a>, <a href="#rfc.xref.Part2.2">1.2.1</a>, <a href="#Part2"><b>9.1</b></a><ul>
    1424                         <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">1.2.1</a></li>
     1420                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#Part2"><b>9.1</b></a>, <a href="#rfc.xref.Part2.1">C</a><ul>
     1421                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">C</a></li>
    14251422                     </ul>
    14261423                  </li>
    1427                   <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2.2</a>, <a href="#rfc.xref.Part4.2">4.2</a>, <a href="#rfc.xref.Part4.3">4.2</a>, <a href="#rfc.xref.Part4.4">5.3</a>, <a href="#rfc.xref.Part4.5">5.3</a>, <a href="#Part4"><b>9.1</b></a><ul>
    1428                         <li><em>Section 2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.3">4.2</a>, <a href="#rfc.xref.Part4.4">5.3</a>, <a href="#rfc.xref.Part4.5">5.3</a></li>
    1429                         <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1.2.2</a>, <a href="#rfc.xref.Part4.2">4.2</a></li>
     1424                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.2</a>, <a href="#rfc.xref.Part4.2">4.2</a>, <a href="#rfc.xref.Part4.3">5.3</a>, <a href="#rfc.xref.Part4.4">5.3</a>, <a href="#Part4"><b>9.1</b></a>, <a href="#rfc.xref.Part4.5">C</a><ul>
     1425                        <li><em>Section 2.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">4.2</a>, <a href="#rfc.xref.Part4.3">5.3</a>, <a href="#rfc.xref.Part4.4">5.3</a></li>
     1426                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.2</a>, <a href="#rfc.xref.Part4.5">C</a></li>
    14301427                     </ul>
    14311428                  </li>
    … …  
    14501447                     </ul>
    14511448                  </li>
    1452                   <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="#RFC5234"><b>9.1</b></a><ul>
    1453                         <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
     1449                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#RFC5234"><b>9.1</b></a>, <a href="#rfc.xref.RFC5234.2">C</a><ul>
     1450                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">C</a></li>
    14541451                     </ul>
    14551452                  </li>

  • draft-ietf-httpbis/latest/p5-range.xml

    r1804 r1805  
    207207
    208208<section title="Syntax Notation" anchor="notation">
    209   <x:anchor-alias value="ALPHA"/>
    210   <x:anchor-alias value="CHAR"/>
    211   <x:anchor-alias value="CR"/>
    212   <x:anchor-alias value="DIGIT"/>
    213   <x:anchor-alias value="LF"/>
    214   <x:anchor-alias value="OCTET"/>
    215   <x:anchor-alias value="SP"/>
    216   <x:anchor-alias value="VCHAR"/>
    217209<t>
    218210   This specification uses the Augmented Backus-Naur Form (ABNF) notation
    219211   of <xref target="RFC5234"/> with the list rule extension defined in
    220    &notation;.  <xref target="collected.abnf"/> shows the collected ABNF
     212   &notation;. <xref target="imported.abnf"/> describes rules imported from
     213   other documents. <xref target="collected.abnf"/> shows the collected ABNF
    221214   with the list rule expanded.
    222215</t>
    223 <t>
    224   The following core rules are included by
    225   reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
    226   ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
    227   DIGIT (decimal 0-9), DQUOTE (double quote),
    228   HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
    229   OCTET (any 8-bit sequence of data), SP (space), and
    230   VCHAR (any visible US-ASCII character).
    231 </t>
    232 
    233 <t>
    234   Note that all rules derived from <x:ref>token</x:ref> are to
    235   be compared case-insensitively, like <x:ref>range-unit</x:ref> and
    236   <x:ref>acceptable-ranges</x:ref>.
    237 </t>
    238 
    239 <section title="Core Rules" anchor="core.rules">
    240   <x:anchor-alias value="token"/>
    241   <x:anchor-alias value="OWS"/>
    242   <x:anchor-alias value="HTTP-date"/>
    243 <t>
    244   The core rules below are defined in <xref target="Part1"/> and
    245   <xref target="Part2"/>:
    246 </t>
    247 <figure><artwork type="abnf2616">
    248   <x:ref>OWS</x:ref>        = &lt;OWS, defined in &whitespace;&gt;
    249   <x:ref>token</x:ref>      = &lt;token, defined in &field-components;&gt;
    250   <x:ref>HTTP-date</x:ref>  = &lt;HTTP-date, defined in &http-date;&gt;
    251 </artwork></figure>
    252 </section>
    253 
    254 <section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
    255   <x:anchor-alias value="entity-tag"/>
    256 <t>
    257   The ABNF rules below are defined in other parts:
    258 </t>
    259 <figure><!--Part4--><artwork type="abnf2616">
    260   <x:ref>entity-tag</x:ref> = &lt;entity-tag, defined in &entity-tags;&gt;
    261 </artwork></figure>
    262 </section>
    263 
    264216</section>
    265217
    … …  
    14221374</section>
    14231375
     1376<section title="Imported ABNF" anchor="imported.abnf">
     1377  <x:anchor-alias value="ALPHA"/>
     1378  <x:anchor-alias value="CHAR"/>
     1379  <x:anchor-alias value="CR"/>
     1380  <x:anchor-alias value="DIGIT"/>
     1381  <x:anchor-alias value="LF"/>
     1382  <x:anchor-alias value="OCTET"/>
     1383  <x:anchor-alias value="SP"/>
     1384  <x:anchor-alias value="VCHAR"/>
     1385  <x:anchor-alias value="token"/>
     1386  <x:anchor-alias value="OWS"/>
     1387  <x:anchor-alias value="HTTP-date"/>
     1388  <x:anchor-alias value="entity-tag"/>
     1389<t>
     1390  The following core rules are included by
     1391  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
     1392  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
     1393  DIGIT (decimal 0-9), DQUOTE (double quote),
     1394  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
     1395  OCTET (any 8-bit sequence of data), SP (space), and
     1396  VCHAR (any visible US-ASCII character).
     1397</t>
     1398<t>
     1399  Note that all rules derived from <x:ref>token</x:ref> are to
     1400  be compared case-insensitively, like <x:ref>range-unit</x:ref> and
     1401  <x:ref>acceptable-ranges</x:ref>.
     1402</t>
     1403<t>
     1404  The rules below are defined in <xref target="Part1"/>:
     1405</t>
     1406<figure><artwork type="abnf2616">
     1407  <x:ref>OWS</x:ref>        = &lt;OWS, defined in &whitespace;&gt;
     1408  <x:ref>token</x:ref>      = &lt;token, defined in &field-components;&gt;
     1409</artwork></figure>
     1410<t>
     1411  The rules below are defined in other parts:
     1412</t>
     1413<figure><artwork type="abnf2616">
     1414  <x:ref>HTTP-date</x:ref>  = &lt;HTTP-date, defined in &http-date;&gt;
     1415  <x:ref>entity-tag</x:ref> = &lt;entity-tag, defined in &entity-tags;&gt;
     1416</artwork></figure>
     1417</section>
     1418
    14241419<?BEGININC p5-range.abnf-appendix ?>
    14251420<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">

  • draft-ietf-httpbis/latest/p6-cache.html

    r1803 r1805  
    487487      <link rel="Chapter" href="#rfc.section.12" title="12 References">
    488488      <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
    489       <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    490       <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
     489      <link rel="Appendix" title="B Imported ABNF" href="#rfc.section.B">
     490      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
     491      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    491492      <link href="p5-range.html" rel="prev">
    492493      <link href="p7-auth.html" rel="next">
    … …  
    559560      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    560561      </p> 
    561       <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p6-cache-19">Appendix&nbsp;C.1</a>.
     562      <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p6-cache-19">Appendix&nbsp;D.1</a>.
    562563      </p>
    563564      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    … …  
    593594               <li>1.3&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
    594595               <li>1.4&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
    595                      <li>1.4.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    596                      <li>1.4.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    597                      <li>1.4.3&nbsp;&nbsp;&nbsp;<a href="#delta-seconds">Delta Seconds</a></li>
     596                     <li>1.4.1&nbsp;&nbsp;&nbsp;<a href="#delta-seconds">Delta Seconds</a></li>
    598597                  </ul>
    599598               </li>
    … …  
    684683         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    685684         <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    686          <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    687          <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    688                <li>C.1&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p6-cache-19</a></li>
     685         <li>B.&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
     686         <li>C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     687         <li>D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     688               <li>D.1&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p6-cache-19</a></li>
    689689            </ul>
    690690         </li>
    … …  
    807807      </p>
    808808      <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    809       <p id="rfc.section.1.4.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF with the list rule expanded.
    810       </p>
    811       <p id="rfc.section.1.4.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    812          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
    813          character).
    814       </p>
    815       <h3 id="rfc.section.1.4.1"><a href="#rfc.section.1.4.1">1.4.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    816       <p id="rfc.section.1.4.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>:
    817       </p>
    818       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    819   <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    820   <a href="#core.rules" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    821 </pre><h3 id="rfc.section.1.4.2"><a href="#rfc.section.1.4.2">1.4.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    822       <p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p>
    823       <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">field-name</a>    = &lt;field-name, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
    824   <a href="#abnf.dependencies" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a>&gt;
    825   <a href="#abnf.dependencies" class="smpl">port</a>          = &lt;port, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>&gt;
    826   <a href="#abnf.dependencies" class="smpl">pseudonym</a>     = &lt;pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a>&gt;
    827   <a href="#abnf.dependencies" class="smpl">uri-host</a>      = &lt;uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>&gt;
    828 </pre><h3 id="rfc.section.1.4.3"><a href="#rfc.section.1.4.3">1.4.3</a>&nbsp;<a id="delta-seconds" href="#delta-seconds">Delta Seconds</a></h3>
    829       <p id="rfc.section.1.4.3.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
    830       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    831 </pre><p id="rfc.section.1.4.3.p.3">If an implementation receives a delta-seconds value larger than the largest positive integer it can represent, or if any of
     809      <p id="rfc.section.1.4.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;B</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF with the list rule expanded.
     810      </p>
     811      <h3 id="rfc.section.1.4.1"><a href="#rfc.section.1.4.1">1.4.1</a>&nbsp;<a id="delta-seconds" href="#delta-seconds">Delta Seconds</a></h3>
     812      <p id="rfc.section.1.4.1.p.1">The delta-seconds rule specifies a non-negative integer, representing time in seconds.</p>
     813      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
     814</pre><p id="rfc.section.1.4.1.p.3">If an implementation receives a delta-seconds value larger than the largest positive integer it can represent, or if any of
    832815         its subsequent calculations overflows, it <em class="bcp14">MUST</em> consider the value to be 2147483648 (2<sup>31</sup>). Recipients parsing a delta-seconds value <em class="bcp14">MUST</em> use an arithmetic type of at least 31 bits of range, and senders <em class="bcp14">MUST NOT</em> send delta-seconds with a value greater than 2147483648.
    833816      </p>
    … …  
    835818      <div id="rfc.iref.c.5"></div>
    836819      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="caching.overview" href="#caching.overview">Overview of Cache Operation</a></h1>
    837       <p id="rfc.section.2.p.1">Proper cache operation preserves the semantics of HTTP transfers (<a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>) while eliminating the transfer of information already held in the cache. Although caching is an entirely <em class="bcp14">OPTIONAL</em> feature of HTTP, we assume that reusing the cached response is desirable and that such reuse is the default behavior when
     820      <p id="rfc.section.2.p.1">Proper cache operation preserves the semantics of HTTP transfers (<a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>) while eliminating the transfer of information already held in the cache. Although caching is an entirely <em class="bcp14">OPTIONAL</em> feature of HTTP, we assume that reusing the cached response is desirable and that such reuse is the default behavior when
    838821         no requirement or locally-desired configuration prevents it. Therefore, HTTP cache requirements are focused on preventing
    839822         a cache from either storing a non-reusable response or reusing a stored response inappropriately.
    … …  
    887870      </p>
    888871      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="incomplete.responses" href="#incomplete.responses">Storing Incomplete Responses</a></h2>
    889       <p id="rfc.section.3.1.p.1">A response message is considered complete when all of the octets indicated by the message framing (<a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) are received prior to the connection being closed. If the request is GET, the response status is <a href="p2-semantics.html#status.200" class="smpl">200
     872      <p id="rfc.section.3.1.p.1">A response message is considered complete when all of the octets indicated by the message framing (<a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) are received prior to the connection being closed. If the request is GET, the response status is <a href="p2-semantics.html#status.200" class="smpl">200
    890873            (OK)</a>, and the entire response header block has been received, a cache <em class="bcp14">MAY</em> store an incomplete response message body if the cache entry is recorded as incomplete. Likewise, a <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> response <em class="bcp14">MAY</em> be stored as if it were an incomplete <a href="p2-semantics.html#status.200" class="smpl">200
    891874            (OK)</a> cache entry. However, a cache <em class="bcp14">MUST NOT</em> store incomplete or partial content responses if it does not support the <a href="p5-range.html#range.retrieval.requests" class="smpl">Range</a> and <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> header fields or if it does not understand the range units used in those fields.
    … …  
    907890      </p>
    908891      <ul>
    909          <li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) and that of the stored response match, and
     892         <li>The presented effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) and that of the stored response match, and
    910893         </li>
    911894         <li>the request method associated with the stored response allows it to be used for the presented request, and</li>
    … …  
    931914      <p id="rfc.section.4.p.3">When a stored response is used to satisfy a request without validation, a cache <em class="bcp14">MUST</em> include a single <a href="#header.age" class="smpl">Age</a> header field (<a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section&nbsp;7.1</a>) in the response with a value equal to the stored response's current_age; see <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.1.3</a>.
    932915      </p>
    933       <p id="rfc.section.4.p.4">A cache <em class="bcp14">MUST</em> write through requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 2.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>) to the origin server; i.e., a cache is not allowed to generate a reply to such a request before having forwarded the request
     916      <p id="rfc.section.4.p.4">A cache <em class="bcp14">MUST</em> write through requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 2.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>) to the origin server; i.e., a cache is not allowed to generate a reply to such a request before having forwarded the request
    934917         and having received a corresponding response.
    935918      </p>
    … …  
    957940         constraints on their results.
    958941      </p>
    959       <div id="rfc.figure.u.4"></div>
     942      <div id="rfc.figure.u.2"></div>
    960943      <p>The calculation to determine if a response is fresh is:</p>  <pre class="text">   response_is_fresh = (freshness_lifetime &gt; current_age)
    961944</pre> <p id="rfc.section.4.1.p.6">The freshness_lifetime is defined in <a href="#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section&nbsp;4.1.1</a>; the current_age is defined in <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.1.3</a>.
    … …  
    985968      <h3 id="rfc.section.4.1.2"><a href="#rfc.section.4.1.2">4.1.2</a>&nbsp;<a id="heuristic.freshness" href="#heuristic.freshness">Calculating Heuristic Freshness</a></h3>
    986969      <p id="rfc.section.4.1.2.p.1">If no explicit expiration time is present in a stored response that has a status code whose definition allows heuristic freshness
    987          to be used (including the following in <a href="p2-semantics.html#status.codes" title="Status Codes">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>: <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, <a href="p2-semantics.html#status.203" class="smpl">203 (Non-Authoritative Information)</a>, <a href="p5-range.html#status.206" class="smpl">206 (Partial
     970         to be used (including the following in <a href="p2-semantics.html#status.codes" title="Status Codes">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>: <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, <a href="p2-semantics.html#status.203" class="smpl">203 (Non-Authoritative Information)</a>, <a href="p5-range.html#status.206" class="smpl">206 (Partial
    988971            Content)</a>, <a href="p2-semantics.html#status.300" class="smpl">300 (Multiple Choices)</a>, <a href="p2-semantics.html#status.301" class="smpl">301 (Moved
    989972            Permanently)</a> and <a href="p2-semantics.html#status.410" class="smpl">410 (Gone)</a>), a cache <em class="bcp14">MAY</em> calculate a heuristic expiration time. A cache <em class="bcp14">MUST NOT</em> use heuristics to determine freshness for responses with status codes that do not explicitly allow it.
    … …  
    10181001      <ul class="empty">
    10191002         <li>HTTP/1.1 requires origin servers to send a <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field, if possible, with every response, giving the time at which the response was generated. The term "date_value"
    1020             denotes the value of the Date header field, in a form appropriate for arithmetic operations. See <a href="p2-semantics.html#header.date" title="Date">Section 9.10</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a> for the definition of the Date header field, and for requirements regarding responses without it.
     1003            denotes the value of the Date header field, in a form appropriate for arithmetic operations. See <a href="p2-semantics.html#header.date" title="Date">Section 9.10</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a> for the definition of the Date header field, and for requirements regarding responses without it.
    10211004         </li>
    10221005      </ul>
    … …  
    10451028         </li>
    10461029      </ol>
    1047       <div id="rfc.figure.u.5"></div> <pre class="text">  apparent_age = max(0, response_time - date_value);
     1030      <div id="rfc.figure.u.3"></div> <pre class="text">  apparent_age = max(0, response_time - date_value);
    10481031
    10491032  response_delay = response_time - request_time;
    10501033  corrected_age_value = age_value + response_delay; 
    1051 </pre> <div id="rfc.figure.u.6"></div>
     1034</pre> <div id="rfc.figure.u.4"></div>
    10521035      <p>These <em class="bcp14">SHOULD</em> be combined as
    10531036      </p>  <pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
    … …  
    10571040         was last validated by the origin server to the corrected_initial_age.
    10581041      </p>
    1059       <div id="rfc.figure.u.7"></div><pre class="text">  resident_time = now - response_time;
     1042      <div id="rfc.figure.u.5"></div><pre class="text">  resident_time = now - response_time;
    10601043  current_age = corrected_initial_age + resident_time;
    10611044</pre><p id="rfc.section.4.1.3.p.14">Additionally, to avoid common problems in date parsing:</p>
    … …  
    11491132      <ul>
    11501133         <li>adding or removing whitespace, where allowed in the header field's syntax</li>
    1151          <li>combining multiple header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>)
     1134         <li>combining multiple header fields with the same field name (see <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>)
    11521135         </li>
    11531136         <li>normalizing both header field values in a way that is known to have identical semantics, according to the header field's specification
    … …  
    12001183      </ul>
    12011184      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="invalidation.after.updates.or.deletions" href="#invalidation.after.updates.or.deletions">Request Methods that Invalidate</a></h1>
    1202       <p id="rfc.section.6.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 2.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin server, intervening caches can use them
     1185      <p id="rfc.section.6.p.1">Because unsafe request methods (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 2.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>) such as PUT, POST or DELETE have the potential for changing state on the origin server, intervening caches can use them
    12031186         to keep their contents up-to-date.
    12041187      </p>
    1205       <p id="rfc.section.6.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) as well as the URI(s) in the <a href="p2-semantics.html#header.location" class="smpl">Location</a> and <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header fields (if present) when a non-error response to a request with an unsafe method is received.
    1206       </p>
    1207       <p id="rfc.section.6.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a <a href="p2-semantics.html#header.location" class="smpl">Location</a> or <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header field if the host part of that URI differs from the host part in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). This helps prevent denial of service attacks.
    1208       </p>
    1209       <p id="rfc.section.6.p.4">A cache <em class="bcp14">MUST</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.
     1188      <p id="rfc.section.6.p.2">A cache <em class="bcp14">MUST</em> invalidate the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) as well as the URI(s) in the <a href="p2-semantics.html#header.location" class="smpl">Location</a> and <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header fields (if present) when a non-error response to a request with an unsafe method is received.
     1189      </p>
     1190      <p id="rfc.section.6.p.3">However, a cache <em class="bcp14">MUST NOT</em> invalidate a URI from a <a href="p2-semantics.html#header.location" class="smpl">Location</a> or <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a> response header field if the host part of that URI differs from the host part in the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). This helps prevent denial of service attacks.
     1191      </p>
     1192      <p id="rfc.section.6.p.4">A cache <em class="bcp14">MUST</em> invalidate the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) when it receives a non-error response to a request with a method whose safety is unknown.
    12101193      </p>
    12111194      <p id="rfc.section.6.p.5">Here, a "non-error response" is one with a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="p2-semantics.html#status.3xx" class="smpl">3xx (Redirection)</a> status code. "Invalidate" means that the cache will either remove all stored responses related to the effective request URI,
    … …  
    12241207         validated at the origin server. Age values are calculated as specified in <a href="#age.calculations" title="Calculating Age">Section&nbsp;4.1.3</a>.
    12251208      </p>
    1226       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#header.age" class="smpl">Age</a> = <a href="#delta-seconds" class="smpl">delta-seconds</a>
    1227 </pre><p id="rfc.section.7.1.p.3">Age field-values are non-negative integers, representing time in seconds (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.3</a>).
     1209      <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#header.age" class="smpl">Age</a> = <a href="#delta-seconds" class="smpl">delta-seconds</a>
     1210</pre><p id="rfc.section.7.1.p.3">Age field-values are non-negative integers, representing time in seconds (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.1</a>).
    12281211      </p>
    12291212      <p id="rfc.section.7.1.p.4">The presence of an Age header field in a response implies that a response is not first-hand. However, the converse is not
    … …  
    12511234         forms, even if one is documented to be preferred. For any directive not defined by this specification, recipients <em class="bcp14">MUST</em> accept both forms.
    12521235      </p>
    1253       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#header.cache-control" class="smpl">Cache-Control</a>   = 1#<a href="#header.cache-control" class="smpl">cache-directive</a>
    1254 
    1255   <a href="#header.cache-control" class="smpl">cache-directive</a> = <a href="#core.rules" class="smpl">token</a> [ "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) ]
     1236      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#header.cache-control" class="smpl">Cache-Control</a>   = 1#<a href="#header.cache-control" class="smpl">cache-directive</a>
     1237
     1238  <a href="#header.cache-control" class="smpl">cache-directive</a> = <a href="#imported.abnf" class="smpl">token</a> [ "=" ( <a href="#imported.abnf" class="smpl">token</a> / <a href="#imported.abnf" class="smpl">quoted-string</a> ) ]
    12561239</pre><p id="rfc.section.7.2.p.7">For the cache directives defined below, no argument is defined (nor allowed) otherwise stated otherwise.</p>
    12571240      <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="cache-request-directive" href="#cache-request-directive">Request Cache-Control Directives</a></h3>
    … …  
    12771260      <p id="rfc.section.7.2.1.3.p.1">Argument syntax: </p>
    12781261      <ul class="empty">
    1279          <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.3</a>)
     1262         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.1</a>)
    12801263         </li>
    12811264      </ul>
    … …  
    12911274      <p id="rfc.section.7.2.1.4.p.1">Argument syntax: </p>
    12921275      <ul class="empty">
    1293          <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.3</a>)
     1276         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.1</a>)
    12941277         </li>
    12951278      </ul>
    … …  
    13061289      <p id="rfc.section.7.2.1.5.p.1">Argument syntax: </p>
    13071290      <ul class="empty">
    1308          <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.3</a>)
     1291         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.1</a>)
    13091292         </li>
    13101293      </ul>
    … …  
    13381321      <p id="rfc.section.7.2.2.2.p.1">Argument syntax: </p>
    13391322      <ul class="empty">
    1340          <li>#<a href="#abnf.dependencies" class="smpl">field-name</a>
     1323         <li>#<a href="#imported.abnf" class="smpl">field-name</a>
    13411324         </li>
    13421325      </ul>
    … …  
    13601343      <p id="rfc.section.7.2.2.3.p.1">Argument syntax: </p>
    13611344      <ul class="empty">
    1362          <li>#<a href="#abnf.dependencies" class="smpl">field-name</a>
     1345         <li>#<a href="#imported.abnf" class="smpl">field-name</a>
    13631346         </li>
    13641347      </ul>
    … …  
    14101393      <p id="rfc.section.7.2.2.7.p.1">Argument syntax: </p>
    14111394      <ul class="empty">
    1412          <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.3</a>)
     1395         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.1</a>)
    14131396         </li>
    14141397      </ul>
    … …  
    14231406      <p id="rfc.section.7.2.2.8.p.1">Argument syntax: </p>
    14241407      <ul class="empty">
    1425          <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.3</a>)
     1408         <li> <a href="#delta-seconds" class="smpl">delta-seconds</a> (see <a href="#delta-seconds" title="Delta Seconds">Section&nbsp;1.4.1</a>)
    14261409         </li>
    14271410      </ul>
    … …  
    14531436         use an otherwise private response in their shared cache(s) could do so by including
    14541437      </p>
    1455       <div id="rfc.figure.u.10"></div><pre class="text">  Cache-Control: private, community="UCI"
     1438      <div id="rfc.figure.u.8"></div><pre class="text">  Cache-Control: private, community="UCI"
    14561439</pre><p id="rfc.section.7.2.3.p.5">A cache seeing this header field will act correctly even if the cache does not understand the community cache-extension, since
    14571440         it will also see and understand the private directive and thus default to the safe behavior.
    … …  
    14871470         that time.
    14881471      </p>
    1489       <p id="rfc.section.7.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a> of <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>; a sender <em class="bcp14">MUST</em> use the rfc1123-date format.
    1490       </p>
    1491       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#header.expires" class="smpl">Expires</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
    1492 </pre><div id="rfc.figure.u.12"></div>
     1472      <p id="rfc.section.7.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>; a sender <em class="bcp14">MUST</em> use the rfc1123-date format.
     1473      </p>
     1474      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#header.expires" class="smpl">Expires</a> = <a href="#imported.abnf" class="smpl">HTTP-date</a>
     1475</pre><div id="rfc.figure.u.10"></div>
    14931476      <p>For example</p>  <pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT
    14941477</pre><p id="rfc.section.7.3.p.6">A cache <em class="bcp14">MUST</em> treat other invalid date formats, especially including the value "0", as in the past (i.e., "already expired").
    … …  
    15171500         deprecates such extensions to improve interoperability.
    15181501      </p>
    1519       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span>  <a href="#header.pragma" class="smpl">Pragma</a>           = 1#<a href="#header.pragma" class="smpl">pragma-directive</a>
     1502      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span>  <a href="#header.pragma" class="smpl">Pragma</a>           = 1#<a href="#header.pragma" class="smpl">pragma-directive</a>
    15201503  <a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / <a href="#header.pragma" class="smpl">extension-pragma</a>
    1521   <a href="#header.pragma" class="smpl">extension-pragma</a> = <a href="#core.rules" class="smpl">token</a> [ "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) ]
     1504  <a href="#header.pragma" class="smpl">extension-pragma</a> = <a href="#imported.abnf" class="smpl">token</a> [ "=" ( <a href="#imported.abnf" class="smpl">token</a> / <a href="#imported.abnf" class="smpl">quoted-string</a> ) ]
    15221505</pre><p id="rfc.section.7.4.p.4">When the <a href="#header.cache-control" class="smpl">Cache-Control</a> header field is not present in a request, the no-cache request pragma-directive <em class="bcp14">MUST</em> have the same effect on caches as if "Cache-Control: no-cache" were present (see <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;7.2.1</a>).
    15231506      </p>
    … …  
    15251508         no-cache is purposefully omitted to target other <a href="#header.cache-control" class="smpl">Cache-Control</a> response directives at HTTP/1.1 caches. For example:
    15261509      </p>
    1527       <div id="rfc.figure.u.14"></div> <pre class="text">GET / HTTP/1.1
     1510      <div id="rfc.figure.u.12"></div> <pre class="text">GET / HTTP/1.1
    15281511Host: www.example.com
    15291512Cache-Control: max-age=30
    … …  
    15471530         the representation.
    15481531      </p>
    1549       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.vary" class="smpl">Vary</a> = "*" / 1#<a href="#abnf.dependencies" class="smpl">field-name</a>
     1532      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.vary" class="smpl">Vary</a> = "*" / 1#<a href="#imported.abnf" class="smpl">field-name</a>
    15501533</pre><p id="rfc.section.7.5.p.5">The set of header fields named by the Vary field value is known as the selecting header fields.</p>
    15511534      <p id="rfc.section.7.5.p.6">A server <em class="bcp14">SHOULD</em> include a Vary header field with any cacheable response that is subject to server-driven negotiation. Doing so allows a cache
    … …  
    15741557         be applied to response messages.
    15751558      </p>
    1576       <div id="rfc.figure.u.16"></div><pre class="inline"><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>  <a href="#header.warning" class="smpl">Warning</a>       = 1#<a href="#header.warning" class="smpl">warning-value</a>
     1559      <div id="rfc.figure.u.14"></div><pre class="inline"><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>  <a href="#header.warning" class="smpl">Warning</a>       = 1#<a href="#header.warning" class="smpl">warning-value</a>
    15771560 
    1578   <a href="#header.warning" class="smpl">warning-value</a> = <a href="#header.warning" class="smpl">warn-code</a> <a href="#notation" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-agent</a> <a href="#notation" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-text</a>
    1579                                         [<a href="#notation" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-date</a>]
     1561  <a href="#header.warning" class="smpl">warning-value</a> = <a href="#header.warning" class="smpl">warn-code</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-agent</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-text</a>
     1562                                        [<a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-date</a>]
    15801563 
    1581   <a href="#header.warning" class="smpl">warn-code</a>  = 3<a href="#notation" class="smpl">DIGIT</a>
    1582   <a href="#header.warning" class="smpl">warn-agent</a> = ( <a href="#abnf.dependencies" class="smpl">uri-host</a> [ ":" <a href="#abnf.dependencies" class="smpl">port</a> ] ) / <a href="#abnf.dependencies" class="smpl">pseudonym</a>
     1564  <a href="#header.warning" class="smpl">warn-code</a>  = 3<a href="#imported.abnf" class="smpl">DIGIT</a>
     1565  <a href="#header.warning" class="smpl">warn-agent</a> = ( <a href="#imported.abnf" class="smpl">uri-host</a> [ ":" <a href="#imported.abnf" class="smpl">port</a> ] ) / <a href="#imported.abnf" class="smpl">pseudonym</a>
    15831566                  ; the name or pseudonym of the server adding
    15841567                  ; the Warning header field, for use in debugging
    1585   <a href="#header.warning" class="smpl">warn-text</a>  = <a href="#core.rules" class="smpl">quoted-string</a>
    1586   <a href="#header.warning" class="smpl">warn-date</a>  = <a href="#notation" class="smpl">DQUOTE</a> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> <a href="#notation" class="smpl">DQUOTE</a>
     1568  <a href="#header.warning" class="smpl">warn-text</a>  = <a href="#imported.abnf" class="smpl">quoted-string</a>
     1569  <a href="#header.warning" class="smpl">warn-date</a>  = <a href="#imported.abnf" class="smpl">DQUOTE</a> <a href="#imported.abnf" class="smpl">HTTP-date</a> <a href="#imported.abnf" class="smpl">DQUOTE</a>
    15871570</pre><p id="rfc.section.7.6.p.5">Multiple warnings can be attached to a response (either by the origin server or by a cache), including multiple warnings with
    15881571         the same code number, only differing in warn-text.
    … …  
    18911874      </p>
    18921875      <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
    1893       <p id="rfc.section.11.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
     1876      <p id="rfc.section.11.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>.
    18941877      </p>
    18951878      <h1 id="rfc.references"><a id="rfc.section.12" href="#rfc.section.12">12.</a> References
    … …  
    19911974      <p id="rfc.section.A.p.6">Introduce Cache Directive and Warn Code Registries. (<a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;7.2.3</a> and <a href="#warn.code.extensions" title="Warn Code Extensions">Section&nbsp;7.6.8</a>)
    19921975      </p>
    1993       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     1976      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
     1977      <p id="rfc.section.B.p.1">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     1978         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
     1979         character).
     1980      </p>
     1981      <p id="rfc.section.B.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>:
     1982      </p>
     1983      <div id="rfc.figure.u.15"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     1984  <a href="#imported.abnf" class="smpl">field-name</a>    = &lt;field-name, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
     1985  <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     1986  <a href="#imported.abnf" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     1987
     1988  <a href="#imported.abnf" class="smpl">port</a>          = &lt;port, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>&gt;
     1989  <a href="#imported.abnf" class="smpl">pseudonym</a>     = &lt;pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 6.2</a>&gt;
     1990  <a href="#imported.abnf" class="smpl">uri-host</a>      = &lt;uri-host, defined in <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.8</a>&gt;
     1991</pre><p id="rfc.section.B.p.4">The rules below are defined in other parts:</p>
     1992      <div id="rfc.figure.u.16"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Semantics and Payloads">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 5.1</a>&gt;
     1993</pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    19941994      <div id="rfc.figure.u.17"></div> <pre class="inline"><a href="#header.age" class="smpl">Age</a> = delta-seconds
    19951995
    … …  
    19991999<a href="#header.expires" class="smpl">Expires</a> = HTTP-date
    20002000
    2001 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 5.1&gt;
    2002 
    2003 <a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
     2001<a href="#imported.abnf" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 5.1&gt;
     2002
     2003<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
    20042004
    20052005<a href="#header.pragma" class="smpl">Pragma</a> = *( "," OWS ) pragma-directive *( OWS "," [ OWS
    … …  
    20182018<a href="#header.pragma" class="smpl">extension-pragma</a> = token [ "=" ( token / quoted-string ) ]
    20192019
    2020 <a href="#abnf.dependencies" class="smpl">field-name</a> = &lt;field-name, defined in [Part1], Section 3.2&gt;
    2021 
    2022 <a href="#abnf.dependencies" class="smpl">port</a> = &lt;port, defined in [Part1], Section 2.8&gt;
     2020<a href="#imported.abnf" class="smpl">field-name</a> = &lt;field-name, defined in [Part1], Section 3.2&gt;
     2021
     2022<a href="#imported.abnf" class="smpl">port</a> = &lt;port, defined in [Part1], Section 2.8&gt;
    20232023<a href="#header.pragma" class="smpl">pragma-directive</a> = "no-cache" / extension-pragma
    2024 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = &lt;pseudonym, defined in [Part1], Section 6.2&gt;
    2025 
    2026 <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
    2027 
    2028 <a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
    2029 
    2030 <a href="#abnf.dependencies" class="smpl">uri-host</a> = &lt;uri-host, defined in [Part1], Section 2.8&gt;
     2024<a href="#imported.abnf" class="smpl">pseudonym</a> = &lt;pseudonym, defined in [Part1], Section 6.2&gt;
     2025
     2026<a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
     2027
     2028<a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
     2029
     2030<a href="#imported.abnf" class="smpl">uri-host</a> = &lt;uri-host, defined in [Part1], Section 2.8&gt;
    20312031
    20322032<a href="#header.warning" class="smpl">warn-agent</a> = ( uri-host [ ":" port ] ) / pseudonym
    … …  
    20362036<a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date
    20372037 ]
    2038 </pre> <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    2039       <p id="rfc.section.C.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://trac.tools.ietf.org/html/draft-ietf-httpbis-p6-cache-19#appendix-C">http://trac.tools.ietf.org/html/draft-ietf-httpbis-p6-cache-19#appendix-C</a>&gt;.
    2040       </p>
    2041       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p6-cache-19</a></h2>
    2042       <p id="rfc.section.C.1.p.1">Closed issues: </p>
     2038</pre> <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     2039      <p id="rfc.section.D.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://trac.tools.ietf.org/html/draft-ietf-httpbis-p6-cache-19#appendix-C">http://trac.tools.ietf.org/html/draft-ietf-httpbis-p6-cache-19#appendix-C</a>&gt;.
     2040      </p>
     2041      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p6-cache-19</a></h2>
     2042      <p id="rfc.section.D.1.p.1">Closed issues: </p>
    20432043      <ul>
    20442044         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/307">http://tools.ietf.org/wg/httpbis/trac/ticket/307</a>&gt;: "untangle Cache-Control ABNF"
    … …  
    21212121                        <li><tt>Cache-Control</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>7.2</b></a></li>
    21222122                        <li><tt>cache-directive</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>7.2</b></a></li>
    2123                         <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>1.4.3</b></a></li>
     2123                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>1.4.1</b></a></li>
    21242124                        <li><tt>Expires</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>7.3</b></a></li>
    21252125                        <li><tt>extension-pragma</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>7.4</b></a></li>
    … …  
    22012201            </li>
    22022202            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    2203                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a>, <a href="#rfc.xref.Part1.2">1.4</a>, <a href="#rfc.xref.Part1.3">1.4.1</a>, <a href="#rfc.xref.Part1.4">1.4.1</a>, <a href="#rfc.xref.Part1.5">1.4.1</a>, <a href="#rfc.xref.Part1.6">1.4.1</a>, <a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.9">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a>, <a href="#rfc.xref.Part1.11">3.1</a>, <a href="#rfc.xref.Part1.12">4</a>, <a href="#rfc.xref.Part1.13">4.3</a>, <a href="#rfc.xref.Part1.14">6</a>, <a href="#rfc.xref.Part1.15">6</a>, <a href="#rfc.xref.Part1.16">6</a>, <a href="#rfc.xref.Part1.17">11</a>, <a href="#Part1"><b>12.1</b></a><ul>
     2203                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a>, <a href="#rfc.xref.Part1.2">1.4</a>, <a href="#rfc.xref.Part1.3">3.1</a>, <a href="#rfc.xref.Part1.4">4</a>, <a href="#rfc.xref.Part1.5">4.3</a>, <a href="#rfc.xref.Part1.6">6</a>, <a href="#rfc.xref.Part1.7">6</a>, <a href="#rfc.xref.Part1.8">6</a>, <a href="#rfc.xref.Part1.9">11</a>, <a href="#Part1"><b>12.1</b></a>, <a href="#rfc.xref.Part1.10">B</a>, <a href="#rfc.xref.Part1.11">B</a>, <a href="#rfc.xref.Part1.12">B</a>, <a href="#rfc.xref.Part1.13">B</a>, <a href="#rfc.xref.Part1.14">B</a>, <a href="#rfc.xref.Part1.15">B</a>, <a href="#rfc.xref.Part1.16">B</a>, <a href="#rfc.xref.Part1.17">B</a><ul>
    22042204                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.4</a></li>
    22052205                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.3</a></li>
    2206                         <li><em>Section 2.8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">1.4.2</a>, <a href="#rfc.xref.Part1.10">1.4.2</a></li>
    2207                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.4.1</a></li>
    2208                         <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">1.4.2</a>, <a href="#rfc.xref.Part1.13">4.3</a></li>
    2209                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.4.1</a>, <a href="#rfc.xref.Part1.6">1.4.1</a></li>
    2210                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">4</a>, <a href="#rfc.xref.Part1.14">6</a>, <a href="#rfc.xref.Part1.15">6</a>, <a href="#rfc.xref.Part1.16">6</a></li>
    2211                         <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">1.4.2</a></li>
    2212                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.17">11</a></li>
    2213                      </ul>
    2214                   </li>
    2215                   <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.4.2</a>, <a href="#rfc.xref.Part2.2">2</a>, <a href="#rfc.xref.Part2.3">4</a>, <a href="#rfc.xref.Part2.4">4.1.2</a>, <a href="#rfc.xref.Part2.5">4.1.3</a>, <a href="#rfc.xref.Part2.6">6</a>, <a href="#rfc.xref.Part2.7">7.3</a>, <a href="#Part2"><b>12.1</b></a><ul>
    2216                         <li><em>Section 2.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">4</a>, <a href="#rfc.xref.Part2.6">6</a></li>
    2217                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">4.1.2</a></li>
    2218                         <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.4.2</a>, <a href="#rfc.xref.Part2.7">7.3</a></li>
    2219                         <li><em>Section 9.10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.5">4.1.3</a></li>
     2206                        <li><em>Section 2.8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.15">B</a>, <a href="#rfc.xref.Part1.17">B</a></li>
     2207                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">4.3</a>, <a href="#rfc.xref.Part1.12">B</a></li>
     2208                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">B</a></li>
     2209                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.13">B</a>, <a href="#rfc.xref.Part1.14">B</a></li>
     2210                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">4</a>, <a href="#rfc.xref.Part1.6">6</a>, <a href="#rfc.xref.Part1.7">6</a>, <a href="#rfc.xref.Part1.8">6</a></li>
     2211                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.16">B</a></li>
     2212                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">11</a></li>
     2213                     </ul>
     2214                  </li>
     2215                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">2</a>, <a href="#rfc.xref.Part2.2">4</a>, <a href="#rfc.xref.Part2.3">4.1.2</a>, <a href="#rfc.xref.Part2.4">4.1.3</a>, <a href="#rfc.xref.Part2.5">6</a>, <a href="#rfc.xref.Part2.6">7.3</a>, <a href="#Part2"><b>12.1</b></a>, <a href="#rfc.xref.Part2.7">B</a><ul>
     2216                        <li><em>Section 2.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">4</a>, <a href="#rfc.xref.Part2.5">6</a></li>
     2217                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">4.1.2</a></li>
     2218                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.6">7.3</a>, <a href="#rfc.xref.Part2.7">B</a></li>
     2219                        <li><em>Section 9.10</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">4.1.3</a></li>
    22202220                     </ul>
    22212221                  </li>
    … …  
    22662266                     </ul>
    22672267                  </li>
    2268                   <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.4</a>, <a href="#rfc.xref.RFC5234.2">1.4</a>, <a href="#RFC5234"><b>12.1</b></a><ul>
    2269                         <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.4</a></li>
     2268                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.4</a>, <a href="#RFC5234"><b>12.1</b></a>, <a href="#rfc.xref.RFC5234.2">B</a><ul>
     2269                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">B</a></li>
    22702270                     </ul>
    22712271                  </li>

  • draft-ietf-httpbis/latest/p6-cache.xml

    r1803 r1805  
    352352
    353353<section title="Syntax Notation" anchor="notation">
    354    <x:anchor-alias value="ALPHA"/>
    355    <x:anchor-alias value="CR"/>
    356    <x:anchor-alias value="DIGIT"/>
    357    <x:anchor-alias value="DQUOTE"/>
    358    <x:anchor-alias value="LF"/>
    359    <x:anchor-alias value="OCTET"/>
    360    <x:anchor-alias value="SP"/>
    361    <x:anchor-alias value="VCHAR"/>
    362354<t>
    363355   This specification uses the Augmented Backus-Naur Form (ABNF) notation
    364356   of <xref target="RFC5234"/> with the list rule extension defined in
    365    &notation;.  <xref target="collected.abnf"/> shows the collected ABNF
     357   &notation;. <xref target="imported.abnf"/> describes rules imported from
     358   other documents. <xref target="collected.abnf"/> shows the collected ABNF
    366359   with the list rule expanded.
    367360</t>
    368 <t>
    369    The following core rules are included by reference, as defined in <xref
    370    target="RFC5234" x:fmt="," x:sec="B.1"/>: ALPHA (letters), CR (carriage
    371    return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double
    372    quote), HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit
    373    sequence of data), SP (space), and VCHAR (any visible US-ASCII character).
    374 </t>
    375 
    376 <section title="Core Rules" anchor="core.rules">
    377    <x:anchor-alias value="quoted-string"/>
    378    <x:anchor-alias value="token"/>
    379    <x:anchor-alias value="OWS"/>
    380 <t>
    381    The core rules below are defined in <xref target="Part1"/>:
    382 </t>
    383 <figure><artwork type="abnf2616">
    384   <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
    385   <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &field-components;&gt;
    386   <x:ref>token</x:ref>         = &lt;token, defined in &field-components;&gt;
    387 </artwork></figure>
    388 </section>
    389 
    390 <section title="ABNF Rules defined in other Parts of the Specification"
    391     anchor="abnf.dependencies">
    392    <x:anchor-alias value="field-name"/>
    393    <x:anchor-alias value="HTTP-date"/>
    394    <x:anchor-alias value="port"/>
    395    <x:anchor-alias value="pseudonym"/>
    396    <x:anchor-alias value="uri-host"/>
    397 <t>
    398    The ABNF rules below are defined in other parts:
    399 </t>
    400 <figure><!--Part1--><artwork type="abnf2616">
    401   <x:ref>field-name</x:ref>    = &lt;field-name, defined in &header-fields;&gt;
    402   <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &http-date;&gt;
    403   <x:ref>port</x:ref>          = &lt;port, defined in &uri;&gt;
    404   <x:ref>pseudonym</x:ref>     = &lt;pseudonym, defined in &header-via;&gt;
    405   <x:ref>uri-host</x:ref>      = &lt;uri-host, defined in &uri;&gt;
    406 </artwork></figure>
    407 </section>
    408361
    409362<section title="Delta Seconds" anchor="delta-seconds">
    … …  
    25922545</section>
    25932546
     2547<section title="Imported ABNF" anchor="imported.abnf">
     2548   <x:anchor-alias value="ALPHA"/>
     2549   <x:anchor-alias value="CR"/>
     2550   <x:anchor-alias value="DIGIT"/>
     2551   <x:anchor-alias value="DQUOTE"/>
     2552   <x:anchor-alias value="LF"/>
     2553   <x:anchor-alias value="OCTET"/>
     2554   <x:anchor-alias value="SP"/>
     2555   <x:anchor-alias value="VCHAR"/>
     2556   <x:anchor-alias value="quoted-string"/>
     2557   <x:anchor-alias value="token"/>
     2558   <x:anchor-alias value="OWS"/>
     2559   <x:anchor-alias value="field-name"/>
     2560   <x:anchor-alias value="HTTP-date"/>
     2561   <x:anchor-alias value="port"/>
     2562   <x:anchor-alias value="pseudonym"/>
     2563   <x:anchor-alias value="uri-host"/>
     2564<t>
     2565   The following core rules are included by reference, as defined in <xref
     2566   target="RFC5234" x:fmt="," x:sec="B.1"/>: ALPHA (letters), CR (carriage
     2567   return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double
     2568   quote), HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit
     2569   sequence of data), SP (space), and VCHAR (any visible US-ASCII character).
     2570</t>
     2571<t>
     2572   The rules below are defined in <xref target="Part1"/>:
     2573</t>
     2574<figure><artwork type="abnf2616">
     2575  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
     2576  <x:ref>field-name</x:ref>    = &lt;field-name, defined in &header-fields;&gt;
     2577  <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &field-components;&gt;
     2578  <x:ref>token</x:ref>         = &lt;token, defined in &field-components;&gt;
     2579
     2580  <x:ref>port</x:ref>          = &lt;port, defined in &uri;&gt;
     2581  <x:ref>pseudonym</x:ref>     = &lt;pseudonym, defined in &header-via;&gt;
     2582  <x:ref>uri-host</x:ref>      = &lt;uri-host, defined in &uri;&gt;
     2583</artwork></figure>
     2584<t>
     2585   The rules below are defined in other parts:
     2586</t>
     2587<figure><artwork type="abnf2616">
     2588  <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &http-date;&gt;
     2589</artwork></figure>
     2590</section>
     2591
    25942592<?BEGININC p6-cache.abnf-appendix ?>
    25952593<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">

  • draft-ietf-httpbis/latest/p7-auth.html

    r1803 r1805  
    480480      <link rel="Chapter" href="#rfc.section.8" title="8 References">
    481481      <link rel="Appendix" title="A Changes from RFCs 2616 and 2617" href="#rfc.section.A">
    482       <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    483       <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
     482      <link rel="Appendix" title="B Imported ABNF" href="#rfc.section.B">
     483      <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C">
     484      <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D">
    484485      <link href="p6-cache.html" rel="prev">
    485486      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.584, 2012-06-24 15:59:38, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    … …  
    541542      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    542543      </p> 
    543       <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p7-auth-19">Appendix&nbsp;C.1</a>.
     544      <p>The changes in this draft are summarized in <a href="#changes.since.19" title="Since draft-ietf-httpbis-p7-auth-19">Appendix&nbsp;D.1</a>.
    544545      </p>
    545546      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    … …  
    572573         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    573574               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
    574                <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
    575                      <li>1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    576                   </ul>
    577                </li>
     575               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a></li>
    578576            </ul>
    579577         </li>
    … …  
    618616         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    619617         <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFCs 2616 and 2617</a></li>
    620          <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    621          <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
    622                <li>C.1&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p7-auth-19</a></li>
     618         <li>B.&nbsp;&nbsp;&nbsp;<a href="#imported.abnf">Imported ABNF</a></li>
     619         <li>C.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     620         <li>D.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     621               <li>D.1&nbsp;&nbsp;&nbsp;<a href="#changes.since.19">Since draft-ietf-httpbis-p7-auth-19</a></li>
    623622            </ul>
    624623         </li>
    … …  
    656655      </p>
    657656      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    658       <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF with the list rule expanded.
    659       </p>
    660       <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    661          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
    662          character).
    663       </p>
    664       <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    665       <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>:
    666       </p>
    667       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">BWS</a>           = &lt;BWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    668   <a href="#core.rules" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    669   <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    670   <a href="#core.rules" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
    671 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="access.authentication.framework" href="#access.authentication.framework">Access Authentication Framework</a></h1>
     657      <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>. <a href="#imported.abnf" title="Imported ABNF">Appendix&nbsp;B</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;C</a> shows the collected ABNF with the list rule expanded.
     658      </p>
     659      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="access.authentication.framework" href="#access.authentication.framework">Access Authentication Framework</a></h1>
    672660      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="challenge.and.response" href="#challenge.and.response">Challenge and Response</a></h2>
    673661      <p id="rfc.section.2.1.p.1">HTTP provides a simple challenge-response authentication mechanism that can be used by a server to challenge a client request
    … …  
    678666      <p id="rfc.section.2.1.p.2">Parameters are name-value pairs where the name is matched case-insensitively, and each parameter name <em class="bcp14">MUST</em> only occur once per challenge.
    679667      </p>
    680       <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.a.1"></span><span id="rfc.iref.a.2"></span><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.b.1"></span><span id="rfc.iref.g.3"></span>  auth-scheme    = <a href="#core.rules" class="smpl">token</a>
     668      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.a.1"></span><span id="rfc.iref.a.2"></span><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.b.1"></span><span id="rfc.iref.g.3"></span>  auth-scheme    = <a href="#imported.abnf" class="smpl">token</a>
    681669 
    682   auth-param     = <a href="#core.rules" class="smpl">token</a> <a href="#core.rules" class="smpl">BWS</a> "=" <a href="#core.rules" class="smpl">BWS</a> ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> )
    683 
    684   b64token       = 1*( <a href="#notation" class="smpl">ALPHA</a> / <a href="#notation" class="smpl">DIGIT</a> /
     670  auth-param     = <a href="#imported.abnf" class="smpl">token</a> <a href="#imported.abnf" class="smpl">BWS</a> "=" <a href="#imported.abnf" class="smpl">BWS</a> ( <a href="#imported.abnf" class="smpl">token</a> / <a href="#imported.abnf" class="smpl">quoted-string</a> )
     671
     672  b64token       = 1*( <a href="#imported.abnf" class="smpl">ALPHA</a> / <a href="#imported.abnf" class="smpl">DIGIT</a> /
    685673                       "-" / "." / "_" / "~" / "+" / "/" ) *"="
    686674</pre><p id="rfc.section.2.1.p.4">The "b64token" syntax allows the 66 unreserved URI characters (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>), plus a few others, so that it can hold a base64, base64url (URL and filename safe alphabet), base32, or base16 (hex) encoding,
    … …  
    691679      <p id="rfc.section.2.1.p.6">The <a href="#status.407" class="smpl">407 (Proxy Authentication Required)</a> response message is used by a proxy to challenge the authorization of a client and <em class="bcp14">MUST</em> include a <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> header field containing at least one challenge applicable to the proxy for the requested resource.
    692680      </p>
    693       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.c.1"></span><span id="rfc.iref.g.4"></span>  <a href="#challenge.and.response" class="smpl">challenge</a>   = <a href="#challenge.and.response" class="smpl">auth-scheme</a> [ 1*<a href="#notation" class="smpl">SP</a> ( <a href="#challenge.and.response" class="smpl">b64token</a> / #<a href="#challenge.and.response" class="smpl">auth-param</a> ) ]
     681      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.c.1"></span><span id="rfc.iref.g.4"></span>  <a href="#challenge.and.response" class="smpl">challenge</a>   = <a href="#challenge.and.response" class="smpl">auth-scheme</a> [ 1*<a href="#imported.abnf" class="smpl">SP</a> ( <a href="#challenge.and.response" class="smpl">b64token</a> / #<a href="#challenge.and.response" class="smpl">auth-param</a> ) ]
    694682</pre><div class="note" id="rfc.section.2.1.p.8">
    695683         <p> <b>Note:</b> User agents will need to take special care in parsing the <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> and <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> header field values because they can contain more than one challenge, or if more than one of each is provided, since the contents
    … …  
    711699         user as appropriate.
    712700      </p>
    713       <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.c.2"></span><span id="rfc.iref.g.5"></span>  <a href="#challenge.and.response" class="smpl">credentials</a> = <a href="#challenge.and.response" class="smpl">auth-scheme</a> [ 1*<a href="#notation" class="smpl">SP</a> ( <a href="#challenge.and.response" class="smpl">b64token</a> / #<a href="#challenge.and.response" class="smpl">auth-param</a> ) ]
     701      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.c.2"></span><span id="rfc.iref.g.5"></span>  <a href="#challenge.and.response" class="smpl">credentials</a> = <a href="#challenge.and.response" class="smpl">auth-scheme</a> [ 1*<a href="#imported.abnf" class="smpl">SP</a> ( <a href="#challenge.and.response" class="smpl">b64token</a> / #<a href="#challenge.and.response" class="smpl">auth-param</a> ) ]
    714702</pre><p id="rfc.section.2.1.p.14">Upon a request for a protected resource that omits credentials, contains invalid credentials (e.g., a bad password) or partial
    715703         credentials (e.g., when the authentication scheme requires more than one round trip), an origin server <em class="bcp14">SHOULD</em> return a <a href="#status.401" class="smpl">401 (Unauthorized)</a> response. Such responses <em class="bcp14">MUST</em> include a <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> header field containing at least one (possibly new) challenge applicable to the requested resource.
    … …  
    731719      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="protection.space" href="#protection.space">Protection Space (Realm)</a></h2>
    732720      <p id="rfc.section.2.2.p.1">The authentication parameter realm is reserved for use by authentication schemes that wish to indicate the scope of protection.</p>
    733       <p id="rfc.section.2.2.p.2">A <dfn>protection space</dfn> is defined by the canonical root URI (the scheme and authority components of the effective request URI; see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) of the server being accessed, in combination with the realm value if present. These realms allow the protected resources
     721      <p id="rfc.section.2.2.p.2">A <dfn>protection space</dfn> is defined by the canonical root URI (the scheme and authority components of the effective request URI; see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>) of the server being accessed, in combination with the realm value if present. These realms allow the protected resources
    734722         on a server to be partitioned into a set of protection spaces, each with its own authentication scheme and/or authorization
    735723         database. The realm value is a string, generally assigned by the origin server, which can have additional semantics specific
    … …  
    766754            <p>HTTP authentication is presumed to be stateless: all of the information necessary to authenticate a request <em class="bcp14">MUST</em> be provided in the request, rather than be dependent on the server remembering prior requests. Authentication based on, or
    767755               bound to, the underlying connection is outside the scope of this specification and inherently flawed unless steps are taken
    768                to ensure that the connection cannot be used by any party other than the authenticated user (see <a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.4</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     756               to ensure that the connection cannot be used by any party other than the authenticated user (see <a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    769757            </p>
    770758         </li>
    … …  
    832820            (Unauthorized)</a> response. Its value consists of credentials containing information of the user agent for the realm of the resource being requested.
    833821      </p>
    834       <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#header.authorization" class="smpl">Authorization</a> = <a href="#challenge.and.response" class="smpl">credentials</a>
     822      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#header.authorization" class="smpl">Authorization</a> = <a href="#challenge.and.response" class="smpl">credentials</a>
    835823</pre><p id="rfc.section.4.1.p.3">If a request is authenticated and a realm specified, the same credentials <em class="bcp14">SHOULD</em> be valid for all other requests within this realm (assuming that the authentication scheme itself does not require otherwise,
    836824         such as credentials that vary according to a challenge value or using synchronized clocks).
    … …  
    853841      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="header.proxy-authenticate" href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
    854842      <p id="rfc.section.4.2.p.1">The "Proxy-Authenticate" header field consists of at least one challenge that indicates the authentication scheme(s) and parameters
    855          applicable to the proxy for this effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). It <em class="bcp14">MUST</em> be included as part of a <a href="#status.407" class="smpl">407 (Proxy Authentication Required)</a> response.
    856       </p>
    857       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> = 1#<a href="#challenge.and.response" class="smpl">challenge</a>
     843         applicable to the proxy for this effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). It <em class="bcp14">MUST</em> be included as part of a <a href="#status.407" class="smpl">407 (Proxy Authentication Required)</a> response.
     844      </p>
     845      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> = 1#<a href="#challenge.and.response" class="smpl">challenge</a>
    858846</pre><p id="rfc.section.4.2.p.3">Unlike <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a>, the Proxy-Authenticate header field applies only to the current connection, and intermediaries <em class="bcp14">SHOULD NOT</em> forward it to downstream clients. However, an intermediate proxy might need to obtain its own credentials by requesting them
    859847         from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate header
    … …  
    869857         the resource being requested.
    870858      </p>
    871       <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a> = <a href="#challenge.and.response" class="smpl">credentials</a>
     859      <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a> = <a href="#challenge.and.response" class="smpl">credentials</a>
    872860</pre><p id="rfc.section.4.3.p.3">Unlike <a href="#header.authorization" class="smpl">Authorization</a>, the Proxy-Authorization header field applies only to the next outbound proxy that demanded authentication using the <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed by the first outbound proxy
    873861         that was expecting to receive credentials. A proxy <em class="bcp14">MAY</em> relay the credentials from the client request to the next proxy if that is the mechanism by which the proxies cooperatively
    … …  
    878866      <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a id="header.www-authenticate" href="#header.www-authenticate">WWW-Authenticate</a></h2>
    879867      <p id="rfc.section.4.4.p.1">The "WWW-Authenticate" header field consists of at least one challenge that indicates the authentication scheme(s) and parameters
    880          applicable to the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
     868         applicable to the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    881869      </p>
    882870      <p id="rfc.section.4.4.p.2">It <em class="bcp14">MUST</em> be included in <a href="#status.401" class="smpl">401 (Unauthorized)</a> response messages and <em class="bcp14">MAY</em> be included in other response messages to indicate that supplying credentials (or different credentials) might affect the
    883871         response.
    884872      </p>
    885       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> = 1#<a href="#challenge.and.response" class="smpl">challenge</a>
     873      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> = 1#<a href="#challenge.and.response" class="smpl">challenge</a>
    886874</pre><p id="rfc.section.4.4.p.4">User agents are advised to take special care in parsing the WWW-Authenticate field value as it might contain more than one
    887875         challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
    888876         comma-separated list of authentication parameters.
    889877      </p>
    890       <div id="rfc.figure.u.9"></div>
     878      <div id="rfc.figure.u.8"></div>
    891879      <p>For instance:</p>  <pre class="text">  WWW-Authenticate: Newauth realm="apps", type=1,
    892880                    title="Login to \"apps\"", Basic realm="simple"
    … …  
    10191007         Lawrence C. Stewart for their work on that specification. See <a href="http://tools.ietf.org/html/rfc2617#section-6">Section 6</a> of <a href="#RFC2617" id="rfc.xref.RFC2617.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a> for further acknowledgements.
    10201008      </p>
    1021       <p id="rfc.section.7.p.2">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> for the Acknowledgments related to this document revision.
     1009      <p id="rfc.section.7.p.2">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a> for the Acknowledgments related to this document revision.
    10221010      </p>
    10231011      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
    … …  
    11091097      <p id="rfc.section.A.p.4">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;4</a>)
    11101098      </p>
    1111       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
     1099      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
     1100      <p id="rfc.section.B.p.1">The following core rules are included by reference, as defined in <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a> of <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     1101         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
     1102         character).
     1103      </p>
     1104      <p id="rfc.section.B.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>:
     1105      </p>
     1106      <div id="rfc.figure.u.9"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">BWS</a>           = &lt;BWS, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     1107  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     1108  <a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     1109  <a href="#imported.abnf" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
     1110</pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    11121111      <div id="rfc.figure.u.10"></div> <pre class="inline"><a href="#header.authorization" class="smpl">Authorization</a> = credentials
    11131112
    1114 <a href="#core.rules" class="smpl">BWS</a> = &lt;BWS, defined in [Part1], Section 3.2.1&gt;
    1115 
    1116 <a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
     1113<a href="#imported.abnf" class="smpl">BWS</a> = &lt;BWS, defined in [Part1], Section 3.2.1&gt;
     1114
     1115<a href="#imported.abnf" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
    11171116
    11181117<a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> = *( "," OWS ) challenge *( OWS "," [ OWS
    … …  
    11341133 *( OWS "," [ OWS auth-param ] ) ] ) ]
    11351134
    1136 <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
    1137 
    1138 <a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
    1139 </pre> <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    1140       <p id="rfc.section.C.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://trac.tools.ietf.org/html/draft-ietf-httpbis-p7-auth-19#appendix-C">http://trac.tools.ietf.org/html/draft-ietf-httpbis-p7-auth-19#appendix-C</a>&gt;.
    1141       </p>
    1142       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p7-auth-19</a></h2>
    1143       <p id="rfc.section.C.1.p.1">Closed issues: </p>
     1135<a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
     1136
     1137<a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
     1138</pre> <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     1139      <p id="rfc.section.D.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://trac.tools.ietf.org/html/draft-ietf-httpbis-p7-auth-19#appendix-C">http://trac.tools.ietf.org/html/draft-ietf-httpbis-p7-auth-19#appendix-C</a>&gt;.
     1140      </p>
     1141      <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;<a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p7-auth-19</a></h2>
     1142      <p id="rfc.section.D.1.p.1">Closed issues: </p>
    11441143      <ul>
    11451144         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/348">http://tools.ietf.org/wg/httpbis/trac/ticket/348</a>&gt;: "Realms and scope"
    … …  
    12081207            </li>
    12091208            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    1210                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2.1</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">2.2</a>, <a href="#rfc.xref.Part1.9">2.3.1</a>, <a href="#rfc.xref.Part1.10">4.2</a>, <a href="#rfc.xref.Part1.11">4.4</a>, <a href="#rfc.xref.Part1.12">7</a>, <a href="#Part1"><b>8.1</b></a><ul>
     1209                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">2.2</a>, <a href="#rfc.xref.Part1.4">2.3.1</a>, <a href="#rfc.xref.Part1.5">4.2</a>, <a href="#rfc.xref.Part1.6">4.4</a>, <a href="#rfc.xref.Part1.7">7</a>, <a href="#Part1"><b>8.1</b></a>, <a href="#rfc.xref.Part1.8">B</a>, <a href="#rfc.xref.Part1.9">B</a>, <a href="#rfc.xref.Part1.10">B</a>, <a href="#rfc.xref.Part1.11">B</a>, <a href="#rfc.xref.Part1.12">B</a><ul>
    12111210                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
    12121211                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a></li>
    1213                         <li><em>Section 2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">2.3.1</a></li>
    1214                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a></li>
    1215                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a></li>
    1216                         <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">2.2</a>, <a href="#rfc.xref.Part1.10">4.2</a>, <a href="#rfc.xref.Part1.11">4.4</a></li>
    1217                         <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">7</a></li>
     1212                        <li><em>Section 2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">2.3.1</a></li>
     1213                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">B</a>, <a href="#rfc.xref.Part1.10">B</a></li>
     1214                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.11">B</a>, <a href="#rfc.xref.Part1.12">B</a></li>
     1215                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">2.2</a>, <a href="#rfc.xref.Part1.5">4.2</a>, <a href="#rfc.xref.Part1.6">4.4</a></li>
     1216                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">7</a></li>
    12181217                     </ul>
    12191218                  </li>
    … …  
    12461245                     </ul>
    12471246                  </li>
    1248                   <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="#RFC5234"><b>8.1</b></a><ul>
    1249                         <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
     1247                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#RFC5234"><b>8.1</b></a>, <a href="#rfc.xref.RFC5234.2">B</a><ul>
     1248                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">B</a></li>
    12501249                     </ul>
    12511250                  </li>

  • draft-ietf-httpbis/latest/p7-auth.xml

    r1803 r1805  
    193193
    194194<section title="Syntax Notation" anchor="notation">
    195   <x:anchor-alias value="ALPHA"/>
    196   <x:anchor-alias value="CR"/>
    197   <x:anchor-alias value="DIGIT"/>
    198   <x:anchor-alias value="LF"/>
    199   <x:anchor-alias value="OCTET"/>
    200   <x:anchor-alias value="VCHAR"/>
    201   <x:anchor-alias value="SP"/>
    202195<t>
    203196   This specification uses the Augmented Backus-Naur Form (ABNF) notation
    204197   of <xref target="RFC5234"/> with the list rule extension defined in
    205    &notation;.  <xref target="collected.abnf"/> shows the collected ABNF
     198   &notation;. <xref target="imported.abnf"/> describes rules imported from
     199   other documents. <xref target="collected.abnf"/> shows the collected ABNF
    206200   with the list rule expanded.
    207201</t>
    208 <t>
    209   The following core rules are included by
    210   reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
    211   ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
    212   DIGIT (decimal 0-9), DQUOTE (double quote),
    213   HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
    214   OCTET (any 8-bit sequence of data), SP (space), and
    215   VCHAR (any visible US-ASCII character).
    216 </t>
    217 
    218 <section title="Core Rules" anchor="core.rules">
    219    <x:anchor-alias value="quoted-string"/>
    220    <x:anchor-alias value="token"/>
    221    <x:anchor-alias value="BWS"/>
    222    <x:anchor-alias value="OWS"/>
    223 <t>
    224    The core rules below are defined in <xref target="Part1"/>:
    225 </t>
    226 <figure><artwork type="abnf2616">
    227   <x:ref>BWS</x:ref>           = &lt;BWS, defined in &whitespace;&gt;
    228   <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
    229   <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &field-components;&gt;
    230   <x:ref>token</x:ref>         = &lt;token, defined in &field-components;&gt;
    231 </artwork></figure>
    232 </section>
    233202</section>
    234203</section>
    … …  
    11471116</section>
    11481117 
     1118<section title="Imported ABNF" anchor="imported.abnf">
     1119  <x:anchor-alias value="ALPHA"/>
     1120  <x:anchor-alias value="CR"/>
     1121  <x:anchor-alias value="DIGIT"/>
     1122  <x:anchor-alias value="LF"/>
     1123  <x:anchor-alias value="OCTET"/>
     1124  <x:anchor-alias value="VCHAR"/>
     1125  <x:anchor-alias value="SP"/>
     1126  <x:anchor-alias value="quoted-string"/>
     1127  <x:anchor-alias value="token"/>
     1128  <x:anchor-alias value="BWS"/>
     1129  <x:anchor-alias value="OWS"/>
     1130<t>
     1131  The following core rules are included by
     1132  reference, as defined in <xref target="RFC5234" x:fmt="of" x:sec="B.1"/>:
     1133  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
     1134  DIGIT (decimal 0-9), DQUOTE (double quote),
     1135  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
     1136  OCTET (any 8-bit sequence of data), SP (space), and
     1137  VCHAR (any visible US-ASCII character).
     1138</t>
     1139<t>
     1140   The rules below are defined in <xref target="Part1"/>:
     1141</t>
     1142<figure><artwork type="abnf2616">
     1143  <x:ref>BWS</x:ref>           = &lt;BWS, defined in &whitespace;&gt;
     1144  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
     1145  <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &field-components;&gt;
     1146  <x:ref>token</x:ref>         = &lt;token, defined in &field-components;&gt;
     1147</artwork></figure>
     1148</section>
     1149
    11491150<?BEGININC p7-auth.abnf-appendix ?>
    11501151<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
Note: See TracChangeset for help on using the changeset viewer.