source: draft-ietf-httpbis/latest/p1-messaging.xml @ 2543

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

xref format (editorial)

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 236.3 KB
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
14  <!ENTITY ID-VERSION "latest">
15  <!ENTITY ID-MONTH "January">
16  <!ENTITY ID-YEAR "2014">
17  <!ENTITY mdash "&#8212;">
18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
19  <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#response.cacheability' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY payload                "<xref target='Part2' x:rel='#payload' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY media-type            "<xref target='Part2' x:rel='#media.type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY content-codings        "<xref target='Part2' x:rel='#content.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
24  <!ENTITY CONNECT                "<xref target='Part2' x:rel='#CONNECT' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
25  <!ENTITY content.negotiation    "<xref target='Part2' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26  <!ENTITY diff-mime              "<xref target='Part2' x:rel='#differences.between.http.and.mime' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
27  <!ENTITY representation         "<xref target='Part2' x:rel='#representations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
28  <!ENTITY HEAD                   "<xref target='Part2' x:rel='#HEAD' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
29  <!ENTITY header-allow           "<xref target='Part2' x:rel='#header.allow' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
30  <!ENTITY header-cache-control   "<xref target='Part6' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
31  <!ENTITY header-content-encoding    "<xref target='Part2' x:rel='#header.content-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
32  <!ENTITY header-content-location    "<xref target='Part2' x:rel='#header.content-location' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
33  <!ENTITY header-content-range   "<xref target='Part5' x:rel='#header.content-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
34  <!ENTITY header-content-type    "<xref target='Part2' x:rel='#header.content-type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
35  <!ENTITY header-date            "<xref target='Part2' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
36  <!ENTITY header-etag            "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
37  <!ENTITY header-expect          "<xref target='Part2' x:rel='#header.expect' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
38  <!ENTITY header-expires         "<xref target='Part6' x:rel='#header.expires' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
39  <!ENTITY header-last-modified   "<xref target='Part4' x:rel='#header.last-modified' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
40  <!ENTITY header-mime-version    "<xref target='Part2' x:rel='#mime-version' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
41  <!ENTITY header-pragma          "<xref target='Part6' x:rel='#header.pragma' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
42  <!ENTITY header-proxy-authenticate  "<xref target='Part7' x:rel='#header.proxy-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
43  <!ENTITY header-proxy-authorization "<xref target='Part7' x:rel='#header.proxy-authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
44  <!ENTITY header-server          "<xref target='Part2' x:rel='#header.server' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
45  <!ENTITY header-warning         "<xref target='Part6' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
46  <!ENTITY idempotent-methods     "<xref target='Part2' x:rel='#idempotent.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
47  <!ENTITY safe-methods           "<xref target='Part2' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
48  <!ENTITY methods                "<xref target='Part2' x:rel='#methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
49  <!ENTITY OPTIONS                "<xref target='Part2' x:rel='#OPTIONS' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
50  <!ENTITY qvalue                 "<xref target='Part2' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
51  <!ENTITY resource               "<xref target='Part2' x:rel='#resources' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
52  <!ENTITY status-codes           "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
53  <!ENTITY status-1xx             "<xref target='Part2' x:rel='#status.1xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
54  <!ENTITY status-203             "<xref target='Part2' x:rel='#status.203' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
55  <!ENTITY status-3xx             "<xref target='Part2' x:rel='#status.3xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
56  <!ENTITY status-304             "<xref target='Part4' x:rel='#status.304' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
57  <!ENTITY status-4xx             "<xref target='Part2' x:rel='#status.4xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
58  <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
59  <!ENTITY iana-header-registry   "<xref target='Part2' x:rel='#header.field.registry' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
60]>
61<?rfc toc="yes" ?>
62<?rfc symrefs="yes" ?>
63<?rfc sortrefs="yes" ?>
64<?rfc compact="yes"?>
65<?rfc subcompact="no" ?>
66<?rfc linkmailto="no" ?>
67<?rfc editing="no" ?>
68<?rfc comments="yes"?>
69<?rfc inline="yes"?>
70<?rfc rfcedstyle="yes"?>
71<?rfc-ext allow-markup-in-artwork="yes" ?>
72<?rfc-ext include-references-in-index="yes" ?>
73<rfc obsoletes="2145,2616" updates="2817,2818" category="std" x:maturity-level="proposed"
74     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"
75     xmlns:x='http://purl.org/net/xml2rfc/ext'>
76<x:link rel="next" basename="p2-semantics"/>
77<x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/>
78<front>
79
80  <title abbrev="HTTP/1.1 Message Syntax and Routing">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
81
82  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
83    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
84    <address>
85      <postal>
86        <street>345 Park Ave</street>
87        <city>San Jose</city>
88        <region>CA</region>
89        <code>95110</code>
90        <country>USA</country>
91      </postal>
92      <email>fielding@gbiv.com</email>
93      <uri>http://roy.gbiv.com/</uri>
94    </address>
95  </author>
96
97  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
98    <organization abbrev="greenbytes">greenbytes GmbH</organization>
99    <address>
100      <postal>
101        <street>Hafenweg 16</street>
102        <city>Muenster</city><region>NW</region><code>48155</code>
103        <country>Germany</country>
104      </postal>
105      <email>julian.reschke@greenbytes.de</email>
106      <uri>http://greenbytes.de/tech/webdav/</uri>
107    </address>
108  </author>
109
110  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
111  <workgroup>HTTPbis Working Group</workgroup>
112
113<abstract>
114<t>
115   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
116   distributed, collaborative, hypertext information systems. HTTP has been in
117   use by the World Wide Web global information initiative since 1990.
118   This document provides an overview of HTTP architecture and its associated
119   terminology, defines the "http" and "https" Uniform Resource Identifier
120   (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements,
121   and describes general security concerns for implementations.
122</t>   
123</abstract>
124
125<note title="Editorial Note (To be removed by RFC Editor)">
126  <t>
127    Discussion of this draft takes place on the HTTPBIS working group
128    mailing list (ietf-http-wg@w3.org), which is archived at
129    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
130  </t>
131  <t>
132    The current issues list is at
133    <eref target="http://tools.ietf.org/wg/httpbis/trac/report/3"/> and related
134    documents (including fancy diffs) can be found at
135    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
136  </t>
137  <t>
138    The changes in this draft are summarized in <xref target="changes.since.25"/>.
139  </t>
140</note>
141</front>
142<middle>
143<section title="Introduction" anchor="introduction">
144<t>
145   The Hypertext Transfer Protocol (HTTP) is an application-level
146   request/response protocol that uses extensible semantics and self-descriptive
147   message payloads for flexible interaction with network-based hypertext
148   information systems. This document is the first in a series of documents
149   that collectively form the HTTP/1.1 specification:
150   <list style="empty">
151    <t>RFC xxx1: Message Syntax and Routing</t>
152    <t><xref target="Part2" x:fmt="none">RFC xxx2</xref>: Semantics and Content</t>
153    <t><xref target="Part4" x:fmt="none">RFC xxx3</xref>: Conditional Requests</t>
154    <t><xref target="Part5" x:fmt="none">RFC xxx4</xref>: Range Requests</t>
155    <t><xref target="Part6" x:fmt="none">RFC xxx5</xref>: Caching</t>
156    <t><xref target="Part7" x:fmt="none">RFC xxx6</xref>: Authentication</t>
157   </list>
158</t>
159<t>
160   This HTTP/1.1 specification obsoletes
161   <xref target="RFC2616" x:fmt="none">RFC 2616</xref> and
162   <xref target="RFC2145" x:fmt="none">RFC 2145</xref> (on HTTP versioning).
163   This specification also updates the use of CONNECT to establish a tunnel,
164   previously defined in <xref target="RFC2817" x:fmt="none">RFC 2817</xref>,
165   and defines the "https" URI scheme that was described informally in
166   <xref target="RFC2818" x:fmt="none">RFC 2818</xref>.
167</t>
168<t>
169   HTTP is a generic interface protocol for information systems. It is
170   designed to hide the details of how a service is implemented by presenting
171   a uniform interface to clients that is independent of the types of
172   resources provided. Likewise, servers do not need to be aware of each
173   client's purpose: an HTTP request can be considered in isolation rather
174   than being associated with a specific type of client or a predetermined
175   sequence of application steps. The result is a protocol that can be used
176   effectively in many different contexts and for which implementations can
177   evolve independently over time.
178</t>
179<t>
180   HTTP is also designed for use as an intermediation protocol for translating
181   communication to and from non-HTTP information systems.
182   HTTP proxies and gateways can provide access to alternative information
183   services by translating their diverse protocols into a hypertext
184   format that can be viewed and manipulated by clients in the same way
185   as HTTP services.
186</t>
187<t>
188   One consequence of this flexibility is that the protocol cannot be
189   defined in terms of what occurs behind the interface. Instead, we
190   are limited to defining the syntax of communication, the intent
191   of received communication, and the expected behavior of recipients.
192   If the communication is considered in isolation, then successful
193   actions ought to be reflected in corresponding changes to the
194   observable interface provided by servers. However, since multiple
195   clients might act in parallel and perhaps at cross-purposes, we
196   cannot require that such changes be observable beyond the scope
197   of a single response.
198</t>
199<t>
200   This document describes the architectural elements that are used or
201   referred to in HTTP, defines the "http" and "https" URI schemes,
202   describes overall network operation and connection management,
203   and defines HTTP message framing and forwarding requirements.
204   Our goal is to define all of the mechanisms necessary for HTTP message
205   handling that are independent of message semantics, thereby defining the
206   complete set of requirements for message parsers and
207   message-forwarding intermediaries.
208</t>
209
210
211<section title="Requirement Notation" anchor="intro.requirements">
212<t>
213   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
214   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
215   document are to be interpreted as described in <xref target="RFC2119"/>.
216</t>
217<t>
218   Conformance criteria and considerations regarding error handling
219   are defined in <xref target="conformance"/>.
220</t>
221</section>
222
223<section title="Syntax Notation" anchor="notation">
224<iref primary="true" item="Grammar" subitem="ALPHA"/>
225<iref primary="true" item="Grammar" subitem="CR"/>
226<iref primary="true" item="Grammar" subitem="CRLF"/>
227<iref primary="true" item="Grammar" subitem="CTL"/>
228<iref primary="true" item="Grammar" subitem="DIGIT"/>
229<iref primary="true" item="Grammar" subitem="DQUOTE"/>
230<iref primary="true" item="Grammar" subitem="HEXDIG"/>
231<iref primary="true" item="Grammar" subitem="HTAB"/>
232<iref primary="true" item="Grammar" subitem="LF"/>
233<iref primary="true" item="Grammar" subitem="OCTET"/>
234<iref primary="true" item="Grammar" subitem="SP"/>
235<iref primary="true" item="Grammar" subitem="VCHAR"/>
236<t>
237   This specification uses the Augmented Backus-Naur Form (ABNF) notation of
238   <xref target="RFC5234"/> with a list extension, defined in
239   <xref target="abnf.extension"/>, that allows for compact definition of
240   comma-separated lists using a '#' operator (similar to how the '*' operator
241   indicates repetition).
242   <xref target="collected.abnf"/> shows the collected grammar with all list
243   operators expanded to standard ABNF notation.
244</t>
245<t anchor="core.rules">
246  <x:anchor-alias value="ALPHA"/>
247  <x:anchor-alias value="CTL"/>
248  <x:anchor-alias value="CR"/>
249  <x:anchor-alias value="CRLF"/>
250  <x:anchor-alias value="DIGIT"/>
251  <x:anchor-alias value="DQUOTE"/>
252  <x:anchor-alias value="HEXDIG"/>
253  <x:anchor-alias value="HTAB"/>
254  <x:anchor-alias value="LF"/>
255  <x:anchor-alias value="OCTET"/>
256  <x:anchor-alias value="SP"/>
257  <x:anchor-alias value="VCHAR"/>
258   The following core rules are included by
259   reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
260   ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
261   DIGIT (decimal 0-9), DQUOTE (double quote),
262   HEXDIG (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed),
263   OCTET (any 8-bit sequence of data), SP (space), and
264   VCHAR (any visible <xref target="USASCII"/> character).
265</t>
266<t>
267   As a convention, ABNF rule names prefixed with "obs-" denote
268   "obsolete" grammar rules that appear for historical reasons.
269</t>
270</section>
271</section>
272
273<section title="Architecture" anchor="architecture">
274<t>
275   HTTP was created for the World Wide Web architecture
276   and has evolved over time to support the scalability needs of a worldwide
277   hypertext system. Much of that architecture is reflected in the terminology
278   and syntax productions used to define HTTP.
279</t>
280
281<section title="Client/Server Messaging" anchor="operation">
282<iref primary="true" item="client"/>
283<iref primary="true" item="server"/>
284<iref primary="true" item="connection"/>
285<t>
286   HTTP is a stateless request/response protocol that operates by exchanging
287   <x:dfn>messages</x:dfn> (<xref target="http.message"/>) across a reliable
288   transport or session-layer
289   "<x:dfn>connection</x:dfn>" (<xref target="connection.management"/>).
290   An HTTP "<x:dfn>client</x:dfn>" is a program that establishes a connection
291   to a server for the purpose of sending one or more HTTP requests.
292   An HTTP "<x:dfn>server</x:dfn>" is a program that accepts connections
293   in order to service HTTP requests by sending HTTP responses.
294</t>
295<iref primary="true" item="user agent"/>
296<iref primary="true" item="origin server"/>
297<iref primary="true" item="browser"/>
298<iref primary="true" item="spider"/>
299<iref primary="true" item="sender"/>
300<iref primary="true" item="recipient"/>
301<t>
302   The terms client and server refer only to the roles that
303   these programs perform for a particular connection.  The same program
304   might act as a client on some connections and a server on others.
305   We use the term "<x:dfn>user agent</x:dfn>" to refer to any of the various
306   client programs that initiate a request, including (but not limited to)
307   browsers, spiders (web-based robots), command-line tools, native
308   applications, and mobile apps.  The term "<x:dfn>origin server</x:dfn>" is
309   used to refer to the program that can originate authoritative responses to
310   a request. For general requirements, we use the terms
311   "<x:dfn>sender</x:dfn>" and "<x:dfn>recipient</x:dfn>" to refer to any
312   component that sends or receives, respectively, a given message.
313</t>
314<t>
315   HTTP relies upon the Uniform Resource Identifier (URI)
316   standard <xref target="RFC3986"/> to indicate the target resource
317   (<xref target="target-resource"/>) and relationships between resources.
318   Messages are passed in a format similar to that used by Internet mail
319   <xref target="RFC5322"/> and the Multipurpose Internet Mail Extensions
320   (MIME) <xref target="RFC2045"/> (see &diff-mime; for the differences
321   between HTTP and MIME messages).
322</t>
323<t>
324   Most HTTP communication consists of a retrieval request (GET) for
325   a representation of some resource identified by a URI.  In the
326   simplest case, this might be accomplished via a single bidirectional
327   connection (===) between the user agent (UA) and the origin server (O).
328</t>
329<figure><artwork type="drawing">
330         request   &gt;
331    <x:highlight>UA</x:highlight> ======================================= <x:highlight>O</x:highlight>
332                                &lt;   response
333</artwork></figure>
334<iref primary="true" item="message"/>
335<iref primary="true" item="request"/>
336<iref primary="true" item="response"/>
337<t>
338   A client sends an HTTP request to a server in the form of a <x:dfn>request</x:dfn>
339   message, beginning with a request-line that includes a method, URI, and
340   protocol version (<xref target="request.line"/>),
341   followed by header fields containing
342   request modifiers, client information, and representation metadata
343   (<xref target="header.fields"/>),
344   an empty line to indicate the end of the header section, and finally
345   a message body containing the payload body (if any,
346   <xref target="message.body"/>).
347</t>
348<t>
349   A server responds to a client's request by sending one or more HTTP
350   <x:dfn>response</x:dfn>
351   messages, each beginning with a status line that
352   includes the protocol version, a success or error code, and textual
353   reason phrase (<xref target="status.line"/>),
354   possibly followed by header fields containing server
355   information, resource metadata, and representation metadata
356   (<xref target="header.fields"/>),
357   an empty line to indicate the end of the header section, and finally
358   a message body containing the payload body (if any,
359   <xref target="message.body"/>).
360</t>
361<t>
362   A connection might be used for multiple request/response exchanges,
363   as defined in <xref target="persistent.connections"/>.
364</t>
365<t>
366   The following example illustrates a typical message exchange for a
367   GET request on the URI "http://www.example.com/hello.txt":
368</t>
369<figure><preamble>
370Client request:
371</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
372GET /hello.txt HTTP/1.1
373User-Agent: curl/7.16.3 libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3
374Host: www.example.com
375Accept-Language: en, mi
376
377</artwork></figure>
378<figure><preamble>
379Server response:
380</preamble><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
381HTTP/1.1 200 OK
382Date: Mon, 27 Jul 2009 12:28:53 GMT
383Server: Apache
384Last-Modified: Wed, 22 Jul 2009 19:15:56 GMT
385ETag: "34aa387-d-1568eb00"
386Accept-Ranges: bytes
387Content-Length: <x:length-of target="exbody"/>
388Vary: Accept-Encoding
389Content-Type: text/plain
390
391<x:span anchor="exbody">Hello World! My payload includes a trailing CRLF.
392</x:span></artwork>
393</figure>
394</section>
395
396<section title="Implementation Diversity" anchor="implementation-diversity">
397<t>
398   When considering the design of HTTP, it is easy to fall into a trap of
399   thinking that all user agents are general-purpose browsers and all origin
400   servers are large public websites. That is not the case in practice.
401   Common HTTP user agents include household appliances, stereos, scales,
402   firmware update scripts, command-line programs, mobile apps,
403   and communication devices in a multitude of shapes and sizes.  Likewise,
404   common HTTP origin servers include home automation units, configurable
405   networking components, office machines, autonomous robots, news feeds,
406   traffic cameras, ad selectors, and video delivery platforms.
407</t>
408<t>
409   The term "user agent" does not imply that there is a human user directly
410   interacting with the software agent at the time of a request. In many
411   cases, a user agent is installed or configured to run in the background
412   and save its results for later inspection (or save only a subset of those
413   results that might be interesting or erroneous). Spiders, for example, are
414   typically given a start URI and configured to follow certain behavior while
415   crawling the Web as a hypertext graph.
416</t>
417<t>
418   The implementation diversity of HTTP means that we cannot assume the
419   user agent can make interactive suggestions to a user or provide adequate
420   warning for security or privacy options.  In the few cases where this
421   specification requires reporting of errors to the user, it is acceptable
422   for such reporting to only be observable in an error console or log file.
423   Likewise, requirements that an automated action be confirmed by the user
424   before proceeding might be met via advance configuration choices,
425   run-time options, or simple avoidance of the unsafe action; confirmation
426   does not imply any specific user interface or interruption of normal
427   processing if the user has already made that choice.
428</t>
429</section>
430
431<section title="Intermediaries" anchor="intermediaries">
432<iref primary="true" item="intermediary"/>
433<t>
434   HTTP enables the use of intermediaries to satisfy requests through
435   a chain of connections.  There are three common forms of HTTP
436   <x:dfn>intermediary</x:dfn>: proxy, gateway, and tunnel.  In some cases,
437   a single intermediary might act as an origin server, proxy, gateway,
438   or tunnel, switching behavior based on the nature of each request.
439</t>
440<figure><artwork type="drawing">
441         &gt;             &gt;             &gt;             &gt;
442    <x:highlight>UA</x:highlight> =========== <x:highlight>A</x:highlight> =========== <x:highlight>B</x:highlight> =========== <x:highlight>C</x:highlight> =========== <x:highlight>O</x:highlight>
443               &lt;             &lt;             &lt;             &lt;
444</artwork></figure>
445<t>
446   The figure above shows three intermediaries (A, B, and C) between the
447   user agent and origin server. A request or response message that
448   travels the whole chain will pass through four separate connections.
449   Some HTTP communication options
450   might apply only to the connection with the nearest, non-tunnel
451   neighbor, only to the end-points of the chain, or to all connections
452   along the chain. Although the diagram is linear, each participant might
453   be engaged in multiple, simultaneous communications. For example, B
454   might be receiving requests from many clients other than A, and/or
455   forwarding requests to servers other than C, at the same time that it
456   is handling A's request. Likewise, later requests might be sent through a
457   different path of connections, often based on dynamic configuration for
458   load balancing.   
459</t>
460<t>
461<iref primary="true" item="upstream"/><iref primary="true" item="downstream"/>
462<iref primary="true" item="inbound"/><iref primary="true" item="outbound"/>
463   We use the terms "<x:dfn>upstream</x:dfn>" and "<x:dfn>downstream</x:dfn>"
464   to describe various requirements in relation to the directional flow of a
465   message: all messages flow from upstream to downstream.
466   Likewise, we use the terms inbound and outbound to refer to
467   directions in relation to the request path:
468   "<x:dfn>inbound</x:dfn>" means toward the origin server and
469   "<x:dfn>outbound</x:dfn>" means toward the user agent.
470</t>
471<t><iref primary="true" item="proxy"/>
472   A "<x:dfn>proxy</x:dfn>" is a message forwarding agent that is selected by the
473   client, usually via local configuration rules, to receive requests
474   for some type(s) of absolute URI and attempt to satisfy those
475   requests via translation through the HTTP interface.  Some translations
476   are minimal, such as for proxy requests for "http" URIs, whereas
477   other requests might require translation to and from entirely different
478   application-level protocols. Proxies are often used to group an
479   organization's HTTP requests through a common intermediary for the
480   sake of security, annotation services, or shared caching.
481</t>
482<t>
483<iref primary="true" item="transforming proxy"/>
484<iref primary="true" item="non-transforming proxy"/>
485   An HTTP-to-HTTP proxy is called a "<x:dfn>transforming proxy</x:dfn>" if it is designed
486   or configured to modify request or response messages in a semantically
487   meaningful way (i.e., modifications, beyond those required by normal
488   HTTP processing, that change the message in a way that would be
489   significant to the original sender or potentially significant to
490   downstream recipients).  For example, a transforming proxy might be
491   acting as a shared annotation server (modifying responses to include
492   references to a local annotation database), a malware filter, a
493   format transcoder, or an intranet-to-Internet privacy filter.  Such
494   transformations are presumed to be desired by the client (or client
495   organization) that selected the proxy and are beyond the scope of
496   this specification.  However, when a proxy is not intended to transform
497   a given message, we use the term "<x:dfn>non-transforming proxy</x:dfn>" to target
498   requirements that preserve HTTP message semantics. See &status-203; and
499   &header-warning; for status and warning codes related to transformations.
500</t>
501<t><iref primary="true" item="gateway"/><iref primary="true" item="reverse proxy"/>
502<iref primary="true" item="accelerator"/>
503   A "<x:dfn>gateway</x:dfn>" (a.k.a., "<x:dfn>reverse proxy</x:dfn>") is an
504   intermediary that acts as an origin server for the outbound connection, but
505   translates received requests and forwards them inbound to another server or
506   servers. Gateways are often used to encapsulate legacy or untrusted
507   information services, to improve server performance through
508   "<x:dfn>accelerator</x:dfn>" caching, and to enable partitioning or load
509   balancing of HTTP services across multiple machines.
510</t>
511<t>
512   All HTTP requirements applicable to an origin server
513   also apply to the outbound communication of a gateway.
514   A gateway communicates with inbound servers using any protocol that
515   it desires, including private extensions to HTTP that are outside
516   the scope of this specification.  However, an HTTP-to-HTTP gateway
517   that wishes to interoperate with third-party HTTP servers ought to conform
518   to user agent requirements on the gateway's inbound connection.
519</t>
520<t><iref primary="true" item="tunnel"/>
521   A "<x:dfn>tunnel</x:dfn>" acts as a blind relay between two connections
522   without changing the messages. Once active, a tunnel is not
523   considered a party to the HTTP communication, though the tunnel might
524   have been initiated by an HTTP request. A tunnel ceases to exist when
525   both ends of the relayed connection are closed. Tunnels are used to
526   extend a virtual connection through an intermediary, such as when
527   Transport Layer Security (TLS, <xref target="RFC5246"/>) is used to
528   establish confidential communication through a shared firewall proxy.
529</t>
530<t><iref primary="true" item="interception proxy"/>
531<iref primary="true" item="transparent proxy"/>
532<iref primary="true" item="captive portal"/>
533   The above categories for intermediary only consider those acting as
534   participants in the HTTP communication.  There are also intermediaries
535   that can act on lower layers of the network protocol stack, filtering or
536   redirecting HTTP traffic without the knowledge or permission of message
537   senders. Network intermediaries often introduce security flaws or
538   interoperability problems by violating HTTP semantics.  For example, an
539   "<x:dfn>interception proxy</x:dfn>" <xref target="RFC3040"/> (also commonly
540   known as a "<x:dfn>transparent proxy</x:dfn>" <xref target="RFC1919"/> or
541   "<x:dfn>captive portal</x:dfn>")
542   differs from an HTTP proxy because it is not selected by the client.
543   Instead, an interception proxy filters or redirects outgoing TCP port 80
544   packets (and occasionally other common port traffic).
545   Interception proxies are commonly found on public network access points,
546   as a means of enforcing account subscription prior to allowing use of
547   non-local Internet services, and within corporate firewalls to enforce
548   network usage policies.
549   They are indistinguishable from a man-in-the-middle attack.
550</t>
551<t>
552   HTTP is defined as a stateless protocol, meaning that each request message
553   can be understood in isolation.  Many implementations depend on HTTP's
554   stateless design in order to reuse proxied connections or dynamically
555   load-balance requests across multiple servers.  Hence, a server &MUST-NOT;
556   assume that two requests on the same connection are from the same user
557   agent unless the connection is secured and specific to that agent.
558   Some non-standard HTTP extensions (e.g., <xref target="RFC4559"/>) have
559   been known to violate this requirement, resulting in security and
560   interoperability problems.
561</t>
562</section>
563
564<section title="Caches" anchor="caches">
565<iref primary="true" item="cache"/>
566<t>
567   A "<x:dfn>cache</x:dfn>" is a local store of previous response messages and the
568   subsystem that controls its message storage, retrieval, and deletion.
569   A cache stores cacheable responses in order to reduce the response
570   time and network bandwidth consumption on future, equivalent
571   requests. Any client or server &MAY; employ a cache, though a cache
572   cannot be used by a server while it is acting as a tunnel.
573</t>
574<t>
575   The effect of a cache is that the request/response chain is shortened
576   if one of the participants along the chain has a cached response
577   applicable to that request. The following illustrates the resulting
578   chain if B has a cached copy of an earlier response from O (via C)
579   for a request that has not been cached by UA or A.
580</t>
581<figure><artwork type="drawing">
582            &gt;             &gt;
583       <x:highlight>UA</x:highlight> =========== <x:highlight>A</x:highlight> =========== <x:highlight>B</x:highlight> - - - - - - <x:highlight>C</x:highlight> - - - - - - <x:highlight>O</x:highlight>
584                  &lt;             &lt;
585</artwork></figure>
586<t><iref primary="true" item="cacheable"/>
587   A response is "<x:dfn>cacheable</x:dfn>" if a cache is allowed to store a copy of
588   the response message for use in answering subsequent requests.
589   Even when a response is cacheable, there might be additional
590   constraints placed by the client or by the origin server on when
591   that cached response can be used for a particular request. HTTP
592   requirements for cache behavior and cacheable responses are
593   defined in &caching-overview;. 
594</t>
595<t>
596   There are a wide variety of architectures and configurations
597   of caches deployed across the World Wide Web and
598   inside large organizations. These include national hierarchies
599   of proxy caches to save transoceanic bandwidth, collaborative systems that
600   broadcast or multicast cache entries, archives of pre-fetched cache
601   entries for use in off-line or high-latency environments, and so on.
602</t>
603</section>
604
605<section title="Conformance and Error Handling" anchor="conformance">
606<t>
607   This specification targets conformance criteria according to the role of
608   a participant in HTTP communication.  Hence, HTTP requirements are placed
609   on senders, recipients, clients, servers, user agents, intermediaries,
610   origin servers, proxies, gateways, or caches, depending on what behavior
611   is being constrained by the requirement. Additional (social) requirements
612   are placed on implementations, resource owners, and protocol element
613   registrations when they apply beyond the scope of a single communication.
614</t>
615<t>
616   The verb "generate" is used instead of "send" where a requirement
617   differentiates between creating a protocol element and merely forwarding a
618   received element downstream.
619</t>
620<t>
621   An implementation is considered conformant if it complies with all of the
622   requirements associated with the roles it partakes in HTTP.
623</t>
624<t>
625   Conformance includes both the syntax and semantics of protocol
626   elements. A sender &MUST-NOT; generate protocol elements that convey a
627   meaning that is known by that sender to be false. A sender &MUST-NOT;
628   generate protocol elements that do not match the grammar defined by the
629   corresponding ABNF rules. Within a given message, a sender &MUST-NOT;
630   generate protocol elements or syntax alternatives that are only allowed to
631   be generated by participants in other roles (i.e., a role that the sender
632   does not have for that message).
633</t>
634<t>
635   When a received protocol element is parsed, the recipient &MUST; be able to
636   parse any value of reasonable length that is applicable to the recipient's
637   role and matches the grammar defined by the corresponding ABNF rules.
638   Note, however, that some received protocol elements might not be parsed.
639   For example, an intermediary forwarding a message might parse a
640   header-field into generic field-name and field-value components, but then
641   forward the header field without further parsing inside the field-value.
642</t>
643<t>
644   HTTP does not have specific length limitations for many of its protocol
645   elements because the lengths that might be appropriate will vary widely,
646   depending on the deployment context and purpose of the implementation.
647   Hence, interoperability between senders and recipients depends on shared
648   expectations regarding what is a reasonable length for each protocol
649   element. Furthermore, what is commonly understood to be a reasonable length
650   for some protocol elements has changed over the course of the past two
651   decades of HTTP use, and is expected to continue changing in the future.
652</t>
653<t>
654   At a minimum, a recipient &MUST; be able to parse and process protocol
655   element lengths that are at least as long as the values that it generates
656   for those same protocol elements in other messages. For example, an origin
657   server that publishes very long URI references to its own resources needs
658   to be able to parse and process those same references when received as a
659   request target.
660</t>
661<t>
662   A recipient &MUST; interpret a received protocol element according to the
663   semantics defined for it by this specification, including extensions to
664   this specification, unless the recipient has determined (through experience
665   or configuration) that the sender incorrectly implements what is implied by
666   those semantics.
667   For example, an origin server might disregard the contents of a received
668   <x:ref>Accept-Encoding</x:ref> header field if inspection of the
669   <x:ref>User-Agent</x:ref> header field indicates a specific implementation
670   version that is known to fail on receipt of certain content codings.
671</t>
672<t>
673   Unless noted otherwise, a recipient &MAY; attempt to recover a usable
674   protocol element from an invalid construct.  HTTP does not define
675   specific error handling mechanisms except when they have a direct impact
676   on security, since different applications of the protocol require
677   different error handling strategies.  For example, a Web browser might
678   wish to transparently recover from a response where the
679   <x:ref>Location</x:ref> header field doesn't parse according to the ABNF,
680   whereas a systems control client might consider any form of error recovery
681   to be dangerous.
682</t>
683</section>
684
685<section title="Protocol Versioning" anchor="http.version">
686  <x:anchor-alias value="HTTP-version"/>
687  <x:anchor-alias value="HTTP-name"/>
688<t>
689   HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate
690   versions of the protocol. This specification defines version "1.1".
691   The protocol version as a whole indicates the sender's conformance
692   with the set of requirements laid out in that version's corresponding
693   specification of HTTP.
694</t>
695<t>
696   The version of an HTTP message is indicated by an HTTP-version field
697   in the first line of the message. HTTP-version is case-sensitive.
698</t>
699<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-version"/><iref primary="true" item="Grammar" subitem="HTTP-name"/>
700  <x:ref>HTTP-version</x:ref>  = <x:ref>HTTP-name</x:ref> "/" <x:ref>DIGIT</x:ref> "." <x:ref>DIGIT</x:ref>
701  <x:ref>HTTP-name</x:ref>     = <x:abnf-char-sequence>"HTTP"</x:abnf-char-sequence> ; "HTTP", case-sensitive
702</artwork></figure>
703<t>
704   The HTTP version number consists of two decimal digits separated by a "."
705   (period or decimal point).  The first digit ("major version") indicates the
706   HTTP messaging syntax, whereas the second digit ("minor version") indicates
707   the highest minor version within that major version to which the sender is
708   conformant and able to understand for future communication.  The minor
709   version advertises the sender's communication capabilities even when the
710   sender is only using a backwards-compatible subset of the protocol,
711   thereby letting the recipient know that more advanced features can
712   be used in response (by servers) or in future requests (by clients).
713</t>
714<t>
715   When an HTTP/1.1 message is sent to an HTTP/1.0 recipient
716   <xref target="RFC1945"/> or a recipient whose version is unknown,
717   the HTTP/1.1 message is constructed such that it can be interpreted
718   as a valid HTTP/1.0 message if all of the newer features are ignored.
719   This specification places recipient-version requirements on some
720   new features so that a conformant sender will only use compatible
721   features until it has determined, through configuration or the
722   receipt of a message, that the recipient supports HTTP/1.1.
723</t>
724<t>
725   The interpretation of a header field does not change between minor
726   versions of the same major HTTP version, though the default
727   behavior of a recipient in the absence of such a field can change.
728   Unless specified otherwise, header fields defined in HTTP/1.1 are
729   defined for all versions of HTTP/1.x.  In particular, the <x:ref>Host</x:ref>
730   and <x:ref>Connection</x:ref> header fields ought to be implemented by all
731   HTTP/1.x implementations whether or not they advertise conformance with
732   HTTP/1.1.
733</t>
734<t>
735   New header fields can be introduced without changing the protocol version
736   if their defined semantics allow them to be safely ignored by recipients
737   that do not recognize them. Header field extensibility is discussed in
738   <xref target="field.extensibility"/>.
739</t>
740<t>
741   Intermediaries that process HTTP messages (i.e., all intermediaries
742   other than those acting as tunnels) &MUST; send their own HTTP-version
743   in forwarded messages.  In other words, they are not allowed to blindly
744   forward the first line of an HTTP message without ensuring that the
745   protocol version in that message matches a version to which that
746   intermediary is conformant for both the receiving and
747   sending of messages.  Forwarding an HTTP message without rewriting
748   the HTTP-version might result in communication errors when downstream
749   recipients use the message sender's version to determine what features
750   are safe to use for later communication with that sender.
751</t>
752<t>
753   A client &SHOULD; send a request version equal to the highest
754   version to which the client is conformant and
755   whose major version is no higher than the highest version supported
756   by the server, if this is known.  A client &MUST-NOT; send a
757   version to which it is not conformant.
758</t>
759<t>
760   A client &MAY; send a lower request version if it is known that
761   the server incorrectly implements the HTTP specification, but only
762   after the client has attempted at least one normal request and determined
763   from the response status code or header fields (e.g., <x:ref>Server</x:ref>) that
764   the server improperly handles higher request versions.
765</t>
766<t>
767   A server &SHOULD; send a response version equal to the highest version to
768   which the server is conformant that has a major version less than or equal
769   to the one received in the request.
770   A server &MUST-NOT; send a version to which it is not conformant.
771   A server can send a <x:ref>505 (HTTP Version Not Supported)</x:ref>
772   response if it wishes, for any reason, to refuse service of the client's
773   major protocol version.
774</t>
775<t>
776   A server &MAY; send an HTTP/1.0 response to a request
777   if it is known or suspected that the client incorrectly implements the
778   HTTP specification and is incapable of correctly processing later
779   version responses, such as when a client fails to parse the version
780   number correctly or when an intermediary is known to blindly forward
781   the HTTP-version even when it doesn't conform to the given minor
782   version of the protocol. Such protocol downgrades &SHOULD-NOT; be
783   performed unless triggered by specific client attributes, such as when
784   one or more of the request header fields (e.g., <x:ref>User-Agent</x:ref>)
785   uniquely match the values sent by a client known to be in error.
786</t>
787<t>
788   The intention of HTTP's versioning design is that the major number
789   will only be incremented if an incompatible message syntax is
790   introduced, and that the minor number will only be incremented when
791   changes made to the protocol have the effect of adding to the message
792   semantics or implying additional capabilities of the sender.  However,
793   the minor version was not incremented for the changes introduced between
794   <xref target="RFC2068"/> and <xref target="RFC2616"/>, and this revision
795   has specifically avoided any such changes to the protocol.
796</t>
797<t>
798   When an HTTP message is received with a major version number that the
799   recipient implements, but a higher minor version number than what the
800   recipient implements, the recipient &SHOULD; process the message as if it
801   were in the highest minor version within that major version to which the
802   recipient is conformant. A recipient can assume that a message with a
803   higher minor version, when sent to a recipient that has not yet indicated
804   support for that higher version, is sufficiently backwards-compatible to be
805   safely processed by any implementation of the same major version.
806</t>
807</section>
808
809<section title="Uniform Resource Identifiers" anchor="uri">
810<iref primary="true" item="resource"/>
811<t>
812   Uniform Resource Identifiers (URIs) <xref target="RFC3986"/> are used
813   throughout HTTP as the means for identifying resources (&resource;).
814   URI references are used to target requests, indicate redirects, and define
815   relationships.
816</t>
817  <x:anchor-alias value="URI-reference"/>
818  <x:anchor-alias value="absolute-URI"/>
819  <x:anchor-alias value="relative-part"/>
820  <x:anchor-alias value="authority"/>
821  <x:anchor-alias value="uri-host"/>
822  <x:anchor-alias value="port"/>
823  <x:anchor-alias value="path-abempty"/>
824  <x:anchor-alias value="segment"/>
825  <x:anchor-alias value="query"/>
826  <x:anchor-alias value="fragment"/>
827  <x:anchor-alias value="absolute-path"/>
828  <x:anchor-alias value="partial-URI"/>
829<t>
830   This specification adopts the definitions of "URI-reference",
831   "absolute-URI", "relative-part", "authority", "port", "host",
832   "path-abempty", "segment", "query", and "fragment" from the
833   URI generic syntax.
834   In addition, we define an "absolute-path" rule (that differs from
835   RFC 3986's "path-absolute" in that it allows a leading "//")
836   and a "partial-URI" rule for protocol elements
837   that allow a relative URI but not a fragment.
838</t>
839<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="URI-reference"><!--exported production--></iref><iref primary="true" item="Grammar" subitem="absolute-URI"/><iref primary="true" item="Grammar" subitem="authority"/><iref primary="true" item="Grammar" subitem="absolute-path"/><iref primary="true" item="Grammar" subitem="port"/><iref primary="true" item="Grammar" subitem="query"/><iref primary="true" item="Grammar" subitem="fragment"/><iref primary="true" item="Grammar" subitem="segment"/><iref primary="true" item="Grammar" subitem="uri-host"/><iref primary="true" item="Grammar" subitem="partial-URI"><!--exported production--></iref>
840  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in <xref target="RFC3986" x:fmt="," x:sec="4.1"/>&gt;
841  <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in <xref target="RFC3986" x:fmt="," x:sec="4.3"/>&gt;
842  <x:ref>relative-part</x:ref> = &lt;relative-part, defined in <xref target="RFC3986" x:fmt="," x:sec="4.2"/>&gt;
843  <x:ref>authority</x:ref>     = &lt;authority, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2"/>&gt;
844  <x:ref>uri-host</x:ref>      = &lt;host, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>&gt;
845  <x:ref>port</x:ref>          = &lt;port, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.3"/>&gt;
846  <x:ref>path-abempty</x:ref>  = &lt;path-abempty, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
847  <x:ref>segment</x:ref>       = &lt;segment, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
848  <x:ref>query</x:ref>         = &lt;query, defined in <xref target="RFC3986" x:fmt="," x:sec="3.4"/>&gt;
849  <x:ref>fragment</x:ref>      = &lt;fragment, defined in <xref target="RFC3986" x:fmt="," x:sec="3.5"/>&gt;
850 
851  <x:ref>absolute-path</x:ref> = 1*( "/" segment )
852  <x:ref>partial-URI</x:ref>   = relative-part [ "?" query ]
853</artwork></figure>
854<t>
855   Each protocol element in HTTP that allows a URI reference will indicate
856   in its ABNF production whether the element allows any form of reference
857   (URI-reference), only a URI in absolute form (absolute-URI), only the
858   path and optional query components, or some combination of the above.
859   Unless otherwise indicated, URI references are parsed
860   relative to the effective request URI
861   (<xref target="effective.request.uri"/>).
862</t>
863
864<section title="http URI scheme" anchor="http.uri">
865  <x:anchor-alias value="http-URI"/>
866  <iref item="http URI scheme" primary="true"/>
867  <iref item="URI scheme" subitem="http" primary="true"/>
868<t>
869   The "http" URI scheme is hereby defined for the purpose of minting
870   identifiers according to their association with the hierarchical
871   namespace governed by a potential HTTP origin server listening for
872   TCP (<xref target="RFC0793"/>) connections on a given port.
873</t>
874<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http-URI"><!--terminal production--></iref>
875  <x:ref>http-URI</x:ref> = "http:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
876             [ "#" <x:ref>fragment</x:ref> ]
877</artwork></figure>
878<t>
879   The HTTP origin server is identified by the generic syntax's
880   <x:ref>authority</x:ref> component, which includes a host identifier
881   and optional TCP port (<xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>).
882   The remainder of the URI, consisting of both the hierarchical path
883   component and optional query component, serves as an identifier for
884   a potential resource within that origin server's name space.
885</t>
886<t>
887   A sender &MUST-NOT; generate an "http" URI with an empty host identifier.
888   A recipient that processes such a URI reference &MUST; reject it as invalid.
889</t>
890<t>
891   If the host identifier is provided as an IP address,
892   then the origin server is any listener on the indicated TCP port at
893   that IP address. If host is a registered name, then that name is
894   considered an indirect identifier and the recipient might use a name
895   resolution service, such as DNS, to find the address of a listener
896   for that host.
897   If the port subcomponent is empty or not given, then TCP port 80 is
898   assumed (the default reserved port for WWW services).
899</t>
900<t>
901   Regardless of the form of host identifier, access to that host is not
902   implied by the mere presence of its name or address. The host might or might
903   not exist and, even when it does exist, might or might not be running an
904   HTTP server or listening to the indicated port. The "http" URI scheme
905   makes use of the delegated nature of Internet names and addresses to
906   establish a naming authority (whatever entity has the ability to place
907   an HTTP server at that Internet name or address) and allows that
908   authority to determine which names are valid and how they might be used.
909</t>
910<t>
911   When an "http" URI is used within a context that calls for access to the
912   indicated resource, a client &MAY; attempt access by resolving
913   the host to an IP address, establishing a TCP connection to that address
914   on the indicated port, and sending an HTTP request message
915   (<xref target="http.message"/>) containing the URI's identifying data
916   (<xref target="message.routing"/>) to the server.
917   If the server responds to that request with a non-interim HTTP response
918   message, as described in &status-codes;, then that response
919   is considered an authoritative answer to the client's request.
920</t>
921<t>
922   Although HTTP is independent of the transport protocol, the "http"
923   scheme is specific to TCP-based services because the name delegation
924   process depends on TCP for establishing authority.
925   An HTTP service based on some other underlying connection protocol
926   would presumably be identified using a different URI scheme, just as
927   the "https" scheme (below) is used for resources that require an
928   end-to-end secured connection. Other protocols might also be used to
929   provide access to "http" identified resources &mdash; it is only the
930   authoritative interface that is specific to TCP.
931</t>
932<t>
933   The URI generic syntax for authority also includes a deprecated
934   userinfo subcomponent (<xref target="RFC3986" x:fmt="," x:sec="3.2.1"/>)
935   for including user authentication information in the URI.  Some
936   implementations make use of the userinfo component for internal
937   configuration of authentication information, such as within command
938   invocation options, configuration files, or bookmark lists, even
939   though such usage might expose a user identifier or password.
940   A sender &MUST-NOT; generate the userinfo subcomponent (and its "@"
941   delimiter) when an "http" URI reference is generated within a message as a
942   request target or header field value.
943   Before making use of an "http" URI reference received from an untrusted
944   source, a recipient ought to parse for userinfo and treat its presence as
945   an error; it is likely being used to obscure the authority for the sake of
946   phishing attacks.
947</t>
948</section>
949
950<section title="https URI scheme" anchor="https.uri">
951   <x:anchor-alias value="https-URI"/>
952   <iref item="https URI scheme"/>
953   <iref item="URI scheme" subitem="https"/>
954<t>
955   The "https" URI scheme is hereby defined for the purpose of minting
956   identifiers according to their association with the hierarchical
957   namespace governed by a potential HTTP origin server listening to a
958   given TCP port for TLS-secured connections
959   (<xref target="RFC0793"/>, <xref target="RFC5246"/>).
960</t>
961<t>
962   All of the requirements listed above for the "http" scheme are also
963   requirements for the "https" scheme, except that a default TCP port
964   of 443 is assumed if the port subcomponent is empty or not given,
965   and the user agent &MUST; ensure that its connection to the origin
966   server is secured through the use of strong encryption, end-to-end,
967   prior to sending the first HTTP request.
968</t>
969<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="https-URI"><!--terminal production--></iref>
970  <x:ref>https-URI</x:ref> = "https:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
971              [ "#" <x:ref>fragment</x:ref> ]
972</artwork></figure>
973<t>
974   Note that the "https" URI scheme depends on both TLS and TCP for
975   establishing authority.
976   Resources made available via the "https" scheme have no shared
977   identity with the "http" scheme even if their resource identifiers
978   indicate the same authority (the same host listening to the same
979   TCP port).  They are distinct name spaces and are considered to be
980   distinct origin servers.  However, an extension to HTTP that is
981   defined to apply to entire host domains, such as the Cookie protocol
982   <xref target="RFC6265"/>, can allow information
983   set by one service to impact communication with other services
984   within a matching group of host domains.
985</t>
986<t>
987   The process for authoritative access to an "https" identified
988   resource is defined in <xref target="RFC2818"/>.
989</t>
990</section>
991
992<section title="http and https URI Normalization and Comparison" anchor="uri.comparison">
993<t>
994   Since the "http" and "https" schemes conform to the URI generic syntax,
995   such URIs are normalized and compared according to the algorithm defined
996   in <xref target="RFC3986" x:fmt="of" x:sec="6"/>, using the defaults
997   described above for each scheme.
998</t>
999<t>
1000   If the port is equal to the default port for a scheme, the normal form is
1001   to omit the port subcomponent. When not being used in absolute form as the
1002   request target of an OPTIONS request, an empty path component is equivalent
1003   to an absolute path of "/", so the normal form is to provide a path of "/"
1004   instead. The scheme and host are case-insensitive and normally provided in
1005   lowercase; all other components are compared in a case-sensitive manner.
1006   Characters other than those in the "reserved" set are equivalent to their
1007   percent-encoded octets (see <xref target="RFC3986" x:fmt=","
1008   x:sec="2.1"/>): the normal form is to not encode them.
1009</t>
1010<t>
1011   For example, the following three URIs are equivalent:
1012</t>
1013<figure><artwork type="example">
1014   http://example.com:80/~smith/home.html
1015   http://EXAMPLE.com/%7Esmith/home.html
1016   http://EXAMPLE.com:/%7esmith/home.html
1017</artwork></figure>
1018</section>
1019</section>
1020</section>
1021
1022<section title="Message Format" anchor="http.message">
1023<x:anchor-alias value="generic-message"/>
1024<x:anchor-alias value="message.types"/>
1025<x:anchor-alias value="HTTP-message"/>
1026<x:anchor-alias value="start-line"/>
1027<iref item="header section"/>
1028<iref item="headers"/>
1029<iref item="header field"/>
1030<t>
1031   All HTTP/1.1 messages consist of a start-line followed by a sequence of
1032   octets in a format similar to the Internet Message Format
1033   <xref target="RFC5322"/>: zero or more header fields (collectively
1034   referred to as the "headers" or the "header section"), an empty line
1035   indicating the end of the header section, and an optional message body.
1036</t>
1037<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-message"><!--terminal production--></iref>
1038  <x:ref>HTTP-message</x:ref>   = <x:ref>start-line</x:ref>
1039                   *( <x:ref>header-field</x:ref> <x:ref>CRLF</x:ref> )
1040                   <x:ref>CRLF</x:ref>
1041                   [ <x:ref>message-body</x:ref> ]
1042</artwork></figure>
1043<t>
1044   The normal procedure for parsing an HTTP message is to read the
1045   start-line into a structure, read each header field into a hash
1046   table by field name until the empty line, and then use the parsed
1047   data to determine if a message body is expected.  If a message body
1048   has been indicated, then it is read as a stream until an amount
1049   of octets equal to the message body length is read or the connection
1050   is closed.
1051</t>
1052<t>
1053   A recipient &MUST; parse an HTTP message as a sequence of octets in an
1054   encoding that is a superset of US-ASCII <xref target="USASCII"/>.
1055   Parsing an HTTP message as a stream of Unicode characters, without regard
1056   for the specific encoding, creates security vulnerabilities due to the
1057   varying ways that string processing libraries handle invalid multibyte
1058   character sequences that contain the octet LF (%x0A).  String-based
1059   parsers can only be safely used within protocol elements after the element
1060   has been extracted from the message, such as within a header field-value
1061   after message parsing has delineated the individual fields.
1062</t>
1063<t>
1064   An HTTP message can be parsed as a stream for incremental processing or
1065   forwarding downstream.  However, recipients cannot rely on incremental
1066   delivery of partial messages, since some implementations will buffer or
1067   delay message forwarding for the sake of network efficiency, security
1068   checks, or payload transformations.
1069</t>
1070<t>
1071   A sender &MUST-NOT; send whitespace between the start-line and
1072   the first header field.
1073   A recipient that receives whitespace between the start-line and
1074   the first header field &MUST; either reject the message as invalid or
1075   consume each whitespace-preceded line without further processing of it
1076   (i.e., ignore the entire line, along with any subsequent lines preceded
1077   by whitespace, until a properly formed header field is received or the
1078   header section is terminated).
1079</t>
1080<t>
1081   The presence of such whitespace in a request
1082   might be an attempt to trick a server into ignoring that field or
1083   processing the line after it as a new request, either of which might
1084   result in a security vulnerability if other implementations within
1085   the request chain interpret the same message differently.
1086   Likewise, the presence of such whitespace in a response might be
1087   ignored by some clients or cause others to cease parsing.
1088</t>
1089
1090<section title="Start Line" anchor="start.line">
1091  <x:anchor-alias value="Start-Line"/>
1092<t>
1093   An HTTP message can either be a request from client to server or a
1094   response from server to client.  Syntactically, the two types of message
1095   differ only in the start-line, which is either a request-line (for requests)
1096   or a status-line (for responses), and in the algorithm for determining
1097   the length of the message body (<xref target="message.body"/>).
1098</t>
1099<t>
1100   In theory, a client could receive requests and a server could receive
1101   responses, distinguishing them by their different start-line formats,
1102   but in practice servers are implemented to only expect a request
1103   (a response is interpreted as an unknown or invalid request method)
1104   and clients are implemented to only expect a response.
1105</t>
1106<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="start-line"/>
1107  <x:ref>start-line</x:ref>     = <x:ref>request-line</x:ref> / <x:ref>status-line</x:ref>
1108</artwork></figure>
1109
1110<section title="Request Line" anchor="request.line">
1111  <x:anchor-alias value="Request"/>
1112  <x:anchor-alias value="request-line"/>
1113<t>
1114   A request-line begins with a method token, followed by a single
1115   space (SP), the request-target, another single space (SP), the
1116   protocol version, and ending with CRLF.
1117</t>
1118<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-line"/>
1119  <x:ref>request-line</x:ref>   = <x:ref>method</x:ref> <x:ref>SP</x:ref> <x:ref>request-target</x:ref> <x:ref>SP</x:ref> <x:ref>HTTP-version</x:ref> <x:ref>CRLF</x:ref>
1120</artwork></figure>
1121<iref primary="true" item="method"/>
1122<t anchor="method">
1123   The method token indicates the request method to be performed on the
1124   target resource. The request method is case-sensitive.
1125</t>
1126<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="method"/>
1127  <x:ref>method</x:ref>         = <x:ref>token</x:ref>
1128</artwork></figure>
1129<t>
1130   The request methods defined by this specification can be found in
1131   &methods;, along with information regarding the HTTP method registry
1132   and considerations for defining new methods.
1133</t>
1134<iref item="request-target"/>
1135<t>
1136   The request-target identifies the target resource upon which to apply
1137   the request, as defined in <xref target="request-target"/>.
1138</t>
1139<t>
1140   Recipients typically parse the request-line into its component parts by
1141   splitting on whitespace (see <xref target="message.robustness"/>), since
1142   no whitespace is allowed in the three components.
1143   Unfortunately, some user agents fail to properly encode or exclude
1144   whitespace found in hypertext references, resulting in those disallowed
1145   characters being sent in a request-target.
1146</t>
1147<t>
1148   Recipients of an invalid request-line &SHOULD; respond with either a
1149   <x:ref>400 (Bad Request)</x:ref> error or a <x:ref>301 (Moved Permanently)</x:ref>
1150   redirect with the request-target properly encoded.  A recipient &SHOULD-NOT;
1151   attempt to autocorrect and then process the request without a redirect,
1152   since the invalid request-line might be deliberately crafted to bypass
1153   security filters along the request chain.
1154</t>
1155<t>
1156   HTTP does not place a pre-defined limit on the length of a request-line.
1157   A server that receives a method longer than any that it implements
1158   &SHOULD; respond with a <x:ref>501 (Not Implemented)</x:ref> status code.
1159   A server ought to be prepared to receive URIs of unbounded length, as
1160   described in <xref target="conformance"/>, and &MUST; respond with a
1161   <x:ref>414 (URI Too Long)</x:ref> status code if the received
1162   request-target is longer than the server wishes to parse (see &status-414;).
1163</t>
1164<t>
1165   Various ad-hoc limitations on request-line length are found in practice.
1166   It is &RECOMMENDED; that all HTTP senders and recipients support, at a
1167   minimum, request-line lengths of 8000 octets.
1168</t>
1169</section>
1170
1171<section title="Status Line" anchor="status.line">
1172  <x:anchor-alias value="response"/>
1173  <x:anchor-alias value="status-line"/>
1174  <x:anchor-alias value="status-code"/>
1175  <x:anchor-alias value="reason-phrase"/>
1176<t>
1177   The first line of a response message is the status-line, consisting
1178   of the protocol version, a space (SP), the status code, another space,
1179   a possibly-empty textual phrase describing the status code, and
1180   ending with CRLF.
1181</t>
1182<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-line"/>
1183  <x:ref>status-line</x:ref> = <x:ref>HTTP-version</x:ref> <x:ref>SP</x:ref> <x:ref>status-code</x:ref> <x:ref>SP</x:ref> <x:ref>reason-phrase</x:ref> <x:ref>CRLF</x:ref>
1184</artwork></figure>
1185<t>
1186   The status-code element is a 3-digit integer code describing the
1187   result of the server's attempt to understand and satisfy the client's
1188   corresponding request. The rest of the response message is to be
1189   interpreted in light of the semantics defined for that status code.
1190   See &status-codes; for information about the semantics of status codes,
1191   including the classes of status code (indicated by the first digit),
1192   the status codes defined by this specification, considerations for the
1193   definition of new status codes, and the IANA registry.
1194</t>
1195<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-code"/>
1196  <x:ref>status-code</x:ref>    = 3<x:ref>DIGIT</x:ref>
1197</artwork></figure>
1198<t>  
1199   The reason-phrase element exists for the sole purpose of providing a
1200   textual description associated with the numeric status code, mostly
1201   out of deference to earlier Internet application protocols that were more
1202   frequently used with interactive text clients. A client &SHOULD; ignore
1203   the reason-phrase content.
1204</t>
1205<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="reason-phrase"/>
1206  <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> )
1207</artwork></figure>
1208</section>
1209</section>
1210
1211<section title="Header Fields" anchor="header.fields">
1212  <x:anchor-alias value="header-field"/>
1213  <x:anchor-alias value="field-content"/>
1214  <x:anchor-alias value="field-name"/>
1215  <x:anchor-alias value="field-value"/>
1216  <x:anchor-alias value="obs-fold"/>
1217<t>
1218   Each header field consists of a case-insensitive field name
1219   followed by a colon (":"), optional leading whitespace, the field value,
1220   and optional trailing whitespace.
1221</t>
1222<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="header-field"/><iref primary="true" item="Grammar" subitem="field-name"/><iref primary="true" item="Grammar" subitem="field-value"/><iref primary="true" item="Grammar" subitem="field-content"/><iref primary="true" item="Grammar" subitem="obs-fold"/>
1223  <x:ref>header-field</x:ref>   = <x:ref>field-name</x:ref> ":" <x:ref>OWS</x:ref> <x:ref>field-value</x:ref> <x:ref>OWS</x:ref>
1224  <x:ref>field-name</x:ref>     = <x:ref>token</x:ref>
1225  <x:ref>field-value</x:ref>    = *( <x:ref>field-content</x:ref> / <x:ref>obs-fold</x:ref> )
1226  <x:ref>field-content</x:ref>  = *( <x:ref>HTAB</x:ref> / <x:ref>SP</x:ref> / <x:ref>VCHAR</x:ref> / <x:ref>obs-text</x:ref> )
1227  <x:ref>obs-fold</x:ref>       = <x:ref>CRLF</x:ref> ( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1228                 ; obsolete line folding
1229                 ; see <xref target="field.parsing"/>
1230</artwork></figure>
1231<t>
1232   The field-name token labels the corresponding field-value as having the
1233   semantics defined by that header field.  For example, the <x:ref>Date</x:ref>
1234   header field is defined in &header-date; as containing the origination
1235   timestamp for the message in which it appears.
1236</t>
1237
1238<section title="Field Extensibility" anchor="field.extensibility">
1239<t>
1240   Header fields are fully extensible: there is no limit on the
1241   introduction of new field names, each presumably defining new semantics,
1242   nor on the number of header fields used in a given message.  Existing
1243   fields are defined in each part of this specification and in many other
1244   specifications outside the core standard.
1245</t>
1246<t>
1247   New header fields can be defined such that, when they are understood by a
1248   recipient, they might override or enhance the interpretation of previously
1249   defined header fields, define preconditions on request evaluation, or
1250   refine the meaning of responses.
1251</t>
1252<t>
1253   A proxy &MUST; forward unrecognized header fields unless the
1254   field-name is listed in the <x:ref>Connection</x:ref> header field
1255   (<xref target="header.connection"/>) or the proxy is specifically
1256   configured to block, or otherwise transform, such fields.
1257   Other recipients &SHOULD; ignore unrecognized header fields.
1258   These requirements allow HTTP's functionality to be enhanced without
1259   requiring prior update of deployed intermediaries.
1260</t>
1261<t>
1262   All defined header fields ought to be registered with IANA in the
1263   Message Header Field Registry, as described in &iana-header-registry;.
1264</t>
1265</section>
1266
1267<section title="Field Order" anchor="field.order">
1268<t>
1269   The order in which header fields with differing field names are
1270   received is not significant. However, it is "good practice" to send
1271   header fields that contain control data first, such as <x:ref>Host</x:ref>
1272   on requests and <x:ref>Date</x:ref> on responses, so that implementations
1273   can decide when not to handle a message as early as possible.  A server
1274   &MUST; wait until the entire header section is received before interpreting
1275   a request message, since later header fields might include conditionals,
1276   authentication credentials, or deliberately misleading duplicate
1277   header fields that would impact request processing.
1278</t>
1279<t>
1280   A sender &MUST-NOT; generate multiple header fields with the same field
1281   name in a message unless either the entire field value for that
1282   header field is defined as a comma-separated list [i.e., #(values)]
1283   or the header field is a well-known exception (as noted below).
1284</t>
1285<t>
1286   A recipient &MAY; combine multiple header fields with the same field name
1287   into one "field-name: field-value" pair, without changing the semantics of
1288   the message, by appending each subsequent field value to the combined
1289   field value in order, separated by a comma. The order in which
1290   header fields with the same field name are received is therefore
1291   significant to the interpretation of the combined field value;
1292   a proxy &MUST-NOT; change the order of these field values when
1293   forwarding a message.
1294</t>
1295<x:note>
1296  <t>
1297   &Note; In practice, the "Set-Cookie" header field (<xref target="RFC6265"/>)
1298   often appears multiple times in a response message and does not use the
1299   list syntax, violating the above requirements on multiple header fields
1300   with the same name. Since it cannot be combined into a single field-value,
1301   recipients ought to handle "Set-Cookie" as a special case while processing
1302   header fields. (See Appendix A.2.3 of <xref target="Kri2001"/> for details.)
1303  </t>
1304</x:note>
1305</section>
1306
1307<section title="Whitespace" anchor="whitespace">
1308<t anchor="rule.LWS">
1309   This specification uses three rules to denote the use of linear
1310   whitespace: OWS (optional whitespace), RWS (required whitespace), and
1311   BWS ("bad" whitespace).
1312</t>
1313<t anchor="rule.OWS">
1314   The OWS rule is used where zero or more linear whitespace octets might
1315   appear. For protocol elements where optional whitespace is preferred to
1316   improve readability, a sender &SHOULD; generate the optional whitespace
1317   as a single SP; otherwise, a sender &SHOULD-NOT; generate optional
1318   whitespace except as needed to white-out invalid or unwanted protocol
1319   elements during in-place message filtering.
1320</t>
1321<t anchor="rule.RWS">
1322   The RWS rule is used when at least one linear whitespace octet is required
1323   to separate field tokens. A sender &SHOULD; generate RWS as a single SP.
1324</t>
1325<t anchor="rule.BWS">
1326   The BWS rule is used where the grammar allows optional whitespace only for
1327   historical reasons. A sender &MUST-NOT; generate BWS in messages.
1328   A recipient &MUST; parse for such bad whitespace and remove it before
1329   interpreting the protocol element.
1330</t>
1331<t anchor="rule.whitespace">
1332  <x:anchor-alias value="BWS"/>
1333  <x:anchor-alias value="OWS"/>
1334  <x:anchor-alias value="RWS"/>
1335</t>
1336<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OWS"/><iref primary="true" item="Grammar" subitem="RWS"/><iref primary="true" item="Grammar" subitem="BWS"/>
1337  <x:ref>OWS</x:ref>            = *( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1338                 ; optional whitespace
1339  <x:ref>RWS</x:ref>            = 1*( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1340                 ; required whitespace
1341  <x:ref>BWS</x:ref>            = <x:ref>OWS</x:ref>
1342                 ; "bad" whitespace
1343</artwork></figure>
1344</section>
1345
1346<section title="Field Parsing" anchor="field.parsing">
1347<t>
1348   Messages are parsed using a generic algorithm, independent of the
1349   individual header field names. The contents within a given field value are
1350   not parsed until a later stage of message interpretation (usually after the
1351   message's entire header section has been processed).
1352   Consequently, this specification does not use ABNF rules to define each
1353   "Field-Name: Field Value" pair, as was done in previous editions.
1354   Instead, this specification uses ABNF rules which are named according to
1355   each registered field name, wherein the rule defines the valid grammar for
1356   that field's corresponding field values (i.e., after the field-value
1357   has been extracted from the header section by a generic field parser).
1358</t>
1359<t>
1360   No whitespace is allowed between the header field-name and colon.
1361   In the past, differences in the handling of such whitespace have led to
1362   security vulnerabilities in request routing and response handling.
1363   A server &MUST; reject any received request message that contains
1364   whitespace between a header field-name and colon with a response code of
1365   <x:ref>400 (Bad Request)</x:ref>. A proxy &MUST; remove any such whitespace
1366   from a response message before forwarding the message downstream.
1367</t>
1368<t>
1369   A field value is preceded by optional whitespace (OWS); a single SP is
1370   preferred. The field value does not include any leading or trailing white
1371   space: OWS occurring before the first non-whitespace octet of the field
1372   value or after the last non-whitespace octet of the field value ought to be
1373   excluded by parsers when extracting the field value from a header field.
1374</t>
1375<t>
1376   A recipient of field-content containing multiple sequential octets of
1377   optional (OWS) or required (RWS) whitespace &SHOULD; either replace the
1378   sequence with a single SP or transform any non-SP octets in the sequence to
1379   SP octets before interpreting the field value or forwarding the message
1380   downstream.
1381</t>
1382<t>
1383   Historically, HTTP header field values could be extended over multiple
1384   lines by preceding each extra line with at least one space or horizontal
1385   tab (obs-fold). This specification deprecates such line folding except
1386   within the message/http media type
1387   (<xref target="internet.media.type.message.http"/>).
1388   A sender &MUST-NOT; generate a message that includes line folding
1389   (i.e., that has any field-value that contains a match to the
1390   <x:ref>obs-fold</x:ref> rule) unless the message is intended for packaging
1391   within the message/http media type.
1392</t>
1393<t>
1394   A server that receives an <x:ref>obs-fold</x:ref> in a request message that
1395   is not within a message/http container &MUST; either reject the message by
1396   sending a <x:ref>400 (Bad Request)</x:ref>, preferably with a
1397   representation explaining that obsolete line folding is unacceptable, or
1398   replace each received <x:ref>obs-fold</x:ref> with one or more
1399   <x:ref>SP</x:ref> octets prior to interpreting the field value or
1400   forwarding the message downstream.
1401</t>
1402<t>
1403   A proxy or gateway that receives an <x:ref>obs-fold</x:ref> in a response
1404   message that is not within a message/http container &MUST; either discard
1405   the message and replace it with a <x:ref>502 (Bad Gateway)</x:ref>
1406   response, preferably with a representation explaining that unacceptable
1407   line folding was received, or replace each received <x:ref>obs-fold</x:ref>
1408   with one or more <x:ref>SP</x:ref> octets prior to interpreting the field
1409   value or forwarding the message downstream.
1410</t>
1411<t>
1412   A user agent that receives an <x:ref>obs-fold</x:ref> in a response message
1413   that is not within a message/http container &MUST; replace each received
1414   <x:ref>obs-fold</x:ref> with one or more <x:ref>SP</x:ref> octets prior to
1415   interpreting the field value.
1416</t>
1417<t>
1418   Historically, HTTP has allowed field content with text in the ISO-8859-1
1419   <xref target="ISO-8859-1"/> charset, supporting other charsets only
1420   through use of <xref target="RFC2047"/> encoding.
1421   In practice, most HTTP header field values use only a subset of the
1422   US-ASCII charset <xref target="USASCII"/>. Newly defined
1423   header fields &SHOULD; limit their field values to US-ASCII octets.
1424   A recipient &SHOULD; treat other octets in field content (obs-text) as
1425   opaque data.
1426</t>
1427</section>
1428
1429<section title="Field Limits" anchor="field.limits">
1430<t>
1431   HTTP does not place a pre-defined limit on the length of each header field
1432   or on the length of the header section as a whole, as described in
1433   <xref target="conformance"/>. Various ad-hoc limitations on individual
1434   header field length are found in practice, often depending on the specific
1435   field semantics.
1436</t>
1437<t>
1438   A server ought to be prepared to receive request header fields of unbounded
1439   length and &MUST; respond with an appropriate
1440   <x:ref>4xx (Client Error)</x:ref> status code if the received header
1441   field(s) are larger than the server wishes to process.
1442</t>
1443<t>
1444   A client ought to be prepared to receive response header fields of
1445   unbounded length.
1446   A client &MAY; discard or truncate received header fields that are larger
1447   than the client wishes to process if the field semantics are such that the
1448   dropped value(s) can be safely ignored without changing the
1449   message framing or response semantics.
1450</t>
1451</section>
1452
1453<section title="Field value components" anchor="field.components">
1454<t anchor="rule.token.separators">
1455  <x:anchor-alias value="tchar"/>
1456  <x:anchor-alias value="token"/>
1457  <x:anchor-alias value="special"/>
1458   Most HTTP header field values are defined using common syntax components
1459   (token, quoted-string, and comment) separated by whitespace or specific
1460   delimiting characters. Delimiters are chosen from the set of US-ASCII
1461   visual characters not allowed in a token ({VCHAR - tchar}).
1462</t>
1463<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="token"/><iref primary="true" item="Grammar" subitem="tchar"/>
1464  <x:ref>token</x:ref>          = 1*<x:ref>tchar</x:ref>
1465<!--
1466  IMPORTANT: when editing "tchar" make sure that "special" is updated accordingly!!!
1467 -->
1468  <x:ref>tchar</x:ref>          = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*"
1469                 / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
1470                 / <x:ref>DIGIT</x:ref> / <x:ref>ALPHA</x:ref>
1471                 ; any <x:ref>VCHAR</x:ref>, except <x:ref>special</x:ref>
1472
1473  <x:ref>special</x:ref>        = "(" / ")" / "&lt;" / ">" / "@" / ","
1474                 / ";" / ":" / "\" / DQUOTE / "/" / "["
1475                 / "]" / "?" / "=" / "{" / "}"
1476</artwork></figure>
1477<t anchor="rule.quoted-string">
1478  <x:anchor-alias value="quoted-string"/>
1479  <x:anchor-alias value="qdtext"/>
1480  <x:anchor-alias value="obs-text"/>
1481   A string of text is parsed as a single value if it is quoted using
1482   double-quote marks.
1483</t>
1484<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-string"/><iref primary="true" item="Grammar" subitem="qdtext"/><iref primary="true" item="Grammar" subitem="obs-text"/>
1485  <x:ref>quoted-string</x:ref>  = <x:ref>DQUOTE</x:ref> *( <x:ref>qdtext</x:ref> / <x:ref>quoted-pair</x:ref> ) <x:ref>DQUOTE</x:ref>
1486  <x:ref>qdtext</x:ref>         = <x:ref>HTAB</x:ref> / <x:ref>SP</x:ref> /%x21 / %x23-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1487  <x:ref>obs-text</x:ref>       = %x80-FF
1488</artwork></figure>
1489<t anchor="rule.comment">
1490  <x:anchor-alias value="comment"/>
1491  <x:anchor-alias value="ctext"/>
1492   Comments can be included in some HTTP header fields by surrounding
1493   the comment text with parentheses. Comments are only allowed in
1494   fields containing "comment" as part of their field value definition.
1495</t>
1496<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="comment"/><iref primary="true" item="Grammar" subitem="ctext"/>
1497  <x:ref>comment</x:ref>        = "(" *( <x:ref>ctext</x:ref> / <x:ref>quoted-pair</x:ref> / <x:ref>comment</x:ref> ) ")"
1498  <x:ref>ctext</x:ref>          = <x:ref>HTAB</x:ref> / <x:ref>SP</x:ref> / %x21-27 / %x2A-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1499</artwork></figure>
1500<t anchor="rule.quoted-pair">
1501  <x:anchor-alias value="quoted-pair"/>
1502   The backslash octet ("\") can be used as a single-octet
1503   quoting mechanism within quoted-string and comment constructs.
1504   Recipients that process the value of a quoted-string &MUST; handle a
1505   quoted-pair as if it were replaced by the octet following the backslash.
1506</t>
1507<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-pair"/>
1508  <x:ref>quoted-pair</x:ref>    = "\" ( <x:ref>HTAB</x:ref> / <x:ref>SP</x:ref> / <x:ref>VCHAR</x:ref> / <x:ref>obs-text</x:ref> )
1509</artwork></figure>
1510<t>
1511   A sender &SHOULD-NOT; generate a quoted-pair in a quoted-string except
1512   where necessary to quote DQUOTE and backslash octets occurring within that
1513   string.
1514   A sender &SHOULD-NOT; generate a quoted-pair in a comment except
1515   where necessary to quote parentheses ["(" and ")"] and backslash octets
1516   occurring within that comment.
1517</t>
1518</section>
1519
1520</section>
1521
1522<section title="Message Body" anchor="message.body">
1523  <x:anchor-alias value="message-body"/>
1524<t>
1525   The message body (if any) of an HTTP message is used to carry the
1526   payload body of that request or response.  The message body is
1527   identical to the payload body unless a transfer coding has been
1528   applied, as described in <xref target="header.transfer-encoding"/>.
1529</t>
1530<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-body"/>
1531  <x:ref>message-body</x:ref> = *OCTET
1532</artwork></figure>
1533<t>
1534   The rules for when a message body is allowed in a message differ for
1535   requests and responses.
1536</t>
1537<t>
1538   The presence of a message body in a request is signaled by a
1539   <x:ref>Content-Length</x:ref> or <x:ref>Transfer-Encoding</x:ref> header
1540   field. Request message framing is independent of method semantics,
1541   even if the method does not define any use for a message body.
1542</t>
1543<t>
1544   The presence of a message body in a response depends on both
1545   the request method to which it is responding and the response
1546   status code (<xref target="status.line"/>).
1547   Responses to the HEAD request method never include a message body
1548   because the associated response header fields (e.g.,
1549   <x:ref>Transfer-Encoding</x:ref>, <x:ref>Content-Length</x:ref>, etc.),
1550   if present, indicate only what their values would have been if the request
1551   method had been GET (&HEAD;).
1552   <x:ref>2xx (Successful)</x:ref> responses to CONNECT switch to tunnel
1553   mode instead of having a message body (&CONNECT;).
1554   All <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, and
1555   <x:ref>304 (Not Modified)</x:ref> responses do not include a message body.
1556   All other responses do include a message body, although the body
1557   might be of zero length.
1558</t>
1559
1560<section title="Transfer-Encoding" anchor="header.transfer-encoding">
1561  <iref primary="true" item="Transfer-Encoding header field" x:for-anchor=""/>
1562  <iref item="chunked (Coding Format)"/>
1563  <x:anchor-alias value="Transfer-Encoding"/>
1564<t>
1565   The Transfer-Encoding header field lists the transfer coding names
1566   corresponding to the sequence of transfer codings that have been
1567   (or will be) applied to the payload body in order to form the message body.
1568   Transfer codings are defined in <xref target="transfer.codings"/>.
1569</t>
1570<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Transfer-Encoding"/>
1571  <x:ref>Transfer-Encoding</x:ref> = 1#<x:ref>transfer-coding</x:ref>
1572</artwork></figure>
1573<t>
1574   Transfer-Encoding is analogous to the Content-Transfer-Encoding field of
1575   MIME, which was designed to enable safe transport of binary data over a
1576   7-bit transport service (<xref target="RFC2045" x:fmt="," x:sec="6"/>).
1577   However, safe transport has a different focus for an 8bit-clean transfer
1578   protocol. In HTTP's case, Transfer-Encoding is primarily intended to
1579   accurately delimit a dynamically generated payload and to distinguish
1580   payload encodings that are only applied for transport efficiency or
1581   security from those that are characteristics of the selected resource.
1582</t>
1583<t>
1584   A recipient &MUST; be able to parse the chunked transfer coding
1585   (<xref target="chunked.encoding"/>) because it plays a crucial role in
1586   framing messages when the payload body size is not known in advance.
1587   A sender &MUST-NOT; apply chunked more than once to a message body
1588   (i.e., chunking an already chunked message is not allowed).
1589   If any transfer coding other than chunked is applied to a request payload
1590   body, the sender &MUST; apply chunked as the final transfer coding to
1591   ensure that the message is properly framed.
1592   If any transfer coding other than chunked is applied to a response payload
1593   body, the sender &MUST; either apply chunked as the final transfer coding
1594   or terminate the message by closing the connection.
1595</t>
1596<figure><preamble>
1597   For example,
1598</preamble><artwork type="example">
1599  Transfer-Encoding: gzip, chunked
1600</artwork><postamble>
1601   indicates that the payload body has been compressed using the gzip
1602   coding and then chunked using the chunked coding while forming the
1603   message body.
1604</postamble></figure>
1605<t>
1606   Unlike <x:ref>Content-Encoding</x:ref> (&content-codings;),
1607   Transfer-Encoding is a property of the message, not of the representation, and
1608   any recipient along the request/response chain &MAY; decode the received
1609   transfer coding(s) or apply additional transfer coding(s) to the message
1610   body, assuming that corresponding changes are made to the Transfer-Encoding
1611   field-value. Additional information about the encoding parameters &MAY; be
1612   provided by other header fields not defined by this specification.
1613</t>
1614<t>
1615   Transfer-Encoding &MAY; be sent in a response to a HEAD request or in a
1616   <x:ref>304 (Not Modified)</x:ref> response (&status-304;) to a GET request,
1617   neither of which includes a message body,
1618   to indicate that the origin server would have applied a transfer coding
1619   to the message body if the request had been an unconditional GET.
1620   This indication is not required, however, because any recipient on
1621   the response chain (including the origin server) can remove transfer
1622   codings when they are not needed.
1623</t>
1624<t>
1625   A server &MUST-NOT; send a Transfer-Encoding header field in any response
1626   with a status code of
1627   <x:ref>1xx (Informational)</x:ref> or <x:ref>204 (No Content)</x:ref>.
1628   A server &MUST-NOT; send a Transfer-Encoding header field in any
1629   <x:ref>2xx (Successful)</x:ref> response to a CONNECT request (&CONNECT;).
1630</t>
1631<t>
1632   Transfer-Encoding was added in HTTP/1.1.  It is generally assumed that
1633   implementations advertising only HTTP/1.0 support will not understand
1634   how to process a transfer-encoded payload.
1635   A client &MUST-NOT; send a request containing Transfer-Encoding unless it
1636   knows the server will handle HTTP/1.1 (or later) requests; such knowledge
1637   might be in the form of specific user configuration or by remembering the
1638   version of a prior received response.
1639   A server &MUST-NOT; send a response containing Transfer-Encoding unless
1640   the corresponding request indicates HTTP/1.1 (or later).
1641</t>
1642<t>
1643   A server that receives a request message with a transfer coding it does
1644   not understand &SHOULD; respond with <x:ref>501 (Not Implemented)</x:ref>.
1645</t>
1646</section>
1647
1648<section title="Content-Length" anchor="header.content-length">
1649  <iref primary="true" item="Content-Length header field" x:for-anchor=""/>
1650  <x:anchor-alias value="Content-Length"/>
1651<t>
1652   When a message does not have a <x:ref>Transfer-Encoding</x:ref> header
1653   field, a Content-Length header field can provide the anticipated size,
1654   as a decimal number of octets, for a potential payload body.
1655   For messages that do include a payload body, the Content-Length field-value
1656   provides the framing information necessary for determining where the body
1657   (and message) ends.  For messages that do not include a payload body, the
1658   Content-Length indicates the size of the selected representation
1659   (&representation;).
1660</t>
1661<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/>
1662  <x:ref>Content-Length</x:ref> = 1*<x:ref>DIGIT</x:ref>
1663</artwork></figure>
1664<t>
1665   An example is
1666</t>
1667<figure><artwork type="example">
1668  Content-Length: 3495
1669</artwork></figure>
1670<t>
1671   A sender &MUST-NOT; send a Content-Length header field in any message that
1672   contains a <x:ref>Transfer-Encoding</x:ref> header field.
1673</t>
1674<t>
1675   A user agent &SHOULD; send a Content-Length in a request message when no
1676   <x:ref>Transfer-Encoding</x:ref> is sent and the request method defines
1677   a meaning for an enclosed payload body. For example, a Content-Length
1678   header field is normally sent in a POST request even when the value is
1679   0 (indicating an empty payload body).  A user agent &SHOULD-NOT; send a
1680   Content-Length header field when the request message does not contain a
1681   payload body and the method semantics do not anticipate such a body.
1682</t>
1683<t>
1684   A server &MAY; send a Content-Length header field in a response to a HEAD
1685   request (&HEAD;); a server &MUST-NOT; send Content-Length in such a
1686   response unless its field-value equals the decimal number of octets that
1687   would have been sent in the payload body of a response if the same
1688   request had used the GET method.
1689</t>
1690<t>
1691   A server &MAY; send a Content-Length header field in a
1692   <x:ref>304 (Not Modified)</x:ref> response to a conditional GET request
1693   (&status-304;); a server &MUST-NOT; send Content-Length in such a
1694   response unless its field-value equals the decimal number of octets that
1695   would have been sent in the payload body of a <x:ref>200 (OK)</x:ref>
1696   response to the same request.
1697</t>
1698<t>
1699   A server &MUST-NOT; send a Content-Length header field in any response
1700   with a status code of
1701   <x:ref>1xx (Informational)</x:ref> or <x:ref>204 (No Content)</x:ref>.
1702   A server &MUST-NOT; send a Content-Length header field in any
1703   <x:ref>2xx (Successful)</x:ref> response to a CONNECT request (&CONNECT;).
1704</t>
1705<t>
1706   Aside from the cases defined above, in the absence of Transfer-Encoding,
1707   an origin server &SHOULD; send a Content-Length header field when the
1708   payload body size is known prior to sending the complete header section.
1709   This will allow downstream recipients to measure transfer progress,
1710   know when a received message is complete, and potentially reuse the
1711   connection for additional requests.
1712</t>
1713<t>
1714   Any Content-Length field value greater than or equal to zero is valid.
1715   Since there is no predefined limit to the length of a payload, a
1716   recipient &MUST; anticipate potentially large decimal numerals and
1717   prevent parsing errors due to integer conversion overflows
1718   (<xref target="attack.protocol.element.size.overflows"/>).
1719</t>
1720<t>
1721   If a message is received that has multiple Content-Length header fields
1722   with field-values consisting of the same decimal value, or a single
1723   Content-Length header field with a field value containing a list of
1724   identical decimal values (e.g., "Content-Length: 42, 42"), indicating that
1725   duplicate Content-Length header fields have been generated or combined by an
1726   upstream message processor, then the recipient &MUST; either reject the
1727   message as invalid or replace the duplicated field-values with a single
1728   valid Content-Length field containing that decimal value prior to
1729   determining the message body length or forwarding the message.
1730</t>
1731<x:note>
1732  <t>
1733   &Note; HTTP's use of Content-Length for message framing differs
1734   significantly from the same field's use in MIME, where it is an optional
1735   field used only within the "message/external-body" media-type.
1736  </t>
1737</x:note>
1738</section>
1739
1740<section title="Message Body Length" anchor="message.body.length">
1741  <iref item="chunked (Coding Format)"/>
1742<t>
1743   The length of a message body is determined by one of the following
1744   (in order of precedence):
1745</t>
1746<t>
1747  <list style="numbers">
1748    <x:lt><t>
1749     Any response to a HEAD request and any response with a
1750     <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, or
1751     <x:ref>304 (Not Modified)</x:ref> status code is always
1752     terminated by the first empty line after the header fields, regardless of
1753     the header fields present in the message, and thus cannot contain a
1754     message body.
1755    </t></x:lt>
1756    <x:lt><t>
1757     Any <x:ref>2xx (Successful)</x:ref> response to a CONNECT request implies that the
1758     connection will become a tunnel immediately after the empty line that
1759     concludes the header fields.  A client &MUST; ignore any
1760     <x:ref>Content-Length</x:ref> or <x:ref>Transfer-Encoding</x:ref> header
1761     fields received in such a message.
1762    </t></x:lt>
1763    <x:lt><t>
1764     If a <x:ref>Transfer-Encoding</x:ref> header field is present
1765     and the chunked transfer coding (<xref target="chunked.encoding"/>)
1766     is the final encoding, the message body length is determined by reading
1767     and decoding the chunked data until the transfer coding indicates the
1768     data is complete.
1769    </t>
1770    <t>
1771     If a <x:ref>Transfer-Encoding</x:ref> header field is present in a
1772     response and the chunked transfer coding is not the final encoding, the
1773     message body length is determined by reading the connection until it is
1774     closed by the server.
1775     If a <x:ref>Transfer-Encoding</x:ref> header field is present in a request and the
1776     chunked transfer coding is not the final encoding, the message body
1777     length cannot be determined reliably; the server &MUST; respond with
1778     the <x:ref>400 (Bad Request)</x:ref> status code and then close the connection.
1779    </t>
1780    <t>
1781     If a message is received with both a <x:ref>Transfer-Encoding</x:ref>
1782     and a <x:ref>Content-Length</x:ref> header field, the Transfer-Encoding
1783     overrides the Content-Length. Such a message might indicate an attempt
1784     to perform request or response smuggling (bypass of security-related
1785     checks on message routing or content) and thus ought to be handled as
1786     an error.  A sender &MUST; remove the received Content-Length field
1787     prior to forwarding such a message downstream.
1788    </t></x:lt>
1789    <x:lt><t>
1790     If a message is received without <x:ref>Transfer-Encoding</x:ref> and with
1791     either multiple <x:ref>Content-Length</x:ref> header fields having
1792     differing field-values or a single Content-Length header field having an
1793     invalid value, then the message framing is invalid and
1794     the recipient &MUST; treat it as an unrecoverable error to prevent
1795     request or response smuggling.
1796     If this is a request message, the server &MUST; respond with
1797     a <x:ref>400 (Bad Request)</x:ref> status code and then close the connection.
1798     If this is a response message received by a proxy,
1799     the proxy &MUST; close the connection to the server, discard the received
1800     response, and send a <x:ref>502 (Bad Gateway)</x:ref> response to the
1801     client.
1802     If this is a response message received by a user agent,
1803     the user agent &MUST; close the connection to the server and discard the
1804     received response.
1805    </t></x:lt>
1806    <x:lt><t>
1807     If a valid <x:ref>Content-Length</x:ref> header field is present without
1808     <x:ref>Transfer-Encoding</x:ref>, its decimal value defines the
1809     expected message body length in octets.
1810     If the sender closes the connection or the recipient times out before the
1811     indicated number of octets are received, the recipient &MUST; consider
1812     the message to be incomplete and close the connection.
1813    </t></x:lt>
1814    <x:lt><t>
1815     If this is a request message and none of the above are true, then the
1816     message body length is zero (no message body is present).
1817    </t></x:lt>
1818    <x:lt><t>
1819     Otherwise, this is a response message without a declared message body
1820     length, so the message body length is determined by the number of octets
1821     received prior to the server closing the connection.
1822    </t></x:lt>
1823  </list>
1824</t>
1825<t>
1826   Since there is no way to distinguish a successfully completed,
1827   close-delimited message from a partially-received message interrupted
1828   by network failure, a server &SHOULD; generate encoding or
1829   length-delimited messages whenever possible.  The close-delimiting
1830   feature exists primarily for backwards compatibility with HTTP/1.0.
1831</t>
1832<t>
1833   A server &MAY; reject a request that contains a message body but
1834   not a <x:ref>Content-Length</x:ref> by responding with
1835   <x:ref>411 (Length Required)</x:ref>.
1836</t>
1837<t>
1838   Unless a transfer coding other than chunked has been applied,
1839   a client that sends a request containing a message body &SHOULD;
1840   use a valid <x:ref>Content-Length</x:ref> header field if the message body
1841   length is known in advance, rather than the chunked transfer coding, since some
1842   existing services respond to chunked with a <x:ref>411 (Length Required)</x:ref>
1843   status code even though they understand the chunked transfer coding.  This
1844   is typically because such services are implemented via a gateway that
1845   requires a content-length in advance of being called and the server
1846   is unable or unwilling to buffer the entire request before processing.
1847</t>
1848<t>
1849   A user agent that sends a request containing a message body &MUST; send a
1850   valid <x:ref>Content-Length</x:ref> header field if it does not know the
1851   server will handle HTTP/1.1 (or later) requests; such knowledge can be in
1852   the form of specific user configuration or by remembering the version of a
1853   prior received response.
1854</t>
1855<t>
1856   If the final response to the last request on a connection has been
1857   completely received and there remains additional data to read, a user agent
1858   &MAY; discard the remaining data or attempt to determine if that data
1859   belongs as part of the prior response body, which might be the case if the
1860   prior message's Content-Length value is incorrect. A client &MUST-NOT;
1861   process, cache, or forward such extra data as a separate response, since
1862   such behavior would be vulnerable to cache poisoning.
1863</t>
1864</section>
1865</section>
1866
1867<section anchor="incomplete.messages" title="Handling Incomplete Messages">
1868<t>
1869   A server that receives an incomplete request message, usually due to a
1870   canceled request or a triggered time-out exception, &MAY; send an error
1871   response prior to closing the connection.
1872</t>
1873<t>
1874   A client that receives an incomplete response message, which can occur
1875   when a connection is closed prematurely or when decoding a supposedly
1876   chunked transfer coding fails, &MUST; record the message as incomplete.
1877   Cache requirements for incomplete responses are defined in
1878   &cache-incomplete;.
1879</t>
1880<t>
1881   If a response terminates in the middle of the header section (before the
1882   empty line is received) and the status code might rely on header fields to
1883   convey the full meaning of the response, then the client cannot assume
1884   that meaning has been conveyed; the client might need to repeat the
1885   request in order to determine what action to take next.
1886</t>
1887<t>
1888   A message body that uses the chunked transfer coding is
1889   incomplete if the zero-sized chunk that terminates the encoding has not
1890   been received.  A message that uses a valid <x:ref>Content-Length</x:ref> is
1891   incomplete if the size of the message body received (in octets) is less than
1892   the value given by Content-Length.  A response that has neither chunked
1893   transfer coding nor Content-Length is terminated by closure of the
1894   connection, and thus is considered complete regardless of the number of
1895   message body octets received, provided that the header section was received
1896   intact.
1897</t>
1898</section>
1899
1900<section title="Message Parsing Robustness" anchor="message.robustness">
1901<t>
1902   Older HTTP/1.0 user agent implementations might send an extra CRLF
1903   after a POST request as a workaround for some early server
1904   applications that failed to read message body content that was
1905   not terminated by a line-ending. An HTTP/1.1 user agent &MUST-NOT;
1906   preface or follow a request with an extra CRLF.  If terminating
1907   the request message body with a line-ending is desired, then the
1908   user agent &MUST; count the terminating CRLF octets as part of the
1909   message body length.
1910</t>
1911<t>
1912   In the interest of robustness, a server that is expecting to receive and
1913   parse a request-line &SHOULD; ignore at least one empty line (CRLF)
1914   received prior to the request-line.
1915</t>
1916<t>
1917   Although the line terminator for the start-line and header
1918   fields is the sequence CRLF, a recipient &MAY; recognize a
1919   single LF as a line terminator and ignore any preceding CR.
1920</t>
1921<t>
1922   Although the request-line and status-line grammar rules require that each
1923   of the component elements be separated by a single SP octet, recipients
1924   &MAY; instead parse on whitespace-delimited word boundaries and, aside
1925   from the CRLF terminator, treat any form of whitespace as the SP separator
1926   while ignoring preceding or trailing whitespace;
1927   such whitespace includes one or more of the following octets:
1928   SP, HTAB, VT (%x0B), FF (%x0C), or bare CR.
1929</t>
1930<t>
1931   When a server listening only for HTTP request messages, or processing
1932   what appears from the start-line to be an HTTP request message,
1933   receives a sequence of octets that does not match the HTTP-message
1934   grammar aside from the robustness exceptions listed above, the
1935   server &SHOULD; respond with a <x:ref>400 (Bad Request)</x:ref> response. 
1936</t>
1937</section>
1938</section>
1939
1940<section title="Transfer Codings" anchor="transfer.codings">
1941  <x:anchor-alias value="transfer-coding"/>
1942  <x:anchor-alias value="transfer-extension"/>
1943<t>
1944   Transfer coding names are used to indicate an encoding
1945   transformation that has been, can be, or might need to be applied to a
1946   payload body in order to ensure "safe transport" through the network.
1947   This differs from a content coding in that the transfer coding is a
1948   property of the message rather than a property of the representation
1949   that is being transferred.
1950</t>
1951<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-coding"/><iref primary="true" item="Grammar" subitem="transfer-extension"/>
1952  <x:ref>transfer-coding</x:ref>    = "chunked" ; <xref target="chunked.encoding"/>
1953                     / "compress" ; <xref target="compress.coding"/>
1954                     / "deflate" ; <xref target="deflate.coding"/>
1955                     / "gzip" ; <xref target="gzip.coding"/>
1956                     / <x:ref>transfer-extension</x:ref>
1957  <x:ref>transfer-extension</x:ref> = <x:ref>token</x:ref> *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>transfer-parameter</x:ref> )
1958</artwork></figure>
1959<t anchor="rule.parameter">
1960  <x:anchor-alias value="transfer-parameter"/>
1961   Parameters are in the form of a name or name=value pair.
1962</t>
1963<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-parameter"/>
1964  <x:ref>transfer-parameter</x:ref> = <x:ref>token</x:ref> <x:ref>BWS</x:ref> "=" <x:ref>BWS</x:ref> ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> )
1965</artwork></figure>
1966<t>
1967   All transfer-coding names are case-insensitive and ought to be registered
1968   within the HTTP Transfer Coding registry, as defined in
1969   <xref target="transfer.coding.registry"/>.
1970   They are used in the <x:ref>TE</x:ref> (<xref target="header.te"/>) and
1971   <x:ref>Transfer-Encoding</x:ref> (<xref target="header.transfer-encoding"/>)
1972   header fields.
1973</t>
1974
1975<section title="Chunked Transfer Coding" anchor="chunked.encoding">
1976  <iref primary="true" item="chunked (Coding Format)"/>
1977  <x:anchor-alias value="chunk"/>
1978  <x:anchor-alias value="chunked-body"/>
1979  <x:anchor-alias value="chunk-data"/>
1980  <x:anchor-alias value="chunk-size"/>
1981  <x:anchor-alias value="last-chunk"/>
1982<t>
1983   The chunked transfer coding wraps the payload body in order to transfer it
1984   as a series of chunks, each with its own size indicator, followed by an
1985   &OPTIONAL; trailer containing header fields. Chunked enables content
1986   streams of unknown size to be transferred as a sequence of length-delimited
1987   buffers, which enables the sender to retain connection persistence and the
1988   recipient to know when it has received the entire message.
1989</t>
1990<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="chunked-body"><!--terminal production--></iref><iref primary="true" item="Grammar" subitem="chunk"/><iref primary="true" item="Grammar" subitem="chunk-size"/><iref primary="true" item="Grammar" subitem="last-chunk"/><iref primary="true" item="Grammar" subitem="chunk-ext"/><iref primary="true" item="Grammar" subitem="chunk-ext-name"/><iref primary="true" item="Grammar" subitem="chunk-ext-val"/><iref primary="true" item="Grammar" subitem="chunk-data"/><iref primary="false" item="Grammar" subitem="trailer-part"/>
1991  <x:ref>chunked-body</x:ref>   = *<x:ref>chunk</x:ref>
1992                   <x:ref>last-chunk</x:ref>
1993                   <x:ref>trailer-part</x:ref>
1994                   <x:ref>CRLF</x:ref>
1995 
1996  <x:ref>chunk</x:ref>          = <x:ref>chunk-size</x:ref> [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
1997                   <x:ref>chunk-data</x:ref> <x:ref>CRLF</x:ref>
1998  <x:ref>chunk-size</x:ref>     = 1*<x:ref>HEXDIG</x:ref>
1999  <x:ref>last-chunk</x:ref>     = 1*("0") [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
2000 
2001  <x:ref>chunk-data</x:ref>     = 1*<x:ref>OCTET</x:ref> ; a sequence of chunk-size octets
2002</artwork></figure>
2003<t>
2004   The chunk-size field is a string of hex digits indicating the size of
2005   the chunk-data in octets. The chunked transfer coding is complete when a
2006   chunk with a chunk-size of zero is received, possibly followed by a
2007   trailer, and finally terminated by an empty line.
2008</t>
2009<t>
2010   A recipient &MUST; be able to parse and decode the chunked transfer coding.
2011</t>
2012
2013<section title="Chunk Extensions" anchor="chunked.extension">
2014  <x:anchor-alias value="chunk-ext"/>
2015  <x:anchor-alias value="chunk-ext-name"/>
2016  <x:anchor-alias value="chunk-ext-val"/>
2017<t>
2018   The chunked encoding allows each chunk to include zero or more chunk
2019   extensions, immediately following the <x:ref>chunk-size</x:ref>, for the
2020   sake of supplying per-chunk metadata (such as a signature or hash),
2021   mid-message control information, or randomization of message body size.
2022</t>
2023<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="chunked-body"><!--terminal production--></iref><iref primary="true" item="Grammar" subitem="chunk"/><iref primary="true" item="Grammar" subitem="chunk-size"/><iref primary="true" item="Grammar" subitem="last-chunk"/><iref primary="true" item="Grammar" subitem="chunk-ext"/><iref primary="true" item="Grammar" subitem="chunk-ext-name"/><iref primary="true" item="Grammar" subitem="chunk-ext-val"/><iref primary="true" item="Grammar" subitem="chunk-data"/><iref primary="false" item="Grammar" subitem="trailer-part"/><iref primary="true" item="Grammar" subitem="quoted-str-nf"/><iref primary="true" item="Grammar" subitem="qdtext-nf"/>
2024  <x:ref>chunk-ext</x:ref>      = *( ";" <x:ref>chunk-ext-name</x:ref> [ "=" <x:ref>chunk-ext-val</x:ref> ] )
2025
2026  <x:ref>chunk-ext-name</x:ref> = <x:ref>token</x:ref>
2027  <x:ref>chunk-ext-val</x:ref>  = <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref>
2028</artwork></figure>
2029<t>
2030   The chunked encoding is specific to each connection and is likely to be
2031   removed or recoded by each recipient (including intermediaries) before any
2032   higher-level application would have a chance to inspect the extensions.
2033   Hence, use of chunk extensions is generally limited to specialized HTTP
2034   services such as "long polling" (where client and server can have shared
2035   expectations regarding the use of chunk extensions) or for padding within
2036   an end-to-end secured connection.
2037</t>
2038<t>
2039   A recipient &MUST; ignore unrecognized chunk extensions.
2040   A server ought to limit the total length of chunk extensions received in a
2041   request to an amount reasonable for the services provided, in the same way
2042   that it applies length limitations and timeouts for other parts of a
2043   message, and generate an appropriate <x:ref>4xx (Client Error)</x:ref>
2044   response if that amount is exceeded.
2045</t>
2046</section>
2047
2048<section title="Chunked Trailer Part" anchor="chunked.trailer.part">
2049  <x:anchor-alias value="trailer-part"/>
2050<t>
2051   A trailer allows the sender to include additional fields at the end of a
2052   chunked message in order to supply metadata that might be dynamically
2053   generated while the message body is sent, such as a message integrity
2054   check, digital signature, or post-processing status. The trailer fields are
2055   identical to header fields, except they are sent in a chunked trailer
2056   instead of the message's header section.
2057</t>
2058<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="trailer-part"/>
2059  <x:ref>trailer-part</x:ref>   = *( <x:ref>header-field</x:ref> <x:ref>CRLF</x:ref> )
2060</artwork></figure>
2061<t>
2062   A sender &MUST-NOT; generate a trailer that contains a field which needs to
2063   be known by the recipient before it can begin processing the message body.
2064   For example, most recipients need to know the values of
2065   <x:ref>Content-Encoding</x:ref> and <x:ref>Content-Type</x:ref> in order to
2066   select a content handler, so placing those fields in a trailer would force
2067   the recipient to buffer the entire body before it could begin, greatly
2068   increasing user-perceived latency and defeating one of the main advantages
2069   of using chunked to send data streams of unknown length.
2070   A sender &MUST-NOT; generate a trailer containing a
2071   <x:ref>Transfer-Encoding</x:ref>,
2072   <x:ref>Content-Length</x:ref>, or
2073   <x:ref>Trailer</x:ref> field.
2074</t>
2075<t>
2076   A server &MUST; generate an empty trailer with the chunked transfer coding
2077   unless at least one of the following is true:
2078  <list style="numbers">
2079    <t>the request included a <x:ref>TE</x:ref> header field that indicates
2080    "trailers" is acceptable in the transfer coding of the response, as
2081    described in <xref target="header.te"/>; or,</t>
2082     
2083    <t>the trailer fields consist entirely of optional metadata and the
2084    recipient could use the message (in a manner acceptable to the generating
2085    server) without receiving that metadata. In other words, the generating
2086    server is willing to accept the possibility that the trailer fields might
2087    be silently discarded along the path to the client.</t>
2088  </list>
2089</t>
2090<t>
2091   The above requirement prevents the need for an infinite buffer when a
2092   message is being received by an HTTP/1.1 (or later) proxy and forwarded to
2093   an HTTP/1.0 recipient.
2094</t>
2095</section>
2096
2097<section title="Decoding Chunked" anchor="decoding.chunked">
2098<t>
2099   A process for decoding the chunked transfer coding
2100   can be represented in pseudo-code as:
2101</t>
2102<figure><artwork type="code">
2103  length := 0
2104  read chunk-size, chunk-ext (if any), and CRLF
2105  while (chunk-size &gt; 0) {
2106     read chunk-data and CRLF
2107     append chunk-data to decoded-body
2108     length := length + chunk-size
2109     read chunk-size, chunk-ext (if any), and CRLF
2110  }
2111  read header-field
2112  while (header-field not empty) {
2113     append header-field to existing header fields
2114     read header-field
2115  }
2116  Content-Length := length
2117  Remove "chunked" from Transfer-Encoding
2118  Remove Trailer from existing header fields
2119</artwork></figure>
2120</section>
2121</section>
2122
2123<section title="Compression Codings" anchor="compression.codings">
2124<t>
2125   The codings defined below can be used to compress the payload of a
2126   message.
2127</t>
2128
2129<section title="Compress Coding" anchor="compress.coding">
2130<iref item="compress (Coding Format)"/>
2131<t>
2132   The "compress" coding is an adaptive Lempel-Ziv-Welch (LZW) coding
2133   <xref target="Welch"/> that is commonly produced by the UNIX file
2134   compression program "compress".
2135   A recipient &SHOULD; consider "x-compress" to be equivalent to "compress".
2136</t>
2137</section>
2138
2139<section title="Deflate Coding" anchor="deflate.coding">
2140<iref item="deflate (Coding Format)"/>
2141<t>
2142   The "deflate" coding is a "zlib" data format <xref target="RFC1950"/>
2143   containing a "deflate" compressed data stream <xref target="RFC1951"/>
2144   that uses a combination of the Lempel-Ziv (LZ77) compression algorithm and
2145   Huffman coding.
2146</t>
2147<x:note>
2148  <t>
2149    &Note; Some incorrect implementations send the "deflate"
2150    compressed data without the zlib wrapper.
2151   </t>
2152</x:note>
2153</section>
2154
2155<section title="Gzip Coding" anchor="gzip.coding">
2156<iref item="gzip (Coding Format)"/>
2157<t>
2158   The "gzip" coding is an LZ77 coding with a 32 bit CRC that is commonly
2159   produced by the gzip file compression program <xref target="RFC1952"/>.
2160   A recipient &SHOULD; consider "x-gzip" to be equivalent to "gzip".
2161</t>
2162</section>
2163
2164</section>
2165
2166<section title="TE" anchor="header.te">
2167  <iref primary="true" item="TE header field" x:for-anchor=""/>
2168  <x:anchor-alias value="TE"/>
2169  <x:anchor-alias value="t-codings"/>
2170  <x:anchor-alias value="t-ranking"/>
2171  <x:anchor-alias value="rank"/>
2172<t>
2173   The "TE" header field in a request indicates what transfer codings,
2174   besides chunked, the client is willing to accept in response, and
2175   whether or not the client is willing to accept trailer fields in a
2176   chunked transfer coding.
2177</t>
2178<t>
2179   The TE field-value consists of a comma-separated list of transfer coding
2180   names, each allowing for optional parameters (as described in
2181   <xref target="transfer.codings"/>), and/or the keyword "trailers".
2182   A client &MUST-NOT; send the chunked transfer coding name in TE;
2183   chunked is always acceptable for HTTP/1.1 recipients.
2184</t>
2185<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TE"/><iref primary="true" item="Grammar" subitem="t-codings"/><iref primary="true" item="Grammar" subitem="t-ranking"/><iref primary="true" item="Grammar" subitem="rank"/>
2186  <x:ref>TE</x:ref>        = #<x:ref>t-codings</x:ref>
2187  <x:ref>t-codings</x:ref> = "trailers" / ( <x:ref>transfer-coding</x:ref> [ <x:ref>t-ranking</x:ref> ] )
2188  <x:ref>t-ranking</x:ref> = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>rank</x:ref>
2189  <x:ref>rank</x:ref>      = ( "0" [ "." 0*3<x:ref>DIGIT</x:ref> ] )
2190             / ( "1" [ "." 0*3("0") ] )
2191</artwork></figure>
2192<t>
2193   Three examples of TE use are below.
2194</t>
2195<figure><artwork type="example">
2196  TE: deflate
2197  TE:
2198  TE: trailers, deflate;q=0.5
2199</artwork></figure>
2200<t>
2201   The presence of the keyword "trailers" indicates that the client is willing
2202   to accept trailer fields in a chunked transfer coding, as defined in
2203   <xref target="chunked.trailer.part"/>, on behalf of itself and any downstream
2204   clients. For requests from an intermediary, this implies that either:
2205   (a) all downstream clients are willing to accept trailer fields in the
2206   forwarded response; or,
2207   (b) the intermediary will attempt to buffer the response on behalf of
2208   downstream recipients.
2209   Note that HTTP/1.1 does not define any means to limit the size of a
2210   chunked response such that an intermediary can be assured of buffering the
2211   entire response.
2212</t>
2213<t>
2214   When multiple transfer codings are acceptable, the client &MAY; rank the
2215   codings by preference using a case-insensitive "q" parameter (similar to
2216   the qvalues used in content negotiation fields, &qvalue;). The rank value
2217   is a real number in the range 0 through 1, where 0.001 is the least
2218   preferred and 1 is the most preferred; a value of 0 means "not acceptable".
2219</t>
2220<t>
2221   If the TE field-value is empty or if no TE field is present, the only
2222   acceptable transfer coding is chunked. A message with no transfer coding
2223   is always acceptable.
2224</t>
2225<t>
2226   Since the TE header field only applies to the immediate connection,
2227   a sender of TE &MUST; also send a "TE" connection option within the
2228   <x:ref>Connection</x:ref> header field (<xref target="header.connection"/>)
2229   in order to prevent the TE field from being forwarded by intermediaries
2230   that do not support its semantics.
2231</t>
2232</section>
2233
2234<section title="Trailer" anchor="header.trailer">
2235  <iref primary="true" item="Trailer header field" x:for-anchor=""/>
2236  <x:anchor-alias value="Trailer"/>
2237<t>
2238   When a message includes a message body encoded with the chunked
2239   transfer coding and the sender desires to send metadata in the form of
2240   trailer fields at the end of the message, the sender &SHOULD; generate a
2241   <x:ref>Trailer</x:ref> header field before the message body to indicate
2242   which fields will be present in the trailers. This allows the recipient
2243   to prepare for receipt of that metadata before it starts processing the body,
2244   which is useful if the message is being streamed and the recipient wishes
2245   to confirm an integrity check on the fly.
2246</t>
2247<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Trailer"/>
2248  <x:ref>Trailer</x:ref> = 1#<x:ref>field-name</x:ref>
2249</artwork></figure>
2250</section>
2251</section>
2252
2253<section title="Message Routing" anchor="message.routing">
2254<t>
2255   HTTP request message routing is determined by each client based on the
2256   target resource, the client's proxy configuration, and
2257   establishment or reuse of an inbound connection.  The corresponding
2258   response routing follows the same connection chain back to the client.
2259</t>
2260
2261<section title="Identifying a Target Resource" anchor="target-resource">
2262  <iref primary="true" item="target resource"/>
2263  <iref primary="true" item="target URI"/>
2264  <x:anchor-alias value="target resource"/>
2265  <x:anchor-alias value="target URI"/>
2266<t>
2267   HTTP is used in a wide variety of applications, ranging from
2268   general-purpose computers to home appliances.  In some cases,
2269   communication options are hard-coded in a client's configuration.
2270   However, most HTTP clients rely on the same resource identification
2271   mechanism and configuration techniques as general-purpose Web browsers.
2272</t>
2273<t>
2274   HTTP communication is initiated by a user agent for some purpose.
2275   The purpose is a combination of request semantics, which are defined in
2276   <xref target="Part2"/>, and a target resource upon which to apply those
2277   semantics.  A URI reference (<xref target="uri"/>) is typically used as
2278   an identifier for the "<x:dfn>target resource</x:dfn>", which a user agent
2279   would resolve to its absolute form in order to obtain the
2280   "<x:dfn>target URI</x:dfn>".  The target URI
2281   excludes the reference's fragment component, if any,
2282   since fragment identifiers are reserved for client-side processing
2283   (<xref target="RFC3986" x:fmt="," x:sec="3.5"/>).
2284</t>
2285</section>
2286
2287<section title="Connecting Inbound" anchor="connecting.inbound">
2288<t>
2289   Once the target URI is determined, a client needs to decide whether
2290   a network request is necessary to accomplish the desired semantics and,
2291   if so, where that request is to be directed.
2292</t>
2293<t>
2294   If the client has a cache <xref target="Part6"/> and the request can be
2295   satisfied by it, then the request is
2296   usually directed there first.
2297</t>
2298<t>
2299   If the request is not satisfied by a cache, then a typical client will
2300   check its configuration to determine whether a proxy is to be used to
2301   satisfy the request.  Proxy configuration is implementation-dependent,
2302   but is often based on URI prefix matching, selective authority matching,
2303   or both, and the proxy itself is usually identified by an "http" or
2304   "https" URI.  If a proxy is applicable, the client connects inbound by
2305   establishing (or reusing) a connection to that proxy.
2306</t>
2307<t>
2308   If no proxy is applicable, a typical client will invoke a handler routine,
2309   usually specific to the target URI's scheme, to connect directly
2310   to an authority for the target resource.  How that is accomplished is
2311   dependent on the target URI scheme and defined by its associated
2312   specification, similar to how this specification defines origin server
2313   access for resolution of the "http" (<xref target="http.uri"/>) and
2314   "https" (<xref target="https.uri"/>) schemes.
2315</t>
2316<t>
2317   HTTP requirements regarding connection management are defined in
2318   <xref target="connection.management"/>.
2319</t>
2320</section>
2321
2322<section title="Request Target" anchor="request-target">
2323<t>
2324   Once an inbound connection is obtained,
2325   the client sends an HTTP request message (<xref target="http.message"/>)
2326   with a request-target derived from the target URI.
2327   There are four distinct formats for the request-target, depending on both
2328   the method being requested and whether the request is to a proxy.
2329</t>   
2330<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-target"/><iref primary="true" item="Grammar" subitem="origin-form"/><iref primary="true" item="Grammar" subitem="absolute-form"/><iref primary="true" item="Grammar" subitem="authority-form"/><iref primary="true" item="Grammar" subitem="asterisk-form"/>
2331  <x:ref>request-target</x:ref> = <x:ref>origin-form</x:ref>
2332                 / <x:ref>absolute-form</x:ref>
2333                 / <x:ref>authority-form</x:ref>
2334                 / <x:ref>asterisk-form</x:ref>
2335
2336  <x:ref>origin-form</x:ref>    = <x:ref>absolute-path</x:ref> [ "?" <x:ref>query</x:ref> ]
2337  <x:ref>absolute-form</x:ref>  = <x:ref>absolute-URI</x:ref>
2338  <x:ref>authority-form</x:ref> = <x:ref>authority</x:ref>
2339  <x:ref>asterisk-form</x:ref>  = "*"
2340</artwork></figure>
2341<t anchor="origin-form"><iref item="origin-form (of request-target)"/>
2342  <x:h>origin-form</x:h>
2343</t>
2344<t>
2345   The most common form of request-target is the <x:dfn>origin-form</x:dfn>.
2346   When making a request directly to an origin server, other than a CONNECT
2347   or server-wide OPTIONS request (as detailed below),
2348   a client &MUST; send only the absolute path and query components of
2349   the target URI as the request-target.
2350   If the target URI's path component is empty, then the client &MUST; send
2351   "/" as the path within the origin-form of request-target.
2352   A <x:ref>Host</x:ref> header field is also sent, as defined in
2353   <xref target="header.host"/>.
2354</t>
2355<t>
2356   For example, a client wishing to retrieve a representation of the resource
2357   identified as
2358</t>
2359<figure><artwork x:indent-with="  " type="example">
2360http://www.example.org/where?q=now
2361</artwork></figure>
2362<t>
2363   directly from the origin server would open (or reuse) a TCP connection
2364   to port 80 of the host "www.example.org" and send the lines:
2365</t>
2366<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2367GET /where?q=now HTTP/1.1
2368Host: www.example.org
2369</artwork></figure>
2370<t>
2371   followed by the remainder of the request message.
2372</t>
2373<t anchor="absolute-form"><iref item="absolute-form (of request-target)"/>
2374  <x:h>absolute-form</x:h>
2375</t>
2376<t>
2377   When making a request to a proxy, other than a CONNECT or server-wide
2378   OPTIONS request (as detailed below), a client &MUST; send the target URI
2379   in <x:dfn>absolute-form</x:dfn> as the request-target.
2380   The proxy is requested to either service that request from a valid cache,
2381   if possible, or make the same request on the client's behalf to either
2382   the next inbound proxy server or directly to the origin server indicated
2383   by the request-target.  Requirements on such "forwarding" of messages are
2384   defined in <xref target="message.forwarding"/>.
2385</t>
2386<t>
2387   An example absolute-form of request-line would be:
2388</t>
2389<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2390GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
2391</artwork></figure>
2392<t>
2393   To allow for transition to the absolute-form for all requests in some
2394   future version of HTTP, a server &MUST; accept the absolute-form
2395   in requests, even though HTTP/1.1 clients will only send them in requests
2396   to proxies.
2397</t>
2398<t anchor="authority-form"><iref item="authority-form (of request-target)"/>
2399  <x:h>authority-form</x:h>
2400</t>
2401<t>
2402   The <x:dfn>authority-form</x:dfn> of request-target is only used for
2403   CONNECT requests (&CONNECT;). When making a CONNECT request to establish a
2404   tunnel through one or more proxies, a client &MUST; send only the target
2405   URI's authority component (excluding any userinfo and its "@" delimiter) as
2406   the request-target. For example,
2407</t>
2408<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2409CONNECT www.example.com:80 HTTP/1.1
2410</artwork></figure>
2411<t anchor="asterisk-form"><iref item="asterisk-form (of request-target)"/>
2412  <x:h>asterisk-form</x:h>
2413</t>
2414<t>
2415   The <x:dfn>asterisk-form</x:dfn> of request-target is only used for a server-wide
2416   OPTIONS request (&OPTIONS;).  When a client wishes to request OPTIONS
2417   for the server as a whole, as opposed to a specific named resource of
2418   that server, the client &MUST; send only "*" (%x2A) as the request-target.
2419   For example,
2420</t>
2421<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2422OPTIONS * HTTP/1.1
2423</artwork></figure>
2424<t>
2425   If a proxy receives an OPTIONS request with an absolute-form of
2426   request-target in which the URI has an empty path and no query component,
2427   then the last proxy on the request chain &MUST; send a request-target
2428   of "*" when it forwards the request to the indicated origin server.
2429</t>
2430<figure><preamble>  
2431   For example, the request
2432</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2433OPTIONS http://www.example.org:8001 HTTP/1.1
2434</artwork></figure>
2435<figure><preamble>  
2436  would be forwarded by the final proxy as
2437</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2438OPTIONS * HTTP/1.1
2439Host: www.example.org:8001
2440</artwork>
2441<postamble>
2442   after connecting to port 8001 of host "www.example.org".
2443</postamble>
2444</figure>
2445</section>
2446
2447<section title="Host" anchor="header.host">
2448  <iref primary="true" item="Host header field" x:for-anchor=""/>
2449  <x:anchor-alias value="Host"/>
2450<t>
2451   The "Host" header field in a request provides the host and port
2452   information from the target URI, enabling the origin
2453   server to distinguish among resources while servicing requests
2454   for multiple host names on a single IP address.
2455</t>
2456<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Host"/>
2457  <x:ref>Host</x:ref> = <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ; <xref target="http.uri"/>
2458</artwork></figure>
2459<t>
2460   A client &MUST; send a Host header field in all HTTP/1.1 request messages.
2461   If the target URI includes an authority component, then a client &MUST;
2462   send a field-value for Host that is identical to that authority
2463   component, excluding any userinfo subcomponent and its "@" delimiter
2464   (<xref target="http.uri"/>).
2465   If the authority component is missing or undefined for the target URI,
2466   then a client &MUST; send a Host header field with an empty field-value.
2467</t>
2468<t>
2469   Since the Host field-value is critical information for handling a request,
2470   a user agent &SHOULD; generate Host as the first header field following the
2471   request-line.
2472</t>
2473<t>
2474   For example, a GET request to the origin server for
2475   &lt;http://www.example.org/pub/WWW/&gt; would begin with:
2476</t>
2477<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2478GET /pub/WWW/ HTTP/1.1
2479Host: www.example.org
2480</artwork></figure>
2481<t>
2482   A client &MUST; send a Host header field in an HTTP/1.1 request even
2483   if the request-target is in the absolute-form, since this
2484   allows the Host information to be forwarded through ancient HTTP/1.0
2485   proxies that might not have implemented Host.
2486</t>
2487<t>
2488   When a proxy receives a request with an absolute-form of
2489   request-target, the proxy &MUST; ignore the received
2490   Host header field (if any) and instead replace it with the host
2491   information of the request-target.  A proxy that forwards such a request
2492   &MUST; generate a new Host field-value based on the received
2493   request-target rather than forward the received Host field-value.
2494</t>
2495<t>
2496   Since the Host header field acts as an application-level routing
2497   mechanism, it is a frequent target for malware seeking to poison
2498   a shared cache or redirect a request to an unintended server.
2499   An interception proxy is particularly vulnerable if it relies on
2500   the Host field-value for redirecting requests to internal
2501   servers, or for use as a cache key in a shared cache, without
2502   first verifying that the intercepted connection is targeting a
2503   valid IP address for that host.
2504</t>
2505<t>
2506   A server &MUST; respond with a <x:ref>400 (Bad Request)</x:ref> status code
2507   to any HTTP/1.1 request message that lacks a Host header field and
2508   to any request message that contains more than one Host header field
2509   or a Host header field with an invalid field-value.
2510</t>
2511</section>
2512
2513<section title="Effective Request URI" anchor="effective.request.uri">
2514  <iref primary="true" item="effective request URI"/>
2515  <x:anchor-alias value="effective request URI"/>
2516<t>
2517   A server that receives an HTTP request message &MUST; reconstruct
2518   the user agent's original target URI, based on the pieces of information
2519   learned from the request-target, <x:ref>Host</x:ref> header field, and
2520   connection context, in order to identify the intended target resource and
2521   properly service the request. The URI derived from this reconstruction
2522   process is referred to as the "<x:dfn>effective request URI</x:dfn>".
2523</t>
2524<t>
2525   For a user agent, the effective request URI is the target URI.
2526</t>
2527<t>
2528   If the request-target is in absolute-form, then the effective request URI
2529   is the same as the request-target.  Otherwise, the effective request URI
2530   is constructed as follows.
2531</t>
2532<t>
2533   If the request is received over a TLS-secured TCP connection,
2534   then the effective request URI's scheme is "https"; otherwise, the
2535   scheme is "http".
2536</t>
2537<t>
2538   If the request-target is in authority-form, then the effective
2539   request URI's authority component is the same as the request-target.
2540   Otherwise, if a <x:ref>Host</x:ref> header field is supplied with a
2541   non-empty field-value, then the authority component is the same as the
2542   Host field-value. Otherwise, the authority component is the concatenation of
2543   the default host name configured for the server, a colon (":"), and the
2544   connection's incoming TCP port number in decimal form.
2545</t>
2546<t>
2547   If the request-target is in authority-form or asterisk-form, then the
2548   effective request URI's combined path and query component is empty.
2549   Otherwise, the combined path and query component is the same as the
2550   request-target.
2551</t>
2552<t>
2553   The components of the effective request URI, once determined as above,
2554   can be combined into absolute-URI form by concatenating the scheme,
2555   "://", authority, and combined path and query component.
2556</t>
2557<figure>
2558<preamble>
2559   Example 1: the following message received over an insecure TCP connection
2560</preamble>
2561<artwork type="example" x:indent-with="  ">
2562GET /pub/WWW/TheProject.html HTTP/1.1
2563Host: www.example.org:8080
2564</artwork>
2565</figure>
2566<figure>
2567<preamble>
2568  has an effective request URI of
2569</preamble>
2570<artwork type="example" x:indent-with="  ">
2571http://www.example.org:8080/pub/WWW/TheProject.html
2572</artwork>
2573</figure>
2574<figure>
2575<preamble>
2576   Example 2: the following message received over a TLS-secured TCP connection
2577</preamble>
2578<artwork type="example" x:indent-with="  ">
2579OPTIONS * HTTP/1.1
2580Host: www.example.org
2581</artwork>
2582</figure>
2583<figure>
2584<preamble>
2585  has an effective request URI of
2586</preamble>
2587<artwork type="example" x:indent-with="  ">
2588https://www.example.org
2589</artwork>
2590</figure>
2591<t>
2592   An origin server that does not allow resources to differ by requested
2593   host &MAY; ignore the <x:ref>Host</x:ref> field-value and instead replace it
2594   with a configured server name when constructing the effective request URI.
2595</t>
2596<t>
2597   Recipients of an HTTP/1.0 request that lacks a <x:ref>Host</x:ref> header
2598   field &MAY; attempt to use heuristics (e.g., examination of the URI path for
2599   something unique to a particular host) in order to guess the
2600   effective request URI's authority component.
2601</t>
2602</section>
2603
2604<section title="Associating a Response to a Request" anchor="associating.response.to.request">
2605<t>
2606   HTTP does not include a request identifier for associating a given
2607   request message with its corresponding one or more response messages.
2608   Hence, it relies on the order of response arrival to correspond exactly
2609   to the order in which requests are made on the same connection.
2610   More than one response message per request only occurs when one or more
2611   informational responses (<x:ref>1xx</x:ref>, see &status-1xx;) precede a
2612   final response to the same request.
2613</t>
2614<t>
2615   A client that has more than one outstanding request on a connection &MUST;
2616   maintain a list of outstanding requests in the order sent and &MUST;
2617   associate each received response message on that connection to the highest
2618   ordered request that has not yet received a final (non-<x:ref>1xx</x:ref>)
2619   response.
2620</t>
2621</section>
2622
2623<section title="Message Forwarding" anchor="message.forwarding">
2624<t>
2625   As described in <xref target="intermediaries"/>, intermediaries can serve
2626   a variety of roles in the processing of HTTP requests and responses.
2627   Some intermediaries are used to improve performance or availability.
2628   Others are used for access control or to filter content.
2629   Since an HTTP stream has characteristics similar to a pipe-and-filter
2630   architecture, there are no inherent limits to the extent an intermediary
2631   can enhance (or interfere) with either direction of the stream.
2632</t>
2633<t>
2634   An intermediary not acting as a tunnel &MUST; implement the
2635   <x:ref>Connection</x:ref> header field, as specified in
2636   <xref target="header.connection"/>, and exclude fields from being forwarded
2637   that are only intended for the incoming connection.
2638</t>
2639<t>
2640   An intermediary &MUST-NOT; forward a message to itself unless it is
2641   protected from an infinite request loop. In general, an intermediary ought
2642   to recognize its own server names, including any aliases, local variations,
2643   or literal IP addresses, and respond to such requests directly.
2644</t>
2645
2646<section title="Via" anchor="header.via">
2647  <iref primary="true" item="Via header field" x:for-anchor=""/>
2648  <x:anchor-alias value="pseudonym"/>
2649  <x:anchor-alias value="received-by"/>
2650  <x:anchor-alias value="received-protocol"/>
2651  <x:anchor-alias value="Via"/>
2652<t>
2653   The "Via" header field indicates the presence of intermediate protocols and
2654   recipients between the user agent and the server (on requests) or between
2655   the origin server and the client (on responses), similar to the
2656   "Received" header field in email
2657   (<xref target="RFC5322" x:fmt="of" x:sec="3.6.7"/>).
2658   Via can be used for tracking message forwards,
2659   avoiding request loops, and identifying the protocol capabilities of
2660   senders along the request/response chain.
2661</t>
2662<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Via"/><iref primary="true" item="Grammar" subitem="received-protocol"/><iref primary="true" item="Grammar" subitem="protocol-name"/><iref primary="true" item="Grammar" subitem="protocol-version"/><iref primary="true" item="Grammar" subitem="received-by"/><iref primary="true" item="Grammar" subitem="pseudonym"/>
2663  <x:ref>Via</x:ref> = 1#( <x:ref>received-protocol</x:ref> <x:ref>RWS</x:ref> <x:ref>received-by</x:ref> [ <x:ref>RWS</x:ref> <x:ref>comment</x:ref> ] )
2664
2665  <x:ref>received-protocol</x:ref> = [ <x:ref>protocol-name</x:ref> "/" ] <x:ref>protocol-version</x:ref>
2666                      ; see <xref target="header.upgrade"/>
2667  <x:ref>received-by</x:ref>       = ( <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ) / <x:ref>pseudonym</x:ref>
2668  <x:ref>pseudonym</x:ref>         = <x:ref>token</x:ref>
2669</artwork></figure>
2670<t>
2671   Multiple Via field values represent each proxy or gateway that has
2672   forwarded the message. Each intermediary appends its own information
2673   about how the message was received, such that the end result is ordered
2674   according to the sequence of forwarding recipients.
2675</t>
2676<t>
2677   A proxy &MUST; send an appropriate Via header field, as described below, in
2678   each message that it forwards.
2679   An HTTP-to-HTTP gateway &MUST; send an appropriate Via header field in
2680   each inbound request message and &MAY; send a Via header field in
2681   forwarded response messages.
2682</t>
2683<t>
2684   For each intermediary, the received-protocol indicates the protocol and
2685   protocol version used by the upstream sender of the message. Hence, the
2686   Via field value records the advertised protocol capabilities of the
2687   request/response chain such that they remain visible to downstream
2688   recipients; this can be useful for determining what backwards-incompatible
2689   features might be safe to use in response, or within a later request, as
2690   described in <xref target="http.version"/>. For brevity, the protocol-name
2691   is omitted when the received protocol is HTTP.
2692</t>
2693<t>
2694   The received-by field is normally the host and optional port number of a
2695   recipient server or client that subsequently forwarded the message.
2696   However, if the real host is considered to be sensitive information, a
2697   sender &MAY; replace it with a pseudonym. If a port is not provided,
2698   a recipient &MAY; interpret that as meaning it was received on the default
2699   TCP port, if any, for the received-protocol.
2700</t>
2701<t>
2702   A sender &MAY; generate comments in the Via header field to identify the
2703   software of each recipient, analogous to the <x:ref>User-Agent</x:ref> and
2704   <x:ref>Server</x:ref> header fields. However, all comments in the Via field
2705   are optional and a recipient &MAY; remove them prior to forwarding the
2706   message.
2707</t>
2708<t>
2709   For example, a request message could be sent from an HTTP/1.0 user
2710   agent to an internal proxy code-named "fred", which uses HTTP/1.1 to
2711   forward the request to a public proxy at p.example.net, which completes
2712   the request by forwarding it to the origin server at www.example.com.
2713   The request received by www.example.com would then have the following
2714   Via header field:
2715</t>
2716<figure><artwork type="example">
2717  Via: 1.0 fred, 1.1 p.example.net
2718</artwork></figure>
2719<t>
2720   An intermediary used as a portal through a network firewall
2721   &SHOULD-NOT; forward the names and ports of hosts within the firewall
2722   region unless it is explicitly enabled to do so. If not enabled, such an
2723   intermediary &SHOULD; replace each received-by host of any host behind the
2724   firewall by an appropriate pseudonym for that host.
2725</t>
2726<t>
2727   An intermediary &MAY; combine an ordered subsequence of Via header
2728   field entries into a single such entry if the entries have identical
2729   received-protocol values. For example,
2730</t>
2731<figure><artwork type="example">
2732  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
2733</artwork></figure>
2734<t>
2735  could be collapsed to
2736</t>
2737<figure><artwork type="example">
2738  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
2739</artwork></figure>
2740<t>
2741   A sender &SHOULD-NOT; combine multiple entries unless they are all
2742   under the same organizational control and the hosts have already been
2743   replaced by pseudonyms. A sender &MUST-NOT; combine entries that
2744   have different received-protocol values.
2745</t>
2746</section>
2747
2748<section title="Transformations" anchor="message.transformations">
2749<t>
2750   Some intermediaries include features for transforming messages and their
2751   payloads.  A transforming proxy might, for example, convert between image
2752   formats in order to save cache space or to reduce the amount of traffic on
2753   a slow link. However, operational problems might occur when these
2754   transformations are applied to payloads intended for critical applications,
2755   such as medical imaging or scientific data analysis, particularly when
2756   integrity checks or digital signatures are used to ensure that the payload
2757   received is identical to the original.
2758</t>
2759<t>
2760   If a proxy receives a request-target with a host name that is not a
2761   fully qualified domain name, it &MAY; add its own domain to the host name
2762   it received when forwarding the request.  A proxy &MUST-NOT; change the
2763   host name if it is a fully qualified domain name.
2764</t>
2765<t>
2766   A proxy &MUST-NOT; modify the "absolute-path" and "query" parts of the
2767   received request-target when forwarding it to the next inbound server,
2768   except as noted above to replace an empty path with "/" or "*".
2769</t>
2770<t>
2771   A proxy &MUST-NOT; modify header fields that provide information about the
2772   end points of the communication chain, the resource state, or the selected
2773   representation. A proxy &MAY; change the message body through application
2774   or removal of a transfer coding (<xref target="transfer.codings"/>).
2775</t>
2776<t>
2777   A non-transforming proxy &MUST-NOT; modify the message payload (&payload;).
2778   A transforming proxy &MUST-NOT; modify the payload of a message that
2779   contains the no-transform cache-control directive.
2780</t>
2781<t>
2782   A transforming proxy &MAY; transform the payload of a message
2783   that does not contain the no-transform cache-control directive;
2784   if the payload is transformed, the transforming proxy &MUST; add a
2785   Warning header field with the warn-code of 214 ("Transformation Applied")
2786   if one does not already appear in the message (see &header-warning;).
2787   If the payload of a <x:ref>200 (OK)</x:ref> response is transformed, the
2788   transforming proxy can also inform downstream recipients that a
2789   transformation has been applied by changing the response status code to
2790   <x:ref>203 (Non-Authoritative Information)</x:ref> (&status-203;).
2791</t>
2792</section>
2793</section>
2794</section>
2795
2796<section title="Connection Management" anchor="connection.management">
2797<t>
2798   HTTP messaging is independent of the underlying transport or
2799   session-layer connection protocol(s).  HTTP only presumes a reliable
2800   transport with in-order delivery of requests and the corresponding
2801   in-order delivery of responses.  The mapping of HTTP request and
2802   response structures onto the data units of an underlying transport
2803   protocol is outside the scope of this specification.
2804</t>
2805<t>
2806   As described in <xref target="connecting.inbound"/>, the specific
2807   connection protocols to be used for an HTTP interaction are determined by
2808   client configuration and the <x:ref>target URI</x:ref>.
2809   For example, the "http" URI scheme
2810   (<xref target="http.uri"/>) indicates a default connection of TCP
2811   over IP, with a default TCP port of 80, but the client might be
2812   configured to use a proxy via some other connection, port, or protocol.
2813</t>
2814<t>
2815   HTTP implementations are expected to engage in connection management,
2816   which includes maintaining the state of current connections,
2817   establishing a new connection or reusing an existing connection,
2818   processing messages received on a connection, detecting connection
2819   failures, and closing each connection.
2820   Most clients maintain multiple connections in parallel, including
2821   more than one connection per server endpoint.
2822   Most servers are designed to maintain thousands of concurrent connections,
2823   while controlling request queues to enable fair use and detect
2824   denial of service attacks.
2825</t>
2826
2827<section title="Connection" anchor="header.connection">
2828  <iref primary="true" item="Connection header field" x:for-anchor=""/>
2829  <iref primary="true" item="close" x:for-anchor=""/>
2830  <x:anchor-alias value="Connection"/>
2831  <x:anchor-alias value="connection-option"/>
2832  <x:anchor-alias value="close"/>
2833<t>
2834   The "Connection" header field allows the sender to indicate desired
2835   control options for the current connection.  In order to avoid confusing
2836   downstream recipients, a proxy or gateway &MUST; remove or replace any
2837   received connection options before forwarding the message.
2838</t>
2839<t>
2840   When a header field aside from Connection is used to supply control
2841   information for or about the current connection, the sender &MUST; list
2842   the corresponding field-name within the "Connection" header field.
2843   A proxy or gateway &MUST; parse a received Connection
2844   header field before a message is forwarded and, for each
2845   connection-option in this field, remove any header field(s) from
2846   the message with the same name as the connection-option, and then
2847   remove the Connection header field itself (or replace it with the
2848   intermediary's own connection options for the forwarded message).
2849</t>
2850<t>
2851   Hence, the Connection header field provides a declarative way of
2852   distinguishing header fields that are only intended for the
2853   immediate recipient ("hop-by-hop") from those fields that are
2854   intended for all recipients on the chain ("end-to-end"), enabling the
2855   message to be self-descriptive and allowing future connection-specific
2856   extensions to be deployed without fear that they will be blindly
2857   forwarded by older intermediaries.
2858</t>
2859<t>
2860   The Connection header field's value has the following grammar:
2861</t>
2862<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="connection-option"/>
2863  <x:ref>Connection</x:ref>        = 1#<x:ref>connection-option</x:ref>
2864  <x:ref>connection-option</x:ref> = <x:ref>token</x:ref>
2865</artwork></figure>
2866<t>
2867   Connection options are case-insensitive.
2868</t>
2869<t>
2870   A sender &MUST-NOT; send a connection option corresponding to a header
2871   field that is intended for all recipients of the payload.
2872   For example, <x:ref>Cache-Control</x:ref> is never appropriate as a
2873   connection option (&header-cache-control;).
2874</t>
2875<t>
2876   The connection options do not always correspond to a header field
2877   present in the message, since a connection-specific header field
2878   might not be needed if there are no parameters associated with a
2879   connection option. In contrast, a connection-specific header field that
2880   is received without a corresponding connection option usually indicates
2881   that the field has been improperly forwarded by an intermediary and
2882   ought to be ignored by the recipient.
2883</t>
2884<t>
2885   When defining new connection options, specification authors ought to survey
2886   existing header field names and ensure that the new connection option does
2887   not share the same name as an already deployed header field.
2888   Defining a new connection option essentially reserves that potential
2889   field-name for carrying additional information related to the
2890   connection option, since it would be unwise for senders to use
2891   that field-name for anything else.
2892</t>
2893<t>
2894   The "<x:dfn>close</x:dfn>" connection option is defined for a
2895   sender to signal that this connection will be closed after completion of
2896   the response. For example,
2897</t>
2898<figure><artwork type="example">
2899  Connection: close
2900</artwork></figure>
2901<t>
2902   in either the request or the response header fields indicates that the
2903   sender is going to close the connection after the current request/response
2904   is complete (<xref target="persistent.tear-down"/>).
2905</t>
2906<t>
2907   A client that does not support <x:ref>persistent connections</x:ref> &MUST;
2908   send the "close" connection option in every request message.
2909</t>
2910<t>
2911   A server that does not support <x:ref>persistent connections</x:ref> &MUST;
2912   send the "close" connection option in every response message that
2913   does not have a <x:ref>1xx (Informational)</x:ref> status code.
2914</t>
2915</section>
2916
2917<section title="Establishment" anchor="persistent.establishment">
2918<t>
2919   It is beyond the scope of this specification to describe how connections
2920   are established via various transport or session-layer protocols.
2921   Each connection applies to only one transport link.
2922</t>
2923</section>
2924
2925<section title="Persistence" anchor="persistent.connections">
2926   <x:anchor-alias value="persistent connections"/>
2927<t>
2928   HTTP/1.1 defaults to the use of "<x:dfn>persistent connections</x:dfn>",
2929   allowing multiple requests and responses to be carried over a single
2930   connection. The "<x:ref>close</x:ref>" connection-option is used to signal
2931   that a connection will not persist after the current request/response.
2932   HTTP implementations &SHOULD; support persistent connections.
2933</t>
2934<t>
2935   A recipient determines whether a connection is persistent or not based on
2936   the most recently received message's protocol version and
2937   <x:ref>Connection</x:ref> header field (if any):
2938   <list style="symbols">
2939     <t>If the <x:ref>close</x:ref> connection option is present, the
2940        connection will not persist after the current response; else,</t>
2941     <t>If the received protocol is HTTP/1.1 (or later), the connection will
2942        persist after the current response; else,</t>
2943     <t>If the received protocol is HTTP/1.0, the "keep-alive"
2944        connection option is present, the recipient is not a proxy, and
2945        the recipient wishes to honor the HTTP/1.0 "keep-alive" mechanism,
2946        the connection will persist after the current response; otherwise,</t>
2947     <t>The connection will close after the current response.</t>
2948   </list>
2949</t>
2950<t>
2951   A server &MAY; assume that an HTTP/1.1 client intends to maintain a
2952   persistent connection until a <x:ref>close</x:ref> connection option
2953   is received in a request.
2954</t>
2955<t>
2956   A client &MAY; reuse a persistent connection until it sends or receives
2957   a <x:ref>close</x:ref> connection option or receives an HTTP/1.0 response
2958   without a "keep-alive" connection option.
2959</t>
2960<t>
2961   In order to remain persistent, all messages on a connection need to
2962   have a self-defined message length (i.e., one not defined by closure
2963   of the connection), as described in <xref target="message.body"/>.
2964   A server &MUST; read the entire request message body or close
2965   the connection after sending its response, since otherwise the
2966   remaining data on a persistent connection would be misinterpreted
2967   as the next request.  Likewise,
2968   a client &MUST; read the entire response message body if it intends
2969   to reuse the same connection for a subsequent request.
2970</t>
2971<t>
2972   A proxy server &MUST-NOT; maintain a persistent connection with an
2973   HTTP/1.0 client (see <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/> for
2974   information and discussion of the problems with the Keep-Alive header field
2975   implemented by many HTTP/1.0 clients).
2976</t>
2977<t>
2978   Clients and servers &SHOULD-NOT; assume that a persistent connection is
2979   maintained for HTTP versions less than 1.1 unless it is explicitly
2980   signaled.
2981   See <xref target="compatibility.with.http.1.0.persistent.connections"/>
2982   for more information on backward compatibility with HTTP/1.0 clients.
2983</t>
2984
2985<section title="Retrying Requests" anchor="persistent.retrying.requests">
2986<t>
2987   Connections can be closed at any time, with or without intention.
2988   Implementations ought to anticipate the need to recover
2989   from asynchronous close events.
2990</t>
2991<t>
2992   When an inbound connection is closed prematurely, a client &MAY; open a new
2993   connection and automatically retransmit an aborted sequence of requests if
2994   all of those requests have idempotent methods (&idempotent-methods;).
2995   A proxy &MUST-NOT; automatically retry non-idempotent requests.
2996</t>
2997<t>
2998   A user agent &MUST-NOT; automatically retry a request with a non-idempotent
2999   method unless it has some means to know that the request semantics are
3000   actually idempotent, regardless of the method, or some means to detect that
3001   the original request was never applied. For example, a user agent that
3002   knows (through design or configuration) that a POST request to a given
3003   resource is safe can repeat that request automatically.
3004   Likewise, a user agent designed specifically to operate on a version
3005   control repository might be able to recover from partial failure conditions
3006   by checking the target resource revision(s) after a failed connection,
3007   reverting or fixing any changes that were partially applied, and then
3008   automatically retrying the requests that failed.
3009</t>
3010<t>
3011   A client &SHOULD-NOT; automatically retry a failed automatic retry.
3012</t>
3013</section>
3014
3015<section title="Pipelining" anchor="pipelining">
3016   <x:anchor-alias value="pipeline"/>
3017<t>
3018   A client that supports persistent connections &MAY; "<x:dfn>pipeline</x:dfn>"
3019   its requests (i.e., send multiple requests without waiting for each
3020   response). A server &MAY; process a sequence of pipelined requests in
3021   parallel if they all have safe methods (&safe-methods;), but &MUST; send
3022   the corresponding responses in the same order that the requests were
3023   received.
3024</t>
3025<t>
3026   A client that pipelines requests &SHOULD; retry unanswered requests if the
3027   connection closes before it receives all of the corresponding responses.
3028   When retrying pipelined requests after a failed connection (a connection
3029   not explicitly closed by the server in its last complete response), a
3030   client &MUST-NOT; pipeline immediately after connection establishment,
3031   since the first remaining request in the prior pipeline might have caused
3032   an error response that can be lost again if multiple requests are sent on a
3033   prematurely closed connection (see the TCP reset problem described in
3034   <xref target="persistent.tear-down"/>).
3035</t>
3036<t>
3037   Idempotent methods (&idempotent-methods;) are significant to pipelining
3038   because they can be automatically retried after a connection failure.
3039   A user agent &SHOULD-NOT; pipeline requests after a non-idempotent method,
3040   until the final response status code for that method has been received,
3041   unless the user agent has a means to detect and recover from partial
3042   failure conditions involving the pipelined sequence.
3043</t>
3044<t>
3045   An intermediary that receives pipelined requests &MAY; pipeline those
3046   requests when forwarding them inbound, since it can rely on the outbound
3047   user agent(s) to determine what requests can be safely pipelined. If the
3048   inbound connection fails before receiving a response, the pipelining
3049   intermediary &MAY; attempt to retry a sequence of requests that have yet
3050   to receive a response if the requests all have idempotent methods;
3051   otherwise, the pipelining intermediary &SHOULD; forward any received
3052   responses and then close the corresponding outbound connection(s) so that
3053   the outbound user agent(s) can recover accordingly.
3054</t>
3055</section>
3056</section>
3057   
3058<section title="Concurrency" anchor="persistent.concurrency">
3059<t>
3060   A client &SHOULD; limit the number of simultaneous open
3061   connections that it maintains to a given server.
3062</t>
3063<t>
3064   Previous revisions of HTTP gave a specific number of connections as a
3065   ceiling, but this was found to be impractical for many applications. As a
3066   result, this specification does not mandate a particular maximum number of
3067   connections, but instead encourages clients to be conservative when opening
3068   multiple connections.
3069</t>
3070<t>
3071   Multiple connections are typically used to avoid the "head-of-line
3072   blocking" problem, wherein a request that takes significant server-side
3073   processing and/or has a large payload blocks subsequent requests on the
3074   same connection. However, each connection consumes server resources.
3075   Furthermore, using multiple connections can cause undesirable side effects
3076   in congested networks.
3077</t>
3078<t>
3079   Note that servers might reject traffic that they deem abusive, including an
3080   excessive number of connections from a client.
3081</t>
3082</section>
3083
3084<section title="Failures and Time-outs" anchor="persistent.failures">
3085<t>
3086   Servers will usually have some time-out value beyond which they will
3087   no longer maintain an inactive connection. Proxy servers might make
3088   this a higher value since it is likely that the client will be making
3089   more connections through the same proxy server. The use of persistent
3090   connections places no requirements on the length (or existence) of
3091   this time-out for either the client or the server.
3092</t>
3093<t>
3094   A client or server that wishes to time-out &SHOULD; issue a graceful close
3095   on the connection. Implementations &SHOULD; constantly monitor open
3096   connections for a received closure signal and respond to it as appropriate,
3097   since prompt closure of both sides of a connection enables allocated system
3098   resources to be reclaimed.
3099</t>
3100<t>
3101   A client, server, or proxy &MAY; close the transport connection at any
3102   time. For example, a client might have started to send a new request
3103   at the same time that the server has decided to close the "idle"
3104   connection. From the server's point of view, the connection is being
3105   closed while it was idle, but from the client's point of view, a
3106   request is in progress.
3107</t>
3108<t>
3109   A server &SHOULD; sustain persistent connections, when possible, and allow
3110   the underlying
3111   transport's flow control mechanisms to resolve temporary overloads, rather
3112   than terminate connections with the expectation that clients will retry.
3113   The latter technique can exacerbate network congestion.
3114</t>
3115<t>
3116   A client sending a message body &SHOULD; monitor
3117   the network connection for an error response while it is transmitting
3118   the request. If the client sees a response that indicates the server does
3119   not wish to receive the message body and is closing the connection, the
3120   client &SHOULD; immediately cease transmitting the body and close its side
3121   of the connection.
3122</t>
3123</section>
3124   
3125<section title="Tear-down" anchor="persistent.tear-down">
3126  <iref primary="false" item="Connection header field" x:for-anchor=""/>
3127  <iref primary="false" item="close" x:for-anchor=""/>
3128<t>
3129   The <x:ref>Connection</x:ref> header field
3130   (<xref target="header.connection"/>) provides a "<x:ref>close</x:ref>"
3131   connection option that a sender &SHOULD; send when it wishes to close
3132   the connection after the current request/response pair.
3133</t>
3134<t>
3135   A client that sends a <x:ref>close</x:ref> connection option &MUST-NOT;
3136   send further requests on that connection (after the one containing
3137   <x:ref>close</x:ref>) and &MUST; close the connection after reading the
3138   final response message corresponding to this request.
3139</t>
3140<t>
3141   A server that receives a <x:ref>close</x:ref> connection option &MUST;
3142   initiate a close of the connection (see below) after it sends the
3143   final response to the request that contained <x:ref>close</x:ref>.
3144   The server &SHOULD; send a <x:ref>close</x:ref> connection option
3145   in its final response on that connection. The server &MUST-NOT; process
3146   any further requests received on that connection.
3147</t>
3148<t>
3149   A server that sends a <x:ref>close</x:ref> connection option &MUST;
3150   initiate a close of the connection (see below) after it sends the
3151   response containing <x:ref>close</x:ref>. The server &MUST-NOT; process
3152   any further requests received on that connection.
3153</t>
3154<t>
3155   A client that receives a <x:ref>close</x:ref> connection option &MUST;
3156   cease sending requests on that connection and close the connection
3157   after reading the response message containing the close; if additional
3158   pipelined requests had been sent on the connection, the client &SHOULD-NOT;
3159   assume that they will be processed by the server.
3160</t>
3161<t>
3162   If a server performs an immediate close of a TCP connection, there is a
3163   significant risk that the client will not be able to read the last HTTP
3164   response.  If the server receives additional data from the client on a
3165   fully-closed connection, such as another request that was sent by the
3166   client before receiving the server's response, the server's TCP stack will
3167   send a reset packet to the client; unfortunately, the reset packet might
3168   erase the client's unacknowledged input buffers before they can be read
3169   and interpreted by the client's HTTP parser.
3170</t>
3171<t>
3172   To avoid the TCP reset problem, servers typically close a connection in
3173   stages. First, the server performs a half-close by closing only the write
3174   side of the read/write connection. The server then continues to read from
3175   the connection until it receives a corresponding close by the client, or
3176   until the server is reasonably certain that its own TCP stack has received
3177   the client's acknowledgement of the packet(s) containing the server's last
3178   response. Finally, the server fully closes the connection.
3179</t>
3180<t>
3181   It is unknown whether the reset problem is exclusive to TCP or might also
3182   be found in other transport connection protocols.
3183</t>
3184</section>
3185
3186<section title="Upgrade" anchor="header.upgrade">
3187  <iref primary="true" item="Upgrade header field" x:for-anchor=""/>
3188  <x:anchor-alias value="Upgrade"/>
3189  <x:anchor-alias value="protocol"/>
3190  <x:anchor-alias value="protocol-name"/>
3191  <x:anchor-alias value="protocol-version"/>
3192<t>
3193   The "Upgrade" header field is intended to provide a simple mechanism
3194   for transitioning from HTTP/1.1 to some other protocol on the same
3195   connection.  A client &MAY; send a list of protocols in the Upgrade
3196   header field of a request to invite the server to switch to one or
3197   more of those protocols, in order of descending preference, before sending
3198   the final response. A server &MAY; ignore a received Upgrade header field
3199   if it wishes to continue using the current protocol on that connection.
3200</t>
3201<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Upgrade"/>
3202  <x:ref>Upgrade</x:ref>          = 1#<x:ref>protocol</x:ref>
3203
3204  <x:ref>protocol</x:ref>         = <x:ref>protocol-name</x:ref> ["/" <x:ref>protocol-version</x:ref>]
3205  <x:ref>protocol-name</x:ref>    = <x:ref>token</x:ref>
3206  <x:ref>protocol-version</x:ref> = <x:ref>token</x:ref>
3207</artwork></figure>
3208<t>
3209   A server that sends a <x:ref>101 (Switching Protocols)</x:ref> response
3210   &MUST; send an Upgrade header field to indicate the new protocol(s) to
3211   which the connection is being switched; if multiple protocol layers are
3212   being switched, the sender &MUST; list the protocols in layer-ascending
3213   order. A server &MUST-NOT; switch to a protocol that was not indicated by
3214   the client in the corresponding request's Upgrade header field.
3215   A server &MAY; choose to ignore the order of preference indicated by the
3216   client and select the new protocol(s) based on other factors, such as the
3217   nature of the request or the current load on the server.
3218</t>
3219<t>
3220   A server that sends a <x:ref>426 (Upgrade Required)</x:ref> response
3221   &MUST; send an Upgrade header field to indicate the acceptable protocols,
3222   in order of descending preference.
3223</t>
3224<t>
3225   A server &MAY; send an Upgrade header field in any other response to
3226   advertise that it implements support for upgrading to the listed protocols,
3227   in order of descending preference, when appropriate for a future request.
3228</t>
3229<figure><preamble>
3230   The following is a hypothetical example sent by a client:
3231</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
3232GET /hello.txt HTTP/1.1
3233Host: www.example.com
3234Connection: upgrade
3235Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
3236
3237</artwork></figure>
3238<t>
3239   Upgrade cannot be used to insist on a protocol change; its acceptance and
3240   use by the server is optional. The capabilities and nature of the
3241   application-level communication after the protocol change is entirely
3242   dependent upon the new protocol(s) chosen. However, immediately after
3243   sending the 101 response, the server is expected to continue responding to
3244   the original request as if it had received its equivalent within the new
3245   protocol (i.e., the server still has an outstanding request to satisfy
3246   after the protocol has been changed, and is expected to do so without
3247   requiring the request to be repeated).
3248</t>
3249<t>
3250   For example, if the Upgrade header field is received in a GET request
3251   and the server decides to switch protocols, it first responds
3252   with a <x:ref>101 (Switching Protocols)</x:ref> message in HTTP/1.1 and
3253   then immediately follows that with the new protocol's equivalent of a
3254   response to a GET on the target resource.  This allows a connection to be
3255   upgraded to protocols with the same semantics as HTTP without the
3256   latency cost of an additional round-trip.  A server &MUST-NOT; switch
3257   protocols unless the received message semantics can be honored by the new
3258   protocol; an OPTIONS request can be honored by any protocol.
3259</t>
3260<figure><preamble>
3261   The following is an example response to the above hypothetical request:
3262</preamble><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
3263HTTP/1.1 101 Switching Protocols
3264Connection: upgrade
3265Upgrade: HTTP/2.0
3266
3267[... data stream switches to HTTP/2.0 with an appropriate response
3268(as defined by new protocol) to the "GET /hello.txt" request ...]
3269</artwork></figure>
3270<t>
3271   When Upgrade is sent, the sender &MUST; also send a
3272   <x:ref>Connection</x:ref> header field (<xref target="header.connection"/>)
3273   that contains an "upgrade" connection option, in order to prevent Upgrade
3274   from being accidentally forwarded by intermediaries that might not implement
3275   the listed protocols.  A server &MUST; ignore an Upgrade header field that
3276   is received in an HTTP/1.0 request.
3277</t>
3278<t>
3279   A client cannot begin using an upgraded protocol on the connection until
3280   it has completely sent the request message (i.e., the client can't change
3281   the protocol it is sending in the middle of a message).
3282   If a server receives both Upgrade and an <x:ref>Expect</x:ref> header field
3283   with the "100-continue" expectation (&header-expect;), the
3284   server &MUST; send a <x:ref>100 (Continue)</x:ref> response before sending
3285   a <x:ref>101 (Switching Protocols)</x:ref> response.
3286</t>
3287<t>
3288   The Upgrade header field only applies to switching protocols on top of the
3289   existing connection; it cannot be used to switch the underlying connection
3290   (transport) protocol, nor to switch the existing communication to a
3291   different connection. For those purposes, it is more appropriate to use a
3292   <x:ref>3xx (Redirection)</x:ref> response (&status-3xx;).
3293</t>
3294<t>
3295   This specification only defines the protocol name "HTTP" for use by
3296   the family of Hypertext Transfer Protocols, as defined by the HTTP
3297   version rules of <xref target="http.version"/> and future updates to this
3298   specification. Additional tokens ought to be registered with IANA using the
3299   registration procedure defined in <xref target="upgrade.token.registry"/>.
3300</t>
3301</section>
3302</section>
3303
3304<section title="ABNF list extension: #rule" anchor="abnf.extension">
3305<t>
3306  A #rule extension to the ABNF rules of <xref target="RFC5234"/> is used to
3307  improve readability in the definitions of some header field values.
3308</t>
3309<t>
3310  A construct "#" is defined, similar to "*", for defining comma-delimited
3311  lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating
3312  at least &lt;n&gt; and at most &lt;m&gt; elements, each separated by a single
3313  comma (",") and optional whitespace (OWS).   
3314</t>
3315<figure><preamble>
3316  Thus, a sender &MUST; expand the list construct as follows:
3317</preamble><artwork type="example">
3318  1#element =&gt; element *( OWS "," OWS element )
3319</artwork></figure>
3320<figure><preamble>
3321  and:
3322</preamble><artwork type="example">
3323  #element =&gt; [ 1#element ]
3324</artwork></figure>
3325<figure><preamble>
3326  and for n &gt;= 1 and m &gt; 1:
3327</preamble><artwork type="example">
3328  &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
3329</artwork></figure>
3330<t>
3331  For compatibility with legacy list rules, a recipient &MUST; parse and ignore
3332  a reasonable number of empty list elements: enough to handle common mistakes
3333  by senders that merge values, but not so much that they could be used as a
3334  denial of service mechanism. In other words, a recipient &MUST; expand the
3335  list construct as follows:
3336</t>
3337<figure><artwork type="example">
3338  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
3339 
3340  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
3341</artwork></figure>
3342<t>
3343  Empty elements do not contribute to the count of elements present.
3344  For example, given these ABNF productions:
3345</t>
3346<figure><artwork type="example">
3347  example-list      = 1#example-list-elmt
3348  example-list-elmt = token ; see <xref target="field.components"/>
3349</artwork></figure>
3350<t>
3351  Then the following are valid values for example-list (not including the
3352  double quotes, which are present for delimitation only):
3353</t>
3354<figure><artwork type="example">
3355  "foo,bar"
3356  "foo ,bar,"
3357  "foo , ,bar,charlie   "
3358</artwork></figure>
3359<t>
3360  In contrast, the following values would be invalid, since at least one
3361  non-empty element is required by the example-list production:
3362</t>
3363<figure><artwork type="example">
3364  ""
3365  ","
3366  ",   ,"
3367</artwork></figure>
3368<t>
3369  <xref target="collected.abnf"/> shows the collected ABNF after the list
3370  constructs have been expanded, as described above, for recipients.
3371</t>
3372</section>
3373
3374<section title="IANA Considerations" anchor="IANA.considerations">
3375
3376<section title="Header Field Registration" anchor="header.field.registration">
3377<t>
3378   HTTP header fields are registered within the Message Header Field Registry
3379   maintained at
3380   <eref target="http://www.iana.org/assignments/message-headers/"/>.
3381</t>
3382<t>
3383   This document defines the following HTTP header fields, so their
3384   associated registry entries shall be updated according to the permanent
3385   registrations below (see <xref target="BCP90"/>):
3386</t>
3387<?BEGININC p1-messaging.iana-headers ?>
3388<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
3389<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
3390   <ttcol>Header Field Name</ttcol>
3391   <ttcol>Protocol</ttcol>
3392   <ttcol>Status</ttcol>
3393   <ttcol>Reference</ttcol>
3394
3395   <c>Connection</c>
3396   <c>http</c>
3397   <c>standard</c>
3398   <c>
3399      <xref target="header.connection"/>
3400   </c>
3401   <c>Content-Length</c>
3402   <c>http</c>
3403   <c>standard</c>
3404   <c>
3405      <xref target="header.content-length"/>
3406   </c>
3407   <c>Host</c>
3408   <c>http</c>
3409   <c>standard</c>
3410   <c>
3411      <xref target="header.host"/>
3412   </c>
3413   <c>TE</c>
3414   <c>http</c>
3415   <c>standard</c>
3416   <c>
3417      <xref target="header.te"/>
3418   </c>
3419   <c>Trailer</c>
3420   <c>http</c>
3421   <c>standard</c>
3422   <c>
3423      <xref target="header.trailer"/>
3424   </c>
3425   <c>Transfer-Encoding</c>
3426   <c>http</c>
3427   <c>standard</c>
3428   <c>
3429      <xref target="header.transfer-encoding"/>
3430   </c>
3431   <c>Upgrade</c>
3432   <c>http</c>
3433   <c>standard</c>
3434   <c>
3435      <xref target="header.upgrade"/>
3436   </c>
3437   <c>Via</c>
3438   <c>http</c>
3439   <c>standard</c>
3440   <c>
3441      <xref target="header.via"/>
3442   </c>
3443</texttable>
3444<!--(END)-->
3445<?ENDINC p1-messaging.iana-headers ?>
3446<t>
3447   Furthermore, the header field-name "Close" shall be registered as
3448   "reserved", since using that name as an HTTP header field might
3449   conflict with the "close" connection option of the "<x:ref>Connection</x:ref>"
3450   header field (<xref target="header.connection"/>).
3451</t>
3452<texttable align="left" suppress-title="true">
3453   <ttcol>Header Field Name</ttcol>
3454   <ttcol>Protocol</ttcol>
3455   <ttcol>Status</ttcol>
3456   <ttcol>Reference</ttcol>
3457
3458   <c>Close</c>
3459   <c>http</c>
3460   <c>reserved</c>
3461   <c>
3462      <xref target="header.field.registration"/>
3463   </c>
3464</texttable>
3465<t>
3466   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
3467</t>
3468</section>
3469
3470<section title="URI Scheme Registration" anchor="uri.scheme.registration">
3471<t>
3472   IANA maintains the registry of URI Schemes <xref target="BCP115"/> at
3473   <eref target="http://www.iana.org/assignments/uri-schemes/"/>.
3474</t>
3475<t>
3476   This document defines the following URI schemes, so their
3477   associated registry entries shall be updated according to the permanent
3478   registrations below:
3479</t>
3480<texttable align="left" suppress-title="true">
3481   <ttcol>URI Scheme</ttcol>
3482   <ttcol>Description</ttcol>
3483   <ttcol>Reference</ttcol>
3484
3485   <c>http</c>
3486   <c>Hypertext Transfer Protocol</c>
3487   <c><xref target="http.uri"/></c>
3488
3489   <c>https</c>
3490   <c>Hypertext Transfer Protocol Secure</c>
3491   <c><xref target="https.uri"/></c>
3492</texttable>
3493</section>
3494
3495<section title="Internet Media Type Registration" anchor="internet.media.type.http">
3496<t>
3497   IANA maintains the registry of Internet media types <xref target="BCP13"/> at
3498   <eref target="http://www.iana.org/assignments/media-types"/>.
3499</t>
3500<t>
3501   This document serves as the specification for the Internet media types
3502   "message/http" and "application/http". The following is to be registered with
3503   IANA.
3504</t>
3505<section title="Internet Media Type message/http" anchor="internet.media.type.message.http">
3506<iref item="Media Type" subitem="message/http" primary="true"/>
3507<iref item="message/http Media Type" primary="true"/>
3508<t>
3509   The message/http type can be used to enclose a single HTTP request or
3510   response message, provided that it obeys the MIME restrictions for all
3511   "message" types regarding line length and encodings.
3512</t>
3513<t>
3514  <list style="hanging" x:indent="12em">
3515    <t hangText="Type name:">
3516      message
3517    </t>
3518    <t hangText="Subtype name:">
3519      http
3520    </t>
3521    <t hangText="Required parameters:">
3522      N/A
3523    </t>
3524    <t hangText="Optional parameters:">
3525      version, msgtype
3526      <list style="hanging">
3527        <t hangText="version:">
3528          The HTTP-version number of the enclosed message
3529          (e.g., "1.1"). If not present, the version can be
3530          determined from the first line of the body.
3531        </t>
3532        <t hangText="msgtype:">
3533          The message type &mdash; "request" or "response". If not
3534          present, the type can be determined from the first
3535          line of the body.
3536        </t>
3537      </list>
3538    </t>
3539    <t hangText="Encoding considerations:">
3540      only "7bit", "8bit", or "binary" are permitted
3541    </t>
3542    <t hangText="Security considerations:">
3543      see <xref target="security.considerations"/>
3544    </t>
3545    <t hangText="Interoperability considerations:">
3546      N/A
3547    </t>
3548    <t hangText="Published specification:">
3549      This specification (see <xref target="internet.media.type.message.http"/>).
3550    </t>
3551    <t hangText="Applications that use this media type:">
3552      N/A
3553    </t>
3554    <t hangText="Fragment identifier considerations:">
3555      N/A
3556    </t>
3557    <t hangText="Additional information:">
3558      <list style="hanging">
3559        <t hangText="Magic number(s):">N/A</t>
3560        <t hangText="Deprecated alias names for this type:">N/A</t>
3561        <t hangText="File extension(s):">N/A</t>
3562        <t hangText="Macintosh file type code(s):">N/A</t>
3563      </list>
3564    </t>
3565    <t hangText="Person and email address to contact for further information:">
3566      See Authors Section.
3567    </t>
3568    <t hangText="Intended usage:">
3569      COMMON
3570    </t>
3571    <t hangText="Restrictions on usage:">
3572      N/A
3573    </t>
3574    <t hangText="Author:">
3575      See Authors Section.
3576    </t>
3577    <t hangText="Change controller:">
3578      IESG
3579    </t>
3580  </list>
3581</t>
3582</section>
3583<section title="Internet Media Type application/http" anchor="internet.media.type.application.http">
3584<iref item="Media Type" subitem="application/http" primary="true"/>
3585<iref item="application/http Media Type" primary="true"/>
3586<t>
3587   The application/http type can be used to enclose a pipeline of one or more
3588   HTTP request or response messages (not intermixed).
3589</t>
3590<t>
3591  <list style="hanging" x:indent="12em">
3592    <t hangText="Type name:">
3593      application
3594    </t>
3595    <t hangText="Subtype name:">
3596      http
3597    </t>
3598    <t hangText="Required parameters:">
3599      N/A
3600    </t>
3601    <t hangText="Optional parameters:">
3602      version, msgtype
3603      <list style="hanging">
3604        <t hangText="version:">
3605          The HTTP-version number of the enclosed messages
3606          (e.g., "1.1"). If not present, the version can be
3607          determined from the first line of the body.
3608        </t>
3609        <t hangText="msgtype:">
3610          The message type &mdash; "request" or "response". If not
3611          present, the type can be determined from the first
3612          line of the body.
3613        </t>
3614      </list>
3615    </t>
3616    <t hangText="Encoding considerations:">
3617      HTTP messages enclosed by this type
3618      are in "binary" format; use of an appropriate
3619      Content-Transfer-Encoding is required when
3620      transmitted via E-mail.
3621    </t>
3622    <t hangText="Security considerations:">
3623      see <xref target="security.considerations"/>
3624    </t>
3625    <t hangText="Interoperability considerations:">
3626      N/A
3627    </t>
3628    <t hangText="Published specification:">
3629      This specification (see <xref target="internet.media.type.application.http"/>).
3630    </t>
3631    <t hangText="Applications that use this media type:">
3632      N/A
3633    </t>
3634    <t hangText="Fragment identifier considerations:">
3635      N/A
3636    </t>
3637    <t hangText="Additional information:">
3638      <list style="hanging">
3639        <t hangText="Deprecated alias names for this type:">N/A</t>
3640        <t hangText="Magic number(s):">N/A</t>
3641        <t hangText="File extension(s):">N/A</t>
3642        <t hangText="Macintosh file type code(s):">N/A</t>
3643      </list>
3644    </t>
3645    <t hangText="Person and email address to contact for further information:">
3646      See Authors Section.
3647    </t>
3648    <t hangText="Intended usage:">
3649      COMMON
3650    </t>
3651    <t hangText="Restrictions on usage:">
3652      N/A
3653    </t>
3654    <t hangText="Author:">
3655      See Authors Section.
3656    </t>
3657    <t hangText="Change controller:">
3658      IESG
3659    </t>
3660  </list>
3661</t>
3662</section>
3663</section>
3664
3665<section title="Transfer Coding Registry" anchor="transfer.coding.registry">
3666<t>
3667   The HTTP Transfer Coding Registry defines the name space for transfer
3668   coding names. It is maintained at <eref target="http://www.iana.org/assignments/http-parameters"/>.
3669</t>
3670
3671<section title="Procedure" anchor="transfer.coding.registry.procedure">
3672<t>
3673   Registrations &MUST; include the following fields:
3674   <list style="symbols">
3675     <t>Name</t>
3676     <t>Description</t>
3677     <t>Pointer to specification text</t>
3678   </list>
3679</t>
3680<t>
3681   Names of transfer codings &MUST-NOT; overlap with names of content codings
3682   (&content-codings;) unless the encoding transformation is identical, as
3683   is the case for the compression codings defined in
3684   <xref target="compression.codings"/>.
3685</t>
3686<t>
3687   Values to be added to this name space require IETF Review (see
3688   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
3689   conform to the purpose of transfer coding defined in this specification.
3690</t>
3691<t>
3692   Use of program names for the identification of encoding formats
3693   is not desirable and is discouraged for future encodings.
3694</t>
3695</section>
3696
3697<section title="Registration" anchor="transfer.coding.registration">
3698<t>
3699   The HTTP Transfer Coding Registry shall be updated with the registrations
3700   below:
3701</t>
3702<texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table">
3703   <ttcol>Name</ttcol>
3704   <ttcol>Description</ttcol>
3705   <ttcol>Reference</ttcol>
3706   <c>chunked</c>
3707   <c>Transfer in a series of chunks</c>
3708   <c>
3709      <xref target="chunked.encoding"/>
3710   </c>
3711   <c>compress</c>
3712   <c>UNIX "compress" data format <xref target="Welch"/></c>
3713   <c>
3714      <xref target="compress.coding"/>
3715   </c>
3716   <c>deflate</c>
3717   <c>"deflate" compressed data (<xref target="RFC1951"/>) inside
3718   the "zlib" data format (<xref target="RFC1950"/>)
3719   </c>
3720   <c>
3721      <xref target="deflate.coding"/>
3722   </c>
3723   <c>gzip</c>
3724   <c>GZIP file format <xref target="RFC1952"/></c>
3725   <c>
3726      <xref target="gzip.coding"/>
3727   </c>
3728   <c>x-compress</c>
3729   <c>Deprecated (alias for compress)</c>
3730   <c>
3731      <xref target="compress.coding"/>
3732   </c>
3733   <c>x-gzip</c>
3734   <c>Deprecated (alias for gzip)</c>
3735   <c>
3736      <xref target="gzip.coding"/>
3737   </c>
3738</texttable>
3739</section>
3740</section>
3741
3742<section title="Content Coding Registration" anchor="content.coding.registration">
3743<t>
3744   IANA maintains the registry of HTTP Content Codings at
3745   <eref target="http://www.iana.org/assignments/http-parameters"/>.
3746</t>
3747<t>
3748   The HTTP Content Codings Registry shall be updated with the registrations
3749   below:
3750</t>
3751<texttable align="left" suppress-title="true" anchor="iana.content.coding.registration.table">
3752   <ttcol>Name</ttcol>
3753   <ttcol>Description</ttcol>
3754   <ttcol>Reference</ttcol>
3755   <c>compress</c>
3756   <c>UNIX "compress" data format <xref target="Welch"/></c>
3757   <c>
3758      <xref target="compress.coding"/>
3759   </c>
3760   <c>deflate</c>
3761   <c>"deflate" compressed data (<xref target="RFC1951"/>) inside
3762   the "zlib" data format (<xref target="RFC1950"/>)</c>
3763   <c>
3764      <xref target="deflate.coding"/>
3765   </c>
3766   <c>gzip</c>
3767   <c>GZIP file format <xref target="RFC1952"/></c>
3768   <c>
3769      <xref target="gzip.coding"/>
3770   </c>
3771   <c>x-compress</c>
3772   <c>Deprecated (alias for compress)</c>
3773   <c>
3774      <xref target="compress.coding"/>
3775   </c>
3776   <c>x-gzip</c>
3777   <c>Deprecated (alias for gzip)</c>
3778   <c>
3779      <xref target="gzip.coding"/>
3780   </c>
3781</texttable>
3782</section>
3783
3784<section title="Upgrade Token Registry" anchor="upgrade.token.registry">
3785<t>
3786   The HTTP Upgrade Token Registry defines the name space for protocol-name
3787   tokens used to identify protocols in the <x:ref>Upgrade</x:ref> header
3788   field. The registry is maintained at <eref target="http://www.iana.org/assignments/http-upgrade-tokens"/>.
3789</t>
3790
3791<section title="Procedure" anchor="upgrade.token.registry.procedure">  
3792<t>
3793   Each registered protocol name is associated with contact information
3794   and an optional set of specifications that details how the connection
3795   will be processed after it has been upgraded.
3796</t>
3797<t>
3798   Registrations happen on a "First Come First Served" basis (see
3799   <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>) and are subject to the
3800   following rules:
3801  <list style="numbers">
3802    <t>A protocol-name token, once registered, stays registered forever.</t>
3803    <t>The registration &MUST; name a responsible party for the
3804       registration.</t>
3805    <t>The registration &MUST; name a point of contact.</t>
3806    <t>The registration &MAY; name a set of specifications associated with
3807       that token. Such specifications need not be publicly available.</t>
3808    <t>The registration &SHOULD; name a set of expected "protocol-version"
3809       tokens associated with that token at the time of registration.</t>
3810    <t>The responsible party &MAY; change the registration at any time.
3811       The IANA will keep a record of all such changes, and make them
3812       available upon request.</t>
3813    <t>The IESG &MAY; reassign responsibility for a protocol token.
3814       This will normally only be used in the case when a
3815       responsible party cannot be contacted.</t>
3816  </list>
3817</t>
3818<t>
3819   This registration procedure for HTTP Upgrade Tokens replaces that
3820   previously defined in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>.
3821</t>
3822</section>
3823
3824<section title="Upgrade Token Registration" anchor="upgrade.token.registration">
3825<t>
3826   The "HTTP" entry in the HTTP Upgrade Token Registry shall be updated with
3827   the registration below:
3828</t>
3829<texttable align="left" suppress-title="true">
3830   <ttcol>Value</ttcol>
3831   <ttcol>Description</ttcol>
3832   <ttcol>Expected Version Tokens</ttcol>
3833   <ttcol>Reference</ttcol>
3834
3835   <c>HTTP</c>
3836   <c>Hypertext Transfer Protocol</c>
3837   <c>any DIGIT.DIGIT (e.g, "2.0")</c>
3838   <c><xref target="http.version"/></c>
3839</texttable>
3840<t>
3841   The responsible party is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
3842</t>
3843</section>
3844</section>
3845
3846</section>
3847
3848<section title="Security Considerations" anchor="security.considerations">
3849<t>
3850   This section is meant to inform developers, information providers, and
3851   users of known security concerns relevant to HTTP/1.1 message syntax,
3852   parsing, and routing.
3853</t>
3854
3855<section title="DNS-related Attacks" anchor="dns.related.attacks">
3856<t>
3857   HTTP clients rely heavily on the Domain Name Service (DNS), and are thus
3858   generally prone to security attacks based on the deliberate misassociation
3859   of IP addresses and DNS names not protected by DNSSEC. Clients need to be
3860   cautious in assuming the validity of an IP number/DNS name association unless
3861   the response is protected by DNSSEC (<xref target="RFC4033"/>).
3862</t>
3863</section>
3864
3865<section title="Intermediaries and Caching" anchor="attack.intermediaries">
3866<t>
3867   By their very nature, HTTP intermediaries are men-in-the-middle, and
3868   represent an opportunity for man-in-the-middle attacks. Compromise of
3869   the systems on which the intermediaries run can result in serious security
3870   and privacy problems. Intermediaries have access to security-related
3871   information, personal information about individual users and
3872   organizations, and proprietary information belonging to users and
3873   content providers. A compromised intermediary, or an intermediary
3874   implemented or configured without regard to security and privacy
3875   considerations, might be used in the commission of a wide range of
3876   potential attacks.
3877</t>
3878<t>
3879   Intermediaries that contain a shared cache are especially vulnerable
3880   to cache poisoning attacks.
3881</t>
3882<t>
3883   Implementers need to consider the privacy and security
3884   implications of their design and coding decisions, and of the
3885   configuration options they provide to operators (especially the
3886   default configuration).
3887</t>
3888<t>
3889   Users need to be aware that intermediaries are no more trustworthy than
3890   the people who run them; HTTP itself cannot solve this problem.
3891</t>
3892</section>
3893
3894<section title="Buffer Overflows" anchor="attack.protocol.element.size.overflows">
3895<t>
3896   Because HTTP uses mostly textual, character-delimited fields, attackers can
3897   overflow buffers in implementations, and/or perform a Denial of Service
3898   against implementations that accept fields with unlimited lengths.
3899</t>
3900<t>
3901   To promote interoperability, this specification makes specific
3902   recommendations for minimum size limits on request-line
3903   (<xref target="request.line"/>)
3904   and header fields (<xref target="header.fields"/>). These are
3905   minimum recommendations, chosen to be supportable even by implementations
3906   with limited resources; it is expected that most implementations will
3907   choose substantially higher limits.
3908</t>
3909<t>
3910   This specification also provides a way for servers to reject messages that
3911   have request-targets that are too long (&status-414;) or request entities
3912   that are too large (&status-4xx;). Additional status codes related to
3913   capacity limits have been defined by extensions to HTTP
3914   <xref target="RFC6585"/>.
3915</t>
3916<t>
3917   Recipients ought to carefully limit the extent to which they read other
3918   fields, including (but not limited to) request methods, response status
3919   phrases, header field-names, and body chunks, so as to avoid denial of
3920   service attacks without impeding interoperability.
3921</t>
3922</section>
3923
3924<section title="Message Integrity" anchor="message.integrity">
3925<t>
3926   HTTP does not define a specific mechanism for ensuring message integrity,
3927   instead relying on the error-detection ability of underlying transport
3928   protocols and the use of length or chunk-delimited framing to detect
3929   completeness. Additional integrity mechanisms, such as hash functions or
3930   digital signatures applied to the content, can be selectively added to
3931   messages via extensible metadata header fields. Historically, the lack of
3932   a single integrity mechanism has been justified by the informal nature of
3933   most HTTP communication.  However, the prevalence of HTTP as an information
3934   access mechanism has resulted in its increasing use within environments
3935   where verification of message integrity is crucial.
3936</t>
3937<t>
3938   User agents are encouraged to implement configurable means for detecting
3939   and reporting failures of message integrity such that those means can be
3940   enabled within environments for which integrity is necessary. For example,
3941   a browser being used to view medical history or drug interaction
3942   information needs to indicate to the user when such information is detected
3943   by the protocol to be incomplete, expired, or corrupted during transfer.
3944   Such mechanisms might be selectively enabled via user agent extensions or
3945   the presence of message integrity metadata in a response.
3946   At a minimum, user agents ought to provide some indication that allows a
3947   user to distinguish between a complete and incomplete response message
3948   (<xref target="incomplete.messages"/>) when such verification is desired.
3949</t>
3950</section>
3951
3952<section title="Server Log Information" anchor="abuse.of.server.log.information">
3953<t>
3954   A server is in the position to save personal data about a user's requests
3955   over time, which might identify their reading patterns or subjects of
3956   interest.  In particular, log information gathered at an intermediary
3957   often contains a history of user agent interaction, across a multitude
3958   of sites, that can be traced to individual users.
3959</t>
3960<t>
3961   HTTP log information is confidential in nature; its handling is often
3962   constrained by laws and regulations.  Log information needs to be securely
3963   stored and appropriate guidelines followed for its analysis.
3964   Anonymization of personal information within individual entries helps,
3965   but is generally not sufficient to prevent real log traces from being
3966   re-identified based on correlation with other access characteristics.
3967   As such, access traces that are keyed to a specific client are unsafe to
3968   publish even if the key is pseudonymous.
3969</t>
3970<t>
3971   To minimize the risk of theft or accidental publication, log information
3972   ought to be purged of personally identifiable information, including
3973   user identifiers, IP addresses, and user-provided query parameters,
3974   as soon as that information is no longer necessary to support operational
3975   needs for security, auditing, or fraud control.
3976</t>
3977</section>
3978</section>
3979
3980<section title="Acknowledgments" anchor="acks">
3981<t>
3982   This edition of HTTP/1.1 builds on the many contributions that went into
3983   <xref target="RFC1945" format="none">RFC 1945</xref>,
3984   <xref target="RFC2068" format="none">RFC 2068</xref>,
3985   <xref target="RFC2145" format="none">RFC 2145</xref>, and
3986   <xref target="RFC2616" format="none">RFC 2616</xref>, including
3987   substantial contributions made by the previous authors, editors, and
3988   working group chairs: Tim Berners-Lee, Ari Luotonen, Roy T. Fielding,
3989   Henrik Frystyk Nielsen, Jim Gettys, Jeffrey C. Mogul, Larry Masinter,
3990   and Paul J. Leach. Mark Nottingham oversaw this effort as working group chair.
3991</t>
3992<t>
3993   Since 1999, the following contributors have helped improve the HTTP
3994   specification by reporting bugs, asking smart questions, drafting or
3995   reviewing text, and evaluating open issues:
3996</t>
3997<?BEGININC acks ?>
3998<t>Adam Barth,
3999Adam Roach,
4000Addison Phillips,
4001Adrian Chadd,
4002Adrien W. de Croy,
4003Alan Ford,
4004Alan Ruttenberg,
4005Albert Lunde,
4006Alek Storm,
4007Alex Rousskov,
4008Alexandre Morgaut,
4009Alexey Melnikov,
4010Alisha Smith,
4011Amichai Rothman,
4012Amit Klein,
4013Amos Jeffries,
4014Andreas Maier,
4015Andreas Petersson,
4016Andrei Popov,
4017Anil Sharma,
4018Anne van Kesteren,
4019Anthony Bryan,
4020Asbjorn Ulsberg,
4021Ashok Kumar,
4022Balachander Krishnamurthy,
4023Barry Leiba,
4024Ben Laurie,
4025Benjamin Carlyle,
4026Benjamin Niven-Jenkins,
4027Benoit Claise,
4028Bil Corry,
4029Bill Burke,
4030Bjoern Hoehrmann,
4031Bob Scheifler,
4032Boris Zbarsky,
4033Brett Slatkin,
4034Brian Kell,
4035Brian McBarron,
4036Brian Pane,
4037Brian Raymor,
4038Brian Smith,
4039Bruce Perens,
4040Bryce Nesbitt,
4041Cameron Heavon-Jones,
4042Carl Kugler,
4043Carsten Bormann,
4044Charles Fry,
4045Chris Burdess,
4046Chris Newman,
4047Christian Huitema,
4048Cyrus Daboo,
4049Dale Robert Anderson,
4050Dan Wing,
4051Dan Winship,
4052Daniel Stenberg,
4053Darrel Miller,
4054Dave Cridland,
4055Dave Crocker,
4056Dave Kristol,
4057Dave Thaler,
4058David Booth,
4059David Singer,
4060David W. Morris,
4061Diwakar Shetty,
4062Dmitry Kurochkin,
4063Drummond Reed,
4064Duane Wessels,
4065Edward Lee,
4066Eitan Adler,
4067Eliot Lear,
4068Emile Stephan,
4069Eran Hammer-Lahav,
4070Eric D. Williams,
4071Eric J. Bowman,
4072Eric Lawrence,
4073Eric Rescorla,
4074Erik Aronesty,
4075EungJun Yi,
4076Evan Prodromou,
4077Felix Geisendoerfer,
4078Florian Weimer,
4079Frank Ellermann,
4080Fred Akalin,
4081Fred Bohle,
4082Frederic Kayser,
4083Gabor Molnar,
4084Gabriel Montenegro,
4085Geoffrey Sneddon,
4086Gervase Markham,
4087Gili Tzabari,
4088Grahame Grieve,
4089Greg Slepak,
4090Greg Wilkins,
4091Grzegorz Calkowski,
4092Harald Tveit Alvestrand,
4093Harry Halpin,
4094Helge Hess,
4095Henrik Nordstrom,
4096Henry S. Thompson,
4097Henry Story,
4098Herbert van de Sompel,
4099Herve Ruellan,
4100Howard Melman,
4101Hugo Haas,
4102Ian Fette,
4103Ian Hickson,
4104Ido Safruti,
4105Ilari Liusvaara,
4106Ilya Grigorik,
4107Ingo Struck,
4108J. Ross Nicoll,
4109James Cloos,
4110James H. Manger,
4111James Lacey,
4112James M. Snell,
4113Jamie Lokier,
4114Jan Algermissen,
4115Jari Arkko,
4116Jeff Hodges (who came up with the term 'effective Request-URI'),
4117Jeff Pinner,
4118Jeff Walden,
4119Jim Luther,
4120Jitu Padhye,
4121Joe D. Williams,
4122Joe Gregorio,
4123Joe Orton,
4124Joel Jaeggli,
4125John C. Klensin,
4126John C. Mallery,
4127John Cowan,
4128John Kemp,
4129John Panzer,
4130John Schneider,
4131John Stracke,
4132John Sullivan,
4133Jonas Sicking,
4134Jonathan A. Rees,
4135Jonathan Billington,
4136Jonathan Moore,
4137Jonathan Silvera,
4138Jordi Ros,
4139Joris Dobbelsteen,
4140Josh Cohen,
4141Julien Pierre,
4142Jungshik Shin,
4143Justin Chapweske,
4144Justin Erenkrantz,
4145Justin James,
4146Kalvinder Singh,
4147Karl Dubost,
4148Kathleen Moriarty,
4149Keith Hoffman,
4150Keith Moore,
4151Ken Murchison,
4152Koen Holtman,
4153Konstantin Voronkov,
4154Kris Zyp,
4155Leif Hedstrom,
4156Lionel Morand,
4157Lisa Dusseault,
4158Maciej Stachowiak,
4159Manu Sporny,
4160Marc Schneider,
4161Marc Slemko,
4162Mark Baker,
4163Mark Pauley,
4164Mark Watson,
4165Markus Isomaki,
4166Markus Lanthaler,
4167Martin J. Duerst,
4168Martin Musatov,
4169Martin Nilsson,
4170Martin Thomson,
4171Matt Lynch,
4172Matthew Cox,
4173Matthew Kerwin,
4174Max Clark,
4175Menachem Dodge,
4176Meral Shirazipour,
4177Michael Burrows,
4178Michael Hausenblas,
4179Michael Scharf,
4180Michael Sweet,
4181Michael Tuexen,
4182Michael Welzl,
4183Mike Amundsen,
4184Mike Belshe,
4185Mike Bishop,
4186Mike Kelly,
4187Mike Schinkel,
4188Miles Sabin,
4189Murray S. Kucherawy,
4190Mykyta Yevstifeyev,
4191Nathan Rixham,
4192Nicholas Shanks,
4193Nico Williams,
4194Nicolas Alvarez,
4195Nicolas Mailhot,
4196Noah Slater,
4197Osama Mazahir,
4198Pablo Castro,
4199Pat Hayes,
4200Patrick R. McManus,
4201Paul E. Jones,
4202Paul Hoffman,
4203Paul Marquess,
4204Pete Resnick,
4205Peter Lepeska,
4206Peter Occil,
4207Peter Saint-Andre,
4208Peter Watkins,
4209Phil Archer,
4210Philippe Mougin,
4211Phillip Hallam-Baker,
4212Piotr Dobrogost,
4213Poul-Henning Kamp,
4214Preethi Natarajan,
4215Rajeev Bector,
4216Ray Polk,
4217Reto Bachmann-Gmuer,
4218Richard Barnes,
4219Richard Cyganiak,
4220Robby Simpson,
4221Robert Brewer,
4222Robert Collins,
4223Robert Mattson,
4224Robert O'Callahan,
4225Robert Olofsson,
4226Robert Sayre,
4227Robert Siemer,
4228Robert de Wilde,
4229Roberto Javier Godoy,
4230Roberto Peon,
4231Roland Zink,
4232Ronny Widjaja,
4233Ryan Hamilton,
4234S. Mike Dierken,
4235Salvatore Loreto,
4236Sam Johnston,
4237Sam Pullara,
4238Sam Ruby,
4239Saurabh Kulkarni,
4240Scott Lawrence (who maintained the original issues list),
4241Sean B. Palmer,
4242Sean Turner,
4243Sebastien Barnoud,
4244Shane McCarron,
4245Shigeki Ohtsu,
4246Simon Yarde,
4247Stefan Eissing,
4248Stefan Tilkov,
4249Stefanos Harhalakis,
4250Stephane Bortzmeyer,
4251Stephen Farrell,
4252Stephen Kent,
4253Stephen Ludin,
4254Stuart Williams,
4255Subbu Allamaraju,
4256Subramanian Moonesamy,
4257Susan Hares,
4258Sylvain Hellegouarch,
4259Tapan Divekar,
4260Tatsuhiro Tsujikawa,
4261Tatsuya Hayashi,
4262Ted Hardie,
4263Ted Lemon,
4264Thomas Broyer,
4265Thomas Fossati,
4266Thomas Maslen,
4267Thomas Nadeau,
4268Thomas Nordin,
4269Thomas Roessler,
4270Tim Bray,
4271Tim Morgan,
4272Tim Olsen,
4273Tom Zhou,
4274Travis Snoozy,
4275Tyler Close,
4276Vincent Murphy,
4277Wenbo Zhu,
4278Werner Baumann,
4279Wilbur Streett,
4280Wilfredo Sanchez Vega,
4281William A. Rowe Jr.,
4282William Chan,
4283Willy Tarreau,
4284Xiaoshu Wang,
4285Yaron Goland,
4286Yngve Nysaeter Pettersen,
4287Yoav Nir,
4288Yogesh Bang,
4289Yuchung Cheng,
4290Yutaka Oiwa,
4291Yves Lafon (long-time member of the editor team),
4292Zed A. Shaw, and
4293Zhong Yu.
4294</t>
4295<?ENDINC acks ?>
4296<t>
4297   See <xref target="RFC2616" x:fmt="of" x:sec="16"/> for additional
4298   acknowledgements from prior revisions.
4299</t>
4300</section>
4301
4302</middle>
4303<back>
4304
4305<references title="Normative References">
4306
4307<reference anchor="Part2">
4308  <front>
4309    <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
4310    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4311      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4312      <address><email>fielding@gbiv.com</email></address>
4313    </author>
4314    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4315      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4316      <address><email>julian.reschke@greenbytes.de</email></address>
4317    </author>
4318    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4319  </front>
4320  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
4321  <x:source href="p2-semantics.xml" basename="p2-semantics">
4322    <x:defines>1xx (Informational)</x:defines>
4323    <x:defines>1xx</x:defines>
4324    <x:defines>100 (Continue)</x:defines>
4325    <x:defines>101 (Switching Protocols)</x:defines>
4326    <x:defines>2xx (Successful)</x:defines>
4327    <x:defines>2xx</x:defines>
4328    <x:defines>200 (OK)</x:defines>
4329    <x:defines>203 (Non-Authoritative Information)</x:defines>
4330    <x:defines>204 (No Content)</x:defines>
4331    <x:defines>3xx (Redirection)</x:defines>
4332    <x:defines>3xx</x:defines>
4333    <x:defines>301 (Moved Permanently)</x:defines>
4334    <x:defines>4xx (Client Error)</x:defines>
4335    <x:defines>4xx</x:defines>
4336    <x:defines>400 (Bad Request)</x:defines>
4337    <x:defines>411 (Length Required)</x:defines>
4338    <x:defines>414 (URI Too Long)</x:defines>
4339    <x:defines>417 (Expectation Failed)</x:defines>
4340    <x:defines>426 (Upgrade Required)</x:defines>
4341    <x:defines>501 (Not Implemented)</x:defines>
4342    <x:defines>502 (Bad Gateway)</x:defines>
4343    <x:defines>505 (HTTP Version Not Supported)</x:defines>
4344    <x:defines>Accept-Encoding</x:defines>
4345    <x:defines>Allow</x:defines>
4346    <x:defines>Content-Encoding</x:defines>
4347    <x:defines>Content-Location</x:defines>
4348    <x:defines>Content-Type</x:defines>
4349    <x:defines>Date</x:defines>
4350    <x:defines>Expect</x:defines>
4351    <x:defines>Location</x:defines>
4352    <x:defines>Server</x:defines>
4353    <x:defines>User-Agent</x:defines>
4354  </x:source>
4355</reference>
4356
4357<reference anchor="Part4">
4358  <front>
4359    <title>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</title>
4360    <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
4361      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4362      <address><email>fielding@gbiv.com</email></address>
4363    </author>
4364    <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
4365      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4366      <address><email>julian.reschke@greenbytes.de</email></address>
4367    </author>
4368    <date month="&ID-MONTH;" year="&ID-YEAR;" />
4369  </front>
4370  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" />
4371  <x:source basename="p4-conditional" href="p4-conditional.xml">
4372    <x:defines>304 (Not Modified)</x:defines>
4373    <x:defines>ETag</x:defines>
4374    <x:defines>Last-Modified</x:defines>
4375  </x:source>
4376</reference>
4377
4378<reference anchor="Part5">
4379  <front>
4380    <title>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title>
4381    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4382      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4383      <address><email>fielding@gbiv.com</email></address>
4384    </author>
4385    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4386      <organization abbrev="W3C">World Wide Web Consortium</organization>
4387      <address><email>ylafon@w3.org</email></address>
4388    </author>
4389    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4390      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4391      <address><email>julian.reschke@greenbytes.de</email></address>
4392    </author>
4393    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4394  </front>
4395  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
4396  <x:source href="p5-range.xml" basename="p5-range">
4397    <x:defines>Content-Range</x:defines>
4398  </x:source>
4399</reference>
4400
4401<reference anchor="Part6">
4402  <front>
4403    <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
4404    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4405      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4406      <address><email>fielding@gbiv.com</email></address>
4407    </author>
4408    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
4409      <organization>Akamai</organization>
4410      <address><email>mnot@mnot.net</email></address>
4411    </author>
4412    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4413      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4414      <address><email>julian.reschke@greenbytes.de</email></address>
4415    </author>
4416    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4417  </front>
4418  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
4419  <x:source href="p6-cache.xml" basename="p6-cache">
4420    <x:defines>Cache-Control</x:defines>
4421    <x:defines>Expires</x:defines>
4422  </x:source>
4423</reference>
4424
4425<reference anchor="Part7">
4426  <front>
4427    <title>Hypertext Transfer Protocol (HTTP/1.1): Authentication</title>
4428    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4429      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4430      <address><email>fielding@gbiv.com</email></address>
4431    </author>
4432    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4433      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4434      <address><email>julian.reschke@greenbytes.de</email></address>
4435    </author>
4436    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4437  </front>
4438  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-&ID-VERSION;"/>
4439  <x:source href="p7-auth.xml" basename="p7-auth">
4440    <x:defines>Proxy-Authenticate</x:defines>
4441    <x:defines>Proxy-Authorization</x:defines>
4442  </x:source>
4443</reference>
4444
4445<reference anchor="RFC5234">
4446  <front>
4447    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
4448    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
4449      <organization>Brandenburg InternetWorking</organization>
4450      <address>
4451        <email>dcrocker@bbiw.net</email>
4452      </address> 
4453    </author>
4454    <author initials="P." surname="Overell" fullname="Paul Overell">
4455      <organization>THUS plc.</organization>
4456      <address>
4457        <email>paul.overell@thus.net</email>
4458      </address>
4459    </author>
4460    <date month="January" year="2008"/>
4461  </front>
4462  <seriesInfo name="STD" value="68"/>
4463  <seriesInfo name="RFC" value="5234"/>
4464</reference>
4465
4466<reference anchor="RFC2119">
4467  <front>
4468    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
4469    <author initials="S." surname="Bradner" fullname="Scott Bradner">
4470      <organization>Harvard University</organization>
4471      <address><email>sob@harvard.edu</email></address>
4472    </author>
4473    <date month="March" year="1997"/>
4474  </front>
4475  <seriesInfo name="BCP" value="14"/>
4476  <seriesInfo name="RFC" value="2119"/>
4477</reference>
4478
4479<reference anchor="RFC3986">
4480 <front>
4481  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
4482  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
4483    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4484    <address>
4485       <email>timbl@w3.org</email>
4486       <uri>http://www.w3.org/People/Berners-Lee/</uri>
4487    </address>
4488  </author>
4489  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
4490    <organization abbrev="Day Software">Day Software</organization>
4491    <address>
4492      <email>fielding@gbiv.com</email>
4493      <uri>http://roy.gbiv.com/</uri>
4494    </address>
4495  </author>
4496  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
4497    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
4498    <address>
4499      <email>LMM@acm.org</email>
4500      <uri>http://larry.masinter.net/</uri>
4501    </address>
4502  </author>
4503  <date month='January' year='2005'></date>
4504 </front>
4505 <seriesInfo name="STD" value="66"/>
4506 <seriesInfo name="RFC" value="3986"/>
4507</reference>
4508
4509<reference anchor="RFC0793">
4510  <front>
4511    <title>Transmission Control Protocol</title>
4512    <author initials='J.' surname='Postel' fullname='Jon Postel'>
4513      <organization>University of Southern California (USC)/Information Sciences Institute</organization>
4514    </author>
4515    <date year='1981' month='September' />
4516  </front>
4517  <seriesInfo name='STD' value='7' />
4518  <seriesInfo name='RFC' value='793' />
4519</reference>
4520
4521<reference anchor="USASCII">
4522  <front>
4523    <title>Coded Character Set -- 7-bit American Standard Code for Information Interchange</title>
4524    <author>
4525      <organization>American National Standards Institute</organization>
4526    </author>
4527    <date year="1986"/>
4528  </front>
4529  <seriesInfo name="ANSI" value="X3.4"/>
4530</reference>
4531
4532<reference anchor="RFC1950">
4533  <front>
4534    <title>ZLIB Compressed Data Format Specification version 3.3</title>
4535    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
4536      <organization>Aladdin Enterprises</organization>
4537      <address><email>ghost@aladdin.com</email></address>
4538    </author>
4539    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"/>
4540    <date month="May" year="1996"/>
4541  </front>
4542  <seriesInfo name="RFC" value="1950"/>
4543  <!--<annotation>
4544    RFC 1950 is an Informational RFC, thus it might be less stable than
4545    this specification. On the other hand, this downward reference was
4546    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4547    therefore it is unlikely to cause problems in practice. See also
4548    <xref target="BCP97"/>.
4549  </annotation>-->
4550</reference>
4551
4552<reference anchor="RFC1951">
4553  <front>
4554    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
4555    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
4556      <organization>Aladdin Enterprises</organization>
4557      <address><email>ghost@aladdin.com</email></address>
4558    </author>
4559    <date month="May" year="1996"/>
4560  </front>
4561  <seriesInfo name="RFC" value="1951"/>
4562  <!--<annotation>
4563    RFC 1951 is an Informational RFC, thus it might be less stable than
4564    this specification. On the other hand, this downward reference was
4565    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4566    therefore it is unlikely to cause problems in practice. See also
4567    <xref target="BCP97"/>.
4568  </annotation>-->
4569</reference>
4570
4571<reference anchor="RFC1952">
4572  <front>
4573    <title>GZIP file format specification version 4.3</title>
4574    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
4575      <organization>Aladdin Enterprises</organization>
4576      <address><email>ghost@aladdin.com</email></address>
4577    </author>
4578    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
4579      <address><email>gzip@prep.ai.mit.edu</email></address>
4580    </author>
4581    <author initials="M." surname="Adler" fullname="Mark Adler">
4582      <address><email>madler@alumni.caltech.edu</email></address>
4583    </author>
4584    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
4585      <address><email>ghost@aladdin.com</email></address>
4586    </author>
4587    <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">
4588      <address><email>randeg@alumni.rpi.edu</email></address>
4589    </author>
4590    <date month="May" year="1996"/>
4591  </front>
4592  <seriesInfo name="RFC" value="1952"/>
4593  <!--<annotation>
4594    RFC 1952 is an Informational RFC, thus it might be less stable than
4595    this specification. On the other hand, this downward reference was
4596    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4597    therefore it is unlikely to cause problems in practice. See also
4598    <xref target="BCP97"/>.
4599  </annotation>-->
4600</reference>
4601
4602<reference anchor="Welch">
4603  <front>
4604    <title>A Technique for High Performance Data Compression</title>
4605    <author initials="T.A." surname="Welch" fullname="Terry A. Welch"/>
4606    <date month="June" year="1984"/>
4607  </front>
4608  <seriesInfo name="IEEE Computer" value="17(6)"/>
4609</reference>
4610
4611</references>
4612
4613<references title="Informative References">
4614
4615<reference anchor="ISO-8859-1">
4616  <front>
4617    <title>
4618     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
4619    </title>
4620    <author>
4621      <organization>International Organization for Standardization</organization>
4622    </author>
4623    <date year="1998"/>
4624  </front>
4625  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
4626</reference>
4627
4628<reference anchor='RFC1919'>
4629  <front>
4630    <title>Classical versus Transparent IP Proxies</title>
4631    <author initials='M.' surname='Chatel' fullname='Marc Chatel'>
4632      <address><email>mchatel@pax.eunet.ch</email></address>
4633    </author>
4634    <date year='1996' month='March' />
4635  </front>
4636  <seriesInfo name='RFC' value='1919' />
4637</reference>
4638
4639<reference anchor="RFC1945">
4640  <front>
4641    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
4642    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4643      <organization>MIT, Laboratory for Computer Science</organization>
4644      <address><email>timbl@w3.org</email></address>
4645    </author>
4646    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4647      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4648      <address><email>fielding@ics.uci.edu</email></address>
4649    </author>
4650    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4651      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
4652      <address><email>frystyk@w3.org</email></address>
4653    </author>
4654    <date month="May" year="1996"/>
4655  </front>
4656  <seriesInfo name="RFC" value="1945"/>
4657</reference>
4658
4659<reference anchor="RFC2045">
4660  <front>
4661    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
4662    <author initials="N." surname="Freed" fullname="Ned Freed">
4663      <organization>Innosoft International, Inc.</organization>
4664      <address><email>ned@innosoft.com</email></address>
4665    </author>
4666    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
4667      <organization>First Virtual Holdings</organization>
4668      <address><email>nsb@nsb.fv.com</email></address>
4669    </author>
4670    <date month="November" year="1996"/>
4671  </front>
4672  <seriesInfo name="RFC" value="2045"/>
4673</reference>
4674
4675<reference anchor="RFC2047">
4676  <front>
4677    <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
4678    <author initials="K." surname="Moore" fullname="Keith Moore">
4679      <organization>University of Tennessee</organization>
4680      <address><email>moore@cs.utk.edu</email></address>
4681    </author>
4682    <date month="November" year="1996"/>
4683  </front>
4684  <seriesInfo name="RFC" value="2047"/>
4685</reference>
4686
4687<reference anchor="RFC2068">
4688  <front>
4689    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
4690    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
4691      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4692      <address><email>fielding@ics.uci.edu</email></address>
4693    </author>
4694    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4695      <organization>MIT Laboratory for Computer Science</organization>
4696      <address><email>jg@w3.org</email></address>
4697    </author>
4698    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4699      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
4700      <address><email>mogul@wrl.dec.com</email></address>
4701    </author>
4702    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4703      <organization>MIT Laboratory for Computer Science</organization>
4704      <address><email>frystyk@w3.org</email></address>
4705    </author>
4706    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4707      <organization>MIT Laboratory for Computer Science</organization>
4708      <address><email>timbl@w3.org</email></address>
4709    </author>
4710    <date month="January" year="1997"/>
4711  </front>
4712  <seriesInfo name="RFC" value="2068"/>
4713</reference>
4714
4715<reference anchor="RFC2145">
4716  <front>
4717    <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
4718    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
4719      <organization>Western Research Laboratory</organization>
4720      <address><email>mogul@wrl.dec.com</email></address>
4721    </author>
4722    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4723      <organization>Department of Information and Computer Science</organization>
4724      <address><email>fielding@ics.uci.edu</email></address>
4725    </author>
4726    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4727      <organization>MIT Laboratory for Computer Science</organization>
4728      <address><email>jg@w3.org</email></address>
4729    </author>
4730    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4731      <organization>W3 Consortium</organization>
4732      <address><email>frystyk@w3.org</email></address>
4733    </author>
4734    <date month="May" year="1997"/>
4735  </front>
4736  <seriesInfo name="RFC" value="2145"/>
4737</reference>
4738
4739<reference anchor="RFC2616">
4740  <front>
4741    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
4742    <author initials="R." surname="Fielding" fullname="R. Fielding">
4743      <organization>University of California, Irvine</organization>
4744      <address><email>fielding@ics.uci.edu</email></address>
4745    </author>
4746    <author initials="J." surname="Gettys" fullname="J. Gettys">
4747      <organization>W3C</organization>
4748      <address><email>jg@w3.org</email></address>
4749    </author>
4750    <author initials="J." surname="Mogul" fullname="J. Mogul">
4751      <organization>Compaq Computer Corporation</organization>
4752      <address><email>mogul@wrl.dec.com</email></address>
4753    </author>
4754    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
4755      <organization>MIT Laboratory for Computer Science</organization>
4756      <address><email>frystyk@w3.org</email></address>
4757    </author>
4758    <author initials="L." surname="Masinter" fullname="L. Masinter">
4759      <organization>Xerox Corporation</organization>
4760      <address><email>masinter@parc.xerox.com</email></address>
4761    </author>
4762    <author initials="P." surname="Leach" fullname="P. Leach">
4763      <organization>Microsoft Corporation</organization>
4764      <address><email>paulle@microsoft.com</email></address>
4765    </author>
4766    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
4767      <organization>W3C</organization>
4768      <address><email>timbl@w3.org</email></address>
4769    </author>
4770    <date month="June" year="1999"/>
4771  </front>
4772  <seriesInfo name="RFC" value="2616"/>
4773</reference>
4774
4775<reference anchor='RFC2817'>
4776  <front>
4777    <title>Upgrading to TLS Within HTTP/1.1</title>
4778    <author initials='R.' surname='Khare' fullname='R. Khare'>
4779      <organization>4K Associates / UC Irvine</organization>
4780      <address><email>rohit@4K-associates.com</email></address>
4781    </author>
4782    <author initials='S.' surname='Lawrence' fullname='S. Lawrence'>
4783      <organization>Agranat Systems, Inc.</organization>
4784      <address><email>lawrence@agranat.com</email></address>
4785    </author>
4786    <date year='2000' month='May' />
4787  </front>
4788  <seriesInfo name='RFC' value='2817' />
4789</reference>
4790
4791<reference anchor='RFC2818'>
4792  <front>
4793    <title>HTTP Over TLS</title>
4794    <author initials='E.' surname='Rescorla' fullname='Eric Rescorla'>
4795      <organization>RTFM, Inc.</organization>
4796      <address><email>ekr@rtfm.com</email></address>
4797    </author>
4798    <date year='2000' month='May' />
4799  </front>
4800  <seriesInfo name='RFC' value='2818' />
4801</reference>
4802
4803<reference anchor='RFC3040'>
4804  <front>
4805    <title>Internet Web Replication and Caching Taxonomy</title>
4806    <author initials='I.' surname='Cooper' fullname='I. Cooper'>
4807      <organization>Equinix, Inc.</organization>
4808    </author>
4809    <author initials='I.' surname='Melve' fullname='I. Melve'>
4810      <organization>UNINETT</organization>
4811    </author>
4812    <author initials='G.' surname='Tomlinson' fullname='G. Tomlinson'>
4813      <organization>CacheFlow Inc.</organization>
4814    </author>
4815    <date year='2001' month='January' />
4816  </front>
4817  <seriesInfo name='RFC' value='3040' />
4818</reference>
4819
4820<reference anchor='BCP90'>
4821  <front>
4822    <title>Registration Procedures for Message Header Fields</title>
4823    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
4824      <organization>Nine by Nine</organization>
4825      <address><email>GK-IETF@ninebynine.org</email></address>
4826    </author>
4827    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
4828      <organization>BEA Systems</organization>
4829      <address><email>mnot@pobox.com</email></address>
4830    </author>
4831    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
4832      <organization>HP Labs</organization>
4833      <address><email>JeffMogul@acm.org</email></address>
4834    </author>
4835    <date year='2004' month='September' />
4836  </front>
4837  <seriesInfo name='BCP' value='90' />
4838  <seriesInfo name='RFC' value='3864' />
4839</reference>
4840
4841<reference anchor='RFC4033'>
4842  <front>
4843    <title>DNS Security Introduction and Requirements</title>
4844    <author initials='R.' surname='Arends' fullname='R. Arends'/>
4845    <author initials='R.' surname='Austein' fullname='R. Austein'/>
4846    <author initials='M.' surname='Larson' fullname='M. Larson'/>
4847    <author initials='D.' surname='Massey' fullname='D. Massey'/>
4848    <author initials='S.' surname='Rose' fullname='S. Rose'/>
4849    <date year='2005' month='March' />
4850  </front>
4851  <seriesInfo name='RFC' value='4033' />
4852</reference>
4853
4854<reference anchor="BCP13">
4855  <front>
4856    <title>Media Type Specifications and Registration Procedures</title>
4857    <author initials="N." surname="Freed" fullname="Ned Freed">
4858      <organization>Oracle</organization>
4859      <address>
4860        <email>ned+ietf@mrochek.com</email>
4861      </address>
4862    </author>
4863    <author initials="J." surname="Klensin" fullname="John C. Klensin">
4864      <address>
4865        <email>john+ietf@jck.com</email>
4866      </address>
4867    </author>
4868    <author initials="T." surname="Hansen" fullname="Tony Hansen">
4869      <organization>AT&amp;T Laboratories</organization>
4870      <address>
4871        <email>tony+mtsuffix@maillennium.att.com</email>
4872      </address>
4873    </author>
4874    <date year="2013" month="January"/>
4875  </front>
4876  <seriesInfo name="BCP" value="13"/>
4877  <seriesInfo name="RFC" value="6838"/>
4878</reference>
4879
4880<reference anchor='BCP115'>
4881  <front>
4882    <title>Guidelines and Registration Procedures for New URI Schemes</title>
4883    <author initials='T.' surname='Hansen' fullname='T. Hansen'>
4884      <organization>AT&amp;T Laboratories</organization>
4885      <address>
4886        <email>tony+urireg@maillennium.att.com</email>
4887      </address>
4888    </author>
4889    <author initials='T.' surname='Hardie' fullname='T. Hardie'>
4890      <organization>Qualcomm, Inc.</organization>
4891      <address>
4892        <email>hardie@qualcomm.com</email>
4893      </address>
4894    </author>
4895    <author initials='L.' surname='Masinter' fullname='L. Masinter'>
4896      <organization>Adobe Systems</organization>
4897      <address>
4898        <email>LMM@acm.org</email>
4899      </address>
4900    </author>
4901    <date year='2006' month='February' />
4902  </front>
4903  <seriesInfo name='BCP' value='115' />
4904  <seriesInfo name='RFC' value='4395' />
4905</reference>
4906
4907<reference anchor='RFC4559'>
4908  <front>
4909    <title>SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows</title>
4910    <author initials='K.' surname='Jaganathan' fullname='K. Jaganathan'/>
4911    <author initials='L.' surname='Zhu' fullname='L. Zhu'/>
4912    <author initials='J.' surname='Brezak' fullname='J. Brezak'/>
4913    <date year='2006' month='June' />
4914  </front>
4915  <seriesInfo name='RFC' value='4559' />
4916</reference>
4917
4918<reference anchor='RFC5226'>
4919  <front>
4920    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
4921    <author initials='T.' surname='Narten' fullname='T. Narten'>
4922      <organization>IBM</organization>
4923      <address><email>narten@us.ibm.com</email></address>
4924    </author>
4925    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
4926      <organization>Google</organization>
4927      <address><email>Harald@Alvestrand.no</email></address>
4928    </author>
4929    <date year='2008' month='May' />
4930  </front>
4931  <seriesInfo name='BCP' value='26' />
4932  <seriesInfo name='RFC' value='5226' />
4933</reference>
4934
4935<reference anchor='RFC5246'>
4936   <front>
4937      <title>The Transport Layer Security (TLS) Protocol Version 1.2</title>
4938      <author initials='T.' surname='Dierks' fullname='T. Dierks'>
4939         <organization />
4940      </author>
4941      <author initials='E.' surname='Rescorla' fullname='E. Rescorla'>
4942         <organization>RTFM, Inc.</organization>
4943      </author>
4944      <date year='2008' month='August' />
4945   </front>
4946   <seriesInfo name='RFC' value='5246' />
4947</reference>
4948
4949<reference anchor="RFC5322">
4950  <front>
4951    <title>Internet Message Format</title>
4952    <author initials="P." surname="Resnick" fullname="P. Resnick">
4953      <organization>Qualcomm Incorporated</organization>
4954    </author>
4955    <date year="2008" month="October"/>
4956  </front>
4957  <seriesInfo name="RFC" value="5322"/>
4958</reference>
4959
4960<reference anchor="RFC6265">
4961  <front>
4962    <title>HTTP State Management Mechanism</title>
4963    <author initials="A." surname="Barth" fullname="Adam Barth">
4964      <organization abbrev="U.C. Berkeley">
4965        University of California, Berkeley
4966      </organization>
4967      <address><email>abarth@eecs.berkeley.edu</email></address>
4968    </author>
4969    <date year="2011" month="April" />
4970  </front>
4971  <seriesInfo name="RFC" value="6265"/>
4972</reference>
4973
4974<reference anchor='RFC6585'>
4975  <front>
4976    <title>Additional HTTP Status Codes</title>
4977    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
4978      <organization>Rackspace</organization>
4979    </author>
4980    <author initials='R.' surname='Fielding' fullname='R. Fielding'>
4981      <organization>Adobe</organization>
4982    </author>
4983    <date year='2012' month='April' />
4984   </front>
4985   <seriesInfo name='RFC' value='6585' />
4986</reference>
4987
4988<!--<reference anchor='BCP97'>
4989  <front>
4990    <title>Handling Normative References to Standards-Track Documents</title>
4991    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
4992      <address>
4993        <email>klensin+ietf@jck.com</email>
4994      </address>
4995    </author>
4996    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
4997      <organization>MIT</organization>
4998      <address>
4999        <email>hartmans-ietf@mit.edu</email>
5000      </address>
5001    </author>
5002    <date year='2007' month='June' />
5003  </front>
5004  <seriesInfo name='BCP' value='97' />
5005  <seriesInfo name='RFC' value='4897' />
5006</reference>-->
5007
5008<reference anchor="Kri2001" target="http://arxiv.org/abs/cs.SE/0105018">
5009  <front>
5010    <title>HTTP Cookies: Standards, Privacy, and Politics</title>
5011    <author initials="D." surname="Kristol" fullname="David M. Kristol"/>
5012    <date year="2001" month="November"/>
5013  </front>
5014  <seriesInfo name="ACM Transactions on Internet Technology" value="1(2)"/>
5015</reference>
5016
5017</references>
5018
5019
5020<section title="HTTP Version History" anchor="compatibility">
5021<t>
5022   HTTP has been in use by the World-Wide Web global information initiative
5023   since 1990. The first version of HTTP, later referred to as HTTP/0.9,
5024   was a simple protocol for hypertext data transfer across the Internet
5025   with only a single request method (GET) and no metadata.
5026   HTTP/1.0, as defined by <xref target="RFC1945"/>, added a range of request
5027   methods and MIME-like messaging that could include metadata about the data
5028   transferred and modifiers on the request/response semantics. However,
5029   HTTP/1.0 did not sufficiently take into consideration the effects of
5030   hierarchical proxies, caching, the need for persistent connections, or
5031   name-based virtual hosts. The proliferation of incompletely-implemented
5032   applications calling themselves "HTTP/1.0" further necessitated a
5033   protocol version change in order for two communicating applications
5034   to determine each other's true capabilities.
5035</t>
5036<t>
5037   HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent
5038   requirements that enable reliable implementations, adding only
5039   those new features that will either be safely ignored by an HTTP/1.0
5040   recipient or only sent when communicating with a party advertising
5041   conformance with HTTP/1.1.
5042</t>
5043<t>
5044   It is beyond the scope of a protocol specification to mandate
5045   conformance with previous versions. HTTP/1.1 was deliberately
5046   designed, however, to make supporting previous versions easy.
5047   We would expect a general-purpose HTTP/1.1 server to understand
5048   any valid request in the format of HTTP/1.0 and respond appropriately
5049   with an HTTP/1.1 message that only uses features understood (or
5050   safely ignored) by HTTP/1.0 clients.  Likewise, we would expect
5051   an HTTP/1.1 client to understand any valid HTTP/1.0 response.
5052</t>
5053<t>
5054   Since HTTP/0.9 did not support header fields in a request,
5055   there is no mechanism for it to support name-based virtual
5056   hosts (selection of resource by inspection of the <x:ref>Host</x:ref> header
5057   field).  Any server that implements name-based virtual hosts
5058   ought to disable support for HTTP/0.9.  Most requests that
5059   appear to be HTTP/0.9 are, in fact, badly constructed HTTP/1.x
5060   requests wherein a buggy client failed to properly encode
5061   linear whitespace found in a URI reference and placed in
5062   the request-target.
5063</t>
5064
5065<section title="Changes from HTTP/1.0" anchor="changes.from.1.0">
5066<t>
5067   This section summarizes major differences between versions HTTP/1.0
5068   and HTTP/1.1.
5069</t>
5070
5071<section title="Multi-homed Web Servers" anchor="changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">
5072<t>
5073   The requirements that clients and servers support the <x:ref>Host</x:ref>
5074   header field (<xref target="header.host"/>), report an error if it is
5075   missing from an HTTP/1.1 request, and accept absolute URIs (<xref target="request-target"/>)
5076   are among the most important changes defined by HTTP/1.1.
5077</t>
5078<t>
5079   Older HTTP/1.0 clients assumed a one-to-one relationship of IP
5080   addresses and servers; there was no other established mechanism for
5081   distinguishing the intended server of a request than the IP address
5082   to which that request was directed. The <x:ref>Host</x:ref> header field was
5083   introduced during the development of HTTP/1.1 and, though it was
5084   quickly implemented by most HTTP/1.0 browsers, additional requirements
5085   were placed on all HTTP/1.1 requests in order to ensure complete
5086   adoption.  At the time of this writing, most HTTP-based services
5087   are dependent upon the Host header field for targeting requests.
5088</t>
5089</section>
5090
5091<section title="Keep-Alive Connections" anchor="compatibility.with.http.1.0.persistent.connections">
5092<t>
5093   In HTTP/1.0, each connection is established by the client prior to the
5094   request and closed by the server after sending the response. However, some
5095   implementations implement the explicitly negotiated ("Keep-Alive") version
5096   of persistent connections described in <xref x:sec="19.7.1" x:fmt="of"
5097   target="RFC2068"/>.
5098</t>
5099<t>
5100   Some clients and servers might wish to be compatible with these previous
5101   approaches to persistent connections, by explicitly negotiating for them
5102   with a "Connection: keep-alive" request header field. However, some
5103   experimental implementations of HTTP/1.0 persistent connections are faulty;
5104   for example, if an HTTP/1.0 proxy server doesn't understand
5105   <x:ref>Connection</x:ref>, it will erroneously forward that header field
5106   to the next inbound server, which would result in a hung connection.
5107</t>
5108<t>
5109   One attempted solution was the introduction of a Proxy-Connection header
5110   field, targeted specifically at proxies. In practice, this was also
5111   unworkable, because proxies are often deployed in multiple layers, bringing
5112   about the same problem discussed above.
5113</t>
5114<t>
5115   As a result, clients are encouraged not to send the Proxy-Connection header
5116   field in any requests.
5117</t>
5118<t>
5119   Clients are also encouraged to consider the use of Connection: keep-alive
5120   in requests carefully; while they can enable persistent connections with
5121   HTTP/1.0 servers, clients using them will need to monitor the
5122   connection for "hung" requests (which indicate that the client ought stop
5123   sending the header field), and this mechanism ought not be used by clients
5124   at all when a proxy is being used.
5125</t>
5126</section>
5127
5128<section title="Introduction of Transfer-Encoding" anchor="introduction.of.transfer-encoding">
5129<t>
5130   HTTP/1.1 introduces the <x:ref>Transfer-Encoding</x:ref> header field
5131   (<xref target="header.transfer-encoding"/>).
5132   Transfer codings need to be decoded prior to forwarding an HTTP message
5133   over a MIME-compliant protocol.
5134</t>
5135</section>
5136
5137</section>
5138
5139<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
5140<t>
5141  HTTP's approach to error handling has been explained.
5142  (<xref target="conformance" />)
5143</t>
5144<t>
5145  The HTTP-version ABNF production has been clarified to be case-sensitive.
5146  Additionally, version numbers has been restricted to single digits, due
5147  to the fact that implementations are known to handle multi-digit version
5148  numbers incorrectly.
5149  (<xref target="http.version"/>)
5150</t>
5151<t>
5152  Userinfo (i.e., username and password) are now disallowed in HTTP and
5153  HTTPS URIs, because of security issues related to their transmission on the
5154  wire.
5155  (<xref target="http.uri" />)
5156</t>
5157<t>
5158  The HTTPS URI scheme is now defined by this specification; previously,
5159  it was done in  <xref target="RFC2818" x:fmt="of" x:sec="2.4"/>.
5160  Furthermore, it implies end-to-end security.
5161  (<xref target="https.uri"/>)
5162</t>
5163<t>
5164  HTTP messages can be (and often are) buffered by implementations; despite
5165  it sometimes being available as a stream, HTTP is fundamentally a
5166  message-oriented protocol.
5167  Minimum supported sizes for various protocol elements have been
5168  suggested, to improve interoperability.
5169  (<xref target="http.message" />)
5170</t>
5171<t>
5172  Invalid whitespace around field-names is now required to be rejected,
5173  because accepting it represents a security vulnerability.
5174  The ABNF productions defining header fields now only list the field value.
5175  (<xref target="header.fields"/>)
5176</t>
5177<t>
5178  Rules about implicit linear whitespace between certain grammar productions
5179  have been removed; now whitespace is only allowed where specifically
5180  defined in the ABNF.
5181  (<xref target="whitespace"/>)
5182</t>
5183<t>
5184  Header fields that span multiple lines ("line folding") are deprecated.
5185  (<xref target="field.parsing" />)
5186</t>
5187<t> 
5188  The NUL octet is no longer allowed in comment and quoted-string text, and
5189  handling of backslash-escaping in them has been clarified.
5190  The quoted-pair rule no longer allows escaping control characters other than
5191  HTAB.
5192  Non-ASCII content in header fields and the reason phrase has been obsoleted
5193  and made opaque (the TEXT rule was removed).
5194  (<xref target="field.components"/>)
5195</t> 
5196<t>
5197  Bogus "<x:ref>Content-Length</x:ref>" header fields are now required to be
5198  handled as errors by recipients.
5199  (<xref target="header.content-length"/>)
5200</t>
5201<t>
5202  The algorithm for determining the message body length has been clarified
5203  to indicate all of the special cases (e.g., driven by methods or status
5204  codes) that affect it, and that new protocol elements cannot define such
5205  special cases.
5206  CONNECT is a new, special case in determining message body length.
5207  "multipart/byteranges" is no longer a way of determining message body length
5208  detection.
5209  (<xref target="message.body.length"/>)
5210</t>
5211<t>
5212  The "identity" transfer coding token has been removed.
5213  (Sections <xref format="counter" target="message.body"/> and
5214  <xref format="counter" target="transfer.codings"/>)
5215</t>
5216<t>
5217  Chunk length does not include the count of the octets in the
5218  chunk header and trailer.
5219  Line folding in chunk extensions is  disallowed.
5220  (<xref target="chunked.encoding"/>)
5221</t>
5222<t>
5223  The meaning of the "deflate" content coding has been clarified.
5224  (<xref target="deflate.coding" />)
5225</t>
5226<t>
5227  The segment + query components of RFC 3986 have been used to define the
5228  request-target, instead of abs_path from RFC 1808.
5229  The asterisk-form of the request-target is only allowed with the OPTIONS
5230  method.
5231  (<xref target="request-target"/>)
5232</t>
5233<t>
5234  The term "Effective Request URI" has been introduced.
5235  (<xref target="effective.request.uri" />)
5236</t>
5237<t>
5238  Gateways do not need to generate <x:ref>Via</x:ref> header fields anymore.
5239  (<xref target="header.via"/>)
5240</t>
5241<t>
5242  Exactly when "close" connection options have to be sent has been clarified.
5243  Also, "hop-by-hop" header fields are required to appear in the Connection header
5244  field; just because they're defined as hop-by-hop in this specification
5245  doesn't exempt them.
5246  (<xref target="header.connection"/>)
5247</t>
5248<t>
5249  The limit of two connections per server has been removed.
5250  An idempotent sequence of requests is no longer required to be retried.
5251  The requirement to retry requests under certain circumstances when the
5252  server prematurely closes the connection has been removed.
5253  Also, some extraneous requirements about when servers are allowed to close
5254  connections prematurely have been removed.
5255  (<xref target="persistent.connections"/>)
5256</t>
5257<t>
5258  The semantics of the <x:ref>Upgrade</x:ref> header field is now defined in
5259  responses other than 101 (this was incorporated from <xref
5260  target="RFC2817"/>). Furthermore, the ordering in the field value is now
5261  significant.
5262  (<xref target="header.upgrade"/>)
5263</t>
5264<t>
5265  Empty list elements in list productions (e.g., a list header field containing
5266  ", ,") have been deprecated.
5267  (<xref target="abnf.extension"/>)
5268</t>
5269<t>
5270  Registration of Transfer Codings now requires IETF Review
5271  (<xref target="transfer.coding.registry"/>)
5272</t>
5273<t>
5274  This specification now defines the Upgrade Token Registry, previously
5275  defined in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>.
5276  (<xref target="upgrade.token.registry"/>)
5277</t>
5278<t>
5279  The expectation to support HTTP/0.9 requests has been removed.
5280  (<xref target="compatibility"/>)
5281</t>
5282<t>
5283  Issues with the Keep-Alive and Proxy-Connection header fields in requests
5284  are pointed out, with use of the latter being discouraged altogether.
5285  (<xref target="compatibility.with.http.1.0.persistent.connections" />)
5286</t>
5287</section>
5288</section>
5289
5290<?BEGININC p1-messaging.abnf-appendix ?>
5291<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
5292<figure>
5293<artwork type="abnf" name="p1-messaging.parsed-abnf">
5294<x:ref>BWS</x:ref> = OWS
5295
5296<x:ref>Connection</x:ref> = *( "," OWS ) connection-option *( OWS "," [ OWS
5297 connection-option ] )
5298<x:ref>Content-Length</x:ref> = 1*DIGIT
5299
5300<x:ref>HTTP-message</x:ref> = start-line *( header-field CRLF ) CRLF [ message-body
5301 ]
5302<x:ref>HTTP-name</x:ref> = %x48.54.54.50 ; HTTP
5303<x:ref>HTTP-version</x:ref> = HTTP-name "/" DIGIT "." DIGIT
5304<x:ref>Host</x:ref> = uri-host [ ":" port ]
5305
5306<x:ref>OWS</x:ref> = *( SP / HTAB )
5307
5308<x:ref>RWS</x:ref> = 1*( SP / HTAB )
5309
5310<x:ref>TE</x:ref> = [ ( "," / t-codings ) *( OWS "," [ OWS t-codings ] ) ]
5311<x:ref>Trailer</x:ref> = *( "," OWS ) field-name *( OWS "," [ OWS field-name ] )
5312<x:ref>Transfer-Encoding</x:ref> = *( "," OWS ) transfer-coding *( OWS "," [ OWS
5313 transfer-coding ] )
5314
5315<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [RFC3986], Section 4.1&gt;
5316<x:ref>Upgrade</x:ref> = *( "," OWS ) protocol *( OWS "," [ OWS protocol ] )
5317
5318<x:ref>Via</x:ref> = *( "," OWS ) ( received-protocol RWS received-by [ RWS comment
5319 ] ) *( OWS "," [ OWS ( received-protocol RWS received-by [ RWS
5320 comment ] ) ] )
5321
5322<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
5323<x:ref>absolute-form</x:ref> = absolute-URI
5324<x:ref>absolute-path</x:ref> = 1*( "/" segment )
5325<x:ref>asterisk-form</x:ref> = "*"
5326<x:ref>authority</x:ref> = &lt;authority, defined in [RFC3986], Section 3.2&gt;
5327<x:ref>authority-form</x:ref> = authority
5328
5329<x:ref>chunk</x:ref> = chunk-size [ chunk-ext ] CRLF chunk-data CRLF
5330<x:ref>chunk-data</x:ref> = 1*OCTET
5331<x:ref>chunk-ext</x:ref> = *( ";" chunk-ext-name [ "=" chunk-ext-val ] )
5332<x:ref>chunk-ext-name</x:ref> = token
5333<x:ref>chunk-ext-val</x:ref> = token / quoted-string
5334<x:ref>chunk-size</x:ref> = 1*HEXDIG
5335<x:ref>chunked-body</x:ref> = *chunk last-chunk trailer-part CRLF
5336<x:ref>comment</x:ref> = "(" *( ctext / quoted-pair / comment ) ")"
5337<x:ref>connection-option</x:ref> = token
5338<x:ref>ctext</x:ref> = HTAB / SP / %x21-27 ; '!'-'''
5339 / %x2A-5B ; '*'-'['
5340 / %x5D-7E ; ']'-'~'
5341 / obs-text
5342
5343<x:ref>field-content</x:ref> = *( HTAB / SP / VCHAR / obs-text )
5344<x:ref>field-name</x:ref> = token
5345<x:ref>field-value</x:ref> = *( field-content / obs-fold )
5346<x:ref>fragment</x:ref> = &lt;fragment, defined in [RFC3986], Section 3.5&gt;
5347
5348<x:ref>header-field</x:ref> = field-name ":" OWS field-value OWS
5349<x:ref>http-URI</x:ref> = "http://" authority path-abempty [ "?" query ] [ "#"
5350 fragment ]
5351<x:ref>https-URI</x:ref> = "https://" authority path-abempty [ "?" query ] [ "#"
5352 fragment ]
5353
5354<x:ref>last-chunk</x:ref> = 1*"0" [ chunk-ext ] CRLF
5355
5356<x:ref>message-body</x:ref> = *OCTET
5357<x:ref>method</x:ref> = token
5358
5359<x:ref>obs-fold</x:ref> = CRLF ( SP / HTAB )
5360<x:ref>obs-text</x:ref> = %x80-FF
5361<x:ref>origin-form</x:ref> = absolute-path [ "?" query ]
5362
5363<x:ref>partial-URI</x:ref> = relative-part [ "?" query ]
5364<x:ref>path-abempty</x:ref> = &lt;path-abempty, defined in [RFC3986], Section 3.3&gt;
5365<x:ref>port</x:ref> = &lt;port, defined in [RFC3986], Section 3.2.3&gt;
5366<x:ref>protocol</x:ref> = protocol-name [ "/" protocol-version ]
5367<x:ref>protocol-name</x:ref> = token
5368<x:ref>protocol-version</x:ref> = token
5369<x:ref>pseudonym</x:ref> = token
5370
5371<x:ref>qdtext</x:ref> = HTAB / SP / "!" / %x23-5B ; '#'-'['
5372 / %x5D-7E ; ']'-'~'
5373 / obs-text
5374<x:ref>query</x:ref> = &lt;query, defined in [RFC3986], Section 3.4&gt;
5375<x:ref>quoted-pair</x:ref> = "\" ( HTAB / SP / VCHAR / obs-text )
5376<x:ref>quoted-string</x:ref> = DQUOTE *( qdtext / quoted-pair ) DQUOTE
5377
5378<x:ref>rank</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
5379<x:ref>reason-phrase</x:ref> = *( HTAB / SP / VCHAR / obs-text )
5380<x:ref>received-by</x:ref> = ( uri-host [ ":" port ] ) / pseudonym
5381<x:ref>received-protocol</x:ref> = [ protocol-name "/" ] protocol-version
5382<x:ref>relative-part</x:ref> = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;
5383<x:ref>request-line</x:ref> = method SP request-target SP HTTP-version CRLF
5384<x:ref>request-target</x:ref> = origin-form / absolute-form / authority-form /
5385 asterisk-form
5386
5387<x:ref>segment</x:ref> = &lt;segment, defined in [RFC3986], Section 3.3&gt;
5388<x:ref>special</x:ref> = "(" / ")" / "&lt;" / "&gt;" / "@" / "," / ";" / ":" / "\" /
5389 DQUOTE / "/" / "[" / "]" / "?" / "=" / "{" / "}"
5390<x:ref>start-line</x:ref> = request-line / status-line
5391<x:ref>status-code</x:ref> = 3DIGIT
5392<x:ref>status-line</x:ref> = HTTP-version SP status-code SP reason-phrase CRLF
5393
5394<x:ref>t-codings</x:ref> = "trailers" / ( transfer-coding [ t-ranking ] )
5395<x:ref>t-ranking</x:ref> = OWS ";" OWS "q=" rank
5396<x:ref>tchar</x:ref> = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*" / "+" / "-" / "." /
5397 "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
5398<x:ref>token</x:ref> = 1*tchar
5399<x:ref>trailer-part</x:ref> = *( header-field CRLF )
5400<x:ref>transfer-coding</x:ref> = "chunked" / "compress" / "deflate" / "gzip" /
5401 transfer-extension
5402<x:ref>transfer-extension</x:ref> = token *( OWS ";" OWS transfer-parameter )
5403<x:ref>transfer-parameter</x:ref> = token BWS "=" BWS ( token / quoted-string )
5404
5405<x:ref>uri-host</x:ref> = &lt;host, defined in [RFC3986], Section 3.2.2&gt;
5406</artwork>
5407</figure>
5408</section>
5409<?ENDINC p1-messaging.abnf-appendix ?>
5410
5411<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
5412
5413<section title="Since RFC 2616">
5414<t>
5415  Changes up to the IETF Last Call draft are summarized
5416  in <eref target="http://trac.tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-24#appendix-C"/>.
5417</t>
5418</section>
5419
5420<section title="Since draft-ietf-httpbis-p1-messaging-24" anchor="changes.since.24">
5421<t>
5422  Closed issues:
5423  <list style="symbols">
5424    <t>
5425      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/502"/>:
5426      "APPSDIR review of draft-ietf-httpbis-p1-messaging-24"
5427    </t>
5428    <t>
5429      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/507"/>:
5430      "integer value parsing"
5431    </t>
5432    <t>
5433      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/517"/>:
5434      "move IANA registrations to correct draft"
5435    </t>
5436  </list>
5437</t>
5438</section>
5439
5440<section title="Since draft-ietf-httpbis-p1-messaging-25" anchor="changes.since.25">
5441<t>
5442  Closed issues:
5443  <list style="symbols">
5444    <t>
5445      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/526"/>:
5446      "check media type registration templates"
5447    </t>
5448    <t>
5449      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/528"/>:
5450      "Redundant rule quoted-str-nf"
5451    </t>
5452    <t>
5453      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/540"/>:
5454      "clarify ABNF layering"
5455    </t>
5456    <t>
5457      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/541"/>:
5458      "use of 'word' ABNF production"
5459    </t>
5460    <t>
5461      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/542"/>:
5462      "improve introduction of list rule"
5463    </t>
5464    <t>
5465      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/544"/>:
5466      "moving 2616/2068/2145 to historic"
5467    </t>
5468  </list>
5469</t>
5470</section>
5471</section>
5472
5473</back>
5474</rfc>
Note: See TracBrowser for help on using the repository browser.