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

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

Resolve #112: replace "to be stored under the supplied Request-URI" by "... at ....". (closes #112).

  • Property svn:eol-style set to native
File size: 127.9 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 "April">
16  <!ENTITY ID-YEAR "2008">
17  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
18  <!ENTITY payload                    "<xref target='Part3' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
19  <!ENTITY conditional                "<xref target='Part4' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY range                      "<xref target='Part5' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY auth                       "<xref target='Part7' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY content-negotiation        "<xref target='Part3' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
24  <!ENTITY notation-abnf              "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
25  <!ENTITY basic-rules                "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26  <!ENTITY general-syntax             "<xref target='Part1' x:rel='#general.syntax' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
27  <!ENTITY uri                        "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
28  <!ENTITY full-date                  "<xref target='Part1' x:rel='#full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
29  <!ENTITY http-url                   "<xref target='Part1' x:rel='#http-url' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
30  <!ENTITY http-version               "<xref target='Part1' x:rel='#http.version' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
31  <!ENTITY use100                     "<xref target='Part1' x:rel='#use.of.the.100.status' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
32  <!ENTITY qvalue                     "<xref target='Part3' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
33  <!ENTITY header-accept              "<xref target='Part3' x:rel='#header.accept' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
34  <!ENTITY header-accept-charset      "<xref target='Part3' x:rel='#header.accept-charset' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
35  <!ENTITY header-accept-encoding     "<xref target='Part3' x:rel='#header.accept-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
36  <!ENTITY header-accept-language     "<xref target='Part3' x:rel='#header.accept-language' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
37  <!ENTITY header-accept-ranges       "<xref target='Part5' x:rel='#header.accept-ranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
38  <!ENTITY header-age                 "<xref target='Part6' x:rel='#header.age' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
39  <!ENTITY header-authorization       "<xref target='Part7' x:rel='#header.authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
40  <!ENTITY header-cache-control       "<xref target='Part6' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
41  <!ENTITY header-content-location    "<xref target='Part3' x:rel='#header.content-location' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
42  <!ENTITY header-content-range       "<xref target='Part5' x:rel='#header.content-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
43  <!ENTITY header-etag                "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
44  <!ENTITY header-expires             "<xref target='Part6' x:rel='#header.expires' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
45  <!ENTITY header-host                "<xref target='Part1' x:rel='#header.host' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
46  <!ENTITY header-if-match            "<xref target='Part4' x:rel='#header.if-match' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
47  <!ENTITY header-if-modified-since   "<xref target='Part4' x:rel='#header.if-modified-since' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
48  <!ENTITY header-if-none-match       "<xref target='Part4' x:rel='#header.if-none-match' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
49  <!ENTITY header-if-range            "<xref target='Part5' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
50  <!ENTITY header-if-unmodified-since "<xref target='Part4' x:rel='#header.if-unmodified-since' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
51  <!ENTITY header-pragma              "<xref target='Part6' x:rel='#header.pragma' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
52  <!ENTITY header-proxy-authenticate  "<xref target='Part7' x:rel='#header.proxy-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
53  <!ENTITY header-proxy-authorization "<xref target='Part7' x:rel='#header.proxy-authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
54  <!ENTITY header-range               "<xref target='Part5' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
55  <!ENTITY header-upgrade             "<xref target='Part5' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
56  <!ENTITY header-te                  "<xref target='Part1' x:rel='#header.upgrade' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
57  <!ENTITY header-vary                "<xref target='Part6' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
58  <!ENTITY header-via                 "<xref target='Part1' x:rel='#header.via' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
59  <!ENTITY header-warning             "<xref target='Part6' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
60  <!ENTITY header-www-authenticate    "<xref target='Part7' x:rel='#header.www-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
61  <!ENTITY message-body               "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
62  <!ENTITY product-tokens             "<xref target='Part1' x:rel='#product.tokens' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
63]>
64<?rfc toc="yes" ?>
65<?rfc symrefs="yes" ?>
66<?rfc sortrefs="yes" ?>
67<?rfc compact="yes"?>
68<?rfc subcompact="no" ?>
69<?rfc linkmailto="no" ?>
70<?rfc editing="no" ?>
71<?rfc comments="yes"?>
72<?rfc inline="yes"?>
73<?rfc-ext allow-markup-in-artwork="yes" ?>
74<?rfc-ext include-references-in-index="yes" ?>
75<rfc obsoletes="2616" category="std"
76     ipr="full3978" docName="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"
77     xmlns:x='http://purl.org/net/xml2rfc/ext'>
78<front>
79
80  <title abbrev="HTTP/1.1, Part 2">HTTP/1.1, part 2: Message Semantics</title>
81
82  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
83    <organization abbrev="Day Software">Day Software</organization>
84    <address>
85      <postal>
86        <street>23 Corporate Plaza DR, Suite 280</street>
87        <city>Newport Beach</city>
88        <region>CA</region>
89        <code>92660</code>
90        <country>USA</country>
91      </postal>
92      <phone>+1-949-706-5300</phone>
93      <facsimile>+1-949-706-5305</facsimile>
94      <email>fielding@gbiv.com</email>
95      <uri>http://roy.gbiv.com/</uri>
96    </address>
97  </author>
98
99  <author initials="J." surname="Gettys" fullname="Jim Gettys">
100    <organization>One Laptop per Child</organization>
101    <address>
102      <postal>
103        <street>21 Oak Knoll Road</street>
104        <city>Carlisle</city>
105        <region>MA</region>
106        <code>01741</code>
107        <country>USA</country>
108      </postal>
109      <email>jg@laptop.org</email>
110      <uri>http://www.laptop.org/</uri>
111    </address>
112  </author>
113 
114  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
115    <organization abbrev="HP">Hewlett-Packard Company</organization>
116    <address>
117      <postal>
118        <street>HP Labs, Large Scale Systems Group</street>
119        <street>1501 Page Mill Road, MS 1177</street>
120        <city>Palo Alto</city>
121        <region>CA</region>
122        <code>94304</code>
123        <country>USA</country>
124      </postal>
125      <email>JeffMogul@acm.org</email>
126    </address>
127  </author>
128
129  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
130    <organization abbrev="Microsoft">Microsoft Corporation</organization>
131    <address>
132      <postal>
133        <street>1 Microsoft Way</street>
134        <city>Redmond</city>
135        <region>WA</region>
136        <code>98052</code>
137        <country>USA</country>
138      </postal>
139      <email>henrikn@microsoft.com</email>
140    </address>
141  </author>
142
143  <author initials="L." surname="Masinter" fullname="Larry Masinter">
144    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
145    <address>
146      <postal>
147        <street>345 Park Ave</street>
148        <city>San Jose</city>
149        <region>CA</region>
150        <code>95110</code>
151        <country>USA</country>
152      </postal>
153      <email>LMM@acm.org</email>
154      <uri>http://larry.masinter.net/</uri>
155    </address>
156  </author>
157 
158  <author initials="P." surname="Leach" fullname="Paul J. Leach">
159    <organization abbrev="Microsoft">Microsoft Corporation</organization>
160    <address>
161      <postal>
162        <street>1 Microsoft Way</street>
163        <city>Redmond</city>
164        <region>WA</region>
165        <code>98052</code>
166      </postal>
167      <email>paulle@microsoft.com</email>
168    </address>
169  </author>
170   
171  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
172    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
173    <address>
174      <postal>
175        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
176        <street>The Stata Center, Building 32</street>
177        <street>32 Vassar Street</street>
178        <city>Cambridge</city>
179        <region>MA</region>
180        <code>02139</code>
181        <country>USA</country>
182      </postal>
183      <email>timbl@w3.org</email>
184      <uri>http://www.w3.org/People/Berners-Lee/</uri>
185    </address>
186  </author>
187
188  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
189    <organization abbrev="W3C">World Wide Web Consortium</organization>
190    <address>
191      <postal>
192        <street>W3C / ERCIM</street>
193        <street>2004, rte des Lucioles</street>
194        <city>Sophia-Antipolis</city>
195        <region>AM</region>
196        <code>06902</code>
197        <country>France</country>
198      </postal>
199      <email>ylafon@w3.org</email>
200      <uri>http://www.raubacapeu.net/people/yves/</uri>
201    </address>
202  </author>
203
204  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
205    <organization abbrev="greenbytes">greenbytes GmbH</organization>
206    <address>
207      <postal>
208        <street>Hafenweg 16</street>
209        <city>Muenster</city><region>NW</region><code>48155</code>
210        <country>Germany</country>
211      </postal>
212      <phone>+49 251 2807760</phone>   
213      <facsimile>+49 251 2807761</facsimile>   
214      <email>julian.reschke@greenbytes.de</email>       
215      <uri>http://greenbytes.de/tech/webdav/</uri>     
216    </address>
217  </author>
218
219  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
220
221<abstract>
222<t>
223   The Hypertext Transfer Protocol (HTTP) is an application-level
224   protocol for distributed, collaborative, hypermedia information
225   systems. HTTP has been in use by the World Wide Web global information
226   initiative since 1990. This document is Part 2 of the seven-part specification
227   that defines the protocol referred to as "HTTP/1.1" and, taken together,
228   obsoletes RFC 2616.  Part 2 defines the semantics of HTTP messages
229   as expressed by request methods, request-header fields, response status codes,
230   and response-header fields.
231</t>
232</abstract>
233
234<note title="Editorial Note (To be removed by RFC Editor)">
235  <t>
236    Discussion of this draft should take place on the HTTPBIS working group
237    mailing list (ietf-http-wg@w3.org). The current issues list is
238    at <eref target="http://www.tools.ietf.org/wg/httpbis/trac/report/11"/>
239    and related documents (including fancy diffs) can be found at
240    <eref target="http://www.tools.ietf.org/wg/httpbis/"/>.
241  </t>
242  <t>
243    This draft incorporates those issue resolutions that were either
244    collected in the original RFC2616 errata list (<eref target="http://purl.org/NET/http-errata"/>),
245    or which were agreed upon on the mailing list between October 2006 and
246    November 2007 (as published in "draft-lafon-rfc2616bis-03").
247  </t>
248</note>
249</front>
250<middle>
251<section title="Introduction" anchor="introduction">
252<t>
253   This document defines HTTP/1.1 request and response semantics.  Each HTTP
254   message, as defined in &messaging;, is in the form of either a request or
255   a response.  An HTTP server listens on a connection for HTTP requests and
256   responds to each request, in the order received on that connection, with
257   one or more HTTP response messages.  This document defines the commonly
258   agreed upon semantics of the HTTP uniform interface, the intentions defined
259   by each request method, and the various response messages that might be
260   expected as a result of applying that method for the requested resource.
261</t>
262<t>
263   This document is currently disorganized in order to minimize the changes
264   between drafts and enable reviewers to see the smaller errata changes.
265   The next draft will reorganize the sections to better reflect the content.
266   In particular, the sections will be ordered according to the typical
267   processing of an HTTP request message (after message parsing): resource
268   mapping, general header fields, methods, request modifiers, response
269   status, and resource metadata.  The current mess reflects how widely
270   dispersed these topics and associated requirements had become in
271   <xref target="RFC2616"/>.
272</t>
273
274<section title="Requirements" anchor="intro.requirements">
275<t>
276   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
277   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
278   document are to be interpreted as described in <xref target="RFC2119"/>.
279</t>
280<t>
281   An implementation is not compliant if it fails to satisfy one or more
282   of the &MUST; or &REQUIRED; level requirements for the protocols it
283   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
284   level and all the &SHOULD; level requirements for its protocols is said
285   to be "unconditionally compliant"; one that satisfies all the &MUST;
286   level requirements but not all the &SHOULD; level requirements for its
287   protocols is said to be "conditionally compliant."
288</t>
289</section>
290</section>
291
292<section title="Notational Conventions and Generic Grammar" anchor="notation">
293  <x:anchor-alias value="comment"/>
294  <x:anchor-alias value="DIGIT"/>
295  <x:anchor-alias value="quoted-string"/>
296  <x:anchor-alias value="token"/>
297<t>
298  This specification uses the ABNF syntax defined in &notation-abnf; and
299  the core rules defined in &basic-rules;:
300  <cref anchor="abnf.dep">ABNF syntax and basic rules will be adopted from RFC 5234, see
301  <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>.</cref>
302</t>
303<figure><artwork type="abnf2616">
304  <x:ref>DIGIT</x:ref>         = &lt;DIGIT, defined in &basic-rules;&gt;
305</artwork></figure>
306<figure><artwork type="abnf2616">
307  <x:anchor-alias value="Accept"/>
308  <x:ref>comment</x:ref>       = &lt;comment, defined in &basic-rules;&gt;
309  <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &basic-rules;&gt;
310  <x:ref>token</x:ref>         = &lt;token, defined in &basic-rules;&gt;
311</artwork></figure>
312<t anchor="abnf.dependencies">
313  <x:anchor-alias value="absoluteURI"/>
314  <x:anchor-alias value="Accept"/>
315  <x:anchor-alias value="Accept-Charset"/>
316  <x:anchor-alias value="Accept-Encoding"/>
317  <x:anchor-alias value="Accept-Language"/>
318  <x:anchor-alias value="Accept-Ranges"/>
319  <x:anchor-alias value="Age"/>
320  <x:anchor-alias value="Authorization"/>
321  <x:anchor-alias value="ETag"/>
322  <x:anchor-alias value="fragment"/>
323  <x:anchor-alias value="Host"/>
324  <x:anchor-alias value="HTTP-date"/>
325  <x:anchor-alias value="If-Match"/>
326  <x:anchor-alias value="If-Modified-Since"/>
327  <x:anchor-alias value="If-None-Match"/>
328  <x:anchor-alias value="If-Range"/>
329  <x:anchor-alias value="If-Unmodified-Since"/>
330  <x:anchor-alias value="product"/>
331  <x:anchor-alias value="Proxy-Authenticate"/>
332  <x:anchor-alias value="Proxy-Authorization"/>
333  <x:anchor-alias value="Range"/>
334  <x:anchor-alias value="relativeURI"/>
335  <x:anchor-alias value="TE"/>
336  <x:anchor-alias value="Vary"/>
337  <x:anchor-alias value="WWW-Authenticate"/>
338  The ABNF rules below are defined in other parts:
339</t>
340<figure><!--Part1--><artwork type="abnf2616">
341  <x:ref>absoluteURI</x:ref>   = &lt;absoluteURI, defined in &general-syntax;&gt;
342  <x:ref>fragment</x:ref>      = &lt;fragment, defined in &general-syntax;&gt;
343  <x:ref>Host</x:ref>          = &lt;Host, defined in &header-host;&gt;
344  <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &full-date;&gt;
345  <x:ref>product</x:ref>       = &lt;product, defined in &product-tokens;&gt;
346  <x:ref>relativeURI</x:ref>   = &lt;relativeURI, defined in &general-syntax;&gt;
347  <x:ref>TE</x:ref>            = &lt;TE, defined in &header-te;&gt;
348</artwork></figure>
349<figure><!--Part3--><artwork type="abnf2616">
350  <x:ref>Accept</x:ref>        = &lt;Accept, defined in &header-accept;&gt;
351  <x:ref>Accept-Charset</x:ref> =
352             &lt;Accept-Charset, defined in &header-accept-charset;&gt;
353  <x:ref>Accept-Encoding</x:ref> =
354             &lt;Accept-Encoding, defined in &header-accept-encoding;&gt;
355  <x:ref>Accept-Language</x:ref> =
356             &lt;Accept-Language, defined in &header-accept-language;&gt;
357</artwork></figure>
358<figure><!--Part4--><artwork type="abnf2616">
359  <x:ref>ETag</x:ref>          = &lt;ETag, defined in &header-etag;&gt;
360  <x:ref>If-Match</x:ref>      = &lt;If-Match, defined in &header-if-match;&gt;
361  <x:ref>If-Modified-Since</x:ref> =
362             &lt;If-Modified-Since, defined in &header-if-modified-since;&gt;
363  <x:ref>If-None-Match</x:ref> = &lt;If-None-Match, defined in &header-if-none-match;&gt;
364  <x:ref>If-Unmodified-Since</x:ref> =
365             &lt;If-Unmodified-Since, defined in &header-if-unmodified-since;&gt;
366</artwork></figure>
367<figure><!--Part5--><artwork type="abnf2616">
368  <x:ref>Accept-Ranges</x:ref> = &lt;Accept-Ranges, defined in &header-accept-ranges;&gt;
369  <x:ref>If-Range</x:ref>      = &lt;If-Range, defined in &header-if-range;&gt;
370  <x:ref>Range</x:ref>         = &lt;Range, defined in &header-range;&gt;
371</artwork></figure>
372<figure><!--Part6--><artwork type="abnf2616">
373  <x:ref>Age</x:ref>           = &lt;Age, defined in &header-age;&gt;
374  <x:ref>Vary</x:ref>          = &lt;Vary, defined in &header-vary;&gt;
375</artwork><!--Part7--></figure>
376<figure><artwork type="abnf2616">
377  <x:ref>Authorization</x:ref> = &lt;Authorization, defined in &header-authorization;&gt;
378  <x:ref>Proxy-Authenticate</x:ref> =
379             &lt;Proxy-Authenticate, defined in &header-proxy-authenticate;&gt;
380  <x:ref>Proxy-Authorization</x:ref> =
381             &lt;Proxy-Authorization, defined in &header-proxy-authorization;&gt;
382  <x:ref>WWW-Authenticate</x:ref> =
383             &lt;WWW-Authenticate, defined in &header-www-authenticate;&gt;
384</artwork></figure>
385</section>
386
387<section title="Method" anchor="method">
388  <x:anchor-alias value="Method"/>
389  <x:anchor-alias value="extension-method"/>
390<t>
391   The Method  token indicates the method to be performed on the
392   resource identified by the Request-URI. The method is case-sensitive.
393</t>
394<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/><iref primary="true" item="Grammar" subitem="extension-method"/>
395  <x:ref>Method</x:ref>         = "OPTIONS"                ; <xref target="OPTIONS"/>
396                 | "GET"                    ; <xref target="GET"/>
397                 | "HEAD"                   ; <xref target="HEAD"/>
398                 | "POST"                   ; <xref target="POST"/>
399                 | "PUT"                    ; <xref target="PUT"/>
400                 | "DELETE"                 ; <xref target="DELETE"/>
401                 | "TRACE"                  ; <xref target="TRACE"/>
402                 | "CONNECT"                ; <xref target="CONNECT"/>
403                 | <x:ref>extension-method</x:ref>
404  <x:ref>extension-method</x:ref> = <x:ref>token</x:ref>
405</artwork></figure>
406<t>
407   The list of methods allowed by a resource can be specified in an
408   Allow header field (<xref target="header.allow"/>). The return code of the response
409   always notifies the client whether a method is currently allowed on a
410   resource, since the set of allowed methods can change dynamically. An
411   origin server &SHOULD; return the status code 405 (Method Not Allowed)
412   if the method is known by the origin server but not allowed for the
413   requested resource, and 501 (Not Implemented) if the method is
414   unrecognized or not implemented by the origin server. The methods GET
415   and HEAD &MUST; be supported by all general-purpose servers. All other
416   methods are &OPTIONAL;; however, if the above methods are implemented,
417   they &MUST; be implemented with the same semantics as those specified
418   in <xref target="method.definitions"/>.
419</t>
420</section>
421
422<section title="Request Header Fields" anchor="request.header.fields">
423  <x:anchor-alias value="extension-code"/>
424  <x:anchor-alias value="request-header"/>
425<t>
426   The request-header fields allow the client to pass additional
427   information about the request, and about the client itself, to the
428   server. These fields act as request modifiers, with semantics
429   equivalent to the parameters on a programming language method
430   invocation.
431</t>
432<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-header"/>
433  <x:ref>request-header</x:ref> = <x:ref>Accept</x:ref>                   ; &header-accept;
434                 | <x:ref>Accept-Charset</x:ref>           ; &header-accept-charset;
435                 | <x:ref>Accept-Encoding</x:ref>          ; &header-accept-encoding;
436                 | <x:ref>Accept-Language</x:ref>          ; &header-accept-language;
437                 | <x:ref>Authorization</x:ref>            ; &header-authorization;
438                 | <x:ref>Expect</x:ref>                   ; <xref target="header.expect"/>
439                 | <x:ref>From</x:ref>                     ; <xref target="header.from"/>
440                 | <x:ref>Host</x:ref>                     ; &header-host;
441                 | <x:ref>If-Match</x:ref>                 ; &header-if-match;
442                 | <x:ref>If-Modified-Since</x:ref>        ; &header-if-modified-since;
443                 | <x:ref>If-None-Match</x:ref>            ; &header-if-none-match;
444                 | <x:ref>If-Range</x:ref>                 ; &header-if-range;
445                 | <x:ref>If-Unmodified-Since</x:ref>      ; &header-if-unmodified-since;
446                 | <x:ref>Max-Forwards</x:ref>             ; <xref target="header.max-forwards"/>
447                 | <x:ref>Proxy-Authorization</x:ref>      ; &header-proxy-authorization;
448                 | <x:ref>Range</x:ref>                    ; &header-range;
449                 | <x:ref>Referer</x:ref>                  ; <xref target="header.referer"/>
450                 | <x:ref>TE</x:ref>                       ; &header-te;
451                 | <x:ref>User-Agent</x:ref>               ; <xref target="header.user-agent"/>
452</artwork></figure>
453<t>
454   Request-header field names can be extended reliably only in
455   combination with a change in the protocol version. However, new or
456   experimental header fields &MAY; be given the semantics of request-header
457   fields if all parties in the communication recognize them to
458   be request-header fields. Unrecognized header fields are treated as
459   entity-header fields.
460</t>
461</section>
462
463<section title="Status Code and Reason Phrase" anchor="status.code.and.reason.phrase">
464  <x:anchor-alias value="Reason-Phrase"/>
465  <x:anchor-alias value="Status-Code"/>
466<t>
467   The Status-Code element is a 3-digit integer result code of the
468   attempt to understand and satisfy the request. The status codes listed
469   below are defined in <xref target="status.codes"/>.
470   The Reason-Phrase is intended to give a short
471   textual description of the Status-Code. The Status-Code is intended
472   for use by automata and the Reason-Phrase is intended for the human
473   user. The client is not required to examine or display the Reason-Phrase.
474</t>
475<t> 
476   The individual values of the numeric status codes defined for
477   HTTP/1.1, and an example set of corresponding Reason-Phrase's, are
478   presented below. The reason phrases listed here are only
479   recommendations -- they &MAY; be replaced by local equivalents without
480   affecting the protocol.
481</t>
482<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"/>
483  <x:ref>Status-Code</x:ref>    =
484         "100"  ; <xref target="status.100"/>: Continue
485       | "101"  ; <xref target="status.101"/>: Switching Protocols
486       | "200"  ; <xref target="status.200"/>: OK
487       | "201"  ; <xref target="status.201"/>: Created
488       | "202"  ; <xref target="status.202"/>: Accepted
489       | "203"  ; <xref target="status.203"/>: Non-Authoritative Information
490       | "204"  ; <xref target="status.204"/>: No Content
491       | "205"  ; <xref target="status.205"/>: Reset Content
492       | "206"  ; <xref target="status.206"/>: Partial Content
493       | "300"  ; <xref target="status.300"/>: Multiple Choices
494       | "301"  ; <xref target="status.301"/>: Moved Permanently
495       | "302"  ; <xref target="status.302"/>: Found
496       | "303"  ; <xref target="status.303"/>: See Other
497       | "304"  ; <xref target="status.304"/>: Not Modified
498       | "305"  ; <xref target="status.305"/>: Use Proxy
499       | "307"  ; <xref target="status.307"/>: Temporary Redirect
500       | "400"  ; <xref target="status.400"/>: Bad Request
501       | "401"  ; <xref target="status.401"/>: Unauthorized
502       | "402"  ; <xref target="status.402"/>: Payment Required
503       | "403"  ; <xref target="status.403"/>: Forbidden
504       | "404"  ; <xref target="status.404"/>: Not Found
505       | "405"  ; <xref target="status.405"/>: Method Not Allowed
506       | "406"  ; <xref target="status.406"/>: Not Acceptable
507       | "407"  ; <xref target="status.407"/>: Proxy Authentication Required
508       | "408"  ; <xref target="status.408"/>: Request Time-out
509       | "409"  ; <xref target="status.409"/>: Conflict
510       | "410"  ; <xref target="status.410"/>: Gone
511       | "411"  ; <xref target="status.411"/>: Length Required
512       | "412"  ; <xref target="status.412"/>: Precondition Failed
513       | "413"  ; <xref target="status.413"/>: Request Entity Too Large
514       | "414"  ; <xref target="status.414"/>: Request-URI Too Large
515       | "415"  ; <xref target="status.415"/>: Unsupported Media Type
516       | "416"  ; <xref target="status.416"/>: Requested range not satisfiable
517       | "417"  ; <xref target="status.417"/>: Expectation Failed
518       | "500"  ; <xref target="status.500"/>: Internal Server Error
519       | "501"  ; <xref target="status.501"/>: Not Implemented
520       | "502"  ; <xref target="status.502"/>: Bad Gateway
521       | "503"  ; <xref target="status.503"/>: Service Unavailable
522       | "504"  ; <xref target="status.504"/>: Gateway Time-out
523       | "505"  ; <xref target="status.505"/>: HTTP Version not supported
524       | <x:ref>extension-code</x:ref>
525
526  <x:ref>extension-code</x:ref> = 3<x:ref>DIGIT</x:ref>
527  <x:ref>Reason-Phrase</x:ref>  = *&lt;<x:ref>TEXT</x:ref>, excluding <x:ref>CR</x:ref>, <x:ref>LF</x:ref>&gt;
528</artwork></figure>
529<t>
530   HTTP status codes are extensible. HTTP applications are not required
531   to understand the meaning of all registered status codes, though such
532   understanding is obviously desirable. However, applications &MUST;
533   understand the class of any status code, as indicated by the first
534   digit, and treat any unrecognized response as being equivalent to the
535   x00 status code of that class, with the exception that an
536   unrecognized response &MUST-NOT; be cached. For example, if an
537   unrecognized status code of 431 is received by the client, it can
538   safely assume that there was something wrong with its request and
539   treat the response as if it had received a 400 status code. In such
540   cases, user agents &SHOULD; present to the user the entity returned
541   with the response, since that entity is likely to include human-readable
542   information which will explain the unusual status.
543</t>
544</section>
545
546<section title="Response Header Fields" anchor="response.header.fields">
547  <x:anchor-alias value="response-header"/>
548<t>
549   The response-header fields allow the server to pass additional
550   information about the response which cannot be placed in the Status-Line.
551   These header fields give information about the server and about
552   further access to the resource identified by the Request-URI.
553</t>
554<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="response-header"/>
555  <x:ref>response-header</x:ref> = <x:ref>Accept-Ranges</x:ref>           ; &header-accept-ranges;
556                  | <x:ref>Age</x:ref>                     ; &header-age;
557                  | <x:ref>Allow</x:ref>                   ; <xref target="header.allow"/>
558                  | <x:ref>ETag</x:ref>                    ; &header-etag;
559                  | <x:ref>Location</x:ref>                ; <xref target="header.location"/>
560                  | <x:ref>Proxy-Authenticate</x:ref>      ; &header-proxy-authenticate;
561                  | <x:ref>Retry-After</x:ref>             ; <xref target="header.retry-after"/>
562                  | <x:ref>Server</x:ref>                  ; <xref target="header.server"/>
563                  | <x:ref>Vary</x:ref>                    ; &header-vary;
564                  | <x:ref>WWW-Authenticate</x:ref>        ; &header-www-authenticate;
565</artwork></figure>
566<t>
567   Response-header field names can be extended reliably only in
568   combination with a change in the protocol version. However, new or
569   experimental header fields &MAY; be given the semantics of response-header
570   fields if all parties in the communication recognize them to
571   be response-header fields. Unrecognized header fields are treated as
572   entity-header fields.
573</t>
574</section>
575
576<section title="Entity" anchor="entity">
577<t>
578   Request and Response messages &MAY; transfer an entity if not otherwise
579   restricted by the request method or response status code. An entity
580   consists of entity-header fields and an entity-body, although some
581   responses will only include the entity-headers. HTTP entity-body and
582   entity-header fields are defined in &payload;.
583</t>
584<t>
585   An entity-body is only present in a message when a message-body is
586   present, as described in &message-body;. The entity-body is obtained
587   from the message-body by decoding any Transfer-Encoding that might
588   have been applied to ensure safe and proper transfer of the message.
589</t>
590</section>
591
592
593<section title="Method Definitions" anchor="method.definitions">
594<t>
595   The set of common methods for HTTP/1.1 is defined below. Although
596   this set can be expanded, additional methods cannot be assumed to
597   share the same semantics for separately extended clients and servers.
598</t>
599
600<section title="Safe and Idempotent Methods" anchor="safe.and.idempotent">
601
602<section title="Safe Methods" anchor="safe.methods">
603<t>
604   Implementors should be aware that the software represents the user in
605   their interactions over the Internet, and should be careful to allow
606   the user to be aware of any actions they might take which may have an
607   unexpected significance to themselves or others.
608</t>
609<t>
610   In particular, the convention has been established that the GET and
611   HEAD methods &SHOULD-NOT;  have the significance of taking an action
612   other than retrieval. These methods ought to be considered "safe".
613   This allows user agents to represent other methods, such as POST, PUT
614   and DELETE, in a special way, so that the user is made aware of the
615   fact that a possibly unsafe action is being requested.
616</t>
617<t>
618   Naturally, it is not possible to ensure that the server does not
619   generate side-effects as a result of performing a GET request; in
620   fact, some dynamic resources consider that a feature. The important
621   distinction here is that the user did not request the side-effects,
622   so therefore cannot be held accountable for them.
623</t>
624</section>
625
626<section title="Idempotent Methods" anchor="idempotent.methods">
627<t>
628   Methods can also have the property of "idempotence" in that (aside
629   from error or expiration issues) the side-effects of N &gt; 0 identical
630   requests is the same as for a single request. The methods GET, HEAD,
631   PUT and DELETE share this property. Also, the methods OPTIONS and
632   TRACE &SHOULD-NOT;  have side effects, and so are inherently idempotent.
633</t>
634<t>
635   However, it is possible that a sequence of several requests is non-idempotent,
636   even if all of the methods executed in that sequence are
637   idempotent. (A sequence is idempotent if a single execution of the
638   entire sequence always yields a result that is not changed by a
639   reexecution of all, or part, of that sequence.) For example, a
640   sequence is non-idempotent if its result depends on a value that is
641   later modified in the same sequence.
642</t>
643<t>
644   A sequence that never has side effects is idempotent, by definition
645   (provided that no concurrent operations are being executed on the
646   same set of resources).
647</t>
648</section>
649</section>
650
651<section title="OPTIONS" anchor="OPTIONS">
652  <iref primary="true" item="OPTIONS method" x:for-anchor=""/>
653  <iref primary="true" item="Methods" subitem="OPTIONS" x:for-anchor=""/>
654<t>
655   The OPTIONS method represents a request for information about the
656   communication options available on the request/response chain
657   identified by the Request-URI. This method allows the client to
658   determine the options and/or requirements associated with a resource,
659   or the capabilities of a server, without implying a resource action
660   or initiating a resource retrieval.
661</t>
662<t>
663   Responses to this method are not cacheable.
664</t>
665<t>
666   If the OPTIONS request includes an entity-body (as indicated by the
667   presence of Content-Length or Transfer-Encoding), then the media type
668   &MUST; be indicated by a Content-Type field. Although this
669   specification does not define any use for such a body, future
670   extensions to HTTP might use the OPTIONS body to make more detailed
671   queries on the server. A server that does not support such an
672   extension &MAY; discard the request body.
673</t>
674<t>
675   If the Request-URI is an asterisk ("*"), the OPTIONS request is
676   intended to apply to the server in general rather than to a specific
677   resource. Since a server's communication options typically depend on
678   the resource, the "*" request is only useful as a "ping" or "no-op"
679   type of method; it does nothing beyond allowing the client to test
680   the capabilities of the server. For example, this can be used to test
681   a proxy for HTTP/1.1 compliance (or lack thereof).
682</t>
683<t>
684   If the Request-URI is not an asterisk, the OPTIONS request applies
685   only to the options that are available when communicating with that
686   resource.
687</t>
688<t>
689   A 200 response &SHOULD; include any header fields that indicate
690   optional features implemented by the server and applicable to that
691   resource (e.g., Allow), possibly including extensions not defined by
692   this specification. The response body, if any, &SHOULD; also include
693   information about the communication options. The format for such a
694   body is not defined by this specification, but might be defined by
695   future extensions to HTTP. Content negotiation &MAY; be used to select
696   the appropriate response format. If no response body is included, the
697   response &MUST; include a Content-Length field with a field-value of
698   "0".
699</t>
700<t>
701   The Max-Forwards request-header field &MAY; be used to target a
702   specific proxy in the request chain. When a proxy receives an OPTIONS
703   request on an absoluteURI for which request forwarding is permitted,
704   the proxy &MUST; check for a Max-Forwards field. If the Max-Forwards
705   field-value is zero ("0"), the proxy &MUST-NOT; forward the message;
706   instead, the proxy &SHOULD; respond with its own communication options.
707   If the Max-Forwards field-value is an integer greater than zero, the
708   proxy &MUST; decrement the field-value when it forwards the request. If
709   no Max-Forwards field is present in the request, then the forwarded
710   request &MUST-NOT; include a Max-Forwards field.
711</t>
712</section>
713
714<section title="GET" anchor="GET">
715  <iref primary="true" item="GET method" x:for-anchor=""/>
716  <iref primary="true" item="Methods" subitem="GET" x:for-anchor=""/>
717<t>
718   The GET method means retrieve whatever information (in the form of an
719   entity) is identified by the Request-URI. If the Request-URI refers
720   to a data-producing process, it is the produced data which shall be
721   returned as the entity in the response and not the source text of the
722   process, unless that text happens to be the output of the process.
723</t>
724<t>
725   The semantics of the GET method change to a "conditional GET" if the
726   request message includes an If-Modified-Since, If-Unmodified-Since,
727   If-Match, If-None-Match, or If-Range header field. A conditional GET
728   method requests that the entity be transferred only under the
729   circumstances described by the conditional header field(s). The
730   conditional GET method is intended to reduce unnecessary network
731   usage by allowing cached entities to be refreshed without requiring
732   multiple requests or transferring data already held by the client.
733</t>
734<t>
735   The semantics of the GET method change to a "partial GET" if the
736   request message includes a Range header field. A partial GET requests
737   that only part of the entity be transferred, as described in &header-range;.
738   The partial GET method is intended to reduce unnecessary
739   network usage by allowing partially-retrieved entities to be
740   completed without transferring data already held by the client.
741</t>
742<t>
743   The response to a GET request is cacheable if and only if it meets
744   the requirements for HTTP caching described in &caching;.
745</t>
746<t>
747   See <xref target="encoding.sensitive.information.in.uris"/> for security considerations when used for forms.
748</t>
749</section>
750
751<section title="HEAD" anchor="HEAD">
752  <iref primary="true" item="HEAD method" x:for-anchor=""/>
753  <iref primary="true" item="Methods" subitem="HEAD" x:for-anchor=""/>
754<t>
755   The HEAD method is identical to GET except that the server &MUST-NOT;
756   return a message-body in the response. The metainformation contained
757   in the HTTP headers in response to a HEAD request &SHOULD; be identical
758   to the information sent in response to a GET request. This method can
759   be used for obtaining metainformation about the entity implied by the
760   request without transferring the entity-body itself. This method is
761   often used for testing hypertext links for validity, accessibility,
762   and recent modification.
763</t>
764<t>
765   The response to a HEAD request &MAY; be cacheable in the sense that the
766   information contained in the response &MAY; be used to update a
767   previously cached entity from that resource. If the new field values
768   indicate that the cached entity differs from the current entity (as
769   would be indicated by a change in Content-Length, Content-MD5, ETag
770   or Last-Modified), then the cache &MUST; treat the cache entry as
771   stale.
772</t>
773</section>
774
775<section title="POST" anchor="POST">
776  <iref primary="true" item="POST method" x:for-anchor=""/>
777  <iref primary="true" item="Methods" subitem="POST" x:for-anchor=""/>
778<t>
779   The POST method is used to request that the origin server accept the
780   entity enclosed in the request as data to be processed by the resource
781   identified by the Request-URI in the Request-Line. POST is designed
782   to allow a uniform method to cover the following functions:
783  <list style="symbols">
784    <t>
785      Annotation of existing resources;
786    </t>
787    <t>
788        Posting a message to a bulletin board, newsgroup, mailing list,
789        or similar group of articles;
790    </t>
791    <t>
792        Providing a block of data, such as the result of submitting a
793        form, to a data-handling process;
794    </t>
795    <t>
796        Extending a database through an append operation.
797    </t>
798  </list>
799</t>
800<t>
801   The actual function performed by the POST method is determined by the
802   server and is usually dependent on the Request-URI.
803</t>
804<t>
805   The action performed by the POST method might not result in a
806   resource that can be identified by a URI. In this case, either 200
807   (OK) or 204 (No Content) is the appropriate response status,
808   depending on whether or not the response includes an entity that
809   describes the result.
810</t>
811<t>
812   If a resource has been created on the origin server, the response
813   &SHOULD; be 201 (Created) and contain an entity which describes the
814   status of the request and refers to the new resource, and a Location
815   header (see <xref target="header.location"/>).
816</t>
817<t>
818   Responses to this method are not cacheable, unless the response
819   includes appropriate Cache-Control or Expires header fields. However,
820   the 303 (See Other) response can be used to direct the user agent to
821   retrieve a cacheable resource.
822</t>
823</section>
824
825<section title="PUT" anchor="PUT">
826  <iref primary="true" item="PUT method" x:for-anchor=""/>
827  <iref primary="true" item="Methods" subitem="PUT" x:for-anchor=""/>
828<t>
829   The PUT method requests that the enclosed entity be stored at the
830   supplied Request-URI. If the Request-URI refers to an already
831   existing resource, the enclosed entity &SHOULD; be considered as a
832   modified version of the one residing on the origin server. If the
833   Request-URI does not point to an existing resource, and that URI is
834   capable of being defined as a new resource by the requesting user
835   agent, the origin server can create the resource with that URI. If a
836   new resource is created at the Request-URI, the origin server &MUST;
837         inform the user agent
838   via the 201 (Created) response. If an existing resource is modified,
839   either the 200 (OK) or 204 (No Content) response codes &SHOULD; be sent
840   to indicate successful completion of the request. If the resource
841   could not be created or modified with the Request-URI, an appropriate
842   error response &SHOULD; be given that reflects the nature of the
843   problem. The recipient of the entity &MUST-NOT; ignore any Content-*
844   (e.g. Content-Range) headers that it does not understand or implement
845   and &MUST; return a 501 (Not Implemented) response in such cases.
846</t>
847<t>
848   If the request passes through a cache and the Request-URI identifies
849   one or more currently cached entities, those entries &SHOULD; be
850   treated as stale. Responses to this method are not cacheable.
851</t>
852<t>
853   The fundamental difference between the POST and PUT requests is
854   reflected in the different meaning of the Request-URI. The URI in a
855   POST request identifies the resource that will handle the enclosed
856   entity. That resource might be a data-accepting process, a gateway to
857   some other protocol, or a separate entity that accepts annotations.
858   In contrast, the URI in a PUT request identifies the entity enclosed
859   with the request -- the user agent knows what URI is intended and the
860   server &MUST-NOT; attempt to apply the request to some other resource.
861   If the server desires that the request be applied to a different URI,
862   it &MUST; send a 301 (Moved Permanently) response; the user agent &MAY;
863   then make its own decision regarding whether or not to redirect the
864   request.
865</t>
866<t>
867   A single resource &MAY; be identified by many different URIs. For
868   example, an article might have a URI for identifying "the current
869   version" which is separate from the URI identifying each particular
870   version. In this case, a PUT request on a general URI might result in
871   several other URIs being defined by the origin server.
872</t>
873<t>
874   HTTP/1.1 does not define how a PUT method affects the state of an
875   origin server.
876</t>
877<t>
878   Unless otherwise specified for a particular entity-header, the
879   entity-headers in the PUT request &SHOULD; be applied to the resource
880   created or modified by the PUT.
881</t>
882</section>
883
884<section title="DELETE" anchor="DELETE">
885  <iref primary="true" item="DELETE method" x:for-anchor=""/>
886  <iref primary="true" item="Methods" subitem="DELETE" x:for-anchor=""/>
887<t>
888   The DELETE method requests that the origin server delete the resource
889   identified by the Request-URI. This method &MAY; be overridden by human
890   intervention (or other means) on the origin server. The client cannot
891   be guaranteed that the operation has been carried out, even if the
892   status code returned from the origin server indicates that the action
893   has been completed successfully. However, the server &SHOULD-NOT; 
894   indicate success unless, at the time the response is given, it
895   intends to delete the resource or move it to an inaccessible
896   location.
897</t>
898<t>
899   A successful response &SHOULD; be 200 (OK) if the response includes an
900   entity describing the status, 202 (Accepted) if the action has not
901   yet been enacted, or 204 (No Content) if the action has been enacted
902   but the response does not include an entity.
903</t>
904<t>
905   If the request passes through a cache and the Request-URI identifies
906   one or more currently cached entities, those entries &SHOULD; be
907   treated as stale. Responses to this method are not cacheable.
908</t>
909</section>
910
911<section title="TRACE" anchor="TRACE">
912  <iref primary="true" item="TRACE method" x:for-anchor=""/>
913  <iref primary="true" item="Methods" subitem="TRACE" x:for-anchor=""/>
914<t>
915   The TRACE method is used to invoke a remote, application-layer loop-back
916   of the request message. The final recipient of the request
917   &SHOULD; reflect the message received back to the client as the
918   entity-body of a 200 (OK) response. The final recipient is either the
919   origin server or the first proxy or gateway to receive a Max-Forwards
920   value of zero (0) in the request (see <xref target="header.max-forwards"/>). A TRACE request
921   &MUST-NOT; include an entity.
922</t>
923<t>
924   TRACE allows the client to see what is being received at the other
925   end of the request chain and use that data for testing or diagnostic
926   information. The value of the Via header field (&header-via;) is of
927   particular interest, since it acts as a trace of the request chain.
928   Use of the Max-Forwards header field allows the client to limit the
929   length of the request chain, which is useful for testing a chain of
930   proxies forwarding messages in an infinite loop.
931</t>
932<t>
933   If the request is valid, the response &SHOULD; contain the entire
934   request message in the entity-body, with a Content-Type of
935   "message/http". Responses to this method &MUST-NOT; be cached.
936</t>
937</section>
938
939<section title="CONNECT" anchor="CONNECT">
940  <iref primary="true" item="CONNECT method" x:for-anchor=""/>
941  <iref primary="true" item="Methods" subitem="CONNECT" x:for-anchor=""/>
942<t>
943   This specification reserves the method name CONNECT for use with a
944   proxy that can dynamically switch to being a tunnel (e.g. SSL
945   tunneling <xref target="Luo1998"/>).
946</t>
947</section>
948</section>
949
950
951<section title="Status Code Definitions" anchor="status.codes">
952<t>
953   Each Status-Code is described below, including a description of which
954   method(s) it can follow and any metainformation required in the
955   response.
956</t>
957
958<section title="Informational 1xx" anchor="status.1xx">
959<t>
960   This class of status code indicates a provisional response,
961   consisting only of the Status-Line and optional headers, and is
962   terminated by an empty line. There are no required headers for this
963   class of status code. Since HTTP/1.0 did not define any 1xx status
964   codes, servers &MUST-NOT; send a 1xx response to an HTTP/1.0 client
965   except under experimental conditions.
966</t>
967<t>
968   A client &MUST; be prepared to accept one or more 1xx status responses
969   prior to a regular response, even if the client does not expect a 100
970   (Continue) status message. Unexpected 1xx status responses &MAY; be
971   ignored by a user agent.
972</t>
973<t>
974   Proxies &MUST; forward 1xx responses, unless the connection between the
975   proxy and its client has been closed, or unless the proxy itself
976   requested the generation of the 1xx response. (For example, if a
977   proxy adds a "Expect: 100-continue" field when it forwards a request,
978   then it need not forward the corresponding 100 (Continue)
979   response(s).)
980</t>
981
982<section title="100 Continue" anchor="status.100">
983  <iref primary="true" item="100 Continue (status code)" x:for-anchor=""/>
984  <iref primary="true" item="Status Codes" subitem="100 Continue" x:for-anchor=""/>
985<t>
986   The client &SHOULD; continue with its request. This interim response is
987   used to inform the client that the initial part of the request has
988   been received and has not yet been rejected by the server. The client
989   &SHOULD; continue by sending the remainder of the request or, if the
990   request has already been completed, ignore this response. The server
991   &MUST; send a final response after the request has been completed. See
992   &use100; for detailed discussion of the use and handling of this
993   status code.
994</t>
995</section>
996
997<section title="101 Switching Protocols" anchor="status.101">
998  <iref primary="true" item="101 Switching Protocols (status code)" x:for-anchor=""/>
999  <iref primary="true" item="Status Codes" subitem="101 Switching Protocols" x:for-anchor=""/>
1000<t>
1001   The server understands and is willing to comply with the client's
1002   request, via the Upgrade message header field (&header-upgrade;), for a
1003   change in the application protocol being used on this connection. The
1004   server will switch protocols to those defined by the response's
1005   Upgrade header field immediately after the empty line which
1006   terminates the 101 response.
1007</t>
1008<t>
1009   The protocol &SHOULD; be switched only when it is advantageous to do
1010   so. For example, switching to a newer version of HTTP is advantageous
1011   over older versions, and switching to a real-time, synchronous
1012   protocol might be advantageous when delivering resources that use
1013   such features.
1014</t>
1015</section>
1016</section>
1017
1018<section title="Successful 2xx" anchor="status.2xx">
1019<t>
1020   This class of status code indicates that the client's request was
1021   successfully received, understood, and accepted.
1022</t>
1023
1024<section title="200 OK" anchor="status.200">
1025  <iref primary="true" item="200 OK (status code)" x:for-anchor=""/>
1026  <iref primary="true" item="Status Codes" subitem="200 OK" x:for-anchor=""/>
1027<t>
1028   The request has succeeded. The information returned with the response
1029   is dependent on the method used in the request, for example:
1030  <list style="hanging">
1031    <t hangText="GET">
1032          an entity corresponding to the requested resource is sent in
1033          the response;
1034    </t>
1035    <t hangText="HEAD">
1036          the entity-header fields corresponding to the requested
1037          resource are sent in the response without any message-body;
1038    </t>
1039    <t hangText="POST">
1040      an entity describing or containing the result of the action;
1041    </t>
1042    <t hangText="TRACE">
1043      an entity containing the request message as received by the
1044      end server.
1045    </t>
1046  </list>
1047</t>
1048</section>
1049
1050<section title="201 Created" anchor="status.201">
1051  <iref primary="true" item="201 Created (status code)" x:for-anchor=""/>
1052  <iref primary="true" item="Status Codes" subitem="201 Created" x:for-anchor=""/>
1053<t>
1054   The request has been fulfilled and resulted in a new resource being
1055   created. The newly created resource can be referenced by the URI(s)
1056   returned in the entity of the response, with the most specific URI
1057   for the resource given by a Location header field. The response
1058   &SHOULD; include an entity containing a list of resource
1059   characteristics and location(s) from which the user or user agent can
1060   choose the one most appropriate. The entity format is specified by
1061   the media type given in the Content-Type header field. The origin
1062   server &MUST; create the resource before returning the 201 status code.
1063   If the action cannot be carried out immediately, the server &SHOULD;
1064   respond with 202 (Accepted) response instead.
1065</t>
1066<t>
1067   A 201 response &MAY; contain an ETag response header field indicating
1068   the current value of the entity tag for the requested variant just
1069   created, see &header-etag;.
1070</t>
1071</section>
1072
1073<section title="202 Accepted" anchor="status.202">
1074  <iref primary="true" item="202 Accepted (status code)" x:for-anchor=""/>
1075  <iref primary="true" item="Status Codes" subitem="202 Accepted" x:for-anchor=""/>
1076<t>
1077   The request has been accepted for processing, but the processing has
1078   not been completed.  The request might or might not eventually be
1079   acted upon, as it might be disallowed when processing actually takes
1080   place. There is no facility for re-sending a status code from an
1081   asynchronous operation such as this.
1082</t>
1083<t>
1084   The 202 response is intentionally non-committal. Its purpose is to
1085   allow a server to accept a request for some other process (perhaps a
1086   batch-oriented process that is only run once per day) without
1087   requiring that the user agent's connection to the server persist
1088   until the process is completed. The entity returned with this
1089   response &SHOULD; include an indication of the request's current status
1090   and either a pointer to a status monitor or some estimate of when the
1091   user can expect the request to be fulfilled.
1092</t>
1093</section>
1094
1095<section title="203 Non-Authoritative Information" anchor="status.203">
1096  <iref primary="true" item="203 Non-Authoritative Information (status code)" x:for-anchor=""/>
1097  <iref primary="true" item="Status Codes" subitem="203 Non-Authoritative Information" x:for-anchor=""/>
1098<t>
1099   The returned metainformation in the entity-header is not the
1100   definitive set as available from the origin server, but is gathered
1101   from a local or a third-party copy. The set presented &MAY; be a subset
1102   or superset of the original version. For example, including local
1103   annotation information about the resource might result in a superset
1104   of the metainformation known by the origin server. Use of this
1105   response code is not required and is only appropriate when the
1106   response would otherwise be 200 (OK).
1107</t>
1108</section>
1109
1110<section title="204 No Content" anchor="status.204">
1111  <iref primary="true" item="204 No Content (status code)" x:for-anchor=""/>
1112  <iref primary="true" item="Status Codes" subitem="204 No Content" x:for-anchor=""/>
1113<t>
1114   The server has fulfilled the request but does not need to return an
1115   entity-body, and might want to return updated metainformation. The
1116   response &MAY; include new or updated metainformation in the form of
1117   entity-headers, which if present &SHOULD; be associated with the
1118   requested variant.
1119</t>
1120<t>
1121   If the client is a user agent, it &SHOULD-NOT;  change its document view
1122   from that which caused the request to be sent. This response is
1123   primarily intended to allow input for actions to take place without
1124   causing a change to the user agent's active document view, although
1125   any new or updated metainformation &SHOULD; be applied to the document
1126   currently in the user agent's active view.
1127</t>
1128<t>
1129   The 204 response &MUST-NOT; include a message-body, and thus is always
1130   terminated by the first empty line after the header fields.
1131</t>
1132</section>
1133
1134<section title="205 Reset Content" anchor="status.205">
1135  <iref primary="true" item="205 Reset Content (status code)" x:for-anchor=""/>
1136  <iref primary="true" item="Status Codes" subitem="205 Reset Content" x:for-anchor=""/>
1137<t>
1138   The server has fulfilled the request and the user agent &SHOULD; reset
1139   the document view which caused the request to be sent. This response
1140   is primarily intended to allow input for actions to take place via
1141   user input, followed by a clearing of the form in which the input is
1142   given so that the user can easily initiate another input action. The
1143   response &MUST-NOT; include an entity.
1144</t>
1145</section>
1146
1147<section title="206 Partial Content" anchor="status.206">
1148  <iref primary="true" item="206 Partial Content (status code)" x:for-anchor=""/>
1149  <iref primary="true" item="Status Codes" subitem="206 Partial Content" x:for-anchor=""/>
1150<t>
1151   The server has fulfilled the partial GET request for the resource
1152   and the enclosed entity is a partial representation as defined in &range;.
1153</t>
1154</section>
1155</section>
1156
1157<section title="Redirection 3xx" anchor="status.3xx">
1158<t>
1159   This class of status code indicates that further action needs to be
1160   taken by the user agent in order to fulfill the request.  The action
1161   required &MAY; be carried out by the user agent without interaction
1162   with the user if and only if the method used in the second request is
1163   GET or HEAD. A client &SHOULD; detect infinite redirection loops, since
1164   such loops generate network traffic for each redirection.
1165  <list><t>
1166      <x:h>Note:</x:h> previous versions of this specification recommended a
1167      maximum of five redirections. Content developers should be aware
1168      that there might be clients that implement such a fixed
1169      limitation.
1170  </t></list>
1171</t>
1172
1173<section title="300 Multiple Choices" anchor="status.300">
1174  <iref primary="true" item="300 Multiple Choices (status code)" x:for-anchor=""/>
1175  <iref primary="true" item="Status Codes" subitem="300 Multiple Choices" x:for-anchor=""/>
1176<t>
1177   The requested resource corresponds to any one of a set of
1178   representations, each with its own specific location, and agent-driven
1179   negotiation information (&content-negotiation;) is being provided so that
1180   the user (or user agent) can select a preferred representation and
1181   redirect its request to that location.
1182</t>
1183<t>
1184   Unless it was a HEAD request, the response &SHOULD; include an entity
1185   containing a list of resource characteristics and location(s) from
1186   which the user or user agent can choose the one most appropriate. The
1187   entity format is specified by the media type given in the Content-Type
1188   header field. Depending upon the format and the capabilities of
1189   the user agent, selection of the most appropriate choice &MAY; be
1190   performed automatically. However, this specification does not define
1191   any standard for such automatic selection.
1192</t>
1193<t>
1194   If the server has a preferred choice of representation, it &SHOULD;
1195   include the specific URI for that representation in the Location
1196   field; user agents &MAY; use the Location field value for automatic
1197   redirection. This response is cacheable unless indicated otherwise.
1198</t>
1199</section>
1200
1201<section title="301 Moved Permanently" anchor="status.301">
1202  <iref primary="true" item="301 Moved Permanently (status code)" x:for-anchor=""/>
1203  <iref primary="true" item="Status Codes" subitem="301 Moved Permanently" x:for-anchor=""/>
1204<t>
1205   The requested resource has been assigned a new permanent URI and any
1206   future references to this resource &SHOULD; use one of the returned
1207   URIs.  Clients with link editing capabilities ought to automatically
1208   re-link references to the Request-URI to one or more of the new
1209   references returned by the server, where possible. This response is
1210   cacheable unless indicated otherwise.
1211</t>
1212<t>
1213   The new permanent URI &SHOULD; be given by the Location field in the
1214   response. Unless the request method was HEAD, the entity of the
1215   response &SHOULD; contain a short hypertext note with a hyperlink to
1216   the new URI(s).
1217</t>
1218<t>
1219   If the 301 status code is received in response to a request method
1220   that is known to be "safe", as defined in <xref target="safe.methods"/>,
1221   then the request &MAY; be automatically redirected by the user agent without
1222   confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
1223   request unless it can be confirmed by the user, since this might
1224   change the conditions under which the request was issued.
1225  <list><t>
1226      <x:h>Note:</x:h> When automatically redirecting a POST request after
1227      receiving a 301 status code, some existing HTTP/1.0 user agents
1228      will erroneously change it into a GET request.
1229  </t></list>
1230</t>
1231</section>
1232
1233<section title="302 Found" anchor="status.302">
1234  <iref primary="true" item="302 Found (status code)" x:for-anchor=""/>
1235  <iref primary="true" item="Status Codes" subitem="302 Found" x:for-anchor=""/>
1236<t>
1237   The requested resource resides temporarily under a different URI.
1238   Since the redirection might be altered on occasion, the client &SHOULD;
1239   continue to use the Request-URI for future requests.  This response
1240   is only cacheable if indicated by a Cache-Control or Expires header
1241   field.
1242</t>
1243<t>
1244   The temporary URI &SHOULD; be given by the Location field in the
1245   response. Unless the request method was HEAD, the entity of the
1246   response &SHOULD; contain a short hypertext note with a hyperlink to
1247   the new URI(s).
1248</t>
1249<t>
1250   If the 302 status code is received in response to a request method
1251   that is known to be "safe", as defined in <xref target="safe.methods"/>,
1252   then the request &MAY; be automatically redirected by the user agent without
1253   confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
1254   request unless it can be confirmed by the user, since this might
1255   change the conditions under which the request was issued.
1256  <list><t>
1257      <x:h>Note:</x:h> <xref target="RFC1945"/> and <xref target="RFC2068"/> specify that the client is not allowed
1258      to change the method on the redirected request.  However, most
1259      existing user agent implementations treat 302 as if it were a 303
1260      response, performing a GET on the Location field-value regardless
1261      of the original request method. The status codes 303 and 307 have
1262      been added for servers that wish to make unambiguously clear which
1263      kind of reaction is expected of the client.
1264  </t></list>
1265</t>
1266</section>
1267
1268<section title="303 See Other" anchor="status.303">
1269  <iref primary="true" item="303 See Other (status code)" x:for-anchor=""/>
1270  <iref primary="true" item="Status Codes" subitem="303 See Other" x:for-anchor=""/>
1271<t>
1272   The response to the request can be found under a different URI and
1273   &SHOULD; be retrieved using a GET method on that resource. This method
1274   exists primarily to allow the output of a POST-activated script to
1275   redirect the user agent to a selected resource. The new URI is not a
1276   substitute reference for the originally requested resource. The 303
1277   response &MUST-NOT; be cached, but the response to the second
1278   (redirected) request might be cacheable.
1279</t>
1280<t>
1281   The different URI &SHOULD; be given by the Location field in the
1282   response. Unless the request method was HEAD, the entity of the
1283   response &SHOULD; contain a short hypertext note with a hyperlink to
1284   the new URI(s).
1285  <list><t>
1286      <x:h>Note:</x:h> Many pre-HTTP/1.1 user agents do not understand the 303
1287      status. When interoperability with such clients is a concern, the
1288      302 status code may be used instead, since most user agents react
1289      to a 302 response as described here for 303.
1290  </t></list>
1291</t>
1292</section>
1293
1294<section title="304 Not Modified" anchor="status.304">
1295  <iref primary="true" item="304 Not Modified (status code)" x:for-anchor=""/>
1296  <iref primary="true" item="Status Codes" subitem="304 Not Modified" x:for-anchor=""/>
1297<t>
1298   The response to the request has not been modified since the conditions
1299   indicated by the client's conditional GET request, as defined in &conditional;.
1300</t>
1301</section>
1302
1303<section title="305 Use Proxy" anchor="status.305">
1304  <iref primary="true" item="305 Use Proxy (status code)" x:for-anchor=""/>
1305  <iref primary="true" item="Status Codes" subitem="305 Use Proxy" x:for-anchor=""/>
1306<t>
1307   The 305 status was defined in a previous version of this specification
1308   (see <xref target="changes.from.rfc.2616"/>), and is now deprecated.
1309</t>
1310</section>
1311
1312<section title="306 (Unused)" anchor="status.306">
1313  <iref primary="true" item="306 (Unused) (status code)" x:for-anchor=""/>
1314  <iref primary="true" item="Status Codes" subitem="306 (Unused)" x:for-anchor=""/>
1315<t>
1316   The 306 status code was used in a previous version of the
1317   specification, is no longer used, and the code is reserved.
1318</t>
1319</section>
1320
1321<section title="307 Temporary Redirect" anchor="status.307">
1322  <iref primary="true" item="307 Temporary Redirect (status code)" x:for-anchor=""/>
1323  <iref primary="true" item="Status Codes" subitem="307 Temporary Redirect" x:for-anchor=""/>
1324<t>
1325   The requested resource resides temporarily under a different URI.
1326   Since the redirection &MAY; be altered on occasion, the client &SHOULD;
1327   continue to use the Request-URI for future requests.  This response
1328   is only cacheable if indicated by a Cache-Control or Expires header
1329   field.
1330</t>
1331<t>
1332   The temporary URI &SHOULD; be given by the Location field in the
1333   response. Unless the request method was HEAD, the entity of the
1334   response &SHOULD; contain a short hypertext note with a hyperlink to
1335   the new URI(s) , since many pre-HTTP/1.1 user agents do not
1336   understand the 307 status. Therefore, the note &SHOULD; contain the
1337   information necessary for a user to repeat the original request on
1338   the new URI.
1339</t>
1340<t>
1341   If the 307 status code is received in response to a request method
1342   that is known to be "safe", as defined in <xref target="safe.methods"/>,
1343   then the request &MAY; be automatically redirected by the user agent without
1344   confirmation.  Otherwise, the user agent &MUST-NOT; automatically redirect the
1345   request unless it can be confirmed by the user, since this might
1346   change the conditions under which the request was issued.
1347</t>
1348</section>
1349</section>
1350
1351<section title="Client Error 4xx" anchor="status.4xx">
1352<t>
1353   The 4xx class of status code is intended for cases in which the
1354   client seems to have erred. Except when responding to a HEAD request,
1355   the server &SHOULD; include an entity containing an explanation of the
1356   error situation, and whether it is a temporary or permanent
1357   condition. These status codes are applicable to any request method.
1358   User agents &SHOULD; display any included entity to the user.
1359</t>
1360<t>
1361   If the client is sending data, a server implementation using TCP
1362   &SHOULD; be careful to ensure that the client acknowledges receipt of
1363   the packet(s) containing the response, before the server closes the
1364   input connection. If the client continues sending data to the server
1365   after the close, the server's TCP stack will send a reset packet to
1366   the client, which may erase the client's unacknowledged input buffers
1367   before they can be read and interpreted by the HTTP application.
1368</t>
1369
1370<section title="400 Bad Request" anchor="status.400">
1371  <iref primary="true" item="400 Bad Request (status code)" x:for-anchor=""/>
1372  <iref primary="true" item="Status Codes" subitem="400 Bad Request" x:for-anchor=""/>
1373<t>
1374   The request could not be understood by the server due to malformed
1375   syntax. The client &SHOULD-NOT;  repeat the request without
1376   modifications.
1377</t>
1378</section>
1379
1380<section title="401 Unauthorized" anchor="status.401">
1381  <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/>
1382  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
1383<t>
1384   The request requires user authentication (see &auth;).
1385</t>
1386</section>
1387
1388<section title="402 Payment Required" anchor="status.402">
1389  <iref primary="true" item="402 Payment Required (status code)" x:for-anchor=""/>
1390  <iref primary="true" item="Status Codes" subitem="402 Payment Required" x:for-anchor=""/>
1391<t>
1392   This code is reserved for future use.
1393</t>
1394</section>
1395
1396<section title="403 Forbidden" anchor="status.403">
1397  <iref primary="true" item="403 Forbidden (status code)" x:for-anchor=""/>
1398  <iref primary="true" item="Status Codes" subitem="403 Forbidden" x:for-anchor=""/>
1399<t>
1400   The server understood the request, but is refusing to fulfill it.
1401   Authorization will not help and the request &SHOULD-NOT;  be repeated.
1402   If the request method was not HEAD and the server wishes to make
1403   public why the request has not been fulfilled, it &SHOULD; describe the
1404   reason for the refusal in the entity.  If the server does not wish to
1405   make this information available to the client, the status code 404
1406   (Not Found) can be used instead.
1407</t>
1408</section>
1409
1410<section title="404 Not Found" anchor="status.404">
1411  <iref primary="true" item="404 Not Found (status code)" x:for-anchor=""/>
1412  <iref primary="true" item="Status Codes" subitem="404 Not Found" x:for-anchor=""/>
1413<t>
1414   The server has not found anything matching the Request-URI. No
1415   indication is given of whether the condition is temporary or
1416   permanent. The 410 (Gone) status code &SHOULD; be used if the server
1417   knows, through some internally configurable mechanism, that an old
1418   resource is permanently unavailable and has no forwarding address.
1419   This status code is commonly used when the server does not wish to
1420   reveal exactly why the request has been refused, or when no other
1421   response is applicable.
1422</t>
1423</section>
1424
1425<section title="405 Method Not Allowed" anchor="status.405">
1426  <iref primary="true" item="405 Method Not Allowed (status code)" x:for-anchor=""/>
1427  <iref primary="true" item="Status Codes" subitem="405 Method Not Allowed" x:for-anchor=""/>
1428<t>
1429   The method specified in the Request-Line is not allowed for the
1430   resource identified by the Request-URI. The response &MUST; include an
1431   Allow header containing a list of valid methods for the requested
1432   resource.
1433</t>
1434</section>
1435
1436<section title="406 Not Acceptable" anchor="status.406">
1437  <iref primary="true" item="406 Not Acceptable (status code)" x:for-anchor=""/>
1438  <iref primary="true" item="Status Codes" subitem="406 Not Acceptable" x:for-anchor=""/>
1439<t>
1440   The resource identified by the request is only capable of generating
1441   response entities which have content characteristics not acceptable
1442   according to the accept headers sent in the request.
1443</t>
1444<t>
1445   Unless it was a HEAD request, the response &SHOULD; include an entity
1446   containing a list of available entity characteristics and location(s)
1447   from which the user or user agent can choose the one most
1448   appropriate. The entity format is specified by the media type given
1449   in the Content-Type header field. Depending upon the format and the
1450   capabilities of the user agent, selection of the most appropriate
1451   choice &MAY; be performed automatically. However, this specification
1452   does not define any standard for such automatic selection.
1453  <list><t>
1454      <x:h>Note:</x:h> HTTP/1.1 servers are allowed to return responses which are
1455      not acceptable according to the accept headers sent in the
1456      request. In some cases, this may even be preferable to sending a
1457      406 response. User agents are encouraged to inspect the headers of
1458      an incoming response to determine if it is acceptable.
1459  </t></list>
1460</t>
1461<t>
1462   If the response could be unacceptable, a user agent &SHOULD;
1463   temporarily stop receipt of more data and query the user for a
1464   decision on further actions.
1465</t>
1466</section>
1467
1468<section title="407 Proxy Authentication Required" anchor="status.407">
1469  <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/>
1470  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/>
1471<t>
1472   This code is similar to 401 (Unauthorized), but indicates that the
1473   client must first authenticate itself with the proxy (see &auth;).
1474</t>
1475</section>
1476
1477<section title="408 Request Timeout" anchor="status.408">
1478  <iref primary="true" item="408 Request Timeout (status code)" x:for-anchor=""/>
1479  <iref primary="true" item="Status Codes" subitem="408 Request Timeout" x:for-anchor=""/>
1480<t>
1481   The client did not produce a request within the time that the server
1482   was prepared to wait. The client &MAY; repeat the request without
1483   modifications at any later time.
1484</t>
1485</section>
1486
1487<section title="409 Conflict" anchor="status.409">
1488  <iref primary="true" item="409 Conflict (status code)" x:for-anchor=""/>
1489  <iref primary="true" item="Status Codes" subitem="409 Conflict" x:for-anchor=""/>
1490<t>
1491   The request could not be completed due to a conflict with the current
1492   state of the resource. This code is only allowed in situations where
1493   it is expected that the user might be able to resolve the conflict
1494   and resubmit the request. The response body &SHOULD; include enough
1495   information for the user to recognize the source of the conflict.
1496   Ideally, the response entity would include enough information for the
1497   user or user agent to fix the problem; however, that might not be
1498   possible and is not required.
1499</t>
1500<t>
1501   Conflicts are most likely to occur in response to a PUT request. For
1502   example, if versioning were being used and the entity being PUT
1503   included changes to a resource which conflict with those made by an
1504   earlier (third-party) request, the server might use the 409 response
1505   to indicate that it can't complete the request. In this case, the
1506   response entity would likely contain a list of the differences
1507   between the two versions in a format defined by the response
1508   Content-Type.
1509</t>
1510</section>
1511
1512<section title="410 Gone" anchor="status.410">
1513  <iref primary="true" item="410 Gone (status code)" x:for-anchor=""/>
1514  <iref primary="true" item="Status Codes" subitem="410 Gone" x:for-anchor=""/>
1515<t>
1516   The requested resource is no longer available at the server and no
1517   forwarding address is known. This condition is expected to be
1518   considered permanent. Clients with link editing capabilities &SHOULD;
1519   delete references to the Request-URI after user approval. If the
1520   server does not know, or has no facility to determine, whether or not
1521   the condition is permanent, the status code 404 (Not Found) &SHOULD; be
1522   used instead. This response is cacheable unless indicated otherwise.
1523</t>
1524<t>
1525   The 410 response is primarily intended to assist the task of web
1526   maintenance by notifying the recipient that the resource is
1527   intentionally unavailable and that the server owners desire that
1528   remote links to that resource be removed. Such an event is common for
1529   limited-time, promotional services and for resources belonging to
1530   individuals no longer working at the server's site. It is not
1531   necessary to mark all permanently unavailable resources as "gone" or
1532   to keep the mark for any length of time -- that is left to the
1533   discretion of the server owner.
1534</t>
1535</section>
1536
1537<section title="411 Length Required" anchor="status.411">
1538  <iref primary="true" item="411 Length Required (status code)" x:for-anchor=""/>
1539  <iref primary="true" item="Status Codes" subitem="411 Length Required" x:for-anchor=""/>
1540<t>
1541   The server refuses to accept the request without a defined Content-Length.
1542   The client &MAY; repeat the request if it adds a valid
1543   Content-Length header field containing the length of the message-body
1544   in the request message.
1545</t>
1546</section>
1547
1548<section title="412 Precondition Failed" anchor="status.412">
1549  <iref primary="true" item="412 Precondition Failed (status code)" x:for-anchor=""/>
1550  <iref primary="true" item="Status Codes" subitem="412 Precondition Failed" x:for-anchor=""/>
1551<t>
1552   The precondition given in one or more of the request-header fields
1553   evaluated to false when it was tested on the server, as defined in
1554   &conditional;.
1555</t>
1556</section>
1557
1558<section title="413 Request Entity Too Large" anchor="status.413">
1559  <iref primary="true" item="413 Request Entity Too Large (status code)" x:for-anchor=""/>
1560  <iref primary="true" item="Status Codes" subitem="413 Request Entity Too Large" x:for-anchor=""/>
1561<t>
1562   The server is refusing to process a request because the request
1563   entity is larger than the server is willing or able to process. The
1564   server &MAY; close the connection to prevent the client from continuing
1565   the request.
1566</t>
1567<t>
1568   If the condition is temporary, the server &SHOULD; include a Retry-After
1569   header field to indicate that it is temporary and after what
1570   time the client &MAY; try again.
1571</t>
1572</section>
1573
1574<section title="414 Request-URI Too Long" anchor="status.414">
1575  <iref primary="true" item="414 Request-URI Too Long (status code)" x:for-anchor=""/>
1576  <iref primary="true" item="Status Codes" subitem="414 Request-URI Too Long" x:for-anchor=""/>
1577<t>
1578   The server is refusing to service the request because the Request-URI
1579   is longer than the server is willing to interpret. This rare
1580   condition is only likely to occur when a client has improperly
1581   converted a POST request to a GET request with long query
1582   information, when the client has descended into a URI "black hole" of
1583   redirection (e.g., a redirected URI prefix that points to a suffix of
1584   itself), or when the server is under attack by a client attempting to
1585   exploit security holes present in some servers using fixed-length
1586   buffers for reading or manipulating the Request-URI.
1587</t>
1588</section>
1589
1590<section title="415 Unsupported Media Type" anchor="status.415">
1591  <iref primary="true" item="415 Unsupported Media Type (status code)" x:for-anchor=""/>
1592  <iref primary="true" item="Status Codes" subitem="415 Unsupported Media Type" x:for-anchor=""/>
1593<t>
1594   The server is refusing to service the request because the entity of
1595   the request is in a format not supported by the requested resource
1596   for the requested method.
1597</t>
1598</section>
1599
1600<section title="416 Requested Range Not Satisfiable" anchor="status.416">
1601  <iref primary="true" item="416 Requested Range Not Satisfiable (status code)" x:for-anchor=""/>
1602  <iref primary="true" item="Status Codes" subitem="416 Requested Range Not Satisfiable" x:for-anchor=""/>
1603<t>
1604   The request included a Range request-header field (&header-range;) and none of
1605   the range-specifier values in this field overlap the current extent
1606   of the selected resource.
1607</t>
1608</section>
1609
1610<section title="417 Expectation Failed" anchor="status.417">
1611  <iref primary="true" item="417 Expectation Failed (status code)" x:for-anchor=""/>
1612  <iref primary="true" item="Status Codes" subitem="417 Expectation Failed" x:for-anchor=""/>
1613<t>
1614   The expectation given in an Expect request-header field (see <xref target="header.expect"/>)
1615   could not be met by this server, or, if the server is a proxy,
1616   the server has unambiguous evidence that the request could not be met
1617   by the next-hop server.
1618</t>
1619</section>
1620</section>
1621
1622<section title="Server Error 5xx" anchor="status.5xx">
1623<t>
1624   Response status codes beginning with the digit "5" indicate cases in
1625   which the server is aware that it has erred or is incapable of
1626   performing the request. Except when responding to a HEAD request, the
1627   server &SHOULD; include an entity containing an explanation of the
1628   error situation, and whether it is a temporary or permanent
1629   condition. User agents &SHOULD; display any included entity to the
1630   user. These response codes are applicable to any request method.
1631</t>
1632
1633<section title="500 Internal Server Error" anchor="status.500">
1634  <iref primary="true" item="500 Internal Server Error (status code)" x:for-anchor=""/>
1635  <iref primary="true" item="Status Codes" subitem="500 Internal Server Error" x:for-anchor=""/>
1636<t>
1637   The server encountered an unexpected condition which prevented it
1638   from fulfilling the request.
1639</t>
1640</section>
1641
1642<section title="501 Not Implemented" anchor="status.501">
1643  <iref primary="true" item="501 Not Implemented (status code)" x:for-anchor=""/>
1644  <iref primary="true" item="Status Codes" subitem="501 Not Implemented" x:for-anchor=""/>
1645<t>
1646   The server does not support the functionality required to fulfill the
1647   request. This is the appropriate response when the server does not
1648   recognize the request method and is not capable of supporting it for
1649   any resource.
1650</t>
1651</section>
1652
1653<section title="502 Bad Gateway" anchor="status.502">
1654  <iref primary="true" item="502 Bad Gateway (status code)" x:for-anchor=""/>
1655  <iref primary="true" item="Status Codes" subitem="502 Bad Gateway" x:for-anchor=""/>
1656<t>
1657   The server, while acting as a gateway or proxy, received an invalid
1658   response from the upstream server it accessed in attempting to
1659   fulfill the request.
1660</t>
1661</section>
1662
1663<section title="503 Service Unavailable" anchor="status.503">
1664  <iref primary="true" item="503 Service Unavailable (status code)" x:for-anchor=""/>
1665  <iref primary="true" item="Status Codes" subitem="503 Service Unavailable" x:for-anchor=""/>
1666<t>
1667   The server is currently unable to handle the request due to a
1668   temporary overloading or maintenance of the server. The implication
1669   is that this is a temporary condition which will be alleviated after
1670   some delay. If known, the length of the delay &MAY; be indicated in a
1671   Retry-After header. If no Retry-After is given, the client &SHOULD;
1672   handle the response as it would for a 500 response.
1673  <list><t>
1674      <x:h>Note:</x:h> The existence of the 503 status code does not imply that a
1675      server must use it when becoming overloaded. Some servers may wish
1676      to simply refuse the connection.
1677  </t></list>
1678</t>
1679</section>
1680
1681<section title="504 Gateway Timeout" anchor="status.504">
1682  <iref primary="true" item="504 Gateway Timeout (status code)" x:for-anchor=""/>
1683  <iref primary="true" item="Status Codes" subitem="504 Gateway Timeout" x:for-anchor=""/>
1684<t>
1685   The server, while acting as a gateway or proxy, did not receive a
1686   timely response from the upstream server specified by the URI (e.g.
1687   HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed
1688   to access in attempting to complete the request.
1689  <list><t>
1690      <x:h>Note:</x:h> Note to implementors: some deployed proxies are known to
1691      return 400 or 500 when DNS lookups time out.
1692  </t></list>
1693</t>
1694</section>
1695
1696<section title="505 HTTP Version Not Supported" anchor="status.505">
1697  <iref primary="true" item="505 HTTP Version Not Supported (status code)" x:for-anchor=""/>
1698  <iref primary="true" item="Status Codes" subitem="505 HTTP Version Not Supported" x:for-anchor=""/>
1699<t>
1700   The server does not support, or refuses to support, the protocol
1701   version that was used in the request message. The server is
1702   indicating that it is unable or unwilling to complete the request
1703   using the same major version as the client, as described in &http-version;,
1704   other than with this error message. The response &SHOULD; contain
1705   an entity describing why that version is not supported and what other
1706   protocols are supported by that server.
1707</t>
1708
1709</section>
1710</section>
1711</section>
1712
1713
1714<section title="Header Field Definitions" anchor="header.fields">
1715<t>
1716   This section defines the syntax and semantics of HTTP/1.1 header fields
1717   related to request and response semantics.
1718</t>
1719<t>
1720   For entity-header fields, both sender and recipient refer to either the
1721   client or the server, depending on who sends and who receives the entity.
1722</t>
1723
1724<section title="Allow" anchor="header.allow">
1725  <iref primary="true" item="Allow header" x:for-anchor=""/>
1726  <iref primary="true" item="Headers" subitem="Allow" x:for-anchor=""/>
1727  <x:anchor-alias value="Allow"/>
1728<t>
1729      The Allow response-header field lists the set of methods advertised as
1730      supported by the resource identified by the Request-URI. The purpose of
1731      this field is strictly to inform the recipient of valid methods
1732      associated with the resource. An Allow header field &MUST; be
1733      present in a 405 (Method Not Allowed) response.
1734</t>
1735<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Allow"/>
1736  <x:ref>Allow</x:ref>   = "Allow" ":" #<x:ref>Method</x:ref>
1737</artwork></figure>
1738<t>
1739      Example of use:
1740</t>
1741<figure><artwork type="example">
1742       Allow: GET, HEAD, PUT
1743</artwork></figure>
1744<t>
1745      The actual set of allowed methods is defined
1746      by the origin server at the time of each request.
1747</t>
1748<t>
1749      A proxy &MUST-NOT; modify the Allow header field even if it does not
1750      understand all the methods specified, since the user agent might
1751      have other means of communicating with the origin server.
1752</t>
1753</section>
1754
1755<section title="Expect" anchor="header.expect">
1756  <iref primary="true" item="Expect header" x:for-anchor=""/>
1757  <iref primary="true" item="Headers" subitem="Expect" x:for-anchor=""/>
1758  <x:anchor-alias value="Expect"/>
1759  <x:anchor-alias value="expectation"/>
1760  <x:anchor-alias value="expectation-extension"/>
1761  <x:anchor-alias value="expect-params"/>
1762<t>
1763   The Expect request-header field is used to indicate that particular
1764   server behaviors are required by the client.
1765</t>
1766<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"/>
1767  <x:ref>Expect</x:ref>       =  "Expect" ":" 1#<x:ref>expectation</x:ref>
1768 
1769  <x:ref>expectation</x:ref>  =  "100-continue" | <x:ref>expectation-extension</x:ref>
1770  <x:ref>expectation-extension</x:ref> =  <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> | <x:ref>quoted-string</x:ref> )
1771                           *<x:ref>expect-params</x:ref> ]
1772  <x:ref>expect-params</x:ref> =  ";" <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> | <x:ref>quoted-string</x:ref> ) ]
1773</artwork></figure>
1774<t>
1775   A server that does not understand or is unable to comply with any of
1776   the expectation values in the Expect field of a request &MUST; respond
1777   with appropriate error status. The server &MUST; respond with a 417
1778   (Expectation Failed) status if any of the expectations cannot be met
1779   or, if there are other problems with the request, some other 4xx
1780   status.
1781</t>
1782<t>
1783   This header field is defined with extensible syntax to allow for
1784   future extensions. If a server receives a request containing an
1785   Expect field that includes an expectation-extension that it does not
1786   support, it &MUST; respond with a 417 (Expectation Failed) status.
1787</t>
1788<t>
1789   Comparison of expectation values is case-insensitive for unquoted
1790   tokens (including the 100-continue token), and is case-sensitive for
1791   quoted-string expectation-extensions.
1792</t>
1793<t>
1794   The Expect mechanism is hop-by-hop: that is, an HTTP/1.1 proxy &MUST;
1795   return a 417 (Expectation Failed) status if it receives a request
1796   with an expectation that it cannot meet. However, the Expect
1797   request-header itself is end-to-end; it &MUST; be forwarded if the
1798   request is forwarded.
1799</t>
1800<t>
1801   Many older HTTP/1.0 and HTTP/1.1 applications do not understand the
1802   Expect header.
1803</t>
1804<t>
1805   See &use100; for the use of the 100 (Continue) status.
1806</t>
1807</section>
1808
1809<section title="From" anchor="header.from">
1810  <iref primary="true" item="From header" x:for-anchor=""/>
1811  <iref primary="true" item="Headers" subitem="From" x:for-anchor=""/>
1812  <x:anchor-alias value="From"/>
1813  <x:anchor-alias value="mailbox"/>
1814<t>
1815   The From request-header field, if given, &SHOULD; contain an Internet
1816   e-mail address for the human user who controls the requesting user
1817   agent. The address &SHOULD; be machine-usable, as defined by "mailbox"
1818   in <xref x:sec="3.4" x:fmt="of" target="RFC2822"/>:
1819</t>
1820<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="From"/>
1821  <x:ref>From</x:ref>    = "From" ":" <x:ref>mailbox</x:ref>
1822 
1823  <x:ref>mailbox</x:ref> = &lt;mailbox, defined in <xref x:sec="3.4" x:fmt="," target="RFC2822"/>&gt;
1824</artwork></figure>
1825<t>
1826   An example is:
1827</t>
1828<figure><artwork type="example">
1829    From: webmaster@example.org
1830</artwork></figure>
1831<t>
1832   This header field &MAY; be used for logging purposes and as a means for
1833   identifying the source of invalid or unwanted requests. It &SHOULD-NOT; 
1834   be used as an insecure form of access protection. The interpretation
1835   of this field is that the request is being performed on behalf of the
1836   person given, who accepts responsibility for the method performed. In
1837   particular, robot agents &SHOULD; include this header so that the
1838   person responsible for running the robot can be contacted if problems
1839   occur on the receiving end.
1840</t>
1841<t>
1842   The Internet e-mail address in this field &MAY; be separate from the
1843   Internet host which issued the request. For example, when a request
1844   is passed through a proxy the original issuer's address &SHOULD; be
1845   used.
1846</t>
1847<t>
1848   The client &SHOULD-NOT;  send the From header field without the user's
1849   approval, as it might conflict with the user's privacy interests or
1850   their site's security policy. It is strongly recommended that the
1851   user be able to disable, enable, and modify the value of this field
1852   at any time prior to a request.
1853</t>
1854</section>
1855
1856<section title="Location" anchor="header.location">
1857  <iref primary="true" item="Location header" x:for-anchor=""/>
1858  <iref primary="true" item="Headers" subitem="Location" x:for-anchor=""/>
1859  <x:anchor-alias value="Location"/>
1860<t>
1861   The Location response-header field is used for the identification of a
1862   new resource or to redirect the recipient to a location other than the
1863   Request-URI for completion of the request.  For 201 (Created)
1864   responses, the Location is that of the new resource which was created
1865   by the request. For 3xx responses, the location &SHOULD; indicate the
1866   server's preferred URI for automatic redirection to the resource. The
1867   field value consists of a single absolute URI.
1868</t>
1869<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Location"/>
1870  <x:ref>Location</x:ref>       = "Location" ":" <x:ref>absoluteURI</x:ref> [ "#" <x:ref>fragment</x:ref> ]
1871</artwork></figure>
1872<t>
1873   An example is:
1874</t>
1875<figure><artwork type="example">
1876    Location: http://www.example.org/pub/WWW/People.html
1877</artwork></figure>
1878<t>
1879  <list><t>
1880      <x:h>Note:</x:h> The Content-Location header field (&header-content-location;) differs
1881      from Location in that the Content-Location identifies the original
1882      location of the entity enclosed in the request. It is therefore
1883      possible for a response to contain header fields for both Location
1884      and Content-Location.
1885  </t></list>
1886</t>
1887<t>
1888   There are circumstances in which a fragment identifier in a Location URL would not be appropriate:
1889   <list style="symbols">
1890      <t>With a 201 Created response, because in this usage the Location header specifies the URL for the entire created resource.</t>
1891      <t>With a 300 Multiple Choices, since the choice decision is intended to be made on resource characteristics and not fragment characteristics.</t>
1892      <t>With 305 Use Proxy.</t>
1893   </list>
1894</t>
1895</section>
1896
1897<section title="Max-Forwards" anchor="header.max-forwards">
1898  <iref primary="true" item="Max-Forwards header" x:for-anchor=""/>
1899  <iref primary="true" item="Headers" subitem="Max-Forwards" x:for-anchor=""/>
1900  <x:anchor-alias value="Max-Forwards"/>
1901<t>
1902   The Max-Forwards request-header field provides a mechanism with the
1903   TRACE (<xref target="TRACE"/>) and OPTIONS (<xref target="OPTIONS"/>) methods to limit the
1904   number of proxies or gateways that can forward the request to the
1905   next inbound server. This can be useful when the client is attempting
1906   to trace a request chain which appears to be failing or looping in
1907   mid-chain.
1908</t>
1909<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Max-Forwards"/>
1910  <x:ref>Max-Forwards</x:ref>   = "Max-Forwards" ":" 1*<x:ref>DIGIT</x:ref>
1911</artwork></figure>
1912<t>
1913   The Max-Forwards value is a decimal integer indicating the remaining
1914   number of times this request message may be forwarded.
1915</t>
1916<t>
1917   Each proxy or gateway recipient of a TRACE or OPTIONS request
1918   containing a Max-Forwards header field &MUST; check and update its
1919   value prior to forwarding the request. If the received value is zero
1920   (0), the recipient &MUST-NOT; forward the request; instead, it &MUST;
1921   respond as the final recipient. If the received Max-Forwards value is
1922   greater than zero, then the forwarded message &MUST; contain an updated
1923   Max-Forwards field with a value decremented by one (1).
1924</t>
1925<t>
1926   The Max-Forwards header field &MAY; be ignored for all other methods
1927   defined by this specification and for any extension methods for which
1928   it is not explicitly referred to as part of that method definition.
1929</t>
1930</section>
1931
1932<section title="Referer" anchor="header.referer">
1933  <iref primary="true" item="Referer header" x:for-anchor=""/>
1934  <iref primary="true" item="Headers" subitem="Referer" x:for-anchor=""/>
1935  <x:anchor-alias value="Referer"/>
1936<t>
1937   The Referer[sic] request-header field allows the client to specify,
1938   for the server's benefit, the address (URI) of the resource from
1939   which the Request-URI was obtained (the "referrer", although the
1940   header field is misspelled.) The Referer request-header allows a
1941   server to generate lists of back-links to resources for interest,
1942   logging, optimized caching, etc. It also allows obsolete or mistyped
1943   links to be traced for maintenance. The Referer field &MUST-NOT; be
1944   sent if the Request-URI was obtained from a source that does not have
1945   its own URI, such as input from the user keyboard.
1946</t>
1947<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Referer"/>
1948  <x:ref>Referer</x:ref>        = "Referer" ":" ( <x:ref>absoluteURI</x:ref> | <x:ref>relativeURI</x:ref> )
1949</artwork></figure>
1950<t>
1951   Example:
1952</t>
1953<figure><artwork type="example">
1954    Referer: http://www.example.org/hypertext/Overview.html
1955</artwork></figure>
1956<t>
1957   If the field value is a relative URI, it &SHOULD; be interpreted
1958   relative to the Request-URI. The URI &MUST-NOT; include a fragment. See
1959   <xref target="encoding.sensitive.information.in.uris"/> for security considerations.
1960</t>
1961</section>
1962
1963<section title="Retry-After" anchor="header.retry-after">
1964  <iref primary="true" item="Retry-After header" x:for-anchor=""/>
1965  <iref primary="true" item="Headers" subitem="Retry-After" x:for-anchor=""/>
1966  <x:anchor-alias value="Retry-After"/>
1967<t>
1968   The Retry-After response-header field can be used with a 503 (Service
1969   Unavailable) response to indicate how long the service is expected to
1970   be unavailable to the requesting client. This field &MAY; also be used
1971   with any 3xx (Redirection) response to indicate the minimum time the
1972   user-agent is asked wait before issuing the redirected request. The
1973   value of this field can be either an HTTP-date or an integer number
1974   of seconds (in decimal) after the time of the response.
1975</t>
1976<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Retry-After"/>
1977  <x:ref>Retry-After</x:ref>   = "Retry-After" ":" ( <x:ref>HTTP-date</x:ref> | <x:ref>delta-seconds</x:ref> )
1978</artwork></figure>
1979<t anchor="rule.delta-seconds">
1980  <x:anchor-alias value="delta-seconds"/>
1981   Time spans are non-negative decimal integers, representing time in
1982   seconds.
1983</t>
1984<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="delta-seconds"/>
1985  <x:ref>delta-seconds</x:ref>  = 1*<x:ref>DIGIT</x:ref>
1986</artwork></figure>
1987<t>
1988   Two examples of its use are
1989</t>
1990<figure><artwork type="example">
1991    Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
1992    Retry-After: 120
1993</artwork></figure>
1994<t>
1995   In the latter example, the delay is 2 minutes.
1996</t>
1997</section>
1998
1999<section title="Server" anchor="header.server">
2000  <iref primary="true" item="Server header" x:for-anchor=""/>
2001  <iref primary="true" item="Headers" subitem="Server" x:for-anchor=""/>
2002  <x:anchor-alias value="Server"/>
2003<t>
2004   The Server response-header field contains information about the
2005   software used by the origin server to handle the request. The field
2006   can contain multiple product tokens (&product-tokens;) and comments
2007   identifying the server and any significant subproducts. The product
2008   tokens are listed in order of their significance for identifying the
2009   application.
2010</t>
2011<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Server"/>
2012  <x:ref>Server</x:ref>         = "Server" ":" 1*( <x:ref>product</x:ref> | <x:ref>comment</x:ref> )
2013</artwork></figure>
2014<t>
2015   Example:
2016</t>
2017<figure><artwork type="example">
2018    Server: CERN/3.0 libwww/2.17
2019</artwork></figure>
2020<t>
2021   If the response is being forwarded through a proxy, the proxy
2022   application &MUST-NOT; modify the Server response-header. Instead, it
2023   &MUST; include a Via field (as described in &header-via;).
2024  <list><t>
2025      <x:h>Note:</x:h> Revealing the specific software version of the server might
2026      allow the server machine to become more vulnerable to attacks
2027      against software that is known to contain security holes. Server
2028      implementors are encouraged to make this field a configurable
2029      option.
2030  </t></list>
2031</t>
2032</section>
2033
2034<section title="User-Agent" anchor="header.user-agent">
2035  <iref primary="true" item="User-Agent header" x:for-anchor=""/>
2036  <iref primary="true" item="Headers" subitem="User-Agent" x:for-anchor=""/>
2037  <x:anchor-alias value="User-Agent"/>
2038<t>
2039   The User-Agent request-header field contains information about the
2040   user agent originating the request. This is for statistical purposes,
2041   the tracing of protocol violations, and automated recognition of user
2042   agents for the sake of tailoring responses to avoid particular user
2043   agent limitations. User agents &SHOULD; include this field with
2044   requests. The field can contain multiple product tokens (&product-tokens;)
2045   and comments identifying the agent and any subproducts which form a
2046   significant part of the user agent. By convention, the product tokens
2047   are listed in order of their significance for identifying the
2048   application.
2049</t>
2050<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="User-Agent"/>
2051  <x:ref>User-Agent</x:ref>     = "User-Agent" ":" 1*( <x:ref>product</x:ref> | <x:ref>comment</x:ref> )
2052</artwork></figure>
2053<t>
2054   Example:
2055</t>
2056<figure><artwork type="example">
2057    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
2058</artwork></figure>
2059</section>
2060
2061</section>
2062
2063<section title="IANA Considerations" anchor="IANA.considerations">
2064<t>
2065   <cref>TBD.</cref>
2066</t>
2067</section>
2068
2069<section title="Security Considerations" anchor="security.considerations">
2070<t>
2071   This section is meant to inform application developers, information
2072   providers, and users of the security limitations in HTTP/1.1 as
2073   described by this document. The discussion does not include
2074   definitive solutions to the problems revealed, though it does make
2075   some suggestions for reducing security risks.
2076</t>
2077
2078<section title="Transfer of Sensitive Information" anchor="security.sensitive">
2079<t>
2080   Like any generic data transfer protocol, HTTP cannot regulate the
2081   content of the data that is transferred, nor is there any a priori
2082   method of determining the sensitivity of any particular piece of
2083   information within the context of any given request. Therefore,
2084   applications &SHOULD; supply as much control over this information as
2085   possible to the provider of that information. Four header fields are
2086   worth special mention in this context: Server, Via, Referer and From.
2087</t>
2088<t>
2089   Revealing the specific software version of the server might allow the
2090   server machine to become more vulnerable to attacks against software
2091   that is known to contain security holes. Implementors &SHOULD; make the
2092   Server header field a configurable option.
2093</t>
2094<t>
2095   Proxies which serve as a portal through a network firewall &SHOULD;
2096   take special precautions regarding the transfer of header information
2097   that identifies the hosts behind the firewall. In particular, they
2098   &SHOULD; remove, or replace with sanitized versions, any Via fields
2099   generated behind the firewall.
2100</t>
2101<t>
2102   The Referer header allows reading patterns to be studied and reverse
2103   links drawn. Although it can be very useful, its power can be abused
2104   if user details are not separated from the information contained in
2105   the Referer. Even when the personal information has been removed, the
2106   Referer header might indicate a private document's URI whose
2107   publication would be inappropriate.
2108</t>
2109<t>
2110   The information sent in the From field might conflict with the user's
2111   privacy interests or their site's security policy, and hence it
2112   &SHOULD-NOT;  be transmitted without the user being able to disable,
2113   enable, and modify the contents of the field. The user &MUST; be able
2114   to set the contents of this field within a user preference or
2115   application defaults configuration.
2116</t>
2117<t>
2118   We suggest, though do not require, that a convenient toggle interface
2119   be provided for the user to enable or disable the sending of From and
2120   Referer information.
2121</t>
2122<t>
2123   The User-Agent (<xref target="header.user-agent"/>) or Server (<xref target="header.server"/>) header
2124   fields can sometimes be used to determine that a specific client or
2125   server have a particular security hole which might be exploited.
2126   Unfortunately, this same information is often used for other valuable
2127   purposes for which HTTP currently has no better mechanism.
2128</t>
2129</section>
2130
2131<section title="Encoding Sensitive Information in URIs" anchor="encoding.sensitive.information.in.uris">
2132<t>
2133   Because the source of a link might be private information or might
2134   reveal an otherwise private information source, it is strongly
2135   recommended that the user be able to select whether or not the
2136   Referer field is sent. For example, a browser client could have a
2137   toggle switch for browsing openly/anonymously, which would
2138   respectively enable/disable the sending of Referer and From
2139   information.
2140</t>
2141<t>
2142   Clients &SHOULD-NOT; include a Referer header field in a (non-secure)
2143   HTTP request if the referring page was transferred with a secure
2144   protocol.
2145</t>
2146<t>
2147   Authors of services should not use
2148   GET-based forms for the submission of sensitive data because that
2149   data will be encoded in the Request-URI. Many existing
2150   servers, proxies, and user agents log or display the Request-URI in
2151   places where it might be visible to third parties. Such services can
2152   use POST-based form submission instead.
2153</t>
2154</section>
2155
2156<section title="Location Headers and Spoofing" anchor="location.spoofing">
2157<t>
2158   If a single server supports multiple organizations that do not trust
2159   one another, then it &MUST; check the values of Location and Content-Location
2160   headers in responses that are generated under control of
2161   said organizations to make sure that they do not attempt to
2162   invalidate resources over which they have no authority.
2163</t>
2164</section>
2165
2166</section>
2167
2168<section title="Acknowledgments" anchor="ack">
2169</section>
2170</middle>
2171<back>
2172
2173<references title="Normative References">
2174
2175<reference anchor="Part1">
2176  <front>
2177    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
2178    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
2179      <organization abbrev="Day Software">Day Software</organization>
2180      <address><email>fielding@gbiv.com</email></address>
2181    </author>
2182    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2183      <organization>One Laptop per Child</organization>
2184      <address><email>jg@laptop.org</email></address>
2185    </author>
2186    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2187      <organization abbrev="HP">Hewlett-Packard Company</organization>
2188      <address><email>JeffMogul@acm.org</email></address>
2189    </author>
2190    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
2191      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2192      <address><email>henrikn@microsoft.com</email></address>
2193    </author>
2194    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2195      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
2196      <address><email>LMM@acm.org</email></address>
2197    </author>
2198    <author initials="P." surname="Leach" fullname="Paul J. Leach">
2199      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2200      <address><email>paulle@microsoft.com</email></address>
2201    </author>
2202    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2203      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
2204      <address><email>timbl@w3.org</email></address>
2205    </author>
2206    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
2207      <organization abbrev="W3C">World Wide Web Consortium</organization>
2208      <address><email>ylafon@w3.org</email></address>
2209    </author>
2210    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
2211      <organization abbrev="greenbytes">greenbytes GmbH</organization>
2212      <address><email>julian.reschke@greenbytes.de</email></address>
2213    </author>
2214    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
2215  </front>
2216  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
2217  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
2218</reference>
2219
2220<reference anchor="Part3">
2221  <front>
2222    <title abbrev="HTTP/1.1">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
2223    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
2224      <organization abbrev="Day Software">Day Software</organization>
2225      <address><email>fielding@gbiv.com</email></address>
2226    </author>
2227    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2228      <organization>One Laptop per Child</organization>
2229      <address><email>jg@laptop.org</email></address>
2230    </author>
2231    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2232      <organization abbrev="HP">Hewlett-Packard Company</organization>
2233      <address><email>JeffMogul@acm.org</email></address>
2234    </author>
2235    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
2236      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2237      <address><email>henrikn@microsoft.com</email></address>
2238    </author>
2239    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2240      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
2241      <address><email>LMM@acm.org</email></address>
2242    </author>
2243    <author initials="P." surname="Leach" fullname="Paul J. Leach">
2244      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2245      <address><email>paulle@microsoft.com</email></address>
2246    </author>
2247    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2248      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
2249      <address><email>timbl@w3.org</email></address>
2250    </author>
2251    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
2252      <organization abbrev="W3C">World Wide Web Consortium</organization>
2253      <address><email>ylafon@w3.org</email></address>
2254    </author>
2255    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
2256      <organization abbrev="greenbytes">greenbytes GmbH</organization>
2257      <address><email>julian.reschke@greenbytes.de</email></address>
2258    </author>
2259    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
2260  </front>
2261  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p3-payload-&ID-VERSION;"/>
2262  <x:source href="p3-payload.xml" basename="p3-payload"/>
2263</reference>
2264
2265<reference anchor="Part4">
2266  <front>
2267    <title abbrev="HTTP/1.1">HTTP/1.1, part 4: Conditional Requests</title>
2268    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
2269      <organization abbrev="Day Software">Day Software</organization>
2270      <address><email>fielding@gbiv.com</email></address>
2271    </author>
2272    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2273      <organization>One Laptop per Child</organization>
2274      <address><email>jg@laptop.org</email></address>
2275    </author>
2276    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2277      <organization abbrev="HP">Hewlett-Packard Company</organization>
2278      <address><email>JeffMogul@acm.org</email></address>
2279    </author>
2280    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
2281      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2282      <address><email>henrikn@microsoft.com</email></address>
2283    </author>
2284    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2285      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
2286      <address><email>LMM@acm.org</email></address>
2287    </author>
2288    <author initials="P." surname="Leach" fullname="Paul J. Leach">
2289      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2290      <address><email>paulle@microsoft.com</email></address>
2291    </author>
2292    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2293      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
2294      <address><email>timbl@w3.org</email></address>
2295    </author>
2296    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
2297      <organization abbrev="W3C">World Wide Web Consortium</organization>
2298      <address><email>ylafon@w3.org</email></address>
2299    </author>
2300    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
2301      <organization abbrev="greenbytes">greenbytes GmbH</organization>
2302      <address><email>julian.reschke@greenbytes.de</email></address>
2303    </author>
2304    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
2305  </front>
2306  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"/>
2307  <x:source href="p4-conditional.xml" basename="p4-conditional"/>
2308</reference>
2309
2310<reference anchor="Part5">
2311  <front>
2312    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
2313    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
2314      <organization abbrev="Day Software">Day Software</organization>
2315      <address><email>fielding@gbiv.com</email></address>
2316    </author>
2317    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2318      <organization>One Laptop per Child</organization>
2319      <address><email>jg@laptop.org</email></address>
2320    </author>
2321    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2322      <organization abbrev="HP">Hewlett-Packard Company</organization>
2323      <address><email>JeffMogul@acm.org</email></address>
2324    </author>
2325    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
2326      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2327      <address><email>henrikn@microsoft.com</email></address>
2328    </author>
2329    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2330      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
2331      <address><email>LMM@acm.org</email></address>
2332    </author>
2333    <author initials="P." surname="Leach" fullname="Paul J. Leach">
2334      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2335      <address><email>paulle@microsoft.com</email></address>
2336    </author>
2337    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2338      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
2339      <address><email>timbl@w3.org</email></address>
2340    </author>
2341    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
2342      <organization abbrev="W3C">World Wide Web Consortium</organization>
2343      <address><email>ylafon@w3.org</email></address>
2344    </author>
2345    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
2346      <organization abbrev="greenbytes">greenbytes GmbH</organization>
2347      <address><email>julian.reschke@greenbytes.de</email></address>
2348    </author>
2349    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
2350  </front>
2351  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
2352  <x:source href="p5-range.xml" basename="p5-range"/>
2353</reference>
2354
2355<reference anchor="Part6">
2356  <front>
2357    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
2358    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
2359      <organization abbrev="Day Software">Day Software</organization>
2360      <address><email>fielding@gbiv.com</email></address>
2361    </author>
2362    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2363      <organization>One Laptop per Child</organization>
2364      <address><email>jg@laptop.org</email></address>
2365    </author>
2366    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2367      <organization abbrev="HP">Hewlett-Packard Company</organization>
2368      <address><email>JeffMogul@acm.org</email></address>
2369    </author>
2370    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
2371      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2372      <address><email>henrikn@microsoft.com</email></address>
2373    </author>
2374    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2375      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
2376      <address><email>LMM@acm.org</email></address>
2377    </author>
2378    <author initials="P." surname="Leach" fullname="Paul J. Leach">
2379      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2380      <address><email>paulle@microsoft.com</email></address>
2381    </author>
2382    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2383      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
2384      <address><email>timbl@w3.org</email></address>
2385    </author>
2386    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
2387      <organization abbrev="W3C">World Wide Web Consortium</organization>
2388      <address><email>ylafon@w3.org</email></address>
2389    </author>
2390    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
2391      <organization abbrev="greenbytes">greenbytes GmbH</organization>
2392      <address><email>julian.reschke@greenbytes.de</email></address>
2393    </author>
2394    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
2395  </front>
2396  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
2397  <x:source href="p6-cache.xml" basename="p6-cache"/>
2398</reference>
2399
2400<reference anchor="Part7">
2401  <front>
2402    <title abbrev="HTTP/1.1">HTTP/1.1, part 7: Authentication</title>
2403    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
2404      <organization abbrev="Day Software">Day Software</organization>
2405      <address><email>fielding@gbiv.com</email></address>
2406    </author>
2407    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2408      <organization>One Laptop per Child</organization>
2409      <address><email>jg@laptop.org</email></address>
2410    </author>
2411    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2412      <organization abbrev="HP">Hewlett-Packard Company</organization>
2413      <address><email>JeffMogul@acm.org</email></address>
2414    </author>
2415    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
2416      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2417      <address><email>henrikn@microsoft.com</email></address>
2418    </author>
2419    <author initials="L." surname="Masinter" fullname="Larry Masinter">
2420      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
2421      <address><email>LMM@acm.org</email></address>
2422    </author>
2423    <author initials="P." surname="Leach" fullname="Paul J. Leach">
2424      <organization abbrev="Microsoft">Microsoft Corporation</organization>
2425      <address><email>paulle@microsoft.com</email></address>
2426    </author>
2427    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2428      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
2429      <address><email>timbl@w3.org</email></address>
2430    </author>
2431    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
2432      <organization abbrev="W3C">World Wide Web Consortium</organization>
2433      <address><email>ylafon@w3.org</email></address>
2434    </author>
2435    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
2436      <organization abbrev="greenbytes">greenbytes GmbH</organization>
2437      <address><email>julian.reschke@greenbytes.de</email></address>
2438    </author>
2439    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
2440  </front>
2441  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-&ID-VERSION;"/>
2442  <x:source href="p7-auth.xml" basename="p7-auth"/>
2443</reference>
2444
2445<reference anchor="RFC2119">
2446  <front>
2447    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
2448    <author initials="S." surname="Bradner" fullname="Scott Bradner">
2449      <organization>Harvard University</organization>
2450      <address><email>sob@harvard.edu</email></address>
2451    </author>
2452    <date month="March" year="1997"/>
2453  </front>
2454  <seriesInfo name="BCP" value="14"/>
2455  <seriesInfo name="RFC" value="2119"/>
2456</reference>
2457
2458</references>
2459
2460<references title="Informative References">
2461
2462<reference anchor="Luo1998">
2463  <front>
2464    <title>Tunneling TCP based protocols through Web proxy servers</title>
2465    <author initials="A." surname="Luotonen" fullname="A. Luotonen">
2466      <organization/>
2467    </author>
2468    <date year="1998" month="August"/>
2469  </front>
2470  <seriesInfo name="Internet-Draft" value="draft-luotonen-web-proxy-tunneling-01"/>
2471</reference>
2472
2473<reference anchor="RFC1945">
2474  <front>
2475    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
2476    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2477      <organization>MIT, Laboratory for Computer Science</organization>
2478      <address><email>timbl@w3.org</email></address>
2479    </author>
2480    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
2481      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
2482      <address><email>fielding@ics.uci.edu</email></address>
2483    </author>
2484    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
2485      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
2486      <address><email>frystyk@w3.org</email></address>
2487    </author>
2488    <date month="May" year="1996"/>
2489  </front>
2490  <seriesInfo name="RFC" value="1945"/>
2491</reference>
2492
2493<reference anchor="RFC2068">
2494  <front>
2495    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
2496    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
2497      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
2498      <address><email>fielding@ics.uci.edu</email></address>
2499    </author>
2500    <author initials="J." surname="Gettys" fullname="Jim Gettys">
2501      <organization>MIT Laboratory for Computer Science</organization>
2502      <address><email>jg@w3.org</email></address>
2503    </author>
2504    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
2505      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
2506      <address><email>mogul@wrl.dec.com</email></address>
2507    </author>
2508    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
2509      <organization>MIT Laboratory for Computer Science</organization>
2510      <address><email>frystyk@w3.org</email></address>
2511    </author>
2512    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
2513      <organization>MIT Laboratory for Computer Science</organization>
2514      <address><email>timbl@w3.org</email></address>
2515    </author>
2516    <date month="January" year="1997"/>
2517  </front>
2518  <seriesInfo name="RFC" value="2068"/>
2519</reference>
2520
2521<reference anchor="RFC2616">
2522  <front>
2523    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
2524    <author initials="R." surname="Fielding" fullname="R. Fielding">
2525      <organization>University of California, Irvine</organization>
2526      <address><email>fielding@ics.uci.edu</email></address>
2527    </author>
2528    <author initials="J." surname="Gettys" fullname="J. Gettys">
2529      <organization>W3C</organization>
2530      <address><email>jg@w3.org</email></address>
2531    </author>
2532    <author initials="J." surname="Mogul" fullname="J. Mogul">
2533      <organization>Compaq Computer Corporation</organization>
2534      <address><email>mogul@wrl.dec.com</email></address>
2535    </author>
2536    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
2537      <organization>MIT Laboratory for Computer Science</organization>
2538      <address><email>frystyk@w3.org</email></address>
2539    </author>
2540    <author initials="L." surname="Masinter" fullname="L. Masinter">
2541      <organization>Xerox Corporation</organization>
2542      <address><email>masinter@parc.xerox.com</email></address>
2543    </author>
2544    <author initials="P." surname="Leach" fullname="P. Leach">
2545      <organization>Microsoft Corporation</organization>
2546      <address><email>paulle@microsoft.com</email></address>
2547    </author>
2548    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
2549      <organization>W3C</organization>
2550      <address><email>timbl@w3.org</email></address>
2551    </author>
2552    <date month="June" year="1999"/>
2553  </front>
2554  <seriesInfo name="RFC" value="2616"/>
2555</reference>
2556
2557<reference anchor="RFC2822">
2558  <front>
2559    <title>Internet Message Format</title>
2560    <author initials="P." surname="Resnick" fullname="P. Resnick">
2561      <organization>QUALCOMM Incorporated</organization>
2562    </author>
2563    <date year="2001" month="April"/>
2564  </front> 
2565  <seriesInfo name="RFC" value="2822"/>
2566</reference>
2567
2568</references>
2569
2570<section title="Compatibility with Previous Versions" anchor="compatibility">
2571<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
2572<t>
2573   Clarified which error code should be used for inbound server failures
2574   (e.g. DNS failures). (<xref target="status.504"/>).
2575</t>
2576<t>
2577   201 (Created) had a race that required an Etag be sent when a resource is
2578   first created. (<xref target="status.201"/>).
2579</t>
2580<t>
2581   Rewrite of message transmission requirements to make it much harder
2582   for implementors to get it wrong, as the consequences of errors here
2583   can have significant impact on the Internet, and to deal with the
2584   following problems:
2585  <list style="numbers">
2586      <t>Changing "HTTP/1.1 or later" to "HTTP/1.1", in contexts where
2587         this was incorrectly placing a requirement on the behavior of
2588         an implementation of a future version of HTTP/1.x</t>
2589
2590      <t>Made it clear that user-agents should retry requests, not
2591         "clients" in general.</t>
2592
2593      <t>Converted requirements for clients to ignore unexpected 100
2594         (Continue) responses, and for proxies to forward 100 responses,
2595         into a general requirement for 1xx responses.</t>
2596
2597      <t>Modified some TCP-specific language, to make it clearer that
2598         non-TCP transports are possible for HTTP.</t>
2599
2600      <t>Require that the origin server &MUST-NOT; wait for the request
2601         body before it sends a required 100 (Continue) response.</t>
2602
2603      <t>Allow, rather than require, a server to omit 100 (Continue) if
2604         it has already seen some of the request body.</t>
2605
2606      <t>Allow servers to defend against denial-of-service attacks and
2607         broken clients.</t>
2608  </list>
2609</t>
2610<t>
2611   This change adds the Expect header and 417 status code.
2612</t>
2613<t>
2614   Clean up confusion between 403 and 404 responses. (Section <xref target="status.403" format="counter"/>,
2615   <xref target="status.404" format="counter"/>, and <xref target="status.410" format="counter"/>)
2616</t>
2617<t>
2618   The PATCH<iref item="PATCH method" primary="true"/><iref item="Methods" subitem="PATCH" primary="true"/>, LINK<iref item="LINK method" primary="true"/><iref item="Methods" subitem="LINK" primary="true"/>, UNLINK<iref item="UNLINK method" primary="true"/><iref item="Methods" subitem="UNLINK" primary="true"/> methods were defined but not commonly
2619   implemented in previous versions of this specification. See <xref target="RFC2068"/>.
2620</t>
2621</section>
2622
2623<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
2624<t>
2625  Clarify definition of POST.
2626  (<xref target="POST"/>)
2627</t>
2628<t>
2629  Failed to consider that there are
2630  many other request methods that are safe to automatically redirect,
2631  and further that the user agent is able to make that determination
2632  based on the request method semantics.
2633  (Sections <xref format="counter" target="status.301"/>,
2634  <xref format="counter" target="status.302"/> and
2635  <xref format="counter" target="status.307"/>)
2636</t>
2637<t>
2638  Deprecate 305 Use Proxy status code, because user agents did not implement it.
2639  It used to indicate that the requested resource must be accessed through the
2640  proxy given by the Location field. The Location field gave the URI of the
2641  proxy. The recipient was expected to repeat this single request via the proxy.
2642  (<xref target="status.305"/>)
2643</t>
2644<t>
2645  Reclassify Allow header as response header, removing the option to
2646  specify it in a PUT request.
2647  Relax the server requirement on the contents of the Allow header and
2648  remove requirement on clients to always trust the header value.
2649  (<xref target="header.allow"/>)
2650</t>
2651<t>
2652  Correct syntax of Location header to allow fragment,
2653  as referred symbol wasn't what was expected, and add some
2654  clarifications as to when it would not be appropriate.
2655  (<xref target="header.location"/>)
2656</t>
2657<t>
2658  In the description of the Server header, the Via field
2659  was described as a SHOULD. The requirement was and is stated
2660  correctly in the description of the Via header in &header-via;.
2661  (<xref target="header.server"/>)
2662</t>
2663</section>
2664
2665</section>
2666
2667<section title="Change Log (to be removed by RFC Editor before publication)">
2668
2669<section title="Since RFC2616">
2670<t>
2671  Extracted relevant partitions from <xref target="RFC2616"/>.
2672</t>
2673</section>
2674
2675<section title="Since draft-ietf-httpbis-p2-semantics-00">
2676<t>
2677  Closed issues:
2678  <list style="symbols"> 
2679    <t>
2680      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/5"/>:
2681      "Via is a MUST"
2682      (<eref target="http://purl.org/NET/http-errata#via-must"/>)
2683    </t>
2684    <t>
2685      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/6"/>:
2686      "Fragments allowed in Location"
2687      (<eref target="http://purl.org/NET/http-errata#location-fragments"/>)
2688    </t>
2689    <t>
2690      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/10"/>:
2691      "Safe Methods vs Redirection"
2692      (<eref target="http://purl.org/NET/http-errata#saferedirect"/>)
2693    </t>
2694    <t>
2695      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/17"/>:
2696      "Revise description of the POST method"
2697      (<eref target="http://purl.org/NET/http-errata#post"/>)
2698    </t>
2699    <t>
2700      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
2701      "Normative and Informative references"
2702    </t>
2703    <t>
2704      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42"/>:
2705      "RFC2606 Compliance"
2706    </t>
2707    <t>
2708      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65"/>:
2709      "Informative references"
2710    </t>
2711    <t>
2712      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/84"/>:
2713      "Redundant cross-references"
2714    </t>
2715  </list>
2716</t>
2717<t>
2718  Other changes:
2719  <list style="symbols"> 
2720    <t>
2721      Move definitions of 304 and 412 condition codes to <xref target="Part4"/>
2722    </t>
2723  </list>
2724</t>
2725</section>
2726
2727<section title="Since draft-ietf-httpbis-p2-semantics-01">
2728<t>
2729  Closed issues:
2730  <list style="symbols"> 
2731    <t>
2732      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/21"/>:
2733      "PUT side effects"
2734    </t>
2735    <t>
2736      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/91"/>:
2737      "Duplicate Host header requirements"
2738    </t>
2739  </list>
2740</t>
2741<t>
2742  Ongoing work on ABNF conversion (<eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
2743  <list style="symbols"> 
2744    <t>
2745      Move "Product Tokens" section (back) into Part 1, as "token" is used
2746      in the definition of the Upgrade header.
2747    </t>
2748    <t>
2749      Add explicit references to BNF syntax and rules imported from other parts of the specification.
2750    </t>
2751    <t>
2752      Copy definition of delta-seconds from Part6 instead of referencing it.
2753    </t>
2754  </list>
2755</t>
2756</section>
2757
2758<section title="Since draft-ietf-httpbis-p2-semantics-02">
2759<t>
2760  Closed issues:
2761  <list style="symbols"> 
2762    <t>
2763      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/24"/>:
2764      "Requiring Allow in 405 responses"
2765    </t>
2766    <t>
2767      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61"/>:
2768      "Redirection vs. Location"
2769    </t>
2770    <t>
2771      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/76"/>:
2772      "305 Use Proxy"
2773    </t>
2774    <t>
2775      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105"/>:
2776      "Classification for Allow header"
2777    </t>
2778    <t>
2779      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/112"/>:
2780      "PUT - 'store under' vs 'store at'"
2781    </t>
2782  </list>
2783</t>
2784</section>
2785
2786</section>
2787
2788</back>
2789</rfc>
Note: See TracBrowser for help on using the repository browser.