Ignore:
Timestamp:
Jan 19, 2014, 11:43:53 PM (6 years ago)
Author:
julian.reschke@…
Message:

update rfc2617.xml (ABNF alignment was off from published version), regen all HTML

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/orig/rfc2616-symrefs.html

    r1305 r2564  
    22  PUBLIC "-//W3C//DTD HTML 4.01//EN">
    33<html lang="en">
    4    <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
     4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
    55      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    66      <title>Hypertext Transfer Protocol -- HTTP/1.1</title><style type="text/css" title="Xml2Rfc (sans serif)">
     
    2424body {
    2525  color: black;
    26   font-family: verdana, helvetica, arial, sans-serif;
    27   font-size: 10pt;
     26  font-family: cambria, helvetica, arial, sans-serif;
     27  font-size: 11pt;
     28  margin-right: 2em;
    2829}
    2930cite {
    3031  font-style: normal;
    3132}
    32 dd {
    33   margin-right: 2em;
    34 }
    3533dl {
    3634  margin-left: 2em;
    3735}
    38 
    3936ul.empty {
    4037  list-style-type: none;
     
    5047}
    5148h1 {
    52   font-size: 14pt;
     49  font-size: 130%;
    5350  line-height: 21pt;
    5451  page-break-after: avoid;
     
    5754  page-break-before: always;
    5855}
    59 h1 a {
    60   color: #333333;
    61 }
    6256h2 {
    63   font-size: 12pt;
     57  font-size: 120%;
    6458  line-height: 15pt;
    6559  page-break-after: avoid;
    6660}
    67 h3, h4, h5, h6 {
    68   font-size: 10pt;
     61h3 {
     62  font-size: 110%;
    6963  page-break-after: avoid;
    7064}
    71 h2 a, h3 a, h4 a, h5 a, h6 a {
     65h4, h5, h6 {
     66  page-break-after: avoid;
     67}
     68h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    7269  color: black;
    7370}
     
    7774li {
    7875  margin-left: 2em;
    79   margin-right: 2em;
    8076}
    8177ol {
    8278  margin-left: 2em;
    83   margin-right: 2em;
    8479}
    8580ol.la {
     
    9489p {
    9590  margin-left: 2em;
    96   margin-right: 2em;
    9791}
    9892pre {
     
    10094  background-color: lightyellow;
    10195  padding: .25em;
     96  page-break-inside: avoid;
    10297}
    10398pre.text2 {
     
    129124  border-spacing: 1px;
    130125  width: 95%;
    131   font-size: 10pt;
     126  font-size: 11pt;
    132127  color: white;
    133128}
     
    137132td.topnowrap {
    138133  vertical-align: top;
    139   white-space: nowrap; 
     134  white-space: nowrap;
    140135}
    141136table.header td {
     
    157152  list-style: none;
    158153  margin-left: 1.5em;
    159   margin-right: 0em;
    160154  padding-left: 0em;
    161155}
     
    163157  line-height: 150%;
    164158  font-weight: bold;
    165   font-size: 10pt;
    166159  margin-left: 0em;
    167   margin-right: 0em;
    168160}
    169161ul.toc li li {
    170162  line-height: normal;
    171163  font-weight: normal;
    172   font-size: 9pt;
     164  font-size: 10pt;
    173165  margin-left: 0em;
    174   margin-right: 0em;
    175166}
    176167li.excluded {
     
    180171  margin-left: 0em;
    181172}
     173.title, .filename, h1, h2, h3, h4 {
     174  font-family: candara, helvetica, arial, sans-serif;
     175}
     176samp, tt, code, pre {
     177  font: consolas, monospace;
     178}
    182179ul.ind, ul.ind ul {
    183180  list-style: none;
    184181  margin-left: 1.5em;
    185   margin-right: 0em;
    186182  padding-left: 0em;
    187183  page-break-before: avoid;
     
    191187  line-height: 200%;
    192188  margin-left: 0em;
    193   margin-right: 0em;
    194189}
    195190ul.ind li li {
     
    197192  line-height: 150%;
    198193  margin-left: 0em;
    199   margin-right: 0em;
    200194}
    201195.avoidbreak {
     
    221215  font-weight: bold;
    222216  text-align: center;
    223   font-size: 9pt;
     217  font-size: 10pt;
    224218}
    225219.filename {
    226220  color: #333333;
     221  font-size: 75%;
    227222  font-weight: bold;
    228   font-size: 12pt;
    229223  line-height: 21pt;
    230224  text-align: center;
     
    232226.fn {
    233227  font-weight: bold;
    234 }
    235 .hidden {
    236   display: none;
    237228}
    238229.left {
     
    243234}
    244235.title {
    245   color: #990000;
    246   font-size: 18pt;
     236  color: green;
     237  font-size: 150%;
    247238  line-height: 18pt;
    248239  font-weight: bold;
     
    250241  margin-top: 36pt;
    251242}
    252 .vcardline {
    253   display: block;
    254 }
    255243.warning {
    256   font-size: 14pt;
     244  font-size: 130%;
    257245  background-color: yellow;
    258246}
     
    263251    display: none;
    264252  }
    265  
     253
    266254  a {
    267255    color: black;
     
    278266    background-color: white;
    279267    vertical-align: top;
    280     font-size: 12pt;
     268    font-size: 110%;
    281269  }
    282270
    283   ul.toc a::after {
     271  ul.toc a:nth-child(2)::after {
    284272    content: leader('.') target-counter(attr(href), page);
    285273  }
    286  
     274
    287275  ul.ind li li a {
    288276    content: target-counter(attr(href), page);
    289277  }
    290  
     278
    291279  .print2col {
    292280    column-count: 2;
     
    298286@page {
    299287  @top-left {
    300        content: "Internet-Draft"; 
    301   } 
     288       content: "Internet-Draft";
     289  }
    302290  @top-right {
    303        content: "June 1999"; 
    304   } 
     291       content: "June 1999";
     292  }
    305293  @top-center {
    306        content: "HTTP/1.1"; 
    307   } 
     294       content: "HTTP/1.1";
     295  }
    308296  @bottom-left {
    309        content: "Fielding, et al."; 
    310   } 
     297       content: "Fielding, et al.";
     298  }
    311299  @bottom-center {
    312        content: "Expires December 1999"; 
    313   } 
     300       content: "Expires December 1999";
     301  }
    314302  @bottom-right {
    315        content: "[Page " counter(page) "]"; 
    316   } 
     303       content: "[Page " counter(page) "]";
     304  }
    317305}
    318306
    319 @page:first { 
     307@page:first {
    320308    @top-left {
    321309      content: normal;
     
    351339      <link rel="Appendix" title="19 Appendices" href="#rfc.section.19">
    352340      <link rel="Appendix" title="20 Index" href="#rfc.section.20">
    353       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.550, 2011-05-30 14:02:12, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     341      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.611, 2013/11/27 12:23:51, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    354342      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    355343      <meta name="dct.creator" content="Fielding, R.">
     
    433421      </table>
    434422      <p class="title">Hypertext Transfer Protocol -- HTTP/1.1<br><span class="filename">rfc2616-symrefs</span></p>
    435       <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    436       <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
    437          is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
    438          6 of BCP 79.
    439       </p>
    440       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
    441          that other groups may also distribute working documents as Internet-Drafts.
    442       </p>
    443       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    444          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    445          in progress”.
    446       </p>
    447       <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
    448       </p>
    449       <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
    450       </p>
    451       <p>This Internet-Draft will expire in December 1999.</p>
    452       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    453       <p>Copyright © The Internet Society (1999). All Rights Reserved.</p>
    454       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
     423      <div id="rfc.status">
     424         <h1><a href="#rfc.status">Status of this Memo</a></h1>
     425         <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
     426            is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
     427            6 of BCP 79.
     428         </p>
     429         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
     430            that other groups may also distribute working documents as Internet-Drafts.
     431         </p>
     432         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     433            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     434            in progress”.
     435         </p>
     436         <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
     437         </p>
     438         <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
     439         </p>
     440         <p>This Internet-Draft will expire in December 1999.</p>
     441      </div>
     442      <div id="rfc.copyrightnotice">
     443         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     444         <p>Copyright © The Internet Society (1999). All Rights Reserved.</p>
     445      </div>
     446      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    455447      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    456448         systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name
    457449         servers and distributed object management systems, through extension of its request methods, error codes and headers <a href="#RFC2324" id="rfc.xref.RFC2324.1"><cite title="Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)">[RFC2324]</cite></a>. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the
    458450         data being transferred.
    459       </p> 
     451      </p>
    460452      <p>HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol
    461453         referred to as "HTTP/1.1", and is an update to RFC 2068 <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
    462       </p> 
    463       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
     454      </p>
     455      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    464456      <p>This version of the HTTP specification contains only XML processing changes from [RFC2616] in internet-draft form for use
    465457         in creating diffs.
    466       </p> 
     458      </p>
    467459      <hr class="noprint">
    468460      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    469461      <ul class="toc">
    470          <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
    471                <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.purpose">Purpose</a></li>
    472                <li>1.2&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    473                <li>1.3&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
    474                <li>1.4&nbsp;&nbsp;&nbsp;<a href="#intro.overall.operation">Overall Operation</a></li>
     462         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     463               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.purpose">Purpose</a></li>
     464               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     465               <li><a href="#rfc.section.1.3">1.3</a>&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
     466               <li><a href="#rfc.section.1.4">1.4</a>&nbsp;&nbsp;&nbsp;<a href="#intro.overall.operation">Overall Operation</a></li>
    475467            </ul>
    476468         </li>
    477          <li>2.&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a><ul>
    478                <li>2.1&nbsp;&nbsp;&nbsp;<a href="#notation.abnf">Augmented BNF</a></li>
    479                <li>2.2&nbsp;&nbsp;&nbsp;<a href="#basic.rules">Basic Rules</a></li>
     469         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a><ul>
     470               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#notation.abnf">Augmented BNF</a></li>
     471               <li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#basic.rules">Basic Rules</a></li>
    480472            </ul>
    481473         </li>
    482          <li>3.&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
    483                <li>3.1&nbsp;&nbsp;&nbsp;<a href="#http.version">HTTP Version</a></li>
    484                <li>3.2&nbsp;&nbsp;&nbsp;<a href="#uri">Uniform Resource Identifiers</a><ul>
    485                      <li>3.2.1&nbsp;&nbsp;&nbsp;<a href="#general.syntax">General Syntax</a></li>
    486                      <li>3.2.2&nbsp;&nbsp;&nbsp;<a href="#http.url">http URL</a></li>
    487                      <li>3.2.3&nbsp;&nbsp;&nbsp;<a href="#uri.comparison">URI Comparison</a></li>
     474         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul>
     475               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#http.version">HTTP Version</a></li>
     476               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#uri">Uniform Resource Identifiers</a><ul>
     477                     <li><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#general.syntax">General Syntax</a></li>
     478                     <li><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#http.url">http URL</a></li>
     479                     <li><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#uri.comparison">URI Comparison</a></li>
    488480                  </ul>
    489481               </li>
    490                <li>3.3&nbsp;&nbsp;&nbsp;<a href="#date.time.formats">Date/Time Formats</a><ul>
    491                      <li>3.3.1&nbsp;&nbsp;&nbsp;<a href="#full.date">Full Date</a></li>
    492                      <li>3.3.2&nbsp;&nbsp;&nbsp;<a href="#delta.seconds">Delta Seconds</a></li>
     482               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#date.time.formats">Date/Time Formats</a><ul>
     483                     <li><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#full.date">Full Date</a></li>
     484                     <li><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#delta.seconds">Delta Seconds</a></li>
    493485                  </ul>
    494486               </li>
    495                <li>3.4&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Sets</a><ul>
    496                      <li>3.4.1&nbsp;&nbsp;&nbsp;<a href="#missing.charset">Missing Charset</a></li>
     487               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#character.sets">Character Sets</a><ul>
     488                     <li><a href="#rfc.section.3.4.1">3.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#missing.charset">Missing Charset</a></li>
    497489                  </ul>
    498490               </li>
    499                <li>3.5&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a></li>
    500                <li>3.6&nbsp;&nbsp;&nbsp;<a href="#transfer.codings">Transfer Codings</a><ul>
    501                      <li>3.6.1&nbsp;&nbsp;&nbsp;<a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li>
     491               <li><a href="#rfc.section.3.5">3.5</a>&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a></li>
     492               <li><a href="#rfc.section.3.6">3.6</a>&nbsp;&nbsp;&nbsp;<a href="#transfer.codings">Transfer Codings</a><ul>
     493                     <li><a href="#rfc.section.3.6.1">3.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li>
    502494                  </ul>
    503495               </li>
    504                <li>3.7&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
    505                      <li>3.7.1&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
    506                      <li>3.7.2&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
     496               <li><a href="#rfc.section.3.7">3.7</a>&nbsp;&nbsp;&nbsp;<a href="#media.types">Media Types</a><ul>
     497                     <li><a href="#rfc.section.3.7.1">3.7.1</a>&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
     498                     <li><a href="#rfc.section.3.7.2">3.7.2</a>&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
    507499                  </ul>
    508500               </li>
    509                <li>3.8&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
    510                <li>3.9&nbsp;&nbsp;&nbsp;<a href="#quality.values">Quality Values</a></li>
    511                <li>3.10&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
    512                <li>3.11&nbsp;&nbsp;&nbsp;<a href="#entity.tags">Entity Tags</a></li>
    513                <li>3.12&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
     501               <li><a href="#rfc.section.3.8">3.8</a>&nbsp;&nbsp;&nbsp;<a href="#product.tokens">Product Tokens</a></li>
     502               <li><a href="#rfc.section.3.9">3.9</a>&nbsp;&nbsp;&nbsp;<a href="#quality.values">Quality Values</a></li>
     503               <li><a href="#rfc.section.3.10">3.10</a>&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
     504               <li><a href="#rfc.section.3.11">3.11</a>&nbsp;&nbsp;&nbsp;<a href="#entity.tags">Entity Tags</a></li>
     505               <li><a href="#rfc.section.3.12">3.12</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
    514506            </ul>
    515507         </li>
    516          <li>4.&nbsp;&nbsp;&nbsp;<a href="#http.message">HTTP Message</a><ul>
    517                <li>4.1&nbsp;&nbsp;&nbsp;<a href="#message.types">Message Types</a></li>
    518                <li>4.2&nbsp;&nbsp;&nbsp;<a href="#message.headers">Message Headers</a></li>
    519                <li>4.3&nbsp;&nbsp;&nbsp;<a href="#message.body">Message Body</a></li>
    520                <li>4.4&nbsp;&nbsp;&nbsp;<a href="#message.length">Message Length</a></li>
    521                <li>4.5&nbsp;&nbsp;&nbsp;<a href="#general.header.fields">General Header Fields</a></li>
     508         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#http.message">HTTP Message</a><ul>
     509               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#message.types">Message Types</a></li>
     510               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#message.headers">Message Headers</a></li>
     511               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#message.body">Message Body</a></li>
     512               <li><a href="#rfc.section.4.4">4.4</a>&nbsp;&nbsp;&nbsp;<a href="#message.length">Message Length</a></li>
     513               <li><a href="#rfc.section.4.5">4.5</a>&nbsp;&nbsp;&nbsp;<a href="#general.header.fields">General Header Fields</a></li>
    522514            </ul>
    523515         </li>
    524          <li>5.&nbsp;&nbsp;&nbsp;<a href="#request">Request</a><ul>
    525                <li>5.1&nbsp;&nbsp;&nbsp;<a href="#request-line">Request-Line</a><ul>
    526                      <li>5.1.1&nbsp;&nbsp;&nbsp;<a href="#method">Method</a></li>
    527                      <li>5.1.2&nbsp;&nbsp;&nbsp;<a href="#request-uri">Request-URI</a></li>
     516         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#request">Request</a><ul>
     517               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#request-line">Request-Line</a><ul>
     518                     <li><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#method">Method</a></li>
     519                     <li><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#request-uri">Request-URI</a></li>
    528520                  </ul>
    529521               </li>
    530                <li>5.2&nbsp;&nbsp;&nbsp;<a href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></li>
    531                <li>5.3&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
     522               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></li>
     523               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
    532524            </ul>
    533525         </li>
    534          <li>6.&nbsp;&nbsp;&nbsp;<a href="#response">Response</a><ul>
    535                <li>6.1&nbsp;&nbsp;&nbsp;<a href="#status-line">Status-Line</a><ul>
    536                      <li>6.1.1&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li>
     526         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#response">Response</a><ul>
     527               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status-line">Status-Line</a><ul>
     528                     <li><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li>
    537529                  </ul>
    538530               </li>
    539                <li>6.2&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
     531               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
    540532            </ul>
    541533         </li>
    542          <li>7.&nbsp;&nbsp;&nbsp;<a href="#entity">Entity</a><ul>
    543                <li>7.1&nbsp;&nbsp;&nbsp;<a href="#entity.header.fields">Entity Header Fields</a></li>
    544                <li>7.2&nbsp;&nbsp;&nbsp;<a href="#entity.body">Entity Body</a><ul>
    545                      <li>7.2.1&nbsp;&nbsp;&nbsp;<a href="#type">Type</a></li>
    546                      <li>7.2.2&nbsp;&nbsp;&nbsp;<a href="#entity.length">Entity Length</a></li>
     534         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#entity">Entity</a><ul>
     535               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#entity.header.fields">Entity Header Fields</a></li>
     536               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#entity.body">Entity Body</a><ul>
     537                     <li><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#type">Type</a></li>
     538                     <li><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#entity.length">Entity Length</a></li>
    547539                  </ul>
    548540               </li>
    549541            </ul>
    550542         </li>
    551          <li>8.&nbsp;&nbsp;&nbsp;<a href="#connections">Connections</a><ul>
    552                <li>8.1&nbsp;&nbsp;&nbsp;<a href="#persistent.connections">Persistent Connections</a><ul>
    553                      <li>8.1.1&nbsp;&nbsp;&nbsp;<a href="#persistent.purpose">Purpose</a></li>
    554                      <li>8.1.2&nbsp;&nbsp;&nbsp;<a href="#persistent.overall">Overall Operation</a><ul>
    555                            <li>8.1.2.1&nbsp;&nbsp;&nbsp;<a href="#persistent.negotiation">Negotiation</a></li>
    556                            <li>8.1.2.2&nbsp;&nbsp;&nbsp;<a href="#pipelining">Pipelining</a></li>
     543         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#connections">Connections</a><ul>
     544               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.connections">Persistent Connections</a><ul>
     545                     <li><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.purpose">Purpose</a></li>
     546                     <li><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.overall">Overall Operation</a><ul>
     547                           <li><a href="#rfc.section.8.1.2.1">8.1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.negotiation">Negotiation</a></li>
     548                           <li><a href="#rfc.section.8.1.2.2">8.1.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#pipelining">Pipelining</a></li>
    557549                        </ul>
    558550                     </li>
    559                      <li>8.1.3&nbsp;&nbsp;&nbsp;<a href="#persistent.proxy">Proxy Servers</a></li>
    560                      <li>8.1.4&nbsp;&nbsp;&nbsp;<a href="#persistent.practical">Practical Considerations</a></li>
     551                     <li><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.proxy">Proxy Servers</a></li>
     552                     <li><a href="#rfc.section.8.1.4">8.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.practical">Practical Considerations</a></li>
    561553                  </ul>
    562554               </li>
    563                <li>8.2&nbsp;&nbsp;&nbsp;<a href="#message.transmission.requirements">Message Transmission Requirements</a><ul>
    564                      <li>8.2.1&nbsp;&nbsp;&nbsp;<a href="#persistent.flow">Persistent Connections and Flow Control</a></li>
    565                      <li>8.2.2&nbsp;&nbsp;&nbsp;<a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li>
    566                      <li>8.2.3&nbsp;&nbsp;&nbsp;<a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>
    567                      <li>8.2.4&nbsp;&nbsp;&nbsp;<a href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li>
     555               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#message.transmission.requirements">Message Transmission Requirements</a><ul>
     556                     <li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.flow">Persistent Connections and Flow Control</a></li>
     557                     <li><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li>
     558                     <li><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>
     559                     <li><a href="#rfc.section.8.2.4">8.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li>
    568560                  </ul>
    569561               </li>
    570562            </ul>
    571563         </li>
    572          <li>9.&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
    573                <li>9.1&nbsp;&nbsp;&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul>
    574                      <li>9.1.1&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
    575                      <li>9.1.2&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
     564         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
     565               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul>
     566                     <li><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
     567                     <li><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
    576568                  </ul>
    577569               </li>
    578                <li>9.2&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
    579                <li>9.3&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
    580                <li>9.4&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
    581                <li>9.5&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
    582                <li>9.6&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
    583                <li>9.7&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
    584                <li>9.8&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
    585                <li>9.9&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
     570               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
     571               <li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
     572               <li><a href="#rfc.section.9.4">9.4</a>&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
     573               <li><a href="#rfc.section.9.5">9.5</a>&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
     574               <li><a href="#rfc.section.9.6">9.6</a>&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
     575               <li><a href="#rfc.section.9.7">9.7</a>&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
     576               <li><a href="#rfc.section.9.8">9.8</a>&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
     577               <li><a href="#rfc.section.9.9">9.9</a>&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
    586578            </ul>
    587579         </li>
    588          <li>10.&nbsp;&nbsp;&nbsp;<a href="#status.codes">Status Code Definitions</a><ul>
    589                <li>10.1&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
    590                      <li>10.1.1&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
    591                      <li>10.1.2&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
     580         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Status Code Definitions</a><ul>
     581               <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
     582                     <li><a href="#rfc.section.10.1.1">10.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
     583                     <li><a href="#rfc.section.10.1.2">10.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
    592584                  </ul>
    593585               </li>
    594                <li>10.2&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
    595                      <li>10.2.1&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
    596                      <li>10.2.2&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
    597                      <li>10.2.3&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
    598                      <li>10.2.4&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
    599                      <li>10.2.5&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
    600                      <li>10.2.6&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
    601                      <li>10.2.7&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
     586               <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
     587                     <li><a href="#rfc.section.10.2.1">10.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
     588                     <li><a href="#rfc.section.10.2.2">10.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
     589                     <li><a href="#rfc.section.10.2.3">10.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
     590                     <li><a href="#rfc.section.10.2.4">10.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
     591                     <li><a href="#rfc.section.10.2.5">10.2.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
     592                     <li><a href="#rfc.section.10.2.6">10.2.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
     593                     <li><a href="#rfc.section.10.2.7">10.2.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    602594                  </ul>
    603595               </li>
    604                <li>10.3&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
    605                      <li>10.3.1&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
    606                      <li>10.3.2&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
    607                      <li>10.3.3&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
    608                      <li>10.3.4&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
    609                      <li>10.3.5&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
    610                      <li>10.3.6&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
    611                      <li>10.3.7&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
    612                      <li>10.3.8&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
     596               <li><a href="#rfc.section.10.3">10.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
     597                     <li><a href="#rfc.section.10.3.1">10.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
     598                     <li><a href="#rfc.section.10.3.2">10.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
     599                     <li><a href="#rfc.section.10.3.3">10.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
     600                     <li><a href="#rfc.section.10.3.4">10.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
     601                     <li><a href="#rfc.section.10.3.5">10.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
     602                     <li><a href="#rfc.section.10.3.6">10.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
     603                     <li><a href="#rfc.section.10.3.7">10.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
     604                     <li><a href="#rfc.section.10.3.8">10.3.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
    613605                  </ul>
    614606               </li>
    615                <li>10.4&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
    616                      <li>10.4.1&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
    617                      <li>10.4.2&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
    618                      <li>10.4.3&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
    619                      <li>10.4.4&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
    620                      <li>10.4.5&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
    621                      <li>10.4.6&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
    622                      <li>10.4.7&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
    623                      <li>10.4.8&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
    624                      <li>10.4.9&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
    625                      <li>10.4.10&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
    626                      <li>10.4.11&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
    627                      <li>10.4.12&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
    628                      <li>10.4.13&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
    629                      <li>10.4.14&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Entity Too Large</a></li>
    630                      <li>10.4.15&nbsp;&nbsp;&nbsp;<a href="#status.414">414 Request-URI Too Long</a></li>
    631                      <li>10.4.16&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
    632                      <li>10.4.17&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
    633                      <li>10.4.18&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
     607               <li><a href="#rfc.section.10.4">10.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
     608                     <li><a href="#rfc.section.10.4.1">10.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
     609                     <li><a href="#rfc.section.10.4.2">10.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
     610                     <li><a href="#rfc.section.10.4.3">10.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
     611                     <li><a href="#rfc.section.10.4.4">10.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
     612                     <li><a href="#rfc.section.10.4.5">10.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
     613                     <li><a href="#rfc.section.10.4.6">10.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
     614                     <li><a href="#rfc.section.10.4.7">10.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
     615                     <li><a href="#rfc.section.10.4.8">10.4.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
     616                     <li><a href="#rfc.section.10.4.9">10.4.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
     617                     <li><a href="#rfc.section.10.4.10">10.4.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
     618                     <li><a href="#rfc.section.10.4.11">10.4.11</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
     619                     <li><a href="#rfc.section.10.4.12">10.4.12</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
     620                     <li><a href="#rfc.section.10.4.13">10.4.13</a>&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
     621                     <li><a href="#rfc.section.10.4.14">10.4.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Entity Too Large</a></li>
     622                     <li><a href="#rfc.section.10.4.15">10.4.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.414">414 Request-URI Too Long</a></li>
     623                     <li><a href="#rfc.section.10.4.16">10.4.16</a>&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
     624                     <li><a href="#rfc.section.10.4.17">10.4.17</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
     625                     <li><a href="#rfc.section.10.4.18">10.4.18</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
    634626                  </ul>
    635627               </li>
    636                <li>10.5&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
    637                      <li>10.5.1&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
    638                      <li>10.5.2&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
    639                      <li>10.5.3&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
    640                      <li>10.5.4&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
    641                      <li>10.5.5&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
    642                      <li>10.5.6&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
     628               <li><a href="#rfc.section.10.5">10.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
     629                     <li><a href="#rfc.section.10.5.1">10.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
     630                     <li><a href="#rfc.section.10.5.2">10.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
     631                     <li><a href="#rfc.section.10.5.3">10.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
     632                     <li><a href="#rfc.section.10.5.4">10.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
     633                     <li><a href="#rfc.section.10.5.5">10.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
     634                     <li><a href="#rfc.section.10.5.6">10.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
    643635                  </ul>
    644636               </li>
    645637            </ul>
    646638         </li>
    647          <li>11.&nbsp;&nbsp;&nbsp;<a href="#access.authentication">Access Authentication</a></li>
    648          <li>12.&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
    649                <li>12.1&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
    650                <li>12.2&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
    651                <li>12.3&nbsp;&nbsp;&nbsp;<a href="#transparent.negotiation">Transparent Negotiation</a></li>
     639         <li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#access.authentication">Access Authentication</a></li>
     640         <li><a href="#rfc.section.12">12.</a>&nbsp;&nbsp;&nbsp;<a href="#content.negotiation">Content Negotiation</a><ul>
     641               <li><a href="#rfc.section.12.1">12.1</a>&nbsp;&nbsp;&nbsp;<a href="#server-driven.negotiation">Server-driven Negotiation</a></li>
     642               <li><a href="#rfc.section.12.2">12.2</a>&nbsp;&nbsp;&nbsp;<a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>
     643               <li><a href="#rfc.section.12.3">12.3</a>&nbsp;&nbsp;&nbsp;<a href="#transparent.negotiation">Transparent Negotiation</a></li>
    652644            </ul>
    653645         </li>
    654          <li>13.&nbsp;&nbsp;&nbsp;<a href="#caching">Caching in HTTP</a><ul>
    655                <li>13.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.1"></a><ul>
    656                      <li>13.1.1&nbsp;&nbsp;&nbsp;<a href="#cache.correctness">Cache Correctness</a></li>
    657                      <li>13.1.2&nbsp;&nbsp;&nbsp;<a href="#warnings">Warnings</a></li>
    658                      <li>13.1.3&nbsp;&nbsp;&nbsp;<a href="#cache-control.mechanisms">Cache-control Mechanisms</a></li>
    659                      <li>13.1.4&nbsp;&nbsp;&nbsp;<a href="#explicit.ua.warnings">Explicit User Agent Warnings</a></li>
    660                      <li>13.1.5&nbsp;&nbsp;&nbsp;<a href="#exceptions.to.the.rules.and.warnings">Exceptions to the Rules and Warnings</a></li>
    661                      <li>13.1.6&nbsp;&nbsp;&nbsp;<a href="#client-controlled.behavior">Client-controlled Behavior</a></li>
     646         <li><a href="#rfc.section.13">13.</a>&nbsp;&nbsp;&nbsp;<a href="#caching">Caching in HTTP</a><ul>
     647               <li><a href="#rfc.section.13.1">13.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.13.1"></a><ul>
     648                     <li><a href="#rfc.section.13.1.1">13.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache.correctness">Cache Correctness</a></li>
     649                     <li><a href="#rfc.section.13.1.2">13.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#warnings">Warnings</a></li>
     650                     <li><a href="#rfc.section.13.1.3">13.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache-control.mechanisms">Cache-control Mechanisms</a></li>
     651                     <li><a href="#rfc.section.13.1.4">13.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#explicit.ua.warnings">Explicit User Agent Warnings</a></li>
     652                     <li><a href="#rfc.section.13.1.5">13.1.5</a>&nbsp;&nbsp;&nbsp;<a href="#exceptions.to.the.rules.and.warnings">Exceptions to the Rules and Warnings</a></li>
     653                     <li><a href="#rfc.section.13.1.6">13.1.6</a>&nbsp;&nbsp;&nbsp;<a href="#client-controlled.behavior">Client-controlled Behavior</a></li>
    662654                  </ul>
    663655               </li>
    664                <li>13.2&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Expiration Model</a><ul>
    665                      <li>13.2.1&nbsp;&nbsp;&nbsp;<a href="#server-specified.expiration">Server-Specified Expiration</a></li>
    666                      <li>13.2.2&nbsp;&nbsp;&nbsp;<a href="#heuristic.expiration">Heuristic Expiration</a></li>
    667                      <li>13.2.3&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Age Calculations</a></li>
    668                      <li>13.2.4&nbsp;&nbsp;&nbsp;<a href="#expiration.calculations">Expiration Calculations</a></li>
    669                      <li>13.2.5&nbsp;&nbsp;&nbsp;<a href="#disambiguating.expiration.values">Disambiguating Expiration Values</a></li>
    670                      <li>13.2.6&nbsp;&nbsp;&nbsp;<a href="#disambiguating.multiple.responses">Disambiguating Multiple Responses</a></li>
     656               <li><a href="#rfc.section.13.2">13.2</a>&nbsp;&nbsp;&nbsp;<a href="#expiration.model">Expiration Model</a><ul>
     657                     <li><a href="#rfc.section.13.2.1">13.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#server-specified.expiration">Server-Specified Expiration</a></li>
     658                     <li><a href="#rfc.section.13.2.2">13.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#heuristic.expiration">Heuristic Expiration</a></li>
     659                     <li><a href="#rfc.section.13.2.3">13.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#age.calculations">Age Calculations</a></li>
     660                     <li><a href="#rfc.section.13.2.4">13.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#expiration.calculations">Expiration Calculations</a></li>
     661                     <li><a href="#rfc.section.13.2.5">13.2.5</a>&nbsp;&nbsp;&nbsp;<a href="#disambiguating.expiration.values">Disambiguating Expiration Values</a></li>
     662                     <li><a href="#rfc.section.13.2.6">13.2.6</a>&nbsp;&nbsp;&nbsp;<a href="#disambiguating.multiple.responses">Disambiguating Multiple Responses</a></li>
    671663                  </ul>
    672664               </li>
    673                <li>13.3&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation Model</a><ul>
    674                      <li>13.3.1&nbsp;&nbsp;&nbsp;<a href="#last-modified.dates">Last-Modified Dates</a></li>
    675                      <li>13.3.2&nbsp;&nbsp;&nbsp;<a href="#entity.tag.cache.validators">Entity Tag Cache Validators</a></li>
    676                      <li>13.3.3&nbsp;&nbsp;&nbsp;<a href="#weak.and.strong.validators">Weak and Strong Validators</a></li>
    677                      <li>13.3.4&nbsp;&nbsp;&nbsp;<a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates">Rules for When to Use Entity Tags and Last-Modified Dates</a></li>
    678                      <li>13.3.5&nbsp;&nbsp;&nbsp;<a href="#non-validating.conditionals">Non-validating Conditionals</a></li>
     665               <li><a href="#rfc.section.13.3">13.3</a>&nbsp;&nbsp;&nbsp;<a href="#validation.model">Validation Model</a><ul>
     666                     <li><a href="#rfc.section.13.3.1">13.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#last-modified.dates">Last-Modified Dates</a></li>
     667                     <li><a href="#rfc.section.13.3.2">13.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#entity.tag.cache.validators">Entity Tag Cache Validators</a></li>
     668                     <li><a href="#rfc.section.13.3.3">13.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#weak.and.strong.validators">Weak and Strong Validators</a></li>
     669                     <li><a href="#rfc.section.13.3.4">13.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates">Rules for When to Use Entity Tags and Last-Modified Dates</a></li>
     670                     <li><a href="#rfc.section.13.3.5">13.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#non-validating.conditionals">Non-validating Conditionals</a></li>
    679671                  </ul>
    680672               </li>
    681                <li>13.4&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Response Cacheability</a></li>
    682                <li>13.5&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses From Caches</a><ul>
    683                      <li>13.5.1&nbsp;&nbsp;&nbsp;<a href="#end-to-end.and.hop-by-hop.headers">End-to-end and Hop-by-hop Headers</a></li>
    684                      <li>13.5.2&nbsp;&nbsp;&nbsp;<a href="#non-modifiable.headers">Non-modifiable Headers</a></li>
    685                      <li>13.5.3&nbsp;&nbsp;&nbsp;<a href="#combining.headers">Combining Headers</a></li>
    686                      <li>13.5.4&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Byte Ranges</a></li>
     673               <li><a href="#rfc.section.13.4">13.4</a>&nbsp;&nbsp;&nbsp;<a href="#response.cacheability">Response Cacheability</a></li>
     674               <li><a href="#rfc.section.13.5">13.5</a>&nbsp;&nbsp;&nbsp;<a href="#constructing.responses.from.caches">Constructing Responses From Caches</a><ul>
     675                     <li><a href="#rfc.section.13.5.1">13.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#end-to-end.and.hop-by-hop.headers">End-to-end and Hop-by-hop Headers</a></li>
     676                     <li><a href="#rfc.section.13.5.2">13.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#non-modifiable.headers">Non-modifiable Headers</a></li>
     677                     <li><a href="#rfc.section.13.5.3">13.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#combining.headers">Combining Headers</a></li>
     678                     <li><a href="#rfc.section.13.5.4">13.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#combining.byte.ranges">Combining Byte Ranges</a></li>
    687679                  </ul>
    688680               </li>
    689                <li>13.6&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
    690                <li>13.7&nbsp;&nbsp;&nbsp;<a href="#shared.and.non-shared.caches">Shared and Non-Shared Caches</a></li>
    691                <li>13.8&nbsp;&nbsp;&nbsp;<a href="#errors.or.incomplete.response.cache.behavior">Errors or Incomplete Response Cache Behavior</a></li>
    692                <li>13.9&nbsp;&nbsp;&nbsp;<a href="#side.effects.of.get.and.head">Side Effects of GET and HEAD</a></li>
    693                <li>13.10&nbsp;&nbsp;&nbsp;<a href="#invalidation.after.updates.or.deletions">Invalidation After Updates or Deletions</a></li>
    694                <li>13.11&nbsp;&nbsp;&nbsp;<a href="#write-through.mandatory">Write-Through Mandatory</a></li>
    695                <li>13.12&nbsp;&nbsp;&nbsp;<a href="#cache.replacement">Cache Replacement</a></li>
    696                <li>13.13&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
     681               <li><a href="#rfc.section.13.6">13.6</a>&nbsp;&nbsp;&nbsp;<a href="#caching.negotiated.responses">Caching Negotiated Responses</a></li>
     682               <li><a href="#rfc.section.13.7">13.7</a>&nbsp;&nbsp;&nbsp;<a href="#shared.and.non-shared.caches">Shared and Non-Shared Caches</a></li>
     683               <li><a href="#rfc.section.13.8">13.8</a>&nbsp;&nbsp;&nbsp;<a href="#errors.or.incomplete.response.cache.behavior">Errors or Incomplete Response Cache Behavior</a></li>
     684               <li><a href="#rfc.section.13.9">13.9</a>&nbsp;&nbsp;&nbsp;<a href="#side.effects.of.get.and.head">Side Effects of GET and HEAD</a></li>
     685               <li><a href="#rfc.section.13.10">13.10</a>&nbsp;&nbsp;&nbsp;<a href="#invalidation.after.updates.or.deletions">Invalidation After Updates or Deletions</a></li>
     686               <li><a href="#rfc.section.13.11">13.11</a>&nbsp;&nbsp;&nbsp;<a href="#write-through.mandatory">Write-Through Mandatory</a></li>
     687               <li><a href="#rfc.section.13.12">13.12</a>&nbsp;&nbsp;&nbsp;<a href="#cache.replacement">Cache Replacement</a></li>
     688               <li><a href="#rfc.section.13.13">13.13</a>&nbsp;&nbsp;&nbsp;<a href="#history.lists">History Lists</a></li>
    697689            </ul>
    698690         </li>
    699          <li>14.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
    700                <li>14.1&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
    701                <li>14.2&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
    702                <li>14.3&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
    703                <li>14.4&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
    704                <li>14.5&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
    705                <li>14.6&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
    706                <li>14.7&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
    707                <li>14.8&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
    708                <li>14.9&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
    709                      <li>14.9.1&nbsp;&nbsp;&nbsp;<a href="#what.is.cacheable">What is Cacheable</a></li>
    710                      <li>14.9.2&nbsp;&nbsp;&nbsp;<a href="#what.may.be.stored.by.caches">What May be Stored by Caches</a></li>
    711                      <li>14.9.3&nbsp;&nbsp;&nbsp;<a href="#modifications.of.the.basic.expiration.mechanism">Modifications of the Basic Expiration Mechanism</a></li>
    712                      <li>14.9.4&nbsp;&nbsp;&nbsp;<a href="#cache.revalidation.and.reload.controls">Cache Revalidation and Reload Controls</a></li>
    713                      <li>14.9.5&nbsp;&nbsp;&nbsp;<a href="#no-transform.directive">No-Transform Directive</a></li>
    714                      <li>14.9.6&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
     691         <li><a href="#rfc.section.14">14.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     692               <li><a href="#rfc.section.14.1">14.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept">Accept</a></li>
     693               <li><a href="#rfc.section.14.2">14.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-charset">Accept-Charset</a></li>
     694               <li><a href="#rfc.section.14.3">14.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-encoding">Accept-Encoding</a></li>
     695               <li><a href="#rfc.section.14.4">14.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-language">Accept-Language</a></li>
     696               <li><a href="#rfc.section.14.5">14.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.accept-ranges">Accept-Ranges</a></li>
     697               <li><a href="#rfc.section.14.6">14.6</a>&nbsp;&nbsp;&nbsp;<a href="#header.age">Age</a></li>
     698               <li><a href="#rfc.section.14.7">14.7</a>&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
     699               <li><a href="#rfc.section.14.8">14.8</a>&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
     700               <li><a href="#rfc.section.14.9">14.9</a>&nbsp;&nbsp;&nbsp;<a href="#header.cache-control">Cache-Control</a><ul>
     701                     <li><a href="#rfc.section.14.9.1">14.9.1</a>&nbsp;&nbsp;&nbsp;<a href="#what.is.cacheable">What is Cacheable</a></li>
     702                     <li><a href="#rfc.section.14.9.2">14.9.2</a>&nbsp;&nbsp;&nbsp;<a href="#what.may.be.stored.by.caches">What May be Stored by Caches</a></li>
     703                     <li><a href="#rfc.section.14.9.3">14.9.3</a>&nbsp;&nbsp;&nbsp;<a href="#modifications.of.the.basic.expiration.mechanism">Modifications of the Basic Expiration Mechanism</a></li>
     704                     <li><a href="#rfc.section.14.9.4">14.9.4</a>&nbsp;&nbsp;&nbsp;<a href="#cache.revalidation.and.reload.controls">Cache Revalidation and Reload Controls</a></li>
     705                     <li><a href="#rfc.section.14.9.5">14.9.5</a>&nbsp;&nbsp;&nbsp;<a href="#no-transform.directive">No-Transform Directive</a></li>
     706                     <li><a href="#rfc.section.14.9.6">14.9.6</a>&nbsp;&nbsp;&nbsp;<a href="#cache.control.extensions">Cache Control Extensions</a></li>
    715707                  </ul>
    716708               </li>
    717                <li>14.10&nbsp;&nbsp;&nbsp;<a href="#header.connection">Connection</a></li>
    718                <li>14.11&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
    719                <li>14.12&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
    720                <li>14.13&nbsp;&nbsp;&nbsp;<a href="#header.content-length">Content-Length</a></li>
    721                <li>14.14&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
    722                <li>14.15&nbsp;&nbsp;&nbsp;<a href="#header.content-md5">Content-MD5</a></li>
    723                <li>14.16&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
    724                <li>14.17&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
    725                <li>14.18&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a><ul>
    726                      <li>14.18.1&nbsp;&nbsp;&nbsp;<a href="#clockless.origin.server.operation">Clockless Origin Server Operation</a></li>
     709               <li><a href="#rfc.section.14.10">14.10</a>&nbsp;&nbsp;&nbsp;<a href="#header.connection">Connection</a></li>
     710               <li><a href="#rfc.section.14.11">14.11</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
     711               <li><a href="#rfc.section.14.12">14.12</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
     712               <li><a href="#rfc.section.14.13">14.13</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-length">Content-Length</a></li>
     713               <li><a href="#rfc.section.14.14">14.14</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
     714               <li><a href="#rfc.section.14.15">14.15</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-md5">Content-MD5</a></li>
     715               <li><a href="#rfc.section.14.16">14.16</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-range">Content-Range</a></li>
     716               <li><a href="#rfc.section.14.17">14.17</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
     717               <li><a href="#rfc.section.14.18">14.18</a>&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a><ul>
     718                     <li><a href="#rfc.section.14.18.1">14.18.1</a>&nbsp;&nbsp;&nbsp;<a href="#clockless.origin.server.operation">Clockless Origin Server Operation</a></li>
    727719                  </ul>
    728720               </li>
    729                <li>14.19&nbsp;&nbsp;&nbsp;<a href="#header.etag">ETag</a></li>
    730                <li>14.20&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
    731                <li>14.21&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
    732                <li>14.22&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
    733                <li>14.23&nbsp;&nbsp;&nbsp;<a href="#header.host">Host</a></li>
    734                <li>14.24&nbsp;&nbsp;&nbsp;<a href="#header.if-match">If-Match</a></li>
    735                <li>14.25&nbsp;&nbsp;&nbsp;<a href="#header.if-modified-since">If-Modified-Since</a></li>
    736                <li>14.26&nbsp;&nbsp;&nbsp;<a href="#header.if-none-match">If-None-Match</a></li>
    737                <li>14.27&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
    738                <li>14.28&nbsp;&nbsp;&nbsp;<a href="#header.if-unmodified-since">If-Unmodified-Since</a></li>
    739                <li>14.29&nbsp;&nbsp;&nbsp;<a href="#header.last-modified">Last-Modified</a></li>
    740                <li>14.30&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
    741                <li>14.31&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
    742                <li>14.32&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
    743                <li>14.33&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
    744                <li>14.34&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
    745                <li>14.35&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
    746                      <li>14.35.1&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
    747                      <li>14.35.2&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
     721               <li><a href="#rfc.section.14.19">14.19</a>&nbsp;&nbsp;&nbsp;<a href="#header.etag">ETag</a></li>
     722               <li><a href="#rfc.section.14.20">14.20</a>&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
     723               <li><a href="#rfc.section.14.21">14.21</a>&nbsp;&nbsp;&nbsp;<a href="#header.expires">Expires</a></li>
     724               <li><a href="#rfc.section.14.22">14.22</a>&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
     725               <li><a href="#rfc.section.14.23">14.23</a>&nbsp;&nbsp;&nbsp;<a href="#header.host">Host</a></li>
     726               <li><a href="#rfc.section.14.24">14.24</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-match">If-Match</a></li>
     727               <li><a href="#rfc.section.14.25">14.25</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-modified-since">If-Modified-Since</a></li>
     728               <li><a href="#rfc.section.14.26">14.26</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-none-match">If-None-Match</a></li>
     729               <li><a href="#rfc.section.14.27">14.27</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
     730               <li><a href="#rfc.section.14.28">14.28</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-unmodified-since">If-Unmodified-Since</a></li>
     731               <li><a href="#rfc.section.14.29">14.29</a>&nbsp;&nbsp;&nbsp;<a href="#header.last-modified">Last-Modified</a></li>
     732               <li><a href="#rfc.section.14.30">14.30</a>&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
     733               <li><a href="#rfc.section.14.31">14.31</a>&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
     734               <li><a href="#rfc.section.14.32">14.32</a>&nbsp;&nbsp;&nbsp;<a href="#header.pragma">Pragma</a></li>
     735               <li><a href="#rfc.section.14.33">14.33</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
     736               <li><a href="#rfc.section.14.34">14.34</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
     737               <li><a href="#rfc.section.14.35">14.35</a>&nbsp;&nbsp;&nbsp;<a href="#header.range">Range</a><ul>
     738                     <li><a href="#rfc.section.14.35.1">14.35.1</a>&nbsp;&nbsp;&nbsp;<a href="#byte.ranges">Byte Ranges</a></li>
     739                     <li><a href="#rfc.section.14.35.2">14.35.2</a>&nbsp;&nbsp;&nbsp;<a href="#range.retrieval.requests">Range Retrieval Requests</a></li>
    748740                  </ul>
    749741               </li>
    750                <li>14.36&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
    751                <li>14.37&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
    752                <li>14.38&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
    753                <li>14.39&nbsp;&nbsp;&nbsp;<a href="#header.te">TE</a></li>
    754                <li>14.40&nbsp;&nbsp;&nbsp;<a href="#header.trailer">Trailer</a></li>
    755                <li>14.41&nbsp;&nbsp;&nbsp;<a href="#header.transfer-encoding">Transfer-Encoding</a></li>
    756                <li>14.42&nbsp;&nbsp;&nbsp;<a href="#header.upgrade">Upgrade</a></li>
    757                <li>14.43&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
    758                <li>14.44&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
    759                <li>14.45&nbsp;&nbsp;&nbsp;<a href="#header.via">Via</a></li>
    760                <li>14.46&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a></li>
    761                <li>14.47&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
     742               <li><a href="#rfc.section.14.36">14.36</a>&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
     743               <li><a href="#rfc.section.14.37">14.37</a>&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
     744               <li><a href="#rfc.section.14.38">14.38</a>&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
     745               <li><a href="#rfc.section.14.39">14.39</a>&nbsp;&nbsp;&nbsp;<a href="#header.te">TE</a></li>
     746               <li><a href="#rfc.section.14.40">14.40</a>&nbsp;&nbsp;&nbsp;<a href="#header.trailer">Trailer</a></li>
     747               <li><a href="#rfc.section.14.41">14.41</a>&nbsp;&nbsp;&nbsp;<a href="#header.transfer-encoding">Transfer-Encoding</a></li>
     748               <li><a href="#rfc.section.14.42">14.42</a>&nbsp;&nbsp;&nbsp;<a href="#header.upgrade">Upgrade</a></li>
     749               <li><a href="#rfc.section.14.43">14.43</a>&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     750               <li><a href="#rfc.section.14.44">14.44</a>&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
     751               <li><a href="#rfc.section.14.45">14.45</a>&nbsp;&nbsp;&nbsp;<a href="#header.via">Via</a></li>
     752               <li><a href="#rfc.section.14.46">14.46</a>&nbsp;&nbsp;&nbsp;<a href="#header.warning">Warning</a></li>
     753               <li><a href="#rfc.section.14.47">14.47</a>&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
    762754            </ul>
    763755         </li>
    764          <li>15.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
    765                <li>15.1&nbsp;&nbsp;&nbsp;<a href="#personal.information">Personal Information</a><ul>
    766                      <li>15.1.1&nbsp;&nbsp;&nbsp;<a href="#abuse.of.server.log.information">Abuse of Server Log Information</a></li>
    767                      <li>15.1.2&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
    768                      <li>15.1.3&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URI's</a></li>
    769                      <li>15.1.4&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></li>
     756         <li><a href="#rfc.section.15">15.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     757               <li><a href="#rfc.section.15.1">15.1</a>&nbsp;&nbsp;&nbsp;<a href="#personal.information">Personal Information</a><ul>
     758                     <li><a href="#rfc.section.15.1.1">15.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#abuse.of.server.log.information">Abuse of Server Log Information</a></li>
     759                     <li><a href="#rfc.section.15.1.2">15.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
     760                     <li><a href="#rfc.section.15.1.3">15.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URI's</a></li>
     761                     <li><a href="#rfc.section.15.1.4">15.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></li>
    770762                  </ul>
    771763               </li>
    772                <li>15.2&nbsp;&nbsp;&nbsp;<a href="#attack.pathname">Attacks Based On File and Path Names</a></li>
    773                <li>15.3&nbsp;&nbsp;&nbsp;<a href="#dns.spoofing">DNS Spoofing</a></li>
    774                <li>15.4&nbsp;&nbsp;&nbsp;<a href="#location.spoofing">Location Headers and Spoofing</a></li>
    775                <li>15.5&nbsp;&nbsp;&nbsp;<a href="#content-disposition.issues">Content-Disposition Issues</a></li>
    776                <li>15.6&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
    777                <li>15.7&nbsp;&nbsp;&nbsp;<a href="#attack.proxies">Proxies and Caching</a><ul>
    778                      <li>15.7.1&nbsp;&nbsp;&nbsp;<a href="#attack.DoS">Denial of Service Attacks on Proxies</a></li>
     764               <li><a href="#rfc.section.15.2">15.2</a>&nbsp;&nbsp;&nbsp;<a href="#attack.pathname">Attacks Based On File and Path Names</a></li>
     765               <li><a href="#rfc.section.15.3">15.3</a>&nbsp;&nbsp;&nbsp;<a href="#dns.spoofing">DNS Spoofing</a></li>
     766               <li><a href="#rfc.section.15.4">15.4</a>&nbsp;&nbsp;&nbsp;<a href="#location.spoofing">Location Headers and Spoofing</a></li>
     767               <li><a href="#rfc.section.15.5">15.5</a>&nbsp;&nbsp;&nbsp;<a href="#content-disposition.issues">Content-Disposition Issues</a></li>
     768               <li><a href="#rfc.section.15.6">15.6</a>&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
     769               <li><a href="#rfc.section.15.7">15.7</a>&nbsp;&nbsp;&nbsp;<a href="#attack.proxies">Proxies and Caching</a><ul>
     770                     <li><a href="#rfc.section.15.7.1">15.7.1</a>&nbsp;&nbsp;&nbsp;<a href="#attack.DoS">Denial of Service Attacks on Proxies</a></li>
    779771                  </ul>
    780772               </li>
    781773            </ul>
    782774         </li>
    783          <li>16.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    784          <li>17.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
    785          <li>18.&nbsp;&nbsp;&nbsp;<a href="#rfc.authors">Authors' Addresses</a></li>
    786          <li>19.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.19">Appendices</a><ul>
    787                <li>19.1&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.http">Internet Media Type message/http and application/http</a></li>
    788                <li>19.2&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
    789                <li>19.3&nbsp;&nbsp;&nbsp;<a href="#tolerant.applications">Tolerant Applications</a></li>
    790                <li>19.4&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a><ul>
    791                      <li>19.4.1&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
    792                      <li>19.4.2&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
    793                      <li>19.4.3&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
    794                      <li>19.4.4&nbsp;&nbsp;&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>
    795                      <li>19.4.5&nbsp;&nbsp;&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>
    796                      <li>19.4.6&nbsp;&nbsp;&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>
    797                      <li>19.4.7&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
     775         <li><a href="#rfc.section.16">16.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     776         <li><a href="#rfc.section.17">17.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
     777         <li><a href="#rfc.section.18">18.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.authors">Authors' Addresses</a></li>
     778         <li><a href="#rfc.section.19">19.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.19">Appendices</a><ul>
     779               <li><a href="#rfc.section.19.1">19.1</a>&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.http">Internet Media Type message/http and application/http</a></li>
     780               <li><a href="#rfc.section.19.2">19.2</a>&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li>
     781               <li><a href="#rfc.section.19.3">19.3</a>&nbsp;&nbsp;&nbsp;<a href="#tolerant.applications">Tolerant Applications</a></li>
     782               <li><a href="#rfc.section.19.4">19.4</a>&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a><ul>
     783                     <li><a href="#rfc.section.19.4.1">19.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
     784                     <li><a href="#rfc.section.19.4.2">19.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>
     785                     <li><a href="#rfc.section.19.4.3">19.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
     786                     <li><a href="#rfc.section.19.4.4">19.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>
     787                     <li><a href="#rfc.section.19.4.5">19.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>
     788                     <li><a href="#rfc.section.19.4.6">19.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>
     789                     <li><a href="#rfc.section.19.4.7">19.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>
    798790                  </ul>
    799791               </li>
    800                <li>19.5&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a><ul>
    801                      <li>19.5.1&nbsp;&nbsp;&nbsp;<a href="#content-disposition">Content-Disposition</a></li>
     792               <li><a href="#rfc.section.19.5">19.5</a>&nbsp;&nbsp;&nbsp;<a href="#additional.features">Additional Features</a><ul>
     793                     <li><a href="#rfc.section.19.5.1">19.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#content-disposition">Content-Disposition</a></li>
    802794                  </ul>
    803795               </li>
    804                <li>19.6&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
    805                      <li>19.6.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul>
    806                            <li>19.6.1.1&nbsp;&nbsp;&nbsp;<a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses</a></li>
     796               <li><a href="#rfc.section.19.6">19.6</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
     797                     <li><a href="#rfc.section.19.6.1">19.6.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul>
     798                           <li><a href="#rfc.section.19.6.1.1">19.6.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses</a></li>
    807799                        </ul>
    808800                     </li>
    809                      <li>19.6.2&nbsp;&nbsp;&nbsp;<a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li>
    810                      <li>19.6.3&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
     801                     <li><a href="#rfc.section.19.6.2">19.6.2</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li>
     802                     <li><a href="#rfc.section.19.6.3">19.6.3</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
    811803                  </ul>
    812804               </li>
    813805            </ul>
    814806         </li>
    815          <li>20.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.20">Index</a></li>
     807         <li><a href="#rfc.section.20">20.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.20">Index</a></li>
    816808         <li><a href="#rfc.index">Index</a></li>
    817809         <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    818810      </ul>
    819       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    820       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.purpose" href="#intro.purpose">Purpose</a></h2>
    821       <p id="rfc.section.1.1.p.1">The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    822          systems. HTTP has been in use by the World-Wide Web global information initiative since 1990. The first version of HTTP, referred
    823          to as HTTP/0.9, was a simple protocol for raw data transfer across the Internet. HTTP/1.0, as defined by RFC 1945 <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, improved the protocol by allowing messages to be in the format of MIME-like messages, containing metainformation about the
    824          data transferred and modifiers on the request/response semantics. However, HTTP/1.0 does not sufficiently take into consideration
    825          the effects of hierarchical proxies, caching, the need for persistent connections, or virtual hosts. In addition, the proliferation
    826          of incompletely-implemented applications calling themselves "HTTP/1.0" has necessitated a protocol version change in order
    827          for two communicating applications to determine each other's true capabilities.
    828       </p>
    829       <p id="rfc.section.1.1.p.2">This specification defines the protocol referred to as "HTTP/1.1". This protocol includes more stringent requirements than
    830          HTTP/1.0 in order to ensure reliable implementation of its features.
    831       </p>
    832       <p id="rfc.section.1.1.p.3">Practical information systems require more functionality than simple retrieval, including search, front-end update, and annotation.
    833          HTTP allows an open-ended set of methods and headers that indicate the purpose of a request <a href="#RFC2324" id="rfc.xref.RFC2324.2"><cite title="Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)">[RFC2324]</cite></a>. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) <a href="#RFC1630" id="rfc.xref.RFC1630.1"><cite title="Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web">[RFC1630]</cite></a>, as a location (URL) <a href="#RFC1738" id="rfc.xref.RFC1738.1"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> or name (URN) <a href="#RFC1737" id="rfc.xref.RFC1737.1"><cite title="Functional Requirements for Uniform Resource Names">[RFC1737]</cite></a>, for indicating the resource to which a method is to be applied. Messages are passed in a format similar to that used by
    834          Internet mail <a href="#RFC822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> as defined by the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>.
    835       </p>
    836       <p id="rfc.section.1.1.p.4">HTTP is also used as a generic protocol for communication between user agents and proxies/gateways to other Internet systems,
    837          including those supported by the SMTP <a href="#RFC821" id="rfc.xref.RFC821.1"><cite title="Simple Mail Transfer Protocol">[RFC821]</cite></a>, NNTP <a href="#RFC977" id="rfc.xref.RFC977.1"><cite title="Network News Transfer Protocol">[RFC977]</cite></a>, FTP <a href="#RFC959" id="rfc.xref.RFC959.1"><cite title="File Transfer Protocol">[RFC959]</cite></a>, Gopher <a href="#RFC1436" id="rfc.xref.RFC1436.1"><cite title="The Internet Gopher Protocol (a distributed document search and retrieval protocol)">[RFC1436]</cite></a>, and WAIS <a href="#WAIS" id="rfc.xref.WAIS.1"><cite title="WAIS Interface Protocol Prototype Functional Specification (v1.5)">[WAIS]</cite></a> protocols. In this way, HTTP allows basic hypermedia access to resources available from diverse applications.
    838       </p>
    839       <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    840       <p id="rfc.section.1.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
    841          in this document are to be interpreted as described in RFC 2119 <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    842       </p>
    843       <p id="rfc.section.1.2.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
    844       </p>
    845       <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="intro.terminology" href="#intro.terminology">Terminology</a></h2>
    846       <p id="rfc.section.1.3.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
    847       <p id="rfc.section.1.3.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>connection</dfn> 
    848       </p>
    849       <ul class="empty">
    850          <li>A transport layer virtual circuit established between two programs for the purpose of communication.</li>
    851       </ul>
    852       <p id="rfc.section.1.3.p.3"> <span id="rfc.iref.m.1"></span>  <dfn>message</dfn> 
    853       </p>
    854       <ul class="empty">
    855          <li>The basic unit of HTTP communication, consisting of a structured sequence of octets matching the syntax defined in <a href="#http.message" title="HTTP Message">Section&nbsp;4</a> and transmitted via the connection.
    856          </li>
    857       </ul>
    858       <p id="rfc.section.1.3.p.4"> <span id="rfc.iref.r.1"></span>  <dfn>request</dfn> 
    859       </p>
    860       <ul class="empty">
    861          <li>An HTTP request message, as defined in <a href="#request" title="Request">Section&nbsp;5</a>.
    862          </li>
    863       </ul>
    864       <p id="rfc.section.1.3.p.5"> <span id="rfc.iref.r.2"></span>  <dfn>response</dfn> 
    865       </p>
    866       <ul class="empty">
    867          <li>An HTTP response message, as defined in <a href="#response" title="Response">Section&nbsp;6</a>.
    868          </li>
    869       </ul>
    870       <p id="rfc.section.1.3.p.6"> <span id="rfc.iref.r.3"></span>  <dfn>resource</dfn> 
    871       </p>
    872       <ul class="empty">
    873          <li>A network data object or service that can be identified by a URI, as defined in <a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;3.2</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or
    874             vary in other ways.
    875          </li>
    876       </ul>
    877       <p id="rfc.section.1.3.p.7"> <span id="rfc.iref.e.1"></span>  <dfn>entity</dfn> 
    878       </p>
    879       <ul class="empty">
    880          <li>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of
    881             entity-header fields and content in the form of an entity-body, as described in <a href="#entity" title="Entity">Section&nbsp;7</a>.
    882          </li>
    883       </ul>
    884       <p id="rfc.section.1.3.p.8"> <span id="rfc.iref.r.4"></span>  <dfn>representation</dfn> 
    885       </p>
    886       <ul class="empty">
    887          <li>An entity included with a response that is subject to content negotiation, as described in <a href="#content.negotiation" title="Content Negotiation">Section&nbsp;12</a>. There may exist multiple representations associated with a particular response status.
    888          </li>
    889       </ul>
    890       <p id="rfc.section.1.3.p.9"> <span id="rfc.iref.c.2"></span>  <dfn>content negotiation</dfn> 
    891       </p>
    892       <ul class="empty">
    893          <li>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="#content.negotiation" title="Content Negotiation">Section&nbsp;12</a>. The representation of entities in any response can be negotiated (including error responses).
    894          </li>
    895       </ul>
    896       <p id="rfc.section.1.3.p.10"> <span id="rfc.iref.v.1"></span>  <dfn>variant</dfn> 
    897       </p>
    898       <ul class="empty">
    899          <li>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations
    900             is termed a `varriant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
    901          </li>
    902       </ul>
    903       <p id="rfc.section.1.3.p.11"> <span id="rfc.iref.c.3"></span>  <dfn>client</dfn> 
    904       </p>
    905       <ul class="empty">
    906          <li>A program that establishes connections for the purpose of sending requests.</li>
    907       </ul>
    908       <p id="rfc.section.1.3.p.12"> <span id="rfc.iref.u.1"></span>  <dfn>user agent</dfn> 
    909       </p>
    910       <ul class="empty">
    911          <li>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user
    912             tools.
    913          </li>
    914       </ul>
    915       <p id="rfc.section.1.3.p.13"> <span id="rfc.iref.s.1"></span>  <dfn>server</dfn> 
    916       </p>
    917       <ul class="empty">
    918          <li>An application program that accepts connections in order to service requests by sending back responses. Any given program
    919             may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the
    920             program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as
    921             an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.
    922          </li>
    923       </ul>
    924       <p id="rfc.section.1.3.p.14"> <span id="rfc.iref.o.1"></span>  <dfn>origin server</dfn> 
    925       </p>
    926       <ul class="empty">
    927          <li>The server on which a given resource resides or is to be created.</li>
    928       </ul>
    929       <p id="rfc.section.1.3.p.15"> <span id="rfc.iref.p.1"></span>  <dfn>proxy</dfn> 
    930       </p>
    931       <ul class="empty">
    932          <li>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients.
    933             Requests are serviced internally or by passing them on, with possible translation, to other servers. A proxy <em class="bcp14">MUST</em> implement both the client and server requirements of this specification. A "transparent proxy" is a proxy that does not modify
    934             the request or response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is
    935             a proxy that modifies the request or response in order to provide some added service to the user agent, such as group annotation
    936             services, media type transformation, protocol reduction, or anonymity filtering. Except where either transparent or non-transparent
    937             behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies.
    938          </li>
    939       </ul>
    940       <p id="rfc.section.1.3.p.16"> <span id="rfc.iref.g.1"></span>  <dfn>gateway</dfn> 
    941       </p>
    942       <ul class="empty">
    943          <li>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the
    944             origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway.
    945          </li>
    946       </ul>
    947       <p id="rfc.section.1.3.p.17"> <span id="rfc.iref.t.1"></span>  <dfn>tunnel</dfn> 
    948       </p>
    949       <ul class="empty">
    950          <li>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered
    951             a party to the HTTP communication, though the tunnel may have been initiated by an HTTP request. The tunnel ceases to exist
    952             when both ends of the relayed connections are closed.
    953          </li>
    954       </ul>
    955       <p id="rfc.section.1.3.p.18"> <span id="rfc.iref.c.4"></span>  <dfn>cache</dfn> 
    956       </p>
    957       <ul class="empty">
    958          <li>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.
    959             A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent
    960             requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.
    961          </li>
    962       </ul>
    963       <p id="rfc.section.1.3.p.19"> <span id="rfc.iref.c.5"></span>  <dfn>cacheable</dfn> 
    964       </p>
    965       <ul class="empty">
    966          <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
    967             The rules for determining the cacheability of HTTP responses are defined in <a href="#caching" title="Caching in HTTP">Section&nbsp;13</a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular
    968             request.
    969          </li>
    970       </ul>
    971       <p id="rfc.section.1.3.p.20"> <span id="rfc.iref.f.1"></span>  <dfn>first-hand</dfn> 
    972       </p>
    973       <ul class="empty">
    974          <li>A response is first-hand if it comes directly and without unnecessary delay from the origin server, perhaps via one or more
    975             proxies. A response is also first-hand if its validity has just been checked directly with the origin server.
    976          </li>
    977       </ul>
    978       <p id="rfc.section.1.3.p.21"> <span id="rfc.iref.e.2"></span>  <dfn>explicit expiration time</dfn> 
    979       </p>
    980       <ul class="empty">
    981          <li>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</li>
    982       </ul>
    983       <p id="rfc.section.1.3.p.22"> <span id="rfc.iref.h.1"></span>  <dfn>heuristic expiration time</dfn> 
    984       </p>
    985       <ul class="empty">
    986          <li>An expiration time assigned by a cache when no explicit expiration time is available.</li>
    987       </ul>
    988       <p id="rfc.section.1.3.p.23"> <span id="rfc.iref.a.1"></span>  <dfn>age</dfn> 
    989       </p>
    990       <ul class="empty">
    991          <li>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</li>
    992       </ul>
    993       <p id="rfc.section.1.3.p.24"> <span id="rfc.iref.f.2"></span>  <dfn>freshness lifetime</dfn> 
    994       </p>
    995       <ul class="empty">
    996          <li>The length of time between the generation of a response and its expiration time.</li>
    997       </ul>
    998       <p id="rfc.section.1.3.p.25"> <span id="rfc.iref.f.3"></span>  <dfn>fresh</dfn> 
    999       </p>
    1000       <ul class="empty">
    1001          <li>A response is fresh if its age has not yet exceeded its freshness lifetime.</li>
    1002       </ul>
    1003       <p id="rfc.section.1.3.p.26"> <span id="rfc.iref.s.2"></span>  <dfn>stale</dfn> 
    1004       </p>
    1005       <ul class="empty">
    1006          <li>A response is stale if its age has passed its freshness lifetime.</li>
    1007       </ul>
    1008       <p id="rfc.section.1.3.p.27"> <span id="rfc.iref.s.3"></span>  <dfn>semantically transparent</dfn> 
    1009       </p>
    1010       <ul class="empty">
    1011          <li>A cache behaves in a "semantically transparent" manner, with respect to a particular response, when its use affects neither
    1012             the requesting client nor the origin server, except to improve performance. When a cache is semantically transparent, the
    1013             client receives exactly the same response (except for hop-by-hop headers) that it would have received had its request been
    1014             handled directly by the origin server.
    1015          </li>
    1016       </ul>
    1017       <p id="rfc.section.1.3.p.28"> <span id="rfc.iref.v.2"></span>  <dfn>validator</dfn> 
    1018       </p>
    1019       <ul class="empty">
    1020          <li>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a cache entry is an equivalent
    1021             copy of an entity.
    1022          </li>
    1023       </ul>
    1024       <p id="rfc.section.1.3.p.29"> <span id="rfc.iref.u.2"></span>  <span id="rfc.iref.d.1"></span>  <dfn>upstream</dfn>/<dfn>downstream</dfn> 
    1025       </p>
    1026       <ul class="empty">
    1027          <li>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</li>
    1028       </ul>
    1029       <p id="rfc.section.1.3.p.30"> <span id="rfc.iref.i.1"></span>  <span id="rfc.iref.o.2"></span>  <dfn>inbound</dfn>/<dfn>outbound</dfn> 
    1030       </p>
    1031       <ul class="empty">
    1032          <li>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server",
    1033             and "outbound" means "traveling toward the user agent"
    1034          </li>
    1035       </ul>
    1036       <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a id="intro.overall.operation" href="#intro.overall.operation">Overall Operation</a></h2>
    1037       <p id="rfc.section.1.4.p.1">The HTTP protocol is a request/response protocol. A client sends a request to the server in the form of a request method,
    1038          URI, and protocol version, followed by a MIME-like message containing request modifiers, client information, and possible
    1039          body content over a connection with a server. The server responds with a status line, including the message's protocol version
    1040          and a success or error code, followed by a MIME-like message containing server information, entity metainformation, and possible
    1041          entity-body content. The relationship between HTTP and MIME is described in <a href="#differences.between.http.entities.and.rfc.2045.entities" title="Differences Between HTTP Entities and RFC 2045 Entities">Appendix&nbsp;19.4</a>.
    1042       </p>
    1043       <p id="rfc.section.1.4.p.2">Most HTTP communication is initiated by a user agent and consists of a request to be applied to a resource on some origin
    1044          server. In the simplest case, this may be accomplished via a single connection (v) between the user agent (UA) and the origin
    1045          server (O).
    1046       </p>
    1047       <div id="rfc.figure.u.1"></div><pre class="drawing">       request chain ------------------------&gt;
     811      <div id="introduction">
     812         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     813         <div id="intro.purpose">
     814            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.purpose">Purpose</a></h2>
     815            <p id="rfc.section.1.1.p.1">The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
     816               systems. HTTP has been in use by the World-Wide Web global information initiative since 1990. The first version of HTTP, referred
     817               to as HTTP/0.9, was a simple protocol for raw data transfer across the Internet. HTTP/1.0, as defined by RFC 1945 <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, improved the protocol by allowing messages to be in the format of MIME-like messages, containing metainformation about the
     818               data transferred and modifiers on the request/response semantics. However, HTTP/1.0 does not sufficiently take into consideration
     819               the effects of hierarchical proxies, caching, the need for persistent connections, or virtual hosts. In addition, the proliferation
     820               of incompletely-implemented applications calling themselves "HTTP/1.0" has necessitated a protocol version change in order
     821               for two communicating applications to determine each other's true capabilities.
     822            </p>
     823            <p id="rfc.section.1.1.p.2">This specification defines the protocol referred to as "HTTP/1.1". This protocol includes more stringent requirements than
     824               HTTP/1.0 in order to ensure reliable implementation of its features.
     825            </p>
     826            <p id="rfc.section.1.1.p.3">Practical information systems require more functionality than simple retrieval, including search, front-end update, and annotation.
     827               HTTP allows an open-ended set of methods and headers that indicate the purpose of a request <a href="#RFC2324" id="rfc.xref.RFC2324.2"><cite title="Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)">[RFC2324]</cite></a>. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) <a href="#RFC1630" id="rfc.xref.RFC1630.1"><cite title="Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web">[RFC1630]</cite></a>, as a location (URL) <a href="#RFC1738" id="rfc.xref.RFC1738.1"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> or name (URN) <a href="#RFC1737" id="rfc.xref.RFC1737.1"><cite title="Functional Requirements for Uniform Resource Names">[RFC1737]</cite></a>, for indicating the resource to which a method is to be applied. Messages are passed in a format similar to that used by
     828               Internet mail <a href="#RFC822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> as defined by the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>.
     829            </p>
     830            <p id="rfc.section.1.1.p.4">HTTP is also used as a generic protocol for communication between user agents and proxies/gateways to other Internet systems,
     831               including those supported by the SMTP <a href="#RFC821" id="rfc.xref.RFC821.1"><cite title="Simple Mail Transfer Protocol">[RFC821]</cite></a>, NNTP <a href="#RFC977" id="rfc.xref.RFC977.1"><cite title="Network News Transfer Protocol">[RFC977]</cite></a>, FTP <a href="#RFC959" id="rfc.xref.RFC959.1"><cite title="File Transfer Protocol">[RFC959]</cite></a>, Gopher <a href="#RFC1436" id="rfc.xref.RFC1436.1"><cite title="The Internet Gopher Protocol (a distributed document search and retrieval protocol)">[RFC1436]</cite></a>, and WAIS <a href="#WAIS" id="rfc.xref.WAIS.1"><cite title="WAIS Interface Protocol Prototype Functional Specification (v1.5)">[WAIS]</cite></a> protocols. In this way, HTTP allows basic hypermedia access to resources available from diverse applications.
     832            </p>
     833         </div>
     834         <div id="intro.requirements">
     835            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     836            <p id="rfc.section.1.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
     837               in this document are to be interpreted as described in RFC 2119 <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
     838            </p>
     839            <p id="rfc.section.1.2.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
     840            </p>
     841         </div>
     842         <div id="intro.terminology">
     843            <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a href="#intro.terminology">Terminology</a></h2>
     844            <p id="rfc.section.1.3.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
     845            <p id="rfc.section.1.3.p.2"><span id="rfc.iref.c.1"></span> <dfn>connection</dfn>
     846            </p>
     847            <ul class="empty">
     848               <li>A transport layer virtual circuit established between two programs for the purpose of communication.</li>
     849            </ul>
     850            <p id="rfc.section.1.3.p.3"><span id="rfc.iref.m.1"></span> <dfn>message</dfn>
     851            </p>
     852            <ul class="empty">
     853               <li>The basic unit of HTTP communication, consisting of a structured sequence of octets matching the syntax defined in <a href="#http.message" title="HTTP Message">Section&nbsp;4</a> and transmitted via the connection.
     854               </li>
     855            </ul>
     856            <p id="rfc.section.1.3.p.4"><span id="rfc.iref.r.1"></span> <dfn>request</dfn>
     857            </p>
     858            <ul class="empty">
     859               <li>An HTTP request message, as defined in <a href="#request" title="Request">Section&nbsp;5</a>.
     860               </li>
     861            </ul>
     862            <p id="rfc.section.1.3.p.5"><span id="rfc.iref.r.2"></span> <dfn>response</dfn>
     863            </p>
     864            <ul class="empty">
     865               <li>An HTTP response message, as defined in <a href="#response" title="Response">Section&nbsp;6</a>.
     866               </li>
     867            </ul>
     868            <p id="rfc.section.1.3.p.6"><span id="rfc.iref.r.3"></span> <dfn>resource</dfn>
     869            </p>
     870            <ul class="empty">
     871               <li>A network data object or service that can be identified by a URI, as defined in <a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;3.2</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or
     872                  vary in other ways.
     873               </li>
     874            </ul>
     875            <p id="rfc.section.1.3.p.7"><span id="rfc.iref.e.1"></span> <dfn>entity</dfn>
     876            </p>
     877            <ul class="empty">
     878               <li>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of
     879                  entity-header fields and content in the form of an entity-body, as described in <a href="#entity" title="Entity">Section&nbsp;7</a>.
     880               </li>
     881            </ul>
     882            <p id="rfc.section.1.3.p.8"><span id="rfc.iref.r.4"></span> <dfn>representation</dfn>
     883            </p>
     884            <ul class="empty">
     885               <li>An entity included with a response that is subject to content negotiation, as described in <a href="#content.negotiation" title="Content Negotiation">Section&nbsp;12</a>. There may exist multiple representations associated with a particular response status.
     886               </li>
     887            </ul>
     888            <p id="rfc.section.1.3.p.9"><span id="rfc.iref.c.2"></span> <dfn>content negotiation</dfn>
     889            </p>
     890            <ul class="empty">
     891               <li>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="#content.negotiation" title="Content Negotiation">Section&nbsp;12</a>. The representation of entities in any response can be negotiated (including error responses).
     892               </li>
     893            </ul>
     894            <p id="rfc.section.1.3.p.10"><span id="rfc.iref.v.1"></span> <dfn>variant</dfn>
     895            </p>
     896            <ul class="empty">
     897               <li>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations
     898                  is termed a `varriant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
     899               </li>
     900            </ul>
     901            <p id="rfc.section.1.3.p.11"><span id="rfc.iref.c.3"></span> <dfn>client</dfn>
     902            </p>
     903            <ul class="empty">
     904               <li>A program that establishes connections for the purpose of sending requests.</li>
     905            </ul>
     906            <p id="rfc.section.1.3.p.12"><span id="rfc.iref.u.1"></span> <dfn>user agent</dfn>
     907            </p>
     908            <ul class="empty">
     909               <li>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user
     910                  tools.
     911               </li>
     912            </ul>
     913            <p id="rfc.section.1.3.p.13"><span id="rfc.iref.s.1"></span> <dfn>server</dfn>
     914            </p>
     915            <ul class="empty">
     916               <li>An application program that accepts connections in order to service requests by sending back responses. Any given program
     917                  may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the
     918                  program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as
     919                  an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.
     920               </li>
     921            </ul>
     922            <p id="rfc.section.1.3.p.14"><span id="rfc.iref.o.1"></span> <dfn>origin server</dfn>
     923            </p>
     924            <ul class="empty">
     925               <li>The server on which a given resource resides or is to be created.</li>
     926            </ul>
     927            <p id="rfc.section.1.3.p.15"><span id="rfc.iref.p.1"></span> <dfn>proxy</dfn>
     928            </p>
     929            <ul class="empty">
     930               <li>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients.
     931                  Requests are serviced internally or by passing them on, with possible translation, to other servers. A proxy <em class="bcp14">MUST</em> implement both the client and server requirements of this specification. A "transparent proxy" is a proxy that does not modify
     932                  the request or response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is
     933                  a proxy that modifies the request or response in order to provide some added service to the user agent, such as group annotation
     934                  services, media type transformation, protocol reduction, or anonymity filtering. Except where either transparent or non-transparent
     935                  behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies.
     936               </li>
     937            </ul>
     938            <p id="rfc.section.1.3.p.16"><span id="rfc.iref.g.1"></span> <dfn>gateway</dfn>
     939            </p>
     940            <ul class="empty">
     941               <li>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the
     942                  origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway.
     943               </li>
     944            </ul>
     945            <p id="rfc.section.1.3.p.17"><span id="rfc.iref.t.1"></span> <dfn>tunnel</dfn>
     946            </p>
     947            <ul class="empty">
     948               <li>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered
     949                  a party to the HTTP communication, though the tunnel may have been initiated by an HTTP request. The tunnel ceases to exist
     950                  when both ends of the relayed connections are closed.
     951               </li>
     952            </ul>
     953            <p id="rfc.section.1.3.p.18"><span id="rfc.iref.c.4"></span> <dfn>cache</dfn>
     954            </p>
     955            <ul class="empty">
     956               <li>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.
     957                  A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent
     958                  requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.
     959               </li>
     960            </ul>
     961            <p id="rfc.section.1.3.p.19"><span id="rfc.iref.c.5"></span> <dfn>cacheable</dfn>
     962            </p>
     963            <ul class="empty">
     964               <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
     965                  The rules for determining the cacheability of HTTP responses are defined in <a href="#caching" title="Caching in HTTP">Section&nbsp;13</a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular
     966                  request.
     967               </li>
     968            </ul>
     969            <p id="rfc.section.1.3.p.20"><span id="rfc.iref.f.1"></span> <dfn>first-hand</dfn>
     970            </p>
     971            <ul class="empty">
     972               <li>A response is first-hand if it comes directly and without unnecessary delay from the origin server, perhaps via one or more
     973                  proxies. A response is also first-hand if its validity has just been checked directly with the origin server.
     974               </li>
     975            </ul>
     976            <p id="rfc.section.1.3.p.21"><span id="rfc.iref.e.2"></span> <dfn>explicit expiration time</dfn>
     977            </p>
     978            <ul class="empty">
     979               <li>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</li>
     980            </ul>
     981            <p id="rfc.section.1.3.p.22"><span id="rfc.iref.h.1"></span> <dfn>heuristic expiration time</dfn>
     982            </p>
     983            <ul class="empty">
     984               <li>An expiration time assigned by a cache when no explicit expiration time is available.</li>
     985            </ul>
     986            <p id="rfc.section.1.3.p.23"><span id="rfc.iref.a.1"></span> <dfn>age</dfn>
     987            </p>
     988            <ul class="empty">
     989               <li>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</li>
     990            </ul>
     991            <p id="rfc.section.1.3.p.24"><span id="rfc.iref.f.2"></span> <dfn>freshness lifetime</dfn>
     992            </p>
     993            <ul class="empty">
     994               <li>The length of time between the generation of a response and its expiration time.</li>
     995            </ul>
     996            <p id="rfc.section.1.3.p.25"><span id="rfc.iref.f.3"></span> <dfn>fresh</dfn>
     997            </p>
     998            <ul class="empty">
     999               <li>A response is fresh if its age has not yet exceeded its freshness lifetime.</li>
     1000            </ul>
     1001            <p id="rfc.section.1.3.p.26"><span id="rfc.iref.s.2"></span> <dfn>stale</dfn>
     1002            </p>
     1003            <ul class="empty">
     1004               <li>A response is stale if its age has passed its freshness lifetime.</li>
     1005            </ul>
     1006            <p id="rfc.section.1.3.p.27"><span id="rfc.iref.s.3"></span> <dfn>semantically transparent</dfn>
     1007            </p>
     1008            <ul class="empty">
     1009               <li>A cache behaves in a "semantically transparent" manner, with respect to a particular response, when its use affects neither
     1010                  the requesting client nor the origin server, except to improve performance. When a cache is semantically transparent, the
     1011                  client receives exactly the same response (except for hop-by-hop headers) that it would have received had its request been
     1012                  handled directly by the origin server.
     1013               </li>
     1014            </ul>
     1015            <p id="rfc.section.1.3.p.28"><span id="rfc.iref.v.2"></span> <dfn>validator</dfn>
     1016            </p>
     1017            <ul class="empty">
     1018               <li>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a cache entry is an equivalent
     1019                  copy of an entity.
     1020               </li>
     1021            </ul>
     1022            <p id="rfc.section.1.3.p.29"><span id="rfc.iref.u.2"></span> <span id="rfc.iref.d.1"></span> <dfn>upstream</dfn>/<dfn>downstream</dfn>
     1023            </p>
     1024            <ul class="empty">
     1025               <li>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</li>
     1026            </ul>
     1027            <p id="rfc.section.1.3.p.30"><span id="rfc.iref.i.1"></span> <span id="rfc.iref.o.2"></span> <dfn>inbound</dfn>/<dfn>outbound</dfn>
     1028            </p>
     1029            <ul class="empty">
     1030               <li>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server",
     1031                  and "outbound" means "traveling toward the user agent"
     1032               </li>
     1033            </ul>
     1034         </div>
     1035         <div id="intro.overall.operation">
     1036            <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a href="#intro.overall.operation">Overall Operation</a></h2>
     1037            <p id="rfc.section.1.4.p.1">The HTTP protocol is a request/response protocol. A client sends a request to the server in the form of a request method,
     1038               URI, and protocol version, followed by a MIME-like message containing request modifiers, client information, and possible
     1039               body content over a connection with a server. The server responds with a status line, including the message's protocol version
     1040               and a success or error code, followed by a MIME-like message containing server information, entity metainformation, and possible
     1041               entity-body content. The relationship between HTTP and MIME is described in <a href="#differences.between.http.entities.and.rfc.2045.entities" title="Differences Between HTTP Entities and RFC 2045 Entities">Appendix&nbsp;19.4</a>.
     1042            </p>
     1043            <p id="rfc.section.1.4.p.2">Most HTTP communication is initiated by a user agent and consists of a request to be applied to a resource on some origin
     1044               server. In the simplest case, this may be accomplished via a single connection (v) between the user agent (UA) and the origin
     1045               server (O).
     1046            </p>
     1047            <div id="rfc.figure.u.1"></div><pre class="drawing">       request chain ------------------------&gt;
    10481048    UA -------------------v------------------- O
    10491049       &lt;----------------------- response chain
    10501050</pre><p id="rfc.section.1.4.p.4">A more complicated situation occurs when one or more intermediaries are present in the request/response chain. There are three
    1051          common forms of intermediary: proxy, gateway, and tunnel. A proxy is a forwarding agent, receiving requests for a URI in its
    1052          absolute form, rewriting all or part of the message, and forwarding the reformatted request toward the server identified by
    1053          the URI. A gateway is a receiving agent, acting as a layer above some other server(s) and, if necessary, translating the requests
    1054          to the underlying server's protocol. A tunnel acts as a relay point between two connections without changing the messages;
    1055          tunnels are used when the communication needs to pass through an intermediary (such as a firewall) even when the intermediary
    1056          cannot understand the contents of the messages.
    1057       </p>
    1058       <div id="rfc.figure.u.2"></div><pre class="drawing">       request chain --------------------------------------&gt;
     1051               common forms of intermediary: proxy, gateway, and tunnel. A proxy is a forwarding agent, receiving requests for a URI in its
     1052               absolute form, rewriting all or part of the message, and forwarding the reformatted request toward the server identified by
     1053               the URI. A gateway is a receiving agent, acting as a layer above some other server(s) and, if necessary, translating the requests
     1054               to the underlying server's protocol. A tunnel acts as a relay point between two connections without changing the messages;
     1055               tunnels are used when the communication needs to pass through an intermediary (such as a firewall) even when the intermediary
     1056               cannot understand the contents of the messages.
     1057            </p>
     1058            <div id="rfc.figure.u.2"></div><pre class="drawing">       request chain --------------------------------------&gt;
    10591059    UA -----v----- A -----v----- B -----v----- C -----v----- O
    10601060       &lt;------------------------------------- response chain
    10611061</pre><p id="rfc.section.1.4.p.6">The figure above shows three intermediaries (A, B, and C) between the user agent and origin server. A request or response
    1062          message that travels the whole chain will pass through four separate connections. This distinction is important because some
    1063          HTTP communication options may apply only to the connection with the nearest, non-tunnel neighbor, only to the end-points
    1064          of the chain, or to all connections along the chain. Although the diagram is linear, each participant may be engaged in multiple,
    1065          simultaneous communications. For example, B may be receiving requests from many clients other than A, and/or forwarding requests
    1066          to servers other than C, at the same time that it is handling A's request.
    1067       </p>
    1068       <p id="rfc.section.1.4.p.7">Any party to the communication which is not acting as a tunnel may employ an internal cache for handling requests. The effect
    1069          of a cache is that the request/response chain is shortened if one of the participants along the chain has a cached response
    1070          applicable to that request. The following illustrates the resulting chain if B has a cached copy of an earlier response from
    1071          O (via C) for a request which has not been cached by UA or A.
    1072       </p>
    1073       <div id="rfc.figure.u.3"></div><pre class="drawing">          request chain ----------&gt;
     1062               message that travels the whole chain will pass through four separate connections. This distinction is important because some
     1063               HTTP communication options may apply only to the connection with the nearest, non-tunnel neighbor, only to the end-points
     1064               of the chain, or to all connections along the chain. Although the diagram is linear, each participant may be engaged in multiple,
     1065               simultaneous communications. For example, B may be receiving requests from many clients other than A, and/or forwarding requests
     1066               to servers other than C, at the same time that it is handling A's request.
     1067            </p>
     1068            <p id="rfc.section.1.4.p.7">Any party to the communication which is not acting as a tunnel may employ an internal cache for handling requests. The effect
     1069               of a cache is that the request/response chain is shortened if one of the participants along the chain has a cached response
     1070               applicable to that request. The following illustrates the resulting chain if B has a cached copy of an earlier response from
     1071               O (via C) for a request which has not been cached by UA or A.
     1072            </p>
     1073            <div id="rfc.figure.u.3"></div><pre class="drawing">          request chain ----------&gt;
    10741074       UA -----v----- A -----v----- B - - - - - - C - - - - - - O
    10751075          &lt;--------- response chain
    10761076</pre><p id="rfc.section.1.4.p.9">Not all responses are usefully cacheable, and some requests may contain modifiers which place special requirements on cache
    1077          behavior. HTTP requirements for cache behavior and cacheable responses are defined in <a href="#caching" title="Caching in HTTP">Section&nbsp;13</a>.
    1078       </p>
    1079       <p id="rfc.section.1.4.p.10">In fact, there are a wide variety of architectures and configurations of caches and proxies currently being experimented with
    1080          or deployed across the World Wide Web. These systems include national hierarchies of proxy caches to save transoceanic bandwidth,
    1081          systems that broadcast or multicast cache entries, organizations that distribute subsets of cached data via CD-ROM, and so
    1082          on. HTTP systems are used in corporate intranets over high-bandwidth links, and for access via PDAs with low-power radio links
    1083          and intermittent connectivity. The goal of HTTP/1.1 is to support the wide diversity of configurations already deployed while
    1084          introducing protocol constructs that meet the needs of those who build web applications that require high reliability and,
    1085          failing that, at least reliable indications of failure.
    1086       </p>
    1087       <p id="rfc.section.1.4.p.11">HTTP communication usually takes place over TCP/IP connections. The default port is TCP 80 <a href="#RFC1700" id="rfc.xref.RFC1700.1"><cite title="Assigned Numbers">[RFC1700]</cite></a>, but other ports can be used. This does not preclude HTTP from being implemented on top of any other protocol on the Internet,
    1088          or on other networks. HTTP only presumes a reliable transport; any protocol that provides such guarantees can be used; the
    1089          mapping of the HTTP/1.1 request and response structures onto the transport data units of the protocol in question is outside
    1090          the scope of this specification.
    1091       </p>
    1092       <p id="rfc.section.1.4.p.12">In HTTP/1.0, most implementations used a new connection for each request/response exchange. In HTTP/1.1, a connection may
    1093          be used for one or more request/response exchanges, although connections may be closed for a variety of reasons (see <a href="#persistent.connections" title="Persistent Connections">Section&nbsp;8.1</a>).
    1094       </p>
    1095       <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1>
    1096       <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="notation.abnf" href="#notation.abnf">Augmented BNF</a></h2>
    1097       <p id="rfc.section.2.1.p.1">All of the mechanisms specified in this document are described in both prose and an augmented Backus-Naur Form (BNF) similar
    1098          to that used by RFC 822 <a href="#RFC822" id="rfc.xref.RFC822.2"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Implementors will need to be familiar with the notation in order to understand this specification. The augmented BNF includes
    1099          the following constructs:
    1100       </p>
    1101       <p id="rfc.section.2.1.p.2">name = definition </p>
    1102       <ul class="empty">
    1103          <li>The name of a rule is simply the name itself (without any enclosing "&lt;" and "&gt;") and is separated from its definition by the
    1104             equal "=" character. White space is only significant in that indentation of continuation lines is used to indicate a rule
    1105             definition that spans more than one line. Certain basic rules are in uppercase, such as SP, LWS, HT, CRLF, DIGIT, ALPHA, etc.
    1106             Angle brackets are used within definitions whenever their presence will facilitate discerning the use of rule names.
    1107          </li>
    1108       </ul>
    1109       <p id="rfc.section.2.1.p.3">"literal" </p>
    1110       <ul class="empty">
    1111          <li>Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive.</li>
    1112       </ul>
    1113       <p id="rfc.section.2.1.p.4">rule1 | rule2 </p>
    1114       <ul class="empty">
    1115          <li>Elements separated by a bar ("|") are alternatives, e.g., "yes | no" will accept yes or no.</li>
    1116       </ul>
    1117       <p id="rfc.section.2.1.p.5">(rule1 rule2) </p>
    1118       <ul class="empty">
    1119          <li>Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo | bar) elem)" allows the token sequences
    1120             "elem foo elem" and "elem bar elem".
    1121          </li>
    1122       </ul>
    1123       <p id="rfc.section.2.1.p.6">*rule </p>
    1124       <ul class="empty">
    1125          <li>The character "*" preceding an element indicates repetition. The full form is "&lt;n&gt;*&lt;m&gt;element" indicating at least &lt;n&gt; and
    1126             at most &lt;m&gt; occurrences of element. Default values are 0 and infinity so that "*(element)" allows any number, including zero;
    1127             "1*element" requires at least one; and "1*2element" allows one or two.
    1128          </li>
    1129       </ul>
    1130       <p id="rfc.section.2.1.p.7">[rule] </p>
    1131       <ul class="empty">
    1132          <li>Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)".</li>
    1133       </ul>
    1134       <p id="rfc.section.2.1.p.8">N rule </p>
    1135       <ul class="empty">
    1136          <li>Specific repetition: "&lt;n&gt;(element)" is equivalent to "&lt;n&gt;*&lt;n&gt;(element)"; that is, exactly &lt;n&gt; occurrences of (element). Thus
    1137             2DIGIT is a 2-digit number, and 3ALPHA is a string of three alphabetic characters.
    1138          </li>
    1139       </ul>
    1140       <p id="rfc.section.2.1.p.9">#rule </p>
    1141       <ul class="empty">
    1142          <li>A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating at
    1143             least &lt;n&gt; and at most &lt;m&gt; elements, each separated by one or more commas (",") and <em class="bcp14">OPTIONAL</em> linear white space (LWS). This makes the usual form of lists very easy; a rule such as
    1144          </li>
    1145          <li>( *LWS element *( *LWS "," *LWS element ))</li>
    1146          <li>can be shown as</li>
    1147          <li>1#element</li>
    1148          <li>Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is,
    1149             "(element), , (element) " is permitted, but counts as only two elements. Therefore, where at least one element is required,
    1150             at least one non-null element <em class="bcp14">MUST</em> be present. Default values are 0 and infinity so that "#element" allows any number, including zero; "1#element" requires at
    1151             least one; and "1#2element" allows one or two.
    1152          </li>
    1153       </ul>
    1154       <p id="rfc.section.2.1.p.10">; comment </p>
    1155       <ul class="empty">
    1156          <li>A semi-colon, set off some distance to the right of rule text, starts a comment that continues to the end of line. This is
    1157             a simple way of including useful notes in parallel with the specifications.
    1158          </li>
    1159       </ul>
    1160       <p id="rfc.section.2.1.p.11">implied *LWS </p>
    1161       <ul class="empty">
    1162          <li>The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included
    1163             between any two adjacent words (token or quoted-string), and between adjacent words and separators, without changing the interpretation
    1164             of a field. At least one delimiter (LWS and/or separators) <em class="bcp14">MUST</em> exist between any two tokens (for the definition of "token" below), since they would otherwise be interpreted as a single
    1165             token.
    1166          </li>
    1167       </ul>
    1168       <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="basic.rules" href="#basic.rules">Basic Rules</a></h2>
    1169       <p id="rfc.section.2.2.p.1">The following rules are used throughout this specification to describe basic parsing constructs. The US-ASCII coded character
    1170          set is defined by ANSI X3.4-1986 <a href="#USASCII" id="rfc.xref.USASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[USASCII]</cite></a>.
    1171       </p>
    1172       <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>    OCTET          = &lt;any 8-bit sequence of data&gt;
     1077               behavior. HTTP requirements for cache behavior and cacheable responses are defined in <a href="#caching" title="Caching in HTTP">Section&nbsp;13</a>.
     1078            </p>
     1079            <p id="rfc.section.1.4.p.10">In fact, there are a wide variety of architectures and configurations of caches and proxies currently being experimented with
     1080               or deployed across the World Wide Web. These systems include national hierarchies of proxy caches to save transoceanic bandwidth,
     1081               systems that broadcast or multicast cache entries, organizations that distribute subsets of cached data via CD-ROM, and so
     1082               on. HTTP systems are used in corporate intranets over high-bandwidth links, and for access via PDAs with low-power radio links
     1083               and intermittent connectivity. The goal of HTTP/1.1 is to support the wide diversity of configurations already deployed while
     1084               introducing protocol constructs that meet the needs of those who build web applications that require high reliability and,
     1085               failing that, at least reliable indications of failure.
     1086            </p>
     1087            <p id="rfc.section.1.4.p.11">HTTP communication usually takes place over TCP/IP connections. The default port is TCP 80 <a href="#RFC1700" id="rfc.xref.RFC1700.1"><cite title="Assigned Numbers">[RFC1700]</cite></a>, but other ports can be used. This does not preclude HTTP from being implemented on top of any other protocol on the Internet,
     1088               or on other networks. HTTP only presumes a reliable transport; any protocol that provides such guarantees can be used; the
     1089               mapping of the HTTP/1.1 request and response structures onto the transport data units of the protocol in question is outside
     1090               the scope of this specification.
     1091            </p>
     1092            <p id="rfc.section.1.4.p.12">In HTTP/1.0, most implementations used a new connection for each request/response exchange. In HTTP/1.1, a connection may
     1093               be used for one or more request/response exchanges, although connections may be closed for a variety of reasons (see <a href="#persistent.connections" title="Persistent Connections">Section&nbsp;8.1</a>).
     1094            </p>
     1095         </div>
     1096      </div>
     1097      <div id="notation">
     1098         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a></h1>
     1099         <div id="notation.abnf">
     1100            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#notation.abnf">Augmented BNF</a></h2>
     1101            <p id="rfc.section.2.1.p.1">All of the mechanisms specified in this document are described in both prose and an augmented Backus-Naur Form (BNF) similar
     1102               to that used by RFC 822 <a href="#RFC822" id="rfc.xref.RFC822.2"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Implementors will need to be familiar with the notation in order to understand this specification. The augmented BNF includes
     1103               the following constructs:
     1104            </p>
     1105            <p id="rfc.section.2.1.p.2">name = definition </p>
     1106            <ul class="empty">
     1107               <li>The name of a rule is simply the name itself (without any enclosing "&lt;" and "&gt;") and is separated from its definition by the
     1108                  equal "=" character. White space is only significant in that indentation of continuation lines is used to indicate a rule
     1109                  definition that spans more than one line. Certain basic rules are in uppercase, such as SP, LWS, HT, CRLF, DIGIT, ALPHA, etc.
     1110                  Angle brackets are used within definitions whenever their presence will facilitate discerning the use of rule names.
     1111               </li>
     1112            </ul>
     1113            <p id="rfc.section.2.1.p.3">"literal" </p>
     1114            <ul class="empty">
     1115               <li>Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive.</li>
     1116            </ul>
     1117            <p id="rfc.section.2.1.p.4">rule1 | rule2 </p>
     1118            <ul class="empty">
     1119               <li>Elements separated by a bar ("|") are alternatives, e.g., "yes | no" will accept yes or no.</li>
     1120            </ul>
     1121            <p id="rfc.section.2.1.p.5">(rule1 rule2) </p>
     1122            <ul class="empty">
     1123               <li>Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo | bar) elem)" allows the token sequences
     1124                  "elem foo elem" and "elem bar elem".
     1125               </li>
     1126            </ul>
     1127            <p id="rfc.section.2.1.p.6">*rule </p>
     1128            <ul class="empty">
     1129               <li>The character "*" preceding an element indicates repetition. The full form is "&lt;n&gt;*&lt;m&gt;element" indicating at least &lt;n&gt; and
     1130                  at most &lt;m&gt; occurrences of element. Default values are 0 and infinity so that "*(element)" allows any number, including zero;
     1131                  "1*element" requires at least one; and "1*2element" allows one or two.
     1132               </li>
     1133            </ul>
     1134            <p id="rfc.section.2.1.p.7">[rule] </p>
     1135            <ul class="empty">
     1136               <li>Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)".</li>
     1137            </ul>
     1138            <p id="rfc.section.2.1.p.8">N rule </p>
     1139            <ul class="empty">
     1140               <li>Specific repetition: "&lt;n&gt;(element)" is equivalent to "&lt;n&gt;*&lt;n&gt;(element)"; that is, exactly &lt;n&gt; occurrences of (element). Thus
     1141                  2DIGIT is a 2-digit number, and 3ALPHA is a string of three alphabetic characters.
     1142               </li>
     1143            </ul>
     1144            <p id="rfc.section.2.1.p.9">#rule </p>
     1145            <ul class="empty">
     1146               <li>A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating at
     1147                  least &lt;n&gt; and at most &lt;m&gt; elements, each separated by one or more commas (",") and <em class="bcp14">OPTIONAL</em> linear white space (LWS). This makes the usual form of lists very easy; a rule such as
     1148               </li>
     1149               <li>( *LWS element *( *LWS "," *LWS element ))</li>
     1150               <li>can be shown as</li>
     1151               <li>1#element</li>
     1152               <li>Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is,
     1153                  "(element), , (element) " is permitted, but counts as only two elements. Therefore, where at least one element is required,
     1154                  at least one non-null element <em class="bcp14">MUST</em> be present. Default values are 0 and infinity so that "#element" allows any number, including zero; "1#element" requires at
     1155                  least one; and "1#2element" allows one or two.
     1156               </li>
     1157            </ul>
     1158            <p id="rfc.section.2.1.p.10">; comment </p>
     1159            <ul class="empty">
     1160               <li>A semi-colon, set off some distance to the right of rule text, starts a comment that continues to the end of line. This is
     1161                  a simple way of including useful notes in parallel with the specifications.
     1162               </li>
     1163            </ul>
     1164            <p id="rfc.section.2.1.p.11">implied *LWS </p>
     1165            <ul class="empty">
     1166               <li>The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included
     1167                  between any two adjacent words (token or quoted-string), and between adjacent words and separators, without changing the interpretation
     1168                  of a field. At least one delimiter (LWS and/or separators) <em class="bcp14">MUST</em> exist between any two tokens (for the definition of "token" below), since they would otherwise be interpreted as a single
     1169                  token.
     1170               </li>
     1171            </ul>
     1172         </div>
     1173         <div id="basic.rules">
     1174            <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#basic.rules">Basic Rules</a></h2>
     1175            <p id="rfc.section.2.2.p.1">The following rules are used throughout this specification to describe basic parsing constructs. The US-ASCII coded character
     1176               set is defined by ANSI X3.4-1986 <a href="#USASCII" id="rfc.xref.USASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[USASCII]</cite></a>.
     1177            </p>
     1178            <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>    OCTET          = &lt;any 8-bit sequence of data&gt;
    11731179    CHAR           = &lt;any US-ASCII character (octets 0 - 127)&gt;
    11741180    UPALPHA        = &lt;any US-ASCII uppercase letter "A".."Z"&gt;
     
    11841190    &lt;"&gt;            = &lt;US-ASCII double-quote mark (34)&gt;
    11851191</pre><p id="rfc.section.2.2.p.3">HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;19.3</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described
    1186          in <a href="#media.types" title="Media Types">Section&nbsp;3.7</a>.
    1187       </p>
    1188       <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.13"></span>    CRLF           = CR LF
     1192               in <a href="#media.types" title="Media Types">Section&nbsp;3.7</a>.
     1193            </p>
     1194            <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.13"></span>    CRLF           = CR LF
    11891195</pre><p id="rfc.section.2.2.p.5">HTTP/1.1 header field values can be folded onto multiple lines if the continuation line begins with a space or horizontal
    1190          tab. All linear white space, including folding, has the same semantics as SP. A recipient <em class="bcp14">MAY</em> replace any linear white space with a single SP before interpreting the field value or forwarding the message downstream.
    1191       </p>
    1192       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.14"></span>    LWS            = [CRLF] 1*( SP | HT )
     1196               tab. All linear white space, including folding, has the same semantics as SP. A recipient <em class="bcp14">MAY</em> replace any linear white space with a single SP before interpreting the field value or forwarding the message downstream.
     1197            </p>
     1198            <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.14"></span>    LWS            = [CRLF] 1*( SP | HT )
    11931199</pre><p id="rfc.section.2.2.p.7">The TEXT rule is only used for descriptive field contents and values that are not intended to be interpreted by the message
    1194          parser. Words of *TEXT <em class="bcp14">MAY</em> contain characters from character sets other than ISO-8859-1 <a href="#ISO-8859" id="rfc.xref.ISO-8859.1"><cite title="Information technology - 8-bit single byte coded graphic - character sets">[ISO-8859]</cite></a> only when encoded according to the rules of RFC 2047 <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[RFC2047]</cite></a>.
    1195       </p>
    1196       <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.15"></span>    TEXT           = &lt;any OCTET except CTLs,
     1200               parser. Words of *TEXT <em class="bcp14">MAY</em> contain characters from character sets other than ISO-8859-1 <a href="#ISO-8859" id="rfc.xref.ISO-8859.1"><cite title="Information technology - 8-bit single byte coded graphic - character sets">[ISO-8859]</cite></a> only when encoded according to the rules of RFC 2047 <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[RFC2047]</cite></a>.
     1201            </p>
     1202            <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.15"></span>    TEXT           = &lt;any OCTET except CTLs,
    11971203                     but including LWS&gt;
    11981204</pre><p id="rfc.section.2.2.p.9">A CRLF is allowed in the definition of TEXT only as part of a header field continuation. It is expected that the folding LWS
    1199          will be replaced with a single SP before interpretation of the TEXT value.
    1200       </p>
    1201       <p id="rfc.section.2.2.p.10">Hexadecimal numeric characters are used in several protocol elements.</p>
    1202       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.16"></span>    HEX            = "A" | "B" | "C" | "D" | "E" | "F"
     1205               will be replaced with a single SP before interpretation of the TEXT value.
     1206            </p>
     1207            <p id="rfc.section.2.2.p.10">Hexadecimal numeric characters are used in several protocol elements.</p>
     1208            <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.16"></span>    HEX            = "A" | "B" | "C" | "D" | "E" | "F"
    12031209                   | "a" | "b" | "c" | "d" | "e" | "f" | DIGIT
    12041210</pre><p id="rfc.section.2.2.p.12">Many HTTP/1.1 header field values consist of words separated by LWS or special characters. These special characters <em class="bcp14">MUST</em> be in a quoted string to be used within a parameter value (as defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.6</a>).
    1205       </p>
    1206       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>    token          = 1*&lt;any CHAR except CTLs or separators&gt;
     1211            </p>
     1212            <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>    token          = 1*&lt;any CHAR except CTLs or separators&gt;
    12071213    separators     = "(" | ")" | "&lt;" | "&gt;" | "@"
    12081214                   | "," | ";" | ":" | "\" | &lt;"&gt;
     
    12101216                   | "{" | "}" | SP | HT
    12111217</pre><p id="rfc.section.2.2.p.14">Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed
    1212          in fields containing "comment" as part of their field value definition. In all other fields, parentheses are considered part
    1213          of the field value.
    1214       </p>
    1215       <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>    comment        = "(" *( ctext | quoted-pair | comment ) ")"
     1218               in fields containing "comment" as part of their field value definition. In all other fields, parentheses are considered part
     1219               of the field value.
     1220            </p>
     1221            <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>    comment        = "(" *( ctext | quoted-pair | comment ) ")"
    12161222    ctext          = &lt;any TEXT excluding "(" and ")"&gt;
    12171223</pre><p id="rfc.section.2.2.p.16">A string of text is parsed as a single word if it is quoted using double-quote marks.</p>
    1218       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>    quoted-string  = ( &lt;"&gt; *(qdtext | quoted-pair ) &lt;"&gt; )
     1224            <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>    quoted-string  = ( &lt;"&gt; *(qdtext | quoted-pair ) &lt;"&gt; )
    12191225    qdtext         = &lt;any TEXT except &lt;"&gt;&gt;
    12201226</pre><p id="rfc.section.2.2.p.18">The backslash character ("\") <em class="bcp14">MAY</em> be used as a single-character quoting mechanism only within quoted-string and comment constructs.
    1221       </p>
    1222       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.23"></span>    quoted-pair    = "\" CHAR
    1223 </pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    1224       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="http.version" href="#http.version">HTTP Version</a></h2>
    1225       <p id="rfc.section.3.1.p.1">HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate versions of the protocol. The protocol versioning policy is intended
    1226          to allow the sender to indicate the format of a message and its capacity for understanding further HTTP communication, rather
    1227          than the features obtained via that communication. No change is made to the version number for the addition of message components
    1228          which do not affect communication behavior or which only add to extensible field values. The &lt;minor&gt; number is incremented
    1229          when the changes made to the protocol add features which do not change the general message parsing algorithm, but which may
    1230          add to the message semantics and imply additional capabilities of the sender. The &lt;major&gt; number is incremented when the format
    1231          of a message within the protocol is changed. See RFC 2145 <a href="#RFC2145" id="rfc.xref.RFC2145.1"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a> for a fuller explanation.
    1232       </p>
    1233       <p id="rfc.section.3.1.p.2">The version of an HTTP message is indicated by an HTTP-Version field in the first line of the message.</p>
    1234       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.24"></span>       HTTP-Version   = "HTTP" "/" 1*DIGIT "." 1*DIGIT
     1227            </p>
     1228            <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.23"></span>    quoted-pair    = "\" CHAR
     1229</pre></div>
     1230      </div>
     1231      <div id="protocol.parameters">
     1232         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#protocol.parameters">Protocol Parameters</a></h1>
     1233         <div id="http.version">
     1234            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#http.version">HTTP Version</a></h2>
     1235            <p id="rfc.section.3.1.p.1">HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate versions of the protocol. The protocol versioning policy is intended
     1236               to allow the sender to indicate the format of a message and its capacity for understanding further HTTP communication, rather
     1237               than the features obtained via that communication. No change is made to the version number for the addition of message components
     1238               which do not affect communication behavior or which only add to extensible field values. The &lt;minor&gt; number is incremented
     1239               when the changes made to the protocol add features which do not change the general message parsing algorithm, but which may
     1240               add to the message semantics and imply additional capabilities of the sender. The &lt;major&gt; number is incremented when the format
     1241               of a message within the protocol is changed. See RFC 2145 <a href="#RFC2145" id="rfc.xref.RFC2145.1"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a> for a fuller explanation.
     1242            </p>
     1243            <p id="rfc.section.3.1.p.2">The version of an HTTP message is indicated by an HTTP-Version field in the first line of the message.</p>
     1244            <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.24"></span>       HTTP-Version   = "HTTP" "/" 1*DIGIT "." 1*DIGIT
    12351245</pre><p id="rfc.section.3.1.p.4">Note that the major and minor numbers <em class="bcp14">MUST</em> be treated as separate integers and that each <em class="bcp14">MAY</em> be incremented higher than a single digit. Thus, HTTP/2.4 is a lower version than HTTP/2.13, which in turn is lower than HTTP/12.3.
    1236          Leading zeros <em class="bcp14">MUST</em> be ignored by recipients and <em class="bcp14">MUST NOT</em> be sent.
    1237       </p>
    1238       <p id="rfc.section.3.1.p.5">An application that sends a request or response message that includes HTTP-Version of "HTTP/1.1" <em class="bcp14">MUST</em> be at least conditionally compliant with this specification. Applications that are at least conditionally compliant with this
    1239          specification <em class="bcp14">SHOULD</em> use an HTTP-Version of "HTTP/1.1" in their messages, and <em class="bcp14">MUST</em> do so for any message that is not compatible with HTTP/1.0. For more details on when to send specific HTTP-Version values,
    1240          see RFC 2145 <a href="#RFC2145" id="rfc.xref.RFC2145.2"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>.
    1241       </p>
    1242       <p id="rfc.section.3.1.p.6">The HTTP version of an application is the highest HTTP version for which the application is at least conditionally compliant.</p>
    1243       <p id="rfc.section.3.1.p.7">Proxy and gateway applications need to be careful when forwarding messages in protocol versions different from that of the
    1244          application. Since the protocol version indicates the protocol capability of the sender, a proxy/gateway <em class="bcp14">MUST NOT</em> send a message with a version indicator which is greater than its actual version. If a higher version request is received,
    1245          the proxy/gateway <em class="bcp14">MUST</em> either downgrade the request version, or respond with an error, or switch to tunnel behavior.
    1246       </p>
    1247       <p id="rfc.section.3.1.p.8">Due to interoperability problems with HTTP/1.0 proxies discovered since the publication of RFC 2068 <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, caching proxies MUST, gateways <em class="bcp14">MAY</em>, and tunnels <em class="bcp14">MUST NOT</em> upgrade the request to the highest version they support. The proxy/gateway's response to that request <em class="bcp14">MUST</em> be in the same major version as the request.
    1248       </p>
    1249       <p id="rfc.section.3.1.p.9"> </p>
    1250       <ul class="empty">
    1251          <li> <b>Note:</b> Converting between versions of HTTP may involve modification of header fields required or forbidden by the versions involved.
    1252          </li>
    1253       </ul>
    1254       <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="uri" href="#uri">Uniform Resource Identifiers</a></h2>
    1255       <p id="rfc.section.3.2.p.1">URIs have been known by many names: WWW addresses, Universal Document Identifiers, Universal Resource Identifiers <a href="#RFC1630" id="rfc.xref.RFC1630.2"><cite title="Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web">[RFC1630]</cite></a>, and finally the combination of Uniform Resource Locators (URL) <a href="#RFC1738" id="rfc.xref.RFC1738.2"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> and Names (URN) <a href="#RFC1737" id="rfc.xref.RFC1737.2"><cite title="Functional Requirements for Uniform Resource Names">[RFC1737]</cite></a>. As far as HTTP is concerned, Uniform Resource Identifiers are simply formatted strings which identify--via name, location,
    1256          or any other characteristic--a resource.
    1257       </p>
    1258       <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;<a id="general.syntax" href="#general.syntax">General Syntax</a></h3>
    1259       <p id="rfc.section.3.2.1.p.1">URIs in HTTP can be represented in absolute form or relative to some known base URI <a href="#RFC1808" id="rfc.xref.RFC1808.1"><cite title="Relative Uniform Resource Locators">[RFC1808]</cite></a>, depending upon the context of their use. The two forms are differentiated by the fact that absolute URIs always begin with
    1260          a scheme name followed by a colon. For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers
    1261          (URI): Generic Syntax and Semantics," RFC 2396 <a href="#RFC2396" id="rfc.xref.RFC2396.1"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a> (which replaces RFCs 1738 <a href="#RFC1738" id="rfc.xref.RFC1738.3"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> and RFC 1808 <a href="#RFC1808" id="rfc.xref.RFC1808.2"><cite title="Relative Uniform Resource Locators">[RFC1808]</cite></a>). This specification adopts the definitions of "URI-reference", "absoluteURI", "relativeURI", "port", "host","abs_path",
    1262          "rel_path", and "authority" from that specification.
    1263       </p>
    1264       <p id="rfc.section.3.2.1.p.2">The HTTP protocol does not place any a priori limit on the length of a URI. Servers <em class="bcp14">MUST</em> be able to handle the URI of any resource they serve, and <em class="bcp14">SHOULD</em> be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server <em class="bcp14">SHOULD</em> return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-URI Too Long">Section&nbsp;10.4.15</a>).
    1265       </p>
    1266       <p id="rfc.section.3.2.1.p.3"> </p>
    1267       <ul class="empty">
    1268          <li> <b>Note:</b> Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations
    1269             might not properly support these lengths.
    1270          </li>
    1271       </ul>
    1272       <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="http.url" href="#http.url">http URL</a></h3>
    1273       <p id="rfc.section.3.2.2.p.1">The "http" scheme is used to locate network resources via the HTTP protocol. This section defines the scheme-specific syntax
    1274          and semantics for http URLs.
    1275       </p>
    1276       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.25"></span>http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
     1246               Leading zeros <em class="bcp14">MUST</em> be ignored by recipients and <em class="bcp14">MUST NOT</em> be sent.
     1247            </p>
     1248            <p id="rfc.section.3.1.p.5">An application that sends a request or response message that includes HTTP-Version of "HTTP/1.1" <em class="bcp14">MUST</em> be at least conditionally compliant with this specification. Applications that are at least conditionally compliant with this
     1249               specification <em class="bcp14">SHOULD</em> use an HTTP-Version of "HTTP/1.1" in their messages, and <em class="bcp14">MUST</em> do so for any message that is not compatible with HTTP/1.0. For more details on when to send specific HTTP-Version values,
     1250               see RFC 2145 <a href="#RFC2145" id="rfc.xref.RFC2145.2"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>.
     1251            </p>
     1252            <p id="rfc.section.3.1.p.6">The HTTP version of an application is the highest HTTP version for which the application is at least conditionally compliant.</p>
     1253            <p id="rfc.section.3.1.p.7">Proxy and gateway applications need to be careful when forwarding messages in protocol versions different from that of the
     1254               application. Since the protocol version indicates the protocol capability of the sender, a proxy/gateway <em class="bcp14">MUST NOT</em> send a message with a version indicator which is greater than its actual version. If a higher version request is received,
     1255               the proxy/gateway <em class="bcp14">MUST</em> either downgrade the request version, or respond with an error, or switch to tunnel behavior.
     1256            </p>
     1257            <p id="rfc.section.3.1.p.8">Due to interoperability problems with HTTP/1.0 proxies discovered since the publication of RFC 2068 <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, caching proxies MUST, gateways <em class="bcp14">MAY</em>, and tunnels <em class="bcp14">MUST NOT</em> upgrade the request to the highest version they support. The proxy/gateway's response to that request <em class="bcp14">MUST</em> be in the same major version as the request.
     1258            </p>
     1259            <p id="rfc.section.3.1.p.9"></p>
     1260            <ul class="empty">
     1261               <li><b>Note:</b> Converting between versions of HTTP may involve modification of header fields required or forbidden by the versions involved.
     1262               </li>
     1263            </ul>
     1264         </div>
     1265         <div id="uri">
     1266            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#uri">Uniform Resource Identifiers</a></h2>
     1267            <p id="rfc.section.3.2.p.1">URIs have been known by many names: WWW addresses, Universal Document Identifiers, Universal Resource Identifiers <a href="#RFC1630" id="rfc.xref.RFC1630.2"><cite title="Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web">[RFC1630]</cite></a>, and finally the combination of Uniform Resource Locators (URL) <a href="#RFC1738" id="rfc.xref.RFC1738.2"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> and Names (URN) <a href="#RFC1737" id="rfc.xref.RFC1737.2"><cite title="Functional Requirements for Uniform Resource Names">[RFC1737]</cite></a>. As far as HTTP is concerned, Uniform Resource Identifiers are simply formatted strings which identify--via name, location,
     1268               or any other characteristic--a resource.
     1269            </p>
     1270            <div id="general.syntax">
     1271               <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;<a href="#general.syntax">General Syntax</a></h3>
     1272               <p id="rfc.section.3.2.1.p.1">URIs in HTTP can be represented in absolute form or relative to some known base URI <a href="#RFC1808" id="rfc.xref.RFC1808.1"><cite title="Relative Uniform Resource Locators">[RFC1808]</cite></a>, depending upon the context of their use. The two forms are differentiated by the fact that absolute URIs always begin with
     1273                  a scheme name followed by a colon. For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers
     1274                  (URI): Generic Syntax and Semantics," RFC 2396 <a href="#RFC2396" id="rfc.xref.RFC2396.1"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a> (which replaces RFCs 1738 <a href="#RFC1738" id="rfc.xref.RFC1738.3"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> and RFC 1808 <a href="#RFC1808" id="rfc.xref.RFC1808.2"><cite title="Relative Uniform Resource Locators">[RFC1808]</cite></a>). This specification adopts the definitions of "URI-reference", "absoluteURI", "relativeURI", "port", "host","abs_path",
     1275                  "rel_path", and "authority" from that specification.
     1276               </p>
     1277               <p id="rfc.section.3.2.1.p.2">The HTTP protocol does not place any a priori limit on the length of a URI. Servers <em class="bcp14">MUST</em> be able to handle the URI of any resource they serve, and <em class="bcp14">SHOULD</em> be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server <em class="bcp14">SHOULD</em> return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-URI Too Long">Section&nbsp;10.4.15</a>).
     1278               </p>
     1279               <p id="rfc.section.3.2.1.p.3"></p>
     1280               <ul class="empty">
     1281                  <li><b>Note:</b> Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations
     1282                     might not properly support these lengths.
     1283                  </li>
     1284               </ul>
     1285            </div>
     1286            <div id="http.url">
     1287               <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a href="#http.url">http URL</a></h3>
     1288               <p id="rfc.section.3.2.2.p.1">The "http" scheme is used to locate network resources via the HTTP protocol. This section defines the scheme-specific syntax
     1289                  and semantics for http URLs.
     1290               </p>
     1291               <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.25"></span>http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
    12771292</pre><p id="rfc.section.3.2.2.p.3">If the port is empty or not given, port 80 is assumed. The semantics are that the identified resource is located at the server
    1278          listening for TCP connections on that port of that host, and the Request-URI for the resource is abs_path (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>). The use of IP addresses in URLs <em class="bcp14">SHOULD</em> be avoided whenever possible (see RFC 1900 <a href="#RFC1900" id="rfc.xref.RFC1900.1"><cite title="Renumbering Needs Work">[RFC1900]</cite></a>). If the abs_path is not present in the URL, it <em class="bcp14">MUST</em> be given as "/" when used as a Request-URI for a resource (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>). If a proxy receives a host name which is not a fully qualified domain name, it <em class="bcp14">MAY</em> add its domain to the host name it received. If a proxy receives a fully qualified domain name, the proxy <em class="bcp14">MUST NOT</em> change the host name.
    1279       </p>
    1280       <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="uri.comparison" href="#uri.comparison">URI Comparison</a></h3>
    1281       <p id="rfc.section.3.2.3.p.1">When comparing two URIs to decide if they match or not, a client <em class="bcp14">SHOULD</em> use a case-sensitive octet-by-octet comparison of the entire URIs, with these exceptions:
    1282       </p>
    1283       <ul>
    1284          <li>A port that is empty or not given is equivalent to the default port for that URI-reference;</li>
    1285          <li>Comparisons of host names <em class="bcp14">MUST</em> be case-insensitive;
    1286          </li>
    1287          <li>Comparisons of scheme names <em class="bcp14">MUST</em> be case-insensitive;
    1288          </li>
    1289          <li>An empty abs_path is equivalent to an abs_path of "/".</li>
    1290       </ul>
    1291       <p id="rfc.section.3.2.3.p.2">Characters other than those in the "reserved" and "unsafe" sets (see RFC 2396 <a href="#RFC2396" id="rfc.xref.RFC2396.2"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>) are equivalent to their ""%" HEX HEX" encoding.
    1292       </p>
    1293       <p id="rfc.section.3.2.3.p.3">For example, the following three URIs are equivalent:</p>
    1294       <div id="rfc.figure.u.15"></div><pre class="text">   http://abc.com:80/~smith/home.html
     1293                  listening for TCP connections on that port of that host, and the Request-URI for the resource is abs_path (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>). The use of IP addresses in URLs <em class="bcp14">SHOULD</em> be avoided whenever possible (see RFC 1900 <a href="#RFC1900" id="rfc.xref.RFC1900.1"><cite title="Renumbering Needs Work">[RFC1900]</cite></a>). If the abs_path is not present in the URL, it <em class="bcp14">MUST</em> be given as "/" when used as a Request-URI for a resource (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>). If a proxy receives a host name which is not a fully qualified domain name, it <em class="bcp14">MAY</em> add its domain to the host name it received. If a proxy receives a fully qualified domain name, the proxy <em class="bcp14">MUST NOT</em> change the host name.
     1294               </p>
     1295            </div>
     1296            <div id="uri.comparison">
     1297               <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a href="#uri.comparison">URI Comparison</a></h3>
     1298               <p id="rfc.section.3.2.3.p.1">When comparing two URIs to decide if they match or not, a client <em class="bcp14">SHOULD</em> use a case-sensitive octet-by-octet comparison of the entire URIs, with these exceptions:
     1299               </p>
     1300               <ul>
     1301                  <li>A port that is empty or not given is equivalent to the default port for that URI-reference;</li>
     1302                  <li>Comparisons of host names <em class="bcp14">MUST</em> be case-insensitive;
     1303                  </li>
     1304                  <li>Comparisons of scheme names <em class="bcp14">MUST</em> be case-insensitive;
     1305                  </li>
     1306                  <li>An empty abs_path is equivalent to an abs_path of "/".</li>
     1307               </ul>
     1308               <p id="rfc.section.3.2.3.p.2">Characters other than those in the "reserved" and "unsafe" sets (see RFC 2396 <a href="#RFC2396" id="rfc.xref.RFC2396.2"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>) are equivalent to their ""%" HEX HEX" encoding.
     1309               </p>
     1310               <p id="rfc.section.3.2.3.p.3">For example, the following three URIs are equivalent:</p>
     1311               <div id="rfc.figure.u.15"></div><pre class="text">   http://abc.com:80/~smith/home.html
    12951312   http://ABC.com/%7Esmith/home.html
    12961313   http://ABC.com:/%7esmith/home.html
    1297 </pre><h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="date.time.formats" href="#date.time.formats">Date/Time Formats</a></h2>
    1298       <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;<a id="full.date" href="#full.date">Full Date</a></h3>
    1299       <p id="rfc.section.3.3.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p>
    1300       <div id="rfc.figure.u.16"></div><pre class="text">   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 822, updated by RFC 1123
     1314</pre></div>
     1315         </div>
     1316         <div id="date.time.formats">
     1317            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#date.time.formats">Date/Time Formats</a></h2>
     1318            <div id="full.date">
     1319               <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;<a href="#full.date">Full Date</a></h3>
     1320               <p id="rfc.section.3.3.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p>
     1321               <div id="rfc.figure.u.16"></div><pre class="text">   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 822, updated by RFC 1123
    13011322   Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036
    13021323   Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    13031324</pre><p id="rfc.section.3.3.1.p.3">The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by RFC 1123 <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a> (an update to RFC 822 <a href="#RFC822" id="rfc.xref.RFC822.3"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>). The second format is in common use, but is based on the obsolete RFC 850 <a href="#RFC1036" id="rfc.xref.RFC1036.1"><cite title="Standard for interchange of USENET messages">[RFC1036]</cite></a> date format and lacks a four-digit year. HTTP/1.1 clients and servers that parse the date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. See <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;19.3</a> for further information.
    1304       </p>
    1305       <ul class="empty">
    1306          <li> <b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that may have been sent by non-HTTP applications,
    1307             as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP.
    1308          </li>
    1309       </ul>
    1310       <p id="rfc.section.3.3.1.p.5">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
    1311          Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for
    1312          time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional LWS beyond that specifically included as SP in the grammar.
    1313       </p>
    1314       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span>    HTTP-date    = rfc1123-date | rfc850-date | asctime-date
     1325               </p>
     1326               <ul class="empty">
     1327                  <li><b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that may have been sent by non-HTTP applications,
     1328                     as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP.
     1329                  </li>
     1330               </ul>
     1331               <p id="rfc.section.3.3.1.p.5">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
     1332                  Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for
     1333                  time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional LWS beyond that specifically included as SP in the grammar.
     1334               </p>
     1335               <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span>    HTTP-date    = rfc1123-date | rfc850-date | asctime-date
    13151336    rfc1123-date = wkday "," SP date1 SP time SP "GMT"
    13161337    rfc850-date  = weekday "," SP date2 SP time SP "GMT"
     
    13311352                 | "May" | "Jun" | "Jul" | "Aug"
    13321353                 | "Sep" | "Oct" | "Nov" | "Dec"
    1333 </pre><p id="rfc.section.3.3.1.p.7"> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers
    1334          are not required to use these formats for user presentation, request logging, etc.
    1335       </p>
    1336       <h3 id="rfc.section.3.3.2"><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;<a id="delta.seconds" href="#delta.seconds">Delta Seconds</a></h3>
    1337       <p id="rfc.section.3.3.2.p.1">Some HTTP header fields allow a time value to be specified as an integer number of seconds, represented in decimal, after
    1338          the time that the message was received.
    1339       </p>
    1340       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.37"></span>    delta-seconds  = 1*DIGIT
    1341 </pre><h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="character.sets" href="#character.sets">Character Sets</a></h2>
    1342       <p id="rfc.section.3.4.p.1">HTTP uses the same definition of the term "character set" as that described for MIME:</p>
    1343       <p id="rfc.section.3.4.p.2">The term "character set" is used in this document to refer to a method used with one or more tables to convert a sequence
    1344          of octets into a sequence of characters. Note that unconditional conversion in the other direction is not required, in that
    1345          not all characters may be available in a given character set and a character set may provide more than one sequence of octets
    1346          to represent a particular character. This definition is intended to allow various kinds of character encoding, from simple
    1347          single-table mappings such as US-ASCII to complex table switching methods such as those that use ISO-2022's techniques. However,
    1348          the definition associated with a MIME character set name <em class="bcp14">MUST</em> fully specify the mapping to be performed from octets to characters. In particular, use of external profiling information
    1349          to determine the exact mapping is not permitted.
    1350       </p>
    1351       <ul class="empty">
    1352          <li> <b>Note:</b> This use of the term "character set" is more commonly referred to as a "character encoding." However, since HTTP and MIME
    1353             share the same registry, it is important that the terminology also be shared.
    1354          </li>
    1355       </ul>
    1356       <p id="rfc.section.3.4.p.4">HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character
    1357          Set registry <a href="#RFC1700" id="rfc.xref.RFC1700.2"><cite title="Assigned Numbers">[RFC1700]</cite></a>.
    1358       </p>
    1359       <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.38"></span>    charset = token
     1354</pre><p id="rfc.section.3.3.1.p.7"><b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers
     1355                  are not required to use these formats for user presentation, request logging, etc.
     1356               </p>
     1357            </div>
     1358            <div id="delta.seconds">
     1359               <h3 id="rfc.section.3.3.2"><a href="#rfc.section.3.3.2">3.3.2</a>&nbsp;<a href="#delta.seconds">Delta Seconds</a></h3>
     1360               <p id="rfc.section.3.3.2.p.1">Some HTTP header fields allow a time value to be specified as an integer number of seconds, represented in decimal, after
     1361                  the time that the message was received.
     1362               </p>
     1363               <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.37"></span>    delta-seconds  = 1*DIGIT
     1364</pre></div>
     1365         </div>
     1366         <div id="character.sets">
     1367            <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#character.sets">Character Sets</a></h2>
     1368            <p id="rfc.section.3.4.p.1">HTTP uses the same definition of the term "character set" as that described for MIME:</p>
     1369            <p id="rfc.section.3.4.p.2">The term "character set" is used in this document to refer to a method used with one or more tables to convert a sequence
     1370               of octets into a sequence of characters. Note that unconditional conversion in the other direction is not required, in that
     1371               not all characters may be available in a given character set and a character set may provide more than one sequence of octets
     1372               to represent a particular character. This definition is intended to allow various kinds of character encoding, from simple
     1373               single-table mappings such as US-ASCII to complex table switching methods such as those that use ISO-2022's techniques. However,
     1374               the definition associated with a MIME character set name <em class="bcp14">MUST</em> fully specify the mapping to be performed from octets to characters. In particular, use of external profiling information
     1375               to determine the exact mapping is not permitted.
     1376            </p>
     1377            <ul class="empty">
     1378               <li><b>Note:</b> This use of the term "character set" is more commonly referred to as a "character encoding." However, since HTTP and MIME
     1379                  share the same registry, it is important that the terminology also be shared.
     1380               </li>
     1381            </ul>
     1382            <p id="rfc.section.3.4.p.4">HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character
     1383               Set registry <a href="#RFC1700" id="rfc.xref.RFC1700.2"><cite title="Assigned Numbers">[RFC1700]</cite></a>.
     1384            </p>
     1385            <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.38"></span>    charset = token
    13601386</pre><p id="rfc.section.3.4.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
    1361          Character Set registry <a href="#RFC1700" id="rfc.xref.RFC1700.3"><cite title="Assigned Numbers">[RFC1700]</cite></a>  <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry.
    1362       </p>
    1363       <p id="rfc.section.3.4.p.7">Implementors should be aware of IETF character set requirements <a href="#RFC2279" id="rfc.xref.RFC2279.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC2279]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
    1364       </p>
    1365       <h3 id="rfc.section.3.4.1"><a href="#rfc.section.3.4.1">3.4.1</a>&nbsp;<a id="missing.charset" href="#missing.charset">Missing Charset</a></h3>
    1366       <p id="rfc.section.3.4.1.p.1">Some HTTP/1.0 software has interpreted a Content-Type header without charset parameter incorrectly to mean "recipient should
    1367          guess." Senders wishing to defeat this behavior <em class="bcp14">MAY</em> include a charset parameter even when the charset is ISO-8859-1 and <em class="bcp14">SHOULD</em> do so when it is known that it will not confuse the recipient.
    1368       </p>
    1369       <p id="rfc.section.3.4.1.p.2">Unfortunately, some older HTTP/1.0 clients did not deal properly with an explicit charset parameter. HTTP/1.1 recipients <em class="bcp14">MUST</em> respect the charset label provided by the sender; and those user agents that have a provision to "guess" a charset <em class="bcp14">MUST</em> use the charset from the content-type field if they support that charset, rather than the recipient's preference, when initially
    1370          displaying a document. See <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;3.7.1</a>.
    1371       </p>
    1372       <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
    1373       <p id="rfc.section.3.5.p.1">Content coding values indicate an encoding transformation that has been or can be applied to an entity. Content codings are
    1374          primarily used to allow a document to be compressed or otherwise usefully transformed without losing the identity of its underlying
    1375          media type and without loss of information. Frequently, the entity is stored in coded form, transmitted directly, and only
    1376          decoded by the recipient.
    1377       </p>
    1378       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.39"></span>    content-coding   = token
     1387               Character Set registry <a href="#RFC1700" id="rfc.xref.RFC1700.3"><cite title="Assigned Numbers">[RFC1700]</cite></a> <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry.
     1388            </p>
     1389            <p id="rfc.section.3.4.p.7">Implementors should be aware of IETF character set requirements <a href="#RFC2279" id="rfc.xref.RFC2279.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC2279]</cite></a> <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
     1390            </p>
     1391            <div id="missing.charset">
     1392               <h3 id="rfc.section.3.4.1"><a href="#rfc.section.3.4.1">3.4.1</a>&nbsp;<a href="#missing.charset">Missing Charset</a></h3>
     1393               <p id="rfc.section.3.4.1.p.1">Some HTTP/1.0 software has interpreted a Content-Type header without charset parameter incorrectly to mean "recipient should
     1394                  guess." Senders wishing to defeat this behavior <em class="bcp14">MAY</em> include a charset parameter even when the charset is ISO-8859-1 and <em class="bcp14">SHOULD</em> do so when it is known that it will not confuse the recipient.
     1395               </p>
     1396               <p id="rfc.section.3.4.1.p.2">Unfortunately, some older HTTP/1.0 clients did not deal properly with an explicit charset parameter. HTTP/1.1 recipients <em class="bcp14">MUST</em> respect the charset label provided by the sender; and those user agents that have a provision to "guess" a charset <em class="bcp14">MUST</em> use the charset from the content-type field if they support that charset, rather than the recipient's preference, when initially
     1397                  displaying a document. See <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;3.7.1</a>.
     1398               </p>
     1399            </div>
     1400         </div>
     1401         <div id="content.codings">
     1402            <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#content.codings">Content Codings</a></h2>
     1403            <p id="rfc.section.3.5.p.1">Content coding values indicate an encoding transformation that has been or can be applied to an entity. Content codings are
     1404               primarily used to allow a document to be compressed or otherwise usefully transformed without losing the identity of its underlying
     1405               media type and without loss of information. Frequently, the entity is stored in coded form, transmitted directly, and only
     1406               decoded by the recipient.
     1407            </p>
     1408            <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.39"></span>    content-coding   = token
    13791409</pre><p id="rfc.section.3.5.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;14.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;14.11</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    1380          mechanism will be required to remove the encoding.
    1381       </p>
    1382       <p id="rfc.section.3.5.p.4">The Internet Assigned Numbers Authority (IANA) acts as a registry for content-coding value tokens. Initially, the registry
    1383          contains the following tokens:
    1384       </p>
    1385       <p id="rfc.section.3.5.p.5">gzip<span id="rfc.iref.g.40"></span> 
    1386       </p>
    1387       <ul class="empty">
    1388          <li>An encoding format produced by the file compression program "gzip" (GNU zip) as described in RFC 1952 <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a>. This format is a Lempel-Ziv coding (LZ77) with a 32 bit CRC.
    1389          </li>
    1390       </ul>
    1391       <p id="rfc.section.3.5.p.6">compress<span id="rfc.iref.c.6"></span> 
    1392       </p>
    1393       <ul class="empty">
    1394          <li>The encoding format produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch
    1395             coding (LZW).
    1396          </li>
    1397          <li>Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings.
    1398             Their use here is representative of historical practice, not good design. For compatibility with previous implementations
    1399             of HTTP, applications <em class="bcp14">SHOULD</em> consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively.
    1400          </li>
    1401       </ul>
    1402       <p id="rfc.section.3.5.p.7">deflate<span id="rfc.iref.d.2"></span> 
    1403       </p>
    1404       <ul class="empty">
    1405          <li>The "zlib" format defined in RFC 1950 <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> in combination with the "deflate" compression mechanism described in RFC 1951 <a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>.
    1406          </li>
    1407       </ul>
    1408       <p id="rfc.section.3.5.p.8">identity<span id="rfc.iref.i.2"></span> 
    1409       </p>
    1410       <ul class="empty">
    1411          <li>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding
    1412             header, and <em class="bcp14">SHOULD NOT</em> be used in the Content-Encoding header.
    1413          </li>
    1414       </ul>
    1415       <p id="rfc.section.3.5.p.9">New content-coding value tokens <em class="bcp14">SHOULD</em> be registered; to allow interoperability between clients and servers, specifications of the content coding algorithms needed
    1416          to implement a new value <em class="bcp14">SHOULD</em> be publicly available and adequate for independent implementation, and conform to the purpose of content coding defined in
    1417          this section.
    1418       </p>
    1419       <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a id="transfer.codings" href="#transfer.codings">Transfer Codings</a></h2>
    1420       <p id="rfc.section.3.6.p.1">Transfer-coding values are used to indicate an encoding transformation that has been, can be, or may need to be applied to
    1421          an entity-body in order to ensure "safe transport" through the network. This differs from a content coding in that the transfer-coding
    1422          is a property of the message, not of the original entity.
    1423       </p>
    1424       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span>    transfer-coding         = "chunked" | transfer-extension
     1410               mechanism will be required to remove the encoding.
     1411            </p>
     1412            <p id="rfc.section.3.5.p.4">The Internet Assigned Numbers Authority (IANA) acts as a registry for content-coding value tokens. Initially, the registry
     1413               contains the following tokens:
     1414            </p>
     1415            <p id="rfc.section.3.5.p.5">gzip<span id="rfc.iref.g.40"></span>
     1416            </p>
     1417            <ul class="empty">
     1418               <li>An encoding format produced by the file compression program "gzip" (GNU zip) as described in RFC 1952 <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a>. This format is a Lempel-Ziv coding (LZ77) with a 32 bit CRC.
     1419               </li>
     1420            </ul>
     1421            <p id="rfc.section.3.5.p.6">compress<span id="rfc.iref.c.6"></span>
     1422            </p>
     1423            <ul class="empty">
     1424               <li>The encoding format produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch
     1425                  coding (LZW).
     1426               </li>
     1427               <li>Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings.
     1428                  Their use here is representative of historical practice, not good design. For compatibility with previous implementations
     1429                  of HTTP, applications <em class="bcp14">SHOULD</em> consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively.
     1430               </li>
     1431            </ul>
     1432            <p id="rfc.section.3.5.p.7">deflate<span id="rfc.iref.d.2"></span>
     1433            </p>
     1434            <ul class="empty">
     1435               <li>The "zlib" format defined in RFC 1950 <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> in combination with the "deflate" compression mechanism described in RFC 1951 <a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>.
     1436               </li>
     1437            </ul>
     1438            <p id="rfc.section.3.5.p.8">identity<span id="rfc.iref.i.2"></span>
     1439            </p>
     1440            <ul class="empty">
     1441               <li>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding
     1442                  header, and <em class="bcp14">SHOULD NOT</em> be used in the Content-Encoding header.
     1443               </li>
     1444            </ul>
     1445            <p id="rfc.section.3.5.p.9">New content-coding value tokens <em class="bcp14">SHOULD</em> be registered; to allow interoperability between clients and servers, specifications of the content coding algorithms needed
     1446               to implement a new value <em class="bcp14">SHOULD</em> be publicly available and adequate for independent implementation, and conform to the purpose of content coding defined in
     1447               this section.
     1448            </p>
     1449         </div>
     1450         <div id="transfer.codings">
     1451            <h2 id="rfc.section.3.6"><a href="#rfc.section.3.6">3.6</a>&nbsp;<a href="#transfer.codings">Transfer Codings</a></h2>
     1452            <p id="rfc.section.3.6.p.1">Transfer-coding values are used to indicate an encoding transformation that has been, can be, or may need to be applied to
     1453               an entity-body in order to ensure "safe transport" through the network. This differs from a content coding in that the transfer-coding
     1454               is a property of the message, not of the original entity.
     1455            </p>
     1456            <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span>    transfer-coding         = "chunked" | transfer-extension
    14251457    transfer-extension      = token *( ";" parameter )
    14261458</pre><p id="rfc.section.3.6.p.3">Parameters are in the form of attribute/value pairs.</p>
    1427       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span>    parameter               = attribute "=" value
     1459            <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span>    parameter               = attribute "=" value
    14281460    attribute               = token
    14291461    value                   = token | quoted-string
    14301462</pre><p id="rfc.section.3.6.p.5">All transfer-coding values are case-insensitive. HTTP/1.1 uses transfer-coding values in the TE header field (<a href="#header.te" id="rfc.xref.header.te.1" title="TE">Section&nbsp;14.39</a>) and in the Transfer-Encoding header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.1" title="Transfer-Encoding">Section&nbsp;14.41</a>).
    1431       </p>
    1432       <p id="rfc.section.3.6.p.6">Whenever a transfer-coding is applied to a message-body, the set of transfer-codings <em class="bcp14">MUST</em> include "chunked", unless the message is terminated by closing the connection. When the "chunked" transfer-coding is used,
    1433          it <em class="bcp14">MUST</em> be the last transfer-coding applied to the message-body. The "chunked" transfer-coding <em class="bcp14">MUST NOT</em> be applied more than once to a message-body. These rules allow the recipient to determine the transfer-length of the message
    1434          (<a href="#message.length" title="Message Length">Section&nbsp;4.4</a>).
    1435       </p>
    1436       <p id="rfc.section.3.6.p.7">Transfer-codings are analogous to the Content-Transfer-Encoding values of 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>, which were designed to enable safe transport of binary data over a 7-bit transport service. However, safe transport has
    1437          a different focus for an 8bit-clean transfer protocol. In HTTP, the only unsafe characteristic of message-bodies is the difficulty
    1438          in determining the exact body length (<a href="#entity.length" title="Entity Length">Section&nbsp;7.2.2</a>), or the desire to encrypt data over a shared transport.
    1439       </p>
    1440       <p id="rfc.section.3.6.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry
    1441          contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.6.1</a>), "identity" (section 3.6.2), "gzip" (<a href="#content.codings" title="Content Codings">Section&nbsp;3.5</a>), "compress" (<a href="#content.codings" title="Content Codings">Section&nbsp;3.5</a>), and "deflate" (<a href="#content.codings" title="Content Codings">Section&nbsp;3.5</a>).
    1442       </p>
    1443       <p id="rfc.section.3.6.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="#content.codings" title="Content Codings">Section&nbsp;3.5</a>).
    1444       </p>
    1445       <p id="rfc.section.3.6.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Unimplemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client.
    1446       </p>
    1447       <h3 id="rfc.section.3.6.1"><a href="#rfc.section.3.6.1">3.6.1</a>&nbsp;<a id="chunked.transfer.encoding" href="#chunked.transfer.encoding">Chunked Transfer Coding</a></h3>
    1448       <p id="rfc.section.3.6.1.p.1">The chunked encoding modifies the body of a message in order to transfer it as a series of chunks, each with its own size
    1449          indicator, followed by an <em class="bcp14">OPTIONAL</em> trailer containing entity-header fields. This allows dynamically produced content to be transferred along with the information
    1450          necessary for the recipient to verify that it has received the full message.
    1451       </p>
    1452       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span><span id="rfc.iref.g.52"></span><span id="rfc.iref.g.53"></span><span id="rfc.iref.g.54"></span>    Chunked-Body   = *chunk
     1463            </p>
     1464            <p id="rfc.section.3.6.p.6">Whenever a transfer-coding is applied to a message-body, the set of transfer-codings <em class="bcp14">MUST</em> include "chunked", unless the message is terminated by closing the connection. When the "chunked" transfer-coding is used,
     1465               it <em class="bcp14">MUST</em> be the last transfer-coding applied to the message-body. The "chunked" transfer-coding <em class="bcp14">MUST NOT</em> be applied more than once to a message-body. These rules allow the recipient to determine the transfer-length of the message
     1466               (<a href="#message.length" title="Message Length">Section&nbsp;4.4</a>).
     1467            </p>
     1468            <p id="rfc.section.3.6.p.7">Transfer-codings are analogous to the Content-Transfer-Encoding values of 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>, which were designed to enable safe transport of binary data over a 7-bit transport service. However, safe transport has
     1469               a different focus for an 8bit-clean transfer protocol. In HTTP, the only unsafe characteristic of message-bodies is the difficulty
     1470               in determining the exact body length (<a href="#entity.length" title="Entity Length">Section&nbsp;7.2.2</a>), or the desire to encrypt data over a shared transport.
     1471            </p>
     1472            <p id="rfc.section.3.6.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry
     1473               contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.6.1</a>), "identity" (section 3.6.2), "gzip" (<a href="#content.codings" title="Content Codings">Section&nbsp;3.5</a>), "compress" (<a href="#content.codings" title="Content Codings">Section&nbsp;3.5</a>), and "deflate" (<a href="#content.codings" title="Content Codings">Section&nbsp;3.5</a>).
     1474            </p>
     1475            <p id="rfc.section.3.6.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="#content.codings" title="Content Codings">Section&nbsp;3.5</a>).
     1476            </p>
     1477            <p id="rfc.section.3.6.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Unimplemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client.
     1478            </p>
     1479            <div id="chunked.transfer.encoding">
     1480               <h3 id="rfc.section.3.6.1"><a href="#rfc.section.3.6.1">3.6.1</a>&nbsp;<a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></h3>
     1481               <p id="rfc.section.3.6.1.p.1">The chunked encoding modifies the body of a message in order to transfer it as a series of chunks, each with its own size
     1482                  indicator, followed by an <em class="bcp14">OPTIONAL</em> trailer containing entity-header fields. This allows dynamically produced content to be transferred along with the information
     1483                  necessary for the recipient to verify that it has received the full message.
     1484               </p>
     1485               <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span><span id="rfc.iref.g.52"></span><span id="rfc.iref.g.53"></span><span id="rfc.iref.g.54"></span>    Chunked-Body   = *chunk
    14531486                     last-chunk
    14541487                     trailer
     
    14661499    trailer        = *(entity-header CRLF)
    14671500</pre><p id="rfc.section.3.6.1.p.3">The chunk-size field is a string of hex digits indicating the size of the chunk. The chunked encoding is ended by any chunk
    1468          whose size is zero, followed by the trailer, which is terminated by an empty line.
    1469       </p>
    1470       <p id="rfc.section.3.6.1.p.4">The trailer allows the sender to include additional HTTP header fields at the end of the message. The Trailer header field
    1471          can be used to indicate which header fields are included in a trailer (see <a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section&nbsp;14.40</a>).
    1472       </p>
    1473       <p id="rfc.section.3.6.1.p.5">A server using chunked transfer-coding in a response <em class="bcp14">MUST NOT</em> use the trailer for any header fields unless at least one of the following is true:
    1474       </p>
    1475       <ol>
    1476          <li>the request included a TE header field that indicates "trailers" is acceptable in the transfer-coding of the response, as
    1477             described in <a href="#header.te" id="rfc.xref.header.te.2" title="TE">Section&nbsp;14.39</a>; or,
    1478          </li>
    1479          <li>the server is the origin server for the response, the trailer fields consist entirely of optional metadata, and the recipient
    1480             could use the message (in a manner acceptable to the origin server) without receiving this metadata. In other words, the origin
    1481             server is willing to accept the possibility that the trailer fields might be silently discarded along the path to the client.
    1482          </li>
    1483       </ol>
    1484       <p id="rfc.section.3.6.1.p.6">This requirement prevents an interoperability failure when the message is being received by an HTTP/1.1 (or later) proxy and
    1485          forwarded to an HTTP/1.0 recipient. It avoids a situation where compliance with the protocol would have necessitated a possibly
    1486          infinite buffer on the proxy.
    1487       </p>
    1488       <p id="rfc.section.3.6.1.p.7">An example process for decoding a Chunked-Body is presented in <a href="#introduction.of.transfer-encoding" title="Introduction of Transfer-Encoding">Appendix&nbsp;19.4.6</a>.
    1489       </p>
    1490       <p id="rfc.section.3.6.1.p.8">All HTTP/1.1 applications <em class="bcp14">MUST</em> be able to receive and decode the "chunked" transfer-coding, and <em class="bcp14">MUST</em> ignore chunk-extension extensions they do not understand.
    1491       </p>
    1492       <h2 id="rfc.section.3.7"><a href="#rfc.section.3.7">3.7</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
    1493       <p id="rfc.section.3.7.p.1">HTTP uses Internet Media Types <a href="#RFC1590" id="rfc.xref.RFC1590.1"><cite title="Media Type Registration Procedure">[RFC1590]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;14.17</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;14.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
    1494       </p>
    1495       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span>    media-type     = type "/" subtype *( ";" parameter )
     1501                  whose size is zero, followed by the trailer, which is terminated by an empty line.
     1502               </p>
     1503               <p id="rfc.section.3.6.1.p.4">The trailer allows the sender to include additional HTTP header fields at the end of the message. The Trailer header field
     1504                  can be used to indicate which header fields are included in a trailer (see <a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section&nbsp;14.40</a>).
     1505               </p>
     1506               <p id="rfc.section.3.6.1.p.5">A server using chunked transfer-coding in a response <em class="bcp14">MUST NOT</em> use the trailer for any header fields unless at least one of the following is true:
     1507               </p>
     1508               <ol>
     1509                  <li>the request included a TE header field that indicates "trailers" is acceptable in the transfer-coding of the response, as
     1510                     described in <a href="#header.te" id="rfc.xref.header.te.2" title="TE">Section&nbsp;14.39</a>; or,
     1511                  </li>
     1512                  <li>the server is the origin server for the response, the trailer fields consist entirely of optional metadata, and the recipient
     1513                     could use the message (in a manner acceptable to the origin server) without receiving this metadata. In other words, the origin
     1514                     server is willing to accept the possibility that the trailer fields might be silently discarded along the path to the client.
     1515                  </li>
     1516               </ol>
     1517               <p id="rfc.section.3.6.1.p.6">This requirement prevents an interoperability failure when the message is being received by an HTTP/1.1 (or later) proxy and
     1518                  forwarded to an HTTP/1.0 recipient. It avoids a situation where compliance with the protocol would have necessitated a possibly
     1519                  infinite buffer on the proxy.
     1520               </p>
     1521               <p id="rfc.section.3.6.1.p.7">An example process for decoding a Chunked-Body is presented in <a href="#introduction.of.transfer-encoding" title="Introduction of Transfer-Encoding">Appendix&nbsp;19.4.6</a>.
     1522               </p>
     1523               <p id="rfc.section.3.6.1.p.8">All HTTP/1.1 applications <em class="bcp14">MUST</em> be able to receive and decode the "chunked" transfer-coding, and <em class="bcp14">MUST</em> ignore chunk-extension extensions they do not understand.
     1524               </p>
     1525            </div>
     1526         </div>
     1527         <div id="media.types">
     1528            <h2 id="rfc.section.3.7"><a href="#rfc.section.3.7">3.7</a>&nbsp;<a href="#media.types">Media Types</a></h2>
     1529            <p id="rfc.section.3.7.p.1">HTTP uses Internet Media Types <a href="#RFC1590" id="rfc.xref.RFC1590.1"><cite title="Media Type Registration Procedure">[RFC1590]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;14.17</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;14.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
     1530            </p>
     1531            <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span>    media-type     = type "/" subtype *( ";" parameter )
    14961532    type           = token
    14971533    subtype        = token
    14981534</pre><p id="rfc.section.3.7.p.3">Parameters <em class="bcp14">MAY</em> follow the type/subtype in the form of attribute/value pairs (as defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.6</a>).
    1499       </p>
    1500       <p id="rfc.section.3.7.p.4">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
    1501          depending on the semantics of the parameter name. Linear white space (LWS) <em class="bcp14">MUST NOT</em> be used between the type and subtype, nor between an attribute and its value. The presence or absence of a parameter might
    1502          be significant to the processing of a media-type, depending on its definition within the media type registry.
    1503       </p>
    1504       <p id="rfc.section.3.7.p.5">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
    1505          implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
    1506       </p>
    1507       <p id="rfc.section.3.7.p.6">Media-type values are registered with the Internet Assigned Number Authority (IANA <a href="#RFC1700" id="rfc.xref.RFC1700.4"><cite title="Assigned Numbers">[RFC1700]</cite></a>). The media type registration process is outlined in RFC 1590 <a href="#RFC1590" id="rfc.xref.RFC1590.2"><cite title="Media Type Registration Procedure">[RFC1590]</cite></a>. Use of non-registered media types is discouraged.
    1508       </p>
    1509       <h3 id="rfc.section.3.7.1"><a href="#rfc.section.3.7.1">3.7.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
    1510       <p id="rfc.section.3.7.1.p.1">Internet media types are registered with a canonical form. An entity-body transferred via HTTP messages <em class="bcp14">MUST</em> be represented in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next
    1511          paragraph.
    1512       </p>
    1513       <p id="rfc.section.3.7.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and
    1514          allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
    1515          entire entity-body. HTTP applications <em class="bcp14">MUST</em> accept CRLF, bare CR, and bare LF as being representative of a line break in text media received via HTTP. In addition, if
    1516          the text is represented in a character set that does not use octets 13 and 10 for CR and LF respectively, as is the case for
    1517          some multi-byte character sets, HTTP allows the use of whatever octet sequences are defined by that character set to represent
    1518          the equivalent of CR and LF for line breaks. This flexibility regarding line breaks applies only to text media in the entity-body;
    1519          a bare CR or LF <em class="bcp14">MUST NOT</em> be substituted for CRLF within any of the HTTP control structures (such as header fields and multipart boundaries).
    1520       </p>
    1521       <p id="rfc.section.3.7.1.p.3">If an entity-body is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
    1522       </p>
    1523       <p id="rfc.section.3.7.1.p.4">The "charset" parameter is used with some media types to define the character set (<a href="#character.sets" title="Character Sets">Section&nbsp;3.4</a>) of the data. When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined
    1524          to have a default charset value of "ISO-8859-1" when received via HTTP. Data in character sets other than "ISO-8859-1" or
    1525          its subsets <em class="bcp14">MUST</em> be labeled with an appropriate charset value. See <a href="#missing.charset" title="Missing Charset">Section&nbsp;3.4.1</a> for compatibility problems.
    1526       </p>
    1527       <h3 id="rfc.section.3.7.2"><a href="#rfc.section.3.7.2">3.7.2</a>&nbsp;<a id="multipart.types" href="#multipart.types">Multipart Types</a></h3>
    1528       <p id="rfc.section.3.7.2.p.1">MIME provides for a number of "multipart" types -- encapsulations of one or more entities within a single message-body. All
    1529          multipart types share a common syntax, as defined in section <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1" id="rfc.xref.RFC2046.1">5.1.1</a> of RFC 2046 <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and <em class="bcp14">MUST</em> include a boundary parameter as part of the media type value. The message body is itself a protocol element and <em class="bcp14">MUST</em> therefore use only CRLF to represent line breaks between body-parts. Unlike in RFC 2046, the epilogue of any multipart message <em class="bcp14">MUST</em> be empty; HTTP applications <em class="bcp14">MUST NOT</em> transmit the epilogue (even if the original multipart contains an epilogue). These restrictions exist in order to preserve
    1530          the self-delimiting nature of a multipart message-body, wherein the "end" of the message-body is indicated by the ending multipart
    1531          boundary.
    1532       </p>
    1533       <p id="rfc.section.3.7.2.p.2">In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. The one exception
    1534          is the "multipart/byteranges" type (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;19.2</a>) when it appears in a 206 (Partial Content) response, which will be interpreted by some HTTP caching mechanisms as described
    1535          in sections <a href="#combining.byte.ranges" title="Combining Byte Ranges">13.5.4</a> and <a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">14.16</a>. In all other cases, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. The MIME header fields within
    1536          each body-part of a multipart message-body do not have any significance to HTTP beyond that defined by their MIME semantics.
    1537       </p>
    1538       <p id="rfc.section.3.7.2.p.3">In general, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. If an application receives
    1539          an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
    1540       </p>
    1541       <ul class="empty">
    1542          <li> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
    1543             method, as described in RFC 1867 <a href="#RFC1867" id="rfc.xref.RFC1867.1"><cite title="Form-based File Upload in HTML">[RFC1867]</cite></a>.
    1544          </li>
    1545       </ul>
    1546       <h2 id="rfc.section.3.8"><a href="#rfc.section.3.8">3.8</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h2>
    1547       <p id="rfc.section.3.8.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
    1548          using product tokens also allow sub-products which form a significant part of the application to be listed, separated by white
    1549          space. By convention, the products are listed in order of their significance for identifying the application.
    1550       </p>
    1551       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span>    product         = token ["/" product-version]
     1535            </p>
     1536            <p id="rfc.section.3.7.p.4">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive,
     1537               depending on the semantics of the parameter name. Linear white space (LWS) <em class="bcp14">MUST NOT</em> be used between the type and subtype, nor between an attribute and its value. The presence or absence of a parameter might
     1538               be significant to the processing of a media-type, depending on its definition within the media type registry.
     1539            </p>
     1540            <p id="rfc.section.3.7.p.5">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
     1541               implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
     1542            </p>
     1543            <p id="rfc.section.3.7.p.6">Media-type values are registered with the Internet Assigned Number Authority (IANA <a href="#RFC1700" id="rfc.xref.RFC1700.4"><cite title="Assigned Numbers">[RFC1700]</cite></a>). The media type registration process is outlined in RFC 1590 <a href="#RFC1590" id="rfc.xref.RFC1590.2"><cite title="Media Type Registration Procedure">[RFC1590]</cite></a>. Use of non-registered media types is discouraged.
     1544            </p>
     1545            <div id="canonicalization.and.text.defaults">
     1546               <h3 id="rfc.section.3.7.1"><a href="#rfc.section.3.7.1">3.7.1</a>&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
     1547               <p id="rfc.section.3.7.1.p.1">Internet media types are registered with a canonical form. An entity-body transferred via HTTP messages <em class="bcp14">MUST</em> be represented in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next
     1548                  paragraph.
     1549               </p>
     1550               <p id="rfc.section.3.7.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and
     1551                  allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an
     1552                  entire entity-body. HTTP applications <em class="bcp14">MUST</em> accept CRLF, bare CR, and bare LF as being representative of a line break in text media received via HTTP. In addition, if
     1553                  the text is represented in a character set that does not use octets 13 and 10 for CR and LF respectively, as is the case for
     1554                  some multi-byte character sets, HTTP allows the use of whatever octet sequences are defined by that character set to represent
     1555                  the equivalent of CR and LF for line breaks. This flexibility regarding line breaks applies only to text media in the entity-body;
     1556                  a bare CR or LF <em class="bcp14">MUST NOT</em> be substituted for CRLF within any of the HTTP control structures (such as header fields and multipart boundaries).
     1557               </p>
     1558               <p id="rfc.section.3.7.1.p.3">If an entity-body is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded.
     1559               </p>
     1560               <p id="rfc.section.3.7.1.p.4">The "charset" parameter is used with some media types to define the character set (<a href="#character.sets" title="Character Sets">Section&nbsp;3.4</a>) of the data. When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined
     1561                  to have a default charset value of "ISO-8859-1" when received via HTTP. Data in character sets other than "ISO-8859-1" or
     1562                  its subsets <em class="bcp14">MUST</em> be labeled with an appropriate charset value. See <a href="#missing.charset" title="Missing Charset">Section&nbsp;3.4.1</a> for compatibility problems.
     1563               </p>
     1564            </div>
     1565            <div id="multipart.types">
     1566               <h3 id="rfc.section.3.7.2"><a href="#rfc.section.3.7.2">3.7.2</a>&nbsp;<a href="#multipart.types">Multipart Types</a></h3>
     1567               <p id="rfc.section.3.7.2.p.1">MIME provides for a number of "multipart" types -- encapsulations of one or more entities within a single message-body. All
     1568                  multipart types share a common syntax, as defined in section <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1" id="rfc.xref.RFC2046.1">5.1.1</a> of RFC 2046 <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and <em class="bcp14">MUST</em> include a boundary parameter as part of the media type value. The message body is itself a protocol element and <em class="bcp14">MUST</em> therefore use only CRLF to represent line breaks between body-parts. Unlike in RFC 2046, the epilogue of any multipart message <em class="bcp14">MUST</em> be empty; HTTP applications <em class="bcp14">MUST NOT</em> transmit the epilogue (even if the original multipart contains an epilogue). These restrictions exist in order to preserve
     1569                  the self-delimiting nature of a multipart message-body, wherein the "end" of the message-body is indicated by the ending multipart
     1570                  boundary.
     1571               </p>
     1572               <p id="rfc.section.3.7.2.p.2">In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. The one exception
     1573                  is the "multipart/byteranges" type (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;19.2</a>) when it appears in a 206 (Partial Content) response, which will be interpreted by some HTTP caching mechanisms as described
     1574                  in sections <a href="#combining.byte.ranges" title="Combining Byte Ranges">13.5.4</a> and <a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">14.16</a>. In all other cases, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. The MIME header fields within
     1575                  each body-part of a multipart message-body do not have any significance to HTTP beyond that defined by their MIME semantics.
     1576               </p>
     1577               <p id="rfc.section.3.7.2.p.3">In general, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. If an application receives
     1578                  an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed".
     1579               </p>
     1580               <ul class="empty">
     1581                  <li><b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request
     1582                     method, as described in RFC 1867 <a href="#RFC1867" id="rfc.xref.RFC1867.1"><cite title="Form-based File Upload in HTML">[RFC1867]</cite></a>.
     1583                  </li>
     1584               </ul>
     1585            </div>
     1586         </div>
     1587         <div id="product.tokens">
     1588            <h2 id="rfc.section.3.8"><a href="#rfc.section.3.8">3.8</a>&nbsp;<a href="#product.tokens">Product Tokens</a></h2>
     1589            <p id="rfc.section.3.8.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
     1590               using product tokens also allow sub-products which form a significant part of the application to be listed, separated by white
     1591               space. By convention, the products are listed in order of their significance for identifying the application.
     1592            </p>
     1593            <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span>    product         = token ["/" product-version]
    15521594    product-version = token
    15531595</pre><p id="rfc.section.3.8.p.3">Examples:</p>
    1554       <div id="rfc.figure.u.26"></div><pre class="text">    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     1596            <div id="rfc.figure.u.26"></div><pre class="text">    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    15551597    Server: Apache/0.8.4
    15561598</pre><p id="rfc.section.3.8.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token character <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
    1557       </p>
    1558       <h2 id="rfc.section.3.9"><a href="#rfc.section.3.9">3.9</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h2>
    1559       <p id="rfc.section.3.9.p.1">HTTP content negotiation (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;12</a>) uses short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
    1560          is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has
    1561          a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
    1562       </p>
    1563       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.60"></span>    qvalue         = ( "0" [ "." 0*3DIGIT ] )
     1599            </p>
     1600         </div>
     1601         <div id="quality.values">
     1602            <h2 id="rfc.section.3.9"><a href="#rfc.section.3.9">3.9</a>&nbsp;<a href="#quality.values">Quality Values</a></h2>
     1603            <p id="rfc.section.3.9.p.1">HTTP content negotiation (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;12</a>) uses short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
     1604               is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has
     1605               a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
     1606            </p>
     1607            <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.60"></span>    qvalue         = ( "0" [ "." 0*3DIGIT ] )
    15641608                   | ( "1" [ "." 0*3("0") ] )
    15651609</pre><p id="rfc.section.3.9.p.3">"Quality values" is a misnomer, since these values merely represent relative degradation in desired quality.</p>
    1566       <h2 id="rfc.section.3.10"><a href="#rfc.section.3.10">3.10</a>&nbsp;<a id="language.tags" href="#language.tags">Language Tags</a></h2>
    1567       <p id="rfc.section.3.10.p.1">A language tag identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information
    1568          to other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and
    1569          Content-Language fields.
    1570       </p>
    1571       <p id="rfc.section.3.10.p.2">The syntax and registry of HTTP language tags is the same as that defined by RFC 1766 <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags:
    1572       </p>
    1573       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span>     language-tag  = primary-tag *( "-" subtag )
     1610         </div>
     1611         <div id="language.tags">
     1612            <h2 id="rfc.section.3.10"><a href="#rfc.section.3.10">3.10</a>&nbsp;<a href="#language.tags">Language Tags</a></h2>
     1613            <p id="rfc.section.3.10.p.1">A language tag identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information
     1614               to other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and
     1615               Content-Language fields.
     1616            </p>
     1617            <p id="rfc.section.3.10.p.2">The syntax and registry of HTTP language tags is the same as that defined by RFC 1766 <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags:
     1618            </p>
     1619            <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span>     language-tag  = primary-tag *( "-" subtag )
    15741620     primary-tag   = 1*8ALPHA
    15751621     subtag        = 1*8ALPHA
    15761622</pre><p id="rfc.section.3.10.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language tags is administered
    1577          by the IANA. Example tags include:
    1578       </p>
    1579       <div id="rfc.figure.u.29"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin
     1623               by the IANA. Example tags include:
     1624            </p>
     1625            <div id="rfc.figure.u.29"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin
    15801626</pre><p id="rfc.section.3.10.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country
    1581          code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered
    1582          in future.)
    1583       </p>
    1584       <h2 id="rfc.section.3.11"><a href="#rfc.section.3.11">3.11</a>&nbsp;<a id="entity.tags" href="#entity.tags">Entity Tags</a></h2>
    1585       <p id="rfc.section.3.11.p.1">Entity tags are used for comparing two or more entities from the same requested resource. HTTP/1.1 uses entity tags in the
    1586          ETag (<a href="#header.etag" id="rfc.xref.header.etag.1" title="ETag">Section&nbsp;14.19</a>), If-Match (<a href="#header.if-match" id="rfc.xref.header.if-match.1" title="If-Match">Section&nbsp;14.24</a>), If-None-Match (<a href="#header.if-none-match" id="rfc.xref.header.if-none-match.1" title="If-None-Match">Section&nbsp;14.26</a>), and If-Range (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;14.27</a>) header fields. The definition of how they are used and compared as cache validators is in <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;13.3.3</a>. An entity tag consists of an opaque quoted string, possibly prefixed by a weakness indicator.
    1587       </p>
    1588       <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span>   entity-tag = [ weak ] opaque-tag
     1627               code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered
     1628               in future.)
     1629            </p>
     1630         </div>
     1631         <div id="entity.tags">
     1632            <h2 id="rfc.section.3.11"><a href="#rfc.section.3.11">3.11</a>&nbsp;<a href="#entity.tags">Entity Tags</a></h2>
     1633            <p id="rfc.section.3.11.p.1">Entity tags are used for comparing two or more entities from the same requested resource. HTTP/1.1 uses entity tags in the
     1634               ETag (<a href="#header.etag" id="rfc.xref.header.etag.1" title="ETag">Section&nbsp;14.19</a>), If-Match (<a href="#header.if-match" id="rfc.xref.header.if-match.1" title="If-Match">Section&nbsp;14.24</a>), If-None-Match (<a href="#header.if-none-match" id="rfc.xref.header.if-none-match.1" title="If-None-Match">Section&nbsp;14.26</a>), and If-Range (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section&nbsp;14.27</a>) header fields. The definition of how they are used and compared as cache validators is in <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;13.3.3</a>. An entity tag consists of an opaque quoted string, possibly prefixed by a weakness indicator.
     1635            </p>
     1636            <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span>   entity-tag = [ weak ] opaque-tag
    15891637   weak       = "W/"
    15901638   opaque-tag = quoted-string
    15911639</pre><p id="rfc.section.3.11.p.3">A "strong entity tag" <em class="bcp14">MAY</em> be shared by two entities of a resource only if they are equivalent by octet equality.
    1592       </p>
    1593       <p id="rfc.section.3.11.p.4">A "weak entity tag," indicated by the "W/" prefix, <em class="bcp14">MAY</em> be shared by two entities of a resource only if the entities are equivalent and could be substituted for each other with no
    1594          significant change in semantics. A weak entity tag can only be used for weak comparison.
    1595       </p>
    1596       <p id="rfc.section.3.11.p.5">An entity tag <em class="bcp14">MUST</em> be unique across all versions of all entities associated with a particular resource. A given entity tag value <em class="bcp14">MAY</em> be used for entities obtained by requests on different URIs. The use of the same entity tag value in conjunction with entities
    1597          obtained by requests on different URIs does not imply the equivalence of those entities.
    1598       </p>
    1599       <h2 id="rfc.section.3.12"><a href="#rfc.section.3.12">3.12</a>&nbsp;<a id="range.units" href="#range.units">Range Units</a></h2>
    1600       <p id="rfc.section.3.12.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1
    1601          uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;14.35</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;14.16</a>) header fields. An entity can be broken down into subranges according to various structural units.
    1602       </p>
    1603       <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.67"></span><span id="rfc.iref.g.68"></span><span id="rfc.iref.g.69"></span>   range-unit       = bytes-unit | other-range-unit
     1640            </p>
     1641            <p id="rfc.section.3.11.p.4">A "weak entity tag," indicated by the "W/" prefix, <em class="bcp14">MAY</em> be shared by two entities of a resource only if the entities are equivalent and could be substituted for each other with no
     1642               significant change in semantics. A weak entity tag can only be used for weak comparison.
     1643            </p>
     1644            <p id="rfc.section.3.11.p.5">An entity tag <em class="bcp14">MUST</em> be unique across all versions of all entities associated with a particular resource. A given entity tag value <em class="bcp14">MAY</em> be used for entities obtained by requests on different URIs. The use of the same entity tag value in conjunction with entities
     1645               obtained by requests on different URIs does not imply the equivalence of those entities.
     1646            </p>
     1647         </div>
     1648         <div id="range.units">
     1649            <h2 id="rfc.section.3.12"><a href="#rfc.section.3.12">3.12</a>&nbsp;<a href="#range.units">Range Units</a></h2>
     1650            <p id="rfc.section.3.12.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1
     1651               uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section&nbsp;14.35</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;14.16</a>) header fields. An entity can be broken down into subranges according to various structural units.
     1652            </p>
     1653            <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.67"></span><span id="rfc.iref.g.68"></span><span id="rfc.iref.g.69"></span>   range-unit       = bytes-unit | other-range-unit
    16041654   bytes-unit       = "bytes"
    16051655   other-range-unit = token
    16061656</pre><p id="rfc.section.3.12.p.3">The only range unit defined by HTTP/1.1 is "bytes". HTTP/1.1 implementations <em class="bcp14">MAY</em> ignore ranges specified using other units.
    1607       </p>
    1608       <p id="rfc.section.3.12.p.4">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges.</p>
    1609       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="http.message" href="#http.message">HTTP Message</a></h1>
    1610       <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="message.types" href="#message.types">Message Types</a></h2>
    1611       <p id="rfc.section.4.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p>
    1612       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.70"></span>    HTTP-message   = Request | Response     ; HTTP/1.1 messages
     1657            </p>
     1658            <p id="rfc.section.3.12.p.4">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges.</p>
     1659         </div>
     1660      </div>
     1661      <div id="http.message">
     1662         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#http.message">HTTP Message</a></h1>
     1663         <div id="message.types">
     1664            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#message.types">Message Types</a></h2>
     1665            <p id="rfc.section.4.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p>
     1666            <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.70"></span>    HTTP-message   = Request | Response     ; HTTP/1.1 messages
    16131667</pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section&nbsp;5</a>) and Response (<a href="#response" title="Response">Section&nbsp;6</a>) messages use the generic message format of RFC 822 <a href="#RFC822" id="rfc.xref.RFC822.4"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header
    1614          fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header
    1615          fields, and possibly a message-body.
    1616       </p>
    1617       <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.71"></span><span id="rfc.iref.g.72"></span>     generic-message = start-line
     1668               fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header
     1669               fields, and possibly a message-body.
     1670            </p>
     1671            <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.71"></span><span id="rfc.iref.g.72"></span>     generic-message = start-line
    16181672                       *(message-header CRLF)
    16191673                       CRLF
     
    16211675     start-line      = Request-Line | Status-Line
    16221676</pre><p id="rfc.section.4.1.p.5">In the interest of robustness, servers <em class="bcp14">SHOULD</em> ignore any empty line(s) received where a Request-Line is expected. In other words, if the server is reading the protocol
    1623          stream at the beginning of a message and receives a CRLF first, it should ignore the CRLF.
    1624       </p>
    1625       <p id="rfc.section.4.1.p.6">Certain buggy HTTP/1.0 client implementations generate extra CRLF's after a POST request. To restate what is explicitly forbidden
    1626          by the BNF, an HTTP/1.1 client <em class="bcp14">MUST NOT</em> preface or follow a request with an extra CRLF.
    1627       </p>
    1628       <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="message.headers" href="#message.headers">Message Headers</a></h2>
    1629       <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>), request-header (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5.3</a>), response-header (<a href="#response.header.fields" title="Response Header Fields">Section&nbsp;6.2</a>), and entity-header (<a href="#entity.header.fields" title="Entity Header Fields">Section&nbsp;7.1</a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc822#section-3.1" id="rfc.xref.RFC822.5">Section 3.1</a> of RFC 822 <a href="#RFC822" id="rfc.xref.RFC822.6"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The
    1630          field value <em class="bcp14">MAY</em> be preceded by any amount of LWS, though a single SP is preferred. Header fields can be extended over multiple lines by preceding
    1631          each extra line with at least one SP or HT. Applications ought to follow "common form", where one is known or indicated, when
    1632          generating HTTP constructs, since there might exist some implementations that fail to accept anything beyond the common forms.
    1633       </p>
    1634       <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.73"></span><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span>    message-header = field-name ":" [ field-value ]
     1677               stream at the beginning of a message and receives a CRLF first, it should ignore the CRLF.
     1678            </p>
     1679            <p id="rfc.section.4.1.p.6">Certain buggy HTTP/1.0 client implementations generate extra CRLF's after a POST request. To restate what is explicitly forbidden
     1680               by the BNF, an HTTP/1.1 client <em class="bcp14">MUST NOT</em> preface or follow a request with an extra CRLF.
     1681            </p>
     1682         </div>
     1683         <div id="message.headers">
     1684            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#message.headers">Message Headers</a></h2>
     1685            <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>), request-header (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5.3</a>), response-header (<a href="#response.header.fields" title="Response Header Fields">Section&nbsp;6.2</a>), and entity-header (<a href="#entity.header.fields" title="Entity Header Fields">Section&nbsp;7.1</a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc822#section-3.1" id="rfc.xref.RFC822.5">Section 3.1</a> of RFC 822 <a href="#RFC822" id="rfc.xref.RFC822.6"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The
     1686               field value <em class="bcp14">MAY</em> be preceded by any amount of LWS, though a single SP is preferred. Header fields can be extended over multiple lines by preceding
     1687               each extra line with at least one SP or HT. Applications ought to follow "common form", where one is known or indicated, when
     1688               generating HTTP constructs, since there might exist some implementations that fail to accept anything beyond the common forms.
     1689            </p>
     1690            <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.73"></span><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span>    message-header = field-name ":" [ field-value ]
    16351691    field-name     = token
    16361692    field-value    = *( field-content | LWS )
     
    16391695                     of token, separators, and quoted-string&gt;
    16401696</pre><p id="rfc.section.4.2.p.3">The field-content does not include any leading or trailing LWS: linear white space occurring before the first non-whitespace
    1641          character of the field-value or after the last non-whitespace character of the field-value. Such leading or trailing LWS <em class="bcp14">MAY</em> be removed without changing the semantics of the field value. Any LWS that occurs between field-content <em class="bcp14">MAY</em> be replaced with a single SP before interpreting the field value or forwarding the message downstream.
    1642       </p>
    1643       <p id="rfc.section.4.2.p.4">The order in which header fields with differing field names are received is not significant. However, it is "good practice"
    1644          to send general-header fields first, followed by request-header or response-header fields, and ending with the entity-header
    1645          fields.
    1646       </p>
    1647       <p id="rfc.section.4.2.p.5">Multiple message-header fields with the same field-name <em class="bcp14">MAY</em> be present in a message if and only if the entire field-value for that header field is defined as a comma-separated list [i.e.,
    1648          #(values)]. It <em class="bcp14">MUST</em> be possible to combine the multiple header fields into one "field-name: field-value" pair, without changing the semantics
    1649          of the message, by appending each subsequent field-value to the first, each separated by a comma. The order in which header
    1650          fields with the same field-name are received is therefore significant to the interpretation of the combined field value, and
    1651          thus a proxy <em class="bcp14">MUST NOT</em> change the order of these field values when a message is forwarded.
    1652       </p>
    1653       <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="message.body" href="#message.body">Message Body</a></h2>
    1654       <p id="rfc.section.4.3.p.1">The message-body (if any) of an HTTP message is used to carry the entity-body associated with the request or response. The
    1655          message-body differs from the entity-body only when a transfer-coding has been applied, as indicated by the Transfer-Encoding
    1656          header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.2" title="Transfer-Encoding">Section&nbsp;14.41</a>).
    1657       </p>
    1658       <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.77"></span>    message-body = entity-body
     1697               character of the field-value or after the last non-whitespace character of the field-value. Such leading or trailing LWS <em class="bcp14">MAY</em> be removed without changing the semantics of the field value. Any LWS that occurs between field-content <em class="bcp14">MAY</em> be replaced with a single SP before interpreting the field value or forwarding the message downstream.
     1698            </p>
     1699            <p id="rfc.section.4.2.p.4">The order in which header fields with differing field names are received is not significant. However, it is "good practice"
     1700               to send general-header fields first, followed by request-header or response-header fields, and ending with the entity-header
     1701               fields.
     1702            </p>
     1703            <p id="rfc.section.4.2.p.5">Multiple message-header fields with the same field-name <em class="bcp14">MAY</em> be present in a message if and only if the entire field-value for that header field is defined as a comma-separated list [i.e.,
     1704               #(values)]. It <em class="bcp14">MUST</em> be possible to combine the multiple header fields into one "field-name: field-value" pair, without changing the semantics
     1705               of the message, by appending each subsequent field-value to the first, each separated by a comma. The order in which header
     1706               fields with the same field-name are received is therefore significant to the interpretation of the combined field value, and
     1707               thus a proxy <em class="bcp14">MUST NOT</em> change the order of these field values when a message is forwarded.
     1708            </p>
     1709         </div>
     1710         <div id="message.body">
     1711            <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#message.body">Message Body</a></h2>
     1712            <p id="rfc.section.4.3.p.1">The message-body (if any) of an HTTP message is used to carry the entity-body associated with the request or response. The
     1713               message-body differs from the entity-body only when a transfer-coding has been applied, as indicated by the Transfer-Encoding
     1714               header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.2" title="Transfer-Encoding">Section&nbsp;14.41</a>).
     1715            </p>
     1716            <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.77"></span>    message-body = entity-body
    16591717                 | &lt;entity-body encoded as per Transfer-Encoding&gt;
    16601718</pre><p id="rfc.section.4.3.p.3">Transfer-Encoding <em class="bcp14">MUST</em> be used to indicate any transfer-codings applied by an application to ensure safe and proper transfer of the message. Transfer-Encoding
    1661          is a property of the message, not of the entity, and thus <em class="bcp14">MAY</em> be added or removed by any application along the request/response chain. (However, <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.6</a> places restrictions on when certain transfer-codings may be used.)
    1662       </p>
    1663       <p id="rfc.section.4.3.p.4">The rules for when a message-body is allowed in a message differ for requests and responses.</p>
    1664       <p id="rfc.section.4.3.p.5">The presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field
    1665          in the request's message-headers. A message-body <em class="bcp14">MUST NOT</em> be included in a request if the specification of the request method (<a href="#method" title="Method">Section&nbsp;5.1.1</a>) does not allow sending an entity-body in requests. A server <em class="bcp14">SHOULD</em> read and forward a message-body on any request; if the request method does not include defined semantics for an entity-body,
    1666          then the message-body <em class="bcp14">SHOULD</em> be ignored when handling the request.
    1667       </p>
    1668       <p id="rfc.section.4.3.p.6">For response messages, whether or not a message-body is included with a message is dependent on both the request method and
    1669          the response status code (<a href="#status.code.and.reason.phrase" title="Status Code and Reason Phrase">Section&nbsp;6.1.1</a>). All responses to the HEAD request method <em class="bcp14">MUST NOT</em> include a message-body, even though the presence of entity-header fields might lead one to believe they do. All 1xx (informational),
    1670          204 (no content), and 304 (not modified) responses <em class="bcp14">MUST NOT</em> include a message-body. All other responses do include a message-body, although it <em class="bcp14">MAY</em> be of zero length.
    1671       </p>
    1672       <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a id="message.length" href="#message.length">Message Length</a></h2>
    1673       <p id="rfc.section.4.4.p.1">The transfer-length of a message is the length of the message-body as it appears in the message; that is, after any transfer-codings
    1674          have been applied. When a message-body is included with a message, the transfer-length of that body is determined by one of
    1675          the following (in order of precedence):
    1676       </p>
    1677       <p id="rfc.section.4.4.p.2"> </p>
    1678       <ol>
    1679          <li>
    1680             <p>Any response message which "<em class="bcp14">MUST NOT</em>" include a message-body (such as the 1xx, 204, and 304 responses and any response to a HEAD request) is always terminated
    1681                by the first empty line after the header fields, regardless of the entity-header fields present in the message.
    1682             </p>
    1683          </li>
    1684          <li>
    1685             <p>If a Transfer-Encoding header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section&nbsp;14.41</a>) is present and has any value other than "identity", then the transfer-length is defined by use of the "chunked" transfer-coding
    1686                (<a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.6</a>), unless the message is terminated by closing the connection.
    1687             </p>
    1688          </li>
    1689          <li>
    1690             <p>If a Content-Length header field (<a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;14.13</a>) is present, its decimal value in OCTETs represents both the entity-length and the transfer-length. The Content-Length header
    1691                field <em class="bcp14">MUST NOT</em> be sent if these two lengths are different (i.e., if a Transfer-Encoding header field is present). If a message is received
    1692                with both a Transfer-Encoding header field and a Content-Length header field, the latter <em class="bcp14">MUST</em> be ignored.
    1693             </p>
    1694          </li>
    1695          <li>
    1696             <p>If the message uses the media type "multipart/byteranges", and the ransfer-length is not otherwise specified, then this self-elimiting
    1697                media type defines the transfer-length. This media type UST NOT be used unless the sender knows that the recipient can arse
    1698                it; the presence in a request of a Range header with ultiple byte-range specifiers from a 1.1 client implies that the lient
    1699                can parse multipart/byteranges responses.
    1700             </p>
    1701             <ul class="empty">
    1702                <li>A range header might be forwarded by a 1.0 proxy that does not understand multipart/byteranges; in this case the server <em class="bcp14">MUST</em> delimit the message using methods defined in items 1, 3 or 5 of this section.
    1703                </li>
    1704             </ul>
    1705          </li>
    1706          <li>
    1707             <p>By the server closing the connection. (Closing the connection cannot be used to indicate the end of a request body, since
    1708                that would leave no possibility for the server to send back a response.)
    1709             </p>
    1710          </li>
    1711       </ol>
    1712       <p id="rfc.section.4.4.p.3">For compatibility with HTTP/1.0 applications, HTTP/1.1 requests containing a message-body <em class="bcp14">MUST</em> include a valid Content-Length header field unless the server is known to be HTTP/1.1 compliant. If a request contains a message-body
    1713          and a Content-Length is not given, the server <em class="bcp14">SHOULD</em> respond with 400 (bad request) if it cannot determine the length of the message, or with 411 (length required) if it wishes
    1714          to insist on receiving a valid Content-Length.
    1715       </p>
    1716       <p id="rfc.section.4.4.p.4">All HTTP/1.1 applications that receive entities <em class="bcp14">MUST</em> accept the "chunked" transfer-coding (<a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.6</a>), thus allowing this mechanism to be used for messages when the message length cannot be determined in advance.
    1717       </p>
    1718       <p id="rfc.section.4.4.p.5">Messages <em class="bcp14">MUST NOT</em> include both a Content-Length header field and a non-identity transfer-coding. If the message does include a non-identity
    1719          transfer-coding, the Content-Length <em class="bcp14">MUST</em> be ignored.
    1720       </p>
    1721       <p id="rfc.section.4.4.p.6">When a Content-Length is given in a message where a message-body is allowed, its field value <em class="bcp14">MUST</em> exactly match the number of OCTETs in the message-body. HTTP/1.1 user agents <em class="bcp14">MUST</em> notify the user when an invalid length is received and detected.
    1722       </p>
    1723       <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;<a id="general.header.fields" href="#general.header.fields">General Header Fields</a></h2>
    1724       <p id="rfc.section.4.5.p.1">There are a few header fields which have general applicability for both request and response messages, but which do not apply
    1725          to the entity being transferred. These header fields apply only to the message being transmitted.
    1726       </p>
    1727       <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.78"></span>    general-header = Cache-Control            ; <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section&nbsp;14.9</a>
     1719               is a property of the message, not of the entity, and thus <em class="bcp14">MAY</em> be added or removed by any application along the request/response chain. (However, <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.6</a> places restrictions on when certain transfer-codings may be used.)
     1720            </p>
     1721            <p id="rfc.section.4.3.p.4">The rules for when a message-body is allowed in a message differ for requests and responses.</p>
     1722            <p id="rfc.section.4.3.p.5">The presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field
     1723               in the request's message-headers. A message-body <em class="bcp14">MUST NOT</em> be included in a request if the specification of the request method (<a href="#method" title="Method">Section&nbsp;5.1.1</a>) does not allow sending an entity-body in requests. A server <em class="bcp14">SHOULD</em> read and forward a message-body on any request; if the request method does not include defined semantics for an entity-body,
     1724               then the message-body <em class="bcp14">SHOULD</em> be ignored when handling the request.
     1725            </p>
     1726            <p id="rfc.section.4.3.p.6">For response messages, whether or not a message-body is included with a message is dependent on both the request method and
     1727               the response status code (<a href="#status.code.and.reason.phrase" title="Status Code and Reason Phrase">Section&nbsp;6.1.1</a>). All responses to the HEAD request method <em class="bcp14">MUST NOT</em> include a message-body, even though the presence of entity-header fields might lead one to believe they do. All 1xx (informational),
     1728               204 (no content), and 304 (not modified) responses <em class="bcp14">MUST NOT</em> include a message-body. All other responses do include a message-body, although it <em class="bcp14">MAY</em> be of zero length.
     1729            </p>
     1730         </div>
     1731         <div id="message.length">
     1732            <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#message.length">Message Length</a></h2>
     1733            <p id="rfc.section.4.4.p.1">The transfer-length of a message is the length of the message-body as it appears in the message; that is, after any transfer-codings
     1734               have been applied. When a message-body is included with a message, the transfer-length of that body is determined by one of
     1735               the following (in order of precedence):
     1736            </p>
     1737            <p id="rfc.section.4.4.p.2"></p>
     1738            <ol>
     1739               <li>
     1740                  <p>Any response message which "<em class="bcp14">MUST NOT</em>" include a message-body (such as the 1xx, 204, and 304 responses and any response to a HEAD request) is always terminated
     1741                     by the first empty line after the header fields, regardless of the entity-header fields present in the message.
     1742                  </p>
     1743               </li>
     1744               <li>
     1745                  <p>If a Transfer-Encoding header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section&nbsp;14.41</a>) is present and has any value other than "identity", then the transfer-length is defined by use of the "chunked" transfer-coding
     1746                     (<a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.6</a>), unless the message is terminated by closing the connection.
     1747                  </p>
     1748               </li>
     1749               <li>
     1750                  <p>If a Content-Length header field (<a href="#header.content-length" id="rfc.xref.header.content-length.1" title="Content-Length">Section&nbsp;14.13</a>) is present, its decimal value in OCTETs represents both the entity-length and the transfer-length. The Content-Length header
     1751                     field <em class="bcp14">MUST NOT</em> be sent if these two lengths are different (i.e., if a Transfer-Encoding header field is present). If a message is received
     1752                     with both a Transfer-Encoding header field and a Content-Length header field, the latter <em class="bcp14">MUST</em> be ignored.
     1753                  </p>
     1754               </li>
     1755               <li>
     1756                  <p>If the message uses the media type "multipart/byteranges", and the ransfer-length is not otherwise specified, then this self-elimiting
     1757                     media type defines the transfer-length. This media type UST NOT be used unless the sender knows that the recipient can arse
     1758                     it; the presence in a request of a Range header with ultiple byte-range specifiers from a 1.1 client implies that the lient
     1759                     can parse multipart/byteranges responses.
     1760                  </p>
     1761                  <ul class="empty">
     1762                     <li>A range header might be forwarded by a 1.0 proxy that does not understand multipart/byteranges; in this case the server <em class="bcp14">MUST</em> delimit the message using methods defined in items 1, 3 or 5 of this section.
     1763                     </li>
     1764                  </ul>
     1765               </li>
     1766               <li>
     1767                  <p>By the server closing the connection. (Closing the connection cannot be used to indicate the end of a request body, since
     1768                     that would leave no possibility for the server to send back a response.)
     1769                  </p>
     1770               </li>
     1771            </ol>
     1772            <p id="rfc.section.4.4.p.3">For compatibility with HTTP/1.0 applications, HTTP/1.1 requests containing a message-body <em class="bcp14">MUST</em> include a valid Content-Length header field unless the server is known to be HTTP/1.1 compliant. If a request contains a message-body
     1773               and a Content-Length is not given, the server <em class="bcp14">SHOULD</em> respond with 400 (bad request) if it cannot determine the length of the message, or with 411 (length required) if it wishes
     1774               to insist on receiving a valid Content-Length.
     1775            </p>
     1776            <p id="rfc.section.4.4.p.4">All HTTP/1.1 applications that receive entities <em class="bcp14">MUST</em> accept the "chunked" transfer-coding (<a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.6</a>), thus allowing this mechanism to be used for messages when the message length cannot be determined in advance.
     1777            </p>
     1778            <p id="rfc.section.4.4.p.5">Messages <em class="bcp14">MUST NOT</em> include both a Content-Length header field and a non-identity transfer-coding. If the message does include a non-identity
     1779               transfer-coding, the Content-Length <em class="bcp14">MUST</em> be ignored.
     1780            </p>
     1781            <p id="rfc.section.4.4.p.6">When a Content-Length is given in a message where a message-body is allowed, its field value <em class="bcp14">MUST</em> exactly match the number of OCTETs in the message-body. HTTP/1.1 user agents <em class="bcp14">MUST</em> notify the user when an invalid length is received and detected.
     1782            </p>
     1783         </div>
     1784         <div id="general.header.fields">
     1785            <h2 id="rfc.section.4.5"><a href="#rfc.section.4.5">4.5</a>&nbsp;<a href="#general.header.fields">General Header Fields</a></h2>
     1786            <p id="rfc.section.4.5.p.1">There are a few header fields which have general applicability for both request and response messages, but which do not apply
     1787               to the entity being transferred. These header fields apply only to the message being transmitted.
     1788            </p>
     1789            <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.78"></span>    general-header = Cache-Control            ; <a href="#header.cache-control" id="rfc.xref.header.cache-control.1" title="Cache-Control">Section&nbsp;14.9</a>
    17281790                   | Connection               ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section&nbsp;14.10</a>
    17291791                   | Date                     ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;14.18</a>
     
    17351797                   | Warning                  ; <a href="#header.warning" id="rfc.xref.header.warning.1" title="Warning">Section&nbsp;14.46</a>
    17361798</pre><p id="rfc.section.4.5.p.3">General-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    1737          or experimental header fields may be given the semantics of general header fields if all parties in the communication recognize
    1738          them to be general-header fields. Unrecognized header fields are treated as entity-header fields.
    1739       </p>
    1740       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="request" href="#request">Request</a></h1>
    1741       <p id="rfc.section.5.p.1">A request message from a client to a server includes, within the first line of that message, the method to be applied to the
    1742          resource, the identifier of the resource, and the protocol version in use.
    1743       </p>
    1744       <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.79"></span>     Request       = Request-Line              ; <a href="#request-line" title="Request-Line">Section&nbsp;5.1</a>
     1799               or experimental header fields may be given the semantics of general header fields if all parties in the communication recognize
     1800               them to be general-header fields. Unrecognized header fields are treated as entity-header fields.
     1801            </p>
     1802         </div>
     1803      </div>
     1804      <div id="request">
     1805         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#request">Request</a></h1>
     1806         <p id="rfc.section.5.p.1">A request message from a client to a server includes, within the first line of that message, the method to be applied to the
     1807            resource, the identifier of the resource, and the protocol version in use.
     1808         </p>
     1809         <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.79"></span>     Request       = Request-Line              ; <a href="#request-line" title="Request-Line">Section&nbsp;5.1</a>
    17451810                     *(( general-header        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    17461811                      | request-header         ; <a href="#request.header.fields" title="Request Header Fields">Section&nbsp;5.3</a>
     
    17481813                     CRLF
    17491814                     [ message-body ]          ; <a href="#message.body" title="Message Body">Section&nbsp;4.3</a>
    1750 </pre><h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="request-line" href="#request-line">Request-Line</a></h2>
    1751       <p id="rfc.section.5.1.p.1">The Request-Line begins with a method token, followed by the Request-URI and the protocol version, and ending with CRLF. The
    1752          elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence.
    1753       </p>
    1754       <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.80"></span>     Request-Line   = Method SP Request-URI SP HTTP-Version CRLF
    1755 </pre><h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a id="method" href="#method">Method</a></h3>
    1756       <p id="rfc.section.5.1.1.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p>
    1757       <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span>    Method         = "OPTIONS"                ; <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;9.2</a>
     1815</pre><div id="request-line">
     1816            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#request-line">Request-Line</a></h2>
     1817            <p id="rfc.section.5.1.p.1">The Request-Line begins with a method token, followed by the Request-URI and the protocol version, and ending with CRLF. The
     1818               elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence.
     1819            </p>
     1820            <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.80"></span>     Request-Line   = Method SP Request-URI SP HTTP-Version CRLF
     1821</pre><div id="method">
     1822               <h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a href="#method">Method</a></h3>
     1823               <p id="rfc.section.5.1.1.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p>
     1824               <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span>    Method         = "OPTIONS"                ; <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;9.2</a>
    17581825                   | "GET"                    ; <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;9.3</a>
    17591826                   | "HEAD"                   ; <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;9.4</a>
     
    17661833    extension-method = token
    17671834</pre><p id="rfc.section.5.1.1.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;14.7</a>). The return code of the response always notifies the client whether a method is currently allowed on a resource, since the
    1768          set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> return the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the requested
    1769          resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
    1770          and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>; however, if the above methods are implemented, they <em class="bcp14">MUST</em> be implemented with the same semantics as those specified in <a href="#method.definitions" title="Method Definitions">Section&nbsp;9</a>.
    1771       </p>
    1772       <h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a id="request-uri" href="#request-uri">Request-URI</a></h3>
    1773       <p id="rfc.section.5.1.2.p.1">The Request-URI is a Uniform Resource Identifier (<a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;3.2</a>) and identifies the resource upon which to apply the request.
    1774       </p>
    1775       <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.83"></span>    Request-URI    = "*" | absoluteURI | abs_path | authority
     1835                  set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> return the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the requested
     1836                  resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
     1837                  and HEAD <em class="bcp14">MUST</em> be supported by all general-purpose servers. All other methods are <em class="bcp14">OPTIONAL</em>; however, if the above methods are implemented, they <em class="bcp14">MUST</em> be implemented with the same semantics as those specified in <a href="#method.definitions" title="Method Definitions">Section&nbsp;9</a>.
     1838               </p>
     1839            </div>
     1840            <div id="request-uri">
     1841               <h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a href="#request-uri">Request-URI</a></h3>
     1842               <p id="rfc.section.5.1.2.p.1">The Request-URI is a Uniform Resource Identifier (<a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;3.2</a>) and identifies the resource upon which to apply the request.
     1843               </p>
     1844               <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.83"></span>    Request-URI    = "*" | absoluteURI | abs_path | authority
    17761845</pre><p id="rfc.section.5.1.2.p.3">The four options for Request-URI are dependent on the nature of the request. The asterisk "*" means that the request does
    1777          not apply to a particular resource, but to the server itself, and is only allowed when the method used does not necessarily
    1778          apply to a resource. One example would be
    1779       </p>
    1780       <div id="rfc.figure.u.41"></div><pre class="text">    OPTIONS * HTTP/1.1
     1846                  not apply to a particular resource, but to the server itself, and is only allowed when the method used does not necessarily
     1847                  apply to a resource. One example would be
     1848               </p>
     1849               <div id="rfc.figure.u.41"></div><pre class="text">    OPTIONS * HTTP/1.1
    17811850</pre><p id="rfc.section.5.1.2.p.5">The absoluteURI form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache,
    1782          and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absoluteURI. In order to avoid request
    1783          loops, a proxy <em class="bcp14">MUST</em> be able to recognize all of its server names, including any aliases, local variations, and the numeric IP address. An example
    1784          Request-Line would be:
    1785       </p>
    1786       <div id="rfc.figure.u.42"></div><pre class="text">    GET http://www.w3.org/pub/WWW/TheProject.html HTTP/1.1
     1851                  and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absoluteURI. In order to avoid request
     1852                  loops, a proxy <em class="bcp14">MUST</em> be able to recognize all of its server names, including any aliases, local variations, and the numeric IP address. An example
     1853                  Request-Line would be:
     1854               </p>
     1855               <div id="rfc.figure.u.42"></div><pre class="text">    GET http://www.w3.org/pub/WWW/TheProject.html HTTP/1.1
    17871856</pre><p id="rfc.section.5.1.2.p.7">To allow for transition to absoluteURIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absoluteURI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies.
    1788       </p>
    1789       <p id="rfc.section.5.1.2.p.8">The authority form is only used by the CONNECT method (<a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;9.9</a>).
    1790       </p>
    1791       <p id="rfc.section.5.1.2.p.9">The most common form of Request-URI is that used to identify a resource on an origin server or gateway. In this case the absolute
    1792          path of the URI <em class="bcp14">MUST</em> be transmitted (see <a href="#general.syntax" title="General Syntax">Section&nbsp;3.2.1</a>, abs_path) as the Request-URI, and the network location of the URI (authority) <em class="bcp14">MUST</em> be transmitted in a Host header field. For example, a client wishing to retrieve the resource above directly from the origin
    1793          server would create a TCP connection to port 80 of the host "www.w3.org" and send the lines:
    1794       </p>
    1795       <div id="rfc.figure.u.43"></div><pre class="text">    GET /pub/WWW/TheProject.html HTTP/1.1
     1857               </p>
     1858               <p id="rfc.section.5.1.2.p.8">The authority form is only used by the CONNECT method (<a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;9.9</a>).
     1859               </p>
     1860               <p id="rfc.section.5.1.2.p.9">The most common form of Request-URI is that used to identify a resource on an origin server or gateway. In this case the absolute
     1861                  path of the URI <em class="bcp14">MUST</em> be transmitted (see <a href="#general.syntax" title="General Syntax">Section&nbsp;3.2.1</a>, abs_path) as the Request-URI, and the network location of the URI (authority) <em class="bcp14">MUST</em> be transmitted in a Host header field. For example, a client wishing to retrieve the resource above directly from the origin
     1862                  server would create a TCP connection to port 80 of the host "www.w3.org" and send the lines:
     1863               </p>
     1864               <div id="rfc.figure.u.43"></div><pre class="text">    GET /pub/WWW/TheProject.html HTTP/1.1
    17961865    Host: www.w3.org
    17971866</pre><p id="rfc.section.5.1.2.p.11">followed by the remainder of the Request. Note that the absolute path cannot be empty; if none is present in the original
    1798          URI, it <em class="bcp14">MUST</em> be given as "/" (the server root).
    1799       </p>
    1800       <p id="rfc.section.5.1.2.p.12">The Request-URI is transmitted in the format specified in <a href="#general.syntax" title="General Syntax">Section&nbsp;3.2.1</a>. If the Request-URI is encoded using the "% HEX HEX" encoding <a href="#RFC2396" id="rfc.xref.RFC2396.3"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, the origin server <em class="bcp14">MUST</em> decode the Request-URI in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid Request-URIs with an appropriate status code.
    1801       </p>
    1802       <p id="rfc.section.5.1.2.p.13">A transparent proxy <em class="bcp14">MUST NOT</em> rewrite the "abs_path" part of the received Request-URI when forwarding it to the next inbound server, except as noted above
    1803          to replace a null abs_path with "/".
    1804       </p>
    1805       <p id="rfc.section.5.1.2.p.14"> </p>
    1806       <ul class="empty">
    1807          <li> <b>Note:</b> The "no rewrite" rule prevents the proxy from changing the meaning of the request when the origin server is improperly using
    1808             a non-reserved URI character for a reserved purpose. Implementors should be aware that some pre-HTTP/1.1 proxies have been
    1809             known to rewrite the Request-URI.
    1810          </li>
    1811       </ul>
    1812       <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="the.resource.identified.by.a.request" href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></h2>
    1813       <p id="rfc.section.5.2.p.1">The exact resource identified by an Internet request is determined by examining both the Request-URI and the Host header field.</p>
    1814       <p id="rfc.section.5.2.p.2">An origin server that does not allow resources to differ by the requested host <em class="bcp14">MAY</em> ignore the Host header field value when determining the resource identified by an HTTP/1.1 request. (But see <a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" title="Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses">Appendix&nbsp;19.6.1.1</a> for other requirements on Host support in HTTP/1.1.)
    1815       </p>
    1816       <p id="rfc.section.5.2.p.3">An origin server that does differentiate resources based on the host requested (sometimes referred to as virtual hosts or
    1817          vanity host names) <em class="bcp14">MUST</em> use the following rules for determining the requested resource on an HTTP/1.1 request:
    1818       </p>
    1819       <ol>
    1820          <li>If Request-URI is an absoluteURI, the host is part of the Request-URI. Any Host header field value in the request <em class="bcp14">MUST</em> be ignored.
    1821          </li>
    1822          <li>If the Request-URI is not an absoluteURI, and the request includes a Host header field, the host is determined by the Host
    1823             header field value.
    1824          </li>
    1825          <li>If the host as determined by rule 1 or 2 is not a valid host on the server, the response <em class="bcp14">MUST</em> be a 400 (Bad Request) error message.
    1826          </li>
    1827       </ol>
    1828       <p id="rfc.section.5.2.p.4">Recipients of an HTTP/1.0 request that lacks a Host header field <em class="bcp14">MAY</em> attempt to use heuristics (e.g., examination of the URI path for something unique to a particular host) in order to determine
    1829          what exact resource is being requested.
    1830       </p>
    1831       <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h2>
    1832       <p id="rfc.section.5.3.p.1">The request-header fields allow the client to pass additional information about the request, and about the client itself,
    1833          to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language
    1834          method invocation.
    1835       </p>
    1836       <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.84"></span>    request-header = Accept                   ; <a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;14.1</a>
     1867                  URI, it <em class="bcp14">MUST</em> be given as "/" (the server root).
     1868               </p>
     1869               <p id="rfc.section.5.1.2.p.12">The Request-URI is transmitted in the format specified in <a href="#general.syntax" title="General Syntax">Section&nbsp;3.2.1</a>. If the Request-URI is encoded using the "% HEX HEX" encoding <a href="#RFC2396" id="rfc.xref.RFC2396.3"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, the origin server <em class="bcp14">MUST</em> decode the Request-URI in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid Request-URIs with an appropriate status code.
     1870               </p>
     1871               <p id="rfc.section.5.1.2.p.13">A transparent proxy <em class="bcp14">MUST NOT</em> rewrite the "abs_path" part of the received Request-URI when forwarding it to the next inbound server, except as noted above
     1872                  to replace a null abs_path with "/".
     1873               </p>
     1874               <p id="rfc.section.5.1.2.p.14"></p>
     1875               <ul class="empty">
     1876                  <li><b>Note:</b> The "no rewrite" rule prevents the proxy from changing the meaning of the request when the origin server is improperly using
     1877                     a non-reserved URI character for a reserved purpose. Implementors should be aware that some pre-HTTP/1.1 proxies have been
     1878                     known to rewrite the Request-URI.
     1879                  </li>
     1880               </ul>
     1881            </div>
     1882         </div>
     1883         <div id="the.resource.identified.by.a.request">
     1884            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></h2>
     1885            <p id="rfc.section.5.2.p.1">The exact resource identified by an Internet request is determined by examining both the Request-URI and the Host header field.</p>
     1886            <p id="rfc.section.5.2.p.2">An origin server that does not allow resources to differ by the requested host <em class="bcp14">MAY</em> ignore the Host header field value when determining the resource identified by an HTTP/1.1 request. (But see <a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" title="Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses">Appendix&nbsp;19.6.1.1</a> for other requirements on Host support in HTTP/1.1.)
     1887            </p>
     1888            <p id="rfc.section.5.2.p.3">An origin server that does differentiate resources based on the host requested (sometimes referred to as virtual hosts or
     1889               vanity host names) <em class="bcp14">MUST</em> use the following rules for determining the requested resource on an HTTP/1.1 request:
     1890            </p>
     1891            <ol>
     1892               <li>If Request-URI is an absoluteURI, the host is part of the Request-URI. Any Host header field value in the request <em class="bcp14">MUST</em> be ignored.
     1893               </li>
     1894               <li>If the Request-URI is not an absoluteURI, and the request includes a Host header field, the host is determined by the Host
     1895                  header field value.
     1896               </li>
     1897               <li>If the host as determined by rule 1 or 2 is not a valid host on the server, the response <em class="bcp14">MUST</em> be a 400 (Bad Request) error message.
     1898               </li>
     1899            </ol>
     1900            <p id="rfc.section.5.2.p.4">Recipients of an HTTP/1.0 request that lacks a Host header field <em class="bcp14">MAY</em> attempt to use heuristics (e.g., examination of the URI path for something unique to a particular host) in order to determine
     1901               what exact resource is being requested.
     1902            </p>
     1903         </div>
     1904         <div id="request.header.fields">
     1905            <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#request.header.fields">Request Header Fields</a></h2>
     1906            <p id="rfc.section.5.3.p.1">The request-header fields allow the client to pass additional information about the request, and about the client itself,
     1907               to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language
     1908               method invocation.
     1909            </p>
     1910            <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.84"></span>    request-header = Accept                   ; <a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;14.1</a>
    18371911                   | Accept-Charset           ; <a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;14.2</a>
    18381912                   | Accept-Encoding          ; <a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;14.3</a>
     
    18541928                   | User-Agent               ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;14.43</a>
    18551929</pre><p id="rfc.section.5.3.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    1856          or experimental header fields <em class="bcp14">MAY</em> be given the semantics of request-header fields if all parties in the communication recognize them to be request-header fields.
    1857          Unrecognized header fields are treated as entity-header fields.
    1858       </p>
    1859       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="response" href="#response">Response</a></h1>
    1860       <p id="rfc.section.6.p.1">After receiving and interpreting a request message, a server responds with an HTTP response message.</p>
    1861       <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.85"></span>    Response      = Status-Line               ; <a href="#status-line" title="Status-Line">Section&nbsp;6.1</a>
     1930               or experimental header fields <em class="bcp14">MAY</em> be given the semantics of request-header fields if all parties in the communication recognize them to be request-header fields.
     1931               Unrecognized header fields are treated as entity-header fields.
     1932            </p>
     1933         </div>
     1934      </div>
     1935      <div id="response">
     1936         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#response">Response</a></h1>
     1937         <p id="rfc.section.6.p.1">After receiving and interpreting a request message, a server responds with an HTTP response message.</p>
     1938         <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.85"></span>    Response      = Status-Line               ; <a href="#status-line" title="Status-Line">Section&nbsp;6.1</a>
    18621939                    *(( general-header        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    18631940                     | response-header        ; <a href="#response.header.fields" title="Response Header Fields">Section&nbsp;6.2</a>
     
    18651942                    CRLF
    18661943                    [ message-body ]          ; <a href="#entity.body" title="Entity Body">Section&nbsp;7.2</a>
    1867 </pre><h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="status-line" href="#status-line">Status-Line</a></h2>
    1868       <p id="rfc.section.6.1.p.1">The first line of a Response message is the Status-Line, consisting of the protocol version followed by a numeric status code
    1869          and its associated textual phrase, with each element separated by SP characters. No CR or LF is allowed except in the final
    1870          CRLF sequence.
    1871       </p>
    1872       <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.86"></span>    Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
    1873 </pre><h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3>
    1874       <p id="rfc.section.6.1.1.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes
    1875          are fully defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;10</a>. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use
    1876          by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.
    1877       </p>
    1878       <p id="rfc.section.6.1.1.p.2">The first digit of the Status-Code defines the class of response. The last two digits do not have any categorization role.
    1879          There are 5 values for the first digit:
    1880       </p>
    1881       <ul>
    1882          <li>1xx: Informational - Request received, continuing process</li>
    1883          <li>2xx: Success - The action was successfully received, understood, and accepted</li>
    1884          <li>3xx: Redirection - Further action must be taken in order to complete the request</li>
    1885          <li>4xx: Client Error - The request contains bad syntax or cannot be fulfilled</li>
    1886          <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li>
    1887       </ul>
    1888       <p id="rfc.section.6.1.1.p.3">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's,
    1889          are presented below. The reason phrases listed here are only recommendations -- they <em class="bcp14">MAY</em> be replaced by local equivalents without affecting the protocol.
    1890       </p>
    1891       <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.87"></span><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span>   Status-Code    =
     1944</pre><div id="status-line">
     1945            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#status-line">Status-Line</a></h2>
     1946            <p id="rfc.section.6.1.p.1">The first line of a Response message is the Status-Line, consisting of the protocol version followed by a numeric status code
     1947               and its associated textual phrase, with each element separated by SP characters. No CR or LF is allowed except in the final
     1948               CRLF sequence.
     1949            </p>
     1950            <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.86"></span>    Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
     1951</pre><div id="status.code.and.reason.phrase">
     1952               <h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3>
     1953               <p id="rfc.section.6.1.1.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes
     1954                  are fully defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;10</a>. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use
     1955                  by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.
     1956               </p>
     1957               <p id="rfc.section.6.1.1.p.2">The first digit of the Status-Code defines the class of response. The last two digits do not have any categorization role.
     1958                  There are 5 values for the first digit:
     1959               </p>
     1960               <ul>
     1961                  <li>1xx: Informational - Request received, continuing process</li>
     1962                  <li>2xx: Success - The action was successfully received, understood, and accepted</li>
     1963                  <li>3xx: Redirection - Further action must be taken in order to complete the request</li>
     1964                  <li>4xx: Client Error - The request contains bad syntax or cannot be fulfilled</li>
     1965                  <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li>
     1966               </ul>
     1967               <p id="rfc.section.6.1.1.p.3">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's,
     1968                  are presented below. The reason phrases listed here are only recommendations -- they <em class="bcp14">MAY</em> be replaced by local equivalents without affecting the protocol.
     1969               </p>
     1970               <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.87"></span><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span>   Status-Code    =
    18921971         "100"  ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;10.1.1</a>: Continue
    18931972       | "101"  ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;10.1.2</a>: Switching Protocols
     
    19352014   Reason-Phrase  = *&lt;TEXT, excluding CR, LF&gt;
    19362015</pre><p id="rfc.section.6.1.1.p.5">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
    1937          though such understanding is obviously desirable. However, applications <em class="bcp14">MUST</em> understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent
    1938          to the x00 status code of that class, with the exception that an unrecognized response <em class="bcp14">MUST NOT</em> be cached. For example, if an unrecognized status code of 431 is received by the client, it can safely assume that there was
    1939          something wrong with its request and treat the response as if it had received a 400 status code. In such cases, user agents <em class="bcp14">SHOULD</em> present to the user the entity returned with the response, since that entity is likely to include human-readable information
    1940          which will explain the unusual status.
    1941       </p>
    1942       <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h2>
    1943       <p id="rfc.section.6.2.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the
    1944          Status-Line. These header fields give information about the server and about further access to the resource identified by
    1945          the Request-URI.
    1946       </p>
    1947       <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.90"></span>    response-header = Accept-Ranges           ; <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;14.5</a>
     2016                  though such understanding is obviously desirable. However, applications <em class="bcp14">MUST</em> understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent
     2017                  to the x00 status code of that class, with the exception that an unrecognized response <em class="bcp14">MUST NOT</em> be cached. For example, if an unrecognized status code of 431 is received by the client, it can safely assume that there was
     2018                  something wrong with its request and treat the response as if it had received a 400 status code. In such cases, user agents <em class="bcp14">SHOULD</em> present to the user the entity returned with the response, since that entity is likely to include human-readable information
     2019                  which will explain the unusual status.
     2020               </p>
     2021            </div>
     2022         </div>
     2023         <div id="response.header.fields">
     2024            <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#response.header.fields">Response Header Fields</a></h2>
     2025            <p id="rfc.section.6.2.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the
     2026               Status-Line. These header fields give information about the server and about further access to the resource identified by
     2027               the Request-URI.
     2028            </p>
     2029            <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.90"></span>    response-header = Accept-Ranges           ; <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;14.5</a>
    19482030                    | Age                     ; <a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section&nbsp;14.6</a>
    19492031                    | ETag                    ; <a href="#header.etag" id="rfc.xref.header.etag.2" title="ETag">Section&nbsp;14.19</a>
     
    19552037                    | WWW-Authenticate        ; <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.1" title="WWW-Authenticate">Section&nbsp;14.47</a>
    19562038</pre><p id="rfc.section.6.2.p.3">Response-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    1957          or experimental header fields <em class="bcp14">MAY</em> be given the semantics of response-header fields if all parties in the communication recognize them to be response-header
    1958          fields. Unrecognized header fields are treated as entity-header fields.
    1959       </p>
    1960       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="entity" href="#entity">Entity</a></h1>
    1961       <p id="rfc.section.7.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer an entity if not otherwise restricted by the request method or response status code. An entity consists of entity-header
    1962          fields and an entity-body, although some responses will only include the entity-headers.
    1963       </p>
    1964       <p id="rfc.section.7.p.2">In this section, both sender and recipient refer to either the client or the server, depending on who sends and who receives
    1965          the entity.
    1966       </p>
    1967       <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="entity.header.fields" href="#entity.header.fields">Entity Header Fields</a></h2>
    1968       <p id="rfc.section.7.1.p.1">Entity-header fields define metainformation about the entity-body or, if no body is present, about the resource identified
    1969          by the request. Some of this metainformation is <em class="bcp14">OPTIONAL</em>; some might be <em class="bcp14">REQUIRED</em> by portions of this specification.
    1970       </p>
    1971       <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span>    entity-header  = Allow                    ; <a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;14.7</a>
     2039               or experimental header fields <em class="bcp14">MAY</em> be given the semantics of response-header fields if all parties in the communication recognize them to be response-header
     2040               fields. Unrecognized header fields are treated as entity-header fields.
     2041            </p>
     2042         </div>
     2043      </div>
     2044      <div id="entity">
     2045         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#entity">Entity</a></h1>
     2046         <p id="rfc.section.7.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer an entity if not otherwise restricted by the request method or response status code. An entity consists of entity-header
     2047            fields and an entity-body, although some responses will only include the entity-headers.
     2048         </p>
     2049         <p id="rfc.section.7.p.2">In this section, both sender and recipient refer to either the client or the server, depending on who sends and who receives
     2050            the entity.
     2051         </p>
     2052         <div id="entity.header.fields">
     2053            <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#entity.header.fields">Entity Header Fields</a></h2>
     2054            <p id="rfc.section.7.1.p.1">Entity-header fields define metainformation about the entity-body or, if no body is present, about the resource identified
     2055               by the request. Some of this metainformation is <em class="bcp14">OPTIONAL</em>; some might be <em class="bcp14">REQUIRED</em> by portions of this specification.
     2056            </p>
     2057            <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span>    entity-header  = Allow                    ; <a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;14.7</a>
    19722058                   | Content-Encoding         ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;14.11</a>
    19732059                   | Content-Language         ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;14.12</a>
     
    19832069    extension-header = message-header
    19842070</pre><p id="rfc.section.7.1.p.3">The extension-header mechanism allows additional entity-header fields to be defined without changing the protocol, but these
    1985          fields cannot be assumed to be recognizable by the recipient. Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored by the recipient and <em class="bcp14">MUST</em> be forwarded by transparent proxies.
    1986       </p>
    1987       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="entity.body" href="#entity.body">Entity Body</a></h2>
    1988       <p id="rfc.section.7.2.p.1">The entity-body (if any) sent with an HTTP request or response is in a format and encoding defined by the entity-header fields.</p>
    1989       <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.93"></span>    entity-body    = *OCTET
     2071               fields cannot be assumed to be recognizable by the recipient. Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored by the recipient and <em class="bcp14">MUST</em> be forwarded by transparent proxies.
     2072            </p>
     2073         </div>
     2074         <div id="entity.body">
     2075            <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#entity.body">Entity Body</a></h2>
     2076            <p id="rfc.section.7.2.p.1">The entity-body (if any) sent with an HTTP request or response is in a format and encoding defined by the entity-header fields.</p>
     2077            <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.93"></span>    entity-body    = *OCTET
    19902078</pre><p id="rfc.section.7.2.p.3">An entity-body is only present in a message when a message-body is present, as described in <a href="#message.body" title="Message Body">Section&nbsp;4.3</a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
    1991          safe and proper transfer of the message.
    1992       </p>
    1993       <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="type" href="#type">Type</a></h3>
    1994       <p id="rfc.section.7.2.1.p.1">When an entity-body is included with a message, the data type of that body is determined via the header fields Content-Type
    1995          and Content-Encoding. These define a two-layer, ordered encoding model:
    1996       </p>
    1997       <div id="rfc.figure.u.51"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) )
     2079               safe and proper transfer of the message.
     2080            </p>
     2081            <div id="type">
     2082               <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a href="#type">Type</a></h3>
     2083               <p id="rfc.section.7.2.1.p.1">When an entity-body is included with a message, the data type of that body is determined via the header fields Content-Type
     2084                  and Content-Encoding. These define a two-layer, ordered encoding model:
     2085               </p>
     2086               <div id="rfc.figure.u.51"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) )
    19982087</pre><p id="rfc.section.7.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content
    1999          codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There
    2000          is no default encoding.
    2001       </p>
    2002       <p id="rfc.section.7.2.1.p.4">Any HTTP/1.1 message containing an entity-body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of that body. If and only if the media type is not given by a
    2003          Content-Type field, the recipient <em class="bcp14">MAY</em> attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the
    2004          resource. If the media type remains unknown, the recipient <em class="bcp14">SHOULD</em> treat it as type "application/octet-stream".
    2005       </p>
    2006       <h3 id="rfc.section.7.2.2"><a href="#rfc.section.7.2.2">7.2.2</a>&nbsp;<a id="entity.length" href="#entity.length">Entity Length</a></h3>
    2007       <p id="rfc.section.7.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="#message.length" title="Message Length">Section&nbsp;4.4</a> defines how the transfer-length of a message-body is determined.
    2008       </p>
    2009       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="connections" href="#connections">Connections</a></h1>
    2010       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="persistent.connections" href="#persistent.connections">Persistent Connections</a></h2>
    2011       <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="persistent.purpose" href="#persistent.purpose">Purpose</a></h3>
    2012       <p id="rfc.section.8.1.1.p.1">Prior to persistent connections, a separate TCP connection was established to fetch each URL, increasing the load on HTTP
    2013          servers and causing congestion on the Internet. The use of inline images and other associated data often require a client
    2014          to make multiple requests of the same server in a short amount of time. Analysis of these performance problems and results
    2015          from a prototype implementation are available <a href="#Pad1995" id="rfc.xref.Pad1995.1"><cite title="Improving HTTP Latency">[Pad1995]</cite></a>  <a href="#Spe" id="rfc.xref.Spe.1"><cite title="Analysis of HTTP Performance Problems">[Spe]</cite></a>. Implementation experience and measurements of actual HTTP/1.1 (RFC 2068) implementations show good results <a href="#Nie1997" id="rfc.xref.Nie1997.1"><cite title="Network Performance Effects of HTTP/1.1, CSS1, and PNG">[Nie1997]</cite></a>. Alternatives have also been explored, for example, T/TCP <a href="#Tou1998" id="rfc.xref.Tou1998.1"><cite title="Analysis of HTTP Performance">[Tou1998]</cite></a>.
    2016       </p>
    2017       <p id="rfc.section.8.1.1.p.2">Persistent HTTP connections have a number of advantages: </p>
    2018       <ul>
    2019          <li>By opening and closing fewer TCP connections, CPU time is saved in routers and hosts (clients, servers, proxies, gateways,
    2020             tunnels, or caches), and memory used for TCP protocol control blocks can be saved in hosts.
    2021          </li>
    2022          <li>HTTP requests and responses can be pipelined on a connection. Pipelining allows a client to make multiple requests without
    2023             waiting for each response, allowing a single TCP connection to be used much more efficiently, with much lower elapsed time.
    2024          </li>
    2025          <li>Network congestion is reduced by reducing the number of packets caused by TCP opens, and by allowing TCP sufficient time to
    2026             determine the congestion state of the network.
    2027          </li>
    2028          <li>Latency on subsequent requests is reduced since there is no time spent in TCP's connection opening handshake.</li>
    2029          <li>HTTP can evolve more gracefully, since errors can be reported without the penalty of closing the TCP connection. Clients using
    2030             future versions of HTTP might optimistically try a new feature, but if communicating with an older server, retry with old
    2031             semantics after an error is reported.
    2032          </li>
    2033       </ul>
    2034       <p id="rfc.section.8.1.1.p.3">HTTP implementations <em class="bcp14">SHOULD</em> implement persistent connections.
    2035       </p>
    2036       <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a id="persistent.overall" href="#persistent.overall">Overall Operation</a></h3>
    2037       <p id="rfc.section.8.1.2.p.1">A significant difference between HTTP/1.1 and earlier versions of HTTP is that persistent connections are the default behavior
    2038          of any HTTP connection. That is, unless otherwise indicated, the client <em class="bcp14">SHOULD</em> assume that the server will maintain a persistent connection, even after error responses from the server.
    2039       </p>
    2040       <p id="rfc.section.8.1.2.p.2">Persistent connections provide a mechanism by which a client and a server can signal the close of a TCP connection. This signaling
    2041          takes place using the Connection header field (<a href="#header.connection" id="rfc.xref.header.connection.2" title="Connection">Section&nbsp;14.10</a>). Once a close has been signaled, the client <em class="bcp14">MUST NOT</em> send any more requests on that connection.
    2042       </p>
    2043       <h4 id="rfc.section.8.1.2.1"><a href="#rfc.section.8.1.2.1">8.1.2.1</a>&nbsp;<a id="persistent.negotiation" href="#persistent.negotiation">Negotiation</a></h4>
    2044       <p id="rfc.section.8.1.2.1.p.1">An HTTP/1.1 server <em class="bcp14">MAY</em> assume that a HTTP/1.1 client intends to maintain a persistent connection unless a Connection header including the connection-token
    2045          "close" was sent in the request. If the server chooses to close the connection immediately after sending the response, it <em class="bcp14">SHOULD</em> send a Connection header including the connection-token close.
    2046       </p>
    2047       <p id="rfc.section.8.1.2.1.p.2">An HTTP/1.1 client <em class="bcp14">MAY</em> expect a connection to remain open, but would decide to keep it open based on whether the response from a server contains
    2048          a Connection header with the connection-token close. In case the client does not want to maintain a connection for more than
    2049          that request, it <em class="bcp14">SHOULD</em> send a Connection header including the connection-token close.
    2050       </p>
    2051       <p id="rfc.section.8.1.2.1.p.3">If either the client or the server sends the close token in the Connection header, that request becomes the last one for the
    2052          connection.
    2053       </p>
    2054       <p id="rfc.section.8.1.2.1.p.4">Clients and servers <em class="bcp14">SHOULD NOT</em> assume that a persistent connection is maintained for HTTP versions less than 1.1 unless it is explicitly signaled. See <a href="#compatibility.with.http.1.0.persistent.connections" title="Compatibility with HTTP/1.0 Persistent Connections">Appendix&nbsp;19.6.2</a> for more information on backward compatibility with HTTP/1.0 clients.
    2055       </p>
    2056       <p id="rfc.section.8.1.2.1.p.5">In order to remain persistent, all messages on the connection <em class="bcp14">MUST</em> have a self-defined message length (i.e., one not defined by closure of the connection), as described in <a href="#message.length" title="Message Length">Section&nbsp;4.4</a>.
    2057       </p>
    2058       <h4 id="rfc.section.8.1.2.2"><a href="#rfc.section.8.1.2.2">8.1.2.2</a>&nbsp;<a id="pipelining" href="#pipelining">Pipelining</a></h4>
    2059       <p id="rfc.section.8.1.2.2.p.1">A client that supports persistent connections <em class="bcp14">MAY</em> "pipeline" its requests (i.e., send multiple requests without waiting for each response). A server <em class="bcp14">MUST</em> send its responses to those requests in the same order that the requests were received.
    2060       </p>
    2061       <p id="rfc.section.8.1.2.2.p.2">Clients which assume persistent connections and pipeline immediately after connection establishment <em class="bcp14">SHOULD</em> be prepared to retry their connection if the first pipelined attempt fails. If a client does such a retry, it <em class="bcp14">MUST NOT</em> pipeline before it knows the connection is persistent. Clients <em class="bcp14">MUST</em> also be prepared to resend their requests if the server closes the connection before sending all of the corresponding responses.
    2062       </p>
    2063       <p id="rfc.section.8.1.2.2.p.3">Clients <em class="bcp14">SHOULD NOT</em> pipeline requests using non-idempotent methods or non-idempotent sequences of methods (see <a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;9.1.2</a>). Otherwise, a premature termination of the transport connection could lead to indeterminate results. A client wishing to
    2064          send a non-idempotent request <em class="bcp14">SHOULD</em> wait to send that request until it has received the response status for the previous request.
    2065       </p>
    2066       <h3 id="rfc.section.8.1.3"><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;<a id="persistent.proxy" href="#persistent.proxy">Proxy Servers</a></h3>
    2067       <p id="rfc.section.8.1.3.p.1">It is especially important that proxies correctly implement the properties of the Connection header field as specified in <a href="#header.connection" id="rfc.xref.header.connection.3" title="Connection">Section&nbsp;14.10</a>.
    2068       </p>
    2069       <p id="rfc.section.8.1.3.p.2">The proxy server <em class="bcp14">MUST</em> signal persistent connections separately with its clients and the origin servers (or other proxy servers) that it connects
    2070          to. Each persistent connection applies to only one transport link.
    2071       </p>
    2072       <p id="rfc.section.8.1.3.p.3">A proxy server <em class="bcp14">MUST NOT</em> establish a HTTP/1.1 persistent connection with an HTTP/1.0 client (but see RFC 2068 <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> for information and discussion of the problems with the Keep-Alive header implemented by many HTTP/1.0 clients).
    2073       </p>
    2074       <h3 id="rfc.section.8.1.4"><a href="#rfc.section.8.1.4">8.1.4</a>&nbsp;<a id="persistent.practical" href="#persistent.practical">Practical Considerations</a></h3>
    2075       <p id="rfc.section.8.1.4.p.1">Servers will usually have some time-out value beyond which they will no longer maintain an inactive connection. Proxy servers
    2076          might make this a higher value since it is likely that the client will be making more connections through the same server.
    2077          The use of persistent connections places no requirements on the length (or existence) of this time-out for either the client
    2078          or the server.
    2079       </p>
    2080       <p id="rfc.section.8.1.4.p.2">When a client or server wishes to time-out it <em class="bcp14">SHOULD</em> issue a graceful close on the transport connection. Clients and servers <em class="bcp14">SHOULD</em> both constantly watch for the other side of the transport close, and respond to it as appropriate. If a client or server does
    2081          not detect the other side's close promptly it could cause unnecessary resource drain on the network.
    2082       </p>
    2083       <p id="rfc.section.8.1.4.p.3">A client, server, or proxy <em class="bcp14">MAY</em> close the transport connection at any time. For example, a client might have started to send a new request at the same time
    2084          that the server has decided to close the "idle" connection. From the server's point of view, the connection is being closed
    2085          while it was idle, but from the client's point of view, a request is in progress.
    2086       </p>
    2087       <p id="rfc.section.8.1.4.p.4">This means that clients, servers, and proxies <em class="bcp14">MUST</em> be able to recover from asynchronous close events. Client software <em class="bcp14">SHOULD</em> reopen the transport connection and retransmit the aborted sequence of requests without user interaction so long as the request
    2088          sequence is idempotent (see <a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;9.1.2</a>). Non-idempotent methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user-agent software with semantic understanding
    2089          of the application <em class="bcp14">MAY</em> substitute for user confirmation. The automatic retry <em class="bcp14">SHOULD NOT</em> be repeated if the second sequence of requests fails.
    2090       </p>
    2091       <p id="rfc.section.8.1.4.p.5">Servers <em class="bcp14">SHOULD</em> always respond to at least one request per connection, if at all possible. Servers <em class="bcp14">SHOULD NOT</em> close a connection in the middle of transmitting a response, unless a network or client failure is suspected.
    2092       </p>
    2093       <p id="rfc.section.8.1.4.p.6">Clients that use persistent connections <em class="bcp14">SHOULD</em> limit the number of simultaneous connections that they maintain to a given server. A single-user client <em class="bcp14">SHOULD NOT</em> maintain more than 2 connections with any server or proxy. A proxy <em class="bcp14">SHOULD</em> use up to 2*N connections to another server or proxy, where N is the number of simultaneously active users. These guidelines
    2094          are intended to improve HTTP response times and avoid congestion.
    2095       </p>
    2096       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="message.transmission.requirements" href="#message.transmission.requirements">Message Transmission Requirements</a></h2>
    2097       <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a id="persistent.flow" href="#persistent.flow">Persistent Connections and Flow Control</a></h3>
    2098       <p id="rfc.section.8.2.1.p.1">HTTP/1.1 servers <em class="bcp14">SHOULD</em> maintain persistent connections and use TCP's flow control mechanisms to resolve temporary overloads, rather than terminating
    2099          connections with the expectation that clients will retry. The latter technique can exacerbate network congestion.
    2100       </p>
    2101       <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a id="persistent.monitor" href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></h3>
    2102       <p id="rfc.section.8.2.2.p.1">An HTTP/1.1 (or later) client sending a message-body <em class="bcp14">SHOULD</em> monitor the network connection for an error status while it is transmitting the request. If the client sees an error status,
    2103          it <em class="bcp14">SHOULD</em> immediately cease transmitting the body. If the body is being sent using a "chunked" encoding (<a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.6</a>), a zero length chunk and empty trailer <em class="bcp14">MAY</em> be used to prematurely mark the end of the message. If the body was preceded by a Content-Length header, the client <em class="bcp14">MUST</em> close the connection.
    2104       </p>
    2105       <h3 id="rfc.section.8.2.3"><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;<a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h3>
    2106       <p id="rfc.section.8.2.3.p.1">The purpose of the 100 (Continue) status (see <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;10.1.1</a>) is to allow a client that is sending a request message with a request body to determine if the origin server is willing
    2107          to accept the request (based on the request headers) before the client sends the request body. In some cases, it might either
    2108          be inappropriate or highly inefficient for the client to send the body if the server will reject the message without looking
    2109          at the body.
    2110       </p>
    2111       <p id="rfc.section.8.2.3.p.2">Requirements for HTTP/1.1 clients: </p>
    2112       <ul>
    2113          <li>If a client will wait for a 100 (Continue) response before sending the request body, it <em class="bcp14">MUST</em> send an Expect request-header field (<a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;14.20</a>) with the "100-continue" expectation.
    2114          </li>
    2115          <li>A client <em class="bcp14">MUST NOT</em> send an Expect request-header field (<a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;14.20</a>) with the "100-continue" expectation if it does not intend to send a request body.
    2116          </li>
    2117       </ul>
    2118       <p id="rfc.section.8.2.3.p.3">Because of the presence of older implementations, the protocol allows ambiguous situations in which a client may send "Expect:
    2119          100-continue" without receiving either a 417 (Expectation Failed) status or a 100 (Continue) status. Therefore, when a client
    2120          sends this header field to an origin server (possibly via a proxy) from which it has never seen a 100 (Continue) status, the
    2121          client <em class="bcp14">SHOULD NOT</em> wait for an indefinite period before sending the request body.
    2122       </p>
    2123       <p id="rfc.section.8.2.3.p.4">Requirements for HTTP/1.1 origin servers: </p>
    2124       <ul>
    2125          <li>Upon receiving a request which includes an Expect request-header field with the "100-continue" expectation, an origin server <em class="bcp14">MUST</em> either respond with 100 (Continue) status and continue to read from the input stream, or respond with a final status code.
    2126             The origin server <em class="bcp14">MUST NOT</em> wait for the request body before sending the 100 (Continue) response. If it responds with a final status code, it <em class="bcp14">MAY</em> close the transport connection or it <em class="bcp14">MAY</em> continue to read and discard the rest of the request. It <em class="bcp14">MUST NOT</em> perform the requested method if it returns a final status code.
    2127          </li>
    2128          <li>An origin server <em class="bcp14">SHOULD NOT</em> send a 100 (Continue) response if the request message does not include an Expect request-header field with the "100-continue"
    2129             expectation, and <em class="bcp14">MUST NOT</em> send a 100 (Continue) response if such a request comes from an HTTP/1.0 (or earlier) client. There is an exception to this
    2130             rule: for compatibility with RFC 2068, a server <em class="bcp14">MAY</em> send a 100 (Continue) status in response to an HTTP/1.1 PUT or POST request that does not include an Expect request-header
    2131             field with the "100-continue" expectation. This exception, the purpose of which is to minimize any client processing delays
    2132             associated with an undeclared wait for 100 (Continue) status, applies only to HTTP/1.1 requests, and not to requests with
    2133             any other HTTP-version value.
    2134          </li>
    2135          <li>An origin server <em class="bcp14">MAY</em> omit a 100 (Continue) response if it has already received some or all of the request body for the corresponding request.
    2136          </li>
    2137          <li>An origin server that sends a 100 (Continue) response <em class="bcp14">MUST</em> ultimately send a final status code, once the request body is received and processed, unless it terminates the transport connection
    2138             prematurely.
    2139          </li>
    2140          <li>If an origin server receives a request that does not include an Expect request-header field with the "100-continue" expectation,
    2141             the request includes a request body, and the server responds with a final status code before reading the entire request body
    2142             from the transport connection, then the server <em class="bcp14">SHOULD NOT</em> close the transport connection until it has read the entire request, or until the client closes the connection. Otherwise,
    2143             the client might not reliably receive the response message. However, this requirement is not be construed as preventing a
    2144             server from defending itself against denial-of-service attacks, or from badly broken client implementations.
    2145          </li>
    2146       </ul>
    2147       <p id="rfc.section.8.2.3.p.5">Requirements for HTTP/1.1 proxies: </p>
    2148       <ul>
    2149          <li>If a proxy receives a request that includes an Expect request-header field with the "100-continue" expectation, and the proxy
    2150             either knows that the next-hop server complies with HTTP/1.1 or higher, or does not know the HTTP version of the next-hop
    2151             server, it <em class="bcp14">MUST</em> forward the request, including the Expect header field.
    2152          </li>
    2153          <li>If the proxy knows that the version of the next-hop server is HTTP/1.0 or lower, it <em class="bcp14">MUST NOT</em> forward the request, and it <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status.
    2154          </li>
    2155          <li>Proxies <em class="bcp14">SHOULD</em> maintain a cache recording the HTTP version numbers received from recently-referenced next-hop servers.
    2156          </li>
    2157          <li>A proxy <em class="bcp14">MUST NOT</em> forward a 100 (Continue) response if the request message was received from an HTTP/1.0 (or earlier) client and did not include
    2158             an Expect request-header field with the "100-continue" expectation. This requirement overrides the general rule for forwarding
    2159             of 1xx responses (see <a href="#status.1xx" title="Informational 1xx">Section&nbsp;10.1</a>).
    2160          </li>
    2161       </ul>
    2162       <h3 id="rfc.section.8.2.4"><a href="#rfc.section.8.2.4">8.2.4</a>&nbsp;<a id="connection.premature" href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></h3>
    2163       <p id="rfc.section.8.2.4.p.1">If an HTTP/1.1 client sends a request which includes a request body, but which does not include an Expect request-header field
    2164          with the "100-continue" expectation, and if the client is not directly connected to an HTTP/1.1 origin server, and if the
    2165          client sees the connection close before receiving any status from the server, the client <em class="bcp14">SHOULD</em> retry the request. If the client does retry this request, it <em class="bcp14">MAY</em> use the following "binary exponential backoff" algorithm to be assured of obtaining a reliable response:
    2166       </p>
    2167       <ol>
    2168          <li>Initiate a new connection to the server</li>
    2169          <li>Transmit the request-headers</li>
    2170          <li>Initialize a variable R to the estimated round-trip time to the server (e.g., based on the time it took to establish the connection),
    2171             or to a constant value of 5 seconds if the round-trip time is not available.
    2172          </li>
    2173          <li>Compute T = R * (2**N), where N is the number of previous retries of this request.</li>
    2174          <li>Wait either for an error response from the server, or for T seconds (whichever comes first)</li>
    2175          <li>If no error response is received, after T seconds transmit the body of the request.</li>
    2176          <li>If client sees that the connection is closed prematurely, repeat from step 1 until the request is accepted, an error response
    2177             is received, or the user becomes impatient and terminates the retry process.
    2178          </li>
    2179       </ol>
    2180       <p id="rfc.section.8.2.4.p.2">If at any point an error status is received, the client </p>
    2181       <ul>
    2182          <li><em class="bcp14">SHOULD NOT</em> continue and
    2183          </li>
    2184          <li><em class="bcp14">SHOULD</em> close the connection if it has not completed sending the request message.
    2185          </li>
    2186       </ul>
    2187       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h1>
    2188       <p id="rfc.section.9.p.1">The set of common methods for HTTP/1.1 is defined below. Although this set can be expanded, additional methods cannot be assumed
    2189          to share the same semantics for separately extended clients and servers. The Host request-header field (<a href="#header.host" id="rfc.xref.header.host.2" title="Host">Section&nbsp;14.23</a>) <em class="bcp14">MUST</em> accompany all HTTP/1.1 requests.
    2190       </p>
    2191       <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2>
    2192       <h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
    2193       <p id="rfc.section.9.1.1.p.1">Implementors should be aware that the software represents the user in their interactions over the Internet, and should be
    2194          careful to allow the user to be aware of any actions they might take which may have an unexpected significance to themselves
    2195          or others.
    2196       </p>
    2197       <p id="rfc.section.9.1.1.p.2">In particular, the convention has been established that the GET and HEAD methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "safe". This allows user
    2198          agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is made aware of the fact
    2199          that a possibly unsafe action is being requested.
    2200       </p>
    2201       <p id="rfc.section.9.1.1.p.3">Naturally, it is not possible to ensure that the server does not generate side-effects as a result of performing a GET request;
    2202          in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the
    2203          side-effects, so therefore cannot be held accountable for them.
    2204       </p>
    2205       <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
    2206       <p id="rfc.section.9.1.2.p.1">Methods can also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N
    2207          &gt; 0 identical requests is the same as for a single request. The methods GET, HEAD, PUT and DELETE share this property. Also,
    2208          the methods OPTIONS and TRACE <em class="bcp14">SHOULD NOT</em> have side effects, and so are inherently idempotent.
    2209       </p>
    2210       <p id="rfc.section.9.1.2.p.2">However, it is possible that a sequence of several requests is non-idempotent, even if all of the methods executed in that
    2211          sequence are idempotent. (A sequence is idempotent if a single execution of the entire sequence always yields a result that
    2212          is not changed by a reexecution of all, or part, of that sequence.) For example, a sequence is non-idempotent if its result
    2213          depends on a value that is later modified in the same sequence.
    2214       </p>
    2215       <p id="rfc.section.9.1.2.p.3">A sequence that never has side effects is idempotent, by definition (provided that no concurrent operations are being executed
    2216          on the same set of resources).
    2217       </p>
    2218       <div id="rfc.iref.o.3"></div>
    2219       <div id="rfc.iref.m.2"></div>
    2220       <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2>
    2221       <p id="rfc.section.9.2.p.1">The OPTIONS method represents a request for information about the communication options available on the request/response
    2222          chain identified by the Request-URI. This method allows the client to determine the options and/or requirements associated
    2223          with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
    2224       </p>
    2225       <p id="rfc.section.9.2.p.2">Responses to this method are not cacheable.</p>
    2226       <p id="rfc.section.9.2.p.3">If the OPTIONS request includes an entity-body (as indicated by the presence of Content-Length or Transfer-Encoding), then
    2227          the media type <em class="bcp14">MUST</em> be indicated by a Content-Type field. Although this specification does not define any use for such a body, future extensions
    2228          to HTTP might use the OPTIONS body to make more detailed queries on the server. A server that does not support such an extension <em class="bcp14">MAY</em> discard the request body.
    2229       </p>
    2230       <p id="rfc.section.9.2.p.4">If the Request-URI is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to
    2231          a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
    2232          as a "ping" or "no-op" type of method; it does nothing beyond allowing the client to test the capabilities of the server.
    2233          For example, this can be used to test a proxy for HTTP/1.1 compliance (or lack thereof).
    2234       </p>
    2235       <p id="rfc.section.9.2.p.5">If the Request-URI is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
    2236          with that resource.
    2237       </p>
    2238       <p id="rfc.section.9.2.p.6">A 200 response <em class="bcp14">SHOULD</em> include any header fields that indicate optional features implemented by the server and applicable to that resource (e.g.,
    2239          Allow), possibly including extensions not defined by this specification. The response body, if any, <em class="bcp14">SHOULD</em> also include information about the communication options. The format for such a body is not defined by this specification,
    2240          but might be defined by future extensions to HTTP. Content negotiation <em class="bcp14">MAY</em> be used to select the appropriate response format. If no response body is included, the response <em class="bcp14">MUST</em> include a Content-Length field with a field-value of "0".
    2241       </p>
    2242       <p id="rfc.section.9.2.p.7">The Max-Forwards request-header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain. When a proxy receives an OPTIONS request on an absoluteURI for which
    2243          request forwarding is permitted, the proxy <em class="bcp14">MUST</em> check for a Max-Forwards field. If the Max-Forwards field-value is zero ("0"), the proxy <em class="bcp14">MUST NOT</em> forward the message; instead, the proxy <em class="bcp14">SHOULD</em> respond with its own communication options. If the Max-Forwards field-value is an integer greater than zero, the proxy <em class="bcp14">MUST</em> decrement the field-value when it forwards the request. If no Max-Forwards field is present in the request, then the forwarded
    2244          request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
    2245       </p>
    2246       <div id="rfc.iref.g.94"></div>
    2247       <div id="rfc.iref.m.3"></div>
    2248       <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="GET" href="#GET">GET</a></h2>
    2249       <p id="rfc.section.9.3.p.1">The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI. If the Request-URI
    2250          refers to a data-producing process, it is the produced data which shall be returned as the entity in the response and not
    2251          the source text of the process, unless that text happens to be the output of the process.
    2252       </p>
    2253       <p id="rfc.section.9.3.p.2">The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since,
    2254          If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the entity be transferred only under
    2255          the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce unnecessary
    2256          network usage by allowing cached entities to be refreshed without requiring multiple requests or transferring data already
    2257          held by the client.
    2258       </p>
    2259       <p id="rfc.section.9.3.p.3">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial
    2260          GET requests that only part of the entity be transferred, as described in <a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section&nbsp;14.35</a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed
    2261          without transferring data already held by the client.
    2262       </p>
    2263       <p id="rfc.section.9.3.p.4">The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching described in <a href="#caching" title="Caching in HTTP">Section&nbsp;13</a>.
    2264       </p>
    2265       <p id="rfc.section.9.3.p.5">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URI's">Section&nbsp;15.1.3</a> for security considerations when used for forms.
    2266       </p>
    2267       <div id="rfc.iref.h.2"></div>
    2268       <div id="rfc.iref.m.4"></div>
    2269       <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h2>
    2270       <p id="rfc.section.9.4.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request <em class="bcp14">SHOULD</em> be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about
    2271          the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext
    2272          links for validity, accessibility, and recent modification.
    2273       </p>
    2274       <p id="rfc.section.9.4.p.2">The response to a HEAD request <em class="bcp14">MAY</em> be cacheable in the sense that the information contained in the response <em class="bcp14">MAY</em> be used to update a previously cached entity from that resource. If the new field values indicate that the cached entity differs
    2275          from the current entity (as would be indicated by a change in Content-Length, Content-MD5, ETag or Last-Modified), then the
    2276          cache <em class="bcp14">MUST</em> treat the cache entry as stale.
    2277       </p>
    2278       <div id="rfc.iref.p.2"></div>
    2279       <div id="rfc.iref.m.5"></div>
    2280       <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a id="POST" href="#POST">POST</a></h2>
    2281       <p id="rfc.section.9.5.p.1">The POST method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of
    2282          the resource identified by the Request-URI in the Request-Line. POST is designed to allow a uniform method to cover the following
    2283          functions:
    2284       </p>
    2285       <ul>
    2286          <li>Annotation of existing resources;</li>
    2287          <li>Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;</li>
    2288          <li>Providing a block of data, such as the result of submitting a form, to a data-handling process;</li>
    2289          <li>Extending a database through an append operation.</li>
    2290       </ul>
    2291       <p id="rfc.section.9.5.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the Request-URI.
    2292          The posted entity is subordinate to that URI in the same way that a file is subordinate to a directory containing it, a news
    2293          article is subordinate to a newsgroup to which it is posted, or a record is subordinate to a database.
    2294       </p>
    2295       <p id="rfc.section.9.5.p.3">The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either
    2296          200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity
    2297          that describes the result.
    2298       </p>
    2299       <p id="rfc.section.9.5.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be 201 (Created) and contain an entity which describes the status of the request and refers to the new resource, and a Location
    2300          header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;14.30</a>).
    2301       </p>
    2302       <p id="rfc.section.9.5.p.5">Responses to this method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields.
    2303          However, the 303 (See Other) response can be used to direct the user agent to retrieve a cacheable resource.
    2304       </p>
    2305       <p id="rfc.section.9.5.p.6">POST requests <em class="bcp14">MUST</em> obey the message transmission requirements set out in <a href="#message.transmission.requirements" title="Message Transmission Requirements">Section&nbsp;8.2</a>.
    2306       </p>
    2307       <p id="rfc.section.9.5.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URI's">Section&nbsp;15.1.3</a> for security considerations.
    2308       </p>
    2309       <div id="rfc.iref.p.3"></div>
    2310       <div id="rfc.iref.m.6"></div>
    2311       <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h2>
    2312       <p id="rfc.section.9.6.p.1">The PUT method requests that the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an
    2313          already existing resource, the enclosed entity <em class="bcp14">SHOULD</em> be considered as a modified version of the one residing on the origin server. If the Request-URI does not point to an existing
    2314          resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create
    2315          the resource with that URI. If a new resource is created, the origin server <em class="bcp14">MUST</em> inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No
    2316          Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request. If the resource could not be created or modified with the Request-URI,
    2317          an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* (e.g. Content-Range) headers that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
    2318       </p>
    2319       <p id="rfc.section.9.6.p.2">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
    2320       </p>
    2321       <p id="rfc.section.9.6.p.3">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The
    2322          URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting
    2323          process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request
    2324          identifies the entity enclosed with the request -- the user agent knows what URI is intended and the server <em class="bcp14">MUST NOT</em> attempt to apply the request to some other resource. If the server desires that the request be applied to a different URI,
    2325          it <em class="bcp14">MUST</em> send a 301 (Moved Permanently) response; the user agent <em class="bcp14">MAY</em> then make its own decision regarding whether or not to redirect the request.
    2326       </p>
    2327       <p id="rfc.section.9.6.p.4">A single resource <em class="bcp14">MAY</em> be identified by many different URIs. For example, an article might have a URI for identifying "the current version" which
    2328          is separate from the URI identifying each particular version. In this case, a PUT request on a general URI might result in
    2329          several other URIs being defined by the origin server.
    2330       </p>
    2331       <p id="rfc.section.9.6.p.5">HTTP/1.1 does not define how a PUT method affects the state of an origin server.</p>
    2332       <p id="rfc.section.9.6.p.6">PUT requests <em class="bcp14">MUST</em> obey the message transmission requirements set out in <a href="#message.transmission.requirements" title="Message Transmission Requirements">Section&nbsp;8.2</a>.
    2333       </p>
    2334       <p id="rfc.section.9.6.p.7">Unless otherwise specified for a particular entity-header, the entity-headers in the PUT request <em class="bcp14">SHOULD</em> be applied to the resource created or modified by the PUT.
    2335       </p>
    2336       <div id="rfc.iref.d.3"></div>
    2337       <div id="rfc.iref.m.7"></div>
    2338       <h2 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h2>
    2339       <p id="rfc.section.9.7.p.1">The DELETE method requests that the origin server delete the resource identified by the Request-URI. This method <em class="bcp14">MAY</em> be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation
    2340          has been carried out, even if the status code returned from the origin server indicates that the action has been completed
    2341          successfully. However, the server <em class="bcp14">SHOULD NOT</em> indicate success unless, at the time the response is given, it intends to delete the resource or move it to an inaccessible
    2342          location.
    2343       </p>
    2344       <p id="rfc.section.9.7.p.2">A successful response <em class="bcp14">SHOULD</em> be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted,
    2345          or 204 (No Content) if the action has been enacted but the response does not include an entity.
    2346       </p>
    2347       <p id="rfc.section.9.7.p.3">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
    2348       </p>
    2349       <div id="rfc.iref.t.2"></div>
    2350       <div id="rfc.iref.m.8"></div>
    2351       <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h2>
    2352       <p id="rfc.section.9.8.p.1">The TRACE method is used to invoke a remote, application-layer loop-back of the request message. The final recipient of the
    2353          request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the entity-body of a 200 (OK) response. The final recipient is either the
    2354          origin server or the first proxy or gateway to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;14.31</a>). A TRACE request <em class="bcp14">MUST NOT</em> include an entity.
    2355       </p>
    2356       <p id="rfc.section.9.8.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing
    2357          or diagnostic information. The value of the Via header field (<a href="#header.via" id="rfc.xref.header.via.2" title="Via">Section&nbsp;14.45</a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the
    2358          client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an
    2359          infinite loop.
    2360       </p>
    2361       <p id="rfc.section.9.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> contain the entire request message in the entity-body, with a Content-Type of "message/http". Responses to this method <em class="bcp14">MUST NOT</em> be cached.
    2362       </p>
    2363       <div id="rfc.iref.c.7"></div>
    2364       <div id="rfc.iref.m.9"></div>
    2365       <h2 id="rfc.section.9.9"><a href="#rfc.section.9.9">9.9</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h2>
    2366       <p id="rfc.section.9.9.p.1">This specification reserves the method name CONNECT for use with a proxy that can dynamically switch to being a tunnel (e.g.
    2367          SSL tunneling <a href="#Luo1998" id="rfc.xref.Luo1998.1"><cite title="Tunneling TCP based protocols through Web proxy servers">[Luo1998]</cite></a>).
    2368       </p>
    2369       <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="status.codes" href="#status.codes">Status Code Definitions</a></h1>
    2370       <p id="rfc.section.10.p.1">Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required
    2371          in the response.
    2372       </p>
    2373       <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
    2374       <p id="rfc.section.10.1.p.1">This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is
    2375          terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any
    2376          1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions.
    2377       </p>
    2378       <p id="rfc.section.10.1.p.2">A client <em class="bcp14">MUST</em> be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100
    2379          (Continue) status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
    2380       </p>
    2381       <p id="rfc.section.10.1.p.3">Proxies <em class="bcp14">MUST</em> forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself
    2382          requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards
    2383          a request, then it need not forward the corresponding 100 (Continue) response(s).)
    2384       </p>
    2385       <div id="rfc.iref.142"></div>
    2386       <div id="rfc.iref.s.4"></div>
    2387       <h3 id="rfc.section.10.1.1"><a href="#rfc.section.10.1.1">10.1.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
    2388       <p id="rfc.section.10.1.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been
    2389          received and has not yet been rejected by the server. The client <em class="bcp14">SHOULD</em> continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The
    2390          server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section&nbsp;8.2.3</a> for detailed discussion of the use and handling of this status code.
    2391       </p>
    2392       <div id="rfc.iref.143"></div>
    2393       <div id="rfc.iref.s.5"></div>
    2394       <h3 id="rfc.section.10.1.2"><a href="#rfc.section.10.1.2">10.1.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    2395       <p id="rfc.section.10.1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section&nbsp;14.42</a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
    2396          by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    2397       </p>
    2398       <p id="rfc.section.10.1.2.p.2">The protocol <em class="bcp14">SHOULD</em> be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over
    2399          older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
    2400          such features.
    2401       </p>
    2402       <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
    2403       <p id="rfc.section.10.2.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
    2404       <div id="rfc.iref.144"></div>
    2405       <div id="rfc.iref.s.6"></div>
    2406       <h3 id="rfc.section.10.2.1"><a href="#rfc.section.10.2.1">10.2.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
    2407       <p id="rfc.section.10.2.1.p.1">The request has succeeded. The information returned with the response is dependent on the method used in the request, for
    2408          example:
    2409       </p>
    2410       <dl>
    2411          <dt>GET</dt>
    2412          <dd>an entity corresponding to the requested resource is sent in the response;</dd>
    2413          <dt>HEAD</dt>
    2414          <dd>the entity-header fields corresponding to the requested resource are sent in the response without any message-body;</dd>
    2415          <dt>POST</dt>
    2416          <dd>an entity describing or containing the result of the action;</dd>
    2417          <dt>TRACE</dt>
    2418          <dd>an entity containing the request message as received by the end server.</dd>
    2419       </dl>
    2420       <div id="rfc.iref.145"></div>
    2421       <div id="rfc.iref.s.7"></div>
    2422       <h3 id="rfc.section.10.2.2"><a href="#rfc.section.10.2.2">10.2.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
    2423       <p id="rfc.section.10.2.2.p.1">The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced
    2424          by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header
    2425          field. The response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose
    2426          the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin
    2427          server <em class="bcp14">MUST</em> create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with 202 (Accepted) response instead.
    2428       </p>
    2429       <p id="rfc.section.10.2.2.p.2">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity tag for the requested variant just created,
    2430          see <a href="#header.etag" id="rfc.xref.header.etag.3" title="ETag">Section&nbsp;14.19</a>.
    2431       </p>
    2432       <div id="rfc.iref.146"></div>
    2433       <div id="rfc.iref.s.8"></div>
    2434       <h3 id="rfc.section.10.2.3"><a href="#rfc.section.10.2.3">10.2.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
    2435       <p id="rfc.section.10.2.3.p.1">The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually
    2436          be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
    2437          code from an asynchronous operation such as this.
    2438       </p>
    2439       <p id="rfc.section.10.2.3.p.2">The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process
    2440          (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
    2441          server persist until the process is completed. The entity returned with this response <em class="bcp14">SHOULD</em> include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the
    2442          user can expect the request to be fulfilled.
    2443       </p>
    2444       <div id="rfc.iref.147"></div>
    2445       <div id="rfc.iref.s.9"></div>
    2446       <h3 id="rfc.section.10.2.4"><a href="#rfc.section.10.2.4">10.2.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    2447       <p id="rfc.section.10.2.4.p.1">The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered
    2448          from a local or a third-party copy. The set presented <em class="bcp14">MAY</em> be a subset or superset of the original version. For example, including local annotation information about the resource might
    2449          result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only
    2450          appropriate when the response would otherwise be 200 (OK).
    2451       </p>
    2452       <div id="rfc.iref.148"></div>
    2453       <div id="rfc.iref.s.10"></div>
    2454       <h3 id="rfc.section.10.2.5"><a href="#rfc.section.10.2.5">10.2.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
    2455       <p id="rfc.section.10.2.5.p.1">The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation.
    2456          The response <em class="bcp14">MAY</em> include new or updated metainformation in the form of entity-headers, which if present <em class="bcp14">SHOULD</em> be associated with the requested variant.
    2457       </p>
    2458       <p id="rfc.section.10.2.5.p.2">If the client is a user agent, it <em class="bcp14">SHOULD NOT</em> change its document view from that which caused the request to be sent. This response is primarily intended to allow input
    2459          for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation <em class="bcp14">SHOULD</em> be applied to the document currently in the user agent's active view.
    2460       </p>
    2461       <p id="rfc.section.10.2.5.p.3">The 204 response <em class="bcp14">MUST NOT</em> include a message-body, and thus is always terminated by the first empty line after the header fields.
    2462       </p>
    2463       <div id="rfc.iref.149"></div>
    2464       <div id="rfc.iref.s.11"></div>
    2465       <h3 id="rfc.section.10.2.6"><a href="#rfc.section.10.2.6">10.2.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
    2466       <p id="rfc.section.10.2.6.p.1">The server has fulfilled the request and the user agent <em class="bcp14">SHOULD</em> reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions
    2467          to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate
    2468          another input action. The response <em class="bcp14">MUST NOT</em> include an entity.
    2469       </p>
    2470       <div id="rfc.iref.150"></div>
    2471       <div id="rfc.iref.s.12"></div>
    2472       <h3 id="rfc.section.10.2.7"><a href="#rfc.section.10.2.7">10.2.7</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h3>
    2473       <p id="rfc.section.10.2.7.p.1">The server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a Range header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section&nbsp;14.35</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section&nbsp;14.27</a>) to make the request conditional.
    2474       </p>
    2475       <p id="rfc.section.10.2.7.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
    2476       </p>
    2477       <ul>
    2478          <li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;14.16</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields
    2479             for each part. If a Content-Length header field is present in the response, its value <em class="bcp14">MUST</em> match the actual number of OCTETs transmitted in the message-body.
    2480          </li>
    2481          <li>Date</li>
    2482          <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
    2483          <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
    2484             variant
    2485          </li>
    2486       </ul>
    2487       <p id="rfc.section.10.2.7.p.3">If the 206 response is the result of an If-Range request that used a strong cache validator (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;13.3.3</a>), the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response <em class="bcp14">MUST NOT</em> include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the
    2488          response <em class="bcp14">MUST</em> include all of the entity-headers that would have been returned with a 200 (OK) response to the same request.
    2489       </p>
    2490       <p id="rfc.section.10.2.7.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see <a href="#combining.byte.ranges" title="Combining Byte Ranges">13.5.4</a>.
    2491       </p>
    2492       <p id="rfc.section.10.2.7.p.5">A cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> cache 206 (Partial) responses.
    2493       </p>
    2494       <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
    2495       <p id="rfc.section.10.3.p.1">This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request.
    2496          The action required <em class="bcp14">MAY</em> be carried out by the user agent without interaction with the user if and only if the method used in the second request is
    2497          GET or HEAD. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection.
    2498       </p>
    2499       <ul class="empty">
    2500          <li> <b>Note:</b> previous versions of this specification recommended a maximum of five redirections. Content developers should be aware that
    2501             there might be clients that implement such a fixed limitation.
    2502          </li>
    2503       </ul>
    2504       <div id="rfc.iref.151"></div>
    2505       <div id="rfc.iref.s.13"></div>
    2506       <h3 id="rfc.section.10.3.1"><a href="#rfc.section.10.3.1">10.3.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    2507       <p id="rfc.section.10.3.1.p.1">The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven
    2508          negotiation information (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;12</a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that
    2509          location.
    2510       </p>
    2511       <p id="rfc.section.10.3.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose
    2512          the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending
    2513          upon the format and the capabilities of the user agent, selection of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    2514       </p>
    2515       <p id="rfc.section.10.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.
    2516       </p>
    2517       <div id="rfc.iref.152"></div>
    2518       <div id="rfc.iref.s.14"></div>
    2519       <h3 id="rfc.section.10.3.2"><a href="#rfc.section.10.3.2">10.3.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    2520       <p id="rfc.section.10.3.2.p.1">The requested resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI
    2521          to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
    2522       </p>
    2523       <p id="rfc.section.10.3.2.p.2">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
    2524       </p>
    2525       <p id="rfc.section.10.3.2.p.3">If the 301 status code is received in response to a request other than GET or HEAD, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
    2526          the request was issued.
    2527       </p>
    2528       <ul class="empty">
    2529          <li> <b>Note:</b> When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously
    2530             change it into a GET request.
    2531          </li>
    2532       </ul>
    2533       <div id="rfc.iref.153"></div>
    2534       <div id="rfc.iref.s.15"></div>
    2535       <h3 id="rfc.section.10.3.3"><a href="#rfc.section.10.3.3">10.3.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    2536       <p id="rfc.section.10.3.3.p.1">The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the
    2537          client <em class="bcp14">SHOULD</em> continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires
    2538          header field.
    2539       </p>
    2540       <p id="rfc.section.10.3.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
    2541       </p>
    2542       <p id="rfc.section.10.3.3.p.3">If the 302 status code is received in response to a request other than GET or HEAD, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
    2543          the request was issued.
    2544       </p>
    2545       <ul class="empty">
    2546          <li> <b>Note:</b> RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. However, most
    2547             existing user agent implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless
    2548             of the original request method. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear
    2549             which kind of reaction is expected of the client.
    2550          </li>
    2551       </ul>
    2552       <div id="rfc.iref.154"></div>
    2553       <div id="rfc.iref.s.16"></div>
    2554       <h3 id="rfc.section.10.3.4"><a href="#rfc.section.10.3.4">10.3.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
    2555       <p id="rfc.section.10.3.4.p.1">The response to the request can be found under a different URI and <em class="bcp14">SHOULD</em> be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script
    2556          to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested
    2557          resource. The 303 response <em class="bcp14">MUST NOT</em> be cached, but the response to the second (redirected) request might be cacheable.
    2558       </p>
    2559       <p id="rfc.section.10.3.4.p.2">The different URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
    2560       </p>
    2561       <ul class="empty">
    2562          <li> <b>Note:</b> Many pre-HTTP/1.1 user agents do not understand the 303 status. When interoperability with such clients is a concern, the
    2563             302 status code may be used instead, since most user agents react to a 302 response as described here for 303.
    2564          </li>
    2565       </ul>
    2566       <div id="rfc.iref.155"></div>
    2567       <div id="rfc.iref.s.17"></div>
    2568       <h3 id="rfc.section.10.3.5"><a href="#rfc.section.10.3.5">10.3.5</a>&nbsp;<a id="status.304" href="#status.304">304 Not Modified</a></h3>
    2569       <p id="rfc.section.10.3.5.p.1">If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server <em class="bcp14">SHOULD</em> respond with this status code. The 304 response <em class="bcp14">MUST NOT</em> contain a message-body, and thus is always terminated by the first empty line after the header fields.
    2570       </p>
    2571       <p id="rfc.section.10.3.5.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
    2572       </p>
    2573       <ul>
    2574          <li>Date, unless its omission is required by <a href="#clockless.origin.server.operation" title="Clockless Origin Server Operation">Section&nbsp;14.18.1</a></li>
    2575       </ul>
    2576       <p id="rfc.section.10.3.5.p.3">If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without
    2577          one (as already specified by [RFC 2068], section <a href="http://tools.ietf.org/html/rfc2068#section-14.19" id="rfc.xref.RFC2068.4">14.19</a>), caches will operate correctly.
    2578       </p>
    2579       <ul>
    2580          <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
    2581          <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
    2582             variant
    2583          </li>
    2584       </ul>
    2585       <p id="rfc.section.10.3.5.p.4">If the conditional GET used a strong cache validator (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;13.3.3</a>), the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response <em class="bcp14">MUST NOT</em> include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
    2586       </p>
    2587       <p id="rfc.section.10.3.5.p.5">If a 304 response indicates an entity not currently cached, then the cache <em class="bcp14">MUST</em> disregard the response and repeat the request without the conditional.
    2588       </p>
    2589       <p id="rfc.section.10.3.5.p.6">If a cache uses a received 304 response to update a cache entry, the cache <em class="bcp14">MUST</em> update the entry to reflect any new field values given in the response.
    2590       </p>
    2591       <div id="rfc.iref.156"></div>
    2592       <div id="rfc.iref.s.18"></div>
    2593       <h3 id="rfc.section.10.3.6"><a href="#rfc.section.10.3.6">10.3.6</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
    2594       <p id="rfc.section.10.3.6.p.1">The requested resource <em class="bcp14">MUST</em> be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is
    2595          expected to repeat this single request via the proxy. 305 responses <em class="bcp14">MUST</em> only be generated by origin servers.
    2596       </p>
    2597       <ul class="empty">
    2598          <li> <b>Note:</b> RFC 2068 was not clear that 305 was intended to redirect a single request, and to be generated by origin servers only. Not
    2599             observing these limitations has significant security consequences.
    2600          </li>
    2601       </ul>
    2602       <div id="rfc.iref.157"></div>
    2603       <div id="rfc.iref.s.19"></div>
    2604       <h3 id="rfc.section.10.3.7"><a href="#rfc.section.10.3.7">10.3.7</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
    2605       <p id="rfc.section.10.3.7.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p>
    2606       <div id="rfc.iref.158"></div>
    2607       <div id="rfc.iref.s.20"></div>
    2608       <h3 id="rfc.section.10.3.8"><a href="#rfc.section.10.3.8">10.3.8</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    2609       <p id="rfc.section.10.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires
    2610          header field.
    2611       </p>
    2612       <p id="rfc.section.10.3.8.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand
    2613          the 307 status. Therefore, the note <em class="bcp14">SHOULD</em> contain the information necessary for a user to repeat the original request on the new URI.
    2614       </p>
    2615       <p id="rfc.section.10.3.8.p.3">If the 307 status code is received in response to a request other than GET or HEAD, the user agent <em class="bcp14">MUST NOT</em> automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which
    2616          the request was issued.
    2617       </p>
    2618       <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
    2619       <p id="rfc.section.10.4.p.1">The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD
    2620          request, the server <em class="bcp14">SHOULD</em> include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    2621          These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included entity to the user.
    2622       </p>
    2623       <p id="rfc.section.10.4.p.2">If the client is sending data, a server implementation using TCP <em class="bcp14">SHOULD</em> be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes
    2624          the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send
    2625          a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted
    2626          by the HTTP application.
    2627       </p>
    2628       <div id="rfc.iref.159"></div>
    2629       <div id="rfc.iref.s.21"></div>
    2630       <h3 id="rfc.section.10.4.1"><a href="#rfc.section.10.4.1">10.4.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    2631       <p id="rfc.section.10.4.1.p.1">The request could not be understood by the server due to malformed syntax. The client <em class="bcp14">SHOULD NOT</em> repeat the request without modifications.
    2632       </p>
    2633       <div id="rfc.iref.160"></div>
    2634       <div id="rfc.iref.s.22"></div>
    2635       <h3 id="rfc.section.10.4.2"><a href="#rfc.section.10.4.2">10.4.2</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h3>
    2636       <p id="rfc.section.10.4.2.p.1">The request requires user authentication. The response <em class="bcp14">MUST</em> include a WWW-Authenticate header field (<a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.2" title="WWW-Authenticate">Section&nbsp;14.47</a>) containing a challenge applicable to the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Authorization header field (<a href="#header.authorization" id="rfc.xref.header.authorization.2" title="Authorization">Section&nbsp;14.8</a>). If the request already included Authorization credentials, then the 401 response indicates that authorization has been
    2637          refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
    2638          already attempted authentication at least once, then the user <em class="bcp14">SHOULD</em> be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP
    2639          access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
    2640       </p>
    2641       <div id="rfc.iref.161"></div>
    2642       <div id="rfc.iref.s.23"></div>
    2643       <h3 id="rfc.section.10.4.3"><a href="#rfc.section.10.4.3">10.4.3</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
    2644       <p id="rfc.section.10.4.3.p.1">This code is reserved for future use.</p>
    2645       <div id="rfc.iref.162"></div>
    2646       <div id="rfc.iref.s.24"></div>
    2647       <h3 id="rfc.section.10.4.4"><a href="#rfc.section.10.4.4">10.4.4</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    2648       <p id="rfc.section.10.4.4.p.1">The server understood the request, but is refusing to fulfill it. Authorization will not help and the request <em class="bcp14">SHOULD NOT</em> be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled,
    2649          it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client,
    2650          the status code 404 (Not Found) can be used instead.
    2651       </p>
    2652       <div id="rfc.iref.163"></div>
    2653       <div id="rfc.iref.s.25"></div>
    2654       <h3 id="rfc.section.10.4.5"><a href="#rfc.section.10.4.5">10.4.5</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    2655       <p id="rfc.section.10.4.5.p.1">The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or
    2656          permanent. The 410 (Gone) status code <em class="bcp14">SHOULD</em> be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable
    2657          and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
    2658          has been refused, or when no other response is applicable.
    2659       </p>
    2660       <div id="rfc.iref.164"></div>
    2661       <div id="rfc.iref.s.26"></div>
    2662       <h3 id="rfc.section.10.4.6"><a href="#rfc.section.10.4.6">10.4.6</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    2663       <p id="rfc.section.10.4.6.p.1">The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource.
    2664       </p>
    2665       <div id="rfc.iref.165"></div>
    2666       <div id="rfc.iref.s.27"></div>
    2667       <h3 id="rfc.section.10.4.7"><a href="#rfc.section.10.4.7">10.4.7</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    2668       <p id="rfc.section.10.4.7.p.1">The resource identified by the request is only capable of generating response entities which have content characteristics
    2669          not acceptable according to the accept headers sent in the request.
    2670       </p>
    2671       <p id="rfc.section.10.4.7.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of available entity characteristics and location(s) from which the user or user agent
    2672          can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field.
    2673          Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice <em class="bcp14">MAY</em> be performed automatically. However, this specification does not define any standard for such automatic selection.
    2674       </p>
    2675       <ul class="empty">
    2676          <li> <b>Note:</b> HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept headers sent in the request.
    2677             In some cases, this may even be preferable to sending a 406 response. User agents are encouraged to inspect the headers of
    2678             an incoming response to determine if it is acceptable.
    2679          </li>
    2680       </ul>
    2681       <p id="rfc.section.10.4.7.p.3">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.
    2682       </p>
    2683       <div id="rfc.iref.166"></div>
    2684       <div id="rfc.iref.s.28"></div>
    2685       <h3 id="rfc.section.10.4.8"><a href="#rfc.section.10.4.8">10.4.8</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h3>
    2686       <p id="rfc.section.10.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The
    2687          proxy <em class="bcp14">MUST</em> return a Proxy-Authenticate header field (<a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section&nbsp;14.33</a>) containing a challenge applicable to the proxy for the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Proxy-Authorization header field (<a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section&nbsp;14.34</a>). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.2"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
    2688       </p>
    2689       <div id="rfc.iref.167"></div>
    2690       <div id="rfc.iref.s.29"></div>
    2691       <h3 id="rfc.section.10.4.9"><a href="#rfc.section.10.4.9">10.4.9</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
    2692       <p id="rfc.section.10.4.9.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time.
    2693       </p>
    2694       <div id="rfc.iref.168"></div>
    2695       <div id="rfc.iref.s.30"></div>
    2696       <h3 id="rfc.section.10.4.10"><a href="#rfc.section.10.4.10">10.4.10</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
    2697       <p id="rfc.section.10.4.10.p.1">The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in
    2698          situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
    2699          body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response entity would include
    2700          enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
    2701       </p>
    2702       <p id="rfc.section.10.4.10.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity
    2703          being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
    2704          use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain
    2705          a list of the differences between the two versions in a format defined by the response Content-Type.
    2706       </p>
    2707       <div id="rfc.iref.169"></div>
    2708       <div id="rfc.iref.s.31"></div>
    2709       <h3 id="rfc.section.10.4.11"><a href="#rfc.section.10.4.11">10.4.11</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    2710       <p id="rfc.section.10.4.11.p.1">The requested resource is no longer available at the server and no forwarding address is known. This condition is expected
    2711          to be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether
    2712          or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead. This response is cacheable unless indicated otherwise.
    2713       </p>
    2714       <p id="rfc.section.10.4.11.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
    2715          is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
    2716          is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
    2717          site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time
    2718          -- that is left to the discretion of the server owner.
    2719       </p>
    2720       <div id="rfc.iref.170"></div>
    2721       <div id="rfc.iref.s.32"></div>
    2722       <h3 id="rfc.section.10.4.12"><a href="#rfc.section.10.4.12">10.4.12</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
    2723       <p id="rfc.section.10.4.12.p.1">The server refuses to accept the request without a defined Content-Length. The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request
    2724          message.
    2725       </p>
    2726       <div id="rfc.iref.171"></div>
    2727       <div id="rfc.iref.s.33"></div>
    2728       <h3 id="rfc.section.10.4.13"><a href="#rfc.section.10.4.13">10.4.13</a>&nbsp;<a id="status.412" href="#status.412">412 Precondition Failed</a></h3>
    2729       <p id="rfc.section.10.4.13.p.1">The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This
    2730          response code allows the client to place preconditions on the current resource metainformation (header field data) and thus
    2731          prevent the requested method from being applied to a resource other than the one intended.
    2732       </p>
    2733       <div id="rfc.iref.172"></div>
    2734       <div id="rfc.iref.s.34"></div>
    2735       <h3 id="rfc.section.10.4.14"><a href="#rfc.section.10.4.14">10.4.14</a>&nbsp;<a id="status.413" href="#status.413">413 Request Entity Too Large</a></h3>
    2736       <p id="rfc.section.10.4.14.p.1">The server is refusing to process a request because the request entity is larger than the server is willing or able to process.
    2737          The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
    2738       </p>
    2739       <p id="rfc.section.10.4.14.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a Retry-After header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.
    2740       </p>
    2741       <div id="rfc.iref.173"></div>
    2742       <div id="rfc.iref.s.35"></div>
    2743       <h3 id="rfc.section.10.4.15"><a href="#rfc.section.10.4.15">10.4.15</a>&nbsp;<a id="status.414" href="#status.414">414 Request-URI Too Long</a></h3>
    2744       <p id="rfc.section.10.4.15.p.1">The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This
    2745          rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query
    2746          information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points
    2747          to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some
    2748          servers using fixed-length buffers for reading or manipulating the Request-URI.
    2749       </p>
    2750       <div id="rfc.iref.174"></div>
    2751       <div id="rfc.iref.s.36"></div>
    2752       <h3 id="rfc.section.10.4.16"><a href="#rfc.section.10.4.16">10.4.16</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    2753       <p id="rfc.section.10.4.16.p.1">The server is refusing to service the request because the entity of the request is in a format not supported by the requested
    2754          resource for the requested method.
    2755       </p>
    2756       <div id="rfc.iref.175"></div>
    2757       <div id="rfc.iref.s.37"></div>
    2758       <h3 id="rfc.section.10.4.17"><a href="#rfc.section.10.4.17">10.4.17</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3>
    2759       <p id="rfc.section.10.4.17.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range request-header field (<a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section&nbsp;14.35</a>), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request
    2760          did not include an If-Range request-header field. (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec
    2761          values were greater than the current length of the selected resource.)
    2762       </p>
    2763       <p id="rfc.section.10.4.17.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range entity-header field specifying the current length of the selected resource (see <a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;14.16</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.
    2764       </p>
    2765       <div id="rfc.iref.176"></div>
    2766       <div id="rfc.iref.s.38"></div>
    2767       <h3 id="rfc.section.10.4.18"><a href="#rfc.section.10.4.18">10.4.18</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    2768       <p id="rfc.section.10.4.18.p.1">The expectation given in an Expect request-header field (see <a href="#header.expect" id="rfc.xref.header.expect.4" title="Expect">Section&nbsp;14.20</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
    2769          not be met by the next-hop server.
    2770       </p>
    2771       <h2 id="rfc.section.10.5"><a href="#rfc.section.10.5">10.5</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
    2772       <p id="rfc.section.10.5.p.1">Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable
    2773          of performing the request. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    2774          User agents <em class="bcp14">SHOULD</em> display any included entity to the user. These response codes are applicable to any request method.
    2775       </p>
    2776       <div id="rfc.iref.177"></div>
    2777       <div id="rfc.iref.s.39"></div>
    2778       <h3 id="rfc.section.10.5.1"><a href="#rfc.section.10.5.1">10.5.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    2779       <p id="rfc.section.10.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    2780       <div id="rfc.iref.178"></div>
    2781       <div id="rfc.iref.s.40"></div>
    2782       <h3 id="rfc.section.10.5.2"><a href="#rfc.section.10.5.2">10.5.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    2783       <p id="rfc.section.10.5.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
    2784          does not recognize the request method and is not capable of supporting it for any resource.
    2785       </p>
    2786       <div id="rfc.iref.179"></div>
    2787       <div id="rfc.iref.s.41"></div>
    2788       <h3 id="rfc.section.10.5.3"><a href="#rfc.section.10.5.3">10.5.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    2789       <p id="rfc.section.10.5.3.p.1">The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting
    2790          to fulfill the request.
    2791       </p>
    2792       <div id="rfc.iref.180"></div>
    2793       <div id="rfc.iref.s.42"></div>
    2794       <h3 id="rfc.section.10.5.4"><a href="#rfc.section.10.5.4">10.5.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    2795       <p id="rfc.section.10.5.4.p.1">The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication
    2796          is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay <em class="bcp14">MAY</em> be indicated in a Retry-After header. If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
    2797       </p>
    2798       <ul class="empty">
    2799          <li> <b>Note:</b> The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish
    2800             to simply refuse the connection.
    2801          </li>
    2802       </ul>
    2803       <div id="rfc.iref.181"></div>
    2804       <div id="rfc.iref.s.43"></div>
    2805       <h3 id="rfc.section.10.5.5"><a href="#rfc.section.10.5.5">10.5.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    2806       <p id="rfc.section.10.5.5.p.1">The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the
    2807          URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
    2808       </p>
    2809       <ul class="empty">
    2810          <li> <b>Note:</b> Note to implementors: some deployed proxies are known to return 400 or 500 when DNS lookups time out.
    2811          </li>
    2812       </ul>
    2813       <div id="rfc.iref.182"></div>
    2814       <div id="rfc.iref.s.44"></div>
    2815       <h3 id="rfc.section.10.5.6"><a href="#rfc.section.10.5.6">10.5.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    2816       <p id="rfc.section.10.5.6.p.1">The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server
    2817          is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    2818          in <a href="#http.version" title="HTTP Version">Section&nbsp;3.1</a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server.
    2819       </p>
    2820       <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="access.authentication" href="#access.authentication">Access Authentication</a></h1>
    2821       <p id="rfc.section.11.p.1">HTTP provides several <em class="bcp14">OPTIONAL</em> challenge-response authentication mechanisms which can be used by a server to challenge a client request and by a client to
    2822          provide authentication information. The general framework for access authentication, and the specification of "basic" and
    2823          "digest" authentication, are specified in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.3"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. This specification adopts the definitions of "challenge" and "credentials" from that specification.
    2824       </p>
    2825       <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1>
    2826       <p id="rfc.section.12.p.1">Most HTTP responses include an entity which contains information for interpretation by a human user. Naturally, it is desirable
    2827          to supply the user with the "best available" entity corresponding to the request. Unfortunately for servers and caches, not
    2828          all users have the same preferences for what is "best," and not all user agents are equally capable of rendering all entity
    2829          types. For that reason, HTTP has provisions for several mechanisms for "content negotiation" -- the process of selecting the
    2830          best representation for a given response when there are multiple representations available.
    2831       </p>
    2832       <ul class="empty">
    2833          <li> <b>Note:</b> This is not called "format negotiation" because the alternate representations may be of the same media type, but use different
    2834             capabilities of that type, be in different languages, etc.
    2835          </li>
    2836       </ul>
    2837       <p id="rfc.section.12.p.2">Any response containing an entity-body <em class="bcp14">MAY</em> be subject to negotiation, including error responses.
    2838       </p>
    2839       <p id="rfc.section.12.p.3">There are two kinds of content negotiation which are possible in HTTP: server-driven and agent-driven negotiation. These two
    2840          kinds of negotiation are orthogonal and thus may be used separately or in combination. One method of combination, referred
    2841          to as transparent negotiation, occurs when a cache uses the agent-driven negotiation information provided by the origin server
    2842          in order to provide server-driven negotiation for subsequent requests.
    2843       </p>
    2844       <h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a>&nbsp;<a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h2>
    2845       <p id="rfc.section.12.1.p.1">If the selection of the best representation for a response is made by an algorithm located at the server, it is called server-driven
    2846          negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g.
    2847          language, content-coding, etc.) and the contents of particular header fields in the request message or on other information
    2848          pertaining to the request (such as the network address of the client).
    2849       </p>
    2850       <p id="rfc.section.12.1.p.2">Server-driven negotiation is advantageous when the algorithm for selecting from among the available representations is difficult