source: draft-ietf-httpbis/latest/p2-semantics.html @ 386

Last change on this file since 386 was 386, checked in by julian.reschke@…, 11 years ago

add missing ABNF references

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 253.3 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://www.w3.org/2006/03/hcard">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>HTTP/1.1, part 2: Message Semantics</title><style type="text/css" title="Xml2Rfc (sans serif)">
7a {
8  text-decoration: none;
9}
10a.smpl {
11  color: black;
12}
13a:hover {
14  text-decoration: underline;
15}
16a:active {
17  text-decoration: underline;
18}
19address {
20  margin-top: 1em;
21  margin-left: 2em;
22  font-style: normal;
23}
24body {
25  color: black;
26  font-family: verdana, helvetica, arial, sans-serif;
27  font-size: 10pt;
28}
29cite {
30  font-style: normal;
31}
32dd {
33  margin-right: 2em;
34}
35dl {
36  margin-left: 2em;
37}
38
39dl.empty dd {
40  margin-top: .5em;
41}
42dl p {
43  margin-left: 0em;
44}
45dt {
46  margin-top: .5em;
47}
48h1 {
49  font-size: 14pt;
50  line-height: 21pt;
51  page-break-after: avoid;
52}
53h1.np {
54  page-break-before: always;
55}
56h1 a {
57  color: #333333;
58}
59h2 {
60  font-size: 12pt;
61  line-height: 15pt;
62  page-break-after: avoid;
63}
64h2 a {
65  color: black;
66}
67h3 {
68  font-size: 10pt;
69  page-break-after: avoid;
70}
71h3 a {
72  color: black;
73}
74h4 {
75  font-size: 10pt;
76  page-break-after: avoid;
77}
78h4 a {
79  color: black;
80}
81h5 {
82  font-size: 10pt;
83  page-break-after: avoid;
84}
85h5 a {
86  color: black;
87}
88img {
89  margin-left: 3em;
90}
91li {
92  margin-left: 2em;
93  margin-right: 2em;
94}
95ol {
96  margin-left: 2em;
97  margin-right: 2em;
98}
99ol p {
100  margin-left: 0em;
101}
102p {
103  margin-left: 2em;
104  margin-right: 2em;
105}
106pre {
107  margin-left: 3em;
108  background-color: lightyellow;
109  padding: .25em;
110}
111pre.text2 {
112  border-style: dotted;
113  border-width: 1px;
114  background-color: #f0f0f0;
115  width: 69em;
116}
117pre.inline {
118  background-color: white;
119  padding: 0em;
120}
121pre.text {
122  border-style: dotted;
123  border-width: 1px;
124  background-color: #f8f8f8;
125  width: 69em;
126}
127pre.drawing {
128  border-style: solid;
129  border-width: 1px;
130  background-color: #f8f8f8;
131  padding: 2em;
132}
133table {
134  margin-left: 2em;
135}
136table.tt {
137  vertical-align: top;
138}
139table.full {
140  border-style: outset;
141  border-width: 1px;
142}
143table.headers {
144  border-style: outset;
145  border-width: 1px;
146}
147table.tt td {
148  vertical-align: top;
149}
150table.full td {
151  border-style: inset;
152  border-width: 1px;
153}
154table.tt th {
155  vertical-align: top;
156}
157table.full th {
158  border-style: inset;
159  border-width: 1px;
160}
161table.headers th {
162  border-style: none none inset none;
163  border-width: 1px;
164}
165table.header {
166  width: 95%;
167  font-size: 10pt;
168  color: white;
169}
170td.top {
171  vertical-align: top;
172}
173td.topnowrap {
174  vertical-align: top;
175  white-space: nowrap; 
176}
177td.header {
178  background-color: gray;
179  width: 50%;
180}
181td.header a {
182  color: white;
183}
184td.reference {
185  vertical-align: top;
186  white-space: nowrap;
187  padding-right: 1em;
188}
189thead {
190  display:table-header-group;
191}
192ul.toc {
193  list-style: none;
194  margin-left: 1.5em;
195  margin-right: 0em;
196  padding-left: 0em;
197}
198li.tocline0 {
199  line-height: 150%;
200  font-weight: bold;
201  font-size: 10pt;
202  margin-left: 0em;
203  margin-right: 0em;
204}
205li.tocline1 {
206  line-height: normal;
207  font-weight: normal;
208  font-size: 9pt;
209  margin-left: 0em;
210  margin-right: 0em;
211}
212li.tocline2 {
213  font-size: 0pt;
214}
215ul p {
216  margin-left: 0em;
217}
218ul.ind {
219  list-style: none;
220  margin-left: 1.5em;
221  margin-right: 0em;
222  padding-left: 0em;
223}
224li.indline0 {
225  font-weight: bold;
226  line-height: 200%;
227  margin-left: 0em;
228  margin-right: 0em;
229}
230li.indline1 {
231  font-weight: normal;
232  line-height: 150%;
233  margin-left: 0em;
234  margin-right: 0em;
235}
236.bcp14 {
237  font-style: normal;
238  text-transform: lowercase;
239  font-variant: small-caps;
240}
241.comment {
242  background-color: yellow;
243}
244.center {
245  text-align: center;
246}
247.error {
248  color: red;
249  font-style: italic;
250  font-weight: bold;
251}
252.figure {
253  font-weight: bold;
254  text-align: center;
255  font-size: 9pt;
256}
257.filename {
258  color: #333333;
259  font-weight: bold;
260  font-size: 12pt;
261  line-height: 21pt;
262  text-align: center;
263}
264.fn {
265  font-weight: bold;
266}
267.hidden {
268  display: none;
269}
270.left {
271  text-align: left;
272}
273.right {
274  text-align: right;
275}
276.title {
277  color: #990000;
278  font-size: 18pt;
279  line-height: 18pt;
280  font-weight: bold;
281  text-align: center;
282  margin-top: 36pt;
283}
284.vcardline {
285  display: block;
286}
287.warning {
288  font-size: 14pt;
289  background-color: yellow;
290}
291
292
293@media print {
294  .noprint {
295    display: none;
296  }
297 
298  a {
299    color: black;
300    text-decoration: none;
301  }
302
303  table.header {
304    width: 90%;
305  }
306
307  td.header {
308    width: 50%;
309    color: black;
310    background-color: white;
311    vertical-align: top;
312    font-size: 12pt;
313  }
314
315  ul.toc a::after {
316    content: leader('.') target-counter(attr(href), page);
317  }
318 
319  a.iref {
320    content: target-counter(attr(href), page);
321  }
322 
323  .print2col {
324    column-count: 2;
325    -moz-column-count: 2;
326    column-fill: auto;
327  }
328}
329
330@page {
331  @top-left {
332       content: "INTERNET DRAFT"; 
333  } 
334  @top-right {
335       content: "November 2008"; 
336  } 
337  @top-center {
338       content: "HTTP/1.1, Part 2"; 
339  } 
340  @bottom-left {
341       content: "Fielding, et al."; 
342  } 
343  @bottom-center {
344       content: "Standards Track"; 
345  } 
346  @bottom-right {
347       content: "[Page " counter(page) "]"; 
348  } 
349}
350
351@page:first { 
352    @top-left {
353      content: normal;
354    }
355    @top-right {
356      content: normal;
357    }
358    @top-center {
359      content: normal;
360    }
361}
362</style><link rel="Contents" href="#rfc.toc">
363      <link rel="Author" href="#rfc.authors">
364      <link rel="Copyright" href="#rfc.copyright">
365      <link rel="Index" href="#rfc.index">
366      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
367      <link rel="Chapter" title="2 Notational Conventions and Generic Grammar" href="#rfc.section.2">
368      <link rel="Chapter" title="3 Method" href="#rfc.section.3">
369      <link rel="Chapter" title="4 Request Header Fields" href="#rfc.section.4">
370      <link rel="Chapter" title="5 Status Code and Reason Phrase" href="#rfc.section.5">
371      <link rel="Chapter" title="6 Response Header Fields" href="#rfc.section.6">
372      <link rel="Chapter" title="7 Entity" href="#rfc.section.7">
373      <link rel="Chapter" title="8 Method Definitions" href="#rfc.section.8">
374      <link rel="Chapter" title="9 Status Code Definitions" href="#rfc.section.9">
375      <link rel="Chapter" title="10 Header Field Definitions" href="#rfc.section.10">
376      <link rel="Chapter" title="11 IANA Considerations" href="#rfc.section.11">
377      <link rel="Chapter" title="12 Security Considerations" href="#rfc.section.12">
378      <link rel="Chapter" title="13 Acknowledgments" href="#rfc.section.13">
379      <link rel="Chapter" href="#rfc.section.14" title="14 References">
380      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
381      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
382      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.400, 2008-10-10 14:04:14, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
383      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
384      <meta name="DC.Creator" content="Fielding, R.">
385      <meta name="DC.Creator" content="Gettys, J.">
386      <meta name="DC.Creator" content="Mogul, J.">
387      <meta name="DC.Creator" content="Frystyk, H.">
388      <meta name="DC.Creator" content="Masinter, L.">
389      <meta name="DC.Creator" content="Leach, P.">
390      <meta name="DC.Creator" content="Berners-Lee, T.">
391      <meta name="DC.Creator" content="Lafon, Y.">
392      <meta name="DC.Creator" content="Reschke, J. F.">
393      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
394      <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-11">
395      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
396      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields.">
397   </head>
398   <body>
399      <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
400         <tr>
401            <td class="header left">Network Working Group</td>
402            <td class="header right">R. Fielding, Editor</td>
403         </tr>
404         <tr>
405            <td class="header left">Internet Draft</td>
406            <td class="header right">Day Software</td>
407         </tr>
408         <tr>
409            <td class="header left">
410               &lt;draft-ietf-httpbis-p2-semantics-latest&gt;
411               
412            </td>
413            <td class="header right">J. Gettys</td>
414         </tr>
415         <tr>
416            <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
417            </td>
418            <td class="header right">One Laptop per Child</td>
419         </tr>
420         <tr>
421            <td class="header left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved)
422            </td>
423            <td class="header right">J. Mogul</td>
424         </tr>
425         <tr>
426            <td class="header left">Intended status: Standards Track</td>
427            <td class="header right">HP</td>
428         </tr>
429         <tr>
430            <td class="header left">Expires: May 2009</td>
431            <td class="header right">H. Frystyk</td>
432         </tr>
433         <tr>
434            <td class="header left"></td>
435            <td class="header right">Microsoft</td>
436         </tr>
437         <tr>
438            <td class="header left"></td>
439            <td class="header right">L. Masinter</td>
440         </tr>
441         <tr>
442            <td class="header left"></td>
443            <td class="header right">Adobe Systems</td>
444         </tr>
445         <tr>
446            <td class="header left"></td>
447            <td class="header right">P. Leach</td>
448         </tr>
449         <tr>
450            <td class="header left"></td>
451            <td class="header right">Microsoft</td>
452         </tr>
453         <tr>
454            <td class="header left"></td>
455            <td class="header right">T. Berners-Lee</td>
456         </tr>
457         <tr>
458            <td class="header left"></td>
459            <td class="header right">W3C/MIT</td>
460         </tr>
461         <tr>
462            <td class="header left"></td>
463            <td class="header right">Y. Lafon, Editor</td>
464         </tr>
465         <tr>
466            <td class="header left"></td>
467            <td class="header right">W3C</td>
468         </tr>
469         <tr>
470            <td class="header left"></td>
471            <td class="header right">J. F. Reschke, Editor</td>
472         </tr>
473         <tr>
474            <td class="header left"></td>
475            <td class="header right">greenbytes</td>
476         </tr>
477         <tr>
478            <td class="header left"></td>
479            <td class="header right">November 14, 2008</td>
480         </tr>
481      </table>
482      <p class="title">HTTP/1.1, part 2: Message Semantics<br><span class="filename">draft-ietf-httpbis-p2-semantics-latest</span></p>
483      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
484      <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
485         is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
486         6 of BCP 79.
487      </p>
488      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
489         that other groups may also distribute working documents as Internet-Drafts.
490      </p>
491      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
492         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
493         in progress”.
494      </p>
495      <p>The list of current Internet-Drafts can be accessed at &lt;<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>&gt;.
496      </p>
497      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
498      </p>
499      <p>This Internet-Draft will expire in May 2009.</p>
500      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
501      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
502         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the
503         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
504         2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and
505         response-header fields.
506      </p> 
507      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
508      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
509         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
510      </p> 
511      <p>The changes in this draft are summarized in <a href="#changes.since.05" title="Since draft-ietf-httpbis-p2-semantics-05">Appendix&nbsp;B.7</a>.
512      </p> 
513      <hr class="noprint">
514      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
515      <ul class="toc">
516         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
517               <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
518            </ul>
519         </li>
520         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a></li>
521         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#method">Method</a><ul class="toc">
522               <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a></li>
523            </ul>
524         </li>
525         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
526         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a><ul class="toc">
527               <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a></li>
528            </ul>
529         </li>
530         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
531         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#entity">Entity</a></li>
532         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul class="toc">
533               <li class="tocline1">8.1&nbsp;&nbsp;&nbsp;<a href="#safe.and.idempotent">Safe and Idempotent Methods</a><ul class="toc">
534                     <li class="tocline1">8.1.1&nbsp;&nbsp;&nbsp;<a href="#safe.methods">Safe Methods</a></li>
535                     <li class="tocline1">8.1.2&nbsp;&nbsp;&nbsp;<a href="#idempotent.methods">Idempotent Methods</a></li>
536                  </ul>
537               </li>
538               <li class="tocline1">8.2&nbsp;&nbsp;&nbsp;<a href="#OPTIONS">OPTIONS</a></li>
539               <li class="tocline1">8.3&nbsp;&nbsp;&nbsp;<a href="#GET">GET</a></li>
540               <li class="tocline1">8.4&nbsp;&nbsp;&nbsp;<a href="#HEAD">HEAD</a></li>
541               <li class="tocline1">8.5&nbsp;&nbsp;&nbsp;<a href="#POST">POST</a></li>
542               <li class="tocline1">8.6&nbsp;&nbsp;&nbsp;<a href="#PUT">PUT</a></li>
543               <li class="tocline1">8.7&nbsp;&nbsp;&nbsp;<a href="#DELETE">DELETE</a></li>
544               <li class="tocline1">8.8&nbsp;&nbsp;&nbsp;<a href="#TRACE">TRACE</a></li>
545               <li class="tocline1">8.9&nbsp;&nbsp;&nbsp;<a href="#CONNECT">CONNECT</a></li>
546            </ul>
547         </li>
548         <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#status.codes">Status Code Definitions</a><ul class="toc">
549               <li class="tocline1">9.1&nbsp;&nbsp;&nbsp;<a href="#status.1xx">Informational 1xx</a><ul class="toc">
550                     <li class="tocline1">9.1.1&nbsp;&nbsp;&nbsp;<a href="#status.100">100 Continue</a></li>
551                     <li class="tocline1">9.1.2&nbsp;&nbsp;&nbsp;<a href="#status.101">101 Switching Protocols</a></li>
552                  </ul>
553               </li>
554               <li class="tocline1">9.2&nbsp;&nbsp;&nbsp;<a href="#status.2xx">Successful 2xx</a><ul class="toc">
555                     <li class="tocline1">9.2.1&nbsp;&nbsp;&nbsp;<a href="#status.200">200 OK</a></li>
556                     <li class="tocline1">9.2.2&nbsp;&nbsp;&nbsp;<a href="#status.201">201 Created</a></li>
557                     <li class="tocline1">9.2.3&nbsp;&nbsp;&nbsp;<a href="#status.202">202 Accepted</a></li>
558                     <li class="tocline1">9.2.4&nbsp;&nbsp;&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></li>
559                     <li class="tocline1">9.2.5&nbsp;&nbsp;&nbsp;<a href="#status.204">204 No Content</a></li>
560                     <li class="tocline1">9.2.6&nbsp;&nbsp;&nbsp;<a href="#status.205">205 Reset Content</a></li>
561                     <li class="tocline1">9.2.7&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
562                  </ul>
563               </li>
564               <li class="tocline1">9.3&nbsp;&nbsp;&nbsp;<a href="#status.3xx">Redirection 3xx</a><ul class="toc">
565                     <li class="tocline1">9.3.1&nbsp;&nbsp;&nbsp;<a href="#status.300">300 Multiple Choices</a></li>
566                     <li class="tocline1">9.3.2&nbsp;&nbsp;&nbsp;<a href="#status.301">301 Moved Permanently</a></li>
567                     <li class="tocline1">9.3.3&nbsp;&nbsp;&nbsp;<a href="#status.302">302 Found</a></li>
568                     <li class="tocline1">9.3.4&nbsp;&nbsp;&nbsp;<a href="#status.303">303 See Other</a></li>
569                     <li class="tocline1">9.3.5&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
570                     <li class="tocline1">9.3.6&nbsp;&nbsp;&nbsp;<a href="#status.305">305 Use Proxy</a></li>
571                     <li class="tocline1">9.3.7&nbsp;&nbsp;&nbsp;<a href="#status.306">306 (Unused)</a></li>
572                     <li class="tocline1">9.3.8&nbsp;&nbsp;&nbsp;<a href="#status.307">307 Temporary Redirect</a></li>
573                  </ul>
574               </li>
575               <li class="tocline1">9.4&nbsp;&nbsp;&nbsp;<a href="#status.4xx">Client Error 4xx</a><ul class="toc">
576                     <li class="tocline1">9.4.1&nbsp;&nbsp;&nbsp;<a href="#status.400">400 Bad Request</a></li>
577                     <li class="tocline1">9.4.2&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
578                     <li class="tocline1">9.4.3&nbsp;&nbsp;&nbsp;<a href="#status.402">402 Payment Required</a></li>
579                     <li class="tocline1">9.4.4&nbsp;&nbsp;&nbsp;<a href="#status.403">403 Forbidden</a></li>
580                     <li class="tocline1">9.4.5&nbsp;&nbsp;&nbsp;<a href="#status.404">404 Not Found</a></li>
581                     <li class="tocline1">9.4.6&nbsp;&nbsp;&nbsp;<a href="#status.405">405 Method Not Allowed</a></li>
582                     <li class="tocline1">9.4.7&nbsp;&nbsp;&nbsp;<a href="#status.406">406 Not Acceptable</a></li>
583                     <li class="tocline1">9.4.8&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
584                     <li class="tocline1">9.4.9&nbsp;&nbsp;&nbsp;<a href="#status.408">408 Request Timeout</a></li>
585                     <li class="tocline1">9.4.10&nbsp;&nbsp;&nbsp;<a href="#status.409">409 Conflict</a></li>
586                     <li class="tocline1">9.4.11&nbsp;&nbsp;&nbsp;<a href="#status.410">410 Gone</a></li>
587                     <li class="tocline1">9.4.12&nbsp;&nbsp;&nbsp;<a href="#status.411">411 Length Required</a></li>
588                     <li class="tocline1">9.4.13&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
589                     <li class="tocline1">9.4.14&nbsp;&nbsp;&nbsp;<a href="#status.413">413 Request Entity Too Large</a></li>
590                     <li class="tocline1">9.4.15&nbsp;&nbsp;&nbsp;<a href="#status.414">414 Request-URI Too Long</a></li>
591                     <li class="tocline1">9.4.16&nbsp;&nbsp;&nbsp;<a href="#status.415">415 Unsupported Media Type</a></li>
592                     <li class="tocline1">9.4.17&nbsp;&nbsp;&nbsp;<a href="#status.416">416 Requested Range Not Satisfiable</a></li>
593                     <li class="tocline1">9.4.18&nbsp;&nbsp;&nbsp;<a href="#status.417">417 Expectation Failed</a></li>
594                  </ul>
595               </li>
596               <li class="tocline1">9.5&nbsp;&nbsp;&nbsp;<a href="#status.5xx">Server Error 5xx</a><ul class="toc">
597                     <li class="tocline1">9.5.1&nbsp;&nbsp;&nbsp;<a href="#status.500">500 Internal Server Error</a></li>
598                     <li class="tocline1">9.5.2&nbsp;&nbsp;&nbsp;<a href="#status.501">501 Not Implemented</a></li>
599                     <li class="tocline1">9.5.3&nbsp;&nbsp;&nbsp;<a href="#status.502">502 Bad Gateway</a></li>
600                     <li class="tocline1">9.5.4&nbsp;&nbsp;&nbsp;<a href="#status.503">503 Service Unavailable</a></li>
601                     <li class="tocline1">9.5.5&nbsp;&nbsp;&nbsp;<a href="#status.504">504 Gateway Timeout</a></li>
602                     <li class="tocline1">9.5.6&nbsp;&nbsp;&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></li>
603                  </ul>
604               </li>
605            </ul>
606         </li>
607         <li class="tocline0">10.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
608               <li class="tocline1">10.1&nbsp;&nbsp;&nbsp;<a href="#header.allow">Allow</a></li>
609               <li class="tocline1">10.2&nbsp;&nbsp;&nbsp;<a href="#header.expect">Expect</a></li>
610               <li class="tocline1">10.3&nbsp;&nbsp;&nbsp;<a href="#header.from">From</a></li>
611               <li class="tocline1">10.4&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
612               <li class="tocline1">10.5&nbsp;&nbsp;&nbsp;<a href="#header.max-forwards">Max-Forwards</a></li>
613               <li class="tocline1">10.6&nbsp;&nbsp;&nbsp;<a href="#header.referer">Referer</a></li>
614               <li class="tocline1">10.7&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
615               <li class="tocline1">10.8&nbsp;&nbsp;&nbsp;<a href="#header.server">Server</a></li>
616               <li class="tocline1">10.9&nbsp;&nbsp;&nbsp;<a href="#header.user-agent">User-Agent</a></li>
617            </ul>
618         </li>
619         <li class="tocline0">11.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc">
620               <li class="tocline1">11.1&nbsp;&nbsp;&nbsp;<a href="#method.registration">Method Registry</a></li>
621               <li class="tocline1">11.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registry</a></li>
622               <li class="tocline1">11.3&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
623            </ul>
624         </li>
625         <li class="tocline0">12.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul class="toc">
626               <li class="tocline1">12.1&nbsp;&nbsp;&nbsp;<a href="#security.sensitive">Transfer of Sensitive Information</a></li>
627               <li class="tocline1">12.2&nbsp;&nbsp;&nbsp;<a href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></li>
628               <li class="tocline1">12.3&nbsp;&nbsp;&nbsp;<a href="#location.spoofing">Location Headers and Spoofing</a></li>
629            </ul>
630         </li>
631         <li class="tocline0">13.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
632         <li class="tocline0">14.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
633               <li class="tocline1">14.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
634               <li class="tocline1">14.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
635            </ul>
636         </li>
637         <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
638         <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">
639               <li class="tocline1">A.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
640               <li class="tocline1">A.2&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
641            </ul>
642         </li>
643         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
644               <li class="tocline1">B.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
645               <li class="tocline1">B.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p2-semantics-00</a></li>
646               <li class="tocline1">B.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.3">Since draft-ietf-httpbis-p2-semantics-01</a></li>
647               <li class="tocline1">B.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></li>
648               <li class="tocline1">B.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></li>
649               <li class="tocline1">B.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></li>
650               <li class="tocline1">B.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></li>
651            </ul>
652         </li>
653         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
654         <li class="tocline0"><a href="#rfc.index">Index</a></li>
655      </ul>
656      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
657      <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
658         to each request, in the order received on that connection, with one or more HTTP response messages. This document defines
659         the commonly agreed upon semantics of the HTTP uniform interface, the intentions defined by each request method, and the various
660         response messages that might be expected as a result of applying that method for the requested resource.
661      </p>
662      <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
663         errata changes. The next draft will reorganize the sections to better reflect the content. In particular, the sections will
664         be ordered according to the typical processing of an HTTP request message (after message parsing): resource mapping, general
665         header fields, methods, request modifiers, response status, and resource metadata. The current mess reflects how widely dispersed
666         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>.
667      </p>
668      <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>
669      <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"
670         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>.
671      </p>
672      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
673      </p>
674      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1>
675      <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="ABNF Extension: #rule">Section 2.1</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> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 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>:
676      </p>
677      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#notation" class="smpl">CR</a>            = &lt;CR, 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 2.2</a>&gt;
678  <a href="#notation" class="smpl">DIGIT</a>         = &lt;DIGIT, 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 2.2</a>&gt;
679  <a href="#notation" class="smpl">LF</a>            = &lt;LF, 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 2.2</a>&gt;
680</pre><div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#notation" class="smpl">comment</a>       = &lt;comment, 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 2.2</a>&gt;
681  <a href="#notation" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
682  <a href="#notation" class="smpl">token</a>         = &lt;token, 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#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
683  <a href="#notation" class="smpl">OWS</a>           = &lt;OWS, 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#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
684  <a href="#notation" class="smpl">RWS</a>           = &lt;RWS, 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#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
685  <a href="#notation" class="smpl">TEXT</a>          = &lt;TEXT, defined in <a href="#Part1" id="rfc.xref.Part1.12"><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 2.2</a>&gt;
686</pre><div id="abnf.dependencies">
687         <p id="rfc.section.2.p.4">                                                  The ABNF rules below are defined in other parts:</p>
688      </div>
689      <div id="rfc.figure.u.3"></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.13"><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 3.2</a>&gt;
690  <a href="#abnf.dependencies" class="smpl">fragment</a>      = &lt;fragment, defined in <a href="#Part1" id="rfc.xref.Part1.14"><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 3.2</a>&gt;
691  <a href="#abnf.dependencies" class="smpl">Host</a>          = &lt;Host, defined in <a href="#Part1" id="rfc.xref.Part1.15"><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 3.2</a>&gt;
692  <a href="#abnf.dependencies" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>&gt;
693  <a href="#abnf.dependencies" class="smpl">product</a>       = &lt;product, defined in <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a>&gt;
694  <a href="#abnf.dependencies" class="smpl">relativeURI</a>   = &lt;relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.18"><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 3.2</a>&gt;
695  <a href="#abnf.dependencies" class="smpl">TE</a>            = &lt;TE, defined in <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>&gt;
696</pre><div id="rfc.figure.u.4"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Accept</a>        = &lt;Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><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>&gt;
697  <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> =
698             &lt;Accept-Charset, defined in <a href="#Part3" id="rfc.xref.Part3.2"><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>&gt;
699  <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> =
700             &lt;Accept-Encoding, defined in <a href="#Part3" id="rfc.xref.Part3.3"><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>&gt;
701  <a href="#abnf.dependencies" class="smpl">Accept-Language</a> =
702             &lt;Accept-Language, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a>&gt;
703</pre><div id="rfc.figure.u.5"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">ETag</a>          = &lt;ETag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a>&gt;
704  <a href="#abnf.dependencies" class="smpl">If-Match</a>      = &lt;If-Match, defined in <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 7.2</a>&gt;
705  <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a> =
706             &lt;If-Modified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 7.3</a>&gt;
707  <a href="#abnf.dependencies" class="smpl">If-None-Match</a> = &lt;If-None-Match, defined in <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 7.4</a>&gt;
708  <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a> =
709             &lt;If-Unmodified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 7.5</a>&gt;
710</pre><div id="rfc.figure.u.6"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a> = &lt;Accept-Ranges, defined in <a href="#Part5" id="rfc.xref.Part5.1"><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 6.1</a>&gt;
711  <a href="#abnf.dependencies" class="smpl">If-Range</a>      = &lt;If-Range, defined in <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 6.3</a>&gt;
712  <a href="#abnf.dependencies" class="smpl">Range</a>         = &lt;Range, defined in <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 6.4</a>&gt;
713</pre><div id="rfc.figure.u.7"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Age</a>           = &lt;Age, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a>&gt;
714  <a href="#abnf.dependencies" class="smpl">Vary</a>          = &lt;Vary, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a>&gt;
715</pre><div id="rfc.figure.u.8"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Authorization</a> = &lt;Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a>&gt;
716  <a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a> =
717             &lt;Proxy-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a>&gt;
718  <a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a> =
719             &lt;Proxy-Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.3"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a>&gt;
720  <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a> =
721             &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;
722</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="method" href="#method">Method</a></h1>
723      <p id="rfc.section.3.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p>
724      <div id="rfc.figure.u.9"></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;8.2</a>
725                 / %x47.45.54               ; "GET", <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;8.3</a>
726                 / %x48.45.41.44            ; "HEAD", <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;8.4</a>
727                 / %x50.4F.53.54            ; "POST", <a href="#POST" id="rfc.xref.POST.1" title="POST">Section&nbsp;8.5</a>
728                 / %x50.55.54               ; "PUT", <a href="#PUT" id="rfc.xref.PUT.1" title="PUT">Section&nbsp;8.6</a>
729                 / %x44.45.4C.45.54.45      ; "DELETE", <a href="#DELETE" id="rfc.xref.DELETE.1" title="DELETE">Section&nbsp;8.7</a>
730                 / %x54.52.41.43.45         ; "TRACE", <a href="#TRACE" id="rfc.xref.TRACE.1" title="TRACE">Section&nbsp;8.8</a>
731                 / %x43.4F.4E.4E.45.43.54   ; "CONNECT", <a href="#CONNECT" id="rfc.xref.CONNECT.1" title="CONNECT">Section&nbsp;8.9</a>
732                 / <a href="#method" class="smpl">extension-method</a>
733  <a href="#method" class="smpl">extension-method</a> = <a href="#notation" class="smpl">token</a>
734</pre><p id="rfc.section.3.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;10.1</a>). The return code of the response always notifies the client whether a method is currently allowed on a resource, since the
735         set of allowed methods can change dynamically. An origin server <em class="bcp14">SHOULD</em> return the status code 405 (Method Not Allowed) if the method is known by the origin server but not allowed for the requested
736         resource, and 501 (Not Implemented) if the method is unrecognized or not implemented by the origin server. The methods GET
737         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;8</a>.
738      </p>
739      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
740      <p id="rfc.section.3.1.p.1">The HTTP Method Registry defines the name space for the Method token in the Request line of an HTTP request.</p>
741      <p id="rfc.section.3.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
742      </p>
743      <ul>
744         <li>Method Name (see <a href="#method" title="Method">Section&nbsp;3</a>)
745         </li>
746         <li>Safe ("yes" or "no", see <a href="#safe.methods" title="Safe Methods">Section&nbsp;8.1.1</a>)
747         </li>
748         <li>Pointer to specification text</li>
749      </ul>
750      <p id="rfc.section.3.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>). Any document registering new method names should be traceable through statuses of either 'Obsoletes' or 'Updates' to this
751         document.
752      </p>
753      <p id="rfc.section.3.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;.
754      </p>
755      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1>
756      <p id="rfc.section.4.p.1">The request-header fields allow the client to pass additional information about the request, and about the client itself,
757         to the server. These fields act as request modifiers, with semantics equivalent to the parameters on a programming language
758         method invocation.
759      </p>
760      <div id="rfc.figure.u.10"></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>
761                 / <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>
762                 / <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>
763                 / <a href="#abnf.dependencies" class="smpl">Accept-Language</a>          ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a>
764                 / <a href="#abnf.dependencies" class="smpl">Authorization</a>            ; <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a>
765                 / <a href="#header.expect" class="smpl">Expect</a>                   ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;10.2</a>
766                 / <a href="#header.from" class="smpl">From</a>                     ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;10.3</a>
767                 / <a href="#abnf.dependencies" class="smpl">Host</a>                     ; <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a>
768                 / <a href="#abnf.dependencies" class="smpl">If-Match</a>                 ; <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 7.2</a>
769                 / <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a>        ; <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 7.3</a>
770                 / <a href="#abnf.dependencies" class="smpl">If-None-Match</a>            ; <a href="#Part4" id="rfc.xref.Part4.8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 7.4</a>
771                 / <a href="#abnf.dependencies" class="smpl">If-Range</a>                 ; <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 6.3</a>
772                 / <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a>      ; <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 7.5</a>
773                 / <a href="#header.max-forwards" class="smpl">Max-Forwards</a>             ; <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;10.5</a>
774                 / <a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a>      ; <a href="#Part7" id="rfc.xref.Part7.6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a>
775                 / <a href="#abnf.dependencies" class="smpl">Range</a>                    ; <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 6.4</a>
776                 / <a href="#header.referer" class="smpl">Referer</a>                  ; <a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;10.6</a>
777                 / <a href="#abnf.dependencies" class="smpl">TE</a>                       ; <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>
778                 / <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;10.9</a>
779</pre><p id="rfc.section.4.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new
780         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.
781         Unrecognized header fields are treated as entity-header fields.
782      </p>
783      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h1>
784      <p id="rfc.section.5.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. The status
785         codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section&nbsp;9</a>. The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use
786         by automata and the Reason-Phrase is intended for the human user. The client is not required to examine or display the Reason-Phrase.
787      </p>
788      <p id="rfc.section.5.p.2">The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's,
789         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.
790      </p>
791      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    =
792         "100"  ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;9.1.1</a>: Continue
793       / "101"  ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;9.1.2</a>: Switching Protocols
794       / "200"  ; <a href="#status.200" id="rfc.xref.status.200.1" title="200 OK">Section&nbsp;9.2.1</a>: OK
795       / "201"  ; <a href="#status.201" id="rfc.xref.status.201.1" title="201 Created">Section&nbsp;9.2.2</a>: Created
796       / "202"  ; <a href="#status.202" id="rfc.xref.status.202.1" title="202 Accepted">Section&nbsp;9.2.3</a>: Accepted
797       / "203"  ; <a href="#status.203" id="rfc.xref.status.203.1" title="203 Non-Authoritative Information">Section&nbsp;9.2.4</a>: Non-Authoritative Information
798       / "204"  ; <a href="#status.204" id="rfc.xref.status.204.1" title="204 No Content">Section&nbsp;9.2.5</a>: No Content
799       / "205"  ; <a href="#status.205" id="rfc.xref.status.205.1" title="205 Reset Content">Section&nbsp;9.2.6</a>: Reset Content
800       / "206"  ; <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section&nbsp;9.2.7</a>: Partial Content
801       / "300"  ; <a href="#status.300" id="rfc.xref.status.300.1" title="300 Multiple Choices">Section&nbsp;9.3.1</a>: Multiple Choices
802       / "301"  ; <a href="#status.301" id="rfc.xref.status.301.1" title="301 Moved Permanently">Section&nbsp;9.3.2</a>: Moved Permanently
803       / "302"  ; <a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section&nbsp;9.3.3</a>: Found
804       / "303"  ; <a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section&nbsp;9.3.4</a>: See Other
805       / "304"  ; <a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;9.3.5</a>: Not Modified
806       / "305"  ; <a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section&nbsp;9.3.6</a>: Use Proxy
807       / "307"  ; <a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section&nbsp;9.3.8</a>: Temporary Redirect
808       / "400"  ; <a href="#status.400" id="rfc.xref.status.400.1" title="400 Bad Request">Section&nbsp;9.4.1</a>: Bad Request
809       / "401"  ; <a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;9.4.2</a>: Unauthorized
810       / "402"  ; <a href="#status.402" id="rfc.xref.status.402.1" title="402 Payment Required">Section&nbsp;9.4.3</a>: Payment Required
811       / "403"  ; <a href="#status.403" id="rfc.xref.status.403.1" title="403 Forbidden">Section&nbsp;9.4.4</a>: Forbidden
812       / "404"  ; <a href="#status.404" id="rfc.xref.status.404.1" title="404 Not Found">Section&nbsp;9.4.5</a>: Not Found
813       / "405"  ; <a href="#status.405" id="rfc.xref.status.405.1" title="405 Method Not Allowed">Section&nbsp;9.4.6</a>: Method Not Allowed
814       / "406"  ; <a href="#status.406" id="rfc.xref.status.406.1" title="406 Not Acceptable">Section&nbsp;9.4.7</a>: Not Acceptable
815       / "407"  ; <a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;9.4.8</a>: Proxy Authentication Required
816       / "408"  ; <a href="#status.408" id="rfc.xref.status.408.1" title="408 Request Timeout">Section&nbsp;9.4.9</a>: Request Time-out
817       / "409"  ; <a href="#status.409" id="rfc.xref.status.409.1" title="409 Conflict">Section&nbsp;9.4.10</a>: Conflict
818       / "410"  ; <a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section&nbsp;9.4.11</a>: Gone
819       / "411"  ; <a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section&nbsp;9.4.12</a>: Length Required
820       / "412"  ; <a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;9.4.13</a>: Precondition Failed
821       / "413"  ; <a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Entity Too Large">Section&nbsp;9.4.14</a>: Request Entity Too Large
822       / "414"  ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 Request-URI Too Long">Section&nbsp;9.4.15</a>: Request-URI Too Large
823       / "415"  ; <a href="#status.415" id="rfc.xref.status.415.1" title="415 Unsupported Media Type">Section&nbsp;9.4.16</a>: Unsupported Media Type
824       / "416"  ; <a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section&nbsp;9.4.17</a>: Requested range not satisfiable
825       / "417"  ; <a href="#status.417" id="rfc.xref.status.417.1" title="417 Expectation Failed">Section&nbsp;9.4.18</a>: Expectation Failed
826       / "500"  ; <a href="#status.500" id="rfc.xref.status.500.1" title="500 Internal Server Error">Section&nbsp;9.5.1</a>: Internal Server Error
827       / "501"  ; <a href="#status.501" id="rfc.xref.status.501.1" title="501 Not Implemented">Section&nbsp;9.5.2</a>: Not Implemented
828       / "502"  ; <a href="#status.502" id="rfc.xref.status.502.1" title="502 Bad Gateway">Section&nbsp;9.5.3</a>: Bad Gateway
829       / "503"  ; <a href="#status.503" id="rfc.xref.status.503.1" title="503 Service Unavailable">Section&nbsp;9.5.4</a>: Service Unavailable
830       / "504"  ; <a href="#status.504" id="rfc.xref.status.504.1" title="504 Gateway Timeout">Section&nbsp;9.5.5</a>: Gateway Time-out
831       / "505"  ; <a href="#status.505" id="rfc.xref.status.505.1" title="505 HTTP Version Not Supported">Section&nbsp;9.5.6</a>: HTTP Version not supported
832       / <a href="#request.header.fields" class="smpl">extension-code</a>
833
834  <a href="#request.header.fields" class="smpl">extension-code</a> = 3<a href="#notation" class="smpl">DIGIT</a>
835  <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a>  = *&lt;<a href="#notation" class="smpl">TEXT</a>, excluding <a href="#notation" class="smpl">CR</a>, <a href="#notation" class="smpl">LF</a>&gt;
836</pre><p id="rfc.section.5.p.4">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
837         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
838         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
839         something wrong with its request and treat the response as if it had received a 400 status code. In such cases, user agents <em class="bcp14">SHOULD</em> present to the user the entity returned with the response, since that entity is likely to include human-readable information
840         which will explain the unusual status.
841      </p>
842      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2>
843      <p id="rfc.section.5.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>
844      <p id="rfc.section.5.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>). Any document registering new status codes should be traceable through statuses of either 'Obsoletes' or 'Updates' to this
845         document.
846      </p>
847      <p id="rfc.section.5.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;.
848      </p>
849      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>
850      <p id="rfc.section.6.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the
851         Status-Line. These header fields give information about the server and about further access to the resource identified by
852         the Request-URI.
853      </p>
854      <div id="rfc.figure.u.12"></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.6"><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 6.1</a>
855                  / <a href="#abnf.dependencies" class="smpl">Age</a>                     ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a>
856                  / <a href="#header.allow" class="smpl">Allow</a>                   ; <a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;10.1</a>
857                  / <a href="#abnf.dependencies" class="smpl">ETag</a>                    ; <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a>
858                  / <a href="#header.location" class="smpl">Location</a>                ; <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;10.4</a>
859                  / <a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a>      ; <a href="#Part7" id="rfc.xref.Part7.7"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a>
860                  / <a href="#header.retry-after" class="smpl">Retry-After</a>             ; <a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;10.7</a>
861                  / <a href="#header.server" class="smpl">Server</a>                  ; <a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;10.8</a>
862                  / <a href="#abnf.dependencies" class="smpl">Vary</a>                    ; <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a>
863                  / <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a>        ; <a href="#Part7" id="rfc.xref.Part7.8"><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>
864</pre><p id="rfc.section.6.p.3">Response-header field names can be extended reliably only in combination with a change in the protocol version. However, new
865         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
866         fields. Unrecognized header fields are treated as entity-header fields.
867      </p>
868      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="entity" href="#entity">Entity</a></h1>
869      <p id="rfc.section.7.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer an entity if not otherwise restricted by the request method or response status code. An entity consists of entity-header
870         fields and an entity-body, although some responses will only include the entity-headers. HTTP entity-body and entity-header
871         fields are defined in <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
872      </p>
873      <p id="rfc.section.7.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.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 entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
874         safe and proper transfer of the message.
875      </p>
876      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h1>
877      <p id="rfc.section.8.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
878         to share the same semantics for separately extended clients and servers.
879      </p>
880      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="safe.and.idempotent" href="#safe.and.idempotent">Safe and Idempotent Methods</a></h2>
881      <div id="rfc.iref.s.1"></div>
882      <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
883      <p id="rfc.section.8.1.1.p.1">Implementors should be aware that the software represents the user in their interactions over the Internet, and should be
884         careful to allow the user to be aware of any actions they might take which may have an unexpected significance to themselves
885         or others.
886      </p>
887      <p id="rfc.section.8.1.1.p.2">In particular, the convention has been established that the GET and HEAD methods <em class="bcp14">SHOULD NOT</em> have the significance of taking an action other than retrieval. These methods ought to be considered "<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
888         made aware of the fact that a possibly unsafe action is being requested.
889      </p>
890      <p id="rfc.section.8.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;
891         in fact, some dynamic resources consider that a feature. The important distinction here is that the user did not request the
892         side-effects, so therefore cannot be held accountable for them.
893      </p>
894      <div id="rfc.iref.i.1"></div>
895      <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a id="idempotent.methods" href="#idempotent.methods">Idempotent Methods</a></h3>
896      <p id="rfc.section.8.1.2.p.1">Methods can also have the property of "idempotence" in that (aside from error or expiration issues) the side-effects of N
897         &gt; 0 identical requests is the same as for a single request. The methods GET, HEAD, PUT and DELETE share this property. Also,
898         the methods OPTIONS and TRACE <em class="bcp14">SHOULD NOT</em> have side effects, and so are inherently idempotent.
899      </p>
900      <p id="rfc.section.8.1.2.p.2">However, it is possible that a sequence of several requests is non-idempotent, even if all of the methods executed in that
901         sequence are idempotent. (A sequence is idempotent if a single execution of the entire sequence always yields a result that
902         is not changed by a reexecution of all, or part, of that sequence.) For example, a sequence is non-idempotent if its result
903         depends on a value that is later modified in the same sequence.
904      </p>
905      <p id="rfc.section.8.1.2.p.3">A sequence that never has side effects is idempotent, by definition (provided that no concurrent operations are being executed
906         on the same set of resources).
907      </p>
908      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="OPTIONS" href="#OPTIONS">OPTIONS</a></h2>
909      <div id="rfc.iref.o.1"></div>
910      <div id="rfc.iref.m.1"></div>
911      <p id="rfc.section.8.2.p.1">The OPTIONS method represents a request for information about the communication options available on the request/response
912         chain identified by the Request-URI. This method allows the client to determine the options and/or requirements associated
913         with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
914      </p>
915      <p id="rfc.section.8.2.p.2">Responses to this method are not cacheable.</p>
916      <p id="rfc.section.8.2.p.3">If the OPTIONS request includes an entity-body (as indicated by the presence of Content-Length or Transfer-Encoding), then
917         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
918         to HTTP might use the OPTIONS body to make more detailed queries on the server.
919      </p>
920      <p id="rfc.section.8.2.p.4">If the Request-URI is an asterisk ("*"), the OPTIONS request is intended to apply to the server in general rather than to
921         a specific resource. Since a server's communication options typically depend on the resource, the "*" request is only useful
922         as a "ping" or "no-op" type of method; it does nothing beyond allowing the client to test the capabilities of the server.
923         For example, this can be used to test a proxy for HTTP/1.1 compliance (or lack thereof).
924      </p>
925      <p id="rfc.section.8.2.p.5">If the Request-URI is not an asterisk, the OPTIONS request applies only to the options that are available when communicating
926         with that resource.
927      </p>
928      <p id="rfc.section.8.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.,
929         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,
930         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".
931      </p>
932      <p id="rfc.section.8.2.p.7">The Max-Forwards request-header field <em class="bcp14">MAY</em> be used to target a specific proxy in the request chain. When a proxy receives an OPTIONS request on an absolute-URI for which
933         request forwarding is permitted, the proxy <em class="bcp14">MUST</em> check for a Max-Forwards field. If the Max-Forwards field-value is zero ("0"), the proxy <em class="bcp14">MUST NOT</em> forward the message; instead, the proxy <em class="bcp14">SHOULD</em> respond with its own communication options. If the Max-Forwards field-value is an integer greater than zero, the proxy <em class="bcp14">MUST</em> decrement the field-value when it forwards the request. If no Max-Forwards field is present in the request, then the forwarded
934         request <em class="bcp14">MUST NOT</em> include a Max-Forwards field.
935      </p>
936      <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="GET" href="#GET">GET</a></h2>
937      <div id="rfc.iref.g.8"></div>
938      <div id="rfc.iref.m.2"></div>
939      <p id="rfc.section.8.3.p.1">The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI. If the Request-URI
940         refers to a data-producing process, it is the produced data which shall be returned as the entity in the response and not
941         the source text of the process, unless that text happens to be the output of the process.
942      </p>
943      <p id="rfc.section.8.3.p.2">The semantics of the GET method change to a "conditional GET" if the request message includes an If-Modified-Since, If-Unmodified-Since,
944         If-Match, If-None-Match, or If-Range header field. A conditional GET method requests that the entity be transferred only under
945         the circumstances described by the conditional header field(s). The conditional GET method is intended to reduce unnecessary
946         network usage by allowing cached entities to be refreshed without requiring multiple requests or transferring data already
947         held by the client.
948      </p>
949      <p id="rfc.section.8.3.p.3">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial
950         GET requests that only part of the entity be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed
951         without transferring data already held by the client.
952      </p>
953      <p id="rfc.section.8.3.p.4">The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching described in <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
954      </p>
955      <p id="rfc.section.8.3.p.5">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;12.2</a> for security considerations when used for forms.
956      </p>
957      <h2 id="rfc.section.8.4"><a href="#rfc.section.8.4">8.4</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h2>
958      <div id="rfc.iref.h.1"></div>
959      <div id="rfc.iref.m.3"></div>
960      <p id="rfc.section.8.4.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> return a message-body in the response. The metainformation contained in the HTTP headers in response to a HEAD request <em class="bcp14">SHOULD</em> be identical to the information sent in response to a GET request. This method can be used for obtaining metainformation about
961         the entity implied by the request without transferring the entity-body itself. This method is often used for testing hypertext
962         links for validity, accessibility, and recent modification.
963      </p>
964      <p id="rfc.section.8.4.p.2">The response to a HEAD request <em class="bcp14">MAY</em> be cacheable in the sense that the information contained in the response <em class="bcp14">MAY</em> be used to update a previously cached entity from that resource. If the new field values indicate that the cached entity differs
965         from the current entity (as would be indicated by a change in Content-Length, Content-MD5, ETag or Last-Modified), then the
966         cache <em class="bcp14">MUST</em> treat the cache entry as stale.
967      </p>
968      <div id="rfc.iref.p.1"></div>
969      <div id="rfc.iref.m.4"></div>
970      <h2 id="rfc.section.8.5"><a href="#rfc.section.8.5">8.5</a>&nbsp;<a id="POST" href="#POST">POST</a></h2>
971      <p id="rfc.section.8.5.p.1">The POST method is used to request that the origin server accept the entity enclosed in the request as data to be processed
972         by the resource identified by the Request-URI in the Request-Line. POST is designed to allow a uniform method to cover the
973         following functions:
974      </p>
975      <ul>
976         <li>Annotation of existing resources;</li>
977         <li>Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;</li>
978         <li>Providing a block of data, such as the result of submitting a form, to a data-handling process;</li>
979         <li>Extending a database through an append operation.</li>
980      </ul>
981      <p id="rfc.section.8.5.p.2">The actual function performed by the POST method is determined by the server and is usually dependent on the Request-URI.</p>
982      <p id="rfc.section.8.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
983         200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity
984         that describes the result.
985      </p>
986      <p id="rfc.section.8.5.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be 201 (Created) and contain an entity which describes the status of the request and refers to the new resource, and a Location
987         header (see <a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section&nbsp;10.4</a>).
988      </p>
989      <p id="rfc.section.8.5.p.5">Responses to this method are not cacheable, unless the response includes appropriate Cache-Control or Expires header fields.
990         However, the 303 (See Other) response can be used to direct the user agent to retrieve a cacheable resource.
991      </p>
992      <div id="rfc.iref.p.2"></div>
993      <div id="rfc.iref.m.5"></div>
994      <h2 id="rfc.section.8.6"><a href="#rfc.section.8.6">8.6</a>&nbsp;<a id="PUT" href="#PUT">PUT</a></h2>
995      <p id="rfc.section.8.6.p.1">The PUT method requests that the enclosed entity be stored at the supplied Request-URI. If the Request-URI refers to an already
996         existing resource, the enclosed entity <em class="bcp14">SHOULD</em> be considered as a modified version of the one residing on the origin server. If the Request-URI does not point to an existing
997         resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create
998         the resource with that URI. If a new resource is created at the 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
999         Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request. If the resource could not be created or modified with the Request-URI,
1000         an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* headers (headers starting with the prefix 'Content-') that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
1001      </p>
1002      <p id="rfc.section.8.6.p.2">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
1003      </p>
1004      <p id="rfc.section.8.6.p.3">The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The
1005         URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting
1006         process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request
1007         identifies the entity enclosed with the request -- the user agent knows what URI is intended and the server <em class="bcp14">MUST NOT</em> attempt to apply the request to some other resource. If the server desires that the request be applied to a different URI,
1008         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.
1009      </p>
1010      <p id="rfc.section.8.6.p.4">A single resource <em class="bcp14">MAY</em> be identified by many different URIs. For example, an article might have a URI for identifying "the current version" which
1011         is separate from the URI identifying each particular version. In this case, a PUT request on a general URI might result in
1012         several other URIs being defined by the origin server.
1013      </p>
1014      <p id="rfc.section.8.6.p.5">HTTP/1.1 does not define how a PUT method affects the state of an origin server.</p>
1015      <p id="rfc.section.8.6.p.6">Unless otherwise specified for a particular entity-header, the entity-headers in the PUT request <em class="bcp14">SHOULD</em> be applied to the resource created or modified by the PUT.
1016      </p>
1017      <div id="rfc.iref.d.1"></div>
1018      <div id="rfc.iref.m.6"></div>
1019      <h2 id="rfc.section.8.7"><a href="#rfc.section.8.7">8.7</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h2>
1020      <p id="rfc.section.8.7.p.1">The DELETE method requests that the origin server delete the resource identified by the Request-URI. This method <em class="bcp14">MAY</em> be overridden by human intervention (or other means) on the origin server. The client cannot be guaranteed that the operation
1021         has been carried out, even if the status code returned from the origin server indicates that the action has been completed
1022         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
1023         location.
1024      </p>
1025      <p id="rfc.section.8.7.p.2">A successful response <em class="bcp14">SHOULD</em> be 200 (OK) if the response includes an entity describing the status, 202 (Accepted) if the action has not yet been enacted,
1026         or 204 (No Content) if the action has been enacted but the response does not include an entity.
1027      </p>
1028      <p id="rfc.section.8.7.p.3">If the request passes through a cache and the Request-URI identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
1029      </p>
1030      <h2 id="rfc.section.8.8"><a href="#rfc.section.8.8">8.8</a>&nbsp;<a id="TRACE" href="#TRACE">TRACE</a></h2>
1031      <div id="rfc.iref.t.1"></div>
1032      <div id="rfc.iref.m.7"></div>
1033      <p id="rfc.section.8.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
1034         request <em class="bcp14">SHOULD</em> reflect the message received back to the client as the entity-body of a 200 (OK) response. The final recipient is either the
1035         origin server or the first proxy or gateway to receive a Max-Forwards value of zero (0) in the request (see <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.2" title="Max-Forwards">Section&nbsp;10.5</a>). A TRACE request <em class="bcp14">MUST NOT</em> include an entity.
1036      </p>
1037      <p id="rfc.section.8.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
1038         or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 8.9</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>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the
1039         client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an
1040         infinite loop.
1041      </p>
1042      <p id="rfc.section.8.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> contain the entire request message in the entity-body, with a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 9.3.1</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>). Responses to this method <em class="bcp14">MUST NOT</em> be cached.
1043      </p>
1044      <div id="rfc.iref.c.1"></div>
1045      <div id="rfc.iref.m.8"></div>
1046      <h2 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h2>
1047      <p id="rfc.section.8.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.
1048         SSL tunneling <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>).
1049      </p>
1050      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="status.codes" href="#status.codes">Status Code Definitions</a></h1>
1051      <p id="rfc.section.9.p.1">Each Status-Code is described below, including a description of which method(s) it can follow and any metainformation required
1052         in the response.
1053      </p>
1054      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2>
1055      <p id="rfc.section.9.1.p.1">This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is
1056         terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any
1057         1xx status codes, servers <em class="bcp14">MUST NOT</em> send a 1xx response to an HTTP/1.0 client except under experimental conditions.
1058      </p>
1059      <p id="rfc.section.9.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
1060         (Continue) status message. Unexpected 1xx status responses <em class="bcp14">MAY</em> be ignored by a user agent.
1061      </p>
1062      <p id="rfc.section.9.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
1063         requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards
1064         a request, then it need not forward the corresponding 100 (Continue) response(s).)
1065      </p>
1066      <div id="rfc.iref.25"></div>
1067      <div id="rfc.iref.s.2"></div>
1068      <h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
1069      <p id="rfc.section.9.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
1070         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
1071         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.25"><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.
1072      </p>
1073      <div id="rfc.iref.26"></div>
1074      <div id="rfc.iref.s.3"></div>
1075      <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
1076      <p id="rfc.section.9.1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined
1077         by the response's Upgrade header field immediately after the empty line which terminates the 101 response.
1078      </p>
1079      <p id="rfc.section.9.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
1080         older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use
1081         such features.
1082      </p>
1083      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
1084      <p id="rfc.section.9.2.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
1085      <div id="rfc.iref.27"></div>
1086      <div id="rfc.iref.s.4"></div>
1087      <h3 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
1088      <p id="rfc.section.9.2.1.p.1">The request has succeeded. The information returned with the response is dependent on the method used in the request, for
1089         example:
1090      </p>
1091      <dl>
1092         <dt>GET</dt>
1093         <dd>an entity corresponding to the requested resource is sent in the response;</dd>
1094         <dt>HEAD</dt>
1095         <dd>the entity-header fields corresponding to the requested resource are sent in the response without any message-body;</dd>
1096         <dt>POST</dt>
1097         <dd>an entity describing or containing the result of the action;</dd>
1098         <dt>TRACE</dt>
1099         <dd>an entity containing the request message as received by the end server.</dd>
1100      </dl>
1101      <div id="rfc.iref.28"></div>
1102      <div id="rfc.iref.s.5"></div>
1103      <h3 id="rfc.section.9.2.2"><a href="#rfc.section.9.2.2">9.2.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
1104      <p id="rfc.section.9.2.2.p.1">The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced
1105         by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header
1106         field. The response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose
1107         the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin
1108         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.
1109      </p>
1110      <p id="rfc.section.9.2.2.p.2">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity tag for the requested variant just created,
1111         see <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a> of <a href="#Part4" id="rfc.xref.Part4.11"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
1112      </p>
1113      <div id="rfc.iref.29"></div>
1114      <div id="rfc.iref.s.6"></div>
1115      <h3 id="rfc.section.9.2.3"><a href="#rfc.section.9.2.3">9.2.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
1116      <p id="rfc.section.9.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
1117         be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status
1118         code from an asynchronous operation such as this.
1119      </p>
1120      <p id="rfc.section.9.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
1121         (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the
1122         server persist until the process is completed. The entity returned with this response <em class="bcp14">SHOULD</em> include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the
1123         user can expect the request to be fulfilled.
1124      </p>
1125      <div id="rfc.iref.30"></div>
1126      <div id="rfc.iref.s.7"></div>
1127      <h3 id="rfc.section.9.2.4"><a href="#rfc.section.9.2.4">9.2.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
1128      <p id="rfc.section.9.2.4.p.1">The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered
1129         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
1130         result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only
1131         appropriate when the response would otherwise be 200 (OK).
1132      </p>
1133      <div id="rfc.iref.31"></div>
1134      <div id="rfc.iref.s.8"></div>
1135      <h3 id="rfc.section.9.2.5"><a href="#rfc.section.9.2.5">9.2.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
1136      <p id="rfc.section.9.2.5.p.1">The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation.
1137         The response <em class="bcp14">MAY</em> include new or updated metainformation in the form of entity-headers, which if present <em class="bcp14">SHOULD</em> be associated with the requested variant.
1138      </p>
1139      <p id="rfc.section.9.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
1140         for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation <em class="bcp14">SHOULD</em> be applied to the document currently in the user agent's active view.
1141      </p>
1142      <p id="rfc.section.9.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.
1143      </p>
1144      <div id="rfc.iref.32"></div>
1145      <div id="rfc.iref.s.9"></div>
1146      <h3 id="rfc.section.9.2.6"><a href="#rfc.section.9.2.6">9.2.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
1147      <p id="rfc.section.9.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
1148         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
1149         another input action. The response <em class="bcp14">MUST NOT</em> include an entity.
1150      </p>
1151      <div id="rfc.iref.33"></div>
1152      <div id="rfc.iref.s.10"></div>
1153      <h3 id="rfc.section.9.2.7"><a href="#rfc.section.9.2.7">9.2.7</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h3>
1154      <p id="rfc.section.9.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed entity is a partial representation as defined
1155         in <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
1156      </p>
1157      <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2>
1158      <p id="rfc.section.9.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.
1159         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
1160         GET or HEAD. A client <em class="bcp14">SHOULD</em> detect infinite redirection loops, since such loops generate network traffic for each redirection.
1161      </p>
1162      <dl class="empty">
1163         <dd> <b>Note:</b> previous versions of this specification recommended a maximum of five redirections. Content developers should be aware that
1164            there might be clients that implement such a fixed limitation.
1165         </dd>
1166      </dl>
1167      <div id="rfc.iref.34"></div>
1168      <div id="rfc.iref.s.11"></div>
1169      <h3 id="rfc.section.9.3.1"><a href="#rfc.section.9.3.1">9.3.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
1170      <p id="rfc.section.9.3.1.p.1">The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven
1171         negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that
1172         location.
1173      </p>
1174      <p id="rfc.section.9.3.1.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose
1175         the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending
1176         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.
1177      </p>
1178      <p id="rfc.section.9.3.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the Location field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.
1179      </p>
1180      <div id="rfc.iref.35"></div>
1181      <div id="rfc.iref.s.12"></div>
1182      <h3 id="rfc.section.9.3.2"><a href="#rfc.section.9.3.2">9.3.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
1183      <p id="rfc.section.9.3.2.p.1">The requested resource has been assigned a new permanent URI and any future references to this resource <em class="bcp14">SHOULD</em> use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI
1184         to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
1185      </p>
1186      <p id="rfc.section.9.3.2.p.2">The new permanent URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
1187      </p>
1188      <p id="rfc.section.9.3.2.p.3">If the 301 status code is received in response to a request method that is known to be "safe", as defined in <a href="#safe.methods" title="Safe Methods">Section&nbsp;8.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
1189         the request was issued.
1190      </p>
1191      <dl class="empty">
1192         <dd> <b>Note:</b> When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously
1193            change it into a GET request.
1194         </dd>
1195      </dl>
1196      <div id="rfc.iref.36"></div>
1197      <div id="rfc.iref.s.13"></div>
1198      <h3 id="rfc.section.9.3.3"><a href="#rfc.section.9.3.3">9.3.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
1199      <p id="rfc.section.9.3.3.p.1">The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the
1200         client <em class="bcp14">SHOULD</em> continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires
1201         header field.
1202      </p>
1203      <p id="rfc.section.9.3.3.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s).
1204      </p>
1205      <p id="rfc.section.9.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;8.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
1206         the request was issued.
1207      </p>
1208      <dl class="empty">
1209         <dd> <b>Note:</b>  <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> specify that the client is not allowed to change the method on the redirected request. However, most existing user agent implementations
1210            treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original request method.
1211            The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected
1212            of the client.
1213         </dd>
1214      </dl>
1215      <div id="rfc.iref.37"></div>
1216      <div id="rfc.iref.s.14"></div>
1217      <h3 id="rfc.section.9.3.4"><a href="#rfc.section.9.3.4">9.3.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
1218      <p id="rfc.section.9.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
1219         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,
1220         be redirected again, or end with an error status. The Location URI is not a substitute reference for the originally requested
1221         resource.
1222      </p>
1223      <p id="rfc.section.9.3.4.p.2">The 303 status is generally applicable to any HTTP method. It is primarily used to allow the output of a POST action to redirect
1224         the user agent to a selected resource, since doing so provides the information corresponding to the POST response in a form
1225         that can be separately identified, bookmarked, and cached independent of the original request.
1226      </p>
1227      <p id="rfc.section.9.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
1228         transferred by the server over HTTP. The Location URI indicates a resource that is descriptive of the requested resource such
1229         that the follow-on representation may be useful without implying that it adequately represents the previously requested resource.
1230         Note that answers to the questions of what can be represented, what representations are adequate, and what might be a useful
1231         description are outside the scope of HTTP and thus entirely determined by the resource owner(s).
1232      </p>
1233      <p id="rfc.section.9.3.4.p.4">A 303 response <em class="bcp14">SHOULD NOT</em> be cached unless it is indicated as cacheable by Cache-Control or Expires header fields. Except for responses to a HEAD request,
1234         the entity of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
1235      </p>
1236      <div id="rfc.iref.38"></div>
1237      <div id="rfc.iref.s.15"></div>
1238      <h3 id="rfc.section.9.3.5"><a href="#rfc.section.9.3.5">9.3.5</a>&nbsp;<a id="status.304" href="#status.304">304 Not Modified</a></h3>
1239      <p id="rfc.section.9.3.5.p.1">The response to the request has not been modified since the conditions indicated by the client's conditional GET request,
1240         as defined in <a href="#Part4" id="rfc.xref.Part4.12"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
1241      </p>
1242      <div id="rfc.iref.39"></div>
1243      <div id="rfc.iref.s.16"></div>
1244      <h3 id="rfc.section.9.3.6"><a href="#rfc.section.9.3.6">9.3.6</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
1245      <p id="rfc.section.9.3.6.p.1">The 305 status was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;A.2</a>), and is now deprecated.
1246      </p>
1247      <div id="rfc.iref.40"></div>
1248      <div id="rfc.iref.s.17"></div>
1249      <h3 id="rfc.section.9.3.7"><a href="#rfc.section.9.3.7">9.3.7</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
1250      <p id="rfc.section.9.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>
1251      <div id="rfc.iref.41"></div>
1252      <div id="rfc.iref.s.18"></div>
1253      <h3 id="rfc.section.9.3.8"><a href="#rfc.section.9.3.8">9.3.8</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
1254      <p id="rfc.section.9.3.8.p.1">The requested resource resides temporarily under a different URI. Since the redirection <em class="bcp14">MAY</em> be altered on occasion, the client <em class="bcp14">SHOULD</em> continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires
1255         header field.
1256      </p>
1257      <p id="rfc.section.9.3.8.p.2">The temporary URI <em class="bcp14">SHOULD</em> be given by the Location field in the response. Unless the request method was HEAD, the entity of the response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand
1258         the 307 status. Therefore, the note <em class="bcp14">SHOULD</em> contain the information necessary for a user to repeat the original request on the new URI.
1259      </p>
1260      <p id="rfc.section.9.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;8.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
1261         the request was issued.
1262      </p>
1263      <h2 id="rfc.section.9.4"><a href="#rfc.section.9.4">9.4</a>&nbsp;<a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2>
1264      <p id="rfc.section.9.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
1265         request, the server <em class="bcp14">SHOULD</em> include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
1266         These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included entity to the user.
1267      </p>
1268      <p id="rfc.section.9.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
1269         the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send
1270         a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted
1271         by the HTTP application.
1272      </p>
1273      <div id="rfc.iref.42"></div>
1274      <div id="rfc.iref.s.19"></div>
1275      <h3 id="rfc.section.9.4.1"><a href="#rfc.section.9.4.1">9.4.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
1276      <p id="rfc.section.9.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.
1277      </p>
1278      <div id="rfc.iref.43"></div>
1279      <div id="rfc.iref.s.20"></div>
1280      <h3 id="rfc.section.9.4.2"><a href="#rfc.section.9.4.2">9.4.2</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h3>
1281      <p id="rfc.section.9.4.2.p.1">The request requires user authentication (see <a href="#Part7" id="rfc.xref.Part7.9"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
1282      </p>
1283      <div id="rfc.iref.44"></div>
1284      <div id="rfc.iref.s.21"></div>
1285      <h3 id="rfc.section.9.4.3"><a href="#rfc.section.9.4.3">9.4.3</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
1286      <p id="rfc.section.9.4.3.p.1">This code is reserved for future use.</p>
1287      <div id="rfc.iref.45"></div>
1288      <div id="rfc.iref.s.22"></div>
1289      <h3 id="rfc.section.9.4.4"><a href="#rfc.section.9.4.4">9.4.4</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
1290      <p id="rfc.section.9.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,
1291         it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client,
1292         the status code 404 (Not Found) can be used instead.
1293      </p>
1294      <div id="rfc.iref.46"></div>
1295      <div id="rfc.iref.s.23"></div>
1296      <h3 id="rfc.section.9.4.5"><a href="#rfc.section.9.4.5">9.4.5</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
1297      <p id="rfc.section.9.4.5.p.1">The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or
1298         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
1299         and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request
1300         has been refused, or when no other response is applicable.
1301      </p>
1302      <div id="rfc.iref.47"></div>
1303      <div id="rfc.iref.s.24"></div>
1304      <h3 id="rfc.section.9.4.6"><a href="#rfc.section.9.4.6">9.4.6</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
1305      <p id="rfc.section.9.4.6.p.1">The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response <em class="bcp14">MUST</em> include an Allow header containing a list of valid methods for the requested resource.
1306      </p>
1307      <div id="rfc.iref.48"></div>
1308      <div id="rfc.iref.s.25"></div>
1309      <h3 id="rfc.section.9.4.7"><a href="#rfc.section.9.4.7">9.4.7</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
1310      <p id="rfc.section.9.4.7.p.1">The resource identified by the request is only capable of generating response entities which have content characteristics
1311         not acceptable according to the accept headers sent in the request.
1312      </p>
1313      <p id="rfc.section.9.4.7.p.2">Unless it was a HEAD request, the response <em class="bcp14">SHOULD</em> include an entity containing a list of available entity characteristics and location(s) from which the user or user agent
1314         can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field.
1315         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.
1316      </p>
1317      <dl class="empty">
1318         <dd> <b>Note:</b> HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept headers sent in the request.
1319            In some cases, this may even be preferable to sending a 406 response. User agents are encouraged to inspect the headers of
1320            an incoming response to determine if it is acceptable.
1321         </dd>
1322      </dl>
1323      <p id="rfc.section.9.4.7.p.3">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.
1324      </p>
1325      <div id="rfc.iref.49"></div>
1326      <div id="rfc.iref.s.26"></div>
1327      <h3 id="rfc.section.9.4.8"><a href="#rfc.section.9.4.8">9.4.8</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h3>
1328      <p id="rfc.section.9.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="#Part7" id="rfc.xref.Part7.10"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
1329      </p>
1330      <div id="rfc.iref.50"></div>
1331      <div id="rfc.iref.s.27"></div>
1332      <h3 id="rfc.section.9.4.9"><a href="#rfc.section.9.4.9">9.4.9</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
1333      <p id="rfc.section.9.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.
1334      </p>
1335      <div id="rfc.iref.51"></div>
1336      <div id="rfc.iref.s.28"></div>
1337      <h3 id="rfc.section.9.4.10"><a href="#rfc.section.9.4.10">9.4.10</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
1338      <p id="rfc.section.9.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
1339         situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response
1340         body <em class="bcp14">SHOULD</em> include enough information for the user to recognize the source of the conflict. Ideally, the response entity would include
1341         enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.
1342      </p>
1343      <p id="rfc.section.9.4.10.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity
1344         being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might
1345         use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain
1346         a list of the differences between the two versions in a format defined by the response Content-Type.
1347      </p>
1348      <div id="rfc.iref.52"></div>
1349      <div id="rfc.iref.s.29"></div>
1350      <h3 id="rfc.section.9.4.11"><a href="#rfc.section.9.4.11">9.4.11</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
1351      <p id="rfc.section.9.4.11.p.1">The requested resource is no longer available at the server and no forwarding address is known. This condition is expected
1352         to be considered permanent. Clients with link editing capabilities <em class="bcp14">SHOULD</em> delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether
1353         or not the condition is permanent, the status code 404 (Not Found) <em class="bcp14">SHOULD</em> be used instead. This response is cacheable unless indicated otherwise.
1354      </p>
1355      <p id="rfc.section.9.4.11.p.2">The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource
1356         is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event
1357         is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's
1358         site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time
1359         -- that is left to the discretion of the server owner.
1360      </p>
1361      <div id="rfc.iref.53"></div>
1362      <div id="rfc.iref.s.30"></div>
1363      <h3 id="rfc.section.9.4.12"><a href="#rfc.section.9.4.12">9.4.12</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
1364      <p id="rfc.section.9.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
1365         message.
1366      </p>
1367      <div id="rfc.iref.54"></div>
1368      <div id="rfc.iref.s.31"></div>
1369      <h3 id="rfc.section.9.4.13"><a href="#rfc.section.9.4.13">9.4.13</a>&nbsp;<a id="status.412" href="#status.412">412 Precondition Failed</a></h3>
1370      <p id="rfc.section.9.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
1371         defined in <a href="#Part4" id="rfc.xref.Part4.13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
1372      </p>
1373      <div id="rfc.iref.55"></div>
1374      <div id="rfc.iref.s.32"></div>
1375      <h3 id="rfc.section.9.4.14"><a href="#rfc.section.9.4.14">9.4.14</a>&nbsp;<a id="status.413" href="#status.413">413 Request Entity Too Large</a></h3>
1376      <p id="rfc.section.9.4.14.p.1">The server is refusing to process a request because the request entity is larger than the server is willing or able to process.
1377         The server <em class="bcp14">MAY</em> close the connection to prevent the client from continuing the request.
1378      </p>
1379      <p id="rfc.section.9.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.
1380      </p>
1381      <div id="rfc.iref.56"></div>
1382      <div id="rfc.iref.s.33"></div>
1383      <h3 id="rfc.section.9.4.15"><a href="#rfc.section.9.4.15">9.4.15</a>&nbsp;<a id="status.414" href="#status.414">414 Request-URI Too Long</a></h3>
1384      <p id="rfc.section.9.4.15.p.1">The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This
1385         rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query
1386         information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points
1387         to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some
1388         servers using fixed-length buffers for reading or manipulating the Request-URI.
1389      </p>
1390      <div id="rfc.iref.57"></div>
1391      <div id="rfc.iref.s.34"></div>
1392      <h3 id="rfc.section.9.4.16"><a href="#rfc.section.9.4.16">9.4.16</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
1393      <p id="rfc.section.9.4.16.p.1">The server is refusing to service the request because the entity of the request is in a format not supported by the requested
1394         resource for the requested method.
1395      </p>
1396      <div id="rfc.iref.58"></div>
1397      <div id="rfc.iref.s.35"></div>
1398      <h3 id="rfc.section.9.4.17"><a href="#rfc.section.9.4.17">9.4.17</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3>
1399      <p id="rfc.section.9.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 6.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>) and none of the range-specifier values in this field overlap the current extent of the selected resource.
1400      </p>
1401      <div id="rfc.iref.59"></div>
1402      <div id="rfc.iref.s.36"></div>
1403      <h3 id="rfc.section.9.4.18"><a href="#rfc.section.9.4.18">9.4.18</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
1404      <p id="rfc.section.9.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;10.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
1405         not be met by the next-hop server.
1406      </p>
1407      <h2 id="rfc.section.9.5"><a href="#rfc.section.9.5">9.5</a>&nbsp;<a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2>
1408      <p id="rfc.section.9.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
1409         of performing the request. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition.
1410         User agents <em class="bcp14">SHOULD</em> display any included entity to the user. These response codes are applicable to any request method.
1411      </p>
1412      <div id="rfc.iref.60"></div>
1413      <div id="rfc.iref.s.37"></div>
1414      <h3 id="rfc.section.9.5.1"><a href="#rfc.section.9.5.1">9.5.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
1415      <p id="rfc.section.9.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
1416      <div id="rfc.iref.61"></div>
1417      <div id="rfc.iref.s.38"></div>
1418      <h3 id="rfc.section.9.5.2"><a href="#rfc.section.9.5.2">9.5.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
1419      <p id="rfc.section.9.5.2.p.1">The server does not support the functionality required to fulfill the request. This is the appropriate response when the server
1420         does not recognize the request method and is not capable of supporting it for any resource.
1421      </p>
1422      <div id="rfc.iref.62"></div>
1423      <div id="rfc.iref.s.39"></div>
1424      <h3 id="rfc.section.9.5.3"><a href="#rfc.section.9.5.3">9.5.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
1425      <p id="rfc.section.9.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
1426         to fulfill the request.
1427      </p>
1428      <div id="rfc.iref.63"></div>
1429      <div id="rfc.iref.s.40"></div>
1430      <h3 id="rfc.section.9.5.4"><a href="#rfc.section.9.5.4">9.5.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
1431      <p id="rfc.section.9.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
1432         is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay <em class="bcp14">MAY</em> be indicated in a Retry-After header. If no Retry-After is given, the client <em class="bcp14">SHOULD</em> handle the response as it would for a 500 response.
1433      </p>
1434      <dl class="empty">
1435         <dd> <b>Note:</b> The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish
1436            to simply refuse the connection.
1437         </dd>
1438      </dl>
1439      <div id="rfc.iref.64"></div>
1440      <div id="rfc.iref.s.41"></div>
1441      <h3 id="rfc.section.9.5.5"><a href="#rfc.section.9.5.5">9.5.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
1442      <p id="rfc.section.9.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
1443         URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
1444      </p>
1445      <dl class="empty">
1446         <dd> <b>Note:</b> Note to implementors: some deployed proxies are known to return 400 or 500 when DNS lookups time out.
1447         </dd>
1448      </dl>
1449      <div id="rfc.iref.65"></div>
1450      <div id="rfc.iref.s.42"></div>
1451      <h3 id="rfc.section.9.5.6"><a href="#rfc.section.9.5.6">9.5.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
1452      <p id="rfc.section.9.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
1453         is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described
1454         in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</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>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server.
1455      </p>
1456      <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
1457      <p id="rfc.section.10.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to request and response semantics.</p>
1458      <p id="rfc.section.10.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
1459         receives the entity.
1460      </p>
1461      <div id="rfc.iref.a.1"></div>
1462      <div id="rfc.iref.h.2"></div>
1463      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2>
1464      <p id="rfc.section.10.1.p.1">The response-header field "Allow" lists the set of methods advertised as supported by the resource identified by the Request-URI.
1465         The purpose of this field is strictly to inform the recipient of valid methods associated with the resource. An Allow header
1466         field <em class="bcp14">MUST</em> be present in a 405 (Method Not Allowed) response.
1467      </p>
1468      <div id="rfc.figure.u.13"></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="#notation" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a>
1469  <a href="#header.allow" class="smpl">Allow-v</a> = #<a href="#method" class="smpl">Method</a>
1470</pre><p id="rfc.section.10.1.p.3">Example of use:</p>
1471      <div id="rfc.figure.u.14"></div><pre class="text">  Allow: GET, HEAD, PUT
1472</pre><p id="rfc.section.10.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
1473      <p id="rfc.section.10.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
1474         means of communicating with the origin server.
1475      </p>
1476      <div id="rfc.iref.e.1"></div>
1477      <div id="rfc.iref.h.3"></div>
1478      <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
1479      <p id="rfc.section.10.2.p.1">The request-header field "Expect" is used to indicate that particular server behaviors are required by the client.</p>
1480      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.expect" class="smpl">Expect</a>       = "Expect" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a>
1481  <a href="#header.expect" class="smpl">Expect-v</a>     = 1#<a href="#header.expect" class="smpl">expectation</a>
1482 
1483  <a href="#header.expect" class="smpl">expectation</a>  = "100-continue" / <a href="#header.expect" class="smpl">expectation-extension</a>
1484  <a href="#header.expect" class="smpl">expectation-extension</a> = <a href="#notation" class="smpl">token</a> [ "=" ( <a href="#notation" class="smpl">token</a> / <a href="#notation" class="smpl">quoted-string</a> )
1485                           *<a href="#header.expect" class="smpl">expect-params</a> ]
1486  <a href="#header.expect" class="smpl">expect-params</a> = ";" <a href="#notation" class="smpl">token</a> [ "=" ( <a href="#notation" class="smpl">token</a> / <a href="#notation" class="smpl">quoted-string</a> ) ]
1487</pre><p id="rfc.section.10.2.p.3">A server that does not understand or is unable to comply with any of the expectation values in the Expect field of a request <em class="bcp14">MUST</em> respond with appropriate error status. The server <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status if any of the expectations cannot be met or, if there are other problems with
1488         the request, some other 4xx status.
1489      </p>
1490      <p id="rfc.section.10.2.p.4">This header field is defined with extensible syntax to allow for future extensions. If a server receives a request containing
1491         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.
1492      </p>
1493      <p id="rfc.section.10.2.p.5">Comparison of expectation values is case-insensitive for unquoted tokens (including the 100-continue token), and is case-sensitive
1494         for quoted-string expectation-extensions.
1495      </p>
1496      <p id="rfc.section.10.2.p.6">The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy <em class="bcp14">MUST</em> return a 417 (Expectation Failed) status if it receives a request with an expectation that it cannot meet. However, the Expect
1497         request-header itself is end-to-end; it <em class="bcp14">MUST</em> be forwarded if the request is forwarded.
1498      </p>
1499      <p id="rfc.section.10.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header.</p>
1500      <p id="rfc.section.10.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.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.
1501      </p>
1502      <div id="rfc.iref.f.1"></div>
1503      <div id="rfc.iref.h.4"></div>
1504      <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a>&nbsp;<a id="header.from" href="#header.from">From</a></h2>
1505      <p id="rfc.section.10.3.p.1">The request-header field "From", 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>:
1506      </p>
1507      <div id="rfc.figure.u.16"></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="#notation" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a>
1508  <a href="#header.from" class="smpl">From-v</a>  = <a href="#header.from" class="smpl">mailbox</a>
1509 
1510  <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;
1511</pre><p id="rfc.section.10.3.p.3">An example is:</p>
1512      <div id="rfc.figure.u.17"></div><pre class="text">  From: webmaster@example.org
1513</pre><p id="rfc.section.10.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
1514         on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header so that the person responsible for running the robot can be contacted if problems occur on the receiving
1515         end.
1516      </p>
1517      <p id="rfc.section.10.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
1518         issuer's address <em class="bcp14">SHOULD</em> be used.
1519      </p>
1520      <p id="rfc.section.10.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
1521         security policy. It is strongly recommended that the user be able to disable, enable, and modify the value of this field at
1522         any time prior to a request.
1523      </p>
1524      <div id="rfc.iref.l.1"></div>
1525      <div id="rfc.iref.h.5"></div>
1526      <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a>&nbsp;<a id="header.location" href="#header.location">Location</a></h2>
1527      <p id="rfc.section.10.4.p.1">The response-header field "Location" is used for the identification of a new resource or to redirect the recipient to a location
1528         other than the Request-URI for completion of the request. For 201 (Created) responses, the Location is that of the new resource
1529         which was created by the request. For 3xx responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource. The field value consists of a single absolute
1530         URI.
1531      </p>
1532      <div id="rfc.figure.u.18"></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="#notation" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a>
1533  <a href="#header.location" class="smpl">Location-v</a>     = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> [ "#" <a href="#abnf.dependencies" class="smpl">fragment</a> ]
1534</pre><p id="rfc.section.10.4.p.3">An example is:</p>
1535      <div id="rfc.figure.u.19"></div><pre class="text">  Location: http://www.example.org/pub/WWW/People.html
1536</pre><p id="rfc.section.10.4.p.5"> </p>
1537      <dl class="empty">
1538         <dd> <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.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the response.
1539            It is therefore possible for a response to contain header fields for both Location and Content-Location.
1540         </dd>
1541      </dl>
1542      <p id="rfc.section.10.4.p.6">There are circumstances in which a fragment identifier in a Location URL would not be appropriate: </p>
1543      <ul>
1544         <li>With a 201 Created response, because in this usage the Location header specifies the URL for the entire created resource.</li>
1545         <li>With a 300 Multiple Choices, since the choice decision is intended to be made on resource characteristics and not fragment
1546            characteristics.
1547         </li>
1548         <li>With 305 Use Proxy.</li>
1549      </ul>
1550      <div id="rfc.iref.m.9"></div>
1551      <div id="rfc.iref.h.6"></div>
1552      <h2 id="rfc.section.10.5"><a href="#rfc.section.10.5">10.5</a>&nbsp;<a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2>
1553      <p id="rfc.section.10.5.p.1">The request-header "Max-Forwards" field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section&nbsp;8.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section&nbsp;8.2</a>) methods to limit the number of proxies or gateways that can forward the request to the next inbound server. This can be
1554         useful when the client is attempting to trace a request chain which appears to be failing or looping in mid-chain.
1555      </p>
1556      <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="#notation" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a>
1557  <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
1558</pre><p id="rfc.section.10.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message may be forwarded.</p>
1559      <p id="rfc.section.10.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).
1560      </p>
1561      <p id="rfc.section.10.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
1562         referred to as part of that method definition.
1563      </p>
1564      <div id="rfc.iref.r.1"></div>
1565      <div id="rfc.iref.h.7"></div>
1566      <h2 id="rfc.section.10.6"><a href="#rfc.section.10.6">10.6</a>&nbsp;<a id="header.referer" href="#header.referer">Referer</a></h2>
1567      <p id="rfc.section.10.6.p.1">The request-header field "Referer" [sic] allows the client to specify, for the server's benefit, the address (URI) of the
1568         resource from which the Request-URI was obtained (the "referrer", although the header field is misspelled.) The Referer request-header
1569         allows a server to generate lists of back-links to resources for interest, logging, optimized caching, etc. It also allows
1570         obsolete or mistyped links to be traced for maintenance. The Referer field <em class="bcp14">MUST NOT</em> be sent if the Request-URI was obtained from a source that does not have its own URI, such as input from the user keyboard.
1571      </p>
1572      <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="#notation" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>
1573  <a href="#header.referer" class="smpl">Referer-v</a>      = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">relativeURI</a>
1574</pre><p id="rfc.section.10.6.p.3">Example:</p>
1575      <div id="rfc.figure.u.22"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
1576</pre><p id="rfc.section.10.6.p.5">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the 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;12.2</a> for security considerations.
1577      </p>
1578      <div id="rfc.iref.r.2"></div>
1579      <div id="rfc.iref.h.8"></div>
1580      <h2 id="rfc.section.10.7"><a href="#rfc.section.10.7">10.7</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2>
1581      <p id="rfc.section.10.7.p.1">The response-header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service
1582         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
1583         the redirected request. The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after
1584         the time of the response.
1585      </p>
1586      <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="#notation" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a>
1587  <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>
1588</pre><div id="rule.delta-seconds">
1589         <p id="rfc.section.10.7.p.3">  Time spans are non-negative decimal integers, representing time in seconds.</p>
1590      </div>
1591      <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>
1592</pre><p id="rfc.section.10.7.p.5">Two examples of its use are</p>
1593      <div id="rfc.figure.u.25"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
1594  Retry-After: 120
1595</pre><p id="rfc.section.10.7.p.7">In the latter example, the delay is 2 minutes.</p>
1596      <div id="rfc.iref.s.43"></div>
1597      <div id="rfc.iref.h.9"></div>
1598      <h2 id="rfc.section.10.8"><a href="#rfc.section.10.8">10.8</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h2>
1599      <p id="rfc.section.10.8.p.1">The response-header field "Server" contains information about the software used by the origin server to handle the request.
1600         The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.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>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance
1601         for identifying the application.
1602      </p>
1603      <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="#notation" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a>
1604  <a href="#header.server" class="smpl">Server-v</a>       = <a href="#abnf.dependencies" class="smpl">product</a>
1605                   *( <a href="#notation" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#notation" class="smpl">comment</a> ) )
1606</pre><p id="rfc.section.10.8.p.3">Example:</p>
1607      <div id="rfc.figure.u.27"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
1608</pre><p id="rfc.section.10.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</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>).
1609      </p>
1610      <dl class="empty">
1611         <dd> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
1612            against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable
1613            option.
1614         </dd>
1615      </dl>
1616      <div id="rfc.iref.u.1"></div>
1617      <div id="rfc.iref.h.10"></div>
1618      <h2 id="rfc.section.10.9"><a href="#rfc.section.10.9">10.9</a>&nbsp;<a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2>
1619      <p id="rfc.section.10.9.p.1">The request-header field "User-Agent" contains information about the user agent originating the request. This is for statistical
1620         purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses
1621         to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</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 identifying the agent and any subproducts which form a significant part of the user agent. By convention, the
1622         product tokens are listed in order of their significance for identifying the application.
1623      </p>
1624      <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="#notation" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a>
1625  <a href="#header.user-agent" class="smpl">User-Agent-v</a>   = <a href="#abnf.dependencies" class="smpl">product</a>
1626                   *( <a href="#notation" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#notation" class="smpl">comment</a> ) )
1627</pre><p id="rfc.section.10.9.p.3">Example:</p>
1628      <div id="rfc.figure.u.29"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
1629</pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
1630      <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
1631      <p id="rfc.section.11.1.p.1">The registration procedure for HTTP Methods is defined by <a href="#method.registry" title="Method Registry">Section&nbsp;3.1</a> of this document.
1632      </p>
1633      <p id="rfc.section.11.1.p.2">The HTTP Method Registry located at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt; should be populated with the registrations below:
1634      </p>
1635      <div id="rfc.table.1">
1636         <div id="iana.method.registration.table"></div>
1637         <table summary="" class="tt full" cellpadding="3" cellspacing="0">
1638            <thead>
1639               <tr>
1640                  <th>Method</th>
1641                  <th>Safe</th>
1642                  <th>Reference</th>
1643               </tr>
1644            </thead>
1645            <tbody>
1646               <tr>
1647                  <td>CONNECT</td>
1648                  <td>no</td>
1649                  <td> <a href="#CONNECT" id="rfc.xref.CONNECT.2" title="CONNECT">Section&nbsp;8.9</a> 
1650                  </td>
1651               </tr>
1652               <tr>
1653                  <td>DELETE</td>
1654                  <td>no</td>
1655                  <td> <a href="#DELETE" id="rfc.xref.DELETE.2" title="DELETE">Section&nbsp;8.7</a> 
1656                  </td>
1657               </tr>
1658               <tr>
1659                  <td>GET</td>
1660                  <td>yes</td>
1661                  <td> <a href="#GET" id="rfc.xref.GET.2" title="GET">Section&nbsp;8.3</a> 
1662                  </td>
1663               </tr>
1664               <tr>
1665                  <td>HEAD</td>
1666                  <td>yes</td>
1667                  <td> <a href="#HEAD" id="rfc.xref.HEAD.2" title="HEAD">Section&nbsp;8.4</a> 
1668                  </td>
1669               </tr>
1670               <tr>
1671                  <td>OPTIONS</td>
1672                  <td>yes</td>
1673                  <td> <a href="#OPTIONS" id="rfc.xref.OPTIONS.3" title="OPTIONS">Section&nbsp;8.2</a> 
1674                  </td>
1675               </tr>
1676               <tr>
1677                  <td>POST</td>
1678                  <td>no</td>
1679                  <td> <a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;8.5</a> 
1680                  </td>
1681               </tr>
1682               <tr>
1683                  <td>PUT</td>
1684                  <td>no</td>
1685                  <td> <a href="#PUT" id="rfc.xref.PUT.2" title="PUT">Section&nbsp;8.6</a> 
1686                  </td>
1687               </tr>
1688               <tr>
1689                  <td>TRACE</td>
1690                  <td>yes</td>
1691                  <td> <a href="#TRACE" id="rfc.xref.TRACE.3" title="TRACE">Section&nbsp;8.8</a> 
1692                  </td>
1693               </tr>
1694            </tbody>
1695         </table>
1696      </div>
1697      <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
1698      <p id="rfc.section.11.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;5.1</a> of this document.
1699      </p>
1700      <p id="rfc.section.11.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; should be updated with the registrations below:
1701      </p>
1702      <div id="rfc.table.2">
1703         <div id="iana.status.code.registration.table"></div>
1704         <table summary="" class="tt full" cellpadding="3" cellspacing="0">
1705            <thead>
1706               <tr>
1707                  <th>Value</th>
1708                  <th>Description</th>
1709                  <th>Reference</th>
1710               </tr>
1711            </thead>
1712            <tbody>
1713               <tr>
1714                  <td>100</td>
1715                  <td>Continue</td>
1716                  <td> <a href="#status.100" id="rfc.xref.status.100.2" title="100 Continue">Section&nbsp;9.1.1</a> 
1717                  </td>
1718               </tr>
1719               <tr>
1720                  <td>101</td>
1721                  <td>Switching Protocols</td>
1722                  <td> <a href="#status.101" id="rfc.xref.status.101.2" title="101 Switching Protocols">Section&nbsp;9.1.2</a> 
1723                  </td>
1724               </tr>
1725               <tr>
1726                  <td>200</td>
1727                  <td>OK</td>
1728                  <td> <a href="#status.200" id="rfc.xref.status.200.2" title="200 OK">Section&nbsp;9.2.1</a> 
1729                  </td>
1730               </tr>
1731               <tr>
1732                  <td>201</td>
1733                  <td>Created</td>
1734                  <td> <a href="#status.201" id="rfc.xref.status.201.2" title="201 Created">Section&nbsp;9.2.2</a> 
1735                  </td>
1736               </tr>
1737               <tr>
1738                  <td>202</td>
1739                  <td>Accepted</td>
1740                  <td> <a href="#status.202" id="rfc.xref.status.202.2" title="202 Accepted">Section&nbsp;9.2.3</a> 
1741                  </td>
1742               </tr>
1743               <tr>
1744                  <td>203</td>
1745                  <td>Non-Authoritative Information</td>
1746                  <td> <a href="#status.203" id="rfc.xref.status.203.2" title="203 Non-Authoritative Information">Section&nbsp;9.2.4</a> 
1747                  </td>
1748               </tr>
1749               <tr>
1750                  <td>204</td>
1751                  <td>No Content</td>
1752                  <td> <a href="#status.204" id="rfc.xref.status.204.2" title="204 No Content">Section&nbsp;9.2.5</a> 
1753                  </td>
1754               </tr>
1755               <tr>
1756                  <td>205</td>
1757                  <td>Reset Content</td>
1758                  <td> <a href="#status.205" id="rfc.xref.status.205.2" title="205 Reset Content">Section&nbsp;9.2.6</a> 
1759                  </td>
1760               </tr>
1761               <tr>
1762                  <td>206</td>
1763                  <td>Partial Content</td>
1764                  <td> <a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;9.2.7</a> 
1765                  </td>
1766               </tr>
1767               <tr>
1768                  <td>300</td>
1769                  <td>Multiple Choices</td>
1770                  <td> <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section&nbsp;9.3.1</a> 
1771                  </td>
1772               </tr>
1773               <tr>
1774                  <td>301</td>
1775                  <td>Moved Permanently</td>
1776                  <td> <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">Section&nbsp;9.3.2</a> 
1777                  </td>
1778               </tr>
1779               <tr>
1780                  <td>302</td>
1781                  <td>Found</td>
1782                  <td> <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">Section&nbsp;9.3.3</a> 
1783                  </td>
1784               </tr>
1785               <tr>
1786                  <td>303</td>
1787                  <td>See Other</td>
1788                  <td> <a href="#status.303" id="rfc.xref.status.303.2" title="303 See Other">Section&nbsp;9.3.4</a> 
1789                  </td>
1790               </tr>
1791               <tr>
1792                  <td>304</td>
1793                  <td>Not Modified</td>
1794                  <td> <a href="#status.304" id="rfc.xref.status.304.2" title="304 Not Modified">Section&nbsp;9.3.5</a> 
1795                  </td>
1796               </tr>
1797               <tr>
1798                  <td>305</td>
1799                  <td>Use Proxy</td>
1800                  <td> <a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;9.3.6</a> 
1801                  </td>
1802               </tr>
1803               <tr>
1804                  <td>306</td>
1805                  <td>(Unused)</td>
1806                  <td> <a href="#status.306" id="rfc.xref.status.306.1" title="306 (Unused)">Section&nbsp;9.3.7</a> 
1807                  </td>
1808               </tr>
1809               <tr>
1810                  <td>307</td>
1811                  <td>Temporary Redirect</td>
1812                  <td> <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">Section&nbsp;9.3.8</a> 
1813                  </td>
1814               </tr>
1815               <tr>
1816                  <td>400</td>
1817                  <td>Bad Request</td>
1818                  <td> <a href="#status.400" id="rfc.xref.status.400.2" title="400 Bad Request">Section&nbsp;9.4.1</a> 
1819                  </td>
1820               </tr>
1821               <tr>
1822                  <td>401</td>
1823                  <td>Unauthorized</td>
1824                  <td> <a href="#status.401" id="rfc.xref.status.401.2" title="401 Unauthorized">Section&nbsp;9.4.2</a> 
1825                  </td>
1826               </tr>
1827               <tr>
1828                  <td>402</td>
1829                  <td>Payment Required</td>
1830                  <td> <a href="#status.402" id="rfc.xref.status.402.2" title="402 Payment Required">Section&nbsp;9.4.3</a> 
1831                  </td>
1832               </tr>
1833               <tr>
1834                  <td>403</td>
1835                  <td>Forbidden</td>
1836                  <td> <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">Section&nbsp;9.4.4</a> 
1837                  </td>
1838               </tr>
1839               <tr>
1840                  <td>404</td>
1841                  <td>Not Found</td>
1842                  <td> <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">Section&nbsp;9.4.5</a> 
1843                  </td>
1844               </tr>
1845               <tr>
1846                  <td>405</td>
1847                  <td>Method Not Allowed</td>
1848                  <td> <a href="#status.405" id="rfc.xref.status.405.2" title="405 Method Not Allowed">Section&nbsp;9.4.6</a> 
1849                  </td>
1850               </tr>
1851               <tr>
1852                  <td>406</td>
1853                  <td>Not Acceptable</td>
1854                  <td> <a href="#status.406" id="rfc.xref.status.406.2" title="406 Not Acceptable">Section&nbsp;9.4.7</a> 
1855                  </td>
1856               </tr>
1857               <tr>
1858                  <td>407</td>
1859                  <td>Proxy Authentication Required</td>
1860                  <td> <a href="#status.407" id="rfc.xref.status.407.2" title="407 Proxy Authentication Required">Section&nbsp;9.4.8</a> 
1861                  </td>
1862               </tr>
1863               <tr>
1864                  <td>408</td>
1865                  <td>Request Timeout</td>
1866                  <td> <a href="#status.408" id="rfc.xref.status.408.2" title="408 Request Timeout">Section&nbsp;9.4.9</a> 
1867                  </td>
1868               </tr>
1869               <tr>
1870                  <td>409</td>
1871                  <td>Conflict</td>
1872                  <td> <a href="#status.409" id="rfc.xref.status.409.2" title="409 Conflict">Section&nbsp;9.4.10</a> 
1873                  </td>
1874               </tr>
1875               <tr>
1876                  <td>410</td>
1877                  <td>Gone</td>
1878                  <td> <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">Section&nbsp;9.4.11</a> 
1879                  </td>
1880               </tr>
1881               <tr>
1882                  <td>411</td>
1883                  <td>Length Required</td>
1884                  <td> <a href="#status.411" id="rfc.xref.status.411.2" title="411 Length Required">Section&nbsp;9.4.12</a> 
1885                  </td>
1886               </tr>
1887               <tr>
1888                  <td>412</td>
1889                  <td>Precondition Failed</td>
1890                  <td> <a href="#status.412" id="rfc.xref.status.412.2" title="412 Precondition Failed">Section&nbsp;9.4.13</a> 
1891                  </td>
1892               </tr>
1893               <tr>
1894                  <td>413</td>
1895                  <td>Request Entity Too Large</td>
1896                  <td> <a href="#status.413" id="rfc.xref.status.413.2" title="413 Request Entity Too Large">Section&nbsp;9.4.14</a> 
1897                  </td>
1898               </tr>
1899               <tr>
1900                  <td>414</td>
1901                  <td>Request-URI Too Long</td>
1902                  <td> <a href="#status.414" id="rfc.xref.status.414.2" title="414 Request-URI Too Long">Section&nbsp;9.4.15</a> 
1903                  </td>
1904               </tr>
1905               <tr>
1906                  <td>415</td>
1907                  <td>Unsupported Media Type</td>
1908                  <td> <a href="#status.415" id="rfc.xref.status.415.2" title="415 Unsupported Media Type">Section&nbsp;9.4.16</a> 
1909                  </td>
1910               </tr>
1911               <tr>
1912                  <td>416</td>
1913                  <td>Requested Range Not Satisfiable</td>
1914                  <td> <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section&nbsp;9.4.17</a> 
1915                  </td>
1916               </tr>
1917               <tr>
1918                  <td>417</td>
1919                  <td>Expectation Failed</td>
1920                  <td> <a href="#status.417" id="rfc.xref.status.417.2" title="417 Expectation Failed">Section&nbsp;9.4.18</a> 
1921                  </td>
1922               </tr>
1923               <tr>
1924                  <td>500</td>
1925                  <td>Internal Server Error</td>
1926                  <td> <a href="#status.500" id="rfc.xref.status.500.2" title="500 Internal Server Error">Section&nbsp;9.5.1</a> 
1927                  </td>
1928               </tr>
1929               <tr>
1930                  <td>501</td>
1931                  <td>Not Implemented</td>
1932                  <td> <a href="#status.501" id="rfc.xref.status.501.2" title="501 Not Implemented">Section&nbsp;9.5.2</a> 
1933                  </td>
1934               </tr>
1935               <tr>
1936                  <td>502</td>
1937                  <td>Bad Gateway</td>
1938                  <td> <a href="#status.502" id="rfc.xref.status.502.2" title="502 Bad Gateway">Section&nbsp;9.5.3</a> 
1939                  </td>
1940               </tr>
1941               <tr>
1942                  <td>503</td>
1943                  <td>Service Unavailable</td>
1944                  <td> <a href="#status.503" id="rfc.xref.status.503.2" title="503 Service Unavailable">Section&nbsp;9.5.4</a> 
1945                  </td>
1946               </tr>
1947               <tr>
1948                  <td>504</td>
1949                  <td>Gateway Timeout</td>
1950                  <td> <a href="#status.504" id="rfc.xref.status.504.2" title="504 Gateway Timeout">Section&nbsp;9.5.5</a> 
1951                  </td>
1952               </tr>
1953               <tr>
1954                  <td>505</td>
1955                  <td>HTTP Version Not Supported</td>
1956                  <td> <a href="#status.505" id="rfc.xref.status.505.2" title="505 HTTP Version Not Supported">Section&nbsp;9.5.6</a> 
1957                  </td>
1958               </tr>
1959            </tbody>
1960         </table>
1961      </div>
1962      <h2 id="rfc.section.11.3"><a href="#rfc.section.11.3">11.3</a>&nbsp;<a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>
1963      <p id="rfc.section.11.3.p.1">The Message Header Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
1964      </p>
1965      <div id="rfc.table.3">
1966         <div id="iana.header.registration.table"></div>
1967         <table summary="" class="tt full" cellpadding="3" cellspacing="0">
1968            <thead>
1969               <tr>
1970                  <th>Header Field Name</th>
1971                  <th>Protocol</th>
1972                  <th>Status</th>
1973                  <th>Reference</th>
1974               </tr>
1975            </thead>
1976            <tbody>
1977               <tr>
1978                  <td>Allow</td>
1979                  <td>http</td>
1980                  <td>standard</td>
1981                  <td> <a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;10.1</a> 
1982                  </td>
1983               </tr>
1984               <tr>
1985                  <td>Expect</td>
1986                  <td>http</td>
1987                  <td>standard</td>
1988                  <td> <a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;10.2</a> 
1989                  </td>
1990               </tr>
1991               <tr>
1992                  <td>From</td>
1993                  <td>http</td>
1994                  <td>standard</td>
1995                  <td> <a href="#header.from" id="rfc.xref.header.from.2" title="From">Section&nbsp;10.3</a> 
1996                  </td>
1997               </tr>
1998               <tr>
1999                  <td>Location</td>
2000                  <td>http</td>
2001                  <td>standard</td>
2002                  <td> <a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;10.4</a> 
2003                  </td>
2004               </tr>
2005               <tr>
2006                  <td>Max-Forwards</td>
2007                  <td>http</td>
2008                  <td>standard</td>
2009                  <td> <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.3" title="Max-Forwards">Section&nbsp;10.5</a> 
2010                  </td>
2011               </tr>
2012               <tr>
2013                  <td>Referer</td>
2014                  <td>http</td>
2015                  <td>standard</td>
2016                  <td> <a href="#header.referer" id="rfc.xref.header.referer.2" title="Referer">Section&nbsp;10.6</a> 
2017                  </td>
2018               </tr>
2019               <tr>
2020                  <td>Retry-After</td>
2021                  <td>http</td>
2022                  <td>standard</td>
2023                  <td> <a href="#header.retry-after" id="rfc.xref.header.retry-after.2" title="Retry-After">Section&nbsp;10.7</a> 
2024                  </td>
2025               </tr>
2026               <tr>
2027                  <td>Server</td>
2028                  <td>http</td>
2029                  <td>standard</td>
2030                  <td> <a href="#header.server" id="rfc.xref.header.server.2" title="Server">Section&nbsp;10.8</a> 
2031                  </td>
2032               </tr>
2033               <tr>
2034                  <td>User-Agent</td>
2035                  <td>http</td>
2036                  <td>standard</td>
2037                  <td> <a href="#header.user-agent" id="rfc.xref.header.user-agent.2" title="User-Agent">Section&nbsp;10.9</a> 
2038                  </td>
2039               </tr>
2040            </tbody>
2041         </table>
2042      </div>
2043      <p id="rfc.section.11.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
2044      <h1 id="rfc.section.12"><a href="#rfc.section.12">12.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
2045      <p id="rfc.section.12.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
2046         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
2047         make some suggestions for reducing security risks.
2048      </p>
2049      <h2 id="rfc.section.12.1"><a href="#rfc.section.12.1">12.1</a>&nbsp;<a id="security.sensitive" href="#security.sensitive">Transfer of Sensitive Information</a></h2>
2050      <p id="rfc.section.12.1.p.1">Like any generic data transfer protocol, HTTP cannot regulate the content of the data that is transferred, nor is there any
2051         a priori method of determining the sensitivity of any particular piece of information within the context of any given request.
2052         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
2053         special mention in this context: Server, Via, Referer and From.
2054      </p>
2055      <p id="rfc.section.12.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
2056         against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the Server header field a configurable option.
2057      </p>
2058      <p id="rfc.section.12.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,
2059         they <em class="bcp14">SHOULD</em> remove, or replace with sanitized versions, any Via fields generated behind the firewall.
2060      </p>
2061      <p id="rfc.section.12.1.p.4">The Referer header allows reading patterns to be studied and reverse links drawn. Although it can be very useful, its power
2062         can be abused if user details are not separated from the information contained in the Referer. Even when the personal information
2063         has been removed, the Referer header might indicate a private document's URI whose publication would be inappropriate.
2064      </p>
2065      <p id="rfc.section.12.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
2066         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.
2067      </p>
2068      <p id="rfc.section.12.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
2069         of From and Referer information.
2070      </p>
2071      <p id="rfc.section.12.1.p.7">The User-Agent (<a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;10.9</a>) or Server (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;10.8</a>) header fields can sometimes be used to determine that a specific client or server have a particular security hole which
2072         might be exploited. Unfortunately, this same information is often used for other valuable purposes for which HTTP currently
2073         has no better mechanism.
2074      </p>
2075      <h2 id="rfc.section.12.2"><a href="#rfc.section.12.2">12.2</a>&nbsp;<a id="encoding.sensitive.information.in.uris" href="#encoding.sensitive.information.in.uris">Encoding Sensitive Information in URIs</a></h2>
2076      <p id="rfc.section.12.2.p.1">Because the source of a link might be private information or might reveal an otherwise private information source, it is strongly
2077         recommended that the user be able to select whether or not the Referer field is sent. For example, a browser client could
2078         have a toggle switch for browsing openly/anonymously, which would respectively enable/disable the sending of Referer and From
2079         information.
2080      </p>
2081      <p id="rfc.section.12.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.
2082      </p>
2083      <p id="rfc.section.12.2.p.3">Authors of services should not use GET-based forms for the submission of sensitive data because that data will be encoded
2084         in the Request-URI. Many existing servers, proxies, and user agents log or display the Request-URI in places where it might
2085         be visible to third parties. Such services can use POST-based form submission instead.
2086      </p>
2087      <h2 id="rfc.section.12.3"><a href="#rfc.section.12.3">12.3</a>&nbsp;<a id="location.spoofing" href="#location.spoofing">Location Headers and Spoofing</a></h2>
2088      <p id="rfc.section.12.3.p.1">If a single server supports multiple organizations that do not trust one another, then it <em class="bcp14">MUST</em> check the values of Location and Content-Location headers in responses that are generated under control of said organizations
2089         to make sure that they do not attempt to invalidate resources over which they have no authority.
2090      </p>
2091      <h1 id="rfc.section.13"><a href="#rfc.section.13">13.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
2092      <h1 id="rfc.references"><a id="rfc.section.14" href="#rfc.section.14">14.</a> References
2093      </h1>
2094      <h2 id="rfc.references.1"><a href="#rfc.section.14.1" id="rfc.section.14.1">14.1</a> Normative References
2095      </h2>
2096      <table summary="Normative References">             
2097         <tr>
2098            <td class="reference"><b id="Part1">[Part1]</b></td>
2099            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), November&nbsp;2008.
2100            </td>
2101         </tr>
2102         <tr>
2103            <td class="reference"><b id="Part3">[Part3]</b></td>
2104            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-latest (work in progress), November&nbsp;2008.
2105            </td>
2106         </tr>
2107         <tr>
2108            <td class="reference"><b id="Part4">[Part4]</b></td>
2109            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), November&nbsp;2008.
2110            </td>
2111         </tr>
2112         <tr>
2113            <td class="reference"><b id="Part5">[Part5]</b></td>
2114            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), November&nbsp;2008.
2115            </td>
2116         </tr>
2117         <tr>
2118            <td class="reference"><b id="Part6">[Part6]</b></td>
2119            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), November&nbsp;2008.
2120            </td>
2121         </tr>
2122         <tr>
2123            <td class="reference"><b id="Part7">[Part7]</b></td>
2124            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), November&nbsp;2008.
2125            </td>
2126         </tr>
2127         <tr>
2128            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
2129            <td class="top"><a 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.
2130            </td>
2131         </tr>
2132      </table>
2133      <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References
2134      </h2>
2135      <table summary="Informative References">             
2136         <tr>
2137            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
2138            <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
2139            </td>
2140         </tr>
2141         <tr>
2142            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
2143            <td class="top"><a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a 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.
2144            </td>
2145         </tr>
2146         <tr>
2147            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
2148            <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a 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.
2149            </td>
2150         </tr>
2151         <tr>
2152            <td class="reference"><b id="RFC2817">[RFC2817]</b></td>
2153            <td class="top"><a title="4K Associates / UC Irvine">Khare, R.</a> and <a 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.
2154            </td>
2155         </tr>
2156         <tr>
2157            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
2158            <td class="top"><a title="Nine by Nine">Klyne, G.</a>, <a title="BEA Systems">Nottingham, M.</a>, and <a 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.
2159            </td>
2160         </tr>
2161         <tr>
2162            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
2163            <td class="top"><a title="IBM">Narten, T.</a> and <a 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.
2164            </td>
2165         </tr>
2166         <tr>
2167            <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
2168            <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
2169            </td>
2170         </tr>
2171      </table>
2172      <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
2173      <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
2174            (editor)
2175            <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><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>
2176      <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
2177      <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><span class="email">JeffMogul@acm.org</span></a></span></address>
2178      <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><span class="email">henrikn@microsoft.com</span></a></span></address>
2179      <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><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>
2180      <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><span class="email">paulle@microsoft.com</span></a></span></address>
2181      <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><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>
2182      <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
2183            (editor)
2184            <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><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>
2185      <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
2186            (editor)
2187            <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><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>
2188      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
2189      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
2190      <p id="rfc.section.A.1.p.1">Clarified which error code should be used for inbound server failures (e.g. DNS failures). (<a href="#status.504" id="rfc.xref.status.504.3" title="504 Gateway Timeout">Section&nbsp;9.5.5</a>).
2191      </p>
2192      <p id="rfc.section.A.1.p.2">201 (Created) had a race that required an Etag be sent when a resource is first created. (<a href="#status.201" id="rfc.xref.status.201.3" title="201 Created">Section&nbsp;9.2.2</a>).
2193      </p>
2194      <p id="rfc.section.A.1.p.3">Rewrite of message transmission requirements to make it much harder for implementors to get it wrong, as the consequences
2195         of errors here can have significant impact on the Internet, and to deal with the following problems:
2196      </p>
2197      <ol>
2198         <li>Changing "HTTP/1.1 or later" to "HTTP/1.1", in contexts where this was incorrectly placing a requirement on the behavior of
2199            an implementation of a future version of HTTP/1.x
2200         </li>
2201         <li>Made it clear that user-agents should retry requests, not "clients" in general.</li>
2202         <li>Converted requirements for clients to ignore unexpected 100 (Continue) responses, and for proxies to forward 100 responses,
2203            into a general requirement for 1xx responses.
2204         </li>
2205         <li>Modified some TCP-specific language, to make it clearer that non-TCP transports are possible for HTTP.</li>
2206         <li>Require that the origin server <em class="bcp14">MUST NOT</em> wait for the request body before it sends a required 100 (Continue) response.
2207         </li>
2208         <li>Allow, rather than require, a server to omit 100 (Continue) if it has already seen some of the request body.</li>
2209         <li>Allow servers to defend against denial-of-service attacks and broken clients.</li>
2210      </ol>
2211      <p id="rfc.section.A.1.p.4">This change adds the Expect header and 417 status code.</p>
2212      <p id="rfc.section.A.1.p.5">Clean up confusion between 403 and 404 responses. (Section <a href="#status.403" id="rfc.xref.status.403.3" title="403 Forbidden">9.4.4</a>, <a href="#status.404" id="rfc.xref.status.404.3" title="404 Not Found">9.4.5</a>, and <a href="#status.410" id="rfc.xref.status.410.3" title="410 Gone">9.4.11</a>)
2213      </p>
2214      <p id="rfc.section.A.1.p.6">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.1">Section 19.6.1</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
2215      </p>
2216      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
2217      <p id="rfc.section.A.2.p.1">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;5.1</a>)
2218      </p>
2219      <p id="rfc.section.A.2.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;8.5</a>)
2220      </p>
2221      <p id="rfc.section.A.2.p.3">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
2222         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">9.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">9.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">9.3.8</a>)
2223      </p>
2224      <p id="rfc.section.A.2.p.4">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the requested resource
2225         must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
2226         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;9.3.6</a>)
2227      </p>
2228      <p id="rfc.section.A.2.p.5">Reclassify Allow header as response header, removing the option to specify it in a PUT request. Relax the server requirement
2229         on the contents of the Allow header and remove requirement on clients to always trust the header value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;10.1</a>)
2230      </p>
2231      <p id="rfc.section.A.2.p.6">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications
2232         as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;10.4</a>)
2233      </p>
2234      <p id="rfc.section.A.2.p.7">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly
2235         in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</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>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;10.8</a>)
2236      </p>
2237      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
2238      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
2239      </h2>
2240      <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
2241      </p>
2242      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-00
2243      </h2>
2244      <p id="rfc.section.B.2.p.1">Closed issues: </p>
2245      <ul>
2246         <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;)
2247         </li>
2248         <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;)
2249         </li>
2250         <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;)
2251         </li>
2252         <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;)
2253         </li>
2254         <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"
2255         </li>
2256         <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"
2257         </li>
2258         <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"
2259         </li>
2260         <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"
2261         </li>
2262      </ul>
2263      <p id="rfc.section.B.2.p.2">Other changes: </p>
2264      <ul>
2265         <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.14"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> 
2266         </li>
2267      </ul>
2268      <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
2269      </h2>
2270      <p id="rfc.section.B.3.p.1">Closed issues: </p>
2271      <ul>
2272         <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"
2273         </li>
2274         <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"
2275         </li>
2276      </ul>
2277      <p id="rfc.section.B.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;):
2278      </p>
2279      <ul>
2280         <li>Move "Product Tokens" section (back) into Part 1, as "token" is used in the definition of the Upgrade header.</li>
2281         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
2282         <li>Copy definition of delta-seconds from Part6 instead of referencing it.</li>
2283      </ul>
2284      <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p2-semantics-02</a></h2>
2285      <p id="rfc.section.B.4.p.1">Closed issues: </p>
2286      <ul>
2287         <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"
2288         </li>
2289         <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"
2290         </li>
2291         <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"
2292         </li>
2293         <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"
2294         </li>
2295         <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"
2296         </li>
2297         <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"
2298         </li>
2299         <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'"
2300         </li>
2301      </ul>
2302      <p id="rfc.section.B.4.p.2">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
2303      </p>
2304      <ul>
2305         <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
2306      </ul>
2307      <p id="rfc.section.B.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;):
2308      </p>
2309      <ul>
2310         <li>Replace string literals when the string really is case-sensitive (method).</li>
2311      </ul>
2312      <h2 id="rfc.section.B.5"><a href="#rfc.section.B.5">B.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>
2313      <p id="rfc.section.B.5.p.1">Closed issues: </p>
2314      <ul>
2315         <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"
2316         </li>
2317         <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"
2318         </li>
2319         <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"
2320         </li>
2321      </ul>
2322      <p id="rfc.section.B.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;):
2323      </p>
2324      <ul>
2325         <li>Added initial proposal for registration process, plus initial content (non-HTTP/1.1 methods to be added by a separate specification).</li>
2326      </ul>
2327      <h2 id="rfc.section.B.6"><a href="#rfc.section.B.6">B.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p2-semantics-04</a></h2>
2328      <p id="rfc.section.B.6.p.1">Closed issues: </p>
2329      <ul>
2330         <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-*"
2331         </li>
2332         <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"
2333         </li>
2334      </ul>
2335      <p id="rfc.section.B.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;):
2336      </p>
2337      <ul>
2338         <li>Use "/" instead of "|" for alternatives.</li>
2339         <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
2340         <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
2341      </ul>
2342      <h2 id="rfc.section.B.7"><a href="#rfc.section.B.7">B.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p2-semantics-05</a></h2>
2343      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
2344      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
2345         authors retain all their rights.
2346      </p>
2347      <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
2348         HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
2349         DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
2350         WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2351      </p>
2352      <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
2353      <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
2354         be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
2355         license under such rights might or might not be available; nor does it represent that it has made any independent effort to
2356         identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
2357         BCP 79.
2358      </p>
2359      <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
2360         of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
2361         of this specification can be obtained from the IETF on-line IPR repository at &lt;<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>&gt;.
2362      </p>
2363      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
2364         rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
2365         at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
2366      </p>
2367      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
2368      <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> 
2369      </p>
2370      <div class="print2col">
2371         <ul class="ind">
2372            <li class="indline0"><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul class="ind">
2373                  <li class="indline1">100 Continue (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.100.1">5</a>, <a class="iref" href="#rfc.iref.25"><b>9.1.1</b></a>, <a class="iref" href="#rfc.xref.status.100.2">11.2</a></li>
2374                  <li class="indline1">101 Switching Protocols (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.101.1">5</a>, <a class="iref" href="#rfc.iref.26"><b>9.1.2</b></a>, <a class="iref" href="#rfc.xref.status.101.2">11.2</a></li>
2375               </ul>
2376            </li>
2377            <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind">
2378                  <li class="indline1">200 OK (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.200.1">5</a>, <a class="iref" href="#rfc.iref.27"><b>9.2.1</b></a>, <a class="iref" href="#rfc.xref.status.200.2">11.2</a></li>
2379                  <li class="indline1">201 Created (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.201.1">5</a>, <a class="iref" href="#rfc.iref.28"><b>9.2.2</b></a>, <a class="iref" href="#rfc.xref.status.201.2">11.2</a>, <a class="iref" href="#rfc.xref.status.201.3">A.1</a></li>
2380                  <li class="indline1">202 Accepted (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.202.1">5</a>, <a class="iref" href="#rfc.iref.29"><b>9.2.3</b></a>, <a class="iref" href="#rfc.xref.status.202.2">11.2</a></li>
2381                  <li class="indline1">203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.203.1">5</a>, <a class="iref" href="#rfc.iref.30"><b>9.2.4</b></a>, <a class="iref" href="#rfc.xref.status.203.2">11.2</a></li>
2382                  <li class="indline1">204 No Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.204.1">5</a>, <a class="iref" href="#rfc.iref.31"><b>9.2.5</b></a>, <a class="iref" href="#rfc.xref.status.204.2">11.2</a></li>
2383                  <li class="indline1">205 Reset Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.205.1">5</a>, <a class="iref" href="#rfc.iref.32"><b>9.2.6</b></a>, <a class="iref" href="#rfc.xref.status.205.2">11.2</a></li>
2384                  <li class="indline1">206 Partial Content (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.206.1">5</a>, <a class="iref" href="#rfc.iref.33"><b>9.2.7</b></a>, <a class="iref" href="#rfc.xref.status.206.2">11.2</a></li>
2385               </ul>
2386            </li>
2387            <li class="indline0"><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul class="ind">
2388                  <li class="indline1">300 Multiple Choices (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.300.1">5</a>, <a class="iref" href="#rfc.iref.34"><b>9.3.1</b></a>, <a class="iref" href="#rfc.xref.status.300.2">11.2</a></li>
2389                  <li class="indline1">301 Moved Permanently (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.301.1">5</a>, <a class="iref" href="#rfc.iref.35"><b>9.3.2</b></a>, <a class="iref" href="#rfc.xref.status.301.2">11.2</a>, <a class="iref" href="#rfc.xref.status.301.3">A.2</a></li>
2390                  <li class="indline1">302 Found (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.302.1">5</a>, <a class="iref" href="#rfc.iref.36"><b>9.3.3</b></a>, <a class="iref" href="#rfc.xref.status.302.2">11.2</a>, <a class="iref" href="#rfc.xref.status.302.3">A.2</a></li>
2391                  <li class="indline1">303 See Other (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.303.1">5</a>, <a class="iref" href="#rfc.iref.37"><b>9.3.4</b></a>, <a class="iref" href="#rfc.xref.status.303.2">11.2</a></li>
2392                  <li class="indline1">304 Not Modified (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.304.1">5</a>, <a class="iref" href="#rfc.iref.38"><b>9.3.5</b></a>, <a class="iref" href="#rfc.xref.status.304.2">11.2</a></li>
2393                  <li class="indline1">305 Use Proxy (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.305.1">5</a>, <a class="iref" href="#rfc.iref.39"><b>9.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">11.2</a>, <a class="iref" href="#rfc.xref.status.305.3">A.2</a></li>
2394                  <li class="indline1">306 (Unused) (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.40"><b>9.3.7</b></a>, <a class="iref" href="#rfc.xref.status.306.1">11.2</a></li>
2395                  <li class="indline1">307 Temporary Redirect (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.307.1">5</a>, <a class="iref" href="#rfc.iref.41"><b>9.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.2">11.2</a>, <a class="iref" href="#rfc.xref.status.307.3">A.2</a></li>
2396               </ul>
2397            </li>
2398            <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind">
2399                  <li class="indline1">400 Bad Request (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.400.1">5</a>, <a class="iref" href="#rfc.iref.42"><b>9.4.1</b></a>, <a class="iref" href="#rfc.xref.status.400.2">11.2</a></li>
2400                  <li class="indline1">401 Unauthorized (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.401.1">5</a>, <a class="iref" href="#rfc.iref.43"><b>9.4.2</b></a>, <a class="iref" href="#rfc.xref.status.401.2">11.2</a></li>
2401                  <li class="indline1">402 Payment Required (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.402.1">5</a>, <a class="iref" href="#rfc.iref.44"><b>9.4.3</b></a>, <a class="iref" href="#rfc.xref.status.402.2">11.2</a></li>
2402                  <li class="indline1">403 Forbidden (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.403.1">5</a>, <a class="iref" href="#rfc.iref.45"><b>9.4.4</b></a>, <a class="iref" href="#rfc.xref.status.403.2">11.2</a>, <a class="iref" href="#rfc.xref.status.403.3">A.1</a></li>
2403                  <li class="indline1">404 Not Found (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.404.1">5</a>, <a class="iref" href="#rfc.iref.46"><b>9.4.5</b></a>, <a class="iref" href="#rfc.xref.status.404.2">11.2</a>, <a class="iref" href="#rfc.xref.status.404.3">A.1</a></li>
2404                  <li class="indline1">405 Method Not Allowed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.405.1">5</a>, <a class="iref" href="#rfc.iref.47"><b>9.4.6</b></a>, <a class="iref" href="#rfc.xref.status.405.2">11.2</a></li>
2405                  <li class="indline1">406 Not Acceptable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.406.1">5</a>, <a class="iref" href="#rfc.iref.48"><b>9.4.7</b></a>, <a class="iref" href="#rfc.xref.status.406.2">11.2</a></li>
2406                  <li class="indline1">407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.407.1">5</a>, <a class="iref" href="#rfc.iref.49"><b>9.4.8</b></a>, <a class="iref" href="#rfc.xref.status.407.2">11.2</a></li>
2407                  <li class="indline1">408 Request Timeout (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.408.1">5</a>, <a class="iref" href="#rfc.iref.50"><b>9.4.9</b></a>, <a class="iref" href="#rfc.xref.status.408.2">11.2</a></li>
2408                  <li class="indline1">409 Conflict (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.409.1">5</a>, <a class="iref" href="#rfc.iref.51"><b>9.4.10</b></a>, <a class="iref" href="#rfc.xref.status.409.2">11.2</a></li>
2409                  <li class="indline1">410 Gone (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.410.1">5</a>, <a class="iref" href="#rfc.iref.52"><b>9.4.11</b></a>, <a class="iref" href="#rfc.xref.status.410.2">11.2</a>, <a class="iref" href="#rfc.xref.status.410.3">A.1</a></li>
2410                  <li class="indline1">411 Length Required (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.411.1">5</a>, <a class="iref" href="#rfc.iref.53"><b>9.4.12</b></a>, <a class="iref" href="#rfc.xref.status.411.2">11.2</a></li>
2411                  <li class="indline1">412 Precondition Failed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.412.1">5</a>, <a class="iref" href="#rfc.iref.54"><b>9.4.13</b></a>, <a class="iref" href="#rfc.xref.status.412.2">11.2</a></li>
2412                  <li class="indline1">413 Request Entity Too Large (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.413.1">5</a>, <a class="iref" href="#rfc.iref.55"><b>9.4.14</b></a>, <a class="iref" href="#rfc.xref.status.413.2">11.2</a></li>
2413                  <li class="indline1">414 Request-URI Too Long (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.414.1">5</a>, <a class="iref" href="#rfc.iref.56"><b>9.4.15</b></a>, <a class="iref" href="#rfc.xref.status.414.2">11.2</a></li>
2414                  <li class="indline1">415 Unsupported Media Type (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.415.1">5</a>, <a class="iref" href="#rfc.iref.57"><b>9.4.16</b></a>, <a class="iref" href="#rfc.xref.status.415.2">11.2</a></li>
2415                  <li class="indline1">416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.416.1">5</a>, <a class="iref" href="#rfc.iref.58"><b>9.4.17</b></a>, <a class="iref" href="#rfc.xref.status.416.2">11.2</a></li>
2416                  <li class="indline1">417 Expectation Failed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.xref.status.417.1">