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

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

update affiliations and document titles in references

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 243.6 KB
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=''>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns=''>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns=''>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns=''>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns=''>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns=''>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns=''>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns=''>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns=''>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns=''>SHOULD NOT</bcp14>">
14  <!ENTITY ID-VERSION "latest">
15  <!ENTITY ID-MONTH "September">
16  <!ENTITY ID-YEAR "2012">
17  <!ENTITY mdash "&#8212;">
18  <!ENTITY Note "<x:h xmlns:x=''>Note:</x:h>">
19  <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' xmlns:x=''/>">
20  <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#response.cacheability' xmlns:x=''/>">
21  <!ENTITY payload                "<xref target='Part2' x:rel='#payload' xmlns:x=''/>">
22  <!ENTITY media-types            "<xref target='Part2' x:rel='#media.types' xmlns:x=''/>">
23  <!ENTITY content-codings        "<xref target='Part2' x:rel='#content.codings' xmlns:x=''/>">
24  <!ENTITY CONNECT                "<xref target='Part2' x:rel='#CONNECT' xmlns:x=''/>">
25  <!ENTITY content.negotiation    "<xref target='Part2' x:rel='#content.negotiation' xmlns:x=''/>">
26  <!ENTITY diff-mime              "<xref target='Part2' x:rel='#differences.between.http.and.mime' xmlns:x=''/>">
27  <!ENTITY representation         "<xref target='Part2' x:rel='#representation' xmlns:x=''/>">
28  <!ENTITY HEAD                   "<xref target='Part2' x:rel='#HEAD' xmlns:x=''/>">
29  <!ENTITY header-allow           "<xref target='Part2' x:rel='#header.allow' xmlns:x=''/>">
30  <!ENTITY header-cache-control   "<xref target='Part6' x:rel='#header.cache-control' xmlns:x=''/>">
31  <!ENTITY header-content-encoding    "<xref target='Part2' x:rel='#header.content-encoding' xmlns:x=''/>">
32  <!ENTITY header-content-location    "<xref target='Part2' x:rel='#header.content-location' xmlns:x=''/>">
33  <!ENTITY header-content-range   "<xref target='Part5' x:rel='#header.content-range' xmlns:x=''/>">
34  <!ENTITY header-content-type    "<xref target='Part2' x:rel='#header.content-type' xmlns:x=''/>">
35  <!ENTITY header-date            "<xref target='Part2' x:rel='' xmlns:x=''/>">
36  <!ENTITY header-etag            "<xref target='Part4' x:rel='#header.etag' xmlns:x=''/>">
37  <!ENTITY header-expires         "<xref target='Part6' x:rel='#header.expires' xmlns:x=''/>">
38  <!ENTITY header-last-modified   "<xref target='Part4' x:rel='#header.last-modified' xmlns:x=''/>">
39  <!ENTITY header-mime-version    "<xref target='Part2' x:rel='#mime-version' xmlns:x=''/>">
40  <!ENTITY header-pragma          "<xref target='Part6' x:rel='#header.pragma' xmlns:x=''/>">
41  <!ENTITY header-proxy-authenticate  "<xref target='Part7' x:rel='#header.proxy-authenticate' xmlns:x=''/>">
42  <!ENTITY header-proxy-authorization "<xref target='Part7' x:rel='#header.proxy-authorization' xmlns:x=''/>">
43  <!ENTITY header-server          "<xref target='Part2' x:rel='#header.server' xmlns:x=''/>">
44  <!ENTITY header-warning         "<xref target='Part6' x:rel='#header.warning' xmlns:x=''/>">
45  <!ENTITY idempotent-methods     "<xref target='Part2' x:rel='#idempotent.methods' xmlns:x=''/>">
46  <!ENTITY methods                "<xref target='Part2' x:rel='#methods' xmlns:x=''/>">
47  <!ENTITY OPTIONS                "<xref target='Part2' x:rel='#OPTIONS' xmlns:x=''/>">
48  <!ENTITY qvalue                 "<xref target='Part2' x:rel='#quality.values' xmlns:x=''/>">
49  <!ENTITY resource               "<xref target='Part2' x:rel='#resource' xmlns:x=''/>">
50  <!ENTITY status-codes           "<xref target='Part2' x:rel='' xmlns:x=''/>">
51  <!ENTITY status-1xx             "<xref target='Part2' x:rel='#status.1xx' xmlns:x=''/>">
52  <!ENTITY status-203             "<xref target='Part2' x:rel='#status.203' xmlns:x=''/>">
53  <!ENTITY status-3xx             "<xref target='Part2' x:rel='#status.3xx' xmlns:x=''/>">
54  <!ENTITY status-304             "<xref target='Part4' x:rel='#status.304' xmlns:x=''/>">
55  <!ENTITY status-4xx             "<xref target='Part2' x:rel='#status.4xx' xmlns:x=''/>">
56  <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x=''/>">
57  <!ENTITY iana-header-registry   "<xref target='Part2' x:rel='#header.field.registry' xmlns:x=''/>">
59<?rfc toc="yes" ?>
60<?rfc symrefs="yes" ?>
61<?rfc sortrefs="yes" ?>
62<?rfc compact="yes"?>
63<?rfc subcompact="no" ?>
64<?rfc linkmailto="no" ?>
65<?rfc editing="no" ?>
66<?rfc comments="yes"?>
67<?rfc inline="yes"?>
68<?rfc rfcedstyle="yes"?>
69<?rfc-ext allow-markup-in-artwork="yes" ?>
70<?rfc-ext include-references-in-index="yes" ?>
71<rfc obsoletes="2145,2616" updates="2817" category="std" x:maturity-level="proposed"
72     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"
73     xmlns:x=''>
74<x:link rel="next" basename="p2-semantics"/>
75<x:feedback template="{docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/>
78  <title abbrev="HTTP/1.1 Message Syntax and Routing">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
80  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
81    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
82    <address>
83      <postal>
84        <street>345 Park Ave</street>
85        <city>San Jose</city>
86        <region>CA</region>
87        <code>95110</code>
88        <country>USA</country>
89      </postal>
90      <email></email>
91      <uri></uri>
92    </address>
93  </author>
95  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
96    <organization abbrev="W3C">World Wide Web Consortium</organization>
97    <address>
98      <postal>
99        <street>W3C / ERCIM</street>
100        <street>2004, rte des Lucioles</street>
101        <city>Sophia-Antipolis</city>
102        <region>AM</region>
103        <code>06902</code>
104        <country>France</country>
105      </postal>
106      <email></email>
107      <uri></uri>
108    </address>
109  </author>
111  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
112    <organization abbrev="greenbytes">greenbytes GmbH</organization>
113    <address>
114      <postal>
115        <street>Hafenweg 16</street>
116        <city>Muenster</city><region>NW</region><code>48155</code>
117        <country>Germany</country>
118      </postal>
119      <email></email>
120      <uri></uri>
121    </address>
122  </author>
124  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
125  <workgroup>HTTPbis Working Group</workgroup>
129   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
130   distributed, collaborative, hypertext information systems. HTTP has been in
131   use by the World Wide Web global information initiative since 1990.
132   This document provides an overview of HTTP architecture and its associated
133   terminology, defines the "http" and "https" Uniform Resource Identifier
134   (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements,
135   and describes general security concerns for implementations.
139<note title="Editorial Note (To be removed by RFC Editor)">
140  <t>
141    Discussion of this draft takes place on the HTTPBIS working group
142    mailing list (, which is archived at
143    <eref target=""/>.
144  </t>
145  <t>
146    The current issues list is at
147    <eref target=""/> and related
148    documents (including fancy diffs) can be found at
149    <eref target=""/>.
150  </t>
151  <t>
152    The changes in this draft are summarized in <xref target="changes.since.20"/>.
153  </t>
157<section title="Introduction" anchor="introduction">
159   The Hypertext Transfer Protocol (HTTP) is an application-level
160   request/response protocol that uses extensible semantics and MIME-like
161   message payloads for flexible interaction with network-based hypertext
162   information systems. This document is the first in a series of documents
163   that collectively form the HTTP/1.1 specification:
164   <list style="empty">
165    <t>RFC xxx1: Message Syntax and Routing</t>
166    <t><xref target="Part2" x:fmt="none">RFC xxx2</xref>: Semantics and Content</t>
167    <t><xref target="Part4" x:fmt="none">RFC xxx3</xref>: Conditional Requests</t>
168    <t><xref target="Part5" x:fmt="none">RFC xxx4</xref>: Range Requests</t>
169    <t><xref target="Part6" x:fmt="none">RFC xxx5</xref>: Caching</t>
170    <t><xref target="Part7" x:fmt="none">RFC xxx6</xref>: Authentication</t>
171   </list>
174   This HTTP/1.1 specification obsoletes and moves to historic status
175   <xref target="RFC2616" x:fmt="none">RFC 2616</xref>, its predecessor
176   <xref target="RFC2068" x:fmt="none">RFC 2068</xref>,
177   <xref target="RFC2145" x:fmt="none">RFC 2145</xref> (on HTTP versioning),
178   and <xref target="RFC2817" x:fmt="none">RFC 2817</xref> (on using CONNECT
179   for TLS upgrades).
182   HTTP is a generic interface protocol for information systems. It is
183   designed to hide the details of how a service is implemented by presenting
184   a uniform interface to clients that is independent of the types of
185   resources provided. Likewise, servers do not need to be aware of each
186   client's purpose: an HTTP request can be considered in isolation rather
187   than being associated with a specific type of client or a predetermined
188   sequence of application steps. The result is a protocol that can be used
189   effectively in many different contexts and for which implementations can
190   evolve independently over time.
193   HTTP is also designed for use as an intermediation protocol for translating
194   communication to and from non-HTTP information systems.
195   HTTP proxies and gateways can provide access to alternative information
196   services by translating their diverse protocols into a hypertext
197   format that can be viewed and manipulated by clients in the same way
198   as HTTP services.
201   One consequence of HTTP flexibility is that the protocol cannot be
202   defined in terms of what occurs behind the interface. Instead, we
203   are limited to defining the syntax of communication, the intent
204   of received communication, and the expected behavior of recipients.
205   If the communication is considered in isolation, then successful
206   actions ought to be reflected in corresponding changes to the
207   observable interface provided by servers. However, since multiple
208   clients might act in parallel and perhaps at cross-purposes, we
209   cannot require that such changes be observable beyond the scope
210   of a single response.
213   This document describes the architectural elements that are used or
214   referred to in HTTP, defines the "http" and "https" URI schemes,
215   describes overall network operation and connection management,
216   and defines HTTP message framing and forwarding requirements.
217   Our goal is to define all of the mechanisms necessary for HTTP message
218   handling that are independent of message semantics, thereby defining the
219   complete set of requirements for message parsers and
220   message-forwarding intermediaries.
224<section title="Requirement Notation" anchor="intro.requirements">
226   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
227   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
228   document are to be interpreted as described in <xref target="RFC2119"/>.
231   Conformance criteria and considerations regarding error handling
232   are defined in <xref target="conformance"/>.
236<section title="Syntax Notation" anchor="notation">
237<iref primary="true" item="Grammar" subitem="ALPHA"/>
238<iref primary="true" item="Grammar" subitem="CR"/>
239<iref primary="true" item="Grammar" subitem="CRLF"/>
240<iref primary="true" item="Grammar" subitem="CTL"/>
241<iref primary="true" item="Grammar" subitem="DIGIT"/>
242<iref primary="true" item="Grammar" subitem="DQUOTE"/>
243<iref primary="true" item="Grammar" subitem="HEXDIG"/>
244<iref primary="true" item="Grammar" subitem="HTAB"/>
245<iref primary="true" item="Grammar" subitem="LF"/>
246<iref primary="true" item="Grammar" subitem="OCTET"/>
247<iref primary="true" item="Grammar" subitem="SP"/>
248<iref primary="true" item="Grammar" subitem="VCHAR"/>
250   This specification uses the Augmented Backus-Naur Form (ABNF) notation
251   of <xref target="RFC5234"/> with the list rule extension defined in
252   <xref target="abnf.extension"/>.  <xref target="collected.abnf"/> shows
253   the collected ABNF with the list rule expanded.
255<t anchor="core.rules">
256  <x:anchor-alias value="ALPHA"/>
257  <x:anchor-alias value="CTL"/>
258  <x:anchor-alias value="CR"/>
259  <x:anchor-alias value="CRLF"/>
260  <x:anchor-alias value="DIGIT"/>
261  <x:anchor-alias value="DQUOTE"/>
262  <x:anchor-alias value="HEXDIG"/>
263  <x:anchor-alias value="HTAB"/>
264  <x:anchor-alias value="LF"/>
265  <x:anchor-alias value="OCTET"/>
266  <x:anchor-alias value="SP"/>
267  <x:anchor-alias value="VCHAR"/>
268   The following core rules are included by
269   reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
270   ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
271   DIGIT (decimal 0-9), DQUOTE (double quote),
272   HEXDIG (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed),
273   OCTET (any 8-bit sequence of data), SP (space), and
274   VCHAR (any visible <xref target="USASCII"/> character).
277   As a convention, ABNF rule names prefixed with "obs-" denote
278   "obsolete" grammar rules that appear for historical reasons.
283<section title="Architecture" anchor="architecture">
285   HTTP was created for the World Wide Web architecture
286   and has evolved over time to support the scalability needs of a worldwide
287   hypertext system. Much of that architecture is reflected in the terminology
288   and syntax productions used to define HTTP.
291<section title="Client/Server Messaging" anchor="operation">
292<iref primary="true" item="client"/>
293<iref primary="true" item="server"/>
294<iref primary="true" item="connection"/>
296   HTTP is a stateless request/response protocol that operates by exchanging
297   <x:dfn>messages</x:dfn> (<xref target="http.message"/>) across a reliable
298   transport or session-layer
299   "<x:dfn>connection</x:dfn>" (<xref target=""/>).
300   An HTTP "<x:dfn>client</x:dfn>" is a program that establishes a connection
301   to a server for the purpose of sending one or more HTTP requests.
302   An HTTP "<x:dfn>server</x:dfn>" is a program that accepts connections
303   in order to service HTTP requests by sending HTTP responses.
305<iref primary="true" item="user agent"/>
306<iref primary="true" item="origin server"/>
307<iref primary="true" item="browser"/>
308<iref primary="true" item="spider"/>
309<iref primary="true" item="sender"/>
310<iref primary="true" item="recipient"/>
312   The terms client and server refer only to the roles that
313   these programs perform for a particular connection.  The same program
314   might act as a client on some connections and a server on others.  We use
315   the term "<x:dfn>user agent</x:dfn>" to refer to the program that initiates a request,
316   such as a WWW browser, editor, or spider (web-traversing robot), and
317   the term "<x:dfn>origin server</x:dfn>" to refer to the program that can originate
318   authoritative responses to a request.  For general requirements, we use
319   the term "<x:dfn>sender</x:dfn>" to refer to whichever component sent a given message
320   and the term "<x:dfn>recipient</x:dfn>" to refer to any component that receives the
321   message.
324   HTTP relies upon the Uniform Resource Identifier (URI)
325   standard <xref target="RFC3986"/> to indicate the target resource
326   (<xref target="target-resource"/>) and relationships between resources.
327   Messages are passed in a format similar to that used by Internet mail
328   <xref target="RFC5322"/> and the Multipurpose Internet Mail Extensions
329   (MIME) <xref target="RFC2045"/> (see &diff-mime; for the differences
330   between HTTP and MIME messages).
333   Most HTTP communication consists of a retrieval request (GET) for
334   a representation of some resource identified by a URI.  In the
335   simplest case, this might be accomplished via a single bidirectional
336   connection (===) between the user agent (UA) and the origin server (O).
338<figure><artwork type="drawing">
339         request   &gt;
340    <x:highlight>UA</x:highlight> ======================================= <x:highlight>O</x:highlight>
341                                &lt;   response
343<iref primary="true" item="message"/>
344<iref primary="true" item="request"/>
345<iref primary="true" item="response"/>
347   A client sends an HTTP request to a server in the form of a <x:dfn>request</x:dfn>
348   message, beginning with a request-line that includes a method, URI, and
349   protocol version (<xref target="request.line"/>),
350   followed by header fields containing
351   request modifiers, client information, and representation metadata
352   (<xref target="header.fields"/>),
353   an empty line to indicate the end of the header section, and finally
354   a message body containing the payload body (if any,
355   <xref target="message.body"/>).
358   A server responds to a client's request by sending one or more HTTP
359   <x:dfn>response</x:dfn>
360   messages, each beginning with a status line that
361   includes the protocol version, a success or error code, and textual
362   reason phrase (<xref target="status.line"/>),
363   possibly followed by header fields containing server
364   information, resource metadata, and representation metadata
365   (<xref target="header.fields"/>),
366   an empty line to indicate the end of the header section, and finally
367   a message body containing the payload body (if any,
368   <xref target="message.body"/>).
371   A connection might be used for multiple request/response exchanges,
372   as defined in <xref target="persistent.connections"/>.
375   The following example illustrates a typical message exchange for a
376   GET request on the URI "":
379client request:
380</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
381GET /hello.txt HTTP/1.1
382User-Agent: curl/7.16.3 libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3
384Accept-Language: en, mi
388server response:
389</preamble><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
390HTTP/1.1 200 OK
391Date: Mon, 27 Jul 2009 12:28:53 GMT
392Server: Apache
393Last-Modified: Wed, 22 Jul 2009 19:15:56 GMT
394ETag: "34aa387-d-1568eb00"
395Accept-Ranges: bytes
396Content-Length: <x:length-of target="exbody"/>
397Vary: Accept-Encoding
398Content-Type: text/plain
400<x:span anchor="exbody">Hello World!
404<section title="Implementation Diversity" anchor="implementation-diversity">
406   When considering the design of HTTP, it is easy to fall into a trap of
407   thinking that all user agents are general-purpose browsers and all origin
408   servers are large public websites. That is not the case in practice.
409   Common HTTP user agents include household appliances, stereos, scales,
410   firmware update scripts, command-line programs, mobile apps,
411   and communication devices in a multitude of shapes and sizes.  Likewise,
412   common HTTP origin servers include home automation units, configurable
413   networking components, office machines, autonomous robots, news feeds,
414   traffic cameras, ad selectors, and video delivery platforms.
417   The term "user agent" does not imply that there is a human user directly
418   interacting with the software agent at the time of a request. In many
419   cases, a user agent is installed or configured to run in the background
420   and save its results for later inspection (or save only a subset of those
421   results that might be interesting or erroneous). Spiders, for example, are
422   typically given a start URI and configured to follow certain behavior while
423   crawling the Web as a hypertext graph.
426   The implementation diversity of HTTP means that we cannot assume the
427   user agent can make interactive suggestions to a user or provide adequate
428   warning for security or privacy options.  In the few cases where this
429   specification requires reporting of errors to the user, it is acceptable
430   for such reporting to only be observable in an error console or log file.
431   Likewise, requirements that an automated action be confirmed by the user
432   before proceeding can me met via advance configuration choices,
433   run-time options, or simply not proceeding with the unsafe action.
437<section title="Intermediaries" anchor="intermediaries">
438<iref primary="true" item="intermediary"/>
440   HTTP enables the use of intermediaries to satisfy requests through
441   a chain of connections.  There are three common forms of HTTP
442   <x:dfn>intermediary</x:dfn>: proxy, gateway, and tunnel.  In some cases,
443   a single intermediary might act as an origin server, proxy, gateway,
444   or tunnel, switching behavior based on the nature of each request.
446<figure><artwork type="drawing">
447         &gt;             &gt;             &gt;             &gt;
448    <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>
449               &lt;             &lt;             &lt;             &lt;
452   The figure above shows three intermediaries (A, B, and C) between the
453   user agent and origin server. A request or response message that
454   travels the whole chain will pass through four separate connections.
455   Some HTTP communication options
456   might apply only to the connection with the nearest, non-tunnel
457   neighbor, only to the end-points of the chain, or to all connections
458   along the chain. Although the diagram is linear, each participant might
459   be engaged in multiple, simultaneous communications. For example, B
460   might be receiving requests from many clients other than A, and/or
461   forwarding requests to servers other than C, at the same time that it
462   is handling A's request.
465<iref primary="true" item="upstream"/><iref primary="true" item="downstream"/>
466<iref primary="true" item="inbound"/><iref primary="true" item="outbound"/>
467   We use the terms "<x:dfn>upstream</x:dfn>" and "<x:dfn>downstream</x:dfn>"
468   to describe various requirements in relation to the directional flow of a
469   message: all messages flow from upstream to downstream.
470   Likewise, we use the terms inbound and outbound to refer to
471   directions in relation to the request path:
472   "<x:dfn>inbound</x:dfn>" means toward the origin server and
473   "<x:dfn>outbound</x:dfn>" means toward the user agent.
475<t><iref primary="true" item="proxy"/>
476   A "<x:dfn>proxy</x:dfn>" is a message forwarding agent that is selected by the
477   client, usually via local configuration rules, to receive requests
478   for some type(s) of absolute URI and attempt to satisfy those
479   requests via translation through the HTTP interface.  Some translations
480   are minimal, such as for proxy requests for "http" URIs, whereas
481   other requests might require translation to and from entirely different
482   application-level protocols. Proxies are often used to group an
483   organization's HTTP requests through a common intermediary for the
484   sake of security, annotation services, or shared caching.
487<iref primary="true" item="transforming proxy"/>
488<iref primary="true" item="non-transforming proxy"/>
489   An HTTP-to-HTTP proxy is called a "<x:dfn>transforming proxy</x:dfn>" if it is designed
490   or configured to modify request or response messages in a semantically
491   meaningful way (i.e., modifications, beyond those required by normal
492   HTTP processing, that change the message in a way that would be
493   significant to the original sender or potentially significant to
494   downstream recipients).  For example, a transforming proxy might be
495   acting as a shared annotation server (modifying responses to include
496   references to a local annotation database), a malware filter, a
497   format transcoder, or an intranet-to-Internet privacy filter.  Such
498   transformations are presumed to be desired by the client (or client
499   organization) that selected the proxy and are beyond the scope of
500   this specification.  However, when a proxy is not intended to transform
501   a given message, we use the term "<x:dfn>non-transforming proxy</x:dfn>" to target
502   requirements that preserve HTTP message semantics. See &status-203; and
503   &header-warning; for status and warning codes related to transformations.
505<t><iref primary="true" item="gateway"/><iref primary="true" item="reverse proxy"/>
506<iref primary="true" item="accelerator"/>
507   A "<x:dfn>gateway</x:dfn>" (a.k.a., "<x:dfn>reverse proxy</x:dfn>")
508   is a receiving agent that acts
509   as a layer above some other server(s) and translates the received
510   requests to the underlying server's protocol.  Gateways are often
511   used to encapsulate legacy or untrusted information services, to
512   improve server performance through "<x:dfn>accelerator</x:dfn>" caching, and to
513   enable partitioning or load-balancing of HTTP services across
514   multiple machines.
517   A gateway behaves as an origin server on its outbound connection and
518   as a user agent on its inbound connection.
519   All HTTP requirements applicable to an origin server
520   also apply to the outbound communication of a gateway.
521   A gateway communicates with inbound servers using any protocol that
522   it desires, including private extensions to HTTP that are outside
523   the scope of this specification.  However, an HTTP-to-HTTP gateway
524   that wishes to interoperate with third-party HTTP servers &MUST;
525   conform to HTTP user agent requirements on the gateway's inbound
526   connection and &MUST; implement the <x:ref>Connection</x:ref>
527   (<xref target="header.connection"/>) and <x:ref>Via</x:ref>
528   (<xref target="header.via"/>) header fields for both connections.
530<t><iref primary="true" item="tunnel"/>
531   A "<x:dfn>tunnel</x:dfn>" acts as a blind relay between two connections
532   without changing the messages. Once active, a tunnel is not
533   considered a party to the HTTP communication, though the tunnel might
534   have been initiated by an HTTP request. A tunnel ceases to exist when
535   both ends of the relayed connection are closed. Tunnels are used to
536   extend a virtual connection through an intermediary, such as when
537   Transport Layer Security (TLS, <xref target="RFC5246"/>) is used to
538   establish confidential communication through a shared firewall proxy.
540<t><iref primary="true" item="interception proxy"/>
541<iref primary="true" item="transparent proxy"/>
542<iref primary="true" item="captive portal"/>
543   The above categories for intermediary only consider those acting as
544   participants in the HTTP communication.  There are also intermediaries
545   that can act on lower layers of the network protocol stack, filtering or
546   redirecting HTTP traffic without the knowledge or permission of message
547   senders. Network intermediaries often introduce security flaws or
548   interoperability problems by violating HTTP semantics.  For example, an
549   "<x:dfn>interception proxy</x:dfn>" <xref target="RFC3040"/> (also commonly
550   known as a "<x:dfn>transparent proxy</x:dfn>" <xref target="RFC1919"/> or
551   "<x:dfn>captive portal</x:dfn>")
552   differs from an HTTP proxy because it is not selected by the client.
553   Instead, an interception proxy filters or redirects outgoing TCP port 80
554   packets (and occasionally other common port traffic).
555   Interception proxies are commonly found on public network access points,
556   as a means of enforcing account subscription prior to allowing use of
557   non-local Internet services, and within corporate firewalls to enforce
558   network usage policies.
559   They are indistinguishable from a man-in-the-middle attack.
562   HTTP is defined as a stateless protocol, meaning that each request message
563   can be understood in isolation.  Many implementations depend on HTTP's
564   stateless design in order to reuse proxied connections or dynamically
565   load balance requests across multiple servers.  Hence, servers &MUST-NOT;
566   assume that two requests on the same connection are from the same user
567   agent unless the connection is secured and specific to that agent.
568   Some non-standard HTTP extensions (e.g., <xref target="RFC4559"/>) have
569   been known to violate this requirement, resulting in security and
570   interoperability problems.
574<section title="Caches" anchor="caches">
575<iref primary="true" item="cache"/>
577   A "<x:dfn>cache</x:dfn>" is a local store of previous response messages and the
578   subsystem that controls its message storage, retrieval, and deletion.
579   A cache stores cacheable responses in order to reduce the response
580   time and network bandwidth consumption on future, equivalent
581   requests. Any client or server &MAY; employ a cache, though a cache
582   cannot be used by a server while it is acting as a tunnel.
585   The effect of a cache is that the request/response chain is shortened
586   if one of the participants along the chain has a cached response
587   applicable to that request. The following illustrates the resulting
588   chain if B has a cached copy of an earlier response from O (via C)
589   for a request which has not been cached by UA or A.
591<figure><artwork type="drawing">
592            &gt;             &gt;
593       <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>
594                  &lt;             &lt;
596<t><iref primary="true" item="cacheable"/>
597   A response is "<x:dfn>cacheable</x:dfn>" if a cache is allowed to store a copy of
598   the response message for use in answering subsequent requests.
599   Even when a response is cacheable, there might be additional
600   constraints placed by the client or by the origin server on when
601   that cached response can be used for a particular request. HTTP
602   requirements for cache behavior and cacheable responses are
603   defined in &caching-overview;. 
606   There are a wide variety of architectures and configurations
607   of caches and proxies deployed across the World Wide Web and
608   inside large organizations. These systems include national hierarchies
609   of proxy caches to save transoceanic bandwidth, systems that
610   broadcast or multicast cache entries, organizations that distribute
611   subsets of cached data via optical media, and so on.
615<section title="Conformance and Error Handling" anchor="conformance">
617   This specification targets conformance criteria according to the role of
618   a participant in HTTP communication.  Hence, HTTP requirements are placed
619   on senders, recipients, clients, servers, user agents, intermediaries,
620   origin servers, proxies, gateways, or caches, depending on what behavior
621   is being constrained by the requirement. Additional (social) requirements
622   are placed on implementations, resource owners, and protocol element
623   registrations when they apply beyond the scope of a single communication.
626   The verb "generate" is used instead of "send" where a requirement
627   differentiates between creating a protocol element and merely forwarding a
628   received element downstream.
631   An implementation is considered conformant if it complies with all of the
632   requirements associated with the roles it partakes in HTTP. Note that
633   SHOULD-level requirements are relevant here, unless one of the documented
634   exceptions is applicable.
637   Conformance applies to both the syntax and semantics of HTTP protocol
638   elements. A sender &MUST-NOT; generate protocol elements that convey a
639   meaning that is known by that sender to be false. A sender &MUST-NOT;
640   generate protocol elements that do not match the grammar defined by the
641   ABNF rules for those protocol elements that are applicable to the sender's
642   role. If a received protocol element is processed, the recipient &MUST; be
643   able to parse any value that would match the ABNF rules for that protocol
644   element, excluding only those rules not applicable to the recipient's role.
647   Unless noted otherwise, a recipient &MAY; attempt to recover a usable
648   protocol element from an invalid construct.  HTTP does not define
649   specific error handling mechanisms except when they have a direct impact
650   on security, since different applications of the protocol require
651   different error handling strategies.  For example, a Web browser might
652   wish to transparently recover from a response where the
653   <x:ref>Location</x:ref> header field doesn't parse according to the ABNF,
654   whereas a systems control client might consider any form of error recovery
655   to be dangerous.
659<section title="Protocol Versioning" anchor="http.version">
660  <x:anchor-alias value="HTTP-version"/>
661  <x:anchor-alias value="HTTP-name"/>
663   HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate
664   versions of the protocol. This specification defines version "1.1".
665   The protocol version as a whole indicates the sender's conformance
666   with the set of requirements laid out in that version's corresponding
667   specification of HTTP.
670   The version of an HTTP message is indicated by an HTTP-version field
671   in the first line of the message. HTTP-version is case-sensitive.
673<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-version"/><iref primary="true" item="Grammar" subitem="HTTP-name"/>
674  <x:ref>HTTP-version</x:ref>  = <x:ref>HTTP-name</x:ref> "/" <x:ref>DIGIT</x:ref> "." <x:ref>DIGIT</x:ref>
675  <x:ref>HTTP-name</x:ref>     = <x:abnf-char-sequence>"HTTP"</x:abnf-char-sequence> ; "HTTP", case-sensitive
678   The HTTP version number consists of two decimal digits separated by a "."
679   (period or decimal point).  The first digit ("major version") indicates the
680   HTTP messaging syntax, whereas the second digit ("minor version") indicates
681   the highest minor version to which the sender is
682   conformant and able to understand for future communication.  The minor
683   version advertises the sender's communication capabilities even when the
684   sender is only using a backwards-compatible subset of the protocol,
685   thereby letting the recipient know that more advanced features can
686   be used in response (by servers) or in future requests (by clients).
689   When an HTTP/1.1 message is sent to an HTTP/1.0 recipient
690   <xref target="RFC1945"/> or a recipient whose version is unknown,
691   the HTTP/1.1 message is constructed such that it can be interpreted
692   as a valid HTTP/1.0 message if all of the newer features are ignored.
693   This specification places recipient-version requirements on some
694   new features so that a conformant sender will only use compatible
695   features until it has determined, through configuration or the
696   receipt of a message, that the recipient supports HTTP/1.1.
699   The interpretation of a header field does not change between minor
700   versions of the same major HTTP version, though the default
701   behavior of a recipient in the absence of such a field can change.
702   Unless specified otherwise, header fields defined in HTTP/1.1 are
703   defined for all versions of HTTP/1.x.  In particular, the <x:ref>Host</x:ref>
704   and <x:ref>Connection</x:ref> header fields ought to be implemented by all
705   HTTP/1.x implementations whether or not they advertise conformance with
706   HTTP/1.1.
709   New header fields can be defined such that, when they are
710   understood by a recipient, they might override or enhance the
711   interpretation of previously defined header fields.  When an
712   implementation receives an unrecognized header field, the recipient
713   &MUST; ignore that header field for local processing regardless of
714   the message's HTTP version.  An unrecognized header field received
715   by a proxy &MUST; be forwarded downstream unless the header field's
716   field-name is listed in the message's <x:ref>Connection</x:ref> header field
717   (see <xref target="header.connection"/>).
718   These requirements allow HTTP's functionality to be enhanced without
719   requiring prior update of deployed intermediaries.
722   Intermediaries that process HTTP messages (i.e., all intermediaries
723   other than those acting as tunnels) &MUST; send their own HTTP-version
724   in forwarded messages.  In other words, they &MUST-NOT; blindly
725   forward the first line of an HTTP message without ensuring that the
726   protocol version in that message matches a version to which that
727   intermediary is conformant for both the receiving and
728   sending of messages.  Forwarding an HTTP message without rewriting
729   the HTTP-version might result in communication errors when downstream
730   recipients use the message sender's version to determine what features
731   are safe to use for later communication with that sender.
734   An HTTP client &SHOULD; send a request version equal to the highest
735   version to which the client is conformant and
736   whose major version is no higher than the highest version supported
737   by the server, if this is known.  An HTTP client &MUST-NOT; send a
738   version to which it is not conformant.
741   An HTTP client &MAY; send a lower request version if it is known that
742   the server incorrectly implements the HTTP specification, but only
743   after the client has attempted at least one normal request and determined
744   from the response status or header fields (e.g., <x:ref>Server</x:ref>) that
745   the server improperly handles higher request versions.
748   An HTTP server &SHOULD; send a response version equal to the highest
749   version to which the server is conformant and
750   whose major version is less than or equal to the one received in the
751   request.  An HTTP server &MUST-NOT; send a version to which it is not
752   conformant.  A server &MAY; send a <x:ref>505 (HTTP Version Not
753   Supported)</x:ref> response if it cannot send a response using the
754   major version used in the client's request.
757   An HTTP server &MAY; send an HTTP/1.0 response to an HTTP/1.0 request
758   if it is known or suspected that the client incorrectly implements the
759   HTTP specification and is incapable of correctly processing later
760   version responses, such as when a client fails to parse the version
761   number correctly or when an intermediary is known to blindly forward
762   the HTTP-version even when it doesn't conform to the given minor
763   version of the protocol. Such protocol downgrades &SHOULD-NOT; be
764   performed unless triggered by specific client attributes, such as when
765   one or more of the request header fields (e.g., <x:ref>User-Agent</x:ref>)
766   uniquely match the values sent by a client known to be in error.
769   The intention of HTTP's versioning design is that the major number
770   will only be incremented if an incompatible message syntax is
771   introduced, and that the minor number will only be incremented when
772   changes made to the protocol have the effect of adding to the message
773   semantics or implying additional capabilities of the sender.  However,
774   the minor version was not incremented for the changes introduced between
775   <xref target="RFC2068"/> and <xref target="RFC2616"/>, and this revision
776   is specifically avoiding any such changes to the protocol.
780<section title="Uniform Resource Identifiers" anchor="uri">
781<iref primary="true" item="resource"/>
783   Uniform Resource Identifiers (URIs) <xref target="RFC3986"/> are used
784   throughout HTTP as the means for identifying resources (&resource;).
785   URI references are used to target requests, indicate redirects, and define
786   relationships.
788  <x:anchor-alias value="URI-reference"/>
789  <x:anchor-alias value="absolute-URI"/>
790  <x:anchor-alias value="relative-part"/>
791  <x:anchor-alias value="authority"/>
792  <x:anchor-alias value="path-abempty"/>
793  <x:anchor-alias value="path-absolute"/>
794  <x:anchor-alias value="port"/>
795  <x:anchor-alias value="query"/>
796  <x:anchor-alias value="uri-host"/>
797  <x:anchor-alias value="partial-URI"/>
799   This specification adopts the definitions of "URI-reference",
800   "absolute-URI", "relative-part", "port", "host",
801   "path-abempty", "path-absolute", "query", and "authority" from the
802   URI generic syntax.
803   In addition, we define a partial-URI rule for protocol elements
804   that allow a relative URI but not a fragment.
806<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="path-absolute"/><iref primary="true" item="Grammar" subitem="port"/><iref primary="true" item="Grammar" subitem="query"/><iref primary="true" item="Grammar" subitem="uri-host"/><iref primary="true" item="Grammar" subitem="partial-URI"><!--exported production--></iref>
807  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in <xref target="RFC3986" x:fmt="," x:sec="4.1"/>&gt;
808  <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in <xref target="RFC3986" x:fmt="," x:sec="4.3"/>&gt;
809  <x:ref>relative-part</x:ref> = &lt;relative-part, defined in <xref target="RFC3986" x:fmt="," x:sec="4.2"/>&gt;
810  <x:ref>authority</x:ref>     = &lt;authority, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2"/>&gt;
811  <x:ref>path-abempty</x:ref>  = &lt;path-abempty, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
812  <x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
813  <x:ref>port</x:ref>          = &lt;port, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.3"/>&gt;
814  <x:ref>query</x:ref>         = &lt;query, defined in <xref target="RFC3986" x:fmt="," x:sec="3.4"/>&gt;
815  <x:ref>uri-host</x:ref>      = &lt;host, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>&gt;
817  <x:ref>partial-URI</x:ref>   = relative-part [ "?" query ]
820   Each protocol element in HTTP that allows a URI reference will indicate
821   in its ABNF production whether the element allows any form of reference
822   (URI-reference), only a URI in absolute form (absolute-URI), only the
823   path and optional query components, or some combination of the above.
824   Unless otherwise indicated, URI references are parsed
825   relative to the effective request URI
826   (<xref target="effective.request.uri"/>).
829<section title="http URI scheme" anchor="http.uri">
830  <x:anchor-alias value="http-URI"/>
831  <iref item="http URI scheme" primary="true"/>
832  <iref item="URI scheme" subitem="http" primary="true"/>
834   The "http" URI scheme is hereby defined for the purpose of minting
835   identifiers according to their association with the hierarchical
836   namespace governed by a potential HTTP origin server listening for
837   TCP connections on a given port.
839<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http-URI"><!--terminal production--></iref>
840  <x:ref>http-URI</x:ref> = "http:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
843   The HTTP origin server is identified by the generic syntax's
844   <x:ref>authority</x:ref> component, which includes a host identifier
845   and optional TCP port (<xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>).
846   The remainder of the URI, consisting of both the hierarchical path
847   component and optional query component, serves as an identifier for
848   a potential resource within that origin server's name space.
851   If the host identifier is provided as an IP literal or IPv4 address,
852   then the origin server is any listener on the indicated TCP port at
853   that IP address. If host is a registered name, then that name is
854   considered an indirect identifier and the recipient might use a name
855   resolution service, such as DNS, to find the address of a listener
856   for that host.
857   The host &MUST-NOT; be empty; if an "http" URI is received with an
858   empty host, then it &MUST; be rejected as invalid.
859   If the port subcomponent is empty or not given, then TCP port 80 is
860   assumed (the default reserved port for WWW services).
863   Regardless of the form of host identifier, access to that host is not
864   implied by the mere presence of its name or address. The host might or might
865   not exist and, even when it does exist, might or might not be running an
866   HTTP server or listening to the indicated port. The "http" URI scheme
867   makes use of the delegated nature of Internet names and addresses to
868   establish a naming authority (whatever entity has the ability to place
869   an HTTP server at that Internet name or address) and allows that
870   authority to determine which names are valid and how they might be used.
873   When an "http" URI is used within a context that calls for access to the
874   indicated resource, a client &MAY; attempt access by resolving
875   the host to an IP address, establishing a TCP connection to that address
876   on the indicated port, and sending an HTTP request message
877   (<xref target="http.message"/>) containing the URI's identifying data
878   (<xref target="message.routing"/>) to the server.
879   If the server responds to that request with a non-interim HTTP response
880   message, as described in &status-codes;, then that response
881   is considered an authoritative answer to the client's request.
884   Although HTTP is independent of the transport protocol, the "http"
885   scheme is specific to TCP-based services because the name delegation
886   process depends on TCP for establishing authority.
887   An HTTP service based on some other underlying connection protocol
888   would presumably be identified using a different URI scheme, just as
889   the "https" scheme (below) is used for resources that require an
890   end-to-end secured connection. Other protocols might also be used to
891   provide access to "http" identified resources &mdash; it is only the
892   authoritative interface used for mapping the namespace that is
893   specific to TCP.
896   The URI generic syntax for authority also includes a deprecated
897   userinfo subcomponent (<xref target="RFC3986" x:fmt="," x:sec="3.2.1"/>)
898   for including user authentication information in the URI.  Some
899   implementations make use of the userinfo component for internal
900   configuration of authentication information, such as within command
901   invocation options, configuration files, or bookmark lists, even
902   though such usage might expose a user identifier or password.
903   Senders &MUST-NOT; include a userinfo subcomponent (and its "@"
904   delimiter) when transmitting an "http" URI in a message.  Recipients
905   of HTTP messages that contain a URI reference &SHOULD; parse for the
906   existence of userinfo and treat its presence as an error, likely
907   indicating that the deprecated subcomponent is being used to obscure
908   the authority for the sake of phishing attacks.
912<section title="https URI scheme" anchor="https.uri">
913   <x:anchor-alias value="https-URI"/>
914   <iref item="https URI scheme"/>
915   <iref item="URI scheme" subitem="https"/>
917   The "https" URI scheme is hereby defined for the purpose of minting
918   identifiers according to their association with the hierarchical
919   namespace governed by a potential HTTP origin server listening to a
920   given TCP port for TLS-secured connections <xref target="RFC5246"/>.
923   All of the requirements listed above for the "http" scheme are also
924   requirements for the "https" scheme, except that a default TCP port
925   of 443 is assumed if the port subcomponent is empty or not given,
926   and the TCP connection &MUST; be secured, end-to-end, through the
927   use of strong encryption prior to sending the first HTTP request.
929<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="https-URI"><!--terminal production--></iref>
930  <x:ref>https-URI</x:ref> = "https:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
933   Unlike the "http" scheme, responses to "https" identified requests
934   are never "public" and thus &MUST-NOT; be reused for shared caching.
935   They can, however, be reused in a private cache if the message is
936   cacheable by default in HTTP or specifically indicated as such by
937   the Cache-Control header field (&header-cache-control;).
940   Resources made available via the "https" scheme have no shared
941   identity with the "http" scheme even if their resource identifiers
942   indicate the same authority (the same host listening to the same
943   TCP port).  They are distinct name spaces and are considered to be
944   distinct origin servers.  However, an extension to HTTP that is
945   defined to apply to entire host domains, such as the Cookie protocol
946   <xref target="RFC6265"/>, can allow information
947   set by one service to impact communication with other services
948   within a matching group of host domains.
951   The process for authoritative access to an "https" identified
952   resource is defined in <xref target="RFC2818"/>.
956<section title="http and https URI Normalization and Comparison" anchor="uri.comparison">
958   Since the "http" and "https" schemes conform to the URI generic syntax,
959   such URIs are normalized and compared according to the algorithm defined
960   in <xref target="RFC3986" x:fmt="," x:sec="6"/>, using the defaults
961   described above for each scheme.
964   If the port is equal to the default port for a scheme, the normal
965   form is to elide the port subcomponent. Likewise, an empty path
966   component is equivalent to an absolute path of "/", so the normal
967   form is to provide a path of "/" instead. The scheme and host
968   are case-insensitive and normally provided in lowercase; all
969   other components are compared in a case-sensitive manner.
970   Characters other than those in the "reserved" set are equivalent
971   to their percent-encoded octets (see <xref target="RFC3986"
972   x:fmt="," x:sec="2.1"/>): the normal form is to not encode them.
975   For example, the following three URIs are equivalent:
977<figure><artwork type="example">
986<section title="Message Format" anchor="http.message">
987<x:anchor-alias value="generic-message"/>
988<x:anchor-alias value="message.types"/>
989<x:anchor-alias value="HTTP-message"/>
990<x:anchor-alias value="start-line"/>
991<iref item="header section"/>
992<iref item="headers"/>
993<iref item="header field"/>
995   All HTTP/1.1 messages consist of a start-line followed by a sequence of
996   octets in a format similar to the Internet Message Format
997   <xref target="RFC5322"/>: zero or more header fields (collectively
998   referred to as the "headers" or the "header section"), an empty line
999   indicating the end of the header section, and an optional message body.
1001<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-message"><!--terminal production--></iref>
1002  <x:ref>HTTP-message</x:ref>   = <x:ref>start-line</x:ref>
1003                   *( <x:ref>header-field</x:ref> <x:ref>CRLF</x:ref> )
1004                   <x:ref>CRLF</x:ref>
1005                   [ <x:ref>message-body</x:ref> ]
1008   The normal procedure for parsing an HTTP message is to read the
1009   start-line into a structure, read each header field into a hash
1010   table by field name until the empty line, and then use the parsed
1011   data to determine if a message body is expected.  If a message body
1012   has been indicated, then it is read as a stream until an amount
1013   of octets equal to the message body length is read or the connection
1014   is closed.
1017   Recipients &MUST; parse an HTTP message as a sequence of octets in an
1018   encoding that is a superset of US-ASCII <xref target="USASCII"/>.
1019   Parsing an HTTP message as a stream of Unicode characters, without regard
1020   for the specific encoding, creates security vulnerabilities due to the
1021   varying ways that string processing libraries handle invalid multibyte
1022   character sequences that contain the octet LF (%x0A).  String-based
1023   parsers can only be safely used within protocol elements after the element
1024   has been extracted from the message, such as within a header field-value
1025   after message parsing has delineated the individual fields.
1028   An HTTP message can be parsed as a stream for incremental processing or
1029   forwarding downstream.  However, recipients cannot rely on incremental
1030   delivery of partial messages, since some implementations will buffer or
1031   delay message forwarding for the sake of network efficiency, security
1032   checks, or payload transformations.
1035<section title="Start Line" anchor="start.line">
1036  <x:anchor-alias value="Start-Line"/>
1038   An HTTP message can either be a request from client to server or a
1039   response from server to client.  Syntactically, the two types of message
1040   differ only in the start-line, which is either a request-line (for requests)
1041   or a status-line (for responses), and in the algorithm for determining
1042   the length of the message body (<xref target="message.body"/>).
1043   In theory, a client could receive requests and a server could receive
1044   responses, distinguishing them by their different start-line formats,
1045   but in practice servers are implemented to only expect a request
1046   (a response is interpreted as an unknown or invalid request method)
1047   and clients are implemented to only expect a response.
1049<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="start-line"/>
1050  <x:ref>start-line</x:ref>     = <x:ref>request-line</x:ref> / <x:ref>status-line</x:ref>
1053   A sender &MUST-NOT; send whitespace between the start-line and
1054   the first header field. The presence of such whitespace in a request
1055   might be an attempt to trick a server into ignoring that field or
1056   processing the line after it as a new request, either of which might
1057   result in a security vulnerability if other implementations within
1058   the request chain interpret the same message differently.
1059   Likewise, the presence of such whitespace in a response might be
1060   ignored by some clients or cause others to cease parsing.
1063<section title="Request Line" anchor="request.line">
1064  <x:anchor-alias value="Request"/>
1065  <x:anchor-alias value="request-line"/>
1067   A request-line begins with a method token, followed by a single
1068   space (SP), the request-target, another single space (SP), the
1069   protocol version, and ending with CRLF.
1071<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-line"/>
1072  <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>
1075   A server &MUST; be able to parse any received message that begins
1076   with a request-line and matches the ABNF rule for HTTP-message.
1078<iref primary="true" item="method"/>
1079<t anchor="method">
1080   The method token indicates the request method to be performed on the
1081   target resource. The request method is case-sensitive.
1083<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="method"/>
1084  <x:ref>method</x:ref>         = <x:ref>token</x:ref>
1087   The methods defined by this specification can be found in
1088   &methods;, along with information regarding the HTTP method registry
1089   and considerations for defining new methods.
1091<iref item="request-target"/>
1093   The request-target identifies the target resource upon which to apply
1094   the request, as defined in <xref target="request-target"/>.
1097   No whitespace is allowed inside the method, request-target, and
1098   protocol version.  Hence, recipients typically parse the request-line
1099   into its component parts by splitting on the SP characters.
1102   Unfortunately, some user agents fail to properly encode hypertext
1103   references that have embedded whitespace, sending the characters
1104   directly instead of properly percent-encoding the disallowed characters.
1105   Recipients of an invalid request-line &SHOULD; respond with either a
1106   <x:ref>400 (Bad Request)</x:ref> error or a <x:ref>301 (Moved Permanently)</x:ref>
1107   redirect with the request-target properly encoded.  Recipients &SHOULD-NOT;
1108   attempt to autocorrect and then process the request without a redirect,
1109   since the invalid request-line might be deliberately crafted to bypass
1110   security filters along the request chain.
1113   HTTP does not place a pre-defined limit on the length of a request-line.
1114   A server that receives a method longer than any that it implements
1115   &SHOULD; respond with either a <x:ref>405 (Method Not Allowed)</x:ref>, if it is an origin
1116   server, or a <x:ref>501 (Not Implemented)</x:ref> status code.
1117   A server &MUST; be prepared to receive URIs of unbounded length and
1118   respond with the <x:ref>414 (URI Too Long)</x:ref> status code if the received
1119   request-target would be longer than the server wishes to handle
1120   (see &status-414;).
1123   Various ad-hoc limitations on request-line length are found in practice.
1124   It is &RECOMMENDED; that all HTTP senders and recipients support, at a
1125   minimum, request-line lengths of up to 8000 octets.
1129<section title="Status Line" anchor="status.line">
1130  <x:anchor-alias value="response"/>
1131  <x:anchor-alias value="status-line"/>
1132  <x:anchor-alias value="status-code"/>
1133  <x:anchor-alias value="reason-phrase"/>
1135   The first line of a response message is the status-line, consisting
1136   of the protocol version, a space (SP), the status code, another space,
1137   a possibly-empty textual phrase describing the status code, and
1138   ending with CRLF.
1140<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-line"/>
1141  <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>
1144   A client &MUST; be able to parse any received message that begins
1145   with a status-line and matches the ABNF rule for HTTP-message.
1148   The status-code element is a 3-digit integer code describing the
1149   result of the server's attempt to understand and satisfy the client's
1150   corresponding request. The rest of the response message is to be
1151   interpreted in light of the semantics defined for that status code.
1152   See &status-codes; for information about the semantics of status codes,
1153   including the classes of status code (indicated by the first digit),
1154   the status codes defined by this specification, considerations for the
1155   definition of new status codes, and the IANA registry.
1157<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-code"/>
1158  <x:ref>status-code</x:ref>    = 3<x:ref>DIGIT</x:ref>
1161   The reason-phrase element exists for the sole purpose of providing a
1162   textual description associated with the numeric status code, mostly
1163   out of deference to earlier Internet application protocols that were more
1164   frequently used with interactive text clients. A client &SHOULD; ignore
1165   the reason-phrase content.
1167<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="reason-phrase"/>
1168  <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> )
1173<section title="Header Fields" anchor="header.fields">
1174  <x:anchor-alias value="header-field"/>
1175  <x:anchor-alias value="field-content"/>
1176  <x:anchor-alias value="field-name"/>
1177  <x:anchor-alias value="field-value"/>
1178  <x:anchor-alias value="obs-fold"/>
1180   Each HTTP header field consists of a case-insensitive field name
1181   followed by a colon (":"), optional whitespace, and the field value.
1183<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"/>
1184  <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>BWS</x:ref>
1185  <x:ref>field-name</x:ref>     = <x:ref>token</x:ref>
1186  <x:ref>field-value</x:ref>    = *( <x:ref>field-content</x:ref> / <x:ref>obs-fold</x:ref> )
1187  <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> )
1188  <x:ref>obs-fold</x:ref>       = <x:ref>CRLF</x:ref> ( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1189                 ; obsolete line folding
1190                 ; see <xref target="field.parsing"/>
1193   The field-name token labels the corresponding field-value as having the
1194   semantics defined by that header field.  For example, the <x:ref>Date</x:ref>
1195   header field is defined in &header-date; as containing the origination
1196   timestamp for the message in which it appears.
1199   HTTP header fields are fully extensible: there is no limit on the
1200   introduction of new field names, each presumably defining new semantics,
1201   or on the number of header fields used in a given message.  Existing
1202   fields are defined in each part of this specification and in many other
1203   specifications outside the standards process.
1204   New header fields can be introduced without changing the protocol version
1205   if their defined semantics allow them to be safely ignored by recipients
1206   that do not recognize them.
1209   New HTTP header fields &SHOULD; be registered with IANA in the
1210   Message Header Field Registry, as described in &iana-header-registry;.
1211   Unrecognized header fields &MUST; be forwarded by a proxy unless the
1212   field-name is listed in the <x:ref>Connection</x:ref> header field
1213   (<xref target="header.connection"/>) or the proxy is specifically
1214   configured to block or otherwise transform such fields.
1215   Unrecognized header fields &SHOULD; be ignored by other recipients.
1218   The order in which header fields with differing field names are
1219   received is not significant. However, it is "good practice" to send
1220   header fields that contain control data first, such as <x:ref>Host</x:ref>
1221   on requests and <x:ref>Date</x:ref> on responses, so that implementations
1222   can decide when not to handle a message as early as possible.  A server
1223   &MUST; wait until the entire header section is received before interpreting
1224   a request message, since later header fields might include conditionals,
1225   authentication credentials, or deliberately misleading duplicate
1226   header fields that would impact request processing.
1229   Multiple header fields with the same field name &MUST-NOT; be
1230   sent in a message unless the entire field value for that
1231   header field is defined as a comma-separated list [i.e., #(values)].
1232   Multiple header fields with the same field name can be combined into
1233   one "field-name: field-value" pair, without changing the semantics of the
1234   message, by appending each subsequent field value to the combined
1235   field value in order, separated by a comma. The order in which
1236   header fields with the same field name are received is therefore
1237   significant to the interpretation of the combined field value;
1238   a proxy &MUST-NOT; change the order of these field values when
1239   forwarding a message.
1242  <t>
1243   &Note; The "Set-Cookie" header field as implemented in
1244   practice can occur multiple times, but does not use the list syntax, and
1245   thus cannot be combined into a single line (<xref target="RFC6265"/>). (See Appendix A.2.3 of <xref target="Kri2001"/>
1246   for details.) Also note that the Set-Cookie2 header field specified in
1247   <xref target="RFC2965"/> does not share this problem.
1248  </t>
1251<section title="Whitespace" anchor="whitespace">
1252<t anchor="rule.LWS">
1253   This specification uses three rules to denote the use of linear
1254   whitespace: OWS (optional whitespace), RWS (required whitespace), and
1255   BWS ("bad" whitespace).
1257<t anchor="rule.OWS">
1258   The OWS rule is used where zero or more linear whitespace octets might
1259   appear. OWS &SHOULD; either not be produced or be produced as a single
1260   SP. Multiple OWS octets that occur within field-content &SHOULD; either
1261   be replaced with a single SP or transformed to all SP octets (each
1262   octet other than SP replaced with SP) before interpreting the field value
1263   or forwarding the message downstream.
1265<t anchor="rule.RWS">
1266   RWS is used when at least one linear whitespace octet is required to
1267   separate field tokens. RWS &SHOULD; be produced as a single SP.
1268   Multiple RWS octets that occur within field-content &SHOULD; either
1269   be replaced with a single SP or transformed to all SP octets before
1270   interpreting the field value or forwarding the message downstream.
1272<t anchor="rule.BWS">
1273   BWS is used where the grammar allows optional whitespace, for historical
1274   reasons, but senders &SHOULD-NOT; produce it in messages;
1275   recipients &MUST; accept such bad optional whitespace and remove it before
1276   interpreting the field value or forwarding the message downstream.
1278<t anchor="rule.whitespace">
1279  <x:anchor-alias value="BWS"/>
1280  <x:anchor-alias value="OWS"/>
1281  <x:anchor-alias value="RWS"/>
1283<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"/>
1284  <x:ref>OWS</x:ref>            = *( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1285                 ; "optional" whitespace
1286  <x:ref>RWS</x:ref>            = 1*( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1287                 ; "required" whitespace
1288  <x:ref>BWS</x:ref>            = <x:ref>OWS</x:ref>
1289                 ; "bad" whitespace
1293<section title="Field Parsing" anchor="field.parsing">
1295   No whitespace is allowed between the header field-name and colon.
1296   In the past, differences in the handling of such whitespace have led to
1297   security vulnerabilities in request routing and response handling.
1298   Any received request message that contains whitespace between a header
1299   field-name and colon &MUST; be rejected with a response code of 400
1300   (Bad Request).  A proxy &MUST; remove any such whitespace from a response
1301   message before forwarding the message downstream.
1304   A field value &MAY; be preceded by optional whitespace (OWS); a single SP is
1305   preferred. The field value does not include any leading or trailing white
1306   space: OWS occurring before the first non-whitespace octet of the
1307   field value or after the last non-whitespace octet of the field value
1308   is ignored and &SHOULD; be removed before further processing (as this does
1309   not change the meaning of the header field).
1312   Historically, HTTP header field values could be extended over multiple
1313   lines by preceding each extra line with at least one space or horizontal
1314   tab (obs-fold). This specification deprecates such line
1315   folding except within the message/http media type
1316   (<xref target=""/>).
1317   HTTP senders &MUST-NOT; produce messages that include line folding
1318   (i.e., that contain any field-value that matches the obs-fold rule) unless
1319   the message is intended for packaging within the message/http media type.
1320   HTTP recipients &SHOULD; accept line folding and replace any embedded
1321   obs-fold whitespace with either a single SP or a matching number of SP
1322   octets (to avoid buffer copying) prior to interpreting the field value or
1323   forwarding the message downstream.
1326   Historically, HTTP has allowed field content with text in the ISO-8859-1
1327   <xref target="ISO-8859-1"/> character encoding and supported other
1328   character sets only through use of <xref target="RFC2047"/> encoding.
1329   In practice, most HTTP header field values use only a subset of the
1330   US-ASCII character encoding <xref target="USASCII"/>. Newly defined
1331   header fields &SHOULD; limit their field values to US-ASCII octets.
1332   Recipients &SHOULD; treat other (obs-text) octets in field content as
1333   opaque data.
1337<section title="Field Length" anchor="field.length">
1339   HTTP does not place a pre-defined limit on the length of header fields,
1340   either in isolation or as a set. A server &MUST; be prepared to receive
1341   request header fields of unbounded length and respond with a <x:ref>4xx
1342   (Client Error)</x:ref> status code if the received header field(s) would be
1343   longer than the server wishes to handle.
1346   A client that receives response header fields that are longer than it wishes
1347   to handle can only treat it as a server error.
1350   Various ad-hoc limitations on header field length are found in practice. It
1351   is &RECOMMENDED; that all HTTP senders and recipients support messages whose
1352   combined header fields have 4000 or more octets.
1356<section title="Field value components" anchor="field.components">
1357<t anchor="rule.token.separators">
1358  <x:anchor-alias value="tchar"/>
1359  <x:anchor-alias value="token"/>
1360  <x:anchor-alias value="special"/>
1361  <x:anchor-alias value="word"/>
1362   Many HTTP header field values consist of words (token or quoted-string)
1363   separated by whitespace or special characters. These special characters
1364   &MUST; be in a quoted string to be used within a parameter value (as defined
1365   in <xref target="transfer.codings"/>).
1367<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="word"/><iref primary="true" item="Grammar" subitem="token"/><iref primary="true" item="Grammar" subitem="tchar"/><iref primary="true" item="Grammar" subitem="special"><!--unused production--></iref>
1368  <x:ref>word</x:ref>           = <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref>
1370  <x:ref>token</x:ref>          = 1*<x:ref>tchar</x:ref>
1372  IMPORTANT: when editing "tchar" make sure that "special" is updated accordingly!!!
1373 -->
1374  <x:ref>tchar</x:ref>          = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*"
1375                 / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
1376                 / <x:ref>DIGIT</x:ref> / <x:ref>ALPHA</x:ref>
1377                 ; any <x:ref>VCHAR</x:ref>, except <x:ref>special</x:ref>
1379  <x:ref>special</x:ref>        = "(" / ")" / "&lt;" / ">" / "@" / ","
1380                 / ";" / ":" / "\" / DQUOTE / "/" / "["
1381                 / "]" / "?" / "=" / "{" / "}"
1383<t anchor="rule.quoted-string">
1384  <x:anchor-alias value="quoted-string"/>
1385  <x:anchor-alias value="qdtext"/>
1386  <x:anchor-alias value="obs-text"/>
1387   A string of text is parsed as a single word if it is quoted using
1388   double-quote marks.
1390<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"/>
1391  <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>
1392  <x:ref>qdtext</x:ref>         = <x:ref>OWS</x:ref> / %x21 / %x23-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1393  <x:ref>obs-text</x:ref>       = %x80-FF
1395<t anchor="rule.quoted-pair">
1396  <x:anchor-alias value="quoted-pair"/>
1397   The backslash octet ("\") can be used as a single-octet
1398   quoting mechanism within quoted-string constructs:
1400<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-pair"/>
1401  <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> )
1404   Recipients that process the value of the quoted-string &MUST; handle a
1405   quoted-pair as if it were replaced by the octet following the backslash.
1408   Senders &SHOULD-NOT; escape octets in quoted-strings that do not require
1409   escaping (i.e., other than DQUOTE and the backslash octet).
1411<t anchor="rule.comment">
1412  <x:anchor-alias value="comment"/>
1413  <x:anchor-alias value="ctext"/>
1414   Comments can be included in some HTTP header fields by surrounding
1415   the comment text with parentheses. Comments are only allowed in
1416   fields containing "comment" as part of their field value definition.
1418<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="comment"/><iref primary="true" item="Grammar" subitem="ctext"/>
1419  <x:ref>comment</x:ref>        = "(" *( <x:ref>ctext</x:ref> / <x:ref>quoted-cpair</x:ref> / <x:ref>comment</x:ref> ) ")"
1420  <x:ref>ctext</x:ref>          = <x:ref>OWS</x:ref> / %x21-27 / %x2A-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1422<t anchor="rule.quoted-cpair">
1423  <x:anchor-alias value="quoted-cpair"/>
1424   The backslash octet ("\") can be used as a single-octet
1425   quoting mechanism within comment constructs:
1427<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-cpair"/>
1428  <x:ref>quoted-cpair</x:ref>   = "\" ( <x:ref>HTAB</x:ref> / <x:ref>SP</x:ref> / <x:ref>VCHAR</x:ref> / <x:ref>obs-text</x:ref> )
1431   Senders &SHOULD-NOT; escape octets in comments that do not require escaping
1432   (i.e., other than the backslash octet "\" and the parentheses "(" and ")").
1438<section title="Message Body" anchor="message.body">
1439  <x:anchor-alias value="message-body"/>
1441   The message body (if any) of an HTTP message is used to carry the
1442   payload body of that request or response.  The message body is
1443   identical to the payload body unless a transfer coding has been
1444   applied, as described in <xref target="header.transfer-encoding"/>.
1446<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-body"/>
1447  <x:ref>message-body</x:ref> = *OCTET
1450   The rules for when a message body is allowed in a message differ for
1451   requests and responses.
1454   The presence of a message body in a request is signaled by a
1455   a <x:ref>Content-Length</x:ref> or <x:ref>Transfer-Encoding</x:ref> header
1456   field. Request message framing is independent of method semantics,
1457   even if the method does not define any use for a message body.
1460   The presence of a message body in a response depends on both
1461   the request method to which it is responding and the response
1462   status code (<xref target="status.line"/>).
1463   Responses to the HEAD request method never include a message body
1464   because the associated response header fields (e.g.,
1465   <x:ref>Transfer-Encoding</x:ref>, <x:ref>Content-Length</x:ref>, etc.),
1466   if present, indicate only what their values would have been if the request
1467   method had been GET (&HEAD;).
1468   <x:ref>2xx (Successful)</x:ref> responses to CONNECT switch to tunnel
1469   mode instead of having a message body (&CONNECT;).
1470   All <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, and
1471   <x:ref>304 (Not Modified)</x:ref> responses &MUST-NOT; include a message body.
1472   All other responses do include a message body, although the body
1473   &MAY; be of zero length.
1476<section title="Transfer-Encoding" anchor="header.transfer-encoding">
1477  <iref primary="true" item="Transfer-Encoding header field" x:for-anchor=""/>
1478  <x:anchor-alias value="Transfer-Encoding"/>
1480   When one or more transfer codings are applied to a payload body in order
1481   to form the message body, a Transfer-Encoding header field &MUST; be sent
1482   in the message and &MUST; contain the list of corresponding
1483   transfer-coding names in the same order that they were applied.
1484   Transfer codings are defined in <xref target="transfer.codings"/>.
1486<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Transfer-Encoding"/>
1487  <x:ref>Transfer-Encoding</x:ref> = 1#<x:ref>transfer-coding</x:ref>
1490   Transfer-Encoding is analogous to the Content-Transfer-Encoding field of
1491   MIME, which was designed to enable safe transport of binary data over a
1492   7-bit transport service (<xref target="RFC2045" x:fmt="," x:sec="6"/>).
1493   However, safe transport has a different focus for an 8bit-clean transfer
1494   protocol. In HTTP's case, Transfer-Encoding is primarily intended to
1495   accurately delimit a dynamically generated payload and to distinguish
1496   payload encodings that are only applied for transport efficiency or
1497   security from those that are characteristics of the target resource.
1500   The "chunked" transfer-coding (<xref target="chunked.encoding"/>)
1501   &MUST; be implemented by all HTTP/1.1 recipients because it plays a
1502   crucial role in delimiting messages when the payload body size is not
1503   known in advance.
1504   When the "chunked" transfer-coding is used, it &MUST; be the last
1505   transfer-coding applied to form the message body and &MUST-NOT;
1506   be applied more than once in a message body.
1507   If any transfer-coding is applied to a request payload body,
1508   the final transfer-coding applied &MUST; be "chunked".
1509   If any transfer-coding is applied to a response payload body, then either
1510   the final transfer-coding applied &MUST; be "chunked" or
1511   the message &MUST; be terminated by closing the connection.
1514   For example,
1515</preamble><artwork type="example">
1516  Transfer-Encoding: gzip, chunked
1518   indicates that the payload body has been compressed using the gzip
1519   coding and then chunked using the chunked coding while forming the
1520   message body.
1523   If more than one Transfer-Encoding header field is present in a message,
1524   the multiple field-values &MUST; be combined into one field-value,
1525   according to the algorithm defined in <xref target="header.fields"/>,
1526   before determining the message body length.
1529   Unlike <x:ref>Content-Encoding</x:ref> (&content-codings;),
1530   Transfer-Encoding is a property of the message, not of the payload, and thus
1531   &MAY; be added or removed by any implementation along the request/response
1532   chain. Additional information about the encoding parameters &MAY; be
1533   provided by other header fields not defined by this specification.
1536   Transfer-Encoding &MAY; be sent in a response to a HEAD request or in a
1537   <x:ref>304 (Not Modified)</x:ref> response (&status-304;) to a GET request,
1538   neither of which includes a message body,
1539   to indicate that the origin server would have applied a transfer coding
1540   to the message body if the request had been an unconditional GET.
1541   This indication is not required, however, because any recipient on
1542   the response chain (including the origin server) can remove transfer
1543   codings when they are not needed.
1546   Transfer-Encoding was added in HTTP/1.1.  It is generally assumed that
1547   implementations advertising only HTTP/1.0 support will not understand
1548   how to process a transfer-encoded payload.
1549   A client &MUST-NOT; send a request containing Transfer-Encoding unless it
1550   knows the server will handle HTTP/1.1 (or later) requests; such knowledge
1551   might be in the form of specific user configuration or by remembering the
1552   version of a prior received response.
1553   A server &MUST-NOT; send a response containing Transfer-Encoding unless
1554   the corresponding request indicates HTTP/1.1 (or later).
1557   A server that receives a request message with a transfer-coding it does
1558   not understand &SHOULD; respond with <x:ref>501 (Not Implemented)</x:ref> and then
1559   close the connection.
1563<section title="Content-Length" anchor="header.content-length">
1564  <iref primary="true" item="Content-Length header field" x:for-anchor=""/>
1565  <x:anchor-alias value="Content-Length"/>
1567   When a message is allowed to contain a message body, does not have a
1568   <x:ref>Transfer-Encoding</x:ref> header field, and has a payload body
1569   length that is known to the sender before the message header section has
1570   been sent, the sender &SHOULD; send a Content-Length header field to
1571   indicate the length of the payload body as a decimal number of octets.
1573<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/>
1574  <x:ref>Content-Length</x:ref> = 1*<x:ref>DIGIT</x:ref>
1577   An example is
1579<figure><artwork type="example">
1580  Content-Length: 3495
1583   A sender &MUST-NOT; send a Content-Length header field in any message that
1584   contains a <x:ref>Transfer-Encoding</x:ref> header field.
1587   A server &MAY; send a Content-Length header field in a response to a HEAD
1588   request (&HEAD;); a server &MUST-NOT; send Content-Length in such a
1589   response unless its field-value equals the decimal number of octets that
1590   would have been sent in the payload body of a response if the same
1591   request had used the GET method.
1594   A server &MAY; send a Content-Length header field in a
1595   <x:ref>304 (Not Modified)</x:ref> response to a conditional GET request
1596   (&status-304;); a server &MUST-NOT; send Content-Length in such a
1597   response unless its field-value equals the decimal number of octets that
1598   would have been sent in the payload body of a <x:ref>200 (OK)</x:ref>
1599   response to the same request.
1602   A server &MUST-NOT; send a Content-Length header field in any response
1603   with a status code of
1604   <x:ref>1xx (Informational)</x:ref> or <x:ref>204 (No Content)</x:ref>.
1605   A server &SHOULD-NOT; send a Content-Length header field in any
1606   <x:ref>2xx (Successful)</x:ref> response to a CONNECT request (&CONNECT;).
1609   Any Content-Length field value greater than or equal to zero is valid.
1610   Since there is no predefined limit to the length of an HTTP payload,
1611   recipients &SHOULD; anticipate potentially large decimal numerals and
1612   prevent parsing errors due to integer conversion overflows
1613   (<xref target="attack.protocol.element.size.overflows"/>).
1616   If a message is received that has multiple Content-Length header fields
1617   with field-values consisting of the same decimal value, or a single
1618   Content-Length header field with a field value containing a list of
1619   identical decimal values (e.g., "Content-Length: 42, 42"), indicating that
1620   duplicate Content-Length header fields have been generated or combined by an
1621   upstream message processor, then the recipient &MUST; either reject the
1622   message as invalid or replace the duplicated field-values with a single
1623   valid Content-Length field containing that decimal value prior to
1624   determining the message body length.
1627  <t>
1628   &Note; HTTP's use of Content-Length for message framing differs
1629   significantly from the same field's use in MIME, where it is an optional
1630   field used only within the "message/external-body" media-type.
1631  </t>
1635<section title="Message Body Length" anchor="message.body.length">
1637   The length of a message body is determined by one of the following
1638   (in order of precedence):
1641  <list style="numbers">
1642    <x:lt><t>
1643     Any response to a HEAD request and any response with a
1644     <x:ref>1xx (Informational)</x:ref>, <x:ref>204 (No Content)</x:ref>, or
1645     <x:ref>304 (Not Modified)</x:ref> status code is always
1646     terminated by the first empty line after the header fields, regardless of
1647     the header fields present in the message, and thus cannot contain a
1648     message body.
1649    </t></x:lt>
1650    <x:lt><t>
1651     Any <x:ref>2xx (Successful)</x:ref> response to a CONNECT request implies that the
1652     connection will become a tunnel immediately after the empty line that
1653     concludes the header fields.  A client &MUST; ignore any
1654     <x:ref>Content-Length</x:ref> or <x:ref>Transfer-Encoding</x:ref> header
1655     fields received in such a message.
1656    </t></x:lt>
1657    <x:lt><t>
1658     If a <x:ref>Transfer-Encoding</x:ref> header field is present
1659     and the "chunked" transfer-coding (<xref target="chunked.encoding"/>)
1660     is the final encoding, the message body length is determined by reading
1661     and decoding the chunked data until the transfer-coding indicates the
1662     data is complete.
1663    </t>
1664    <t>
1665     If a <x:ref>Transfer-Encoding</x:ref> header field is present in a
1666     response and the "chunked" transfer-coding is not the final encoding, the
1667     message body length is determined by reading the connection until it is
1668     closed by the server.
1669     If a Transfer-Encoding header field is present in a request and the
1670     "chunked" transfer-coding is not the final encoding, the message body
1671     length cannot be determined reliably; the server &MUST; respond with
1672     the <x:ref>400 (Bad Request)</x:ref> status code and then close the connection.
1673    </t>
1674    <t>
1675     If a message is received with both a <x:ref>Transfer-Encoding</x:ref>
1676     and a <x:ref>Content-Length</x:ref> header field, the
1677     Transfer-Encoding overrides the Content-Length.
1678     Such a message might indicate an attempt to perform request or response
1679     smuggling (bypass of security-related checks on message routing or content)
1680     and thus ought to be handled as an error.  The provided Content-Length &MUST;
1681     be removed, prior to forwarding the message downstream, or replaced with
1682     the real message body length after the transfer-coding is decoded.
1683    </t></x:lt>
1684    <x:lt><t>
1685     If a message is received without <x:ref>Transfer-Encoding</x:ref> and with
1686     either multiple <x:ref>Content-Length</x:ref> header fields having
1687     differing field-values or a single Content-Length header field having an
1688     invalid value, then the message framing is invalid and &MUST; be treated
1689     as an error to prevent request or response smuggling.
1690     If this is a request message, the server &MUST; respond with
1691     a <x:ref>400 (Bad Request)</x:ref> status code and then close the connection.
1692     If this is a response message received by a proxy, the proxy
1693     &MUST; discard the received response, send a <x:ref>502 (Bad Gateway)</x:ref>
1694     status code as its downstream response, and then close the connection.
1695     If this is a response message received by a user-agent, it &MUST; be
1696     treated as an error by discarding the message and closing the connection.
1697    </t></x:lt>
1698    <x:lt><t>
1699     If a valid <x:ref>Content-Length</x:ref> header field is present without
1700     <x:ref>Transfer-Encoding</x:ref>, its decimal value defines the
1701     message body length in octets.  If the actual number of octets sent in
1702     the message is less than the indicated Content-Length, the recipient
1703     &MUST; consider the message to be incomplete and treat the connection
1704     as no longer usable.
1705     If the actual number of octets sent in the message is more than the indicated
1706     Content-Length, the recipient &MUST; only process the message body up to the
1707     field value's number of octets; the remainder of the message &MUST; either
1708     be discarded or treated as the next message in a pipeline.  For the sake of
1709     robustness, a user-agent &MAY; attempt to detect and correct such an error
1710     in message framing if it is parsing the response to the last request on
1711     a connection and the connection has been closed by the server.
1712    </t></x:lt>
1713    <x:lt><t>
1714     If this is a request message and none of the above are true, then the
1715     message body length is zero (no message body is present).
1716    </t></x:lt>
1717    <x:lt><t>
1718     Otherwise, this is a response message without a declared message body
1719     length, so the message body length is determined by the number of octets
1720     received prior to the server closing the connection.
1721    </t></x:lt>
1722  </list>
1725   Since there is no way to distinguish a successfully completed,
1726   close-delimited message from a partially-received message interrupted
1727   by network failure, a server &SHOULD; use encoding or
1728   length-delimited messages whenever possible.  The close-delimiting
1729   feature exists primarily for backwards compatibility with HTTP/1.0.
1732   A server &MAY; reject a request that contains a message body but
1733   not a <x:ref>Content-Length</x:ref> by responding with
1734   <x:ref>411 (Length Required)</x:ref>.
1737   Unless a transfer-coding other than "chunked" has been applied,
1738   a client that sends a request containing a message body &SHOULD;
1739   use a valid <x:ref>Content-Length</x:ref> header field if the message body
1740   length is known in advance, rather than the "chunked" encoding, since some
1741   existing services respond to "chunked" with a <x:ref>411 (Length Required)</x:ref>
1742   status code even though they understand the chunked encoding.  This
1743   is typically because such services are implemented via a gateway that
1744   requires a content-length in advance of being called and the server
1745   is unable or unwilling to buffer the entire request before processing.
1748   A client that sends a request containing a message body &MUST; include a
1749   valid <x:ref>Content-Length</x:ref> header field if it does not know the
1750   server will handle HTTP/1.1 (or later) requests; such knowledge can be in
1751   the form of specific user configuration or by remembering the version of a
1752   prior received response.
1757<section anchor="incomplete.messages" title="Handling Incomplete Messages">
1759   Request messages that are prematurely terminated, possibly due to a
1760   canceled connection or a server-imposed time-out exception, &MUST;
1761   result in closure of the connection; sending an error response
1762   prior to closing the connection is &OPTIONAL;.
1765   Response messages that are prematurely terminated, usually by closure
1766   of the connection prior to receiving the expected number of octets or by
1767   failure to decode a transfer-encoded message body, &MUST; be recorded
1768   as incomplete.  A response that terminates in the middle of the header
1769   block (before the empty line is received) cannot be assumed to convey the
1770   full semantics of the response and &MUST; be treated as an error.
1773   A message body that uses the chunked transfer encoding is
1774   incomplete if the zero-sized chunk that terminates the encoding has not
1775   been received.  A message that uses a valid <x:ref>Content-Length</x:ref> is
1776   incomplete if the size of the message body received (in octets) is less than
1777   the value given by Content-Length.  A response that has neither chunked
1778   transfer encoding nor Content-Length is terminated by closure of the
1779   connection, and thus is considered complete regardless of the number of
1780   message body octets received, provided that the header block was received
1781   intact.
1784   A user agent &MUST-NOT; render an incomplete response message body as if
1785   it were complete (i.e., some indication needs to be given to the user that an
1786   error occurred).  Cache requirements for incomplete responses are defined
1787   in &cache-incomplete;.
1790   A server &MUST; read the entire request message body or close
1791   the connection after sending its response, since otherwise the
1792   remaining data on a persistent connection would be misinterpreted
1793   as the next request.  Likewise,
1794   a client &MUST; read the entire response message body if it intends
1795   to reuse the same connection for a subsequent request.  Pipelining
1796   multiple requests on a connection is described in <xref target="pipelining"/>.
1800<section title="Message Parsing Robustness" anchor="message.robustness">
1802   Older HTTP/1.0 client implementations might send an extra CRLF
1803   after a POST request as a lame workaround for some early server
1804   applications that failed to read message body content that was
1805   not terminated by a line-ending. An HTTP/1.1 client &MUST-NOT;
1806   preface or follow a request with an extra CRLF.  If terminating
1807   the request message body with a line-ending is desired, then the
1808   client &MUST; include the terminating CRLF octets as part of the
1809   message body length.
1812   In the interest of robustness, servers &SHOULD; ignore at least one
1813   empty line received where a request-line is expected. In other words, if
1814   the server is reading the protocol stream at the beginning of a
1815   message and receives a CRLF first, it &SHOULD; ignore the CRLF.
1816   Likewise, although the line terminator for the start-line and header
1817   fields is the sequence CRLF, we recommend that recipients recognize a
1818   single LF as a line terminator and ignore any CR.
1821   When a server listening only for HTTP request messages, or processing
1822   what appears from the start-line to be an HTTP request message,
1823   receives a sequence of octets that does not match the HTTP-message
1824   grammar aside from the robustness exceptions listed above, the
1825   server &MUST; respond with an HTTP/1.1 <x:ref>400 (Bad Request)</x:ref> response. 
1830<section title="Transfer Codings" anchor="transfer.codings">
1831  <x:anchor-alias value="transfer-coding"/>
1832  <x:anchor-alias value="transfer-extension"/>
1834   Transfer-coding values are used to indicate an encoding
1835   transformation that has been, can be, or might need to be applied to a
1836   payload body in order to ensure "safe transport" through the network.
1837   This differs from a content coding in that the transfer-coding is a
1838   property of the message rather than a property of the representation
1839   that is being transferred.
1841<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-coding"/><iref primary="true" item="Grammar" subitem="transfer-extension"/>
1842  <x:ref>transfer-coding</x:ref>    = "chunked" ; <xref target="chunked.encoding"/>
1843                     / "compress" ; <xref target="compress.coding"/>
1844                     / "deflate" ; <xref target="deflate.coding"/>
1845                     / "gzip" ; <xref target="gzip.coding"/>
1846                     / <x:ref>transfer-extension</x:ref>
1847  <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> )
1849<t anchor="rule.parameter">
1850  <x:anchor-alias value="attribute"/>
1851  <x:anchor-alias value="transfer-parameter"/>
1852  <x:anchor-alias value="value"/>
1853   Parameters are in the form of attribute/value pairs.
1855<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-parameter"/><iref primary="true" item="Grammar" subitem="attribute"/><iref primary="true" item="Grammar" subitem="value"/><iref primary="true" item="Grammar" subitem="date2"/><iref primary="true" item="Grammar" subitem="date3"/>
1856  <x:ref>transfer-parameter</x:ref> = <x:ref>attribute</x:ref> <x:ref>BWS</x:ref> "=" <x:ref>BWS</x:ref> <x:ref>value</x:ref>
1857  <x:ref>attribute</x:ref>          = <x:ref>token</x:ref>
1858  <x:ref>value</x:ref>              = <x:ref>word</x:ref>
1861   All transfer-coding values are case-insensitive and &SHOULD; be registered
1862   within the HTTP Transfer Coding registry, as defined in
1863   <xref target="transfer.coding.registry"/>.
1864   They are used in the <x:ref>TE</x:ref> (<xref target="header.te"/>) and
1865   <x:ref>Transfer-Encoding</x:ref> (<xref target="header.transfer-encoding"/>)
1866   header fields.
1869<section title="Chunked Transfer Coding" anchor="chunked.encoding">
1870  <iref item="chunked (Coding Format)"/>
1871  <x:anchor-alias value="chunk"/>
1872  <x:anchor-alias value="chunked-body"/>
1873  <x:anchor-alias value="chunk-data"/>
1874  <x:anchor-alias value="chunk-ext"/>
1875  <x:anchor-alias value="chunk-ext-name"/>
1876  <x:anchor-alias value="chunk-ext-val"/>
1877  <x:anchor-alias value="chunk-size"/>
1878  <x:anchor-alias value="last-chunk"/>
1879  <x:anchor-alias value="trailer-part"/>
1880  <x:anchor-alias value="quoted-str-nf"/>
1881  <x:anchor-alias value="qdtext-nf"/>
1883   The chunked encoding modifies the body of a message in order to
1884   transfer it as a series of chunks, each with its own size indicator,
1885   followed by an &OPTIONAL; trailer containing header fields. This
1886   allows dynamically produced content to be transferred along with the
1887   information necessary for the recipient to verify that it has
1888   received the full message.
1890<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="true" item="Grammar" subitem="trailer-part"/><iref primary="true" item="Grammar" subitem="quoted-str-nf"/><iref primary="true" item="Grammar" subitem="qdtext-nf"/>
1891  <x:ref>chunked-body</x:ref>   = *<x:ref>chunk</x:ref>
1892                   <x:ref>last-chunk</x:ref>
1893                   <x:ref>trailer-part</x:ref>
1894                   <x:ref>CRLF</x:ref>
1896  <x:ref>chunk</x:ref>          = <x:ref>chunk-size</x:ref> [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
1897                   <x:ref>chunk-data</x:ref> <x:ref>CRLF</x:ref>
1898  <x:ref>chunk-size</x:ref>     = 1*<x:ref>HEXDIG</x:ref>
1899  <x:ref>last-chunk</x:ref>     = 1*("0") [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
1901  <x:ref>chunk-ext</x:ref>      = *( ";" <x:ref>chunk-ext-name</x:ref> [ "=" <x:ref>chunk-ext-val</x:ref> ] )
1902  <x:ref>chunk-ext-name</x:ref> = <x:ref>token</x:ref>
1903  <x:ref>chunk-ext-val</x:ref>  = <x:ref>token</x:ref> / <x:ref>quoted-str-nf</x:ref>
1904  <x:ref>chunk-data</x:ref>     = 1*<x:ref>OCTET</x:ref> ; a sequence of chunk-size octets
1905  <x:ref>trailer-part</x:ref>   = *( <x:ref>header-field</x:ref> <x:ref>CRLF</x:ref> )
1907  <x:ref>quoted-str-nf</x:ref>  = <x:ref>DQUOTE</x:ref> *( <x:ref>qdtext-nf</x:ref> / <x:ref>quoted-pair</x:ref> ) <x:ref>DQUOTE</x:ref>
1908                 ; like <x:ref>quoted-string</x:ref>, but disallowing line folding
1909  <x:ref>qdtext-nf</x:ref>      = <x:ref>HTAB</x:ref> / <x:ref>SP</x:ref> / %x21 / %x23-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1912   Chunk extensions within the chucked encoding are deprecated.
1913   Senders &SHOULD-NOT; send chunk-ext.
1914   Definition of new chunk extensions is discouraged.
1917   The chunk-size field is a string of hex digits indicating the size of
1918   the chunk-data in octets. The chunked encoding is ended by any chunk whose size is
1919   zero, followed by the trailer, which is terminated by an empty line.
1922<section title="Trailer" anchor="header.trailer">
1923  <iref primary="true" item="Trailer header field" x:for-anchor=""/>
1924  <x:anchor-alias value="Trailer"/>
1926   A trailer allows the sender to include additional fields at the end of a
1927   chunked message in order to supply metadata that might be dynamically
1928   generated while the message body is sent, such as a message integrity
1929   check, digital signature, or post-processing status.
1930   The trailer &MUST-NOT; contain fields that need to be known before a
1931   recipient processes the body, such as <x:ref>Transfer-Encoding</x:ref>,
1932   <x:ref>Content-Length</x:ref>, and <x:ref>Trailer</x:ref>.
1935   When a message includes a message body encoded with the chunked
1936   transfer-coding and the sender desires to send metadata in the form of
1937   trailer fields at the end of the message, the sender &SHOULD; send a
1938   <x:ref>Trailer</x:ref> header field before the message body to indicate
1939   which fields will be present in the trailers. This allows the recipient
1940   to prepare for receipt of that metadata before it starts processing the body,
1941   which is useful if the message is being streamed and the recipient wishes
1942   to confirm an integrity check on the fly.
1944<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Trailer"/>
1945  <x:ref>Trailer</x:ref> = 1#<x:ref>field-name</x:ref>
1948   If no <x:ref>Trailer</x:ref> header field is present, the sender of a
1949   chunked message body &SHOULD; send an empty trailer.
1952   A server &MUST; send an empty trailer with the chunked transfer-coding
1953   unless at least one of the following is true:
1954  <list style="numbers">
1955    <t>the request included a <x:ref>TE</x:ref> header field that indicates
1956    "trailers" is acceptable in the transfer-coding of the response, as
1957    described in <xref target="header.te"/>; or,</t>
1959    <t>the trailer fields consist entirely of optional metadata and the
1960    recipient could use the message (in a manner acceptable to the server where
1961    the field originated) without receiving that metadata. In other words,
1962    the server that generated the header field is willing to accept the
1963    possibility that the trailer fields might be silently discarded along
1964    the path to the client.</t>
1965  </list>
1968   The above requirement prevents the need for an infinite buffer when a
1969   message is being received by an HTTP/1.1 (or later) proxy and forwarded to
1970   an HTTP/1.0 recipient.
1974<section title="Decoding chunked" anchor="decoding.chunked">
1976   A process for decoding the "chunked" transfer-coding
1977   can be represented in pseudo-code as:
1979<figure><artwork type="code">
1980  length := 0
1981  read chunk-size, chunk-ext (if any) and CRLF
1982  while (chunk-size &gt; 0) {
1983     read chunk-data and CRLF
1984     append chunk-data to decoded-body
1985     length := length + chunk-size
1986     read chunk-size and CRLF
1987  }
1988  read header-field
1989  while (header-field not empty) {
1990     append header-field to existing header fields
1991     read header-field
1992  }
1993  Content-Length := length
1994  Remove "chunked" from Transfer-Encoding
1995  Remove Trailer from existing header fields
1998   All recipients &MUST; be able to receive and decode the
1999   "chunked" transfer-coding and &MUST; ignore chunk-ext extensions
2000   they do not understand.
2005<section title="Compression Codings" anchor="compression.codings">
2007   The codings defined below can be used to compress the payload of a
2008   message.
2011<section title="Compress Coding" anchor="compress.coding">
2012<iref item="compress (Coding Format)"/>
2014   The "compress" format is produced by the common UNIX file compression
2015   program "compress". This format is an adaptive Lempel-Ziv-Welch
2016   coding (LZW). Recipients &SHOULD; consider "x-compress" to be
2017   equivalent to "compress".
2021<section title="Deflate Coding" anchor="deflate.coding">
2022<iref item="deflate (Coding Format)"/>
2024   The "deflate" format is defined as the "deflate" compression mechanism
2025   (described in <xref target="RFC1951"/>) used inside the "zlib"
2026   data format (<xref target="RFC1950"/>).
2029  <t>
2030    &Note; Some incorrect implementations send the "deflate"
2031    compressed data without the zlib wrapper.
2032   </t>
2036<section title="Gzip Coding" anchor="gzip.coding">
2037<iref item="gzip (Coding Format)"/>
2039   The "gzip" format is produced by the file compression program
2040   "gzip" (GNU zip), as described in <xref target="RFC1952"/>. This format is a
2041   Lempel-Ziv coding (LZ77) with a 32 bit CRC.
2042   Recipients &SHOULD; consider "x-gzip" to be equivalent to "gzip".
2048<section title="TE" anchor="header.te">
2049  <iref primary="true" item="TE header field" x:for-anchor=""/>
2050  <x:anchor-alias value="TE"/>
2051  <x:anchor-alias value="t-codings"/>
2052  <x:anchor-alias value="t-ranking"/>
2053  <x:anchor-alias value="rank"/>
2055   The "TE" header field in a request indicates what transfer-codings,
2056   besides "chunked", the client is willing to accept in response, and
2057   whether or not the client is willing to accept trailer fields in a
2058   chunked transfer-coding.
2061   The TE field-value consists of a comma-separated list of transfer-coding
2062   names, each allowing for optional parameters (as described in
2063   <xref target="transfer.codings"/>), and/or the keyword "trailers".
2064   Clients &MUST-NOT; send the chunked transfer-coding name in TE;
2065   chunked is always acceptable for HTTP/1.1 recipients.
2067<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"/>
2068  <x:ref>TE</x:ref>        = #<x:ref>t-codings</x:ref>
2069  <x:ref>t-codings</x:ref> = "trailers" / ( <x:ref>transfer-coding</x:ref> [ <x:ref>t-ranking</x:ref> ] )
2070  <x:ref>t-ranking</x:ref> = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>rank</x:ref>
2071  <x:ref>rank</x:ref>      = ( "0" [ "." 0*3<x:ref>DIGIT</x:ref> ] )
2072             / ( "1" [ "." 0*3("0") ] )
2075   Three examples of TE use are below.
2077<figure><artwork type="example">
2078  TE: deflate
2079  TE:
2080  TE: trailers, deflate;q=0.5
2083   The presence of the keyword "trailers" indicates that the client is
2084   willing to accept trailer fields in a chunked transfer-coding,
2085   as defined in <xref target="chunked.encoding"/>, on behalf of itself and
2086   any downstream clients. For chained requests, this implies that either:
2087   (a) all downstream clients are willing to accept trailer fields in the
2088   forwarded response; or,
2089   (b) the client will attempt to buffer the response on behalf of downstream
2090   recipients.
2091   Note that HTTP/1.1 does not define any means to limit the size of a
2092   chunked response such that a client can be assured of buffering the
2093   entire response.
2096   When multiple transfer-codings are acceptable, the client &MAY; rank the
2097   codings by preference using a case-insensitive "q" parameter (similar to
2098   the qvalues used in content negotiation fields, &qvalue;). The rank value
2099   is a real number in the range 0 through 1, where 0.001 is the least
2100   preferred and 1 is the most preferred; a value of 0 means "not acceptable".
2103   If the TE field-value is empty or if no TE field is present, the only
2104   acceptable transfer-coding is "chunked". A message with no transfer-coding
2105   is always acceptable.
2108   Since the TE header field only applies to the immediate connection,
2109   a sender of TE &MUST; also send a "TE" connection option within the
2110   <x:ref>Connection</x:ref> header field (<xref target="header.connection"/>)
2111   in order to prevent the TE field from being forwarded by intermediaries
2112   that do not support its semantics.
2117<section title="Message Routing" anchor="message.routing">
2119   HTTP request message routing is determined by each client based on the
2120   target resource, the client's proxy configuration, and
2121   establishment or reuse of an inbound connection.  The corresponding
2122   response routing follows the same connection chain back to the client.
2125<section title="Identifying a Target Resource" anchor="target-resource">
2126  <iref primary="true" item="target resource"/>
2127  <iref primary="true" item="target URI"/>
2128  <x:anchor-alias value="target resource"/>
2129  <x:anchor-alias value="target URI"/>
2131   HTTP is used in a wide variety of applications, ranging from
2132   general-purpose computers to home appliances.  In some cases,
2133   communication options are hard-coded in a client's configuration.
2134   However, most HTTP clients rely on the same resource identification
2135   mechanism and configuration techniques as general-purpose Web browsers.
2138   HTTP communication is initiated by a user agent for some purpose.
2139   The purpose is a combination of request semantics, which are defined in
2140   <xref target="Part2"/>, and a target resource upon which to apply those
2141   semantics.  A URI reference (<xref target="uri"/>) is typically used as
2142   an identifier for the "<x:dfn>target resource</x:dfn>", which a user agent
2143   would resolve to its absolute form in order to obtain the
2144   "<x:dfn>target URI</x:dfn>".  The target URI
2145   excludes the reference's fragment identifier component, if any,
2146   since fragment identifiers are reserved for client-side processing
2147   (<xref target="RFC3986" x:fmt="," x:sec="3.5"/>).
2151<section title="Connecting Inbound" anchor="connecting.inbound">
2153   Once the target URI is determined, a client needs to decide whether
2154   a network request is necessary to accomplish the desired semantics and,
2155   if so, where that request is to be directed.
2158   If the client has a response cache and the request semantics can be
2159   satisfied by a cache (<xref target="Part6"/>), then the request is
2160   usually directed to the cache first.
2163   If the request is not satisfied by a cache, then a typical client will
2164   check its configuration to determine whether a proxy is to be used to
2165   satisfy the request.  Proxy configuration is implementation-dependent,
2166   but is often based on URI prefix matching, selective authority matching,
2167   or both, and the proxy itself is usually identified by an "http" or
2168   "https" URI.  If a proxy is applicable, the client connects inbound by
2169   establishing (or reusing) a connection to that proxy.
2172   If no proxy is applicable, a typical client will invoke a handler routine,
2173   usually specific to the target URI's scheme, to connect directly
2174   to an authority for the target resource.  How that is accomplished is
2175   dependent on the target URI scheme and defined by its associated
2176   specification, similar to how this specification defines origin server
2177   access for resolution of the "http" (<xref target="http.uri"/>) and
2178   "https" (<xref target="https.uri"/>) schemes.
2181   HTTP requirements regarding connection management are defined in
2182   <xref target=""/>.
2186<section title="Request Target" anchor="request-target">
2188   Once an inbound connection is obtained,
2189   the client sends an HTTP request message (<xref target="http.message"/>)
2190   with a request-target derived from the target URI.
2191   There are four distinct formats for the request-target, depending on both
2192   the method being requested and whether the request is to a proxy.
2194<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"/>
2195  <x:ref>request-target</x:ref> = <x:ref>origin-form</x:ref>
2196                 / <x:ref>absolute-form</x:ref>
2197                 / <x:ref>authority-form</x:ref>
2198                 / <x:ref>asterisk-form</x:ref>
2200  <x:ref>origin-form</x:ref>    = <x:ref>path-absolute</x:ref> [ "?" <x:ref>query</x:ref> ]
2201  <x:ref>absolute-form</x:ref>  = <x:ref>absolute-URI</x:ref>
2202  <x:ref>authority-form</x:ref> = <x:ref>authority</x:ref>
2203  <x:ref>asterisk-form</x:ref>  = "*"
2205<t anchor="origin-form"><iref item="origin-form (of request-target)"/>
2206   The most common form of request-target is the origin-form.
2207   When making a request directly to an origin server, other than a CONNECT
2208   or server-wide OPTIONS request (as detailed below),
2209   a client &MUST; send only the absolute path and query components of
2210   the target URI as the request-target.
2211   If the target URI's path component is empty, then the client &MUST; send
2212   "/" as the path within the origin-form of request-target.
2213   A <x:ref>Host</x:ref> header field is also sent, as defined in
2214   <xref target=""/>, containing the target URI's
2215   authority component (excluding any userinfo).
2218   For example, a client wishing to retrieve a representation of the resource
2219   identified as
2221<figure><artwork x:indent-with="  " type="example">
2225   directly from the origin server would open (or reuse) a TCP connection
2226   to port 80 of the host "" and send the lines:
2228<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2229GET /where?q=now HTTP/1.1
2233   followed by the remainder of the request message.
2235<t anchor="absolute-form"><iref item="absolute-form (of request-target)"/>
2236   When making a request to a proxy, other than a CONNECT or server-wide
2237   OPTIONS request (as detailed below), a client &MUST; send the target URI
2238   in absolute-form as the request-target.
2239   The proxy is requested to either service that request from a valid cache,
2240   if possible, or make the same request on the client's behalf to either
2241   the next inbound proxy server or directly to the origin server indicated
2242   by the request-target.  Requirements on such "forwarding" of messages are
2243   defined in <xref target="message.forwarding"/>.
2246   An example absolute-form of request-line would be:
2248<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2249GET HTTP/1.1
2252   To allow for transition to the absolute-form for all requests in some
2253   future version of HTTP, HTTP/1.1 servers &MUST; accept the absolute-form
2254   in requests, even though HTTP/1.1 clients will only send them in requests
2255   to proxies.
2257<t anchor="authority-form"><iref item="authority-form (of request-target)"/>
2258   The authority-form of request-target is only used for CONNECT requests
2259   (&CONNECT;).  When making a CONNECT request to establish a tunnel through
2260   one or more proxies, a client &MUST; send only the target URI's
2261   authority component (excluding any userinfo) as the request-target.
2262   For example,
2264<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2267<t anchor="asterisk-form"><iref item="asterisk-form (of request-target)"/>
2268   The asterisk-form of request-target is only used for a server-wide
2269   OPTIONS request (&OPTIONS;).  When a client wishes to request OPTIONS
2270   for the server as a whole, as opposed to a specific named resource of
2271   that server, the client &MUST; send only "*" (%x2A) as the request-target.
2272   For example,
2274<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2275OPTIONS * HTTP/1.1
2278   If a proxy receives an OPTIONS request with an absolute-form of
2279   request-target in which the URI has an empty path and no query component,
2280   then the last proxy on the request chain &MUST; send a request-target
2281   of "*" when it forwards the request to the indicated origin server.
2284   For example, the request
2285</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2289  would be forwarded by the final proxy as
2290</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2291OPTIONS * HTTP/1.1
2295   after connecting to port 8001 of host "".
2300<section title="Host" anchor="">
2301  <iref primary="true" item="Host header field" x:for-anchor=""/>
2302  <x:anchor-alias value="Host"/>
2304   The "Host" header field in a request provides the host and port
2305   information from the target URI, enabling the origin
2306   server to distinguish among resources while servicing requests
2307   for multiple host names on a single IP address.  Since the Host
2308   field-value is critical information for handling a request, it
2309   &SHOULD; be sent as the first header field following the request-line.
2311<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Host"/>
2312  <x:ref>Host</x:ref> = <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ; <xref target="http.uri"/>
2315   A client &MUST; send a Host header field in all HTTP/1.1 request
2316   messages.  If the target URI includes an authority component, then
2317   the Host field-value &MUST; be identical to that authority component
2318   after excluding any userinfo (<xref target="http.uri"/>).
2319   If the authority component is missing or undefined for the target URI,
2320   then the Host header field &MUST; be sent with an empty field-value.
2323   For example, a GET request to the origin server for
2324   &lt;; would begin with:
2326<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2327GET /pub/WWW/ HTTP/1.1
2331   The Host header field &MUST; be sent in an HTTP/1.1 request even
2332   if the request-target is in the absolute-form, since this
2333   allows the Host information to be forwarded through ancient HTTP/1.0
2334   proxies that might not have implemented Host.
2337   When a proxy receives a request with an absolute-form of
2338   request-target, the proxy &MUST; ignore the received
2339   Host header field (if any) and instead replace it with the host
2340   information of the request-target.  If the proxy forwards the request,
2341   it &MUST; generate a new Host field-value based on the received
2342   request-target rather than forward the received Host field-value.
2345   Since the Host header field acts as an application-level routing
2346   mechanism, it is a frequent target for malware seeking to poison
2347   a shared cache or redirect a request to an unintended server.
2348   An interception proxy is particularly vulnerable if it relies on
2349   the Host field-value for redirecting requests to internal
2350   servers, or for use as a cache key in a shared cache, without
2351   first verifying that the intercepted connection is targeting a
2352   valid IP address for that host.
2355   A server &MUST; respond with a <x:ref>400 (Bad Request)</x:ref> status code
2356   to any HTTP/1.1 request message that lacks a Host header field and
2357   to any request message that contains more than one Host header field
2358   or a Host header field with an invalid field-value.
2362<section title="Effective Request URI" anchor="effective.request.uri">
2363  <iref primary="true" item="effective request URI"/>
2365   A server that receives an HTTP request message &MUST; reconstruct
2366   the user agent's original target URI, based on the pieces of information
2367   learned from the request-target, <x:ref>Host</x:ref> header field, and
2368   connection context, in order to identify the intended target resource and
2369   properly service the request. The URI derived from this reconstruction
2370   process is referred to as the "<x:dfn>effective request URI</x:dfn>".
2373   For a user agent, the effective request URI is the target URI.
2376   If the request-target is in absolute-form, then the effective request URI
2377   is the same as the request-target.  Otherwise, the effective request URI
2378   is constructed as follows.
2381   If the request is received over a TLS-secured TCP connection,
2382   then the effective request URI's scheme is "https"; otherwise, the
2383   scheme is "http".
2386   If the request-target is in authority-form, then the effective
2387   request URI's authority component is the same as the request-target.
2388   Otherwise, if a <x:ref>Host</x:ref> header field is supplied with a
2389   non-empty field-value, then the authority component is the same as the
2390   Host field-value. Otherwise, the authority component is the concatenation of
2391   the default host name configured for the server, a colon (":"), and the
2392   connection's incoming TCP port number in decimal form.
2395   If the request-target is in authority-form or asterisk-form, then the
2396   effective request URI's combined path and query component is empty.
2397   Otherwise, the combined path and query component is the same as the
2398   request-target.
2401   The components of the effective request URI, once determined as above,
2402   can be combined into absolute-URI form by concatenating the scheme,
2403   "://", authority, and combined path and query component.
2407   Example 1: the following message received over an insecure TCP connection
2409<artwork type="example" x:indent-with="  ">
2410GET /pub/WWW/TheProject.html HTTP/1.1
2416  has an effective request URI of
2418<artwork type="example" x:indent-with="  ">
2424   Example 2: the following message received over a TLS-secured TCP connection
2426<artwork type="example" x:indent-with="  ">
2427OPTIONS * HTTP/1.1
2433  has an effective request URI of
2435<artwork type="example" x:indent-with="  ">
2440   An origin server that does not allow resources to differ by requested
2441   host &MAY; ignore the <x:ref>Host</x:ref> field-value and instead replace it
2442   with a configured server name when constructing the effective request URI.
2445   Recipients of an HTTP/1.0 request that lacks a <x:ref>Host</x:ref> header
2446   field &MAY; attempt to use heuristics (e.g., examination of the URI path for
2447   something unique to a particular host) in order to guess the
2448   effective request URI's authority component.
2452<section title="Message Forwarding" anchor="message.forwarding">
2454   As described in <xref target="intermediaries"/>, intermediaries can serve
2455   a variety of roles in the processing of HTTP requests and responses.
2456   Some intermediaries are used to improve performance or availability.
2457   Others are used for access control or to filter content.
2458   Since an HTTP stream has characteristics similar to a pipe-and-filter
2459   architecture, there are no inherent limits to the extent an intermediary
2460   can enhance (or interfere) with either direction of the stream.
2463   Intermediaries that forward a message &MUST; implement the
2464   <x:ref>Connection</x:ref> header field, as specified in
2465   <xref target="header.connection"/>, to exclude fields that are only
2466   intended for the incoming connection.
2469   In order to avoid request loops, a proxy that forwards requests to other
2470   proxies &MUST; be able to recognize and exclude all of its own server
2471   names, including any aliases, local variations, or literal IP addresses.
2475<section title="Via" anchor="header.via">
2476  <iref primary="true" item="Via header field" x:for-anchor=""/>
2477  <x:anchor-alias value="pseudonym"/>
2478  <x:anchor-alias value="received-by"/>
2479  <x:anchor-alias value="received-protocol"/>
2480  <x:anchor-alias value="Via"/>
2482   The "Via" header field &MUST; be sent by a proxy or gateway
2483   in forwarded messages to
2484   indicate the intermediate protocols and recipients between the user
2485   agent and the server on requests, and between the origin server and
2486   the client on responses. It is analogous to the "Received" field
2487   used by email systems (<xref target="RFC5322" x:fmt="of" x:sec="3.6.7"/>).
2488   Via is used in HTTP for tracking message forwards,
2489   avoiding request loops, and identifying the protocol capabilities of
2490   all senders along the request/response chain.
2492<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"/>
2493  <x:ref>Via</x:ref>               = 1#( <x:ref>received-protocol</x:ref> <x:ref>RWS</x:ref> <x:ref>received-by</x:ref>
2494                          [ <x:ref>RWS</x:ref> <x:ref>comment</x:ref> ] )
2495  <x:ref>received-protocol</x:ref> = [ <x:ref>protocol-name</x:ref> "/" ] <x:ref>protocol-version</x:ref>
2496  <x:ref>received-by</x:ref>       = ( <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ) / <x:ref>pseudonym</x:ref>
2497  <x:ref>pseudonym</x:ref>         = <x:ref>token</x:ref>
2500   The received-protocol indicates the protocol version of the message
2501   received by the server or client along each segment of the
2502   request/response chain. The received-protocol version is appended to
2503   the Via field value when the message is forwarded so that information
2504   about the protocol capabilities of upstream applications remains
2505   visible to all recipients.
2508   The protocol-name is excluded if and only if it would be "HTTP". The
2509   received-by field is normally the host and optional port number of a
2510   recipient server or client that subsequently forwarded the message.
2511   However, if the real host is considered to be sensitive information,
2512   it &MAY; be replaced by a pseudonym. If the port is not given, it &MAY;
2513   be assumed to be the default port of the received-protocol.
2516   Multiple Via field values represent each proxy or gateway that has
2517   forwarded the message. Each recipient &MUST; append its information
2518   such that the end result is ordered according to the sequence of
2519   forwarding applications.
2522   Comments &MAY; be used in the Via header field to identify the software
2523   of each recipient, analogous to the <x:ref>User-Agent</x:ref> and
2524   <x:ref>Server</x:ref> header fields. However, all comments in the Via field
2525   are optional and &MAY; be removed by any recipient prior to forwarding the
2526   message.
2529   For example, a request message could be sent from an HTTP/1.0 user
2530   agent to an internal proxy code-named "fred", which uses HTTP/1.1 to
2531   forward the request to a public proxy at, which completes
2532   the request by forwarding it to the origin server at
2533   The request received by would then have the following
2534   Via header field:
2536<figure><artwork type="example">
2537  Via: 1.0 fred, 1.1 (Apache/1.1)
2540   A proxy or gateway used as a portal through a network firewall
2541   &SHOULD-NOT; forward the names and ports of hosts within the firewall
2542   region unless it is explicitly enabled to do so. If not enabled, the
2543   received-by host of any host behind the firewall &SHOULD; be replaced
2544   by an appropriate pseudonym for that host.
2547   A proxy or gateway &MAY; combine an ordered subsequence of Via header
2548   field entries into a single such entry if the entries have identical
2549   received-protocol values. For example,
2551<figure><artwork type="example">
2552  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
2555  could be collapsed to
2557<figure><artwork type="example">
2558  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
2561   Senders &SHOULD-NOT; combine multiple entries unless they are all
2562   under the same organizational control and the hosts have already been
2563   replaced by pseudonyms. Senders &MUST-NOT; combine entries which
2564   have different received-protocol values.
2568<section title="Message Transforming" anchor="message.transforming">
2570   If a proxy receives a request-target with a host name that is not a
2571   fully qualified domain name, it &MAY; add its own domain to the host name
2572   it received when forwarding the request.  A proxy &MUST-NOT; change the
2573   host name if it is a fully qualified domain name.
2576   A non-transforming proxy &MUST-NOT; modify the "path-absolute" and "query"
2577   parts of the received request-target when forwarding it to the next inbound
2578   server, except as noted above to replace an empty path with "/" or "*".
2581   A non-transforming proxy &MUST; preserve the message payload (&payload;),
2582   though it &MAY; change the message body through application or removal
2583   of a transfer-coding (<xref target="transfer.codings"/>).
2586   A non-transforming proxy &SHOULD-NOT; modify header fields that provide
2587   information about the end points of the communication chain, the resource
2588   state, or the selected representation.
2591   A non-transforming proxy &MUST-NOT; modify any of the following fields in a
2592   request or response, and it &MUST-NOT; add any of these fields if not
2593   already present:
2594  <list style="symbols">
2595    <t><x:ref>Allow</x:ref> (&header-allow;)</t>
2596    <t><x:ref>Content-Location</x:ref> (&header-content-location;)</t>
2597    <t>Content-MD5 (<xref target="RFC2616" x:fmt="of" x:sec="14.15"/>)</t>
2598    <t><x:ref>ETag</x:ref> (&header-etag;)</t>
2599    <t><x:ref>Last-Modified</x:ref> (&header-last-modified;)</t>
2600    <t><x:ref>Server</x:ref> (&header-server;)</t>
2601  </list>
2604   A non-transforming proxy &MUST-NOT; modify an <x:ref>Expires</x:ref>
2605   header field (&header-expires;) if already present in a response, but
2606   it &MAY; add an <x:ref>Expires</x:ref> header field with a field-value
2607   identical to that of the <x:ref>Date</x:ref> header field.
2610   A proxy &MUST-NOT; modify or add any of the following fields in a
2611   message that contains the no-transform cache-control directive:
2612  <list style="symbols">
2613    <t><x:ref>Content-Encoding</x:ref> (&header-content-encoding;)</t>
2614    <t><x:ref>Content-Range</x:ref> (&header-content-range;)</t>
2615    <t><x:ref>Content-Type</x:ref> (&header-content-type;)</t>
2616  </list>
2619   A transforming proxy &MAY; modify or add these fields to a message
2620   that does not include no-transform, but if it does so, it &MUST; add a
2621   Warning 214 (Transformation applied) if one does not already appear
2622   in the message (see &header-warning;).
2625  <t>
2626    <x:h>Warning:</x:h> Unnecessary modification of header fields might
2627    cause authentication failures if stronger authentication
2628    mechanisms are introduced in later versions of HTTP. Such
2629    authentication mechanisms &MAY; rely on the values of header fields
2630    not listed here.
2631  </t>
2635<section title="Associating a Response to a Request" anchor="">
2637   HTTP does not include a request identifier for associating a given
2638   request message with its corresponding one or more response messages.
2639   Hence, it relies on the order of response arrival to correspond exactly
2640   to the order in which requests are made on the same connection.
2641   More than one response message per request only occurs when one or more
2642   informational responses (<x:ref>1xx</x:ref>, see &status-1xx;) precede a final response
2643   to the same request.
2646   A client that uses persistent connections and sends more than one request
2647   per connection &MUST; maintain a list of outstanding requests in the
2648   order sent on that connection and &MUST; associate each received response
2649   message to the highest ordered request that has not yet received a final
2650   (non-<x:ref>1xx</x:ref>) response.
2655<section title="Connection Management" anchor="">
2657   HTTP messaging is independent of the underlying transport or
2658   session-layer connection protocol(s).  HTTP only presumes a reliable
2659   transport with in-order delivery of requests and the corresponding
2660   in-order delivery of responses.  The mapping of HTTP request and
2661   response structures onto the data units of an underlying transport
2662   protocol is outside the scope of this specification.
2665   As described in <xref target="connecting.inbound"/>, the specific
2666   connection protocols to be used for an HTTP interaction are determined by
2667   client configuration and the <x:ref>target URI</x:ref>.
2668   For example, the "http" URI scheme
2669   (<xref target="http.uri"/>) indicates a default connection of TCP
2670   over IP, with a default TCP port of 80, but the client might be
2671   configured to use a proxy via some other connection, port, or protocol.
2674   HTTP implementations are expected to engage in connection management,
2675   which includes maintaining the state of current connections,
2676   establishing a new connection or reusing an existing connection,
2677   processing messages received on a connection, detecting connection
2678   failures, and closing each connection.
2679   Most clients maintain multiple connections in parallel, including
2680   more than one connection per server endpoint.
2681   Most servers are designed to maintain thousands of concurrent connections,
2682   while controlling request queues to enable fair use and detect
2683   denial of service attacks.
2686<section title="Connection" anchor="header.connection">
2687  <iref primary="true" item="Connection header field" x:for-anchor=""/>
2688  <iref primary="true" item="close" x:for-anchor=""/>
2689  <x:anchor-alias value="Connection"/>
2690  <x:anchor-alias value="connection-option"/>
2691  <x:anchor-alias value="close"/>
2693   The "Connection" header field allows the sender to indicate desired
2694   control options for the current connection.  In order to avoid confusing
2695   downstream recipients, a proxy or gateway &MUST; remove or replace any
2696   received connection options before forwarding the message.
2699   When a header field is used to supply control information for or about
2700   the current connection, the sender &SHOULD; list the corresponding
2701   field-name within the "Connection" header field.
2702   A proxy or gateway &MUST; parse a received Connection
2703   header field before a message is forwarded and, for each
2704   connection-option in this field, remove any header field(s) from
2705   the message with the same name as the connection-option, and then
2706   remove the Connection header field itself (or replace it with the
2707   intermediary's own connection options for the forwarded message).
2710   Hence, the Connection header field provides a declarative way of
2711   distinguishing header fields that are only intended for the
2712   immediate recipient ("hop-by-hop") from those fields that are
2713   intended for all recipients on the chain ("end-to-end"), enabling the
2714   message to be self-descriptive and allowing future connection-specific
2715   extensions to be deployed without fear that they will be blindly
2716   forwarded by older intermediaries.
2719   The Connection header field's value has the following grammar:
2721<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="connection-option"/>
2722  <x:ref>Connection</x:ref>        = 1#<x:ref>connection-option</x:ref>
2723  <x:ref>connection-option</x:ref> = <x:ref>token</x:ref>
2726   Connection options are case-insensitive.
2729   A sender &MUST-NOT; include field-names in the Connection header
2730   field-value for fields that are defined as expressing constraints
2731   for all recipients in the request or response chain, such as the
2732   Cache-Control header field (&header-cache-control;).
2735   The connection options do not have to correspond to a header field
2736   present in the message, since a connection-specific header field
2737   might not be needed if there are no parameters associated with that
2738   connection option.  Recipients that trigger certain connection
2739   behavior based on the presence of connection options &MUST; do so
2740   based on the presence of the connection-option rather than only the
2741   presence of the optional header field.  In other words, if the
2742   connection option is received as a header field but not indicated
2743   within the Connection field-value, then the recipient &MUST; ignore
2744   the connection-specific header field because it has likely been
2745   forwarded by an intermediary that is only partially conformant.
2748   When defining new connection options, specifications ought to
2749   carefully consider existing deployed header fields and ensure
2750   that the new connection option does not share the same name as
2751   an unrelated header field that might already be deployed.
2752   Defining a new connection option essentially reserves that potential
2753   field-name for carrying additional information related to the
2754   connection option, since it would be unwise for senders to use
2755   that field-name for anything else.
2758   The "<x:dfn>close</x:dfn>" connection option is defined for a
2759   sender to signal that this connection will be closed after completion of
2760   the response. For example,
2762<figure><artwork type="example">
2763  Connection: close
2766   in either the request or the response header fields indicates that
2767   the connection &SHOULD; be closed after the current request/response
2768   is complete (<xref target="persistent.tear-down"/>).
2771   A client that does not support persistent connections &MUST;
2772   send the "close" connection option in every request message.
2775   A server that does not support persistent connections &MUST;
2776   send the "close" connection option in every response message that
2777   does not have a <x:ref>1xx (Informational)</x:ref> status code.
2781<section title="Persistent Connections" anchor="persistent.connections">
2782  <x:anchor-alias value="persistent connections"/>
2784   HTTP was originally designed to use a separate connection for each
2785   request/response pair. As the Web evolved and embedded requests became
2786   common for inline images, the connection establishment overhead was
2787   a significant drain on performance and a concern for Internet congestion.
2788   Message framing (via <x:ref>Content-Length</x:ref>) and optional
2789   long-lived connections (via Keep-Alive) were added to HTTP/1.0 in order
2790   to improve performance for some requests. However, these extensions were
2791   insufficient for dynamically generated responses and difficult to use
2792   with intermediaries.
2795   HTTP/1.1 defaults to the use of "<x:ref>persistent connections</x:ref>",
2796   which allow multiple requests and responses to be carried over a single
2797   connection. The "<x:ref>close</x:ref>" connection-option is used to
2798   signal that a connection will close after the current request/response.
2799   Persistent connections have a number of advantages:
2800  <list style="symbols">
2801      <t>
2802        By opening and closing fewer connections, CPU time is saved
2803        in routers and hosts (clients, servers, proxies, gateways,
2804        tunnels, or caches), and memory used for protocol control
2805        blocks can be saved in hosts.
2806      </t>
2807      <t>
2808        Most requests and responses can be pipelined on a connection.
2809        Pipelining allows a client to make multiple requests without
2810        waiting for each response, allowing a single connection to
2811        be used much more efficiently and with less overall latency.
2812      </t>
2813      <t>
2814        For TCP connections, network congestion is reduced by eliminating the
2815        packets associated with the three way handshake and graceful close
2816        procedures, and by allowing sufficient time to determine the
2817        congestion state of the network.
2818      </t>
2819      <t>
2820        Latency on subsequent requests is reduced since there is no time
2821        spent in the connection opening handshake.
2822      </t>
2823      <t>
2824        HTTP can evolve more gracefully, since most errors can be reported
2825        without the penalty of closing the connection. Clients using
2826        future versions of HTTP might optimistically try a new feature,
2827        but if communicating with an older server, retry with old
2828        semantics after an error is reported.
2829      </t>
2830    </list>
2833   HTTP implementations &SHOULD; implement persistent connections.
2836<section title="Establishment" anchor="persistent.establishment">
2838   It is beyond the scope of this specification to describe how connections
2839   are established via various transport or session-layer protocols.
2840   Each connection applies to only one transport link.
2843   A recipient determines whether a connection is persistent or not based on
2844   the most recently received message's protocol version and
2845   <x:ref>Connection</x:ref> header field (if any):
2846   <list style="symbols">
2847     <t>If the <x:ref>close</x:ref> connection option is present, the
2848        connection will not persist after the current response; else,</t>
2849     <t>If the received protocol is HTTP/1.1 (or later), the connection will
2850        persist after the current response; else,</t>
2851     <t>If the received protocol is HTTP/1.0, the "keep-alive"
2852        connection option is present, the recipient is not a proxy, and
2853        the recipient wishes to honor the HTTP/1.0 "keep-alive" mechanism,
2854        the connection will persist after the current response; otherwise,</t>
2855     <t>The connection will close after the current response.</t>
2856   </list>
2859   A proxy server &MUST-NOT; maintain a persistent connection with an
2860   HTTP/1.0 client (see <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/> for
2861   information and discussion of the problems with the Keep-Alive header field
2862   implemented by many HTTP/1.0 clients).
2866<section title="Reuse" anchor="persistent.reuse">
2868   In order to remain persistent, all messages on a connection &MUST;
2869   have a self-defined message length (i.e., one not defined by closure
2870   of the connection), as described in <xref target="message.body"/>.
2873   A server &MAY; assume that an HTTP/1.1 client intends to maintain a
2874   persistent connection until a <x:ref>close</x:ref> connection option
2875   is received in a request.
2878   A client &MAY; reuse a persistent connection until it sends or receives
2879   a <x:ref>close</x:ref> connection option or receives an HTTP/1.0 response
2880   without a "keep-alive" connection option.
2883   Clients and servers &SHOULD-NOT; assume that a persistent connection is
2884   maintained for HTTP versions less than 1.1 unless it is explicitly
2885   signaled.
2886   See <xref target="compatibility.with.http.1.0.persistent.connections"/>
2887   for more information on backward compatibility with HTTP/1.0 clients.
2890<section title="Pipelining" anchor="pipelining">
2892   A client that supports persistent connections &MAY; "pipeline" its
2893   requests (i.e., send multiple requests without waiting for each
2894   response). A server &MUST; send its responses to those requests in the
2895   same order that the requests were received.
2898   Clients which assume persistent connections and pipeline immediately
2899   after connection establishment &SHOULD; be prepared to retry their
2900   connection if the first pipelined attempt fails. If a client does
2901   such a retry, it &MUST-NOT; pipeline before it knows the connection is
2902   persistent. Clients &MUST; also be prepared to resend their requests if
2903   the server closes the connection before sending all of the
2904   corresponding responses.
2907   Clients &SHOULD-NOT; pipeline requests using non-idempotent request methods
2908   or non-idempotent sequences of request methods (see &idempotent-methods;).
2909   Otherwise, a premature termination of the transport connection could lead
2910   to indeterminate results. A client wishing to send a non-idempotent
2911   request &SHOULD; wait to send that request until it has received the
2912   response status line for the previous request.
2916<section title="Retrying Requests" anchor="persistent.retrying.requests">
2918   Senders can close the transport connection at any time. Therefore,
2919   clients, servers, and proxies &MUST; be able to recover
2920   from asynchronous close events. Client software &MAY; reopen the
2921   transport connection and retransmit the aborted sequence of requests
2922   without user interaction so long as the request sequence is
2923   idempotent (see &idempotent-methods;). Non-idempotent request methods or sequences
2924   &MUST-NOT; be automatically retried, although user agents &MAY; offer a
2925   human operator the choice of retrying the request(s). Confirmation by
2926   user-agent software with semantic understanding of the application
2927   &MAY; substitute for user confirmation. The automatic retry &SHOULD-NOT;
2928   be repeated if the second sequence of requests fails.
2933<section title="Concurrency" anchor="persistent.concurrency">
2935   Clients &SHOULD; limit the number of simultaneous
2936   connections that they maintain to a given server.
2939   Previous revisions of HTTP gave a specific number of connections as a
2940   ceiling, but this was found to be impractical for many applications. As a
2941   result, this specification does not mandate a particular maximum number of
2942   connections, but instead encourages clients to be conservative when opening
2943   multiple connections.
2946   Multiple connections are typically used to avoid the "head-of-line
2947   blocking" problem, wherein a request that takes significant server-side
2948   processing and/or has a large payload blocks subsequent requests on the
2949   same connection. However, each connection consumes server resources.
2950   Furthermore, using multiple connections can cause undesirable side effects
2951   in congested networks.
2954   Note that servers might reject traffic that they deem abusive, including an
2955   excessive number of connections from a client.
2959<section title="Failures and Time-outs" anchor="persistent.failures">
2961   Servers will usually have some time-out value beyond which they will
2962   no longer maintain an inactive connection. Proxy servers might make
2963   this a higher value since it is likely that the client will be making
2964   more connections through the same server. The use of persistent
2965   connections places no requirements on the length (or existence) of
2966   this time-out for either the client or the server.
2969   When a client or server wishes to time-out it &SHOULD; issue a graceful
2970   close on the transport connection. Clients and servers &SHOULD; both
2971   constantly watch for the other side of the transport close, and
2972   respond to it as appropriate. If a client or server does not detect
2973   the other side's close promptly it could cause unnecessary resource
2974   drain on the network.
2977   A client, server, or proxy &MAY; close the transport connection at any
2978   time. For example, a client might have started to send a new request
2979   at the same time that the server has decided to close the "idle"
2980   connection. From the server's point of view, the connection is being
2981   closed while it was idle, but from the client's point of view, a
2982   request is in progress.
2985   Servers &SHOULD; maintain persistent connections and allow the underlying
2986   transport's flow control mechanisms to resolve temporary overloads, rather
2987   than terminate connections with the expectation that clients will retry.
2988   The latter technique can exacerbate network congestion.
2991   A client sending a message body &SHOULD; monitor
2992   the network connection for an error status code while it is transmitting
2993   the request. If the client sees an error status code, it &SHOULD;
2994   immediately cease transmitting the body and close the connection.
2998<section title="Tear-down" anchor="persistent.tear-down">
2999  <iref primary="false" item="Connection header field" x:for-anchor=""/>
3000  <iref primary="false" item="close" x:for-anchor=""/>
3002   The <x:ref>Connection</x:ref> header field
3003   (<xref target="header.connection"/>) provides a "<x:ref>close</x:ref>"
3004   connection option that a sender &SHOULD; send when it wishes to close
3005   the connection after the current request/response pair.
3008   A client that sends a <x:ref>close</x:ref> connection option &MUST-NOT;
3009   send further requests on that connection (after the one containing
3010   <x:ref>close</x:ref>) and &MUST; close the connection after reading the
3011   final response message corresponding to this request.
3014   A server that receives a <x:ref>close</x:ref> connection option &MUST;
3015   initiate a lingering close of the connection after it sends the final
3016   response to the request that contained <x:ref>close</x:ref>.
3017   The server &SHOULD; include a <x:ref>close</x:ref> connection option
3018   in its final response on that connection. The server &MUST-NOT; process
3019   any further requests received on that connection.
3022   A server that sends a <x:ref>close</x:ref> connection option &MUST;
3023   initiate a lingering close of the connection after it sends the
3024   response containing <x:ref>close</x:ref>. The server &MUST-NOT; process
3025   any further requests received on that connection.
3028   A client that receives a <x:ref>close</x:ref> connection option &MUST;
3029   cease sending requests on that connection and close the connection
3030   after reading the response message containing the close; if additional
3031   pipelined requests had been sent on the connection, the client &SHOULD;
3032   assume that they will not be processed by the server.
3035   If a server performs an immediate close of a TCP connection, there is a
3036   significant risk that the client will not be able to read the last HTTP
3037   response.  If the server receives additional data from the client on a
3038   fully-closed connection, such as another request that was sent by the
3039   client before receiving the server's response, the server's TCP stack will
3040   send a reset packet to the client; unfortunately, the reset packet might
3041   erase the client's unacknowledged input buffers before they can be read
3042   and interpreted by the client's HTTP parser.
3045   To avoid the TCP reset problem, a server can perform a lingering close on a
3046   connection by closing only the write side of the read/write connection
3047   (a half-close) and continuing to read from the connection until the
3048   connection is closed by the client or the server is reasonably certain
3049   that its own TCP stack has received the client's acknowledgement of the
3050   packet(s) containing the server's last response. It is then safe for the
3051   server to fully close the connection.
3054   It is unknown whether the reset problem is exclusive to TCP or might also
3055   be found in other transport connection protocols.
3060<section title="Upgrade" anchor="header.upgrade">
3061  <iref primary="true" item="Upgrade header field" x:for-anchor=""/>
3062  <x:anchor-alias value="Upgrade"/>
3063  <x:anchor-alias value="protocol"/>
3064  <x:anchor-alias value="protocol-name"/>
3065  <x:anchor-alias value="protocol-version"/>
3067   The "Upgrade" header field is intended to provide a simple mechanism
3068   for transitioning from HTTP/1.1 to some other protocol on the same
3069   connection.  A client &MAY; send a list of protocols in the Upgrade
3070   header field of a request to invite the server to switch to one or
3071   more of those protocols before sending the final response.
3072   A server &MUST; send an Upgrade header field in <x:ref>101 (Switching
3073   Protocols)</x:ref> responses to indicate which protocol(s) are being
3074   switched to, and &MUST; send it in <x:ref>426 (Upgrade Required)</x:ref>
3075   responses to indicate acceptable protocols.
3076   A server &MAY; send an Upgrade header field in any other response to
3077   indicate that they might be willing to upgrade to one of the
3078   specified protocols for a future request.
3080<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Upgrade"/>
3081  <x:ref>Upgrade</x:ref>          = 1#<x:ref>protocol</x:ref>
3083  <x:ref>protocol</x:ref>         = <x:ref>protocol-name</x:ref> ["/" <x:ref>protocol-version</x:ref>]
3084  <x:ref>protocol-name</x:ref>    = <x:ref>token</x:ref>
3085  <x:ref>protocol-version</x:ref> = <x:ref>token</x:ref>
3088   For example,
3090<figure><artwork type="example">
3091  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
3094   Upgrade eases the difficult transition between incompatible protocols by
3095   allowing the client to initiate a request in the more commonly
3096   supported protocol while indicating to the server that it would like
3097   to use a "better" protocol if available (where "better" is determined
3098   by the server, possibly according to the nature of the request method
3099   or target resource).
3102   Upgrade cannot be used to insist on a protocol change; its acceptance and
3103   use by the server is optional. The capabilities and nature of the
3104   application-level communication after the protocol change is entirely
3105   dependent upon the new protocol chosen, although the first action
3106   after changing the protocol &MUST; be a response to the initial HTTP
3107   request that contained the Upgrade header field.
3110   For example, if the Upgrade header field is received in a GET request
3111   and the server decides to switch protocols, then it &MUST; first respond
3112   with a <x:ref>101 (Switching Protocols)</x:ref> message in HTTP/1.1 and
3113   then immediately follow that with the new protocol's equivalent of a
3114   response to a GET on the target resource.  This allows a connection to be
3115   upgraded to protocols with the same semantics as HTTP without the
3116   latency cost of an additional round-trip.  A server &MUST-NOT; switch
3117   protocols unless the received message semantics can be honored by the new
3118   protocol; an OPTIONS request can be honored by any protocol.
3121   When Upgrade is sent, a sender &MUST; also send a
3122   <x:ref>Connection</x:ref> header field (<xref target="header.connection"/>)
3123   that contains the "upgrade" connection option, in order to prevent Upgrade
3124   from being accidentally forwarded by intermediaries that might not implement
3125   the listed protocols.  A server &MUST; ignore an Upgrade header field that
3126   is received in an HTTP/1.0 request.
3129   The Upgrade header field only applies to switching application-level
3130   protocols on the existing connection; it cannot be used
3131   to switch to a protocol on a different connection. For that purpose, it is
3132   more appropriate to use a <x:ref>3xx (Redirection)</x:ref> response
3133   (&status-3xx;).
3136   This specification only defines the protocol name "HTTP" for use by
3137   the family of Hypertext Transfer Protocols, as defined by the HTTP
3138   version rules of <xref target="http.version"/> and future updates to this
3139   specification. Additional tokens can be registered with IANA using the
3140   registration procedure defined in <xref target="upgrade.token.registry"/>.
3145<section title="IANA Considerations" anchor="IANA.considerations">
3147<section title="Header Field Registration" anchor="header.field.registration">
3149   HTTP header fields are registered within the Message Header Field Registry
3150   <xref target="RFC3864"/> maintained by IANA at
3151   <eref target=""/>.
3154   This document defines the following HTTP header fields, so their
3155   associated registry entries shall be updated according to the permanent
3156   registrations below:
3158<?BEGININC p1-messaging.iana-headers ?>
3159<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
3160<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
3161   <ttcol>Header Field Name</ttcol>
3162   <ttcol>Protocol</ttcol>
3163   <ttcol>Status</ttcol>
3164   <ttcol>Reference</ttcol>
3166   <c>Connection</c>
3167   <c>http</c>
3168   <c>standard</c>
3169   <c>
3170      <xref target="header.connection"/>
3171   </c>
3172   <c>Content-Length</c>
3173   <c>http</c>
3174   <c>standard</c>
3175   <c>
3176      <xref target="header.content-length"/>
3177   </c>
3178   <c>Host</c>
3179   <c>http</c>
3180   <c>standard</c>
3181   <c>
3182      <xref target=""/>
3183   </c>
3184   <c>TE</c>
3185   <c>http</c>
3186   <c>standard</c>
3187   <c>
3188      <xref target="header.te"/>
3189   </c>
3190   <c>Trailer</c>
3191   <c>http</c>
3192   <c>standard</c>
3193   <c>
3194      <xref target="header.trailer"/>
3195   </c>
3196   <c>Transfer-Encoding</c>
3197   <c>http</c>
3198   <c>standard</c>
3199   <c>
3200      <xref target="header.transfer-encoding"/>
3201   </c>
3202   <c>Upgrade</c>
3203   <c>http</c>
3204   <c>standard</c>
3205   <c>
3206      <xref target="header.upgrade"/>
3207   </c>
3208   <c>Via</c>
3209   <c>http</c>
3210   <c>standard</c>
3211   <c>
3212      <xref target="header.via"/>
3213   </c>
3216<?ENDINC p1-messaging.iana-headers ?>
3218   Furthermore, the header field-name "Close" shall be registered as
3219   "reserved", since using that name as an HTTP header field might
3220   conflict with the "close" connection option of the "<x:ref>Connection</x:ref>"
3221   header field (<xref target="header.connection"/>).
3223<texttable align="left" suppress-title="true">
3224   <ttcol>Header Field Name</ttcol>
3225   <ttcol>Protocol</ttcol>
3226   <ttcol>Status</ttcol>
3227   <ttcol>Reference</ttcol>
3229   <c>Close</c>
3230   <c>http</c>
3231   <c>reserved</c>
3232   <c>
3233      <xref target="header.field.registration"/>
3234   </c>
3237   The change controller is: "IETF ( - Internet Engineering Task Force".
3241<section title="URI Scheme Registration" anchor="uri.scheme.registration">
3243   IANA maintains the registry of URI Schemes <xref target="RFC4395"/> at
3244   <eref target=""/>.
3247   This document defines the following URI schemes, so their
3248   associated registry entries shall be updated according to the permanent
3249   registrations below:
3251<texttable align="left" suppress-title="true">
3252   <ttcol>URI Scheme</ttcol>
3253   <ttcol>Description</ttcol>
3254   <ttcol>Reference</ttcol>
3256   <c>http</c>
3257   <c>Hypertext Transfer Protocol</c>
3258   <c><xref target="http.uri"/></c>
3260   <c>https</c>
3261   <c>Hypertext Transfer Protocol Secure</c>
3262   <c><xref target="https.uri"/></c>
3266<section title="Internet Media Type Registrations" anchor="">
3268   This document serves as the specification for the Internet media types
3269   "message/http" and "application/http". The following is to be registered with
3270   IANA (see <xref target="RFC4288"/>).
3272<section title="Internet Media Type message/http" anchor="">
3273<iref item="Media Type" subitem="message/http" primary="true"/>
3274<iref item="message/http Media Type" primary="true"/>
3276   The message/http type can be used to enclose a single HTTP request or
3277   response message, provided that it obeys the MIME restrictions for all
3278   "message" types regarding line length and encodings.
3281  <list style="hanging" x:indent="12em">
3282    <t hangText="Type name:">
3283      message
3284    </t>
3285    <t hangText="Subtype name:">
3286      http
3287    </t>
3288    <t hangText="Required parameters:">
3289      none
3290    </t>
3291    <t hangText="Optional parameters:">
3292      version, msgtype
3293      <list style="hanging">
3294        <t hangText="version:">
3295          The HTTP-version number of the enclosed message
3296          (e.g., "1.1"). If not present, the version can be
3297          determined from the first line of the body.
3298        </t>
3299        <t hangText="msgtype:">
3300          The message type &mdash; "request" or "response". If not
3301          present, the type can be determined from the first
3302          line of the body.
3303        </t>
3304      </list>
3305    </t>
3306    <t hangText="Encoding considerations:">
3307      only "7bit", "8bit", or "binary" are permitted
3308    </t>
3309    <t hangText="Security considerations:">
3310      none
3311    </t>
3312    <t hangText="Interoperability considerations:">
3313      none
3314    </t>
3315    <t hangText="Published specification:">
3316      This specification (see <xref target=""/>).
3317    </t>
3318    <t hangText="Applications that use this media type:">
3319    </t>
3320    <t hangText="Additional information:">
3321      <list style="hanging">
3322        <t hangText="Magic number(s):">none</t>
3323        <t hangText="File extension(s):">none</t>
3324        <t hangText="Macintosh file type code(s):">none</t>
3325      </list>
3326    </t>
3327    <t hangText="Person and email address to contact for further information:">
3328      See Authors Section.
3329    </t>
3330    <t hangText="Intended usage:">
3331      COMMON
3332    </t>
3333    <t hangText="Restrictions on usage:">
3334      none
3335    </t>
3336    <t hangText="Author/Change controller:">
3337      IESG
3338    </t>
3339  </list>
3342<section title="Internet Media Type application/http" anchor="">
3343<iref item="Media Type" subitem="application/http" primary="true"/>
3344<iref item="application/http Media Type" primary="true"/>
3346   The application/http type can be used to enclose a pipeline of one or more
3347   HTTP request or response messages (not intermixed).
3350  <list style="hanging" x:indent="12em">
3351    <t hangText="Type name:">
3352      application
3353    </t>
3354    <t hangText="Subtype name:">
3355      http
3356    </t>
3357    <t hangText="Required parameters:">
3358      none
3359    </t>
3360    <t hangText="Optional parameters:">
3361      version, msgtype
3362      <list style="hanging">
3363        <t hangText="version:">
3364          The HTTP-version number of the enclosed messages
3365          (e.g., "1.1"). If not present, the version can be
3366          determined from the first line of the body.
3367        </t>
3368        <t hangText="msgtype:">
3369          The message type &mdash; "request" or "response". If not
3370          present, the type can be determined from the first
3371          line of the body.
3372        </t>
3373      </list>
3374    </t>
3375    <t hangText="Encoding considerations:">
3376      HTTP messages enclosed by this type
3377      are in "binary" format; use of an appropriate
3378      Content-Transfer-Encoding is required when
3379      transmitted via E-mail.
3380    </t>
3381    <t hangText="Security considerations:">
3382      none
3383    </t>
3384    <t hangText="Interoperability considerations:">
3385      none
3386    </t>
3387    <t hangText="Published specification:">
3388      This specification (see <xref target=""/>).
3389    </t>
3390    <t hangText="Applications that use this media type:">
3391    </t>
3392    <t hangText="Additional information:">
3393      <list style="hanging">
3394        <t hangText="Magic number(s):">none</t>
3395        <t hangText="File extension(s):">none</t>
3396        <t hangText="Macintosh file type code(s):">none</t>
3397      </list>
3398    </t>
3399    <t hangText="Person and email address to contact for further information:">
3400      See Authors Section.
3401    </t>
3402    <t hangText="Intended usage:">
3403      COMMON
3404    </t>
3405    <t hangText="Restrictions on usage:">
3406      none
3407    </t>
3408    <t hangText="Author/Change controller:">
3409      IESG
3410    </t>
3411  </list>
3416<section title="Transfer Coding Registry" anchor="transfer.coding.registry">
3418   The HTTP Transfer Coding Registry defines the name space for transfer
3419   coding names.
3422   Registrations &MUST; include the following fields:
3423   <list style="symbols">
3424     <t>Name</t>
3425     <t>Description</t>
3426     <t>Pointer to specification text</t>
3427   </list>
3430   Names of transfer codings &MUST-NOT; overlap with names of content codings
3431   (&content-codings;) unless the encoding transformation is identical, as
3432   is the case for the compression codings defined in
3433   <xref target="compression.codings"/>.
3436   Values to be added to this name space require IETF Review (see
3437   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
3438   conform to the purpose of transfer coding defined in this section.
3439   Use of program names for the identification of encoding formats
3440   is not desirable and is discouraged for future encodings.
3443   The registry itself is maintained at
3444   <eref target=""/>.
3448<section title="Transfer Coding Registrations" anchor="transfer.coding.registration">
3450   The HTTP Transfer Coding Registry shall be updated with the registrations
3451   below:
3453<texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table">
3454   <ttcol>Name</ttcol>
3455   <ttcol>Description</ttcol>
3456   <ttcol>Reference</ttcol>
3457   <c>chunked</c>
3458   <c>Transfer in a series of chunks</c>
3459   <c>
3460      <xref target="chunked.encoding"/>
3461   </c>
3462   <c>compress</c>
3463   <c>UNIX "compress" program method</c>
3464   <c>
3465      <xref target="compress.coding"/>
3466   </c>
3467   <c>deflate</c>
3468   <c>"deflate" compression mechanism (<xref target="RFC1951"/>) used inside
3469   the "zlib" data format (<xref target="RFC1950"/>)
3470   </c>
3471   <c>
3472      <xref target="deflate.coding"/>
3473   </c>
3474   <c>gzip</c>
3475   <c>Same as GNU zip <xref target="RFC1952"/></c>
3476   <c>
3477      <xref target="gzip.coding"/>
3478   </c>
3482<section title="Upgrade Token Registry" anchor="upgrade.token.registry">
3484   The HTTP Upgrade Token Registry defines the name space for protocol-name
3485   tokens used to identify protocols in the <x:ref>Upgrade</x:ref> header
3486   field. Each registered protocol name is associated with contact information
3487   and an optional set of specifications that details how the connection
3488   will be processed after it has been upgraded.
3491   Registrations happen on a "First Come First Served" basis (see
3492   <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>) and are subject to the
3493   following rules:
3494  <list style="numbers">
3495    <t>A protocol-name token, once registered, stays registered forever.</t>
3496    <t>The registration &MUST; name a responsible party for the
3497       registration.</t>
3498    <t>The registration &MUST; name a point of contact.</t>
3499    <t>The registration &MAY; name a set of specifications associated with
3500       that token. Such specifications need not be publicly available.</t>
3501    <t>The registration &SHOULD; name a set of expected "protocol-version"
3502       tokens associated with that token at the time of registration.</t>
3503    <t>The responsible party &MAY; change the registration at any time.
3504       The IANA will keep a record of all such changes, and make them
3505       available upon request.</t>
3506    <t>The IESG &MAY; reassign responsibility for a protocol token.
3507       This will normally only be used in the case when a
3508       responsible party cannot be contacted.</t>
3509  </list>
3512   This registration procedure for HTTP Upgrade Tokens replaces that
3513   previously defined in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>.
3517<section title="Upgrade Token Registration" anchor="upgrade.token.registration">
3519   The HTTP Upgrade Token Registry shall be updated with the registration
3520   below:
3522<texttable align="left" suppress-title="true">
3523   <ttcol>Value</ttcol>
3524   <ttcol>Description</ttcol>
3525   <ttcol>Expected Version Tokens</ttcol>
3526   <ttcol>Reference</ttcol>
3528   <c>HTTP</c>
3529   <c>Hypertext Transfer Protocol</c>
3530   <c>any DIGIT.DIGIT (e.g, "2.0")</c>
3531   <c><xref target="http.version"/></c>
3534   The responsible party is: "IETF ( - Internet Engineering Task Force".
3540<section title="Security Considerations" anchor="security.considerations">
3542   This section is meant to inform application developers, information
3543   providers, and users of the security limitations in HTTP/1.1 as
3544   described by this document. The discussion does not include
3545   definitive solutions to the problems revealed, though it does make
3546   some suggestions for reducing security risks.
3549<section title="Personal Information" anchor="personal.information">
3551   HTTP clients are often privy to large amounts of personal information,
3552   including both information provided by the user to interact with resources
3553   (e.g., the user's name, location, mail address, passwords, encryption
3554   keys, etc.) and information about the user's browsing activity over
3555   time (e.g., history, bookmarks, etc.). HTTP implementations need to
3556   prevent unintentional leakage of this information.
3560<section title="Abuse of Server Log Information" anchor="abuse.of.server.log.information">
3562   A server is in the position to save personal data about a user's
3563   requests which might identify their reading patterns or subjects of
3564   interest.  In particular, log information gathered at an intermediary
3565   often contains a history of user agent interaction, across a multitude
3566   of sites, that can be traced to individual users.
3569   HTTP log information is confidential in nature; its handling is often
3570   constrained by laws and regulations.  Log information needs to be securely
3571   stored and appropriate guidelines followed for its analysis.
3572   Anonymization of personal information within individual entries helps,
3573   but is generally not sufficient to prevent real log traces from being
3574   re-identified based on correlation with other access characteristics.
3575   As such, access traces that are keyed to a specific client should not
3576   be published even if the key is pseudonymous.
3579   To minimize the risk of theft or accidental publication, log information
3580   should be purged of personally identifiable information, including
3581   user identifiers, IP addresses, and user-provided query parameters,
3582   as soon as that information is no longer necessary to support operational
3583   needs for security, auditing, or fraud control.
3587<section title="Attacks Based On File and Path Names" anchor="attack.pathname">
3589   Origin servers &SHOULD; be careful to restrict
3590   the documents returned by HTTP requests to be only those that were
3591   intended by the server administrators. If an HTTP server translates
3592   HTTP URIs directly into file system calls, the server &MUST; take
3593   special care not to serve files that were not intended to be
3594   delivered to HTTP clients. For example, UNIX, Microsoft Windows, and
3595   other operating systems use ".." as a path component to indicate a
3596   directory level above the current one. On such a system, an HTTP
3597   server &MUST; disallow any such construct in the request-target if it
3598   would otherwise allow access to a resource outside those intended to
3599   be accessible via the HTTP server. Similarly, files intended for
3600   reference only internally to the server (such as access control
3601   files, configuration files, and script code) &MUST; be protected from
3602   inappropriate retrieval, since they might contain sensitive
3603   information.
3607<section title="DNS-related Attacks" anchor="dns.related.attacks">
3609   HTTP clients rely heavily on the Domain Name Service (DNS), and are thus
3610   generally prone to security attacks based on the deliberate misassociation
3611   of IP addresses and DNS names not protected by DNSSec. Clients need to be
3612   cautious in assuming the validity of an IP number/DNS name association unless
3613   the response is protected by DNSSec (<xref target="RFC4033"/>).
3617<section title="Intermediaries and Caching" anchor="attack.intermediaries">
3619   By their very nature, HTTP intermediaries are men-in-the-middle, and
3620   represent an opportunity for man-in-the-middle attacks. Compromise of
3621   the systems on which the intermediaries run can result in serious security
3622   and privacy problems. Intermediaries have access to security-related
3623   information, personal information about individual users and
3624   organizations, and proprietary information belonging to users and
3625   content providers. A compromised intermediary, or an intermediary
3626   implemented or configured without regard to security and privacy
3627   considerations, might be used in the commission of a wide range of
3628   potential attacks.
3631   Intermediaries that contain a shared cache are especially vulnerable
3632   to cache poisoning attacks.
3635   Implementers need to consider the privacy and security
3636   implications of their design and coding decisions, and of the
3637   configuration options they provide to operators (especially the
3638   default configuration).
3641   Users need to be aware that intermediaries are no more trustworthy than
3642   the people who run them; HTTP itself cannot solve this problem.
3646<section title="Protocol Element Size Overflows" anchor="attack.protocol.element.size.overflows">
3648   Because HTTP uses mostly textual, character-delimited fields, attackers can
3649   overflow buffers in implementations, and/or perform a Denial of Service
3650   against implementations that accept fields with unlimited lengths.
3653   To promote interoperability, this specification makes specific
3654   recommendations for minimum size limits on request-line
3655   (<xref target="request.line"/>)
3656   and blocks of header fields (<xref target="header.fields"/>). These are
3657   minimum recommendations, chosen to be supportable even by implementations
3658   with limited resources; it is expected that most implementations will
3659   choose substantially higher limits.
3662   This specification also provides a way for servers to reject messages that
3663   have request-targets that are too long (&status-414;) or request entities
3664   that are too large (&status-4xx;).
3667   Recipients &SHOULD; carefully limit the extent to which they read other
3668   fields, including (but not limited to) request methods, response status
3669   phrases, header field-names, and body chunks, so as to avoid denial of
3670   service attacks without impeding interoperability.
3675<section title="Acknowledgments" anchor="acks">
3677   This edition of HTTP builds on the many contributions that went into
3678   <xref target="RFC1945" format="none">RFC 1945</xref>,
3679   <xref target="RFC2068" format="none">RFC 2068</xref>,
3680   <xref target="RFC2145" format="none">RFC 2145</xref>, and
3681   <xref target="RFC2616" format="none">RFC 2616</xref>, including
3682   substantial contributions made by the previous authors, editors, and
3683   working group chairs: Tim Berners-Lee, Ari Luotonen, Roy T. Fielding,
3684   Henrik Frystyk Nielsen, Jim Gettys, Jeffrey C. Mogul, Larry Masinter,
3685   Paul J. Leach, and Mark Nottingham.
3686   See <xref target="RFC2616" x:fmt="of" x:sec="16"/> for additional
3687   acknowledgements from prior revisions.
3690   Since 1999, the following contributors have helped improve the HTTP
3691   specification by reporting bugs, asking smart questions, drafting or
3692   reviewing text, and evaluating open issues:
3694<?BEGININC acks ?>
3695<t>Adam Barth,
3696Adam Roach,
3697Addison Phillips,
3698Adrian Chadd,
3699Adrien W. de Croy,
3700Alan Ford,
3701Alan Ruttenberg,
3702Albert Lunde,
3703Alek Storm,
3704Alex Rousskov,
3705Alexandre Morgaut,
3706Alexey Melnikov,
3707Alisha Smith,
3708Amichai Rothman,
3709Amit Klein,
3710Amos Jeffries,
3711Andreas Maier,
3712Andreas Petersson,
3713Anil Sharma,
3714Anne van Kesteren,
3715Anthony Bryan,
3716Asbjorn Ulsberg,
3717Balachander Krishnamurthy,
3718Barry Leiba,
3719Ben Laurie,
3720Benjamin Niven-Jenkins,
3721Bil Corry,
3722Bill Burke,
3723Bjoern Hoehrmann,
3724Bob Scheifler,
3725Boris Zbarsky,
3726Brett Slatkin,
3727Brian Kell,
3728Brian McBarron,
3729Brian Pane,
3730Brian Smith,
3731Bryce Nesbitt,
3732Cameron Heavon-Jones,
3733Carl Kugler,
3734Carsten Bormann,
3735Charles Fry,
3736Chris Newman,
3737Cyrus Daboo,
3738Dale Robert Anderson,
3739Dan Wing,
3740Dan Winship,
3741Daniel Stenberg,
3742Dave Cridland,
3743Dave Crocker,
3744Dave Kristol,
3745David Booth,
3746David Singer,
3747David W. Morris,
3748Diwakar Shetty,
3749Dmitry Kurochkin,
3750Drummond Reed,
3751Duane Wessels,
3752Edward Lee,
3753Eliot Lear,
3754Eran Hammer-Lahav,
3755Eric D. Williams,
3756Eric J. Bowman,
3757Eric Lawrence,
3758Eric Rescorla,
3759Erik Aronesty,
3760Evan Prodromou,
3761Florian Weimer,
3762Frank Ellermann,
3763Fred Bohle,
3764Gabriel Montenegro,
3765Geoffrey Sneddon,
3766Gervase Markham,
3767Grahame Grieve,
3768Greg Wilkins,
3769Harald Tveit Alvestrand,
3770Harry Halpin,
3771Helge Hess,
3772Henrik Nordstrom,
3773Henry S. Thompson,
3774Henry Story,
3775Herbert van de Sompel,
3776Howard Melman,
3777Hugo Haas,
3778Ian Fette,
3779Ian Hickson,
3780Ido Safruti,
3781Ingo Struck,
3782J. Ross Nicoll,
3783James H. Manger,
3784James Lacey,
3785James M. Snell,
3786Jamie Lokier,
3787Jan Algermissen,
3788Jeff Hodges (who came up with the term 'effective Request-URI'),
3789Jeff Walden,
3790Jim Luther,
3791Joe D. Williams,
3792Joe Gregorio,
3793Joe Orton,
3794John C. Klensin,
3795John C. Mallery,
3796John Cowan,
3797John Kemp,
3798John Panzer,
3799John Schneider,
3800John Stracke,
3801John Sullivan,
3802Jonas Sicking,
3803Jonathan Billington,
3804Jonathan Moore,
3805Jonathan Rees,
3806Jonathan Silvera,
3807Jordi Ros,
3808Joris Dobbelsteen,
3809Josh Cohen,
3810Julien Pierre,
3811Jungshik Shin,
3812Justin Chapweske,
3813Justin Erenkrantz,
3814Justin James,
3815Kalvinder Singh,
3816Karl Dubost,
3817Keith Hoffman,
3818Keith Moore,
3819Koen Holtman,
3820Konstantin Voronkov,
3821Kris Zyp,
3822Lisa Dusseault,
3823Maciej Stachowiak,
3824Marc Schneider,
3825Marc Slemko,
3826Mark Baker,
3827Mark Pauley,
3828Mark Watson,
3829Markus Isomaki,
3830Markus Lanthaler,
3831Martin J. Duerst,
3832Martin Musatov,
3833Martin Nilsson,
3834Martin Thomson,
3835Matt Lynch,
3836Matthew Cox,
3837Max Clark,
3838Michael Burrows,
3839Michael Hausenblas,
3840Mike Amundsen,
3841Mike Belshe,
3842Mike Kelly,
3843Mike Schinkel,
3844Miles Sabin,
3845Murray S. Kucherawy,
3846Mykyta Yevstifeyev,
3847Nathan Rixham,
3848Nicholas Shanks,
3849Nico Williams,
3850Nicolas Alvarez,
3851Nicolas Mailhot,
3852Noah Slater,
3853Pablo Castro,
3854Pat Hayes,
3855Patrick R. McManus,
3856Paul E. Jones,
3857Paul Hoffman,
3858Paul Marquess,
3859Peter Lepeska,
3860Peter Saint-Andre,
3861Peter Watkins,
3862Phil Archer,
3863Philippe Mougin,
3864Phillip Hallam-Baker,
3865Poul-Henning Kamp,
3866Preethi Natarajan,
3867Rajeev Bector,
3868Ray Polk,
3869Reto Bachmann-Gmuer,
3870Richard Cyganiak,
3871Robert Brewer,
3872Robert Collins,
3873Robert O'Callahan,
3874Robert Olofsson,
3875Robert Sayre,
3876Robert Siemer,
3877Robert de Wilde,
3878Roberto Javier Godoy,
3879Roberto Peon,
3880Ronny Widjaja,
3881S. Mike Dierken,
3882Salvatore Loreto,
3883Sam Johnston,
3884Sam Ruby,
3885Scott Lawrence (who maintained the original issues list),
3886Sean B. Palmer,
3887Shane McCarron,
3888Stefan Eissing,
3889Stefan Tilkov,
3890Stefanos Harhalakis,
3891Stephane Bortzmeyer,
3892Stephen Farrell,
3893Stephen Ludin,
3894Stuart Williams,
3895Subbu Allamaraju,
3896Sylvain Hellegouarch,
3897Tapan Divekar,
3898Tatsuya Hayashi,
3899Ted Hardie,
3900Thomas Broyer,
3901Thomas Nordin,
3902Thomas Roessler,
3903Tim Bray,
3904Tim Morgan,
3905Tim Olsen,
3906Tom Zhou,
3907Travis Snoozy,
3908Tyler Close,
3909Vincent Murphy,
3910Wenbo Zhu,
3911Werner Baumann,
3912Wilbur Streett,
3913Wilfredo Sanchez Vega,
3914William A. Rowe Jr.,
3915William Chan,
3916Willy Tarreau,
3917Xiaoshu Wang,
3918Yaron Goland,
3919Yngve Nysaeter Pettersen,
3920Yoav Nir,
3921Yogesh Bang,
3922Yutaka Oiwa,
3923Zed A. Shaw, and
3924Zhong Yu.
3926<?ENDINC acks ?>
3932<references title="Normative References">
3934<reference anchor="Part2">
3935  <front>
3936    <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
3937    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3938      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
3939      <address><email></email></address>
3940    </author>
3941    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3942      <organization abbrev="W3C">World Wide Web Consortium</organization>
3943      <address><email></email></address>
3944    </author>
3945    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3946      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3947      <address><email></email></address>
3948    </author>
3949    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
3950  </front>
3951  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
3952  <x:source href="p2-semantics.xml" basename="p2-semantics">
3953    <x:defines>1xx (Informational)</x:defines>
3954    <x:defines>1xx</x:defines>
3955    <x:defines>100 (Continue)</x:defines>
3956    <x:defines>101 (Switching Protocols)</x:defines>
3957    <x:defines>2xx (Successful)</x:defines>
3958    <x:defines>2xx</x:defines>
3959    <x:defines>200 (OK)</x:defines>
3960    <x:defines>204 (No Content)</x:defines>
3961    <x:defines>3xx (Redirection)</x:defines>
3962    <x:defines>3xx</x:defines>
3963    <x:defines>301 (Moved Permanently)</x:defines>
3964    <x:defines>4xx (Client Error)</x:defines>
3965    <x:defines>4xx</x:defines>
3966    <x:defines>400 (Bad Request)</x:defines>
3967    <x:defines>405 (Method Not Allowed)</x:defines>
3968    <x:defines>411 (Length Required)</x:defines>
3969    <x:defines>414 (URI Too Long)</x:defines>
3970    <x:defines>417 (Expectation Failed)</x:defines>
3971    <x:defines>426 (Upgrade Required)</x:defines>
3972    <x:defines>501 (Not Implemented)</x:defines>
3973    <x:defines>502 (Bad Gateway)</x:defines>
3974    <x:defines>505 (HTTP Version Not Supported)</x:defines>
3975    <x:defines>Allow</x:defines>
3976    <x:defines>Content-Encoding</x:defines>
3977    <x:defines>Content-Location</x:defines>
3978    <x:defines>Content-Type</x:defines>
3979    <x:defines>Date</x:defines>
3980    <x:defines>Expect</x:defines>
3981    <x:defines>Location</x:defines>
3982    <x:defines>Server</x:defines>
3983    <x:defines>User-Agent</x:defines>
3984  </x:source>
3987<reference anchor="Part4">
3988  <front>
3989    <title>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</title>
3990    <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
3991      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
3992      <address><email></email></address>
3993    </author>
3994    <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
3995      <organization abbrev="W3C">World Wide Web Consortium</organization>
3996      <address><email></email></address>
3997    </author>
3998    <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
3999      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4000      <address><email></email></address>
4001    </author>
4002    <date month="&ID-MONTH;" year="&ID-YEAR;" />
4003  </front>
4004  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;" />
4005  <x:source basename="p4-conditional" href="p4-conditional.xml">
4006    <x:defines>304 (Not Modified)</x:defines>
4007    <x:defines>ETag</x:defines>
4008    <x:defines>Last-Modified</x:defines>
4009  </x:source>
4012<reference anchor="Part5">
4013  <front>
4014    <title>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title>
4015    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4016      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4017      <address><email></email></address>
4018    </author>
4019    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4020      <organization abbrev="W3C">World Wide Web Consortium</organization>
4021      <address><email></email></address>
4022    </author>
4023    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4024      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4025      <address><email></email></address>
4026    </author>
4027    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4028  </front>
4029  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
4030  <x:source href="p5-range.xml" basename="p5-range">
4031    <x:defines>Content-Range</x:defines>
4032  </x:source>
4035<reference anchor="Part6">
4036  <front>
4037    <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
4038    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4039      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4040      <address><email></email></address>
4041    </author>
4042    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4043      <organization abbrev="W3C">World Wide Web Consortium</organization>
4044      <address><email></email></address>
4045    </author>
4046    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
4047      <organization>Akamai</organization>
4048      <address><email></email></address>
4049    </author>
4050    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4051      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4052      <address><email></email></address>
4053    </author>
4054    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4055  </front>
4056  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
4057  <x:source href="p6-cache.xml" basename="p6-cache">
4058    <x:defines>Expires</x:defines>
4059  </x:source>
4062<reference anchor="Part7">
4063  <front>
4064    <title>Hypertext Transfer Protocol (HTTP/1.1): Authentication</title>
4065    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4066      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4067      <address><email></email></address>
4068    </author>
4069    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4070      <organization abbrev="W3C">World Wide Web Consortium</organization>
4071      <address><email></email></address>
4072    </author>
4073    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4074      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4075      <address><email></email></address>
4076    </author>
4077    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4078  </front>
4079  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-&ID-VERSION;"/>
4080  <x:source href="p7-auth.xml" basename="p7-auth">
4081    <x:defines>Proxy-Authenticate</x:defines>
4082    <x:defines>Proxy-Authorization</x:defines>
4083  </x:source>
4086<reference anchor="RFC5234">
4087  <front>
4088    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
4089    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
4090      <organization>Brandenburg InternetWorking</organization>
4091      <address>
4092        <email></email>
4093      </address> 
4094    </author>
4095    <author initials="P." surname="Overell" fullname="Paul Overell">
4096      <organization>THUS plc.</organization>
4097      <address>
4098        <email></email>
4099      </address>
4100    </author>
4101    <date month="January" year="2008"/>
4102  </front>
4103  <seriesInfo name="STD" value="68"/>
4104  <seriesInfo name="RFC" value="5234"/>
4107<reference anchor="RFC2119">
4108  <front>
4109    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
4110    <author initials="S." surname="Bradner" fullname="Scott Bradner">
4111      <organization>Harvard University</organization>
4112      <address><email></email></address>
4113    </author>
4114    <date month="March" year="1997"/>
4115  </front>
4116  <seriesInfo name="BCP" value="14"/>
4117  <seriesInfo name="RFC" value="2119"/>
4120<reference anchor="RFC3986">
4121 <front>
4122  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
4123  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
4124    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4125    <address>
4126       <email></email>
4127       <uri></uri>
4128    </address>
4129  </author>
4130  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
4131    <organization abbrev="Day Software">Day Software</organization>
4132    <address>
4133      <email></email>
4134      <uri></uri>
4135    </address>
4136  </author>
4137  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
4138    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
4139    <address>
4140      <email></email>
4141      <uri></uri>
4142    </address>
4143  </author>
4144  <date month='January' year='2005'></date>
4145 </front>
4146 <seriesInfo name="STD" value="66"/>
4147 <seriesInfo name="RFC" value="3986"/>
4150<reference anchor="USASCII">
4151  <front>
4152    <title>Coded Character Set -- 7-bit American Standard Code for Information Interchange</title>
4153    <author>
4154      <organization>American National Standards Institute</organization>
4155    </author>
4156    <date year="1986"/>
4157  </front>
4158  <seriesInfo name="ANSI" value="X3.4"/>
4161<reference anchor="RFC1950">
4162  <front>
4163    <title>ZLIB Compressed Data Format Specification version 3.3</title>
4164    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
4165      <organization>Aladdin Enterprises</organization>
4166      <address><email></email></address>
4167    </author>
4168    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"/>
4169    <date month="May" year="1996"/>
4170  </front>
4171  <seriesInfo name="RFC" value="1950"/>
4172  <!--<annotation>
4173    RFC 1950 is an Informational RFC, thus it might be less stable than
4174    this specification. On the other hand, this downward reference was
4175    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4176    therefore it is unlikely to cause problems in practice. See also
4177    <xref target="BCP97"/>.
4178  </annotation>-->
4181<reference anchor="RFC1951">
4182  <front>
4183    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
4184    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
4185      <organization>Aladdin Enterprises</organization>
4186      <address><email></email></address>
4187    </author>
4188    <date month="May" year="1996"/>
4189  </front>
4190  <seriesInfo name="RFC" value="1951"/>
4191  <!--<annotation>
4192    RFC 1951 is an Informational RFC, thus it might be less stable than
4193    this specification. On the other hand, this downward reference was
4194    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4195    therefore it is unlikely to cause problems in practice. See also
4196    <xref target="BCP97"/>.
4197  </annotation>-->
4200<reference anchor="RFC1952">
4201  <front>
4202    <title>GZIP file format specification version 4.3</title>
4203    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
4204      <organization>Aladdin Enterprises</organization>
4205      <address><email></email></address>
4206    </author>
4207    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
4208      <address><email></email></address>
4209    </author>
4210    <author initials="M." surname="Adler" fullname="Mark Adler">
4211      <address><email></email></address>
4212    </author>
4213    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
4214      <address><email></email></address>
4215    </author>
4216    <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">
4217      <address><email></email></address>
4218    </author>
4219    <date month="May" year="1996"/>
4220  </front>
4221  <seriesInfo name="RFC" value="1952"/>
4222  <!--<annotation>
4223    RFC 1952 is an Informational RFC, thus it might be less stable than
4224    this specification. On the other hand, this downward reference was
4225    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4226    therefore it is unlikely to cause problems in practice. See also
4227    <xref target="BCP97"/>.
4228  </annotation>-->
4233<references title="Informative References">
4235<reference anchor="ISO-8859-1">
4236  <front>
4237    <title>
4238     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
4239    </title>
4240    <author>
4241      <organization>International Organization for Standardization</organization>
4242    </author>
4243    <date year="1998"/>
4244  </front>
4245  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
4248<reference anchor='RFC1919'>
4249  <front>
4250    <title>Classical versus Transparent IP Proxies</title>
4251    <author initials='M.' surname='Chatel' fullname='Marc Chatel'>
4252      <address><email></email></address>
4253    </author>
4254    <date year='1996' month='March' />
4255  </front>
4256  <seriesInfo name='RFC' value='1919' />
4259<reference anchor="RFC1945">
4260  <front>
4261    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
4262    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4263      <organization>MIT, Laboratory for Computer Science</organization>
4264      <address><email></email></address>
4265    </author>
4266    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4267      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4268      <address><email></email></address>
4269    </author>
4270    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4271      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
4272      <address><email></email></address>
4273    </author>
4274    <date month="May" year="1996"/>
4275  </front>
4276  <seriesInfo name="RFC" value="1945"/>
4279<reference anchor="RFC2045">
4280  <front>
4281    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
4282    <author initials="N." surname="Freed" fullname="Ned Freed">
4283      <organization>Innosoft International, Inc.</organization>
4284      <address><email></email></address>
4285    </author>
4286    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
4287      <organization>First Virtual Holdings</organization>
4288      <address><email></email></address>
4289    </author>
4290    <date month="November" year="1996"/>
4291  </front>
4292  <seriesInfo name="RFC" value="2045"/>
4295<reference anchor="RFC2047">
4296  <front>
4297    <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
4298    <author initials="K." surname="Moore" fullname="Keith Moore">
4299      <organization>University of Tennessee</organization>
4300      <address><email></email></address>
4301    </author>
4302    <date month="November" year="1996"/>
4303  </front>
4304  <seriesInfo name="RFC" value="2047"/>
4307<reference anchor="RFC2068">
4308  <front>
4309    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
4310    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
4311      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4312      <address><email></email></address>
4313    </author>
4314    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4315      <organization>MIT Laboratory for Computer Science</organization>
4316      <address><email></email></address>
4317    </author>
4318    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4319      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
4320      <address><email></email></address>
4321    </author>
4322    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4323      <organization>MIT Laboratory for Computer Science</organization>
4324      <address><email></email></address>
4325    </author>
4326    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4327      <organization>MIT Laboratory for Computer Science</organization>
4328      <address><email></email></address>
4329    </author>
4330    <date month="January" year="1997"/>
4331  </front>
4332  <seriesInfo name="RFC" value="2068"/>
4335<reference anchor="RFC2145">
4336  <front>
4337    <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
4338    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
4339      <organization>Western Research Laboratory</organization>
4340      <address><email></email></address>
4341    </author>
4342    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4343      <organization>Department of Information and Computer Science</organization>
4344      <address><email></email></address>
4345    </author>
4346    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4347      <organization>MIT Laboratory for Computer Science</organization>
4348      <address><email></email></address>
4349    </author>
4350    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4351      <organization>W3 Consortium</organization>
4352      <address><email></email></address>
4353    </author>
4354    <date month="May" year="1997"/>
4355  </front>
4356  <seriesInfo name="RFC" value="2145"/>
4359<reference anchor="RFC2616">
4360  <front>
4361    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
4362    <author initials="R." surname="Fielding" fullname="R. Fielding">
4363      <organization>University of California, Irvine</organization>
4364      <address><email></email></address>
4365    </author>
4366    <author initials="J." surname="Gettys" fullname="J. Gettys">
4367      <organization>W3C</organization>
4368      <address><email></email></address>
4369    </author>
4370    <author initials="J." surname="Mogul" fullname="J. Mogul">
4371      <organization>Compaq Computer Corporation</organization>
4372      <address><email></email></address>
4373    </author>
4374    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
4375      <organization>MIT Laboratory for Computer Science</organization>
4376      <address><email></email></address>
4377    </author>
4378    <author initials="L." surname="Masinter" fullname="L. Masinter">
4379      <organization>Xerox Corporation</organization>
4380      <address><email></email></address>
4381    </author>
4382    <author initials="P." surname="Leach" fullname="P. Leach">
4383      <organization>Microsoft Corporation</organization>
4384      <address><email></email></address>
4385    </author>
4386    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
4387      <organization>W3C</organization>
4388      <address><email></email></address>
4389    </author>
4390    <date month="June" year="1999"/>
4391  </front>
4392  <seriesInfo name="RFC" value="2616"/>
4395<reference anchor='RFC2817'>
4396  <front>
4397    <title>Upgrading to TLS Within HTTP/1.1</title>
4398    <author initials='R.' surname='Khare' fullname='R. Khare'>
4399      <organization>4K Associates / UC Irvine</organization>
4400      <address><email></email></address>
4401    </author>
4402    <author initials='S.' surname='Lawrence' fullname='S. Lawrence'>
4403      <organization>Agranat Systems, Inc.</organization>
4404      <address><email></email></address>
4405    </author>
4406    <date year='2000' month='May' />
4407  </front>
4408  <seriesInfo name='RFC' value='2817' />
4411<reference anchor='RFC2818'>
4412  <front>
4413    <title>HTTP Over TLS</title>
4414    <author initials='E.' surname='Rescorla' fullname='Eric Rescorla'>
4415      <organization>RTFM, Inc.</organization>
4416      <address><email></email></address>
4417    </author>
4418    <date year='2000' month='May' />
4419  </front>
4420  <seriesInfo name='RFC' value='2818' />
4423<reference anchor='RFC2965'>
4424  <front>
4425    <title>HTTP State Management Mechanism</title>
4426    <author initials='D. M.' surname='Kristol' fullname='David M. Kristol'>
4427      <organization>Bell Laboratories, Lucent Technologies</organization>
4428      <address><email></email></address>
4429    </author>
4430    <author initials='L.' surname='Montulli' fullname='Lou Montulli'>
4431      <organization>, Inc.</organization>
4432      <address><email></email></address>
4433    </author>
4434    <date year='2000' month='October' />
4435  </front>
4436  <seriesInfo name='RFC' value='2965' />
4439<reference anchor='RFC3040'>
4440  <front>
4441    <title>Internet Web Replication and Caching Taxonomy</title>
4442    <author initials='I.' surname='Cooper' fullname='I. Cooper'>
4443      <organization>Equinix, Inc.</organization>
4444    </author>
4445    <author initials='I.' surname='Melve' fullname='I. Melve'>
4446      <organization>UNINETT</organization>
4447    </author>
4448    <author initials='G.' surname='Tomlinson' fullname='G. Tomlinson'>
4449      <organization>CacheFlow Inc.</organization>
4450    </author>
4451    <date year='2001' month='January' />
4452  </front>
4453  <seriesInfo name='RFC' value='3040' />
4456<reference anchor='RFC3864'>
4457  <front>
4458    <title>Registration Procedures for Message Header Fields</title>
4459    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
4460      <organization>Nine by Nine</organization>
4461      <address><email></email></address>
4462    </author>
4463    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
4464      <organization>BEA Systems</organization>
4465      <address><email></email></address>
4466    </author>
4467    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
4468      <organization>HP Labs</organization>
4469      <address><email></email></address>
4470    </author>
4471    <date year='2004' month='September' />
4472  </front>
4473  <seriesInfo name='BCP' value='90' />
4474  <seriesInfo name='RFC' value='3864' />
4477<reference anchor='RFC4033'>
4478  <front>
4479    <title>DNS Security Introduction and Requirements</title>
4480    <author initials='R.' surname='Arends' fullname='R. Arends'/>
4481    <author initials='R.' surname='Austein' fullname='R. Austein'/>
4482    <author initials='M.' surname='Larson' fullname='M. Larson'/>
4483    <author initials='D.' surname='Massey' fullname='D. Massey'/>
4484    <author initials='S.' surname='Rose' fullname='S. Rose'/>
4485    <date year='2005' month='March' />
4486  </front>
4487  <seriesInfo name='RFC' value='4033' />
4490<reference anchor="RFC4288">
4491  <front>
4492    <title>Media Type Specifications and Registration Procedures</title>
4493    <author initials="N." surname="Freed" fullname="N. Freed">
4494      <organization>Sun Microsystems</organization>
4495      <address>
4496        <email></email>
4497      </address>
4498    </author>
4499    <author initials="J." surname="Klensin" fullname="J. Klensin">
4500      <address>
4501        <email></email>
4502      </address>
4503    </author>
4504    <date year="2005" month="December"/>
4505  </front>
4506  <seriesInfo name="BCP" value="13"/>
4507  <seriesInfo name="RFC" value="4288"/>
4510<reference anchor='RFC4395'>
4511  <front>
4512    <title>Guidelines and Registration Procedures for New URI Schemes</title>
4513    <author initials='T.' surname='Hansen' fullname='T. Hansen'>
4514      <organization>AT&amp;T Laboratories</organization>
4515      <address>
4516        <email></email>
4517      </address>
4518    </author>
4519    <author initials='T.' surname='Hardie' fullname='T. Hardie'>
4520      <organization>Qualcomm, Inc.</organization>
4521      <address>
4522        <email></email>
4523      </address>
4524    </author>
4525    <author initials='L.' surname='Masinter' fullname='L. Masinter'>
4526      <organization>Adobe Systems</organization>
4527      <address>
4528        <email></email>
4529      </address>
4530    </author>
4531    <date year='2006' month='February' />
4532  </front>
4533  <seriesInfo name='BCP' value='115' />
4534  <seriesInfo name='RFC' value='4395' />
4537<reference anchor='RFC4559'>
4538  <front>
4539    <title>SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows</title>
4540    <author initials='K.' surname='Jaganathan' fullname='K. Jaganathan'/>
4541    <author initials='L.' surname='Zhu' fullname='L. Zhu'/>
4542    <author initials='J.' surname='Brezak' fullname='J. Brezak'/>
4543    <date year='2006' month='June' />
4544  </front>
4545  <seriesInfo name='RFC' value='4559' />
4548<reference anchor='RFC5226'>
4549  <front>
4550    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
4551    <author initials='T.' surname='Narten' fullname='T. Narten'>
4552      <organization>IBM</organization>
4553      <address><email></email></address>
4554    </author>
4555    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
4556      <organization>Google</organization>
4557      <address><email></email></address>
4558    </author>
4559    <date year='2008' month='May' />
4560  </front>
4561  <seriesInfo name='BCP' value='26' />
4562  <seriesInfo name='RFC' value='5226' />
4565<reference anchor='RFC5246'>
4566   <front>
4567      <title>The Transport Layer Security (TLS) Protocol Version 1.2</title>
4568      <author initials='T.' surname='Dierks' fullname='T. Dierks'>
4569         <organization />
4570      </author>
4571      <author initials='E.' surname='Rescorla' fullname='E. Rescorla'>
4572         <organization>RTFM, Inc.</organization>
4573      </author>
4574      <date year='2008' month='August' />
4575   </front>
4576   <seriesInfo name='RFC' value='5246' />
4579<reference anchor="RFC5322">
4580  <front>
4581    <title>Internet Message Format</title>
4582    <author initials="P." surname="Resnick" fullname="P. Resnick">
4583      <organization>Qualcomm Incorporated</organization>
4584    </author>
4585    <date year="2008" month="October"/>
4586  </front>
4587  <seriesInfo name="RFC" value="5322"/>
4590<reference anchor="RFC6265">
4591  <front>
4592    <title>HTTP State Management Mechanism</title>
4593    <author initials="A." surname="Barth" fullname="Adam Barth">
4594      <organization abbrev="U.C. Berkeley">
4595        University of California, Berkeley
4596      </organization>
4597      <address><email></email></address>
4598    </author>
4599    <date year="2011" month="April" />
4600  </front>
4601  <seriesInfo name="RFC" value="6265"/>
4604<!--<reference anchor='BCP97'>
4605  <front>
4606    <title>Handling Normative References to Standards-Track Documents</title>
4607    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
4608      <address>
4609        <email></email>
4610      </address>
4611    </author>
4612    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
4613      <organization>MIT</organization>
4614      <address>
4615        <email></email>
4616      </address>
4617    </author>
4618    <date year='2007' month='June' />
4619  </front>
4620  <seriesInfo name='BCP' value='97' />
4621  <seriesInfo name='RFC' value='4897' />
4624<reference anchor="Kri2001" target="">
4625  <front>
4626    <title>HTTP Cookies: Standards, Privacy, and Politics</title>
4627    <author initials="D." surname="Kristol" fullname="David M. Kristol"/>
4628    <date year="2001" month="November"/>
4629  </front>
4630  <seriesInfo name="ACM Transactions on Internet Technology" value="Vol. 1, #2"/>
4636<section title="HTTP Version History" anchor="compatibility">
4638   HTTP has been in use by the World-Wide Web global information initiative
4639   since 1990. The first version of HTTP, later referred to as HTTP/0.9,
4640   was a simple protocol for hypertext data transfer across the Internet
4641   with only a single request method (GET) and no metadata.
4642   HTTP/1.0, as defined by <xref target="RFC1945"/>, added a range of request
4643   methods and MIME-like messaging that could include metadata about the data
4644   transferred and modifiers on the request/response semantics. However,
4645   HTTP/1.0 did not sufficiently take into consideration the effects of
4646   hierarchical proxies, caching, the need for persistent connections, or
4647   name-based virtual hosts. The proliferation of incompletely-implemented
4648   applications calling themselves "HTTP/1.0" further necessitated a
4649   protocol version change in order for two communicating applications
4650   to determine each other's true capabilities.
4653   HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent
4654   requirements that enable reliable implementations, adding only
4655   those new features that will either be safely ignored by an HTTP/1.0
4656   recipient or only sent when communicating with a party advertising
4657   conformance with HTTP/1.1.
4660   It is beyond the scope of a protocol specification to mandate
4661   conformance with previous versions. HTTP/1.1 was deliberately
4662   designed, however, to make supporting previous versions easy.
4663   We would expect a general-purpose HTTP/1.1 server to understand
4664   any valid request in the format of HTTP/1.0 and respond appropriately
4665   with an HTTP/1.1 message that only uses features understood (or
4666   safely ignored) by HTTP/1.0 clients.  Likewise, we would expect
4667   an HTTP/1.1 client to understand any valid HTTP/1.0 response.
4670   Since HTTP/0.9 did not support header fields in a request,
4671   there is no mechanism for it to support name-based virtual
4672   hosts (selection of resource by inspection of the <x:ref>Host</x:ref> header
4673   field).  Any server that implements name-based virtual hosts
4674   ought to disable support for HTTP/0.9.  Most requests that
4675   appear to be HTTP/0.9 are, in fact, badly constructed HTTP/1.x
4676   requests wherein a buggy client failed to properly encode
4677   linear whitespace found in a URI reference and placed in
4678   the request-target.
4681<section title="Changes from HTTP/1.0" anchor="changes.from.1.0">
4683   This section summarizes major differences between versions HTTP/1.0
4684   and HTTP/1.1.
4687<section title="Multi-homed Web Servers" anchor="">
4689   The requirements that clients and servers support the <x:ref>Host</x:ref>
4690   header field (<xref target=""/>), report an error if it is
4691   missing from an HTTP/1.1 request, and accept absolute URIs (<xref target="request-target"/>)
4692   are among the most important changes defined by HTTP/1.1.
4695   Older HTTP/1.0 clients assumed a one-to-one relationship of IP
4696   addresses and servers; there was no other established mechanism for
4697   distinguishing the intended server of a request than the IP address
4698   to which that request was directed. The <x:ref>Host</x:ref> header field was
4699   introduced during the development of HTTP/1.1 and, though it was
4700   quickly implemented by most HTTP/1.0 browsers, additional requirements
4701   were placed on all HTTP/1.1 requests in order to ensure complete
4702   adoption.  At the time of this writing, most HTTP-based services
4703   are dependent upon the Host header field for targeting requests.
4707<section title="Keep-Alive Connections" anchor="compatibility.with.http.1.0.persistent.connections">
4709   In HTTP/1.0, each connection is established by the client prior to the
4710   request and closed by the server after sending the response. However, some
4711   implementations implement the explicitly negotiated ("Keep-Alive") version
4712   of persistent connections described in <xref x:sec="19.7.1" x:fmt="of"
4713   target="RFC2068"/>.
4716   Some clients and servers might wish to be compatible with these previous
4717   approaches to persistent connections, by explicitly negotiating for them
4718   with a "Connection: keep-alive" request header field. However, some
4719   experimental implementations of HTTP/1.0 persistent connections are faulty;
4720   for example, if a HTTP/1.0 proxy server doesn't understand
4721   <x:ref>Connection</x:ref>, it will erroneously forward that header field
4722   to the next inbound server, which would result in a hung connection.
4725   One attempted solution was the introduction of a Proxy-Connection header
4726   field, targeted specifically at proxies. In practice, this was also
4727   unworkable, because proxies are often deployed in multiple layers, bringing
4728   about the same problem discussed above.
4731   As a result, clients are encouraged not to send the Proxy-Connection header
4732   field in any requests.
4735   Clients are also encouraged to consider the use of Connection: keep-alive
4736   in requests carefully; while they can enable persistent connections with
4737   HTTP/1.0 servers, clients using them need will need to monitor the
4738   connection for "hung" requests (which indicate that the client ought stop
4739   sending the header field), and this mechanism ought not be used by clients
4740   at all when a proxy is being used.
4744<section title="Introduction of Transfer-Encoding" anchor="introduction.of.transfer-encoding">
4746   HTTP/1.1 introduces the <x:ref>Transfer-Encoding</x:ref> header field
4747   (<xref target="header.transfer-encoding"/>). Proxies/gateways &MUST; remove
4748   any transfer-coding prior to forwarding a message via a MIME-compliant
4749   protocol.
4755<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
4757  Clarify that the string "HTTP" in the HTTP-version ABNF production is case
4758  sensitive. Restrict the version numbers to be single digits due to the fact
4759  that implementations are known to handle multi-digit version numbers
4760  incorrectly.
4761  (<xref target="http.version"/>)
4764  Require that invalid whitespace around field-names be rejected.
4765  Change ABNF productions for header fields to only define the field value.
4766  (<xref target="header.fields"/>)
4769  Rules about implicit linear whitespace between certain grammar productions
4770  have been removed; now whitespace is only allowed where specifically
4771  defined in the ABNF.
4772  (<xref target="whitespace"/>)
4775  The NUL octet is no longer allowed in comment and quoted-string
4776  text. The quoted-pair rule no longer allows escaping control characters other than HTAB.
4777  Non-ASCII content in header fields and reason phrase has been obsoleted and
4778  made opaque (the TEXT rule was removed).
4779  (<xref target="field.components"/>)
4782  Require recipients to handle bogus "<x:ref>Content-Length</x:ref>" header
4783  fields as errors.
4784  (<xref target="message.body"/>)
4787  Remove reference to non-existent identity transfer-coding value tokens.
4788  (Sections <xref format="counter" target="message.body"/> and
4789  <xref format="counter" target="transfer.codings"/>)
4792  Clarification that the chunk length does not include the count of the octets
4793  in the chunk header and trailer. Furthermore disallowed line folding
4794  in chunk extensions, and deprecate their use.
4795  (<xref target="chunked.encoding"/>)
4798  Update use of abs_path production from RFC 1808 to the path-absolute + query
4799  components of RFC 3986. State that the asterisk form is allowed for the OPTIONS
4800  request method only.
4801  (<xref target="request-target"/>)
4804  Clarify exactly when "close" connection options have to be sent; drop
4805  notion of header fields being "hop-by-hop" without being listed in the
4806  Connection header field.
4807  (<xref target="header.connection"/>)
4810  Remove hard limit of two connections per server.
4811  Remove requirement to retry a sequence of requests as long it was idempotent.
4812  Remove requirements about when servers are allowed to close connections
4813  prematurely.
4814  (<xref target="persistent.connections"/>)
4817  Remove requirement to retry requests under certain circumstances when the
4818  server prematurely closes the connection.
4819  (<xref target="persistent.reuse"/>)
4822  Define the semantics of the <x:ref>Upgrade</x:ref> header field in responses
4823  other than 101 (this was incorporated from <xref target="RFC2817"/>).
4824  (<xref target="header.upgrade"/>)
4827  Registration of Transfer Codings now requires IETF Review
4828  (<xref target="transfer.coding.registry"/>)
4831  Take over the Upgrade Token Registry, previously defined in
4832  <xref target="RFC2817" x:fmt="of" x:sec="7.2"/>.
4833  (<xref target="upgrade.token.registry"/>)
4836  Empty list elements in list productions have been deprecated.
4837  (<xref target="abnf.extension"/>)
4842<section title="ABNF list extension: #rule" anchor="abnf.extension">
4844  A #rule extension to the ABNF rules of <xref target="RFC5234"/> is used to
4845  improve readability in the definitions of some header field values.
4848  A construct "#" is defined, similar to "*", for defining comma-delimited
4849  lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating
4850  at least &lt;n&gt; and at most &lt;m&gt; elements, each separated by a single
4851  comma (",") and optional whitespace (OWS).   
4854  Thus,
4855</preamble><artwork type="example">
4856  1#element =&gt; element *( OWS "," OWS element )
4859  and:
4860</preamble><artwork type="example">
4861  #element =&gt; [ 1#element ]
4864  and for n &gt;= 1 and m &gt; 1:
4865</preamble><artwork type="example">
4866  &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
4869  For compatibility with legacy list rules, recipients &SHOULD; accept empty
4870  list elements. In other words, consumers would follow the list productions:
4872<figure><artwork type="example">
4873  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
4875  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
4878  Note that empty elements do not contribute to the count of elements present,
4879  though.
4882  For example, given these ABNF productions:
4884<figure><artwork type="example">
4885  example-list      = 1#example-list-elmt
4886  example-list-elmt = token ; see <xref target="field.components"/>
4889  Then these are valid values for example-list (not including the double
4890  quotes, which are present for delimitation only):
4892<figure><artwork type="example">
4893  "foo,bar"
4894  "foo ,bar,"
4895  "foo , ,bar,charlie   "
4898  But these values would be invalid, as at least one non-empty element is
4899  required:
4901<figure><artwork type="example">
4902  ""
4903  ","
4904  ",   ,"
4907  <xref target="collected.abnf"/> shows the collected ABNF, with the list rules
4908  expanded as explained above.
4912<?BEGININC p1-messaging.abnf-appendix ?>
4913<section xmlns:x="" title="Collected ABNF" anchor="collected.abnf">
4915<artwork type="abnf" name="p1-messaging.parsed-abnf">
4916<x:ref>BWS</x:ref> = OWS
4918<x:ref>Connection</x:ref> = *( "," OWS ) connection-option *( OWS "," [ OWS
4919 connection-option ] )
4920<x:ref>Content-Length</x:ref> = 1*DIGIT
4922<x:ref>HTTP-message</x:ref> = start-line *( header-field CRLF ) CRLF [ message-body
4923 ]
4924<x:ref>HTTP-name</x:ref> = %x48.54.54.50 ; HTTP
4925<x:ref>HTTP-version</x:ref> = HTTP-name "/" DIGIT "." DIGIT
4926<x:ref>Host</x:ref> = uri-host [ ":" port ]
4928<x:ref>OWS</x:ref> = *( SP / HTAB )
4930<x:ref>RWS</x:ref> = 1*( SP / HTAB )
4932<x:ref>TE</x:ref> = [ ( "," / t-codings ) *( OWS "," [ OWS t-codings ] ) ]
4933<x:ref>Trailer</x:ref> = *( "," OWS ) field-name *( OWS "," [ OWS field-name ] )
4934<x:ref>Transfer-Encoding</x:ref> = *( "," OWS ) transfer-coding *( OWS "," [ OWS
4935 transfer-coding ] )
4937<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [RFC3986], Section 4.1&gt;
4938<x:ref>Upgrade</x:ref> = *( "," OWS ) protocol *( OWS "," [ OWS protocol ] )
4940<x:ref>Via</x:ref> = *( "," OWS ) ( received-protocol RWS received-by [ RWS comment
4941 ] ) *( OWS "," [ OWS ( received-protocol RWS received-by [ RWS
4942 comment ] ) ] )
4944<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
4945<x:ref>absolute-form</x:ref> = absolute-URI
4946<x:ref>asterisk-form</x:ref> = "*"
4947<x:ref>attribute</x:ref> = token
4948<x:ref>authority</x:ref> = &lt;authority, defined in [RFC3986], Section 3.2&gt;
4949<x:ref>authority-form</x:ref> = authority
4951<x:ref>chunk</x:ref> = chunk-size [ chunk-ext ] CRLF chunk-data CRLF
4952<x:ref>chunk-data</x:ref> = 1*OCTET
4953<x:ref>chunk-ext</x:ref> = *( ";" chunk-ext-name [ "=" chunk-ext-val ] )
4954<x:ref>chunk-ext-name</x:ref> = token
4955<x:ref>chunk-ext-val</x:ref> = token / quoted-str-nf
4956<x:ref>chunk-size</x:ref> = 1*HEXDIG
4957<x:ref>chunked-body</x:ref> = *chunk last-chunk trailer-part CRLF
4958<x:ref>comment</x:ref> = "(" *( ctext / quoted-cpair / comment ) ")"
4959<x:ref>connection-option</x:ref> = token
4960<x:ref>ctext</x:ref> = OWS / %x21-27 ; '!'-'''
4961 / %x2A-5B ; '*'-'['
4962 / %x5D-7E ; ']'-'~'
4963 / obs-text
4965<x:ref>field-content</x:ref> = *( HTAB / SP / VCHAR / obs-text )
4966<x:ref>field-name</x:ref> = token
4967<x:ref>field-value</x:ref> = *( field-content / obs-fold )
4969<x:ref>header-field</x:ref> = field-name ":" OWS field-value BWS
4970<x:ref>http-URI</x:ref> = "http://" authority path-abempty [ "?" query ]
4971<x:ref>https-URI</x:ref> = "https://" authority path-abempty [ "?" query ]
4973<x:ref>last-chunk</x:ref> = 1*"0" [ chunk-ext ] CRLF
4975<x:ref>message-body</x:ref> = *OCTET
4976<x:ref>method</x:ref> = token
4978<x:ref>obs-fold</x:ref> = CRLF ( SP / HTAB )
4979<x:ref>obs-text</x:ref> = %x80-FF
4980<x:ref>origin-form</x:ref> = path-absolute [ "?" query ]
4982<x:ref>partial-URI</x:ref> = relative-part [ "?" query ]
4983<x:ref>path-abempty</x:ref> = &lt;path-abempty, defined in [RFC3986], Section 3.3&gt;
4984<x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in [RFC3986], Section 3.3&gt;
4985<x:ref>port</x:ref> = &lt;port, defined in [RFC3986], Section 3.2.3&gt;
4986<x:ref>protocol</x:ref> = protocol-name [ "/" protocol-version ]
4987<x:ref>protocol-name</x:ref> = token
4988<x:ref>protocol-version</x:ref> = token
4989<x:ref>pseudonym</x:ref> = token
4991<x:ref>qdtext</x:ref> = OWS / "!" / %x23-5B ; '#'-'['
4992 / %x5D-7E ; ']'-'~'
4993 / obs-text
4994<x:ref>qdtext-nf</x:ref> = HTAB / SP / "!" / %x23-5B ; '#'-'['
4995 / %x5D-7E ; ']'-'~'
4996 / obs-text
4997<x:ref>query</x:ref> = &lt;query, defined in [RFC3986], Section 3.4&gt;
4998<x:ref>quoted-cpair</x:ref> = "\" ( HTAB / SP / VCHAR / obs-text )
4999<x:ref>quoted-pair</x:ref> = "\" ( HTAB / SP / VCHAR / obs-text )
5000<x:ref>quoted-str-nf</x:ref> = DQUOTE *( qdtext-nf / quoted-pair ) DQUOTE
5001<x:ref>quoted-string</x:ref> = DQUOTE *( qdtext / quoted-pair ) DQUOTE
5003<x:ref>rank</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
5004<x:ref>reason-phrase</x:ref> = *( HTAB / SP / VCHAR / obs-text )
5005<x:ref>received-by</x:ref> = ( uri-host [ ":" port ] ) / pseudonym
5006<x:ref>received-protocol</x:ref> = [ protocol-name "/" ] protocol-version
5007<x:ref>relative-part</x:ref> = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;
5008<x:ref>request-line</x:ref> = method SP request-target SP HTTP-version CRLF
5009<x:ref>request-target</x:ref> = origin-form / absolute-form / authority-form /
5010 asterisk-form
5012<x:ref>special</x:ref> = "(" / ")" / "&lt;" / "&gt;" / "@" / "," / ";" / ":" / "\" /
5013 DQUOTE / "/" / "[" / "]" / "?" / "=" / "{" / "}"
5014<x:ref>start-line</x:ref> = request-line / status-line
5015<x:ref>status-code</x:ref> = 3DIGIT
5016<x:ref>status-line</x:ref> = HTTP-version SP status-code SP reason-phrase CRLF
5018<x:ref>t-codings</x:ref> = "trailers" / ( transfer-coding [ t-ranking ] )
5019<x:ref>t-ranking</x:ref> = OWS ";" OWS "q=" rank
5020<x:ref>tchar</x:ref> = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*" / "+" / "-" / "." /
5021 "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
5022<x:ref>token</x:ref> = 1*tchar
5023<x:ref>trailer-part</x:ref> = *( header-field CRLF )
5024<x:ref>transfer-coding</x:ref> = "chunked" / "compress" / "deflate" / "gzip" /
5025 transfer-extension
5026<x:ref>transfer-extension</x:ref> = token *( OWS ";" OWS transfer-parameter )
5027<x:ref>transfer-parameter</x:ref> = attribute BWS "=" BWS value
5029<x:ref>uri-host</x:ref> = &lt;host, defined in [RFC3986], Section 3.2.2&gt;
5031<x:ref>value</x:ref> = word
5033<x:ref>word</x:ref> = token / quoted-string
5037<?ENDINC p1-messaging.abnf-appendix ?>
5039<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
5041<section title="Since RFC 2616">
5043  Extracted relevant partitions from <xref target="RFC2616"/>.
5047<section title="Since draft-ietf-httpbis-p1-messaging-00">
5049  Closed issues:
5050  <list style="symbols">
5051    <t>
5052      <eref target=""/>:
5053      "HTTP Version should be case sensitive"
5054      (<eref target=""/>)
5055    </t>
5056    <t>
5057      <eref target=""/>:
5058      "'unsafe' characters"
5059      (<eref target=""/>)
5060    </t>
5061    <t>
5062      <eref target=""/>:
5063      "Chunk Size Definition"
5064      (<eref target=""/>)
5065    </t>
5066    <t>
5067      <eref target=""/>:
5068      "Message Length"
5069      (<eref target=""/>)
5070    </t>
5071    <t>
5072      <eref target=""/>:
5073      "Media Type Registrations"
5074      (<eref target=""/>)
5075    </t>
5076    <t>
5077      <eref target=""/>:
5078      "URI includes query"
5079      (<eref target=""/>)
5080    </t>
5081    <t>
5082      <eref target=""/>:
5083      "No close on 1xx responses"
5084      (<eref target=""/>)
5085    </t>
5086    <t>
5087      <eref target=""/>:
5088      "Remove 'identity' token references"
5089      (<eref target=""/>)
5090    </t>
5091    <t>
5092      <eref target=""/>:
5093      "Import query BNF"
5094    </t>
5095    <t>
5096      <eref target=""/>:
5097      "qdtext BNF"
5098    </t>
5099    <t>
5100      <eref target=""/>:
5101      "Normative and Informative references"
5102    </t>
5103    <t>
5104      <eref target=""/>:
5105      "RFC2606 Compliance"
5106    </t>
5107    <t>
5108      <eref target=""/>:
5109      "RFC977 reference"
5110    </t>
5111    <t>
5112      <eref target=""/>:
5113      "RFC1700 references"
5114    </t>
5115    <t>
5116      <eref target=""/>:
5117      "inconsistency in date format explanation"
5118    </t>
5119    <t>
5120      <eref target=""/>:
5121      "Date reference typo"
5122    </t>
5123    <t>
5124      <eref target=""/>:
5125      "Informative references"
5126    </t>
5127    <t>
5128      <eref target=""/>:
5129      "ISO-8859-1 Reference"
5130    </t>
5131    <t>
5132      <eref target=""/>:
5133      "Normative up-to-date references"
5134    </t>
5135  </list>
5138  Other changes:
5139  <list style="symbols">
5140    <t>
5141      Update media type registrations to use RFC4288 template.
5142    </t>
5143    <t>
5144      Use names of RFC4234 core rules DQUOTE and HTAB,
5145      fix broken ABNF for chunk-data
5146      (work in progress on <eref target=""/>)
5147    </t>
5148  </list>
5152<section title="Since draft-ietf-httpbis-p1-messaging-01">
5154  Closed issues:
5155  <list style="symbols">
5156    <t>
5157      <eref target=""/>:
5158      "Bodies on GET (and other) requests"
5159    </t>
5160    <t>
5161      <eref target=""/>:
5162      "Updating to RFC4288"
5163    </t>
5164    <t>
5165      <eref target=""/>:
5166      "Status Code and Reason Phrase"
5167    </t>
5168    <t>
5169      <eref target=""/>:
5170      "rel_path not used"
5171    </t>
5172  </list>
5175  Ongoing work on ABNF conversion (<eref target=""/>):
5176  <list style="symbols">
5177    <t>
5178      Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" ->
5179      "trailer-part").
5180    </t>
5181    <t>
5182      Avoid underscore character in rule names ("http_URL" ->
5183      "http-URL", "abs_path" -> "path-absolute").
5184    </t>
5185    <t>
5186      Add rules for terms imported from URI spec ("absoluteURI", "authority",
5187      "path-absolute", "port", "query", "relativeURI", "host) &mdash; these will
5188      have to be updated when switching over to RFC3986.
5189    </t>
5190    <t>
5191      Synchronize core rules with RFC5234.
5192    </t>
5193    <t>
5194      Get rid of prose rules that span multiple lines.
5195    </t>
5196    <t>
5197      Get rid of unused rules LOALPHA and UPALPHA.
5198    </t>
5199    <t>
5200      Move "Product Tokens" section (back) into Part 1, as "token" is used
5201      in the definition of the Upgrade header field.
5202    </t>
5203    <t>
5204      Add explicit references to BNF syntax and rules imported from other parts of the specification.
5205    </t>
5206    <t>
5207      Rewrite prose rule "token" in terms of "tchar", rewrite prose rule "TEXT".
5208    </t>
5209  </list>
5213<section title="Since draft-ietf-httpbis-p1-messaging-02" anchor="changes.since.02">
5215  Closed issues:
5216  <list style="symbols">
5217    <t>
5218      <eref target=""/>:
5219      "HTTP-date vs. rfc1123-date"
5220    </t>
5221    <t>
5222      <eref target=""/>:
5223      "WS in quoted-pair"
5224    </t>
5225  </list>
5228  Ongoing work on IANA Message Header Field Registration (<eref target=""/>):
5229  <list style="symbols">
5230    <t>
5231      Reference RFC 3984, and update header field registrations for header
5232      fields defined in this document.
5233    </t>
5234  </list>
5237  Ongoing work on ABNF conversion (<eref target=""/>):
5238  <list style="symbols">
5239    <t>
5240      Replace string literals when the string really is case-sensitive (HTTP-version).
5241    </t>
5242  </list>
5246<section title="Since draft-ietf-httpbis-p1-messaging-03" anchor="changes.since.03">
5248  Closed issues:
5249  <list style="symbols">
5250    <t>
5251      <eref target=""/>:
5252      "Connection closing"
5253    </t>
5254    <t>
5255      <eref target=""/>:
5256      "Move registrations and registry information to IANA Considerations"
5257    </t>
5258    <t>
5259      <eref target=""/>:
5260      "need new URL for PAD1995 reference"
5261    </t>
5262    <t>
5263      <eref target=""/>:
5264      "IANA Considerations: update HTTP URI scheme registration"
5265    </t>
5266    <t>
5267      <eref target=""/>:
5268      "Cite HTTPS URI scheme definition"
5269    </t>
5270    <t>
5271      <eref target=""/>:
5272      "List-type header fields vs Set-Cookie"
5273    </t>
5274  </list>
5277  Ongoing work on ABNF conversion (<eref target=""/>):
5278  <list style="symbols">
5279    <t>
5280      Replace string literals when the string really is case-sensitive (HTTP-Date).
5281    </t>
5282    <t>
5283      Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.
5284    </t>
5285  </list>
5289<section title="Since draft-ietf-httpbis-p1-messaging-04" anchor="changes.since.04">
5291  Closed issues:
5292  <list style="symbols">
5293    <t>
5294      <eref target=""/>:
5295      "Out-of-date reference for URIs"
5296    </t>
5297    <t>
5298      <eref target=""/>:
5299      "RFC 2822 is updated by RFC 5322"
5300    </t>
5301  </list>
5304  Ongoing work on ABNF conversion (<eref target=""/>):
5305  <list style="symbols">
5306    <t>
5307      Use "/" instead of "|" for alternatives.
5308    </t>
5309    <t>
5310      Get rid of RFC822 dependency; use RFC5234 plus extensions instead.
5311    </t>
5312    <t>
5313      Only reference RFC 5234's core rules.
5314    </t>
5315    <t>
5316      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
5317      whitespace ("OWS") and required whitespace ("RWS").
5318    </t>
5319    <t>
5320      Rewrite ABNFs to spell out whitespace rules, factor out
5321      header field value format definitions.
5322    </t>
5323  </list>
5327<section title="Since draft-ietf-httpbis-p1-messaging-05" anchor="changes.since.05">
5329  Closed issues:
5330  <list style="symbols">
5331    <t>
5332      <eref target=""/>:
5333      "Header LWS"
5334    </t>
5335    <t>
5336      <eref target=""/>:
5337      "Sort 1.3 Terminology"
5338    </t>
5339    <t>
5340      <eref target=""/>:
5341      "RFC2047 encoded words"
5342    </t>
5343    <t>
5344      <eref target=""/>:
5345      "Character Encodings in TEXT"
5346    </t>
5347    <t>
5348      <eref target=""/>:
5349      "Line Folding"
5350    </t>
5351    <t>
5352      <eref target=""/>:
5353      "OPTIONS * and proxies"
5354    </t>
5355    <t>
5356      <eref target=""/>:
5357      "reason-phrase BNF"
5358    </t>
5359    <t>
5360      <eref target=""/>:
5361      "Use of TEXT"
5362    </t>
5363    <t>
5364      <eref target=""/>:
5365      "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
5366    </t>
5367    <t>
5368      <eref target=""/>:
5369      "RFC822 reference left in discussion of date formats"
5370    </t>
5371  </list>
5374  Final work on ABNF conversion (<eref target=""/>):
5375  <list style="symbols">
5376    <t>
5377      Rewrite definition of list rules, deprecate empty list elements.
5378    </t>
5379    <t>
5380      Add appendix containing collected and expanded ABNF.
5381    </t>
5382  </list>
5385  Other changes:
5386  <list style="symbols">
5387    <t>
5388      Rewrite introduction; add mostly new Architecture Section.
5389    </t>
5390    <t>
5391      Move definition of quality values from Part 3 into Part 1;
5392      make TE request header field grammar independent of accept-params (defined in Part 3).
5393    </t>
5394  </list>
5398<section title="Since draft-ietf-httpbis-p1-messaging-06" anchor="changes.since.06">
5400  Closed issues:
5401  <list style="symbols">
5402    <t>
5403      <eref target=""/>:
5404      "base for numeric protocol elements"
5405    </t>
5406    <t>
5407      <eref target=""/>:
5408      "comment ABNF"
5409    </t>
5410  </list>
5413  Partly resolved issues:
5414  <list style="symbols">
5415    <t>
5416      <eref target=""/>:
5417      "205 Bodies" (took out language that implied that there might be
5418      methods for which a payload body MUST NOT be included)
5419    </t>
5420    <t>
5421      <eref target=""/>:
5422      "editorial improvements around HTTP-date"
5423    </t>
5424  </list>
5428<section title="Since draft-ietf-httpbis-p1-messaging-07" anchor="changes.since.07">
5430  Closed issues:
5431  <list style="symbols">
5432    <t>
5433      <eref target=""/>:
5434      "Repeating single-value header fields"
5435    </t>
5436    <t>
5437      <eref target=""/>:
5438      "increase connection limit"
5439    </t>
5440    <t>
5441      <eref target=""/>:
5442      "IP addresses in URLs"
5443    </t>
5444    <t>
5445      <eref target=""/>:
5446      "take over HTTP Upgrade Token Registry"
5447    </t>
5448    <t>
5449      <eref target=""/>:
5450      "CR and LF in chunk extension values"
5451    </t>
5452    <t>
5453      <eref target=""/>:
5454      "HTTP/0.9 support"
5455    </t>
5456    <t>
5457      <eref target=""/>:
5458      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
5459    </t>
5460    <t>
5461      <eref target=""/>:
5462      "move definitions of gzip/deflate/compress to part 1"
5463    </t>
5464    <t>
5465      <eref target=""/>:
5466      "disallow control characters in quoted-pair"
5467    </t>
5468  </list>
5471  Partly resolved issues:
5472  <list style="symbols">
5473    <t>
5474      <eref target=""/>:
5475      "update IANA requirements wrt Transfer-Coding values" (add the
5476      IANA Considerations subsection)
5477    </t>
5478  </list>
5482<section title="Since draft-ietf-httpbis-p1-messaging-08" anchor="changes.since.08">
5484  Closed issues:
5485  <list style="symbols">
5486    <t>
5487      <eref target=""/>:
5488      "header parsing, treatment of leading and trailing OWS"
5489    </t>
5490  </list>
5493  Partly resolved issues:
5494  <list style="symbols">
5495    <t>
5496      <eref target=""/>:
5497      "Placement of 13.5.1 and 13.5.2"
5498    </t>
5499    <t>
5500      <eref target=""/>:
5501      "use of term "word" when talking about header field structure"
5502    </t>
5503  </list>
5507<section title="Since draft-ietf-httpbis-p1-messaging-09" anchor="changes.since.09">
5509  Closed issues:
5510  <list style="symbols">
5511    <t>
5512      <eref target=""/>:
5513      "Clarification of the term 'deflate'"
5514    </t>
5515    <t>
5516      <eref target=""/>:
5517      "OPTIONS * and proxies"
5518    </t>
5519    <t>
5520      <eref target=""/>:
5521      "MIME-Version not listed in P1, general header fields"
5522    </t>
5523    <t>
5524      <eref target=""/>:
5525      "IANA registry for content/transfer encodings"
5526    </t>
5527    <t>
5528      <eref target=""/>:
5529      "Case-sensitivity of HTTP-date"
5530    </t>
5531    <t>
5532      <eref target=""/>:
5533      "use of term "word" when talking about header field structure"
5534    </t>
5535  </list>
5538  Partly resolved issues:
5539  <list style="symbols">
5540    <t>
5541      <eref target=""/>:
5542      "Term for the requested resource's URI"
5543    </t>
5544  </list>
5548<section title="Since draft-ietf-httpbis-p1-messaging-10" anchor="changes.since.10">
5550  Closed issues:
5551  <list style="symbols">
5552    <t>
5553      <eref target=""/>:
5554      "Connection Closing"
5555    </t>
5556    <t>
5557      <eref target=""/>:
5558      "Delimiting messages with multipart/byteranges"
5559    </t>
5560    <t>
5561      <eref target=""/>:
5562      "Handling multiple Content-Length header fields"
5563    </t>
5564    <t>
5565      <eref target=""/>:
5566      "Clarify entity / representation / variant terminology"
5567    </t>
5568    <t>
5569      <eref target=""/>:
5570      "consider removing the 'changes from 2068' sections"
5571    </t>
5572  </list>
5575  Partly resolved issues:
5576  <list style="symbols">
5577    <t>
5578      <eref target=""/>:
5579      "HTTP(s) URI scheme definitions"
5580    </t>
5581  </list>
5585<section title="Since draft-ietf-httpbis-p1-messaging-11" anchor="changes.since.11">
5587  Closed issues:
5588  <list style="symbols">
5589    <t>
5590      <eref target=""/>:
5591      "Trailer requirements"
5592    </t>
5593    <t>
5594      <eref target=""/>:
5595      "Text about clock requirement for caches belongs in p6"
5596    </t>
5597    <t>
5598      <eref target=""/>:
5599      "effective request URI: handling of missing host in HTTP/1.0"
5600    </t>
5601    <t>
5602      <eref target=""/>:
5603      "confusing Date requirements for clients"
5604    </t>
5605  </list>
5608  Partly resolved issues:
5609  <list style="symbols">
5610    <t>
5611      <eref target=""/>:
5612      "Handling multiple Content-Length header fields"
5613    </t>
5614  </list>
5618<section title="Since draft-ietf-httpbis-p1-messaging-12" anchor="changes.since.12">
5620  Closed issues:
5621  <list style="symbols">
5622    <t>
5623      <eref target=""/>:
5624      "RFC2145 Normative"
5625    </t>
5626    <t>
5627      <eref target=""/>:
5628      "HTTP(s) URI scheme definitions" (tune the requirements on userinfo)
5629    </t>
5630    <t>
5631      <eref target=""/>:
5632      "define 'transparent' proxy"
5633    </t>
5634    <t>
5635      <eref target=""/>:
5636      "Header Field Classification"
5637    </t>
5638    <t>
5639      <eref target=""/>:
5640      "Is * usable as a request-uri for new methods?"
5641    </t>
5642    <t>
5643      <eref target=""/>:
5644      "Migrate Upgrade details from RFC2817"
5645    </t>
5646    <t>
5647      <eref target=""/>:
5648      "untangle ABNFs for header fields"
5649    </t>
5650    <t>
5651      <eref target=""/>:
5652      "update RFC 2109 reference"
5653    </t>
5654  </list>
5658<section title="Since draft-ietf-httpbis-p1-messaging-13" anchor="changes.since.13">
5660  Closed issues:
5661  <list style="symbols">
5662    <t>
5663      <eref target=""/>:
5664      "Allow is not in 13.5.2"
5665    </t>
5666    <t>
5667      <eref target=""/>:
5668      "Handling multiple Content-Length header fields"
5669    </t>
5670    <t>
5671      <eref target=""/>:
5672      "untangle ABNFs for header fields"
5673    </t>
5674    <t>
5675      <eref target=""/>:
5676      "Content-Length ABNF broken"
5677    </t>
5678  </list>
5682<section title="Since draft-ietf-httpbis-p1-messaging-14" anchor="changes.since.14">
5684  Closed issues:
5685  <list style="symbols">
5686    <t>
5687      <eref target=""/>:
5688      "HTTP-version should be redefined as fixed length pair of DIGIT . DIGIT"
5689    </t>
5690    <t>
5691      <eref target=""/>:
5692      "Recommend minimum sizes for protocol elements"
5693    </t>
5694    <t>
5695      <eref target=""/>:
5696      "Set expectations around buffering"
5697    </t>
5698    <t>
5699      <eref target=""/>:
5700      "Considering messages in isolation"
5701    </t>
5702  </list>
5706<section title="Since draft-ietf-httpbis-p1-messaging-15" anchor="changes.since.15">
5708  Closed issues:
5709  <list style="symbols">
5710    <t>
5711      <eref target=""/>:
5712      "DNS Spoofing / DNS Binding advice"
5713    </t>
5714    <t>
5715      <eref target=""/>:
5716      "move RFCs 2145, 2616, 2817 to Historic status"
5717    </t>
5718    <t>
5719      <eref target=""/>:
5720      "\-escaping in quoted strings"
5721    </t>
5722    <t>
5723      <eref target=""/>:
5724      "'Close' should be reserved in the HTTP header field registry"
5725    </t>
5726  </list>
5730<section title="Since draft-ietf-httpbis-p1-messaging-16" anchor="changes.since.16">
5732  Closed issues:
5733  <list style="symbols">
5734    <t>
5735      <eref target=""/>:
5736      "Document HTTP's error-handling philosophy"
5737    </t>
5738    <t>
5739      <eref target=""/>:
5740      "Explain header field registration"
5741    </t>
5742    <t>
5743      <eref target=""/>:
5744      "Revise Acknowledgements Sections"
5745    </t>
5746    <t>
5747      <eref target=""/>:
5748      "Retrying Requests"
5749    </t>
5750    <t>
5751      <eref target=""/>:
5752      "Closing the connection on server error"
5753    </t>
5754  </list>
5758<section title="Since draft-ietf-httpbis-p1-messaging-17" anchor="changes.since.17">
5760  Closed issues:
5761  <list style="symbols">
5762    <t>
5763      <eref target=""/>:
5764      "Proxy-Connection and Keep-Alive"
5765    </t>
5766    <t>
5767      <eref target=""/>:
5768      "Clarify 'User Agent'"
5769    </t>
5770    <t>
5771      <eref target=""/>:
5772      "Define non-final responses"
5773    </t>
5774    <t>
5775      <eref target=""/>:
5776      "intended maturity level vs normative references"
5777    </t>
5778    <t>
5779      <eref target=""/>:
5780      "Intermediary rewriting of queries"
5781    </t>
5782  </list>
5786<section title="Since draft-ietf-httpbis-p1-messaging-18" anchor="changes.since.18">
5788  Closed issues:
5789  <list style="symbols">
5790    <t>
5791      <eref target=""/>:
5792      "message-body in CONNECT response"
5793    </t>
5794    <t>
5795      <eref target=""/>:
5796      "Misplaced text on connection handling in p2"
5797    </t>
5798    <t>
5799      <eref target=""/>:
5800      "wording of line folding rule"
5801    </t>
5802    <t>
5803      <eref target=""/>:
5804      "chunk-extensions"
5805    </t>
5806    <t>
5807      <eref target=""/>:
5808      "make IANA policy definitions consistent"
5809    </t>
5810  </list>
5814<section title="Since draft-ietf-httpbis-p1-messaging-19" anchor="changes.since.19">
5816  Closed issues:
5817  <list style="symbols">
5818    <t>
5819      <eref target=""/>:
5820      "make IANA policy definitions consistent"
5821    </t>
5822    <t>
5823      <eref target=""/>:
5824      "clarify connection header field values are case-insensitive"
5825    </t>
5826    <t>
5827      <eref target=""/>:
5828      "ABNF requirements for recipients"
5829    </t>
5830    <t>
5831      <eref target=""/>:
5832      "note introduction of new IANA registries as normative changes"
5833    </t>
5834    <t>
5835      <eref target=""/>:
5836      "Reference to ISO-8859-1 is informative"
5837    </t>
5838  </list>
5842<section title="Since draft-ietf-httpbis-p1-messaging-20" anchor="changes.since.20">
5844  Closed issues:
5845  <list style="symbols">
5846    <t>
5847      <eref target=""/>:
5848      "is 'q=' case-sensitive?"
5849    </t>
5850    <t>
5851      <eref target=""/>:
5852      "Semantics of HTTPS"
5853    </t>
5854  </list>
5857  Other changes:
5858  <list style="symbols">
5859    <t>
5860      Drop notion of header fields being "hop-by-hop" without being listed in
5861      the Connection header field.     
5862    </t>
5863    <t>
5864      Section about connection management rewritten; dropping some historic
5865      information.
5866    </t>
5867    <t>
5868      Move description of "100-continue" into Part 2.
5869    </t>
5870    <t>
5871      Rewrite the persistent connection and Upgrade requirements to be
5872      actionable by role and consistent with the rest of HTTP.
5873    </t>
5874  </list>
Note: See TracBrowser for help on using the repository browser.