Ignore:
Timestamp:
14/06/14 11:20:37 (7 years ago)
Author:
julian.reschke@…
Message:

update to latest version of rfc2629.xslt, regen all HTML

File:
1 edited

Legend:

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

    <
    r717 r2726  
    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>HTTP/1.1, part 2: Message Semantics</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 {
     
    3334  margin-left: 2em;
    3435}
    35 dd {
    36   margin-right: 2em;
    37 }
    3836dl {
    3937  margin-left: 2em;
    4038}
    41 
    42 dl.empty dd {
     39ul.empty {
     40  list-style-type: none;
     41}
     42ul.empty li {
    4343  margin-top: .5em;
    4444}
     
    5050}
    5151h1 {
    52   font-size: 14pt;
     52  font-size: 130%;
    5353  line-height: 21pt;
    5454  page-break-after: avoid;
     
    5757  page-break-before: always;
    5858}
    59 h1 a {
    60   color: #333333;
    61 }
    6259h2 {
    63   font-size: 12pt;
     60  font-size: 120%;
    6461  line-height: 15pt;
    6562  page-break-after: avoid;
    6663}
    67 h3, h4, h5, h6 {
    68   font-size: 10pt;
     64h3 {
     65  font-size: 110%;
    6966  page-break-after: avoid;
    7067}
    71 h2 a, h3 a, h4 a, h5 a, h6 a {
     68h4, h5, h6 {
     69  page-break-after: avoid;
     70}
     71h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
    7272  color: black;
    7373}
     
    7777li {
    7878  margin-left: 2em;
    79   margin-right: 2em;
    8079}
    8180ol {
    8281  margin-left: 2em;
    83   margin-right: 2em;
     82}
     83ol.la {
     84  list-style-type: lower-alpha;
     85}
     86ol.ua {
     87  list-style-type: upper-alpha;
    8488}
    8589ol p {
     
    8892p {
    8993  margin-left: 2em;
    90   margin-right: 2em;
    9194}
    9295pre {
     
    9497  background-color: lightyellow;
    9598  padding: .25em;
     99  page-break-inside: avoid;
    96100}
    97101pre.text2 {
     
    122126table.tt {
    123127  vertical-align: top;
     128  border-color: gray;
     129}
     130table.tt th {
     131  border-color: gray;
     132}
     133table.tt td {
     134  border-color: gray;
     135}
     136table.all {
     137  border-style: solid;
     138  border-width: 2px;
    124139}
    125140table.full {
    126   border-style: outset;
    127   border-width: 1px;
    128 }
    129 table.headers {
    130   border-style: outset;
    131   border-width: 1px;
     141  border-style: solid;
     142  border-width: 2px;
    132143}
    133144table.tt td {
    134145  vertical-align: top;
    135146}
     147table.all td {
     148  border-style: solid;
     149  border-width: 1px;
     150}
    136151table.full td {
    137   border-style: inset;
     152  border-style: none solid;
    138153  border-width: 1px;
    139154}
     
    141156  vertical-align: top;
    142157}
     158table.all th {
     159  border-style: solid;
     160  border-width: 1px;
     161}
    143162table.full th {
    144   border-style: inset;
    145   border-width: 1px;
     163  border-style: solid;
     164  border-width: 1px 1px 2px 1px;
    146165}
    147166table.headers th {
    148   border-style: none none inset none;
    149   border-width: 1px;
     167  border-style: none none solid none;
     168  border-width: 2px;
    150169}
    151170table.left {
     
    162181  caption-side: bottom;
    163182  font-weight: bold;
    164   font-size: 9pt;
     183  font-size: 10pt;
    165184  margin-top: .5em;
    166185}
    167186
    168187table.header {
     188  border-spacing: 1px;
    169189  width: 95%;
    170   font-size: 10pt;
     190  font-size: 11pt;
    171191  color: white;
    172192}
     
    176196td.topnowrap {
    177197  vertical-align: top;
    178   white-space: nowrap; 
    179 }
    180 td.header {
     198  white-space: nowrap;
     199}
     200table.header td {
    181201  background-color: gray;
    182202  width: 50%;
    183203}
    184 td.header a {
     204table.header a {
    185205  color: white;
    186206}
     
    193213  display:table-header-group;
    194214}
    195 ul.toc {
     215ul.toc, ul.toc ul {
    196216  list-style: none;
    197217  margin-left: 1.5em;
    198   margin-right: 0em;
    199218  padding-left: 0em;
    200219}
    201 li.tocline0 {
     220ul.toc li {
    202221  line-height: 150%;
    203222  font-weight: bold;
     223  margin-left: 0em;
     224}
     225ul.toc li li {
     226  line-height: normal;
     227  font-weight: normal;
    204228  font-size: 10pt;
    205229  margin-left: 0em;
    206   margin-right: 0em;
    207 }
    208 li.tocline1 {
    209   line-height: normal;
    210   font-weight: normal;
    211   font-size: 9pt;
    212   margin-left: 0em;
    213   margin-right: 0em;
    214 }
    215 li.tocline2 {
     230}
     231li.excluded {
    216232  font-size: 0pt;
    217233}
     
    219235  margin-left: 0em;
    220236}
    221 ul.ind {
     237.title, .filename, h1, h2, h3, h4 {
     238  font-family: candara, helvetica, arial, sans-serif;
     239}
     240samp, tt, code, pre {
     241  font: consolas, monospace;
     242}
     243ul.ind, ul.ind ul {
    222244  list-style: none;
    223245  margin-left: 1.5em;
    224   margin-right: 0em;
    225246  padding-left: 0em;
    226247  page-break-before: avoid;
    227248}
    228 li.indline0 {
     249ul.ind li {
    229250  font-weight: bold;
    230251  line-height: 200%;
    231252  margin-left: 0em;
    232   margin-right: 0em;
    233 }
    234 li.indline1 {
     253}
     254ul.ind li li {
    235255  font-weight: normal;
    236256  line-height: 150%;
    237257  margin-left: 0em;
    238   margin-right: 0em;
    239258}
    240259.avoidbreak {
     
    260279  font-weight: bold;
    261280  text-align: center;
    262   font-size: 9pt;
     281  font-size: 10pt;
    263282}
    264283.filename {
    265284  color: #333333;
     285  font-size: 75%;
    266286  font-weight: bold;
    267   font-size: 12pt;
    268287  line-height: 21pt;
    269288  text-align: center;
     
    272291  font-weight: bold;
    273292}
    274 .hidden {
    275   display: none;
    276 }
    277293.left {
    278294  text-align: left;
     
    282298}
    283299.title {
    284   color: #990000;
    285   font-size: 18pt;
     300  color: green;
     301  font-size: 150%;
    286302  line-height: 18pt;
    287303  font-weight: bold;
     
    289305  margin-top: 36pt;
    290306}
    291 .vcardline {
    292   display: block;
    293 }
    294307.warning {
    295   font-size: 14pt;
     308  font-size: 130%;
    296309  background-color: yellow;
    297310}
     
    302315    display: none;
    303316  }
    304  
     317
    305318  a {
    306319    color: black;
     
    317330    background-color: white;
    318331    vertical-align: top;
    319     font-size: 12pt;
     332    font-size: 110%;
    320333  }
    321334
    322   ul.toc a::after {
     335  ul.toc a:nth-child(2)::after {
    323336    content: leader('.') target-counter(attr(href), page);
    324337  }
    325  
    326   a.iref {
     338
     339  ul.ind li li a {
    327340    content: target-counter(attr(href), page);
    328341  }
    329  
     342
    330343  .print2col {
    331344    column-count: 2;
     
    337350@page {
    338351  @top-left {
    339        content: "INTERNET DRAFT";
    340   } 
     352       content: "Internet-Draft";
     353  }
    341354  @top-right {
    342        content: "October 2009"; 
    343   } 
     355       content: "October 2009";
     356  }
    344357  @top-center {
    345        content: "HTTP/1.1, Part 2"; 
    346   } 
     358       content: "HTTP/1.1, Part 2";
     359  }
    347360  @bottom-left {
    348        content: "Fielding, et al."; 
    349   } 
     361       content: "Fielding, et al.";
     362  }
    350363  @bottom-center {
    351        content: "Standards Track";
    352   } 
     364       content: "Expires April 29, 2010";
     365  }
    353366  @bottom-right {
    354        content: "[Page " counter(page) "]"; 
    355   } 
    356 }
    357 
    358 @page:first { 
     367       content: "[Page " counter(page) "]";
     368  }
     369}
     370
     371@page:first {
    359372    @top-left {
    360373      content: normal;
     
    369382</style><link rel="Contents" href="#rfc.toc">
    370383      <link rel="Author" href="#rfc.authors">
    371       <link rel="Copyright" href="#rfc.copyright">
     384      <link rel="Copyright" href="#rfc.copyrightnotice">
    372385      <link rel="Index" href="#rfc.index">
    373386      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
     
    387400      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    388401      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    389       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.477, 2009-10-09 21:33:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    390       <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    391       <meta name="DC.Creator" content="Fielding, R.">
    392       <meta name="DC.Creator" content="Gettys, J.">
    393       <meta name="DC.Creator" content="Mogul, J.">
    394       <meta name="DC.Creator" content="Frystyk, H.">
    395       <meta name="DC.Creator" content="Masinter, L.">
    396       <meta name="DC.Creator" content="Leach, P.">
    397       <meta name="DC.Creator" content="Berners-Lee, T.">
    398       <meta name="DC.Creator" content="Lafon, Y.">
    399       <meta name="DC.Creator" content="Reschke, J. F.">
    400       <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-08">
    401       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-10-26">
    402       <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    403       <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields.">
     402      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     403      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     404      <meta name="dct.creator" content="Fielding, R.">
     405      <meta name="dct.creator" content="Gettys, J.">
     406      <meta name="dct.creator" content="Mogul, J.">
     407      <meta name="dct.creator" content="Frystyk, H.">
     408      <meta name="dct.creator" content="Masinter, L.">
     409      <meta name="dct.creator" content="Leach, P.">
     410      <meta name="dct.creator" content="Berners-Lee, T.">
     411      <meta name="dct.creator" content="Lafon, Y.">
     412      <meta name="dct.creator" content="Reschke, J. F.">
     413      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-08">
     414      <meta name="dct.issued" scheme="ISO8601" content="2009-10-26">
     415      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     416      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields.">
    404417      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields.">
    405418   </head>
    406419   <body>
    407       <table class="header" border="0" cellpadding="1" cellspacing="1">
    408          <tr>
    409             <td class="header left">HTTPbis Working Group</td>
    410             <td class="header right">R. Fielding, Editor</td>
    411          </tr>
    412          <tr>
    413             <td class="header left">Internet Draft</td>
    414             <td class="header right">Day Software</td>
    415          </tr>
    416          <tr>
    417             <td class="header left">
    418                &lt;draft-ietf-httpbis-p2-semantics-08&gt;
    419                
    420             </td>
    421             <td class="header right">J. Gettys</td>
    422          </tr>
    423          <tr>
    424             <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    425             </td>
    426             <td class="header right">One Laptop per Child</td>
    427          </tr>
    428          <tr>
    429             <td class="header left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved)
    430             </td>
    431             <td class="header right">J. Mogul</td>
    432          </tr>
    433          <tr>
    434             <td class="header left">Intended status: Standards Track</td>
    435             <td class="header right">HP</td>
    436          </tr>
    437          <tr>
    438             <td class="header left">Expires: April 29, 2010</td>
    439             <td class="header right">H. Frystyk</td>
    440          </tr>
    441          <tr>
    442             <td class="header left"></td>
    443             <td class="header right">Microsoft</td>
    444          </tr>
    445          <tr>
    446             <td class="header left"></td>
    447             <td class="header right">L. Masinter</td>
    448          </tr>
    449          <tr>
    450             <td class="header left"></td>
    451             <td class="header right">Adobe Systems</td>
    452          </tr>
    453          <tr>
    454             <td class="header left"></td>
    455             <td class="header right">P. Leach</td>
    456          </tr>
    457          <tr>
    458             <td class="header left"></td>
    459             <td class="header right">Microsoft</td>
    460          </tr>
    461          <tr>
    462             <td class="header left"></td>
    463             <td class="header right">T. Berners-Lee</td>
    464          </tr>
    465          <tr>
    466             <td class="header left"></td>
    467             <td class="header right">W3C/MIT</td>
    468          </tr>
    469          <tr>
    470             <td class="header left"></td>
    471             <td class="header right">Y. Lafon, Editor</td>
    472          </tr>
    473          <tr>
    474             <td class="header left"></td>
    475             <td class="header right">W3C</td>
    476          </tr>
    477          <tr>
    478             <td class="header left"></td>
    479             <td class="header right">J. F. Reschke, Editor</td>
    480          </tr>
    481          <tr>
    482             <td class="header left"></td>
    483             <td class="header right">greenbytes</td>
    484          </tr>
    485          <tr>
    486             <td class="header left"></td>
    487             <td class="header right">October 26, 2009</td>
    488          </tr>
     420      <table class="header">
     421         <tbody>
     422            <tr>
     423               <td class="left">HTTPbis Working Group</td>
     424               <td class="right">R. Fielding, Editor</td>
     425            </tr>
     426            <tr>
     427               <td class="left">Internet-Draft</td>
     428               <td class="right">Day Software</td>
     429            </tr>
     430            <tr>
     431               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     432               </td>
     433               <td class="right">J. Gettys</td>
     434            </tr>
     435            <tr>
     436               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2817">2817</a> (if approved)
     437               </td>
     438               <td class="right">One Laptop per Child</td>
     439            </tr>
     440            <tr>
     441               <td class="left">Intended status: Standards Track</td>
     442               <td class="right">J. Mogul</td>
     443            </tr>
     444            <tr>
     445               <td class="left">Expires: April 29, 2010</td>
     446               <td class="right">HP</td>
     447            </tr>
     448            <tr>
     449               <td class="left"></td>
     450               <td class="right">H. Frystyk</td>
     451            </tr>
     452            <tr>
     453               <td class="left"></td>
     454               <td class="right">Microsoft</td>
     455            </tr>
     456            <tr>
     457               <td class="left"></td>
     458               <td class="right">L. Masinter</td>
     459            </tr>
     460            <tr>
     461               <td class="left"></td>
     462               <td class="right">Adobe Systems</td>
     463            </tr>
     464            <tr>
     465               <td class="left"></td>
     466               <td class="right">P. Leach</td>
     467            </tr>
     468            <tr>
     469               <td class="left"></td>
     470               <td class="right">Microsoft</td>
     471            </tr>
     472            <tr>
     473               <td class="left"></td>
     474               <td class="right">T. Berners-Lee</td>
     475            </tr>
     476            <tr>
     477               <td class="left"></td>
     478               <td class="right">W3C/MIT</td>
     479            </tr>
     480            <tr>
     481               <td class="left"></td>
     482               <td class="right">Y. Lafon, Editor</td>
     483            </tr>
     484            <tr>
     485               <td class="left"></td>
     486               <td class="right">W3C</td>
     487            </tr>
     488            <tr>
     489               <td class="left"></td>
     490               <td class="right">J. Reschke, Editor</td>
     491            </tr>
     492            <tr>
     493               <td class="left"></td>
     494               <td class="right">greenbytes</td>
     495            </tr>
     496            <tr>
     497               <td class="left"></td>
     498               <td class="right">October 26, 2009</td>
     499            </tr>
     500         </tbody>
    489501      </table>
    490502      <p class="title">HTTP/1.1, part 2: Message Semantics<br><span class="filename">draft-ietf-httpbis-p2-semantics-08</span></p>
    491       <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
    492       <p>This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain
    493          material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s)
    494          controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of
    495          such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the
    496          copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of
    497          it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it
    498          into languages other than English.
    499       </p>
    500       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
    501          that other groups may also distribute working documents as Internet-Drafts.
    502       </p>
    503       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    504          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    505          in progress”.
    506       </p>
    507       <p>The list of current Internet-Drafts can be accessed at &lt;<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>&gt;.
    508       </p>
    509       <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    510       </p>
    511       <p>This Internet-Draft will expire in April 29, 2010.</p>
    512       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    513       <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    514       <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date
    515          of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
    516       </p>
    517       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
     503      <div id="rfc.status">
     504         <h1><a href="#rfc.status">Status of this Memo</a></h1>
     505         <p>This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain
     506            material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s)
     507            controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of
     508            such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the
     509            copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of
     510            it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it
     511            into languages other than English.
     512         </p>
     513         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
     514            that other groups may also distribute working documents as Internet-Drafts.
     515         </p>
     516         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     517            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     518            in progress”.
     519         </p>
     520         <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>.
     521         </p>
     522         <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>.
     523         </p>
     524         <p>This Internet-Draft will expire on April 29, 2010.</p>
     525      </div>
     526      <div id="rfc.copyrightnotice">
     527         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     528         <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     529         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date
     530            of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
     531         </p>
     532      </div>
     533      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    518534      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    519535         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the
     
    521537         2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and
    522538         response-header fields.
    523       </p> 
    524       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
     539      </p>
     540      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    525541      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    526542         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    527       </p> 
     543      </p>
    528544      <p>The changes in this draft are summarized in <a href="#changes.since.07" title="Since draft-ietf-httpbis-p2-semantics-07">Appendix&nbsp;C.9</a>.
    529       </p> 
     545      </p>
    530546      <hr class="noprint">
    531547      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    532548      <ul class="toc">
    533          <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
    534                <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    535                <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul class="toc">
    536                      <li class="tocline1">1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    537                      <li class="tocline1">1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     549         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     550               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     551               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     552                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     553                     <li><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    538554                  </ul>
    539555               </li>
    540556            </ul>
    541557         </li>
    542          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#method">Method</a><ul class="toc">
    543                <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a></li>
     558         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#method">Method</a><ul>
     559               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a></li>
    544560            </ul>
    545561         </li>
    546          <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
    547          <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a><ul class="toc">
    548                <li class="tocline1">4.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a></li>
     562         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
     563         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a><ul>
     564               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a></li>
    549565            </ul>
    550566         </li>
    551          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
    552          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#entity">Entity</a><ul class="toc">
    553                <li class="tocline1">6.1&nbsp;&nbsp;&nbsp;<a href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></li>
     567         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
     568         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#entity">Entity</a><ul>
     569               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></li>
    554570            </ul>
    555571         </li>
    556          <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul class="toc">
    557                <li class="tocline1">7.1&nbsp;&nbsp;&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul class="toc">
    558                      <li class="tocline1">7.1.1&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
    559                      <li class="tocline1">7.1.2&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
     572         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
     573               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul>
     574                     <li><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
     575                     <li><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
    560576                  </ul>
    561577               </li>
    562                <li class="tocline1">7.2&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
    563                <li class="tocline1">7.3&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
    564                <li class="tocline1">7.4&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
    565                <li class="tocline1">7.5&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
    566                <li class="tocline1">7.6&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
    567                <li class="tocline1">7.7&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
    568                <li class="tocline1">7.8&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
    569                <li class="tocline1">7.9&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
     578               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
     579               <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
     580               <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
     581               <li><a href="#rfc.section.7.5">7.5</a>&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
     582               <li><a href="#rfc.section.7.6">7.6</a>&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
     583               <li><a href="#rfc.section.7.7">7.7</a>&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
     584               <li><a href="#rfc.section.7.8">7.8</a>&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
     585               <li><a href="#rfc.section.7.9">7.9</a>&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
    570586            </ul>
    571587         </li>
    572          <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#status.codes">Status Code Definitions</a><ul class="toc">
    573                <li class="tocline1">8.1&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul class="toc">
    574                      <li class="tocline1">8.1.1&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
    575                      <li class="tocline1">8.1.2&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
     588         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Status Code Definitions</a><ul>
     589               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
     590                     <li><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
     591                     <li><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
    576592                  </ul>
    577593               </li>
    578                <li class="tocline1">8.2&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul class="toc">
    579                      <li class="tocline1">8.2.1&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
    580                      <li class="tocline1">8.2.2&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
    581                      <li class="tocline1">8.2.3&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
    582                      <li class="tocline1">8.2.4&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
    583                      <li class="tocline1">8.2.5&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
    584                      <li class="tocline1">8.2.6&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
    585                      <li class="tocline1">8.2.7&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
     594               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
     595                     <li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
     596                     <li><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
     597                     <li><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
     598                     <li><a href="#rfc.section.8.2.4">8.2.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
     599                     <li><a href="#rfc.section.8.2.5">8.2.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
     600                     <li><a href="#rfc.section.8.2.6">8.2.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
     601                     <li><a href="#rfc.section.8.2.7">8.2.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    586602                  </ul>
    587603               </li>
    588                <li class="tocline1">8.3&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul class="toc">
    589                      <li class="tocline1">8.3.1&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
    590                      <li class="tocline1">8.3.2&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
    591                      <li class="tocline1">8.3.3&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
    592                      <li class="tocline1">8.3.4&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
    593                      <li class="tocline1">8.3.5&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
    594                      <li class="tocline1">8.3.6&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
    595                      <li class="tocline1">8.3.7&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
    596                      <li class="tocline1">8.3.8&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
     604               <li><a href="#rfc.section.8.3">8.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
     605                     <li><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
     606                     <li><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
     607                     <li><a href="#rfc.section.8.3.3">8.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
     608                     <li><a href="#rfc.section.8.3.4">8.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
     609                     <li><a href="#rfc.section.8.3.5">8.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
     610                     <li><a href="#rfc.section.8.3.6">8.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
     611                     <li><a href="#rfc.section.8.3.7">8.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
     612                     <li><a href="#rfc.section.8.3.8">8.3.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
    597613                  </ul>
    598614               </li>
    599                <li class="tocline1">8.4&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul class="toc">
    600                      <li class="tocline1">8.4.1&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
    601                      <li class="tocline1">8.4.2&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
    602                      <li class="tocline1">8.4.3&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
    603                      <li class="tocline1">8.4.4&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
    604                      <li class="tocline1">8.4.5&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
    605                      <li class="tocline1">8.4.6&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
    606                      <li class="tocline1">8.4.7&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
    607                      <li class="tocline1">8.4.8&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
    608                      <li class="tocline1">8.4.9&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
    609                      <li class="tocline1">8.4.10&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
    610                      <li class="tocline1">8.4.11&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
    611                      <li class="tocline1">8.4.12&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
    612                      <li class="tocline1">8.4.13&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
    613                      <li class="tocline1">8.4.14&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Entity Too Large</a></li>
    614                      <li class="tocline1">8.4.15&nbsp;&nbsp;&nbsp;<a href="#status.414">414 URI Too Long</a></li>
    615                      <li class="tocline1">8.4.16&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
    616                      <li class="tocline1">8.4.17&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
    617                      <li class="tocline1">8.4.18&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
     615               <li><a href="#rfc.section.8.4">8.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
     616                     <li><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
     617                     <li><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
     618                     <li><a href="#rfc.section.8.4.3">8.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
     619                     <li><a href="#rfc.section.8.4.4">8.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
     620                     <li><a href="#rfc.section.8.4.5">8.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
     621                     <li><a href="#rfc.section.8.4.6">8.4.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
     622                     <li><a href="#rfc.section.8.4.7">8.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
     623                     <li><a href="#rfc.section.8.4.8">8.4.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
     624                     <li><a href="#rfc.section.8.4.9">8.4.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
     625                     <li><a href="#rfc.section.8.4.10">8.4.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
     626                     <li><a href="#rfc.section.8.4.11">8.4.11</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
     627                     <li><a href="#rfc.section.8.4.12">8.4.12</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
     628                     <li><a href="#rfc.section.8.4.13">8.4.13</a>&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
     629                     <li><a href="#rfc.section.8.4.14">8.4.14</a>&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Entity Too Large</a></li>
     630                     <li><a href="#rfc.section.8.4.15">8.4.15</a>&nbsp;&nbsp;&nbsp;<a href="#status.414">414 URI Too Long</a></li>
     631                     <li><a href="#rfc.section.8.4.16">8.4.16</a>&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
     632                     <li><a href="#rfc.section.8.4.17">8.4.17</a>&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
     633                     <li><a href="#rfc.section.8.4.18">8.4.18</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
    618634                  </ul>
    619635               </li>
    620                <li class="tocline1">8.5&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul class="toc">
    621                      <li class="tocline1">8.5.1&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
    622                      <li class="tocline1">8.5.2&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
    623                      <li class="tocline1">8.5.3&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
    624                      <li class="tocline1">8.5.4&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
    625                      <li class="tocline1">8.5.5&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
    626                      <li class="tocline1">8.5.6&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
     636               <li><a href="#rfc.section.8.5">8.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
     637                     <li><a href="#rfc.section.8.5.1">8.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
     638                     <li><a href="#rfc.section.8.5.2">8.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
     639                     <li><a href="#rfc.section.8.5.3">8.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
     640                     <li><a href="#rfc.section.8.5.4">8.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
     641                     <li><a href="#rfc.section.8.5.5">8.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
     642                     <li><a href="#rfc.section.8.5.6">8.5.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
    627643                  </ul>
    628644               </li>
    629645            </ul>
    630646         </li>
    631          <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
    632                <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
    633                <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
    634                <li class="tocline1">9.3&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
    635                <li class="tocline1">9.4&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
    636                <li class="tocline1">9.5&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
    637                <li class="tocline1">9.6&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
    638                <li class="tocline1">9.7&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
    639                <li class="tocline1">9.8&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
    640                <li class="tocline1">9.9&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     647         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     648               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
     649               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
     650               <li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
     651               <li><a href="#rfc.section.9.4">9.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
     652               <li><a href="#rfc.section.9.5">9.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
     653               <li><a href="#rfc.section.9.6">9.6</a>&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
     654               <li><a href="#rfc.section.9.7">9.7</a>&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
     655               <li><a href="#rfc.section.9.8">9.8</a>&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
     656               <li><a href="#rfc.section.9.9">9.9</a>&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
    641657            </ul>
    642658         </li>
    643          <li class="tocline0">10.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
    644                <li class="tocline1">10.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
    645                <li class="tocline1">10.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
    646                <li class="tocline1">10.3&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
     659         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     660               <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
     661               <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
     662               <li><a href="#rfc.section.10.3">10.3</a>&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
    647663            </ul>
    648664         </li>
    649          <li class="tocline0">11.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul class="toc">
    650                <li class="tocline1">11.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
    651                <li class="tocline1">11.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
    652                <li class="tocline1">11.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing">Location Headers and Spoofing</a></li>
     665         <li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     666               <li><a href="#rfc.section.11.1">11.1</a>&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
     667               <li><a href="#rfc.section.11.2">11.2</a>&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
     668               <li><a href="#rfc.section.11.3">11.3</a>&nbsp;&nbsp;&nbsp;<a href="#location.spoofing">Location Headers and Spoofing</a></li>
    653669            </ul>
    654670         </li>
    655          <li class="tocline0">12.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    656          <li class="tocline0">13.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
    657                <li class="tocline1">13.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    658                <li class="tocline1">13.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     671         <li><a href="#rfc.section.12">12.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     672         <li><a href="#rfc.section.13">13.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     673               <li><a href="#rfc.section.13.1">13.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     674               <li><a href="#rfc.section.13.2">13.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    659675            </ul>
    660676         </li>
    661          <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
    662          <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">
    663                <li class="tocline1">A.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
    664                <li class="tocline1">A.2&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
     677         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
     678               <li><a href="#rfc.section.A.1">A.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
     679               <li><a href="#rfc.section.A.2">A.2</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    665680            </ul>
    666681         </li>
    667          <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    668          <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
    669                <li class="tocline1">C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
    670                <li class="tocline1">C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
    671                <li class="tocline1">C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p2-semantics-01</a></li>
    672                <li class="tocline1">C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
    673                <li class="tocline1">C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
    674                <li class="tocline1">C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
    675                <li class="tocline1">C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
    676                <li class="tocline1">C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li>
    677                <li class="tocline1">C.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li>
     682         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
     683         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
     684               <li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
     685               <li><a href="#rfc.section.C.2">C.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
     686               <li><a href="#rfc.section.C.3">C.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p2-semantics-01</a></li>
     687               <li><a href="#rfc.section.C.4">C.4</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
     688               <li><a href="#rfc.section.C.5">C.5</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
     689               <li><a href="#rfc.section.C.6">C.6</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
     690               <li><a href="#rfc.section.C.7">C.7</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
     691               <li><a href="#rfc.section.C.8">C.8</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li>
     692               <li><a href="#rfc.section.C.9">C.9</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li>
    678693            </ul>
    679694         </li>
    680          <li class="tocline0"><a href="#rfc.index">Index</a></li>
     695         <li><a href="#rfc.index">Index</a></li>
     696         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    681697      </ul>
    682       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    683       <p id="rfc.section.1.p.1">This document defines HTTP/1.1 request and response semantics. Each HTTP message, as defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, is in the form of either a request or a response. An HTTP server listens on a connection for HTTP requests and responds
    684          to each request, in the order received on that connection, with one or more HTTP response messages. This document defines
    685          the commonly agreed upon semantics of the HTTP uniform interface, the intentions defined by each request method, and the various
    686          response messages that might be expected as a result of applying that method for the requested resource.
    687       </p>
    688       <p id="rfc.section.1.p.2">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
    689          errata changes. The next draft will reorganize the sections to better reflect the content. In particular, the sections will
    690          be ordered according to the typical processing of an HTTP request message (after message parsing): resource mapping, general
    691          header fields, methods, request modifiers, response status, and resource metadata. The current mess reflects how widely dispersed
    692          these topics and associated requirements had become in <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    693       </p>
    694       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
    695       <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
    696          in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
    697       </p>
    698       <p id="rfc.section.1.1.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."
    699       </p>
    700       <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
    701       <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF, with the list rule expanded.
    702       </p>
    703       <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    704          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
    705          and WSP (whitespace).
    706       </p>
    707       <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
    708       <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
    709       </p>
    710       <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
     698      <div id="introduction">
     699         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     700         <p id="rfc.section.1.p.1">This document defines HTTP/1.1 request and response semantics. Each HTTP message, as defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, is in the form of either a request or a response. An HTTP server listens on a connection for HTTP requests and responds
     701            to each request, in the order received on that connection, with one or more HTTP response messages. This document defines
     702            the commonly agreed upon semantics of the HTTP uniform interface, the intentions defined by each request method, and the various
     703            response messages that might be expected as a result of applying that method for the requested resource.
     704         </p>
     705         <p id="rfc.section.1.p.2">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
     706            errata changes. The next draft will reorganize the sections to better reflect the content. In particular, the sections will
     707            be ordered according to the typical processing of an HTTP request message (after message parsing): resource mapping, general
     708            header fields, methods, request modifiers, response status, and resource metadata. The current mess reflects how widely dispersed
     709            these topics and associated requirements had become in <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     710         </p>
     711         <div id="intro.requirements">
     712            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     713            <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
     714               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
     715            </p>
     716            <p id="rfc.section.1.1.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."
     717            </p>
     718         </div>
     719         <div id="notation">
     720            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     721            <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF, with the list rule expanded.
     722            </p>
     723            <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="https://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     724               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
     725               and WSP (whitespace).
     726            </p>
     727            <div id="core.rules">
     728               <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a href="#core.rules">Core Rules</a></h3>
     729               <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
     730               </p>
     731               <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    711732  <a href="#core.rules" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    712733  <a href="#core.rules" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    713734  <a href="#core.rules" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    714735  <a href="#core.rules" class="smpl">obs-text</a>      = &lt;obs-text, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
    715 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
    716       <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
    717       <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt;
     736</pre></div>
     737            <div id="abnf.dependencies">
     738               <h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
     739               <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
     740               <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absolute-URI</a>  = &lt;absolute-URI, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt;
    718741  <a href="#abnf.dependencies" class="smpl">comment</a>       = &lt;comment, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a>&gt;
    719742  <a href="#abnf.dependencies" class="smpl">Host</a>          = &lt;Host, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.6</a>&gt;
     
    749772  <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a> =
    750773             &lt;WWW-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 3.4</a>&gt;
    751 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="method" href="#method">Method</a></h1>
    752       <p id="rfc.section.2.p.1">The Method token indicates the method to be performed on the resource identified by the request-target. The method is case-sensitive.</p>
    753       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  <a href="#method" class="smpl">Method</a>         = %x4F.50.54.49.4F.4E.53   ; "OPTIONS", <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;7.2</a>
     774</pre></div>
     775         </div>
     776      </div>
     777      <div id="method">
     778         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#method">Method</a></h1>
     779         <p id="rfc.section.2.p.1">The Method token indicates the method to be performed on the resource identified by the request-target. The method is case-sensitive.</p>
     780         <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  <a href="#method" class="smpl">Method</a>         = %x4F.50.54.49.4F.4E.53   ; "OPTIONS", <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;7.2</a>
    754781                 / %x47.45.54               ; "GET", <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;7.3</a>
    755782                 / %x48.45.41.44            ; "HEAD", <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;7.4</a>
     
    762789  <a href="#method" class="smpl">extension-method</a> = <a href="#core.rules" class="smpl">token</a>
    763790</pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;9.1</a>). The return code of the response always notifies the client whether a method is currently allowed on a resource, since the
    764          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
    765          resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
    766          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;7</a>.
    767       </p>
    768       <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
    769       <p id="rfc.section.2.1.p.1">The HTTP Method Registry defines the name space for the Method token in the Request line of an HTTP request.</p>
    770       <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    771       </p>
    772       <ul>
    773          <li>Method Name (see <a href="#method" title="Method">Section&nbsp;2</a>)
    774          </li>
    775          <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>)
    776          </li>
    777          <li>Pointer to specification text</li>
    778       </ul>
    779       <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    780       </p>
    781       <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
    782       </p>
    783       <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1>
    784       <p id="rfc.section.3.p.1">The request-header fields allow the client to pass additional information about the request, and about the client itself,
    785          to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language
    786          method invocation.
    787       </p>
    788       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#request.header.fields" class="smpl">request-header</a> = <a href="#abnf.dependencies" class="smpl">Accept</a>                   ; <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 5.1</a>
     791            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
     792            resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
     793            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;7</a>.
     794         </p>
     795         <div id="method.registry">
     796            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#method.registry">Method Registry</a></h2>
     797            <p id="rfc.section.2.1.p.1">The HTTP Method Registry defines the name space for the Method token in the Request line of an HTTP request.</p>
     798            <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     799            </p>
     800            <ul>
     801               <li>Method Name (see <a href="#method" title="Method">Section&nbsp;2</a>)
     802               </li>
     803               <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>)
     804               </li>
     805               <li>Pointer to specification text</li>
     806            </ul>
     807            <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     808            </p>
     809            <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
     810            </p>
     811         </div>
     812      </div>
     813      <div id="request.header.fields">
     814         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#request.header.fields">Request Header Fields</a></h1>
     815         <p id="rfc.section.3.p.1">The request-header fields allow the client to pass additional information about the request, and about the client itself,
     816            to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language
     817            method invocation.
     818         </p>
     819         <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#request.header.fields" class="smpl">request-header</a> = <a href="#abnf.dependencies" class="smpl">Accept</a>                   ; <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 5.1</a>
    789820                 / <a href="#abnf.dependencies" class="smpl">Accept-Charset</a>           ; <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 5.2</a>
    790821                 / <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a>          ; <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 5.3</a>
     
    806837                 / <a href="#header.user-agent" class="smpl">User-Agent</a>               ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;9.9</a>
    807838</pre><p id="rfc.section.3.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    808          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.
    809          Unrecognized header fields are treated as entity-header fields.
    810       </p>
    811       <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h1>
    812       <p id="rfc.section.4.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. The status
    813          codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;8</a>. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use
    814          by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.
    815       </p>
    816       <p id="rfc.section.4.p.2">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's,
    817          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.
    818       </p>
    819       <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    =
     839            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.
     840            Unrecognized header fields are treated as entity-header fields.
     841         </p>
     842      </div>
     843      <div id="status.code.and.reason.phrase">
     844         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h1>
     845         <p id="rfc.section.4.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. The status
     846            codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;8</a>. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use
     847            by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.
     848         </p>
     849         <p id="rfc.section.4.p.2">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's,
     850            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.
     851         </p>
     852         <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    =
    820853         "100"  ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;8.1.1</a>: Continue
    821854       / "101"  ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;8.1.2</a>: Switching Protocols
     
    863896  <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a>  = *( <a href="#notation" class="smpl">WSP</a> / <a href="#notation" class="smpl">VCHAR</a> / <a href="#core.rules" class="smpl">obs-text</a> )
    864897</pre><p id="rfc.section.4.p.4">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
    865          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
    866          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
    867          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
    868          which will explain the unusual status.
    869       </p>
    870       <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2>
    871       <p id="rfc.section.4.1.p.1">The HTTP Status Code Registry defines the name space for the Status-Code token in the Status line of an HTTP response.</p>
    872       <p id="rfc.section.4.1.p.2">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    873       </p>
    874       <p id="rfc.section.4.1.p.3">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
    875       </p>
    876       <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>
    877       <p id="rfc.section.5.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the
    878          Status-Line. These header fields give information about the server and about further access to the resource identified by
    879          the request-target.
    880       </p>
    881       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#response.header.fields" class="smpl">response-header</a> = <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a>           ; <a href="#Part5" id="rfc.xref.Part5.7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a>
     898            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
     899            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
     900            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
     901            which will explain the unusual status.
     902         </p>
     903         <div id="status.code.registry">
     904            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#status.code.registry">Status Code Registry</a></h2>
     905            <p id="rfc.section.4.1.p.1">The HTTP Status Code Registry defines the name space for the Status-Code token in the Status line of an HTTP response.</p>
     906            <p id="rfc.section.4.1.p.2">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     907            </p>
     908            <p id="rfc.section.4.1.p.3">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
     909            </p>
     910         </div>
     911      </div>
     912      <div id="response.header.fields">
     913         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#response.header.fields">Response Header Fields</a></h1>
     914         <p id="rfc.section.5.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the
     915            Status-Line. These header fields give information about the server and about further access to the resource identified by
     916            the request-target.
     917         </p>
     918         <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#response.header.fields" class="smpl">response-header</a> = <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a>           ; <a href="#Part5" id="rfc.xref.Part5.7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a>
    882919                  / <a href="#abnf.dependencies" class="smpl">Age</a>                     ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 3.1</a>
    883920                  / <a href="#header.allow" class="smpl">Allow</a>                   ; <a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;9.1</a>
     
    890927                  / <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a>        ; <a href="#Part7" id="rfc.xref.Part7.10"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 3.4</a>
    891928</pre><p id="rfc.section.5.p.3">Response-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    892          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
    893          fields. Unrecognized header fields are treated as entity-header fields.
    894       </p>
    895       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="entity" href="#entity">Entity</a></h1>
    896       <p id="rfc.section.6.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
    897          fields and an entity-body, although some responses will only include the entity-headers. HTTP entity-body and entity-header
    898          fields are defined in <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    899       </p>
    900       <p id="rfc.section.6.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
    901          safe and proper transfer of the message.
    902       </p>
    903       <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="identifying.response.associated.with.representation" href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></h2>
    904       <p id="rfc.section.6.1.p.1">It is sometimes necessary to determine the identity of the resource associated with a representation.</p>
    905       <p id="rfc.section.6.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p>
    906       <p id="rfc.section.6.1.p.3">In the common case, an HTTP response is a representation of the resource located at the request-URI. However, this is not
    907          always the case. To determine the URI of the resource a response is associated with, the following rules are used (first match
    908          winning):
    909       </p>
    910       <ol>
    911          <li>If the response status code is 200 or 203 and the request method was GET, the response is a representation of the resource
    912             at the request-URI.
    913          </li>
    914          <li>If the response status is 204, 206, or 304 and the request method was GET or HEAD, the response is a partial representation
    915             of the resource at the request-URI (see <a href="p6-cache.html#combining.headers" title="Combining Responses">Section 2.7</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    916          </li>
    917          <li>If the response has a Content-Location header, and that URI is the same as the request-URI <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: (see [ref])]</span>, the response is a representation of the resource at the request-URI.
    918          </li>
    919          <li>If the response has a Content-Location header, and that URI is not the same as the request-URI, the response asserts that
    920             it is a representation of the resource at the Content-Location URI (but it may not be).
    921          </li>
    922          <li>Otherwise, the response is a representation of an anonymous (i.e., unidentified) resource.</li>
    923       </ol>
    924       <p id="rfc.section.6.1.p.5"> <span class="comment" id="TODO-req-uri">[<a href="#TODO-req-uri" class="smpl">TODO-req-uri</a>: Note that 'request-URI' is used here; however, we need to come up with a term to denote "the URI that can be inferred from
    925             examining the request-target and the Host header." (see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;). Also, the comparison function is going to have to be defined somewhere, because we already need to compare URIs for things
    926             like cache invalidation.]</span>
    927       </p>
    928       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h1>
    929       <p id="rfc.section.7.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
    930          to share the same semantics for separately extended clients and servers.
    931       </p>
    932       <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2>
    933       <div id="rfc.iref.s.1"></div>
    934       <h3 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
    935       <p id="rfc.section.7.1.1.p.1">Implementors should be aware that the software represents the user in their interactions over the Internet, and should be
    936          careful to allow the user to be aware of any actions they might take which may have an unexpected significance to themselves
    937          or others.
    938       </p>
    939       <p id="rfc.section.7.1.1.p.2">In particular, the convention has been established that the GET, HEAD, OPTIONS, and TRACE methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "<dfn id="safe">safe</dfn>". This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is
    940          made aware of the fact that a possibly unsafe action is being requested.
    941       </p>
    942       <p id="rfc.section.7.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;
    943          in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the
    944          side-effects, so therefore cannot be held accountable for them.
    945       </p>
    946       <div id="rfc.iref.i.1"></div>
    947       <h3 id="rfc.section.7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
    948       <p id="rfc.section.7.1.2.p.1">Methods can also have the property of "idempotence" in that, aside from error or expiration issues, the intended effect of
    949          multiple identical requests is the same as for a single request. The methods PUT, DELETE, and all safe methods are idempotent.
    950          It is important to note that idempotence refers only to changes requested by the client: a server is free to change its state
    951          due to multiple requests for the purpose of tracking those requests, versioning of results, etc.
    952       </p>
    953       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2>
    954       <div id="rfc.iref.o.1"></div>
    955       <div id="rfc.iref.m.1"></div>
    956       <p id="rfc.section.7.2.p.1">The OPTIONS method represents a request for information about the communication options available on the request/response
    957          chain identified by the request-target. This method allows the client to determine the options and/or requirements associated
    958          with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
    959       </p>
    960       <p id="rfc.section.7.2.p.2">Responses to this method are not cacheable.</p>
    961       <p id="rfc.section.7.2.p.3">If the OPTIONS request includes an entity-body (as indicated by the presence of Content-Length or Transfer-Encoding), then
    962          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
    963          to HTTP might use the OPTIONS body to make more detailed queries on the server.
    964       </p>
    965       <p id="rfc.section.7.2.p.4">If the request-target is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than
    966          to a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
    967          as a "ping" or "no-op" type of method; it does nothing beyond allowing the client to test the capabilities of the server.
    968          For example, this can be used to test a proxy for HTTP/1.1 compliance (or lack thereof).
    969       </p>
    970       <p id="rfc.section.7.2.p.5">If the request-target is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
    971          with that resource.
    972       </p>
    973       <p id="rfc.section.7.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.,
    974          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,
    975          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".
    976       </p>
    977       <p id="rfc.section.7.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 absolute-URI for which
    978          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
    979          request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
    980       </p>
    981       <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="GET" href="#GET">GET</a></h2>
    982       <div id="rfc.iref.g.8"></div>
    983       <div id="rfc.iref.m.2"></div>
    984       <p id="rfc.section.7.3.p.1">The GET method means retrieve whatever information (in the form of an entity) is identified by the request-target. If the
    985          request-target refers to a data-producing process, it is the produced data which shall be returned as the entity in the response
    986          and not the source text of the process, unless that text happens to be the output of the process.
    987       </p>
    988       <p id="rfc.section.7.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,
    989          If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the entity be transferred only under
    990          the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce unnecessary
    991          network usage by allowing cached entities to be refreshed without requiring multiple requests or transferring data already
    992          held by the client.
    993       </p>
    994       <p id="rfc.section.7.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
    995          GET requests that only part of the entity be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed
    996          without transferring data already held by the client.
    997       </p>
    998       <p id="rfc.section.7.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="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
    999       </p>
    1000       <p id="rfc.section.7.3.p.5">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations when used for forms.
    1001       </p>
    1002       <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h2>
    1003       <div id="rfc.iref.h.1"></div>
    1004       <div id="rfc.iref.m.3"></div>
    1005       <p id="rfc.section.7.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
    1006          the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext
    1007          links for validity, accessibility, and recent modification.
    1008       </p>
    1009       <p id="rfc.section.7.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
    1010          from the current entity (as would be indicated by a change in Content-Length, Content-MD5, ETag or Last-Modified), then the
    1011          cache <em class="bcp14">MUST</em> treat the cache entry as stale.
    1012       </p>
    1013       <div id="rfc.iref.p.1"></div>
    1014       <div id="rfc.iref.m.4"></div>
    1015       <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="POST" href="#POST">POST</a></h2>
    1016       <p id="rfc.section.7.5.p.1">The POST method is used to request that the origin server accept the entity enclosed in the request as data to be processed
    1017          by the resource identified by the request-target in the Request-Line. POST is designed to allow a uniform method to cover
    1018          the following functions:
    1019       </p>
    1020       <ul>
    1021          <li>Annotation of existing resources;</li>
    1022          <li>Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;</li>
    1023          <li>Providing a block of data, such as the result of submitting a form, to a data-handling process;</li>
    1024          <li>Extending a database through an append operation.</li>
    1025       </ul>
    1026       <p id="rfc.section.7.5.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the request-target.</p>
    1027       <p id="rfc.section.7.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
    1028          200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity
    1029          that describes the result.
    1030       </p>
    1031       <p id="rfc.section.7.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
    1032          header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;9.4</a>).
    1033       </p>
    1034       <p id="rfc.section.7.5.p.5">Responses to this method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields.
    1035          However, the 303 (See Other) response can be used to direct the user agent to retrieve a cacheable resource.
    1036       </p>
    1037       <div id="rfc.iref.p.2"></div>
    1038       <div id="rfc.iref.m.5"></div>
    1039       <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h2>
    1040       <p id="rfc.section.7.6.p.1">The PUT method requests that the enclosed entity be stored at the supplied request-target. If the request-target refers to
    1041          an 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-target does not point to an existing
    1042          resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create
    1043          the resource with that URI. If a new resource is created at the request-target, 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
    1044          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-target,
    1045          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-* headers (headers starting with the prefix 'Content-') that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
    1046       </p>
    1047       <p id="rfc.section.7.6.p.2">If the request passes through a cache and the request-target 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.
    1048       </p>
    1049       <p id="rfc.section.7.6.p.3">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the request-target.
    1050          The URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting
    1051          process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request
    1052          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,
    1053          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.
    1054       </p>
    1055       <p id="rfc.section.7.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
    1056          is separate from the URI identifying each particular version. In this case, a PUT request on a general URI might result in
    1057          several other URIs being defined by the origin server.
    1058       </p>
    1059       <p id="rfc.section.7.6.p.5">HTTP/1.1 does not define how a PUT method affects the state of an origin server.</p>
    1060       <p id="rfc.section.7.6.p.6">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.
    1061       </p>
    1062       <div id="rfc.iref.d.1"></div>
    1063       <div id="rfc.iref.m.6"></div>
    1064       <h2 id="rfc.section.7.7"><a href="#rfc.section.7.7">7.7</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h2>
    1065       <p id="rfc.section.7.7.p.1">The DELETE method requests that the origin server delete the resource identified by the request-target. 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
    1066          has been carried out, even if the status code returned from the origin server indicates that the action has been completed
    1067          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
    1068          location.
    1069       </p>
    1070       <p id="rfc.section.7.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,
    1071          or 204 (No Content) if the action has been enacted but the response does not include an entity.
    1072       </p>
    1073       <p id="rfc.section.7.7.p.3">If the request passes through a cache and the request-target 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.
    1074       </p>
    1075       <h2 id="rfc.section.7.8"><a href="#rfc.section.7.8">7.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h2>
    1076       <div id="rfc.iref.t.1"></div>
    1077       <div id="rfc.iref.m.7"></div>
    1078       <p id="rfc.section.7.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
    1079          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
    1080          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;9.5</a>). A TRACE request <em class="bcp14">MUST NOT</em> include an entity.
    1081       </p>
    1082       <p id="rfc.section.7.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
    1083          or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the
    1084          client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an
    1085          infinite loop.
    1086       </p>
    1087       <p id="rfc.section.7.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" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 10.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Responses to this method <em class="bcp14">MUST NOT</em> be cached.
    1088       </p>
    1089       <div id="rfc.iref.c.1"></div>
    1090       <div id="rfc.iref.m.8"></div>
    1091       <h2 id="rfc.section.7.9"><a href="#rfc.section.7.9">7.9</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h2>
    1092       <p id="rfc.section.7.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.
    1093          SSL tunneling <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>).
    1094       </p>
    1095       <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="status.codes" href="#status.codes">Status Code Definitions</a></h1>
    1096       <p id="rfc.section.8.p.1">Each Status-Code is described below, including any metainformation required in the response.</p>
    1097       <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
    1098       <p id="rfc.section.8.1.p.1">This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is
    1099          terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any
    1100          1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions.
    1101       </p>
    1102       <p id="rfc.section.8.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
    1103          (Continue) status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
    1104       </p>
    1105       <p id="rfc.section.8.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
    1106          requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards
    1107          a request, then it need not forward the corresponding 100 (Continue) response(s).)
    1108       </p>
    1109       <div id="rfc.iref.25"></div>
    1110       <div id="rfc.iref.s.2"></div>
    1111       <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
    1112       <p id="rfc.section.8.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
    1113          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
    1114          server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
    1115       </p>
    1116       <div id="rfc.iref.26"></div>
    1117       <div id="rfc.iref.s.3"></div>
    1118       <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    1119       <p id="rfc.section.8.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="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
    1120          by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    1121       </p>
    1122       <p id="rfc.section.8.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
    1123          older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
    1124          such features.
    1125       </p>
    1126       <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
    1127       <p id="rfc.section.8.2.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
    1128       <div id="rfc.iref.27"></div>
    1129       <div id="rfc.iref.s.4"></div>
    1130       <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
    1131       <p id="rfc.section.8.2.1.p.1">The request has succeeded. The information returned with the response is dependent on the method used in the request, for
    1132          example:
    1133       </p>
    1134       <dl>
    1135          <dt>GET</dt>
    1136          <dd>an entity corresponding to the requested resource is sent in the response;</dd>
    1137          <dt>HEAD</dt>
    1138          <dd>the entity-header fields corresponding to the requested resource are sent in the response without any message-body;</dd>
    1139          <dt>POST</dt>
    1140          <dd>an entity describing or containing the result of the action;</dd>
    1141          <dt>TRACE</dt>
    1142          <dd>an entity containing the request message as received by the end server.</dd>
    1143       </dl>
    1144       <div id="rfc.iref.28"></div>
    1145       <div id="rfc.iref.s.5"></div>
    1146       <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
    1147       <p id="rfc.section.8.2.2.p.1">The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced
    1148          by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header
    1149          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
    1150          the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin
    1151          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.
    1152       </p>
    1153       <p id="rfc.section.8.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,
    1154          see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    1155       </p>
    1156       <div id="rfc.iref.29"></div>
    1157       <div id="rfc.iref.s.6"></div>
    1158       <h3 id="rfc.section.8.2.3"><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
    1159       <p id="rfc.section.8.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
    1160          be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
    1161          code from an asynchronous operation such as this.
    1162       </p>
    1163       <p id="rfc.section.8.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
    1164          (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
    1165          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
    1166          user can expect the request to be fulfilled.
    1167       </p>
    1168       <div id="rfc.iref.30"></div>
    1169       <div id="rfc.iref.s.7"></div>
    1170       <h3 id="rfc.section.8.2.4"><a href="#rfc.section.8.2.4">8.2.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    1171       <p id="rfc.section.8.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
    1172          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
    1173          result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only
    1174          appropriate when the response would otherwise be 200 (OK).
    1175       </p>
    1176       <div id="rfc.iref.31"></div>
    1177       <div id="rfc.iref.s.8"></div>
    1178       <h3 id="rfc.section.8.2.5"><a href="#rfc.section.8.2.5">8.2.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
    1179       <p id="rfc.section.8.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.
    1180          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.
    1181       </p>
    1182       <p id="rfc.section.8.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
    1183          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.
    1184       </p>
    1185       <p id="rfc.section.8.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.
    1186       </p>
    1187       <div id="rfc.iref.32"></div>
    1188       <div id="rfc.iref.s.9"></div>
    1189       <h3 id="rfc.section.8.2.6"><a href="#rfc.section.8.2.6">8.2.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
    1190       <p id="rfc.section.8.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
    1191          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
    1192          another input action. The response <em class="bcp14">MUST NOT</em> include an entity.
    1193       </p>
    1194       <div id="rfc.iref.33"></div>
    1195       <div id="rfc.iref.s.10"></div>
    1196       <h3 id="rfc.section.8.2.7"><a href="#rfc.section.8.2.7">8.2.7</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h3>
    1197       <p id="rfc.section.8.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed entity is a partial representation as defined
    1198          in <a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
    1199       </p>
    1200       <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
    1201       <p id="rfc.section.8.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.
    1202          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
    1203          GET or HEAD. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection.
    1204       </p>
    1205       <div class="note">
    1206          <p> <b>Note:</b> an earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers should be aware that there might be clients that implement such a fixed limitation.
    1207          </p>
     929            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
     930            fields. Unrecognized header fields are treated as entity-header fields.
     931         </p>
    1208932      </div>
    1209       <div id="rfc.iref.34"></div>
    1210       <div id="rfc.iref.s.11"></div>
    1211       <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    1212       <p id="rfc.section.8.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
    1213          negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that
    1214          location.
    1215       </p>
    1216       <p id="rfc.section.8.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
    1217          the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending
    1218          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.
    1219       </p>
    1220       <p id="rfc.section.8.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.
    1221       </p>
    1222       <div id="rfc.iref.35"></div>
    1223       <div id="rfc.iref.s.12"></div>
    1224       <h3 id="rfc.section.8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    1225       <p id="rfc.section.8.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-target
    1226          to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
    1227       </p>
    1228       <p id="rfc.section.8.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).
    1229       </p>
    1230       <p id="rfc.section.8.3.2.p.3">If the 301 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, 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
    1231          the request was issued.
    1232       </p>
    1233       <div class="note">
    1234          <p> <b>Note:</b> When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously
    1235             change it into a GET request.
    1236          </p>
     933      <div id="entity">
     934         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#entity">Entity</a></h1>
     935         <p id="rfc.section.6.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
     936            fields and an entity-body, although some responses will only include the entity-headers. HTTP entity-body and entity-header
     937            fields are defined in <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     938         </p>
     939         <p id="rfc.section.6.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
     940            safe and proper transfer of the message.
     941         </p>
     942         <div id="identifying.response.associated.with.representation">
     943            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></h2>
     944            <p id="rfc.section.6.1.p.1">It is sometimes necessary to determine the identity of the resource associated with a representation.</p>
     945            <p id="rfc.section.6.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p>
     946            <p id="rfc.section.6.1.p.3">In the common case, an HTTP response is a representation of the resource located at the request-URI. However, this is not
     947               always the case. To determine the URI of the resource a response is associated with, the following rules are used (first match
     948               winning):
     949            </p>
     950            <ol>
     951               <li>If the response status code is 200 or 203 and the request method was GET, the response is a representation of the resource
     952                  at the request-URI.
     953               </li>
     954               <li>If the response status is 204, 206, or 304 and the request method was GET or HEAD, the response is a partial representation
     955                  of the resource at the request-URI (see <a href="p6-cache.html#combining.headers" title="Combining Responses">Section 2.7</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     956               </li>
     957               <li>If the response has a Content-Location header, and that URI is the same as the request-URI <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: (see [ref])]</span>, the response is a representation of the resource at the request-URI.
     958               </li>
     959               <li>If the response has a Content-Location header, and that URI is not the same as the request-URI, the response asserts that
     960                  it is a representation of the resource at the Content-Location URI (but it may not be).
     961               </li>
     962               <li>Otherwise, the response is a representation of an anonymous (i.e., unidentified) resource.</li>
     963            </ol>
     964            <p id="rfc.section.6.1.p.5"><span class="comment" id="TODO-req-uri">[<a href="#TODO-req-uri" class="smpl">TODO-req-uri</a>: Note that 'request-URI' is used here; however, we need to come up with a term to denote "the URI that can be inferred from
     965                  examining the request-target and the Host header." (see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;). Also, the comparison function is going to have to be defined somewhere, because we already need to compare URIs for things
     966                  like cache invalidation.]</span>
     967            </p>
     968         </div>
    1237969      </div>
    1238       <div id="rfc.iref.36"></div>
    1239       <div id="rfc.iref.s.13"></div>
    1240       <h3 id="rfc.section.8.3.3"><a href="#rfc.section.8.3.3">8.3.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    1241       <p id="rfc.section.8.3.3.p.1">The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the
    1242          client <em class="bcp14">SHOULD</em> continue to use the request-target for future requests. This response is only cacheable if indicated by a Cache-Control or
    1243          Expires header field.
    1244       </p>
    1245       <p id="rfc.section.8.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).
    1246       </p>
    1247       <p id="rfc.section.8.3.3.p.3">If the 302 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, 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
    1248          the request was issued.
    1249       </p>
    1250       <div class="note">
    1251          <p> <b>Note:</b> HTTP/1.0 (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="http://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>) and the first version of HTTP/1.1 (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3.3">Section 10.3.3</a>) specify that the client is not allowed to change the method on the redirected request. However, most existing user agent
    1252             implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original
    1253             request method. Therefore, a previous version of this specification (<a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="http://tools.ietf.org/html/rfc2616#section-10.3.3">Section 10.3.3</a>) has added the status codes <a href="#status.303" id="rfc.xref.status.303.2">303</a> and <a href="#status.307" id="rfc.xref.status.307.2">307</a> for servers that wish to make unambiguously clear which kind of reaction is expected of the client.
    1254          </p>
     970      <div id="method.definitions">
     971         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#method.definitions">Method Definitions</a></h1>
     972         <p id="rfc.section.7.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
     973            to share the same semantics for separately extended clients and servers.
     974         </p>
     975         <div id="safe.and.idempotent">
     976            <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2>
     977            <div id="safe.methods">
     978               <div id="rfc.iref.s.1"></div>
     979               <h3 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;<a href="#safe.methods">Safe Methods</a></h3>
     980               <p id="rfc.section.7.1.1.p.1">Implementors should be aware that the software represents the user in their interactions over the Internet, and should be
     981                  careful to allow the user to be aware of any actions they might take which may have an unexpected significance to themselves
     982                  or others.
     983               </p>
     984               <p id="rfc.section.7.1.1.p.2">In particular, the convention has been established that the GET, HEAD, OPTIONS, and TRACE methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "<dfn id="safe">safe</dfn>". This allows user agents to represent other methods, such as POST, PUT and DELETE, in a special way, so that the user is
     985                  made aware of the fact that a possibly unsafe action is being requested.
     986               </p>
     987               <p id="rfc.section.7.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;
     988                  in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the
     989                  side-effects, so therefore cannot be held accountable for them.
     990               </p>
     991            </div>
     992            <div id="idempotent.methods">
     993               <div id="rfc.iref.i.1"></div>
     994               <h3 id="rfc.section.7.1.2"><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></h3>
     995               <p id="rfc.section.7.1.2.p.1">Methods can also have the property of "idempotence" in that, aside from error or expiration issues, the intended effect of
     996                  multiple identical requests is the same as for a single request. The methods PUT, DELETE, and all safe methods are idempotent.
     997                  It is important to note that idempotence refers only to changes requested by the client: a server is free to change its state
     998                  due to multiple requests for the purpose of tracking those requests, versioning of results, etc.
     999               </p>
     1000            </div>
     1001         </div>
     1002         <div id="OPTIONS">
     1003            <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#OPTIONS">OPTIONS</a></h2>
     1004            <div id="rfc.iref.o.1"></div>
     1005            <div id="rfc.iref.m.1"></div>
     1006            <p id="rfc.section.7.2.p.1">The OPTIONS method represents a request for information about the communication options available on the request/response
     1007               chain identified by the request-target. This method allows the client to determine the options and/or requirements associated
     1008               with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
     1009            </p>
     1010            <p id="rfc.section.7.2.p.2">Responses to this method are not cacheable.</p>
     1011            <p id="rfc.section.7.2.p.3">If the OPTIONS request includes an entity-body (as indicated by the presence of Content-Length or Transfer-Encoding), then
     1012               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
     1013               to HTTP might use the OPTIONS body to make more detailed queries on the server.
     1014            </p>
     1015            <p id="rfc.section.7.2.p.4">If the request-target is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than
     1016               to a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
     1017               as a "ping" or "no-op" type of method; it does nothing beyond allowing the client to test the capabilities of the server.
     1018               For example, this can be used to test a proxy for HTTP/1.1 compliance (or lack thereof).
     1019            </p>
     1020            <p id="rfc.section.7.2.p.5">If the request-target is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
     1021               with that resource.
     1022            </p>
     1023            <p id="rfc.section.7.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.,
     1024               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,
     1025               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".
     1026            </p>
     1027            <p id="rfc.section.7.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 absolute-URI for which
     1028               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
     1029               request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
     1030            </p>
     1031         </div>
     1032         <div id="GET">
     1033            <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a href="#GET">GET</a></h2>
     1034            <div id="rfc.iref.g.8"></div>
     1035            <div id="rfc.iref.m.2"></div>
     1036            <p id="rfc.section.7.3.p.1">The GET method means retrieve whatever information (in the form of an entity) is identified by the request-target. If the
     1037               request-target refers to a data-producing process, it is the produced data which shall be returned as the entity in the response
     1038               and not the source text of the process, unless that text happens to be the output of the process.
     1039            </p>
     1040            <p id="rfc.section.7.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,
     1041               If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the entity be transferred only under
     1042               the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce unnecessary
     1043               network usage by allowing cached entities to be refreshed without requiring multiple requests or transferring data already
     1044               held by the client.
     1045            </p>
     1046            <p id="rfc.section.7.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
     1047               GET requests that only part of the entity be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed
     1048               without transferring data already held by the client.
     1049            </p>
     1050            <p id="rfc.section.7.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="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
     1051            </p>
     1052            <p id="rfc.section.7.3.p.5">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations when used for forms.
     1053            </p>
     1054         </div>
     1055         <div id="HEAD">
     1056            <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a href="#HEAD">HEAD</a></h2>
     1057            <div id="rfc.iref.h.1"></div>
     1058            <div id="rfc.iref.m.3"></div>
     1059            <p id="rfc.section.7.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
     1060               the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext
     1061               links for validity, accessibility, and recent modification.
     1062            </p>
     1063            <p id="rfc.section.7.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
     1064               from the current entity (as would be indicated by a change in Content-Length, Content-MD5, ETag or Last-Modified), then the
     1065               cache <em class="bcp14">MUST</em> treat the cache entry as stale.
     1066            </p>
     1067         </div>
     1068         <div id="POST">
     1069            <div id="rfc.iref.p.1"></div>
     1070            <div id="rfc.iref.m.4"></div>
     1071            <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a href="#POST">POST</a></h2>
     1072            <p id="rfc.section.7.5.p.1">The POST method is used to request that the origin server accept the entity enclosed in the request as data to be processed
     1073               by the resource identified by the request-target in the Request-Line. POST is designed to allow a uniform method to cover
     1074               the following functions:
     1075            </p>
     1076            <ul>
     1077               <li>Annotation of existing resources;</li>
     1078               <li>Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;</li>
     1079               <li>Providing a block of data, such as the result of submitting a form, to a data-handling process;</li>
     1080               <li>Extending a database through an append operation.</li>
     1081            </ul>
     1082            <p id="rfc.section.7.5.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the request-target.</p>
     1083            <p id="rfc.section.7.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
     1084               200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity
     1085               that describes the result.
     1086            </p>
     1087            <p id="rfc.section.7.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
     1088               header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;9.4</a>).
     1089            </p>
     1090            <p id="rfc.section.7.5.p.5">Responses to this method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields.
     1091               However, the 303 (See Other) response can be used to direct the user agent to retrieve a cacheable resource.
     1092            </p>
     1093         </div>
     1094         <div id="PUT">
     1095            <div id="rfc.iref.p.2"></div>
     1096            <div id="rfc.iref.m.5"></div>
     1097            <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a href="#PUT">PUT</a></h2>
     1098            <p id="rfc.section.7.6.p.1">The PUT method requests that the enclosed entity be stored at the supplied request-target. If the request-target refers to
     1099               an 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-target does not point to an existing
     1100               resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create
     1101               the resource with that URI. If a new resource is created at the request-target, 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
     1102               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-target,
     1103               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-* headers (headers starting with the prefix 'Content-') that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
     1104            </p>
     1105            <p id="rfc.section.7.6.p.2">If the request passes through a cache and the request-target 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.
     1106            </p>
     1107            <p id="rfc.section.7.6.p.3">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the request-target.
     1108               The URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting
     1109               process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request
     1110               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,
     1111               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.
     1112            </p>
     1113            <p id="rfc.section.7.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
     1114               is separate from the URI identifying each particular version. In this case, a PUT request on a general URI might result in
     1115               several other URIs being defined by the origin server.
     1116            </p>
     1117            <p id="rfc.section.7.6.p.5">HTTP/1.1 does not define how a PUT method affects the state of an origin server.</p>
     1118            <p id="rfc.section.7.6.p.6">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.
     1119            </p>
     1120         </div>
     1121         <div id="DELETE">
     1122            <div id="rfc.iref.d.1"></div>
     1123            <div id="rfc.iref.m.6"></div>
     1124            <h2 id="rfc.section.7.7"><a href="#rfc.section.7.7">7.7</a>&nbsp;<a href="#DELETE">DELETE</a></h2>
     1125            <p id="rfc.section.7.7.p.1">The DELETE method requests that the origin server delete the resource identified by the request-target. 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
     1126               has been carried out, even if the status code returned from the origin server indicates that the action has been completed
     1127               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
     1128               location.
     1129            </p>
     1130            <p id="rfc.section.7.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,
     1131               or 204 (No Content) if the action has been enacted but the response does not include an entity.
     1132            </p>
     1133            <p id="rfc.section.7.7.p.3">If the request passes through a cache and the request-target 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.
     1134            </p>
     1135         </div>
     1136         <div id="TRACE">
     1137            <h2 id="rfc.section.7.8"><a href="#rfc.section.7.8">7.8</a>&nbsp;<a href="#TRACE">TRACE</a></h2>
     1138            <div id="rfc.iref.t.1"></div>
     1139            <div id="rfc.iref.m.7"></div>
     1140            <p id="rfc.section.7.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
     1141               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
     1142               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;9.5</a>). A TRACE request <em class="bcp14">MUST NOT</em> include an entity.
     1143            </p>
     1144            <p id="rfc.section.7.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
     1145               or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the
     1146               client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an
     1147               infinite loop.
     1148            </p>
     1149            <p id="rfc.section.7.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" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 10.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Responses to this method <em class="bcp14">MUST NOT</em> be cached.
     1150            </p>
     1151         </div>
     1152         <div id="CONNECT">
     1153            <div id="rfc.iref.c.1"></div>
     1154            <div id="rfc.iref.m.8"></div>
     1155            <h2 id="rfc.section.7.9"><a href="#rfc.section.7.9">7.9</a>&nbsp;<a href="#CONNECT">CONNECT</a></h2>
     1156            <p id="rfc.section.7.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.
     1157               SSL tunneling <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>).
     1158            </p>
     1159         </div>
    12551160      </div>
    1256       <div id="rfc.iref.37"></div>
    1257       <div id="rfc.iref.s.14"></div>
    1258       <h3 id="rfc.section.8.3.4"><a href="#rfc.section.8.3.4">8.3.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
    1259       <p id="rfc.section.8.3.4.p.1">The server directs the user agent to a different resource, indicated by a URI in the Location header field, that provides
    1260          an indirect response to the original request. The user agent <em class="bcp14">MAY</em> perform a GET request on the URI in the Location field in order to obtain a representation corresponding to the response,
    1261          be redirected again, or end with an error status. The Location URI is not a substitute reference for the originally requested
    1262          resource.
    1263       </p>
    1264       <p id="rfc.section.8.3.4.p.2">The 303 status is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to redirect
    1265          the user agent to a selected resource, since doing so provides the information corresponding to the POST response in a form
    1266          that can be separately identified, bookmarked, and cached independent of the original request.
    1267       </p>
    1268       <p id="rfc.section.8.3.4.p.3">A 303 response to a GET request indicates that the requested resource does not have a representation of its own that can be
    1269          transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the requested resource such
    1270          that the follow-on representation may be useful without implying that it adequately represents the previously requested resource.
    1271          Note that answers to the questions of what can be represented, what representations are adequate, and what might be a useful
    1272          description are outside the scope of HTTP and thus entirely determined by the URI owner(s).
    1273       </p>
    1274       <p id="rfc.section.8.3.4.p.4">A 303 response <em class="bcp14">SHOULD NOT</em> be cached unless it is indicated as cacheable by Cache-Control or Expires header fields. Except for responses to a HEAD request,
    1275          the entity of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
    1276       </p>
    1277       <div id="rfc.iref.38"></div>
    1278       <div id="rfc.iref.s.15"></div>
    1279       <h3 id="rfc.section.8.3.5"><a href="#rfc.section.8.3.5">8.3.5</a>&nbsp;<a id="status.304" href="#status.304">304 Not Modified</a></h3>
    1280       <p id="rfc.section.8.3.5.p.1">The response to the request has not been modified since the conditions indicated by the client's conditional GET request,
    1281          as defined in <a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a> of <a href="#Part4" id="rfc.xref.Part4.14"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    1282       </p>
    1283       <div id="rfc.iref.39"></div>
    1284       <div id="rfc.iref.s.16"></div>
    1285       <h3 id="rfc.section.8.3.6"><a href="#rfc.section.8.3.6">8.3.6</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
    1286       <p id="rfc.section.8.3.6.p.1">The 305 status was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;A.2</a>), and is now deprecated.
    1287       </p>
    1288       <div id="rfc.iref.40"></div>
    1289       <div id="rfc.iref.s.17"></div>
    1290       <h3 id="rfc.section.8.3.7"><a href="#rfc.section.8.3.7">8.3.7</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
    1291       <p id="rfc.section.8.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>
    1292       <div id="rfc.iref.41"></div>
    1293       <div id="rfc.iref.s.18"></div>
    1294       <h3 id="rfc.section.8.3.8"><a href="#rfc.section.8.3.8">8.3.8</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    1295       <p id="rfc.section.8.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-target for future requests. This response is only cacheable if indicated by a Cache-Control or
    1296          Expires header field.
    1297       </p>
    1298       <p id="rfc.section.8.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
    1299          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.
    1300       </p>
    1301       <p id="rfc.section.8.3.8.p.3">If the 307 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, 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
    1302          the request was issued.
    1303       </p>
    1304       <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
    1305       <p id="rfc.section.8.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
    1306          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.
    1307          These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included entity to the user.
    1308       </p>
    1309       <p id="rfc.section.8.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
    1310          the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send
    1311          a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted
    1312          by the HTTP application.
    1313       </p>
    1314       <div id="rfc.iref.42"></div>
    1315       <div id="rfc.iref.s.19"></div>
    1316       <h3 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    1317       <p id="rfc.section.8.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.
    1318       </p>
    1319       <div id="rfc.iref.43"></div>
    1320       <div id="rfc.iref.s.20"></div>
    1321       <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h3>
    1322       <p id="rfc.section.8.4.2.p.1">The request requires user authentication (see <a href="p7-auth.html#status.401" title="401 Unauthorized">Section 2.1</a> of <a href="#Part7" id="rfc.xref.Part7.11"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
    1323       </p>
    1324       <div id="rfc.iref.44"></div>
    1325       <div id="rfc.iref.s.21"></div>
    1326       <h3 id="rfc.section.8.4.3"><a href="#rfc.section.8.4.3">8.4.3</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
    1327       <p id="rfc.section.8.4.3.p.1">This code is reserved for future use.</p>
    1328       <div id="rfc.iref.45"></div>
    1329       <div id="rfc.iref.s.22"></div>
    1330       <h3 id="rfc.section.8.4.4"><a href="#rfc.section.8.4.4">8.4.4</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    1331       <p id="rfc.section.8.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,
    1332          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,
    1333          the status code 404 (Not Found) can be used instead.
    1334       </p>
    1335       <div id="rfc.iref.46"></div>
    1336       <div id="rfc.iref.s.23"></div>
    1337       <h3 id="rfc.section.8.4.5"><a href="#rfc.section.8.4.5">8.4.5</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    1338       <p id="rfc.section.8.4.5.p.1">The server has not found anything matching the request-target. No indication is given of whether the condition is temporary
    1339          or 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
    1340          and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
    1341          has been refused, or when no other response is applicable.
    1342       </p>
    1343       <div id="rfc.iref.47"></div>
    1344       <div id="rfc.iref.s.24"></div>
    1345       <h3 id="rfc.section.8.4.6"><a href="#rfc.section.8.4.6">8.4.6</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    1346       <p id="rfc.section.8.4.6.p.1">The method specified in the Request-Line is not allowed for the resource identified by the request-target. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource.
    1347       </p>
    1348       <div id="rfc.iref.48"></div>
    1349       <div id="rfc.iref.s.25"></div>
    1350       <h3 id="rfc.section.8.4.7"><a href="#rfc.section.8.4.7">8.4.7</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    1351       <p id="rfc.section.8.4.7.p.1">The resource identified by the request is only capable of generating response entities which have content characteristics
    1352          not acceptable according to the accept headers sent in the request.
    1353       </p>
    1354       <p id="rfc.section.8.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
    1355          can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field.
    1356          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.
    1357       </p>
    1358       <div class="note">
    1359          <p> <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.
    1360             In some cases, this may even be preferable to sending a 406 response. User agents are encouraged to inspect the headers of
    1361             an incoming response to determine if it is acceptable.
    1362          </p>
     1161      <div id="status.codes">
     1162         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#status.codes">Status Code Definitions</a></h1>
     1163         <p id="rfc.section.8.p.1">Each Status-Code is described below, including any metainformation required in the response.</p>
     1164         <div id="status.1xx">
     1165            <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a href="#status.1xx">Informational 1xx</a></h2>
     1166            <p id="rfc.section.8.1.p.1">This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is
     1167               terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any
     1168               1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions.
     1169            </p>
     1170            <p id="rfc.section.8.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
     1171               (Continue) status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
     1172            </p>
     1173            <p id="rfc.section.8.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
     1174               requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards
     1175               a request, then it need not forward the corresponding 100 (Continue) response(s).)
     1176            </p>
     1177            <div id="status.100">
     1178               <div id="rfc.iref.1.1"></div>
     1179               <div id="rfc.iref.s.2"></div>
     1180               <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a href="#status.100">100 Continue</a></h3>
     1181               <p id="rfc.section.8.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
     1182                  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
     1183                  server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
     1184               </p>
     1185            </div>
     1186            <div id="status.101">
     1187               <div id="rfc.iref.1.2"></div>
     1188               <div id="rfc.iref.s.3"></div>
     1189               <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a href="#status.101">101 Switching Protocols</a></h3>
     1190               <p id="rfc.section.8.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="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     1191                  by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
     1192               </p>
     1193               <p id="rfc.section.8.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
     1194                  older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
     1195                  such features.
     1196               </p>
     1197            </div>
     1198         </div>
     1199         <div id="status.2xx">
     1200            <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a href="#status.2xx">Successful 2xx</a></h2>
     1201            <p id="rfc.section.8.2.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
     1202            <div id="status.200">
     1203               <div id="rfc.iref.2.1"></div>
     1204               <div id="rfc.iref.s.4"></div>
     1205               <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a href="#status.200">200 OK</a></h3>
     1206               <p id="rfc.section.8.2.1.p.1">The request has succeeded. The information returned with the response is dependent on the method used in the request, for
     1207                  example:
     1208               </p>
     1209               <dl>
     1210                  <dt>GET</dt>
     1211                  <dd>an entity corresponding to the requested resource is sent in the response;</dd>
     1212                  <dt>HEAD</dt>
     1213                  <dd>the entity-header fields corresponding to the requested resource are sent in the response without any message-body;</dd>
     1214                  <dt>POST</dt>
     1215                  <dd>an entity describing or containing the result of the action;</dd>
     1216                  <dt>TRACE</dt>
     1217                  <dd>an entity containing the request message as received by the end server.</dd>
     1218               </dl>
     1219            </div>
     1220            <div id="status.201">
     1221               <div id="rfc.iref.2.2"></div>
     1222               <div id="rfc.iref.s.5"></div>
     1223               <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a href="#status.201">201 Created</a></h3>
     1224               <p id="rfc.section.8.2.2.p.1">The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced
     1225                  by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header
     1226                  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
     1227                  the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin
     1228                  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.
     1229               </p>
     1230               <p id="rfc.section.8.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,
     1231                  see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
     1232               </p>
     1233            </div>
     1234            <div id="status.202">
     1235               <div id="rfc.iref.2.3"></div>
     1236               <div id="rfc.iref.s.6"></div>
     1237               <h3 id="rfc.section.8.2.3"><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;<a href="#status.202">202 Accepted</a></h3>
     1238               <p id="rfc.section.8.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
     1239                  be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
     1240                  code from an asynchronous operation such as this.
     1241               </p>
     1242               <p id="rfc.section.8.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
     1243                  (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
     1244                  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
     1245                  user can expect the request to be fulfilled.
     1246               </p>
     1247            </div>
     1248            <div id="status.203">
     1249               <div id="rfc.iref.2.4"></div>
     1250               <div id="rfc.iref.s.7"></div>
     1251               <h3 id="rfc.section.8.2.4"><a href="#rfc.section.8.2.4">8.2.4</a>&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></h3>
     1252               <p id="rfc.section.8.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
     1253                  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
     1254                  result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only
     1255                  appropriate when the response would otherwise be 200 (OK).
     1256               </p>
     1257            </div>
     1258            <div id="status.204">
     1259               <div id="rfc.iref.2.5"></div>
     1260               <div id="rfc.iref.s.8"></div>
     1261               <h3 id="rfc.section.8.2.5"><a href="#rfc.section.8.2.5">8.2.5</a>&nbsp;<a href="#status.204">204 No Content</a></h3>
     1262               <p id="rfc.section.8.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.
     1263                  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.
     1264               </p>
     1265               <p id="rfc.section.8.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
     1266                  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.
     1267               </p>
     1268               <p id="rfc.section.8.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.
     1269               </p>
     1270            </div>
     1271            <div id="status.205">
     1272               <div id="rfc.iref.2.6"></div>
     1273               <div id="rfc.iref.s.9"></div>
     1274               <h3 id="rfc.section.8.2.6"><a href="#rfc.section.8.2.6">8.2.6</a>&nbsp;<a href="#status.205">205 Reset Content</a></h3>
     1275               <p id="rfc.section.8.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
     1276                  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
     1277                  another input action. The response <em class="bcp14">MUST NOT</em> include an entity.
     1278               </p>
     1279            </div>
     1280            <div id="status.206">
     1281               <div id="rfc.iref.2.7"></div>
     1282               <div id="rfc.iref.s.10"></div>
     1283               <h3 id="rfc.section.8.2.7"><a href="#rfc.section.8.2.7">8.2.7</a>&nbsp;<a href="#status.206">206 Partial Content</a></h3>
     1284               <p id="rfc.section.8.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed entity is a partial representation as defined
     1285                  in <a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
     1286               </p>
     1287            </div>
     1288         </div>
     1289         <div id="status.3xx">
     1290            <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a href="#status.3xx">Redirection 3xx</a></h2>
     1291            <p id="rfc.section.8.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.
     1292               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
     1293               GET or HEAD. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection.
     1294            </p>
     1295            <div class="note" id="rfc.section.8.3.p.2">
     1296               <p><b>Note:</b> an earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="https://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers should be aware that there might be clients that implement such a fixed limitation.
     1297               </p>
     1298            </div>
     1299            <div id="status.300">
     1300               <div id="rfc.iref.3.1"></div>
     1301               <div id="rfc.iref.s.11"></div>
     1302               <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a href="#status.300">300 Multiple Choices</a></h3>
     1303               <p id="rfc.section.8.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
     1304                  negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that
     1305                  location.
     1306               </p>
     1307               <p id="rfc.section.8.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
     1308                  the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending
     1309                  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.
     1310               </p>
     1311               <p id="rfc.section.8.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.
     1312               </p>
     1313            </div>
     1314            <div id="status.301">
     1315               <div id="rfc.iref.3.2"></div>
     1316               <div id="rfc.iref.s.12"></div>
     1317               <h3 id="rfc.section.8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;<a href="#status.301">301 Moved Permanently</a></h3>
     1318               <p id="rfc.section.8.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-target
     1319                  to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
     1320               </p>
     1321               <p id="rfc.section.8.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).
     1322               </p>
     1323               <p id="rfc.section.8.3.2.p.3">If the 301 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, 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
     1324                  the request was issued.
     1325               </p>
     1326               <div class="note" id="rfc.section.8.3.2.p.4">
     1327                  <p><b>Note:</b> When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously
     1328                     change it into a GET request.
     1329                  </p>
     1330               </div>
     1331            </div>
     1332            <div id="status.302">
     1333               <div id="rfc.iref.3.3"></div>
     1334               <div id="rfc.iref.s.13"></div>
     1335               <h3 id="rfc.section.8.3.3"><a href="#rfc.section.8.3.3">8.3.3</a>&nbsp;<a href="#status.302">302 Found</a></h3>
     1336               <p id="rfc.section.8.3.3.p.1">The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the
     1337                  client <em class="bcp14">SHOULD</em> continue to use the request-target for future requests. This response is only cacheable if indicated by a Cache-Control or
     1338                  Expires header field.
     1339               </p>
     1340               <p id="rfc.section.8.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).
     1341               </p>
     1342               <p id="rfc.section.8.3.3.p.3">If the 302 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, 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
     1343                  the request was issued.
     1344               </p>
     1345               <div class="note" id="rfc.section.8.3.3.p.4">
     1346                  <p><b>Note:</b> HTTP/1.0 (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="https://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>) and the first version of HTTP/1.1 (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="https://tools.ietf.org/html/rfc2068#section-10.3.3">Section 10.3.3</a>) specify that the client is not allowed to change the method on the redirected request. However, most existing user agent
     1347                     implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original
     1348                     request method. Therefore, a previous version of this specification (<a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="https://tools.ietf.org/html/rfc2616#section-10.3.3">Section 10.3.3</a>) has added the status codes <a href="#status.303" id="rfc.xref.status.303.2">303</a> and <a href="#status.307" id="rfc.xref.status.307.2">307</a> for servers that wish to make unambiguously clear which kind of reaction is expected of the client.
     1349                  </p>
     1350               </div>
     1351            </div>
     1352            <div id="status.303">
     1353               <div id="rfc.iref.3.4"></div>
     1354               <div id="rfc.iref.s.14"></div>
     1355               <h3 id="rfc.section.8.3.4"><a href="#rfc.section.8.3.4">8.3.4</a>&nbsp;<a href="#status.303">303 See Other</a></h3>
     1356               <p id="rfc.section.8.3.4.p.1">The server directs the user agent to a different resource, indicated by a URI in the Location header field, that provides
     1357                  an indirect response to the original request. The user agent <em class="bcp14">MAY</em> perform a GET request on the URI in the Location field in order to obtain a representation corresponding to the response,
     1358                  be redirected again, or end with an error status. The Location URI is not a substitute reference for the originally requested
     1359                  resource.
     1360               </p>
     1361               <p id="rfc.section.8.3.4.p.2">The 303 status is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to redirect
     1362                  the user agent to a selected resource, since doing so provides the information corresponding to the POST response in a form
     1363                  that can be separately identified, bookmarked, and cached independent of the original request.
     1364               </p>
     1365               <p id="rfc.section.8.3.4.p.3">A 303 response to a GET request indicates that the requested resource does not have a representation of its own that can be
     1366                  transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the requested resource such
     1367                  that the follow-on representation may be useful without implying that it adequately represents the previously requested resource.
     1368                  Note that answers to the questions of what can be represented, what representations are adequate, and what might be a useful
     1369                  description are outside the scope of HTTP and thus entirely determined by the URI owner(s).
     1370               </p>
     1371               <p id="rfc.section.8.3.4.p.4">A 303 response <em class="bcp14">SHOULD NOT</em> be cached unless it is indicated as cacheable by Cache-Control or Expires header fields. Except for responses to a HEAD request,
     1372                  the entity of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
     1373               </p>
     1374            </div>
     1375            <div id="status.304">
     1376               <div id="rfc.iref.3.5"></div>
     1377               <div id="rfc.iref.s.15"></div>
     1378               <h3 id="rfc.section.8.3.5"><a href="#rfc.section.8.3.5">8.3.5</a>&nbsp;<a href="#status.304">304 Not Modified</a></h3>
     1379               <p id="rfc.section.8.3.5.p.1">The response to the request has not been modified since the conditions indicated by the client's conditional GET request,
     1380                  as defined in <a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a> of <a href="#Part4" id="rfc.xref.Part4.14"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
     1381               </p>
     1382            </div>
     1383            <div id="status.305">
     1384               <div id="rfc.iref.3.6"></div>
     1385               <div id="rfc.iref.s.16"></div>
     1386               <h3 id="rfc.section.8.3.6"><a href="#rfc.section.8.3.6">8.3.6</a>&nbsp;<a href="#status.305">305 Use Proxy</a></h3>
     1387               <p id="rfc.section.8.3.6.p.1">The 305 status was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;A.2</a>), and is now deprecated.
     1388               </p>
     1389            </div>
     1390            <div id="status.306">
     1391               <div id="rfc.iref.3.7"></div>
     1392               <div id="rfc.iref.s.17"></div>
     1393               <h3 id="rfc.section.8.3.7"><a href="#rfc.section.8.3.7">8.3.7</a>&nbsp;<a href="#status.306">306 (Unused)</a></h3>
     1394               <p id="rfc.section.8.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>
     1395            </div>
     1396            <div id="status.307">
     1397               <div id="rfc.iref.3.8"></div>
     1398               <div id="rfc.iref.s.18"></div>
     1399               <h3 id="rfc.section.8.3.8"><a href="#rfc.section.8.3.8">8.3.8</a>&nbsp;<a href="#status.307">307 Temporary Redirect</a></h3>
     1400               <p id="rfc.section.8.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-target for future requests. This response is only cacheable if indicated by a Cache-Control or
     1401                  Expires header field.
     1402               </p>
     1403               <p id="rfc.section.8.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
     1404                  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.
     1405               </p>
     1406               <p id="rfc.section.8.3.8.p.3">If the 307 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>, then the request <em class="bcp14">MAY</em> be automatically redirected by the user agent without confirmation. Otherwise, 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
     1407                  the request was issued.
     1408               </p>
     1409            </div>
     1410         </div>
     1411         <div id="status.4xx">
     1412            <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a href="#status.4xx">Client Error 4xx</a></h2>
     1413            <p id="rfc.section.8.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
     1414               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.
     1415               These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included entity to the user.
     1416            </p>
     1417            <p id="rfc.section.8.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
     1418               the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send
     1419               a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted
     1420               by the HTTP application.
     1421            </p>
     1422            <div id="status.400">
     1423               <div id="rfc.iref.4.1"></div>
     1424               <div id="rfc.iref.s.19"></div>
     1425               <h3 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a href="#status.400">400 Bad Request</a></h3>
     1426               <p id="rfc.section.8.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.
     1427               </p>
     1428            </div>
     1429            <div id="status.401">
     1430               <div id="rfc.iref.4.2"></div>
     1431               <div id="rfc.iref.s.20"></div>
     1432               <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a href="#status.401">401 Unauthorized</a></h3>
     1433               <p id="rfc.section.8.4.2.p.1">The request requires user authentication (see <a href="p7-auth.html#status.401" title="401 Unauthorized">Section 2.1</a> of <a href="#Part7" id="rfc.xref.Part7.11"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
     1434               </p>
     1435            </div>
     1436            <div id="status.402">
     1437               <div id="rfc.iref.4.3"></div>
     1438               <div id="rfc.iref.s.21"></div>
     1439               <h3 id="rfc.section.8.4.3"><a href="#rfc.section.8.4.3">8.4.3</a>&nbsp;<a href="#status.402">402 Payment Required</a></h3>
     1440               <p id="rfc.section.8.4.3.p.1">This code is reserved for future use.</p>
     1441            </div>
     1442            <div id="status.403">
     1443               <div id="rfc.iref.4.4"></div>
     1444               <div id="rfc.iref.s.22"></div>
     1445               <h3 id="rfc.section.8.4.4"><a href="#rfc.section.8.4.4">8.4.4</a>&nbsp;<a href="#status.403">403 Forbidden</a></h3>
     1446               <p id="rfc.section.8.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,
     1447                  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,
     1448                  the status code 404 (Not Found) can be used instead.
     1449               </p>
     1450            </div>
     1451            <div id="status.404">
     1452               <div id="rfc.iref.4.5"></div>
     1453               <div id="rfc.iref.s.23"></div>
     1454               <h3 id="rfc.section.8.4.5"><a href="#rfc.section.8.4.5">8.4.5</a>&nbsp;<a href="#status.404">404 Not Found</a></h3>
     1455               <p id="rfc.section.8.4.5.p.1">The server has not found anything matching the request-target. No indication is given of whether the condition is temporary
     1456                  or 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
     1457                  and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
     1458                  has been refused, or when no other response is applicable.
     1459               </p>
     1460            </div>
     1461            <div id="status.405">
     1462               <div id="rfc.iref.4.6"></div>
     1463               <div id="rfc.iref.s.24"></div>
     1464               <h3 id="rfc.section.8.4.6"><a href="#rfc.section.8.4.6">8.4.6</a>&nbsp;<a href="#status.405">405 Method Not Allowed</a></h3>
     1465               <p id="rfc.section.8.4.6.p.1">The method specified in the Request-Line is not allowed for the resource identified by the request-target. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource.
     1466               </p>
     1467            </div>
     1468            <div id="status.406">
     1469               <div id="rfc.iref.4.7"></div>
     1470               <div id="rfc.iref.s.25"></div>
     1471               <h3 id="rfc.section.8.4.7"><a href="#rfc.section.8.4.7">8.4.7</a>&nbsp;<a href="#status.406">406 Not Acceptable</a></h3>
     1472               <p id="rfc.section.8.4.7.p.1">The resource identified by the request is only capable of generating response entities which have content characteristics
     1473                  not acceptable according to the accept headers sent in the request.
     1474               </p>
     1475               <p id="rfc.section.8.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
     1476                  can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field.
     1477                  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.
     1478               </p>
     1479               <div class="note" id="rfc.section.8.4.7.p.3">
     1480                  <p><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.
     1481                     In some cases, this may even be preferable to sending a 406 response. User agents are encouraged to inspect the headers of
     1482                     an incoming response to determine if it is acceptable.
     1483                  </p>
     1484               </div>
     1485               <p id="rfc.section.8.4.7.p.4">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.
     1486               </p>
     1487            </div>
     1488            <div id="status.407">
     1489               <div id="rfc.iref.4.8"></div>
     1490               <div id="rfc.iref.s.26"></div>
     1491               <h3 id="rfc.section.8.4.8"><a href="#rfc.section.8.4.8">8.4.8</a>&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></h3>
     1492               <p id="rfc.section.8.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 2.2</a> of <a href="#Part7" id="rfc.xref.Part7.12"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
     1493               </p>
     1494            </div>
     1495            <div id="status.408">
     1496               <div id="rfc.iref.4.9"></div>
     1497               <div id="rfc.iref.s.27"></div>
     1498               <h3 id="rfc.section.8.4.9"><a href="#rfc.section.8.4.9">8.4.9</a>&nbsp;<a href="#status.408">408 Request Timeout</a></h3>
     1499               <p id="rfc.section.8.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.
     1500               </p>
     1501            </div>
     1502            <div id="status.409">
     1503               <div id="rfc.iref.4.10"></div>
     1504               <div id="rfc.iref.s.28"></div>
     1505               <h3 id="rfc.section.8.4.10"><a href="#rfc.section.8.4.10">8.4.10</a>&nbsp;<a href="#status.409">409 Conflict</a></h3>
     1506               <p id="rfc.section.8.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
     1507                  situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
     1508                  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
     1509                  enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
     1510               </p>
     1511               <p id="rfc.section.8.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
     1512                  being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
     1513                  use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain
     1514                  a list of the differences between the two versions in a format defined by the response Content-Type.
     1515               </p>
     1516            </div>
     1517            <div id="status.410">
     1518               <div id="rfc.iref.4.11"></div>
     1519               <div id="rfc.iref.s.29"></div>
     1520               <h3 id="rfc.section.8.4.11"><a href="#rfc.section.8.4.11">8.4.11</a>&nbsp;<a href="#status.410">410 Gone</a></h3>
     1521               <p id="rfc.section.8.4.11.p.1">The requested resource is no longer available at the server and no forwarding address is known. This condition is expected
     1522                  to be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the request-target after user approval. If the server does not know, or has no facility to determine,
     1523                  whether 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.
     1524               </p>
     1525               <p id="rfc.section.8.4.11.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
     1526                  is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
     1527                  is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
     1528                  site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time
     1529                  -- that is left to the discretion of the server owner.
     1530               </p>
     1531            </div>
     1532            <div id="status.411">
     1533               <div id="rfc.iref.4.12"></div>
     1534               <div id="rfc.iref.s.30"></div>
     1535               <h3 id="rfc.section.8.4.12"><a href="#rfc.section.8.4.12">8.4.12</a>&nbsp;<a href="#status.411">411 Length Required</a></h3>
     1536               <p id="rfc.section.8.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
     1537                  message.
     1538               </p>
     1539            </div>
     1540            <div id="status.412">
     1541               <div id="rfc.iref.4.13"></div>
     1542               <div id="rfc.iref.s.31"></div>
     1543               <h3 id="rfc.section.8.4.13"><a href="#rfc.section.8.4.13">8.4.13</a>&nbsp;<a href="#status.412">412 Precondition Failed</a></h3>
     1544               <p id="rfc.section.8.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, as
     1545                  defined in <a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4.15"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
     1546               </p>
     1547            </div>
     1548            <div id="status.413">
     1549               <div id="rfc.iref.4.14"></div>
     1550               <div id="rfc.iref.s.32"></div>
     1551               <h3 id="rfc.section.8.4.14"><a href="#rfc.section.8.4.14">8.4.14</a>&nbsp;<a href="#status.413">413 Request Entity Too Large</a></h3>
     1552               <p id="rfc.section.8.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.
     1553                  The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
     1554               </p>
     1555               <p id="rfc.section.8.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.
     1556               </p>
     1557            </div>
     1558            <div id="status.414">
     1559               <div id="rfc.iref.4.15"></div>
     1560               <div id="rfc.iref.s.33"></div>
     1561               <h3 id="rfc.section.8.4.15"><a href="#rfc.section.8.4.15">8.4.15</a>&nbsp;<a href="#status.414">414 URI Too Long</a></h3>
     1562               <p id="rfc.section.8.4.15.p.1">The server is refusing to service the request because the request-target is longer than the server is willing to interpret.
     1563                  This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
     1564                  query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
     1565                  points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present
     1566                  in some servers using fixed-length buffers for reading or manipulating the request-target.
     1567               </p>
     1568            </div>
     1569            <div id="status.415">
     1570               <div id="rfc.iref.4.16"></div>
     1571               <div id="rfc.iref.s.34"></div>
     1572               <h3 id="rfc.section.8.4.16"><a href="#rfc.section.8.4.16">8.4.16</a>&nbsp;<a href="#status.415">415 Unsupported Media Type</a></h3>
     1573               <p id="rfc.section.8.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
     1574                  resource for the requested method.
     1575               </p>
     1576            </div>
     1577            <div id="status.416">
     1578               <div id="rfc.iref.4.17"></div>
     1579               <div id="rfc.iref.s.35"></div>
     1580               <h3 id="rfc.section.8.4.17"><a href="#rfc.section.8.4.17">8.4.17</a>&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></h3>
     1581               <p id="rfc.section.8.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.11"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource. See <a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.12"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>
     1582               </p>
     1583            </div>
     1584            <div id="status.417">
     1585               <div id="rfc.iref.4.18"></div>
     1586               <div id="rfc.iref.s.36"></div>
     1587               <h3 id="rfc.section.8.4.18"><a href="#rfc.section.8.4.18">8.4.18</a>&nbsp;<a href="#status.417">417 Expectation Failed</a></h3>
     1588               <p id="rfc.section.8.4.18.p.1">The expectation given in an Expect request-header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;9.2</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
     1589                  not be met by the next-hop server.
     1590               </p>
     1591            </div>
     1592         </div>
     1593         <div id="status.5xx">
     1594            <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a href="#status.5xx">Server Error 5xx</a></h2>
     1595            <p id="rfc.section.8.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
     1596               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.
     1597               User agents <em class="bcp14">SHOULD</em> display any included entity to the user. These response codes are applicable to any request method.
     1598            </p>
     1599            <div id="status.500">
     1600               <div id="rfc.iref.5.1"></div>
     1601               <div id="rfc.iref.s.37"></div>
     1602               <h3 id="rfc.section.8.5.1"><a href="#rfc.section.8.5.1">8.5.1</a>&nbsp;<a href="#status.500">500 Internal Server Error</a></h3>
     1603               <p id="rfc.section.8.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
     1604            </div>
     1605            <div id="status.501">
     1606               <div id="rfc.iref.5.2"></div>
     1607               <div id="rfc.iref.s.38"></div>
     1608               <h3 id="rfc.section.8.5.2"><a href="#rfc.section.8.5.2">8.5.2</a>&nbsp;<a href="#status.501">501 Not Implemented</a></h3>
     1609               <p id="rfc.section.8.5.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
     1610                  does not recognize the request method and is not capable of supporting it for any resource.
     1611               </p>
     1612            </div>
     1613            <div id="status.502">
     1614               <div id="rfc.iref.5.3"></div>
     1615               <div id="rfc.iref.s.39"></div>
     1616               <h3 id="rfc.section.8.5.3"><a href="#rfc.section.8.5.3">8.5.3</a>&nbsp;<a href="#status.502">502 Bad Gateway</a></h3>
     1617               <p id="rfc.section.8.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
     1618                  to fulfill the request.
     1619               </p>
     1620            </div>
     1621            <div id="status.503">
     1622               <div id="rfc.iref.5.4"></div>
     1623               <div id="rfc.iref.s.40"></div>
     1624               <h3 id="rfc.section.8.5.4"><a href="#rfc.section.8.5.4">8.5.4</a>&nbsp;<a href="#status.503">503 Service Unavailable</a></h3>
     1625               <p id="rfc.section.8.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
     1626                  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.
     1627               </p>
     1628               <div class="note" id="rfc.section.8.5.4.p.2">
     1629                  <p><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
     1630                     to simply refuse the connection.
     1631                  </p>
     1632               </div>
     1633            </div>
     1634            <div id="status.504">
     1635               <div id="rfc.iref.5.5"></div>
     1636               <div id="rfc.iref.s.41"></div>
     1637               <h3 id="rfc.section.8.5.5"><a href="#rfc.section.8.5.5">8.5.5</a>&nbsp;<a href="#status.504">504 Gateway Timeout</a></h3>
     1638               <p id="rfc.section.8.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
     1639                  URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
     1640               </p>
     1641               <div class="note" id="rfc.section.8.5.5.p.2">
     1642                  <p><b>Note:</b> Note to implementors: some deployed proxies are known to return 400 or 500 when DNS lookups time out.
     1643                  </p>
     1644               </div>
     1645            </div>
     1646            <div id="status.505">
     1647               <div id="rfc.iref.5.6"></div>
     1648               <div id="rfc.iref.s.42"></div>
     1649               <h3 id="rfc.section.8.5.6"><a href="#rfc.section.8.5.6">8.5.6</a>&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></h3>
     1650               <p id="rfc.section.8.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
     1651                  is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
     1652                  in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, 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.
     1653               </p>
     1654            </div>
     1655         </div>
    13631656      </div>
    1364       <p id="rfc.section.8.4.7.p.4">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.
    1365       </p>
    1366       <div id="rfc.iref.49"></div>
    1367       <div id="rfc.iref.s.26"></div>
    1368       <h3 id="rfc.section.8.4.8"><a href="#rfc.section.8.4.8">8.4.8</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h3>
    1369       <p id="rfc.section.8.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 2.2</a> of <a href="#Part7" id="rfc.xref.Part7.12"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
    1370       </p>
    1371       <div id="rfc.iref.50"></div>
    1372       <div id="rfc.iref.s.27"></div>
    1373       <h3 id="rfc.section.8.4.9"><a href="#rfc.section.8.4.9">8.4.9</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
    1374       <p id="rfc.section.8.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.
    1375       </p>
    1376       <div id="rfc.iref.51"></div>
    1377       <div id="rfc.iref.s.28"></div>
    1378       <h3 id="rfc.section.8.4.10"><a href="#rfc.section.8.4.10">8.4.10</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
    1379       <p id="rfc.section.8.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
    1380          situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
    1381          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
    1382          enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
    1383       </p>
    1384       <p id="rfc.section.8.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
    1385          being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
    1386          use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain
    1387          a list of the differences between the two versions in a format defined by the response Content-Type.
    1388       </p>
    1389       <div id="rfc.iref.52"></div>
    1390       <div id="rfc.iref.s.29"></div>
    1391       <h3 id="rfc.section.8.4.11"><a href="#rfc.section.8.4.11">8.4.11</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    1392       <p id="rfc.section.8.4.11.p.1">The requested resource is no longer available at the server and no forwarding address is known. This condition is expected
    1393          to be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the request-target after user approval. If the server does not know, or has no facility to determine,
    1394          whether 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.
    1395       </p>
    1396       <p id="rfc.section.8.4.11.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
    1397          is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
    1398          is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
    1399          site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time
    1400          -- that is left to the discretion of the server owner.
    1401       </p>
    1402       <div id="rfc.iref.53"></div>
    1403       <div id="rfc.iref.s.30"></div>
    1404       <h3 id="rfc.section.8.4.12"><a href="#rfc.section.8.4.12">8.4.12</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
    1405       <p id="rfc.section.8.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
    1406          message.
    1407       </p>
    1408       <div id="rfc.iref.54"></div>
    1409       <div id="rfc.iref.s.31"></div>
    1410       <h3 id="rfc.section.8.4.13"><a href="#rfc.section.8.4.13">8.4.13</a>&nbsp;<a id="status.412" href="#status.412">412 Precondition Failed</a></h3>
    1411       <p id="rfc.section.8.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, as
    1412          defined in <a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4.15"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    1413       </p>
    1414       <div id="rfc.iref.55"></div>
    1415       <div id="rfc.iref.s.32"></div>
    1416       <h3 id="rfc.section.8.4.14"><a href="#rfc.section.8.4.14">8.4.14</a>&nbsp;<a id="status.413" href="#status.413">413 Request Entity Too Large</a></h3>
    1417       <p id="rfc.section.8.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.
    1418          The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
    1419       </p>
    1420       <p id="rfc.section.8.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.
    1421       </p>
    1422       <div id="rfc.iref.56"></div>
    1423       <div id="rfc.iref.s.33"></div>
    1424       <h3 id="rfc.section.8.4.15"><a href="#rfc.section.8.4.15">8.4.15</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
    1425       <p id="rfc.section.8.4.15.p.1">The server is refusing to service the request because the request-target is longer than the server is willing to interpret.
    1426          This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
    1427          query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
    1428          points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present
    1429          in some servers using fixed-length buffers for reading or manipulating the request-target.
    1430       </p>
    1431       <div id="rfc.iref.57"></div>
    1432       <div id="rfc.iref.s.34"></div>
    1433       <h3 id="rfc.section.8.4.16"><a href="#rfc.section.8.4.16">8.4.16</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    1434       <p id="rfc.section.8.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
    1435          resource for the requested method.
    1436       </p>
    1437       <div id="rfc.iref.58"></div>
    1438       <div id="rfc.iref.s.35"></div>
    1439       <h3 id="rfc.section.8.4.17"><a href="#rfc.section.8.4.17">8.4.17</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3>
    1440       <p id="rfc.section.8.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.11"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource. See <a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.12"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>
    1441       </p>
    1442       <div id="rfc.iref.59"></div>
    1443       <div id="rfc.iref.s.36"></div>
    1444       <h3 id="rfc.section.8.4.18"><a href="#rfc.section.8.4.18">8.4.18</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    1445       <p id="rfc.section.8.4.18.p.1">The expectation given in an Expect request-header field (see <a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section&nbsp;9.2</a>) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could
    1446          not be met by the next-hop server.
    1447       </p>
    1448       <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
    1449       <p id="rfc.section.8.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
    1450          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.
    1451          User agents <em class="bcp14">SHOULD</em> display any included entity to the user. These response codes are applicable to any request method.
    1452       </p>
    1453       <div id="rfc.iref.60"></div>
    1454       <div id="rfc.iref.s.37"></div>
    1455       <h3 id="rfc.section.8.5.1"><a href="#rfc.section.8.5.1">8.5.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    1456       <p id="rfc.section.8.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    1457       <div id="rfc.iref.61"></div>
    1458       <div id="rfc.iref.s.38"></div>
    1459       <h3 id="rfc.section.8.5.2"><a href="#rfc.section.8.5.2">8.5.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    1460       <p id="rfc.section.8.5.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
    1461          does not recognize the request method and is not capable of supporting it for any resource.
    1462       </p>
    1463       <div id="rfc.iref.62"></div>
    1464       <div id="rfc.iref.s.39"></div>
    1465       <h3 id="rfc.section.8.5.3"><a href="#rfc.section.8.5.3">8.5.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    1466       <p id="rfc.section.8.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
    1467          to fulfill the request.
    1468       </p>
    1469       <div id="rfc.iref.63"></div>
    1470       <div id="rfc.iref.s.40"></div>
    1471       <h3 id="rfc.section.8.5.4"><a href="#rfc.section.8.5.4">8.5.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    1472       <p id="rfc.section.8.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
    1473          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.
    1474       </p>
    1475       <div class="note">
    1476          <p> <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
    1477             to simply refuse the connection.
    1478          </p>
    1479       </div>
    1480       <div id="rfc.iref.64"></div>
    1481       <div id="rfc.iref.s.41"></div>
    1482       <h3 id="rfc.section.8.5.5"><a href="#rfc.section.8.5.5">8.5.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    1483       <p id="rfc.section.8.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
    1484          URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
    1485       </p>
    1486       <div class="note">
    1487          <p> <b>Note:</b> Note to implementors: some deployed proxies are known to return 400 or 500 when DNS lookups time out.
    1488          </p>
    1489       </div>
    1490       <div id="rfc.iref.65"></div>
    1491       <div id="rfc.iref.s.42"></div>
    1492       <h3 id="rfc.section.8.5.6"><a href="#rfc.section.8.5.6">8.5.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    1493       <p id="rfc.section.8.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server
    1494          is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    1495          in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, 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.
    1496       </p>
    1497       <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
    1498       <p id="rfc.section.9.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>
    1499       <p id="rfc.section.9.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
    1500          receives the entity.
    1501       </p>
    1502       <div id="rfc.iref.a.1"></div>
    1503       <div id="rfc.iref.h.2"></div>
    1504       <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
    1505       <p id="rfc.section.9.1.p.1">The "Allow" response-header field lists the set of methods advertised as supported by the resource identified by the request-target.
    1506          The purpose of this field is strictly to inform the recipient of valid methods associated with the resource.
    1507       </p>
    1508       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#header.allow" class="smpl">Allow</a>   = "Allow" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a>
     1657      <div id="header.fields">
     1658         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     1659         <p id="rfc.section.9.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>
     1660         <p id="rfc.section.9.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
     1661            receives the entity.
     1662         </p>
     1663         <div id="header.allow">
     1664            <div id="rfc.iref.a.1"></div>
     1665            <div id="rfc.iref.h.2"></div>
     1666            <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a href="#header.allow">Allow</a></h2>
     1667            <p id="rfc.section.9.1.p.1">The "Allow" response-header field lists the set of methods advertised as supported by the resource identified by the request-target.
     1668               The purpose of this field is strictly to inform the recipient of valid methods associated with the resource.
     1669            </p>
     1670            <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#header.allow" class="smpl">Allow</a>   = "Allow" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a>
    15091671  <a href="#header.allow" class="smpl">Allow-v</a> = #<a href="#method" class="smpl">Method</a>
    15101672</pre><p id="rfc.section.9.1.p.3">Example of use:</p>
    1511       <div id="rfc.figure.u.13"></div><pre class="text">  Allow: GET, HEAD, PUT
     1673            <div id="rfc.figure.u.13"></div><pre class="text">  Allow: GET, HEAD, PUT
    15121674</pre><p id="rfc.section.9.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    1513       <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other
    1514          means of communicating with the origin server.
    1515       </p>
    1516       <div id="rfc.iref.e.1"></div>
    1517       <div id="rfc.iref.h.3"></div>
    1518       <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
    1519       <p id="rfc.section.9.2.p.1">The "Expect" request-header field is used to indicate that particular server behaviors are required by the client.</p>
    1520       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.expect" class="smpl">Expect</a>       = "Expect" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a>
     1675            <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other
     1676               means of communicating with the origin server.
     1677            </p>
     1678         </div>
     1679         <div id="header.expect">
     1680            <div id="rfc.iref.e.1"></div>
     1681            <div id="rfc.iref.h.3"></div>
     1682            <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a href="#header.expect">Expect</a></h2>
     1683            <p id="rfc.section.9.2.p.1">The "Expect" request-header field is used to indicate that particular server behaviors are required by the client.</p>
     1684            <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.expect" class="smpl">Expect</a>       = "Expect" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a>
    15211685  <a href="#header.expect" class="smpl">Expect-v</a>     = 1#<a href="#header.expect" class="smpl">expectation</a>
    15221686 
     
    15261690  <a href="#header.expect" class="smpl">expect-params</a> = ";" <a href="#core.rules" class="smpl">token</a> [ "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) ]
    15271691</pre><p id="rfc.section.9.2.p.3">A server that does not understand or is unable to comply with any of the expectation values in the Expect field of a request <em class="bcp14">MUST</em> respond with appropriate error status. The server <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status if any of the expectations cannot be met or, if there are other problems with
    1528          the request, some other 4xx status.
    1529       </p>
    1530       <p id="rfc.section.9.2.p.4">This header field is defined with extensible syntax to allow for future extensions. If a server receives a request containing
    1531          an Expect field that includes an expectation-extension that it does not support, it <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status.
    1532       </p>
    1533       <p id="rfc.section.9.2.p.5">Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token), and is case-sensitive
    1534          for quoted-string expectation-extensions.
    1535       </p>
    1536       <p id="rfc.section.9.2.p.6">The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy <em class="bcp14">MUST</em> return a 417 (Expectation Failed) status if it receives a request with an expectation that it cannot meet. However, the Expect
    1537          request-header itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
    1538       </p>
    1539       <p id="rfc.section.9.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header.</p>
    1540       <p id="rfc.section.9.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.
    1541       </p>
    1542       <div id="rfc.iref.f.1"></div>
    1543       <div id="rfc.iref.h.4"></div>
    1544       <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
    1545       <p id="rfc.section.9.3.p.1">The "From" request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
    1546       </p>
    1547       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.from" class="smpl">From</a>    = "From" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a>
     1692               the request, some other 4xx status.
     1693            </p>
     1694            <p id="rfc.section.9.2.p.4">This header field is defined with extensible syntax to allow for future extensions. If a server receives a request containing
     1695               an Expect field that includes an expectation-extension that it does not support, it <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status.
     1696            </p>
     1697            <p id="rfc.section.9.2.p.5">Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token), and is case-sensitive
     1698               for quoted-string expectation-extensions.
     1699            </p>
     1700            <p id="rfc.section.9.2.p.6">The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy <em class="bcp14">MUST</em> return a 417 (Expectation Failed) status if it receives a request with an expectation that it cannot meet. However, the Expect
     1701               request-header itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
     1702            </p>
     1703            <p id="rfc.section.9.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header.</p>
     1704            <p id="rfc.section.9.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.
     1705            </p>
     1706         </div>
     1707         <div id="header.from">
     1708            <div id="rfc.iref.f.1"></div>
     1709            <div id="rfc.iref.h.4"></div>
     1710            <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a href="#header.from">From</a></h2>
     1711            <p id="rfc.section.9.3.p.1">The "From" request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="https://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
     1712            </p>
     1713            <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.from" class="smpl">From</a>    = "From" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a>
    15481714  <a href="#header.from" class="smpl">From-v</a>  = <a href="#header.from" class="smpl">mailbox</a>
    15491715 
    1550   <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
     1716  <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="https://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
    15511717</pre><p id="rfc.section.9.3.p.3">An example is:</p>
    1552       <div id="rfc.figure.u.16"></div><pre class="text">  From: webmaster@example.org
     1718            <div id="rfc.figure.u.16"></div><pre class="text">  From: webmaster@example.org
    15531719</pre><p id="rfc.section.9.3.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed
    1554          on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header so that the person responsible for running the robot can be contacted if problems occur on the receiving
    1555          end.
    1556       </p>
    1557       <p id="rfc.section.9.3.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original
    1558          issuer's address <em class="bcp14">SHOULD</em> be used.
    1559       </p>
    1560       <p id="rfc.section.9.3.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's
    1561          security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
    1562          any time prior to a request.
    1563       </p>
    1564       <div id="rfc.iref.l.1"></div>
    1565       <div id="rfc.iref.h.5"></div>
    1566       <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
    1567       <p id="rfc.section.9.4.p.1">The "Location" response-header field is used to identify a newly created resource, or to redirect the recipient to a different
    1568          location for completion of the request.
    1569       </p>
    1570       <p id="rfc.section.9.4.p.2">For 201 (Created) responses, the Location is the URI of the new resource which was created by the request. For 3xx responses,
    1571          the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
    1572       </p>
    1573       <p id="rfc.section.9.4.p.3">The field value consists of a single URI.</p>
    1574       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  <a href="#header.location" class="smpl">Location</a>       = "Location" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a>
     1720               on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header so that the person responsible for running the robot can be contacted if problems occur on the receiving
     1721               end.
     1722            </p>
     1723            <p id="rfc.section.9.3.p.6">The Internet e-mail address in this field <em class="bcp14">MAY</em> be separate from the Internet host which issued the request. For example, when a request is passed through a proxy the original
     1724               issuer's address <em class="bcp14">SHOULD</em> be used.
     1725            </p>
     1726            <p id="rfc.section.9.3.p.7">The client <em class="bcp14">SHOULD NOT</em> send the From header field without the user's approval, as it might conflict with the user's privacy interests or their site's
     1727               security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
     1728               any time prior to a request.
     1729            </p>
     1730         </div>
     1731         <div id="header.location">
     1732            <div id="rfc.iref.l.1"></div>
     1733            <div id="rfc.iref.h.5"></div>
     1734            <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a href="#header.location">Location</a></h2>
     1735            <p id="rfc.section.9.4.p.1">The "Location" response-header field is used to identify a newly created resource, or to redirect the recipient to a different
     1736               location for completion of the request.
     1737            </p>
     1738            <p id="rfc.section.9.4.p.2">For 201 (Created) responses, the Location is the URI of the new resource which was created by the request. For 3xx responses,
     1739               the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
     1740            </p>
     1741            <p id="rfc.section.9.4.p.3">The field value consists of a single URI.</p>
     1742            <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span>  <a href="#header.location" class="smpl">Location</a>       = "Location" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a>
    15751743  <a href="#header.location" class="smpl">Location-v</a>     = <a href="#abnf.dependencies" class="smpl">URI</a>
    15761744</pre><p id="rfc.section.9.4.p.5">An example is:</p>
    1577       <div id="rfc.figure.u.18"></div><pre class="text">  Location: http://www.example.org/pub/WWW/People.html
     1745            <div id="rfc.figure.u.18"></div><pre class="text">  Location: http://www.example.org/pub/WWW/People.html
    15781746</pre><p id="rfc.section.9.4.p.7">There are circumstances in which a fragment identifier in a Location URI would not be appropriate: </p>
    1579       <ul>
    1580          <li>With a 201 Created response, because in this usage the Location header specifies the URI for the entire created resource.</li>
    1581          <li>With 305 Use Proxy.</li>
    1582       </ul>
    1583       <div class="note">
    1584          <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 5.7</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the response.
    1585             It is therefore possible for a response to contain header fields for both Location and Content-Location.
    1586          </p>
    1587       </div>
    1588       <div id="rfc.iref.m.9"></div>
    1589       <div id="rfc.iref.h.6"></div>
    1590       <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
    1591       <p id="rfc.section.9.5.p.1">The "Max-Forwards" request-header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;7.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;7.2</a>) methods to limit the number of times that the request is forwarded by proxies or gateways. This can be useful when the client
    1592          is attempting to trace a request which appears to be failing or looping in mid-chain.
    1593       </p>
    1594       <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a>   = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a>
     1747            <ul>
     1748               <li>With a 201 Created response, because in this usage the Location header specifies the URI for the entire created resource.</li>
     1749               <li>With 305 Use Proxy.</li>
     1750            </ul>
     1751            <div class="note" id="rfc.section.9.4.p.8">
     1752               <p><b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 5.7</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the response.
     1753                  It is therefore possible for a response to contain header fields for both Location and Content-Location.
     1754               </p>
     1755            </div>
     1756         </div>
     1757         <div id="header.max-forwards">
     1758            <div id="rfc.iref.m.9"></div>
     1759            <div id="rfc.iref.h.6"></div>
     1760            <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a href="#header.max-forwards">Max-Forwards</a></h2>
     1761            <p id="rfc.section.9.5.p.1">The "Max-Forwards" request-header field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;7.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;7.2</a>) methods to limit the number of times that the request is forwarded by proxies or gateways. This can be useful when the client
     1762               is attempting to trace a request which appears to be failing or looping in mid-chain.
     1763            </p>
     1764            <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a>   = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a>
    15951765  <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    15961766</pre><p id="rfc.section.9.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message may be forwarded.</p>
    1597       <p id="rfc.section.9.5.p.4">Each proxy or gateway recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
    1598       </p>
    1599       <p id="rfc.section.9.5.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other methods defined by this specification and for any extension methods for which it is not explicitly
    1600          referred to as part of that method definition.
    1601       </p>
    1602       <div id="rfc.iref.r.1"></div>
    1603       <div id="rfc.iref.h.7"></div>
    1604       <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
    1605       <p id="rfc.section.9.6.p.1">The "Referer" [sic] request-header field allows the client to specify the URI of the resource from which the request-target
    1606          was obtained (the "referrer", although the header field is misspelled.).
    1607       </p>
    1608       <p id="rfc.section.9.6.p.2">The Referer header allows servers to generate lists of back-links to resources for interest, logging, optimized caching, etc.
    1609          It also allows obsolete or mistyped links to be traced for maintenance. Some servers use Referer as a means of controlling
    1610          where they allow links from (so-called "deep linking"), but it should be noted that legitimate requests are not required to
    1611          contain a Referer header field.
    1612       </p>
    1613       <p id="rfc.section.9.6.p.3">If the request-target was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the
    1614          Referer field MUST either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not
    1615          apply to sources with non-HTTP URIs (e.g., FTP).
    1616       </p>
    1617       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>
     1767            <p id="rfc.section.9.5.p.4">Each proxy or gateway recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
     1768            </p>
     1769            <p id="rfc.section.9.5.p.5">The Max-Forwards header field <em class="bcp14">MAY</em> be ignored for all other methods defined by this specification and for any extension methods for which it is not explicitly
     1770               referred to as part of that method definition.
     1771            </p>
     1772         </div>
     1773         <div id="header.referer">
     1774            <div id="rfc.iref.r.1"></div>
     1775            <div id="rfc.iref.h.7"></div>
     1776            <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a href="#header.referer">Referer</a></h2>
     1777            <p id="rfc.section.9.6.p.1">The "Referer" [sic] request-header field allows the client to specify the URI of the resource from which the request-target
     1778               was obtained (the "referrer", although the header field is misspelled.).
     1779            </p>
     1780            <p id="rfc.section.9.6.p.2">The Referer header allows servers to generate lists of back-links to resources for interest, logging, optimized caching, etc.
     1781               It also allows obsolete or mistyped links to be traced for maintenance. Some servers use Referer as a means of controlling
     1782               where they allow links from (so-called "deep linking"), but it should be noted that legitimate requests are not required to
     1783               contain a Referer header field.
     1784            </p>
     1785            <p id="rfc.section.9.6.p.3">If the request-target was obtained from a source that does not have its own URI (e.g., input from the user keyboard), the
     1786               Referer field MUST either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not
     1787               apply to sources with non-HTTP URIs (e.g., FTP).
     1788            </p>
     1789            <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>
    16181790  <a href="#header.referer" class="smpl">Referer-v</a>      = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    16191791</pre><p id="rfc.section.9.6.p.5">Example:</p>
    1620       <div id="rfc.figure.u.21"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
     1792            <div id="rfc.figure.u.21"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
    16211793</pre><p id="rfc.section.9.6.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the request-target. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations.
    1622       </p>
    1623       <div id="rfc.iref.r.2"></div>
    1624       <div id="rfc.iref.h.8"></div>
    1625       <h2 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
    1626       <p id="rfc.section.9.7.p.1">The response-header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service
    1627          is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked wait before issuing
    1628          the redirected request.
    1629       </p>
    1630       <p id="rfc.section.9.7.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
    1631       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a>   = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a>
     1794            </p>
     1795         </div>
     1796         <div id="header.retry-after">
     1797            <div id="rfc.iref.r.2"></div>
     1798            <div id="rfc.iref.h.8"></div>
     1799            <h2 id="rfc.section.9.7"><a href="#rfc.section.9.7">9.7</a>&nbsp;<a href="#header.retry-after">Retry-After</a></h2>
     1800            <p id="rfc.section.9.7.p.1">The response-header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service
     1801               is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked wait before issuing
     1802               the redirected request.
     1803            </p>
     1804            <p id="rfc.section.9.7.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
     1805            <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a>   = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a>
    16321806  <a href="#header.retry-after" class="smpl">Retry-After-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
    16331807</pre><div id="rule.delta-seconds">
    1634          <p id="rfc.section.9.7.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p>
    1635       </div>
    1636       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
     1808               <p id="rfc.section.9.7.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p>
     1809            </div>
     1810            <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    16371811</pre><p id="rfc.section.9.7.p.6">Two examples of its use are</p>
    1638       <div id="rfc.figure.u.24"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
     1812            <div id="rfc.figure.u.24"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    16391813  Retry-After: 120
    16401814</pre><p id="rfc.section.9.7.p.8">In the latter example, the delay is 2 minutes.</p>
    1641       <div id="rfc.iref.s.43"></div>
    1642       <div id="rfc.iref.h.9"></div>
    1643       <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
    1644       <p id="rfc.section.9.8.p.1">The "Server" response-header field contains information about the software used by the origin server to handle the request.</p>
    1645       <p id="rfc.section.9.8.p.2">The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
    1646          identifying the application.
    1647       </p>
    1648       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span>  <a href="#header.server" class="smpl">Server</a>         = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a>
     1815         </div>
     1816         <div id="header.server">
     1817            <div id="rfc.iref.s.43"></div>
     1818            <div id="rfc.iref.h.9"></div>
     1819            <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a>&nbsp;<a href="#header.server">Server</a></h2>
     1820            <p id="rfc.section.9.8.p.1">The "Server" response-header field contains information about the software used by the origin server to handle the request.</p>
     1821            <p id="rfc.section.9.8.p.2">The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the server and any significant subproducts. The product tokens are listed in order of their significance for
     1822               identifying the application.
     1823            </p>
     1824            <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span>  <a href="#header.server" class="smpl">Server</a>         = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a>
    16491825  <a href="#header.server" class="smpl">Server-v</a>       = <a href="#abnf.dependencies" class="smpl">product</a>
    16501826                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
    16511827</pre><p id="rfc.section.9.8.p.4">Example:</p>
    1652       <div id="rfc.figure.u.26"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
     1828            <div id="rfc.figure.u.26"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    16531829</pre><p id="rfc.section.9.8.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    1654       </p>
    1655       <div class="note">
    1656          <p> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    1657             against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable
    1658             option.
    1659          </p>
    1660       </div>
    1661       <div id="rfc.iref.u.1"></div>
    1662       <div id="rfc.iref.h.10"></div>
    1663       <h2 id="rfc.section.9.9"><a href="#rfc.section.9.9">9.9</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>
    1664       <p id="rfc.section.9.9.p.1">The "User-Agent" request-header field contains information about the user agent originating the request. This is for statistical
    1665          purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses
    1666          to avoid particular user agent limitations.
    1667       </p>
    1668       <p id="rfc.section.9.9.p.2">User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and any subproducts which form a significant part of the user agent. By convention, the product tokens
    1669          are listed in order of their significance for identifying the application.
    1670       </p>
    1671       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a>     = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a>
     1830            </p>
     1831            <div class="note" id="rfc.section.9.8.p.7">
     1832               <p><b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
     1833                  against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable
     1834                  option.
     1835               </p>
     1836            </div>
     1837         </div>
     1838         <div id="header.user-agent">
     1839            <div id="rfc.iref.u.1"></div>
     1840            <div id="rfc.iref.h.10"></div>
     1841            <h2 id="rfc.section.9.9"><a href="#rfc.section.9.9">9.9</a>&nbsp;<a href="#header.user-agent">User-Agent</a></h2>
     1842            <p id="rfc.section.9.9.p.1">The "User-Agent" request-header field contains information about the user agent originating the request. This is for statistical
     1843               purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses
     1844               to avoid particular user agent limitations.
     1845            </p>
     1846            <p id="rfc.section.9.9.p.2">User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 6.3</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments (<a href="p1-messaging.html#header.fields" title="Header Fields">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and any subproducts which form a significant part of the user agent. By convention, the product tokens
     1847               are listed in order of their significance for identifying the application.
     1848            </p>
     1849            <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a>     = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a>
    16721850  <a href="#header.user-agent" class="smpl">User-Agent-v</a>   = <a href="#abnf.dependencies" class="smpl">product</a>
    16731851                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
    16741852</pre><p id="rfc.section.9.9.p.4">Example:</p>
    1675       <div id="rfc.figure.u.28"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    1676 </pre><h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    1677       <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
    1678       <p id="rfc.section.10.1.p.1">The registration procedure for HTTP Methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.1</a> of this document.
    1679       </p>
    1680       <p id="rfc.section.10.1.p.2">The HTTP Method Registry located at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; should be populated with the registrations below:
    1681       </p>
    1682       <div id="rfc.table.1">
    1683          <div id="iana.method.registration.table"></div>
    1684          <table class="tt full left" cellpadding="3" cellspacing="0">
    1685             <thead>
    1686                <tr>
    1687                   <th>Method</th>
    1688                   <th>Safe</th>
    1689                   <th>Reference</th>
    1690                </tr>
    1691             </thead>
    1692             <tbody>
    1693                <tr>
    1694                   <td class="left">CONNECT</td>
    1695                   <td class="left">no</td>
    1696                   <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;7.9</a>
    1697                   </td>
    1698                </tr>
    1699                <tr>
    1700                   <td class="left">DELETE</td>
    1701                   <td class="left">no</td>
    1702                   <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;7.7</a>
    1703                   </td>
    1704                </tr>
    1705                <tr>
    1706                   <td class="left">GET</td>
    1707                   <td class="left">yes</td>
    1708                   <td class="left"> <a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;7.3</a>
    1709                   </td>
    1710                </tr>
    1711                <tr>
    1712                   <td class="left">HEAD</td>
    1713                   <td class="left">yes</td>
    1714                   <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;7.4</a>
    1715                   </td>
    1716                </tr>
    1717                <tr>
    1718                   <td class="left">OPTIONS</td>
    1719                   <td class="left">yes</td>
    1720                   <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;7.2</a>
    1721                   </td>
    1722                </tr>
    1723                <tr>
    1724                   <td class="left">POST</td>
    1725                   <td class="left">no</td>
    1726                   <td class="left"> <a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;7.5</a>
    1727                   </td>
    1728                </tr>
    1729                <tr>
    1730                   <td class="left">PUT</td>
    1731                   <td class="left">no</td>
    1732                   <td class="left"> <a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;7.6</a>
    1733                   </td>
    1734                </tr>
    1735                <tr>
    1736                   <td class="left">TRACE</td>
    1737                   <td class="left">yes</td>
    1738                   <td class="left"> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;7.8</a>
    1739                   </td>
    1740                </tr>
    1741             </tbody>
    1742          </table>
     1853            <div id="rfc.figure.u.28"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     1854</pre></div>
    17431855      </div>
    1744       <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
    1745       <p id="rfc.section.10.2.p.1">The registration procedure for HTTP Status Codes -- previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> -- is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.1</a> of this document.
    1746       </p>
    1747       <p id="rfc.section.10.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; should be updated with the registrations below:
    1748       </p>
    1749       <div id="rfc.table.2">
    1750          <div id="iana.status.code.registration.table"></div>
    1751          <table class="tt full left" cellpadding="3" cellspacing="0">
    1752             <thead>
    1753                <tr>
    1754                   <th>Value</th>
    1755                   <th>Description</th>
    1756                   <th>Reference</th>
    1757                </tr>
    1758             </thead>
    1759             <tbody>
    1760                <tr>
    1761                   <td class="left">100</td>
    1762                   <td class="left">Continue</td>
    1763                   <td class="left"> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;8.1.1</a>
    1764                   </td>
    1765                </tr>
    1766                <tr>
    1767                   <td class="left">101</td>
    1768                   <td class="left">Switching Protocols</td>
    1769                   <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;8.1.2</a>
    1770                   </td>
    1771                </tr>
    1772                <tr>
    1773                   <td class="left">200</td>
    1774                   <td class="left">OK</td>
    1775                   <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;8.2.1</a>
    1776                   </td>
    1777                </tr>
    1778                <tr>
    1779                   <td class="left">201</td>
    1780                   <td class="left">Created</td>
    1781                   <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;8.2.2</a>
    1782                   </td>
    1783                </tr>
    1784                <tr>
    1785                   <td class="left">202</td>
    1786                   <td class="left">Accepted</td>
    1787                   <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;8.2.3</a>
    1788                   </td>
    1789                </tr>
    1790                <tr>
    1791                   <td class="left">203</td>
    1792                   <td class="left">Non-Authoritative Information</td>
    1793                   <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;8.2.4</a>
    1794                   </td>
    1795                </tr>
    1796                <tr>
    1797                   <td class="left">204</td>
    1798                   <td class="left">No Content</td>
    1799                   <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;8.2.5</a>
    1800                   </td>
    1801                </tr>
    1802                <tr>
    1803                   <td class="left">205</td>
    1804                   <td class="left">Reset Content</td>
    1805                   <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;8.2.6</a>
    1806                   </td>
    1807                </tr>
    1808                <tr>
    1809                   <td class="left">300</td>
    1810                   <td class="left">Multiple Choices</td>
    1811                   <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;8.3.1</a>
    1812                   </td>
    1813                </tr>
    1814                <tr>
    1815                   <td class="left">301</td>
    1816                   <td class="left">Moved Permanently</td>
    1817                   <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;8.3.2</a>
    1818                   </td>
    1819                </tr>
    1820                <tr>
    1821                   <td class="left">302</td>
    1822                   <td class="left">Found</td>
    1823                   <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;8.3.3</a>
    1824                   </td>
    1825                </tr>
    1826                <tr>
    1827                   <td class="left">303</td>
    1828                   <td class="left">See Other</td>
    1829                   <td class="left"> <a href="#status.303" id="rfc.xref.status.303.3" title="303 See Other">Section&nbsp;8.3.4</a>
    1830                   </td>
    1831                </tr>
    1832                <tr>
    1833                   <td class="left">305</td>
    1834                   <td class="left">Use Proxy</td>
    1835                   <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;8.3.6</a>
    1836                   </td>
    1837                </tr>
    1838                <tr>
    1839                   <td class="left">306</td>
    1840                   <td class="left">(Unused)</td>
    1841                   <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;8.3.7</a>
    1842                   </td>
    1843                </tr>
    1844                <tr>
    1845                   <td class="left">307</td>
    1846                   <td class="left">Temporary Redirect</td>
    1847                   <td class="left"> <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">Section&nbsp;8.3.8</a>
    1848                   </td>
    1849                </tr>
    1850                <tr>
    1851                   <td class="left">400</td>
    1852                   <td class="left">Bad Request</td>
    1853                   <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;8.4.1</a>
    1854                   </td>
    1855                </tr>
    1856                <tr>
    1857                   <td class="left">402</td>
    1858                   <td class="left">Payment Required</td>
    1859                   <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;8.4.3</a>
    1860                   </td>
    1861                </tr>
    1862                <tr>
    1863                   <td class="left">403</td>
    1864                   <td class="left">Forbidden</td>
    1865                   <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;8.4.4</a>
    1866                   </td>
    1867                </tr>
    1868                <tr>
    1869                   <td class="left">404</td>
    1870                   <td class="left">Not Found</td>
    1871                   <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;8.4.5</a>
    1872                   </td>
    1873                </tr>
    1874                <tr>
    1875                   <td class="left">405</td>
    1876                   <td class="left">Method Not Allowed</td>
    1877                   <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;8.4.6</a>
    1878                   </td>
    1879                </tr>
    1880                <tr>
    1881                   <td class="left">406</td>
    1882                   <td class="left">Not Acceptable</td>
    1883                   <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;8.4.7</a>
    1884                   </td>
    1885                </tr>
    1886                <tr>
    1887                   <td class="left">407</td>
    1888                   <td class="left">Proxy Authentication Required</td>
    1889                   <td class="left"> <a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;8.4.8</a>
    1890                   </td>
    1891                </tr>
    1892                <tr>
    1893                   <td class="left">408</td>
    1894                   <td class="left">Request Timeout</td>
    1895                   <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;8.4.9</a>
    1896                   </td>
    1897                </tr>
    1898                <tr>
    1899                   <td class="left">409</td>
    1900                   <td class="left">Conflict</td>
    1901                   <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;8.4.10</a>
    1902                   </td>
    1903                </tr>
    1904                <tr>
    1905                   <td class="left">410</td>
    1906                   <td class="left">Gone</td>
    1907                   <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;8.4.11</a>
    1908                   </td>
    1909                </tr>
    1910                <tr>
    1911                   <td class="left">411</td>
    1912                   <td class="left">Length Required</td>
    1913                   <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;8.4.12</a>
    1914                   </td>
    1915                </tr>
    1916                <tr>
    1917                   <td class="left">413</td>
    1918                   <td class="left">Request Entity Too Large</td>
    1919                   <td class="left"> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Entity Too Large">Section&nbsp;8.4.14</a>
    1920                   </td>
    1921                </tr>
    1922                <tr>
    1923                   <td class="left">414</td>
    1924                   <td class="left">URI Too Long</td>
    1925                   <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;8.4.15</a>
    1926                   </td>
    1927                </tr>
    1928                <tr>
    1929                   <td class="left">415</td>
    1930                   <td class="left">Unsupported Media Type</td>
    1931                   <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;8.4.16</a>
    1932                   </td>
    1933                </tr>
    1934                <tr>
    1935                   <td class="left">417</td>
    1936                   <td class="left">Expectation Failed</td>
    1937                   <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;8.4.18</a>
    1938                   </td>
    1939                </tr>
    1940                <tr>
    1941                   <td class="left">500</td>
    1942                   <td class="left">Internal Server Error</td>
    1943                   <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;8.5.1</a>
    1944                   </td>
    1945                </tr>
    1946                <tr>
    1947                   <td class="left">501</td>
    1948                   <td class="left">Not Implemented</td>
    1949                   <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;8.5.2</a>
    1950                   </td>
    1951                </tr>
    1952                <tr>
    1953                   <td class="left">502</td>
    1954                   <td class="left">Bad Gateway</td>
    1955                   <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;8.5.3</a>
    1956                   </td>
    1957                </tr>
    1958                <tr>
    1959                   <td class="left">503</td>
    1960                   <td class="left">Service Unavailable</td>
    1961                   <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;8.5.4</a>
    1962                   </td>
    1963                </tr>
    1964                <tr>
    1965                   <td class="left">504</td>
    1966                   <td class="left">Gateway Timeout</td>
    1967                   <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>
    1968                   </td>
    1969                </tr>
    1970                <tr>
    1971                   <td class="left">505</td>
    1972                   <td class="left">HTTP Version Not Supported</td>
    1973                   <td class="left"> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;8.5.6</a>
    1974                   </td>
    1975                </tr>
    1976             </tbody>
    1977          </table>
     1856      <div id="IANA.considerations">
     1857         <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     1858         <div id="method.registration">
     1859            <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a href="#method.registration">Method Registry</a></h2>
     1860            <p id="rfc.section.10.1.p.1">The registration procedure for HTTP Methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;2.1</a> of this document.
     1861            </p>
     1862            <p id="rfc.section.10.1.p.2">The HTTP Method Registry located at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; should be populated with the registrations below:
     1863            </p>
     1864            <div id="rfc.table.1">
     1865               <div id="iana.method.registration.table"></div>
     1866               <table class="tt full left" cellpadding="3" cellspacing="0">
     1867                  <thead>
     1868                     <tr>
     1869                        <th>Method</th>
     1870                        <th>Safe</th>
     1871                        <th>Reference</th>
     1872                     </tr>
     1873                  </thead>
     1874                  <tbody>
     1875                     <tr>
     1876                        <td class="left">CONNECT</td>
     1877                        <td class="left">no</td>
     1878                        <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;7.9</a>
     1879                        </td>
     1880                     </tr>
     1881                     <tr>
     1882                        <td class="left">DELETE</td>
     1883                        <td class="left">no</td>
     1884                        <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;7.7</a>
     1885                        </td>
     1886                     </tr>
     1887                     <tr>
     1888                        <td class="left">GET</td>
     1889                        <td class="left">yes</td>
     1890                        <td class="left"><a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;7.3</a>
     1891                        </td>
     1892                     </tr>
     1893                     <tr>
     1894                        <td class="left">HEAD</td>
     1895                        <td class="left">yes</td>
     1896                        <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;7.4</a>
     1897                        </td>
     1898                     </tr>
     1899                     <tr>
     1900                        <td class="left">OPTIONS</td>
     1901                        <td class="left">yes</td>
     1902                        <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;7.2</a>
     1903                        </td>
     1904                     </tr>
     1905                     <tr>
     1906                        <td class="left">POST</td>
     1907                        <td class="left">no</td>
     1908                        <td class="left"><a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;7.5</a>
     1909                        </td>
     1910                     </tr>
     1911                     <tr>
     1912                        <td class="left">PUT</td>
     1913                        <td class="left">no</td>
     1914                        <td class="left"><a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;7.6</a>
     1915                        </td>
     1916                     </tr>
     1917                     <tr>
     1918                        <td class="left">TRACE</td>
     1919                        <td class="left">yes</td>
     1920                        <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;7.8</a>
     1921                        </td>
     1922                     </tr>
     1923                  </tbody>
     1924               </table>
     1925            </div>
     1926         </div>
     1927         <div id="status.code.registration">
     1928            <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a href="#status.code.registration">Status Code Registry</a></h2>
     1929            <p id="rfc.section.10.2.p.1">The registration procedure for HTTP Status Codes -- previously defined in <a href="https://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> -- is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.1</a> of this document.
     1930            </p>
     1931            <p id="rfc.section.10.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; should be updated with the registrations below:
     1932            </p>
     1933            <div id="rfc.table.2">
     1934               <div id="iana.status.code.registration.table"></div>
     1935               <table class="tt full left" cellpadding="3" cellspacing="0">
     1936                  <thead>
     1937                     <tr>
     1938                        <th>Value</th>
     1939                        <th>Description</th>
     1940                        <th>Reference</th>
     1941                     </tr>
     1942                  </thead>
     1943                  <tbody>
     1944                     <tr>
     1945                        <td class="left">100</td>
     1946                        <td class="left">Continue</td>
     1947                        <td class="left"><a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;8.1.1</a>
     1948                        </td>
     1949                     </tr>
     1950                     <tr>
     1951                        <td class="left">101</td>
     1952                        <td class="left">Switching Protocols</td>
     1953                        <td class="left"><a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;8.1.2</a>
     1954                        </td>
     1955                     </tr>
     1956                     <tr>
     1957                        <td class="left">200</td>
     1958                        <td class="left">OK</td>
     1959                        <td class="left"><a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;8.2.1</a>
     1960                        </td>
     1961                     </tr>
     1962                     <tr>
     1963                        <td class="left">201</td>
     1964                        <td class="left">Created</td>
     1965                        <td class="left"><a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;8.2.2</a>
     1966                        </td>
     1967                     </tr>
     1968                     <tr>
     1969                        <td class="left">202</td>
     1970                        <td class="left">Accepted</td>
     1971                        <td class="left"><a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;8.2.3</a>
     1972                        </td>
     1973                     </tr>
     1974                     <tr>
     1975                        <td class="left">203</td>
     1976                        <td class="left">Non-Authoritative Information</td>
     1977                        <td class="left"><a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;8.2.4</a>
     1978                        </td>
     1979                     </tr>
     1980                     <tr>
     1981                        <td class="left">204</td>
     1982                        <td class="left">No Content</td>
     1983                        <td class="left"><a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;8.2.5</a>
     1984                        </td>
     1985                     </tr>
     1986                     <tr>
     1987                        <td class="left">205</td>
     1988                        <td class="left">Reset Content</td>
     1989                        <td class="left"><a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;8.2.6</a>
     1990                        </td>
     1991                     </tr>
     1992                     <tr>
     1993                        <td class="left">300</td>
     1994                        <td class="left">Multiple Choices</td>
     1995                        <td class="left"><a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;8.3.1</a>
     1996                        </td>
     1997                     </tr>
     1998                     <tr>
     1999                        <td class="left">301</td>
     2000                        <td class="left">Moved Permanently</td>
     2001                        <td class="left"><a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;8.3.2</a>
     2002                        </td>
     2003                     </tr>
     2004                     <tr>
     2005                        <td class="left">302</td>
     2006                        <td class="left">Found</td>
     2007                        <td class="left"><a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;8.3.3</a>
     2008                        </td>
     2009                     </tr>
     2010                     <tr>
     2011                        <td class="left">303</td>
     2012                        <td class="left">See Other</td>
     2013                        <td class="left"><a href="#status.303" id="rfc.xref.status.303.3" title="303 See Other">Section&nbsp;8.3.4</a>
     2014                        </td>
     2015                     </tr>
     2016                     <tr>
     2017                        <td class="left">305</td>
     2018                        <td class="left">Use Proxy</td>
     2019                        <td class="left"><a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;8.3.6</a>
     2020                        </td>
     2021                     </tr>
     2022                     <tr>
     2023                        <td class="left">306</td>
     2024                        <td class="left">(Unused)</td>
     2025                        <td class="left"><a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;8.3.7</a>
     2026                        </td>
     2027                     </tr>
     2028                     <tr>
     2029                        <td class="left">307</td>
     2030                        <td class="left">Temporary Redirect</td>
     2031                        <td class="left"><a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">Section&nbsp;8.3.8</a>
     2032                        </td>
     2033                     </tr>
     2034                     <tr>
     2035                        <td class="left">400</td>
     2036                        <td class="left">Bad Request</td>
     2037                        <td class="left"><a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;8.4.1</a>
     2038                        </td>
     2039                     </tr>
     2040                     <tr>
     2041                        <td class="left">402</td>
     2042                        <td class="left">Payment Required</td>
     2043                        <td class="left"><a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;8.4.3</a>
     2044                        </td>
     2045                     </tr>
     2046                     <tr>
     2047                        <td class="left">403</td>
     2048                        <td class="left">Forbidden</td>
     2049                        <td class="left"><a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;8.4.4</a>
     2050                        </td>
     2051                     </tr>
     2052                     <tr>
     2053                        <td class="left">404</td>
     2054                        <td class="left">Not Found</td>
     2055                        <td class="left"><a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;8.4.5</a>
     2056                        </td>
     2057                     </tr>
     2058                     <tr>
     2059                        <td class="left">405</td>
     2060                        <td class="left">Method Not Allowed</td>
     2061                        <td class="left"><a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;8.4.6</a>
     2062                        </td>
     2063                     </tr>
     2064                     <tr>
     2065                        <td class="left">406</td>
     2066                        <td class="left">Not Acceptable</td>
     2067                        <td class="left"><a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;8.4.7</a>
     2068                        </td>
     2069                     </tr>
     2070                     <tr>
     2071                        <td class="left">407</td>
     2072                        <td class="left">Proxy Authentication Required</td>
     2073                        <td class="left"><a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;8.4.8</a>
     2074                        </td>
     2075                     </tr>
     2076                     <tr>
     2077                        <td class="left">408</td>
     2078                        <td class="left">Request Timeout</td>
     2079                        <td class="left"><a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;8.4.9</a>
     2080                        </td>
     2081                     </tr>
     2082                     <tr>
     2083                        <td class="left">409</td>
     2084                        <td class="left">Conflict</td>
     2085                        <td class="left"><a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;8.4.10</a>
     2086                        </td>
     2087                     </tr>
     2088                     <tr>
     2089                        <td class="left">410</td>
     2090                        <td class="left">Gone</td>
     2091                        <td class="left"><a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;8.4.11</a>
     2092                        </td>
     2093                     </tr>
     2094                     <tr>
     2095                        <td class="left">411</td>
     2096                        <td class="left">Length Required</td>
     2097                        <td class="left"><a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;8.4.12</a>
     2098                        </td>
     2099                     </tr>
     2100                     <tr>
     2101                        <td class="left">413</td>
     2102                        <td class="left">Request Entity Too Large</td>
     2103                        <td class="left"><a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Entity Too Large">Section&nbsp;8.4.14</a>
     2104                        </td>
     2105                     </tr>
     2106                     <tr>
     2107                        <td class="left">414</td>
     2108                        <td class="left">URI Too Long</td>
     2109                        <td class="left"><a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;8.4.15</a>
     2110                        </td>
     2111                     </tr>
     2112                     <tr>
     2113                        <td class="left">415</td>
     2114                        <td class="left">Unsupported Media Type</td>
     2115                        <td class="left"><a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;8.4.16</a>
     2116                        </td>
     2117                     </tr>
     2118                     <tr>
     2119                        <td class="left">417</td>
     2120                        <td class="left">Expectation Failed</td>
     2121                        <td class="left"><a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;8.4.18</a>
     2122                        </td>
     2123                     </tr>
     2124                     <tr>
     2125                        <td class="left">500</td>
     2126                        <td class="left">Internal Server Error</td>
     2127                        <td class="left"><a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;8.5.1</a>
     2128                        </td>
     2129                     </tr>
     2130                     <tr>
     2131                        <td class="left">501</td>
     2132                        <td class="left">Not Implemented</td>
     2133                        <td class="left"><a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;8.5.2</a>
     2134                        </td>
     2135                     </tr>
     2136                     <tr>
     2137                        <td class="left">502</td>
     2138                        <td class="left">Bad Gateway</td>
     2139                        <td class="left"><a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;8.5.3</a>
     2140                        </td>
     2141                     </tr>
     2142                     <tr>
     2143                        <td class="left">503</td>
     2144                        <td class="left">Service Unavailable</td>
     2145                        <td class="left"><a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;8.5.4</a>
     2146                        </td>
     2147                     </tr>
     2148                     <tr>
     2149                        <td class="left">504</td>
     2150                        <td class="left">Gateway Timeout</td>
     2151                        <td class="left"><a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>
     2152                        </td>
     2153                     </tr>
     2154                     <tr>
     2155                        <td class="left">505</td>
     2156                        <td class="left">HTTP Version Not Supported</td>
     2157                        <td class="left"><a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;8.5.6</a>
     2158                        </td>
     2159                     </tr>
     2160                  </tbody>
     2161               </table>
     2162            </div>
     2163         </div>
     2164         <div id="message.header.registration">
     2165            <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a href="#message.header.registration">Message Header Registration</a></h2>
     2166            <p id="rfc.section.10.3.p.1">The Message Header Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
     2167            </p>
     2168            <div id="rfc.table.3">
     2169               <div id="iana.header.registration.table"></div>
     2170               <table class="tt full left" cellpadding="3" cellspacing="0">
     2171                  <thead>
     2172                     <tr>
     2173                        <th>Header Field Name</th>
     2174                        <th>Protocol</th>
     2175                        <th>Status</th>
     2176                        <th>Reference</th>
     2177                     </tr>
     2178                  </thead>
     2179                  <tbody>
     2180                     <tr>
     2181                        <td class="left">Allow</td>
     2182                        <td class="left">http</td>
     2183                        <td class="left">standard</td>
     2184                        <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;9.1</a>
     2185                        </td>
     2186                     </tr>
     2187                     <tr>
     2188                        <td class="left">Expect</td>
     2189                        <td class="left">http</td>
     2190                        <td class="left">standard</td>
     2191                        <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;9.2</a>
     2192                        </td>
     2193                     </tr>
     2194                     <tr>
     2195                        <td class="left">From</td>
     2196                        <td class="left">http</td>
     2197                        <td class="left">standard</td>
     2198                        <td class="left"><a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;9.3</a>
     2199                        </td>
     2200                     </tr>
     2201                     <tr>
     2202                        <td class="left">Location</td>
     2203                        <td class="left">http</td>
     2204                        <td class="left">standard</td>
     2205                        <td class="left"><a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;9.4</a>
     2206                        </td>
     2207                     </tr>
     2208                     <tr>
     2209                        <td class="left">Max-Forwards</td>
     2210                        <td class="left">http</td>
     2211                        <td class="left">standard</td>
     2212                        <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;9.5</a>
     2213                        </td>
     2214                     </tr>
     2215                     <tr>
     2216                        <td class="left">Referer</td>
     2217                        <td class="left">http</td>
     2218                        <td class="left">standard</td>
     2219                        <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;9.6</a>
     2220                        </td>
     2221                     </tr>
     2222                     <tr>
     2223                        <td class="left">Retry-After</td>
     2224                        <td class="left">http</td>
     2225                        <td class="left">standard</td>
     2226                        <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;9.7</a>
     2227                        </td>
     2228                     </tr>
     2229                     <tr>
     2230                        <td class="left">Server</td>
     2231                        <td class="left">http</td>
     2232                        <td class="left">standard</td>
     2233                        <td class="left"><a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;9.8</a>
     2234                        </td>
     2235                     </tr>
     2236                     <tr>
     2237                        <td class="left">User-Agent</td>
     2238                        <td class="left">http</td>
     2239                        <td class="left">standard</td>
     2240                        <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;9.9</a>
     2241                        </td>
     2242                     </tr>
     2243                  </tbody>
     2244               </table>
     2245            </div>
     2246            <p id="rfc.section.10.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     2247         </div>
    19782248      </div>
    1979       <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>
    1980       <p id="rfc.section.10.3.p.1">The Message Header Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
    1981       </p>
    1982       <div id="rfc.table.3">
    1983          <div id="iana.header.registration.table"></div>
    1984          <table class="tt full left" cellpadding="3" cellspacing="0">
    1985             <thead>
    1986                <tr>
    1987                   <th>Header Field Name</th>
    1988                   <th>Protocol</th>
    1989                   <th>Status</th>
    1990                   <th>Reference</th>
    1991                </tr>
    1992             </thead>
    1993             <tbody>
    1994                <tr>
    1995                   <td class="left">Allow</td>
    1996                   <td class="left">http</td>
    1997                   <td class="left">standard</td>
    1998                   <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;9.1</a>
    1999                   </td>
    2000                </tr>
    2001                <tr>
    2002                   <td class="left">Expect</td>
    2003                   <td class="left">http</td>
    2004                   <td class="left">standard</td>
    2005                   <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;9.2</a>
    2006                   </td>
    2007                </tr>
    2008                <tr>
    2009                   <td class="left">From</td>
    2010                   <td class="left">http</td>
    2011                   <td class="left">standard</td>
    2012                   <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;9.3</a>
    2013                   </td>
    2014                </tr>
    2015                <tr>
    2016                   <td class="left">Location</td>
    2017                   <td class="left">http</td>
    2018                   <td class="left">standard</td>
    2019                   <td class="left"> <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;9.4</a>
    2020                   </td>
    2021                </tr>
    2022                <tr>
    2023                   <td class="left">Max-Forwards</td>
    2024                   <td class="left">http</td>
    2025                   <td class="left">standard</td>
    2026                   <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;9.5</a>
    2027                   </td>
    2028                </tr>
    2029                <tr>
    2030                   <td class="left">Referer</td>
    2031                   <td class="left">http</td>
    2032                   <td class="left">standard</td>
    2033                   <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;9.6</a>
    2034                   </td>
    2035                </tr>
    2036                <tr>
    2037                   <td class="left">Retry-After</td>
    2038                   <td class="left">http</td>
    2039                   <td class="left">standard</td>
    2040                   <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;9.7</a>
    2041                   </td>
    2042                </tr>
    2043                <tr>
    2044                   <td class="left">Server</td>
    2045                   <td class="left">http</td>
    2046                   <td class="left">standard</td>
    2047                   <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;9.8</a>
    2048                   </td>
    2049                </tr>
    2050                <tr>
    2051                   <td class="left">User-Agent</td>
    2052                   <td class="left">http</td>
    2053                   <td class="left">standard</td>
    2054                   <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;9.9</a>
    2055                   </td>
    2056                </tr>
    2057             </tbody>
    2058          </table>
     2249      <div id="security.considerations">
     2250         <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     2251         <p id="rfc.section.11.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
     2252            as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
     2253            make some suggestions for reducing security risks.
     2254         </p>
     2255         <div id="security.sensitive">
     2256            <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></h2>
     2257            <p id="rfc.section.11.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
     2258               a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
     2259               Therefore, applications <em class="bcp14">SHOULD</em> supply as much control over this information as possible to the provider of that information. Four header fields are worth
     2260               special mention in this context: Server, Via, Referer and From.
     2261            </p>
     2262            <p id="rfc.section.11.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
     2263               against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option.
     2264            </p>
     2265            <p id="rfc.section.11.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
     2266               they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall.
     2267            </p>
     2268            <p id="rfc.section.11.1.p.4">The Referer header allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its power
     2269               can be abused if user details are not separated from the information contained in the Referer. Even when the personal information
     2270               has been removed, the Referer header might indicate a private document's URI whose publication would be inappropriate.
     2271            </p>
     2272            <p id="rfc.section.11.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and
     2273               hence it <em class="bcp14">SHOULD NOT</em> be transmitted without the user being able to disable, enable, and modify the contents of the field. The user <em class="bcp14">MUST</em> be able to set the contents of this field within a user preference or application defaults configuration.
     2274            </p>
     2275            <p id="rfc.section.11.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
     2276               of From and Referer information.
     2277            </p>
     2278            <p id="rfc.section.11.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;9.9</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;9.8</a>) header fields can sometimes be used to determine that a specific client or server have a particular security hole which
     2279               might be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently
     2280               has no better mechanism.
     2281            </p>
     2282            <p id="rfc.section.11.1.p.8">Some methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;7.8</a>) may expose information sent in request headers in the response entity. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials and other headers that might be used to collect
     2283               data from the client.
     2284            </p>
     2285         </div>
     2286         <div id="encoding.sensitive.information.in.uris">
     2287            <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
     2288            <p id="rfc.section.11.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
     2289               recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could
     2290               have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From
     2291               information.
     2292            </p>
     2293            <p id="rfc.section.11.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
     2294            </p>
     2295            <p id="rfc.section.11.2.p.3">Authors of services should not use GET-based forms for the submission of sensitive data because that data will be encoded
     2296               in the Request-target. Many existing servers, proxies, and user agents log or display the Request-target in places where it
     2297               might be visible to third parties. Such services can use POST-based form submission instead.
     2298            </p>
     2299         </div>
     2300         <div id="location.spoofing">
     2301            <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a href="#location.spoofing">Location Headers and Spoofing</a></h2>
     2302            <p id="rfc.section.11.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location headers in responses that are generated under control of said organizations
     2303               to make sure that they do not attempt to invalidate resources over which they have no authority.
     2304            </p>
     2305         </div>
    20592306      </div>
    2060       <p id="rfc.section.10.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    2061       <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    2062       <p id="rfc.section.11.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
    2063          as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    2064          make some suggestions for reducing security risks.
    2065       </p>
    2066       <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
    2067       <p id="rfc.section.11.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
    2068          a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
    2069          Therefore, applications <em class="bcp14">SHOULD</em> supply as much control over this information as possible to the provider of that information. Four header fields are worth
    2070          special mention in this context: Server, Via, Referer and From.
    2071       </p>
    2072       <p id="rfc.section.11.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    2073          against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option.
    2074       </p>
    2075       <p id="rfc.section.11.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
    2076          they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall.
    2077       </p>
    2078       <p id="rfc.section.11.1.p.4">The Referer header allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its power
    2079          can be abused if user details are not separated from the information contained in the Referer. Even when the personal information
    2080          has been removed, the Referer header might indicate a private document's URI whose publication would be inappropriate.
    2081       </p>
    2082       <p id="rfc.section.11.1.p.5">The information sent in the From field might conflict with the user's privacy interests or their site's security policy, and
    2083          hence it <em class="bcp14">SHOULD NOT</em> be transmitted without the user being able to disable, enable, and modify the contents of the field. The user <em class="bcp14">MUST</em> be able to set the contents of this field within a user preference or application defaults configuration.
    2084       </p>
    2085       <p id="rfc.section.11.1.p.6">We suggest, though do not require, that a convenient toggle interface be provided for the user to enable or disable the sending
    2086          of From and Referer information.
    2087       </p>
    2088       <p id="rfc.section.11.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;9.9</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;9.8</a>) header fields can sometimes be used to determine that a specific client or server have a particular security hole which
    2089          might be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently
    2090          has no better mechanism.
    2091       </p>
    2092       <p id="rfc.section.11.1.p.8">Some methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;7.8</a>) may expose information sent in request headers in the response entity. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials and other headers that might be used to collect
    2093          data from the client.
    2094       </p>
    2095       <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
    2096       <p id="rfc.section.11.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
    2097          recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could
    2098          have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From
    2099          information.
    2100       </p>
    2101       <p id="rfc.section.11.2.p.2">Clients <em class="bcp14">SHOULD NOT</em> include a Referer header field in a (non-secure) HTTP request if the referring page was transferred with a secure protocol.
    2102       </p>
    2103       <p id="rfc.section.11.2.p.3">Authors of services should not use GET-based forms for the submission of sensitive data because that data will be encoded
    2104          in the Request-target. Many existing servers, proxies, and user agents log or display the Request-target in places where it
    2105          might be visible to third parties. Such services can use POST-based form submission instead.
    2106       </p>
    2107       <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a id="location.spoofing" href="#location.spoofing">Location Headers and Spoofing</a></h2>
    2108       <p id="rfc.section.11.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location headers in responses that are generated under control of said organizations
    2109          to make sure that they do not attempt to invalidate resources over which they have no authority.
    2110       </p>
    2111       <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
     2307      <div id="ack">
     2308         <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     2309      </div>
    21122310      <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References
    21132311      </h1>
    21142312      <h2 id="rfc.references.1"><a href="#rfc.section.13.1" id="rfc.section.13.1">13.1</a> Normative References
    21152313      </h2>
    2116       <table>               
     2314      <table>
    21172315         <tr>
    21182316            <td class="reference"><b id="Part1">[Part1]</b></td>
    2119             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-08">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-08 (work in progress), October&nbsp;2009.
     2317            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-08">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-08 (work in progress), October&nbsp;2009.
    21202318            </td>
    21212319         </tr>
    21222320         <tr>
    21232321            <td class="reference"><b id="Part3">[Part3]</b></td>
    2124             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-08">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-08 (work in progress), October&nbsp;2009.
     2322            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-08">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-08 (work in progress), October&nbsp;2009.
    21252323            </td>
    21262324         </tr>
    21272325         <tr>
    21282326            <td class="reference"><b id="Part4">[Part4]</b></td>
    2129             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-08">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-08 (work in progress), October&nbsp;2009.
     2327            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-08">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-08 (work in progress), October&nbsp;2009.
    21302328            </td>
    21312329         </tr>
    21322330         <tr>
    21332331            <td class="reference"><b id="Part5">[Part5]</b></td>
    2134             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-08">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-08 (work in progress), October&nbsp;2009.
     2332            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-08">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-08 (work in progress), October&nbsp;2009.
    21352333            </td>
    21362334         </tr>
    21372335         <tr>
    21382336            <td class="reference"><b id="Part6">[Part6]</b></td>
    2139             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-08">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-08 (work in progress), October&nbsp;2009.
     2337            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-08">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-08 (work in progress), October&nbsp;2009.
    21402338            </td>
    21412339         </tr>
    21422340         <tr>
    21432341            <td class="reference"><b id="Part7">[Part7]</b></td>
    2144             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-08">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-08 (work in progress), October&nbsp;2009.
     2342            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-08">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-08 (work in progress), October&nbsp;2009.
    21452343            </td>
    21462344         </tr>
    21472345         <tr>
    21482346            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    2149             <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
     2347            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
    21502348            </td>
    21512349         </tr>
    21522350         <tr>
    21532351            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    2154             <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     2352            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
    21552353            </td>
    21562354         </tr>
     
    21582356      <h2 id="rfc.references.2"><a href="#rfc.section.13.2" id="rfc.section.13.2">13.2</a> Informative References
    21592357      </h2>
    2160       <table>             
     2358      <table>
    21612359         <tr>
    21622360            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    2163             <td class="top"><a href="mailto:timbl@w3.org" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
     2361            <td class="top"><a href="mailto:timbl@w3.org" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium, MIT Laboratory for Computer Science">H. Nielsen</a>, “<a href="https://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
    21642362            </td>
    21652363         </tr>
    21662364         <tr>
    21672365            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
    2168             <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a href="mailto:timbl@w3.org" title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
     2366            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a href="mailto:timbl@w3.org" title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
    21692367            </td>
    21702368         </tr>
    21712369         <tr>
    21722370            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    2173             <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     2371            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    21742372            </td>
    21752373         </tr>
    21762374         <tr>
    21772375            <td class="reference"><b id="RFC2817">[RFC2817]</b></td>
    2178             <td class="top"><a href="mailto:rohit@4K-associates.com" title="4K Associates / UC Irvine">Khare, R.</a> and <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">S. Lawrence</a>, “<a href="http://tools.ietf.org/html/rfc2817">Upgrading to TLS Within HTTP/1.1</a>”, RFC&nbsp;2817, May&nbsp;2000.
     2376            <td class="top"><a href="mailto:rohit@4K-associates.com" title="4K Associates / UC Irvine">Khare, R.</a> and <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">S. Lawrence</a>, “<a href="https://tools.ietf.org/html/rfc2817">Upgrading to TLS Within HTTP/1.1</a>”, RFC&nbsp;2817, May&nbsp;2000.
    21792377            </td>
    21802378         </tr>
    21812379         <tr>
    21822380            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    2183             <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
     2381            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
    21842382            </td>
    21852383         </tr>
    21862384         <tr>
    21872385            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
    2188             <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
     2386            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
    21892387            </td>
    21902388         </tr>
    21912389         <tr>
    21922390            <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
    2193             <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
     2391            <td class="top">Resnick, P., “<a href="https://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
    21942392            </td>
    21952393         </tr>
    21962394      </table>
    2197       <div class="avoidbreak">
    2198          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    2199          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    2200                (editor)
    2201                <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
    2202          <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:jg@laptop.org"><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
    2203          <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:JeffMogul@acm.org"><span class="email">JeffMogul@acm.org</span></a></span></address>
    2204          <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:henrikn@microsoft.com"><span class="email">henrikn@microsoft.com</span></a></span></address>
    2205          <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems, Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:LMM@acm.org"><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address>
    2206          <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a href="mailto:paulle@microsoft.com"><span class="email">paulle@microsoft.com</span></a></span></address>
    2207          <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:timbl@w3.org"><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address>
    2208          <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
    2209                (editor)
    2210                <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span>&nbsp;<span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">EMail: <a href="mailto:ylafon@w3.org"><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address>
    2211          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
    2212                (editor)
    2213                <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
     2395      <div id="compatibility">
     2396         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
     2397         <div id="changes.from.rfc.2068">
     2398            <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
     2399            <p id="rfc.section.A.1.p.1">Clarified which error code should be used for inbound server failures (e.g. DNS failures). (<a href="#status.504" id="rfc.xref.status.504.3" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>).
     2400            </p>
     2401            <p id="rfc.section.A.1.p.2">201 (Created) had a race that required an Etag be sent when a resource is first created. (<a href="#status.201" id="rfc.xref.status.201.3" title="201 Created">Section&nbsp;8.2.2</a>).
     2402            </p>
     2403            <p id="rfc.section.A.1.p.3">303 (See Also) and 307 (Temporary Redirect) added to address user agent failure to implement status code 302 properly. (Section <a href="#status.303" id="rfc.xref.status.303.4" title="303 See Other">8.3.4</a> and <a href="#status.307" id="rfc.xref.status.307.4" title="307 Temporary Redirect">8.3.8</a>)
     2404            </p>
     2405            <p id="rfc.section.A.1.p.4">Rewrite of message transmission requirements to make it much harder for implementors to get it wrong, as the consequences
     2406               of errors here can have significant impact on the Internet, and to deal with the following problems:
     2407            </p>
     2408            <ol>
     2409               <li>Changing "HTTP/1.1 or later" to "HTTP/1.1", in contexts where this was incorrectly placing a requirement on the behavior of
     2410                  an implementation of a future version of HTTP/1.x
     2411               </li>
     2412               <li>Made it clear that user-agents should retry requests, not "clients" in general.</li>
     2413               <li>Converted requirements for clients to ignore unexpected 100 (Continue) responses, and for proxies to forward 100 responses,
     2414                  into a general requirement for 1xx responses.
     2415               </li>
     2416               <li>Modified some TCP-specific language, to make it clearer that non-TCP transports are possible for HTTP.</li>
     2417               <li>Require that the origin server <em class="bcp14">MUST NOT</em> wait for the request body before it sends a required 100 (Continue) response.
     2418               </li>
     2419               <li>Allow, rather than require, a server to omit 100 (Continue) if it has already seen some of the request body.</li>
     2420               <li>Allow servers to defend against denial-of-service attacks and broken clients.</li>
     2421            </ol>
     2422            <p id="rfc.section.A.1.p.5">This change adds the Expect header and 417 status code.</p>
     2423            <p id="rfc.section.A.1.p.6">Clean up confusion between 403 and 404 responses. (Section <a href="#status.403" id="rfc.xref.status.403.3" title="403 Forbidden">8.4.4</a>, <a href="#status.404" id="rfc.xref.status.404.3" title="404 Not Found">8.4.5</a>, and <a href="#status.410" id="rfc.xref.status.410.3" title="410 Gone">8.4.11</a>)
     2424            </p>
     2425            <p id="rfc.section.A.1.p.7">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="https://tools.ietf.org/html/rfc2068#section-19.6.1">Section 19.6.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
     2426            </p>
     2427         </div>
     2428         <div id="changes.from.rfc.2616">
     2429            <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     2430            <p id="rfc.section.A.2.p.1">This document takes over the Status Code Registry, previously defined in <a href="https://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.1</a>)
     2431            </p>
     2432            <p id="rfc.section.A.2.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;7.5</a>)
     2433            </p>
     2434            <p id="rfc.section.A.2.p.3">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
     2435               user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">8.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">8.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.5" title="307 Temporary Redirect">8.3.8</a>)
     2436            </p>
     2437            <p id="rfc.section.A.2.p.4">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the requested resource
     2438               must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
     2439               was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;8.3.6</a>)
     2440            </p>
     2441            <p id="rfc.section.A.2.p.5">Reclassify Allow header as response header, removing the option to specify it in a PUT request. Relax the server requirement
     2442               on the contents of the Allow header and remove requirement on clients to always trust the header value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;9.1</a>)
     2443            </p>
     2444            <p id="rfc.section.A.2.p.6">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications
     2445               as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.4</a>)
     2446            </p>
     2447            <p id="rfc.section.A.2.p.7">Allow Referer value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.6</a>)
     2448            </p>
     2449            <p id="rfc.section.A.2.p.8">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly
     2450               in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;9.8</a>)
     2451            </p>
     2452         </div>
    22142453      </div>
    2215       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    2216       <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
    2217       <p id="rfc.section.A.1.p.1">Clarified which error code should be used for inbound server failures (e.g. DNS failures). (<a href="#status.504" id="rfc.xref.status.504.3" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>).
    2218       </p>
    2219       <p id="rfc.section.A.1.p.2">201 (Created) had a race that required an Etag be sent when a resource is first created. (<a href="#status.201" id="rfc.xref.status.201.3" title="201 Created">Section&nbsp;8.2.2</a>).
    2220       </p>
    2221       <p id="rfc.section.A.1.p.3">303 (See Also) and 307 (Temporary Redirect) added to address user agent failure to implement status code 302 properly. (Section <a href="#status.303" id="rfc.xref.status.303.4" title="303 See Other">8.3.4</a> and <a href="#status.307" id="rfc.xref.status.307.4" title="307 Temporary Redirect">8.3.8</a>)
    2222       </p>
    2223       <p id="rfc.section.A.1.p.4">Rewrite of message transmission requirements to make it much harder for implementors to get it wrong, as the consequences
    2224          of errors here can have significant impact on the Internet, and to deal with the following problems:
    2225       </p>
    2226       <ol>
    2227          <li>Changing "HTTP/1.1 or later" to "HTTP/1.1", in contexts where this was incorrectly placing a requirement on the behavior of
    2228             an implementation of a future version of HTTP/1.x
    2229          </li>
    2230          <li>Made it clear that user-agents should retry requests, not "clients" in general.</li>
    2231          <li>Converted requirements for clients to ignore unexpected 100 (Continue) responses, and for proxies to forward 100 responses,
    2232             into a general requirement for 1xx responses.
    2233          </li>
    2234          <li>Modified some TCP-specific language, to make it clearer that non-TCP transports are possible for HTTP.</li>
    2235          <li>Require that the origin server <em class="bcp14">MUST NOT</em> wait for the request body before it sends a required 100 (Continue) response.
    2236          </li>
    2237          <li>Allow, rather than require, a server to omit 100 (Continue) if it has already seen some of the request body.</li>
    2238          <li>Allow servers to defend against denial-of-service attacks and broken clients.</li>
    2239       </ol>
    2240       <p id="rfc.section.A.1.p.5">This change adds the Expect header and 417 status code.</p>
    2241       <p id="rfc.section.A.1.p.6">Clean up confusion between 403 and 404 responses. (Section <a href="#status.403" id="rfc.xref.status.403.3" title="403 Forbidden">8.4.4</a>, <a href="#status.404" id="rfc.xref.status.404.3" title="404 Not Found">8.4.5</a>, and <a href="#status.410" id="rfc.xref.status.410.3" title="410 Gone">8.4.11</a>)
    2242       </p>
    2243       <p id="rfc.section.A.1.p.7">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.1">Section 19.6.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
    2244       </p>
    2245       <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    2246       <p id="rfc.section.A.2.p.1">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;4.1</a>)
    2247       </p>
    2248       <p id="rfc.section.A.2.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;7.5</a>)
    2249       </p>
    2250       <p id="rfc.section.A.2.p.3">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
    2251          user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">8.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">8.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.5" title="307 Temporary Redirect">8.3.8</a>)
    2252       </p>
    2253       <p id="rfc.section.A.2.p.4">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the requested resource
    2254          must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
    2255          was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;8.3.6</a>)
    2256       </p>
    2257       <p id="rfc.section.A.2.p.5">Reclassify Allow header as response header, removing the option to specify it in a PUT request. Relax the server requirement
    2258          on the contents of the Allow header and remove requirement on clients to always trust the header value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;9.1</a>)
    2259       </p>
    2260       <p id="rfc.section.A.2.p.6">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications
    2261          as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.4</a>)
    2262       </p>
    2263       <p id="rfc.section.A.2.p.7">Allow Referer value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.6</a>)
    2264       </p>
    2265       <p id="rfc.section.A.2.p.8">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly
    2266          in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;9.8</a>)
    2267       </p>
    2268       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    2269       <div id="rfc.figure.u.29"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = &lt;Accept, defined in [Part3], Section 5.1&gt;
     2454      <div id="collected.abnf">
     2455         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     2456         <div id="rfc.figure.u.29"></div><pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = &lt;Accept, defined in [Part3], Section 5.1&gt;
    22702457<a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = &lt;Accept-Charset, defined in [Part3], Section 5.2&gt;
    22712458<a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> = &lt;Accept-Encoding, defined in [Part3], Section 5.3&gt;
     
    23762563
    23772564<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
    2378 </pre> <div id="rfc.figure.u.30"></div>
    2379       <p>ABNF diagnostics:</p><pre class="inline">; Reason-Phrase defined but not used
     2565</pre><div id="rfc.figure.u.30"></div>
     2566         <p>ABNF diagnostics:</p><pre class="inline">; Reason-Phrase defined but not used
    23802567; Status-Code defined but not used
    23812568; request-header defined but not used
    23822569; response-header defined but not used
    2383 </pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    2384       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
    2385       </h2>
    2386       <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    2387       </p>
    2388       <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
    2389       </h2>
    2390       <p id="rfc.section.C.2.p.1">Closed issues: </p>
    2391       <ul>
    2392          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/5">http://tools.ietf.org/wg/httpbis/trac/ticket/5</a>&gt;: "Via is a MUST" (&lt;<a href="http://purl.org/NET/http-errata#via-must">http://purl.org/NET/http-errata#via-must</a>&gt;)
    2393          </li>
    2394          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/6">http://tools.ietf.org/wg/httpbis/trac/ticket/6</a>&gt;: "Fragments allowed in Location" (&lt;<a href="http://purl.org/NET/http-errata#location-fragments">http://purl.org/NET/http-errata#location-fragments</a>&gt;)
    2395          </li>
    2396          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/10">http://tools.ietf.org/wg/httpbis/trac/ticket/10</a>&gt;: "Safe Methods vs Redirection" (&lt;<a href="http://purl.org/NET/http-errata#saferedirect">http://purl.org/NET/http-errata#saferedirect</a>&gt;)
    2397          </li>
    2398          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/17">http://tools.ietf.org/wg/httpbis/trac/ticket/17</a>&gt;: "Revise description of the POST method" (&lt;<a href="http://purl.org/NET/http-errata#post">http://purl.org/NET/http-errata#post</a>&gt;)
    2399          </li>
    2400          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
    2401          </li>
    2402          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/42">http://tools.ietf.org/wg/httpbis/trac/ticket/42</a>&gt;: "RFC2606 Compliance"
    2403          </li>
    2404          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/65">http://tools.ietf.org/wg/httpbis/trac/ticket/65</a>&gt;: "Informative references"
    2405          </li>
    2406          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/84">http://tools.ietf.org/wg/httpbis/trac/ticket/84</a>&gt;: "Redundant cross-references"
    2407          </li>
    2408       </ul>
    2409       <p id="rfc.section.C.2.p.2">Other changes: </p>
    2410       <ul>
    2411          <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.16"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>
    2412          </li>
    2413       </ul>
    2414       <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
    2415       </h2>
    2416       <p id="rfc.section.C.3.p.1">Closed issues: </p>
    2417       <ul>
    2418          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/21">http://tools.ietf.org/wg/httpbis/trac/ticket/21</a>&gt;: "PUT side effects"
    2419          </li>
    2420          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/91">http://tools.ietf.org/wg/httpbis/trac/ticket/91</a>&gt;: "Duplicate Host header requirements"
    2421          </li>
    2422       </ul>
    2423       <p id="rfc.section.C.3.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    2424       </p>
    2425       <ul>
    2426          <li>Move "Product Tokens" section (back) into Part 1, as "token" is used in the definition of the Upgrade header.</li>
    2427          <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    2428          <li>Copy definition of delta-seconds from Part6 instead of referencing it.</li>
    2429       </ul>
    2430       <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></h2>
    2431       <p id="rfc.section.C.4.p.1">Closed issues: </p>
    2432       <ul>
    2433          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/24">http://tools.ietf.org/wg/httpbis/trac/ticket/24</a>&gt;: "Requiring Allow in 405 responses"
    2434          </li>
    2435          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/59">http://tools.ietf.org/wg/httpbis/trac/ticket/59</a>&gt;: "Status Code Registry"
    2436          </li>
    2437          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/61">http://tools.ietf.org/wg/httpbis/trac/ticket/61</a>&gt;: "Redirection vs. Location"
    2438          </li>
    2439          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/70">http://tools.ietf.org/wg/httpbis/trac/ticket/70</a>&gt;: "Cacheability of 303 response"
    2440          </li>
    2441          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/76">http://tools.ietf.org/wg/httpbis/trac/ticket/76</a>&gt;: "305 Use Proxy"
    2442          </li>
    2443          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/105">http://tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header"
    2444          </li>
    2445          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/112">http://tools.ietf.org/wg/httpbis/trac/ticket/112</a>&gt;: "PUT - 'store under' vs 'store at'"
    2446          </li>
    2447       </ul>
    2448       <p id="rfc.section.C.4.p.2">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    2449       </p>
    2450       <ul>
    2451          <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
    2452       </ul>
    2453       <p id="rfc.section.C.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    2454       </p>
    2455       <ul>
    2456          <li>Replace string literals when the string really is case-sensitive (method).</li>
    2457       </ul>
    2458       <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>
    2459       <p id="rfc.section.C.5.p.1">Closed issues: </p>
    2460       <ul>
    2461          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/98">http://tools.ietf.org/wg/httpbis/trac/ticket/98</a>&gt;: "OPTIONS request bodies"
    2462          </li>
    2463          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/119">http://tools.ietf.org/wg/httpbis/trac/ticket/119</a>&gt;: "Description of CONNECT should refer to RFC2817"
    2464          </li>
    2465          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/125">http://tools.ietf.org/wg/httpbis/trac/ticket/125</a>&gt;: "Location Content-Location reference request/response mixup"
    2466          </li>
    2467       </ul>
    2468       <p id="rfc.section.C.5.p.2">Ongoing work on Method Registry (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/72">http://tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
    2469       </p>
    2470       <ul>
    2471          <li>Added initial proposal for registration process, plus initial content (non-HTTP/1.1 methods to be added by a separate specification).</li>
    2472       </ul>
    2473       <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2>
    2474       <p id="rfc.section.C.6.p.1">Closed issues: </p>
    2475       <ul>
    2476          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/103">http://tools.ietf.org/wg/httpbis/trac/ticket/103</a>&gt;: "Content-*"
    2477          </li>
    2478          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/132">http://tools.ietf.org/wg/httpbis/trac/ticket/132</a>&gt;: "RFC 2822 is updated by RFC 5322"
    2479          </li>
    2480       </ul>
    2481       <p id="rfc.section.C.6.p.2">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    2482       </p>
    2483       <ul>
    2484          <li>Use "/" instead of "|" for alternatives.</li>
    2485          <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
    2486          <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
    2487       </ul>
    2488       <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></h2>
    2489       <p id="rfc.section.C.7.p.1">Closed issues: </p>
    2490       <ul>
    2491          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/94">http://tools.ietf.org/wg/httpbis/trac/ticket/94</a>&gt;: "Reason-Phrase BNF"
    2492          </li>
    2493       </ul>
    2494       <p id="rfc.section.C.7.p.2">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    2495       </p>
    2496       <ul>
    2497          <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    2498       </ul>
    2499       <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></h2>
    2500       <p id="rfc.section.C.8.p.1">Closed issues: </p>
    2501       <ul>
    2502          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/144">http://tools.ietf.org/wg/httpbis/trac/ticket/144</a>&gt;: "Clarify when Referer is sent"
    2503