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

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

Rewrite header ABNFs to spell out whitespace rules, factor out value format definitions. (related to #36)

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