source: draft-ietf-httpbis/latest/p2-semantics.xml @ 1303

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

update rfc2629.xslt, bump up document dates

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