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

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

s/resource/represenation of.../ (editorial)

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