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

Last change on this file since 1043 was 1043, checked in by mnot@…, 9 years ago

Remove RFC2119 from status code considerations; for #229.

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