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/12/p2-semantics.html

    r1051 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 
    4239ul.empty {
    4340  list-style-type: none;
     
    5350}
    5451h1 {
    55   font-size: 14pt;
     52  font-size: 130%;
    5653  line-height: 21pt;
    5754  page-break-after: avoid;
     
    6057  page-break-before: always;
    6158}
    62 h1 a {
    63   color: #333333;
    64 }
    6559h2 {
    66   font-size: 12pt;
     60  font-size: 120%;
    6761  line-height: 15pt;
    6862  page-break-after: avoid;
    6963}
    70 h3, h4, h5, h6 {
    71   font-size: 10pt;
     64h3 {
     65  font-size: 110%;
    7266  page-break-after: avoid;
    7367}
    74 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 {
    7572  color: black;
    7673}
     
    8077li {
    8178  margin-left: 2em;
    82   margin-right: 2em;
    8379}
    8480ol {
    8581  margin-left: 2em;
    86   margin-right: 2em;
     82}
     83ol.la {
     84  list-style-type: lower-alpha;
     85}
     86ol.ua {
     87  list-style-type: upper-alpha;
    8788}
    8889ol p {
     
    9192p {
    9293  margin-left: 2em;
    93   margin-right: 2em;
    9494}
    9595pre {
     
    9797  background-color: lightyellow;
    9898  padding: .25em;
     99  page-break-inside: avoid;
    99100}
    100101pre.text2 {
     
    125126table.tt {
    126127  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;
    127139}
    128140table.full {
    129   border-style: outset;
    130   border-width: 1px;
    131 }
    132 table.headers {
    133   border-style: outset;
    134   border-width: 1px;
     141  border-style: solid;
     142  border-width: 2px;
    135143}
    136144table.tt td {
    137145  vertical-align: top;
    138146}
     147table.all td {
     148  border-style: solid;
     149  border-width: 1px;
     150}
    139151table.full td {
    140   border-style: inset;
     152  border-style: none solid;
    141153  border-width: 1px;
    142154}
     
    144156  vertical-align: top;
    145157}
     158table.all th {
     159  border-style: solid;
     160  border-width: 1px;
     161}
    146162table.full th {
    147   border-style: inset;
    148   border-width: 1px;
     163  border-style: solid;
     164  border-width: 1px 1px 2px 1px;
    149165}
    150166table.headers th {
    151   border-style: none none inset none;
    152   border-width: 1px;
     167  border-style: none none solid none;
     168  border-width: 2px;
    153169}
    154170table.left {
     
    165181  caption-side: bottom;
    166182  font-weight: bold;
    167   font-size: 9pt;
     183  font-size: 10pt;
    168184  margin-top: .5em;
    169185}
     
    172188  border-spacing: 1px;
    173189  width: 95%;
    174   font-size: 10pt;
     190  font-size: 11pt;
    175191  color: white;
    176192}
     
    180196td.topnowrap {
    181197  vertical-align: top;
    182   white-space: nowrap; 
     198  white-space: nowrap;
    183199}
    184200table.header td {
     
    197213  display:table-header-group;
    198214}
    199 ul.toc {
     215ul.toc, ul.toc ul {
    200216  list-style: none;
    201217  margin-left: 1.5em;
    202   margin-right: 0em;
    203218  padding-left: 0em;
    204219}
    205 li.tocline0 {
     220ul.toc li {
    206221  line-height: 150%;
    207222  font-weight: bold;
     223  margin-left: 0em;
     224}
     225ul.toc li li {
     226  line-height: normal;
     227  font-weight: normal;
    208228  font-size: 10pt;
    209229  margin-left: 0em;
    210   margin-right: 0em;
    211 }
    212 li.tocline1 {
    213   line-height: normal;
    214   font-weight: normal;
    215   font-size: 9pt;
    216   margin-left: 0em;
    217   margin-right: 0em;
    218 }
    219 li.tocline2 {
     230}
     231li.excluded {
    220232  font-size: 0pt;
    221233}
     
    223235  margin-left: 0em;
    224236}
    225 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 {
    226244  list-style: none;
    227245  margin-left: 1.5em;
    228   margin-right: 0em;
    229246  padding-left: 0em;
    230247  page-break-before: avoid;
    231248}
    232 li.indline0 {
     249ul.ind li {
    233250  font-weight: bold;
    234251  line-height: 200%;
    235252  margin-left: 0em;
    236   margin-right: 0em;
    237 }
    238 li.indline1 {
     253}
     254ul.ind li li {
    239255  font-weight: normal;
    240256  line-height: 150%;
    241257  margin-left: 0em;
    242   margin-right: 0em;
    243258}
    244259.avoidbreak {
     
    264279  font-weight: bold;
    265280  text-align: center;
    266   font-size: 9pt;
     281  font-size: 10pt;
    267282}
    268283.filename {
    269284  color: #333333;
     285  font-size: 75%;
    270286  font-weight: bold;
    271   font-size: 12pt;
    272287  line-height: 21pt;
    273288  text-align: center;
     
    276291  font-weight: bold;
    277292}
    278 .hidden {
    279   display: none;
    280 }
    281293.left {
    282294  text-align: left;
     
    286298}
    287299.title {
    288   color: #990000;
    289   font-size: 18pt;
     300  color: green;
     301  font-size: 150%;
    290302  line-height: 18pt;
    291303  font-weight: bold;
     
    293305  margin-top: 36pt;
    294306}
    295 .vcardline {
    296   display: block;
    297 }
    298307.warning {
    299   font-size: 14pt;
     308  font-size: 130%;
    300309  background-color: yellow;
    301310}
     
    306315    display: none;
    307316  }
    308  
     317
    309318  a {
    310319    color: black;
     
    321330    background-color: white;
    322331    vertical-align: top;
    323     font-size: 12pt;
     332    font-size: 110%;
    324333  }
    325334
    326   ul.toc a::after {
     335  ul.toc a:nth-child(2)::after {
    327336    content: leader('.') target-counter(attr(href), page);
    328337  }
    329  
    330   a.iref {
     338
     339  ul.ind li li a {
    331340    content: target-counter(attr(href), page);
    332341  }
    333  
     342
    334343  .print2col {
    335344    column-count: 2;
     
    341350@page {
    342351  @top-left {
    343        content: "Internet-Draft"; 
    344   } 
     352       content: "Internet-Draft";
     353  }
    345354  @top-right {
    346        content: "October 2010"; 
    347   } 
     355       content: "October 2010";
     356  }
    348357  @top-center {
    349        content: "HTTP/1.1, Part 2"; 
    350   } 
     358       content: "HTTP/1.1, Part 2";
     359  }
    351360  @bottom-left {
    352        content: "Fielding, et al."; 
    353   } 
     361       content: "Fielding, et al.";
     362  }
    354363  @bottom-center {
    355        content: "Standards Track";
    356   } 
     364       content: "Expires April 28, 2011";
     365  }
    357366  @bottom-right {
    358        content: "[Page " counter(page) "]"; 
    359   } 
    360 }
    361 
    362 @page:first { 
     367       content: "[Page " counter(page) "]";
     368  }
     369}
     370
     371@page:first {
    363372    @top-left {
    364373      content: normal;
     
    391400      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    392401      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    393       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.524, 2010-09-14 12:37:11, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     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/">
    394403      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    395404      <meta name="dct.creator" content="Fielding, R.">
     
    420429            </tr>
    421430            <tr>
    422                <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     431               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    423432               </td>
    424433               <td class="right">J. Gettys</td>
    425434            </tr>
    426435            <tr>
    427                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved)
     436               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2817">2817</a> (if approved)
    428437               </td>
    429438               <td class="right">Alcatel-Lucent</td>
     
    492501      </table>
    493502      <p class="title">HTTP/1.1, part 2: Message Semantics<br><span class="filename">draft-ietf-httpbis-p2-semantics-12</span></p>
    494       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
     503      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    495504      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
    496505         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the
     
    498507         2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and
    499508         response-header fields.
    500       </p> 
    501       <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
     509      </p>
     510      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    502511      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
    503512         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
    504       </p> 
     513      </p>
    505514      <p>The changes in this draft are summarized in <a href="#changes.since.11" title="Since draft-ietf-httpbis-p2-semantics-11">Appendix&nbsp;C.13</a>.
    506       </p>
    507       <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
    508       <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
    509       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
    510          working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
    511515      </p>
    512       <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
    513          documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
    514          in progress”.
    515       </p>
    516       <p>This Internet-Draft will expire on April 28, 2011.</p>
    517       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    518       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    519       <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
    520          and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
    521          text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
    522          BSD License.
    523       </p>
    524       <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
    525          10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
    526          allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
    527          controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
    528          works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
    529          it into languages other than English.
    530       </p>
     516      <div id="rfc.status">
     517         <h1><a href="#rfc.status">Status of This Memo</a></h1>
     518         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
     519         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
     520            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
     521         </p>
     522         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
     523            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
     524            in progress”.
     525         </p>
     526         <p>This Internet-Draft will expire on April 28, 2011.</p>
     527      </div>
     528      <div id="rfc.copyrightnotice">
     529         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
     530         <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     531         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
     532            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
     533            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
     534            BSD License.
     535         </p>
     536         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
     537            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
     538            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
     539            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
     540            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
     541            it into languages other than English.
     542         </p>
     543      </div>
    531544      <hr class="noprint">
    532545      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    533546      <ul class="toc">
    534          <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
    535                <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
    536                <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul class="toc">
    537                      <li class="tocline1">1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
    538                      <li class="tocline1">1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
     547         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
     548               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
     549               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
     550                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
     551                     <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>
    539552                  </ul>
    540553               </li>
    541554            </ul>
    542555         </li>
    543          <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#method">Method</a><ul class="toc">
    544                <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul class="toc">
    545                      <li class="tocline1">2.1.1&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
     556         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#method">Method</a><ul>
     557               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul>
     558                     <li><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
    546559                  </ul>
    547560               </li>
    548561            </ul>
    549562         </li>
    550          <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
    551          <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a><ul class="toc">
    552                <li class="tocline1">4.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a><ul class="toc">
    553                      <li class="tocline1">4.1.1&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li>
     563         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
     564         <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>
     565               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a><ul>
     566                     <li><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li>
    554567                  </ul>
    555568               </li>
    556569            </ul>
    557570         </li>
    558          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
    559          <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#representation">Representation</a><ul class="toc">
    560                <li class="tocline1">6.1&nbsp;&nbsp;&nbsp;<a href="#identifying.response.associated.with.representation">Identifying the Resource Associated with a Representation</a></li>
     571         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
     572         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#representation">Representation</a><ul>
     573               <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>
    561574            </ul>
    562575         </li>
    563          <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul class="toc">
    564                <li class="tocline1">7.1&nbsp;&nbsp;&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul class="toc">
    565                      <li class="tocline1">7.1.1&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
    566                      <li class="tocline1">7.1.2&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
     576         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul>
     577               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul>
     578                     <li><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
     579                     <li><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
    567580                  </ul>
    568581               </li>
    569                <li class="tocline1">7.2&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
    570                <li class="tocline1">7.3&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
    571                <li class="tocline1">7.4&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
    572                <li class="tocline1">7.5&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
    573                <li class="tocline1">7.6&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
    574                <li class="tocline1">7.7&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
    575                <li class="tocline1">7.8&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
    576                <li class="tocline1">7.9&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
     582               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
     583               <li><a href="#rfc.section.7.3">7.3</a>&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
     584               <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
     585               <li><a href="#rfc.section.7.5">7.5</a>&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
     586               <li><a href="#rfc.section.7.6">7.6</a>&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
     587               <li><a href="#rfc.section.7.7">7.7</a>&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
     588               <li><a href="#rfc.section.7.8">7.8</a>&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
     589               <li><a href="#rfc.section.7.9">7.9</a>&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
    577590            </ul>
    578591         </li>
    579          <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#status.codes">Status Code Definitions</a><ul class="toc">
    580                <li class="tocline1">8.1&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul class="toc">
    581                      <li class="tocline1">8.1.1&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
    582                      <li class="tocline1">8.1.2&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
     592         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#status.codes">Status Code Definitions</a><ul>
     593               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul>
     594                     <li><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
     595                     <li><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
    583596                  </ul>
    584597               </li>
    585                <li class="tocline1">8.2&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul class="toc">
    586                      <li class="tocline1">8.2.1&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
    587                      <li class="tocline1">8.2.2&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
    588                      <li class="tocline1">8.2.3&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
    589                      <li class="tocline1">8.2.4&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
    590                      <li class="tocline1">8.2.5&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
    591                      <li class="tocline1">8.2.6&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
    592                      <li class="tocline1">8.2.7&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
     598               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul>
     599                     <li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
     600                     <li><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
     601                     <li><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
     602                     <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>
     603                     <li><a href="#rfc.section.8.2.5">8.2.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
     604                     <li><a href="#rfc.section.8.2.6">8.2.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
     605                     <li><a href="#rfc.section.8.2.7">8.2.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    593606                  </ul>
    594607               </li>
    595                <li class="tocline1">8.3&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul class="toc">
    596                      <li class="tocline1">8.3.1&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
    597                      <li class="tocline1">8.3.2&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
    598                      <li class="tocline1">8.3.3&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
    599                      <li class="tocline1">8.3.4&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
    600                      <li class="tocline1">8.3.5&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
    601                      <li class="tocline1">8.3.6&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
    602                      <li class="tocline1">8.3.7&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
    603                      <li class="tocline1">8.3.8&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
     608               <li><a href="#rfc.section.8.3">8.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul>
     609                     <li><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
     610                     <li><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
     611                     <li><a href="#rfc.section.8.3.3">8.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
     612                     <li><a href="#rfc.section.8.3.4">8.3.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
     613                     <li><a href="#rfc.section.8.3.5">8.3.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
     614                     <li><a href="#rfc.section.8.3.6">8.3.6</a>&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
     615                     <li><a href="#rfc.section.8.3.7">8.3.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
     616                     <li><a href="#rfc.section.8.3.8">8.3.8</a>&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
    604617                  </ul>
    605618               </li>
    606                <li class="tocline1">8.4&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul class="toc">
    607                      <li class="tocline1">8.4.1&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
    608                      <li class="tocline1">8.4.2&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
    609                      <li class="tocline1">8.4.3&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
    610                      <li class="tocline1">8.4.4&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
    611                      <li class="tocline1">8.4.5&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
    612                      <li class="tocline1">8.4.6&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
    613                      <li class="tocline1">8.4.7&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
    614                      <li class="tocline1">8.4.8&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
    615                      <li class="tocline1">8.4.9&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
    616                      <li class="tocline1">8.4.10&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
    617                      <li class="tocline1">8.4.11&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
    618                      <li class="tocline1">8.4.12&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
    619                      <li class="tocline1">8.4.13&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
    620                      <li class="tocline1">8.4.14&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Entity Too Large</a></li>
    621                      <li class="tocline1">8.4.15&nbsp;&nbsp;&nbsp;<a href="#status.414">414 URI Too Long</a></li>
    622                      <li class="tocline1">8.4.16&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
    623                      <li class="tocline1">8.4.17&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
    624                      <li class="tocline1">8.4.18&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
     619               <li><a href="#rfc.section.8.4">8.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul>
     620                     <li><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
     621                     <li><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
     622                     <li><a href="#rfc.section.8.4.3">8.4.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
     623                     <li><a href="#rfc.section.8.4.4">8.4.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
     624                     <li><a href="#rfc.section.8.4.5">8.4.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
     625                     <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>
     626                     <li><a href="#rfc.section.8.4.7">8.4.7</a>&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
     627                     <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>
     628                     <li><a href="#rfc.section.8.4.9">8.4.9</a>&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
     629                     <li><a href="#rfc.section.8.4.10">8.4.10</a>&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
     630                     <li><a href="#rfc.section.8.4.11">8.4.11</a>&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
     631                     <li><a href="#rfc.section.8.4.12">8.4.12</a>&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
     632                     <li><a href="#rfc.section.8.4.13">8.4.13</a>&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
     633                     <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>
     634                     <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>
     635                     <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>
     636                     <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>
     637                     <li><a href="#rfc.section.8.4.18">8.4.18</a>&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
    625638                  </ul>
    626639               </li>
    627                <li class="tocline1">8.5&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul class="toc">
    628                      <li class="tocline1">8.5.1&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
    629                      <li class="tocline1">8.5.2&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
    630                      <li class="tocline1">8.5.3&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
    631                      <li class="tocline1">8.5.4&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
    632                      <li class="tocline1">8.5.5&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
    633                      <li class="tocline1">8.5.6&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
     640               <li><a href="#rfc.section.8.5">8.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul>
     641                     <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>
     642                     <li><a href="#rfc.section.8.5.2">8.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
     643                     <li><a href="#rfc.section.8.5.3">8.5.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
     644                     <li><a href="#rfc.section.8.5.4">8.5.4</a>&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
     645                     <li><a href="#rfc.section.8.5.5">8.5.5</a>&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
     646                     <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>
    634647                  </ul>
    635648               </li>
    636649            </ul>
    637650         </li>
    638          <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
    639                <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
    640                <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
    641                <li class="tocline1">9.3&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
    642                <li class="tocline1">9.4&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
    643                <li class="tocline1">9.5&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
    644                <li class="tocline1">9.6&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
    645                <li class="tocline1">9.7&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
    646                <li class="tocline1">9.8&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
    647                <li class="tocline1">9.9&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
     651         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
     652               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
     653               <li><a href="#rfc.section.9.2">9.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
     654               <li><a href="#rfc.section.9.3">9.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
     655               <li><a href="#rfc.section.9.4">9.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
     656               <li><a href="#rfc.section.9.5">9.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
     657               <li><a href="#rfc.section.9.6">9.6</a>&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
     658               <li><a href="#rfc.section.9.7">9.7</a>&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
     659               <li><a href="#rfc.section.9.8">9.8</a>&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
     660               <li><a href="#rfc.section.9.9">9.9</a>&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
    648661            </ul>
    649662         </li>
    650          <li class="tocline0">10.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
    651                <li class="tocline1">10.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
    652                <li class="tocline1">10.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
    653                <li class="tocline1">10.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
     663         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
     664               <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
     665               <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
     666               <li><a href="#rfc.section.10.3">10.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    654667            </ul>
    655668         </li>
    656          <li class="tocline0">11.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul class="toc">
    657                <li class="tocline1">11.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
    658                <li class="tocline1">11.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
    659                <li class="tocline1">11.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing">Location Headers and Spoofing</a></li>
     669         <li><a href="#rfc.section.11">11.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
     670               <li><a href="#rfc.section.11.1">11.1</a>&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
     671               <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>
     672               <li><a href="#rfc.section.11.3">11.3</a>&nbsp;&nbsp;&nbsp;<a href="#location.spoofing">Location Headers and Spoofing</a></li>
    660673            </ul>
    661674         </li>
    662          <li class="tocline0">12.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
    663          <li class="tocline0">13.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
    664                <li class="tocline1">13.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    665                <li class="tocline1">13.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     675         <li><a href="#rfc.section.12">12.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
     676         <li><a href="#rfc.section.13">13.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     677               <li><a href="#rfc.section.13.1">13.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     678               <li><a href="#rfc.section.13.2">13.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    666679            </ul>
    667680         </li>
    668          <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
    669          <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
    670          <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
    671          <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">
    672                <li class="tocline1">C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC 2616</a></li>
    673                <li class="tocline1">C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
    674                <li class="tocline1">C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p2-semantics-01</a></li>
    675                <li class="tocline1">C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
    676                <li class="tocline1">C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
    677                <li class="tocline1">C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
    678                <li class="tocline1">C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
    679                <li class="tocline1">C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p2-semantics-06</a></li>
    680                <li class="tocline1">C.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></li>
    681                <li class="tocline1">C.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></li>
    682                <li class="tocline1">C.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></li>
    683                <li class="tocline1">C.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></li>
    684                <li class="tocline1">C.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></li>
     681         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</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 RFC 2616</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>
     693               <li><a href="#rfc.section.C.10">C.10</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></li>
     694               <li><a href="#rfc.section.C.11">C.11</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p2-semantics-09</a></li>
     695               <li><a href="#rfc.section.C.12">C.12</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p2-semantics-10</a></li>
     696               <li><a href="#rfc.section.C.13">C.13</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p2-semantics-11</a></li>
    685697            </ul>
    686698         </li>
    687          <li class="tocline0"><a href="#rfc.index">Index</a></li>
     699         <li><a href="#rfc.index">Index</a></li>
     700         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    688701      </ul>
    689       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    690       <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
    691          to each request, in the order received on that connection, with one or more HTTP response messages. This document defines
    692          the commonly agreed upon semantics of the HTTP uniform interface, the intentions defined by each request method, and the various
    693          response messages that might be expected as a result of applying that method to the target resource.
    694       </p>
    695       <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
    696          errata changes. A future draft will reorganize the sections to better reflect the content. In particular, the sections will
    697          be ordered according to the typical processing of an HTTP request message (after message parsing): resource mapping, general
    698          header fields, methods, request modifiers, response status, and resource metadata. The current mess reflects how widely dispersed
    699          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>.
    700       </p>
    701       <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>
    702       <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"
    703          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>.
    704       </p>
    705       <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
    706          protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
    707          for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
    708          all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
    709       </p>
    710       <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>
    711       <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.
    712       </p>
    713       <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
    714          (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
    715          and WSP (whitespace).
    716       </p>
    717       <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>
    718       <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>:
    719       </p>
    720       <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;
     702      <div id="introduction">
     703         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
     704         <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
     705            to each request, in the order received on that connection, with one or more HTTP response messages. This document defines
     706            the commonly agreed upon semantics of the HTTP uniform interface, the intentions defined by each request method, and the various
     707            response messages that might be expected as a result of applying that method to the target resource.
     708         </p>
     709         <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
     710            errata changes. A future draft will reorganize the sections to better reflect the content. In particular, the sections will
     711            be ordered according to the typical processing of an HTTP request message (after message parsing): resource mapping, general
     712            header fields, methods, request modifiers, response status, and resource metadata. The current mess reflects how widely dispersed
     713            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>.
     714         </p>
     715         <div id="intro.requirements">
     716            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
     717            <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"
     718               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>.
     719            </p>
     720            <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
     721               protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
     722               for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
     723               all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
     724            </p>
     725         </div>
     726         <div id="notation">
     727            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
     728            <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.
     729            </p>
     730            <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
     731               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
     732               and WSP (whitespace).
     733            </p>
     734            <div id="core.rules">
     735               <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>
     736               <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>:
     737               </p>
     738               <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;
    721739  <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;
    722740  <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;
    723741  <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;
    724742  <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;
    725 </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>
    726       <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
    727       <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;
     743</pre></div>
     744            <div id="abnf.dependencies">
     745               <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>
     746               <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
     747               <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;
    728748  <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;
    729749  <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;
     
    759779  <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a> =
    760780             &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 4.4</a>&gt;
    761 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="method" href="#method">Method</a></h1>
    762       <p id="rfc.section.2.p.1">The Method token indicates the method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The method is case-sensitive.
    763       </p>
    764       <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>
     781</pre></div>
     782         </div>
     783      </div>
     784      <div id="method">
     785         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#method">Method</a></h1>
     786         <p id="rfc.section.2.p.1">The Method token indicates the method to be performed on the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). The method is case-sensitive.
     787         </p>
     788         <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>
    765789                 / %x47.45.54               ; "GET", <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;7.3</a>
    766790                 / %x48.45.41.44            ; "HEAD", <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;7.4</a>
     
    773797  <a href="#method" class="smpl">extension-method</a> = <a href="#core.rules" class="smpl">token</a>
    774798</pre><p id="rfc.section.2.p.3">The list of methods allowed by a resource can be specified in an Allow header field (<a href="#header.allow" id="rfc.xref.header.allow.1" title="Allow">Section&nbsp;9.1</a>). The status code of the response always notifies the client whether a method is currently allowed on a resource, since the
    775          set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> respond with the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the
    776          resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
    777          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>.
    778       </p>
    779       <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>
    780       <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>
    781       <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    782       </p>
    783       <ul>
    784          <li>Method Name (see <a href="#method" title="Method">Section&nbsp;2</a>)
    785          </li>
    786          <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>)
    787          </li>
    788          <li>Pointer to specification text</li>
    789       </ul>
    790       <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>).
    791       </p>
    792       <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;.
    793       </p>
    794       <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
    795       <p id="rfc.section.2.1.1.p.1">When it is necessary to express new semantics for a HTTP request that aren't specific to a single application or media type,
    796          and currently defined methods are inadequate, it may be appropriate to register a new method.
    797       </p>
    798       <p id="rfc.section.2.1.1.p.2">HTTP methods are generic; that is, they are potentially applicable to any resource, not just one particular media type, "type"
    799          of resource, or application. As such, it is preferred that new HTTP methods be registered in a document that isn't specific
    800          to a single application, so that this is clear.
    801       </p>
    802       <p id="rfc.section.2.1.1.p.3">Due to the parsing rules defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, definitions of HTTP methods cannot prohibit the presence of a message-body on either the request or the response message
    803          (with responses to HEAD requests being the single exception). Definitions of new methods cannot change this rule, but they
    804          can specify that only zero-length bodies (as opposed to absent bodies) are allowed.
    805       </p>
    806       <p id="rfc.section.2.1.1.p.4">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>) and whether they are idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;7.1.2</a>). They also need to state whether they can be cached (<a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>); in particular what conditions a cache may store the response, and under what conditions such a stored response may be used
    807          to satisfy a subsequent request.
    808       </p>
    809       <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>
    810       <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,
    811          to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language
    812          method invocation.
    813       </p>
    814       <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 6.1</a>
     799            set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> respond with the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the
     800            resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
     801            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>.
     802         </p>
     803         <div id="method.registry">
     804            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#method.registry">Method Registry</a></h2>
     805            <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>
     806            <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     807            </p>
     808            <ul>
     809               <li>Method Name (see <a href="#method" title="Method">Section&nbsp;2</a>)
     810               </li>
     811               <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>)
     812               </li>
     813               <li>Pointer to specification text</li>
     814            </ul>
     815            <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>).
     816            </p>
     817            <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;.
     818            </p>
     819            <div id="considerations.for.new.methods">
     820               <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
     821               <p id="rfc.section.2.1.1.p.1">When it is necessary to express new semantics for a HTTP request that aren't specific to a single application or media type,
     822                  and currently defined methods are inadequate, it may be appropriate to register a new method.
     823               </p>
     824               <p id="rfc.section.2.1.1.p.2">HTTP methods are generic; that is, they are potentially applicable to any resource, not just one particular media type, "type"
     825                  of resource, or application. As such, it is preferred that new HTTP methods be registered in a document that isn't specific
     826                  to a single application, so that this is clear.
     827               </p>
     828               <p id="rfc.section.2.1.1.p.3">Due to the parsing rules defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, definitions of HTTP methods cannot prohibit the presence of a message-body on either the request or the response message
     829                  (with responses to HEAD requests being the single exception). Definitions of new methods cannot change this rule, but they
     830                  can specify that only zero-length bodies (as opposed to absent bodies) are allowed.
     831               </p>
     832               <p id="rfc.section.2.1.1.p.4">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>) and whether they are idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section&nbsp;7.1.2</a>). They also need to state whether they can be cached (<a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>); in particular what conditions a cache may store the response, and under what conditions such a stored response may be used
     833                  to satisfy a subsequent request.
     834               </p>
     835            </div>
     836         </div>
     837      </div>
     838      <div id="request.header.fields">
     839         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#request.header.fields">Request Header Fields</a></h1>
     840         <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,
     841            to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language
     842            method invocation.
     843         </p>
     844         <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 6.1</a>
    815845                 / <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 6.2</a>
    816846                 / <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 6.3</a>
     
    832862                 / <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>
    833863</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
    834          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.
    835       </p>
    836       <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>
    837       <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
    838          codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;8</a>, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.7"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>.
    839       </p>
    840       <p id="rfc.section.4.p.2">The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use
    841          by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.
    842       </p>
    843       <p id="rfc.section.4.p.3">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase
    844          values, 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.
    845       </p>
    846       <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> =
     864            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.
     865         </p>
     866      </div>
     867      <div id="status.code.and.reason.phrase">
     868         <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>
     869         <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
     870            codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;8</a>, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.7"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>.
     871         </p>
     872         <p id="rfc.section.4.p.2">The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use
     873            by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.
     874         </p>
     875         <p id="rfc.section.4.p.3">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase
     876            values, 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.
     877         </p>
     878         <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> =
    847879       "100"  ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;8.1.1</a>: Continue
    848880     / "101"  ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;8.1.2</a>: Switching Protocols
     
    890922  <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> )
    891923</pre><p id="rfc.section.4.p.5">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
    892          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
    893          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
    894          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 representation enclosed with the response, since that representation is likely to include human-readable
    895          information which will explain the unusual status.
    896       </p>
    897       <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>
    898       <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>
    899       <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>).
    900       </p>
    901       <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;.
    902       </p>
    903       <h3 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;<a id="considerations.for.new.status.codes" href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h3>
    904       <p id="rfc.section.4.1.1.p.1">When it is necessary to express new semantics for a HTTP response that aren't specific to a single application or media type,
    905          and currently defined status codes are inadequate, a new status code can be registered.
    906       </p>
    907       <p id="rfc.section.4.1.1.p.2">HTTP status codes are generic; that is, they are potentially applicable to any resource, not just one particular media type,
    908          "type" of resource, or application. As such, it is preferred that new HTTP status codes be registered in a document that isn't
    909          specific to a single application, so that this is clear.
    910       </p>
    911       <p id="rfc.section.4.1.1.p.3">Definitions of new HTTP status codes typically explain the request conditions that produce a response containing the status
    912          code (e.g., combinations of request headers and/or method(s)), along with any interactions with response headers (e.g., those
    913          that are required, those that modify the semantics of the response).
    914       </p>
    915       <p id="rfc.section.4.1.1.p.4">New HTTP status codes are required to fall under one of the categories defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;8</a>. To allow existing parsers to properly handle them, new status codes cannot disallow a response body, although they can mandate
    916          a zero-length response body. They can require the presence of one or more particular HTTP response header(s).
    917       </p>
    918       <p id="rfc.section.4.1.1.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section&nbsp;6.1</a>; by default, it is anonymous).
    919       </p>
    920       <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>
    921       <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
    922          Status-Line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</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>).
    923       </p>
    924       <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.9"><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>
     924            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
     925            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
     926            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 representation enclosed with the response, since that representation is likely to include human-readable
     927            information which will explain the unusual status.
     928         </p>
     929         <div id="status.code.registry">
     930            <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>
     931            <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>
     932            <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>).
     933            </p>
     934            <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;.
     935            </p>
     936            <div id="considerations.for.new.status.codes">
     937               <h3 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a>&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h3>
     938               <p id="rfc.section.4.1.1.p.1">When it is necessary to express new semantics for a HTTP response that aren't specific to a single application or media type,
     939                  and currently defined status codes are inadequate, a new status code can be registered.
     940               </p>
     941               <p id="rfc.section.4.1.1.p.2">HTTP status codes are generic; that is, they are potentially applicable to any resource, not just one particular media type,
     942                  "type" of resource, or application. As such, it is preferred that new HTTP status codes be registered in a document that isn't
     943                  specific to a single application, so that this is clear.
     944               </p>
     945               <p id="rfc.section.4.1.1.p.3">Definitions of new HTTP status codes typically explain the request conditions that produce a response containing the status
     946                  code (e.g., combinations of request headers and/or method(s)), along with any interactions with response headers (e.g., those
     947                  that are required, those that modify the semantics of the response).
     948               </p>
     949               <p id="rfc.section.4.1.1.p.4">New HTTP status codes are required to fall under one of the categories defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;8</a>. To allow existing parsers to properly handle them, new status codes cannot disallow a response body, although they can mandate
     950                  a zero-length response body. They can require the presence of one or more particular HTTP response header(s).
     951               </p>
     952               <p id="rfc.section.4.1.1.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section&nbsp;6.1</a>; by default, it is anonymous).
     953               </p>
     954            </div>
     955         </div>
     956      </div>
     957      <div id="response.header.fields">
     958         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#response.header.fields">Response Header Fields</a></h1>
     959         <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
     960            Status-Line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</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>).
     961         </p>
     962         <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.9"><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>
    925963                  / <a href="#abnf.dependencies" class="smpl">Age</a>                     ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 3.1</a>
    926964                  / <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>
     
    933971                  / <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a>        ; <a href="#Part7" id="rfc.xref.Part7.11"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a>
    934972</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
    935          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
    936          fields.
    937       </p>
    938       <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="representation" href="#representation">Representation</a></h1>
    939       <p id="rfc.section.6.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer a representation if not otherwise restricted by the request method or response status code. A representation consists
    940          of metadata (representation header fields) and data (representation body). When a complete or partial representation is enclosed
    941          in an HTTP message, it is referred to as the payload of the message. HTTP representations 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>.
    942       </p>
    943       <p id="rfc.section.6.p.2">A representation body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The representation body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied
    944          to ensure safe and proper transfer of the message.
    945       </p>
    946       <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>
    947       <p id="rfc.section.6.1.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p>
    948       <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>
    949       <p id="rfc.section.6.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</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>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
    950          rules are used (with the first applicable one being selected):
    951       </p>
    952       <ol>
    953          <li>If the response status code is 200 or 203 and the request method was GET, the response payload is a representation of the
    954             target resource.
    955          </li>
    956          <li>If the response status code is 204, 206, or 304 and the request method was GET or HEAD, the response payload is a partial
    957             representation of the target (see <a href="p6-cache.html#combining.responses" title="Combining Responses">Section 2.8</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    958          </li>
    959          <li>If the response has a Content-Location header field, and that URI is the same as the effective request URI, the response payload
    960             is a representation of the target resource.
    961          </li>
    962          <li>If the response has a Content-Location header field, and that URI is not the same as the effective request URI, then the response
    963             asserts that its payload is a representation of the resource identified by the Content-Location URI. However, such an assertion
    964             cannot be trusted unless it can be verified by other means (not defined by HTTP).
    965          </li>
    966          <li>Otherwise, the response is a representation of an anonymous (i.e., unidentified) resource.</li>
    967       </ol>
    968       <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>: The comparison function is going to have to be defined somewhere, because we already need to compare URIs for things like
    969             cache invalidation.]</span>
    970       </p>
    971       <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="method.definitions" 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       <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>
    976       <div id="rfc.iref.s.1"></div>
    977       <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>
    978       <p id="rfc.section.7.1.1.p.1">Implementors need to be aware that the software represents the user in their interactions over the Internet, and need to allow
    979          the user to be aware of any actions they take which might have an unexpected significance to themselves or others.
    980       </p>
    981       <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
    982          made aware of the fact that a possibly unsafe action is being requested.
    983       </p>
    984       <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;
    985          in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the
    986          side-effects, so therefore cannot be held accountable for them.
    987       </p>
    988       <div id="rfc.iref.i.1"></div>
    989       <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>
    990       <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
    991          multiple identical requests is the same as for a single request. The methods PUT, DELETE, and all safe methods are idempotent.
    992          It is important to note that idempotence refers only to changes requested by the client: a server is free to change its state
    993          due to multiple requests for the purpose of tracking those requests, versioning of results, etc.
    994       </p>
    995       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2>
    996       <div id="rfc.iref.o.1"></div>
    997       <div id="rfc.iref.m.1"></div>
    998       <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
    999          chain identified by the effective request URI. This method allows the client to determine the options and/or requirements
    1000          associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
    1001       </p>
    1002       <p id="rfc.section.7.2.p.2">Responses to this method are not cacheable.</p>
    1003       <p id="rfc.section.7.2.p.3">If the OPTIONS request includes a message-body (as indicated by the presence of Content-Length or Transfer-Encoding), then
    1004          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
    1005          to HTTP might use the OPTIONS body to make more detailed queries on the server.
    1006       </p>
    1007       <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
    1008          to a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
    1009          as a "ping" or "no-op" type of method; it does nothing beyond allowing the client to test the capabilities of the server.
    1010          For example, this can be used to test a proxy for HTTP/1.1 compliance (or lack thereof).
    1011       </p>
    1012       <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
    1013          with that resource.
    1014       </p>
    1015       <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.,
    1016          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,
    1017          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".
    1018       </p>
    1019       <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 (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;9.5</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
    1020       </p>
    1021       <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="GET" href="#GET">GET</a></h2>
    1022       <div id="rfc.iref.g.8"></div>
    1023       <div id="rfc.iref.m.2"></div>
    1024       <p id="rfc.section.7.3.p.1">The GET method means retrieve whatever information (in the form of a representation) currently corresponds to the target resource.</p>
    1025       <p id="rfc.section.7.3.p.2">If the target resource is a data-producing process, it is the produced data which shall be returned as the representation
    1026          in the response and not the source text of the process, unless that text happens to be the output of the process.
    1027       </p>
    1028       <p id="rfc.section.7.3.p.3">The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since,
    1029          If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the representation be transferred
    1030          only under the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce
    1031          unnecessary network usage by allowing cached representations to be refreshed without requiring multiple requests or transferring
    1032          data already held by the client.
    1033       </p>
    1034       <p id="rfc.section.7.3.p.4">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial
    1035          GET requests that only part of the representation 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.10"><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 representations to
    1036          be completed without transferring data already held by the client.
    1037       </p>
    1038       <p id="rfc.section.7.3.p.5">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    1039       </p>
    1040       <p id="rfc.section.7.3.p.6">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.
    1041       </p>
    1042       <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h2>
    1043       <div id="rfc.iref.h.1"></div>
    1044       <div id="rfc.iref.m.3"></div>
    1045       <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 metadata contained in the HTTP header fields 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 metadata about the
    1046          representation implied by the request without transferring the representation body. This method is often used for testing
    1047          hypertext links for validity, accessibility, and recent modification.
    1048       </p>
    1049       <p id="rfc.section.7.4.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request; see <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. It also <em class="bcp14">MAY</em> be used to update a previously cached representation from that resource; if the new field values indicate that the cached
    1050          representation differs from the current representation (as would be indicated by a change in Content-Length, Content-MD5,
    1051          ETag or Last-Modified), then the cache <em class="bcp14">MUST</em> treat the cache entry as stale.
    1052       </p>
    1053       <div id="rfc.iref.p.1"></div>
    1054       <div id="rfc.iref.m.4"></div>
    1055       <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="POST" href="#POST">POST</a></h2>
    1056       <p id="rfc.section.7.5.p.1">The POST method is used to request that the origin server accept the representation enclosed in the request as data to be
    1057          processed by the target resource. POST is designed to allow a uniform method to cover the following functions:
    1058       </p>
    1059       <ul>
    1060          <li>Annotation of existing resources;</li>
    1061          <li>Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;</li>
    1062          <li>Providing a block of data, such as the result of submitting a form, to a data-handling process;</li>
    1063          <li>Extending a database through an append operation.</li>
    1064       </ul>
    1065       <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 effective request
    1066          URI.
    1067       </p>
    1068       <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
    1069          200 (OK) or 204 (No Content) is the appropriate response status code, depending on whether or not the response includes a
    1070          representation that describes the result.
    1071       </p>
    1072       <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 a representation which describes the status of the request and refers to the new resource, and
    1073          a Location header field (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;9.4</a>).
    1074       </p>
    1075       <p id="rfc.section.7.5.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a Content-Location header field (see <a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
    1076       </p>
    1077       <p id="rfc.section.7.5.p.6">Note that POST caching is not widely implemented. However, the 303 (See Other) response can be used to direct the user agent
    1078          to retrieve a cacheable resource.
    1079       </p>
    1080       <div id="rfc.iref.p.2"></div>
    1081       <div id="rfc.iref.m.5"></div>
    1082       <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h2>
    1083       <p id="rfc.section.7.6.p.1">The PUT method requests that the enclosed representation be stored at the effective request URI. If the effective request
    1084          URI refers to an already existing resource, the enclosed representation <em class="bcp14">SHOULD</em> be considered a modified version of the one residing on the origin server. Otherwise, if the effective request URI does not
    1085          point to an existing resource, and that URI is capable of being defined as a new resource by the requesting user agent, the
    1086          origin server can create the resource with that URI.
    1087       </p>
    1088       <p id="rfc.section.7.6.p.2">If a new resource is created at the effective request URI, 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
    1089          Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request.
    1090       </p>
    1091       <p id="rfc.section.7.6.p.3">If the target resource could not be created or modified, an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the representation <em class="bcp14">MUST NOT</em> ignore any Content-* header fields (headers starting with the prefix "Content-") that it does not understand or implement
    1092          and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
    1093       </p>
    1094       <p id="rfc.section.7.6.p.4">If the request passes through a cache that has one or more stored responses for the effective request URI, those stored responses <em class="bcp14">SHOULD</em> be marked as stale if the response to the PUT request has a success status code. Responses to the PUT method are not cacheable.
    1095       </p>
    1096       <p id="rfc.section.7.6.p.5">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the effective request
    1097          URI. The URI in a POST request identifies the resource that will handle the enclosed representation. That resource might be
    1098          a data-accepting process, a gateway to some other protocol, or a document that accepts annotations. In contrast, the URI in
    1099          a PUT request identifies the resource for which enclosed representation is a new or replacement value; the user agent knows
    1100          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,
    1101          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.
    1102       </p>
    1103       <p id="rfc.section.7.6.p.6">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
    1104          is separate from the URI identifying each particular version. In this case, a PUT request on a general URI might result in
    1105          several other URIs being defined by the origin server.
    1106       </p>
    1107       <p id="rfc.section.7.6.p.7">HTTP/1.1 does not define how a PUT method affects the state of an origin server.</p>
    1108       <p id="rfc.section.7.6.p.8">Header fields in a PUT request that are recognized as representation metadata <em class="bcp14">SHOULD</em> be applied to the resource created or modified by the PUT. Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored.
    1109       </p>
    1110       <div id="rfc.iref.d.1"></div>
    1111       <div id="rfc.iref.m.6"></div>
    1112       <h2 id="rfc.section.7.7"><a href="#rfc.section.7.7">7.7</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h2>
    1113       <p id="rfc.section.7.7.p.1">The DELETE method requests that the origin server delete the target resource. 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
    1114          has been carried out, even if the status code returned from the origin server indicates that the action has been completed
    1115          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
    1116          location.
    1117       </p>
    1118       <p id="rfc.section.7.7.p.2">A successful response <em class="bcp14">SHOULD</em> be 200 (OK) if the response includes an representation describing the status, 202 (Accepted) if the action has not yet been
    1119          enacted, or 204 (No Content) if the action has been enacted but the response does not include a representation.
    1120       </p>
    1121       <p id="rfc.section.7.7.p.3">If the request passes through a cache and the effective request URI identifies one or more currently cached representations,
    1122          those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to the DELETE method are not cacheable.
    1123       </p>
    1124       <h2 id="rfc.section.7.8"><a href="#rfc.section.7.8">7.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h2>
    1125       <div id="rfc.iref.t.1"></div>
    1126       <div id="rfc.iref.m.7"></div>
    1127       <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
    1128          request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message-body of a 200 (OK) response. The final recipient is either
    1129          the 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.3" title="Max-Forwards">Section&nbsp;9.5</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message-body.
    1130       </p>
    1131       <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
    1132          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.24"><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
    1133          client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an
    1134          infinite loop.
    1135       </p>
    1136       <p id="rfc.section.7.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have 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.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and contain a message-body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
    1137       </p>
    1138       <div id="rfc.iref.c.1"></div>
    1139       <div id="rfc.iref.m.8"></div>
    1140       <h2 id="rfc.section.7.9"><a href="#rfc.section.7.9">7.9</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h2>
    1141       <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.,
    1142          SSL tunneling <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>).
    1143       </p>
    1144       <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>
    1145       <p id="rfc.section.8.p.1">Each Status-Code is described below, including any metadata required in the response.</p>
    1146       <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>
    1147       <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 header fields,
    1148          and is terminated by an empty line. There are no required header fields for this class of status code. Since HTTP/1.0 did
    1149          not define any 1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions.
    1150       </p>
    1151       <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
    1152          (Continue) status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
    1153       </p>
    1154       <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
    1155          requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards
    1156          a request, then it need not forward the corresponding 100 (Continue) response(s).)
    1157       </p>
    1158       <div id="rfc.iref.25"></div>
    1159       <div id="rfc.iref.s.2"></div>
    1160       <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>
    1161       <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
    1162          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
    1163          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.26"><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.
    1164       </p>
    1165       <div id="rfc.iref.26"></div>
    1166       <div id="rfc.iref.s.3"></div>
    1167       <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>
    1168       <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="p1-messaging.html#header.upgrade" title="Upgrade">Section 9.8</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>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
    1169          by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
    1170       </p>
    1171       <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
    1172          older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
    1173          such features.
    1174       </p>
    1175       <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>
    1176       <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>
    1177       <div id="rfc.iref.27"></div>
    1178       <div id="rfc.iref.s.4"></div>
    1179       <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>
    1180       <p id="rfc.section.8.2.1.p.1">The request has succeeded. The payload returned with the response is dependent on the method used in the request, for example: </p>
    1181       <dl>
    1182          <dt>GET</dt>
    1183          <dd>a representation of the target resource is sent in the response;</dd>
    1184          <dt>HEAD</dt>
    1185          <dd>the same representation as GET, except without the message-body;</dd>
    1186          <dt>POST</dt>
    1187          <dd>a representation describing or containing the result of the action;</dd>
    1188          <dt>TRACE</dt>
    1189          <dd>a representation containing the request message as received by the end server.</dd>
    1190       </dl>
    1191       <p id="rfc.section.8.2.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    1192       </p>
    1193       <div id="rfc.iref.28"></div>
    1194       <div id="rfc.iref.s.5"></div>
    1195       <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>
    1196       <p id="rfc.section.8.2.2.p.1">The request has been fulfilled and has resulted in a new resource being created. The newly created resource can be referenced
    1197          by the URI(s) returned in the payload of the response, with the most specific URI for the resource given by a Location header
    1198          field. The response <em class="bcp14">SHOULD</em> include a payload containing a list of resource characteristics and location(s) from which the user or user agent can choose
    1199          the one most appropriate. The payload format is specified by the media type given in the Content-Type header field. The origin
    1200          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.
    1201       </p>
    1202       <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 representation of the resource
    1203          just created (see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.14"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    1204       </p>
    1205       <div id="rfc.iref.29"></div>
    1206       <div id="rfc.iref.s.6"></div>
    1207       <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>
    1208       <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
    1209          be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
    1210          code from an asynchronous operation such as this.
    1211       </p>
    1212       <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
    1213          (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
    1214          server persist until the process is completed. The representation 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
    1215          user can expect the request to be fulfilled.
    1216       </p>
    1217       <div id="rfc.iref.30"></div>
    1218       <div id="rfc.iref.s.7"></div>
    1219       <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>
    1220       <p id="rfc.section.8.2.4.p.1">The returned metadata in the header fields is not the definitive set as available from the origin server, but is gathered
    1221          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
    1222          result in a superset of the metadata known by the origin server. Use of this response code is not required and is only appropriate
    1223          when the response would otherwise be 200 (OK).
    1224       </p>
    1225       <p id="rfc.section.8.2.4.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
    1226       </p>
    1227       <div id="rfc.iref.31"></div>
    1228       <div id="rfc.iref.s.8"></div>
    1229       <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>
    1230       <p id="rfc.section.8.2.5.p.1">The server has successfully fulfilled the request, but there is no additional content to return in the response payload body.
    1231          The resource metadata and representation metadata in the response message's header fields refer to the target resource and
    1232          its current representation, respectively, after the requested action. For example, if a 204 status code is received in response
    1233          to a PUT and the response contains an ETag header field, then the value of that field is the current entity-tag for the representation
    1234          that was successfully PUT.
    1235       </p>
    1236       <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
    1237          for actions to take place without causing a change to the user agent's active document view, although any new or updated metadata <em class="bcp14">SHOULD</em> be applied to the document currently in the user agent's active view.
    1238       </p>
    1239       <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.
    1240       </p>
    1241       <div id="rfc.iref.32"></div>
    1242       <div id="rfc.iref.s.9"></div>
    1243       <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>
    1244       <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
    1245          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
    1246          another input action. The response <em class="bcp14">MUST NOT</em> include a message-body.
    1247       </p>
    1248       <div id="rfc.iref.33"></div>
    1249       <div id="rfc.iref.s.10"></div>
    1250       <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>
    1251       <p id="rfc.section.8.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed payload is a partial representation as
    1252          defined in <a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</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>.
    1253       </p>
    1254       <p id="rfc.section.8.2.7.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 206 responses.
    1255       </p>
    1256       <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>
    1257       <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.
    1258          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
    1259          known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection.
    1260       </p>
    1261       <div class="note" id="rfc.section.8.3.p.2">
    1262          <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 need to be aware that some clients might implement such a fixed limitation.
    1263          </p>
     973            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
     974            fields.
     975         </p>
    1264976      </div>
    1265       <div id="rfc.iref.34"></div>
    1266       <div id="rfc.iref.s.11"></div>
    1267       <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>
    1268       <p id="rfc.section.8.3.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information
    1269          (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</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>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
    1270          location.
    1271       </p>
    1272       <p id="rfc.section.8.3.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of representation metadata and location(s) from which the user or user agent can
    1273          choose the one most appropriate. The data format is specified by the media type given in the Content-Type header field. Depending
    1274          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.
    1275       </p>
    1276       <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.
    1277       </p>
    1278       <p id="rfc.section.8.3.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    1279       </p>
    1280       <div id="rfc.iref.35"></div>
    1281       <div id="rfc.iref.s.12"></div>
    1282       <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>
    1283       <p id="rfc.section.8.3.2.p.1">The target 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 effective
    1284          request URI to one or more of the new references returned by the server, where possible.
    1285       </p>
    1286       <p id="rfc.section.8.3.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
    1287       </p>
    1288       <p id="rfc.section.8.3.2.p.3">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 representation of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
    1289       </p>
    1290       <p id="rfc.section.8.3.2.p.4">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
    1291          the request was issued.
    1292       </p>
    1293       <div class="note" id="rfc.section.8.3.2.p.5">
    1294          <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
    1295             change it into a GET request.
    1296          </p>
     977      <div id="representation">
     978         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#representation">Representation</a></h1>
     979         <p id="rfc.section.6.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer a representation if not otherwise restricted by the request method or response status code. A representation consists
     980            of metadata (representation header fields) and data (representation body). When a complete or partial representation is enclosed
     981            in an HTTP message, it is referred to as the payload of the message. HTTP representations 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>.
     982         </p>
     983         <p id="rfc.section.6.p.2">A representation body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The representation body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied
     984            to ensure safe and proper transfer of the message.
     985         </p>
     986         <div id="identifying.response.associated.with.representation">
     987            <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>
     988            <p id="rfc.section.6.1.p.1">It is sometimes necessary to determine an identifier for the resource associated with a representation.</p>
     989            <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>
     990            <p id="rfc.section.6.1.p.3">In the common case, an HTTP response is a representation of the target resource (see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</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>). However, this is not always the case. To determine the URI of the resource a response is associated with, the following
     991               rules are used (with the first applicable one being selected):
     992            </p>
     993            <ol>
     994               <li>If the response status code is 200 or 203 and the request method was GET, the response payload is a representation of the
     995                  target resource.
     996               </li>
     997               <li>If the response status code is 204, 206, or 304 and the request method was GET or HEAD, the response payload is a partial
     998                  representation of the target (see <a href="p6-cache.html#combining.responses" title="Combining Responses">Section 2.8</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     999               </li>
     1000               <li>If the response has a Content-Location header field, and that URI is the same as the effective request URI, the response payload
     1001                  is a representation of the target resource.
     1002               </li>
     1003               <li>If the response has a Content-Location header field, and that URI is not the same as the effective request URI, then the response
     1004                  asserts that its payload is a representation of the resource identified by the Content-Location URI. However, such an assertion
     1005                  cannot be trusted unless it can be verified by other means (not defined by HTTP).
     1006               </li>
     1007               <li>Otherwise, the response is a representation of an anonymous (i.e., unidentified) resource.</li>
     1008            </ol>
     1009            <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>: The comparison function is going to have to be defined somewhere, because we already need to compare URIs for things like
     1010                  cache invalidation.]</span>
     1011            </p>
     1012         </div>
    12971013      </div>
    1298       <div id="rfc.iref.36"></div>
    1299       <div id="rfc.iref.s.13"></div>
    1300       <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>
    1301       <p id="rfc.section.8.3.3.p.1">The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
    1302       </p>
    1303       <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 representation of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
    1304       </p>
    1305       <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
    1306          the request was issued.
    1307       </p>
    1308       <div class="note" id="rfc.section.8.3.3.p.4">
    1309          <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
    1310             implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original
    1311             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.
    1312          </p>
     1014      <div id="method.definitions">
     1015         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#method.definitions">Method Definitions</a></h1>
     1016         <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
     1017            to share the same semantics for separately extended clients and servers.
     1018         </p>
     1019         <div id="safe.and.idempotent">
     1020            <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>
     1021            <div id="safe.methods">
     1022               <div id="rfc.iref.s.1"></div>
     1023               <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>
     1024               <p id="rfc.section.7.1.1.p.1">Implementors need to be aware that the software represents the user in their interactions over the Internet, and need to allow
     1025                  the user to be aware of any actions they take which might have an unexpected significance to themselves or others.
     1026               </p>
     1027               <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
     1028                  made aware of the fact that a possibly unsafe action is being requested.
     1029               </p>
     1030               <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;
     1031                  in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the
     1032                  side-effects, so therefore cannot be held accountable for them.
     1033               </p>
     1034            </div>
     1035            <div id="idempotent.methods">
     1036               <div id="rfc.iref.i.1"></div>
     1037               <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>
     1038               <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
     1039                  multiple identical requests is the same as for a single request. The methods PUT, DELETE, and all safe methods are idempotent.
     1040                  It is important to note that idempotence refers only to changes requested by the client: a server is free to change its state
     1041                  due to multiple requests for the purpose of tracking those requests, versioning of results, etc.
     1042               </p>
     1043            </div>
     1044         </div>
     1045         <div id="OPTIONS">
     1046            <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#OPTIONS">OPTIONS</a></h2>
     1047            <div id="rfc.iref.o.1"></div>
     1048            <div id="rfc.iref.m.1"></div>
     1049            <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
     1050               chain identified by the effective request URI. This method allows the client to determine the options and/or requirements
     1051               associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
     1052            </p>
     1053            <p id="rfc.section.7.2.p.2">Responses to this method are not cacheable.</p>
     1054            <p id="rfc.section.7.2.p.3">If the OPTIONS request includes a message-body (as indicated by the presence of Content-Length or Transfer-Encoding), then
     1055               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
     1056               to HTTP might use the OPTIONS body to make more detailed queries on the server.
     1057            </p>
     1058            <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
     1059               to a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
     1060               as a "ping" or "no-op" type of method; it does nothing beyond allowing the client to test the capabilities of the server.
     1061               For example, this can be used to test a proxy for HTTP/1.1 compliance (or lack thereof).
     1062            </p>
     1063            <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
     1064               with that resource.
     1065            </p>
     1066            <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.,
     1067               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,
     1068               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".
     1069            </p>
     1070            <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 (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;9.5</a>). If no Max-Forwards field is present in the request, then the forwarded request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
     1071            </p>
     1072         </div>
     1073         <div id="GET">
     1074            <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a href="#GET">GET</a></h2>
     1075            <div id="rfc.iref.g.8"></div>
     1076            <div id="rfc.iref.m.2"></div>
     1077            <p id="rfc.section.7.3.p.1">The GET method means retrieve whatever information (in the form of a representation) currently corresponds to the target resource.</p>
     1078            <p id="rfc.section.7.3.p.2">If the target resource is a data-producing process, it is the produced data which shall be returned as the representation
     1079               in the response and not the source text of the process, unless that text happens to be the output of the process.
     1080            </p>
     1081            <p id="rfc.section.7.3.p.3">The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since,
     1082               If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the representation be transferred
     1083               only under the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce
     1084               unnecessary network usage by allowing cached representations to be refreshed without requiring multiple requests or transferring
     1085               data already held by the client.
     1086            </p>
     1087            <p id="rfc.section.7.3.p.4">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial
     1088               GET requests that only part of the representation 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.10"><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 representations to
     1089               be completed without transferring data already held by the client.
     1090            </p>
     1091            <p id="rfc.section.7.3.p.5">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1092            </p>
     1093            <p id="rfc.section.7.3.p.6">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.
     1094            </p>
     1095         </div>
     1096         <div id="HEAD">
     1097            <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a href="#HEAD">HEAD</a></h2>
     1098            <div id="rfc.iref.h.1"></div>
     1099            <div id="rfc.iref.m.3"></div>
     1100            <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 metadata contained in the HTTP header fields 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 metadata about the
     1101               representation implied by the request without transferring the representation body. This method is often used for testing
     1102               hypertext links for validity, accessibility, and recent modification.
     1103            </p>
     1104            <p id="rfc.section.7.4.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request; see <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. It also <em class="bcp14">MAY</em> be used to update a previously cached representation from that resource; if the new field values indicate that the cached
     1105               representation differs from the current representation (as would be indicated by a change in Content-Length, Content-MD5,
     1106               ETag or Last-Modified), then the cache <em class="bcp14">MUST</em> treat the cache entry as stale.
     1107            </p>
     1108         </div>
     1109         <div id="POST">
     1110            <div id="rfc.iref.p.1"></div>
     1111            <div id="rfc.iref.m.4"></div>
     1112            <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a href="#POST">POST</a></h2>
     1113            <p id="rfc.section.7.5.p.1">The POST method is used to request that the origin server accept the representation enclosed in the request as data to be
     1114               processed by the target resource. POST is designed to allow a uniform method to cover the following functions:
     1115            </p>
     1116            <ul>
     1117               <li>Annotation of existing resources;</li>
     1118               <li>Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;</li>
     1119               <li>Providing a block of data, such as the result of submitting a form, to a data-handling process;</li>
     1120               <li>Extending a database through an append operation.</li>
     1121            </ul>
     1122            <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 effective request
     1123               URI.
     1124            </p>
     1125            <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
     1126               200 (OK) or 204 (No Content) is the appropriate response status code, depending on whether or not the response includes a
     1127               representation that describes the result.
     1128            </p>
     1129            <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 a representation which describes the status of the request and refers to the new resource, and
     1130               a Location header field (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;9.4</a>).
     1131            </p>
     1132            <p id="rfc.section.7.5.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 2.3.1</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a Content-Location header field (see <a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
     1133            </p>
     1134            <p id="rfc.section.7.5.p.6">Note that POST caching is not widely implemented. However, the 303 (See Other) response can be used to direct the user agent
     1135               to retrieve a cacheable resource.
     1136            </p>
     1137         </div>
     1138         <div id="PUT">
     1139            <div id="rfc.iref.p.2"></div>
     1140            <div id="rfc.iref.m.5"></div>
     1141            <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a href="#PUT">PUT</a></h2>
     1142            <p id="rfc.section.7.6.p.1">The PUT method requests that the enclosed representation be stored at the effective request URI. If the effective request
     1143               URI refers to an already existing resource, the enclosed representation <em class="bcp14">SHOULD</em> be considered a modified version of the one residing on the origin server. Otherwise, if the effective request URI does not
     1144               point to an existing resource, and that URI is capable of being defined as a new resource by the requesting user agent, the
     1145               origin server can create the resource with that URI.
     1146            </p>
     1147            <p id="rfc.section.7.6.p.2">If a new resource is created at the effective request URI, 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
     1148               Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request.
     1149            </p>
     1150            <p id="rfc.section.7.6.p.3">If the target resource could not be created or modified, an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the representation <em class="bcp14">MUST NOT</em> ignore any Content-* header fields (headers starting with the prefix "Content-") that it does not understand or implement
     1151               and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
     1152            </p>
     1153            <p id="rfc.section.7.6.p.4">If the request passes through a cache that has one or more stored responses for the effective request URI, those stored responses <em class="bcp14">SHOULD</em> be marked as stale if the response to the PUT request has a success status code. Responses to the PUT method are not cacheable.
     1154            </p>
     1155            <p id="rfc.section.7.6.p.5">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the effective request
     1156               URI. The URI in a POST request identifies the resource that will handle the enclosed representation. That resource might be
     1157               a data-accepting process, a gateway to some other protocol, or a document that accepts annotations. In contrast, the URI in
     1158               a PUT request identifies the resource for which enclosed representation is a new or replacement value; the user agent knows
     1159               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,
     1160               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.
     1161            </p>
     1162            <p id="rfc.section.7.6.p.6">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
     1163               is separate from the URI identifying each particular version. In this case, a PUT request on a general URI might result in
     1164               several other URIs being defined by the origin server.
     1165            </p>
     1166            <p id="rfc.section.7.6.p.7">HTTP/1.1 does not define how a PUT method affects the state of an origin server.</p>
     1167            <p id="rfc.section.7.6.p.8">Header fields in a PUT request that are recognized as representation metadata <em class="bcp14">SHOULD</em> be applied to the resource created or modified by the PUT. Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored.
     1168            </p>
     1169         </div>
     1170         <div id="DELETE">
     1171            <div id="rfc.iref.d.1"></div>
     1172            <div id="rfc.iref.m.6"></div>
     1173            <h2 id="rfc.section.7.7"><a href="#rfc.section.7.7">7.7</a>&nbsp;<a href="#DELETE">DELETE</a></h2>
     1174            <p id="rfc.section.7.7.p.1">The DELETE method requests that the origin server delete the target resource. 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
     1175               has been carried out, even if the status code returned from the origin server indicates that the action has been completed
     1176               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
     1177               location.
     1178            </p>
     1179            <p id="rfc.section.7.7.p.2">A successful response <em class="bcp14">SHOULD</em> be 200 (OK) if the response includes an representation describing the status, 202 (Accepted) if the action has not yet been
     1180               enacted, or 204 (No Content) if the action has been enacted but the response does not include a representation.
     1181            </p>
     1182            <p id="rfc.section.7.7.p.3">If the request passes through a cache and the effective request URI identifies one or more currently cached representations,
     1183               those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to the DELETE method are not cacheable.
     1184            </p>
     1185         </div>
     1186         <div id="TRACE">
     1187            <h2 id="rfc.section.7.8"><a href="#rfc.section.7.8">7.8</a>&nbsp;<a href="#TRACE">TRACE</a></h2>
     1188            <div id="rfc.iref.t.1"></div>
     1189            <div id="rfc.iref.m.7"></div>
     1190            <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
     1191               request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the message-body of a 200 (OK) response. The final recipient is either
     1192               the 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.3" title="Max-Forwards">Section&nbsp;9.5</a>). A TRACE request <em class="bcp14">MUST NOT</em> include a message-body.
     1193            </p>
     1194            <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
     1195               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.24"><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
     1196               client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an
     1197               infinite loop.
     1198            </p>
     1199            <p id="rfc.section.7.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> have 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.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and contain a message-body that encloses a copy of the entire request message. Responses to the TRACE method are not cacheable.
     1200            </p>
     1201         </div>
     1202         <div id="CONNECT">
     1203            <div id="rfc.iref.c.1"></div>
     1204            <div id="rfc.iref.m.8"></div>
     1205            <h2 id="rfc.section.7.9"><a href="#rfc.section.7.9">7.9</a>&nbsp;<a href="#CONNECT">CONNECT</a></h2>
     1206            <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.,
     1207               SSL tunneling <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>).
     1208            </p>
     1209         </div>
    13131210      </div>
    1314       <div id="rfc.iref.37"></div>
    1315       <div id="rfc.iref.s.14"></div>
    1316       <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>
    1317       <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
    1318          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,
    1319          be redirected again, or end with an error status. The Location URI is not a substitute reference for the effective request
    1320          URI.
    1321       </p>
    1322       <p id="rfc.section.8.3.4.p.2">The 303 status code is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action
    1323          to redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response
    1324          in a form that can be separately identified, bookmarked, and cached independent of the original request.
    1325       </p>
    1326       <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
    1327          transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the target resource, such
    1328          that the follow-on representation might be useful to recipients without implying that it adequately represents the target
    1329          resource. Note that answers to the questions of what can be represented, what representations are adequate, and what might
    1330          be a useful description are outside the scope of HTTP and thus entirely determined by the URI owner(s).
    1331       </p>
    1332       <p id="rfc.section.8.3.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
    1333       </p>
    1334       <div id="rfc.iref.38"></div>
    1335       <div id="rfc.iref.s.15"></div>
    1336       <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>
    1337       <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,
    1338          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.15"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    1339       </p>
    1340       <div id="rfc.iref.39"></div>
    1341       <div id="rfc.iref.s.16"></div>
    1342       <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>
    1343       <p id="rfc.section.8.3.6.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;A</a>), and is now deprecated.
    1344       </p>
    1345       <div id="rfc.iref.40"></div>
    1346       <div id="rfc.iref.s.17"></div>
    1347       <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>
    1348       <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>
    1349       <div id="rfc.iref.41"></div>
    1350       <div id="rfc.iref.s.18"></div>
    1351       <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>
    1352       <p id="rfc.section.8.3.8.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
    1353       </p>
    1354       <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 representation 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 the
    1355          307 status code. Therefore, the note <em class="bcp14">SHOULD</em> contain the information necessary for a user to repeat the original request on the new URI.
    1356       </p>
    1357       <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
    1358          the request was issued.
    1359       </p>
    1360       <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>
    1361       <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
    1362          request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    1363          These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
    1364       </p>
    1365       <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
    1366          the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send
    1367          a reset packet to the client, which might erase the client's unacknowledged input buffers before they can be read and interpreted
    1368          by the HTTP application.
    1369       </p>
    1370       <div id="rfc.iref.42"></div>
    1371       <div id="rfc.iref.s.19"></div>
    1372       <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>
    1373       <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.
    1374       </p>
    1375       <div id="rfc.iref.43"></div>
    1376       <div id="rfc.iref.s.20"></div>
    1377       <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>
    1378       <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 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.12"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
    1379       </p>
    1380       <div id="rfc.iref.44"></div>
    1381       <div id="rfc.iref.s.21"></div>
    1382       <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>
    1383       <p id="rfc.section.8.4.3.p.1">This code is reserved for future use.</p>
    1384       <div id="rfc.iref.45"></div>
    1385       <div id="rfc.iref.s.22"></div>
    1386       <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>
    1387       <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,
    1388          it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the representation. If the server does not wish to make this information available
    1389          to the client, the status code 404 (Not Found) can be used instead.
    1390       </p>
    1391       <div id="rfc.iref.46"></div>
    1392       <div id="rfc.iref.s.23"></div>
    1393       <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>
    1394       <p id="rfc.section.8.4.5.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary
    1395          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
    1396          and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
    1397          has been refused, or when no other response is applicable.
    1398       </p>
    1399       <div id="rfc.iref.47"></div>
    1400       <div id="rfc.iref.s.24"></div>
    1401       <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>
    1402       <p id="rfc.section.8.4.6.p.1">The method specified in the Request-Line is not allowed for the target resource. The response <em class="bcp14">MUST</em> include an Allow header field containing a list of valid methods for the requested resource.
    1403       </p>
    1404       <div id="rfc.iref.48"></div>
    1405       <div id="rfc.iref.s.25"></div>
    1406       <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>
    1407       <p id="rfc.section.8.4.7.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
    1408          not acceptable according to the accept header fields sent in the request.
    1409       </p>
    1410       <p id="rfc.section.8.4.7.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of available representation characteristics and location(s) from which the user
    1411          or user agent can choose the one most appropriate. The data format is specified by the media type given in the Content-Type
    1412          header field. 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.
    1413       </p>
    1414       <div class="note" id="rfc.section.8.4.7.p.3">
    1415          <p> <b>Note:</b> HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept header fields sent in the
    1416             request. In some cases, this might even be preferable to sending a 406 response. User agents are encouraged to inspect the
    1417             header fields of an incoming response to determine if it is acceptable.
    1418          </p>
     1211      <div id="status.codes">
     1212         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#status.codes">Status Code Definitions</a></h1>
     1213         <p id="rfc.section.8.p.1">Each Status-Code is described below, including any metadata required in the response.</p>
     1214         <div id="status.1xx">
     1215            <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a href="#status.1xx">Informational 1xx</a></h2>
     1216            <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 header fields,
     1217               and is terminated by an empty line. There are no required header fields for this class of status code. Since HTTP/1.0 did
     1218               not define any 1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions.
     1219            </p>
     1220            <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
     1221               (Continue) status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
     1222            </p>
     1223            <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
     1224               requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards
     1225               a request, then it need not forward the corresponding 100 (Continue) response(s).)
     1226            </p>
     1227            <div id="status.100">
     1228               <div id="rfc.iref.1.1"></div>
     1229               <div id="rfc.iref.s.2"></div>
     1230               <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>
     1231               <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
     1232                  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
     1233                  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.26"><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.
     1234               </p>
     1235            </div>
     1236            <div id="status.101">
     1237               <div id="rfc.iref.1.2"></div>
     1238               <div id="rfc.iref.s.3"></div>
     1239               <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>
     1240               <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="p1-messaging.html#header.upgrade" title="Upgrade">Section 9.8</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>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
     1241                  by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
     1242               </p>
     1243               <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
     1244                  older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
     1245                  such features.
     1246               </p>
     1247            </div>
     1248         </div>
     1249         <div id="status.2xx">
     1250            <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a href="#status.2xx">Successful 2xx</a></h2>
     1251            <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>
     1252            <div id="status.200">
     1253               <div id="rfc.iref.2.1"></div>
     1254               <div id="rfc.iref.s.4"></div>
     1255               <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>
     1256               <p id="rfc.section.8.2.1.p.1">The request has succeeded. The payload returned with the response is dependent on the method used in the request, for example: </p>
     1257               <dl>
     1258                  <dt>GET</dt>
     1259                  <dd>a representation of the target resource is sent in the response;</dd>
     1260                  <dt>HEAD</dt>
     1261                  <dd>the same representation as GET, except without the message-body;</dd>
     1262                  <dt>POST</dt>
     1263                  <dd>a representation describing or containing the result of the action;</dd>
     1264                  <dt>TRACE</dt>
     1265                  <dd>a representation containing the request message as received by the end server.</dd>
     1266               </dl>
     1267               <p id="rfc.section.8.2.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
     1268               </p>
     1269            </div>
     1270            <div id="status.201">
     1271               <div id="rfc.iref.2.2"></div>
     1272               <div id="rfc.iref.s.5"></div>
     1273               <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>
     1274               <p id="rfc.section.8.2.2.p.1">The request has been fulfilled and has resulted in a new resource being created. The newly created resource can be referenced
     1275                  by the URI(s) returned in the payload of the response, with the most specific URI for the resource given by a Location header
     1276                  field. The response <em class="bcp14">SHOULD</em> include a payload containing a list of resource characteristics and location(s) from which the user or user agent can choose
     1277                  the one most appropriate. The payload format is specified by the media type given in the Content-Type header field. The origin
     1278                  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.
     1279               </p>
     1280               <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 representation of the resource
     1281                  just created (see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.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>
     1284            <div id="status.202">
     1285               <div id="rfc.iref.2.3"></div>
     1286               <div id="rfc.iref.s.6"></div>
     1287               <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>
     1288               <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
     1289                  be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
     1290                  code from an asynchronous operation such as this.
     1291               </p>
     1292               <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
     1293                  (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
     1294                  server persist until the process is completed. The representation 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
     1295                  user can expect the request to be fulfilled.
     1296               </p>
     1297            </div>
     1298            <div id="status.203">
     1299               <div id="rfc.iref.2.4"></div>
     1300               <div id="rfc.iref.s.7"></div>
     1301               <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>
     1302               <p id="rfc.section.8.2.4.p.1">The returned metadata in the header fields is not the definitive set as available from the origin server, but is gathered
     1303                  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
     1304                  result in a superset of the metadata known by the origin server. Use of this response code is not required and is only appropriate
     1305                  when the response would otherwise be 200 (OK).
     1306               </p>
     1307               <p id="rfc.section.8.2.4.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
     1308               </p>
     1309            </div>
     1310            <div id="status.204">
     1311               <div id="rfc.iref.2.5"></div>
     1312               <div id="rfc.iref.s.8"></div>
     1313               <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>
     1314               <p id="rfc.section.8.2.5.p.1">The server has successfully fulfilled the request, but there is no additional content to return in the response payload body.
     1315                  The resource metadata and representation metadata in the response message's header fields refer to the target resource and
     1316                  its current representation, respectively, after the requested action. For example, if a 204 status code is received in response
     1317                  to a PUT and the response contains an ETag header field, then the value of that field is the current entity-tag for the representation
     1318                  that was successfully PUT.
     1319               </p>
     1320               <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
     1321                  for actions to take place without causing a change to the user agent's active document view, although any new or updated metadata <em class="bcp14">SHOULD</em> be applied to the document currently in the user agent's active view.
     1322               </p>
     1323               <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.
     1324               </p>
     1325            </div>
     1326            <div id="status.205">
     1327               <div id="rfc.iref.2.6"></div>
     1328               <div id="rfc.iref.s.9"></div>
     1329               <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>
     1330               <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
     1331                  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
     1332                  another input action. The response <em class="bcp14">MUST NOT</em> include a message-body.
     1333               </p>
     1334            </div>
     1335            <div id="status.206">
     1336               <div id="rfc.iref.2.7"></div>
     1337               <div id="rfc.iref.s.10"></div>
     1338               <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>
     1339               <p id="rfc.section.8.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed payload is a partial representation as
     1340                  defined in <a href="p5-range.html#status.206" title="206 Partial Content">Section 3.1</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>.
     1341               </p>
     1342               <p id="rfc.section.8.2.7.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 206 responses.
     1343               </p>
     1344            </div>
     1345         </div>
     1346         <div id="status.3xx">
     1347            <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a href="#status.3xx">Redirection 3xx</a></h2>
     1348            <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.
     1349               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
     1350               known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;7.1.1</a>. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection.
     1351            </p>
     1352            <div class="note" id="rfc.section.8.3.p.2">
     1353               <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 need to be aware that some clients might implement such a fixed limitation.
     1354               </p>
     1355            </div>
     1356            <div id="status.300">
     1357               <div id="rfc.iref.3.1"></div>
     1358               <div id="rfc.iref.s.11"></div>
     1359               <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>
     1360               <p id="rfc.section.8.3.1.p.1">The target resource has more than one representation, each with its own specific location, and agent-driven negotiation information
     1361                  (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</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>) is being provided so that the user (or user agent) can select a preferred representation by redirecting its request to that
     1362                  location.
     1363               </p>
     1364               <p id="rfc.section.8.3.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of representation metadata and location(s) from which the user or user agent can
     1365                  choose the one most appropriate. The data format is specified by the media type given in the Content-Type header field. Depending
     1366                  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.
     1367               </p>
     1368               <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.
     1369               </p>
     1370               <p id="rfc.section.8.3.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
     1371               </p>
     1372            </div>
     1373            <div id="status.301">
     1374               <div id="rfc.iref.3.2"></div>
     1375               <div id="rfc.iref.s.12"></div>
     1376               <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>
     1377               <p id="rfc.section.8.3.2.p.1">The target 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 effective
     1378                  request URI to one or more of the new references returned by the server, where possible.
     1379               </p>
     1380               <p id="rfc.section.8.3.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 301 responses.
     1381               </p>
     1382               <p id="rfc.section.8.3.2.p.3">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 representation of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
     1383               </p>
     1384               <p id="rfc.section.8.3.2.p.4">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
     1385                  the request was issued.
     1386               </p>
     1387               <div class="note" id="rfc.section.8.3.2.p.5">
     1388                  <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
     1389                     change it into a GET request.
     1390                  </p>
     1391               </div>
     1392            </div>
     1393            <div id="status.302">
     1394               <div id="rfc.iref.3.3"></div>
     1395               <div id="rfc.iref.s.13"></div>
     1396               <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>
     1397               <p id="rfc.section.8.3.3.p.1">The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
     1398               </p>
     1399               <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 representation of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
     1400               </p>
     1401               <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
     1402                  the request was issued.
     1403               </p>
     1404               <div class="note" id="rfc.section.8.3.3.p.4">
     1405                  <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
     1406                     implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original
     1407                     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.
     1408                  </p>
     1409               </div>
     1410            </div>
     1411            <div id="status.303">
     1412               <div id="rfc.iref.3.4"></div>
     1413               <div id="rfc.iref.s.14"></div>
     1414               <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>
     1415               <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
     1416                  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,
     1417                  be redirected again, or end with an error status. The Location URI is not a substitute reference for the effective request
     1418                  URI.
     1419               </p>
     1420               <p id="rfc.section.8.3.4.p.2">The 303 status code is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action
     1421                  to redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response
     1422                  in a form that can be separately identified, bookmarked, and cached independent of the original request.
     1423               </p>
     1424               <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
     1425                  transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the target resource, such
     1426                  that the follow-on representation might be useful to recipients without implying that it adequately represents the target
     1427                  resource. Note that answers to the questions of what can be represented, what representations are adequate, and what might
     1428                  be a useful description are outside the scope of HTTP and thus entirely determined by the URI owner(s).
     1429               </p>
     1430               <p id="rfc.section.8.3.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
     1431               </p>
     1432            </div>
     1433            <div id="status.304">
     1434               <div id="rfc.iref.3.5"></div>
     1435               <div id="rfc.iref.s.15"></div>
     1436               <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>
     1437               <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,
     1438                  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.15"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
     1439               </p>
     1440            </div>
     1441            <div id="status.305">
     1442               <div id="rfc.iref.3.6"></div>
     1443               <div id="rfc.iref.s.16"></div>
     1444               <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>
     1445               <p id="rfc.section.8.3.6.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;A</a>), and is now deprecated.
     1446               </p>
     1447            </div>
     1448            <div id="status.306">
     1449               <div id="rfc.iref.3.7"></div>
     1450               <div id="rfc.iref.s.17"></div>
     1451               <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>
     1452               <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>
     1453            </div>
     1454            <div id="status.307">
     1455               <div id="rfc.iref.3.8"></div>
     1456               <div id="rfc.iref.s.18"></div>
     1457               <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>
     1458               <p id="rfc.section.8.3.8.p.1">The target resource resides temporarily under a different URI. Since the redirection can change over time, the client <em class="bcp14">SHOULD</em> continue to use the effective request URI for future requests.
     1459               </p>
     1460               <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 representation 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 the
     1461                  307 status code. Therefore, the note <em class="bcp14">SHOULD</em> contain the information necessary for a user to repeat the original request on the new URI.
     1462               </p>
     1463               <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
     1464                  the request was issued.
     1465               </p>
     1466            </div>
     1467         </div>
     1468         <div id="status.4xx">
     1469            <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>
     1470            <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
     1471               request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
     1472               These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user.
     1473            </p>
     1474            <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
     1475               the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send
     1476               a reset packet to the client, which might erase the client's unacknowledged input buffers before they can be read and interpreted
     1477               by the HTTP application.
     1478            </p>
     1479            <div id="status.400">
     1480               <div id="rfc.iref.4.1"></div>
     1481               <div id="rfc.iref.s.19"></div>
     1482               <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>
     1483               <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.
     1484               </p>
     1485            </div>
     1486            <div id="status.401">
     1487               <div id="rfc.iref.4.2"></div>
     1488               <div id="rfc.iref.s.20"></div>
     1489               <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>
     1490               <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 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.12"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
     1491               </p>
     1492            </div>
     1493            <div id="status.402">
     1494               <div id="rfc.iref.4.3"></div>
     1495               <div id="rfc.iref.s.21"></div>
     1496               <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>
     1497               <p id="rfc.section.8.4.3.p.1">This code is reserved for future use.</p>
     1498            </div>
     1499            <div id="status.403">
     1500               <div id="rfc.iref.4.4"></div>
     1501               <div id="rfc.iref.s.22"></div>
     1502               <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>
     1503               <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,
     1504                  it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the representation. If the server does not wish to make this information available
     1505                  to the client, the status code 404 (Not Found) can be used instead.
     1506               </p>
     1507            </div>
     1508            <div id="status.404">
     1509               <div id="rfc.iref.4.5"></div>
     1510               <div id="rfc.iref.s.23"></div>
     1511               <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>
     1512               <p id="rfc.section.8.4.5.p.1">The server has not found anything matching the effective request URI. No indication is given of whether the condition is temporary
     1513                  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
     1514                  and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
     1515                  has been refused, or when no other response is applicable.
     1516               </p>
     1517            </div>
     1518            <div id="status.405">
     1519               <div id="rfc.iref.4.6"></div>
     1520               <div id="rfc.iref.s.24"></div>
     1521               <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>
     1522               <p id="rfc.section.8.4.6.p.1">The method specified in the Request-Line is not allowed for the target resource. The response <em class="bcp14">MUST</em> include an Allow header field containing a list of valid methods for the requested resource.
     1523               </p>
     1524            </div>
     1525            <div id="status.406">
     1526               <div id="rfc.iref.4.7"></div>
     1527               <div id="rfc.iref.s.25"></div>
     1528               <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>
     1529               <p id="rfc.section.8.4.7.p.1">The resource identified by the request is only capable of generating response representations which have content characteristics
     1530                  not acceptable according to the accept header fields sent in the request.
     1531               </p>
     1532               <p id="rfc.section.8.4.7.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include a representation containing a list of available representation characteristics and location(s) from which the user
     1533                  or user agent can choose the one most appropriate. The data format is specified by the media type given in the Content-Type
     1534                  header field. 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.
     1535               </p>
     1536               <div class="note" id="rfc.section.8.4.7.p.3">
     1537                  <p><b>Note:</b> HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept header fields sent in the
     1538                     request. In some cases, this might even be preferable to sending a 406 response. User agents are encouraged to inspect the
     1539                     header fields of an incoming response to determine if it is acceptable.
     1540                  </p>
     1541               </div>
     1542               <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.
     1543               </p>
     1544            </div>
     1545            <div id="status.407">
     1546               <div id="rfc.iref.4.8"></div>
     1547               <div id="rfc.iref.s.26"></div>
     1548               <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>
     1549               <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 3.2</a> of <a href="#Part7" id="rfc.xref.Part7.13"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
     1550               </p>
     1551            </div>
     1552            <div id="status.408">
     1553               <div id="rfc.iref.4.9"></div>
     1554               <div id="rfc.iref.s.27"></div>
     1555               <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>
     1556               <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.
     1557               </p>
     1558            </div>
     1559            <div id="status.409">
     1560               <div id="rfc.iref.4.10"></div>
     1561               <div id="rfc.iref.s.28"></div>
     1562               <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>
     1563               <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
     1564                  situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
     1565                  body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response representation would
     1566                  include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
     1567               </p>
     1568               <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 representation
     1569                  being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
     1570                  use the 409 response to indicate that it can't complete the request. In this case, the response representation would likely
     1571                  contain a list of the differences between the two versions in a format defined by the response Content-Type.
     1572               </p>
     1573            </div>
     1574            <div id="status.410">
     1575               <div id="rfc.iref.4.11"></div>
     1576               <div id="rfc.iref.s.29"></div>
     1577               <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>
     1578               <p id="rfc.section.8.4.11.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to
     1579                  be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the effective request URI after user approval. If the server does not know, or has no facility to determine,
     1580                  whether or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead.
     1581               </p>
     1582               <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
     1583                  is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
     1584                  is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
     1585                  site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time
     1586                  -- that is left to the discretion of the server owner.
     1587               </p>
     1588               <p id="rfc.section.8.4.11.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
     1589               </p>
     1590            </div>
     1591            <div id="status.411">
     1592               <div id="rfc.iref.4.12"></div>
     1593               <div id="rfc.iref.s.30"></div>
     1594               <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>
     1595               <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
     1596                  message.
     1597               </p>
     1598            </div>
     1599            <div id="status.412">
     1600               <div id="rfc.iref.4.13"></div>
     1601               <div id="rfc.iref.s.31"></div>
     1602               <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>
     1603               <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
     1604                  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.16"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
     1605               </p>
     1606            </div>
     1607            <div id="status.413">
     1608               <div id="rfc.iref.4.14"></div>
     1609               <div id="rfc.iref.s.32"></div>
     1610               <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>
     1611               <p id="rfc.section.8.4.14.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able
     1612                  to process. The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
     1613               </p>
     1614               <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.
     1615               </p>
     1616            </div>
     1617            <div id="status.414">
     1618               <div id="rfc.iref.4.15"></div>
     1619               <div id="rfc.iref.s.33"></div>
     1620               <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>
     1621               <p id="rfc.section.8.4.15.p.1">The server is refusing to service the request because the effective request URI is longer than the server is willing to interpret.
     1622                  This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
     1623                  query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
     1624                  points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present
     1625                  in some servers using fixed-length buffers for reading or manipulating the effective request URI.
     1626               </p>
     1627            </div>
     1628            <div id="status.415">
     1629               <div id="rfc.iref.4.16"></div>
     1630               <div id="rfc.iref.s.34"></div>
     1631               <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>
     1632               <p id="rfc.section.8.4.16.p.1">The server is refusing to service the request because the representation of the request is in a format not supported by the
     1633                  target resource for the requested method.
     1634               </p>
     1635            </div>
     1636            <div id="status.416">
     1637               <div id="rfc.iref.4.17"></div>
     1638               <div id="rfc.iref.s.35"></div>
     1639               <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>
     1640               <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.12"><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.13"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
     1641               </p>
     1642            </div>
     1643            <div id="status.417">
     1644               <div id="rfc.iref.4.18"></div>
     1645               <div id="rfc.iref.s.36"></div>
     1646               <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>
     1647               <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
     1648                  not be met by the next-hop server.
     1649               </p>
     1650            </div>
     1651         </div>
     1652         <div id="status.5xx">
     1653            <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>
     1654            <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
     1655               of performing the request. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
     1656               User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
     1657            </p>
     1658            <div id="status.500">
     1659               <div id="rfc.iref.5.1"></div>
     1660               <div id="rfc.iref.s.37"></div>
     1661               <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>
     1662               <p id="rfc.section.8.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
     1663            </div>
     1664            <div id="status.501">
     1665               <div id="rfc.iref.5.2"></div>
     1666               <div id="rfc.iref.s.38"></div>
     1667               <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>
     1668               <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
     1669                  does not recognize the request method and is not capable of supporting it for any resource.
     1670               </p>
     1671            </div>
     1672            <div id="status.502">
     1673               <div id="rfc.iref.5.3"></div>
     1674               <div id="rfc.iref.s.39"></div>
     1675               <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>
     1676               <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
     1677                  to fulfill the request.
     1678               </p>
     1679            </div>
     1680            <div id="status.503">
     1681               <div id="rfc.iref.5.4"></div>
     1682               <div id="rfc.iref.s.40"></div>
     1683               <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>
     1684               <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
     1685                  is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field. If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
     1686               </p>
     1687               <div class="note" id="rfc.section.8.5.4.p.2">
     1688                  <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 might
     1689                     wish to simply refuse the connection.
     1690                  </p>
     1691               </div>
     1692            </div>
     1693            <div id="status.504">
     1694               <div id="rfc.iref.5.5"></div>
     1695               <div id="rfc.iref.s.41"></div>
     1696               <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>
     1697               <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
     1698                  URI (e.g., HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed to access in attempting to complete the request.
     1699               </p>
     1700               <div class="note" id="rfc.section.8.5.5.p.2">
     1701                  <p><b>Note</b> to implementors: some deployed proxies are known to return 400 or 500 when DNS lookups time out.
     1702                  </p>
     1703               </div>
     1704            </div>
     1705            <div id="status.505">
     1706               <div id="rfc.iref.5.6"></div>
     1707               <div id="rfc.iref.s.42"></div>
     1708               <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>
     1709               <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
     1710                  is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
     1711                  in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 2.5</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>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server.
     1712               </p>
     1713            </div>
     1714         </div>
    14191715      </div>
    1420       <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.
    1421       </p>
    1422       <div id="rfc.iref.49"></div>
    1423       <div id="rfc.iref.s.26"></div>
    1424       <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>
    1425       <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 3.2</a> of <a href="#Part7" id="rfc.xref.Part7.13"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
    1426       </p>
    1427       <div id="rfc.iref.50"></div>
    1428       <div id="rfc.iref.s.27"></div>
    1429       <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>
    1430       <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.
    1431       </p>
    1432       <div id="rfc.iref.51"></div>
    1433       <div id="rfc.iref.s.28"></div>
    1434       <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>
    1435       <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
    1436          situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
    1437          body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response representation would
    1438          include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
    1439       </p>
    1440       <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 representation
    1441          being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
    1442          use the 409 response to indicate that it can't complete the request. In this case, the response representation would likely
    1443          contain a list of the differences between the two versions in a format defined by the response Content-Type.
    1444       </p>
    1445       <div id="rfc.iref.52"></div>
    1446       <div id="rfc.iref.s.29"></div>
    1447       <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>
    1448       <p id="rfc.section.8.4.11.p.1">The target resource is no longer available at the server and no forwarding address is known. This condition is expected to
    1449          be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the effective request URI after user approval. If the server does not know, or has no facility to determine,
    1450          whether or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead.
    1451       </p>
    1452       <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
    1453          is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
    1454          is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
    1455          site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time
    1456          -- that is left to the discretion of the server owner.
    1457       </p>
    1458       <p id="rfc.section.8.4.11.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    1459       </p>
    1460       <div id="rfc.iref.53"></div>
    1461       <div id="rfc.iref.s.30"></div>
    1462       <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>
    1463       <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
    1464          message.
    1465       </p>
    1466       <div id="rfc.iref.54"></div>
    1467       <div id="rfc.iref.s.31"></div>
    1468       <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>
    1469       <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
    1470          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.16"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    1471       </p>
    1472       <div id="rfc.iref.55"></div>
    1473       <div id="rfc.iref.s.32"></div>
    1474       <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>
    1475       <p id="rfc.section.8.4.14.p.1">The server is refusing to process a request because the request representation is larger than the server is willing or able
    1476          to process. The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
    1477       </p>
    1478       <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.
    1479       </p>
    1480       <div id="rfc.iref.56"></div>
    1481       <div id="rfc.iref.s.33"></div>
    1482       <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>
    1483       <p id="rfc.section.8.4.15.p.1">The server is refusing to service the request because the effective request URI is longer than the server is willing to interpret.
    1484          This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long
    1485          query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that
    1486          points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present
    1487          in some servers using fixed-length buffers for reading or manipulating the effective request URI.
    1488       </p>
    1489       <div id="rfc.iref.57"></div>
    1490       <div id="rfc.iref.s.34"></div>
    1491       <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>
    1492       <p id="rfc.section.8.4.16.p.1">The server is refusing to service the request because the representation of the request is in a format not supported by the
    1493          target resource for the requested method.
    1494       </p>
    1495       <div id="rfc.iref.58"></div>
    1496       <div id="rfc.iref.s.35"></div>
    1497       <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>
    1498       <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.12"><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.13"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
    1499       </p>
    1500       <div id="rfc.iref.59"></div>
    1501       <div id="rfc.iref.s.36"></div>
    1502       <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>
    1503       <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
    1504          not be met by the next-hop server.
    1505       </p>
    1506       <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>
    1507       <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
    1508          of performing the request. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    1509          User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    1510       </p>
    1511       <div id="rfc.iref.60"></div>
    1512       <div id="rfc.iref.s.37"></div>
    1513       <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>
    1514       <p id="rfc.section.8.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    1515       <div id="rfc.iref.61"></div>
    1516       <div id="rfc.iref.s.38"></div>
    1517       <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>
    1518       <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
    1519          does not recognize the request method and is not capable of supporting it for any resource.
    1520       </p>
    1521       <div id="rfc.iref.62"></div>
    1522       <div id="rfc.iref.s.39"></div>
    1523       <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>
    1524       <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
    1525          to fulfill the request.
    1526       </p>
    1527       <div id="rfc.iref.63"></div>
    1528       <div id="rfc.iref.s.40"></div>
    1529       <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>
    1530       <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
    1531          is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay <em class="bcp14">MAY</em> be indicated in a Retry-After header field. If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
    1532       </p>
    1533       <div class="note" id="rfc.section.8.5.4.p.2">
    1534          <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 might
    1535             wish to simply refuse the connection.
    1536          </p>
    1537       </div>
    1538       <div id="rfc.iref.64"></div>
    1539       <div id="rfc.iref.s.41"></div>
    1540       <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>
    1541       <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
    1542          URI (e.g., HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed to access in attempting to complete the request.
    1543       </p>
    1544       <div class="note" id="rfc.section.8.5.5.p.2">
    1545          <p> <b>Note</b> to implementors: some deployed proxies are known to return 400 or 500 when DNS lookups time out.
    1546          </p>
    1547       </div>
    1548       <div id="rfc.iref.65"></div>
    1549       <div id="rfc.iref.s.42"></div>
    1550       <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>
    1551       <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
    1552          is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
    1553          in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 2.5</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>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain a representation describing why that version is not supported and what other protocols are supported by that server.
    1554       </p>
    1555       <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>
    1556       <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>
    1557       <div id="rfc.iref.a.1"></div>
    1558       <div id="rfc.iref.h.2"></div>
    1559       <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>
    1560       <p id="rfc.section.9.1.p.1">The "Allow" response-header field lists the set of methods advertised as supported by the target resource. The purpose of
    1561          this field is strictly to inform the recipient of valid methods associated with the resource.
    1562       </p>
    1563       <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>
     1716      <div id="header.fields">
     1717         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
     1718         <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>
     1719         <div id="header.allow">
     1720            <div id="rfc.iref.a.1"></div>
     1721            <div id="rfc.iref.h.2"></div>
     1722            <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a href="#header.allow">Allow</a></h2>
     1723            <p id="rfc.section.9.1.p.1">The "Allow" response-header field lists the set of methods advertised as supported by the target resource. The purpose of
     1724               this field is strictly to inform the recipient of valid methods associated with the resource.
     1725            </p>
     1726            <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>
    15641727  <a href="#header.allow" class="smpl">Allow-v</a> = #<a href="#method" class="smpl">Method</a>
    15651728</pre><p id="rfc.section.9.1.p.3">Example of use:</p>
    1566       <div id="rfc.figure.u.13"></div><pre class="text">  Allow: GET, HEAD, PUT
     1729            <div id="rfc.figure.u.13"></div><pre class="text">  Allow: GET, HEAD, PUT
    15671730</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>
    1568       <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
    1569          means of communicating with the origin server.
    1570       </p>
    1571       <div id="rfc.iref.e.1"></div>
    1572       <div id="rfc.iref.h.3"></div>
    1573       <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>
    1574       <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>
    1575       <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>
     1731            <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
     1732               means of communicating with the origin server.
     1733            </p>
     1734         </div>
     1735         <div id="header.expect">
     1736            <div id="rfc.iref.e.1"></div>
     1737            <div id="rfc.iref.h.3"></div>
     1738            <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a href="#header.expect">Expect</a></h2>
     1739            <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>
     1740            <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>
    15761741  <a href="#header.expect" class="smpl">Expect-v</a>     = 1#<a href="#header.expect" class="smpl">expectation</a>
    15771742 
     
    15811746  <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> ) ]
    15821747</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 code. The server <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status code if any of the expectations cannot be met or, if there are other problems
    1583          with the request, some other 4xx status code.
    1584       </p>
    1585       <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
    1586          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 code.
    1587       </p>
    1588       <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
    1589          for quoted-string expectation-extensions.
    1590       </p>
    1591       <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 code if it receives a request with an expectation that it cannot meet. However, the
    1592          Expect request-header field itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
    1593       </p>
    1594       <p id="rfc.section.9.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
    1595       <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.29"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status code.
    1596       </p>
    1597       <div id="rfc.iref.f.1"></div>
    1598       <div id="rfc.iref.h.4"></div>
    1599       <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>
    1600       <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>:
    1601       </p>
    1602       <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>
     1748               with the request, some other 4xx status code.
     1749            </p>
     1750            <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
     1751               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 code.
     1752            </p>
     1753            <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
     1754               for quoted-string expectation-extensions.
     1755            </p>
     1756            <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 code if it receives a request with an expectation that it cannot meet. However, the
     1757               Expect request-header field itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
     1758            </p>
     1759            <p id="rfc.section.9.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header field.</p>
     1760            <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.29"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status code.
     1761            </p>
     1762         </div>
     1763         <div id="header.from">
     1764            <div id="rfc.iref.f.1"></div>
     1765            <div id="rfc.iref.h.4"></div>
     1766            <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a href="#header.from">From</a></h2>
     1767            <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>:
     1768            </p>
     1769            <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>
    16031770  <a href="#header.from" class="smpl">From-v</a>  = <a href="#header.from" class="smpl">mailbox</a>
    16041771 
    1605   <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;
     1772  <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;
    16061773</pre><p id="rfc.section.9.3.p.3">An example is:</p>
    1607       <div id="rfc.figure.u.16"></div><pre class="text">  From: webmaster@example.org
     1774            <div id="rfc.figure.u.16"></div><pre class="text">  From: webmaster@example.org
    16081775</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
    1609          on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header field so that the person responsible for running the robot can be contacted if problems occur on the receiving
    1610          end.
    1611       </p>
    1612       <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
    1613          issuer's address <em class="bcp14">SHOULD</em> be used.
    1614       </p>
    1615       <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
    1616          security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
    1617          any time prior to a request.
    1618       </p>
    1619       <div id="rfc.iref.l.1"></div>
    1620       <div id="rfc.iref.h.5"></div>
    1621       <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>
    1622       <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
    1623          location for completion of the request.
    1624       </p>
    1625       <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,
    1626          the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
    1627       </p>
    1628       <p id="rfc.section.9.4.p.3">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>).
    1629       </p>
    1630       <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>
     1776               on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header field so that the person responsible for running the robot can be contacted if problems occur on the receiving
     1777               end.
     1778            </p>
     1779            <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
     1780               issuer's address <em class="bcp14">SHOULD</em> be used.
     1781            </p>
     1782            <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
     1783               security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
     1784               any time prior to a request.
     1785            </p>
     1786         </div>
     1787         <div id="header.location">
     1788            <div id="rfc.iref.l.1"></div>
     1789            <div id="rfc.iref.h.5"></div>
     1790            <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a href="#header.location">Location</a></h2>
     1791            <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
     1792               location for completion of the request.
     1793            </p>
     1794            <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,
     1795               the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource.
     1796            </p>
     1797            <p id="rfc.section.9.4.p.3">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="https://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="https://tools.ietf.org/html/rfc3986#section-5">Section 5</a>).
     1798            </p>
     1799            <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>
    16311800  <a href="#header.location" class="smpl">Location-v</a>     = <a href="#abnf.dependencies" class="smpl">URI-reference</a>
    1632 </pre><div id="rfc.figure.u.18"></div> 
    1633       <p>Examples are:</p>  <pre class="text">  Location: http://www.example.org/pub/WWW/People.html#tim
     1801</pre><div id="rfc.figure.u.18"></div>
     1802            <p>Examples are:</p><pre class="text">  Location: http://www.example.org/pub/WWW/People.html#tim
    16341803</pre><div id="rfc.figure.u.19"></div><pre class="text">  Location: /index.html
    16351804</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>
    1636       <ul>
    1637          <li>With a 201 Created response, because in this usage the Location header field specifies the URI for the entire created resource.</li>
    1638          <li>With 305 Use Proxy.</li>
    1639       </ul>
    1640       <div class="note" id="rfc.section.9.4.p.8">
    1641          <p> <b>Note:</b> This specification does not define precedence rules for the case where the original URI, as navigated to by the user agent,
    1642             and the Location header field value both contain fragment identifiers.
    1643          </p>
    1644       </div>
    1645       <div class="note" id="rfc.section.9.4.p.9">
    1646          <p> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
    1647             It is therefore possible for a response to contain header fields for both Location and Content-Location.
    1648          </p>
    1649       </div>
    1650       <div id="rfc.iref.m.9"></div>
    1651       <div id="rfc.iref.h.6"></div>
    1652       <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>
    1653       <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
    1654          is attempting to trace a request which appears to be failing or looping in mid-chain.
    1655       </p>
    1656       <div id="rfc.figure.u.20"></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>
     1805            <ul>
     1806               <li>With a 201 Created response, because in this usage the Location header field specifies the URI for the entire created resource.</li>
     1807               <li>With 305 Use Proxy.</li>
     1808            </ul>
     1809            <div class="note" id="rfc.section.9.4.p.8">
     1810               <p><b>Note:</b> This specification does not define precedence rules for the case where the original URI, as navigated to by the user agent,
     1811                  and the Location header field value both contain fragment identifiers.
     1812               </p>
     1813            </div>
     1814            <div class="note" id="rfc.section.9.4.p.9">
     1815               <p><b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the most specific resource corresponding to the enclosed representation.
     1816                  It is therefore possible for a response to contain header fields for both Location and Content-Location.
     1817               </p>
     1818            </div>
     1819         </div>
     1820         <div id="header.max-forwards">
     1821            <div id="rfc.iref.m.9"></div>
     1822            <div id="rfc.iref.h.6"></div>
     1823            <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>
     1824            <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
     1825               is attempting to trace a request which appears to be failing or looping in mid-chain.
     1826            </p>
     1827            <div id="rfc.figure.u.20"></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>
    16571828  <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    16581829</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 can be forwarded.</p>
    1659       <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).
    1660       </p>
    1661       <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
    1662          referred to as part of that method definition.
    1663       </p>
    1664       <div id="rfc.iref.r.1"></div>
    1665       <div id="rfc.iref.h.7"></div>
    1666       <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>
    1667       <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 effective request
    1668          URI was obtained (the "referrer", although the header field is misspelled.).
    1669       </p>
    1670       <p id="rfc.section.9.6.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
    1671          etc. It also allows obsolete or mistyped links to be traced for maintenance. Some servers use Referer as a means of controlling
    1672          where they allow links from (so-called "deep linking"), but legitimate requests do not always contain a Referer header field.
    1673       </p>
    1674       <p id="rfc.section.9.6.p.3">If the effective request URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard),
    1675          the Referer field <em class="bcp14">MUST</em> either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not apply to sources with
    1676          non-HTTP URIs (e.g., FTP).
    1677       </p>
    1678       <div id="rfc.figure.u.21"></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>
     1830            <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).
     1831            </p>
     1832            <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
     1833               referred to as part of that method definition.
     1834            </p>
     1835         </div>
     1836         <div id="header.referer">
     1837            <div id="rfc.iref.r.1"></div>
     1838            <div id="rfc.iref.h.7"></div>
     1839            <h2 id="rfc.section.9.6"><a href="#rfc.section.9.6">9.6</a>&nbsp;<a href="#header.referer">Referer</a></h2>
     1840            <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 effective request
     1841               URI was obtained (the "referrer", although the header field is misspelled.).
     1842            </p>
     1843            <p id="rfc.section.9.6.p.2">The Referer header field allows servers to generate lists of back-links to resources for interest, logging, optimized caching,
     1844               etc. It also allows obsolete or mistyped links to be traced for maintenance. Some servers use Referer as a means of controlling
     1845               where they allow links from (so-called "deep linking"), but legitimate requests do not always contain a Referer header field.
     1846            </p>
     1847            <p id="rfc.section.9.6.p.3">If the effective request URI was obtained from a source that does not have its own URI (e.g., input from the user keyboard),
     1848               the Referer field <em class="bcp14">MUST</em> either be sent with the value "about:blank", or not be sent at all. Note that this requirement does not apply to sources with
     1849               non-HTTP URIs (e.g., FTP).
     1850            </p>
     1851            <div id="rfc.figure.u.21"></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>
    16791852  <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>
    16801853</pre><p id="rfc.section.9.6.p.5">Example:</p>
    1681       <div id="rfc.figure.u.22"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
     1854            <div id="rfc.figure.u.22"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
    16821855</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 effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations.
    1683       </p>
    1684       <div id="rfc.iref.r.2"></div>
    1685       <div id="rfc.iref.h.8"></div>
    1686       <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>
    1687       <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
    1688          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
    1689          the redirected request.
    1690       </p>
    1691       <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>
    1692       <div id="rfc.figure.u.23"></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>
     1856            </p>
     1857         </div>
     1858         <div id="header.retry-after">
     1859            <div id="rfc.iref.r.2"></div>
     1860            <div id="rfc.iref.h.8"></div>
     1861            <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>
     1862            <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
     1863               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
     1864               the redirected request.
     1865            </p>
     1866            <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>
     1867            <div id="rfc.figure.u.23"></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>
    16931868  <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>
    16941869</pre><div id="rule.delta-seconds">
    1695          <p id="rfc.section.9.7.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p>
    1696       </div>
    1697       <div id="rfc.figure.u.24"></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>
     1870               <p id="rfc.section.9.7.p.4"> Time spans are non-negative decimal integers, representing time in seconds.</p>
     1871            </div>
     1872            <div id="rfc.figure.u.24"></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>
    16981873</pre><p id="rfc.section.9.7.p.6">Two examples of its use are</p>
    1699       <div id="rfc.figure.u.25"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
     1874            <div id="rfc.figure.u.25"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    17001875  Retry-After: 120
    17011876</pre><p id="rfc.section.9.7.p.8">In the latter example, the delay is 2 minutes.</p>
    1702       <div id="rfc.iref.s.43"></div>
    1703       <div id="rfc.iref.h.9"></div>
    1704       <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>
    1705       <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>
    1706       <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.30"><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.31"><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
    1707          identifying the application.
    1708       </p>
    1709       <div id="rfc.figure.u.26"></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>
     1877         </div>
     1878         <div id="header.server">
     1879            <div id="rfc.iref.s.43"></div>
     1880            <div id="rfc.iref.h.9"></div>
     1881            <h2 id="rfc.section.9.8"><a href="#rfc.section.9.8">9.8</a>&nbsp;<a href="#header.server">Server</a></h2>
     1882            <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>
     1883            <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.30"><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.31"><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
     1884               identifying the application.
     1885            </p>
     1886            <div id="rfc.figure.u.26"></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>
    17101887  <a href="#header.server" class="smpl">Server-v</a>       = <a href="#abnf.dependencies" class="smpl">product</a>
    17111888                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
    17121889</pre><p id="rfc.section.9.8.p.4">Example:</p>
    1713       <div id="rfc.figure.u.27"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
     1890            <div id="rfc.figure.u.27"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    17141891</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 field. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.32"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    1715       </p>
    1716       <div class="note" id="rfc.section.9.8.p.7">
    1717          <p> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    1718             against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable
    1719             option.
    1720          </p>
    1721       </div>
    1722       <div id="rfc.iref.u.1"></div>
    1723       <div id="rfc.iref.h.10"></div>
    1724       <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>
    1725       <p id="rfc.section.9.9.p.1">The "User-Agent" request-header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests.
    1726       </p>
    1727       <p id="rfc.section.9.9.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
    1728          user agent limitations.
    1729       </p>
    1730       <p id="rfc.section.9.9.p.3">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.33"><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.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
    1731          for identifying the application.
    1732       </p>
    1733       <p id="rfc.section.9.9.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
    1734          fine-grained detail, and to limit (or even prohibit) the addition of subproducts by third parties. Overly long and detailed
    1735          User-Agent field values make requests larger and can also be used to identify ("fingerprint") the user against their wishes.
    1736       </p>
    1737       <p id="rfc.section.9.9.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
    1738          with them, as this circumvents the purpose of the field. Finally, they are encouraged not to use comments to identify products;
    1739          doing so makes the field value more difficult to parse.
    1740       </p>
    1741       <div id="rfc.figure.u.28"></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>
     1892            </p>
     1893            <div class="note" id="rfc.section.9.8.p.7">
     1894               <p><b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
     1895                  against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable
     1896                  option.
     1897               </p>
     1898            </div>
     1899         </div>
     1900         <div id="header.user-agent">
     1901            <div id="rfc.iref.u.1"></div>
     1902            <div id="rfc.iref.h.10"></div>
     1903            <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>
     1904            <p id="rfc.section.9.9.p.1">The "User-Agent" request-header field contains information about the user agent originating the request. User agents <em class="bcp14">SHOULD</em> include this field with requests.
     1905            </p>
     1906            <p id="rfc.section.9.9.p.2">Typically, it is used for statistical purposes, the tracing of protocol violations, and tailoring responses to avoid particular
     1907               user agent limitations.
     1908            </p>
     1909            <p id="rfc.section.9.9.p.3">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.33"><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.34"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) identifying the agent and its significant subproducts. By convention, the product tokens are listed in order of their significance
     1910               for identifying the application.
     1911            </p>
     1912            <p id="rfc.section.9.9.p.4">Because this field is usually sent on every request a user agent makes, implementations are encouraged not to include needlessly
     1913               fine-grained detail, and to limit (or even prohibit) the addition of subproducts by third parties. Overly long and detailed
     1914               User-Agent field values make requests larger and can also be used to identify ("fingerprint") the user against their wishes.
     1915            </p>
     1916            <p id="rfc.section.9.9.p.5">Likewise, implementations are encouraged not to use the product tokens of other implementations in order to declare compatibility
     1917               with them, as this circumvents the purpose of the field. Finally, they are encouraged not to use comments to identify products;
     1918               doing so makes the field value more difficult to parse.
     1919            </p>
     1920            <div id="rfc.figure.u.28"></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>
    17421921  <a href="#header.user-agent" class="smpl">User-Agent-v</a>   = <a href="#abnf.dependencies" class="smpl">product</a>
    17431922                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
    17441923</pre><p id="rfc.section.9.9.p.7">Example:</p>
    1745       <div id="rfc.figure.u.29"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    1746 </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>
    1747       <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>
    1748       <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.
    1749       </p>
    1750       <p id="rfc.section.10.1.p.2">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
    1751       </p>
    1752       <div id="rfc.table.1">
    1753          <div id="iana.method.registration.table"></div>
    1754          <table class="tt full left" cellpadding="3" cellspacing="0">
    1755             <thead>
    1756                <tr>
    1757                   <th>Method</th>
    1758                   <th>Safe</th>
    1759                   <th>Reference</th>
    1760                </tr>
    1761             </thead>
    1762             <tbody>
    1763                <tr>
    1764                   <td class="left">CONNECT</td>
    1765                   <td class="left">no</td>
    1766                   <td class="left"> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;7.9</a>
    1767                   </td>
    1768                </tr>
    1769                <tr>
    1770                   <td class="left">DELETE</td>
    1771                   <td class="left">no</td>
    1772                   <td class="left"> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;7.7</a>
    1773                   </td>
    1774                </tr>
    1775                <tr>
    1776                   <td class="left">GET</td>
    1777                   <td class="left">yes</td>
    1778                   <td class="left"> <a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;7.3</a>
    1779                   </td>
    1780                </tr>
    1781                <tr>
    1782                   <td class="left">HEAD</td>
    1783                   <td class="left">yes</td>
    1784                   <td class="left"> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;7.4</a>
    1785                   </td>
    1786                </tr>
    1787                <tr>
    1788                   <td class="left">OPTIONS</td>
    1789                   <td class="left">yes</td>
    1790                   <td class="left"> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;7.2</a>
    1791                   </td>
    1792                </tr>
    1793                <tr>
    1794                   <td class="left">POST</td>
    1795                   <td class="left">no</td>
    1796                   <td class="left"> <a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;7.5</a>
    1797                   </td>
    1798                </tr>
    1799                <tr>
    1800                   <td class="left">PUT</td>
    1801                   <td class="left">no</td>
    1802                   <td class="left"> <a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;7.6</a>
    1803                   </td>
    1804                </tr>
    1805                <tr>
    1806                   <td class="left">TRACE</td>
    1807                   <td class="left">yes</td>
    1808                   <td class="left"> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;7.8</a>
    1809                   </td>
    1810                </tr>
    1811             </tbody>
    1812          </table>
     1924            <div id="rfc.figure.u.29"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     1925</pre></div>
    18131926      </div>
    1814       <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>
    1815       <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.
    1816       </p>
    1817       <p id="rfc.section.10.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
    1818       </p>
    1819       <div id="rfc.table.2">
    1820          <div id="iana.status.code.registration.table"></div>
    1821          <table class="tt full left" cellpadding="3" cellspacing="0">
    1822             <thead>
    1823                <tr>
    1824                   <th>Value</th>
    1825                   <th>Description</th>
    1826                   <th>Reference</th>
    1827                </tr>
    1828             </thead>
    1829             <tbody>
    1830                <tr>
    1831                   <td class="left">100</td>
    1832                   <td class="left">Continue</td>
    1833                   <td class="left"> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;8.1.1</a>
    1834                   </td>
    1835                </tr>
    1836                <tr>
    1837                   <td class="left">101</td>
    1838                   <td class="left">Switching Protocols</td>
    1839                   <td class="left"> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;8.1.2</a>
    1840                   </td>
    1841                </tr>
    1842                <tr>
    1843                   <td class="left">200</td>
    1844                   <td class="left">OK</td>
    1845                   <td class="left"> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;8.2.1</a>
    1846                   </td>
    1847                </tr>
    1848                <tr>
    1849                   <td class="left">201</td>
    1850                   <td class="left">Created</td>
    1851                   <td class="left"> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;8.2.2</a>
    1852                   </td>
    1853                </tr>
    1854                <tr>
    1855                   <td class="left">202</td>
    1856                   <td class="left">Accepted</td>
    1857                   <td class="left"> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;8.2.3</a>
    1858                   </td>
    1859                </tr>
    1860                <tr>
    1861                   <td class="left">203</td>
    1862                   <td class="left">Non-Authoritative Information</td>
    1863                   <td class="left"> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;8.2.4</a>
    1864                   </td>
    1865                </tr>
    1866                <tr>
    1867                   <td class="left">204</td>
    1868                   <td class="left">No Content</td>
    1869                   <td class="left"> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;8.2.5</a>
    1870                   </td>
    1871                </tr>
    1872                <tr>
    1873                   <td class="left">205</td>
    1874                   <td class="left">Reset Content</td>
    1875                   <td class="left"> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;8.2.6</a>
    1876                   </td>
    1877                </tr>
    1878                <tr>
    1879                   <td class="left">300</td>
    1880                   <td class="left">Multiple Choices</td>
    1881                   <td class="left"> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;8.3.1</a>
    1882                   </td>
    1883                </tr>
    1884                <tr>
    1885                   <td class="left">301</td>
    1886                   <td class="left">Moved Permanently</td>
    1887                   <td class="left"> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;8.3.2</a>
    1888                   </td>
    1889                </tr>
    1890                <tr>
    1891                   <td class="left">302</td>
    1892                   <td class="left">Found</td>
    1893                   <td class="left"> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;8.3.3</a>
    1894                   </td>
    1895                </tr>
    1896                <tr>
    1897                   <td class="left">303</td>
    1898                   <td class="left">See Other</td>
    1899                   <td class="left"> <a href="#status.303" id="rfc.xref.status.303.3" title="303 See Other">Section&nbsp;8.3.4</a>
    1900                   </td>
    1901                </tr>
    1902                <tr>
    1903                   <td class="left">305</td>
    1904                   <td class="left">Use Proxy</td>
    1905                   <td class="left"> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;8.3.6</a>
    1906                   </td>
    1907                </tr>
    1908                <tr>
    1909                   <td class="left">306</td>
    1910                   <td class="left">(Unused)</td>
    1911                   <td class="left"> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;8.3.7</a>
    1912                   </td>
    1913                </tr>
    1914                <tr>
    1915                   <td class="left">307</td>
    1916                   <td class="left">Temporary Redirect</td>
    1917                   <td class="left"> <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">Section&nbsp;8.3.8</a>
    1918                   </td>
    1919                </tr>
    1920                <tr>
    1921                   <td class="left">400</td>
    1922                   <td class="left">Bad Request</td>
    1923                   <td class="left"> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;8.4.1</a>
    1924                   </td>
    1925                </tr>
    1926                <tr>
    1927                   <td class="left">402</td>
    1928                   <td class="left">Payment Required</td>
    1929                   <td class="left"> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;8.4.3</a>
    1930                   </td>
    1931                </tr>
    1932                <tr>
    1933                   <td class="left">403</td>
    1934                   <td class="left">Forbidden</td>
    1935                   <td class="left"> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;8.4.4</a>
    1936                   </td>
    1937                </tr>
    1938                <tr>
    1939                   <td class="left">404</td>
    1940                   <td class="left">Not Found</td>
    1941                   <td class="left"> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;8.4.5</a>
    1942                   </td>
    1943                </tr>
    1944                <tr>
    1945                   <td class="left">405</td>
    1946                   <td class="left">Method Not Allowed</td>
    1947                   <td class="left"> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;8.4.6</a>
    1948                   </td>
    1949                </tr>
    1950                <tr>
    1951                   <td class="left">406</td>
    1952                   <td class="left">Not Acceptable</td>
    1953                   <td class="left"> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;8.4.7</a>
    1954                   </td>
    1955                </tr>
    1956                <tr>
    1957                   <td class="left">407</td>
    1958                   <td class="left">Proxy Authentication Required</td>
    1959                   <td class="left"> <a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;8.4.8</a>
    1960                   </td>
    1961                </tr>
    1962                <tr>
    1963                   <td class="left">408</td>
    1964                   <td class="left">Request Timeout</td>
    1965                   <td class="left"> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;8.4.9</a>
    1966                   </td>
    1967                </tr>
    1968                <tr>
    1969                   <td class="left">409</td>
    1970                   <td class="left">Conflict</td>
    1971                   <td class="left"> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;8.4.10</a>
    1972                   </td>
    1973                </tr>
    1974                <tr>
    1975                   <td class="left">410</td>
    1976                   <td class="left">Gone</td>
    1977                   <td class="left"> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;8.4.11</a>
    1978                   </td>
    1979                </tr>
    1980                <tr>
    1981                   <td class="left">411</td>
    1982                   <td class="left">Length Required</td>
    1983                   <td class="left"> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;8.4.12</a>
    1984                   </td>
    1985                </tr>
    1986                <tr>
    1987                   <td class="left">413</td>
    1988                   <td class="left">Request Entity Too Large</td>
    1989                   <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>
    1990                   </td>
    1991                </tr>
    1992                <tr>
    1993                   <td class="left">414</td>
    1994                   <td class="left">URI Too Long</td>
    1995                   <td class="left"> <a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;8.4.15</a>
    1996                   </td>
    1997                </tr>
    1998                <tr>
    1999                   <td class="left">415</td>
    2000                   <td class="left">Unsupported Media Type</td>
    2001                   <td class="left"> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;8.4.16</a>
    2002                   </td>
    2003                </tr>
    2004                <tr>
    2005                   <td class="left">417</td>
    2006                   <td class="left">Expectation Failed</td>
    2007                   <td class="left"> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;8.4.18</a>
    2008                   </td>
    2009                </tr>
    2010                <tr>
    2011                   <td class="left">500</td>
    2012                   <td class="left">Internal Server Error</td>
    2013                   <td class="left"> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;8.5.1</a>
    2014                   </td>
    2015                </tr>
    2016                <tr>
    2017                   <td class="left">501</td>
    2018                   <td class="left">Not Implemented</td>
    2019                   <td class="left"> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;8.5.2</a>
    2020                   </td>
    2021                </tr>
    2022                <tr>
    2023                   <td class="left">502</td>
    2024                   <td class="left">Bad Gateway</td>
    2025                   <td class="left"> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;8.5.3</a>
    2026                   </td>
    2027                </tr>
    2028                <tr>
    2029                   <td class="left">503</td>
    2030                   <td class="left">Service Unavailable</td>
    2031                   <td class="left"> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;8.5.4</a>
    2032                   </td>
    2033                </tr>
    2034                <tr>
    2035                   <td class="left">504</td>
    2036                   <td class="left">Gateway Timeout</td>
    2037                   <td class="left"> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>
    2038                   </td>
    2039                </tr>
    2040                <tr>
    2041                   <td class="left">505</td>
    2042                   <td class="left">HTTP Version Not Supported</td>
    2043                   <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>
    2044                   </td>
    2045                </tr>
    2046             </tbody>
    2047          </table>
     1927      <div id="IANA.considerations">
     1928         <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
     1929         <div id="method.registration">
     1930            <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a href="#method.registration">Method Registry</a></h2>
     1931            <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.
     1932            </p>
     1933            <p id="rfc.section.10.1.p.2">The HTTP Method Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; and be populated with the registrations below:
     1934            </p>
     1935            <div id="rfc.table.1">
     1936               <div id="iana.method.registration.table"></div>
     1937               <table class="tt full left" cellpadding="3" cellspacing="0">
     1938                  <thead>
     1939                     <tr>
     1940                        <th>Method</th>
     1941                        <th>Safe</th>
     1942                        <th>Reference</th>
     1943                     </tr>
     1944                  </thead>
     1945                  <tbody>
     1946                     <tr>
     1947                        <td class="left">CONNECT</td>
     1948                        <td class="left">no</td>
     1949                        <td class="left"><a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;7.9</a>
     1950                        </td>
     1951                     </tr>
     1952                     <tr>
     1953                        <td class="left">DELETE</td>
     1954                        <td class="left">no</td>
     1955                        <td class="left"><a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;7.7</a>
     1956                        </td>
     1957                     </tr>
     1958                     <tr>
     1959                        <td class="left">GET</td>
     1960                        <td class="left">yes</td>
     1961                        <td class="left"><a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;7.3</a>
     1962                        </td>
     1963                     </tr>
     1964                     <tr>
     1965                        <td class="left">HEAD</td>
     1966                        <td class="left">yes</td>
     1967                        <td class="left"><a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;7.4</a>
     1968                        </td>
     1969                     </tr>
     1970                     <tr>
     1971                        <td class="left">OPTIONS</td>
     1972                        <td class="left">yes</td>
     1973                        <td class="left"><a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;7.2</a>
     1974                        </td>
     1975                     </tr>
     1976                     <tr>
     1977                        <td class="left">POST</td>
     1978                        <td class="left">no</td>
     1979                        <td class="left"><a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;7.5</a>
     1980                        </td>
     1981                     </tr>
     1982                     <tr>
     1983                        <td class="left">PUT</td>
     1984                        <td class="left">no</td>
     1985                        <td class="left"><a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;7.6</a>
     1986                        </td>
     1987                     </tr>
     1988                     <tr>
     1989                        <td class="left">TRACE</td>
     1990                        <td class="left">yes</td>
     1991                        <td class="left"><a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;7.8</a>
     1992                        </td>
     1993                     </tr>
     1994                  </tbody>
     1995               </table>
     1996            </div>
     1997         </div>
     1998         <div id="status.code.registration">
     1999            <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>
     2000            <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.
     2001            </p>
     2002            <p id="rfc.section.10.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
     2003            </p>
     2004            <div id="rfc.table.2">
     2005               <div id="iana.status.code.registration.table"></div>
     2006               <table class="tt full left" cellpadding="3" cellspacing="0">
     2007                  <thead>
     2008                     <tr>
     2009                        <th>Value</th>
     2010                        <th>Description</th>
     2011                        <th>Reference</th>
     2012                     </tr>
     2013                  </thead>
     2014                  <tbody>
     2015                     <tr>
     2016                        <td class="left">100</td>
     2017                        <td class="left">Continue</td>
     2018                        <td class="left"><a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;8.1.1</a>
     2019                        </td>
     2020                     </tr>
     2021                     <tr>
     2022                        <td class="left">101</td>
     2023                        <td class="left">Switching Protocols</td>
     2024                        <td class="left"><a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;8.1.2</a>
     2025                        </td>
     2026                     </tr>
     2027                     <tr>
     2028                        <td class="left">200</td>
     2029                        <td class="left">OK</td>
     2030                        <td class="left"><a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;8.2.1</a>
     2031                        </td>
     2032                     </tr>
     2033                     <tr>
     2034                        <td class="left">201</td>
     2035                        <td class="left">Created</td>
     2036                        <td class="left"><a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;8.2.2</a>
     2037                        </td>
     2038                     </tr>
     2039                     <tr>
     2040                        <td class="left">202</td>
     2041                        <td class="left">Accepted</td>
     2042                        <td class="left"><a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;8.2.3</a>
     2043                        </td>
     2044                     </tr>
     2045                     <tr>
     2046                        <td class="left">203</td>
     2047                        <td class="left">Non-Authoritative Information</td>
     2048                        <td class="left"><a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;8.2.4</a>
     2049                        </td>
     2050                     </tr>
     2051                     <tr>
     2052                        <td class="left">204</td>
     2053                        <td class="left">No Content</td>
     2054                        <td class="left"><a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;8.2.5</a>
     2055                        </td>
     2056                     </tr>
     2057                     <tr>
     2058                        <td class="left">205</td>
     2059                        <td class="left">Reset Content</td>
     2060                        <td class="left"><a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;8.2.6</a>
     2061                        </td>
     2062                     </tr>
     2063                     <tr>
     2064                        <td class="left">300</td>
     2065                        <td class="left">Multiple Choices</td>
     2066                        <td class="left"><a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;8.3.1</a>
     2067                        </td>
     2068                     </tr>
     2069                     <tr>
     2070                        <td class="left">301</td>
     2071                        <td class="left">Moved Permanently</td>
     2072                        <td class="left"><a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;8.3.2</a>
     2073                        </td>
     2074                     </tr>
     2075                     <tr>
     2076                        <td class="left">302</td>
     2077                        <td class="left">Found</td>
     2078                        <td class="left"><a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;8.3.3</a>
     2079                        </td>
     2080                     </tr>
     2081                     <tr>
     2082                        <td class="left">303</td>
     2083                        <td class="left">See Other</td>
     2084                        <td class="left"><a href="#status.303" id="rfc.xref.status.303.3" title="303 See Other">Section&nbsp;8.3.4</a>
     2085                        </td>
     2086                     </tr>
     2087                     <tr>
     2088                        <td class="left">305</td>
     2089                        <td class="left">Use Proxy</td>
     2090                        <td class="left"><a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;8.3.6</a>
     2091                        </td>
     2092                     </tr>
     2093                     <tr>
     2094                        <td class="left">306</td>
     2095                        <td class="left">(Unused)</td>
     2096                        <td class="left"><a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;8.3.7</a>
     2097                        </td>
     2098                     </tr>
     2099                     <tr>
     2100                        <td class="left">307</td>
     2101                        <td class="left">Temporary Redirect</td>
     2102                        <td class="left"><a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">Section&nbsp;8.3.8</a>
     2103                        </td>
     2104                     </tr>
     2105                     <tr>
     2106                        <td class="left">400</td>
     2107                        <td class="left">Bad Request</td>
     2108                        <td class="left"><a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;8.4.1</a>
     2109                        </td>
     2110                     </tr>
     2111                     <tr>
     2112                        <td class="left">402</td>
     2113                        <td class="left">Payment Required</td>
     2114                        <td class="left"><a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;8.4.3</a>
     2115                        </td>
     2116                     </tr>
     2117                     <tr>
     2118                        <td class="left">403</td>
     2119                        <td class="left">Forbidden</td>
     2120                        <td class="left"><a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;8.4.4</a>
     2121                        </td>
     2122                     </tr>
     2123                     <tr>
     2124                        <td class="left">404</td>
     2125                        <td class="left">Not Found</td>
     2126                        <td class="left"><a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;8.4.5</a>
     2127                        </td>
     2128                     </tr>
     2129                     <tr>
     2130                        <td class="left">405</td>
     2131                        <td class="left">Method Not Allowed</td>
     2132                        <td class="left"><a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;8.4.6</a>
     2133                        </td>
     2134                     </tr>
     2135                     <tr>
     2136                        <td class="left">406</td>
     2137                        <td class="left">Not Acceptable</td>
     2138                        <td class="left"><a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;8.4.7</a>
     2139                        </td>
     2140                     </tr>
     2141                     <tr>
     2142                        <td class="left">407</td>
     2143                        <td class="left">Proxy Authentication Required</td>
     2144                        <td class="left"><a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;8.4.8</a>
     2145                        </td>
     2146                     </tr>
     2147                     <tr>
     2148                        <td class="left">408</td>
     2149                        <td class="left">Request Timeout</td>
     2150                        <td class="left"><a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;8.4.9</a>
     2151                        </td>
     2152                     </tr>
     2153                     <tr>
     2154                        <td class="left">409</td>
     2155                        <td class="left">Conflict</td>
     2156                        <td class="left"><a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;8.4.10</a>
     2157                        </td>
     2158                     </tr>
     2159                     <tr>
     2160                        <td class="left">410</td>
     2161                        <td class="left">Gone</td>
     2162                        <td class="left"><a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;8.4.11</a>
     2163                        </td>
     2164                     </tr>
     2165                     <tr>
     2166                        <td class="left">411</td>
     2167                        <td class="left">Length Required</td>
     2168                        <td class="left"><a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;8.4.12</a>
     2169                        </td>
     2170                     </tr>
     2171                     <tr>
     2172                        <td class="left">413</td>
     2173                        <td class="left">Request Entity Too Large</td>
     2174                        <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>
     2175                        </td>
     2176                     </tr>
     2177                     <tr>
     2178                        <td class="left">414</td>
     2179                        <td class="left">URI Too Long</td>
     2180                        <td class="left"><a href="#status.414" id="rfc.xref.status.414.2" title="414 URI Too Long">Section&nbsp;8.4.15</a>
     2181                        </td>
     2182                     </tr>
     2183                     <tr>
     2184                        <td class="left">415</td>
     2185                        <td class="left">Unsupported Media Type</td>
     2186                        <td class="left"><a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;8.4.16</a>
     2187                        </td>
     2188                     </tr>
     2189                     <tr>
     2190                        <td class="left">417</td>
     2191                        <td class="left">Expectation Failed</td>
     2192                        <td class="left"><a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;8.4.18</a>
     2193                        </td>
     2194                     </tr>
     2195                     <tr>
     2196                        <td class="left">500</td>
     2197                        <td class="left">Internal Server Error</td>
     2198                        <td class="left"><a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;8.5.1</a>
     2199                        </td>
     2200                     </tr>
     2201                     <tr>
     2202                        <td class="left">501</td>
     2203                        <td class="left">Not Implemented</td>
     2204                        <td class="left"><a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;8.5.2</a>
     2205                        </td>
     2206                     </tr>
     2207                     <tr>
     2208                        <td class="left">502</td>
     2209                        <td class="left">Bad Gateway</td>
     2210                        <td class="left"><a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;8.5.3</a>
     2211                        </td>
     2212                     </tr>
     2213                     <tr>
     2214                        <td class="left">503</td>
     2215                        <td class="left">Service Unavailable</td>
     2216                        <td class="left"><a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;8.5.4</a>
     2217                        </td>
     2218                     </tr>
     2219                     <tr>
     2220                        <td class="left">504</td>
     2221                        <td class="left">Gateway Timeout</td>
     2222                        <td class="left"><a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;8.5.5</a>
     2223                        </td>
     2224                     </tr>
     2225                     <tr>
     2226                        <td class="left">505</td>
     2227                        <td class="left">HTTP Version Not Supported</td>
     2228                        <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>
     2229                        </td>
     2230                     </tr>
     2231                  </tbody>
     2232               </table>
     2233            </div>
     2234         </div>
     2235         <div id="header.field.registration">
     2236            <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
     2237            <p id="rfc.section.10.3.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
     2238            </p>
     2239            <div id="rfc.table.3">
     2240               <div id="iana.header.registration.table"></div>
     2241               <table class="tt full left" cellpadding="3" cellspacing="0">
     2242                  <thead>
     2243                     <tr>
     2244                        <th>Header Field Name</th>
     2245                        <th>Protocol</th>
     2246                        <th>Status</th>
     2247                        <th>Reference</th>
     2248                     </tr>
     2249                  </thead>
     2250                  <tbody>
     2251                     <tr>
     2252                        <td class="left">Allow</td>
     2253                        <td class="left">http</td>
     2254                        <td class="left">standard</td>
     2255                        <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;9.1</a>
     2256                        </td>
     2257                     </tr>
     2258                     <tr>
     2259                        <td class="left">Expect</td>
     2260                        <td class="left">http</td>
     2261                        <td class="left">standard</td>
     2262                        <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;9.2</a>
     2263                        </td>
     2264                     </tr>
     2265                     <tr>
     2266                        <td class="left">From</td>
     2267                        <td class="left">http</td>
     2268                        <td class="left">standard</td>
     2269                        <td class="left"><a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;9.3</a>
     2270                        </td>
     2271                     </tr>
     2272                     <tr>
     2273                        <td class="left">Location</td>
     2274                        <td class="left">http</td>
     2275                        <td class="left">standard</td>
     2276                        <td class="left"><a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;9.4</a>
     2277                        </td>
     2278                     </tr>
     2279                     <tr>
     2280                        <td class="left">Max-Forwards</td>
     2281                        <td class="left">http</td>
     2282                        <td class="left">standard</td>
     2283                        <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;9.5</a>
     2284                        </td>
     2285                     </tr>
     2286                     <tr>
     2287                        <td class="left">Referer</td>
     2288                        <td class="left">http</td>
     2289                        <td class="left">standard</td>
     2290                        <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;9.6</a>
     2291                        </td>
     2292                     </tr>
     2293                     <tr>
     2294                        <td class="left">Retry-After</td>
     2295                        <td class="left">http</td>
     2296                        <td class="left">standard</td>
     2297                        <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;9.7</a>
     2298                        </td>
     2299                     </tr>
     2300                     <tr>
     2301                        <td class="left">Server</td>
     2302                        <td class="left">http</td>
     2303                        <td class="left">standard</td>
     2304                        <td class="left"><a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;9.8</a>
     2305                        </td>
     2306                     </tr>
     2307                     <tr>
     2308                        <td class="left">User-Agent</td>
     2309                        <td class="left">http</td>
     2310                        <td class="left">standard</td>
     2311                        <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;9.9</a>
     2312                        </td>
     2313                     </tr>
     2314                  </tbody>
     2315               </table>
     2316            </div>
     2317            <p id="rfc.section.10.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     2318         </div>
    20482319      </div>
    2049       <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    2050       <p id="rfc.section.10.3.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
    2051       </p>
    2052       <div id="rfc.table.3">
    2053          <div id="iana.header.registration.table"></div>
    2054          <table class="tt full left" cellpadding="3" cellspacing="0">
    2055             <thead>
    2056                <tr>
    2057                   <th>Header Field Name</th>
    2058                   <th>Protocol</th>
    2059                   <th>Status</th>
    2060                   <th>Reference</th>
    2061                </tr>
    2062             </thead>
    2063             <tbody>
    2064                <tr>
    2065                   <td class="left">Allow</td>
    2066                   <td class="left">http</td>
    2067                   <td class="left">standard</td>
    2068                   <td class="left"> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;9.1</a>
    2069                   </td>
    2070                </tr>
    2071                <tr>
    2072                   <td class="left">Expect</td>
    2073                   <td class="left">http</td>
    2074                   <td class="left">standard</td>
    2075                   <td class="left"> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;9.2</a>
    2076                   </td>
    2077                </tr>
    2078                <tr>
    2079                   <td class="left">From</td>
    2080                   <td class="left">http</td>
    2081                   <td class="left">standard</td>
    2082                   <td class="left"> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;9.3</a>
    2083                   </td>
    2084                </tr>
    2085                <tr>
    2086                   <td class="left">Location</td>
    2087                   <td class="left">http</td>
    2088                   <td class="left">standard</td>
    2089                   <td class="left"> <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;9.4</a>
    2090                   </td>
    2091                </tr>
    2092                <tr>
    2093                   <td class="left">Max-Forwards</td>
    2094                   <td class="left">http</td>
    2095                   <td class="left">standard</td>
    2096                   <td class="left"> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.4" title="Max-Forwards">Section&nbsp;9.5</a>
    2097                   </td>
    2098                </tr>
    2099                <tr>
    2100                   <td class="left">Referer</td>
    2101                   <td class="left">http</td>
    2102                   <td class="left">standard</td>
    2103                   <td class="left"> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;9.6</a>
    2104                   </td>
    2105                </tr>
    2106                <tr>
    2107                   <td class="left">Retry-After</td>
    2108                   <td class="left">http</td>
    2109                   <td class="left">standard</td>
    2110                   <td class="left"> <a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;9.7</a>
    2111                   </td>
    2112                </tr>
    2113                <tr>
    2114                   <td class="left">Server</td>
    2115                   <td class="left">http</td>
    2116                   <td class="left">standard</td>
    2117                   <td class="left"> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;9.8</a>
    2118                   </td>
    2119                </tr>
    2120                <tr>
    2121                   <td class="left">User-Agent</td>
    2122                   <td class="left">http</td>
    2123                   <td class="left">standard</td>
    2124                   <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;9.9</a>
    2125                   </td>
    2126                </tr>
    2127             </tbody>
    2128          </table>
     2320      <div id="security.considerations">
     2321         <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
     2322         <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
     2323            as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
     2324            make some suggestions for reducing security risks.
     2325         </p>
     2326         <div id="security.sensitive">
     2327            <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>
     2328            <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
     2329               a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
     2330               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
     2331               special mention in this context: Server, Via, Referer and From.
     2332            </p>
     2333            <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
     2334               against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option.
     2335            </p>
     2336            <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,
     2337               they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall.
     2338            </p>
     2339            <p id="rfc.section.11.1.p.4">The Referer header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its
     2340               power can be abused if user details are not separated from the information contained in the Referer. Even when the personal
     2341               information has been removed, the Referer header field might indicate a private document's URI whose publication would be
     2342               inappropriate.
     2343            </p>
     2344            <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
     2345               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.
     2346            </p>
     2347            <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
     2348               of From and Referer information.
     2349            </p>
     2350            <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
     2351               might be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently
     2352               has no better mechanism.
     2353            </p>
     2354            <p id="rfc.section.11.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,
     2355               to uniquely identify the user.
     2356            </p>
     2357            <p id="rfc.section.11.1.p.9">Some methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;7.8</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials and other header fields that might be used
     2358               to collect data from the client.
     2359            </p>
     2360         </div>
     2361         <div id="encoding.sensitive.information.in.uris">
     2362            <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>
     2363            <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
     2364               recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could
     2365               have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From
     2366               information.
     2367            </p>
     2368            <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.
     2369            </p>
     2370            <p id="rfc.section.11.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing
     2371               servers, proxies, and user agents log or display the request-target in places where it might be visible to third parties.
     2372               Such services can use POST-based form submission instead.
     2373            </p>
     2374         </div>
     2375         <div id="location.spoofing">
     2376            <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>
     2377            <p id="rfc.section.11.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location header fields in responses that are generated under control of said organizations
     2378               to make sure that they do not attempt to invalidate resources over which they have no authority.
     2379            </p>
     2380         </div>
    21292381      </div>
    2130       <p id="rfc.section.10.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    2131       <h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    2132       <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
    2133          as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
    2134          make some suggestions for reducing security risks.
    2135       </p>
    2136       <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>
    2137       <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
    2138          a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
    2139          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
    2140          special mention in this context: Server, Via, Referer and From.
    2141       </p>
    2142       <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
    2143          against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option.
    2144       </p>
    2145       <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,
    2146          they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall.
    2147       </p>
    2148       <p id="rfc.section.11.1.p.4">The Referer header field allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its
    2149          power can be abused if user details are not separated from the information contained in the Referer. Even when the personal
    2150          information has been removed, the Referer header field might indicate a private document's URI whose publication would be
    2151          inappropriate.
    2152       </p>
    2153       <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
    2154          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.
    2155       </p>
    2156       <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
    2157          of From and Referer information.
    2158       </p>
    2159       <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
    2160          might be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently
    2161          has no better mechanism.
    2162       </p>
    2163       <p id="rfc.section.11.1.p.8">Furthermore, the User-Agent header field may contain enough entropy to be used, possibly in conjunction with other material,
    2164          to uniquely identify the user.
    2165       </p>
    2166       <p id="rfc.section.11.1.p.9">Some methods, like TRACE (<a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;7.8</a>), expose information that was sent in request header fields within the body of their response. Clients <em class="bcp14">SHOULD</em> be careful with sensitive information, like Cookies, Authorization credentials and other header fields that might be used
    2167          to collect data from the client.
    2168       </p>
    2169       <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>
    2170       <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
    2171          recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could
    2172          have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From
    2173          information.
    2174       </p>
    2175       <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.
    2176       </p>
    2177       <p id="rfc.section.11.2.p.3">Authors of services <em class="bcp14">SHOULD NOT</em> use GET-based forms for the submission of sensitive data because that data will be placed in the request-target. Many existing
    2178          servers, proxies, and user agents log or display the request-target in places where it might be visible to third parties.
    2179          Such services can use POST-based form submission instead.
    2180       </p>
    2181       <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>
    2182       <p id="rfc.section.11.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location header fields in responses that are generated under control of said organizations
    2183          to make sure that they do not attempt to invalidate resources over which they have no authority.
    2184       </p>
    2185       <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
     2382      <div id="ack">
     2383         <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
     2384      </div>
    21862385      <h1 id="rfc.references"><a id="rfc.section.13" href="#rfc.section.13">13.</a> References
    21872386      </h1>
    21882387      <h2 id="rfc.references.1"><a href="#rfc.section.13.1" id="rfc.section.13.1">13.1</a> Normative References
    21892388      </h2>
    2190       <table>                 
     2389      <table>
    21912390         <tr>
    21922391            <td class="reference"><b id="Part1">[Part1]</b></td>
    2193             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-12">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-12 (work in progress), October&nbsp;2010.
     2392            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-12">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-12 (work in progress), October&nbsp;2010.
    21942393            </td>
    21952394         </tr>
    21962395         <tr>
    21972396            <td class="reference"><b id="Part3">[Part3]</b></td>
    2198             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-12">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-12 (work in progress), October&nbsp;2010.
     2397            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-12">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-12 (work in progress), October&nbsp;2010.
    21992398            </td>
    22002399         </tr>
    22012400         <tr>
    22022401            <td class="reference"><b id="Part4">[Part4]</b></td>
    2203             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-12">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-12 (work in progress), October&nbsp;2010.
     2402            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-12">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-12 (work in progress), October&nbsp;2010.
    22042403            </td>
    22052404         </tr>
    22062405         <tr>
    22072406            <td class="reference"><b id="Part5">[Part5]</b></td>
    2208             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-12">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-12 (work in progress), October&nbsp;2010.
     2407            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-12">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-12 (work in progress), October&nbsp;2010.
    22092408            </td>
    22102409         </tr>
    22112410         <tr>
    22122411            <td class="reference"><b id="Part6">[Part6]</b></td>
    2213             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-12">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-12 (work in progress), October&nbsp;2010.
     2412            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-12">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-12 (work in progress), October&nbsp;2010.
    22142413            </td>
    22152414         </tr>
    22162415         <tr>
    22172416            <td class="reference"><b id="Part7">[Part7]</b></td>
    2218             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-12">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-12 (work in progress), October&nbsp;2010.
     2417            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-12">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-12 (work in progress), October&nbsp;2010.
    22192418            </td>
    22202419         </tr>
    22212420         <tr>
    22222421            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    2223             <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.
     2422            <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.
    22242423            </td>
    22252424         </tr>
    22262425         <tr>
    22272426            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
    2228             <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
     2427            <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="https://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
    22292428            </td>
    22302429         </tr>
    22312430         <tr>
    22322431            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    2233             <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.
     2432            <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.
    22342433            </td>
    22352434         </tr>
     
    22372436      <h2 id="rfc.references.2"><a href="#rfc.section.13.2" id="rfc.section.13.2">13.2</a> Informative References
    22382437      </h2>
    2239       <table>             
     2438      <table>
    22402439         <tr>
    22412440            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    2242             <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="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
     2441            <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.
    22432442            </td>
    22442443         </tr>
    22452444         <tr>
    22462445            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
    2247             <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.
     2446            <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.
    22482447            </td>
    22492448         </tr>
    22502449         <tr>
    22512450            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    2252             <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.
     2451            <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.
    22532452            </td>
    22542453         </tr>
    22552454         <tr>
    22562455            <td class="reference"><b id="RFC2817">[RFC2817]</b></td>
    2257             <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.
     2456            <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.
    22582457            </td>
    22592458         </tr>
    22602459         <tr>
    22612460            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    2262             <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.
     2461            <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.
    22632462            </td>
    22642463         </tr>
    22652464         <tr>
    22662465            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
    2267             <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.
     2466            <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.
    22682467            </td>
    22692468         </tr>
    22702469         <tr>
    22712470            <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
    2272             <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
     2471            <td class="top">Resnick, P., “<a href="https://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
    22732472            </td>
    22742473         </tr>
    22752474      </table>
    2276       <div class="avoidbreak">
    2277          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    2278          <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
    2279                (editor)
    2280                <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>
    2281          <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">Alcatel-Lucent Bell Labs</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@freedesktop.org"><span class="email">jg@freedesktop.org</span></a></span><span class="vcardline">URI: <a href="http://gettys.wordpress.com/" class="url">http://gettys.wordpress.com/</a></span></address>
    2282          <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>
    2283          <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>
    2284          <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>
    2285          <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>
    2286          <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>
    2287          <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
    2288                (editor)
    2289                <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>
    2290          <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
    2291                (editor)
    2292                <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>
     2475      <div id="changes.from.rfc.2616">
     2476         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
     2477         <p id="rfc.section.A.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>)
     2478         </p>
     2479         <p id="rfc.section.A.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;7.5</a>)
     2480         </p>
     2481         <p id="rfc.section.A.p.3">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
     2482            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.4" title="307 Temporary Redirect">8.3.8</a>)
     2483         </p>
     2484         <p id="rfc.section.A.p.4">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource
     2485            must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
     2486            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>)
     2487         </p>
     2488         <p id="rfc.section.A.p.5">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement
     2489            on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;9.1</a>)
     2490         </p>
     2491         <p id="rfc.section.A.p.6">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
     2492            symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate.
     2493            (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.4</a>)
     2494         </p>
     2495         <p id="rfc.section.A.p.7">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.6</a>)
     2496         </p>
     2497         <p id="rfc.section.A.p.8">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated
     2498            correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.35"><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>)
     2499         </p>
    22932500      </div>
    2294       <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
    2295       <p id="rfc.section.A.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>)
    2296       </p>
    2297       <p id="rfc.section.A.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;7.5</a>)
    2298       </p>
    2299       <p id="rfc.section.A.p.3">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
    2300          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.4" title="307 Temporary Redirect">8.3.8</a>)
    2301       </p>
    2302       <p id="rfc.section.A.p.4">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource
    2303          must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
    2304          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>)
    2305       </p>
    2306       <p id="rfc.section.A.p.5">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement
    2307          on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;9.1</a>)
    2308       </p>
    2309       <p id="rfc.section.A.p.6">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
    2310          symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate.
    2311          (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.4</a>)
    2312       </p>
    2313       <p id="rfc.section.A.p.7">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.6</a>)
    2314       </p>
    2315       <p id="rfc.section.A.p.8">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated
    2316          correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.35"><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>)
    2317       </p>
    2318       <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    2319       <div id="rfc.figure.u.30"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = &lt;Accept, defined in [Part3], Section 6.1&gt;
     2501      <div id="collected.abnf">
     2502         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
     2503         <div id="rfc.figure.u.30"></div><pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = &lt;Accept, defined in [Part3], Section 6.1&gt;
    23202504<a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = &lt;Accept-Charset, defined in [Part3], Section 6.2&gt;
    23212505<a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> = &lt;Accept-Encoding, defined in [Part3], Section 6.3&gt;
     
    24262610
    24272611<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
    2428 </pre> <div id="rfc.figure.u.31"></div>
    2429       <p>ABNF diagnostics:</p><pre class="inline">; Reason-Phrase defined but not used
     2612</pre><div id="rfc.figure.u.31"></div>
     2613         <p>ABNF diagnostics:</p><pre class="inline">; Reason-Phrase defined but not used
    24302614; Status-Code defined but not used
    24312615; request-header defined but not used
    24322616; response-header defined but not used
    2433 </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>
    2434       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC 2616
    2435       </h2>
    2436       <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>.
    2437       </p>
    2438       <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
    2439       </h2>
    2440       <p id="rfc.section.C.2.p.1">Closed issues: </p>
    2441       <ul>
    2442          <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;)
    2443          </li>
    2444          <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;)
    2445          </li>
    2446          <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;)
    2447          </li>
    2448          <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;)
    2449          </li>
    2450          <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"
    2451          </li>
    2452          <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"
    2453          </li>
    2454          <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"
    2455          </li>
    2456          <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"
    2457          </li>
    2458       </ul>
    2459       <p id="rfc.section.C.2.p.2">Other changes: </p>
    2460       <ul>
    2461          <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.17"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>
    2462          </li>
    2463       </ul>
    2464       <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
    2465       </h2>
    2466       <p id="rfc.section.C.3.p.1">Closed issues: </p>
    2467       <ul>
    2468          <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"
    2469          </li>
    2470          <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"
    2471          </li>
    2472       </ul>
    2473       <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;):
    2474       </p>
    2475       <ul>
    2476          <li>Move "Product Tokens" section (back) into Part 1, as "token" is used in the definition of the Upgrade header field.</li>
    2477          <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    2478          <li>Copy definition of delta-seconds from Part6 instead of referencing it.</li>
    2479       </ul>
    2480       <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>
    2481       <p id="rfc.section.C.4.p.1">Closed issues: </p>
    2482       <ul>
    2483          <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"
    2484          </li>
    2485          <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"
    2486          </li>
    2487          <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"
    2488          </li>
    2489          <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"
    2490          </li>
    2491          <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"
    2492          </li>
    2493          <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"
    2494          </li>
    2495          <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'"
    2496          </li>
    2497       </ul>
    2498       <p id="rfc.section.C.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
    2499       </p>
    2500       <ul>
    2501          <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li>
    2502       </ul>
    2503       <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;):
    2504       </p>
    2505       <ul>
    2506          <li>Replace string literals when the string really is case-sensitive (method).</li>
    2507       </ul>
    2508       <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>
    2509       <p id="rfc.section.C.5.p.1">Closed issues: </p>
    2510       <ul>
    2511          <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"
    2512          </li>
    2513          <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"
    2514          </li>
    2515          <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"
    2516          </li>
    2517       </ul>
    2518       <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;):
    2519       </p>
    2520       <ul>
    2521          <li>Added initial proposal for registration process, plus initial content (non-HTTP/1.1 methods to be added by a separate specification).</li>
    2522       </ul>
    2523       <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>
    2524       <p id="rfc.section.C.6.p.1">Closed issues: </p>
    2525       <ul>
    2526          <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-*"
    2527          </li>
    2528          <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"
    2529          </li>
    2530       </ul>
    2531       <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;):
    2532       </p>
    2533       <ul>
    2534          <li>Use "/" instead of "|" for alternatives.</li>
    2535          <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
    2536          <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
    2537       </ul>
    2538       <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>
    2539       <p id="rfc.section.C.7.p.1">Closed issues: </p>
    2540       <ul>
    2541          <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"
    2542          </li>
    2543       </ul>
    2544       <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;):
    2545       </p>
    2546       <ul>
    2547          <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
    2548       </ul>
    2549       <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>
    2550       <p id="rfc.section.C.8.p.1">Closed issues: </p>
    2551       <ul>
    2552          <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"
    2553          </li>
    2554          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/164">http://tools.ietf.org/wg/httpbis/trac/ticket/164</a>&gt;: "status codes vs methods"
    2555          </li>
    2556          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/170">http://tools.ietf.org/wg/httpbis/trac/ticket/170</a>&gt;: "Do not require "updates" relation for specs that register status codes or method names"
    2557          </li>
    2558       </ul>
    2559       <h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p2-semantics-07</a></h2>
    2560       <p id="rfc.section.C.9.p.1">Closed issues: </p>
    2561       <ul>
    2562          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/27">http://tools.ietf.org/wg/httpbis/trac/ticket/27</a>&gt;: "Idempotency"
    2563          </li>
    2564          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/33">http://tools.ietf.org/wg/httpbis/trac/ticket/33</a>&gt;: "TRACE security considerations"
    2565          </li>
    2566          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/110">http://tools.ietf.org/wg/httpbis/trac/ticket/110</a>&gt;: "Clarify rules for determining what entities a response carries"
    2567          </li>
    2568          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/140">http://tools.ietf.org/wg/httpbis/trac/ticket/140</a>&gt;: "update note citing RFC 1945 and 2068"
    2569          </li>
    2570          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/182">http://tools.ietf.org/wg/httpbis/trac/ticket/182</a>&gt;: "update note about redirect limit"
    2571          </li>
    2572          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/191">http://tools.ietf.org/wg/httpbis/trac/ticket/191</a>&gt;: "Location header ABNF should use 'URI'"
    2573          </li>
    2574          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/192">http://tools.ietf.org/wg/httpbis/trac/ticket/192</a>&gt;: "fragments in Location vs status 303"
    2575          </li>
    2576          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/198">http://tools.ietf.org/wg/httpbis/trac/ticket/198</a>&gt;: "move IANA registrations for optional status codes"
    2577          </li>
    2578       </ul>
    2579       <p id="rfc.section.C.9.p.2">Partly resolved issues: </p>
    2580       <ul>
    2581          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/171">http://tools.ietf.org/wg/httpbis/trac/ticket/171</a>&gt;: "Are OPTIONS and TRACE safe?"
    2582          </li>
    2583       </ul>
    2584       <h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p2-semantics-08</a></h2>
    2585       <p id="rfc.section.C.10.p.1">C