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

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

Point out that retrieval in HTTP is GET or HEAD (see [1421] and #310)

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