Changeset 2748


Ignore:
Timestamp:
Jan 3, 2016, 4:39:18 AM (3 years ago)
Author:
julian.reschke@…
Message:

Update XSLTs, fix Makefile wrt sorting of ABNF, regen HTML

Files:
17 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/Makefile

    r2734 r2748  
    6767
    6868%.parsed-abnf: %.abnf
    69         $(bap)/bap -i $(bap)/core.abnf < $< | sort | $(bap)/bap -k -i $(bap)/core.abnf -l 69 >$@
     69        $(bap)/bap -i $(bap)/core.abnf < $< | LC_ALL=C sort | $(bap)/bap -k -i $(bap)/core.abnf -l 69 >$@
    7070
    7171%.abnf-appendix: %.parsed-abnf
  • draft-ietf-httpbis/latest/common-abnf.sh

    r2667 r2748  
    1818        fgrep -v ", defined in [RFC723" | \
    1919        fgrep -v ", see [RFC723" | \
    20         sort | uniq | \
     20        LC_ALL=C sort | uniq | \
    2121        $bap/bap -k -i $bap/core.abnf
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2734 r2748  
    44   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    6       <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title><script>
     6      <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title><script type="application/javascript">
    77var buttonsAdded = false;
    88
     
    1717
    1818function feedback() {
    19   toggleButtonsToElementsByName("h1");
    2019  toggleButtonsToElementsByName("h2");
    2120  toggleButtonsToElementsByName("h3");
    2221  toggleButtonsToElementsByName("h4");
     22  toggleButtonsToElementsByName("h5");
    2323
    2424  buttonsAdded = !buttonsAdded;
     
    147147  margin-left: 0em;
    148148}
     149dl.reference > dt {
     150  font-weight: bold;
     151}
     152dl.reference > dd {
     153  margin-left: 6em;
     154}
    149155h1 {
     156  color: green;
     157  font-size: 150%;
     158  line-height: 18pt;
     159  font-weight: bold;
     160  text-align: center;
     161  margin-top: 36pt;
     162  margin-bottom: 0pt;
     163}
     164h2 {
    150165  font-size: 130%;
    151166  line-height: 21pt;
    152167  page-break-after: avoid;
    153168}
    154 h1.np {
     169h2.np {
    155170  page-break-before: always;
    156171}
    157 h2 {
     172h3 {
    158173  font-size: 120%;
    159174  line-height: 15pt;
    160175  page-break-after: avoid;
    161176}
    162 h3 {
     177h4 {
    163178  font-size: 110%;
    164179  page-break-after: avoid;
    165180}
    166 h4, h5, h6 {
     181h5, h6 {
    167182  page-break-after: avoid;
    168183}
     
    266281  border-width: 2px;
    267282}
    268 table.left {
     283table.tleft {
    269284  margin-right: auto;
    270285}
    271 table.right {
     286table.tright {
    272287  margin-left: auto;
    273288}
    274 table.center {
     289table.tcenter {
    275290  margin-left: auto;
    276291  margin-right: auto;
     
    303318  color: white;
    304319}
    305 td.reference {
    306   vertical-align: top;
    307   white-space: nowrap;
    308   padding-right: 1em;
    309 }
    310320thead {
    311321  display:table-header-group;
     
    333343  margin-left: 0em;
    334344}
    335 .title, .filename, h1, h2, h3, h4 {
     345.filename, h1, h2, h3, h4 {
    336346  font-family: candara, calibri, segoe, optima, arial, sans-serif;
    337347}
     
    381391.filename {
    382392  color: #333333;
    383   font-size: 75%;
     393  font-size: 112%;
    384394  font-weight: bold;
    385395  line-height: 21pt;
    386396  text-align: center;
     397  margin-top: 0pt;
    387398}
    388399.fn {
     
    394405.right {
    395406  text-align: right;
    396 }
    397 .title {
    398   color: green;
    399   font-size: 150%;
    400   line-height: 18pt;
    401   font-weight: bold;
    402   text-align: center;
    403   margin-top: 36pt;
    404407}
    405408.warning {
     
    428431  border: 1px solid silver;
    429432  border-radius: 5px;
     433}
     434.publishedasrfc {
     435  background-color: yellow;
     436  color: green;
     437  font-size: 14pt;
     438  text-align: center;
    430439}
    431440
     
    528537      <link rel="Alternate" title="RFC7230" href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7230.html">
    529538      <link href="p2-semantics.html" rel="next">
    530       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.710, 2014/12/09 13:12:18, XSLT vendor: Saxonica http://www.saxonica.com/">
     539      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.756, 2015/12/31 17:59:21, XSLT vendor: Saxonica http://www.saxonica.com/">
    531540      <meta name="keywords" content="Hypertext Transfer Protocol, HTTP, HTTP message format">
    532541      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     
    571580         </tbody>
    572581      </table>
    573       <p class="title" id="rfc.title">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing<br><span class="filename">draft-ietf-httpbis-p1-messaging-latest</span></p>
    574       <p style="color: green; text-align: center; font-size: 14pt; background-color: yellow;"><b>Note:</b> a later version of this document has been published as <a href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7230.html">RFC7230</a>.
     582      <div id="rfc.title">
     583         <h1>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</h1>
     584         <div class="filename">draft-ietf-httpbis-p1-messaging-latest</div>
     585      </div>
     586      <p class="publishedasrfc"><b>Note:</b> a later version of this document has been published as <a href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7230.html">RFC7230</a>.
    575587         
    576588      </p>
    577       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
     589      <h2 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h2>
    578590      <p>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for
    579591         distributed, collaborative, hypertext information systems. This document provides
     
    582594         syntax and parsing requirements, and describes related security concerns for implementations.
    583595      </p>
    584       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
     596      <h2 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h2>
    585597      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org),
    586598         which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
     
    592604      </p>
    593605      <div id="rfc.status">
    594          <h1><a href="#rfc.status">Status of This Memo</a></h1>
     606         <h2><a href="#rfc.status">Status of This Memo</a></h2>
    595607         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78
    596608            and BCP 79.
     
    607619      </div>
    608620      <div id="rfc.copyrightnotice">
    609          <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     621         <h2><a href="#rfc.copyrightnotice">Copyright Notice</a></h2>
    610622         <p>Copyright © 2014 IETF Trust and the persons identified as the document authors. All
    611623            rights reserved.
     
    630642      <hr class="noprint">
    631643      <div id="rfc.toc">
    632          <h1 class="np"><a href="#rfc.toc">Table of Contents</a></h1>
     644         <h2 class="np"><a href="#rfc.toc">Table of Contents</a></h2>
    633645         <ul class="toc">
    634646            <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     
    783795      </div>
    784796      <div id="introduction">
    785          <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     797         <h2 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h2>
    786798         <div id="rfc.section.1.p.1">
    787799            <p>The Hypertext Transfer Protocol (HTTP) is a stateless application-level request/response
     
    842854         </div>
    843855         <div id="intro.requirements">
    844             <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements Notation</a></h2>
     856            <h3 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements Notation</a></h3>
    845857            <div id="rfc.section.1.1.p.1">
    846858               <p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
     
    855867         </div>
    856868         <div id="notation">
    857             <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     869            <h3 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h3>
    858870            <div id="rfc.section.1.2.p.1">
    859871               <p>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 a list extension, defined in <a href="#abnf.extension" title="ABNF List Extension: #rule">Section&nbsp;7</a>, that allows for compact definition of comma-separated lists using a '#' operator
     
    877889      </div>
    878890      <div id="architecture">
    879          <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#architecture">Architecture</a></h1>
     891         <h2 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#architecture">Architecture</a></h2>
    880892         <div id="rfc.section.2.p.1">
    881893            <p>HTTP was created for the World Wide Web (WWW) architecture and has evolved over time
     
    885897         </div>
    886898         <div id="operation">
    887             <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#operation">Client/Server Messaging</a></h2>
     899            <h3 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#operation">Client/Server Messaging</a></h3>
    888900            <div id="rfc.section.2.1.p.1">
    889901               <p>HTTP is a stateless request/response protocol that operates by exchanging <dfn>messages</dfn> (<a href="#http.message" title="Message Format">Section&nbsp;3</a>) across a reliable transport- or session-layer "<dfn>connection</dfn>" (<a href="#connection.management" title="Connection Management">Section&nbsp;6</a>). An HTTP "<dfn>client</dfn>" is a program that establishes a connection to a server for the purpose of sending
     
    944956               </p>
    945957            </div>
    946             <div id="rfc.section.2.1.p.8">
     958            <div id="rfc.section.2.1.p.8" class="avoidbreakafter">
    947959               <p>The following example illustrates a typical message exchange for a GET request (<a href="p2-semantics.html#GET" title="GET">Section 4.3.1</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>) on the URI "http://www.example.com/hello.txt":
    948960               </p>
     
    970982         </div>
    971983         <div id="implementation-diversity">
    972             <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#implementation-diversity">Implementation Diversity</a></h2>
     984            <h3 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#implementation-diversity">Implementation Diversity</a></h3>
    973985            <div id="rfc.section.2.2.p.1">
    974986               <p>When considering the design of HTTP, it is easy to fall into a trap of thinking that
     
    10041016         </div>
    10051017         <div id="intermediaries">
    1006             <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a href="#intermediaries">Intermediaries</a></h2>
     1018            <h3 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a href="#intermediaries">Intermediaries</a></h3>
    10071019            <div id="rfc.section.2.3.p.1">
    10081020               <p>HTTP enables the use of intermediaries to satisfy requests through a chain of connections.
     
    11021114         </div>
    11031115         <div id="caches">
    1104             <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a href="#caches">Caches</a></h2>
     1116            <h3 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a href="#caches">Caches</a></h3>
    11051117            <div id="rfc.section.2.4.p.1">
    11061118               <p>A "<dfn>cache</dfn>" is a local store of previous response messages and the subsystem that controls its
     
    11401152         </div>
    11411153         <div id="conformance">
    1142             <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;<a href="#conformance">Conformance and Error Handling</a></h2>
     1154            <h3 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;<a href="#conformance">Conformance and Error Handling</a></h3>
    11431155            <div id="rfc.section.2.5.p.1">
    11441156               <p>This specification targets conformance criteria according to the role of a participant
     
    12141226         </div>
    12151227         <div id="http.version">
    1216             <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a href="#http.version">Protocol Versioning</a></h2>
     1228            <h3 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a href="#http.version">Protocol Versioning</a></h3>
    12171229            <div id="rfc.section.2.6.p.1">
    12181230               <p>HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate versions of the protocol.
     
    13221334         </div>
    13231335         <div id="uri">
    1324             <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a href="#uri">Uniform Resource Identifiers</a></h2>
     1336            <h3 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a>&nbsp;<a href="#uri">Uniform Resource Identifiers</a></h3>
    13251337            <div id="rfc.section.2.7.p.1">
    13261338               <p>Uniform Resource Identifiers (URIs) <a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> are used throughout HTTP as the means for identifying resources (<a href="p2-semantics.html#resources" title="Resources">Section 2</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). URI references are used to target requests, indicate redirects, and define relationships.
     
    13611373            </div>
    13621374            <div id="http.uri">
    1363                <h3 id="rfc.section.2.7.1"><a href="#rfc.section.2.7.1">2.7.1</a>&nbsp;<a href="#http.uri">http URI Scheme</a></h3>
     1375               <h4 id="rfc.section.2.7.1"><a href="#rfc.section.2.7.1">2.7.1</a>&nbsp;<a href="#http.uri">http URI Scheme</a></h4>
    13641376               <div id="rfc.section.2.7.1.p.1">
    13651377                  <p>The "http" URI scheme is hereby defined for the purpose of minting identifiers according
     
    14301442            </div>
    14311443            <div id="https.uri">
    1432                <h3 id="rfc.section.2.7.2"><a href="#rfc.section.2.7.2">2.7.2</a>&nbsp;<a href="#https.uri">https URI Scheme</a></h3>
     1444               <h4 id="rfc.section.2.7.2"><a href="#rfc.section.2.7.2">2.7.2</a>&nbsp;<a href="#https.uri">https URI Scheme</a></h4>
    14331445               <div id="rfc.section.2.7.2.p.1">
    14341446                  <p>The "https" URI scheme is hereby defined for the purpose of minting identifiers according
     
    14641476            </div>
    14651477            <div id="uri.comparison">
    1466                <h3 id="rfc.section.2.7.3"><a href="#rfc.section.2.7.3">2.7.3</a>&nbsp;<a href="#uri.comparison">http and https URI Normalization and Comparison</a></h3>
     1478               <h4 id="rfc.section.2.7.3"><a href="#rfc.section.2.7.3">2.7.3</a>&nbsp;<a href="#uri.comparison">http and https URI Normalization and Comparison</a></h4>
    14671479               <div id="rfc.section.2.7.3.p.1">
    14681480                  <p>Since the "http" and "https" schemes conform to the URI generic syntax, such URIs
     
    14811493                  </p>
    14821494               </div>
    1483                <div id="rfc.section.2.7.3.p.3">
     1495               <div id="rfc.section.2.7.3.p.3" class="avoidbreakafter">
    14841496                  <p>For example, the following three URIs are equivalent:</p>
    14851497               </div>
     
    14921504      </div>
    14931505      <div id="http.message">
    1494          <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#http.message">Message Format</a></h1>
     1506         <h2 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#http.message">Message Format</a></h2>
    14951507         <div id="rfc.section.3.p.1">
    14961508            <p>All HTTP/1.1 messages consist of a start-line followed by a sequence of octets in
     
    15481560         </div>
    15491561         <div id="start.line">
    1550             <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#start.line">Start Line</a></h2>
     1562            <h3 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#start.line">Start Line</a></h3>
    15511563            <div id="rfc.section.3.1.p.1">
    15521564               <p>An HTTP message can be either a request from client to server or a response from server
     
    15661578</pre></div>
    15671579            <div id="request.line">
    1568                <h3 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;<a href="#request.line">Request Line</a></h3>
     1580               <h4 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;<a href="#request.line">Request Line</a></h4>
    15691581               <div id="rfc.section.3.1.1.p.1">
    15701582                  <p>A request-line begins with a method token, followed by a single space (SP), the request-target,
     
    16211633            </div>
    16221634            <div id="status.line">
    1623                <h3 id="rfc.section.3.1.2"><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;<a href="#status.line">Status Line</a></h3>
     1635               <h4 id="rfc.section.3.1.2"><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;<a href="#status.line">Status Line</a></h4>
    16241636               <div id="rfc.section.3.1.2.p.1">
    16251637                  <p>The first line of a response message is the status-line, consisting of the protocol
     
    16531665         </div>
    16541666         <div id="header.fields">
    1655             <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.fields">Header Fields</a></h2>
     1667            <h3 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.fields">Header Fields</a></h3>
    16561668            <div id="rfc.section.3.2.p.1">
    16571669               <p>Each header field consists of a case-insensitive field name followed by a colon (":"),
     
    16761688            </div>
    16771689            <div id="field.extensibility">
    1678                <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;<a href="#field.extensibility">Field Extensibility</a></h3>
     1690               <h4 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;<a href="#field.extensibility">Field Extensibility</a></h4>
    16791691               <div id="rfc.section.3.2.1.p.1">
    16801692                  <p>Header fields are fully extensible: there is no limit on the introduction of new field
     
    17031715            </div>
    17041716            <div id="field.order">
    1705                <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a href="#field.order">Field Order</a></h3>
     1717               <h4 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a href="#field.order">Field Order</a></h4>
    17061718               <div id="rfc.section.3.2.2.p.1">
    17071719                  <p>The order in which header fields with differing field names are received is not significant.
     
    17381750            </div>
    17391751            <div id="whitespace">
    1740                <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a href="#whitespace">Whitespace</a></h3>
     1752               <h4 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a href="#whitespace">Whitespace</a></h4>
    17411753               <div id="rule.LWS">
    17421754                  <div id="rfc.section.3.2.3.p.1">
     
    17811793            </div>
    17821794            <div id="field.parsing">
    1783                <h3 id="rfc.section.3.2.4"><a href="#rfc.section.3.2.4">3.2.4</a>&nbsp;<a href="#field.parsing">Field Parsing</a></h3>
     1795               <h4 id="rfc.section.3.2.4"><a href="#rfc.section.3.2.4">3.2.4</a>&nbsp;<a href="#field.parsing">Field Parsing</a></h4>
    17841796               <div id="rfc.section.3.2.4.p.1">
    17851797                  <p>Messages are parsed using a generic algorithm, independent of the individual header
     
    18381850            </div>
    18391851            <div id="field.limits">
    1840                <h3 id="rfc.section.3.2.5"><a href="#rfc.section.3.2.5">3.2.5</a>&nbsp;<a href="#field.limits">Field Limits</a></h3>
     1852               <h4 id="rfc.section.3.2.5"><a href="#rfc.section.3.2.5">3.2.5</a>&nbsp;<a href="#field.limits">Field Limits</a></h4>
    18411853               <div id="rfc.section.3.2.5.p.1">
    18421854                  <p>HTTP does not place a predefined limit on the length of each header field or on the
     
    18591871            </div>
    18601872            <div id="field.components">
    1861                <h3 id="rfc.section.3.2.6"><a href="#rfc.section.3.2.6">3.2.6</a>&nbsp;<a href="#field.components">Field Value Components</a></h3>
     1873               <h4 id="rfc.section.3.2.6"><a href="#rfc.section.3.2.6">3.2.6</a>&nbsp;<a href="#field.components">Field Value Components</a></h4>
    18621874               <div id="rule.token.separators">
    18631875                  <div id="rfc.section.3.2.6.p.1">
     
    19131925         </div>
    19141926         <div id="message.body">
    1915             <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#message.body">Message Body</a></h2>
     1927            <h3 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#message.body">Message Body</a></h3>
    19161928            <div id="rfc.section.3.3.p.1">
    19171929               <p>The message body (if any) of an HTTP message is used to carry the payload body of
     
    19401952            </div>
    19411953            <div id="header.transfer-encoding">
    1942                <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;<a href="#header.transfer-encoding">Transfer-Encoding</a></h3>
     1954               <h4 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;<a href="#header.transfer-encoding">Transfer-Encoding</a></h4>
    19431955               <div id="rfc.section.3.3.1.p.1">
    19441956                  <p>The Transfer-Encoding header field lists the transfer coding names corresponding to
     
    20092021            </div>
    20102022            <div id="header.content-length">
    2011                <h3 id="rfc.section.3.3.2"><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;<a href="#header.content-length">Content-Length</a></h3>
     2023               <h4 id="rfc.section.3.3.2"><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;<a href="#header.content-length">Content-Length</a></h4>
    20122024               <div id="rfc.section.3.3.2.p.1">
    20132025                  <p>When a message does not have a <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> header field, a Content-Length header field can provide the anticipated size, as a
     
    20862098            </div>
    20872099            <div id="message.body.length">
    2088                <h3 id="rfc.section.3.3.3"><a href="#rfc.section.3.3.3">3.3.3</a>&nbsp;<a href="#message.body.length">Message Body Length</a></h3>
    2089                <div id="rfc.section.3.3.3.p.1">
     2100               <h4 id="rfc.section.3.3.3"><a href="#rfc.section.3.3.3">3.3.3</a>&nbsp;<a href="#message.body.length">Message Body Length</a></h4>
     2101               <div id="rfc.section.3.3.3.p.1" class="avoidbreakafter">
    20902102                  <p>The length of a message body is determined by one of the following (in order of precedence):</p>
    20912103               </div>
     
    21782190         </div>
    21792191         <div id="incomplete.messages">
    2180             <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#incomplete.messages">Handling Incomplete Messages</a></h2>
     2192            <h3 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#incomplete.messages">Handling Incomplete Messages</a></h3>
    21812193            <div id="rfc.section.3.4.p.1">
    21822194               <p>A server that receives an incomplete request message, usually due to a canceled request
     
    22092221         </div>
    22102222         <div id="message.robustness">
    2211             <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#message.robustness">Message Parsing Robustness</a></h2>
     2223            <h3 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#message.robustness">Message Parsing Robustness</a></h3>
    22122224            <div id="rfc.section.3.5.p.1">
    22132225               <p>Older HTTP/1.0 user agent implementations might send an extra CRLF after a POST request
     
    22462258      </div>
    22472259      <div id="transfer.codings">
    2248          <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#transfer.codings">Transfer Codings</a></h1>
     2260         <h2 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#transfer.codings">Transfer Codings</a></h2>
    22492261         <div id="rfc.section.4.p.1">
    22502262            <p>Transfer coding names are used to indicate an encoding transformation that has been,
     
    22752287         </div>
    22762288         <div id="chunked.encoding">
    2277             <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#chunked.encoding">Chunked Transfer Coding</a></h2>
     2289            <h3 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#chunked.encoding">Chunked Transfer Coding</a></h3>
    22782290            <div id="rfc.section.4.1.p.1">
    22792291               <p>The chunked transfer coding wraps the payload body in order to transfer it as a series
     
    23082320            </div>
    23092321            <div id="chunked.extension">
    2310                <h3 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;<a href="#chunked.extension">Chunk Extensions</a></h3>
     2322               <h4 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;<a href="#chunked.extension">Chunk Extensions</a></h4>
    23112323               <div id="rfc.section.4.1.1.p.1">
    23122324                  <p>The chunked encoding allows each chunk to include zero or more chunk extensions, immediately
     
    23382350            </div>
    23392351            <div id="chunked.trailer.part">
    2340                <h3 id="rfc.section.4.1.2"><a href="#rfc.section.4.1.2">4.1.2</a>&nbsp;<a href="#chunked.trailer.part">Chunked Trailer Part</a></h3>
     2352               <h4 id="rfc.section.4.1.2"><a href="#rfc.section.4.1.2">4.1.2</a>&nbsp;<a href="#chunked.trailer.part">Chunked Trailer Part</a></h4>
    23412353               <div id="rfc.section.4.1.2.p.1">
    23422354                  <p>A trailer allows the sender to include additional fields at the end of a chunked message
     
    23702382            </div>
    23712383            <div id="decoding.chunked">
    2372                <h3 id="rfc.section.4.1.3"><a href="#rfc.section.4.1.3">4.1.3</a>&nbsp;<a href="#decoding.chunked">Decoding Chunked</a></h3>
    2373                <div id="rfc.section.4.1.3.p.1">
     2384               <h4 id="rfc.section.4.1.3"><a href="#rfc.section.4.1.3">4.1.3</a>&nbsp;<a href="#decoding.chunked">Decoding Chunked</a></h4>
     2385               <div id="rfc.section.4.1.3.p.1" class="avoidbreakafter">
    23742386                  <p>A process for decoding the chunked transfer coding can be represented in pseudo-code
    23752387                     as:
     
    23982410         </div>
    23992411         <div id="compression.codings">
    2400             <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#compression.codings">Compression Codings</a></h2>
     2412            <h3 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#compression.codings">Compression Codings</a></h3>
    24012413            <div id="rfc.section.4.2.p.1">
    24022414               <p>The codings defined below can be used to compress the payload of a message.</p>
    24032415            </div>
    24042416            <div id="compress.coding">
    2405                <h3 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a href="#compress.coding">Compress Coding</a></h3>
     2417               <h4 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a href="#compress.coding">Compress Coding</a></h4>
    24062418               <div id="rfc.section.4.2.1.p.1">
    24072419                  <p>The "compress" coding is an adaptive Lempel-Ziv-Welch (LZW) coding <a href="#Welch" id="rfc.xref.Welch.1"><cite title="A Technique for High-Performance Data Compression">[Welch]</cite></a> that is commonly produced by the UNIX file compression program "compress". A recipient <em class="bcp14">SHOULD</em> consider "x-compress" to be equivalent to "compress".
     
    24102422            </div>
    24112423            <div id="deflate.coding">
    2412                <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a href="#deflate.coding">Deflate Coding</a></h3>
     2424               <h4 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a href="#deflate.coding">Deflate Coding</a></h4>
    24132425               <div id="rfc.section.4.2.2.p.1">
    24142426                  <p>The "deflate" coding is a "zlib" data format <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> containing a "deflate" compressed data stream <a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a> that uses a combination of the Lempel-Ziv (LZ77) compression algorithm and Huffman
     
    24252437            </div>
    24262438            <div id="gzip.coding">
    2427                <h3 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a href="#gzip.coding">Gzip Coding</a></h3>
     2439               <h4 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a href="#gzip.coding">Gzip Coding</a></h4>
    24282440               <div id="rfc.section.4.2.3.p.1">
    24292441                  <p>The "gzip" coding is an LZ77 coding with a 32-bit Cyclic Redundancy Check (CRC) that
     
    24342446         </div>
    24352447         <div id="header.te">
    2436             <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#header.te">TE</a></h2>
     2448            <h3 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#header.te">TE</a></h3>
    24372449            <div id="rfc.section.4.3.p.1">
    24382450               <p>The "TE" header field in a request indicates what transfer codings, besides chunked,
     
    24882500         </div>
    24892501         <div id="header.trailer">
    2490             <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#header.trailer">Trailer</a></h2>
     2502            <h3 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#header.trailer">Trailer</a></h3>
    24912503            <div id="rfc.section.4.4.p.1">
    24922504               <p>When a message includes a message body encoded with the chunked transfer coding and
     
    25032515      </div>
    25042516      <div id="message.routing">
    2505          <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#message.routing">Message Routing</a></h1>
     2517         <h2 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#message.routing">Message Routing</a></h2>
    25062518         <div id="rfc.section.5.p.1">
    25072519            <p>HTTP request message routing is determined by each client based on the target resource,
     
    25112523         </div>
    25122524         <div id="target-resource">
    2513             <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#target-resource">Identifying a Target Resource</a></h2>
     2525            <h3 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#target-resource">Identifying a Target Resource</a></h3>
    25142526            <div id="rfc.section.5.1.p.1">
    25152527               <p>HTTP is used in a wide variety of applications, ranging from general-purpose computers
     
    25272539         </div>
    25282540         <div id="connecting.inbound">
    2529             <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#connecting.inbound">Connecting Inbound</a></h2>
     2541            <h3 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#connecting.inbound">Connecting Inbound</a></h3>
    25302542            <div id="rfc.section.5.2.p.1">
    25312543               <p>Once the target URI is determined, a client needs to decide whether a network request
     
    25622574         </div>
    25632575         <div id="request-target">
    2564             <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#request-target">Request Target</a></h2>
     2576            <h3 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#request-target">Request Target</a></h3>
    25652577            <div id="rfc.section.5.3.p.1">
    25662578               <p>Once an inbound connection is obtained, the client sends an HTTP request message (<a href="#http.message" title="Message Format">Section&nbsp;3</a>) with a request-target derived from the target URI. There are four distinct formats
     
    25752587</pre></div>
    25762588            <div id="origin-form">
    2577                <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a href="#origin-form">origin-form</a></h3>
     2589               <h4 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a href="#origin-form">origin-form</a></h4>
    25782590               <div id="rfc.section.5.3.1.p.1">
    25792591                  <p>The most common form of request-target is the <dfn>origin-form</dfn>.
     
    25952607               <div id="rfc.figure.u.40"><pre class="text">http://www.example.org/where?q=now
    25962608</pre></div>
    2597                <div id="rfc.section.5.3.1.p.4">
     2609               <div id="rfc.section.5.3.1.p.4" class="avoidbreakafter">
    25982610                  <p>directly from the origin server would open (or reuse) a TCP connection to port 80
    25992611                     of the host "www.example.org" and send the lines:
     
    26082620            </div>
    26092621            <div id="absolute-form">
    2610                <h3 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a href="#absolute-form">absolute-form</a></h3>
     2622               <h4 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a href="#absolute-form">absolute-form</a></h4>
    26112623               <div id="rfc.section.5.3.2.p.1">
    26122624                  <p>When making a request to a proxy, other than a CONNECT or server-wide OPTIONS request
     
    26232635                  </p>
    26242636               </div>
    2625                <div id="rfc.section.5.3.2.p.3">
     2637               <div id="rfc.section.5.3.2.p.3" class="avoidbreakafter">
    26262638                  <p>An example absolute-form of request-line would be:</p>
    26272639               </div>
     
    26362648            </div>
    26372649            <div id="authority-form">
    2638                <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a href="#authority-form">authority-form</a></h3>
     2650               <h4 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a href="#authority-form">authority-form</a></h4>
    26392651               <div id="rfc.section.5.3.3.p.1">
    26402652                  <p>The <dfn>authority-form</dfn> of request-target is only used for CONNECT requests (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 4.3.6</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>).
     
    26532665            </div>
    26542666            <div id="asterisk-form">
    2655                <h3 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a href="#asterisk-form">asterisk-form</a></h3>
     2667               <h4 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a href="#asterisk-form">asterisk-form</a></h4>
    26562668               <div id="rfc.section.5.3.4.p.1">
    26572669                  <p>The <dfn>asterisk-form</dfn> of request-target is only used for a server-wide OPTIONS request (<a href="p2-semantics.html#OPTIONS" title="OPTIONS">Section 4.3.7</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>).
     
    26852697         </div>
    26862698         <div id="header.host">
    2687             <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.host">Host</a></h2>
     2699            <h3 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#header.host">Host</a></h3>
    26882700            <div id="rfc.section.5.4.p.1">
    26892701               <p>The "Host" header field in a request provides the host and port information from the
     
    27052717               </p>
    27062718            </div>
    2707             <div id="rfc.section.5.4.p.4">
     2719            <div id="rfc.section.5.4.p.4" class="avoidbreakafter">
    27082720               <p>For example, a GET request to the origin server for &lt;http://www.example.org/pub/WWW/&gt;
    27092721                  would begin with:
     
    27422754         </div>
    27432755         <div id="effective.request.uri">
    2744             <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a href="#effective.request.uri">Effective Request URI</a></h2>
     2756            <h3 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a href="#effective.request.uri">Effective Request URI</a></h3>
    27452757            <div id="rfc.section.5.5.p.1">
    27462758               <p>Since the request-target often contains only part of the user agent's target URI,
     
    28092821         </div>
    28102822         <div id="associating.response.to.request">
    2811             <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a>&nbsp;<a href="#associating.response.to.request">Associating a Response to a Request</a></h2>
     2823            <h3 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a>&nbsp;<a href="#associating.response.to.request">Associating a Response to a Request</a></h3>
    28122824            <div id="rfc.section.5.6.p.1">
    28132825               <p>HTTP does not include a request identifier for associating a given request message
     
    28252837         </div>
    28262838         <div id="message.forwarding">
    2827             <h2 id="rfc.section.5.7"><a href="#rfc.section.5.7">5.7</a>&nbsp;<a href="#message.forwarding">Message Forwarding</a></h2>
     2839            <h3 id="rfc.section.5.7"><a href="#rfc.section.5.7">5.7</a>&nbsp;<a href="#message.forwarding">Message Forwarding</a></h3>
    28282840            <div id="rfc.section.5.7.p.1">
    28292841               <p>As described in <a href="#intermediaries" title="Intermediaries">Section&nbsp;2.3</a>, intermediaries can serve a variety of roles in the processing of HTTP requests and
     
    28462858            </div>
    28472859            <div id="header.via">
    2848                <h3 id="rfc.section.5.7.1"><a href="#rfc.section.5.7.1">5.7.1</a>&nbsp;<a href="#header.via">Via</a></h3>
     2860               <h4 id="rfc.section.5.7.1"><a href="#rfc.section.5.7.1">5.7.1</a>&nbsp;<a href="#header.via">Via</a></h4>
    28492861               <div id="rfc.section.5.7.1.p.1">
    28502862                  <p>The "Via" header field indicates the presence of intermediate protocols and recipients
     
    28932905                  </p>
    28942906               </div>
    2895                <div id="rfc.section.5.7.1.p.7">
     2907               <div id="rfc.section.5.7.1.p.7" class="avoidbreakafter">
    28962908                  <p>For example, a request message could be sent from an HTTP/1.0 user agent to an internal
    28972909                     proxy code-named "fred", which uses HTTP/1.1 to forward the request to a public proxy
     
    29282940            </div>
    29292941            <div id="message.transformations">
    2930                <h3 id="rfc.section.5.7.2"><a href="#rfc.section.5.7.2">5.7.2</a>&nbsp;<a href="#message.transformations">Transformations</a></h3>
     2942               <h4 id="rfc.section.5.7.2"><a href="#rfc.section.5.7.2">5.7.2</a>&nbsp;<a href="#message.transformations">Transformations</a></h4>
    29312943               <div id="rfc.section.5.7.2.p.1">
    29322944                  <p>Some intermediaries include features for transforming messages and their payloads.
     
    29872999      </div>
    29883000      <div id="connection.management">
    2989          <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#connection.management">Connection Management</a></h1>
     3001         <h2 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#connection.management">Connection Management</a></h2>
    29903002         <div id="rfc.section.6.p.1">
    29913003            <p>HTTP messaging is independent of the underlying transport- or session-layer connection
     
    30143026         </div>
    30153027         <div id="header.connection">
    3016             <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#header.connection">Connection</a></h2>
     3028            <h3 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#header.connection">Connection</a></h3>
    30173029            <div id="rfc.section.6.1.p.1">
    30183030               <p>The "Connection" header field allows the sender to indicate desired control options
     
    30383050               </p>
    30393051            </div>
    3040             <div id="rfc.section.6.1.p.4">
     3052            <div id="rfc.section.6.1.p.4" class="avoidbreakafter">
    30413053               <p>The Connection header field's value has the following grammar:</p>
    30423054            </div>
     
    30923104         </div>
    30933105         <div id="persistent.establishment">
    3094             <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#persistent.establishment">Establishment</a></h2>
     3106            <h3 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#persistent.establishment">Establishment</a></h3>
    30953107            <div id="rfc.section.6.2.p.1">
    30963108               <p>It is beyond the scope of this specification to describe how connections are established
     
    31013113         </div>
    31023114         <div id="persistent.connections">
    3103             <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a href="#persistent.connections">Persistence</a></h2>
     3115            <h3 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a href="#persistent.connections">Persistence</a></h3>
    31043116            <div id="rfc.section.6.3.p.1">
    31053117               <p>HTTP/1.1 defaults to the use of "<dfn>persistent connections</dfn>", allowing multiple requests and responses to be carried over a single connection.
     
    31503162            </div>
    31513163            <div id="persistent.retrying.requests">
    3152                <h3 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;<a href="#persistent.retrying.requests">Retrying Requests</a></h3>
     3164               <h4 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;<a href="#persistent.retrying.requests">Retrying Requests</a></h4>
    31533165               <div id="rfc.section.6.3.1.p.1">
    31543166                  <p>Connections can be closed at any time, with or without intention. Implementations
     
    31793191            </div>
    31803192            <div id="pipelining">
    3181                <h3 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;<a href="#pipelining">Pipelining</a></h3>
     3193               <h4 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;<a href="#pipelining">Pipelining</a></h4>
    31823194               <div id="rfc.section.6.3.2.p.1">
    31833195                  <p>A client that supports persistent connections <em class="bcp14">MAY</em> "<dfn>pipeline</dfn>" its requests (i.e., send multiple requests without waiting for each response). A
     
    32133225         </div>
    32143226         <div id="persistent.concurrency">
    3215             <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a href="#persistent.concurrency">Concurrency</a></h2>
     3227            <h3 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a href="#persistent.concurrency">Concurrency</a></h3>
    32163228            <div id="rfc.section.6.4.p.1">
    32173229               <p>A client ought to limit the number of simultaneous open connections that it maintains
     
    32423254         </div>
    32433255         <div id="persistent.failures">
    3244             <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a href="#persistent.failures">Failures and Timeouts</a></h2>
     3256            <h3 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a href="#persistent.failures">Failures and Timeouts</a></h3>
    32453257            <div id="rfc.section.6.5.p.1">
    32463258               <p>Servers will usually have some timeout value beyond which they will no longer maintain
     
    32793291         </div>
    32803292         <div id="persistent.tear-down">
    3281             <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a href="#persistent.tear-down">Tear-down</a></h2>
     3293            <h3 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a href="#persistent.tear-down">Tear-down</a></h3>
    32823294            <div id="rfc.section.6.6.p.1">
    32833295               <p>The <a href="#header.connection" class="smpl">Connection</a> header field (<a href="#header.connection" id="rfc.xref.header.connection.4" title="Connection">Section&nbsp;6.1</a>) provides a "<a href="#header.connection" class="smpl">close</a>" connection option that a sender <em class="bcp14">SHOULD</em> send when it wishes to close the connection after the current request/response pair.
     
    33313343         </div>
    33323344         <div id="header.upgrade">
    3333             <h2 id="rfc.section.6.7"><a href="#rfc.section.6.7">6.7</a>&nbsp;<a href="#header.upgrade">Upgrade</a></h2>
     3345            <h3 id="rfc.section.6.7"><a href="#rfc.section.6.7">6.7</a>&nbsp;<a href="#header.upgrade">Upgrade</a></h3>
    33343346            <div id="rfc.section.6.7.p.1">
    33353347               <p>The "Upgrade" header field is intended to provide a simple mechanism for transitioning
     
    34263438      </div>
    34273439      <div id="abnf.extension">
    3428          <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#abnf.extension">ABNF List Extension: #rule</a></h1>
     3440         <h2 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#abnf.extension">ABNF List Extension: #rule</a></h2>
    34293441         <div id="rfc.section.7.p.1">
    34303442            <p>A #rule extension to the ABNF rules of <a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> is used to improve readability in the definitions of some header field values.
     
    34473459            <p>and for n &gt;= 1 and m &gt; 1:</p><pre class="text">  &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
    34483460</pre></div>
    3449          <div id="rfc.section.7.p.3">
     3461         <div id="rfc.section.7.p.3" class="avoidbreakafter">
    34503462            <p>For compatibility with legacy list rules, a recipient <em class="bcp14">MUST</em> parse and ignore a reasonable number of empty list elements: enough to handle common
    34513463               mistakes by senders that merge values, but not so much that they could be used as
     
    34573469  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
    34583470</pre></div>
    3459          <div id="rfc.section.7.p.4">
     3471         <div id="rfc.section.7.p.4" class="avoidbreakafter">
    34603472            <p>Empty elements do not contribute to the count of elements present. For example, given
    34613473               these ABNF productions:
     
    34653477  example-list-elmt = token ; see <a href="#field.components" title="Field Value Components">Section&nbsp;3.2.6</a>
    34663478</pre></div>
    3467          <div id="rfc.section.7.p.5">
     3479         <div id="rfc.section.7.p.5" class="avoidbreakafter">
    34683480            <p>Then the following are valid values for example-list (not including the double quotes,
    34693481               which are present for delimitation only):
     
    34743486  "foo , ,bar,charlie   "
    34753487</pre></div>
    3476          <div id="rfc.section.7.p.6">
     3488         <div id="rfc.section.7.p.6" class="avoidbreakafter">
    34773489            <p>In contrast, the following values would be invalid, since at least one non-empty element
    34783490               is required by the example-list production:
     
    34893501      </div>
    34903502      <div id="IANA.considerations">
    3491          <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     3503         <h2 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h2>
    34923504         <div id="header.field.registration">
    3493             <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
     3505            <h3 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h3>
    34943506            <div id="rfc.section.8.1.p.1">
    34953507               <p>HTTP header fields are registered within the "Message Headers" registry maintained
     
    35043516            <div id="rfc.table.1">
    35053517               <div id="iana.header.registration.table"></div>
    3506                <table class="tt full left" cellpadding="3" cellspacing="0">
     3518               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    35073519                  <thead>
    35083520                     <tr>
     
    35803592            </div>
    35813593            <div id="rfc.table.u.1">
    3582                <table class="tt full left" cellpadding="3" cellspacing="0">
     3594               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    35833595                  <thead>
    35843596                     <tr>
     
    36053617         </div>
    36063618         <div id="uri.scheme.registration">
    3607             <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a href="#uri.scheme.registration">URI Scheme Registration</a></h2>
     3619            <h3 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a href="#uri.scheme.registration">URI Scheme Registration</a></h3>
    36083620            <div id="rfc.section.8.2.p.1">
    36093621               <p>IANA maintains the registry of URI Schemes <a href="#BCP115" id="rfc.xref.BCP115.1"><cite title="Guidelines and Registration Procedures for New URI Schemes">[BCP115]</cite></a> at &lt;<a href="http://www.iana.org/assignments/uri-schemes/">http://www.iana.org/assignments/uri-schemes/</a>&gt;.
     
    36163628            </div>
    36173629            <div id="rfc.table.u.2">
    3618                <table class="tt full left" cellpadding="3" cellspacing="0">
     3630               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    36193631                  <thead>
    36203632                     <tr>
     
    36403652         </div>
    36413653         <div id="internet.media.type.http">
    3642             <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a href="#internet.media.type.http">Internet Media Type Registration</a></h2>
     3654            <h3 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a href="#internet.media.type.http">Internet Media Type Registration</a></h3>
    36433655            <div id="rfc.section.8.3.p.1">
    36443656               <p>IANA maintains the registry of Internet media types <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a> at &lt;<a href="http://www.iana.org/assignments/media-types">http://www.iana.org/assignments/media-types</a>&gt;.
     
    36513663            </div>
    36523664            <div id="internet.media.type.message.http">
    3653                <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a href="#internet.media.type.message.http">Internet Media Type message/http</a></h3>
     3665               <h4 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a href="#internet.media.type.message.http">Internet Media Type message/http</a></h4>
    36543666               <div id="rfc.section.8.3.1.p.1">
    36553667                  <p>The message/http type can be used to enclose a single HTTP request or response message,
     
    37203732            </div>
    37213733            <div id="internet.media.type.application.http">
    3722                <h3 id="rfc.section.8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;<a href="#internet.media.type.application.http">Internet Media Type application/http</a></h3>
     3734               <h4 id="rfc.section.8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;<a href="#internet.media.type.application.http">Internet Media Type application/http</a></h4>
    37233735               <div id="rfc.section.8.3.2.p.1">
    37243736                  <p>The application/http type can be used to enclose a pipeline of one or more HTTP request
     
    37913803         </div>
    37923804         <div id="transfer.coding.registry">
    3793             <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a href="#transfer.coding.registry">Transfer Coding Registry</a></h2>
     3805            <h3 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a href="#transfer.coding.registry">Transfer Coding Registry</a></h3>
    37943806            <div id="rfc.section.8.4.p.1">
    37953807               <p>The "HTTP Transfer Coding Registry" defines the namespace for transfer coding names.
     
    37983810            </div>
    37993811            <div id="transfer.coding.registry.procedure">
    3800                <h3 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a href="#transfer.coding.registry.procedure">Procedure</a></h3>
     3812               <h4 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a href="#transfer.coding.registry.procedure">Procedure</a></h4>
    38013813               <div id="rfc.section.8.4.1.p.1">
    38023814                  <p>Registrations <em class="bcp14">MUST</em> include the following fields:
     
    38243836            </div>
    38253837            <div id="transfer.coding.registration">
    3826                <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a href="#transfer.coding.registration">Registration</a></h3>
    3827                <div id="rfc.section.8.4.2.p.1">
     3838               <h4 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a href="#transfer.coding.registration">Registration</a></h4>
     3839               <div id="rfc.section.8.4.2.p.1" class="avoidbreakafter">
    38283840                  <p>The "HTTP Transfer Coding Registry" has been updated with the registrations below:</p>
    38293841               </div>
    38303842               <div id="rfc.table.2">
    38313843                  <div id="iana.transfer.coding.registration.table"></div>
    3832                   <table class="tt full left" cellpadding="3" cellspacing="0">
     3844                  <table class="tt full tleft" cellpadding="3" cellspacing="0">
    38333845                     <thead>
    38343846                        <tr>
     
    38823894         </div>
    38833895         <div id="content.coding.registration">
    3884             <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a href="#content.coding.registration">Content Coding Registration</a></h2>
     3896            <h3 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a href="#content.coding.registration">Content Coding Registration</a></h3>
    38853897            <div id="rfc.section.8.5.p.1">
    38863898               <p>IANA maintains the "HTTP Content Coding Registry" at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    38873899               </p>
    38883900            </div>
    3889             <div id="rfc.section.8.5.p.2">
     3901            <div id="rfc.section.8.5.p.2" class="avoidbreakafter">
    38903902               <p>The "HTTP Content Coding Registry" has been updated with the registrations below:</p>
    38913903            </div>
    38923904            <div id="rfc.table.3">
    38933905               <div id="iana.content.coding.registration.table"></div>
    3894                <table class="tt full left" cellpadding="3" cellspacing="0">
     3906               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    38953907                  <thead>
    38963908                     <tr>
     
    39373949         </div>
    39383950         <div id="upgrade.token.registry">
    3939             <h2 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a>&nbsp;<a href="#upgrade.token.registry">Upgrade Token Registry</a></h2>
     3951            <h3 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a>&nbsp;<a href="#upgrade.token.registry">Upgrade Token Registry</a></h3>
    39403952            <div id="rfc.section.8.6.p.1">
    39413953               <p>The "Hypertext Transfer Protocol (HTTP) Upgrade Token Registry" defines the namespace
     
    39443956            </div>
    39453957            <div id="upgrade.token.registry.procedure">
    3946                <h3 id="rfc.section.8.6.1"><a href="#rfc.section.8.6.1">8.6.1</a>&nbsp;<a href="#upgrade.token.registry.procedure">Procedure</a></h3>
     3958               <h4 id="rfc.section.8.6.1"><a href="#rfc.section.8.6.1">8.6.1</a>&nbsp;<a href="#upgrade.token.registry.procedure">Procedure</a></h4>
    39473959               <div id="rfc.section.8.6.1.p.1">
    39483960                  <p>Each registered protocol name is associated with contact information and an optional
     
    39813993            </div>
    39823994            <div id="upgrade.token.registration">
    3983                <h3 id="rfc.section.8.6.2"><a href="#rfc.section.8.6.2">8.6.2</a>&nbsp;<a href="#upgrade.token.registration">Upgrade Token Registration</a></h3>
    3984                <div id="rfc.section.8.6.2.p.1">
     3995               <h4 id="rfc.section.8.6.2"><a href="#rfc.section.8.6.2">8.6.2</a>&nbsp;<a href="#upgrade.token.registration">Upgrade Token Registration</a></h4>
     3996               <div id="rfc.section.8.6.2.p.1" class="avoidbreakafter">
    39853997                  <p>The "HTTP" entry in the upgrade token registry has been updated with the registration
    39863998                     below:
     
    39884000               </div>
    39894001               <div id="rfc.table.u.3">
    3990                   <table class="tt full left" cellpadding="3" cellspacing="0">
     4002                  <table class="tt full tleft" cellpadding="3" cellspacing="0">
    39914003                     <thead>
    39924004                        <tr>
     
    40144026      </div>
    40154027      <div id="security.considerations">
    4016          <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     4028         <h2 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h2>
    40174029         <div id="rfc.section.9.p.1">
    40184030            <p>This section is meant to inform developers, information providers, and users of known
     
    40224034         </div>
    40234035         <div id="establishing.authority">
    4024             <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a href="#establishing.authority">Establishing Authority</a></h2>
     4036            <h3 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a href="#establishing.authority">Establishing Authority</a></h3>
    40254037            <div id="rfc.section.9.1.p.1">
    40264038               <p>HTTP relies on the notion of an <dfn>authoritative response</dfn>: a response that has been determined by (or at the direction of) the authority identified
     
    40644076         </div>
    40654077         <div id="risks.intermediaries">
    4066             <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a href="#risks.intermediaries">Risks of Intermediaries</a></h2>
     4078            <h3 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a href="#risks.intermediaries">Risks of Intermediaries</a></h3>
    40674079            <div id="rfc.section.9.2.p.1">
    40684080               <p>By their very nature, HTTP intermediaries are men-in-the-middle and, thus, represent
     
    40944106         </div>
    40954107         <div id="attack.protocol.element.length">
    4096             <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a href="#attack.protocol.element.length">Attacks via Protocol Element Length</a></h2>
     4108            <h3 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a href="#attack.protocol.element.length">Attacks via Protocol Element Length</a></h3>
    40974109            <div id="rfc.section.9.3.p.1">
    40984110               <p>Because HTTP uses mostly textual, character-delimited fields, parsers are often vulnerable
     
    41234135         </div>
    41244136         <div id="response.splitting">
    4125             <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a href="#response.splitting">Response Splitting</a></h2>
     4137            <h3 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a href="#response.splitting">Response Splitting</a></h3>
    41264138            <div id="rfc.section.9.4.p.1">
    41274139               <p>Response splitting (a.k.a, CRLF injection) is a common technique, used in various
     
    41654177         </div>
    41664178         <div id="request.smuggling">
    4167             <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a href="#request.smuggling">Request Smuggling</a></h2>
     4179            <h3 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a href="#request.smuggling">Request Smuggling</a></h3>
    41684180            <div id="rfc.section.9.5.p.1">
    41694181               <p>Request smuggling (<a href="#Linhart" id="rfc.xref.Linhart.1"><cite title="HTTP Request Smuggling">[Linhart]</cite></a>) is a technique that exploits differences in protocol parsing among various recipients
     
    41804192         </div>
    41814193         <div id="message.integrity">
    4182             <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a href="#message.integrity">Message Integrity</a></h2>
     4194            <h3 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a href="#message.integrity">Message Integrity</a></h3>
    41834195            <div id="rfc.section.9.6.p.1">
    41844196               <p>HTTP does not define a specific mechanism for ensuring message integrity, instead
     
    42074219         </div>
    42084220         <div id="message.confidentiality">
    4209             <h2 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a href="#message.confidentiality">Message Confidentiality</a></h2>
     4221            <h3 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a href="#message.confidentiality">Message Confidentiality</a></h3>
    42104222            <div id="rfc.section.9.7.p.1">
    42114223               <p>HTTP relies on underlying transport protocols to provide message confidentiality when
     
    42234235         </div>
    42244236         <div id="privacy.of.server.log.information">
    4225             <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a>&nbsp;<a href="#privacy.of.server.log.information">Privacy of Server Log Information</a></h2>
     4237            <h3 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a>&nbsp;<a href="#privacy.of.server.log.information">Privacy of Server Log Information</a></h3>
    42264238            <div id="rfc.section.9.8.p.1">
    42274239               <p>A server is in the position to save personal data about a user's requests over time,
     
    42514263      </div>
    42524264      <div id="acks">
    4253          <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
     4265         <h2 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a href="#acks">Acknowledgments</a></h2>
    42544266         <div id="rfc.section.10.p.1">
    42554267            <p>This edition of HTTP/1.1 builds on the many contributions that went into <a href="#RFC1945" id="rfc.xref.RFC1945.2">RFC 1945</a>, <a href="#RFC2068" id="rfc.xref.RFC2068.3">RFC 2068</a>, <a href="#RFC2145" id="rfc.xref.RFC2145.2">RFC 2145</a>, and <a href="#RFC2616" id="rfc.xref.RFC2616.3">RFC 2616</a>, including substantial contributions made by the previous authors, editors, and Working
     
    42594271            </p>
    42604272         </div>
    4261          <div id="rfc.section.10.p.2">
     4273         <div id="rfc.section.10.p.2" class="avoidbreakafter">
    42624274            <p>Since 1999, the following contributors have helped improve the HTTP specification
    42634275               by reporting bugs, asking smart questions, drafting or reviewing text, and evaluating
     
    43284340         </div>
    43294341      </div>
    4330       <h1 id="rfc.references"><a id="rfc.section.11" href="#rfc.section.11">11.</a> References
    4331       </h1>
    4332       <h2 id="rfc.references.1"><a href="#rfc.section.11.1" id="rfc.section.11.1">11.1</a> Normative References
     4342      <h2 id="rfc.references"><a id="rfc.section.11" href="#rfc.section.11">11.</a> References
    43334343      </h2>
    4334       <table>
    4335          <tr>
    4336             <td class="reference"><b id="RFC0793">[RFC0793]</b></td>
    4337             <td class="top">Postel, J., “<a href="https://tools.ietf.org/html/rfc793">Transmission Control Protocol</a>”, STD&nbsp;7, RFC&nbsp;793, September&nbsp;1981.
    4338             </td>
    4339          </tr>
    4340          <tr>
    4341             <td class="reference"><b id="RFC1950">[RFC1950]</b></td>
    4342             <td class="top">Deutsch, L. and J-L. Gailly, “<a href="https://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.
    4343             </td>
    4344          </tr>
    4345          <tr>
    4346             <td class="reference"><b id="RFC1951">[RFC1951]</b></td>
    4347             <td class="top">Deutsch, P., “<a href="https://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996.
    4348             </td>
    4349          </tr>
    4350          <tr>
    4351             <td class="reference"><b id="RFC1952">[RFC1952]</b></td>
    4352             <td class="top">Deutsch, P., Gailly, J-L., Adler, M., Deutsch, L., and G. Randers-Pehrson, “<a href="https://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996.
    4353             </td>
    4354          </tr>
    4355          <tr>
    4356             <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    4357             <td class="top">Bradner, S., “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
    4358             </td>
    4359          </tr>
    4360          <tr>
    4361             <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
    4362             <td class="top">Berners-Lee, T., Fielding, R., and L. Masinter, “<a href="https://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
    4363             </td>
    4364          </tr>
    4365          <tr>
    4366             <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    4367             <td class="top">Crocker, D., Ed. and P. Overell, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
    4368             </td>
    4369          </tr>
    4370          <tr>
    4371             <td class="reference"><b id="RFC7231">[RFC7231]</b></td>
    4372             <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2014.
    4373             </td>
    4374          </tr>
    4375          <tr>
    4376             <td class="reference"><b id="RFC7232">[RFC7232]</b></td>
    4377             <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2014.
    4378             </td>
    4379          </tr>
    4380          <tr>
    4381             <td class="reference"><b id="RFC7233">[RFC7233]</b></td>
    4382             <td class="top">Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2014.
    4383             </td>
    4384          </tr>
    4385          <tr>
    4386             <td class="reference"><b id="RFC7234">[RFC7234]</b></td>
    4387             <td class="top">Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2014.
    4388             </td>
    4389          </tr>
    4390          <tr>
    4391             <td class="reference"><b id="RFC7235">[RFC7235]</b></td>
    4392             <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), June&nbsp;2014.
    4393             </td>
    4394          </tr>
    4395          <tr>
    4396             <td class="reference"><b id="USASCII">[USASCII]</b></td>
    4397             <td class="top">American National Standards Institute, “Coded Character Set -- 7-bit American Standard Code for Information Interchange”, ANSI&nbsp;X3.4, 1986.</td>
    4398          </tr>
    4399          <tr>
    4400             <td class="reference"><b id="Welch">[Welch]</b></td>
    4401             <td class="top">Welch, T., “A Technique for High-Performance Data Compression”, IEEE Computer&nbsp;17(6), June&nbsp;1984.</td>
    4402          </tr>
    4403       </table>
    4404       <h2 id="rfc.references.2"><a href="#rfc.section.11.2" id="rfc.section.11.2">11.2</a> Informative References
    4405       </h2>
    4406       <table>
    4407          <tr>
    4408             <td class="reference"><b id="BCP115">[BCP115]</b></td>
    4409             <td class="top">Hansen, T., Hardie, T., and L. Masinter, “<a href="https://tools.ietf.org/html/rfc4395">Guidelines and Registration Procedures for New URI Schemes</a>”, BCP&nbsp;115, RFC&nbsp;4395, February&nbsp;2006.
    4410             </td>
    4411          </tr>
    4412          <tr>
    4413             <td class="reference"><b id="BCP13">[BCP13]</b></td>
    4414             <td class="top">Freed, N., Klensin, J., and T. Hansen, “<a href="https://tools.ietf.org/html/rfc6838">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;6838, January&nbsp;2013.
    4415             </td>
    4416          </tr>
    4417          <tr>
    4418             <td class="reference"><b id="BCP90">[BCP90]</b></td>
    4419             <td class="top">Klyne, G., Nottingham, M., and J. Mogul, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
    4420             </td>
    4421          </tr>
    4422          <tr>
    4423             <td class="reference"><b id="Georgiev">[Georgiev]</b></td>
    4424             <td class="top">Georgiev, M., Iyengar, S., Jana, S., Anubhai, R., Boneh, D., and V. Shmatikov, “<a href="http://doi.acm.org/10.1145/2382196.2382204">The Most Dangerous Code in the World: Validating SSL Certificates in Non-browser Software</a>”, In Proceedings of the 2012 ACM Conference on Computer and Communications Security
    4425                (CCS '12), pp. 38-49, October&nbsp;2012, &lt;<a href="http://doi.acm.org/10.1145/2382196.2382204">http://doi.acm.org/10.1145/2382196.2382204</a>&gt;.
    4426             </td>
    4427          </tr>
    4428          <tr>
    4429             <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
    4430             <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1:
    4431                Latin alphabet No. 1”, ISO/IEC&nbsp;8859-1:1998, 1998.
    4432             </td>
    4433          </tr>
    4434          <tr>
    4435             <td class="reference"><b id="Klein">[Klein]</b></td>
    4436             <td class="top">Klein, A., “<a href="http://packetstormsecurity.com/papers/general/whitepaper_httpresponse.pdf">Divide and Conquer - HTTP Response Splitting, Web Cache Poisoning Attacks, and Related
    4437                   Topics</a>”, March&nbsp;2004, &lt;<a href="http://packetstormsecurity.com/papers/general/whitepaper_httpresponse.pdf">http://packetstormsecurity.com/papers/general/whitepaper_httpresponse.pdf</a>&gt;.
    4438             </td>
    4439          </tr>
    4440          <tr>
    4441             <td class="reference"><b id="Kri2001">[Kri2001]</b></td>
    4442             <td class="top">Kristol, D., “<a href="http://arxiv.org/abs/cs.SE/0105018">HTTP Cookies: Standards, Privacy, and Politics</a>”, ACM Transactions on Internet Technology&nbsp;1(2), November&nbsp;2001, &lt;<a href="http://arxiv.org/abs/cs.SE/0105018">http://arxiv.org/abs/cs.SE/0105018</a>&gt;.
    4443             </td>
    4444          </tr>
    4445          <tr>
    4446             <td class="reference"><b id="Linhart">[Linhart]</b></td>
    4447             <td class="top">Linhart, C., Klein, A., Heled, R., and S. Orrin, “<a href="http://www.watchfire.com/news/whitepapers.aspx">HTTP Request Smuggling</a>”, June&nbsp;2005, &lt;<a href="http://www.watchfire.com/news/whitepapers.aspx">http://www.watchfire.com/news/whitepapers.aspx</a>&gt;.
    4448             </td>
    4449          </tr>
    4450          <tr>
    4451             <td class="reference"><b id="RFC1919">[RFC1919]</b></td>
    4452             <td class="top">Chatel, M., “<a href="https://tools.ietf.org/html/rfc1919">Classical versus Transparent IP Proxies</a>”, RFC&nbsp;1919, March&nbsp;1996.
    4453             </td>
    4454          </tr>
    4455          <tr>
    4456             <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    4457             <td class="top">Berners-Lee, T., Fielding, R., and H. Nielsen, “<a href="https://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
    4458             </td>
    4459          </tr>
    4460          <tr>
    4461             <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
    4462             <td class="top">Freed, N. and N. Borenstein, “<a href="https://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message
    4463                   Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
    4464             </td>
    4465          </tr>
    4466          <tr>
    4467             <td class="reference"><b id="RFC2047">[RFC2047]</b></td>
    4468             <td class="top">Moore, K., “<a href="https://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions
    4469                   for Non-ASCII Text</a>”, RFC&nbsp;2047, November&nbsp;1996.
    4470             </td>
    4471          </tr>
    4472          <tr>
    4473             <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
    4474             <td class="top">Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
    4475             </td>
    4476          </tr>
    4477          <tr>
    4478             <td class="reference"><b id="RFC2145">[RFC2145]</b></td>
    4479             <td class="top">Mogul, J., Fielding, R., Gettys, J., and H. Nielsen, “<a href="https://tools.ietf.org/html/rfc2145">Use and Interpretation of HTTP Version Numbers</a>”, RFC&nbsp;2145, May&nbsp;1997.
    4480             </td>
    4481          </tr>
    4482          <tr>
    4483             <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    4484             <td class="top">Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    4485             </td>
    4486          </tr>
    4487          <tr>
    4488             <td class="reference"><b id="RFC2817">[RFC2817]</b></td>
    4489             <td class="top">Khare, R. and S. Lawrence, “<a href="https://tools.ietf.org/html/rfc2817">Upgrading to TLS Within HTTP/1.1</a>”, RFC&nbsp;2817, May&nbsp;2000.
    4490             </td>
    4491          </tr>
    4492          <tr>
    4493             <td class="reference"><b id="RFC2818">[RFC2818]</b></td>
    4494             <td class="top">Rescorla, E., “<a href="https://tools.ietf.org/html/rfc2818">HTTP Over TLS</a>”, RFC&nbsp;2818, May&nbsp;2000.
    4495             </td>
    4496          </tr>
    4497          <tr>
    4498             <td class="reference"><b id="RFC3040">[RFC3040]</b></td>
    4499             <td class="top">Cooper, I., Melve, I., and G. Tomlinson, “<a href="https://tools.ietf.org/html/rfc3040">Internet Web Replication and Caching Taxonomy</a>”, RFC&nbsp;3040, January&nbsp;2001.
    4500             </td>
    4501          </tr>
    4502          <tr>
    4503             <td class="reference"><b id="RFC4033">[RFC4033]</b></td>
    4504             <td class="top">Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, “<a href="https://tools.ietf.org/html/rfc4033">DNS Security Introduction and Requirements</a>”, RFC&nbsp;4033, March&nbsp;2005.
    4505             </td>
    4506          </tr>
    4507          <tr>
    4508             <td class="reference"><b id="RFC4559">[RFC4559]</b></td>
    4509             <td class="top">Jaganathan, K., Zhu, L., and J. Brezak, “<a href="https://tools.ietf.org/html/rfc4559">SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows</a>”, RFC&nbsp;4559, June&nbsp;2006.
    4510             </td>
    4511          </tr>
    4512          <tr>
    4513             <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
    4514             <td class="top">Narten, T. and H. Alvestrand, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
    4515             </td>
    4516          </tr>
    4517          <tr>
    4518             <td class="reference"><b id="RFC5246">[RFC5246]</b></td>
    4519             <td class="top">Dierks, T. and E. Rescorla, “<a href="https://tools.ietf.org/html/rfc5246">The Transport Layer Security (TLS) Protocol Version 1.2</a>”, RFC&nbsp;5246, August&nbsp;2008.
    4520             </td>
    4521          </tr>
    4522          <tr>
    4523             <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
    4524             <td class="top">Resnick, P., “<a href="https://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
    4525             </td>
    4526          </tr>
    4527          <tr>
    4528             <td class="reference"><b id="RFC6265">[RFC6265]</b></td>
    4529             <td class="top">Barth, A., “<a href="https://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
    4530             </td>
    4531          </tr>
    4532          <tr>
    4533             <td class="reference"><b id="RFC6585">[RFC6585]</b></td>
    4534             <td class="top">Nottingham, M. and R. Fielding, “<a href="https://tools.ietf.org/html/rfc6585">Additional HTTP Status Codes</a>”, RFC&nbsp;6585, April&nbsp;2012.
    4535             </td>
    4536          </tr>
    4537       </table>
     4344      <h3 id="rfc.references.1"><a href="#rfc.section.11.1" id="rfc.section.11.1">11.1</a> Normative References
     4345      </h3>
     4346      <dl class="reference">
     4347         <dt id="RFC0793">[RFC0793]</dt>
     4348         <dd>Postel, J., “<a href="https://tools.ietf.org/html/rfc793">Transmission Control Protocol</a>”, STD&nbsp;7, RFC&nbsp;793, September&nbsp;1981.
     4349         </dd>
     4350         <dt id="RFC1950">[RFC1950]</dt>
     4351         <dd>Deutsch, L. and J-L. Gailly, “<a href="https://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC&nbsp;1950, May&nbsp;1996.
     4352         </dd>
     4353         <dt id="RFC1951">[RFC1951]</dt>
     4354         <dd>Deutsch, P., “<a href="https://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC&nbsp;1951, May&nbsp;1996.
     4355         </dd>
     4356         <dt id="RFC1952">[RFC1952]</dt>
     4357         <dd>Deutsch, P., Gailly, J-L., Adler, M., Deutsch, L., and G. Randers-Pehrson, “<a href="https://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC&nbsp;1952, May&nbsp;1996.
     4358         </dd>
     4359         <dt id="RFC2119">[RFC2119]</dt>
     4360         <dd>Bradner, S., “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
     4361         </dd>
     4362         <dt id="RFC3986">[RFC3986]</dt>
     4363         <dd>Berners-Lee, T., Fielding, R., and L. Masinter, “<a href="https://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
     4364         </dd>
     4365         <dt id="RFC5234">[RFC5234]</dt>
     4366         <dd>Crocker, D., Ed. and P. Overell, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     4367         </dd>
     4368         <dt id="RFC7231">[RFC7231]</dt>
     4369         <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2014.
     4370         </dd>
     4371         <dt id="RFC7232">[RFC7232]</dt>
     4372         <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2014.
     4373         </dd>
     4374         <dt id="RFC7233">[RFC7233]</dt>
     4375         <dd>Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2014.
     4376         </dd>
     4377         <dt id="RFC7234">[RFC7234]</dt>
     4378         <dd>Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2014.
     4379         </dd>
     4380         <dt id="RFC7235">[RFC7235]</dt>
     4381         <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), June&nbsp;2014.
     4382         </dd>
     4383         <dt id="USASCII">[USASCII]</dt>
     4384         <dd>American National Standards Institute, “Coded Character Set -- 7-bit American Standard Code for Information Interchange”, ANSI&nbsp;X3.4, 1986.</dd>
     4385         <dt id="Welch">[Welch]</dt>
     4386         <dd>Welch, T., “A Technique for High-Performance Data Compression”, IEEE Computer&nbsp;17(6), June&nbsp;1984.</dd>
     4387      </dl>
     4388      <h3 id="rfc.references.2"><a href="#rfc.section.11.2" id="rfc.section.11.2">11.2</a> Informative References
     4389      </h3>
     4390      <dl class="reference">
     4391         <dt id="BCP115">[BCP115]</dt>
     4392         <dd>Hansen, T., Hardie, T., and L. Masinter, “<a href="https://tools.ietf.org/html/rfc4395">Guidelines and Registration Procedures for New URI Schemes</a>”, BCP&nbsp;115, RFC&nbsp;4395, February&nbsp;2006.
     4393         </dd>
     4394         <dt id="BCP13">[BCP13]</dt>
     4395         <dd>Freed, N., Klensin, J., and T. Hansen, “<a href="https://tools.ietf.org/html/rfc6838">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;6838, January&nbsp;2013.
     4396         </dd>
     4397         <dt id="BCP90">[BCP90]</dt>
     4398         <dd>Klyne, G., Nottingham, M., and J. Mogul, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
     4399         </dd>
     4400         <dt id="Georgiev">[Georgiev]</dt>
     4401         <dd>Georgiev, M., Iyengar, S., Jana, S., Anubhai, R., Boneh, D., and V. Shmatikov, “<a href="http://doi.acm.org/10.1145/2382196.2382204">The Most Dangerous Code in the World: Validating SSL Certificates in Non-browser Software</a>”, In Proceedings of the 2012 ACM Conference on Computer and Communications Security
     4402            (CCS '12), pp. 38-49, October&nbsp;2012, &lt;<a href="http://doi.acm.org/10.1145/2382196.2382204">http://doi.acm.org/10.1145/2382196.2382204</a>&gt;.
     4403         </dd>
     4404         <dt id="ISO-8859-1">[ISO-8859-1]</dt>
     4405         <dd>International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1:
     4406            Latin alphabet No. 1”, ISO/IEC&nbsp;8859-1:1998, 1998.
     4407         </dd>
     4408         <dt id="Klein">[Klein]</dt>
     4409         <dd>Klein, A., “<a href="http://packetstormsecurity.com/papers/general/whitepaper_httpresponse.pdf">Divide and Conquer - HTTP Response Splitting, Web Cache Poisoning Attacks, and Related
     4410               Topics</a>”, March&nbsp;2004, &lt;<a href="http://packetstormsecurity.com/papers/general/whitepaper_httpresponse.pdf">http://packetstormsecurity.com/papers/general/whitepaper_httpresponse.pdf</a>&gt;.
     4411         </dd>
     4412         <dt id="Kri2001">[Kri2001]</dt>
     4413         <dd>Kristol, D., “<a href="http://arxiv.org/abs/cs.SE/0105018">HTTP Cookies: Standards, Privacy, and Politics</a>”, ACM Transactions on Internet Technology&nbsp;1(2), November&nbsp;2001, &lt;<a href="http://arxiv.org/abs/cs.SE/0105018">http://arxiv.org/abs/cs.SE/0105018</a>&gt;.
     4414         </dd>
     4415         <dt id="Linhart">[Linhart]</dt>
     4416         <dd>Linhart, C., Klein, A., Heled, R., and S. Orrin, “<a href="http://www.watchfire.com/news/whitepapers.aspx">HTTP Request Smuggling</a>”, June&nbsp;2005, &lt;<a href="http://www.watchfire.com/news/whitepapers.aspx">http://www.watchfire.com/news/whitepapers.aspx</a>&gt;.
     4417         </dd>
     4418         <dt id="RFC1919">[RFC1919]</dt>
     4419         <dd>Chatel, M., “<a href="https://tools.ietf.org/html/rfc1919">Classical versus Transparent IP Proxies</a>”, RFC&nbsp;1919, March&nbsp;1996.
     4420         </dd>
     4421         <dt id="RFC1945">[RFC1945]</dt>
     4422         <dd>Berners-Lee, T., Fielding, R., and H. Nielsen, “<a href="https://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
     4423         </dd>
     4424         <dt id="RFC2045">[RFC2045]</dt>
     4425         <dd>Freed, N. and N. Borenstein, “<a href="https://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message
     4426               Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
     4427         </dd>
     4428         <dt id="RFC2047">[RFC2047]</dt>
     4429         <dd>Moore, K., “<a href="https://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions
     4430               for Non-ASCII Text</a>”, RFC&nbsp;2047, November&nbsp;1996.
     4431         </dd>
     4432         <dt id="RFC2068">[RFC2068]</dt>
     4433         <dd>Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
     4434         </dd>
     4435         <dt id="RFC2145">[RFC2145]</dt>
     4436         <dd>Mogul, J., Fielding, R., Gettys, J., and H. Nielsen, “<a href="https://tools.ietf.org/html/rfc2145">Use and Interpretation of HTTP Version Numbers</a>”, RFC&nbsp;2145, May&nbsp;1997.
     4437         </dd>
     4438         <dt id="RFC2616">[RFC2616]</dt>
     4439         <dd>Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     4440         </dd>
     4441         <dt id="RFC2817">[RFC2817]</dt>
     4442         <dd>Khare, R. and S. Lawrence, “<a href="https://tools.ietf.org/html/rfc2817">Upgrading to TLS Within HTTP/1.1</a>”, RFC&nbsp;2817, May&nbsp;2000.
     4443         </dd>
     4444         <dt id="RFC2818">[RFC2818]</dt>
     4445         <dd>Rescorla, E., “<a href="https://tools.ietf.org/html/rfc2818">HTTP Over TLS</a>”, RFC&nbsp;2818, May&nbsp;2000.
     4446         </dd>
     4447         <dt id="RFC3040">[RFC3040]</dt>
     4448         <dd>Cooper, I., Melve, I., and G. Tomlinson, “<a href="https://tools.ietf.org/html/rfc3040">Internet Web Replication and Caching Taxonomy</a>”, RFC&nbsp;3040, January&nbsp;2001.
     4449         </dd>
     4450         <dt id="RFC4033">[RFC4033]</dt>
     4451         <dd>Arends, R., Austein, R., Larson, M., Massey, D., and S. Rose, “<a href="https://tools.ietf.org/html/rfc4033">DNS Security Introduction and Requirements</a>”, RFC&nbsp;4033, March&nbsp;2005.
     4452         </dd>
     4453         <dt id="RFC4559">[RFC4559]</dt>
     4454         <dd>Jaganathan, K., Zhu, L., and J. Brezak, “<a href="https://tools.ietf.org/html/rfc4559">SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows</a>”, RFC&nbsp;4559, June&nbsp;2006.
     4455         </dd>
     4456         <dt id="RFC5226">[RFC5226]</dt>
     4457         <dd>Narten, T. and H. Alvestrand, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
     4458         </dd>
     4459         <dt id="RFC5246">[RFC5246]</dt>
     4460         <dd>Dierks, T. and E. Rescorla, “<a href="https://tools.ietf.org/html/rfc5246">The Transport Layer Security (TLS) Protocol Version 1.2</a>”, RFC&nbsp;5246, August&nbsp;2008.
     4461         </dd>
     4462         <dt id="RFC5322">[RFC5322]</dt>
     4463         <dd>Resnick, P., “<a href="https://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
     4464         </dd>
     4465         <dt id="RFC6265">[RFC6265]</dt>
     4466         <dd>Barth, A., “<a href="https://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
     4467         </dd>
     4468         <dt id="RFC6585">[RFC6585]</dt>
     4469         <dd>Nottingham, M. and R. Fielding, “<a href="https://tools.ietf.org/html/rfc6585">Additional HTTP Status Codes</a>”, RFC&nbsp;6585, April&nbsp;2012.
     4470         </dd>
     4471      </dl>
    45384472      <div id="compatibility">
    4539          <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#compatibility">HTTP Version History</a></h1>
     4473         <h2 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#compatibility">HTTP Version History</a></h2>
    45404474         <div id="rfc.section.A.p.1">
    45414475            <p>HTTP has been in use since 1990. The first version, later referred to as HTTP/0.9,
     
    45734507         </div>
    45744508         <div id="changes.from.1.0">
    4575             <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#changes.from.1.0">Changes from HTTP/1.0</a></h2>
     4509            <h3 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#changes.from.1.0">Changes from HTTP/1.0</a></h3>
    45764510            <div id="rfc.section.A.1.p.1">
    45774511               <p>This section summarizes major differences between versions HTTP/1.0 and HTTP/1.1.</p>
    45784512            </div>
    45794513            <div id="changes.to.simplify.multihomed.web.servers.and.conserve.ip.addresses">
    4580                <h3 id="rfc.section.A.1.1"><a href="#rfc.section.A.1.1">A.1.1</a>&nbsp;<a href="#changes.to.simplify.multihomed.web.servers.and.conserve.ip.addresses">Multihomed Web Servers</a></h3>
     4514               <h4 id="rfc.section.A.1.1"><a href="#rfc.section.A.1.1">A.1.1</a>&nbsp;<a href="#changes.to.simplify.multihomed.web.servers.and.conserve.ip.addresses">Multihomed Web Servers</a></h4>
    45814515               <div id="rfc.section.A.1.1.p.1">
    45824516                  <p>The requirements that clients and servers support the <a href="#header.host" class="smpl">Host</a> header field (<a href="#header.host" id="rfc.xref.header.host.3" title="Host">Section&nbsp;5.4</a>), report an error if it is missing from an HTTP/1.1 request, and accept absolute
     
    45964530            </div>
    45974531            <div id="compatibility.with.http.1.0.persistent.connections">
    4598                <h3 id="rfc.section.A.1.2"><a href="#rfc.section.A.1.2">A.1.2</a>&nbsp;<a href="#compatibility.with.http.1.0.persistent.connections">Keep-Alive Connections</a></h3>
     4532               <h4 id="rfc.section.A.1.2"><a href="#rfc.section.A.1.2">A.1.2</a>&nbsp;<a href="#compatibility.with.http.1.0.persistent.connections">Keep-Alive Connections</a></h4>
    45994533               <div id="rfc.section.A.1.2.p.1">
    46004534                  <p>In HTTP/1.0, each connection is established by the client prior to the request and
     
    46344568            </div>
    46354569            <div id="introduction.of.transfer-encoding">
    4636                <h3 id="rfc.section.A.1.3"><a href="#rfc.section.A.1.3">A.1.3</a>&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h3>
     4570               <h4 id="rfc.section.A.1.3"><a href="#rfc.section.A.1.3">A.1.3</a>&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h4>
    46374571               <div id="rfc.section.A.1.3.p.1">
    46384572                  <p>HTTP/1.1 introduces the <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.4" title="Transfer-Encoding">Section&nbsp;3.3.1</a>). Transfer codings need to be decoded prior to forwarding an HTTP message over a
     
    46434577         </div>
    46444578         <div id="changes.from.rfc.2616">
    4645             <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     4579            <h3 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h3>
    46464580            <div id="rfc.section.A.2.p.1">
    46474581               <p>HTTP's approach to error handling has been explained. (<a href="#conformance" title="Conformance and Error Handling">Section&nbsp;2.5</a>)
     
    47774711      </div>
    47784712      <div id="collected.abnf">
    4779          <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     4713         <h2 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h2>
    47804714         <div id="rfc.figure.u.72"><pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS
    47814715
     
    48924826</pre></div>
    48934827      </div>
    4894       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
     4828      <h2 id="rfc.index"><a href="#rfc.index">Index</a></h2>
    48954829      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a>
    48964830      </p>
     
    52395173      </div>
    52405174      <div class="avoidbreakinside">
    5241          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     5175         <h2 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h2>
    52425176         <p><b>Roy T. Fielding</b>
    52435177            (editor)
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2734 r2748  
    44   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    6       <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title><script>
     6      <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title><script type="application/javascript">
    77var buttonsAdded = false;
    88
     
    1717
    1818function feedback() {
    19   toggleButtonsToElementsByName("h1");
    2019  toggleButtonsToElementsByName("h2");
    2120  toggleButtonsToElementsByName("h3");
    2221  toggleButtonsToElementsByName("h4");
     22  toggleButtonsToElementsByName("h5");
    2323
    2424  buttonsAdded = !buttonsAdded;
     
    147147  margin-left: 0em;
    148148}
     149dl.reference > dt {
     150  font-weight: bold;
     151}
     152dl.reference > dd {
     153  margin-left: 6em;
     154}
    149155h1 {
     156  color: green;
     157  font-size: 150%;
     158  line-height: 18pt;
     159  font-weight: bold;
     160  text-align: center;
     161  margin-top: 36pt;
     162  margin-bottom: 0pt;
     163}
     164h2 {
    150165  font-size: 130%;
    151166  line-height: 21pt;
    152167  page-break-after: avoid;
    153168}
    154 h1.np {
     169h2.np {
    155170  page-break-before: always;
    156171}
    157 h2 {
     172h3 {
    158173  font-size: 120%;
    159174  line-height: 15pt;
    160175  page-break-after: avoid;
    161176}
    162 h3 {
     177h4 {
    163178  font-size: 110%;
    164179  page-break-after: avoid;
    165180}
    166 h4, h5, h6 {
     181h5, h6 {
    167182  page-break-after: avoid;
    168183}
     
    266281  border-width: 2px;
    267282}
    268 table.left {
     283table.tleft {
    269284  margin-right: auto;
    270285}
    271 table.right {
     286table.tright {
    272287  margin-left: auto;
    273288}
    274 table.center {
     289table.tcenter {
    275290  margin-left: auto;
    276291  margin-right: auto;
     
    303318  color: white;
    304319}
    305 td.reference {
    306   vertical-align: top;
    307   white-space: nowrap;
    308   padding-right: 1em;
    309 }
    310320thead {
    311321  display:table-header-group;
     
    333343  margin-left: 0em;
    334344}
    335 .title, .filename, h1, h2, h3, h4 {
     345.filename, h1, h2, h3, h4 {
    336346  font-family: candara, calibri, segoe, optima, arial, sans-serif;
    337347}
     
    381391.filename {
    382392  color: #333333;
    383   font-size: 75%;
     393  font-size: 112%;
    384394  font-weight: bold;
    385395  line-height: 21pt;
    386396  text-align: center;
     397  margin-top: 0pt;
    387398}
    388399.fn {
     
    394405.right {
    395406  text-align: right;
    396 }
    397 .title {
    398   color: green;
    399   font-size: 150%;
    400   line-height: 18pt;
    401   font-weight: bold;
    402   text-align: center;
    403   margin-top: 36pt;
    404407}
    405408.warning {
     
    428431  border: 1px solid silver;
    429432  border-radius: 5px;
     433}
     434.publishedasrfc {
     435  background-color: yellow;
     436  color: green;
     437  font-size: 14pt;
     438  text-align: center;
    430439}
    431440
     
    531540      <link href="p1-messaging.html" rel="prev">
    532541      <link href="p4-conditional.html" rel="next">
    533       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.710, 2014/12/09 13:12:18, XSLT vendor: Saxonica http://www.saxonica.com/">
     542      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.756, 2015/12/31 17:59:21, XSLT vendor: Saxonica http://www.saxonica.com/">
    534543      <meta name="keywords" content="Hypertext Transfer Protocol, HTTP, HTTP semantics, HTTP payload, HTTP content, HTTP method, HTTP status code">
    535544      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     
    573582         </tbody>
    574583      </table>
    575       <p class="title" id="rfc.title">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content<br><span class="filename">draft-ietf-httpbis-p2-semantics-latest</span></p>
    576       <p style="color: green; text-align: center; font-size: 14pt; background-color: yellow;"><b>Note:</b> a later version of this document has been published as <a href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7231.html">RFC7231</a>.
     584      <div id="rfc.title">
     585         <h1>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</h1>
     586         <div class="filename">draft-ietf-httpbis-p2-semantics-latest</div>
     587      </div>
     588      <p class="publishedasrfc"><b>Note:</b> a later version of this document has been published as <a href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7231.html">RFC7231</a>.
    577589         
    578590      </p>
    579       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
     591      <h2 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h2>
    580592      <p>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for
    581593         distributed, collaborative, hypertext information systems. This document defines the
     
    584596         (metadata and body content) and mechanisms for content negotiation.
    585597      </p>
    586       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
     598      <h2 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h2>
    587599      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org),
    588600         which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
     
    594606      </p>
    595607      <div id="rfc.status">
    596          <h1><a href="#rfc.status">Status of This Memo</a></h1>
     608         <h2><a href="#rfc.status">Status of This Memo</a></h2>
    597609         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78
    598610            and BCP 79.
     
    609621      </div>
    610622      <div id="rfc.copyrightnotice">
    611          <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     623         <h2><a href="#rfc.copyrightnotice">Copyright Notice</a></h2>
    612624         <p>Copyright © 2014 IETF Trust and the persons identified as the document authors. All
    613625            rights reserved.
     
    632644      <hr class="noprint">
    633645      <div id="rfc.toc">
    634          <h1 class="np"><a href="#rfc.toc">Table of Contents</a></h1>
     646         <h2 class="np"><a href="#rfc.toc">Table of Contents</a></h2>
    635647         <ul class="toc">
    636648            <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     
    832844      </div>
    833845      <div id="introduction">
    834          <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     846         <h2 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h2>
    835847         <div id="rfc.section.1.p.1">
    836848            <p>Each Hypertext Transfer Protocol (HTTP) message is either a request or a response.
     
    862874         </div>
    863875         <div id="conformance">
    864             <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#conformance">Conformance and Error Handling</a></h2>
     876            <h3 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#conformance">Conformance and Error Handling</a></h3>
    865877            <div id="rfc.section.1.1.p.1">
    866878               <p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
     
    875887         </div>
    876888         <div id="notation">
    877             <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     889            <h3 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h3>
    878890            <div id="rfc.section.1.2.p.1">
    879891               <p>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 a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF List Extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator
     
    889901      </div>
    890902      <div id="resources">
    891          <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#resources">Resources</a></h1>
     903         <h2 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#resources">Resources</a></h2>
    892904         <div id="rfc.section.2.p.1">
    893905            <p>The target of an HTTP request is called a "<dfn>resource</dfn>". HTTP does not limit the nature of a resource; it merely defines an interface that
     
    908920      </div>
    909921      <div id="representations">
    910          <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#representations">Representations</a></h1>
     922         <h2 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#representations">Representations</a></h2>
    911923         <div id="rfc.section.3.p.1">
    912924            <p>Considering that a resource could be anything, and that the uniform interface provided
     
    931943         </div>
    932944         <div id="representation.metadata">
    933             <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#representation.metadata">Representation Metadata</a></h2>
     945            <h3 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#representation.metadata">Representation Metadata</a></h3>
    934946            <div id="rfc.section.3.1.p.1">
    935947               <p>Representation header fields provide metadata about the representation. When a message
     
    940952               </p>
    941953            </div>
    942             <div id="rfc.section.3.1.p.2">
     954            <div id="rfc.section.3.1.p.2" class="avoidbreakafter">
    943955               <p>The following header fields convey representation metadata:</p>
    944956            </div>
    945957            <div id="rfc.table.u.1">
    946                <table class="tt full left" cellpadding="3" cellspacing="0">
     958               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    947959                  <thead>
    948960                     <tr>
     
    972984            </div>
    973985            <div id="data.type">
    974                <h3 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;<a href="#data.type">Processing Representation Data</a></h3>
     986               <h4 id="rfc.section.3.1.1"><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;<a href="#data.type">Processing Representation Data</a></h4>
    975987               <div id="media.type">
    976                   <h4 id="rfc.section.3.1.1.1"><a href="#rfc.section.3.1.1.1">3.1.1.1</a>&nbsp;<a href="#media.type">Media Type</a></h4>
     988                  <h5 id="rfc.section.3.1.1.1"><a href="#rfc.section.3.1.1.1">3.1.1.1</a>&nbsp;<a href="#media.type">Media Type</a></h5>
    977989                  <div id="rfc.section.3.1.1.1.p.1">
    978990                     <p>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.2" title="Content-Type">Section&nbsp;3.1.1.5</a>) and <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;5.3.2</a>) header fields in order to provide open and extensible data typing and type negotiation.
     
    10001012                     </p>
    10011013                  </div>
    1002                   <div id="rfc.section.3.1.1.1.p.4">
     1014                  <div id="rfc.section.3.1.1.1.p.4" class="avoidbreakafter">
    10031015                     <p>A parameter value that matches the <a href="#imported.abnf" class="smpl">token</a> production can be transmitted either as a token or within a quoted-string. The quoted
    10041016                        and unquoted values are equivalent. For example, the following examples are all equivalent,
     
    10251037               </div>
    10261038               <div id="charset">
    1027                   <h4 id="rfc.section.3.1.1.2"><a href="#rfc.section.3.1.1.2">3.1.1.2</a>&nbsp;<a href="#charset">Charset</a></h4>
     1039                  <h5 id="rfc.section.3.1.1.2"><a href="#rfc.section.3.1.1.2">3.1.1.2</a>&nbsp;<a href="#charset">Charset</a></h5>
    10281040                  <div id="rfc.section.3.1.1.2.p.1">
    10291041                     <p>HTTP uses <dfn>charset</dfn> names to indicate or negotiate the character encoding scheme of a textual representation <a href="#RFC6365" id="rfc.xref.RFC6365.2"><cite title="Terminology Used in Internationalization in the IETF">[RFC6365]</cite></a>. A charset is identified by a case-insensitive token.
     
    10381050               </div>
    10391051               <div id="canonicalization.and.text.defaults">
    1040                   <h4 id="rfc.section.3.1.1.3"><a href="#rfc.section.3.1.1.3">3.1.1.3</a>&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h4>
     1052                  <h5 id="rfc.section.3.1.1.3"><a href="#rfc.section.3.1.1.3">3.1.1.3</a>&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h5>
    10411053                  <div id="rfc.section.3.1.1.3.p.1">
    10421054                     <p>Internet media types are registered with a canonical form in order to be interoperable
     
    10681080               </div>
    10691081               <div id="multipart.types">
    1070                   <h4 id="rfc.section.3.1.1.4"><a href="#rfc.section.3.1.1.4">3.1.1.4</a>&nbsp;<a href="#multipart.types">Multipart Types</a></h4>
     1082                  <h5 id="rfc.section.3.1.1.4"><a href="#rfc.section.3.1.1.4">3.1.1.4</a>&nbsp;<a href="#multipart.types">Multipart Types</a></h5>
    10711083                  <div id="rfc.section.3.1.1.4.p.1">
    10721084                     <p>MIME provides for a number of "multipart" types — encapsulations of one or more representations
     
    10861098               </div>
    10871099               <div id="header.content-type">
    1088                   <h4 id="rfc.section.3.1.1.5"><a href="#rfc.section.3.1.1.5">3.1.1.5</a>&nbsp;<a href="#header.content-type">Content-Type</a></h4>
     1100                  <h5 id="rfc.section.3.1.1.5"><a href="#rfc.section.3.1.1.5">3.1.1.5</a>&nbsp;<a href="#header.content-type">Content-Type</a></h5>
    10891101                  <div id="rfc.section.3.1.1.5.p.1">
    10901102                     <p>The "Content-Type" header field indicates the media type of the associated representation:
     
    11221134            </div>
    11231135            <div id="data.encoding">
    1124                <h3 id="rfc.section.3.1.2"><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;<a href="#data.encoding">Encoding for Compression or Integrity</a></h3>
     1136               <h4 id="rfc.section.3.1.2"><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;<a href="#data.encoding">Encoding for Compression or Integrity</a></h4>
    11251137               <div id="content.codings">
    1126                   <h4 id="rfc.section.3.1.2.1"><a href="#rfc.section.3.1.2.1">3.1.2.1</a>&nbsp;<a href="#content.codings">Content Codings</a></h4>
     1138                  <h5 id="rfc.section.3.1.2.1"><a href="#rfc.section.3.1.2.1">3.1.2.1</a>&nbsp;<a href="#content.codings">Content Codings</a></h5>
    11271139                  <div id="rfc.section.3.1.2.1.p.1">
    11281140                     <p>Content coding values indicate an encoding transformation that has been or can be
     
    11531165               </div>
    11541166               <div id="header.content-encoding">
    1155                   <h4 id="rfc.section.3.1.2.2"><a href="#rfc.section.3.1.2.2">3.1.2.2</a>&nbsp;<a href="#header.content-encoding">Content-Encoding</a></h4>
     1167                  <h5 id="rfc.section.3.1.2.2"><a href="#rfc.section.3.1.2.2">3.1.2.2</a>&nbsp;<a href="#header.content-encoding">Content-Encoding</a></h5>
    11561168                  <div id="rfc.section.3.1.2.2.p.1">
    11571169                     <p>The "Content-Encoding" header field indicates what content codings have been applied
     
    12031215            </div>
    12041216            <div id="audience.language">
    1205                <h3 id="rfc.section.3.1.3"><a href="#rfc.section.3.1.3">3.1.3</a>&nbsp;<a href="#audience.language">Audience Language</a></h3>
     1217               <h4 id="rfc.section.3.1.3"><a href="#rfc.section.3.1.3">3.1.3</a>&nbsp;<a href="#audience.language">Audience Language</a></h4>
    12061218               <div id="language.tags">
    1207                   <h4 id="rfc.section.3.1.3.1"><a href="#rfc.section.3.1.3.1">3.1.3.1</a>&nbsp;<a href="#language.tags">Language Tags</a></h4>
     1219                  <h5 id="rfc.section.3.1.3.1"><a href="#rfc.section.3.1.3.1">3.1.3.1</a>&nbsp;<a href="#language.tags">Language Tags</a></h5>
    12081220                  <div id="rfc.section.3.1.3.1.p.1">
    12091221                     <p>A language tag, as defined in <a href="#RFC5646" id="rfc.xref.RFC5646.1"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, identifies a natural language spoken, written, or otherwise conveyed by human beings
     
    12181230                  <div id="rfc.figure.u.10"><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, see <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="https://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
    12191231</pre></div>
    1220                   <div id="rfc.section.3.1.3.1.p.3">
     1232                  <div id="rfc.section.3.1.3.1.p.3" class="avoidbreakafter">
    12211233                     <p>A language tag is a sequence of one or more case-insensitive subtags, each separated
    12221234                        by a hyphen character ("-", %x2D). In most cases, a language tag consists of a primary
     
    12351247               </div>
    12361248               <div id="header.content-language">
    1237                   <h4 id="rfc.section.3.1.3.2"><a href="#rfc.section.3.1.3.2">3.1.3.2</a>&nbsp;<a href="#header.content-language">Content-Language</a></h4>
     1249                  <h5 id="rfc.section.3.1.3.2"><a href="#rfc.section.3.1.3.2">3.1.3.2</a>&nbsp;<a href="#header.content-language">Content-Language</a></h5>
    12381250                  <div id="rfc.section.3.1.3.2.p.1">
    12391251                     <p>The "Content-Language" header field describes the natural language(s) of the intended
     
    12821294            </div>
    12831295            <div id="identification">
    1284                <h3 id="rfc.section.3.1.4"><a href="#rfc.section.3.1.4">3.1.4</a>&nbsp;<a href="#identification">Identification</a></h3>
     1296               <h4 id="rfc.section.3.1.4"><a href="#rfc.section.3.1.4">3.1.4</a>&nbsp;<a href="#identification">Identification</a></h4>
    12851297               <div id="identifying.payload">
    1286                   <h4 id="rfc.section.3.1.4.1"><a href="#rfc.section.3.1.4.1">3.1.4.1</a>&nbsp;<a href="#identifying.payload">Identifying a Representation</a></h4>
     1298                  <h5 id="rfc.section.3.1.4.1"><a href="#rfc.section.3.1.4.1">3.1.4.1</a>&nbsp;<a href="#identifying.payload">Identifying a Representation</a></h5>
    12871299                  <div id="rfc.section.3.1.4.1.p.1">
    12881300                     <p>When a complete or partial representation is transferred in a message payload, it
     
    13261338               </div>
    13271339               <div id="header.content-location">
    1328                   <h4 id="rfc.section.3.1.4.2"><a href="#rfc.section.3.1.4.2">3.1.4.2</a>&nbsp;<a href="#header.content-location">Content-Location</a></h4>
     1340                  <h5 id="rfc.section.3.1.4.2"><a href="#rfc.section.3.1.4.2">3.1.4.2</a>&nbsp;<a href="#header.content-location">Content-Location</a></h5>
    13291341                  <div id="rfc.section.3.1.4.2.p.1">
    13301342                     <p>The "Content-Location" header field references a URI that can be used as an identifier
     
    14041416         </div>
    14051417         <div id="representation.data">
    1406             <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#representation.data">Representation Data</a></h2>
     1418            <h3 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#representation.data">Representation Data</a></h3>
    14071419            <div id="rfc.section.3.2.p.1">
    14081420               <p>The representation data associated with an HTTP message is either provided as the
     
    14121424               </p>
    14131425            </div>
    1414             <div id="rfc.section.3.2.p.2">
     1426            <div id="rfc.section.3.2.p.2" class="avoidbreakafter">
    14151427               <p>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:
    14161428               </p>
     
    14201432         </div>
    14211433         <div id="payload">
    1422             <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#payload">Payload Semantics</a></h2>
     1434            <h3 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#payload">Payload Semantics</a></h3>
    14231435            <div id="rfc.section.3.3.p.1">
    14241436               <p>Some HTTP messages transfer a complete or partial representation as the message "<dfn>payload</dfn>". In some cases, a payload might contain only the associated representation's header
     
    14491461            </div>
    14501462            <div id="rfc.table.u.2">
    1451                <table class="tt full left" cellpadding="3" cellspacing="0">
     1463               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    14521464                  <thead>
    14531465                     <tr>
     
    14781490         </div>
    14791491         <div id="content.negotiation">
    1480             <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#content.negotiation">Content Negotiation</a></h2>
     1492            <h3 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#content.negotiation">Content Negotiation</a></h3>
    14811493            <div id="rfc.section.3.4.p.1">
    14821494               <p>When responses convey payload information, whether indicating a success or an error,
     
    15101522            </div>
    15111523            <div id="proactive.negotiation">
    1512                <h3 id="rfc.section.3.4.1"><a href="#rfc.section.3.4.1">3.4.1</a>&nbsp;<a href="#proactive.negotiation">Proactive Negotiation</a></h3>
     1524               <h4 id="rfc.section.3.4.1"><a href="#rfc.section.3.4.1">3.4.1</a>&nbsp;<a href="#proactive.negotiation">Proactive Negotiation</a></h4>
    15131525               <div id="rfc.section.3.4.1.p.1">
    15141526                  <p>When content negotiation preferences are sent by the user agent in a request to encourage
     
    15591571            </div>
    15601572            <div id="reactive.negotiation">
    1561                <h3 id="rfc.section.3.4.2"><a href="#rfc.section.3.4.2">3.4.2</a>&nbsp;<a href="#reactive.negotiation">Reactive Negotiation</a></h3>
     1573               <h4 id="rfc.section.3.4.2"><a href="#rfc.section.3.4.2">3.4.2</a>&nbsp;<a href="#reactive.negotiation">Reactive Negotiation</a></h4>
    15621574               <div id="rfc.section.3.4.2.p.1">
    15631575                  <p>With <dfn>reactive negotiation</dfn> (a.k.a., <dfn>agent-driven negotiation</dfn>), selection of the best response representation (regardless of the status code) is
     
    16051617      </div>
    16061618      <div id="methods">
    1607          <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#methods">Request Methods</a></h1>
     1619         <h2 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#methods">Request Methods</a></h2>
    16081620         <div id="method.overview">
    1609             <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#method.overview">Overview</a></h2>
     1621            <h3 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#method.overview">Overview</a></h3>
    16101622            <div id="rfc.section.4.1.p.1">
    16111623               <p>The request method token is the primary source of request semantics; it indicates
     
    16461658            <div id="rfc.table.1">
    16471659               <div id="table.of.methods"></div>
    1648                <table class="tt full left" cellpadding="3" cellspacing="0">
     1660               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    16491661                  <thead>
    16501662                     <tr>
     
    17171729         </div>
    17181730         <div id="method.properties">
    1719             <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#method.properties">Common Method Properties</a></h2>
     1731            <h3 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#method.properties">Common Method Properties</a></h3>
    17201732            <div id="safe.methods">
    1721                <h3 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a href="#safe.methods">Safe Methods</a></h3>
     1733               <h4 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a>&nbsp;<a href="#safe.methods">Safe Methods</a></h4>
    17221734               <div id="rfc.section.4.2.1.p.1">
    17231735                  <p>Request methods are considered "<dfn>safe</dfn>" if their defined semantics are essentially read-only; i.e., the client does not
     
    17721784            </div>
    17731785            <div id="idempotent.methods">
    1774                <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></h3>
     1786               <h4 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></h4>
    17751787               <div id="rfc.section.4.2.2.p.1">
    17761788                  <p>A request method is considered "<dfn id="idempotent">idempotent</dfn>" if the intended effect on the server of multiple identical requests with that method
     
    17981810            </div>
    17991811            <div id="cacheable.methods">
    1800                <h3 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></h3>
     1812               <h4 id="rfc.section.4.2.3"><a href="#rfc.section.4.2.3">4.2.3</a>&nbsp;<a href="#cacheable.methods">Cacheable Methods</a></h4>
    18011813               <div id="rfc.section.4.2.3.p.1">
    18021814                  <p>Request methods can be defined as "<dfn id="cacheable">cacheable</dfn>" to indicate that responses to them are allowed to be stored for future reuse; for
     
    18091821         </div>
    18101822         <div id="method.definitions">
    1811             <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#method.definitions">Method Definitions</a></h2>
     1823            <h3 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#method.definitions">Method Definitions</a></h3>
    18121824            <div id="GET">
    1813                <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a href="#GET">GET</a></h3>
     1825               <h4 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a href="#GET">GET</a></h4>
    18141826               <div id="rfc.iref.g.13"></div>
    18151827               <div id="rfc.section.4.3.1.p.1">
     
    18501862            </div>
    18511863            <div id="HEAD">
    1852                <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;<a href="#HEAD">HEAD</a></h3>
     1864               <h4 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;<a href="#HEAD">HEAD</a></h4>
    18531865               <div id="rfc.iref.h.1"></div>
    18541866               <div id="rfc.section.4.3.2.p.1">
     
    18731885            </div>
    18741886            <div id="POST">
    1875                <h3 id="rfc.section.4.3.3"><a href="#rfc.section.4.3.3">4.3.3</a>&nbsp;<a href="#POST">POST</a></h3>
     1887               <h4 id="rfc.section.4.3.3"><a href="#rfc.section.4.3.3">4.3.3</a>&nbsp;<a href="#POST">POST</a></h4>
    18761888               <div id="rfc.section.4.3.3.p.1">
    18771889                  <p>The POST method requests that the <a href="#resources" class="smpl">target resource</a> process the representation enclosed in the request according to the resource's own
     
    19191931            </div>
    19201932            <div id="PUT">
    1921                <h3 id="rfc.section.4.3.4"><a href="#rfc.section.4.3.4">4.3.4</a>&nbsp;<a href="#PUT">PUT</a></h3>
     1933               <h4 id="rfc.section.4.3.4"><a href="#rfc.section.4.3.4">4.3.4</a>&nbsp;<a href="#PUT">PUT</a></h4>
    19221934               <div id="rfc.iref.p.1"></div>
    19231935               <div id="rfc.section.4.3.4.p.1">
     
    20342046            </div>
    20352047            <div id="DELETE">
    2036                <h3 id="rfc.section.4.3.5"><a href="#rfc.section.4.3.5">4.3.5</a>&nbsp;<a href="#DELETE">DELETE</a></h3>
     2048               <h4 id="rfc.section.4.3.5"><a href="#rfc.section.4.3.5">4.3.5</a>&nbsp;<a href="#DELETE">DELETE</a></h4>
    20372049               <div id="rfc.iref.d.1"></div>
    20382050               <div id="rfc.section.4.3.5.p.1">
     
    20832095            </div>
    20842096            <div id="CONNECT">
    2085                <h3 id="rfc.section.4.3.6"><a href="#rfc.section.4.3.6">4.3.6</a>&nbsp;<a href="#CONNECT">CONNECT</a></h3>
     2097               <h4 id="rfc.section.4.3.6"><a href="#rfc.section.4.3.6">4.3.6</a>&nbsp;<a href="#CONNECT">CONNECT</a></h4>
    20862098               <div id="rfc.section.4.3.6.p.1">
    20872099                  <p>The CONNECT method requests that the recipient establish a tunnel to the destination
     
    21582170            </div>
    21592171            <div id="OPTIONS">
    2160                <h3 id="rfc.section.4.3.7"><a href="#rfc.section.4.3.7">4.3.7</a>&nbsp;<a href="#OPTIONS">OPTIONS</a></h3>
     2172               <h4 id="rfc.section.4.3.7"><a href="#rfc.section.4.3.7">4.3.7</a>&nbsp;<a href="#OPTIONS">OPTIONS</a></h4>
    21612173               <div id="rfc.iref.o.1"></div>
    21622174               <div id="rfc.section.4.3.7.p.1">
     
    22052217            </div>
    22062218            <div id="TRACE">
    2207                <h3 id="rfc.section.4.3.8"><a href="#rfc.section.4.3.8">4.3.8</a>&nbsp;<a href="#TRACE">TRACE</a></h3>
     2219               <h4 id="rfc.section.4.3.8"><a href="#rfc.section.4.3.8">4.3.8</a>&nbsp;<a href="#TRACE">TRACE</a></h4>
    22082220               <div id="rfc.iref.t.1"></div>
    22092221               <div id="rfc.section.4.3.8.p.1">
     
    22392251      </div>
    22402252      <div id="request.header.fields">
    2241          <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#request.header.fields">Request Header Fields</a></h1>
     2253         <h2 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#request.header.fields">Request Header Fields</a></h2>
    22422254         <div id="rfc.section.5.p.1">
    22432255            <p>A client sends request header fields to provide more information about the request
     
    22492261         </div>
    22502262         <div id="request.controls">
    2251             <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#request.controls">Controls</a></h2>
     2263            <h3 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#request.controls">Controls</a></h3>
    22522264            <div id="rfc.section.5.1.p.1">
    22532265               <p>Controls are request header fields that direct specific handling of the request.</p>
    22542266            </div>
    22552267            <div id="rfc.table.u.3">
    2256                <table class="tt full left" cellpadding="3" cellspacing="0">
     2268               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    22572269                  <thead>
    22582270                     <tr>
     
    22942306            </div>
    22952307            <div id="header.expect">
    2296                <h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a href="#header.expect">Expect</a></h3>
     2308               <h4 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a href="#header.expect">Expect</a></h4>
    22972309               <div id="rfc.section.5.1.1.p.1">
    22982310                  <p>The "Expect" header field in a request indicates a certain set of behaviors (expectations)
     
    23982410            </div>
    23992411            <div id="header.max-forwards">
    2400                <h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a href="#header.max-forwards">Max-Forwards</a></h3>
     2412               <h4 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a href="#header.max-forwards">Max-Forwards</a></h4>
    24012413               <div id="rfc.section.5.1.2.p.1">
    24022414                  <p>The "Max-Forwards" header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;4.3.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;4.3.7</a>) request methods to limit the number of times that the request is forwarded by proxies.
     
    24282440         </div>
    24292441         <div id="request.conditionals">
    2430             <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#request.conditionals">Conditionals</a></h2>
     2442            <h3 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#request.conditionals">Conditionals</a></h3>
    24312443            <div id="rfc.section.5.2.p.1">
    24322444               <p>The HTTP conditional request header fields <a href="#RFC7232" id="rfc.xref.RFC7232.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a> allow a client to place a precondition on the state of the target resource, so that
     
    24402452            </div>
    24412453            <div id="rfc.table.u.4">
    2442                <table class="tt full left" cellpadding="3" cellspacing="0">
     2454               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    24432455                  <thead>
    24442456                     <tr>
     
    24732485         </div>
    24742486         <div id="request.conneg">
    2475             <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#request.conneg">Content Negotiation</a></h2>
     2487            <h3 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#request.conneg">Content Negotiation</a></h3>
    24762488            <div id="rfc.section.5.3.p.1">
    24772489               <p>The following request header fields are sent by a user agent to engage in <a href="#proactive.negotiation" class="smpl">proactive negotiation</a> of the response content, as defined in <a href="#proactive.negotiation" title="Proactive Negotiation">Section&nbsp;3.4.1</a>. The preferences sent in these fields apply to any content in the response, including
     
    24812493            </div>
    24822494            <div id="rfc.table.u.5">
    2483                <table class="tt full left" cellpadding="3" cellspacing="0">
     2495               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    24842496                  <thead>
    24852497                     <tr>
     
    25092521            </div>
    25102522            <div id="quality.values">
    2511                <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a href="#quality.values">Quality Values</a></h3>
     2523               <h4 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a href="#quality.values">Quality Values</a></h4>
    25122524               <div id="rfc.section.5.3.1.p.1">
    25132525                  <p>Many of the request header fields for <a href="#proactive.negotiation" class="smpl">proactive negotiation</a> use a common parameter, named "q" (case-insensitive), to assign a relative "weight"
     
    25352547            </div>
    25362548            <div id="header.accept">
    2537                <h3 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a href="#header.accept">Accept</a></h3>
     2549               <h4 id="rfc.section.5.3.2"><a href="#rfc.section.5.3.2">5.3.2</a>&nbsp;<a href="#header.accept">Accept</a></h4>
    25382550               <div id="rfc.section.5.3.2.p.1">
    25392551                  <p>The "Accept" header field can be used by user agents to specify response media types
     
    26312643          text/html;level=2;q=0.4, */*;q=0.5
    26322644</pre></div>
    2633                <div id="rfc.section.5.3.2.p.13">
     2645               <div id="rfc.section.5.3.2.p.13" class="avoidbreakafter">
    26342646                  <p>would cause the following values to be associated:</p>
    26352647               </div>
    26362648               <div id="rfc.table.u.6">
    2637                   <table class="tt full left" cellpadding="3" cellspacing="0">
     2649                  <table class="tt full tleft" cellpadding="3" cellspacing="0">
    26382650                     <thead>
    26392651                        <tr>
     
    26782690            </div>
    26792691            <div id="header.accept-charset">
    2680                <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a href="#header.accept-charset">Accept-Charset</a></h3>
     2692               <h4 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a href="#header.accept-charset">Accept-Charset</a></h4>
    26812693               <div id="rfc.section.5.3.3.p.1">
    26822694                  <p>The "Accept-Charset" header field can be sent by a user agent to indicate what charsets
     
    27192731            </div>
    27202732            <div id="header.accept-encoding">
    2721                <h3 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></h3>
     2733               <h4 id="rfc.section.5.3.4"><a href="#rfc.section.5.3.4">5.3.4</a>&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></h4>
    27222734               <div id="rfc.section.5.3.4.p.1">
    27232735                  <p>The "Accept-Encoding" header field can be used by user agents to indicate what response
     
    27882800            </div>
    27892801            <div id="header.accept-language">
    2790                <h3 id="rfc.section.5.3.5"><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;<a href="#header.accept-language">Accept-Language</a></h3>
     2802               <h4 id="rfc.section.5.3.5"><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;<a href="#header.accept-language">Accept-Language</a></h4>
    27912803               <div id="rfc.section.5.3.5.p.1">
    27922804                  <p>The "Accept-Language" header field can be used by user agents to indicate the set
     
    28582870         </div>
    28592871         <div id="request.auth">
    2860             <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#request.auth">Authentication Credentials</a></h2>
     2872            <h3 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a href="#request.auth">Authentication Credentials</a></h3>
    28612873            <div id="rfc.section.5.4.p.1">
    28622874               <p>Two header fields are used for carrying authentication credentials, as defined in <a href="#RFC7235" id="rfc.xref.RFC7235.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a>. Note that various custom mechanisms for user authentication use the Cookie header
     
    28652877            </div>
    28662878            <div id="rfc.table.u.7">
    2867                <table class="tt full left" cellpadding="3" cellspacing="0">
     2879               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    28682880                  <thead>
    28692881                     <tr>
     
    28862898         </div>
    28872899         <div id="request.context">
    2888             <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a href="#request.context">Request Context</a></h2>
     2900            <h3 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a href="#request.context">Request Context</a></h3>
    28892901            <div id="rfc.section.5.5.p.1">
    28902902               <p>The following request header fields provide additional information about the request
     
    28942906            </div>
    28952907            <div id="rfc.table.u.8">
    2896                <table class="tt full left" cellpadding="3" cellspacing="0">
     2908               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    28972909                  <thead>
    28982910                     <tr>
     
    29182930            </div>
    29192931            <div id="header.from">
    2920                <h3 id="rfc.section.5.5.1"><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;<a href="#header.from">From</a></h3>
    2921                <div id="rfc.section.5.5.1.p.1">
     2932               <h4 id="rfc.section.5.5.1"><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;<a href="#header.from">From</a></h4>
     2933               <div id="rfc.section.5.5.1.p.1" class="avoidbreakafter">
    29222934                  <p>The "From" header field contains an Internet email address for a human user who controls
    29232935                     the requesting user agent. The address ought to be machine-usable, as defined by "mailbox"
     
    29292941  <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, see <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="https://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
    29302942</pre></div>
    2931                <div id="rfc.section.5.5.1.p.2">
     2943               <div id="rfc.section.5.5.1.p.2" class="avoidbreakafter">
    29322944                  <p>An example is:</p>
    29332945               </div>
     
    29522964            </div>
    29532965            <div id="header.referer">
    2954                <h3 id="rfc.section.5.5.2"><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;<a href="#header.referer">Referer</a></h3>
     2966               <h4 id="rfc.section.5.5.2"><a href="#rfc.section.5.5.2">5.5.2</a>&nbsp;<a href="#header.referer">Referer</a></h4>
    29552967               <div id="rfc.section.5.5.2.p.1">
    29562968                  <p>The "Referer" [sic] header field allows the user agent to specify a URI reference
     
    29682980                  </p>
    29692981               </div>
    2970                <div id="rfc.section.5.5.2.p.3">
     2982               <div id="rfc.section.5.5.2.p.3" class="avoidbreakafter">
    29712983                  <p>Example:</p>
    29722984               </div>
     
    30013013            </div>
    30023014            <div id="header.user-agent">
    3003                <h3 id="rfc.section.5.5.3"><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;<a href="#header.user-agent">User-Agent</a></h3>
     3015               <h4 id="rfc.section.5.5.3"><a href="#rfc.section.5.5.3">5.5.3</a>&nbsp;<a href="#header.user-agent">User-Agent</a></h4>
    30043016               <div id="rfc.section.5.5.3.p.1">
    30053017                  <p>The "User-Agent" header field contains information about the user agent originating
     
    30303042                  </p>
    30313043               </div>
    3032                <div id="rfc.section.5.5.3.p.4">
     3044               <div id="rfc.section.5.5.3.p.4" class="avoidbreakafter">
    30333045                  <p>Example:</p>
    30343046               </div>
     
    30533065      </div>
    30543066      <div id="status.codes">
    3055          <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#status.codes">Response Status Codes</a></h1>
     3067         <h2 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#status.codes">Response Status Codes</a></h2>
    30563068         <div id="rfc.section.6.p.1">
    30573069            <p>The status-code element is a three-digit integer code giving the result of the attempt
     
    30923104         </div>
    30933105         <div id="overview.of.status.codes">
    3094             <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#overview.of.status.codes">Overview of Status Codes</a></h2>
     3106            <h3 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#overview.of.status.codes">Overview of Status Codes</a></h3>
    30953107            <div id="rfc.section.6.1.p.1">
    30963108               <p>The status codes listed below are defined in this specification, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 4</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>, <a href="p5-range.html#range.response" title="Responses to a Range Request">Section 4</a> of <a href="#RFC7233" id="rfc.xref.RFC7233.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[RFC7233]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#RFC7235" id="rfc.xref.RFC7235.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[RFC7235]</cite></a>. The reason phrases listed here are only recommendations — they can be replaced by
     
    31063118            </div>
    31073119            <div id="rfc.table.u.9">
    3108                <table class="tt full left" cellpadding="3" cellspacing="0">
     3120               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    31093121                  <thead>
    31103122                     <tr>
     
    33313343         </div>
    33323344         <div id="status.1xx">
    3333             <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#status.1xx">Informational 1xx</a></h2>
     3345            <h3 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#status.1xx">Informational 1xx</a></h3>
    33343346            <div id="rfc.section.6.2.p.1">
    33353347               <p>The <dfn>1xx (Informational)</dfn> class of status code indicates an interim response for communicating connection status
     
    33523364            </div>
    33533365            <div id="status.100">
    3354                <h3 id="rfc.section.6.2.1"><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;<a href="#status.100">100 Continue</a></h3>
     3366               <h4 id="rfc.section.6.2.1"><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;<a href="#status.100">100 Continue</a></h4>
    33553367               <div id="rfc.section.6.2.1.p.1">
    33563368                  <p>The <dfn>100 (Continue)</dfn> status code indicates that the initial part of a request has been received and has
     
    33703382            </div>
    33713383            <div id="status.101">
    3372                <h3 id="rfc.section.6.2.2"><a href="#rfc.section.6.2.2">6.2.2</a>&nbsp;<a href="#status.101">101 Switching Protocols</a></h3>
     3384               <h4 id="rfc.section.6.2.2"><a href="#rfc.section.6.2.2">6.2.2</a>&nbsp;<a href="#status.101">101 Switching Protocols</a></h4>
    33733385               <div id="rfc.section.6.2.2.p.1">
    33743386                  <p>The <dfn>101 (Switching Protocols)</dfn> status code indicates that the server understands and is willing to comply with the
     
    33873399         </div>
    33883400         <div id="status.2xx">
    3389             <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a href="#status.2xx">Successful 2xx</a></h2>
     3401            <h3 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a href="#status.2xx">Successful 2xx</a></h3>
    33903402            <div id="rfc.section.6.3.p.1">
    33913403               <p>The <dfn>2xx (Successful)</dfn> class of status code indicates that the client's request was successfully received,
     
    33943406            </div>
    33953407            <div id="status.200">
    3396                <h3 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;<a href="#status.200">200 OK</a></h3>
     3408               <h4 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;<a href="#status.200">200 OK</a></h4>
    33973409               <div id="rfc.section.6.3.1.p.1">
    33983410                  <p>The <dfn>200 (OK)</dfn> status code indicates that the request has succeeded. The payload sent in a 200 response
     
    34303442            </div>
    34313443            <div id="status.201">
    3432                <h3 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;<a href="#status.201">201 Created</a></h3>
     3444               <h4 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;<a href="#status.201">201 Created</a></h4>
    34333445               <div id="rfc.section.6.3.2.p.1">
    34343446                  <p>The <dfn>201 (Created)</dfn> status code indicates that the request has been fulfilled and has resulted in one
     
    34443456            </div>
    34453457            <div id="status.202">
    3446                <h3 id="rfc.section.6.3.3"><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;<a href="#status.202">202 Accepted</a></h3>
     3458               <h4 id="rfc.section.6.3.3"><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;<a href="#status.202">202 Accepted</a></h4>
    34473459               <div id="rfc.section.6.3.3.p.1">
    34483460                  <p>The <dfn>202 (Accepted)</dfn> status code indicates that the request has been accepted for processing, but the processing
     
    34633475            </div>
    34643476            <div id="status.203">
    3465                <h3 id="rfc.section.6.3.4"><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></h3>
     3477               <h4 id="rfc.section.6.3.4"><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></h4>
    34663478               <div id="rfc.section.6.3.4.p.1">
    34673479                  <p>The <dfn>203 (Non-Authoritative Information)</dfn> status code indicates that the request was successful but the enclosed payload has
     
    34833495            </div>
    34843496            <div id="status.204">
    3485                <h3 id="rfc.section.6.3.5"><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;<a href="#status.204">204 No Content</a></h3>
     3497               <h4 id="rfc.section.6.3.5"><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;<a href="#status.204">204 No Content</a></h4>
    34863498               <div id="rfc.section.6.3.5.p.1">
    34873499                  <p>The <dfn>204 (No Content)</dfn> status code indicates that the server has successfully fulfilled the request and that
     
    35243536            </div>
    35253537            <div id="status.205">
    3526                <h3 id="rfc.section.6.3.6"><a href="#rfc.section.6.3.6">6.3.6</a>&nbsp;<a href="#status.205">205 Reset Content</a></h3>
     3538               <h4 id="rfc.section.6.3.6"><a href="#rfc.section.6.3.6">6.3.6</a>&nbsp;<a href="#status.205">205 Reset Content</a></h4>
    35273539               <div id="rfc.section.6.3.6.p.1">
    35283540                  <p>The <dfn>205 (Reset Content)</dfn> status code indicates that the server has fulfilled the request and desires that the
     
    35503562         </div>
    35513563         <div id="status.3xx">
    3552             <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a href="#status.3xx">Redirection 3xx</a></h2>
     3564            <h3 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a href="#status.3xx">Redirection 3xx</a></h3>
    35533565            <div id="rfc.section.6.4.p.1">
    35543566               <p>The <dfn>3xx (Redirection)</dfn> class of status code indicates that further action needs to be taken by the user agent
     
    36053617            </div>
    36063618            <div id="status.300">
    3607                <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;<a href="#status.300">300 Multiple Choices</a></h3>
     3619               <h4 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;<a href="#status.300">300 Multiple Choices</a></h4>
    36083620               <div id="rfc.section.6.4.1.p.1">
    36093621                  <p>The <dfn>300 (Multiple Choices)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> has more than one representation, each with its own more specific identifier, and
     
    36493661            </div>
    36503662            <div id="status.301">
    3651                <h3 id="rfc.section.6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a>&nbsp;<a href="#status.301">301 Moved Permanently</a></h3>
     3663               <h4 id="rfc.section.6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a>&nbsp;<a href="#status.301">301 Moved Permanently</a></h4>
    36523664               <div id="rfc.section.6.4.2.p.1">
    36533665                  <p>The <dfn>301 (Moved Permanently)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> has been assigned a new permanent URI and any future references to this resource ought
     
    36773689            </div>
    36783690            <div id="status.302">
    3679                <h3 id="rfc.section.6.4.3"><a href="#rfc.section.6.4.3">6.4.3</a>&nbsp;<a href="#status.302">302 Found</a></h3>
     3691               <h4 id="rfc.section.6.4.3"><a href="#rfc.section.6.4.3">6.4.3</a>&nbsp;<a href="#status.302">302 Found</a></h4>
    36803692               <div id="rfc.section.6.4.3.p.1">
    36813693                  <p>The <dfn>302 (Found)</dfn> status code indicates that the target resource resides temporarily under a different
     
    36993711            </div>
    37003712            <div id="status.303">
    3701                <h3 id="rfc.section.6.4.4"><a href="#rfc.section.6.4.4">6.4.4</a>&nbsp;<a href="#status.303">303 See Other</a></h3>
     3713               <h4 id="rfc.section.6.4.4"><a href="#rfc.section.6.4.4">6.4.4</a>&nbsp;<a href="#status.303">303 See Other</a></h4>
    37023714               <div id="rfc.section.6.4.4.p.1">
    37033715                  <p>The <dfn>303 (See Other)</dfn> status code indicates that the server is redirecting the user agent to a different
     
    37333745            </div>
    37343746            <div id="status.305">
    3735                <h3 id="rfc.section.6.4.5"><a href="#rfc.section.6.4.5">6.4.5</a>&nbsp;<a href="#status.305">305 Use Proxy</a></h3>
     3747               <h4 id="rfc.section.6.4.5"><a href="#rfc.section.6.4.5">6.4.5</a>&nbsp;<a href="#status.305">305 Use Proxy</a></h4>
    37363748               <div id="rfc.section.6.4.5.p.1">
    37373749                  <p>The <dfn>305 (Use Proxy)</dfn> status code was defined in a previous version of this specification and is now deprecated
     
    37413753            </div>
    37423754            <div id="status.306">
    3743                <h3 id="rfc.section.6.4.6"><a href="#rfc.section.6.4.6">6.4.6</a>&nbsp;<a href="#status.306">306 (Unused)</a></h3>
     3755               <h4 id="rfc.section.6.4.6"><a href="#rfc.section.6.4.6">6.4.6</a>&nbsp;<a href="#status.306">306 (Unused)</a></h4>
    37443756               <div id="rfc.section.6.4.6.p.1">
    37453757                  <p>The 306 status code was defined in a previous version of this specification, is no
     
    37493761            </div>
    37503762            <div id="status.307">
    3751                <h3 id="rfc.section.6.4.7"><a href="#rfc.section.6.4.7">6.4.7</a>&nbsp;<a href="#status.307">307 Temporary Redirect</a></h3>
     3763               <h4 id="rfc.section.6.4.7"><a href="#rfc.section.6.4.7">6.4.7</a>&nbsp;<a href="#status.307">307 Temporary Redirect</a></h4>
    37523764               <div id="rfc.section.6.4.7.p.1">
    37533765                  <p>The <dfn>307 (Temporary Redirect)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> resides temporarily under a different URI and the user agent <em class="bcp14">MUST NOT</em> change the request method if it performs an automatic redirection to that URI. Since
     
    37733785         </div>
    37743786         <div id="status.4xx">
    3775             <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a href="#status.4xx">Client Error 4xx</a></h2>
     3787            <h3 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a href="#status.4xx">Client Error 4xx</a></h3>
    37763788            <div id="rfc.section.6.5.p.1">
    37773789               <p>The <dfn>4xx (Client Error)</dfn> class of status code indicates that the client seems to have erred. Except when responding
     
    37823794            </div>
    37833795            <div id="status.400">
    3784                <h3 id="rfc.section.6.5.1"><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;<a href="#status.400">400 Bad Request</a></h3>
     3796               <h4 id="rfc.section.6.5.1"><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;<a href="#status.400">400 Bad Request</a></h4>
    37853797               <div id="rfc.section.6.5.1.p.1">
    37863798                  <p>The <dfn>400 (Bad Request)</dfn> status code indicates that the server cannot or will not process the request due to
     
    37913803            </div>
    37923804            <div id="status.402">
    3793                <h3 id="rfc.section.6.5.2"><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;<a href="#status.402">402 Payment Required</a></h3>
     3805               <h4 id="rfc.section.6.5.2"><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;<a href="#status.402">402 Payment Required</a></h4>
    37943806               <div id="rfc.section.6.5.2.p.1">
    37953807                  <p>The <dfn>402 (Payment Required)</dfn> status code is reserved for future use.
     
    37983810            </div>
    37993811            <div id="status.403">
    3800                <h3 id="rfc.section.6.5.3"><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;<a href="#status.403">403 Forbidden</a></h3>
     3812               <h4 id="rfc.section.6.5.3"><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;<a href="#status.403">403 Forbidden</a></h4>
    38013813               <div id="rfc.section.6.5.3.p.1">
    38023814                  <p>The <dfn>403 (Forbidden)</dfn> status code indicates that the server understood the request but refuses to authorize
     
    38173829            </div>
    38183830            <div id="status.404">
    3819                <h3 id="rfc.section.6.5.4"><a href="#rfc.section.6.5.4">6.5.4</a>&nbsp;<a href="#status.404">404 Not Found</a></h3>
     3831               <h4 id="rfc.section.6.5.4"><a href="#rfc.section.6.5.4">6.5.4</a>&nbsp;<a href="#status.404">404 Not Found</a></h4>
    38203832               <div id="rfc.section.6.5.4.p.1">
    38213833                  <p>The <dfn>404 (Not Found)</dfn> status code indicates that the origin server did not find a current representation
     
    38323844            </div>
    38333845            <div id="status.405">
    3834                <h3 id="rfc.section.6.5.5"><a href="#rfc.section.6.5.5">6.5.5</a>&nbsp;<a href="#status.405">405 Method Not Allowed</a></h3>
     3846               <h4 id="rfc.section.6.5.5"><a href="#rfc.section.6.5.5">6.5.5</a>&nbsp;<a href="#status.405">405 Method Not Allowed</a></h4>
    38353847               <div id="rfc.section.6.5.5.p.1">
    38363848                  <p>The <dfn>405 (Method Not Allowed)</dfn> status code indicates that the method received in the request-line is known by the
     
    38463858            </div>
    38473859            <div id="status.406">
    3848                <h3 id="rfc.section.6.5.6"><a href="#rfc.section.6.5.6">6.5.6</a>&nbsp;<a href="#status.406">406 Not Acceptable</a></h3>
     3860               <h4 id="rfc.section.6.5.6"><a href="#rfc.section.6.5.6">6.5.6</a>&nbsp;<a href="#status.406">406 Not Acceptable</a></h4>
    38493861               <div id="rfc.section.6.5.6.p.1">
    38503862                  <p>The <dfn>406 (Not Acceptable)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> does not have a current representation that would be acceptable to the user agent,
     
    38613873            </div>
    38623874            <div id="status.408">
    3863                <h3 id="rfc.section.6.5.7"><a href="#rfc.section.6.5.7">6.5.7</a>&nbsp;<a href="#status.408">408 Request Timeout</a></h3>
     3875               <h4 id="rfc.section.6.5.7"><a href="#rfc.section.6.5.7">6.5.7</a>&nbsp;<a href="#status.408">408 Request Timeout</a></h4>
    38643876               <div id="rfc.section.6.5.7.p.1">
    38653877                  <p>The <dfn>408 (Request Timeout)</dfn> status code indicates that the server did not receive a complete request message within
     
    38713883            </div>
    38723884            <div id="status.409">
    3873                <h3 id="rfc.section.6.5.8"><a href="#rfc.section.6.5.8">6.5.8</a>&nbsp;<a href="#status.409">409 Conflict</a></h3>
     3885               <h4 id="rfc.section.6.5.8"><a href="#rfc.section.6.5.8">6.5.8</a>&nbsp;<a href="#status.409">409 Conflict</a></h4>
    38743886               <div id="rfc.section.6.5.8.p.1">
    38753887                  <p>The <dfn>409 (Conflict)</dfn> status code indicates that the request could not be completed due to a conflict with
     
    38903902            </div>
    38913903            <div id="status.410">
    3892                <h3 id="rfc.section.6.5.9"><a href="#rfc.section.6.5.9">6.5.9</a>&nbsp;<a href="#status.410">410 Gone</a></h3>
     3904               <h4 id="rfc.section.6.5.9"><a href="#rfc.section.6.5.9">6.5.9</a>&nbsp;<a href="#status.410">410 Gone</a></h4>
    38933905               <div id="rfc.section.6.5.9.p.1">
    38943906                  <p>The <dfn>410 (Gone)</dfn> status code indicates that access to the <a href="#resources" class="smpl">target resource</a> is no longer available at the origin server and that this condition is likely to be
     
    39143926            </div>
    39153927            <div id="status.411">
    3916                <h3 id="rfc.section.6.5.10"><a href="#rfc.section.6.5.10">6.5.10</a>&nbsp;<a href="#status.411">411 Length Required</a></h3>
     3928               <h4 id="rfc.section.6.5.10"><a href="#rfc.section.6.5.10">6.5.10</a>&nbsp;<a href="#status.411">411 Length Required</a></h4>
    39173929               <div id="rfc.section.6.5.10.p.1">
    39183930                  <p>The <dfn>411 (Length Required)</dfn> status code indicates that the server refuses to accept the request without a defined <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> (<a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>). The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length
     
    39223934            </div>
    39233935            <div id="status.413">
    3924                <h3 id="rfc.section.6.5.11"><a href="#rfc.section.6.5.11">6.5.11</a>&nbsp;<a href="#status.413">413 Payload Too Large</a></h3>
     3936               <h4 id="rfc.section.6.5.11"><a href="#rfc.section.6.5.11">6.5.11</a>&nbsp;<a href="#status.413">413 Payload Too Large</a></h4>
    39253937               <div id="rfc.section.6.5.11.p.1">
    39263938                  <p>The <dfn>413 (Payload Too Large)</dfn> status code indicates that the server is refusing to process a request because the
     
    39343946            </div>
    39353947            <div id="status.414">
    3936                <h3 id="rfc.section.6.5.12"><a href="#rfc.section.6.5.12">6.5.12</a>&nbsp;<a href="#status.414">414 URI Too Long</a></h3>
     3948               <h4 id="rfc.section.6.5.12"><a href="#rfc.section.6.5.12">6.5.12</a>&nbsp;<a href="#status.414">414 URI Too Long</a></h4>
    39373949               <div id="rfc.section.6.5.12.p.1">
    39383950                  <p>The <dfn>414 (URI Too Long)</dfn> status code indicates that the server is refusing to service the request because the
     
    39513963            </div>
    39523964            <div id="status.415">
    3953                <h3 id="rfc.section.6.5.13"><a href="#rfc.section.6.5.13">6.5.13</a>&nbsp;<a href="#status.415">415 Unsupported Media Type</a></h3>
     3965               <h4 id="rfc.section.6.5.13"><a href="#rfc.section.6.5.13">6.5.13</a>&nbsp;<a href="#status.415">415 Unsupported Media Type</a></h4>
    39543966               <div id="rfc.section.6.5.13.p.1">
    39553967                  <p>The <dfn>415 (Unsupported Media Type)</dfn> status code indicates that the origin server is refusing to service the request because
     
    39593971            </div>
    39603972            <div id="status.417">
    3961                <h3 id="rfc.section.6.5.14"><a href="#rfc.section.6.5.14">6.5.14</a>&nbsp;<a href="#status.417">417 Expectation Failed</a></h3>
     3973               <h4 id="rfc.section.6.5.14"><a href="#rfc.section.6.5.14">6.5.14</a>&nbsp;<a href="#status.417">417 Expectation Failed</a></h4>
    39623974               <div id="rfc.section.6.5.14.p.1">
    39633975                  <p>The <dfn>417 (Expectation Failed)</dfn> status code indicates that the expectation given in the request's <a href="#header.expect" class="smpl">Expect</a> header field (<a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;5.1.1</a>) could not be met by at least one of the inbound servers.
     
    39663978            </div>
    39673979            <div id="status.426">
    3968                <h3 id="rfc.section.6.5.15"><a href="#rfc.section.6.5.15">6.5.15</a>&nbsp;<a href="#status.426">426 Upgrade Required</a></h3>
     3980               <h4 id="rfc.section.6.5.15"><a href="#rfc.section.6.5.15">6.5.15</a>&nbsp;<a href="#status.426">426 Upgrade Required</a></h4>
    39693981               <div id="rfc.section.6.5.15.p.1">
    39703982                  <p>The <dfn>426 (Upgrade Required)</dfn> status code indicates that the server refuses to perform the request using the current
     
    39853997         </div>
    39863998         <div id="status.5xx">
    3987             <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a href="#status.5xx">Server Error 5xx</a></h2>
     3999            <h3 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a href="#status.5xx">Server Error 5xx</a></h3>
    39884000            <div id="rfc.section.6.6.p.1">
    39894001               <p>The <dfn>5xx (Server Error)</dfn> class of status code indicates that the server is aware that it has erred or is incapable
     
    39954007            </div>
    39964008            <div id="status.500">
    3997                <h3 id="rfc.section.6.6.1"><a href="#rfc.section.6.6.1">6.6.1</a>&nbsp;<a href="#status.500">500 Internal Server Error</a></h3>
     4009               <h4 id="rfc.section.6.6.1"><a href="#rfc.section.6.6.1">6.6.1</a>&nbsp;<a href="#status.500">500 Internal Server Error</a></h4>
    39984010               <div id="rfc.section.6.6.1.p.1">
    39994011                  <p>The <dfn>500 (Internal Server Error)</dfn> status code indicates that the server encountered an unexpected condition that prevented
     
    40034015            </div>
    40044016            <div id="status.501">
    4005                <h3 id="rfc.section.6.6.2"><a href="#rfc.section.6.6.2">6.6.2</a>&nbsp;<a href="#status.501">501 Not Implemented</a></h3>
     4017               <h4 id="rfc.section.6.6.2"><a href="#rfc.section.6.6.2">6.6.2</a>&nbsp;<a href="#status.501">501 Not Implemented</a></h4>
    40064018               <div id="rfc.section.6.6.2.p.1">
    40074019                  <p>The <dfn>501 (Not Implemented)</dfn> status code indicates that the server does not support the functionality required
     
    40174029            </div>
    40184030            <div id="status.502">
    4019                <h3 id="rfc.section.6.6.3"><a href="#rfc.section.6.6.3">6.6.3</a>&nbsp;<a href="#status.502">502 Bad Gateway</a></h3>
     4031               <h4 id="rfc.section.6.6.3"><a href="#rfc.section.6.6.3">6.6.3</a>&nbsp;<a href="#status.502">502 Bad Gateway</a></h4>
    40204032               <div id="rfc.section.6.6.3.p.1">
    40214033                  <p>The <dfn>502 (Bad Gateway)</dfn> status code indicates that the server, while acting as a gateway or proxy, received
     
    40264038            </div>
    40274039            <div id="status.503">
    4028                <h3 id="rfc.section.6.6.4"><a href="#rfc.section.6.6.4">6.6.4</a>&nbsp;<a href="#status.503">503 Service Unavailable</a></h3>
     4040               <h4 id="rfc.section.6.6.4"><a href="#rfc.section.6.6.4">6.6.4</a>&nbsp;<a href="#status.503">503 Service Unavailable</a></h4>
    40294041               <div id="rfc.section.6.6.4.p.1">
    40304042                  <p>The <dfn>503 (Service Unavailable)</dfn> status code indicates that the server is currently unable to handle the request due
     
    40434055            </div>
    40444056            <div id="status.504">
    4045                <h3 id="rfc.section.6.6.5"><a href="#rfc.section.6.6.5">6.6.5</a>&nbsp;<a href="#status.504">504 Gateway Timeout</a></h3>
     4057               <h4 id="rfc.section.6.6.5"><a href="#rfc.section.6.6.5">6.6.5</a>&nbsp;<a href="#status.504">504 Gateway Timeout</a></h4>
    40464058               <div id="rfc.section.6.6.5.p.1">
    40474059                  <p>The <dfn>504 (Gateway Timeout)</dfn> status code indicates that the server, while acting as a gateway or proxy, did not
     
    40524064            </div>
    40534065            <div id="status.505">
    4054                <h3 id="rfc.section.6.6.6"><a href="#rfc.section.6.6.6">6.6.6</a>&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></h3>
     4066               <h4 id="rfc.section.6.6.6"><a href="#rfc.section.6.6.6">6.6.6</a>&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></h4>
    40554067               <div id="rfc.section.6.6.6.p.1">
    40564068                  <p>The <dfn>505 (HTTP Version Not Supported)</dfn> status code indicates that the server does not support, or refuses to support, the
     
    40654077      </div>
    40664078      <div id="response.header.fields">
    4067          <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#response.header.fields">Response Header Fields</a></h1>
     4079         <h2 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#response.header.fields">Response Header Fields</a></h2>
    40684080         <div id="rfc.section.7.p.1">
    40694081            <p>The response header fields allow the server to pass additional information about the
     
    40794091         </div>
    40804092         <div id="response.control.data">
    4081             <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#response.control.data">Control Data</a></h2>
     4093            <h3 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#response.control.data">Control Data</a></h3>
    40824094            <div id="rfc.section.7.1.p.1">
    40834095               <p>Response header fields can supply control data that supplements the status code, directs
     
    40864098            </div>
    40874099            <div id="rfc.table.u.10">
    4088                <table class="tt full left" cellpadding="3" cellspacing="0">
     4100               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    40894101                  <thead>
    40904102                     <tr>
     
    41304142            </div>
    41314143            <div id="origination.date">
    4132                <h3 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;<a href="#origination.date">Origination Date</a></h3>
     4144               <h4 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;<a href="#origination.date">Origination Date</a></h4>
    41334145               <div id="http.date">
    4134                   <h4 id="rfc.section.7.1.1.1"><a href="#rfc.section.7.1.1.1">7.1.1.1</a>&nbsp;<a href="#http.date">Date/Time Formats</a></h4>
     4146                  <h5 id="rfc.section.7.1.1.1"><a href="#rfc.section.7.1.1.1">7.1.1.1</a>&nbsp;<a href="#http.date">Date/Time Formats</a></h5>
    41354147                  <div id="rfc.section.7.1.1.1.p.1">
    41364148                     <p>Prior to 1995, there were three different formats commonly used by servers to communicate
     
    42574269               </div>
    42584270               <div id="header.date">
    4259                   <h4 id="rfc.section.7.1.1.2"><a href="#rfc.section.7.1.1.2">7.1.1.2</a>&nbsp;<a href="#header.date">Date</a></h4>
     4271                  <h5 id="rfc.section.7.1.1.2"><a href="#rfc.section.7.1.1.2">7.1.1.2</a>&nbsp;<a href="#header.date">Date</a></h5>
    42604272                  <div id="rfc.section.7.1.1.2.p.1">
    42614273                     <p>The "Date" header field represents the date and time at which the message was originated,
     
    42974309            </div>
    42984310            <div id="header.location">
    4299                <h3 id="rfc.section.7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;<a href="#header.location">Location</a></h3>
     4311               <h4 id="rfc.section.7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;<a href="#header.location">Location</a></h4>
    43004312               <div id="rfc.section.7.1.2.p.1">
    43014313                  <p>The "Location" header field is used in some responses to refer to a specific resource
     
    43604372            </div>
    43614373            <div id="header.retry-after">
    4362                <h3 id="rfc.section.7.1.3"><a href="#rfc.section.7.1.3">7.1.3</a>&nbsp;<a href="#header.retry-after">Retry-After</a></h3>
     4374               <h4 id="rfc.section.7.1.3"><a href="#rfc.section.7.1.3">7.1.3</a>&nbsp;<a href="#header.retry-after">Retry-After</a></h4>
    43634375               <div id="rfc.section.7.1.3.p.1">
    43644376                  <p>Servers send the "Retry-After" header field to indicate how long the user agent ought
     
    43934405            </div>
    43944406            <div id="header.vary">
    4395                <h3 id="rfc.section.7.1.4"><a href="#rfc.section.7.1.4">7.1.4</a>&nbsp;<a href="#header.vary">Vary</a></h3>
     4407               <h4 id="rfc.section.7.1.4"><a href="#rfc.section.7.1.4">7.1.4</a>&nbsp;<a href="#header.vary">Vary</a></h4>
    43964408               <div id="rfc.section.7.1.4.p.1">
    43974409                  <p>The "Vary" header field in a response describes what parts of a request message, aside
     
    44544466         </div>
    44554467         <div id="response.validator">
    4456             <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#response.validator">Validator Header Fields</a></h2>
     4468            <h3 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#response.validator">Validator Header Fields</a></h3>
    44574469            <div id="rfc.section.7.2.p.1">
    44584470               <p>Validator header fields convey metadata about the <a href="#representations" class="smpl">selected representation</a> (<a href="#representations" title="Representations">Section&nbsp;3</a>). In responses to safe requests, validator fields describe the selected representation
     
    44744486            </div>
    44754487            <div id="rfc.table.u.11">
    4476                <table class="tt full left" cellpadding="3" cellspacing="0">
     4488               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    44774489                  <thead>
    44784490                     <tr>
     
    44954507         </div>
    44964508         <div id="response.auth">
    4497             <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a href="#response.auth">Authentication Challenges</a></h2>
     4509            <h3 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a href="#response.auth">Authentication Challenges</a></h3>
    44984510            <div id="rfc.section.7.3.p.1">
    44994511               <p>Authentication challenges indicate what mechanisms are available for the client to
     
    45024514            </div>
    45034515            <div id="rfc.table.u.12">
    4504                <table class="tt full left" cellpadding="3" cellspacing="0">
     4516               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    45054517                  <thead>
    45064518                     <tr>
     
    45234535         </div>
    45244536         <div id="response.context">
    4525             <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a href="#response.context">Response Context</a></h2>
     4537            <h3 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a href="#response.context">Response Context</a></h3>
    45264538            <div id="rfc.section.7.4.p.1">
    45274539               <p>The remaining response header fields provide more information about the <a href="#resources" class="smpl">target resource</a> for potential use in later requests.
     
    45294541            </div>
    45304542            <div id="rfc.table.u.13">
    4531                <table class="tt full left" cellpadding="3" cellspacing="0">
     4543               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    45324544                  <thead>
    45334545                     <tr>
     
    45534565            </div>
    45544566            <div id="header.allow">
    4555                <h3 id="rfc.section.7.4.1"><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;<a href="#header.allow">Allow</a></h3>
     4567               <h4 id="rfc.section.7.4.1"><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;<a href="#header.allow">Allow</a></h4>
    45564568               <div id="rfc.section.7.4.1.p.1">
    45574569                  <p>The "Allow" header field lists the set of methods advertised as supported by the <a href="#resources" class="smpl">target resource</a>. The purpose of this field is strictly to inform the recipient of valid request methods
     
    45614573               <div id="rfc.figure.u.60"><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#method.overview" class="smpl">method</a>
    45624574</pre></div>
    4563                <div id="rfc.section.7.4.1.p.2">
     4575               <div id="rfc.section.7.4.1.p.2" class="avoidbreakafter">
    45644576                  <p>Example of use:</p>
    45654577               </div>
     
    45804592            </div>
    45814593            <div id="header.server">
    4582                <h3 id="rfc.section.7.4.2"><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;<a href="#header.server">Server</a></h3>
     4594               <h4 id="rfc.section.7.4.2"><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;<a href="#header.server">Server</a></h4>
    45834595               <div id="rfc.section.7.4.2.p.1">
    45844596                  <p>The "Server" header field contains information about the software used by the origin
     
    45994611                  </p>
    46004612               </div>
    4601                <div id="rfc.section.7.4.2.p.3">
     4613               <div id="rfc.section.7.4.2.p.3" class="avoidbreakafter">
    46024614                  <p>Example:</p>
    46034615               </div>
     
    46154627      </div>
    46164628      <div id="IANA.considerations">
    4617          <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     4629         <h2 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h2>
    46184630         <div id="method.registry">
    4619             <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a href="#method.registry">Method Registry</a></h2>
     4631            <h3 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a href="#method.registry">Method Registry</a></h3>
    46204632            <div id="rfc.section.8.1.p.1">
    46214633               <p>The "Hypertext Transfer Protocol (HTTP) Method Registry" defines the namespace for
     
    46244636            </div>
    46254637            <div id="method.registry.procedure">
    4626                <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a href="#method.registry.procedure">Procedure</a></h3>
     4638               <h4 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a href="#method.registry.procedure">Procedure</a></h4>
    46274639               <div id="rfc.section.8.1.1.p.1">
    46284640                  <p>HTTP method registrations <em class="bcp14">MUST</em> include the following fields:
     
    46444656            </div>
    46454657            <div id="considerations.for.new.methods">
    4646                <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
     4658               <h4 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></h4>
    46474659               <div id="rfc.section.8.1.2.p.1">
    46484660                  <p>Standardized methods are generic; that is, they are potentially applicable to any
     
    46794691            </div>
    46804692            <div id="method.registration">
    4681                <h3 id="rfc.section.8.1.3"><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;<a href="#method.registration">Registrations</a></h3>
    4682                <div id="rfc.section.8.1.3.p.1">
     4693               <h4 id="rfc.section.8.1.3"><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;<a href="#method.registration">Registrations</a></h4>
     4694               <div id="rfc.section.8.1.3.p.1" class="avoidbreakafter">
    46834695                  <p>The "Hypertext Transfer Protocol (HTTP) Method Registry" has been populated with the
    46844696                     registrations below:
     
    46874699               <div id="rfc.table.2">
    46884700                  <div id="iana.method.registration.table"></div>
    4689                   <table class="tt full left" cellpadding="3" cellspacing="0">
     4701                  <table class="tt full tleft" cellpadding="3" cellspacing="0">
    46904702                     <thead>
    46914703                        <tr>
     
    47594771         </div>
    47604772         <div id="status.code.registry">
    4761             <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a href="#status.code.registry">Status Code Registry</a></h2>
     4773            <h3 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a href="#status.code.registry">Status Code Registry</a></h3>
    47624774            <div id="rfc.section.8.2.p.1">
    47634775               <p>The "Hypertext Transfer Protocol (HTTP) Status Code Registry" defines the namespace
     
    47714783            </div>
    47724784            <div id="status.code.registry.procedure">
    4773                <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a href="#status.code.registry.procedure">Procedure</a></h3>
     4785               <h4 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a href="#status.code.registry.procedure">Procedure</a></h4>
    47744786               <div id="rfc.section.8.2.1.p.1">
    47754787                  <p>A registration <em class="bcp14">MUST</em> include the following fields:
     
    47874799            </div>
    47884800            <div id="considerations.for.new.status.codes">
    4789                <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h3>
     4801               <h4 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h4>
    47904802               <div id="rfc.section.8.2.2.p.1">
    47914803                  <p>When it is necessary to express semantics for a response that are not defined by current
     
    48314843            </div>
    48324844            <div id="status.code.registration">
    4833                <h3 id="rfc.section.8.2.3"><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;<a href="#status.code.registration">Registrations</a></h3>
    4834                <div id="rfc.section.8.2.3.p.1">
     4845               <h4 id="rfc.section.8.2.3"><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;<a href="#status.code.registration">Registrations</a></h4>
     4846               <div id="rfc.section.8.2.3.p.1" class="avoidbreakafter">
    48354847                  <p>The status code registry has been updated with the registrations below:</p>
    48364848               </div>
    48374849               <div id="rfc.table.3">
    48384850                  <div id="iana.status.code.registration.table"></div>
    4839                   <table class="tt full left" cellpadding="3" cellspacing="0">
     4851                  <table class="tt full tleft" cellpadding="3" cellspacing="0">
    48404852                     <thead>
    48414853                        <tr>
     
    50685080         </div>
    50695081         <div id="header.field.registry">
    5070             <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a href="#header.field.registry">Header Field Registry</a></h2>
     5082            <h3 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a href="#header.field.registry">Header Field Registry</a></h3>
    50715083            <div id="rfc.section.8.3.p.1">
    50725084               <p>HTTP header fields are registered within the "Message Headers" registry located at &lt;<a href="http://www.iana.org/assignments/message-headers">http://www.iana.org/assignments/message-headers</a>&gt;, as defined by <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>.
     
    50745086            </div>
    50755087            <div id="considerations.for.new.header.fields">
    5076                <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></h3>
     5088               <h4 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a href="#considerations.for.new.header.fields">Considerations for New Header Fields</a></h4>
    50775089               <div id="rfc.section.8.3.1.p.1">
    50785090                  <p>Header fields are key:value pairs that can be used to communicate data about the message,
     
    51125124                  </p>
    51135125               </div>
    5114                <div id="rfc.section.8.3.1.p.7">
     5126               <div id="rfc.section.8.3.1.p.7" class="avoidbreakafter">
    51155127                  <p>For example, a textual date and a URI (either of which might contain a comma) could
    51165128                     be safely carried in field-values like these:
     
    51975209            </div>
    51985210            <div id="header.field.registration">
    5199                <h3 id="rfc.section.8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;<a href="#header.field.registration">Registrations</a></h3>
    5200                <div id="rfc.section.8.3.2.p.1">
     5211               <h4 id="rfc.section.8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;<a href="#header.field.registration">Registrations</a></h4>
     5212               <div id="rfc.section.8.3.2.p.1" class="avoidbreakafter">
    52015213                  <p>The "Message Headers" registry has been updated with the following permanent registrations:</p>
    52025214               </div>
    52035215               <div id="rfc.table.4">
    52045216                  <div id="iana.header.registration.table"></div>
    5205                   <table class="tt full left" cellpadding="3" cellspacing="0">
     5217                  <table class="tt full tleft" cellpadding="3" cellspacing="0">
    52065218                     <thead>
    52075219                        <tr>
     
    53645376         </div>
    53655377         <div id="content.coding.registry">
    5366             <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></h2>
     5378            <h3 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a href="#content.coding.registry">Content Coding Registry</a></h3>
    53675379            <div id="rfc.section.8.4.p.1">
    53685380               <p>The "HTTP Content Coding Registry" defines the namespace for content coding names
     
    53715383            </div>
    53725384            <div id="content.coding.procedure">
    5373                <h3 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a href="#content.coding.procedure">Procedure</a></h3>
     5385               <h4 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a href="#content.coding.procedure">Procedure</a></h4>
    53745386               <div id="rfc.section.8.4.1.p.1">
    53755387                  <p>Content coding registrations <em class="bcp14">MUST</em> include the following fields:
     
    53925404            </div>
    53935405            <div id="content.coding.registration">
    5394                <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a href="#content.coding.registration">Registrations</a></h3>
    5395                <div id="rfc.section.8.4.2.p.1">
     5406               <h4 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a href="#content.coding.registration">Registrations</a></h4>
     5407               <div id="rfc.section.8.4.2.p.1" class="avoidbreakafter">
    53965408                  <p>The "HTTP Content Coding Registry" has been updated with the registrations below:</p>
    53975409               </div>
    53985410               <div id="rfc.table.5">
    53995411                  <div id="iana.content.coding.registration.table"></div>
    5400                   <table class="tt full left" cellpadding="3" cellspacing="0">
     5412                  <table class="tt full tleft" cellpadding="3" cellspacing="0">
    54015413                     <thead>
    54025414                        <tr>
     
    54215433      </div>
    54225434      <div id="security.considerations">
    5423          <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     5435         <h2 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h2>
    54245436         <div id="rfc.section.9.p.1">
    54255437            <p>This section is meant to inform developers, information providers, and users of known
     
    54395451         </div>
    54405452         <div id="attack.pathname">
    5441             <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a href="#attack.pathname">Attacks Based on File and Path Names</a></h2>
     5453            <h3 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a href="#attack.pathname">Attacks Based on File and Path Names</a></h3>
    54425454            <div id="rfc.section.9.1.p.1">
    54435455               <p>Origin servers frequently make use of their local file system to manage the mapping
     
    54665478         </div>
    54675479         <div id="attack.injection">
    5468             <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a href="#attack.injection">Attacks Based on Command, Code, or Query Injection</a></h2>
     5480            <h3 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a href="#attack.injection">Attacks Based on Command, Code, or Query Injection</a></h3>
    54695481            <div id="rfc.section.9.2.p.1">
    54705482               <p>Origin servers often use parameters within the URI as a means of identifying system
     
    55015513         </div>
    55025514         <div id="personal.information">
    5503             <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a href="#personal.information">Disclosure of Personal Information</a></h2>
     5515            <h3 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a href="#personal.information">Disclosure of Personal Information</a></h3>
    55045516            <div id="rfc.section.9.3.p.1">
    55055517               <p>Clients are often privy to large amounts of personal information, including both information
     
    55125524         </div>
    55135525         <div id="sensitive.information.in.uris">
    5514             <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a href="#sensitive.information.in.uris">Disclosure of Sensitive Information in URIs</a></h2>
     5526            <h3 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a href="#sensitive.information.in.uris">Disclosure of Sensitive Information in URIs</a></h3>
    55155527            <div id="rfc.section.9.4.p.1">
    55165528               <p>URIs are intended to be shared, not secured, even when they identify secure resources.
     
    55375549         </div>
    55385550         <div id="fragment.disclosure">
    5539             <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a href="#fragment.disclosure">Disclosure of Fragment after Redirects</a></h2>
     5551            <h3 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a href="#fragment.disclosure">Disclosure of Fragment after Redirects</a></h3>
    55405552            <div id="rfc.section.9.5.p.1">
    55415553               <p>Although fragment identifiers used within URI references are not sent in requests,
     
    55515563         </div>
    55525564         <div id="disclosure.product.information">
    5553             <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a href="#disclosure.product.information">Disclosure of Product Information</a></h2>
     5565            <h3 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a href="#disclosure.product.information">Disclosure of Product Information</a></h3>
    55545566            <div id="rfc.section.9.6.p.1">
    55555567               <p>The <a href="#header.user-agent" class="smpl">User-Agent</a> (<a href="#header.user-agent" id="rfc.xref.header.user-agent.4" title="User-Agent">Section&nbsp;5.5.3</a>), <a href="p1-messaging.html#header.via" class="smpl">Via</a> (<a href="p1-messaging.html#header.via" title="Via">Section 5.7.1</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.44"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>), and <a href="#header.server" class="smpl">Server</a> (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;7.4.2</a>) header fields often reveal information about the respective sender's software systems.
     
    55675579         </div>
    55685580         <div id="fingerprinting">
    5569             <h2 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a href="#fingerprinting">Browser Fingerprinting</a></h2>
     5581            <h3 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a href="#fingerprinting">Browser Fingerprinting</a></h3>
    55705582            <div id="rfc.section.9.7.p.1">
    55715583               <p>Browser fingerprinting is a set of techniques for identifying a specific user agent
     
    56155627      </div>
    56165628      <div id="acks">
    5617          <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
     5629         <h2 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a href="#acks">Acknowledgments</a></h2>
    56185630         <div id="rfc.section.10.p.1">
    56195631            <p>See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.45"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     
    56215633         </div>
    56225634      </div>
    5623       <h1 id="rfc.references"><a id="rfc.section.11" href="#rfc.section.11">11.</a> References
    5624       </h1>
    5625       <h2 id="rfc.references.1"><a href="#rfc.section.11.1" id="rfc.section.11.1">11.1</a> Normative References
     5635      <h2 id="rfc.references"><a id="rfc.section.11" href="#rfc.section.11">11.</a> References
    56265636      </h2>
    5627       <table>
    5628          <tr>
    5629             <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
    5630             <td class="top">Freed, N. and N. Borenstein, “<a href="https://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message
    5631                   Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
    5632             </td>
    5633          </tr>
    5634          <tr>
    5635             <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    5636             <td class="top">Freed, N. and N. Borenstein, “<a href="https://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
    5637             </td>
    5638          </tr>
    5639          <tr>
    5640             <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    5641             <td class="top">Bradner, S., “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
    5642             </td>
    5643          </tr>
    5644          <tr>
    5645             <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
    5646             <td class="top">Berners-Lee, T., Fielding, R., and L. Masinter, “<a href="https://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
    5647             </td>
    5648          </tr>
    5649          <tr>
    5650             <td class="reference"><b id="RFC4647">[RFC4647]</b></td>
    5651             <td class="top">Phillips, A., Ed. and M. Davis, Ed., “<a href="https://tools.ietf.org/html/rfc4647">Matching of Language Tags</a>”, BCP&nbsp;47, RFC&nbsp;4647, September&nbsp;2006.
    5652             </td>
    5653          </tr>
    5654          <tr>
    5655             <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    5656             <td class="top">Crocker, D., Ed. and P. Overell, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
    5657             </td>
    5658          </tr>
    5659          <tr>
    5660             <td class="reference"><b id="RFC5646">[RFC5646]</b></td>
    5661             <td class="top">Phillips, A., Ed. and M. Davis, Ed., “<a href="https://tools.ietf.org/html/rfc5646">Tags for Identifying Languages</a>”, BCP&nbsp;47, RFC&nbsp;5646, September&nbsp;2009.
    5662             </td>
    5663          </tr>
    5664          <tr>
    5665             <td class="reference"><b id="RFC6365">[RFC6365]</b></td>
    5666             <td class="top">Hoffman, P. and J. Klensin, “<a href="https://tools.ietf.org/html/rfc6365">Terminology Used in Internationalization in the IETF</a>”, BCP&nbsp;166, RFC&nbsp;6365, September&nbsp;2011.
    5667             </td>
    5668          </tr>
    5669          <tr>
    5670             <td class="reference"><b id="RFC7230">[RFC7230]</b></td>
    5671             <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2014.
    5672             </td>
    5673          </tr>
    5674          <tr>
    5675             <td class="reference"><b id="RFC7232">[RFC7232]</b></td>
    5676             <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2014.
    5677             </td>
    5678          </tr>
    5679          <tr>
    5680             <td class="reference"><b id="RFC7233">[RFC7233]</b></td>
    5681             <td class="top">Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2014.
    5682             </td>
    5683          </tr>
    5684          <tr>
    5685             <td class="reference"><b id="RFC7234">[RFC7234]</b></td>
    5686             <td class="top">Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2014.
    5687             </td>
    5688          </tr>
    5689          <tr>
    5690             <td class="reference"><b id="RFC7235">[RFC7235]</b></td>
    5691             <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), June&nbsp;2014.
    5692             </td>
    5693          </tr>
    5694       </table>
    5695       <h2 id="rfc.references.2"><a href="#rfc.section.11.2" id="rfc.section.11.2">11.2</a> Informative References
    5696       </h2>
    5697       <table>
    5698          <tr>
    5699             <td class="reference"><b id="BCP13">[BCP13]</b></td>
    5700             <td class="top">Freed, N., Klensin, J., and T. Hansen, “<a href="https://tools.ietf.org/html/rfc6838">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;6838, January&nbsp;2013.
    5701             </td>
    5702          </tr>
    5703          <tr>
    5704             <td class="reference"><b id="BCP178">[BCP178]</b></td>
    5705             <td class="top">Saint-Andre, P., Crocker, D., and M. Nottingham, “<a href="https://tools.ietf.org/html/rfc6648">Deprecating the "X-" Prefix and Similar Constructs in Application Protocols</a>”, BCP&nbsp;178, RFC&nbsp;6648, June&nbsp;2012.
    5706             </td>
    5707          </tr>
    5708          <tr>
    5709             <td class="reference"><b id="BCP90">[BCP90]</b></td>
    5710             <td class="top">Klyne, G., Nottingham, M., and J. Mogul, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
    5711             </td>
    5712          </tr>
    5713          <tr>
    5714             <td class="reference"><b id="OWASP">[OWASP]</b></td>
    5715             <td class="top">van der Stock, A., Ed., “<a href="https://www.owasp.org/">A Guide to Building Secure Web Applications and Web Services</a>”, The Open Web Application Security Project (OWASP)&nbsp;2.0.1, July&nbsp;2005, &lt;<a href="https://www.owasp.org/">https://www.owasp.org/</a>&gt;.
    5716             </td>
    5717          </tr>
    5718          <tr>
    5719             <td class="reference"><b id="REST">[REST]</b></td>
    5720             <td class="top">Fielding, R., “<a href="http://roy.gbiv.com/pubs/dissertation/top.htm">Architectural Styles and the Design of Network-based Software Architectures</a>”, Doctoral Dissertation, University of California, Irvine, September&nbsp;2000, &lt;<a href="http://roy.gbiv.com/pubs/dissertation/top.htm">http://roy.gbiv.com/pubs/dissertation/top.htm</a>&gt;.
    5721             </td>
    5722          </tr>
    5723          <tr>
    5724             <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    5725             <td class="top">Berners-Lee, T., Fielding, R., and H. Nielsen, “<a href="https://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
    5726             </td>
    5727          </tr>
    5728          <tr>
    5729             <td class="reference"><b id="RFC2049">[RFC2049]</b></td>
    5730             <td class="top">Freed, N. and N. Borenstein, “<a href="https://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC&nbsp;2049, November&nbsp;1996.
    5731             </td>
    5732          </tr>
    5733          <tr>
    5734             <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
    5735             <td class="top">Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
    5736             </td>
    5737          </tr>
    5738          <tr>
    5739             <td class="reference"><b id="RFC2295">[RFC2295]</b></td>
    5740             <td class="top">Holtman, K. and A. Mutz, “<a href="https://tools.ietf.org/html/rfc2295">Transparent Content Negotiation in HTTP</a>”, RFC&nbsp;2295, March&nbsp;1998.
    5741             </td>
    5742          </tr>
    5743          <tr>
    5744             <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
    5745             <td class="top">Masinter, L., “<a href="https://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
    5746             </td>
    5747          </tr>
    5748          <tr>
    5749             <td class="reference"><b id="RFC2557">[RFC2557]</b></td>
    5750             <td class="top">Palme, F., Hopmann, A., Shelness, N., and E. Stefferud, “<a href="https://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC&nbsp;2557, March&nbsp;1999.
    5751             </td>
    5752          </tr>
    5753          <tr>
    5754             <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    5755             <td class="top">Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    5756             </td>
    5757          </tr>
    5758          <tr>
    5759             <td class="reference"><b id="RFC2774">[RFC2774]</b></td>
    5760             <td class="top">Frystyk, H., Leach, P., and S. Lawrence, “<a href="https://tools.ietf.org/html/rfc2774">An HTTP Extension Framework</a>”, RFC&nbsp;2774, February&nbsp;2000.
    5761             </td>
    5762          </tr>
    5763          <tr>
    5764             <td class="reference"><b id="RFC2817">[RFC2817]</b></td>
    5765             <td class="top">Khare, R. and S. Lawrence, “<a href="https://tools.ietf.org/html/rfc2817">Upgrading to TLS Within HTTP/1.1</a>”, RFC&nbsp;2817, May&nbsp;2000.
    5766             </td>
    5767          </tr>
    5768          <tr>
    5769             <td class="reference"><b id="RFC2978">[RFC2978]</b></td>
    5770             <td class="top">Freed, N. and J. Postel, “<a href="https://tools.ietf.org/html/rfc2978">IANA Charset Registration Procedures</a>”, BCP&nbsp;19, RFC&nbsp;2978, October&nbsp;2000.
    5771             </td>
    5772          </tr>
    5773          <tr>
    5774             <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
    5775             <td class="top">Narten, T. and H. Alvestrand, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
    5776             </td>
    5777          </tr>
    5778          <tr>
    5779             <td class="reference"><b id="RFC5246">[RFC5246]</b></td>
    5780             <td class="top">Dierks, T. and E. Rescorla, “<a href="https://tools.ietf.org/html/rfc5246">The Transport Layer Security (TLS) Protocol Version 1.2</a>”, RFC&nbsp;5246, August&nbsp;2008.
    5781             </td>
    5782          </tr>
    5783          <tr>
    5784             <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
    5785             <td class="top">Resnick, P., “<a href="https://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
    5786             </td>
    5787          </tr>
    5788          <tr>
    5789             <td class="reference"><b id="RFC5789">[RFC5789]</b></td>
    5790             <td class="top">Dusseault, L. and J. Snell, “<a href="https://tools.ietf.org/html/rfc5789">PATCH Method for HTTP</a>”, RFC&nbsp;5789, March&nbsp;2010.
    5791             </td>
    5792          </tr>
    5793          <tr>
    5794             <td class="reference"><b id="RFC5905">[RFC5905]</b></td>
    5795             <td class="top">Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, “<a href="https://tools.ietf.org/html/rfc5905">Network Time Protocol Version 4: Protocol and Algorithms Specification</a>”, RFC&nbsp;5905, June&nbsp;2010.
    5796             </td>
    5797          </tr>
    5798          <tr>
    5799             <td class="reference"><b id="RFC5987">[RFC5987]</b></td>
    5800             <td class="top">Reschke, J., “<a href="https://tools.ietf.org/html/rfc5987">Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header
    5801                   Field Parameters</a>”, RFC&nbsp;5987, August&nbsp;2010.
    5802             </td>
    5803          </tr>
    5804          <tr>
    5805             <td class="reference"><b id="RFC5988">[RFC5988]</b></td>
    5806             <td class="top">Nottingham, M., “<a href="https://tools.ietf.org/html/rfc5988">Web Linking</a>”, RFC&nbsp;5988, October&nbsp;2010.
    5807             </td>
    5808          </tr>
    5809          <tr>
    5810             <td class="reference"><b id="RFC6265">[RFC6265]</b></td>
    5811             <td class="top">Barth, A., “<a href="https://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
    5812             </td>
    5813          </tr>
    5814          <tr>
    5815             <td class="reference"><b id="RFC6266">[RFC6266]</b></td>
    5816             <td class="top">Reschke, J., “<a href="https://tools.ietf.org/html/rfc6266">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>”, RFC&nbsp;6266, June&nbsp;2011.
    5817             </td>
    5818          </tr>
    5819          <tr>
    5820             <td class="reference"><b id="RFC7238">[RFC7238]</b></td>
    5821             <td class="top">Reschke, J., “<a href="https://tools.ietf.org/html/draft-reschke-http-status-308-07">The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)</a>”, Internet-Draft&nbsp;draft-reschke-http-status-308-07 (work in progress), March&nbsp;2012.
    5822             </td>
    5823          </tr>
    5824       </table>
     5637      <h3 id="rfc.references.1"><a href="#rfc.section.11.1" id="rfc.section.11.1">11.1</a> Normative References
     5638      </h3>
     5639      <dl class="reference">
     5640         <dt id="RFC2045">[RFC2045]</dt>
     5641         <dd>Freed, N. and N. Borenstein, “<a href="https://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message
     5642               Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
     5643         </dd>
     5644         <dt id="RFC2046">[RFC2046]</dt>
     5645         <dd>Freed, N. and N. Borenstein, “<a href="https://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
     5646         </dd>
     5647         <dt id="RFC2119">[RFC2119]</dt>
     5648         <dd>Bradner, S., “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
     5649         </dd>
     5650         <dt id="RFC3986">[RFC3986]</dt>
     5651         <dd>Berners-Lee, T., Fielding, R., and L. Masinter, “<a href="https://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
     5652         </dd>
     5653         <dt id="RFC4647">[RFC4647]</dt>
     5654         <dd>Phillips, A., Ed. and M. Davis, Ed., “<a href="https://tools.ietf.org/html/rfc4647">Matching of Language Tags</a>”, BCP&nbsp;47, RFC&nbsp;4647, September&nbsp;2006.
     5655         </dd>
     5656         <dt id="RFC5234">[RFC5234]</dt>
     5657         <dd>Crocker, D., Ed. and P. Overell, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     5658         </dd>
     5659         <dt id="RFC5646">[RFC5646]</dt>
     5660         <dd>Phillips, A., Ed. and M. Davis, Ed., “<a href="https://tools.ietf.org/html/rfc5646">Tags for Identifying Languages</a>”, BCP&nbsp;47, RFC&nbsp;5646, September&nbsp;2009.
     5661         </dd>
     5662         <dt id="RFC6365">[RFC6365]</dt>
     5663         <dd>Hoffman, P. and J. Klensin, “<a href="https://tools.ietf.org/html/rfc6365">Terminology Used in Internationalization in the IETF</a>”, BCP&nbsp;166, RFC&nbsp;6365, September&nbsp;2011.
     5664         </dd>
     5665         <dt id="RFC7230">[RFC7230]</dt>
     5666         <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2014.
     5667         </dd>
     5668         <dt id="RFC7232">[RFC7232]</dt>
     5669         <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), June&nbsp;2014.
     5670         </dd>
     5671         <dt id="RFC7233">[RFC7233]</dt>
     5672         <dd>Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2014.
     5673         </dd>
     5674         <dt id="RFC7234">[RFC7234]</dt>
     5675         <dd>Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2014.
     5676         </dd>
     5677         <dt id="RFC7235">[RFC7235]</dt>
     5678         <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), June&nbsp;2014.
     5679         </dd>
     5680      </dl>
     5681      <h3 id="rfc.references.2"><a href="#rfc.section.11.2" id="rfc.section.11.2">11.2</a> Informative References
     5682      </h3>
     5683      <dl class="reference">
     5684         <dt id="BCP13">[BCP13]</dt>
     5685         <dd>Freed, N., Klensin, J., and T. Hansen, “<a href="https://tools.ietf.org/html/rfc6838">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;6838, January&nbsp;2013.
     5686         </dd>
     5687         <dt id="BCP178">[BCP178]</dt>
     5688         <dd>Saint-Andre, P., Crocker, D., and M. Nottingham, “<a href="https://tools.ietf.org/html/rfc6648">Deprecating the "X-" Prefix and Similar Constructs in Application Protocols</a>”, BCP&nbsp;178, RFC&nbsp;6648, June&nbsp;2012.
     5689         </dd>
     5690         <dt id="BCP90">[BCP90]</dt>
     5691         <dd>Klyne, G., Nottingham, M., and J. Mogul, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
     5692         </dd>
     5693         <dt id="OWASP">[OWASP]</dt>
     5694         <dd>van der Stock, A., Ed., “<a href="https://www.owasp.org/">A Guide to Building Secure Web Applications and Web Services</a>”, The Open Web Application Security Project (OWASP)&nbsp;2.0.1, July&nbsp;2005, &lt;<a href="https://www.owasp.org/">https://www.owasp.org/</a>&gt;.
     5695         </dd>
     5696         <dt id="REST">[REST]</dt>
     5697         <dd>Fielding, R., “<a href="http://roy.gbiv.com/pubs/dissertation/top.htm">Architectural Styles and the Design of Network-based Software Architectures</a>”, Doctoral Dissertation, University of California, Irvine, September&nbsp;2000, &lt;<a href="http://roy.gbiv.com/pubs/dissertation/top.htm">http://roy.gbiv.com/pubs/dissertation/top.htm</a>&gt;.
     5698         </dd>
     5699         <dt id="RFC1945">[RFC1945]</dt>
     5700         <dd>Berners-Lee, T., Fielding, R., and H. Nielsen, “<a href="https://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
     5701         </dd>
     5702         <dt id="RFC2049">[RFC2049]</dt>
     5703         <dd>Freed, N. and N. Borenstein, “<a href="https://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC&nbsp;2049, November&nbsp;1996.
     5704         </dd>
     5705         <dt id="RFC2068">[RFC2068]</dt>
     5706         <dd>Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
     5707         </dd>
     5708         <dt id="RFC2295">[RFC2295]</dt>
     5709         <dd>Holtman, K. and A. Mutz, “<a href="https://tools.ietf.org/html/rfc2295">Transparent Content Negotiation in HTTP</a>”, RFC&nbsp;2295, March&nbsp;1998.
     5710         </dd>
     5711         <dt id="RFC2388">[RFC2388]</dt>
     5712         <dd>Masinter, L., “<a href="https://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
     5713         </dd>
     5714         <dt id="RFC2557">[RFC2557]</dt>
     5715         <dd>Palme, F., Hopmann, A., Shelness, N., and E. Stefferud, “<a href="https://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC&nbsp;2557, March&nbsp;1999.
     5716         </dd>
     5717         <dt id="RFC2616">[RFC2616]</dt>
     5718         <dd>Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     5719         </dd>
     5720         <dt id="RFC2774">[RFC2774]</dt>
     5721         <dd>Frystyk, H., Leach, P., and S. Lawrence, “<a href="https://tools.ietf.org/html/rfc2774">An HTTP Extension Framework</a>”, RFC&nbsp;2774, February&nbsp;2000.
     5722         </dd>
     5723         <dt id="RFC2817">[RFC2817]</dt>
     5724         <dd>Khare, R. and S. Lawrence, “<a href="https://tools.ietf.org/html/rfc2817">Upgrading to TLS Within HTTP/1.1</a>”, RFC&nbsp;2817, May&nbsp;2000.
     5725         </dd>
     5726         <dt id="RFC2978">[RFC2978]</dt>
     5727         <dd>Freed, N. and J. Postel, “<a href="https://tools.ietf.org/html/rfc2978">IANA Charset Registration Procedures</a>”, BCP&nbsp;19, RFC&nbsp;2978, October&nbsp;2000.
     5728         </dd>
     5729         <dt id="RFC5226">[RFC5226]</dt>
     5730         <dd>Narten, T. and H. Alvestrand, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
     5731         </dd>
     5732         <dt id="RFC5246">[RFC5246]</dt>
     5733         <dd>Dierks, T. and E. Rescorla, “<a href="https://tools.ietf.org/html/rfc5246">The Transport Layer Security (TLS) Protocol Version 1.2</a>”, RFC&nbsp;5246, August&nbsp;2008.
     5734         </dd>
     5735         <dt id="RFC5322">[RFC5322]</dt>
     5736         <dd>Resnick, P., “<a href="https://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
     5737         </dd>
     5738         <dt id="RFC5789">[RFC5789]</dt>
     5739         <dd>Dusseault, L. and J. Snell, “<a href="https://tools.ietf.org/html/rfc5789">PATCH Method for HTTP</a>”, RFC&nbsp;5789, March&nbsp;2010.
     5740         </dd>
     5741         <dt id="RFC5905">[RFC5905]</dt>
     5742         <dd>Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, “<a href="https://tools.ietf.org/html/rfc5905">Network Time Protocol Version 4: Protocol and Algorithms Specification</a>”, RFC&nbsp;5905, June&nbsp;2010.
     5743         </dd>
     5744         <dt id="RFC5987">[RFC5987]</dt>
     5745         <dd>Reschke, J., “<a href="https://tools.ietf.org/html/rfc5987">Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header
     5746               Field Parameters</a>”, RFC&nbsp;5987, August&nbsp;2010.
     5747         </dd>
     5748         <dt id="RFC5988">[RFC5988]</dt>
     5749         <dd>Nottingham, M., “<a href="https://tools.ietf.org/html/rfc5988">Web Linking</a>”, RFC&nbsp;5988, October&nbsp;2010.
     5750         </dd>
     5751         <dt id="RFC6265">[RFC6265]</dt>
     5752         <dd>Barth, A., “<a href="https://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
     5753         </dd>
     5754         <dt id="RFC6266">[RFC6266]</dt>
     5755         <dd>Reschke, J., “<a href="https://tools.ietf.org/html/rfc6266">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>”, RFC&nbsp;6266, June&nbsp;2011.
     5756         </dd>
     5757         <dt id="RFC7238">[RFC7238]</dt>
     5758         <dd>Reschke, J., “<a href="https://tools.ietf.org/html/draft-reschke-http-status-308-07">The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)</a>”, Internet-Draft&nbsp;draft-reschke-http-status-308-07 (work in progress), March&nbsp;2012.
     5759         </dd>
     5760      </dl>
    58255761      <div id="differences.between.http.and.mime">
    5826          <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h1>
     5762         <h2 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h2>
    58275763         <div id="rfc.section.A.p.1">
    58285764            <p>HTTP/1.1 uses many of the constructs defined for the Internet Message Format <a href="#RFC5322" id="rfc.xref.RFC5322.7"><cite title="Internet Message Format">[RFC5322]</cite></a> and the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> to allow a message body to be transmitted in an open variety of representations and
     
    58425778         </div>
    58435779         <div id="mime-version">
    5844             <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#mime-version">MIME-Version</a></h2>
     5780            <h3 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#mime-version">MIME-Version</a></h3>
    58455781            <div id="rfc.section.A.1.p.1">
    58465782               <p>HTTP is not a MIME-compliant protocol. However, messages can include a single MIME-Version
     
    58535789         </div>
    58545790         <div id="conversion.to.canonical.form">
    5855             <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2>
     5791            <h3 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h3>
    58565792            <div id="rfc.section.A.2.p.1">
    58575793               <p>MIME requires that an Internet mail body part be converted to canonical form prior
     
    58775813         </div>
    58785814         <div id="conversion.of.date.formats">
    5879             <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a>&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></h2>
     5815            <h3 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a>&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></h3>
    58805816            <div id="rfc.section.A.3.p.1">
    58815817               <p>HTTP/1.1 uses a restricted set of date formats (<a href="#http.date" title="Date/Time Formats">Section&nbsp;7.1.1.1</a>) to simplify the process of date comparison. Proxies and gateways from other protocols
     
    58865822         </div>
    58875823         <div id="conversion.content-encoding">
    5888             <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a>&nbsp;<a href="#conversion.content-encoding">Conversion of Content-Encoding</a></h2>
     5824            <h3 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a>&nbsp;<a href="#conversion.content-encoding">Conversion of Content-Encoding</a></h3>
    58895825            <div id="rfc.section.A.4.p.1">
    58905826               <p>MIME does not include any concept equivalent to HTTP/1.1's <a href="#header.content-encoding" class="smpl">Content-Encoding</a> header field. Since this acts as a modifier on the media type, proxies and gateways
     
    58975833         </div>
    58985834         <div id="conversion.content-transfer-encoding">
    5899             <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a href="#conversion.content-transfer-encoding">Conversion of Content-Transfer-Encoding</a></h2>
     5835            <h3 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a href="#conversion.content-transfer-encoding">Conversion of Content-Transfer-Encoding</a></h3>
    59005836            <div id="rfc.section.A.5.p.1">
    59015837               <p>HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways
     
    59155851         </div>
    59165852         <div id="mhtml.line.length">
    5917             <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2>
     5853            <h3 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></h3>
    59185854            <div id="rfc.section.A.6.p.1">
    59195855               <p>HTTP implementations that share code with MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does
     
    59285864      </div>
    59295865      <div id="changes.from.rfc.2616">
    5930          <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
     5866         <h2 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    59315867         <div id="rfc.section.B.p.1">
    59325868            <p>The primary changes in this revision have been editorial in nature: extracting the
     
    60766012      </div>
    60776013      <div id="imported.abnf">
    6078          <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#imported.abnf">Imported ABNF</a></h1>
     6014         <h2 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#imported.abnf">Imported ABNF</a></h2>
    60796015         <div id="rfc.section.C.p.1">
    60806016            <p>The following core rules are included by reference, as defined in <a href="https://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a> of <a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal
     
    60846020            </p>
    60856021         </div>
    6086          <div id="rfc.section.C.p.2">
     6022         <div id="rfc.section.C.p.2" class="avoidbreakafter">
    60876023            <p>The rules below are defined in <a href="#RFC7230" id="rfc.xref.RFC7230.47"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>:
    60886024            </p>
     
    61016037      </div>
    61026038      <div id="collected.abnf">
    6103          <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     6039         <h2 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h2>
    61046040         <div id="rfc.section.D.p.1">
    61056041            <p>In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.58"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     
    62356171</pre></div>
    62366172      </div>
    6237       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
     6173      <h2 id="rfc.index"><a href="#rfc.index">Index</a></h2>
    62386174      <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.X">X</a>
    62396175      </p>
     
    66266562      </div>
    66276563      <div class="avoidbreakinside">
    6628          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     6564         <h2 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h2>
    66296565         <p><b>Roy T. Fielding</b>
    66306566            (editor)
  • draft-ietf-httpbis/latest/p4-conditional.html

    r2734 r2748  
    44   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    6       <title>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</title><script>
     6      <title>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</title><script type="application/javascript">
    77var buttonsAdded = false;
    88
     
    1717
    1818function feedback() {
    19   toggleButtonsToElementsByName("h1");
    2019  toggleButtonsToElementsByName("h2");
    2120  toggleButtonsToElementsByName("h3");
    2221  toggleButtonsToElementsByName("h4");
     22  toggleButtonsToElementsByName("h5");
    2323
    2424  buttonsAdded = !buttonsAdded;
     
    147147  margin-left: 0em;
    148148}
     149dl.reference > dt {
     150  font-weight: bold;
     151}
     152dl.reference > dd {
     153  margin-left: 6em;
     154}
    149155h1 {
     156  color: green;
     157  font-size: 150%;
     158  line-height: 18pt;
     159  font-weight: bold;
     160  text-align: center;
     161  margin-top: 36pt;
     162  margin-bottom: 0pt;
     163}
     164h2 {
    150165  font-size: 130%;
    151166  line-height: 21pt;
    152167  page-break-after: avoid;
    153168}
    154 h1.np {
     169h2.np {
    155170  page-break-before: always;
    156171}
    157 h2 {
     172h3 {
    158173  font-size: 120%;
    159174  line-height: 15pt;
    160175  page-break-after: avoid;
    161176}
    162 h3 {
     177h4 {
    163178  font-size: 110%;
    164179  page-break-after: avoid;
    165180}
    166 h4, h5, h6 {
     181h5, h6 {
    167182  page-break-after: avoid;
    168183}
     
    266281  border-width: 2px;
    267282}
    268 table.left {
     283table.tleft {
    269284  margin-right: auto;
    270285}
    271 table.right {
     286table.tright {
    272287  margin-left: auto;
    273288}
    274 table.center {
     289table.tcenter {
    275290  margin-left: auto;
    276291  margin-right: auto;
     
    303318  color: white;
    304319}
    305 td.reference {
    306   vertical-align: top;
    307   white-space: nowrap;
    308   padding-right: 1em;
    309 }
    310320thead {
    311321  display:table-header-group;
     
    333343  margin-left: 0em;
    334344}
    335 .title, .filename, h1, h2, h3, h4 {
     345.filename, h1, h2, h3, h4 {
    336346  font-family: candara, calibri, segoe, optima, arial, sans-serif;
    337347}
     
    381391.filename {
    382392  color: #333333;
    383   font-size: 75%;
     393  font-size: 112%;
    384394  font-weight: bold;
    385395  line-height: 21pt;
    386396  text-align: center;
     397  margin-top: 0pt;
    387398}
    388399.fn {
     
    394405.right {
    395406  text-align: right;
    396 }
    397 .title {
    398   color: green;
    399   font-size: 150%;
    400   line-height: 18pt;
    401   font-weight: bold;
    402   text-align: center;
    403   margin-top: 36pt;
    404407}
    405408.warning {
     
    428431  border: 1px solid silver;
    429432  border-radius: 5px;
     433}
     434.publishedasrfc {
     435  background-color: yellow;
     436  color: green;
     437  font-size: 14pt;
     438  text-align: center;
    430439}
    431440
     
    529538      <link href="p2-semantics.html" rel="prev">
    530539      <link href="p5-range.html" rel="next">
    531       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.710, 2014/12/09 13:12:18, XSLT vendor: Saxonica http://www.saxonica.com/">
     540      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.756, 2015/12/31 17:59:21, XSLT vendor: Saxonica http://www.saxonica.com/">
    532541      <meta name="keywords" content="Hypertext Transfer Protocol, HTTP, HTTP conditional requests">
    533542      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     
    566575         </tbody>
    567576      </table>
    568       <p class="title" id="rfc.title">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests<br><span class="filename">draft-ietf-httpbis-p4-conditional-latest</span></p>
    569       <p style="color: green; text-align: center; font-size: 14pt; background-color: yellow;"><b>Note:</b> a later version of this document has been published as <a href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7232.html">RFC7232</a>.
     577      <div id="rfc.title">
     578         <h1>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</h1>
     579         <div class="filename">draft-ietf-httpbis-p4-conditional-latest</div>
     580      </div>
     581      <p class="publishedasrfc"><b>Note:</b> a later version of this document has been published as <a href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7232.html">RFC7232</a>.
    570582         
    571583      </p>
    572       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
     584      <h2 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h2>
    573585      <p>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for
    574586         distributed, collaborative, hypertext information systems. This document defines HTTP/1.1
     
    578590         false.
    579591      </p>
    580       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
     592      <h2 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h2>
    581593      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org),
    582594         which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
     
    588600      </p>
    589601      <div id="rfc.status">
    590          <h1><a href="#rfc.status">Status of This Memo</a></h1>
     602         <h2><a href="#rfc.status">Status of This Memo</a></h2>
    591603         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78
    592604            and BCP 79.
     
    603615      </div>
    604616      <div id="rfc.copyrightnotice">
    605          <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     617         <h2><a href="#rfc.copyrightnotice">Copyright Notice</a></h2>
    606618         <p>Copyright © 2014 IETF Trust and the persons identified as the document authors. All
    607619            rights reserved.
     
    626638      <hr class="noprint">
    627639      <div id="rfc.toc">
    628          <h1 class="np"><a href="#rfc.toc">Table of Contents</a></h1>
     640         <h2 class="np"><a href="#rfc.toc">Table of Contents</a></h2>
    629641         <ul class="toc">
    630642            <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     
    684696      </div>
    685697      <div id="introduction">
    686          <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     698         <h2 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h2>
    687699         <div id="rfc.section.1.p.1">
    688700            <p>Conditional requests are HTTP requests <a href="#RFC7231" id="rfc.xref.RFC7231.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a> that include one or more header fields indicating a precondition to be tested before
     
    714726         </div>
    715727         <div id="conformance">
    716             <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#conformance">Conformance and Error Handling</a></h2>
     728            <h3 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#conformance">Conformance and Error Handling</a></h3>
    717729            <div id="rfc.section.1.1.p.1">
    718730               <p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
     
    727739         </div>
    728740         <div id="notation">
    729             <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     741            <h3 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h3>
    730742            <div id="rfc.section.1.2.p.1">
    731743               <p>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 a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF List Extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator
     
    736748      </div>
    737749      <div id="validators">
    738          <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#validators">Validators</a></h1>
     750         <h2 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#validators">Validators</a></h2>
    739751         <div id="rfc.section.2.p.1">
    740752            <p>This specification defines two forms of metadata that are commonly used to observe
     
    745757         </div>
    746758         <div id="weak.and.strong.validators">
    747             <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#weak.and.strong.validators">Weak versus Strong</a></h2>
     759            <h3 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#weak.and.strong.validators">Weak versus Strong</a></h3>
    748760            <div id="rfc.section.2.1.p.1">
    749761               <p>Validators come in two flavors: strong or weak. Weak validators are easy to generate
     
    834846         </div>
    835847         <div id="header.last-modified">
    836             <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#header.last-modified">Last-Modified</a></h2>
     848            <h3 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#header.last-modified">Last-Modified</a></h3>
    837849            <div id="rfc.section.2.2.p.1">
    838850               <p>The "Last-Modified" header field in a response provides a timestamp indicating the
     
    849861</pre></div>
    850862            <div id="lastmod.generation">
    851                <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a href="#lastmod.generation">Generation</a></h3>
     863               <h4 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a href="#lastmod.generation">Generation</a></h4>
    852864               <div id="rfc.section.2.2.1.p.1">
    853865                  <p>An origin server <em class="bcp14">SHOULD</em> send Last-Modified for any selected representation for which a last modification date
     
    888900            </div>
    889901            <div id="lastmod.comparison">
    890                <h3 id="rfc.section.2.2.2"><a href="#rfc.section.2.2.2">2.2.2</a>&nbsp;<a href="#lastmod.comparison">Comparison</a></h3>
     902               <h4 id="rfc.section.2.2.2"><a href="#rfc.section.2.2.2">2.2.2</a>&nbsp;<a href="#lastmod.comparison">Comparison</a></h4>
    891903               <div id="rfc.section.2.2.2.p.1">
    892904                  <p>A Last-Modified time, when used as a validator in a request, is implicitly weak unless
     
    935947         </div>
    936948         <div id="header.etag">
    937             <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a href="#header.etag">ETag</a></h2>
     949            <h3 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a href="#header.etag">ETag</a></h3>
    938950            <div id="rfc.section.2.3.p.1">
    939951               <p>The "ETag" header field in a response provides the current entity-tag for the selected
     
    981993            </div>
    982994            <div id="entity.tag.generation">
    983                <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a href="#entity.tag.generation">Generation</a></h3>
     995               <h4 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a href="#entity.tag.generation">Generation</a></h4>
    984996               <div id="rfc.section.2.3.1.p.1">
    985997                  <p>The principle behind entity-tags is that only the service author knows the implementation
     
    10081020            </div>
    10091021            <div id="entity.tag.comparison">
    1010                <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a href="#entity.tag.comparison">Comparison</a></h3>
     1022               <h4 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a href="#entity.tag.comparison">Comparison</a></h4>
    10111023               <div id="rfc.section.2.3.2.p.1">
    10121024                  <p>There are two entity-tag comparison functions, depending on whether or not the comparison
     
    10221034                  </ul>
    10231035               </div>
    1024                <div id="rfc.section.2.3.2.p.2">
     1036               <div id="rfc.section.2.3.2.p.2" class="avoidbreakafter">
    10251037                  <p>The example below shows the results for a set of entity-tag pairs and both the weak
    10261038                     and strong comparison function results:
     
    10281040               </div>
    10291041               <div id="rfc.table.u.1">
    1030                   <table class="tt full left" cellpadding="3" cellspacing="0">
     1042                  <table class="tt full tleft" cellpadding="3" cellspacing="0">
    10311043                     <thead>
    10321044                        <tr>
     
    10671079            </div>
    10681080            <div id="example.entity.tag.vs.conneg">
    1069                <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a href="#example.entity.tag.vs.conneg">Example: Entity-Tags Varying on Content-Negotiated Resources</a></h3>
    1070                <div id="rfc.section.2.3.3.p.1">
     1081               <h4 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a href="#example.entity.tag.vs.conneg">Example: Entity-Tags Varying on Content-Negotiated Resources</a></h4>
     1082               <div id="rfc.section.2.3.3.p.1" class="avoidbreakafter">
    10711083                  <p>Consider a resource that is subject to content negotiation (<a href="p2-semantics.html#content.negotiation" title="Content Negotiation">Section 3.4</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>), and where the representations sent in response to 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 5.3.4</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>):
    10721084                  </p>
     
    10781090
    10791091</pre></div>
    1080                <div id="rfc.section.2.3.3.p.2">
     1092               <div id="rfc.section.2.3.3.p.2" class="avoidbreakafter">
    10811093                  <p>In this case, the response might or might not use the gzip content coding. If it does
    10821094                     not, the response might look like:
     
    10971109Hello World!
    10981110</span></pre></div>
    1099                <div id="rfc.section.2.3.3.p.3">
     1111               <div id="rfc.section.2.3.3.p.3" class="avoidbreakafter">
    11001112                  <p>An alternative representation that does use gzip content coding would be:</p>
    11011113               </div>
     
    11221134         </div>
    11231135         <div id="when.to.use.entity.tags.and.last-modified.dates">
    1124             <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a href="#when.to.use.entity.tags.and.last-modified.dates">When to Use Entity-Tags and Last-Modified Dates</a></h2>
     1136            <h3 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a href="#when.to.use.entity.tags.and.last-modified.dates">When to Use Entity-Tags and Last-Modified Dates</a></h3>
    11251137            <div id="rfc.section.2.4.p.1">
    11261138               <p>In <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> responses to GET or HEAD, an origin server:
     
    11591171      </div>
    11601172      <div id="preconditions">
    1161          <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#preconditions">Precondition Header Fields</a></h1>
     1173         <h2 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#preconditions">Precondition Header Fields</a></h2>
    11621174         <div id="rfc.section.3.p.1">
    11631175            <p>This section defines the syntax and semantics of HTTP/1.1 header fields for applying
     
    11661178         </div>
    11671179         <div id="header.if-match">
    1168             <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.if-match">If-Match</a></h2>
     1180            <h3 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.if-match">If-Match</a></h3>
    11691181            <div id="rfc.section.3.1.p.1">
    11701182               <p>The "If-Match" header field makes the request method conditional on the recipient
     
    11821194            <div id="rfc.figure.u.8"><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>
    11831195</pre></div>
    1184             <div id="rfc.section.3.1.p.3">
     1196            <div id="rfc.section.3.1.p.3" class="avoidbreakafter">
    11851197               <p>Examples:</p>
    11861198            </div>
     
    12201232         </div>
    12211233         <div id="header.if-none-match">
    1222             <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.if-none-match">If-None-Match</a></h2>
     1234            <h3 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.if-none-match">If-None-Match</a></h3>
    12231235            <div id="rfc.section.3.2.p.1">
    12241236               <p>The "If-None-Match" header field makes the request method conditional on a recipient
     
    12351247            <div id="rfc.figure.u.10"><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>
    12361248</pre></div>
    1237             <div id="rfc.section.3.2.p.3">
     1249            <div id="rfc.section.3.2.p.3" class="avoidbreakafter">
    12381250               <p>Examples:</p>
    12391251            </div>
     
    12781290         </div>
    12791291         <div id="header.if-modified-since">
    1280             <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#header.if-modified-since">If-Modified-Since</a></h2>
     1292            <h3 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#header.if-modified-since">If-Modified-Since</a></h3>
    12811293            <div id="rfc.section.3.3.p.1">
    12821294               <p>The "If-Modified-Since" header field makes a GET or HEAD request method conditional
     
    12881300            <div id="rfc.figure.u.12"><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>
    12891301</pre></div>
    1290             <div id="rfc.section.3.3.p.2">
     1302            <div id="rfc.section.3.3.p.2" class="avoidbreakafter">
    12911303               <p>An example of the field is:</p>
    12921304            </div>
     
    13471359         </div>
    13481360         <div id="header.if-unmodified-since">
    1349             <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#header.if-unmodified-since">If-Unmodified-Since</a></h2>
     1361            <h3 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#header.if-unmodified-since">If-Unmodified-Since</a></h3>
    13501362            <div id="rfc.section.3.4.p.1">
    13511363               <p>The "If-Unmodified-Since" header field makes the request method conditional on the
     
    13561368            <div id="rfc.figure.u.14"><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>
    13571369</pre></div>
    1358             <div id="rfc.section.3.4.p.2">
     1370            <div id="rfc.section.3.4.p.2" class="avoidbreakafter">
    13591371               <p>An example of the field is:</p>
    13601372            </div>
     
    14031415         </div>
    14041416         <div id="header.if-range">
    1405             <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#header.if-range">If-Range</a></h2>
     1417            <h3 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#header.if-range">If-Range</a></h3>
    14061418            <div id="rfc.section.3.5.p.1">
    14071419               <p>The "If-Range" header field provides a special conditional request mechanism that
     
    14131425      </div>
    14141426      <div id="status.code.definitions">
    1415          <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#status.code.definitions">Status Code Definitions</a></h1>
     1427         <h2 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#status.code.definitions">Status Code Definitions</a></h2>
    14161428         <div id="status.304">
    1417             <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#status.304">304 Not Modified</a></h2>
     1429            <h3 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#status.304">304 Not Modified</a></h3>
    14181430            <div id="rfc.section.4.1.p.1">
    14191431               <p>The <dfn>304 (Not Modified)</dfn> status code indicates that a conditional GET or HEAD request has been received and
     
    14471459         </div>
    14481460         <div id="status.412">
    1449             <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#status.412">412 Precondition Failed</a></h2>
     1461            <h3 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#status.412">412 Precondition Failed</a></h3>
    14501462            <div id="rfc.section.4.2.p.1">
    14511463               <p>The <dfn>412 (Precondition Failed)</dfn> status code indicates that one or more conditions given in the request header fields
     
    14591471      </div>
    14601472      <div id="evaluation">
    1461          <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#evaluation">Evaluation</a></h1>
     1473         <h2 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#evaluation">Evaluation</a></h2>
    14621474         <div id="rfc.section.5.p.1">
    14631475            <p>Except when excluded below, a recipient cache or origin server <em class="bcp14">MUST</em> evaluate received request preconditions after it has successfully performed its normal
     
    14941506      </div>
    14951507      <div id="precedence">
    1496          <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#precedence">Precedence</a></h1>
     1508         <h2 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#precedence">Precedence</a></h2>
    14971509         <div id="rfc.section.6.p.1">
    14981510            <p>When more than one conditional request header field is present in a request, the order
     
    15621574      </div>
    15631575      <div id="IANA.considerations">
    1564          <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     1576         <h2 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h2>
    15651577         <div id="status.code.registration">
    1566             <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h2>
    1567             <div id="rfc.section.7.1.p.1">
     1578            <h3 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h3>
     1579            <div id="rfc.section.7.1.p.1" class="avoidbreakafter">
    15681580               <p>The "Hypertext Transfer Protocol (HTTP) Status Code Registry" located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; has been updated with the registrations below:
    15691581               </p>
     
    15711583            <div id="rfc.table.1">
    15721584               <div id="iana.status.code.registration.table"></div>
    1573                <table class="tt full left" cellpadding="3" cellspacing="0">
     1585               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    15741586                  <thead>
    15751587                     <tr>
     
    15971609         </div>
    15981610         <div id="header.field.registration">
    1599             <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
     1611            <h3 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h3>
    16001612            <div id="rfc.section.7.2.p.1">
    16011613               <p>HTTP header fields are registered within the "Message Headers" registry maintained
     
    16031615               </p>
    16041616            </div>
    1605             <div id="rfc.section.7.2.p.2">
     1617            <div id="rfc.section.7.2.p.2" class="avoidbreakafter">
    16061618               <p>This document defines the following HTTP header fields, so their associated registry
    16071619                  entries have been updated according to the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
     
    16101622            <div id="rfc.table.2">
    16111623               <div id="iana.header.registration.table"></div>
    1612                <table class="tt full left" cellpadding="3" cellspacing="0">
     1624               <table class="tt full tleft" cellpadding="3" cellspacing="0">
    16131625                  <thead>
    16141626                     <tr>
     
    16711683      </div>
    16721684      <div id="security.considerations">
    1673          <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     1685         <h2 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h2>
    16741686         <div id="rfc.section.8.p.1">
    16751687            <p>This section is meant to inform developers, information providers, and users of known
     
    17011713      </div>
    17021714      <div id="acks">
    1703          <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
     1715         <h2 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#acks">Acknowledgments</a></h2>
    17041716         <div id="rfc.section.9.p.1">
    17051717            <p>See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     
    17071719         </div>
    17081720      </div>
    1709       <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
    1710       </h1>
    1711       <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
     1721      <h2 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
    17121722      </h2>
    1713       <table>
    1714          <tr>
    1715             <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    1716             <td class="top">Bradner, S., “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
    1717             </td>
    1718          </tr>
    1719          <tr>
    1720             <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    1721             <td class="top">Crocker, D., Ed. and P. Overell, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
    1722             </td>
    1723          </tr>
    1724          <tr>
    1725             <td class="reference"><b id="RFC7230">[RFC7230]</b></td>
    1726             <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2014.
    1727             </td>
    1728          </tr>
    1729          <tr>
    1730             <td class="reference"><b id="RFC7231">[RFC7231]</b></td>
    1731             <td class="top">Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2014.
    1732             </td>
    1733          </tr>
    1734          <tr>
    1735             <td class="reference"><b id="RFC7233">[RFC7233]</b></td>
    1736             <td class="top">Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2014.
    1737             </td>
    1738          </tr>
    1739          <tr>
    1740             <td class="reference"><b id="RFC7234">[RFC7234]</b></td>
    1741             <td class="top">Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2014.
    1742             </td>
    1743          </tr>
    1744       </table>
    1745       <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
    1746       </h2>
    1747       <table>
    1748          <tr>
    1749             <td class="reference"><b id="BCP90">[BCP90]</b></td>
    1750             <td class="top">Klyne, G., Nottingham, M., and J. Mogul, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
    1751             </td>
    1752          </tr>
    1753          <tr>
    1754             <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    1755             <td class="top">Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    1756             </td>
    1757          </tr>
    1758          <tr>
    1759             <td class="reference"><b id="RFC4918">[RFC4918]</b></td>
    1760             <td class="top">Dusseault, L., Ed., “<a href="https://tools.ietf.org/html/rfc4918">HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)</a>”, RFC&nbsp;4918, June&nbsp;2007.
    1761             </td>
    1762          </tr>
    1763       </table>
     1723      <h3 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
     1724      </h3>
     1725      <dl class="reference">
     1726         <dt id="RFC2119">[RFC2119]</dt>
     1727         <dd>Bradner, S., “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
     1728         </dd>
     1729         <dt id="RFC5234">[RFC5234]</dt>
     1730         <dd>Crocker, D., Ed. and P. Overell, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     1731         </dd>
     1732         <dt id="RFC7230">[RFC7230]</dt>
     1733         <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), June&nbsp;2014.
     1734         </dd>
     1735         <dt id="RFC7231">[RFC7231]</dt>
     1736         <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), June&nbsp;2014.
     1737         </dd>
     1738         <dt id="RFC7233">[RFC7233]</dt>
     1739         <dd>Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), June&nbsp;2014.
     1740         </dd>
     1741         <dt id="RFC7234">[RFC7234]</dt>
     1742         <dd>Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), June&nbsp;2014.
     1743         </dd>
     1744      </dl>
     1745      <h3 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
     1746      </h3>
     1747      <dl class="reference">
     1748         <dt id="BCP90">[BCP90]</dt>
     1749         <dd>Klyne, G., Nottingham, M., and J. Mogul, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
     1750         </dd>
     1751         <dt id="RFC2616">[RFC2616]</dt>
     1752         <dd>Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     1753         </dd>
     1754         <dt id="RFC4918">[RFC4918]</dt>
     1755         <dd>Dusseault, L., Ed., “<a href="https://tools.ietf.org/html/rfc4918">HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)</a>”, RFC&nbsp;4918, June&nbsp;2007.
     1756         </dd>
     1757      </dl>
    17641758      <div id="changes.from.rfc.2616">
    1765          <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
     1759         <h2 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    17661760         <div id="rfc.section.A.p.1">
    17671761            <p>The definition of validator weakness has been expanded and clarified. (<a href="#weak.and.strong.validators" title="Weak versus Strong">Section&nbsp;2.1</a>)
     
    17881782      </div>
    17891783      <div id="imported.abnf">
    1790          <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#imported.abnf">Imported ABNF</a></h1>
     1784         <h2 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#imported.abnf">Imported ABNF</a></h2>
    17911785         <div id="rfc.section.B.p.1">
    17921786            <p>The following core rules are included by reference, as defined in <a href="https://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
     
    17951789            </p>
    17961790         </div>
    1797          <div id="rfc.section.B.p.2">
     1791         <div id="rfc.section.B.p.2" class="avoidbreakafter">
    17981792            <p>The rules below are defined in <a href="#RFC7230" id="rfc.xref.RFC7230.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>:
    17991793            </p>
     
    18021796  <a href="#imported.abnf" class="smpl">obs-text</a>      = &lt;obs-text, see <a href="#RFC7230" id="rfc.xref.RFC7230.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field Value Components">Section 3.2.6</a>&gt;
    18031797</pre></div>
    1804          <div id="rfc.section.B.p.3">
     1798         <div id="rfc.section.B.p.3" class="avoidbreakafter">
    18051799            <p>The rules below are defined in other parts:</p>
    18061800         </div>
     
    18091803      </div>
    18101804      <div id="collected.abnf">
    1811          <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     1805         <h2 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h2>
    18121806         <div id="rfc.section.C.p.1">
    18131807            <p>In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>.
     
    18391833</pre></div>
    18401834      </div>
    1841       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
     1835      <h2 id="rfc.index"><a href="#rfc.index">Index</a></h2>
    18421836      <p class="noprint"><a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a>
    18431837      </p>
     
    19501944      </div>
    19511945      <div class="avoidbreakinside">
    1952          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     1946         <h2 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h2>
    19531947         <p><b>Roy T. Fielding</b>
    19541948            (editor)
  • draft-ietf-httpbis/latest/p5-range.html

    r2734 r2748  
    44   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    6       <title>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title><script>
     6      <title>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title><script type="application/javascript">
    77var buttonsAdded = false;
    88
     
    1717
    1818function feedback() {
    19   toggleButtonsToElementsByName("h1");
    2019  toggleButtonsToElementsByName("h2");
    2120  toggleButtonsToElementsByName("h3");
    2221  toggleButtonsToElementsByName("h4");
     22  toggleButtonsToElementsByName("h5");
    2323
    2424  buttonsAdded = !buttonsAdded;
     
    147147  margin-left: 0em;
    148148}
     149dl.reference > dt {
     150  font-weight: bold;
     151}
     152dl.reference > dd {
     153  margin-left: 6em;
     154}
    149155h1 {
     156  color: green;
     157  font-size: 150%;
     158  line-height: 18pt;
     159  font-weight: bold;
     160  text-align: center;
     161  margin-top: 36pt;
     162  margin-bottom: 0pt;
     163}
     164h2 {
    150165  font-size: 130%;
    151166  line-height: 21pt;
    152167  page-break-after: avoid;
    153168}
    154 h1.np {
     169h2.np {
    155170  page-break-before: always;
    156171}
    157 h2 {
     172h3 {
    158173  font-size: 120%;
    159174  line-height: 15pt;
    160175  page-break-after: avoid;
    161176}
    162 h3 {
     177h4 {
    163178  font-size: 110%;
    164179  page-break-after: avoid;
    165180}
    166 h4, h5, h6 {
     181h5, h6 {
    167182  page-break-after: avoid;
    168183}
     
    266281  border-width: 2px;
    267282}
    268 table.left {
     283table.tleft {
    269284  margin-right: auto;
    270285}
    271 table.right {
     286table.tright {
    272287  margin-left: auto;
    273288}
    274 table.center {
     289table.tcenter {
    275290  margin-left: auto;
    276291  margin-right: auto;
     
    303318  color: white;
    304319}
    305 td.reference {
    306   vertical-align: top;
    307   white-space: nowrap;
    308   padding-right: 1em;
    309 }
    310320thead {
    311321  display:table-header-group;
     
    333343  margin-left: 0em;
    334344}
    335 .title, .filename, h1, h2, h3, h4 {
     345.filename, h1, h2, h3, h4 {
    336346  font-family: candara, calibri, segoe, optima, arial, sans-serif;
    337347}
     
    381391.filename {
    382392  color: #333333;
    383   font-size: 75%;
     393  font-size: 112%;
    384394  font-weight: bold;
    385395  line-height: 21pt;
    386396  text-align: center;
     397  margin-top: 0pt;
    387398}
    388399.fn {
     
    394405.right {
    395406  text-align: right;
    396 }
    397 .title {
    398   color: green;
    399   font-size: 150%;
    400   line-height: 18pt;
    401   font-weight: bold;
    402   text-align: center;
    403   margin-top: 36pt;
    404407}
    405408.warning {
     
    428431  border: 1px solid silver;
    429432  border-radius: 5px;
     433}
     434.publishedasrfc {
     435  background-color: yellow;
     436  color: green;
     437  font-size: 14pt;
     438  text-align: center;
    430439}
    431440
     
    528537      <link href="p4-conditional.html" rel="prev">
    529538      <link href="p6-cache.html" rel="next">
    530       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.710, 2014/12/09 13:12:18, XSLT vendor: Saxonica http://www.saxonica.com/">
     539      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.756, 2015/12/31 17:59:21, XSLT vendor: Saxonica http://www.saxonica.com/">
    531540      <meta name="keywords" content="Hypertext Transfer Protocol, HTTP, HTTP Range Requests">
    532541      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     
    574583    &nbs