source: draft-ietf-httpbis/14/draft-ietf-httpbis-p2-semantics-14.xml @ 1271

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

-14

  • Property svn:eol-style set to native
File size: 154.4 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<!--
3    This XML document is the output of clean-for-DTD.xslt; a tool that strips
4    extensions to RFC2629(bis) from documents for processing with xml2rfc.
5-->
6<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
7<?rfc toc="yes" ?>
8<?rfc symrefs="yes" ?>
9<?rfc sortrefs="yes" ?>
10<?rfc compact="yes"?>
11<?rfc subcompact="no" ?>
12<?rfc linkmailto="no" ?>
13<?rfc editing="no" ?>
14<?rfc comments="yes"?>
15<?rfc inline="yes"?>
16<?rfc rfcedstyle="yes"?>
17<!DOCTYPE rfc
18  PUBLIC "" "rfc2629.dtd">
19<rfc obsoletes="2616" updates="2817" category="std" ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p2-semantics-14">
20<front>
21
22  <title abbrev="HTTP/1.1, Part 2">HTTP/1.1, part 2: Message Semantics</title>
23
24  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
25    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
26    <address>
27      <postal>
28        <street>345 Park Ave</street>
29        <city>San Jose</city>
30        <region>CA</region>
31        <code>95110</code>
32        <country>USA</country>
33      </postal>
34      <email>fielding@gbiv.com</email>
35      <uri>http://roy.gbiv.com/</uri>
36    </address>
37  </author>
38
39  <author initials="J." surname="Gettys" fullname="Jim Gettys">
40    <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
41    <address>
42      <postal>
43        <street>21 Oak Knoll Road</street>
44        <city>Carlisle</city>
45        <region>MA</region>
46        <code>01741</code>
47        <country>USA</country>
48      </postal>
49      <email>jg@freedesktop.org</email>
50      <uri>http://gettys.wordpress.com/</uri>
51    </address>
52  </author>
53 
54  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
55    <organization abbrev="HP">Hewlett-Packard Company</organization>
56    <address>
57      <postal>
58        <street>HP Labs, Large Scale Systems Group</street>
59        <street>1501 Page Mill Road, MS 1177</street>
60        <city>Palo Alto</city>
61        <region>CA</region>
62        <code>94304</code>
63        <country>USA</country>
64      </postal>
65      <email>JeffMogul@acm.org</email>
66    </address>
67  </author>
68
69  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
70    <organization abbrev="Microsoft">Microsoft Corporation</organization>
71    <address>
72      <postal>
73        <street>1 Microsoft Way</street>
74        <city>Redmond</city>
75        <region>WA</region>
76        <code>98052</code>
77        <country>USA</country>
78      </postal>
79      <email>henrikn@microsoft.com</email>
80    </address>
81  </author>
82
83  <author initials="L." surname="Masinter" fullname="Larry Masinter">
84    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
85    <address>
86      <postal>
87        <street>345 Park Ave</street>
88        <city>San Jose</city>
89        <region>CA</region>
90        <code>95110</code>
91        <country>USA</country>
92      </postal>
93      <email>LMM@acm.org</email>
94      <uri>http://larry.masinter.net/</uri>
95    </address>
96  </author>
97 
98  <author initials="P." surname="Leach" fullname="Paul J. Leach">
99    <organization abbrev="Microsoft">Microsoft Corporation</organization>
100    <address>
101      <postal>
102        <street>1 Microsoft Way</street>
103        <city>Redmond</city>
104        <region>WA</region>
105        <code>98052</code>
106      </postal>
107      <email>paulle@microsoft.com</email>
108    </address>
109  </author>
110   
111  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
112    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
113    <address>
114      <postal>
115        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
116        <street>The Stata Center, Building 32</street>
117        <street>32 Vassar Street</street>
118        <city>Cambridge</city>
119        <region>MA</region>
120        <code>02139</code>
121        <country>USA</country>
122      </postal>
123      <email>timbl@w3.org</email>
124      <uri>http://www.w3.org/People/Berners-Lee/</uri>
125    </address>
126  </author>
127
128  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
129    <organization abbrev="W3C">World Wide Web Consortium</organization>
130    <address>
131      <postal>
132        <street>W3C / ERCIM</street>
133        <street>2004, rte des Lucioles</street>
134        <city>Sophia-Antipolis</city>
135        <region>AM</region>
136        <code>06902</code>
137        <country>France</country>
138      </postal>
139      <email>ylafon@w3.org</email>
140      <uri>http://www.raubacapeu.net/people/yves/</uri>
141    </address>
142  </author>
143
144  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
145    <organization abbrev="greenbytes">greenbytes GmbH</organization>
146    <address>
147      <postal>
148        <street>Hafenweg 16</street>
149        <city>Muenster</city><region>NW</region><code>48155</code>
150        <country>Germany</country>
151      </postal>
152      <phone>+49 251 2807760</phone>
153      <facsimile>+49 251 2807761</facsimile>
154      <email>julian.reschke@greenbytes.de</email>
155      <uri>http://greenbytes.de/tech/webdav/</uri>
156    </address>
157  </author>
158
159  <date month="April" year="2011" day="18"/>
160  <workgroup>HTTPbis Working Group</workgroup>
161
162<abstract>
163<t>
164   The Hypertext Transfer Protocol (HTTP) is an application-level
165   protocol for distributed, collaborative, hypermedia information
166   systems. HTTP has been in use by the World Wide Web global information
167   initiative since 1990. This document is Part 2 of the seven-part specification
168   that defines the protocol referred to as "HTTP/1.1" and, taken together,
169   obsoletes RFC 2616.  Part 2 defines the semantics of HTTP messages
170   as expressed by request methods, request header fields, response status codes,
171   and response header fields.
172</t>
173</abstract>
174
175<note title="Editorial Note (To be removed by RFC Editor)">
176  <t>
177    Discussion of this draft should take place on the HTTPBIS working group
178    mailing list (ietf-http-wg@w3.org), which is archived at
179    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
180  </t>
181  <t>
182    The current issues list is at
183    <eref target="http://tools.ietf.org/wg/httpbis/trac/report/3"/> and related
184    documents (including fancy diffs) can be found at
185    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
186  </t>
187  <t>
188    The changes in this draft are summarized in <xref target="changes.since.13"/>.
189  </t>
190</note>
191</front>
192<middle>
193<section title="Introduction" anchor="introduction">
194<t>
195   This document defines HTTP/1.1 request and response semantics.  Each HTTP
196   message, as defined in <xref target="Part1"/>, is in the form of either a request or
197   a response.  An HTTP server listens on a connection for HTTP requests and
198   responds to each request, in the order received on that connection, with
199   one or more HTTP response messages.  This document defines the commonly
200   agreed upon semantics of the HTTP uniform interface, the intentions defined
201   by each request method, and the various response messages that might be
202   expected as a result of applying that method to the target resource.
203</t>
204<t>
205   This document is currently disorganized in order to minimize the changes
206   between drafts and enable reviewers to see the smaller errata changes.
207   A future draft will reorganize the sections to better reflect the content.
208   In particular, the sections will be ordered according to the typical
209   processing of an HTTP request message (after message parsing): resource
210   mapping, methods, request modifying header fields, response status,
211   status modifying header fields, and resource metadata.  The current mess
212   reflects how widely dispersed these topics and associated requirements
213   had become in <xref target="RFC2616"/>.
214</t>
215
216<section title="Requirements" anchor="intro.requirements">
217<t>
218   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
219   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
220   document are to be interpreted as described in <xref target="RFC2119"/>.
221</t>
222<t>
223   An implementation is not compliant if it fails to satisfy one or more
224   of the "MUST" or "REQUIRED" level requirements for the protocols it
225   implements. An implementation that satisfies all the "MUST" or "REQUIRED"
226   level and all the "SHOULD" level requirements for its protocols is said
227   to be "unconditionally compliant"; one that satisfies all the "MUST"
228   level requirements but not all the "SHOULD" level requirements for its
229   protocols is said to be "conditionally compliant".
230</t>
231</section>
232
233<section title="Syntax Notation" anchor="notation">
234 
235 
236 
237 
238 
239<t>
240  This specification uses the ABNF syntax defined in Section 1.2 of <xref target="Part1"/> (which
241  extends the syntax defined in <xref target="RFC5234"/> with a list rule).
242  <xref target="collected.abnf"/> shows the collected ABNF, with the list
243  rule expanded.
244</t>
245<t>
246  The following core rules are included by
247  reference, as defined in <xref target="RFC5234"/>, Appendix B.1:
248  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
249  DIGIT (decimal 0-9), DQUOTE (double quote),
250  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
251  OCTET (any 8-bit sequence of data), SP (space),
252  VCHAR (any visible USASCII character),
253  and WSP (whitespace).
254</t>
255
256<section title="Core Rules" anchor="core.rules">
257 
258 
259 
260 
261 
262<t>
263  The core rules below are defined in Section 1.2.2 of <xref target="Part1"/>:
264</t>
265<figure><artwork type="abnf2616"><![CDATA[
266  quoted-string = <quoted-string, defined in [Part1], Section 1.2.2>
267  token         = <token, defined in [Part1], Section 1.2.2>
268  OWS           = <OWS, defined in [Part1], Section 1.2.2>
269  RWS           = <RWS, defined in [Part1], Section 1.2.2>
270  obs-text      = <obs-text, defined in [Part1], Section 1.2.2>
271]]></artwork></figure>
272</section>
273
274<section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
275 
276 
277 
278 
279 
280 
281<t>
282  The ABNF rules below are defined in other parts:
283</t>
284<figure><artwork type="abnf2616"><![CDATA[
285  absolute-URI  = <absolute-URI, defined in [Part1], Section 2.6>
286  comment       = <comment, defined in [Part1], Section 3.2>
287  HTTP-date     = <HTTP-date, defined in [Part1], Section 6.1>
288  partial-URI   = <partial-URI, defined in [Part1], Section 2.6>
289  product       = <product, defined in [Part1], Section 6.3>
290  URI-reference = <URI-reference, defined in [Part1], Section 2.6>
291]]></artwork></figure>
292</section>
293</section>
294</section>
295
296<section title="Method" anchor="method">
297 
298 
299<t>
300   The Method token indicates the request method to be performed on the target
301   resource (Section 4.3 of <xref target="Part1"/>). The method is case-sensitive.
302</t>
303<figure><iref primary="true" item="Grammar" subitem="Method"/><artwork type="abnf2616"><![CDATA[
304  Method         = token
305]]></artwork></figure>
306<t>
307   The list of methods allowed by a resource can be specified in an
308   Allow header field (<xref target="header.allow"/>). The status code of the response
309   always notifies the client whether a method is currently allowed on a
310   resource, since the set of allowed methods can change dynamically. An
311   origin server SHOULD respond with the status code 405 (Method Not Allowed)
312   if the method is known by the origin server but not allowed for the
313   resource, and 501 (Not Implemented) if the method is
314   unrecognized or not implemented by the origin server. The methods GET
315   and HEAD MUST be supported by all general-purpose servers. All other
316   methods are OPTIONAL; however, if the above methods are implemented,
317   they MUST be implemented with the same semantics as those specified
318   in <xref target="method.definitions"/>.
319</t>
320
321<section title="Overview of Methods" anchor="overview.of.methods">
322<t>
323  The methods listed below are defined in <xref target="method.definitions"/>.
324</t>
325<texttable align="left">
326  <ttcol>Method Name</ttcol><ttcol>Defined in...</ttcol>
327 
328  <c>OPTIONS</c> <c><xref target="OPTIONS"/></c>
329  <c>GET</c> <c><xref target="GET"/></c>
330  <c>HEAD</c> <c><xref target="HEAD"/></c>
331  <c>POST</c> <c><xref target="POST"/></c>
332  <c>PUT</c> <c><xref target="PUT"/></c>
333  <c>DELETE</c> <c><xref target="DELETE"/></c>
334  <c>TRACE</c> <c><xref target="TRACE"/></c>
335  <c>CONNECT</c> <c><xref target="CONNECT"/></c>
336</texttable>
337<t>
338  Note that this list is not exhaustive — it does not include request methods defined
339  in other specifications.
340</t>
341</section>
342
343<section title="Method Registry" anchor="method.registry">
344<t>
345  The HTTP Method Registry defines the name space for the Method token in the
346  Request line of an HTTP request.
347</t>
348<t>
349  Registrations MUST include the following fields:
350  <list style="symbols">
351    <t>Method Name (see <xref target="method"/>)</t>
352    <t>Safe ("yes" or "no", see <xref target="safe.methods"/>)</t>
353    <t>Pointer to specification text</t>
354  </list>
355</t>
356<t>
357  Values to be added to this name space are subject to IETF review
358  (<xref target="RFC5226"/>, Section 4.1).
359</t>
360<t>
361  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-methods"/>.
362</t>
363
364<section title="Considerations for New Methods" anchor="considerations.for.new.methods">
365<t>
366   When it is necessary to express new semantics for a HTTP request that
367   aren't specific to a single application or media type, and currently defined
368   methods are inadequate, it may be appropriate to register a new method.
369</t>
370<t>
371   HTTP methods are generic; that is, they are potentially applicable to any
372   resource, not just one particular media type, "type" of resource, or
373   application. As such, it is preferred that new HTTP methods be registered
374   in a document that isn't specific to a single application, so that this is
375   clear.
376</t>
377<t>
378   Due to the parsing rules defined in Section 3.3 of <xref target="Part1"/>, definitions of HTTP
379   methods cannot prohibit the presence of a message-body on either the request
380   or the response message (with responses to HEAD requests being the single
381   exception). Definitions of new methods cannot change this rule, but they can
382   specify that only zero-length bodies (as opposed to absent bodies) are allowed.
383</t>
384<t>
385   New method definitions need to indicate whether they are safe (<xref target="safe.methods"/>), what semantics (if any) the request body has,
386   and whether they are idempotent (<xref target="idempotent.methods"/>).
387   They also need to state whether they can be cached (<xref target="Part6"/>); in
388   particular what conditions a cache may store the response, and under what
389   conditions such a stored response may be used to satisfy a subsequent
390   request.
391</t>
392</section>
393
394</section>
395</section>
396
397<section title="Request Header Fields" anchor="request.header.fields">
398 
399<t>
400   The request header fields allow the client to pass additional
401   information about the request, and about the client itself, to the
402   server. These fields act as request modifiers, with semantics
403   equivalent to the parameters on a programming language method
404   invocation.
405</t>
406<texttable align="left">
407  <ttcol>Header Field Name</ttcol>
408  <ttcol>Defined in...</ttcol>
409
410  <c>Accept</c> <c>Section 6.1 of <xref target="Part3"/></c>
411  <c>Accept-Charset</c> <c>Section 6.2 of <xref target="Part3"/></c>
412  <c>Accept-Encoding</c> <c>Section 6.3 of <xref target="Part3"/></c>
413  <c>Accept-Language</c> <c>Section 6.4 of <xref target="Part3"/></c>
414  <c>Authorization</c> <c>Section 4.1 of <xref target="Part7"/></c>
415  <c>Expect</c> <c><xref target="header.expect"/></c>
416  <c>From</c> <c><xref target="header.from"/></c>
417  <c>Host</c> <c>Section 9.4 of <xref target="Part1"/></c>
418  <c>If-Match</c> <c>Section 3.1 of <xref target="Part4"/></c>
419  <c>If-Modified-Since</c> <c>Section 3.3 of <xref target="Part4"/></c>
420  <c>If-None-Match</c> <c>Section 3.2 of <xref target="Part4"/></c>
421  <c>If-Range</c> <c>Section 5.3 of <xref target="Part5"/></c>
422  <c>If-Unmodified-Since</c> <c>Section 3.4 of <xref target="Part4"/></c>
423  <c>Max-Forwards</c> <c><xref target="header.max-forwards"/></c>
424  <c>Proxy-Authorization</c> <c>Section 4.3 of <xref target="Part7"/></c>
425  <c>Range</c> <c>Section 5.4 of <xref target="Part5"/></c>
426  <c>Referer</c> <c><xref target="header.referer"/></c>
427  <c>TE</c> <c>Section 9.5 of <xref target="Part1"/></c>
428  <c>User-Agent</c> <c><xref target="header.user-agent"/></c>
429</texttable>
430</section>
431
432<section title="Status Code and Reason Phrase" anchor="status.code.and.reason.phrase">
433 
434 
435 
436<t>
437   The Status-Code element is a 3-digit integer result code of the attempt to
438   understand and satisfy the request.
439</t>
440<t>
441   The Reason-Phrase is intended to give a short textual description of the
442   Status-Code and is intended for a human user. The client does not need
443   to examine or display the Reason-Phrase.
444</t>
445<figure><iref primary="true" item="Grammar" subitem="Status-Code"/><iref primary="true" item="Grammar" subitem="extension-code"/><iref primary="true" item="Grammar" subitem="Reason-Phrase"/><artwork type="abnf2616"><![CDATA[
446  Status-Code    = 3DIGIT
447  Reason-Phrase  = *( WSP / VCHAR / obs-text )
448]]></artwork></figure>
449<t>
450   HTTP status codes are extensible. HTTP applications are not required
451   to understand the meaning of all registered status codes, though such
452   understanding is obviously desirable. However, applications MUST
453   understand the class of any status code, as indicated by the first
454   digit, and treat any unrecognized response as being equivalent to the
455   x00 status code of that class, with the exception that an
456   unrecognized response MUST NOT be cached. For example, if an
457   unrecognized status code of 431 is received by the client, it can
458   safely assume that there was something wrong with its request and
459   treat the response as if it had received a 400 status code. In such
460   cases, user agents SHOULD present to the user the representation enclosed
461   with the response, since that representation is likely to include human-readable
462   information which will explain the unusual status.
463</t>
464
465<section title="Overview of Status Codes" anchor="overview.of.status.codes">
466<t> 
467   The status codes listed below are defined in <xref target="status.codes"/>
468   of this specification, Section 4 of <xref target="Part4"/>, Section 3 of <xref target="Part5"/>, and Section 3 of <xref target="Part7"/>.
469   The reason phrases listed here are only recommendations — they can be
470   replaced by local equivalents without affecting the protocol.
471</t>
472<texttable align="left">
473  <ttcol>Status-Code</ttcol>
474  <ttcol>Reason-Phrase</ttcol>
475  <ttcol>Defined in...</ttcol>
476 
477  <c>100</c> <c>Continue</c> <c><xref target="status.100"/></c>
478  <c>101</c> <c>Switching Protocols</c> <c><xref target="status.101"/></c>
479
480  <c>200</c> <c>OK</c> <c><xref target="status.200"/></c>
481  <c>201</c> <c>Created</c> <c><xref target="status.201"/></c>
482  <c>202</c> <c>Accepted</c> <c><xref target="status.202"/></c>
483  <c>203</c> <c>Non-Authoritative Information</c> <c><xref target="status.203"/></c>
484  <c>204</c> <c>No Content</c> <c><xref target="status.204"/></c>
485  <c>205</c> <c>Reset Content</c> <c><xref target="status.205"/></c>
486  <c>206</c> <c>Partial Content</c> <c>Section 3.1 of <xref target="Part5"/></c>
487
488  <c>300</c> <c>Multiple Choices</c> <c><xref target="status.300"/></c>
489  <c>301</c> <c>Moved Permanently</c> <c><xref target="status.301"/></c>
490  <c>302</c> <c>Found</c> <c><xref target="status.302"/></c>
491  <c>303</c> <c>See Other</c> <c><xref target="status.303"/></c>
492  <c>304</c> <c>Not Modified</c> <c>Section 4.1 of <xref target="Part4"/></c>
493  <c>305</c> <c>Use Proxy</c> <c><xref target="status.305"/></c>
494  <c>307</c> <c>Temporary Redirect</c> <c><xref target="status.307"/></c>
495
496  <c>400</c> <c>Bad Request</c> <c><xref target="status.400"/></c>
497  <c>401</c> <c>Unauthorized</c> <c>Section 3.1 of <xref target="Part7"/></c>
498  <c>402</c> <c>Payment Required</c> <c><xref target="status.402"/></c>
499  <c>403</c> <c>Forbidden</c> <c><xref target="status.403"/></c>
500  <c>404</c> <c>Not Found</c> <c><xref target="status.404"/></c>
501  <c>405</c> <c>Method Not Allowed</c> <c><xref target="status.405"/></c>
502  <c>406</c> <c>Not Acceptable</c> <c><xref target="status.406"/></c>
503  <c>407</c> <c>Proxy Authentication Required</c> <c>Section 3.2 of <xref target="Part7"/></c>
504  <c>408</c> <c>Request Time-out</c> <c><xref target="status.408"/></c>
505  <c>409</c> <c>Conflict</c> <c><xref target="status.409"/></c>
506  <c>410</c> <c>Gone</c> <c><xref target="status.410"/></c>
507  <c>411</c> <c>Length Required</c> <c><xref target="status.411"/></c>
508  <c>412</c> <c>Precondition Failed</c> <c>Section 4.2 of <xref target="Part4"/></c>
509  <c>413</c> <c>Request Entity Too Large</c> <c><xref target="status.413"/></c>
510  <c>414</c> <c>URI Too Long</c> <c><xref target="status.414"/></c>
511  <c>415</c> <c>Unsupported Media Type</c> <c><xref target="status.415"/></c>
512  <c>416</c> <c>Requested range not satisfiable</c> <c>Section 3.2 of <xref target="Part5"/></c>
513  <c>417</c> <c>Expectation Failed</c> <c><xref target="status.417"/></c>
514  <c>426</c> <c>Upgrade Required</c> <c><xref target="status.426"/></c>
515
516  <c>500</c> <c>Internal Server Error</c> <c><xref target="status.500"/></c>
517  <c>501</c> <c>Not Implemented</c> <c><xref target="status.501"/></c>
518  <c>502</c> <c>Bad Gateway</c> <c><xref target="status.502"/></c>
519  <c>503</c> <c>Service Unavailable</c> <c><xref target="status.503"/></c>
520  <c>504</c> <c>Gateway Time-out</c> <c><xref target="status.504"/></c>
521  <c>505</c> <c>HTTP Version not supported</c> <c><xref target="status.505"/></c>
522</texttable>
523<t>
524   Note that this list is not exhaustive — it does not include
525   extension status codes defined in other specifications.
526</t>
527</section>
528
529<section title="Status Code Registry" anchor="status.code.registry">
530<t>
531  The HTTP Status Code Registry defines the name space for the Status-Code
532  token in the Status-Line of an HTTP response.
533</t>
534<t>
535  Values to be added to this name space are subject to IETF review
536  (<xref target="RFC5226"/>, Section 4.1).
537</t>
538<t>
539  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>.
540</t>
541
542<section title="Considerations for New Status Codes" anchor="considerations.for.new.status.codes">
543<t>
544   When it is necessary to express new semantics for a HTTP response that
545   aren't specific to a single application or media type, and currently defined
546   status codes are inadequate, a new status code can be registered.
547</t>
548<t>
549   HTTP status codes are generic; that is, they are potentially applicable to
550   any resource, not just one particular media type, "type" of resource, or
551   application. As such, it is preferred that new HTTP status codes be
552   registered in a document that isn't specific to a single application, so
553   that this is clear.
554</t>
555<t>
556   Definitions of new HTTP status codes typically explain the request
557   conditions that produce a response containing the status code (e.g.,
558   combinations of request headers and/or method(s)), along with any
559   interactions with response headers (e.g., those that are required, those
560   that modify the semantics of the response).
561</t>
562<t>
563   New HTTP status codes are required to fall under one of the categories
564   defined in <xref target="status.codes"/>. To allow existing parsers to
565   properly handle them, new status codes cannot disallow a response body,
566   although they can mandate a zero-length response body. They can require the
567   presence of one or more particular HTTP response header(s).
568</t>
569<t>
570   Likewise, their definitions can specify that caches are allowed to use
571   heuristics to determine their freshness (see <xref target="Part6"/>; by default, it is
572   not allowed), and can define how to determine the resource which they
573   carry a representation for (see <xref target="identifying.response.associated.with.representation"/>; by default,
574   it is anonymous).
575</t>
576</section>
577
578</section>
579
580</section>
581
582<section title="Response Header Fields" anchor="response.header.fields">
583 
584<t>
585   The response header fields allow the server to pass additional
586   information about the response which cannot be placed in the Status-Line.
587   These header fields give information about the server and about
588   further access to the target resource (Section 4.3 of <xref target="Part1"/>).
589</t>
590<texttable align="left">
591  <ttcol>Header Field Name</ttcol><ttcol>Defined in...</ttcol>
592
593  <c>Accept-Ranges</c> <c>Section 5.1 of <xref target="Part5"/></c>
594  <c>Age</c> <c>Section 3.1 of <xref target="Part6"/></c>
595  <c>Allow</c> <c><xref target="header.allow"/></c>
596  <c>ETag</c> <c>Section 2.2 of <xref target="Part4"/></c>
597  <c>Location</c> <c><xref target="header.location"/></c>
598  <c>Proxy-Authenticate</c> <c>Section 4.2 of <xref target="Part7"/></c>
599  <c>Retry-After</c> <c><xref target="header.retry-after"/></c>
600  <c>Server</c> <c><xref target="header.server"/></c>
601  <c>Vary</c> <c>Section 3.5 of <xref target="Part6"/></c>
602  <c>WWW-Authenticate</c> <c>Section 4.4 of <xref target="Part7"/></c>
603</texttable>
604</section>
605
606<section title="Representation" anchor="representation">
607<t>
608   Request and Response messages MAY transfer a representation if not otherwise
609   restricted by the request method or response status code. A representation
610   consists of metadata (representation header fields) and data (representation
611   body).  When a complete or partial representation is enclosed in an HTTP message,
612   it is referred to as the payload of the message. HTTP representations
613   are defined in <xref target="Part3"/>.
614</t>
615<t>
616   A representation body is only present in a message when a message-body is
617   present, as described in Section 3.3 of <xref target="Part1"/>. The representation body is obtained
618   from the message-body by decoding any Transfer-Encoding that might
619   have been applied to ensure safe and proper transfer of the message.
620</t>
621
622<section title="Identifying the Resource Associated with a Representation" anchor="identifying.response.associated.with.representation">
623<t>
624   It is sometimes necessary to determine an identifier for the resource
625   associated with a representation.
626</t>
627<t>
628   An HTTP request representation, when present, is always associated with an
629   anonymous (i.e., unidentified) resource.
630</t>
631<t>
632   In the common case, an HTTP response is a representation of the target
633   resource (see Section 4.3 of <xref target="Part1"/>). However, this is not always the
634   case. To determine the URI of the resource a response is associated with,
635   the following rules are used (with the first applicable one being selected):
636</t>
637<t><list style="numbers">
638   <t>If the response status code is 200 or 203 and the request method was GET,
639   the response payload is a representation of the target resource.</t>
640   <t>If the response status code is 204, 206, or 304 and the request method was GET
641   or HEAD, the response payload is a partial representation of the target
642   resource (see Section 2.8 of <xref target="Part6"/>).</t>
643   <t>If the response has a Content-Location header field, and that URI is the same
644   as the effective request URI, the response payload is a representation of the
645   target resource.</t>
646   <t>If the response has a Content-Location header field, and that URI is not the
647   same as the effective request URI, then the response asserts that its
648   payload is a representation of the resource identified by the
649   Content-Location URI. However, such an assertion cannot be trusted unless
650   it can be verified by other means (not defined by HTTP).</t>
651   <t>Otherwise, the response is a representation of an anonymous (i.e.,
652   unidentified) resource.</t>
653</list></t>
654<t>
655  <cref anchor="TODO-req-uri">
656   The comparison function is going to have to be defined somewhere,
657   because we already need to compare URIs for things like cache invalidation.</cref>
658</t>
659</section>
660
661</section>
662
663
664<section title="Method Definitions" anchor="method.definitions">
665<t>
666   The set of common request methods for HTTP/1.1 is defined below. Although
667   this set can be expanded, additional methods cannot be assumed to
668   share the same semantics for separately extended clients and servers.
669</t>
670
671<section title="Safe and Idempotent Methods" anchor="safe.and.idempotent">
672
673<section title="Safe Methods" anchor="safe.methods">
674<iref item="Safe Methods" primary="true"/>
675<t>
676   Implementors need to be aware that the software represents the user in
677   their interactions over the Internet, and need to allow
678   the user to be aware of any actions they take which might have an
679   unexpected significance to themselves or others.
680</t>
681<t>
682   In particular, the convention has been established that the GET, HEAD,
683   OPTIONS, and TRACE request methods SHOULD NOT have the significance
684   of taking an action other than retrieval. These request methods ought
685   to be considered "safe".
686   This allows user agents to represent other methods, such as POST, PUT
687   and DELETE, in a special way, so that the user is made aware of the
688   fact that a possibly unsafe action is being requested.
689</t>
690<t>
691   Naturally, it is not possible to ensure that the server does not
692   generate side-effects as a result of performing a GET request; in
693   fact, some dynamic resources consider that a feature. The important
694   distinction here is that the user did not request the side-effects,
695   so therefore cannot be held accountable for them.
696</t>
697</section>
698
699<section title="Idempotent Methods" anchor="idempotent.methods">
700<iref item="Idempotent Methods" primary="true"/>
701<t>
702   Request methods can also have the property of "idempotence" in that,
703   aside from error or expiration issues, the intended effect of multiple
704   identical requests is the same as for a single request.
705   PUT, DELETE, and all safe request methods are idempotent.
706   It is important to note that idempotence refers only to changes
707   requested by the client: a server is free to change its state due
708   to multiple requests for the purpose of tracking those requests,
709   versioning of results, etc.
710</t>
711</section>
712</section>
713
714<section title="OPTIONS" anchor="OPTIONS">
715 
716  <iref primary="true" item="OPTIONS method"/>
717  <iref primary="true" item="Methods" subitem="OPTIONS"/>
718<t>
719   The OPTIONS method requests information about the
720   communication options available on the request/response chain
721   identified by the effective request URI. This method allows a client to
722   determine the options and/or requirements associated with a resource,
723   or the capabilities of a server, without implying a resource action
724   or initiating a resource retrieval.
725</t>
726<t>
727   Responses to the OPTIONS method are not cacheable.
728</t>
729<t>
730   If the OPTIONS request includes a message-body (as indicated by the
731   presence of Content-Length or Transfer-Encoding), then the media type
732   MUST be indicated by a Content-Type field. Although this
733   specification does not define any use for such a body, future
734   extensions to HTTP might use the OPTIONS body to make more detailed
735   queries on the server.
736</t>
737<t>
738   If the request-target is an asterisk ("*"), the OPTIONS request is
739   intended to apply to the server in general rather than to a specific
740   resource. Since a server's communication options typically depend on
741   the resource, the "*" request is only useful as a "ping" or "no-op"
742   type of method; it does nothing beyond allowing the client to test
743   the capabilities of the server. For example, this can be used to test
744   a proxy for HTTP/1.1 compliance (or lack thereof).
745</t>
746<t>
747   If the request-target is not an asterisk, the OPTIONS request applies
748   only to the options that are available when communicating with that
749   resource.
750</t>
751<t>
752   A 200 response SHOULD include any header fields that indicate
753   optional features implemented by the server and applicable to that
754   resource (e.g., Allow), possibly including extensions not defined by
755   this specification. The response body, if any, SHOULD also include
756   information about the communication options. The format for such a
757   body is not defined by this specification, but might be defined by
758   future extensions to HTTP. Content negotiation MAY be used to select
759   the appropriate response format. If no response body is included, the
760   response MUST include a Content-Length field with a field-value of
761   "0".
762</t>
763<t>
764   The Max-Forwards header field MAY be used to target a
765   specific proxy in the request chain (see <xref target="header.max-forwards"/>).
766   If no Max-Forwards field is present in the request, then the forwarded
767   request MUST NOT include a Max-Forwards field.
768</t>
769</section>
770
771<section title="GET" anchor="GET">
772 
773  <iref primary="true" item="GET method"/>
774  <iref primary="true" item="Methods" subitem="GET"/>
775<t>
776   The GET method requests transfer of a current representation of
777   the target resource.
778</t>
779<t>   
780   If the target resource is a data-producing process, it is the
781   produced data which shall be returned as the representation in the response and not
782   the source text of the process, unless that text happens to be the output of
783   the process.
784</t>
785<t>
786   The semantics of the GET method change to a "conditional GET" if the
787   request message includes an If-Modified-Since, If-Unmodified-Since,
788   If-Match, If-None-Match, or If-Range header field. A conditional GET
789   requests that the representation be transferred only under the
790   circumstances described by the conditional header field(s). The
791   conditional GET request is intended to reduce unnecessary network
792   usage by allowing cached representations to be refreshed without requiring
793   multiple requests or transferring data already held by the client.
794</t>
795<t>
796   The semantics of the GET method change to a "partial GET" if the
797   request message includes a Range header field. A partial GET requests
798   that only part of the representation be transferred, as described in Section 5.4 of <xref target="Part5"/>.
799   The partial GET request is intended to reduce unnecessary
800   network usage by allowing partially-retrieved representations to be
801   completed without transferring data already held by the client.
802</t>
803<t>
804   Bodies on GET requests have no defined semantics. Note that sending a body
805   on a GET request might cause some existing implementations to reject the
806   request.
807</t>
808<t>
809   The response to a GET request is cacheable and MAY be used to satisfy
810   subsequent GET and HEAD requests (see <xref target="Part6"/>).
811</t>
812<t>
813   See <xref target="encoding.sensitive.information.in.uris"/> for security considerations when used for forms.
814</t>
815</section>
816
817<section title="HEAD" anchor="HEAD">
818 
819  <iref primary="true" item="HEAD method"/>
820  <iref primary="true" item="Methods" subitem="HEAD"/>
821<t>
822   The HEAD method is identical to GET except that the server MUST NOT
823   return a message-body in the response. The metadata contained
824   in the HTTP header fields in response to a HEAD request SHOULD be identical
825   to the information sent in response to a GET request. This method can
826   be used for obtaining metadata about the representation implied by the
827   request without transferring the representation body. This method is
828   often used for testing hypertext links for validity, accessibility,
829   and recent modification.
830</t>
831<t>
832   The response to a HEAD request is cacheable and MAY be used to satisfy
833   a subsequent HEAD request; see <xref target="Part6"/>. It also MAY be used to update a previously cached
834   representation from that resource; if the new field values
835   indicate that the cached representation differs from the current representation (as
836   would be indicated by a change in Content-Length, Content-MD5, ETag
837   or Last-Modified), then the cache MUST treat the cache entry as
838   stale.
839</t>
840<t>
841   Bodies on HEAD requests have no defined semantics. Note that sending a body
842   on a HEAD request might cause some existing implementations to reject the
843   request.
844</t>
845</section>
846
847<section title="POST" anchor="POST">
848  <iref primary="true" item="POST method"/>
849  <iref primary="true" item="Methods" subitem="POST"/>
850<t>
851   The POST method requests that the origin server accept the
852   representation enclosed in the request as data to be processed by the
853   target resource. POST is designed to allow a uniform method to cover the
854   following functions:
855  <list style="symbols">
856    <t>
857      Annotation of existing resources;
858    </t>
859    <t>
860        Posting a message to a bulletin board, newsgroup, mailing list,
861        or similar group of articles;
862    </t>
863    <t>
864        Providing a block of data, such as the result of submitting a
865        form, to a data-handling process;
866    </t>
867    <t>
868        Extending a database through an append operation.
869    </t>
870  </list>
871</t>
872<t>
873   The actual function performed by the POST method is determined by the
874   server and is usually dependent on the effective request URI.
875</t>
876<t>
877   The action performed by the POST method might not result in a
878   resource that can be identified by a URI. In this case, either 200
879   (OK) or 204 (No Content) is the appropriate response status code,
880   depending on whether or not the response includes a representation that
881   describes the result.
882</t>
883<t>
884   If a resource has been created on the origin server, the response
885   SHOULD be 201 (Created) and contain a representation which describes the
886   status of the request and refers to the new resource, and a Location
887   header field (see <xref target="header.location"/>).
888</t>
889<t>
890   Responses to POST requests are only cacheable when they
891   include explicit freshness information (see Section 2.3.1 of <xref target="Part6"/>). A
892   cached POST response with a Content-Location header field
893   (see Section 6.7 of <xref target="Part3"/>) whose value is the effective
894   Request URI MAY be used to satisfy subsequent GET and HEAD requests.
895</t>
896<t>
897   Note that POST caching is not widely implemented.
898   However, the 303 (See Other) response can be used to direct the
899   user agent to retrieve a cacheable resource.
900</t>
901</section>
902
903<section title="PUT" anchor="PUT">
904  <iref primary="true" item="PUT method"/>
905  <iref primary="true" item="Methods" subitem="PUT"/>
906<t>
907   The PUT method requests that the state of the target resource
908   be created or replaced with the state defined by the representation
909   enclosed in the request message payload.  A successful PUT of a given
910   representation would suggest that a subsequent GET on that same target
911   resource will result in an equivalent representation being returned in
912   a 200 (OK) response.  However, there is no guarantee that such a state
913   change will be observable, since the target resource might be acted
914   upon by other user agents in parallel, or might be subject to dynamic
915   processing by the origin server, before any subsequent GET is received.
916   A successful response only implies that the user agent's intent was
917   achieved at the time of its processing by the origin server.
918</t>
919<t>   
920   If the target resource does not have a current representation and
921   the PUT successfully creates one, then the origin server MUST inform
922   the user agent by sending a 201 (Created) response.  If the target
923   resource does have a current representation and that representation is
924   successfully modified in accordance with the state of the enclosed
925   representation, then either a 200 (OK) or 204 (No Content) response
926   SHOULD be sent to indicate successful completion of the request.
927</t>
928<t>
929   Unrecognized header fields SHOULD be ignored (i.e., not saved
930   as part of the resource state).
931</t>
932<t>
933   An origin server SHOULD verify that the PUT representation is
934   consistent with any constraints which the server has for the target
935   resource that cannot or will not be changed by the PUT.  This is
936   particularly important when the origin server uses internal
937   configuration information related to the URI in order to set the
938   values for representation metadata on GET responses.  When a PUT
939   representation is inconsistent with the target resource, the origin
940   server SHOULD either make them consistent, by transforming the
941   representation or changing the resource configuration, or respond
942   with an appropriate error message containing sufficient information
943   to explain why the representation is unsuitable.  The 409 (Conflict)
944   or 415 (Unsupported Media Type) status codes are suggested, with the
945   latter being specific to constraints on Content-Type values.
946</t>
947<t>
948   For example, if the target resource is configured to always have a
949   Content-Type of "text/html" and the representation being PUT has a
950   Content-Type of "image/jpeg", then the origin server SHOULD do one of:
951   (a) reconfigure the target resource to reflect the new media type;
952   (b) transform the PUT representation to a format consistent with that
953   of the resource before saving it as the new resource state; or,
954   (c) reject the request with a 415 response indicating that the target
955   resource is limited to "text/html", perhaps including a link to a
956   different resource that would be a suitable target for the new
957   representation.
958</t>
959<t>
960   HTTP does not define exactly how a PUT method affects the state
961   of an origin server beyond what can be expressed by the intent of
962   the user agent request and the semantics of the origin server response.
963   It does not define what a resource might be, in any sense of that
964   word, beyond the interface provided via HTTP.  It does not define
965   how resource state is "stored", nor how such storage might change
966   as a result of a change in resource state, nor how the origin server
967   translates resource state into representations.  Generally speaking,
968   all implementation details behind the resource interface are
969   intentionally hidden by the server.
970</t>
971<t>
972   The fundamental difference between the POST and PUT methods is
973   highlighted by the different intent for the target resource.
974   The target resource in a POST request is intended to handle the
975   enclosed representation as a data-accepting process, such as for
976   a gateway to some other protocol or a document that accepts annotations.
977   In contrast, the target resource in a PUT request is intended to
978   take the enclosed representation as a new or replacement value.
979   Hence, the intent of PUT is idempotent and visible to intermediaries,
980   even though the exact effect is only known by the origin server.
981</t>
982<t>
983   Proper interpretation of a PUT request presumes that the user agent
984   knows what target resource is desired.  A service that is intended
985   to select a proper URI on behalf of the client, after receiving
986   a state-changing request, SHOULD be implemented using the POST
987   method rather than PUT.  If the origin server will not make the
988   requested PUT state change to the target resource and instead
989   wishes to have it applied to a different resource, such as when the
990   resource has been moved to a different URI, then the origin server
991   MUST send a 301 (Moved Permanently) response; the user agent MAY
992   then make its own decision regarding whether or not to redirect the
993   request.
994</t>
995<t>
996   A PUT request applied to the target resource MAY have side-effects
997   on other resources.  For example, an article might have a URI for
998   identifying "the current version" (a resource) which is separate
999   from the URIs identifying each particular version (different
1000   resources that at one point shared the same state as the current version
1001   resource).  A successful PUT request on "the current version" URI might
1002   therefore create a new version resource in addition to changing the
1003   state of the target resource, and might also cause links to be added
1004   between the related resources.
1005</t>
1006<t>
1007   An origin server SHOULD reject any PUT request that contains a
1008   Content-Range header field, since it might be misinterpreted as
1009   partial content (or might be partial content that is being mistakenly
1010   PUT as a full representation).  Partial content updates are
1011   possible by targeting a separately identified resource with state
1012   that overlaps a portion of the larger resource, or by using a
1013   different method that has been specifically defined for partial
1014   updates (for example, the PATCH method defined in
1015   <xref target="RFC5789"/>).
1016</t>
1017<t>
1018   Responses to the PUT method are not cacheable. If a PUT request passes
1019   through a cache that has one or more stored responses for the effective
1020   request URI, those stored responses will be invalidated (see
1021   Section 2.5 of <xref target="Part6"/>).
1022</t>
1023</section>
1024
1025<section title="DELETE" anchor="DELETE">
1026  <iref primary="true" item="DELETE method"/>
1027  <iref primary="true" item="Methods" subitem="DELETE"/>
1028<t>
1029   The DELETE method requests that the origin server delete the target
1030   resource. This method MAY be overridden by
1031   human intervention (or other means) on the origin server. The client cannot
1032   be guaranteed that the operation has been carried out, even if the
1033   status code returned from the origin server indicates that the action
1034   has been completed successfully. However, the server SHOULD NOT
1035   indicate success unless, at the time the response is given, it
1036   intends to delete the resource or move it to an inaccessible
1037   location.
1038</t>
1039<t>
1040   A successful response SHOULD be 200 (OK) if the response includes an
1041   representation describing the status, 202 (Accepted) if the action has not
1042   yet been enacted, or 204 (No Content) if the action has been enacted
1043   but the response does not include a representation.
1044</t>
1045<t>
1046   Bodies on DELETE requests have no defined semantics. Note that sending a body
1047   on a DELETE request might cause some existing implementations to reject the
1048   request.
1049</t>
1050<t>
1051   Responses to the DELETE method are not cacheable. If a DELETE request
1052   passes through a cache that has one or more stored responses for the
1053   effective request URI, those stored responses will be invalidated (see
1054   Section 2.5 of <xref target="Part6"/>).
1055</t>
1056</section>
1057
1058<section title="TRACE" anchor="TRACE">
1059 
1060  <iref primary="true" item="TRACE method"/>
1061  <iref primary="true" item="Methods" subitem="TRACE"/>
1062<t>
1063   The TRACE method requests a remote, application-layer loop-back
1064   of the request message. The final recipient of the request
1065   SHOULD reflect the message received back to the client as the
1066   message-body of a 200 (OK) response. The final recipient is either the
1067   origin server or the first proxy to receive a Max-Forwards
1068   value of zero (0) in the request (see <xref target="header.max-forwards"/>).
1069   A TRACE request MUST NOT include a message-body.
1070</t>
1071<t>
1072   TRACE allows the client to see what is being received at the other
1073   end of the request chain and use that data for testing or diagnostic
1074   information. The value of the Via header field (Section 9.9 of <xref target="Part1"/>) is of
1075   particular interest, since it acts as a trace of the request chain.
1076   Use of the Max-Forwards header field allows the client to limit the
1077   length of the request chain, which is useful for testing a chain of
1078   proxies forwarding messages in an infinite loop.
1079</t>
1080<t>
1081   If the request is valid, the response SHOULD have a Content-Type of
1082   "message/http" (see Section 10.3.1 of <xref target="Part1"/>) and contain a message-body
1083   that encloses a copy of the entire request message.
1084   Responses to the TRACE method are not cacheable.
1085</t>
1086</section>
1087
1088<section title="CONNECT" anchor="CONNECT">
1089  <iref primary="true" item="CONNECT method"/>
1090  <iref primary="true" item="Methods" subitem="CONNECT"/>
1091<t>
1092   The CONNECT method requests that the proxy establish a tunnel
1093   to the request-target and then restrict its behavior to blind
1094   forwarding of packets until the connection is closed.
1095</t>
1096<t>
1097   When using CONNECT, the request-target MUST use the authority form
1098   (Section 4.1.2 of <xref target="Part1"/>); i.e., the request-target consists of only the
1099   host name and port number of the tunnel destination, separated by a colon.
1100   For example,
1101</t>
1102<figure><artwork type="message/http; msgtype=&#34;request&#34;"><![CDATA[
1103  CONNECT server.example.com:80 HTTP/1.1
1104  Host: server.example.com:80
1105 
1106  ]]></artwork></figure>
1107<t>
1108   Other HTTP mechanisms can be used normally with the CONNECT method —
1109   except end-to-end protocol Upgrade requests, since the
1110   tunnel must be established first.
1111</t>
1112<t>
1113   For example, proxy authentication might be used to establish the
1114   authority to create a tunnel:
1115</t>
1116<figure><artwork type="message/http; msgtype=&#34;request&#34;"><![CDATA[
1117  CONNECT server.example.com:80 HTTP/1.1
1118  Host: server.example.com:80
1119  Proxy-Authorization: basic aGVsbG86d29ybGQ=
1120 
1121  ]]></artwork></figure>
1122<t>
1123   Bodies on CONNECT requests have no defined semantics. Note that sending a body
1124   on a CONNECT request might cause some existing implementations to reject the
1125   request.
1126</t>
1127<t>
1128   Like any other pipelined HTTP/1.1 request, data to be tunnel may be
1129   sent immediately after the blank line. The usual caveats also apply:
1130   data may be discarded if the eventual response is negative, and the
1131   connection may be reset with no response if more than one TCP segment
1132   is outstanding.
1133</t>
1134
1135<section title="Establishing a Tunnel with CONNECT">
1136<t>
1137   Any successful (2xx) response to a CONNECT request indicates that the
1138   proxy has established a connection to the requested host and port,
1139   and has switched to tunneling the current connection to that server
1140   connection.
1141</t>
1142<t>
1143   It may be the case that the proxy itself can only reach the requested
1144   origin server through another proxy.  In this case, the first proxy
1145   SHOULD make a CONNECT request of that next proxy, requesting a tunnel
1146   to the authority.  A proxy MUST NOT respond with any 2xx status code
1147   unless it has either a direct or tunnel connection established to the
1148   authority.
1149</t>
1150<t>
1151   An origin server which receives a CONNECT request for itself MAY
1152   respond with a 2xx status code to indicate that a connection is
1153   established.
1154</t>
1155<t>
1156   If at any point either one of the peers gets disconnected, any
1157   outstanding data that came from that peer will be passed to the other
1158   one, and after that also the other connection will be terminated by
1159   the proxy. If there is outstanding data to that peer undelivered,
1160   that data will be discarded.
1161</t>
1162
1163</section>
1164</section>
1165</section>
1166
1167
1168<section title="Status Code Definitions" anchor="status.codes">
1169<t>
1170   Each Status-Code is described below, including any metadata required
1171   in the response.
1172</t>
1173
1174<section title="Informational 1xx" anchor="status.1xx">
1175<t>
1176   This class of status code indicates a provisional response,
1177   consisting only of the Status-Line and optional header fields, and is
1178   terminated by an empty line. There are no required header fields for this
1179   class of status code. Since HTTP/1.0 did not define any 1xx status
1180   codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client
1181   except under experimental conditions.
1182</t>
1183<t>
1184   A client MUST be prepared to accept one or more 1xx status responses
1185   prior to a regular response, even if the client does not expect a 100
1186   (Continue) status message. Unexpected 1xx status responses MAY be
1187   ignored by a user agent.
1188</t>
1189<t>
1190   Proxies MUST forward 1xx responses, unless the connection between the
1191   proxy and its client has been closed, or unless the proxy itself
1192   requested the generation of the 1xx response. (For example, if a
1193   proxy adds a "Expect: 100-continue" field when it forwards a request,
1194   then it need not forward the corresponding 100 (Continue)
1195   response(s).)
1196</t>
1197
1198<section title="100 Continue" anchor="status.100">
1199  <iref primary="true" item="100 Continue (status code)"/>
1200  <iref primary="true" item="Status Codes" subitem="100 Continue"/>
1201<t>
1202   The client SHOULD continue with its request. This interim response is
1203   used to inform the client that the initial part of the request has
1204   been received and has not yet been rejected by the server. The client
1205   SHOULD continue by sending the remainder of the request or, if the
1206   request has already been completed, ignore this response. The server
1207   MUST send a final response after the request has been completed. See
1208   Section 7.2.3 of <xref target="Part1"/> for detailed discussion of the use and handling of this
1209   status code.
1210</t>
1211</section>
1212
1213<section title="101 Switching Protocols" anchor="status.101">
1214  <iref primary="true" item="101 Switching Protocols (status code)"/>
1215  <iref primary="true" item="Status Codes" subitem="101 Switching Protocols"/>
1216<t>
1217   The server understands and is willing to comply with the client's
1218   request, via the Upgrade message header field (Section 9.8 of <xref target="Part1"/>), for a
1219   change in the application protocol being used on this connection. The
1220   server will switch protocols to those defined by the response's
1221   Upgrade header field immediately after the empty line which
1222   terminates the 101 response.
1223</t>
1224<t>
1225   The protocol SHOULD be switched only when it is advantageous to do
1226   so. For example, switching to a newer version of HTTP is advantageous
1227   over older versions, and switching to a real-time, synchronous
1228   protocol might be advantageous when delivering resources that use
1229   such features.
1230</t>
1231</section>
1232</section>
1233
1234<section title="Successful 2xx" anchor="status.2xx">
1235<t>
1236   This class of status code indicates that the client's request was
1237   successfully received, understood, and accepted.
1238</t>
1239
1240<section title="200 OK" anchor="status.200">
1241  <iref primary="true" item="200 OK (status code)"/>
1242  <iref primary="true" item="Status Codes" subitem="200 OK"/>
1243<t>
1244   The request has succeeded. The payload returned with the response
1245   is dependent on the method used in the request, for example:
1246  <list style="hanging">
1247    <t hangText="GET">
1248          a representation of the target resource is sent in the response;
1249    </t>
1250    <t hangText="HEAD">
1251          the same representation as GET, except without the message-body;
1252    </t>
1253    <t hangText="POST">
1254      a representation describing or containing the result of the action;
1255    </t>
1256    <t hangText="TRACE">
1257      a representation containing the request message as received by the
1258      end server.
1259    </t>
1260  </list>
1261</t>
1262<t>
1263   Caches MAY use a heuristic (see Section 2.3.1.1 of <xref target="Part6"/>) to determine
1264   freshness for 200 responses.
1265</t>
1266</section>
1267
1268<section title="201 Created" anchor="status.201">
1269  <iref primary="true" item="201 Created (status code)"/>
1270  <iref primary="true" item="Status Codes" subitem="201 Created"/>
1271<t>
1272   The request has been fulfilled and has resulted in a new resource being
1273   created. The newly created resource can be referenced by the URI(s)
1274   returned in the payload of the response, with the most specific URI
1275   for the resource given by a Location header field. The response
1276   SHOULD include a payload containing a list of resource
1277   characteristics and location(s) from which the user or user agent can
1278   choose the one most appropriate. The payload format is specified by
1279   the media type given in the Content-Type header field. The origin
1280   server MUST create the resource before returning the 201 status code.
1281   If the action cannot be carried out immediately, the server SHOULD
1282   respond with 202 (Accepted) response instead.
1283</t>
1284<t>
1285   A 201 response MAY contain an ETag response header field indicating
1286   the current value of the entity-tag for the representation of the resource
1287   just created (see Section 2.2 of <xref target="Part4"/>).
1288</t>
1289</section>
1290
1291<section title="202 Accepted" anchor="status.202">
1292  <iref primary="true" item="202 Accepted (status code)"/>
1293  <iref primary="true" item="Status Codes" subitem="202 Accepted"/>
1294<t>
1295   The request has been accepted for processing, but the processing has
1296   not been completed.  The request might or might not eventually be
1297   acted upon, as it might be disallowed when processing actually takes
1298   place. There is no facility for re-sending a status code from an
1299   asynchronous operation such as this.
1300</t>
1301<t>
1302   The 202 response is intentionally non-committal. Its purpose is to
1303   allow a server to accept a request for some other process (perhaps a
1304   batch-oriented process that is only run once per day) without
1305   requiring that the user agent's connection to the server persist
1306   until the process is completed. The representation returned with this
1307   response SHOULD include an indication of the request's current status
1308   and either a pointer to a status monitor or some estimate of when the
1309   user can expect the request to be fulfilled.
1310</t>
1311</section>
1312
1313<section title="203 Non-Authoritative Information" anchor="status.203">
1314  <iref primary="true" item="203 Non-Authoritative Information (status code)"/>
1315  <iref primary="true" item="Status Codes" subitem="203 Non-Authoritative Information"/>
1316<t>
1317   The returned metadata in the header fields is not the
1318   definitive set as available from the origin server, but is gathered
1319   from a local or a third-party copy. The set presented MAY be a subset
1320   or superset of the original version. For example, including local
1321   annotation information about the resource might result in a superset
1322   of the metadata known by the origin server. Use of this
1323   response code is not required and is only appropriate when the
1324   response would otherwise be 200 (OK).
1325</t>
1326<t>
1327   Caches MAY use a heuristic (see Section 2.3.1.1 of <xref target="Part6"/>) to determine
1328   freshness for 203 responses.
1329</t>
1330
1331</section>
1332
1333<section title="204 No Content" anchor="status.204">
1334  <iref primary="true" item="204 No Content (status code)"/>
1335  <iref primary="true" item="Status Codes" subitem="204 No Content"/>
1336<t>
1337   The 204 (No Content) status code indicates that the server has
1338   successfully fulfilled the request and that there is no additional
1339   content to return in the response payload body.  Metadata in the
1340   response header fields refer to the target resource and its current
1341   representation after the requested action.
1342</t>
1343<t>
1344   For example, if a 204 status code is received in response to a PUT
1345   request and the response contains an ETag header field, then the PUT
1346   was successful and the ETag field-value contains the entity-tag for
1347   the new representation of that target resource.
1348</t>
1349<t>
1350   The 204 response allows a server to indicate that the action has been
1351   successfully applied to the target resource while implying that the
1352   user agent SHOULD NOT traverse away from its current "document view"
1353   (if any).  The server assumes that the user agent will provide some
1354   indication of the success to its user, in accord with its own interface,
1355   and apply any new or updated metadata in the response to the active
1356   representation.
1357   For example, a 204 status code is commonly used with document editing
1358   interfaces corresponding to a "save" action, such that the document
1359   being saved remains available to the user for editing. It is also
1360   frequently used with interfaces that expect automated data transfers
1361   to be prevalent, such as within distributed version control systems.
1362</t>
1363<t>
1364   The 204 response MUST NOT include a message-body, and thus is always
1365   terminated by the first empty line after the header fields.
1366</t>
1367</section>
1368
1369<section title="205 Reset Content" anchor="status.205">
1370  <iref primary="true" item="205 Reset Content (status code)"/>
1371  <iref primary="true" item="Status Codes" subitem="205 Reset Content"/>
1372<t>
1373   The server has fulfilled the request and the user agent SHOULD reset
1374   the document view which caused the request to be sent. This response
1375   is primarily intended to allow input for actions to take place via
1376   user input, followed by a clearing of the form in which the input is
1377   given so that the user can easily initiate another input action.
1378</t>
1379<t>   
1380   The message-body included with the response MUST be empty. Note that
1381   receivers still need to parse the response according to the algorithm defined
1382   in Section 3.3 of <xref target="Part1"/>.
1383</t>
1384</section>
1385
1386<section title="206 Partial Content" anchor="status.206">
1387  <iref primary="true" item="206 Partial Content (status code)"/>
1388  <iref primary="true" item="Status Codes" subitem="206 Partial Content"/>
1389 
1390<t>
1391   The server has fulfilled the partial GET request for the resource
1392   and the enclosed payload is a partial representation as defined in Section 3.1 of <xref target="Part5"/>.
1393</t>
1394<t>
1395   Caches MAY use a heuristic (see Section 2.3.1.1 of <xref target="Part6"/>) to determine
1396   freshness for 206 responses.
1397</t>
1398</section>
1399</section>
1400
1401<section title="Redirection 3xx" anchor="status.3xx">
1402<t>
1403   This class of status code indicates that further action needs to be
1404   taken by the user agent in order to fulfill the request.  The action
1405   required MAY be carried out by the user agent without interaction
1406   with the user if and only if the method used in the second request is
1407   known to be "safe", as defined in <xref target="safe.methods"/>.
1408   A client SHOULD detect infinite redirection loops, since such loops
1409   generate network traffic for each redirection.
1410</t>
1411<t><list>
1412  <t>
1413    Note: An earlier version of this specification recommended a
1414    maximum of five redirections (<xref target="RFC2068"/>, Section 10.3).
1415    Content developers need to be aware that some clients might
1416    implement such a fixed limitation.
1417  </t>
1418</list></t>
1419
1420<section title="300 Multiple Choices" anchor="status.300">
1421  <iref primary="true" item="300 Multiple Choices (status code)"/>
1422  <iref primary="true" item="Status Codes" subitem="300 Multiple Choices"/>
1423<t>
1424   The target resource has more than one
1425   representation, each with its own specific location, and agent-driven
1426   negotiation information (Section 5 of <xref target="Part3"/>) is being provided so that
1427   the user (or user agent) can select a preferred representation by
1428   redirecting its request to that location.
1429</t>
1430<t>
1431   Unless it was a HEAD request, the response SHOULD include a representation
1432   containing a list of representation metadata and location(s) from
1433   which the user or user agent can choose the one most appropriate. The
1434   data format is specified by the media type given in the Content-Type
1435   header field. Depending upon the format and the capabilities of
1436   the user agent, selection of the most appropriate choice MAY be
1437   performed automatically. However, this specification does not define
1438   any standard for such automatic selection.
1439</t>
1440<t>
1441   If the server has a preferred choice of representation, it SHOULD
1442   include the specific URI for that representation in the Location
1443   field; user agents MAY use the Location field value for automatic
1444   redirection.
1445</t>
1446<t>
1447   Caches MAY use a heuristic (see Section 2.3.1.1 of <xref target="Part6"/>) to determine
1448   freshness for 300 responses.
1449</t>
1450
1451</section>
1452
1453<section title="301 Moved Permanently" anchor="status.301">
1454  <iref primary="true" item="301 Moved Permanently (status code)"/>
1455  <iref primary="true" item="Status Codes" subitem="301 Moved Permanently"/>
1456<t>
1457   The target resource has been assigned a new permanent URI and any
1458   future references to this resource SHOULD use one of the returned
1459   URIs.  Clients with link editing capabilities ought to automatically
1460   re-link references to the effective request URI to one or more of the new
1461   references returned by the server, where possible.
1462</t>
1463<t>
1464   Caches MAY use a heuristic (see Section 2.3.1.1 of <xref target="Part6"/>) to determine
1465   freshness for 301 responses.
1466</t>
1467<t>
1468   The new permanent URI SHOULD be given by the Location field in the
1469   response. Unless the request method was HEAD, the representation of the
1470   response SHOULD contain a short hypertext note with a hyperlink to
1471   the new URI(s).
1472</t>
1473<t>
1474   If the 301 status code is received in response to a request method
1475   that is known to be "safe", as defined in <xref target="safe.methods"/>,
1476   then the request MAY be automatically redirected by the user agent without
1477   confirmation.  Otherwise, the user agent MUST NOT automatically redirect the
1478   request unless it can be confirmed by the user, since this might
1479   change the conditions under which the request was issued.
1480</t>
1481<t><list>
1482  <t>
1483    Note: When automatically redirecting a POST request after
1484    receiving a 301 status code, some existing HTTP/1.0 user agents
1485    will erroneously change it into a GET request.
1486  </t>
1487</list></t>
1488</section>
1489
1490<section title="302 Found" anchor="status.302">
1491  <iref primary="true" item="302 Found (status code)"/>
1492  <iref primary="true" item="Status Codes" subitem="302 Found"/>
1493<t>
1494   The target resource resides temporarily under a different URI.
1495   Since the redirection might be altered on occasion, the client SHOULD
1496   continue to use the effective request URI for future requests.
1497</t>
1498<t>
1499   The temporary URI SHOULD be given by the Location field in the
1500   response. Unless the request method was HEAD, the representation of the
1501   response SHOULD contain a short hypertext note with a hyperlink to
1502   the new URI(s).
1503</t>
1504<t>
1505   If the 302 status code is received in response to a request method
1506   that is known to be "safe", as defined in <xref target="safe.methods"/>,
1507   then the request MAY be automatically redirected by the user agent without
1508   confirmation.  Otherwise, the user agent MUST NOT automatically redirect the
1509   request unless it can be confirmed by the user, since this might
1510   change the conditions under which the request was issued.
1511</t>
1512<t><list>
1513  <t>
1514    Note: HTTP/1.0 (<xref target="RFC1945"/>, Section 9.3)
1515    and the first version of HTTP/1.1 (<xref target="RFC2068"/>, Section 10.3.3)
1516    specify that the client is not allowed to change the method on the
1517    redirected request.  However, most existing user agent implementations
1518    treat 302 as if it were a 303 response, performing a GET on the Location
1519    field-value regardless of the original request method. Therefore, a
1520    previous version of this specification
1521    (<xref target="RFC2616"/>, Section 10.3.3) has added the
1522    status codes
1523    <xref target="status.303" format="none">303</xref> and
1524    <xref target="status.307" format="none">307</xref> for servers that wish
1525    to make unambiguously clear which kind of reaction is expected of the
1526    client.
1527  </t>
1528</list></t>
1529</section>
1530
1531<section title="303 See Other" anchor="status.303">
1532  <iref primary="true" item="303 See Other (status code)"/>
1533  <iref primary="true" item="Status Codes" subitem="303 See Other"/>
1534<t>
1535   The server directs the user agent to a different resource, indicated
1536   by a URI in the Location header field, that provides an indirect
1537   response to the original request.  The user agent MAY perform a GET
1538   request on the URI in the Location field in order to obtain a
1539   representation corresponding to the response, be redirected again,
1540   or end with an error status.  The Location URI is not a substitute
1541   reference for the effective request URI.
1542</t>
1543<t>
1544   The 303 status code is generally applicable to any HTTP method.  It is
1545   primarily used to allow the output of a POST action to redirect
1546   the user agent to a selected resource, since doing so provides the
1547   information corresponding to the POST response in a form that
1548   can be separately identified, bookmarked, and cached independent
1549   of the original request.
1550</t>
1551<t>
1552   A 303 response to a GET request indicates that the requested
1553   resource does not have a representation of its own that can be
1554   transferred by the server over HTTP.  The Location URI indicates a
1555   resource that is descriptive of the target resource, such that the
1556   follow-on representation might be useful to recipients without
1557   implying that it adequately represents the target resource.
1558   Note that answers to the questions of what can be represented, what
1559   representations are adequate, and what might be a useful description
1560   are outside the scope of HTTP and thus entirely determined by the
1561   URI owner(s).
1562</t>
1563<t>
1564   Except for responses to a HEAD request, the representation of a 303
1565   response SHOULD contain a short hypertext note with a hyperlink
1566   to the Location URI.
1567</t>
1568</section>
1569
1570<section title="304 Not Modified" anchor="status.304">
1571  <iref primary="true" item="304 Not Modified (status code)"/>
1572  <iref primary="true" item="Status Codes" subitem="304 Not Modified"/>
1573 
1574<t>
1575   The response to the request has not been modified since the conditions
1576   indicated by the client's conditional GET request, as defined in Section 4.1 of <xref target="Part4"/>.
1577</t>
1578</section>
1579
1580<section title="305 Use Proxy" anchor="status.305">
1581  <iref primary="true" item="305 Use Proxy (status code)"/>
1582  <iref primary="true" item="Status Codes" subitem="305 Use Proxy"/>
1583<t>
1584   The 305 status code was defined in a previous version of this specification
1585   (see <xref target="changes.from.rfc.2616"/>), and is now deprecated.
1586</t>
1587</section>
1588
1589<section title="306 (Unused)" anchor="status.306">
1590  <iref primary="true" item="306 (Unused) (status code)"/>
1591  <iref primary="true" item="Status Codes" subitem="306 (Unused)"/>
1592<t>
1593   The 306 status code was used in a previous version of the
1594   specification, is no longer used, and the code is reserved.
1595</t>
1596</section>
1597
1598<section title="307 Temporary Redirect" anchor="status.307">
1599  <iref primary="true" item="307 Temporary Redirect (status code)"/>
1600  <iref primary="true" item="Status Codes" subitem="307 Temporary Redirect"/>
1601<t>
1602   The target resource resides temporarily under a different URI.
1603   Since the redirection can change over time, the client SHOULD
1604   continue to use the effective request URI for future requests.
1605</t>
1606<t>
1607   The temporary URI SHOULD be given by the Location field in the
1608   response. Unless the request method was HEAD, the representation of the
1609   response SHOULD contain a short hypertext note with a hyperlink to
1610   the new URI(s), since many pre-HTTP/1.1 user agents do not
1611   understand the 307 status code. Therefore, the note SHOULD contain the
1612   information necessary for a user to repeat the original request on
1613   the new URI.
1614</t>
1615<t>
1616   If the 307 status code is received in response to a request method
1617   that is known to be "safe", as defined in <xref target="safe.methods"/>,
1618   then the request MAY be automatically redirected by the user agent without
1619   confirmation.  Otherwise, the user agent MUST NOT automatically redirect the
1620   request unless it can be confirmed by the user, since this might
1621   change the conditions under which the request was issued.
1622</t>
1623</section>
1624</section>
1625
1626<section title="Client Error 4xx" anchor="status.4xx">
1627<t>
1628   The 4xx class of status code is intended for cases in which the
1629   client seems to have erred. Except when responding to a HEAD request,
1630   the server SHOULD include a representation containing an explanation of the
1631   error situation, and whether it is a temporary or permanent
1632   condition. These status codes are applicable to any request method.
1633   User agents SHOULD display any included representation to the user.
1634</t>
1635<t>
1636   If the client is sending data, a server implementation using TCP
1637   SHOULD be careful to ensure that the client acknowledges receipt of
1638   the packet(s) containing the response, before the server closes the
1639   input connection. If the client continues sending data to the server
1640   after the close, the server's TCP stack will send a reset packet to
1641   the client, which might erase the client's unacknowledged input buffers
1642   before they can be read and interpreted by the HTTP application.
1643</t>
1644
1645<section title="400 Bad Request" anchor="status.400">
1646  <iref primary="true" item="400 Bad Request (status code)"/>
1647  <iref primary="true" item="Status Codes" subitem="400 Bad Request"/>
1648<t>
1649   The request could not be understood by the server due to malformed
1650   syntax. The client SHOULD NOT repeat the request without
1651   modifications.
1652</t>
1653</section>
1654
1655<section title="401 Unauthorized" anchor="status.401">
1656  <iref primary="true" item="401 Unauthorized (status code)"/>
1657  <iref primary="true" item="Status Codes" subitem="401 Unauthorized"/>
1658 
1659<t>
1660   The request requires user authentication (see Section 3.1 of <xref target="Part7"/>).
1661</t>
1662</section>
1663
1664<section title="402 Payment Required" anchor="status.402">
1665  <iref primary="true" item="402 Payment Required (status code)"/>
1666  <iref primary="true" item="Status Codes" subitem="402 Payment Required"/>
1667<t>
1668   This code is reserved for future use.
1669</t>
1670</section>
1671
1672<section title="403 Forbidden" anchor="status.403">
1673  <iref primary="true" item="403 Forbidden (status code)"/>
1674  <iref primary="true" item="Status Codes" subitem="403 Forbidden"/>
1675<t>
1676   The server understood the request, but is refusing to fulfill it.
1677   Authorization will not help and the request SHOULD NOT  be repeated.
1678   If the request method was not HEAD and the server wishes to make
1679   public why the request has not been fulfilled, it SHOULD describe the
1680   reason for the refusal in the representation.  If the server does not wish to
1681   make this information available to the client, the status code 404
1682   (Not Found) can be used instead.
1683</t>
1684</section>
1685
1686<section title="404 Not Found" anchor="status.404">
1687  <iref primary="true" item="404 Not Found (status code)"/>
1688  <iref primary="true" item="Status Codes" subitem="404 Not Found"/>
1689<t>
1690   The server has not found anything matching the effective request URI. No
1691   indication is given of whether the condition is temporary or
1692   permanent. The 410 (Gone) status code SHOULD be used if the server
1693   knows, through some internally configurable mechanism, that an old
1694   resource is permanently unavailable and has no forwarding address.
1695   This status code is commonly used when the server does not wish to
1696   reveal exactly why the request has been refused, or when no other
1697   response is applicable.
1698</t>
1699</section>
1700
1701<section title="405 Method Not Allowed" anchor="status.405">
1702  <iref primary="true" item="405 Method Not Allowed (status code)"/>
1703  <iref primary="true" item="Status Codes" subitem="405 Method Not Allowed"/>
1704<t>
1705   The method specified in the Request-Line is not allowed for the target
1706   resource. The response MUST include an
1707   Allow header field containing a list of valid methods for the requested
1708   resource.
1709</t>
1710</section>
1711
1712<section title="406 Not Acceptable" anchor="status.406">
1713  <iref primary="true" item="406 Not Acceptable (status code)"/>
1714  <iref primary="true" item="Status Codes" subitem="406 Not Acceptable"/>
1715<t>
1716   The resource identified by the request is only capable of generating
1717   response representations which have content characteristics not acceptable
1718   according to the accept header fields sent in the request.
1719</t>
1720<t>
1721   Unless it was a HEAD request, the response SHOULD include a representation
1722   containing a list of available representation characteristics and location(s)
1723   from which the user or user agent can choose the one most
1724   appropriate. The data format is specified by the media type given
1725   in the Content-Type header field. Depending upon the format and the
1726   capabilities of the user agent, selection of the most appropriate
1727   choice MAY be performed automatically. However, this specification
1728   does not define any standard for such automatic selection.
1729</t>
1730<t><list>
1731  <t>
1732    Note: HTTP/1.1 servers are allowed to return responses which are
1733    not acceptable according to the accept header fields sent in the
1734    request. In some cases, this might even be preferable to sending a
1735    406 response. User agents are encouraged to inspect the header fields of
1736    an incoming response to determine if it is acceptable.
1737  </t>
1738</list></t>
1739<t>
1740   If the response could be unacceptable, a user agent SHOULD
1741   temporarily stop receipt of more data and query the user for a
1742   decision on further actions.
1743</t>
1744</section>
1745
1746<section title="407 Proxy Authentication Required" anchor="status.407">
1747  <iref primary="true" item="407 Proxy Authentication Required (status code)"/>
1748  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required"/>
1749<t>
1750   This code is similar to 401 (Unauthorized), but indicates that the
1751   client must first authenticate itself with the proxy (see Section 3.2 of <xref target="Part7"/>).
1752</t>
1753</section>
1754
1755<section title="408 Request Timeout" anchor="status.408">
1756  <iref primary="true" item="408 Request Timeout (status code)"/>
1757  <iref primary="true" item="Status Codes" subitem="408 Request Timeout"/>
1758<t>
1759   The client did not produce a request within the time that the server
1760   was prepared to wait. The client MAY repeat the request without
1761   modifications at any later time.
1762</t>
1763</section>
1764
1765<section title="409 Conflict" anchor="status.409">
1766  <iref primary="true" item="409 Conflict (status code)"/>
1767  <iref primary="true" item="Status Codes" subitem="409 Conflict"/>
1768<t>
1769   The request could not be completed due to a conflict with the current
1770   state of the resource. This code is only allowed in situations where
1771   it is expected that the user might be able to resolve the conflict
1772   and resubmit the request. The response body SHOULD include enough
1773   information for the user to recognize the source of the conflict.
1774   Ideally, the response representation would include enough information for the
1775   user or user agent to fix the problem; however, that might not be
1776   possible and is not required.
1777</t>
1778<t>
1779   Conflicts are most likely to occur in response to a PUT request. For
1780   example, if versioning were being used and the representation being PUT
1781   included changes to a resource which conflict with those made by an
1782   earlier (third-party) request, the server might use the 409 response
1783   to indicate that it can't complete the request. In this case, the
1784   response representation would likely contain a list of the differences
1785   between the two versions in a format defined by the response
1786   Content-Type.
1787</t>
1788</section>
1789
1790<section title="410 Gone" anchor="status.410">
1791  <iref primary="true" item="410 Gone (status code)"/>
1792  <iref primary="true" item="Status Codes" subitem="410 Gone"/>
1793<t>
1794   The target resource is no longer available at the server and no
1795   forwarding address is known. This condition is expected to be
1796   considered permanent. Clients with link editing capabilities SHOULD
1797   delete references to the effective request URI after user approval. If the
1798   server does not know, or has no facility to determine, whether or not
1799   the condition is permanent, the status code 404 (Not Found) SHOULD be
1800   used instead.
1801</t>
1802<t>
1803   The 410 response is primarily intended to assist the task of web
1804   maintenance by notifying the recipient that the resource is
1805   intentionally unavailable and that the server owners desire that
1806   remote links to that resource be removed. Such an event is common for
1807   limited-time, promotional services and for resources belonging to
1808   individuals no longer working at the server's site. It is not
1809   necessary to mark all permanently unavailable resources as "gone" or
1810   to keep the mark for any length of time — that is left to the
1811   discretion of the server owner.
1812</t>
1813<t>
1814   Caches MAY use a heuristic (see Section 2.3.1.1 of <xref target="Part6"/>) to determine freshness
1815   for 410 responses.
1816</t>
1817
1818</section>
1819
1820<section title="411 Length Required" anchor="status.411">
1821  <iref primary="true" item="411 Length Required (status code)"/>
1822  <iref primary="true" item="Status Codes" subitem="411 Length Required"/>
1823<t>
1824   The server refuses to accept the request without a defined Content-Length.
1825   The client MAY repeat the request if it adds a valid
1826   Content-Length header field containing the length of the message-body
1827   in the request message.
1828</t>
1829</section>
1830
1831<section title="412 Precondition Failed" anchor="status.412">
1832  <iref primary="true" item="412 Precondition Failed (status code)"/>
1833  <iref primary="true" item="Status Codes" subitem="412 Precondition Failed"/>
1834 
1835<t>
1836   The precondition given in one or more of the header fields
1837   evaluated to false when it was tested on the server, as defined in
1838   Section 4.2 of <xref target="Part4"/>.
1839</t>
1840</section>
1841
1842<section title="413 Request Entity Too Large" anchor="status.413">
1843  <iref primary="true" item="413 Request Entity Too Large (status code)"/>
1844  <iref primary="true" item="Status Codes" subitem="413 Request Entity Too Large"/>
1845<t>
1846   The server is refusing to process a request because the request
1847   representation is larger than the server is willing or able to process. The
1848   server MAY close the connection to prevent the client from continuing
1849   the request.
1850</t>
1851<t>
1852   If the condition is temporary, the server SHOULD include a Retry-After
1853   header field to indicate that it is temporary and after what
1854   time the client MAY try again.
1855</t>
1856</section>
1857
1858<section title="414 URI Too Long" anchor="status.414">
1859  <iref primary="true" item="414 URI Too Long (status code)"/>
1860  <iref primary="true" item="Status Codes" subitem="414 URI Too Long"/>
1861<t>
1862   The server is refusing to service the request because the effective request URI
1863   is longer than the server is willing to interpret. This rare
1864   condition is only likely to occur when a client has improperly
1865   converted a POST request to a GET request with long query
1866   information, when the client has descended into a URI "black hole" of
1867   redirection (e.g., a redirected URI prefix that points to a suffix of
1868   itself), or when the server is under attack by a client attempting to
1869   exploit security holes present in some servers using fixed-length
1870   buffers for reading or manipulating the effective request URI.
1871</t>
1872</section>
1873
1874<section title="415 Unsupported Media Type" anchor="status.415">
1875  <iref primary="true" item="415 Unsupported Media Type (status code)"/>
1876  <iref primary="true" item="Status Codes" subitem="415 Unsupported Media Type"/>
1877<t>
1878   The server is refusing to service the request because the request
1879   payload is in a format not supported by this request method on the
1880   target resource.
1881</t>
1882</section>
1883
1884<section title="416 Requested Range Not Satisfiable" anchor="status.416">
1885  <iref primary="true" item="416 Requested Range Not Satisfiable (status code)"/>
1886  <iref primary="true" item="Status Codes" subitem="416 Requested Range Not Satisfiable"/>
1887 
1888<t>
1889   The request included a Range header field (Section 5.4 of <xref target="Part5"/>) and none of
1890   the range-specifier values in this field overlap the current extent
1891   of the selected resource. See Section 3.2 of <xref target="Part5"/>.
1892</t>
1893</section>
1894
1895<section title="417 Expectation Failed" anchor="status.417">
1896  <iref primary="true" item="417 Expectation Failed (status code)"/>
1897  <iref primary="true" item="Status Codes" subitem="417 Expectation Failed"/>
1898<t>
1899   The expectation given in an Expect header field (see <xref target="header.expect"/>)
1900   could not be met by this server, or, if the server is a proxy,
1901   the server has unambiguous evidence that the request could not be met
1902   by the next-hop server.
1903</t>
1904</section>
1905
1906<section title="426 Upgrade Required" anchor="status.426">
1907  <iref primary="true" item="426 Upgrade Required (status code)"/>
1908  <iref primary="true" item="Status Codes" subitem="426 Upgrade Required"/>
1909<t>
1910   The request can not be completed without a prior protocol upgrade. This
1911   response MUST include an Upgrade header field (Section 9.8 of <xref target="Part1"/>)
1912   specifying the required protocols.
1913</t>
1914<figure>
1915<preamble>Example:</preamble>
1916<artwork type="message/http; msgtype=&#34;request&#34;"><![CDATA[
1917  HTTP/1.1 426 Upgrade Required
1918  Upgrade: HTTP/2.0
1919  Connection: Upgrade
1920 
1921  ]]></artwork></figure>
1922<t>
1923   The server SHOULD include a message body in the 426 response which
1924   indicates in human readable form the reason for the error and describes any
1925   alternative courses which may be available to the user.
1926</t>
1927</section>
1928</section>
1929
1930<section title="Server Error 5xx" anchor="status.5xx">
1931<t>
1932   Response status codes beginning with the digit "5" indicate cases in
1933   which the server is aware that it has erred or is incapable of
1934   performing the request. Except when responding to a HEAD request, the
1935   server SHOULD include a representation containing an explanation of the
1936   error situation, and whether it is a temporary or permanent
1937   condition. User agents SHOULD display any included representation to the
1938   user. These response codes are applicable to any request method.
1939</t>
1940
1941<section title="500 Internal Server Error" anchor="status.500">
1942  <iref primary="true" item="500 Internal Server Error (status code)"/>
1943  <iref primary="true" item="Status Codes" subitem="500 Internal Server Error"/>
1944<t>
1945   The server encountered an unexpected condition which prevented it
1946   from fulfilling the request.
1947</t>
1948</section>
1949
1950<section title="501 Not Implemented" anchor="status.501">
1951  <iref primary="true" item="501 Not Implemented (status code)"/>
1952  <iref primary="true" item="Status Codes" subitem="501 Not Implemented"/>
1953<t>
1954   The server does not support the functionality required to fulfill the
1955   request. This is the appropriate response when the server does not
1956   recognize the request method and is not capable of supporting it for
1957   any resource.
1958</t>
1959</section>
1960
1961<section title="502 Bad Gateway" anchor="status.502">
1962  <iref primary="true" item="502 Bad Gateway (status code)"/>
1963  <iref primary="true" item="Status Codes" subitem="502 Bad Gateway"/>
1964<t>
1965   The server, while acting as a gateway or proxy, received an invalid
1966   response from the upstream server it accessed in attempting to
1967   fulfill the request.
1968</t>
1969</section>
1970
1971<section title="503 Service Unavailable" anchor="status.503">
1972  <iref primary="true" item="503 Service Unavailable (status code)"/>
1973  <iref primary="true" item="Status Codes" subitem="503 Service Unavailable"/>
1974<t>
1975   The server is currently unable to handle the request due to a
1976   temporary overloading or maintenance of the server. The implication
1977   is that this is a temporary condition which will be alleviated after
1978   some delay. If known, the length of the delay MAY be indicated in a
1979   Retry-After header field. If no Retry-After is given, the client SHOULD
1980   handle the response as it would for a 500 response.
1981</t>
1982<t><list>
1983  <t>
1984    Note: The existence of the 503 status code does not imply that a
1985    server must use it when becoming overloaded. Some servers might wish
1986    to simply refuse the connection.
1987  </t>
1988</list></t>
1989</section>
1990
1991<section title="504 Gateway Timeout" anchor="status.504">
1992  <iref primary="true" item="504 Gateway Timeout (status code)"/>
1993  <iref primary="true" item="Status Codes" subitem="504 Gateway Timeout"/>
1994<t>
1995   The server, while acting as a gateway or proxy, did not receive a
1996   timely response from the upstream server specified by the URI (e.g.,
1997   HTTP, FTP, LDAP) or some other auxiliary server (e.g., DNS) it needed
1998   to access in attempting to complete the request.
1999</t>
2000<t><list>
2001  <t>
2002    Note to implementors: some deployed proxies are known to
2003    return 400 or 500 when DNS lookups time out.
2004  </t>
2005</list></t>
2006</section>
2007
2008<section title="505 HTTP Version Not Supported" anchor="status.505">
2009  <iref primary="true" item="505 HTTP Version Not Supported (status code)"/>
2010  <iref primary="true" item="Status Codes" subitem="505 HTTP Version Not Supported"/>
2011<t>
2012   The server does not support, or refuses to support, the protocol
2013   version that was used in the request message. The server is
2014   indicating that it is unable or unwilling to complete the request
2015   using the same major version as the client, as described in Section 2.5 of <xref target="Part1"/>,
2016   other than with this error message. The response SHOULD contain
2017   a representation describing why that version is not supported and what other
2018   protocols are supported by that server.
2019</t>
2020
2021</section>
2022</section>
2023</section>
2024
2025
2026<section title="Header Field Definitions" anchor="header.fields">
2027<t>
2028   This section defines the syntax and semantics of HTTP/1.1 header fields
2029   related to request and response semantics.
2030</t>
2031
2032<section title="Allow" anchor="header.allow">
2033  <iref primary="true" item="Allow header field"/>
2034  <iref primary="true" item="Header Fields" subitem="Allow"/>
2035 
2036<t>
2037   The "Allow" header field lists the set of methods advertised as
2038   supported by the target resource. The purpose of this field is strictly to
2039   inform the recipient of valid request methods associated with the resource.
2040</t>
2041<figure><iref primary="true" item="Grammar" subitem="Allow"/><artwork type="abnf2616"><![CDATA[
2042  Allow = #Method
2043]]></artwork></figure>
2044<t>
2045   Example of use:
2046</t>
2047<figure><artwork type="example"><![CDATA[
2048  Allow: GET, HEAD, PUT
2049]]></artwork></figure>
2050<t>
2051   The actual set of allowed methods is defined by the origin server at the
2052   time of each request.
2053</t>
2054<t>
2055   A proxy MUST NOT modify the Allow header field — it does not need to
2056   understand all the methods specified in order to handle them according to
2057   the generic message handling rules.
2058</t>
2059</section>
2060
2061<section title="Expect" anchor="header.expect">
2062  <iref primary="true" item="Expect header field"/>
2063  <iref primary="true" item="Header Fields" subitem="Expect"/>
2064 
2065 
2066 
2067 
2068<t>
2069   The "Expect" header field is used to indicate that particular
2070   server behaviors are required by the client.
2071</t>
2072<figure><iref primary="true" item="Grammar" subitem="Expect"/><iref primary="true" item="Grammar" subitem="expectation"/><iref primary="true" item="Grammar" subitem="expectation-extension"/><iref primary="true" item="Grammar" subitem="expect-params"/><artwork type="abnf2616"><![CDATA[
2073  Expect       = 1#expectation
2074 
2075  expectation  = "100-continue" / expectation-extension
2076  expectation-extension = token [ "=" ( token / quoted-string )
2077                           *expect-params ]
2078  expect-params = ";" token [ "=" ( token / quoted-string ) ]
2079]]></artwork></figure>
2080<t>
2081   A server that does not understand or is unable to comply with any of
2082   the expectation values in the Expect field of a request MUST respond
2083   with appropriate error status code. The server MUST respond with a 417
2084   (Expectation Failed) status code if any of the expectations cannot be met
2085   or, if there are other problems with the request, some other 4xx
2086   status code.
2087</t>
2088<t>
2089   This header field is defined with extensible syntax to allow for
2090   future extensions. If a server receives a request containing an
2091   Expect field that includes an expectation-extension that it does not
2092   support, it MUST respond with a 417 (Expectation Failed) status code.
2093</t>
2094<t>
2095   Comparison of expectation values is case-insensitive for unquoted
2096   tokens (including the 100-continue token), and is case-sensitive for
2097   quoted-string expectation-extensions.
2098</t>
2099<t>
2100   The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy MUST
2101   return a 417 (Expectation Failed) status code if it receives a request
2102   with an expectation that it cannot meet. However, the Expect
2103   header field itself is end-to-end; it MUST be forwarded if the
2104   request is forwarded.
2105</t>
2106<t>
2107   Many older HTTP/1.0 and HTTP/1.1 applications do not understand the
2108   Expect header field.
2109</t>
2110<t>
2111   See Section 7.2.3 of <xref target="Part1"/> for the use of the 100 (Continue) status code.
2112</t>
2113</section>
2114
2115<section title="From" anchor="header.from">
2116  <iref primary="true" item="From header field"/>
2117  <iref primary="true" item="Header Fields" subitem="From"/>
2118 
2119 
2120<t>
2121   The "From" header field, if given, SHOULD contain an Internet
2122   e-mail address for the human user who controls the requesting user
2123   agent. The address SHOULD be machine-usable, as defined by "mailbox"
2124   in Section 3.4 of <xref target="RFC5322"/>:
2125</t>
2126<figure><iref primary="true" item="Grammar" subitem="From"/><artwork type="abnf2616"><![CDATA[
2127  From    = mailbox
2128 
2129  mailbox = <mailbox, defined in [RFC5322], Section 3.4>
2130]]></artwork></figure>
2131<t>
2132   An example is:
2133</t>
2134<figure><artwork type="example"><![CDATA[
2135  From: webmaster@example.org
2136]]></artwork></figure>
2137<t>
2138   This header field MAY be used for logging purposes and as a means for
2139   identifying the source of invalid or unwanted requests. It SHOULD NOT
2140   be used as an insecure form of access protection. The interpretation
2141   of this field is that the request is being performed on behalf of the
2142   person given, who accepts responsibility for the method performed. In
2143   particular, robot agents SHOULD include this header field so that the
2144   person responsible for running the robot can be contacted if problems
2145   occur on the receiving end.
2146</t>
2147<t>
2148   The Internet e-mail address in this field MAY be separate from the
2149   Internet host which issued the request. For example, when a request
2150   is passed through a proxy the original issuer's address SHOULD be
2151   used.
2152</t>
2153<t>
2154   The client SHOULD NOT  send the From header field without the user's
2155   approval, as it might conflict with the user's privacy interests or
2156   their site's security policy. It is strongly recommended that the
2157   user be able to disable, enable, and modify the value of this field
2158   at any time prior to a request.
2159</t>
2160</section>
2161
2162<section title="Location" anchor="header.location">
2163  <iref primary="true" item="Location header field"/>
2164  <iref primary="true" item="Header Fields" subitem="Location"/>
2165 
2166<t>
2167   The "Location" header field is used to identify a newly created
2168   resource, or to redirect the recipient to a different location for
2169   completion of the request.
2170</t>
2171<t>
2172   For 201 (Created) responses, the Location is the URI of the new resource
2173   which was created by the request. For 3xx responses, the location SHOULD
2174   indicate the server's preferred URI for automatic redirection to the
2175   resource.
2176</t>
2177<t>
2178   The field value consists of a single URI-reference. When it has the form
2179   of a relative reference (<xref target="RFC3986"/>, Section 4.2),
2180   the final value is computed by resolving it against the effective request
2181   URI (<xref target="RFC3986"/>, Section 5).
2182</t>
2183<figure><iref primary="true" item="Grammar" subitem="Location"/><artwork type="abnf2616"><![CDATA[
2184  Location = URI-reference
2185]]></artwork></figure>
2186<figure>
2187<preamble>Examples are:</preamble><!--DO NOT DARE changing the vertical WSP below, it's necessary this way for xml2rfc-->
2188<artwork type="example"><![CDATA[
2189  Location: http://www.example.org/pub/WWW/People.html#tim
2190]]></artwork></figure><figure><artwork type="example"><![CDATA[  Location: /index.html
2191]]></artwork></figure>
2192<t>
2193   There are circumstances in which a fragment identifier in a Location URI
2194   would not be appropriate:
2195   <list style="symbols">
2196      <t>With a 201 Created response, because in this usage the Location header
2197      field specifies the URI for the entire created resource.</t>
2198      <t>With 305 Use Proxy.</t>
2199   </list>
2200</t>
2201<t><list>
2202  <t>
2203    Note: This specification does not define precedence rules
2204    for the case where the original URI, as navigated to by the user
2205    agent, and the Location header field value both contain fragment
2206    identifiers. Thus be aware that including fragment identifiers might
2207    inconvenience anyone relying on the semantics of the original URI's
2208    fragment identifier.
2209  </t>
2210</list></t>
2211<t><list>
2212  <t>
2213    Note: The Content-Location header field (Section 6.7 of <xref target="Part3"/>) differs
2214    from Location in that the Content-Location identifies the most specific
2215    resource corresponding to the enclosed representation.
2216    It is therefore possible for a response to contain header fields for
2217    both Location and Content-Location.
2218  </t>
2219</list></t>
2220</section>
2221
2222<section title="Max-Forwards" anchor="header.max-forwards">
2223  <iref primary="true" item="Max-Forwards header field"/>
2224  <iref primary="true" item="Header Fields" subitem="Max-Forwards"/>
2225 
2226<t>
2227   The "Max-Forwards" header field provides a mechanism with the
2228   TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>)
2229   methods to limit the number of times that the request is forwarded by
2230   proxies. This can be useful when the client is attempting to
2231   trace a request which appears to be failing or looping in mid-chain.
2232</t>
2233<figure><iref primary="true" item="Grammar" subitem="Max-Forwards"/><artwork type="abnf2616"><![CDATA[
2234  Max-Forwards = 1*DIGIT
2235]]></artwork></figure>
2236<t>
2237   The Max-Forwards value is a decimal integer indicating the remaining
2238   number of times this request message can be forwarded.
2239</t>
2240<t>
2241   Each recipient of a TRACE or OPTIONS request
2242   containing a Max-Forwards header field MUST check and update its
2243   value prior to forwarding the request. If the received value is zero
2244   (0), the recipient MUST NOT forward the request; instead, it MUST
2245   respond as the final recipient. If the received Max-Forwards value is
2246   greater than zero, then the forwarded message MUST contain an updated
2247   Max-Forwards field with a value decremented by one (1).
2248</t>
2249<t>
2250   The Max-Forwards header field MAY be ignored for all other request
2251   methods.
2252</t>
2253</section>
2254
2255<section title="Referer" anchor="header.referer">
2256  <iref primary="true" item="Referer header field"/>
2257  <iref primary="true" item="Header Fields" subitem="Referer"/>
2258 
2259<t>
2260   The "Referer" [sic] header field allows the client to specify the
2261   URI of the resource from which the effective request URI was obtained (the
2262   "referrer", although the header field is misspelled.).
2263</t>
2264<t>
2265   The Referer header field allows servers to generate lists of back-links to
2266   resources for interest, logging, optimized caching, etc. It also allows
2267   obsolete or mistyped links to be traced for maintenance. Some servers use
2268   Referer as a means of controlling where they allow links from (so-called
2269   "deep linking"), but legitimate requests do not always
2270   contain a Referer header field.
2271</t>
2272<t>
2273   If the effective request URI was obtained from a source that does not have its own
2274   URI (e.g., input from the user keyboard), the Referer field MUST either be
2275   sent with the value "about:blank", or not be sent at all. Note that this
2276   requirement does not apply to sources with non-HTTP URIs (e.g., FTP).
2277</t>
2278<figure><iref primary="true" item="Grammar" subitem="Referer"/><artwork type="abnf2616"><![CDATA[
2279  Referer = absolute-URI / partial-URI
2280]]></artwork></figure>
2281<t>
2282   Example:
2283</t>
2284<figure><artwork type="example"><![CDATA[
2285  Referer: http://www.example.org/hypertext/Overview.html
2286]]></artwork></figure>
2287<t>
2288   If the field value is a relative URI, it SHOULD be interpreted
2289   relative to the effective request URI. The URI MUST NOT include a fragment. See
2290   <xref target="encoding.sensitive.information.in.uris"/> for security considerations.
2291</t>
2292</section>
2293
2294<section title="Retry-After" anchor="header.retry-after">
2295  <iref primary="true" item="Retry-After header field"/>
2296  <iref primary="true" item="Header Fields" subitem="Retry-After"/>
2297 
2298<t>
2299   The header "Retry-After" field can be used with a 503 (Service
2300   Unavailable) response to indicate how long the service is expected to
2301   be unavailable to the requesting client. This field MAY also be used
2302   with any 3xx (Redirection) response to indicate the minimum time the
2303   user-agent is asked wait before issuing the redirected request.
2304</t>
2305<t>
2306   The value of this field can be either an HTTP-date or an integer number
2307   of seconds (in decimal) after the time of the response.
2308</t>
2309<figure><iref primary="true" item="Grammar" subitem="Retry-After"/><artwork type="abnf2616"><![CDATA[
2310  Retry-After = HTTP-date / delta-seconds
2311]]></artwork></figure>
2312<t anchor="rule.delta-seconds">
2313 
2314   Time spans are non-negative decimal integers, representing time in
2315   seconds.
2316</t>
2317<figure><iref primary="true" item="Grammar" subitem="delta-seconds"/><artwork type="abnf2616"><![CDATA[
2318  delta-seconds  = 1*DIGIT
2319]]></artwork></figure>
2320<t>
2321   Two examples of its use are
2322</t>
2323<figure><artwork type="example"><![CDATA[
2324  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
2325  Retry-After: 120
2326]]></artwork></figure>
2327<t>
2328   In the latter example, the delay is 2 minutes.
2329</t>
2330</section>
2331
2332<section title="Server" anchor="header.server">
2333  <iref primary="true" item="Server header field"/>
2334  <iref primary="true" item="Header Fields" subitem="Server"/>
2335 
2336<t>
2337   The "Server" header field contains information about the
2338   software used by the origin server to handle the request.
2339</t>
2340<t>
2341   The field can contain multiple product tokens (Section 6.3 of <xref target="Part1"/>) and
2342   comments (Section 3.2 of <xref target="Part1"/>) identifying the server and any significant
2343   subproducts. The product tokens are listed in order of their significance
2344   for identifying the application.
2345</t>
2346<figure><iref primary="true" item="Grammar" subitem="Server"/><artwork type="abnf2616"><![CDATA[
2347  Server = product *( RWS ( product / comment ) )
2348]]></artwork></figure>
2349<t>
2350   Example:
2351</t>
2352<figure><artwork type="example"><![CDATA[
2353  Server: CERN/3.0 libwww/2.17
2354]]></artwork></figure>
2355<t>
2356   If the response is being forwarded through a proxy, the proxy
2357   application MUST NOT modify the Server header field. Instead, it
2358   MUST include a Via field (as described in Section 9.9 of <xref target="Part1"/>).
2359</t>
2360<t><list>
2361  <t>
2362    Note: Revealing the specific software version of the server might
2363    allow the server machine to become more vulnerable to attacks
2364    against software that is known to contain security holes. Server
2365    implementors are encouraged to make this field a configurable
2366    option.
2367  </t>
2368</list></t>
2369</section>
2370
2371<section title="User-Agent" anchor="header.user-agent">
2372  <iref primary="true" item="User-Agent header field"/>
2373  <iref primary="true" item="Header Fields" subitem="User-Agent"/>
2374 
2375<t>
2376   The "User-Agent" header field contains information about the user
2377   agent originating the request. User agents SHOULD include this field with
2378   requests.
2379</t>
2380<t>
2381   Typically, it is used for statistical purposes, the tracing of protocol
2382   violations, and tailoring responses to avoid particular user agent
2383   limitations.
2384</t>
2385<t>
2386   The field can contain multiple product tokens (Section 6.3 of <xref target="Part1"/>)
2387   and comments (Section 3.2 of <xref target="Part1"/>) identifying the agent and its
2388   significant subproducts. By convention, the product tokens are listed in
2389   order of their significance for identifying the application.
2390</t>
2391<t>
2392   Because this field is usually sent on every request a user agent makes,
2393   implementations are encouraged not to include needlessly fine-grained
2394   detail, and to limit (or even prohibit) the addition of subproducts by third
2395   parties. Overly long and detailed User-Agent field values make requests
2396   larger and can also be used to identify ("fingerprint") the user against
2397   their wishes.
2398</t>
2399<t>
2400   Likewise, implementations are encouraged not to use the product tokens of
2401   other implementations in order to declare compatibility with them, as this
2402   circumvents the purpose of the field. Finally, they are encouraged not to
2403   use comments to identify products; doing so makes the field value more
2404   difficult to parse.
2405</t>
2406<figure><iref primary="true" item="Grammar" subitem="User-Agent"/><artwork type="abnf2616"><![CDATA[
2407  User-Agent = product *( RWS ( product / comment ) )
2408]]></artwork></figure>
2409<t>
2410   Example:
2411</t>
2412<figure><artwork type="example"><![CDATA[
2413  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
2414]]></artwork></figure>
2415</section>
2416
2417</section>
2418
2419<section title="IANA Considerations" anchor="IANA.considerations">
2420
2421<section title="Method Registry" anchor="method.registration">
2422<t>
2423  The registration procedure for HTTP request methods is defined by
2424  <xref target="method.registry"/> of this document.
2425</t>
2426<t>
2427   The HTTP Method Registry shall be created at <eref target="http://www.iana.org/assignments/http-methods"/>
2428   and be populated with the registrations below:
2429</t>
2430
2431<!--AUTOGENERATED FROM extract-method-defs.xslt, do not edit manually-->
2432<texttable align="left" suppress-title="true" anchor="iana.method.registration.table">
2433   <ttcol>Method</ttcol>
2434   <ttcol>Safe</ttcol>
2435   <ttcol>Reference</ttcol>
2436   <c>CONNECT</c>
2437   <c>no</c>
2438   <c>
2439      <xref target="CONNECT"/>
2440   </c>
2441   <c>DELETE</c>
2442   <c>no</c>
2443   <c>
2444      <xref target="DELETE"/>
2445   </c>
2446   <c>GET</c>
2447   <c>yes</c>
2448   <c>
2449      <xref target="GET"/>
2450   </c>
2451   <c>HEAD</c>
2452   <c>yes</c>
2453   <c>
2454      <xref target="HEAD"/>
2455   </c>
2456   <c>OPTIONS</c>
2457   <c>yes</c>
2458   <c>
2459      <xref target="OPTIONS"/>
2460   </c>
2461   <c>POST</c>
2462   <c>no</c>
2463   <c>
2464      <xref target="POST"/>
2465   </c>
2466   <c>PUT</c>
2467   <c>no</c>
2468   <c>
2469      <xref target="PUT"/>
2470   </c>
2471   <c>TRACE</c>
2472   <c>yes</c>
2473   <c>
2474      <xref target="TRACE"/>
2475   </c>
2476</texttable>
2477<!--(END)-->
2478
2479</section>
2480
2481<section title="Status Code Registry" anchor="status.code.registration">
2482<t>
2483   The registration procedure for HTTP Status Codes — previously defined
2484   in Section 7.1 of <xref target="RFC2817"/> — is now defined
2485   by <xref target="status.code.registry"/> of this document.
2486</t>
2487<t>
2488   The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
2489   shall be updated with the registrations below:
2490</t>
2491
2492<!--AUTOGENERATED FROM extract-status-code-defs.xslt, do not edit manually-->
2493<texttable align="left" suppress-title="true" anchor="iana.status.code.registration.table">
2494   <ttcol>Value</ttcol>
2495   <ttcol>Description</ttcol>
2496   <ttcol>Reference</ttcol>
2497   <c>100</c>
2498   <c>Continue</c>
2499   <c>
2500      <xref target="status.100"/>
2501   </c>
2502   <c>101</c>
2503   <c>Switching Protocols</c>
2504   <c>
2505      <xref target="status.101"/>
2506   </c>
2507   <c>200</c>
2508   <c>OK</c>
2509   <c>
2510      <xref target="status.200"/>
2511   </c>
2512   <c>201</c>
2513   <c>Created</c>
2514   <c>
2515      <xref target="status.201"/>
2516   </c>
2517   <c>202</c>
2518   <c>Accepted</c>
2519   <c>
2520      <xref target="status.202"/>
2521   </c>
2522   <c>203</c>
2523   <c>Non-Authoritative Information</c>
2524   <c>
2525      <xref target="status.203"/>
2526   </c>
2527   <c>204</c>
2528   <c>No Content</c>
2529   <c>
2530      <xref target="status.204"/>
2531   </c>
2532   <c>205</c>
2533   <c>Reset Content</c>
2534   <c>
2535      <xref target="status.205"/>
2536   </c>
2537   <c>300</c>
2538   <c>Multiple Choices</c>
2539   <c>
2540      <xref target="status.300"/>
2541   </c>
2542   <c>301</c>
2543   <c>Moved Permanently</c>
2544   <c>
2545      <xref target="status.301"/>
2546   </c>
2547   <c>302</c>
2548   <c>Found</c>
2549   <c>
2550      <xref target="status.302"/>
2551   </c>
2552   <c>303</c>
2553   <c>See Other</c>
2554   <c>
2555      <xref target="status.303"/>
2556   </c>
2557   <c>305</c>
2558   <c>Use Proxy</c>
2559   <c>
2560      <xref target="status.305"/>
2561   </c>
2562   <c>306</c>
2563   <c>(Unused)</c>
2564   <c>
2565      <xref target="status.306"/>
2566   </c>
2567   <c>307</c>
2568   <c>Temporary Redirect</c>
2569   <c>
2570      <xref target="status.307"/>
2571   </c>
2572   <c>400</c>
2573   <c>Bad Request</c>
2574   <c>
2575      <xref target="status.400"/>
2576   </c>
2577   <c>402</c>
2578   <c>Payment Required</c>
2579   <c>
2580      <xref target="status.402"/>
2581   </c>
2582   <c>403</c>
2583   <c>Forbidden</c>
2584   <c>
2585      <xref target="status.403"/>
2586   </c>
2587   <c>404</c>
2588   <c>Not Found</c>
2589   <c>
2590      <xref target="status.404"/>
2591   </c>
2592   <c>405</c>
2593   <c>Method Not Allowed</c>
2594   <c>
2595      <xref target="status.405"/>
2596   </c>
2597   <c>406</c>
2598   <c>Not Acceptable</c>
2599   <c>
2600      <xref target="status.406"/>
2601   </c>
2602   <c>407</c>
2603   <c>Proxy Authentication Required</c>
2604   <c>
2605      <xref target="status.407"/>
2606   </c>
2607   <c>408</c>
2608   <c>Request Timeout</c>
2609   <c>
2610      <xref target="status.408"/>
2611   </c>
2612   <c>409</c>
2613   <c>Conflict</c>
2614   <c>
2615      <xref target="status.409"/>
2616   </c>
2617   <c>410</c>
2618   <c>Gone</c>
2619   <c>
2620      <xref target="status.410"/>
2621   </c>
2622   <c>411</c>
2623   <c>Length Required</c>
2624   <c>
2625      <xref target="status.411"/>
2626   </c>
2627   <c>413</c>
2628   <c>Request Entity Too Large</c>
2629   <c>
2630      <xref target="status.413"/>
2631   </c>
2632   <c>414</c>
2633   <c>URI Too Long</c>
2634   <c>
2635      <xref target="status.414"/>
2636   </c>
2637   <c>415</c>
2638   <c>Unsupported Media Type</c>
2639   <c>
2640      <xref target="status.415"/>
2641   </c>
2642   <c>417</c>
2643   <c>Expectation Failed</c>
2644   <c>
2645      <xref target="status.417"/>
2646   </c>
2647   <c>426</c>
2648   <c>Upgrade Required</c>
2649   <c>
2650      <xref target="status.426"/>
2651   </c>
2652   <c>500</c>
2653   <c>Internal Server Error</c>
2654   <c>
2655      <xref target="status.500"/>
2656   </c>
2657   <c>501</c>
2658   <c>Not Implemented</c>
2659   <c>
2660      <xref target="status.501"/>
2661   </c>
2662   <c>502</c>
2663   <c>Bad Gateway</c>
2664   <c>
2665      <xref target="status.502"/>
2666   </c>
2667   <c>503</c>
2668   <c>Service Unavailable</c>
2669   <c>
2670      <xref target="status.503"/>
2671   </c>
2672   <c>504</c>
2673   <c>Gateway Timeout</c>
2674   <c>
2675      <xref target="status.504"/>
2676   </c>
2677   <c>505</c>
2678   <c>HTTP Version Not Supported</c>
2679   <c>
2680      <xref target="status.505"/>
2681   </c>
2682</texttable>
2683<!--(END)-->
2684
2685</section>
2686<section title="Header Field Registration" anchor="header.field.registration">
2687<t>
2688   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
2689   with the permanent registrations below (see <xref target="RFC3864"/>):
2690</t>
2691
2692<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
2693<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
2694   <ttcol>Header Field Name</ttcol>
2695   <ttcol>Protocol</ttcol>
2696   <ttcol>Status</ttcol>
2697   <ttcol>Reference</ttcol>
2698
2699   <c>Allow</c>
2700   <c>http</c>
2701   <c>standard</c>
2702   <c>
2703      <xref target="header.allow"/>
2704   </c>
2705   <c>Expect</c>
2706   <c>http</c>
2707   <c>standard</c>
2708   <c>
2709      <xref target="header.expect"/>
2710   </c>
2711   <c>From</c>
2712   <c>http</c>
2713   <c>standard</c>
2714   <c>
2715      <xref target="header.from"/>
2716   </c>
2717   <c>Location</c>
2718   <c>http</c>
2719   <c>standard</c>
2720   <c>
2721      <xref target="header.location"/>
2722   </c>
2723   <c>Max-Forwards</c>
2724   <c>http</c>
2725   <c>standard</c>
2726   <c>
2727      <xref target="header.max-forwards"/>
2728   </c>
2729   <c>Referer</c>
2730   <c>http</c>
2731   <c>standard</c>
2732   <c>
2733      <xref target="header.referer"/>
2734   </c>
2735   <c>Retry-After</c>
2736   <c>http</c>
2737   <c>standard</c>
2738   <c>
2739      <xref target="header.retry-after"/>
2740   </c>
2741   <c>Server</c>
2742   <c>http</c>
2743   <c>standard</c>
2744   <c>
2745      <xref target="header.server"/>
2746   </c>
2747   <c>User-Agent</c>
2748   <c>http</c>
2749   <c>standard</c>
2750   <c>
2751      <xref target="header.user-agent"/>
2752   </c>
2753</texttable>
2754<!--(END)-->
2755
2756<t>
2757   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
2758</t>
2759</section>
2760</section>
2761
2762<section title="Security Considerations" anchor="security.considerations">
2763<t>
2764   This section is meant to inform application developers, information
2765   providers, and users of the security limitations in HTTP/1.1 as
2766   described by this document. The discussion does not include
2767   definitive solutions to the problems revealed, though it does make
2768   some suggestions for reducing security risks.
2769</t>
2770
2771<section title="Transfer of Sensitive Information" anchor="security.sensitive">
2772<t>
2773   Like any generic data transfer protocol, HTTP cannot regulate the
2774   content of the data that is transferred, nor is there any a priori
2775   method of determining the sensitivity of any particular piece of
2776   information within the context of any given request. Therefore,
2777   applications SHOULD supply as much control over this information as
2778   possible to the provider of that information. Four header fields are
2779   worth special mention in this context: Server, Via, Referer and From.
2780</t>
2781<t>
2782   Revealing the specific software version of the server might allow the
2783   server machine to become more vulnerable to attacks against software
2784   that is known to contain security holes. Implementors SHOULD make the
2785   Server header field a configurable option.
2786</t>
2787<t>
2788   Proxies which serve as a portal through a network firewall SHOULD
2789   take special precautions regarding the transfer of header information
2790   that identifies the hosts behind the firewall. In particular, they
2791   SHOULD remove, or replace with sanitized versions, any Via fields
2792   generated behind the firewall.
2793</t>
2794<t>
2795   The Referer header field allows reading patterns to be studied and reverse
2796   links drawn. Although it can be very useful, its power can be abused
2797   if user details are not separated from the information contained in
2798   the Referer. Even when the personal information has been removed, the
2799   Referer header field might indicate a private document's URI whose
2800   publication would be inappropriate.
2801</t>
2802<t>
2803   The information sent in the From field might conflict with the user's
2804   privacy interests or their site's security policy, and hence it
2805   SHOULD NOT  be transmitted without the user being able to disable,
2806   enable, and modify the contents of the field. The user MUST be able
2807   to set the contents of this field within a user preference or
2808   application defaults configuration.
2809</t>
2810<t>
2811   We suggest, though do not require, that a convenient toggle interface
2812   be provided for the user to enable or disable the sending of From and
2813   Referer information.
2814</t>
2815<t>
2816   The User-Agent (<xref target="header.user-agent"/>) or Server (<xref target="header.server"/>) header fields can sometimes be used to determine
2817   that a specific client or server have a particular security hole which might
2818   be exploited. Unfortunately, this same information is often used for other
2819   valuable purposes for which HTTP currently has no better mechanism.
2820</t>
2821<t>
2822   Furthermore, the User-Agent header field may contain enough entropy to be
2823   used, possibly in conjunction with other material, to uniquely identify the
2824   user.
2825</t>
2826<t>
2827   Some request methods, like TRACE (<xref target="TRACE"/>), expose information
2828   that was sent in request header fields within the body of their response.
2829   Clients SHOULD be careful with sensitive information, like Cookies,
2830   Authorization credentials, and other header fields that might be used to
2831   collect data from the client.
2832</t> 
2833</section>
2834
2835<section title="Encoding Sensitive Information in URIs" anchor="encoding.sensitive.information.in.uris">
2836<t>
2837   Because the source of a link might be private information or might
2838   reveal an otherwise private information source, it is strongly
2839   recommended that the user be able to select whether or not the
2840   Referer field is sent. For example, a browser client could have a
2841   toggle switch for browsing openly/anonymously, which would
2842   respectively enable/disable the sending of Referer and From
2843   information.
2844</t>
2845<t>
2846   Clients SHOULD NOT include a Referer header field in a (non-secure)
2847   HTTP request if the referring page was transferred with a secure
2848   protocol.
2849</t>
2850<t>
2851   Authors of services SHOULD NOT use GET-based forms for the submission of
2852   sensitive data because that data will be placed in the request-target. Many
2853   existing servers, proxies, and user agents log or display the request-target
2854   in places where it might be visible to third parties. Such services can
2855   use POST-based form submission instead.
2856</t>
2857</section>
2858
2859<section title="Location Headers and Spoofing" anchor="location.spoofing">
2860<t>
2861   If a single server supports multiple organizations that do not trust
2862   one another, then it MUST check the values of Location and Content-Location
2863   header fields in responses that are generated under control of
2864   said organizations to make sure that they do not attempt to
2865   invalidate resources over which they have no authority.
2866</t>
2867</section>
2868
2869<section title="Security Considerations for CONNECT">
2870<t>
2871   Since tunneled data is opaque to the proxy, there are additional
2872   risks to tunneling to other well-known or reserved ports.
2873   A HTTP client CONNECTing to port 25 could relay spam
2874   via SMTP, for example. As such, proxies SHOULD restrict CONNECT
2875   access to a small number of known ports.
2876</t>
2877</section>
2878
2879</section>
2880
2881<section title="Acknowledgments" anchor="ack">
2882</section>
2883</middle>
2884<back>
2885
2886<references title="Normative References">
2887
2888<reference anchor="Part1">
2889  <front>
2890    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
2891    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
2892      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2893      <address><email>fielding@gbiv.com</email></address>
2894    </author>
2895    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2896      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
2897      <address><email>jg@freedesktop.org</email></address>
2898    </author>
2899    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2900      <organization abbrev="HP">Hewlett-Packard Company</organization>
2901      <address><email>JeffMogul@acm.org</email></address>
2902    </author>
2903    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
2904      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2905      <address><email>henrikn@microsoft.com</email></address>
2906    </author>
2907    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2908      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2909      <address><email>LMM@acm.org</email></address>
2910    </author>
2911    <author initials="P." surname="Leach" fullname="Paul J. Leach">
2912      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2913      <address><email>paulle@microsoft.com</email></address>
2914    </author>
2915    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2916      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
2917      <address><email>timbl@w3.org</email></address>
2918    </author>
2919    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
2920      <organization abbrev="W3C">World Wide Web Consortium</organization>
2921      <address><email>ylafon@w3.org</email></address>
2922    </author>
2923    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
2924      <organization abbrev="greenbytes">greenbytes GmbH</organization>
2925      <address><email>julian.reschke@greenbytes.de</email></address>
2926    </author>
2927    <date month="April" year="2011"/>
2928  </front>
2929  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-14"/>
2930 
2931</reference>
2932
2933<reference anchor="Part3">
2934  <front>
2935    <title abbrev="HTTP/1.1">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
2936    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
2937      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2938      <address><email>fielding@gbiv.com</email></address>
2939    </author>
2940    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2941      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
2942      <address><email>jg@freedesktop.org</email></address>
2943    </author>
2944    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2945      <organization abbrev="HP">Hewlett-Packard Company</organization>
2946      <address><email>JeffMogul@acm.org</email></address>
2947    </author>
2948    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
2949      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2950      <address><email>henrikn@microsoft.com</email></address>
2951    </author>
2952    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2953      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2954      <address><email>LMM@acm.org</email></address>
2955    </author>
2956    <author initials="P." surname="Leach" fullname="Paul J. Leach">
2957      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2958      <address><email>paulle@microsoft.com</email></address>
2959    </author>
2960    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2961      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
2962      <address><email>timbl@w3.org</email></address>
2963    </author>
2964    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
2965      <organization abbrev="W3C">World Wide Web Consortium</organization>
2966      <address><email>ylafon@w3.org</email></address>
2967    </author>
2968    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
2969      <organization abbrev="greenbytes">greenbytes GmbH</organization>
2970      <address><email>julian.reschke@greenbytes.de</email></address>
2971    </author>
2972    <date month="April" year="2011"/>
2973  </front>
2974  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p3-payload-14"/>
2975 
2976</reference>
2977
2978<reference anchor="Part4">
2979  <front>
2980    <title abbrev="HTTP/1.1">HTTP/1.1, part 4: Conditional Requests</title>
2981    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
2982      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2983      <address><email>fielding@gbiv.com</email></address>
2984    </author>
2985    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2986      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
2987      <address><email>jg@freedesktop.org</email></address>
2988    </author>
2989    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2990      <organization abbrev="HP">Hewlett-Packard Company</organization>
2991      <address><email>JeffMogul@acm.org</email></address>
2992    </author>
2993    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
2994      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2995      <address><email>henrikn@microsoft.com</email></address>
2996    </author>
2997    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2998      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
2999      <address><email>LMM@acm.org</email></address>
3000    </author>
3001    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3002      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3003      <address><email>paulle@microsoft.com</email></address>
3004    </author>
3005    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3006      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3007      <address><email>timbl@w3.org</email></address>
3008    </author>
3009    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3010      <organization abbrev="W3C">World Wide Web Consortium</organization>
3011      <address><email>ylafon@w3.org</email></address>
3012    </author>
3013    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3014      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3015      <address><email>julian.reschke@greenbytes.de</email></address>
3016    </author>
3017    <date month="April" year="2011"/>
3018  </front>
3019  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-14"/>
3020 
3021</reference>
3022
3023<reference anchor="Part5">
3024  <front>
3025    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
3026    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3027      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
3028      <address><email>fielding@gbiv.com</email></address>
3029    </author>
3030    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3031      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
3032      <address><email>jg@freedesktop.org</email></address>
3033    </author>
3034    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3035      <organization abbrev="HP">Hewlett-Packard Company</organization>
3036      <address><email>JeffMogul@acm.org</email></address>
3037    </author>
3038    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3039      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3040      <address><email>henrikn@microsoft.com</email></address>
3041    </author>
3042    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3043      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
3044      <address><email>LMM@acm.org</email></address>
3045    </author>
3046    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3047      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3048      <address><email>paulle@microsoft.com</email></address>
3049    </author>
3050    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3051      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3052      <address><email>timbl@w3.org</email></address>
3053    </author>
3054    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3055      <organization abbrev="W3C">World Wide Web Consortium</organization>
3056      <address><email>ylafon@w3.org</email></address>
3057    </author>
3058    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3059      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3060      <address><email>julian.reschke@greenbytes.de</email></address>
3061    </author>
3062    <date month="April" year="2011"/>
3063  </front>
3064  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-14"/>
3065 
3066</reference>
3067
3068<reference anchor="Part6">
3069  <front>
3070    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
3071    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3072      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
3073      <address><email>fielding@gbiv.com</email></address>
3074    </author>
3075    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3076      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
3077      <address><email>jg@freedesktop.org</email></address>
3078    </author>
3079    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3080      <organization abbrev="HP">Hewlett-Packard Company</organization>
3081      <address><email>JeffMogul@acm.org</email></address>
3082    </author>
3083    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3084      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3085      <address><email>henrikn@microsoft.com</email></address>
3086    </author>
3087    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3088      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
3089      <address><email>LMM@acm.org</email></address>
3090    </author>
3091    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3092      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3093      <address><email>paulle@microsoft.com</email></address>
3094    </author>
3095    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3096      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3097      <address><email>timbl@w3.org</email></address>
3098    </author>
3099    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3100      <organization abbrev="W3C">World Wide Web Consortium</organization>
3101      <address><email>ylafon@w3.org</email></address>
3102    </author>
3103    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
3104      <address><email>mnot@mnot.net</email></address>
3105    </author>
3106    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3107      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3108      <address><email>julian.reschke@greenbytes.de</email></address>
3109    </author>
3110    <date month="April" year="2011"/>
3111  </front>
3112  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-14"/>
3113 
3114</reference>
3115
3116<reference anchor="Part7">
3117  <front>
3118    <title abbrev="HTTP/1.1">HTTP/1.1, part 7: Authentication</title>
3119    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3120      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
3121      <address><email>fielding@gbiv.com</email></address>
3122    </author>
3123    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3124      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
3125      <address><email>jg@freedesktop.org</email></address>
3126    </author>
3127    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3128      <organization abbrev="HP">Hewlett-Packard Company</organization>
3129      <address><email>JeffMogul@acm.org</email></address>
3130    </author>
3131    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3132      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3133      <address><email>henrikn@microsoft.com</email></address>
3134    </author>
3135    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3136      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
3137      <address><email>LMM@acm.org</email></address>
3138    </author>
3139    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3140      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3141      <address><email>paulle@microsoft.com</email></address>
3142    </author>
3143    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3144      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3145      <address><email>timbl@w3.org</email></address>
3146    </author>
3147    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3148      <organization abbrev="W3C">World Wide Web Consortium</organization>
3149      <address><email>ylafon@w3.org</email></address>
3150    </author>
3151    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3152      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3153      <address><email>julian.reschke@greenbytes.de</email></address>
3154    </author>
3155    <date month="April" year="2011"/>
3156  </front>
3157  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-14"/>
3158 
3159</reference>
3160
3161<reference anchor="RFC2119">
3162  <front>
3163    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
3164    <author initials="S." surname="Bradner" fullname="Scott Bradner">
3165      <organization>Harvard University</organization>
3166      <address><email>sob@harvard.edu</email></address>
3167    </author>
3168    <date month="March" year="1997"/>
3169  </front>
3170  <seriesInfo name="BCP" value="14"/>
3171  <seriesInfo name="RFC" value="2119"/>
3172</reference>
3173
3174<reference anchor="RFC3986">
3175 <front>
3176  <title abbrev="URI Generic Syntax">Uniform Resource Identifier (URI): Generic Syntax</title>
3177  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3178    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3179    <address>
3180       <email>timbl@w3.org</email>
3181       <uri>http://www.w3.org/People/Berners-Lee/</uri>
3182    </address>
3183  </author>
3184  <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
3185    <organization abbrev="Day Software">Day Software</organization>
3186    <address>
3187      <email>fielding@gbiv.com</email>
3188      <uri>http://roy.gbiv.com/</uri>
3189    </address>
3190  </author>
3191  <author initials="L." surname="Masinter" fullname="Larry Masinter">
3192    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
3193    <address>
3194      <email>LMM@acm.org</email>
3195      <uri>http://larry.masinter.net/</uri>
3196    </address>
3197  </author>
3198  <date month="January" year="2005"/>
3199 </front>
3200 <seriesInfo name="STD" value="66"/>
3201 <seriesInfo name="RFC" value="3986"/>
3202</reference>
3203
3204<reference anchor="RFC5234">
3205  <front>
3206    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
3207    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
3208      <organization>Brandenburg InternetWorking</organization>
3209      <address>
3210        <email>dcrocker@bbiw.net</email>
3211      </address> 
3212    </author>
3213    <author initials="P." surname="Overell" fullname="Paul Overell">
3214      <organization>THUS plc.</organization>
3215      <address>
3216        <email>paul.overell@thus.net</email>
3217      </address>
3218    </author>
3219    <date month="January" year="2008"/>
3220  </front>
3221  <seriesInfo name="STD" value="68"/>
3222  <seriesInfo name="RFC" value="5234"/>
3223</reference>
3224
3225</references>
3226
3227<references title="Informative References">
3228
3229<reference anchor="RFC1945">
3230  <front>
3231    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
3232    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3233      <organization>MIT, Laboratory for Computer Science</organization>
3234      <address><email>timbl@w3.org</email></address>
3235    </author>
3236    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
3237      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
3238      <address><email>fielding@ics.uci.edu</email></address>
3239    </author>
3240    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
3241      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
3242      <address><email>frystyk@w3.org</email></address>
3243    </author>
3244    <date month="May" year="1996"/>
3245  </front>
3246  <seriesInfo name="RFC" value="1945"/>
3247</reference>
3248
3249<reference anchor="RFC2068">
3250  <front>
3251    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
3252    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
3253      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
3254      <address><email>fielding@ics.uci.edu</email></address>
3255    </author>
3256    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3257      <organization>MIT Laboratory for Computer Science</organization>
3258      <address><email>jg@w3.org</email></address>
3259    </author>
3260    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3261      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
3262      <address><email>mogul@wrl.dec.com</email></address>
3263    </author>
3264    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
3265      <organization>MIT Laboratory for Computer Science</organization>
3266      <address><email>frystyk@w3.org</email></address>
3267    </author>
3268    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3269      <organization>MIT Laboratory for Computer Science</organization>
3270      <address><email>timbl@w3.org</email></address>
3271    </author>
3272    <date month="January" year="1997"/>
3273  </front>
3274  <seriesInfo name="RFC" value="2068"/>
3275</reference>
3276
3277<reference anchor="RFC2616">
3278  <front>
3279    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
3280    <author initials="R." surname="Fielding" fullname="R. Fielding">
3281      <organization>University of California, Irvine</organization>
3282      <address><email>fielding@ics.uci.edu</email></address>
3283    </author>
3284    <author initials="J." surname="Gettys" fullname="J. Gettys">
3285      <organization>W3C</organization>
3286      <address><email>jg@w3.org</email></address>
3287    </author>
3288    <author initials="J." surname="Mogul" fullname="J. Mogul">
3289      <organization>Compaq Computer Corporation</organization>
3290      <address><email>mogul@wrl.dec.com</email></address>
3291    </author>
3292    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
3293      <organization>MIT Laboratory for Computer Science</organization>
3294      <address><email>frystyk@w3.org</email></address>
3295    </author>
3296    <author initials="L." surname="Masinter" fullname="L. Masinter">
3297      <organization>Xerox Corporation</organization>
3298      <address><email>masinter@parc.xerox.com</email></address>
3299    </author>
3300    <author initials="P." surname="Leach" fullname="P. Leach">
3301      <organization>Microsoft Corporation</organization>
3302      <address><email>paulle@microsoft.com</email></address>
3303    </author>
3304    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
3305      <organization>W3C</organization>
3306      <address><email>timbl@w3.org</email></address>
3307    </author>
3308    <date month="June" year="1999"/>
3309  </front>
3310  <seriesInfo name="RFC" value="2616"/>
3311</reference>
3312
3313<reference anchor="RFC2817">
3314  <front>
3315    <title>Upgrading to TLS Within HTTP/1.1</title>
3316    <author initials="R." surname="Khare" fullname="R. Khare">
3317      <organization>4K Associates / UC Irvine</organization>
3318      <address><email>rohit@4K-associates.com</email></address>
3319    </author>
3320    <author initials="S." surname="Lawrence" fullname="S. Lawrence">
3321      <organization>Agranat Systems, Inc.</organization>
3322      <address><email>lawrence@agranat.com</email></address>
3323    </author>
3324    <date year="2000" month="May"/>
3325  </front>
3326  <seriesInfo name="RFC" value="2817"/>
3327</reference>
3328
3329<reference anchor="RFC3864">
3330  <front>
3331    <title>Registration Procedures for Message Header Fields</title>
3332    <author initials="G." surname="Klyne" fullname="G. Klyne">
3333      <organization>Nine by Nine</organization>
3334      <address><email>GK-IETF@ninebynine.org</email></address>
3335    </author>
3336    <author initials="M." surname="Nottingham" fullname="M. Nottingham">
3337      <organization>BEA Systems</organization>
3338      <address><email>mnot@pobox.com</email></address>
3339    </author>
3340    <author initials="J." surname="Mogul" fullname="J. Mogul">
3341      <organization>HP Labs</organization>
3342      <address><email>JeffMogul@acm.org</email></address>
3343    </author>
3344    <date year="2004" month="September"/>
3345  </front>
3346  <seriesInfo name="BCP" value="90"/>
3347  <seriesInfo name="RFC" value="3864"/>
3348</reference>
3349
3350<reference anchor="RFC5226">
3351  <front>
3352    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
3353    <author initials="T." surname="Narten" fullname="T. Narten">
3354      <organization>IBM</organization>
3355      <address><email>narten@us.ibm.com</email></address>
3356    </author>
3357    <author initials="H." surname="Alvestrand" fullname="H. Alvestrand">
3358      <organization>Google</organization>
3359      <address><email>Harald@Alvestrand.no</email></address>
3360    </author>
3361    <date year="2008" month="May"/>
3362  </front>
3363  <seriesInfo name="BCP" value="26"/>
3364  <seriesInfo name="RFC" value="5226"/>
3365</reference>
3366
3367<reference anchor="RFC5322">
3368  <front>
3369    <title>Internet Message Format</title>
3370    <author initials="P." surname="Resnick" fullname="P. Resnick">
3371      <organization>Qualcomm Incorporated</organization>
3372    </author>
3373    <date year="2008" month="October"/>
3374  </front> 
3375  <seriesInfo name="RFC" value="5322"/>
3376</reference>
3377
3378<reference anchor="RFC5789">
3379  <front>
3380    <title>PATCH Method for HTTP</title>
3381    <author initials="L." surname="Dusseault" fullname="L. Dusseault">
3382      <organization>Linden Lab</organization>
3383    </author>
3384    <author initials="J." surname="Snell" fullname="J. Snell"/>
3385    <date year="2010" month="March"/>
3386  </front>
3387  <seriesInfo name="RFC" value="5789"/>
3388</reference>
3389
3390</references>
3391
3392<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
3393<t>
3394  This document takes over the Status Code Registry, previously defined
3395  in Section 7.1 of <xref target="RFC2817"/>.
3396  (<xref target="status.code.registry"/>)
3397</t>
3398<t>
3399  Clarify definition of POST.
3400  (<xref target="POST"/>)
3401</t>
3402<t>
3403  Remove requirement to handle all Content-* header fields; ban use of
3404  Content-Range with PUT.
3405  (<xref target="PUT"/>)
3406</t>
3407<t>
3408  Take over definition of CONNECT method from <xref target="RFC2817"/>.
3409  (<xref target="CONNECT"/>)
3410</t>
3411<t>
3412  Failed to consider that there are
3413  many other request methods that are safe to automatically redirect,
3414  and further that the user agent is able to make that determination
3415  based on the request method semantics.
3416  (Sections <xref format="counter" target="status.301"/>,
3417  <xref format="counter" target="status.302"/> and
3418  <xref format="counter" target="status.307"/>)
3419</t>
3420<t>
3421  Deprecate 305 Use Proxy status code, because user agents did not implement it.
3422  It used to indicate that the target resource must be accessed through the
3423  proxy given by the Location field. The Location field gave the URI of the
3424  proxy. The recipient was expected to repeat this single request via the proxy.
3425  (<xref target="status.305"/>)
3426</t>
3427<t>
3428  Define status 426 (Upgrade Required) (this was incorporated from
3429  <xref target="RFC2817"/>).
3430  (<xref target="status.426"/>)
3431</t>
3432<t>
3433  Change ABNF productions for header fields to only define the field value.
3434  (<xref target="header.fields"/>)
3435</t>
3436<t>
3437  Reclassify "Allow" as response header field, removing the option to
3438  specify it in a PUT request.
3439  Relax the server requirement on the contents of the Allow header field and
3440  remove requirement on clients to always trust the header field value.
3441  (<xref target="header.allow"/>)
3442</t>
3443<t>
3444  Correct syntax of Location header field to allow URI references (including
3445  relative references and fragments), as referred symbol "absoluteURI" wasn't
3446  what was expected, and add some clarifications as to when use of fragments
3447  would not be appropriate.
3448  (<xref target="header.location"/>)
3449</t>
3450<t>
3451  Restrict Max-Forwards header field to OPTIONS and TRACE (previously,
3452  extension methods could have used it as well).
3453  (<xref target="header.max-forwards"/>)
3454</t>
3455<t>
3456  Allow Referer field value of "about:blank" as alternative to not specifying it.
3457  (<xref target="header.referer"/>)
3458</t>
3459<t>
3460  In the description of the Server header field, the Via field
3461  was described as a SHOULD. The requirement was and is stated
3462  correctly in the description of the Via header field in Section 9.9 of <xref target="Part1"/>.
3463  (<xref target="header.server"/>)
3464</t>
3465</section>
3466
3467
3468<section title="Collected ABNF" anchor="collected.abnf">
3469<figure>
3470<artwork type="abnf" name="p2-semantics.parsed-abnf"><![CDATA[
3471Allow = [ ( "," / Method ) *( OWS "," [ OWS Method ] ) ]
3472
3473Expect = *( "," OWS ) expectation *( OWS "," [ OWS expectation ] )
3474
3475From = mailbox
3476
3477HTTP-date = <HTTP-date, defined in [Part1], Section 6.1>
3478
3479Location = URI-reference
3480
3481Max-Forwards = 1*DIGIT
3482Method = token
3483
3484OWS = <OWS, defined in [Part1], Section 1.2.2>
3485
3486RWS = <RWS, defined in [Part1], Section 1.2.2>
3487Reason-Phrase = *( WSP / VCHAR / obs-text )
3488Referer = absolute-URI / partial-URI
3489Retry-After = HTTP-date / delta-seconds
3490
3491Server = product *( RWS ( product / comment ) )
3492Status-Code = 3DIGIT
3493
3494URI-reference = <URI-reference, defined in [Part1], Section 2.6>
3495User-Agent = product *( RWS ( product / comment ) )
3496
3497absolute-URI = <absolute-URI, defined in [Part1], Section 2.6>
3498
3499comment = <comment, defined in [Part1], Section 3.2>
3500
3501delta-seconds = 1*DIGIT
3502
3503expect-params = ";" token [ "=" ( token / quoted-string ) ]
3504expectation = "100-continue" / expectation-extension
3505expectation-extension = token [ "=" ( token / quoted-string )
3506 *expect-params ]
3507
3508mailbox = <mailbox, defined in [RFC5322], Section 3.4>
3509
3510obs-text = <obs-text, defined in [Part1], Section 1.2.2>
3511
3512partial-URI = <partial-URI, defined in [Part1], Section 2.6>
3513product = <product, defined in [Part1], Section 6.3>
3514
3515quoted-string = <quoted-string, defined in [Part1], Section 1.2.2>
3516
3517token = <token, defined in [Part1], Section 1.2.2>
3518]]></artwork>
3519</figure>
3520<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline"><![CDATA[
3521; Allow defined but not used
3522; Expect defined but not used
3523; From defined but not used
3524; Location defined but not used
3525; Max-Forwards defined but not used
3526; Reason-Phrase defined but not used
3527; Referer defined but not used
3528; Retry-After defined but not used
3529; Server defined but not used
3530; Status-Code defined but not used
3531; User-Agent defined but not used
3532]]></artwork></figure></section>
3533
3534
3535<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
3536
3537<section title="Since RFC 2616">
3538<t>
3539  Extracted relevant partitions from <xref target="RFC2616"/>.
3540</t>
3541</section>
3542
3543<section title="Since draft-ietf-httpbis-p2-semantics-00">
3544<t>
3545  Closed issues:
3546  <list style="symbols"> 
3547    <t>
3548      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/5"/>:
3549      "Via is a MUST"
3550      (<eref target="http://purl.org/NET/http-errata#via-must"/>)
3551    </t>
3552    <t>
3553      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/6"/>:
3554      "Fragments allowed in Location"
3555      (<eref target="http://purl.org/NET/http-errata#location-fragments"/>)
3556    </t>
3557    <t>
3558      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/10"/>:
3559      "Safe Methods vs Redirection"
3560      (<eref target="http://purl.org/NET/http-errata#saferedirect"/>)
3561    </t>
3562    <t>
3563      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/17"/>:
3564      "Revise description of the POST method"
3565      (<eref target="http://purl.org/NET/http-errata#post"/>)
3566    </t>
3567    <t>
3568      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
3569      "Normative and Informative references"
3570    </t>
3571    <t>
3572      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/42"/>:
3573      "RFC2606 Compliance"
3574    </t>
3575    <t>
3576      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/65"/>:
3577      "Informative references"
3578    </t>
3579    <t>
3580      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/84"/>:
3581      "Redundant cross-references"
3582    </t>
3583  </list>
3584</t>
3585<t>
3586  Other changes:
3587  <list style="symbols"> 
3588    <t>
3589      Move definitions of 304 and 412 condition codes to <xref target="Part4"/>
3590    </t>
3591  </list>
3592</t>
3593</section>
3594
3595<section title="Since draft-ietf-httpbis-p2-semantics-01">
3596<t>
3597  Closed issues:
3598  <list style="symbols"> 
3599    <t>
3600      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/21"/>:
3601      "PUT side effects"
3602    </t>
3603    <t>
3604      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/91"/>:
3605      "Duplicate Host header requirements"
3606    </t>
3607  </list>
3608</t>
3609<t>
3610  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
3611  <list style="symbols"> 
3612    <t>
3613      Move "Product Tokens" section (back) into Part 1, as "token" is used
3614      in the definition of the Upgrade header field.
3615    </t>
3616    <t>
3617      Add explicit references to BNF syntax and rules imported from other parts of the specification.
3618    </t>
3619    <t>
3620      Copy definition of delta-seconds from Part6 instead of referencing it.
3621    </t>
3622  </list>
3623</t>
3624</section>
3625
3626<section title="Since draft-ietf-httpbis-p2-semantics-02" anchor="changes.since.02">
3627<t>
3628  Closed issues:
3629  <list style="symbols"> 
3630    <t>
3631      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/24"/>:
3632      "Requiring Allow in 405 responses"
3633    </t>
3634    <t>
3635      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/59"/>:
3636      "Status Code Registry"
3637    </t>
3638    <t>
3639      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/61"/>:
3640      "Redirection vs. Location"
3641    </t>
3642    <t>
3643      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/70"/>:
3644      "Cacheability of 303 response"
3645    </t>
3646    <t>
3647      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/76"/>:
3648      "305 Use Proxy"
3649    </t>
3650    <t>
3651      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/105"/>:
3652      "Classification for Allow header"
3653    </t>
3654    <t>
3655      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/112"/>:
3656      "PUT - 'store under' vs 'store at'"
3657    </t>
3658  </list>
3659</t>
3660<t>
3661  Ongoing work on IANA Message Header Field Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
3662  <list style="symbols"> 
3663    <t>
3664      Reference RFC 3984, and update header field registrations for headers defined
3665      in this document.
3666    </t>
3667  </list>
3668</t>
3669<t>
3670  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
3671  <list style="symbols"> 
3672    <t>
3673      Replace string literals when the string really is case-sensitive (method).
3674    </t>
3675  </list>
3676</t>
3677</section>
3678
3679<section title="Since draft-ietf-httpbis-p2-semantics-03" anchor="changes.since.03">
3680<t>
3681  Closed issues:
3682  <list style="symbols"> 
3683    <t>
3684      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/98"/>:
3685      "OPTIONS request bodies"
3686    </t>
3687    <t>
3688      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/119"/>:
3689      "Description of CONNECT should refer to RFC2817"
3690    </t>
3691    <t>
3692      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/125"/>:
3693      "Location Content-Location reference request/response mixup"
3694    </t>
3695  </list>
3696</t>
3697<t>
3698  Ongoing work on Method Registry (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/72"/>):
3699  <list style="symbols"> 
3700    <t>
3701      Added initial proposal for registration process, plus initial
3702      content (non-HTTP/1.1 methods to be added by a separate specification).
3703    </t>
3704  </list>
3705</t>
3706</section>
3707
3708<section title="Since draft-ietf-httpbis-p2-semantics-04" anchor="changes.since.04">
3709<t>
3710  Closed issues:
3711  <list style="symbols"> 
3712    <t>
3713      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/103"/>:
3714      "Content-*"
3715    </t>
3716    <t>
3717      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
3718      "RFC 2822 is updated by RFC 5322"
3719    </t>
3720  </list>
3721</t>
3722<t>
3723  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
3724  <list style="symbols"> 
3725    <t>
3726      Use "/" instead of "|" for alternatives.
3727    </t>
3728    <t>
3729      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
3730      whitespace ("OWS") and required whitespace ("RWS").
3731    </t>
3732    <t>
3733      Rewrite ABNFs to spell out whitespace rules, factor out
3734      header field value format definitions.
3735    </t>
3736  </list>
3737</t>
3738</section>
3739
3740<section title="Since draft-ietf-httpbis-p2-semantics-05" anchor="changes.since.05">
3741<t>
3742  Closed issues:
3743  <list style="symbols"> 
3744    <t>
3745      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/94"/>:
3746      "Reason-Phrase BNF"
3747    </t>
3748  </list>
3749</t>
3750<t>
3751  Final work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
3752  <list style="symbols"> 
3753    <t>
3754      Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.
3755    </t>
3756  </list>
3757</t>
3758</section>
3759
3760<section title="Since draft-ietf-httpbis-p2-semantics-06" anchor="changes.since.06">
3761<t>
3762  Closed issues:
3763  <list style="symbols"> 
3764    <t>
3765      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/144"/>:
3766      "Clarify when Referer is sent"
3767    </t>
3768    <t>
3769      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/164"/>:
3770      "status codes vs methods"
3771    </t>
3772    <t>
3773      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/170"/>:
3774      "Do not require "updates" relation for specs that register status codes or method names"
3775    </t>
3776  </list>
3777</t>
3778</section>
3779
3780<section title="Since draft-ietf-httpbis-p2-semantics-07" anchor="changes.since.07">
3781<t>
3782  Closed issues:
3783  <list style="symbols"> 
3784    <t>
3785      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/27"/>:
3786      "Idempotency"
3787    </t>
3788    <t>
3789      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/33"/>:
3790      "TRACE security considerations"
3791    </t>
3792    <t>
3793      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/110"/>:
3794      "Clarify rules for determining what entities a response carries"
3795    </t>
3796    <t>
3797      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/140"/>:
3798      "update note citing RFC 1945 and 2068"
3799    </t>
3800    <t>
3801      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/182"/>:
3802      "update note about redirect limit"
3803    </t>
3804    <t>
3805      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/191"/>:
3806      "Location header ABNF should use 'URI'"
3807    </t>
3808    <t>
3809      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/192"/>:
3810      "fragments in Location vs status 303"
3811    </t>
3812    <t>
3813      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/198"/>:
3814      "move IANA registrations for optional status codes"
3815    </t>
3816  </list>
3817</t>
3818<t>
3819  Partly resolved issues:
3820  <list style="symbols"> 
3821    <t>
3822      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/171"/>:
3823      "Are OPTIONS and TRACE safe?"
3824    </t>
3825  </list>
3826</t>
3827</section>
3828
3829<section title="Since draft-ietf-httpbis-p2-semantics-08" anchor="changes.since.08">
3830<t>
3831  Closed issues:
3832  <list style="symbols"> 
3833    <t>
3834      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/10"/>:
3835      "Safe Methods vs Redirection" (we missed the introduction to the 3xx
3836      status codes when fixing this previously)
3837    </t>
3838  </list>
3839</t>
3840</section>
3841
3842<section title="Since draft-ietf-httpbis-p2-semantics-09" anchor="changes.since.09">
3843<t>
3844  Closed issues:
3845  <list style="symbols"> 
3846    <t>
3847      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/43"/>:
3848      "Fragment combination / precedence during redirects"
3849    </t>
3850  </list>
3851</t>
3852<t>
3853  Partly resolved issues:
3854  <list style="symbols"> 
3855    <t>
3856      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/185"/>:
3857      "Location header payload handling"
3858    </t>
3859    <t>
3860      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196"/>:
3861      "Term for the requested resource's URI"
3862    </t>
3863  </list>
3864</t>
3865</section>
3866
3867<section title="Since draft-ietf-httpbis-p2-semantics-10" anchor="changes.since.10">
3868<t>
3869  Closed issues:
3870  <list style="symbols"> 
3871    <t>
3872      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/69"/>:
3873      "Clarify 'Requested Variant'"
3874    </t>
3875    <t>
3876      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/109"/>:
3877      "Clarify entity / representation / variant terminology"
3878    </t>
3879    <t>
3880      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/139"/>:
3881      "Methods and Caching"
3882    </t>
3883    <t>
3884      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/190"/>:
3885      "OPTIONS vs Max-Forwards"
3886    </t>
3887    <t>
3888      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/199"/>:
3889      "Status codes and caching"
3890    </t>
3891    <t>
3892      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/220"/>:
3893      "consider removing the 'changes from 2068' sections"
3894    </t>
3895  </list>
3896</t>
3897</section>
3898
3899<section title="Since draft-ietf-httpbis-p2-semantics-11" anchor="changes.since.11">
3900<t>
3901  Closed issues:
3902  <list style="symbols"> 
3903    <t>
3904      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/229"/>:
3905      "Considerations for new status codes"
3906    </t>
3907    <t>
3908      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/230"/>:
3909      "Considerations for new methods"
3910    </t>
3911    <t>
3912      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/232"/>:
3913      "User-Agent guidelines" (relating to the 'User-Agent' header field)
3914    </t>
3915  </list>
3916</t>
3917</section>
3918
3919<section title="Since draft-ietf-httpbis-p2-semantics-12" anchor="changes.since.12">
3920<t>
3921  Closed issues:
3922  <list style="symbols"> 
3923    <t>
3924      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/43"/>:
3925      "Fragment combination / precedence during redirects" (added warning
3926      about having a fragid on the redirect may cause inconvenience in
3927      some cases)
3928    </t>
3929    <t>
3930      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/79"/>:
3931      "Content-* vs. PUT"
3932    </t>
3933    <t>
3934      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/88"/>:
3935      "205 Bodies"
3936    </t>
3937    <t>
3938      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/102"/>:
3939      "Understanding Content-* on non-PUT requests"
3940    </t>
3941    <t>
3942      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/103"/>:
3943      "Content-*"
3944    </t>
3945    <t>
3946      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/104"/>:
3947      "Header type defaulting"
3948    </t>
3949    <t>
3950      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/112"/>:
3951      "PUT - 'store under' vs 'store at'"
3952    </t>
3953    <t>
3954      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/137"/>:
3955      "duplicate ABNF for Reason-Phrase"
3956    </t>
3957    <t>
3958      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/180"/>:
3959      "Note special status of Content-* prefix in header registration procedures"
3960    </t>
3961    <t>
3962      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/203"/>:
3963      "Max-Forwards vs extension methods"
3964    </t>
3965    <t>
3966      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/213"/>:
3967      "What is the value space of HTTP status codes?" (actually fixed in
3968      draft-ietf-httpbis-p2-semantics-11)
3969    </t>
3970    <t>
3971      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/224"/>:
3972      "Header Classification"
3973    </t>
3974    <t>
3975      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/225"/>:
3976      "PUT side effect: invalidation or just stale?"
3977    </t>
3978    <t>
3979      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/226"/>:
3980      "proxies not supporting certain methods"
3981    </t>
3982    <t>
3983      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/239"/>:
3984      "Migrate CONNECT from RFC2817 to p2"
3985    </t>
3986    <t>
3987      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/240"/>:
3988      "Migrate Upgrade details from RFC2817"
3989    </t>
3990    <t>
3991      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/267"/>:
3992      "clarify PUT semantics'"
3993    </t>
3994    <t>
3995      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/275"/>:
3996      "duplicate ABNF for 'Method'"
3997    </t>
3998    <t>
3999      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/276"/>:
4000      "untangle ABNFs for header fields"
4001    </t>
4002  </list>
4003</t>
4004</section>
4005
4006<section title="Since draft-ietf-httpbis-p2-semantics-13" anchor="changes.since.13">
4007<t>
4008  Closed issues:
4009  <list style="symbols"> 
4010    <t>
4011      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/276"/>:
4012      "untangle ABNFs for header fields"
4013    </t>
4014    <t>
4015      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/251"/>:
4016      "message-body in CONNECT request"
4017    </t>
4018  </list>
4019</t>
4020</section>
4021
4022</section>
4023
4024</back>
4025</rfc>
Note: See TracBrowser for help on using the repository browser.