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

Last change on this file since 1570 was 1570, checked in by fielding@…, 10 years ago

#250 message-body in CONNECT response

Change message body parsing of successful CONNECT responses such that
the tunnel begins immediately after the header block, as implemented in
practice, and any Content-Length or Transfer-Encoding is ignored.

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 243.8 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 "March">
16  <!ENTITY ID-YEAR "2012">
17  <!ENTITY mdash "&#8212;">
18  <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' xmlns:x=''/>">
19  <!ENTITY cache-incomplete       "<xref target='Part6' x:rel='#response.cacheability' xmlns:x=''/>">
20  <!ENTITY payload                "<xref target='Part3' xmlns:x=''/>">
21  <!ENTITY media-types            "<xref target='Part3' x:rel='#media.types' xmlns:x=''/>">
22  <!ENTITY content-codings        "<xref target='Part3' x:rel='#content.codings' xmlns:x=''/>">
23  <!ENTITY CONNECT                "<xref target='Part2' x:rel='#CONNECT' xmlns:x=''/>">
24  <!ENTITY content.negotiation    "<xref target='Part3' x:rel='#content.negotiation' xmlns:x=''/>">
25  <!ENTITY diff-mime              "<xref target='Part3' x:rel='#differences.between.http.and.mime' xmlns:x=''/>">
26  <!ENTITY representation         "<xref target='Part3' x:rel='#representation' xmlns:x=''/>">
27  <!ENTITY header-cache-control   "<xref target='Part6' x:rel='#header.cache-control' xmlns:x=''/>">
28  <!ENTITY header-date            "<xref target='Part2' x:rel='' xmlns:x=''/>">
29  <!ENTITY header-expect          "<xref target='Part2' x:rel='#header.expect' xmlns:x=''/>">
30  <!ENTITY header-mime-version    "<xref target='Part3' x:rel='#mime-version' xmlns:x=''/>">
31  <!ENTITY header-pragma          "<xref target='Part6' x:rel='#header.pragma' xmlns:x=''/>">
32  <!ENTITY header-warning         "<xref target='Part6' x:rel='#header.warning' xmlns:x=''/>">
33  <!ENTITY idempotent-methods     "<xref target='Part2' x:rel='#idempotent.methods' xmlns:x=''/>">
34  <!ENTITY method                 "<xref target='Part2' x:rel='#method' xmlns:x=''/>">
35  <!ENTITY status-code-reasonphr  "<xref target='Part2' x:rel='#status.code.and.reason.phrase' xmlns:x=''/>">
36  <!ENTITY status-codes           "<xref target='Part2' x:rel='' xmlns:x=''/>">
37  <!ENTITY status-100             "<xref target='Part2' x:rel='#status.100' xmlns:x=''/>">
38  <!ENTITY status-1xx             "<xref target='Part2' x:rel='#status.1xx' xmlns:x=''/>">
39  <!ENTITY status-203             "<xref target='Part2' x:rel='#status.203' xmlns:x=''/>">
40  <!ENTITY status-3xx             "<xref target='Part2' x:rel='#status.3xx' xmlns:x=''/>">
41  <!ENTITY status-4xx             "<xref target='Part2' x:rel='#status.4xx' xmlns:x=''/>">
42  <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x=''/>">
43  <!ENTITY cons-new-header-fields "<xref target='Part2' x:rel='#considerations.for.creating.header.fields' xmlns:x=''/>">
45<?rfc toc="yes" ?>
46<?rfc symrefs="yes" ?>
47<?rfc sortrefs="yes" ?>
48<?rfc compact="yes"?>
49<?rfc subcompact="no" ?>
50<?rfc linkmailto="no" ?>
51<?rfc editing="no" ?>
52<?rfc comments="yes"?>
53<?rfc inline="yes"?>
54<?rfc rfcedstyle="yes"?>
55<?rfc-ext allow-markup-in-artwork="yes" ?>
56<?rfc-ext include-references-in-index="yes" ?>
57<rfc obsoletes="2145,2616" updates="2817" category="std" x:maturity-level="proposed"
58     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"
59     xmlns:x=''>
60<x:link rel="next" basename="p2-semantics"/>
61<x:feedback template="{docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/>
64  <title abbrev="HTTP/1.1, Part 1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
66  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
67    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
68    <address>
69      <postal>
70        <street>345 Park Ave</street>
71        <city>San Jose</city>
72        <region>CA</region>
73        <code>95110</code>
74        <country>USA</country>
75      </postal>
76      <email></email>
77      <uri></uri>
78    </address>
79  </author>
81  <author initials="J." surname="Gettys" fullname="Jim Gettys">
82    <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
83    <address>
84      <postal>
85        <street>21 Oak Knoll Road</street>
86        <city>Carlisle</city>
87        <region>MA</region>
88        <code>01741</code>
89        <country>USA</country>
90      </postal>
91      <email></email>
92      <uri></uri>
93    </address>
94  </author>
96  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
97    <organization abbrev="HP">Hewlett-Packard Company</organization>
98    <address>
99      <postal>
100        <street>HP Labs, Large Scale Systems Group</street>
101        <street>1501 Page Mill Road, MS 1177</street>
102        <city>Palo Alto</city>
103        <region>CA</region>
104        <code>94304</code>
105        <country>USA</country>
106      </postal>
107      <email></email>
108    </address>
109  </author>
111  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
112    <organization abbrev="Microsoft">Microsoft Corporation</organization>
113    <address>
114      <postal>
115        <street>1 Microsoft Way</street>
116        <city>Redmond</city>
117        <region>WA</region>
118        <code>98052</code>
119        <country>USA</country>
120      </postal>
121      <email></email>
122    </address>
123  </author>
125  <author initials="L." surname="Masinter" fullname="Larry Masinter">
126    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
127    <address>
128      <postal>
129        <street>345 Park Ave</street>
130        <city>San Jose</city>
131        <region>CA</region>
132        <code>95110</code>
133        <country>USA</country>
134      </postal>
135      <email></email>
136      <uri></uri>
137    </address>
138  </author>
140  <author initials="P." surname="Leach" fullname="Paul J. Leach">
141    <organization abbrev="Microsoft">Microsoft Corporation</organization>
142    <address>
143      <postal>
144        <street>1 Microsoft Way</street>
145        <city>Redmond</city>
146        <region>WA</region>
147        <code>98052</code>
148      </postal>
149      <email></email>
150    </address>
151  </author>
153  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
154    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
155    <address>
156      <postal>
157        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
158        <street>The Stata Center, Building 32</street>
159        <street>32 Vassar Street</street>
160        <city>Cambridge</city>
161        <region>MA</region>
162        <code>02139</code>
163        <country>USA</country>
164      </postal>
165      <email></email>
166      <uri></uri>
167    </address>
168  </author>
170  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
171    <organization abbrev="W3C">World Wide Web Consortium</organization>
172    <address>
173      <postal>
174        <street>W3C / ERCIM</street>
175        <street>2004, rte des Lucioles</street>
176        <city>Sophia-Antipolis</city>
177        <region>AM</region>
178        <code>06902</code>
179        <country>France</country>
180      </postal>
181      <email></email>
182      <uri></uri>
183    </address>
184  </author>
186  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
187    <organization abbrev="greenbytes">greenbytes GmbH</organization>
188    <address>
189      <postal>
190        <street>Hafenweg 16</street>
191        <city>Muenster</city><region>NW</region><code>48155</code>
192        <country>Germany</country>
193      </postal>
194      <phone>+49 251 2807760</phone>
195      <facsimile>+49 251 2807761</facsimile>
196      <email></email>
197      <uri></uri>
198    </address>
199  </author>
201  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
202  <workgroup>HTTPbis Working Group</workgroup>
206   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
207   distributed, collaborative, hypertext information systems. HTTP has been in
208   use by the World Wide Web global information initiative since 1990. This
209   document is Part 1 of the seven-part specification that defines the protocol
210   referred to as "HTTP/1.1" and, taken together, obsoletes
211   <xref target="RFC2616" x:fmt="none">RFC 2616</xref> and moves it to historic
212   status, along with its predecessor <xref target="RFC2068" x:fmt="none">RFC
213   2068</xref>.
216   Part 1 provides an overview of HTTP and its associated terminology, defines
217   the "http" and "https" Uniform Resource Identifier (URI) schemes, defines
218   the generic message syntax and parsing requirements for HTTP message frames,
219   and describes general security concerns for implementations.
222   This part also obsoletes RFCs <xref target="RFC2145" x:fmt="none">2145</xref>
223   (on HTTP version numbers) and <xref target="RFC2817" x:fmt="none">2817</xref>
224   (on using CONNECT for TLS upgrades) and moves them to historic status.
228<note title="Editorial Note (To be removed by RFC Editor)">
229  <t>
230    Discussion of this draft should take place on the HTTPBIS working group
231    mailing list (, which is archived at
232    <eref target=""/>.
233  </t>
234  <t>
235    The current issues list is at
236    <eref target=""/> and related
237    documents (including fancy diffs) can be found at
238    <eref target=""/>.
239  </t>
240  <t>
241    The changes in this draft are summarized in <xref target="changes.since.18"/>.
242  </t>
246<section title="Introduction" anchor="introduction">
248   The Hypertext Transfer Protocol (HTTP) is an application-level
249   request/response protocol that uses extensible semantics and MIME-like
250   message payloads for flexible interaction with network-based hypertext
251   information systems. HTTP relies upon the Uniform Resource Identifier (URI)
252   standard <xref target="RFC3986"/> to indicate the target resource and
253   relationships between resources.
254   Messages are passed in a format similar to that used by Internet mail
255   <xref target="RFC5322"/> and the Multipurpose Internet Mail Extensions
256   (MIME) <xref target="RFC2045"/> (see &diff-mime; for the differences
257   between HTTP and MIME messages).
260   HTTP is a generic interface protocol for information systems. It is
261   designed to hide the details of how a service is implemented by presenting
262   a uniform interface to clients that is independent of the types of
263   resources provided. Likewise, servers do not need to be aware of each
264   client's purpose: an HTTP request can be considered in isolation rather
265   than being associated with a specific type of client or a predetermined
266   sequence of application steps. The result is a protocol that can be used
267   effectively in many different contexts and for which implementations can
268   evolve independently over time.
271   HTTP is also designed for use as an intermediation protocol for translating
272   communication to and from non-HTTP information systems.
273   HTTP proxies and gateways can provide access to alternative information
274   services by translating their diverse protocols into a hypertext
275   format that can be viewed and manipulated by clients in the same way
276   as HTTP services.
279   One consequence of HTTP flexibility is that the protocol cannot be
280   defined in terms of what occurs behind the interface. Instead, we
281   are limited to defining the syntax of communication, the intent
282   of received communication, and the expected behavior of recipients.
283   If the communication is considered in isolation, then successful
284   actions ought to be reflected in corresponding changes to the
285   observable interface provided by servers. However, since multiple
286   clients might act in parallel and perhaps at cross-purposes, we
287   cannot require that such changes be observable beyond the scope
288   of a single response.
291   This document is Part 1 of the seven-part specification of HTTP,
292   defining the protocol referred to as "HTTP/1.1", obsoleting
293   <xref target="RFC2616"/> and <xref target="RFC2145"/>.
294   Part 1 describes the architectural elements that are used or
295   referred to in HTTP, defines the "http" and "https" URI schemes,
296   describes overall network operation and connection management,
297   and defines HTTP message framing and forwarding requirements.
298   Our goal is to define all of the mechanisms necessary for HTTP message
299   handling that are independent of message semantics, thereby defining the
300   complete set of requirements for message parsers and
301   message-forwarding intermediaries.
304<section title="Requirement Notation" anchor="intro.requirements">
306   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
307   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
308   document are to be interpreted as described in <xref target="RFC2119"/>.
312<section title="Syntax Notation" anchor="notation">
313<iref primary="true" item="Grammar" subitem="ALPHA"/>
314<iref primary="true" item="Grammar" subitem="CR"/>
315<iref primary="true" item="Grammar" subitem="CRLF"/>
316<iref primary="true" item="Grammar" subitem="CTL"/>
317<iref primary="true" item="Grammar" subitem="DIGIT"/>
318<iref primary="true" item="Grammar" subitem="DQUOTE"/>
319<iref primary="true" item="Grammar" subitem="HEXDIG"/>
320<iref primary="true" item="Grammar" subitem="HTAB"/>
321<iref primary="true" item="Grammar" subitem="LF"/>
322<iref primary="true" item="Grammar" subitem="OCTET"/>
323<iref primary="true" item="Grammar" subitem="SP"/>
324<iref primary="true" item="Grammar" subitem="VCHAR"/>
326   This specification uses the Augmented Backus-Naur Form (ABNF) notation
327   of <xref target="RFC5234"/> with the list rule extension defined in
328   <xref target="abnf.extension"/>.  <xref target="collected.abnf"/> shows
329   the collected ABNF with the list rule expanded.
331<t anchor="core.rules">
332  <x:anchor-alias value="ALPHA"/>
333  <x:anchor-alias value="CTL"/>
334  <x:anchor-alias value="CR"/>
335  <x:anchor-alias value="CRLF"/>
336  <x:anchor-alias value="DIGIT"/>
337  <x:anchor-alias value="DQUOTE"/>
338  <x:anchor-alias value="HEXDIG"/>
339  <x:anchor-alias value="HTAB"/>
340  <x:anchor-alias value="LF"/>
341  <x:anchor-alias value="OCTET"/>
342  <x:anchor-alias value="SP"/>
343  <x:anchor-alias value="VCHAR"/>
344   The following core rules are included by
345   reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
346   ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
347   DIGIT (decimal 0-9), DQUOTE (double quote),
348   HEXDIG (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed),
349   OCTET (any 8-bit sequence of data), SP (space), and
350   VCHAR (any visible <xref target="USASCII"/> character).
353   As a convention, ABNF rule names prefixed with "obs-" denote
354   "obsolete" grammar rules that appear for historical reasons.
359<section title="Architecture" anchor="architecture">
361   HTTP was created for the World Wide Web architecture
362   and has evolved over time to support the scalability needs of a worldwide
363   hypertext system. Much of that architecture is reflected in the terminology
364   and syntax productions used to define HTTP.
367<section title="Client/Server Messaging" anchor="operation">
368<iref primary="true" item="client"/>
369<iref primary="true" item="server"/>
370<iref primary="true" item="connection"/>
372   HTTP is a stateless request/response protocol that operates by exchanging
373   <x:dfn>messages</x:dfn> (<xref target="http.message"/>) across a reliable
374   transport or session-layer
375   "<x:dfn>connection</x:dfn>". An HTTP "<x:dfn>client</x:dfn>" is a
376   program that establishes a connection to a server for the purpose of
377   sending one or more HTTP requests.  An HTTP "<x:dfn>server</x:dfn>" is a
378   program that accepts connections in order to service HTTP requests by
379   sending HTTP responses.
381<iref primary="true" item="user agent"/>
382<iref primary="true" item="origin server"/>
383<iref primary="true" item="browser"/>
384<iref primary="true" item="spider"/>
385<iref primary="true" item="sender"/>
386<iref primary="true" item="recipient"/>
388   Note that the terms client and server refer only to the roles that
389   these programs perform for a particular connection.  The same program
390   might act as a client on some connections and a server on others.  We use
391   the term "<x:dfn>user agent</x:dfn>" to refer to the program that initiates a request,
392   such as a WWW browser, editor, or spider (web-traversing robot), and
393   the term "<x:dfn>origin server</x:dfn>" to refer to the program that can originate
394   authoritative responses to a request.  For general requirements, we use
395   the term "<x:dfn>sender</x:dfn>" to refer to whichever component sent a given message
396   and the term "<x:dfn>recipient</x:dfn>" to refer to any component that receives the
397   message.
400  <t>
401    <x:h>Note:</x:h> The term 'user agent' covers both those situations where
402    there is a user (human) interacting with the software agent (and for which
403    user interface or interactive suggestions might be made, e.g., warning the
404    user or given the user an option in the case of security or privacy
405    options) and also those where the software agent may act autonomously.
406  </t>
409   Most HTTP communication consists of a retrieval request (GET) for
410   a representation of some resource identified by a URI.  In the
411   simplest case, this might be accomplished via a single bidirectional
412   connection (===) between the user agent (UA) and the origin server (O).
414<figure><artwork type="drawing">
415         request   &gt;
416    UA ======================================= O
417                                &lt;   response
419<iref primary="true" item="message"/>
420<iref primary="true" item="request"/>
421<iref primary="true" item="response"/>
423   A client sends an HTTP request to the server in the form of a <x:dfn>request</x:dfn>
424   message, beginning with a request-line that includes a method, URI, and
425   protocol version (<xref target="request.line"/>),
426   followed by MIME-like header fields containing
427   request modifiers, client information, and payload metadata
428   (<xref target="header.fields"/>),
429   an empty line to indicate the end of the header section, and finally
430   a message body containing the payload body (if any,
431   <xref target="message.body"/>).
434   A server responds to the client's request by sending one or more HTTP
435   <x:dfn>response</x:dfn>
436   messages, each beginning with a status line that
437   includes the protocol version, a success or error code, and textual
438   reason phrase (<xref target="status.line"/>),
439   possibly followed by MIME-like header fields containing server
440   information, resource metadata, and payload metadata
441   (<xref target="header.fields"/>),
442   an empty line to indicate the end of the header section, and finally
443   a message body containing the payload body (if any,
444   <xref target="message.body"/>).
447   The following example illustrates a typical message exchange for a
448   GET request on the URI "":
451client request:
452</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
453GET /hello.txt HTTP/1.1
454User-Agent: curl/7.16.3 libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3
456Accept: */*
460server response:
461</preamble><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
462HTTP/1.1 200 OK
463Date: Mon, 27 Jul 2009 12:28:53 GMT
464Server: Apache
465Last-Modified: Wed, 22 Jul 2009 19:15:56 GMT
466ETag: "34aa387-d-1568eb00"
467Accept-Ranges: bytes
468Content-Length: <x:length-of target="exbody"/>
469Vary: Accept-Encoding
470Content-Type: text/plain
472<x:span anchor="exbody">Hello World!
476<section title="Connections and Transport Independence" anchor="transport-independence">
478   HTTP messaging is independent of the underlying transport or
479   session-layer connection protocol(s).  HTTP only presumes a reliable
480   transport with in-order delivery of requests and the corresponding
481   in-order delivery of responses.  The mapping of HTTP request and
482   response structures onto the data units of the underlying transport
483   protocol is outside the scope of this specification.
486   The specific connection protocols to be used for an interaction
487   are determined by client configuration and the target resource's URI.
488   For example, the "http" URI scheme
489   (<xref target="http.uri"/>) indicates a default connection of TCP
490   over IP, with a default TCP port of 80, but the client might be
491   configured to use a proxy via some other connection port or protocol
492   instead of using the defaults.
495   A connection might be used for multiple HTTP request/response exchanges,
496   as defined in <xref target="persistent.connections"/>.
500<section title="Intermediaries" anchor="intermediaries">
501<iref primary="true" item="intermediary"/>
503   HTTP enables the use of intermediaries to satisfy requests through
504   a chain of connections.  There are three common forms of HTTP
505   <x:dfn>intermediary</x:dfn>: proxy, gateway, and tunnel.  In some cases,
506   a single intermediary might act as an origin server, proxy, gateway,
507   or tunnel, switching behavior based on the nature of each request.
509<figure><artwork type="drawing">
510         &gt;             &gt;             &gt;             &gt;
511    <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>
512               &lt;             &lt;             &lt;             &lt;
515   The figure above shows three intermediaries (A, B, and C) between the
516   user agent and origin server. A request or response message that
517   travels the whole chain will pass through four separate connections.
518   Some HTTP communication options
519   might apply only to the connection with the nearest, non-tunnel
520   neighbor, only to the end-points of the chain, or to all connections
521   along the chain. Although the diagram is linear, each participant might
522   be engaged in multiple, simultaneous communications. For example, B
523   might be receiving requests from many clients other than A, and/or
524   forwarding requests to servers other than C, at the same time that it
525   is handling A's request.
528<iref primary="true" item="upstream"/><iref primary="true" item="downstream"/>
529<iref primary="true" item="inbound"/><iref primary="true" item="outbound"/>
530   We use the terms "<x:dfn>upstream</x:dfn>" and "<x:dfn>downstream</x:dfn>"
531   to describe various requirements in relation to the directional flow of a
532   message: all messages flow from upstream to downstream.
533   Likewise, we use the terms inbound and outbound to refer to
534   directions in relation to the request path:
535   "<x:dfn>inbound</x:dfn>" means toward the origin server and
536   "<x:dfn>outbound</x:dfn>" means toward the user agent.
538<t><iref primary="true" item="proxy"/>
539   A "<x:dfn>proxy</x:dfn>" is a message forwarding agent that is selected by the
540   client, usually via local configuration rules, to receive requests
541   for some type(s) of absolute URI and attempt to satisfy those
542   requests via translation through the HTTP interface.  Some translations
543   are minimal, such as for proxy requests for "http" URIs, whereas
544   other requests might require translation to and from entirely different
545   application-layer protocols. Proxies are often used to group an
546   organization's HTTP requests through a common intermediary for the
547   sake of security, annotation services, or shared caching.
550<iref primary="true" item="transforming proxy"/>
551<iref primary="true" item="non-transforming proxy"/>
552   An HTTP-to-HTTP proxy is called a "<x:dfn>transforming proxy</x:dfn>" if it is designed
553   or configured to modify request or response messages in a semantically
554   meaningful way (i.e., modifications, beyond those required by normal
555   HTTP processing, that change the message in a way that would be
556   significant to the original sender or potentially significant to
557   downstream recipients).  For example, a transforming proxy might be
558   acting as a shared annotation server (modifying responses to include
559   references to a local annotation database), a malware filter, a
560   format transcoder, or an intranet-to-Internet privacy filter.  Such
561   transformations are presumed to be desired by the client (or client
562   organization) that selected the proxy and are beyond the scope of
563   this specification.  However, when a proxy is not intended to transform
564   a given message, we use the term "<x:dfn>non-transforming proxy</x:dfn>" to target
565   requirements that preserve HTTP message semantics. See &status-203; and
566   &header-warning; for status and warning codes related to transformations.
568<t><iref primary="true" item="gateway"/><iref primary="true" item="reverse proxy"/>
569<iref primary="true" item="accelerator"/>
570   A "<x:dfn>gateway</x:dfn>" (a.k.a., "<x:dfn>reverse proxy</x:dfn>")
571   is a receiving agent that acts
572   as a layer above some other server(s) and translates the received
573   requests to the underlying server's protocol.  Gateways are often
574   used to encapsulate legacy or untrusted information services, to
575   improve server performance through "<x:dfn>accelerator</x:dfn>" caching, and to
576   enable partitioning or load-balancing of HTTP services across
577   multiple machines.
580   A gateway behaves as an origin server on its outbound connection and
581   as a user agent on its inbound connection.
582   All HTTP requirements applicable to an origin server
583   also apply to the outbound communication of a gateway.
584   A gateway communicates with inbound servers using any protocol that
585   it desires, including private extensions to HTTP that are outside
586   the scope of this specification.  However, an HTTP-to-HTTP gateway
587   that wishes to interoperate with third-party HTTP servers &MUST;
588   conform to HTTP user agent requirements on the gateway's inbound
589   connection and &MUST; implement the Connection
590   (<xref target="header.connection"/>) and Via (<xref target="header.via"/>)
591   header fields for both connections.
593<t><iref primary="true" item="tunnel"/>
594   A "<x:dfn>tunnel</x:dfn>" acts as a blind relay between two connections
595   without changing the messages. Once active, a tunnel is not
596   considered a party to the HTTP communication, though the tunnel might
597   have been initiated by an HTTP request. A tunnel ceases to exist when
598   both ends of the relayed connection are closed. Tunnels are used to
599   extend a virtual connection through an intermediary, such as when
600   transport-layer security is used to establish private communication
601   through a shared firewall proxy.
603<t><iref primary="true" item="interception proxy"/><iref primary="true" item="transparent proxy"/>
604<iref primary="true" item="captive portal"/>
605   In addition, there may exist network intermediaries that are not
606   considered part of the HTTP communication but nevertheless act as
607   filters or redirecting agents (usually violating HTTP semantics,
608   causing security problems, and otherwise making a mess of things).
609   Such a network intermediary, often referred to as an "<x:dfn>interception proxy</x:dfn>"
610   <xref target="RFC3040"/>, "<x:dfn>transparent proxy</x:dfn>" <xref target="RFC1919"/>,
611   or "<x:dfn>captive portal</x:dfn>",
612   differs from an HTTP proxy because it has not been selected by the client.
613   Instead, the network intermediary redirects outgoing TCP port 80 packets
614   (and occasionally other common port traffic) to an internal HTTP server.
615   Interception proxies are commonly found on public network access points,
616   as a means of enforcing account subscription prior to allowing use of
617   non-local Internet services, and within corporate firewalls to enforce
618   network usage policies.
619   They are indistinguishable from a man-in-the-middle attack.
622   HTTP is defined as a stateless protocol, meaning that each request message
623   can be understood in isolation.  Many implementations depend on HTTP's
624   stateless design in order to reuse proxied connections or dynamically
625   load balance requests across multiple servers.  Hence, servers &MUST-NOT;
626   assume that two requests on the same connection are from the same user
627   agent unless the connection is secured and specific to that agent.
628   Some non-standard HTTP extensions (e.g., <xref target="RFC4559"/>) have
629   been known to violate this requirement, resulting in security and
630   interoperability problems.
634<section title="Caches" anchor="caches">
635<iref primary="true" item="cache"/>
637   A "<x:dfn>cache</x:dfn>" is a local store of previous response messages and the
638   subsystem that controls its message storage, retrieval, and deletion.
639   A cache stores cacheable responses in order to reduce the response
640   time and network bandwidth consumption on future, equivalent
641   requests. Any client or server &MAY; employ a cache, though a cache
642   cannot be used by a server while it is acting as a tunnel.
645   The effect of a cache is that the request/response chain is shortened
646   if one of the participants along the chain has a cached response
647   applicable to that request. The following illustrates the resulting
648   chain if B has a cached copy of an earlier response from O (via C)
649   for a request which has not been cached by UA or A.
651<figure><artwork type="drawing">
652            &gt;             &gt;
653       UA =========== A =========== B - - - - - - C - - - - - - O
654                  &lt;             &lt;
656<t><iref primary="true" item="cacheable"/>
657   A response is "<x:dfn>cacheable</x:dfn>" if a cache is allowed to store a copy of
658   the response message for use in answering subsequent requests.
659   Even when a response is cacheable, there might be additional
660   constraints placed by the client or by the origin server on when
661   that cached response can be used for a particular request. HTTP
662   requirements for cache behavior and cacheable responses are
663   defined in &caching-overview;. 
666   There are a wide variety of architectures and configurations
667   of caches and proxies deployed across the World Wide Web and
668   inside large organizations. These systems include national hierarchies
669   of proxy caches to save transoceanic bandwidth, systems that
670   broadcast or multicast cache entries, organizations that distribute
671   subsets of cached data via optical media, and so on.
675<section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
677   This specification targets conformance criteria according to the role of
678   a participant in HTTP communication.  Hence, HTTP requirements are placed
679   on senders, recipients, clients, servers, user agents, intermediaries,
680   origin servers, proxies, gateways, or caches, depending on what behavior
681   is being constrained by the requirement.
684   An implementation is considered conformant if it complies with all of the
685   requirements associated with the roles it partakes in HTTP.
688   Senders &MUST-NOT; generate protocol elements that do not match the grammar
689   defined by the ABNF rules for those protocol elements.
692   Unless otherwise noted, recipients &MAY; attempt to recover a usable
693   protocol element from an invalid construct.  HTTP does not define
694   specific error handling mechanisms except when they have a direct impact
695   on security, since different applications of the protocol require
696   different error handling strategies.  For example, a Web browser might
697   wish to transparently recover from a response where the Location header
698   field doesn't parse according to the ABNF, whereas a systems control
699   client might consider any form of error recovery to be dangerous.
703<section title="Protocol Versioning" anchor="http.version">
704  <x:anchor-alias value="HTTP-version"/>
705  <x:anchor-alias value="HTTP-name"/>
707   HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate
708   versions of the protocol. This specification defines version "1.1".
709   The protocol version as a whole indicates the sender's conformance
710   with the set of requirements laid out in that version's corresponding
711   specification of HTTP.
714   The version of an HTTP message is indicated by an HTTP-version field
715   in the first line of the message. HTTP-version is case-sensitive.
717<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-version"/><iref primary="true" item="Grammar" subitem="HTTP-name"/>
718  <x:ref>HTTP-version</x:ref>  = <x:ref>HTTP-name</x:ref> "/" <x:ref>DIGIT</x:ref> "." <x:ref>DIGIT</x:ref>
719  <x:ref>HTTP-name</x:ref>     = <x:abnf-char-sequence>"HTTP"</x:abnf-char-sequence> ; "HTTP", case-sensitive
722   The HTTP version number consists of two decimal digits separated by a "."
723   (period or decimal point).  The first digit ("major version") indicates the
724   HTTP messaging syntax, whereas the second digit ("minor version") indicates
725   the highest minor version to which the sender is
726   conformant and able to understand for future communication.  The minor
727   version advertises the sender's communication capabilities even when the
728   sender is only using a backwards-compatible subset of the protocol,
729   thereby letting the recipient know that more advanced features can
730   be used in response (by servers) or in future requests (by clients).
733   When an HTTP/1.1 message is sent to an HTTP/1.0 recipient
734   <xref target="RFC1945"/> or a recipient whose version is unknown,
735   the HTTP/1.1 message is constructed such that it can be interpreted
736   as a valid HTTP/1.0 message if all of the newer features are ignored.
737   This specification places recipient-version requirements on some
738   new features so that a conformant sender will only use compatible
739   features until it has determined, through configuration or the
740   receipt of a message, that the recipient supports HTTP/1.1.
743   The interpretation of a header field does not change between minor
744   versions of the same major HTTP version, though the default
745   behavior of a recipient in the absence of such a field can change.
746   Unless specified otherwise, header fields defined in HTTP/1.1 are
747   defined for all versions of HTTP/1.x.  In particular, the Host and
748   Connection header fields ought to be implemented by all HTTP/1.x
749   implementations whether or not they advertise conformance with HTTP/1.1.
752   New header fields can be defined such that, when they are
753   understood by a recipient, they might override or enhance the
754   interpretation of previously defined header fields.  When an
755   implementation receives an unrecognized header field, the recipient
756   &MUST; ignore that header field for local processing regardless of
757   the message's HTTP version.  An unrecognized header field received
758   by a proxy &MUST; be forwarded downstream unless the header field's
759   field-name is listed in the message's Connection header-field
760   (see <xref target="header.connection"/>).
761   These requirements allow HTTP's functionality to be enhanced without
762   requiring prior update of deployed intermediaries.
765   Intermediaries that process HTTP messages (i.e., all intermediaries
766   other than those acting as tunnels) &MUST; send their own HTTP-version
767   in forwarded messages.  In other words, they &MUST-NOT; blindly
768   forward the first line of an HTTP message without ensuring that the
769   protocol version in that message matches a version to which that
770   intermediary is conformant for both the receiving and
771   sending of messages.  Forwarding an HTTP message without rewriting
772   the HTTP-version might result in communication errors when downstream
773   recipients use the message sender's version to determine what features
774   are safe to use for later communication with that sender.
777   An HTTP client &SHOULD; send a request version equal to the highest
778   version to which the client is conformant and
779   whose major version is no higher than the highest version supported
780   by the server, if this is known.  An HTTP client &MUST-NOT; send a
781   version to which it is not conformant.
784   An HTTP client &MAY; send a lower request version if it is known that
785   the server incorrectly implements the HTTP specification, but only
786   after the client has attempted at least one normal request and determined
787   from the response status or header fields (e.g., Server) that the
788   server improperly handles higher request versions.
791   An HTTP server &SHOULD; send a response version equal to the highest
792   version to which the server is conformant and
793   whose major version is less than or equal to the one received in the
794   request.  An HTTP server &MUST-NOT; send a version to which it is not
795   conformant.  A server &MAY; send a 505 (HTTP
796   Version Not Supported) response if it cannot send a response using the
797   major version used in the client's request.
800   An HTTP server &MAY; send an HTTP/1.0 response to an HTTP/1.0 request
801   if it is known or suspected that the client incorrectly implements the
802   HTTP specification and is incapable of correctly processing later
803   version responses, such as when a client fails to parse the version
804   number correctly or when an intermediary is known to blindly forward
805   the HTTP-version even when it doesn't conform to the given minor
806   version of the protocol. Such protocol downgrades &SHOULD-NOT; be
807   performed unless triggered by specific client attributes, such as when
808   one or more of the request header fields (e.g., User-Agent) uniquely
809   match the values sent by a client known to be in error.
812   The intention of HTTP's versioning design is that the major number
813   will only be incremented if an incompatible message syntax is
814   introduced, and that the minor number will only be incremented when
815   changes made to the protocol have the effect of adding to the message
816   semantics or implying additional capabilities of the sender.  However,
817   the minor version was not incremented for the changes introduced between
818   <xref target="RFC2068"/> and <xref target="RFC2616"/>, and this revision
819   is specifically avoiding any such changes to the protocol.
823<section title="Uniform Resource Identifiers" anchor="uri">
824<iref primary="true" item="resource"/>
826   Uniform Resource Identifiers (URIs) <xref target="RFC3986"/> are used
827   throughout HTTP as the means for identifying resources. URI references
828   are used to target requests, indicate redirects, and define relationships.
829   HTTP does not limit what a resource might be; it merely defines an interface
830   that can be used to interact with a resource via HTTP. More information on
831   the scope of URIs and resources can be found in <xref target="RFC3986"/>.
833  <x:anchor-alias value="URI-reference"/>
834  <x:anchor-alias value="absolute-URI"/>
835  <x:anchor-alias value="relative-part"/>
836  <x:anchor-alias value="authority"/>
837  <x:anchor-alias value="path-abempty"/>
838  <x:anchor-alias value="path-absolute"/>
839  <x:anchor-alias value="port"/>
840  <x:anchor-alias value="query"/>
841  <x:anchor-alias value="uri-host"/>
842  <x:anchor-alias value="partial-URI"/>
844   This specification adopts the definitions of "URI-reference",
845   "absolute-URI", "relative-part", "port", "host",
846   "path-abempty", "path-absolute", "query", and "authority" from the
847   URI generic syntax <xref target="RFC3986"/>.
848   In addition, we define a partial-URI rule for protocol elements
849   that allow a relative URI but not a fragment.
851<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="URI-reference"/><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"/>
852  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in <xref target="RFC3986" x:fmt="," x:sec="4.1"/>&gt;
853  <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in <xref target="RFC3986" x:fmt="," x:sec="4.3"/>&gt;
854  <x:ref>relative-part</x:ref> = &lt;relative-part, defined in <xref target="RFC3986" x:fmt="," x:sec="4.2"/>&gt;
855  <x:ref>authority</x:ref>     = &lt;authority, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2"/>&gt;
856  <x:ref>path-abempty</x:ref>  = &lt;path-abempty, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
857  <x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
858  <x:ref>port</x:ref>          = &lt;port, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.3"/>&gt;
859  <x:ref>query</x:ref>         = &lt;query, defined in <xref target="RFC3986" x:fmt="," x:sec="3.4"/>&gt;
860  <x:ref>uri-host</x:ref>      = &lt;host, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>&gt;
862  <x:ref>partial-URI</x:ref>   = relative-part [ "?" query ]
865   Each protocol element in HTTP that allows a URI reference will indicate
866   in its ABNF production whether the element allows any form of reference
867   (URI-reference), only a URI in absolute form (absolute-URI), only the
868   path and optional query components, or some combination of the above.
869   Unless otherwise indicated, URI references are parsed relative to the
870   effective request URI, which defines the default base URI for references
871   in both the request and its corresponding response.
874<section title="http URI scheme" anchor="http.uri">
875  <x:anchor-alias value="http-URI"/>
876  <iref item="http URI scheme" primary="true"/>
877  <iref item="URI scheme" subitem="http" primary="true"/>
879   The "http" URI scheme is hereby defined for the purpose of minting
880   identifiers according to their association with the hierarchical
881   namespace governed by a potential HTTP origin server listening for
882   TCP connections on a given port.
884<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http-URI"/>
885  <x:ref>http-URI</x:ref> = "http:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
888   The HTTP origin server is identified by the generic syntax's
889   <x:ref>authority</x:ref> component, which includes a host identifier
890   and optional TCP port (<xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>).
891   The remainder of the URI, consisting of both the hierarchical path
892   component and optional query component, serves as an identifier for
893   a potential resource within that origin server's name space.
896   If the host identifier is provided as an IP literal or IPv4 address,
897   then the origin server is any listener on the indicated TCP port at
898   that IP address. If host is a registered name, then that name is
899   considered an indirect identifier and the recipient might use a name
900   resolution service, such as DNS, to find the address of a listener
901   for that host.
902   The host &MUST-NOT; be empty; if an "http" URI is received with an
903   empty host, then it &MUST; be rejected as invalid.
904   If the port subcomponent is empty or not given, then TCP port 80 is
905   assumed (the default reserved port for WWW services).
908   Regardless of the form of host identifier, access to that host is not
909   implied by the mere presence of its name or address. The host might or might
910   not exist and, even when it does exist, might or might not be running an
911   HTTP server or listening to the indicated port. The "http" URI scheme
912   makes use of the delegated nature of Internet names and addresses to
913   establish a naming authority (whatever entity has the ability to place
914   an HTTP server at that Internet name or address) and allows that
915   authority to determine which names are valid and how they might be used.
918   When an "http" URI is used within a context that calls for access to the
919   indicated resource, a client &MAY; attempt access by resolving
920   the host to an IP address, establishing a TCP connection to that address
921   on the indicated port, and sending an HTTP request message
922   (<xref target="http.message"/>) containing the URI's identifying data
923   (<xref target="message.routing"/>) to the server.
924   If the server responds to that request with a non-interim HTTP response
925   message, as described in &status-code-reasonphr;, then that response
926   is considered an authoritative answer to the client's request.
929   Although HTTP is independent of the transport protocol, the "http"
930   scheme is specific to TCP-based services because the name delegation
931   process depends on TCP for establishing authority.
932   An HTTP service based on some other underlying connection protocol
933   would presumably be identified using a different URI scheme, just as
934   the "https" scheme (below) is used for servers that require an SSL/TLS
935   transport layer on a connection. Other protocols might also be used to
936   provide access to "http" identified resources &mdash; it is only the
937   authoritative interface used for mapping the namespace that is
938   specific to TCP.
941   The URI generic syntax for authority also includes a deprecated
942   userinfo subcomponent (<xref target="RFC3986" x:fmt="," x:sec="3.2.1"/>)
943   for including user authentication information in the URI.  Some
944   implementations make use of the userinfo component for internal
945   configuration of authentication information, such as within command
946   invocation options, configuration files, or bookmark lists, even
947   though such usage might expose a user identifier or password.
948   Senders &MUST-NOT; include a userinfo subcomponent (and its "@"
949   delimiter) when transmitting an "http" URI in a message.  Recipients
950   of HTTP messages that contain a URI reference &SHOULD; parse for the
951   existence of userinfo and treat its presence as an error, likely
952   indicating that the deprecated subcomponent is being used to obscure
953   the authority for the sake of phishing attacks.
957<section title="https URI scheme" anchor="https.uri">
958   <x:anchor-alias value="https-URI"/>
959   <iref item="https URI scheme"/>
960   <iref item="URI scheme" subitem="https"/>
962   The "https" URI scheme is hereby defined for the purpose of minting
963   identifiers according to their association with the hierarchical
964   namespace governed by a potential HTTP origin server listening for
965   SSL/TLS-secured connections on a given TCP port.
968   All of the requirements listed above for the "http" scheme are also
969   requirements for the "https" scheme, except that a default TCP port
970   of 443 is assumed if the port subcomponent is empty or not given,
971   and the TCP connection &MUST; be secured for privacy through the
972   use of strong encryption prior to sending the first HTTP request.
974<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="https-URI"/>
975  <x:ref>https-URI</x:ref> = "https:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
978   Unlike the "http" scheme, responses to "https" identified requests
979   are never "public" and thus &MUST-NOT; be reused for shared caching.
980   They can, however, be reused in a private cache if the message is
981   cacheable by default in HTTP or specifically indicated as such by
982   the Cache-Control header field (&header-cache-control;).
985   Resources made available via the "https" scheme have no shared
986   identity with the "http" scheme even if their resource identifiers
987   indicate the same authority (the same host listening to the same
988   TCP port).  They are distinct name spaces and are considered to be
989   distinct origin servers.  However, an extension to HTTP that is
990   defined to apply to entire host domains, such as the Cookie protocol
991   <xref target="RFC6265"/>, can allow information
992   set by one service to impact communication with other services
993   within a matching group of host domains.
996   The process for authoritative access to an "https" identified
997   resource is defined in <xref target="RFC2818"/>.
1001<section title="http and https URI Normalization and Comparison" anchor="uri.comparison">
1003   Since the "http" and "https" schemes conform to the URI generic syntax,
1004   such URIs are normalized and compared according to the algorithm defined
1005   in <xref target="RFC3986" x:fmt="," x:sec="6"/>, using the defaults
1006   described above for each scheme.
1009   If the port is equal to the default port for a scheme, the normal
1010   form is to elide the port subcomponent. Likewise, an empty path
1011   component is equivalent to an absolute path of "/", so the normal
1012   form is to provide a path of "/" instead. The scheme and host
1013   are case-insensitive and normally provided in lowercase; all
1014   other components are compared in a case-sensitive manner.
1015   Characters other than those in the "reserved" set are equivalent
1016   to their percent-encoded octets (see <xref target="RFC3986"
1017   x:fmt="," x:sec="2.1"/>): the normal form is to not encode them.
1020   For example, the following three URIs are equivalent:
1022<figure><artwork type="example">
1031<section title="Message Format" anchor="http.message">
1032<x:anchor-alias value="generic-message"/>
1033<x:anchor-alias value="message.types"/>
1034<x:anchor-alias value="HTTP-message"/>
1035<x:anchor-alias value="start-line"/>
1036<iref item="header section"/>
1037<iref item="headers"/>
1038<iref item="header field"/>
1040   All HTTP/1.1 messages consist of a start-line followed by a sequence of
1041   octets in a format similar to the Internet Message Format
1042   <xref target="RFC5322"/>: zero or more header fields (collectively
1043   referred to as the "headers" or the "header section"), an empty line
1044   indicating the end of the header section, and an optional message body.
1046<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-message"/>
1047  <x:ref>HTTP-message</x:ref>   = <x:ref>start-line</x:ref>
1048                   *( <x:ref>header-field</x:ref> <x:ref>CRLF</x:ref> )
1049                   <x:ref>CRLF</x:ref>
1050                   [ <x:ref>message-body</x:ref> ]
1053   The normal procedure for parsing an HTTP message is to read the
1054   start-line into a structure, read each header field into a hash
1055   table by field name until the empty line, and then use the parsed
1056   data to determine if a message body is expected.  If a message body
1057   has been indicated, then it is read as a stream until an amount
1058   of octets equal to the message body length is read or the connection
1059   is closed.
1062   Recipients &MUST; parse an HTTP message as a sequence of octets in an
1063   encoding that is a superset of US-ASCII <xref target="USASCII"/>.
1064   Parsing an HTTP message as a stream of Unicode characters, without regard
1065   for the specific encoding, creates security vulnerabilities due to the
1066   varying ways that string processing libraries handle invalid multibyte
1067   character sequences that contain the octet LF (%x0A).  String-based
1068   parsers can only be safely used within protocol elements after the element
1069   has been extracted from the message, such as within a header field-value
1070   after message parsing has delineated the individual fields.
1073   An HTTP message can be parsed as a stream for incremental processing or
1074   forwarding downstream.  However, recipients cannot rely on incremental
1075   delivery of partial messages, since some implementations will buffer or
1076   delay message forwarding for the sake of network efficiency, security
1077   checks, or payload transformations.
1080<section title="Start Line" anchor="start.line">
1081  <x:anchor-alias value="Start-Line"/>
1083   An HTTP message can either be a request from client to server or a
1084   response from server to client.  Syntactically, the two types of message
1085   differ only in the start-line, which is either a request-line (for requests)
1086   or a status-line (for responses), and in the algorithm for determining
1087   the length of the message body (<xref target="message.body"/>).
1088   In theory, a client could receive requests and a server could receive
1089   responses, distinguishing them by their different start-line formats,
1090   but in practice servers are implemented to only expect a request
1091   (a response is interpreted as an unknown or invalid request method)
1092   and clients are implemented to only expect a response.
1094<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="start-line"/>
1095  <x:ref>start-line</x:ref>     = <x:ref>request-line</x:ref> / <x:ref>status-line</x:ref>
1100   Implementations &MUST-NOT; send whitespace between the start-line and
1101   the first header field. The presence of such whitespace in a request
1102   might be an attempt to trick a server into ignoring that field or
1103   processing the line after it as a new request, either of which might
1104   result in a security vulnerability if other implementations within
1105   the request chain interpret the same message differently.
1106   Likewise, the presence of such whitespace in a response might be
1107   ignored by some clients or cause others to cease parsing.
1110<section title="Request Line" anchor="request.line">
1111  <x:anchor-alias value="Request"/>
1112  <x:anchor-alias value="request-line"/>
1114   A request-line begins with a method token, followed by a single
1115   space (SP), the request-target, another single space (SP), the
1116   protocol version, and ending with CRLF.
1118<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-line"/>
1119  <x:ref>request-line</x:ref>   = <x:ref>method</x:ref> <x:ref>SP</x:ref> <x:ref>request-target</x:ref> <x:ref>SP</x:ref> <x:ref>HTTP-version</x:ref> <x:ref>CRLF</x:ref>
1122<section title="Method" anchor="method">
1123  <x:anchor-alias value="method"/>
1125   The method token indicates the request method to be performed on the
1126   target resource. The request method is case-sensitive.
1128<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="method"/>
1129  <x:ref>method</x:ref>         = <x:ref>token</x:ref>
1132   The methods defined by this specification can be found in
1133   &method;, along with information regarding the HTTP method registry
1134   and considerations for defining new methods.
1138<section title="request-target" anchor="request-target">
1139  <x:anchor-alias value="request-target"/>
1141   The request-target identifies the target resource upon which to apply
1142   the request.  The four options for request-target are described in
1143   <xref target="request-target-types"/>.
1145<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-target"/>
1146  <x:ref>request-target</x:ref> = "*"
1147                 / <x:ref>absolute-URI</x:ref>
1148                 / ( <x:ref>path-absolute</x:ref> [ "?" <x:ref>query</x:ref> ] )
1149                 / <x:ref>authority</x:ref>
1152   HTTP does not place a pre-defined limit on the length of a request-target.
1153   A server &MUST; be prepared to receive URIs of unbounded length and
1154   respond with the 414 (URI Too Long) status code if the received
1155   request-target would be longer than the server wishes to handle
1156   (see &status-414;).
1159   Various ad-hoc limitations on request-target length are found in practice.
1160   It is &RECOMMENDED; that all HTTP senders and recipients support
1161   request-target lengths of 8000 or more octets.
1164  <t>
1165    <x:h>Note:</x:h> Fragments (<xref target="RFC3986" x:fmt="," x:sec="3.5"/>)
1166    are not part of the request-target and thus will not be transmitted
1167    in an HTTP request.
1168  </t>
1173<section title="Response Status Line" anchor="status.line">
1174  <x:anchor-alias value="response"/>
1175  <x:anchor-alias value="status-line"/>
1177   The first line of a response message is the status-line, consisting
1178   of the protocol version, a space (SP), the status code, another space,
1179   a possibly-empty textual phrase describing the status code, and
1180   ending with CRLF.
1182<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-line"/>
1183  <x:ref>status-line</x:ref> = <x:ref>HTTP-version</x:ref> <x:ref>SP</x:ref> <x:ref>status-code</x:ref> <x:ref>SP</x:ref> <x:ref>reason-phrase</x:ref> <x:ref>CRLF</x:ref>
1186<section title="Status Code" anchor="status.code">
1187  <x:anchor-alias value="status-code"/>
1189   The status-code element is a 3-digit integer result code of the attempt to
1190   understand and satisfy the request. See &status-code-reasonphr; for
1191   further information, such as the list of status codes defined by this
1192   specification, the IANA registry, and considerations for new status codes.
1194<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-code"/>
1195  <x:ref>status-code</x:ref>    = 3<x:ref>DIGIT</x:ref>
1199<section title="Reason Phrase" anchor="reason.phrase">
1200  <x:anchor-alias value="reason-phrase"/>
1202   The reason-phrase element exists for the sole purpose of providing a
1203   textual description associated with the numeric status code, mostly
1204   out of deference to earlier Internet application protocols that were more
1205   frequently used with interactive text clients. A client &SHOULD; ignore
1206   the reason-phrase content.
1208<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="reason-phrase"/>
1209  <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> )
1215<section title="Header Fields" anchor="header.fields">
1216  <x:anchor-alias value="header-field"/>
1217  <x:anchor-alias value="field-content"/>
1218  <x:anchor-alias value="field-name"/>
1219  <x:anchor-alias value="field-value"/>
1220  <x:anchor-alias value="obs-fold"/>
1222   Each HTTP header field consists of a case-insensitive field name
1223   followed by a colon (":"), optional whitespace, and the field value.
1225<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"/>
1226  <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>
1227  <x:ref>field-name</x:ref>     = <x:ref>token</x:ref>
1228  <x:ref>field-value</x:ref>    = *( <x:ref>field-content</x:ref> / <x:ref>obs-fold</x:ref> )
1229  <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> )
1230  <x:ref>obs-fold</x:ref>       = <x:ref>CRLF</x:ref> ( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1231                 ; obsolete line folding
1232                 ; see <xref target="field.parsing"/>
1235   The field-name token labels the corresponding field-value as having the
1236   semantics defined by that header field.  For example, the Date header field
1237   is defined in &header-date; as containing the origination
1238   timestamp for the message in which it appears.
1241   HTTP header fields are fully extensible: there is no limit on the
1242   introduction of new field names, each presumably defining new semantics,
1243   or on the number of header fields used in a given message.  Existing
1244   fields are defined in each part of this specification and in many other
1245   specifications outside the standards process.
1246   New header fields can be introduced without changing the protocol version
1247   if their defined semantics allow them to be safely ignored by recipients
1248   that do not recognize them.
1251   New HTTP header fields &SHOULD; be registered with IANA according
1252   to the procedures in &cons-new-header-fields;.
1253   Unrecognized header fields &MUST; be forwarded by a proxy unless the
1254   field-name is listed in the Connection header field
1255   (<xref target="header.connection"/>) or the proxy is specifically
1256   configured to block or otherwise transform such fields.
1257   Unrecognized header fields &SHOULD; be ignored by other recipients.
1260   The order in which header fields with differing field names are
1261   received is not significant. However, it is "good practice" to send
1262   header fields that contain control data first, such as Host on
1263   requests and Date on responses, so that implementations can decide
1264   when not to handle a message as early as possible.  A server &MUST;
1265   wait until the entire header section is received before interpreting
1266   a request message, since later header fields might include conditionals,
1267   authentication credentials, or deliberately misleading duplicate
1268   header fields that would impact request processing.
1271   Multiple header fields with the same field name &MUST-NOT; be
1272   sent in a message unless the entire field value for that
1273   header field is defined as a comma-separated list [i.e., #(values)].
1274   Multiple header fields with the same field name can be combined into
1275   one "field-name: field-value" pair, without changing the semantics of the
1276   message, by appending each subsequent field value to the combined
1277   field value in order, separated by a comma. The order in which
1278   header fields with the same field name are received is therefore
1279   significant to the interpretation of the combined field value;
1280   a proxy &MUST-NOT; change the order of these field values when
1281   forwarding a message.
1284  <t>
1285   <x:h>Note:</x:h> The "Set-Cookie" header field as implemented in
1286   practice can occur multiple times, but does not use the list syntax, and
1287   thus cannot be combined into a single line (<xref target="RFC6265"/>). (See Appendix A.2.3 of <xref target="Kri2001"/>
1288   for details.) Also note that the Set-Cookie2 header field specified in
1289   <xref target="RFC2965"/> does not share this problem.
1290  </t>
1293<section title="Whitespace" anchor="whitespace">
1294<t anchor="rule.LWS">
1295   This specification uses three rules to denote the use of linear
1296   whitespace: OWS (optional whitespace), RWS (required whitespace), and
1297   BWS ("bad" whitespace).
1299<t anchor="rule.OWS">
1300   The OWS rule is used where zero or more linear whitespace octets might
1301   appear. OWS &SHOULD; either not be produced or be produced as a single
1302   SP. Multiple OWS octets that occur within field-content &SHOULD; either
1303   be replaced with a single SP or transformed to all SP octets (each
1304   octet other than SP replaced with SP) before interpreting the field value
1305   or forwarding the message downstream.
1307<t anchor="rule.RWS">
1308   RWS is used when at least one linear whitespace octet is required to
1309   separate field tokens. RWS &SHOULD; be produced as a single SP.
1310   Multiple RWS octets that occur within field-content &SHOULD; either
1311   be replaced with a single SP or transformed to all SP octets before
1312   interpreting the field value or forwarding the message downstream.
1314<t anchor="rule.BWS">
1315   BWS is used where the grammar allows optional whitespace for historical
1316   reasons but senders &SHOULD-NOT; produce it in messages. HTTP/1.1
1317   recipients &MUST; accept such bad optional whitespace and remove it before
1318   interpreting the field value or forwarding the message downstream.
1320<t anchor="rule.whitespace">
1321  <x:anchor-alias value="BWS"/>
1322  <x:anchor-alias value="OWS"/>
1323  <x:anchor-alias value="RWS"/>
1325<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"/>
1326  <x:ref>OWS</x:ref>            = *( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1327                 ; "optional" whitespace
1328  <x:ref>RWS</x:ref>            = 1*( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1329                 ; "required" whitespace
1330  <x:ref>BWS</x:ref>            = <x:ref>OWS</x:ref>
1331                 ; "bad" whitespace
1335<section title="Field Parsing" anchor="field.parsing">
1337   No whitespace is allowed between the header field-name and colon.
1338   In the past, differences in the handling of such whitespace have led to
1339   security vulnerabilities in request routing and response handling.
1340   Any received request message that contains whitespace between a header
1341   field-name and colon &MUST; be rejected with a response code of 400
1342   (Bad Request).  A proxy &MUST; remove any such whitespace from a response
1343   message before forwarding the message downstream.
1346   A field value &MAY; be preceded by optional whitespace (OWS); a single SP is
1347   preferred. The field value does not include any leading or trailing white
1348   space: OWS occurring before the first non-whitespace octet of the
1349   field value or after the last non-whitespace octet of the field value
1350   is ignored and &SHOULD; be removed before further processing (as this does
1351   not change the meaning of the header field).
1354   Historically, HTTP header field values could be extended over multiple
1355   lines by preceding each extra line with at least one space or horizontal
1356   tab (obs-fold). This specification deprecates such line
1357   folding except within the message/http media type
1358   (<xref target=""/>).
1359   HTTP senders &MUST-NOT; produce messages that include line folding
1360   (i.e., that contain any field-value that matches the obs-fold rule) unless
1361   the message is intended for packaging within the message/http media type.
1362   HTTP recipients &SHOULD; accept line folding and replace any embedded
1363   obs-fold whitespace with either a single SP or a matching number of SP
1364   octets (to avoid buffer copying) prior to interpreting the field value or
1365   forwarding the message downstream.
1368   Historically, HTTP has allowed field content with text in the ISO-8859-1
1369   <xref target="ISO-8859-1"/> character encoding and supported other
1370   character sets only through use of <xref target="RFC2047"/> encoding.
1371   In practice, most HTTP header field values use only a subset of the
1372   US-ASCII character encoding <xref target="USASCII"/>. Newly defined
1373   header fields &SHOULD; limit their field values to US-ASCII octets.
1374   Recipients &SHOULD; treat other (obs-text) octets in field content as
1375   opaque data.
1379<section title="Field Length" anchor="field.length">
1381   HTTP does not place a pre-defined limit on the length of header fields,
1382   either in isolation or as a set. A server &MUST; be prepared to receive
1383   request header fields of unbounded length and respond with a 4xx status
1384   code if the received header field(s) would be longer than the server wishes
1385   to handle.
1388   A client that receives response headers that are longer than it wishes to
1389   handle can only treat it as a server error.
1392   Various ad-hoc limitations on header length are found in practice. It is
1393   &RECOMMENDED; that all HTTP senders and recipients support messages whose
1394   combined header fields have 4000 or more octets.
1398<section title="Field value components" anchor="field.components">
1399<t anchor="rule.token.separators">
1400  <x:anchor-alias value="tchar"/>
1401  <x:anchor-alias value="token"/>
1402  <x:anchor-alias value="special"/>
1403  <x:anchor-alias value="word"/>
1404   Many HTTP/1.1 header field values consist of words (token or quoted-string)
1405   separated by whitespace or special characters. These special characters
1406   &MUST; be in a quoted string to be used within a parameter value (as defined
1407   in <xref target="transfer.codings"/>).
1409<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"/>
1410  <x:ref>word</x:ref>           = <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref>
1412  <x:ref>token</x:ref>          = 1*<x:ref>tchar</x:ref>
1414  IMPORTANT: when editing "tchar" make sure that "special" is updated accordingly!!!
1415 -->
1416  <x:ref>tchar</x:ref>          = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*"
1417                 / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
1418                 / <x:ref>DIGIT</x:ref> / <x:ref>ALPHA</x:ref>
1419                 ; any <x:ref>VCHAR</x:ref>, except <x:ref>special</x:ref>
1421  <x:ref>special</x:ref>        = "(" / ")" / "&lt;" / ">" / "@" / ","
1422                 / ";" / ":" / "\" / DQUOTE / "/" / "["
1423                 / "]" / "?" / "=" / "{" / "}"
1425<t anchor="rule.quoted-string">
1426  <x:anchor-alias value="quoted-string"/>
1427  <x:anchor-alias value="qdtext"/>
1428  <x:anchor-alias value="obs-text"/>
1429   A string of text is parsed as a single word if it is quoted using
1430   double-quote marks.
1432<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"/>
1433  <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>
1434  <x:ref>qdtext</x:ref>         = <x:ref>OWS</x:ref> / %x21 / %x23-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1435  <x:ref>obs-text</x:ref>       = %x80-FF
1437<t anchor="rule.quoted-pair">
1438  <x:anchor-alias value="quoted-pair"/>
1439   The backslash octet ("\") can be used as a single-octet
1440   quoting mechanism within quoted-string constructs:
1442<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-pair"/>
1443  <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> )
1446   Recipients that process the value of the quoted-string &MUST; handle a
1447   quoted-pair as if it were replaced by the octet following the backslash.
1450   Senders &SHOULD-NOT; escape octets in quoted-strings that do not require
1451   escaping (i.e., other than DQUOTE and the backslash octet).
1453<t anchor="rule.comment">
1454  <x:anchor-alias value="comment"/>
1455  <x:anchor-alias value="ctext"/>
1456   Comments can be included in some HTTP header fields by surrounding
1457   the comment text with parentheses. Comments are only allowed in
1458   fields containing "comment" as part of their field value definition.
1460<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="comment"/><iref primary="true" item="Grammar" subitem="ctext"/>
1461  <x:ref>comment</x:ref>        = "(" *( <x:ref>ctext</x:ref> / <x:ref>quoted-cpair</x:ref> / <x:ref>comment</x:ref> ) ")"
1462  <x:ref>ctext</x:ref>          = <x:ref>OWS</x:ref> / %x21-27 / %x2A-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1464<t anchor="rule.quoted-cpair">
1465  <x:anchor-alias value="quoted-cpair"/>
1466   The backslash octet ("\") can be used as a single-octet
1467   quoting mechanism within comment constructs:
1469<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-cpair"/>
1470  <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> )
1473   Senders &SHOULD-NOT; escape octets in comments that do not require escaping
1474   (i.e., other than the backslash octet "\" and the parentheses "(" and ")").
1478<section title="ABNF list extension: #rule" anchor="abnf.extension">
1480  A #rule extension to the ABNF rules of <xref target="RFC5234"/> is used to
1481  improve readability in the definitions of some header field values.
1484  A construct "#" is defined, similar to "*", for defining comma-delimited
1485  lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating
1486  at least &lt;n&gt; and at most &lt;m&gt; elements, each separated by a single
1487  comma (",") and optional whitespace (OWS).   
1490  Thus,
1491</preamble><artwork type="example">
1492  1#element =&gt; element *( OWS "," OWS element )
1495  and:
1496</preamble><artwork type="example">
1497  #element =&gt; [ 1#element ]
1500  and for n &gt;= 1 and m &gt; 1:
1501</preamble><artwork type="example">
1502  &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
1505  For compatibility with legacy list rules, recipients &SHOULD; accept empty
1506  list elements. In other words, consumers would follow the list productions:
1508<figure><artwork type="example">
1509  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
1511  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
1514  Note that empty elements do not contribute to the count of elements present,
1515  though.
1518  For example, given these ABNF productions:
1520<figure><artwork type="example">
1521  example-list      = 1#example-list-elmt
1522  example-list-elmt = token ; see <xref target="field.components"/>
1525  Then these are valid values for example-list (not including the double
1526  quotes, which are present for delimitation only):
1528<figure><artwork type="example">
1529  "foo,bar"
1530  "foo ,bar,"
1531  "foo , ,bar,charlie   "
1534  But these values would be invalid, as at least one non-empty element is
1535  required:
1537<figure><artwork type="example">
1538  ""
1539  ","
1540  ",   ,"
1543  <xref target="collected.abnf"/> shows the collected ABNF, with the list rules
1544  expanded as explained above.
1549<section title="Message Body" anchor="message.body">
1550  <x:anchor-alias value="message-body"/>
1552   The message body (if any) of an HTTP message is used to carry the
1553   payload body of that request or response.  The message body is
1554   identical to the payload body unless a transfer coding has been
1555   applied, as described in <xref target="header.transfer-encoding"/>.
1557<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-body"/>
1558  <x:ref>message-body</x:ref> = *OCTET
1561   The rules for when a message body is allowed in a message differ for
1562   requests and responses.
1565   The presence of a message body in a request is signaled by a
1566   a Content-Length or Transfer-Encoding header field.
1567   Request message framing is independent of method semantics,
1568   even if the method does not define any use for a message body.
1571   The presence of a message body in a response depends on both
1572   the request method to which it is responding and the response
1573   status code (<xref target="status.code"/>).
1574   Responses to the HEAD request method never include a message body
1575   because the associated response header fields (e.g., Transfer-Encoding,
1576   Content-Length, etc.) only indicate what their values would have been
1577   if the request method had been GET.
1578   Successful (2xx) responses to CONNECT switch to tunnel mode instead of
1579   having a message body.
1580   All 1xx (Informational), 204 (No Content), and 304 (Not Modified)
1581   responses &MUST-NOT; include a message body.
1582   All other responses do include a message body, although the body
1583   &MAY; be of zero length.
1586<section title="Transfer-Encoding" anchor="header.transfer-encoding">
1587  <iref primary="true" item="Transfer-Encoding header field" x:for-anchor=""/>
1588  <iref primary="true" item="Header Fields" subitem="Transfer-Encoding" x:for-anchor=""/>
1589  <x:anchor-alias value="Transfer-Encoding"/>
1591   When one or more transfer codings are applied to a payload body in order
1592   to form the message body, a Transfer-Encoding header field &MUST; be sent
1593   in the message and &MUST; contain the list of corresponding
1594   transfer-coding names in the same order that they were applied.
1595   Transfer codings are defined in <xref target="transfer.codings"/>.
1597<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Transfer-Encoding"/>
1598  <x:ref>Transfer-Encoding</x:ref> = 1#<x:ref>transfer-coding</x:ref>
1601   Transfer-Encoding is analogous to the Content-Transfer-Encoding field of
1602   MIME, which was designed to enable safe transport of binary data over a
1603   7-bit transport service (<xref target="RFC2045" x:fmt="," x:sec="6"/>).
1604   However, safe transport has a different focus for an 8bit-clean transfer
1605   protocol. In HTTP's case, Transfer-Encoding is primarily intended to
1606   accurately delimit a dynamically generated payload and to distinguish
1607   payload encodings that are only applied for transport efficiency or
1608   security from those that are characteristics of the target resource.
1611   The "chunked" transfer-coding (<xref target="chunked.encoding"/>)
1612   &MUST; be implemented by all HTTP/1.1 recipients because it plays a
1613   crucial role in delimiting messages when the payload body size is not
1614   known in advance.
1615   When the "chunked" transfer-coding is used, it &MUST; be the last
1616   transfer-coding applied to form the message body and &MUST-NOT;
1617   be applied more than once in a message body.
1618   If any transfer-coding is applied to a request payload body,
1619   the final transfer-coding applied &MUST; be "chunked".
1620   If any transfer-coding is applied to a response payload body, then either
1621   the final transfer-coding applied &MUST; be "chunked" or
1622   the message &MUST; be terminated by closing the connection.
1625   For example,
1626</preamble><artwork type="example">
1627  Transfer-Encoding: gzip, chunked
1629   indicates that the payload body has been compressed using the gzip
1630   coding and then chunked using the chunked coding while forming the
1631   message body.
1634   If more than one Transfer-Encoding header field is present in a message,
1635   the multiple field-values &MUST; be combined into one field-value,
1636   according to the algorithm defined in <xref target="header.fields"/>,
1637   before determining the message body length.
1640   Unlike Content-Encoding (&content-codings;), Transfer-Encoding is a
1641   property of the message, not of the payload, and thus &MAY; be added or
1642   removed by any implementation along the request/response chain.
1643   Additional information about the encoding parameters &MAY; be provided
1644   by other header fields not defined by this specification.
1647   Transfer-Encoding &MAY; be sent in a response to a HEAD request or in a
1648   304 response to a GET request, neither of which includes a message body,
1649   to indicate that the origin server would have applied a transfer coding
1650   to the message body if the request had been an unconditional GET.
1651   This indication is not required, however, because any recipient on
1652   the response chain (including the origin server) can remove transfer
1653   codings when they are not needed.
1656   Transfer-Encoding was added in HTTP/1.1.  It is generally assumed that
1657   implementations advertising only HTTP/1.0 support will not understand
1658   how to process a transfer-encoded payload.
1659   A client &MUST-NOT; send a request containing Transfer-Encoding unless it
1660   knows the server will handle HTTP/1.1 (or later) requests; such knowledge
1661   might be in the form of specific user configuration or by remembering the
1662   version of a prior received response.
1663   A server &MUST-NOT; send a response containing Transfer-Encoding unless
1664   the corresponding request indicates HTTP/1.1 (or later).
1667   A server that receives a request message with a transfer-coding it does
1668   not understand &SHOULD; respond with 501 (Not Implemented) and then
1669   close the connection.
1673<section title="Content-Length" anchor="header.content-length">
1674  <iref primary="true" item="Content-Length header field" x:for-anchor=""/>
1675  <iref primary="true" item="Header Fields" subitem="Content-Length" x:for-anchor=""/>
1676  <x:anchor-alias value="Content-Length"/>
1678   When a message does not have a Transfer-Encoding header field and the
1679   payload body length can be determined prior to being transferred, a
1680   Content-Length header field &SHOULD; be sent to indicate the length of the
1681   payload body that is either present as the message body, for requests
1682   and non-HEAD responses other than 304, or would have been present had
1683   the request been an unconditional GET.  The length is expressed as a
1684   decimal number of octets.
1686<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/>
1687  <x:ref>Content-Length</x:ref> = 1*<x:ref>DIGIT</x:ref>
1690   An example is
1692<figure><artwork type="example">
1693  Content-Length: 3495
1696   In the case of a response to a HEAD request, Content-Length indicates
1697   the size of the payload body (without any potential transfer-coding)
1698   that would have been sent had the request been a GET.
1699   In the case of a 304 (Not Modified) response to a GET request,
1700   Content-Length indicates the size of the payload body (without
1701   any potential transfer-coding) that would have been sent in a 200 (OK)
1702   response.
1705   HTTP's use of Content-Length is significantly different from how it is
1706   used in MIME, where it is an optional field used only within the
1707   "message/external-body" media-type.
1710   Any Content-Length field value greater than or equal to zero is valid.
1711   Since there is no predefined limit to the length of an HTTP payload,
1712   recipients &SHOULD; anticipate potentially large decimal numerals and
1713   prevent parsing errors due to integer conversion overflows
1714   (<xref target="attack.protocol.element.size.overflows"/>).
1717   If a message is received that has multiple Content-Length header fields
1718   (<xref target="header.content-length"/>) with field-values consisting
1719   of the same decimal value, or a single Content-Length header field with
1720   a field value containing a list of identical decimal values (e.g.,
1721   "Content-Length: 42, 42"), indicating that duplicate Content-Length
1722   header fields have been generated or combined by an upstream message
1723   processor, then the recipient &MUST; either reject the message as invalid
1724   or replace the duplicated field-values with a single valid Content-Length
1725   field containing that decimal value prior to determining the message body
1726   length.
1730<section title="Message Body Length" anchor="message.body.length">
1732   The length of a message body is determined by one of the following
1733   (in order of precedence):
1736  <list style="numbers">
1737    <x:lt><t>
1738     Any response to a HEAD request and any response with a status
1739     code of 100-199, 204, or 304 is always terminated by the first
1740     empty line after the header fields, regardless of the header
1741     fields present in the message, and thus cannot contain a message body.
1742    </t></x:lt>
1743    <x:lt><t>
1744     Any successful (2xx) response to a CONNECT request implies that the
1745     connection will become a tunnel immediately after the empty line that
1746     concludes the header fields.  A client &MUST; ignore any Content-Length
1747     or Transfer-Encoding header fields received in such a message.
1748    </t></x:lt>
1749    <x:lt><t>
1750     If a Transfer-Encoding header field is present
1751     and the "chunked" transfer-coding (<xref target="chunked.encoding"/>)
1752     is the final encoding, the message body length is determined by reading
1753     and decoding the chunked data until the transfer-coding indicates the
1754     data is complete.
1755    </t>
1756    <t>
1757     If a Transfer-Encoding header field is present in a response and the
1758     "chunked" transfer-coding is not the final encoding, the message body
1759     length is determined by reading the connection until it is closed by
1760     the server.
1761     If a Transfer-Encoding header field is present in a request and the
1762     "chunked" transfer-coding is not the final encoding, the message body
1763     length cannot be determined reliably; the server &MUST; respond with
1764     the 400 (Bad Request) status code and then close the connection.
1765    </t>
1766    <t>
1767     If a message is received with both a Transfer-Encoding header field
1768     and a Content-Length header field, the Transfer-Encoding overrides
1769     the Content-Length.
1770     Such a message might indicate an attempt to perform request or response
1771     smuggling (bypass of security-related checks on message routing or content)
1772     and thus ought to be handled as an error.  The provided Content-Length &MUST;
1773     be removed, prior to forwarding the message downstream, or replaced with
1774     the real message body length after the transfer-coding is decoded.
1775    </t></x:lt>
1776    <x:lt><t>
1777     If a message is received without Transfer-Encoding and with either
1778     multiple Content-Length header fields having differing field-values or
1779     a single Content-Length header field having an invalid value, then the
1780     message framing is invalid and &MUST; be treated as an error to
1781     prevent request or response smuggling.
1782     If this is a request message, the server &MUST; respond with
1783     a 400 (Bad Request) status code and then close the connection.
1784     If this is a response message received by a proxy, the proxy
1785     &MUST; discard the received response, send a 502 (Bad Gateway)
1786     status code as its downstream response, and then close the connection.
1787     If this is a response message received by a user-agent, it &MUST; be
1788     treated as an error by discarding the message and closing the connection.
1789    </t></x:lt>
1790    <x:lt><t>
1791     If a valid Content-Length header field
1792     is present without Transfer-Encoding, its decimal value defines the
1793     message body length in octets.  If the actual number of octets sent in
1794     the message is less than the indicated Content-Length, the recipient
1795     &MUST; consider the message to be incomplete and treat the connection
1796     as no longer usable.
1797     If the actual number of octets sent in the message is more than the indicated
1798     Content-Length, the recipient &MUST; only process the message body up to the
1799     field value's number of octets; the remainder of the message &MUST; either
1800     be discarded or treated as the next message in a pipeline.  For the sake of
1801     robustness, a user-agent &MAY; attempt to detect and correct such an error
1802     in message framing if it is parsing the response to the last request on
1803     a connection and the connection has been closed by the server.
1804    </t></x:lt>
1805    <x:lt><t>
1806     If this is a request message and none of the above are true, then the
1807     message body length is zero (no message body is present).
1808    </t></x:lt>
1809    <x:lt><t>
1810     Otherwise, this is a response message without a declared message body
1811     length, so the message body length is determined by the number of octets
1812     received prior to the server closing the connection.
1813    </t></x:lt>
1814  </list>
1817   Since there is no way to distinguish a successfully completed,
1818   close-delimited message from a partially-received message interrupted
1819   by network failure, implementations &SHOULD; use encoding or
1820   length-delimited messages whenever possible.  The close-delimiting
1821   feature exists primarily for backwards compatibility with HTTP/1.0.
1824   A server &MAY; reject a request that contains a message body but
1825   not a Content-Length by responding with 411 (Length Required).
1828   Unless a transfer-coding other than "chunked" has been applied,
1829   a client that sends a request containing a message body &SHOULD;
1830   use a valid Content-Length header field if the message body length
1831   is known in advance, rather than the "chunked" encoding, since some
1832   existing services respond to "chunked" with a 411 (Length Required)
1833   status code even though they understand the chunked encoding.  This
1834   is typically because such services are implemented via a gateway that
1835   requires a content-length in advance of being called and the server
1836   is unable or unwilling to buffer the entire request before processing.
1839   A client that sends a request containing a message body &MUST; include a
1840   valid Content-Length header field if it does not know the server will
1841   handle HTTP/1.1 (or later) requests; such knowledge can be in the form
1842   of specific user configuration or by remembering the version of a prior
1843   received response.
1848<section anchor="incomplete.messages" title="Handling Incomplete Messages">
1850   Request messages that are prematurely terminated, possibly due to a
1851   cancelled connection or a server-imposed time-out exception, &MUST;
1852   result in closure of the connection; sending an HTTP/1.1 error response
1853   prior to closing the connection is &OPTIONAL;.
1856   Response messages that are prematurely terminated, usually by closure
1857   of the connection prior to receiving the expected number of octets or by
1858   failure to decode a transfer-encoded message body, &MUST; be recorded
1859   as incomplete.  A response that terminates in the middle of the header
1860   block (before the empty line is received) cannot be assumed to convey the
1861   full semantics of the response and &MUST; be treated as an error.
1864   A message body that uses the chunked transfer encoding is
1865   incomplete if the zero-sized chunk that terminates the encoding has not
1866   been received.  A message that uses a valid Content-Length is incomplete
1867   if the size of the message body received (in octets) is less than the
1868   value given by Content-Length.  A response that has neither chunked
1869   transfer encoding nor Content-Length is terminated by closure of the
1870   connection, and thus is considered complete regardless of the number of
1871   message body octets received, provided that the header block was received
1872   intact.
1875   A user agent &MUST-NOT; render an incomplete response message body as if
1876   it were complete (i.e., some indication must be given to the user that an
1877   error occurred).  Cache requirements for incomplete responses are defined
1878   in &cache-incomplete;.
1881   A server &MUST; read the entire request message body or close
1882   the connection after sending its response, since otherwise the
1883   remaining data on a persistent connection would be misinterpreted
1884   as the next request.  Likewise,
1885   a client &MUST; read the entire response message body if it intends
1886   to reuse the same connection for a subsequent request.  Pipelining
1887   multiple requests on a connection is described in <xref target="pipelining"/>.
1891<section title="Message Parsing Robustness" anchor="message.robustness">
1893   Older HTTP/1.0 client implementations might send an extra CRLF
1894   after a POST request as a lame workaround for some early server
1895   applications that failed to read message body content that was
1896   not terminated by a line-ending. An HTTP/1.1 client &MUST-NOT;
1897   preface or follow a request with an extra CRLF.  If terminating
1898   the request message body with a line-ending is desired, then the
1899   client &MUST; include the terminating CRLF octets as part of the
1900   message body length.
1903   In the interest of robustness, servers &SHOULD; ignore at least one
1904   empty line received where a request-line is expected. In other words, if
1905   the server is reading the protocol stream at the beginning of a
1906   message and receives a CRLF first, it &SHOULD; ignore the CRLF.
1907   Likewise, although the line terminator for the start-line and header
1908   fields is the sequence CRLF, we recommend that recipients recognize a
1909   single LF as a line terminator and ignore any CR.
1912   When a server listening only for HTTP request messages, or processing
1913   what appears from the start-line to be an HTTP request message,
1914   receives a sequence of octets that does not match the HTTP-message
1915   grammar aside from the robustness exceptions listed above, the
1916   server &MUST; respond with an HTTP/1.1 400 (Bad Request) response. 
1921<section title="Message Routing" anchor="message.routing">
1923   In most cases, the user agent is provided a URI reference
1924   from which it determines an absolute URI for identifying the target
1925   resource.  When a request to the resource is initiated, all or part
1926   of that URI is used to construct the HTTP request-target.
1929<section title="Types of Request Target" anchor="request-target-types">
1931   The proper format choice of the four options available to request-target
1932   depends on the method being requested and if the request is being made to
1933   a proxy.
1935<t anchor="origin-form"><iref item="origin form (of request-target)"/>
1936   The most common form of request-target is that used when making
1937   a request to an origin server ("origin form") to access a resource
1938   identified by an "http" (<xref target="http.uri"/>) or
1939   "https" (<xref target="https.uri"/>) URI.
1940   In this case, the absolute path and query components of the URI
1941   &MUST; be transmitted as the request-target and the authority component
1942   (excluding any userinfo) &MUST; be transmitted in a Host header field.
1943   For example, a client wishing to retrieve a representation of the resource
1944   identified as
1946<figure><artwork x:indent-with="  ">
1950   directly from the origin server would open (or reuse) a TCP connection
1951   to port 80 of the host "" and send the lines:
1953<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
1954GET /where?q=now HTTP/1.1
1958   followed by the remainder of the request. Note that the origin form
1959   of request-target always starts with an absolute path. If the target
1960   resource's URI path is empty, then an absolute path of "/" &MUST; be
1961   provided in the request-target.
1964   If the request-target is percent-encoded
1965   (<xref target="RFC3986" x:fmt="," x:sec="2.1"/>), the origin server
1966   &MUST; decode the request-target in order to
1967   properly interpret the request. Servers &SHOULD; respond to invalid
1968   request-targets with an appropriate status code.
1970<t anchor="absolute-URI-form"><iref item="absolute-URI form (of request-target)"/>
1971   The "absolute-URI" form of request-target is &REQUIRED; when the request
1972   is being made to a proxy.  The proxy is requested to either forward the
1973   request or service it from a valid cache, and then return the response.
1974   Note that the proxy &MAY; forward the request on to another proxy or
1975   directly to the server specified by the absolute-URI.
1976   In order to avoid request loops, a proxy that forwards requests to other
1977   proxies &MUST; be able to recognize and exclude all of its own server
1978   names, including any aliases, local variations, or literal IP addresses.
1979   An example request-line would be:
1981<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
1982GET HTTP/1.1
1985   To allow for transition to absolute-URIs in all requests in future
1986   versions of HTTP, all HTTP/1.1 servers &MUST; accept the absolute-URI
1987   form in requests, even though HTTP/1.1 clients will only generate
1988   them in requests to proxies.
1991   If a proxy receives a host name that is not a fully qualified domain
1992   name, it &MAY; add its domain to the host name it received. If a proxy
1993   receives a fully qualified domain name, the proxy &MUST-NOT; change
1994   the host name.
1996<t anchor="authority-form"><iref item="authority form (of request-target)"/>
1997   The "authority form" of request-target, which &MUST-NOT; be used
1998   with any request method other than CONNECT, is used to establish a
1999   tunnel through one or more proxies (&CONNECT;).  For example,
2001<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2004<t anchor="asterix-form"><iref item="asterisk form (of request-target)"/>
2005   The asterisk ("*") form of request-target, which &MUST-NOT; be used
2006   with any request method other than OPTIONS, means that the request
2007   applies to the server as a whole (the listening process) rather than
2008   to a specific named resource at that server.  For example,
2010<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2011OPTIONS * HTTP/1.1
2014   If a proxy receives an OPTIONS request with an absolute-URI form of
2015   request-target in which the URI has an empty path and no query component,
2016   then the last proxy on the request chain &MUST; use a request-target
2017   of "*" when it forwards the request to the indicated origin server.
2020   For example, the request
2021</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2025  would be forwarded by the final proxy as
2026</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2027OPTIONS * HTTP/1.1
2031   after connecting to port 8001 of host "".
2035   A non-transforming proxy &MUST-NOT; rewrite the "path-absolute" and "query"
2036   parts of the received request-target when forwarding it to the next inbound
2037   server, except as noted above to replace a null path-absolute with "/" or
2038   "*".
2042<section title="The Resource Identified by a Request" anchor="">
2044   The exact resource identified by an Internet request is determined by
2045   examining both the request-target and the Host header field.
2048   An origin server that does not allow resources to differ by the
2049   requested host &MAY; ignore the Host header field value when
2050   determining the resource identified by an HTTP/1.1 request. (But see
2051   <xref target=""/>
2052   for other requirements on Host support in HTTP/1.1.)
2055   An origin server that does differentiate resources based on the host
2056   requested (sometimes referred to as virtual hosts or vanity host
2057   names) &MUST; use the following rules for determining the requested
2058   resource on an HTTP/1.1 request:
2059  <list style="numbers">
2060    <t>If request-target is an absolute-URI, the host is part of the
2061     request-target. Any Host header field value in the request &MUST; be
2062     ignored.</t>
2063    <t>If the request-target is not an absolute-URI, and the request includes
2064     a Host header field, the host is determined by the Host header
2065     field value.</t>
2066    <t>If the host as determined by rule 1 or 2 is not a valid host on
2067     the server, the response &MUST; be a 400 (Bad Request) error message.</t>
2068  </list>
2071   Recipients of an HTTP/1.0 request that lacks a Host header field &MAY;
2072   attempt to use heuristics (e.g., examination of the URI path for
2073   something unique to a particular host) in order to determine what
2074   exact resource is being requested.
2078<section title="Effective Request URI" anchor="effective.request.uri">
2079  <iref primary="true" item="effective request URI"/>
2080  <iref primary="true" item="target resource"/>
2082   HTTP requests often do not carry the absolute URI (<xref target="RFC3986" x:fmt="," x:sec="4.3"/>)
2083   for the target resource; instead, the URI needs to be inferred from the
2084   request-target, Host header field, and connection context. The result of
2085   this process is called the "effective request URI".  The "target resource"
2086   is the resource identified by the effective request URI.
2089   If the request-target is an absolute-URI, then the effective request URI is
2090   the request-target.
2093   If the request-target uses the origin form or the asterisk form,
2094   and the Host header field is present, then the effective request URI is
2095   constructed by concatenating
2098  <list style="symbols">
2099    <t>
2100      the scheme name: "http" if the request was received over an insecure
2101      TCP connection, or "https" when received over a SSL/TLS-secured TCP
2102      connection,
2103    </t>
2104    <t>
2105      the octet sequence "://",
2106    </t>
2107    <t>
2108      the authority component, as specified in the Host header field
2109      (<xref target=""/>), and
2110    </t>
2111    <t>
2112      the request-target obtained from the request-line, unless the
2113      request-target is just the asterisk "*".
2114    </t>
2115  </list>
2118   If the request-target uses the origin form or the asterisk form,
2119   and the Host header field is not present, then the effective request URI is
2120   undefined.
2123   Otherwise, when request-target uses the authority form, the effective
2124   request URI is undefined.
2128   Example 1: the effective request URI for the message
2130<artwork type="example" x:indent-with="  ">
2131GET /pub/WWW/TheProject.html HTTP/1.1
2135  (received over an insecure TCP connection) is "http", plus "://", plus the
2136  authority component "", plus the request-target
2137  "/pub/WWW/TheProject.html", thus
2138  "".
2143   Example 2: the effective request URI for the message
2145<artwork type="example" x:indent-with="  ">
2146OPTIONS * HTTP/1.1
2150  (received over an SSL/TLS secured TCP connection) is "https", plus "://", plus the
2151  authority component "", thus "".
2155   Effective request URIs are compared using the rules described in
2156   <xref target="uri.comparison"/>, except that empty path components &MUST-NOT;
2157   be treated as equivalent to an absolute path of "/".
2161<section title="Associating a Response to a Request" anchor="">
2163   HTTP does not include a request identifier for associating a given
2164   request message with its corresponding one or more response messages.
2165   Hence, it relies on the order of response arrival to correspond exactly
2166   to the order in which requests are made on the same connection.
2167   More than one response message per request only occurs when one or more
2168   informational responses (1xx, see &status-1xx;) precede a final response
2169   to the same request.
2172   A client that uses persistent connections and sends more than one request
2173   per connection &MUST; maintain a list of outstanding requests in the
2174   order sent on that connection and &MUST; associate each received response
2175   message to the highest ordered request that has not yet received a final
2176   (non-1xx) response.
2181<section title="Transfer Codings" anchor="transfer.codings">
2182  <x:anchor-alias value="transfer-coding"/>
2183  <x:anchor-alias value="transfer-extension"/>
2185   Transfer-coding values are used to indicate an encoding
2186   transformation that has been, can be, or might need to be applied to a
2187   payload body in order to ensure "safe transport" through the network.
2188   This differs from a content coding in that the transfer-coding is a
2189   property of the message rather than a property of the representation
2190   that is being transferred.
2192<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-coding"/><iref primary="true" item="Grammar" subitem="transfer-extension"/>
2193  <x:ref>transfer-coding</x:ref>    = "chunked" ; <xref target="chunked.encoding"/>
2194                     / "compress" ; <xref target="compress.coding"/>
2195                     / "deflate" ; <xref target="deflate.coding"/>
2196                     / "gzip" ; <xref target="gzip.coding"/>
2197                     / <x:ref>transfer-extension</x:ref>
2198  <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> )
2200<t anchor="rule.parameter">
2201  <x:anchor-alias value="attribute"/>
2202  <x:anchor-alias value="transfer-parameter"/>
2203  <x:anchor-alias value="value"/>
2204   Parameters are in the form of attribute/value pairs.
2206<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"/>
2207  <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>
2208  <x:ref>attribute</x:ref>          = <x:ref>token</x:ref>
2209  <x:ref>value</x:ref>              = <x:ref>word</x:ref>
2212   All transfer-coding values are case-insensitive. HTTP/1.1 uses
2213   transfer-coding values in the TE header field (<xref target="header.te"/>) and in
2214   the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).
2217<section title="Chunked Transfer Coding" anchor="chunked.encoding">
2218  <iref item="chunked (Coding Format)"/>
2219  <iref item="Coding Format" subitem="chunked"/>
2220  <x:anchor-alias value="chunk"/>
2221  <x:anchor-alias value="chunked-body"/>
2222  <x:anchor-alias value="chunk-data"/>
2223  <x:anchor-alias value="chunk-ext"/>
2224  <x:anchor-alias value="chunk-ext-name"/>
2225  <x:anchor-alias value="chunk-ext-val"/>
2226  <x:anchor-alias value="chunk-size"/>
2227  <x:anchor-alias value="last-chunk"/>
2228  <x:anchor-alias value="trailer-part"/>
2229  <x:anchor-alias value="quoted-str-nf"/>
2230  <x:anchor-alias value="qdtext-nf"/>
2232   The chunked encoding modifies the body of a message in order to
2233   transfer it as a series of chunks, each with its own size indicator,
2234   followed by an &OPTIONAL; trailer containing header fields. This
2235   allows dynamically produced content to be transferred along with the
2236   information necessary for the recipient to verify that it has
2237   received the full message.
2239<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="chunked-body"/><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"/>
2240  <x:ref>chunked-body</x:ref>   = *<x:ref>chunk</x:ref>
2241                   <x:ref>last-chunk</x:ref>
2242                   <x:ref>trailer-part</x:ref>
2243                   <x:ref>CRLF</x:ref>
2245  <x:ref>chunk</x:ref>          = <x:ref>chunk-size</x:ref> [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
2246                   <x:ref>chunk-data</x:ref> <x:ref>CRLF</x:ref>
2247  <x:ref>chunk-size</x:ref>     = 1*<x:ref>HEXDIG</x:ref>
2248  <x:ref>last-chunk</x:ref>     = 1*("0") [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
2250  <x:ref>chunk-ext</x:ref>      = *( ";" <x:ref>chunk-ext-name</x:ref> [ "=" <x:ref>chunk-ext-val</x:ref> ] )
2251  <x:ref>chunk-ext-name</x:ref> = <x:ref>token</x:ref>
2252  <x:ref>chunk-ext-val</x:ref>  = <x:ref>token</x:ref> / <x:ref>quoted-str-nf</x:ref>
2253  <x:ref>chunk-data</x:ref>     = 1*<x:ref>OCTET</x:ref> ; a sequence of chunk-size octets
2254  <x:ref>trailer-part</x:ref>   = *( <x:ref>header-field</x:ref> <x:ref>CRLF</x:ref> )
2256  <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>
2257                 ; like <x:ref>quoted-string</x:ref>, but disallowing line folding
2258  <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>
2261   The chunk-size field is a string of hex digits indicating the size of
2262   the chunk-data in octets. The chunked encoding is ended by any chunk whose size is
2263   zero, followed by the trailer, which is terminated by an empty line.
2266   The trailer allows the sender to include additional HTTP header
2267   fields at the end of the message. The Trailer header field can be
2268   used to indicate which header fields are included in a trailer (see
2269   <xref target="header.trailer"/>).
2272   A server using chunked transfer-coding in a response &MUST-NOT; use the
2273   trailer for any header fields unless at least one of the following is
2274   true:
2275  <list style="numbers">
2276    <t>the request included a TE header field that indicates "trailers" is
2277     acceptable in the transfer-coding of the  response, as described in
2278     <xref target="header.te"/>; or,</t>
2280    <t>the trailer fields consist entirely of optional metadata, and the
2281    recipient could use the message (in a manner acceptable to the server where
2282    the field originated) without receiving it. In other words, the server that
2283    generated the header (often but not always the origin server) is willing to
2284    accept the possibility that the trailer fields might be silently discarded
2285    along the path to the client.</t>
2286  </list>
2289   This requirement prevents an interoperability failure when the
2290   message is being received by an HTTP/1.1 (or later) proxy and
2291   forwarded to an HTTP/1.0 recipient. It avoids a situation where
2292   conformance with the protocol would have necessitated a possibly
2293   infinite buffer on the proxy.
2296   A process for decoding the "chunked" transfer-coding
2297   can be represented in pseudo-code as:
2299<figure><artwork type="code">
2300  length := 0
2301  read chunk-size, chunk-ext (if any) and CRLF
2302  while (chunk-size &gt; 0) {
2303     read chunk-data and CRLF
2304     append chunk-data to decoded-body
2305     length := length + chunk-size
2306     read chunk-size and CRLF
2307  }
2308  read header-field
2309  while (header-field not empty) {
2310     append header-field to existing header fields
2311     read header-field
2312  }
2313  Content-Length := length
2314  Remove "chunked" from Transfer-Encoding
2317   All HTTP/1.1 applications &MUST; be able to receive and decode the
2318   "chunked" transfer-coding and &MUST; ignore chunk-ext extensions
2319   they do not understand.
2322   Use of chunk-ext extensions by senders is deprecated; they &SHOULD-NOT; be
2323   sent and definition of new chunk-extensions is discouraged.
2327<section title="Compression Codings" anchor="compression.codings">
2329   The codings defined below can be used to compress the payload of a
2330   message.
2333   <x:h>Note:</x:h> Use of program names for the identification of encoding formats
2334   is not desirable and is discouraged for future encodings. Their
2335   use here is representative of historical practice, not good
2336   design.
2339   <x:h>Note:</x:h> For compatibility with previous implementations of HTTP,
2340   applications &SHOULD; consider "x-gzip" and "x-compress" to be
2341   equivalent to "gzip" and "compress" respectively.
2344<section title="Compress Coding" anchor="compress.coding">
2345<iref item="compress (Coding Format)"/>
2346<iref item="Coding Format" subitem="compress"/>
2348   The "compress" format is produced by the common UNIX file compression
2349   program "compress". This format is an adaptive Lempel-Ziv-Welch
2350   coding (LZW).
2354<section title="Deflate Coding" anchor="deflate.coding">
2355<iref item="deflate (Coding Format)"/>
2356<iref item="Coding Format" subitem="deflate"/>
2358   The "deflate" format is defined as the "deflate" compression mechanism
2359   (described in <xref target="RFC1951"/>) used inside the "zlib"
2360   data format (<xref target="RFC1950"/>).
2363  <t>
2364    <x:h>Note:</x:h> Some incorrect implementations send the "deflate"
2365    compressed data without the zlib wrapper.
2366   </t>
2370<section title="Gzip Coding" anchor="gzip.coding">
2371<iref item="gzip (Coding Format)"/>
2372<iref item="Coding Format" subitem="gzip"/>
2374   The "gzip" format is produced by the file compression program
2375   "gzip" (GNU zip), as described in <xref target="RFC1952"/>. This format is a
2376   Lempel-Ziv coding (LZ77) with a 32 bit CRC.
2382<section title="Transfer Coding Registry" anchor="transfer.coding.registry">
2384   The HTTP Transfer Coding Registry defines the name space for the transfer
2385   coding names.
2388   Registrations &MUST; include the following fields:
2389   <list style="symbols">
2390     <t>Name</t>
2391     <t>Description</t>
2392     <t>Pointer to specification text</t>
2393   </list>
2396   Names of transfer codings &MUST-NOT; overlap with names of content codings
2397   (&content-codings;), unless the encoding transformation is identical (as it
2398   is the case for the compression codings defined in
2399   <xref target="compression.codings"/>).
2402   Values to be added to this name space require IETF Review (see
2403   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
2404   conform to the purpose of transfer coding defined in this section.
2407   The registry itself is maintained at
2408   <eref target=""/>.
2412<section title="TE" anchor="header.te">
2413  <iref primary="true" item="TE header field" x:for-anchor=""/>
2414  <iref primary="true" item="Header Fields" subitem="TE" x:for-anchor=""/>
2415  <x:anchor-alias value="TE"/>
2416  <x:anchor-alias value="t-codings"/>
2417  <x:anchor-alias value="te-params"/>
2418  <x:anchor-alias value="te-ext"/>
2420   The "TE" header field indicates what extension transfer-codings
2421   the client is willing to accept in the response, and whether or not it is
2422   willing to accept trailer fields in a chunked transfer-coding.
2425   Its value consists of the keyword "trailers" and/or a comma-separated
2426   list of extension transfer-coding names with optional accept
2427   parameters (as described in <xref target="transfer.codings"/>).
2429<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="te-params"/><iref primary="true" item="Grammar" subitem="te-ext"/>
2430  <x:ref>TE</x:ref>        = #<x:ref>t-codings</x:ref>
2431  <x:ref>t-codings</x:ref> = "trailers" / ( <x:ref>transfer-extension</x:ref> [ <x:ref>te-params</x:ref> ] )
2432  <x:ref>te-params</x:ref> = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> *( <x:ref>te-ext</x:ref> )
2433  <x:ref>te-ext</x:ref>    = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>token</x:ref> [ "=" <x:ref>word</x:ref> ]
2436   The presence of the keyword "trailers" indicates that the client is
2437   willing to accept trailer fields in a chunked transfer-coding, as
2438   defined in <xref target="chunked.encoding"/>. This keyword is reserved for use with
2439   transfer-coding values even though it does not itself represent a
2440   transfer-coding.
2443   Examples of its use are:
2445<figure><artwork type="example">
2446  TE: deflate
2447  TE:
2448  TE: trailers, deflate;q=0.5
2451   The TE header field only applies to the immediate connection.
2452   Therefore, the keyword &MUST; be supplied within a Connection header
2453   field (<xref target="header.connection"/>) whenever TE is present in an HTTP/1.1 message.
2456   A server tests whether a transfer-coding is acceptable, according to
2457   a TE field, using these rules:
2458  <list style="numbers">
2459    <x:lt>
2460      <t>The "chunked" transfer-coding is always acceptable. If the
2461         keyword "trailers" is listed, the client indicates that it is
2462         willing to accept trailer fields in the chunked response on
2463         behalf of itself and any downstream clients. The implication is
2464         that, if given, the client is stating that either all
2465         downstream clients are willing to accept trailer fields in the
2466         forwarded response, or that it will attempt to buffer the
2467         response on behalf of downstream recipients.
2468      </t><t>
2469         <x:h>Note:</x:h> HTTP/1.1 does not define any means to limit the size of a
2470         chunked response such that a client can be assured of buffering
2471         the entire response.</t>
2472    </x:lt>
2473    <x:lt>
2474      <t>If the transfer-coding being tested is one of the transfer-codings
2475         listed in the TE field, then it is acceptable unless it
2476         is accompanied by a qvalue of 0. (As defined in <xref target="quality.values"/>, a
2477         qvalue of 0 means "not acceptable".)</t>
2478    </x:lt>
2479    <x:lt>
2480      <t>If multiple transfer-codings are acceptable, then the
2481         acceptable transfer-coding with the highest non-zero qvalue is
2482         preferred.  The "chunked" transfer-coding always has a qvalue
2483         of 1.</t>
2484    </x:lt>
2485  </list>
2488   If the TE field-value is empty or if no TE field is present, the only
2489   acceptable transfer-coding is "chunked". A message with no transfer-coding is
2490   always acceptable.
2493<section title="Quality Values" anchor="quality.values">
2494  <x:anchor-alias value="qvalue"/>
2496   Both transfer codings (TE request header field, <xref target="header.te"/>)
2497   and content negotiation (&content.negotiation;) use short "floating point"
2498   numbers to indicate the relative importance ("weight") of various
2499   negotiable parameters.  A weight is normalized to a real number in
2500   the range 0 through 1, where 0 is the minimum and 1 the maximum
2501   value. If a parameter has a quality value of 0, then content with
2502   this parameter is "not acceptable" for the client. HTTP/1.1
2503   applications &MUST-NOT; generate more than three digits after the
2504   decimal point. User configuration of these values &SHOULD; also be
2505   limited in this fashion.
2507<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="qvalue"/>
2508  <x:ref>qvalue</x:ref>         = ( "0" [ "." 0*3<x:ref>DIGIT</x:ref> ] )
2509                 / ( "1" [ "." 0*3("0") ] )
2512  <t>
2513     <x:h>Note:</x:h> "Quality values" is a misnomer, since these values merely represent
2514     relative degradation in desired quality.
2515  </t>
2520<section title="Trailer" anchor="header.trailer">
2521  <iref primary="true" item="Trailer header field" x:for-anchor=""/>
2522  <iref primary="true" item="Header Fields" subitem="Trailer" x:for-anchor=""/>
2523  <x:anchor-alias value="Trailer"/>
2525   The "Trailer" header field indicates that the given set of
2526   header fields is present in the trailer of a message encoded with
2527   chunked transfer-coding.
2529<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Trailer"/>
2530  <x:ref>Trailer</x:ref> = 1#<x:ref>field-name</x:ref>
2533   An HTTP/1.1 message &SHOULD; include a Trailer header field in a
2534   message using chunked transfer-coding with a non-empty trailer. Doing
2535   so allows the recipient to know which header fields to expect in the
2536   trailer.
2539   If no Trailer header field is present, the trailer &SHOULD-NOT;  include
2540   any header fields. See <xref target="chunked.encoding"/> for restrictions on the use of
2541   trailer fields in a "chunked" transfer-coding.
2544   Message header fields listed in the Trailer header field &MUST-NOT;
2545   include the following header fields:
2546  <list style="symbols">
2547    <t>Transfer-Encoding</t>
2548    <t>Content-Length</t>
2549    <t>Trailer</t>
2550  </list>
2555<section title="Connections" anchor="connections">
2557<section title="Persistent Connections" anchor="persistent.connections">
2559<section title="Purpose" anchor="persistent.purpose">
2561   Prior to persistent connections, a separate TCP connection was
2562   established for each request, increasing the load on HTTP servers
2563   and causing congestion on the Internet. The use of inline images and
2564   other associated data often requires a client to make multiple
2565   requests of the same server in a short amount of time. Analysis of
2566   these performance problems and results from a prototype
2567   implementation are available <xref target="Pad1995"/> <xref target="Spe"/>. Implementation experience and
2568   measurements of actual HTTP/1.1 implementations show good
2569   results <xref target="Nie1997"/>. Alternatives have also been explored, for example,
2570   T/TCP <xref target="Tou1998"/>.
2573   Persistent HTTP connections have a number of advantages:
2574  <list style="symbols">
2575      <t>
2576        By opening and closing fewer TCP connections, CPU time is saved
2577        in routers and hosts (clients, servers, proxies, gateways,
2578        tunnels, or caches), and memory used for TCP protocol control
2579        blocks can be saved in hosts.
2580      </t>
2581      <t>
2582        HTTP requests and responses can be pipelined on a connection.
2583        Pipelining allows a client to make multiple requests without
2584        waiting for each response, allowing a single TCP connection to
2585        be used much more efficiently, with much lower elapsed time.
2586      </t>
2587      <t>
2588        Network congestion is reduced by reducing the number of packets
2589        caused by TCP opens, and by allowing TCP sufficient time to
2590        determine the congestion state of the network.
2591      </t>
2592      <t>
2593        Latency on subsequent requests is reduced since there is no time
2594        spent in TCP's connection opening handshake.
2595      </t>
2596      <t>
2597        HTTP can evolve more gracefully, since errors can be reported
2598        without the penalty of closing the TCP connection. Clients using
2599        future versions of HTTP might optimistically try a new feature,
2600        but if communicating with an older server, retry with old
2601        semantics after an error is reported.
2602      </t>
2603    </list>
2606   HTTP implementations &SHOULD; implement persistent connections.
2610<section title="Overall Operation" anchor="persistent.overall">
2612   A significant difference between HTTP/1.1 and earlier versions of
2613   HTTP is that persistent connections are the default behavior of any
2614   HTTP connection. That is, unless otherwise indicated, the client
2615   &SHOULD; assume that the server will maintain a persistent connection,
2616   even after error responses from the server.
2619   Persistent connections provide a mechanism by which a client and a
2620   server can signal the close of a TCP connection. This signaling takes
2621   place using the Connection header field (<xref target="header.connection"/>). Once a close
2622   has been signaled, the client &MUST-NOT; send any more requests on that
2623   connection.
2626<section title="Negotiation" anchor="persistent.negotiation">
2628   An HTTP/1.1 server &MAY; assume that a HTTP/1.1 client intends to
2629   maintain a persistent connection unless a Connection header field including
2630   the connection-token "close" was sent in the request. If the server
2631   chooses to close the connection immediately after sending the
2632   response, it &SHOULD; send a Connection header field including the
2633   connection-token "close".
2636   An HTTP/1.1 client &MAY; expect a connection to remain open, but would
2637   decide to keep it open based on whether the response from a server
2638   contains a Connection header field with the connection-token close. In case
2639   the client does not want to maintain a connection for more than that
2640   request, it &SHOULD; send a Connection header field including the
2641   connection-token close.
2644   If either the client or the server sends the close token in the
2645   Connection header field, that request becomes the last one for the
2646   connection.
2649   Clients and servers &SHOULD-NOT;  assume that a persistent connection is
2650   maintained for HTTP versions less than 1.1 unless it is explicitly
2651   signaled. See <xref target="compatibility.with.http.1.0.persistent.connections"/> for more information on backward
2652   compatibility with HTTP/1.0 clients.
2655   In order to remain persistent, all messages on the connection &MUST;
2656   have a self-defined message length (i.e., one not defined by closure
2657   of the connection), as described in <xref target="message.body"/>.
2661<section title="Pipelining" anchor="pipelining">
2663   A client that supports persistent connections &MAY; "pipeline" its
2664   requests (i.e., send multiple requests without waiting for each
2665   response). A server &MUST; send its responses to those requests in the
2666   same order that the requests were received.
2669   Clients which assume persistent connections and pipeline immediately
2670   after connection establishment &SHOULD; be prepared to retry their
2671   connection if the first pipelined attempt fails. If a client does
2672   such a retry, it &MUST-NOT; pipeline before it knows the connection is
2673   persistent. Clients &MUST; also be prepared to resend their requests if
2674   the server closes the connection before sending all of the
2675   corresponding responses.
2678   Clients &SHOULD-NOT; pipeline requests using non-idempotent request methods or
2679   non-idempotent sequences of request methods (see &idempotent-methods;). Otherwise, a
2680   premature termination of the transport connection could lead to
2681   indeterminate results. A client wishing to send a non-idempotent
2682   request &SHOULD; wait to send that request until it has received the
2683   response status line for the previous request.
2688<section title="Proxy Servers" anchor="persistent.proxy">
2690   It is especially important that proxies correctly implement the
2691   properties of the Connection header field as specified in <xref target="header.connection"/>.
2694   The proxy server &MUST; signal persistent connections separately with
2695   its clients and the origin servers (or other proxy servers) that it
2696   connects to. Each persistent connection applies to only one transport
2697   link.
2700   A proxy server &MUST-NOT; establish a HTTP/1.1 persistent connection
2701   with an HTTP/1.0 client (but see <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/>
2702   for information and discussion of the problems with the Keep-Alive header field
2703   implemented by many HTTP/1.0 clients).
2706<section title="End-to-end and Hop-by-hop Header Fields" anchor="end-to-end.and.hop-by-hop.header-fields">
2708  <cref anchor="TODO-end-to-end" source="jre">
2709    Restored from <eref target=""/>.
2710    See also <eref target=""/>.
2711  </cref>
2714   For the purpose of defining the behavior of caches and non-caching
2715   proxies, we divide HTTP header fields into two categories:
2716  <list style="symbols">
2717      <t>End-to-end header fields, which are  transmitted to the ultimate
2718        recipient of a request or response. End-to-end header fields in
2719        responses &MUST; be stored as part of a cache entry and &MUST; be
2720        transmitted in any response formed from a cache entry.</t>
2722      <t>Hop-by-hop header fields, which are meaningful only for a single
2723        transport-level connection, and are not stored by caches or
2724        forwarded by proxies.</t>
2725  </list>
2728   The following HTTP/1.1 header fields are hop-by-hop header fields:
2729  <list style="symbols">
2730      <t>Connection</t>
2731      <t>Keep-Alive</t>
2732      <t>Proxy-Authenticate</t>
2733      <t>Proxy-Authorization</t>
2734      <t>TE</t>
2735      <t>Trailer</t>
2736      <t>Transfer-Encoding</t>
2737      <t>Upgrade</t>
2738  </list>
2741   All other header fields defined by HTTP/1.1 are end-to-end header fields.
2744   Other hop-by-hop header fields &MUST; be listed in a Connection header field
2745   (<xref target="header.connection"/>).
2749<section title="Non-modifiable Header Fields" anchor="non-modifiable.header-fields">
2751  <cref anchor="TODO-non-mod-headers" source="jre">
2752    Restored from <eref target=""/>.
2753    See also <eref target=""/>.
2754  </cref>
2757   Some features of HTTP/1.1, such as Digest Authentication, depend on the
2758   value of certain end-to-end header fields. A non-transforming proxy &SHOULD-NOT;
2759   modify an end-to-end header field unless the definition of that header field requires
2760   or specifically allows that.
2763   A non-transforming proxy &MUST-NOT; modify any of the following fields in a
2764   request or response, and it &MUST-NOT; add any of these fields if not
2765   already present:
2766  <list style="symbols">
2767    <t>Allow</t>
2768    <t>Content-Location</t>
2769    <t>Content-MD5</t>
2770    <t>ETag</t>
2771    <t>Last-Modified</t>
2772    <t>Server</t>
2773  </list>
2776   A non-transforming proxy &MUST-NOT; modify any of the following fields in a
2777   response:
2778  <list style="symbols">
2779    <t>Expires</t>
2780  </list>
2783   but it &MAY; add any of these fields if not already present. If an
2784   Expires header field is added, it &MUST; be given a field-value identical to
2785   that of the Date header field in that response.
2788   A proxy &MUST-NOT; modify or add any of the following fields in a
2789   message that contains the no-transform cache-control directive, or in
2790   any request:
2791  <list style="symbols">
2792    <t>Content-Encoding</t>
2793    <t>Content-Range</t>
2794    <t>Content-Type</t>
2795  </list>
2798   A transforming proxy &MAY; modify or add these fields to a message
2799   that does not include no-transform, but if it does so, it &MUST; add a
2800   Warning 214 (Transformation applied) if one does not already appear
2801   in the message (see &header-warning;).
2804  <t>
2805    <x:h>Warning:</x:h> Unnecessary modification of end-to-end header fields might
2806    cause authentication failures if stronger authentication
2807    mechanisms are introduced in later versions of HTTP. Such
2808    authentication mechanisms &MAY; rely on the values of header fields
2809    not listed here.
2810  </t>
2813   A non-transforming proxy &MUST; preserve the message payload (&payload;),
2814   though it &MAY; change the message body through application or removal
2815   of a transfer-coding (<xref target="transfer.codings"/>).
2821<section title="Practical Considerations" anchor="persistent.practical">
2823   Servers will usually have some time-out value beyond which they will
2824   no longer maintain an inactive connection. Proxy servers might make
2825   this a higher value since it is likely that the client will be making
2826   more connections through the same server. The use of persistent
2827   connections places no requirements on the length (or existence) of
2828   this time-out for either the client or the server.
2831   When a client or server wishes to time-out it &SHOULD; issue a graceful
2832   close on the transport connection. Clients and servers &SHOULD; both
2833   constantly watch for the other side of the transport close, and
2834   respond to it as appropriate. If a client or server does not detect
2835   the other side's close promptly it could cause unnecessary resource
2836   drain on the network.
2839   A client, server, or proxy &MAY; close the transport connection at any
2840   time. For example, a client might have started to send a new request
2841   at the same time that the server has decided to close the "idle"
2842   connection. From the server's point of view, the connection is being
2843   closed while it was idle, but from the client's point of view, a
2844   request is in progress.
2847   Clients (including proxies) &SHOULD; limit the number of simultaneous
2848   connections that they maintain to a given server (including proxies).
2851   Previous revisions of HTTP gave a specific number of connections as a
2852   ceiling, but this was found to be impractical for many applications. As a
2853   result, this specification does not mandate a particular maximum number of
2854   connections, but instead encourages clients to be conservative when opening
2855   multiple connections.
2858   In particular, while using multiple connections avoids the "head-of-line
2859   blocking" problem (whereby a request that takes significant server-side
2860   processing and/or has a large payload can block subsequent requests on the
2861   same connection), each connection used consumes server resources (sometimes
2862   significantly), and furthermore using multiple connections can cause
2863   undesirable side effects in congested networks.
2866   Note that servers might reject traffic that they deem abusive, including an
2867   excessive number of connections from a client.
2871<section title="Retrying Requests" anchor="persistent.retrying.requests">
2873   Senders can close the transport connection at any time. Therefore,
2874   clients, servers, and proxies &MUST; be able to recover
2875   from asynchronous close events. Client software &MAY; reopen the
2876   transport connection and retransmit the aborted sequence of requests
2877   without user interaction so long as the request sequence is
2878   idempotent (see &idempotent-methods;). Non-idempotent request methods or sequences
2879   &MUST-NOT; be automatically retried, although user agents &MAY; offer a
2880   human operator the choice of retrying the request(s). Confirmation by
2881   user-agent software with semantic understanding of the application
2882   &MAY; substitute for user confirmation. The automatic retry &SHOULD-NOT;
2883   be repeated if the second sequence of requests fails.
2889<section title="Message Transmission Requirements" anchor="message.transmission.requirements">
2891<section title="Persistent Connections and Flow Control" anchor="persistent.flow">
2893   HTTP/1.1 servers &SHOULD; maintain persistent connections and use TCP's
2894   flow control mechanisms to resolve temporary overloads, rather than
2895   terminating connections with the expectation that clients will retry.
2896   The latter technique can exacerbate network congestion.
2900<section title="Monitoring Connections for Error Status Messages" anchor="persistent.monitor">
2902   An HTTP/1.1 (or later) client sending a message body &SHOULD; monitor
2903   the network connection for an error status code while it is transmitting
2904   the request. If the client sees an error status code, it &SHOULD;
2905   immediately cease transmitting the body. If the body is being sent
2906   using a "chunked" encoding (<xref target="transfer.codings"/>), a zero length chunk and
2907   empty trailer &MAY; be used to prematurely mark the end of the message.
2908   If the body was preceded by a Content-Length header field, the client &MUST;
2909   close the connection.
2913<section title="Use of the 100 (Continue) Status" anchor="use.of.the.100.status">
2915   The purpose of the 100 (Continue) status code (see &status-100;) is to
2916   allow a client that is sending a request message with a request body
2917   to determine if the origin server is willing to accept the request
2918   (based on the request header fields) before the client sends the request
2919   body. In some cases, it might either be inappropriate or highly
2920   inefficient for the client to send the body if the server will reject
2921   the message without looking at the body.
2924   Requirements for HTTP/1.1 clients:
2925  <list style="symbols">
2926    <t>
2927        If a client will wait for a 100 (Continue) response before
2928        sending the request body, it &MUST; send an Expect header
2929        field (&header-expect;) with the "100-continue" expectation.
2930    </t>
2931    <t>
2932        A client &MUST-NOT; send an Expect header field (&header-expect;)
2933        with the "100-continue" expectation if it does not intend
2934        to send a request body.
2935    </t>
2936  </list>
2939   Because of the presence of older implementations, the protocol allows
2940   ambiguous situations in which a client might send "Expect: 100-continue"
2941   without receiving either a 417 (Expectation Failed)
2942   or a 100 (Continue) status code. Therefore, when a client sends this
2943   header field to an origin server (possibly via a proxy) from which it
2944   has never seen a 100 (Continue) status code, the client &SHOULD-NOT; 
2945   wait for an indefinite period before sending the request body.
2948   Requirements for HTTP/1.1 origin servers:
2949  <list style="symbols">
2950    <t> Upon receiving a request which includes an Expect header
2951        field with the "100-continue" expectation, an origin server &MUST;
2952        either respond with 100 (Continue) status code and continue to read
2953        from the input stream, or respond with a final status code. The
2954        origin server &MUST-NOT; wait for the request body before sending
2955        the 100 (Continue) response. If it responds with a final status
2956        code, it &MAY; close the transport connection or it &MAY; continue
2957        to read and discard the rest of the request.  It &MUST-NOT;
2958        perform the request method if it returns a final status code.
2959    </t>
2960    <t> An origin server &SHOULD-NOT;  send a 100 (Continue) response if
2961        the request message does not include an Expect header
2962        field with the "100-continue" expectation, and &MUST-NOT; send a
2963        100 (Continue) response if such a request comes from an HTTP/1.0
2964        (or earlier) client. There is an exception to this rule: for
2965        compatibility with <xref target="RFC2068"/>, a server &MAY; send a 100 (Continue)
2966        status code in response to an HTTP/1.1 PUT or POST request that does
2967        not include an Expect header field with the "100-continue"
2968        expectation. This exception, the purpose of which is
2969        to minimize any client processing delays associated with an
2970        undeclared wait for 100 (Continue) status code, applies only to
2971        HTTP/1.1 requests, and not to requests with any other HTTP-version
2972        value.
2973    </t>
2974    <t> An origin server &MAY; omit a 100 (Continue) response if it has
2975        already received some or all of the request body for the
2976        corresponding request.
2977    </t>
2978    <t> An origin server that sends a 100 (Continue) response &MUST;
2979        ultimately send a final status code, once the request body is
2980        received and processed, unless it terminates the transport
2981        connection prematurely.
2982    </t>
2983    <t> If an origin server receives a request that does not include an
2984        Expect header field with the "100-continue" expectation,
2985        the request includes a request body, and the server responds
2986        with a final status code before reading the entire request body
2987        from the transport connection, then the server &SHOULD-NOT;  close
2988        the transport connection until it has read the entire request,
2989        or until the client closes the connection. Otherwise, the client
2990        might not reliably receive the response message. However, this
2991        requirement ought not be construed as preventing a server from
2992        defending itself against denial-of-service attacks, or from
2993        badly broken client implementations.
2994      </t>
2995    </list>
2998   Requirements for HTTP/1.1 proxies:
2999  <list style="symbols">
3000    <t> If a proxy receives a request that includes an Expect header
3001        field with the "100-continue" expectation, and the proxy
3002        either knows that the next-hop server complies with HTTP/1.1 or
3003        higher, or does not know the HTTP version of the next-hop
3004        server, it &MUST; forward the request, including the Expect header
3005        field.
3006    </t>
3007    <t> If the proxy knows that the version of the next-hop server is
3008        HTTP/1.0 or lower, it &MUST-NOT; forward the request, and it &MUST;
3009        respond with a 417 (Expectation Failed) status code.
3010    </t>
3011    <t> Proxies &SHOULD; maintain a record of the HTTP version
3012        numbers received from recently-referenced next-hop servers.
3013    </t>
3014    <t> A proxy &MUST-NOT; forward a 100 (Continue) response if the
3015        request message was received from an HTTP/1.0 (or earlier)
3016        client and did not include an Expect header field with
3017        the "100-continue" expectation. This requirement overrides the
3018        general rule for forwarding of 1xx responses (see &status-1xx;).
3019    </t>
3020  </list>
3024<section title="Closing Connections on Error" anchor="closing.connections.on.error">
3026   If the client is sending data, a server implementation using TCP
3027   &SHOULD; be careful to ensure that the client acknowledges receipt of
3028   the packet(s) containing the response, before the server closes the
3029   input connection. If the client continues sending data to the server
3030   after the close, the server's TCP stack will send a reset packet to
3031   the client, which might erase the client's unacknowledged input buffers
3032   before they can be read and interpreted by the HTTP application.
3040<section title="Miscellaneous notes that might disappear" anchor="misc">
3041<section title="Scheme aliases considered harmful" anchor="scheme.aliases">
3043   <cref anchor="TBD-aliases-harmful">describe why aliases like webcal are harmful.</cref>
3047<section title="Use of HTTP for proxy communication" anchor="http.proxy">
3049   <cref anchor="TBD-proxy-other">Configured to use HTTP to proxy HTTP or other protocols.</cref>
3053<section title="Interception of HTTP for access control" anchor="http.intercept">
3055   <cref anchor="TBD-intercept">Interception of HTTP traffic for initiating access control.</cref>
3059<section title="Use of HTTP by other protocols" anchor="http.others">
3061   <cref anchor="TBD-profiles">Profiles of HTTP defined by other protocol.
3062   Extensions of HTTP like WebDAV.</cref>
3066<section title="Use of HTTP by media type specification" anchor="">
3068   <cref anchor="TBD-hypertext">Instructions on composing HTTP requests via hypertext formats.</cref>
3073<section title="Header Field Definitions" anchor="header.field.definitions">
3075   This section defines the syntax and semantics of HTTP header fields
3076   related to message origination, framing, and routing.
3078<texttable align="left">
3079  <ttcol>Header Field Name</ttcol>
3080  <ttcol>Defined in...</ttcol>
3082  <c>Connection</c> <c><xref target="header.connection"/></c>
3083  <c>Content-Length</c> <c><xref target="header.content-length"/></c>
3084  <c>Host</c> <c><xref target=""/></c>
3085  <c>TE</c> <c><xref target="header.te"/></c>
3086  <c>Trailer</c> <c><xref target="header.trailer"/></c>
3087  <c>Transfer-Encoding</c> <c><xref target="header.transfer-encoding"/></c>
3088  <c>Upgrade</c> <c><xref target="header.upgrade"/></c>
3089  <c>Via</c> <c><xref target="header.via"/></c>
3092<section title="Connection" anchor="header.connection">
3093  <iref primary="true" item="Connection header field" x:for-anchor=""/>
3094  <iref primary="true" item="Header Fields" subitem="Connection" x:for-anchor=""/>
3095  <x:anchor-alias value="Connection"/>
3096  <x:anchor-alias value="connection-token"/>
3098   The "Connection" header field allows the sender to specify
3099   options that are desired only for that particular connection.
3100   Such connection options &MUST; be removed or replaced before the
3101   message can be forwarded downstream by a proxy or gateway.
3102   This mechanism also allows the sender to indicate which HTTP
3103   header fields used in the message are only intended for the
3104   immediate recipient ("hop-by-hop"), as opposed to all recipients
3105   on the chain ("end-to-end"), enabling the message to be
3106   self-descriptive and allowing future connection-specific extensions
3107   to be deployed in HTTP without fear that they will be blindly
3108   forwarded by previously deployed intermediaries.
3111   The Connection header field's value has the following grammar:
3113<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="connection-token"/>
3114  <x:ref>Connection</x:ref>       = 1#<x:ref>connection-token</x:ref>
3115  <x:ref>connection-token</x:ref> = <x:ref>token</x:ref>
3118   A proxy or gateway &MUST; parse a received Connection
3119   header field before a message is forwarded and, for each
3120   connection-token in this field, remove any header field(s) from
3121   the message with the same name as the connection-token, and then
3122   remove the Connection header field itself or replace it with the
3123   sender's own connection options for the forwarded message.
3126   A sender &MUST-NOT; include field-names in the Connection header
3127   field-value for fields that are defined as expressing constraints
3128   for all recipients in the request or response chain, such as the
3129   Cache-Control header field (&header-cache-control;).
3132   The connection options do not have to correspond to a header field
3133   present in the message, since a connection-specific header field
3134   might not be needed if there are no parameters associated with that
3135   connection option.  Recipients that trigger certain connection
3136   behavior based on the presence of connection options &MUST; do so
3137   based on the presence of the connection-token rather than only the
3138   presence of the optional header field.  In other words, if the
3139   connection option is received as a header field but not indicated
3140   within the Connection field-value, then the recipient &MUST; ignore
3141   the connection-specific header field because it has likely been
3142   forwarded by an intermediary that is only partially conformant.
3145   When defining new connection options, specifications ought to
3146   carefully consider existing deployed header fields and ensure
3147   that the new connection-token does not share the same name as
3148   an unrelated header field that might already be deployed.
3149   Defining a new connection-token essentially reserves that potential
3150   field-name for carrying additional information related to the
3151   connection option, since it would be unwise for senders to use
3152   that field-name for anything else.
3155   HTTP/1.1 defines the "close" connection option for the sender to
3156   signal that the connection will be closed after completion of the
3157   response. For example,
3159<figure><artwork type="example">
3160  Connection: close
3163   in either the request or the response header fields indicates that
3164   the connection &SHOULD-NOT;  be considered "persistent" (<xref target="persistent.connections"/>)
3165   after the current request/response is complete.
3168   An HTTP/1.1 client that does not support persistent connections &MUST;
3169   include the "close" connection option in every request message.
3172   An HTTP/1.1 server that does not support persistent connections &MUST;
3173   include the "close" connection option in every response message that
3174   does not have a 1xx (Informational) status code.
3178<section title="Host" anchor="">
3179  <iref primary="true" item="Host header field" x:for-anchor=""/>
3180  <iref primary="true" item="Header Fields" subitem="Host" x:for-anchor=""/>
3181  <x:anchor-alias value="Host"/>
3183   The "Host" header field in a request provides the host and port
3184   information from the target resource's URI, enabling the origin
3185   server to distinguish between resources while servicing requests
3186   for multiple host names on a single IP address.  Since the Host
3187   field-value is critical information for handling a request, it
3188   &SHOULD; be sent as the first header field following the request-line.
3190<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Host"/>
3191  <x:ref>Host</x:ref> = <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ; <xref target="http.uri"/>
3194   A client &MUST; send a Host header field in all HTTP/1.1 request
3195   messages.  If the target resource's URI includes an authority
3196   component, then the Host field-value &MUST; be identical to that
3197   authority component after excluding any userinfo (<xref target="http.uri"/>).
3198   If the authority component is missing or undefined for the target
3199   resource's URI, then the Host header field &MUST; be sent with an
3200   empty field-value.
3203   For example, a GET request to the origin server for
3204   &lt;; would begin with:
3206<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
3207GET /pub/WWW/ HTTP/1.1
3211   The Host header field &MUST; be sent in an HTTP/1.1 request even
3212   if the request-target is in the form of an absolute-URI, since this
3213   allows the Host information to be forwarded through ancient HTTP/1.0
3214   proxies that might not have implemented Host.
3217   When an HTTP/1.1 proxy receives a request with a request-target in
3218   the form of an absolute-URI, the proxy &MUST; ignore the received
3219   Host header field (if any) and instead replace it with the host
3220   information of the request-target.  When a proxy forwards a request,
3221   it &MUST; generate the Host header field based on the received
3222   absolute-URI rather than the received Host.
3225   Since the Host header field acts as an application-level routing
3226   mechanism, it is a frequent target for malware seeking to poison
3227   a shared cache or redirect a request to an unintended server.
3228   An interception proxy is particularly vulnerable if it relies on
3229   the Host header field value for redirecting requests to internal
3230   servers, or for use as a cache key in a shared cache, without
3231   first verifying that the intercepted connection is targeting a
3232   valid IP address for that host.
3235   A server &MUST; respond with a 400 (Bad Request) status code to
3236   any HTTP/1.1 request message that lacks a Host header field and
3237   to any request message that contains more than one Host header field
3238   or a Host header field with an invalid field-value.
3241   See Sections <xref target="" format="counter"/>
3242   and <xref target="" format="counter"/>
3243   for other requirements relating to Host.
3247<section title="Upgrade" anchor="header.upgrade">
3248  <iref primary="true" item="Upgrade header field" x:for-anchor=""/>
3249  <iref primary="true" item="Header Fields" subitem="Upgrade" x:for-anchor=""/>
3250  <x:anchor-alias value="Upgrade"/>
3251  <x:anchor-alias value="protocol"/>
3252  <x:anchor-alias value="protocol-name"/>
3253  <x:anchor-alias value="protocol-version"/>
3255   The "Upgrade" header field allows the client to specify what
3256   additional communication protocols it would like to use, if the server
3257   chooses to switch protocols. Servers can use it to indicate what protocols
3258   they are willing to switch to.
3260<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Upgrade"/>
3261  <x:ref>Upgrade</x:ref>          = 1#<x:ref>protocol</x:ref>
3263  <x:ref>protocol</x:ref>         = <x:ref>protocol-name</x:ref> ["/" <x:ref>protocol-version</x:ref>]
3264  <x:ref>protocol-name</x:ref>    = <x:ref>token</x:ref>
3265  <x:ref>protocol-version</x:ref> = <x:ref>token</x:ref>
3268   For example,
3270<figure><artwork type="example">
3271  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
3274   The Upgrade header field is intended to provide a simple mechanism
3275   for transitioning from HTTP/1.1 to some other, incompatible protocol. It
3276   does so by allowing the client to advertise its desire to use another
3277   protocol, such as a later version of HTTP with a higher major version
3278   number, even though the current request has been made using HTTP/1.1.
3279   This eases the difficult transition between incompatible protocols by
3280   allowing the client to initiate a request in the more commonly
3281   supported protocol while indicating to the server that it would like
3282   to use a "better" protocol if available (where "better" is determined
3283   by the server, possibly according to the nature of the request method
3284   or target resource).
3287   The Upgrade header field only applies to switching application-layer
3288   protocols upon the existing transport-layer connection. Upgrade
3289   cannot be used to insist on a protocol change; its acceptance and use
3290   by the server is optional. The capabilities and nature of the
3291   application-layer communication after the protocol change is entirely
3292   dependent upon the new protocol chosen, although the first action
3293   after changing the protocol &MUST; be a response to the initial HTTP
3294   request containing the Upgrade header field.
3297   The Upgrade header field only applies to the immediate connection.
3298   Therefore, the upgrade keyword &MUST; be supplied within a Connection
3299   header field (<xref target="header.connection"/>) whenever Upgrade is present in an
3300   HTTP/1.1 message.
3303   The Upgrade header field cannot be used to indicate a switch to a
3304   protocol on a different connection. For that purpose, it is more
3305   appropriate to use a 3xx redirection response (&status-3xx;).
3308   Servers &MUST; include the "Upgrade" header field in 101 (Switching
3309   Protocols) responses to indicate which protocol(s) are being switched to,
3310   and &MUST; include it in 426 (Upgrade Required) responses to indicate
3311   acceptable protocols to upgrade to. Servers &MAY; include it in any other
3312   response to indicate that they are willing to upgrade to one of the
3313   specified protocols.
3316   This specification only defines the protocol name "HTTP" for use by
3317   the family of Hypertext Transfer Protocols, as defined by the HTTP
3318   version rules of <xref target="http.version"/> and future updates to this
3319   specification. Additional tokens can be registered with IANA using the
3320   registration procedure defined below. 
3323<section title="Upgrade Token Registry" anchor="upgrade.token.registry">
3325   The HTTP Upgrade Token Registry defines the name space for protocol-name
3326   tokens used to identify protocols in the Upgrade header field.
3327   Each registered protocol-name is associated with contact information and
3328   an optional set of specifications that details how the connection
3329   will be processed after it has been upgraded.
3332   Registrations require IETF Review (see
3333   <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>) and are subject to the
3334   following rules:
3335  <list style="numbers">
3336    <t>A protocol-name token, once registered, stays registered forever.</t>
3337    <t>The registration &MUST; name a responsible party for the
3338       registration.</t>
3339    <t>The registration &MUST; name a point of contact.</t>
3340    <t>The registration &MAY; name a set of specifications associated with
3341       that token. Such specifications need not be publicly available.</t>
3342    <t>The registration &SHOULD; name a set of expected "protocol-version"
3343       tokens associated with that token at the time of registration.</t>
3344    <t>The responsible party &MAY; change the registration at any time.
3345       The IANA will keep a record of all such changes, and make them
3346       available upon request.</t>
3347    <t>The IESG &MAY; reassign responsibility for a protocol token.
3348       This will normally only be used in the case when a
3349       responsible party cannot be contacted.</t>
3350  </list>
3357<section title="Via" anchor="header.via">
3358  <iref primary="true" item="Via header field" x:for-anchor=""/>
3359  <iref primary="true" item="Header Fields" subitem="Via" x:for-anchor=""/>
3360  <x:anchor-alias value="pseudonym"/>
3361  <x:anchor-alias value="received-by"/>
3362  <x:anchor-alias value="received-protocol"/>
3363  <x:anchor-alias value="Via"/>
3365   The "Via" header field &MUST; be sent by a proxy or gateway to
3366   indicate the intermediate protocols and recipients between the user
3367   agent and the server on requests, and between the origin server and
3368   the client on responses. It is analogous to the "Received" field
3369   used by email systems (<xref target="RFC5322" x:fmt="of" x:sec="3.6.7"/>)
3370   and is intended to be used for tracking message forwards,
3371   avoiding request loops, and identifying the protocol capabilities of
3372   all senders along the request/response chain.
3374<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"/>
3375  <x:ref>Via</x:ref>               = 1#( <x:ref>received-protocol</x:ref> <x:ref>RWS</x:ref> <x:ref>received-by</x:ref>
3376                          [ <x:ref>RWS</x:ref> <x:ref>comment</x:ref> ] )
3377  <x:ref>received-protocol</x:ref> = [ <x:ref>protocol-name</x:ref> "/" ] <x:ref>protocol-version</x:ref>
3378  <x:ref>received-by</x:ref>       = ( <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ) / <x:ref>pseudonym</x:ref>
3379  <x:ref>pseudonym</x:ref>         = <x:ref>token</x:ref>
3382   The received-protocol indicates the protocol version of the message
3383   received by the server or client along each segment of the
3384   request/response chain. The received-protocol version is appended to
3385   the Via field value when the message is forwarded so that information
3386   about the protocol capabilities of upstream applications remains
3387   visible to all recipients.
3390   The protocol-name is excluded if and only if it would be "HTTP". The
3391   received-by field is normally the host and optional port number of a
3392   recipient server or client that subsequently forwarded the message.
3393   However, if the real host is considered to be sensitive information,
3394   it &MAY; be replaced by a pseudonym. If the port is not given, it &MAY;
3395   be assumed to be the default port of the received-protocol.
3398   Multiple Via field values represent each proxy or gateway that has
3399   forwarded the message. Each recipient &MUST; append its information
3400   such that the end result is ordered according to the sequence of
3401   forwarding applications.
3404   Comments &MAY; be used in the Via header field to identify the software
3405   of each recipient, analogous to the User-Agent and Server header fields.
3406   However, all comments in the Via field are optional and &MAY; be removed
3407   by any recipient prior to forwarding the message.
3410   For example, a request message could be sent from an HTTP/1.0 user
3411   agent to an internal proxy code-named "fred", which uses HTTP/1.1 to
3412   forward the request to a public proxy at, which completes
3413   the request by forwarding it to the origin server at
3414   The request received by would then have the following
3415   Via header field:
3417<figure><artwork type="example">
3418  Via: 1.0 fred, 1.1 (Apache/1.1)
3421   A proxy or gateway used as a portal through a network firewall
3422   &SHOULD-NOT; forward the names and ports of hosts within the firewall
3423   region unless it is explicitly enabled to do so. If not enabled, the
3424   received-by host of any host behind the firewall &SHOULD; be replaced
3425   by an appropriate pseudonym for that host.
3428   For organizations that have strong privacy requirements for hiding
3429   internal structures, a proxy or gateway &MAY; combine an ordered
3430   subsequence of Via header field entries with identical received-protocol
3431   values into a single such entry. For example,
3433<figure><artwork type="example">
3434  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
3437  could be collapsed to
3439<figure><artwork type="example">
3440  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
3443   Senders &SHOULD-NOT; combine multiple entries unless they are all
3444   under the same organizational control and the hosts have already been
3445   replaced by pseudonyms. Senders &MUST-NOT; combine entries which
3446   have different received-protocol values.
3452<section title="IANA Considerations" anchor="IANA.considerations">
3454<section title="Header Field Registration" anchor="header.field.registration">
3456   The Message Header Field Registry located at <eref target=""/> shall be updated
3457   with the permanent registrations below (see <xref target="RFC3864"/>):
3459<?BEGININC p1-messaging.iana-headers ?>
3460<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
3461<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
3462   <ttcol>Header Field Name</ttcol>
3463   <ttcol>Protocol</ttcol>
3464   <ttcol>Status</ttcol>
3465   <ttcol>Reference</ttcol>
3467   <c>Connection</c>
3468   <c>http</c>
3469   <c>standard</c>
3470   <c>
3471      <xref target="header.connection"/>
3472   </c>
3473   <c>Content-Length</c>
3474   <c>http</c>
3475   <c>standard</c>
3476   <c>
3477      <xref target="header.content-length"/>
3478   </c>
3479   <c>Host</c>
3480   <c>http</c>
3481   <c>standard</c>
3482   <c>
3483      <xref target=""/>
3484   </c>
3485   <c>TE</c>
3486   <c>http</c>
3487   <c>standard</c>
3488   <c>
3489      <xref target="header.te"/>
3490   </c>
3491   <c>Trailer</c>
3492   <c>http</c>
3493   <c>standard</c>
3494   <c>
3495      <xref target="header.trailer"/>
3496   </c>
3497   <c>Transfer-Encoding</c>
3498   <c>http</c>
3499   <c>standard</c>
3500   <c>
3501      <xref target="header.transfer-encoding"/>
3502   </c>
3503   <c>Upgrade</c>
3504   <c>http</c>
3505   <c>standard</c>
3506   <c>
3507      <xref target="header.upgrade"/>
3508   </c>
3509   <c>Via</c>
3510   <c>http</c>
3511   <c>standard</c>
3512   <c>
3513      <xref target="header.via"/>
3514   </c>
3517<?ENDINC p1-messaging.iana-headers ?>
3519   Furthermore, the header field name "Close" shall be registered as "reserved", as its use as
3520   HTTP header field would be in conflict with the use of the "close" connection
3521   option for the "Connection" header field (<xref target="header.connection"/>).
3523<texttable align="left" suppress-title="true">
3524   <ttcol>Header Field Name</ttcol>
3525   <ttcol>Protocol</ttcol>
3526   <ttcol>Status</ttcol>
3527   <ttcol>Reference</ttcol>
3529   <c>Close</c>
3530   <c>http</c>
3531   <c>reserved</c>
3532   <c>
3533      <xref target="header.field.registration"/>
3534   </c>
3537   The change controller is: "IETF ( - Internet Engineering Task Force".
3541<section title="URI Scheme Registration" anchor="uri.scheme.registration">
3543   The entries for the "http" and "https" URI Schemes in the registry located at
3544   <eref target=""/>
3545   shall be updated to point to Sections <xref target="http.uri" format="counter"/>
3546   and <xref target="https.uri" format="counter"/> of this document
3547   (see <xref target="RFC4395"/>).
3551<section title="Internet Media Type Registrations" anchor="">
3553   This document serves as the specification for the Internet media types
3554   "message/http" and "application/http". The following is to be registered with
3555   IANA (see <xref target="RFC4288"/>).
3557<section title="Internet Media Type message/http" anchor="">
3558<iref item="Media Type" subitem="message/http" primary="true"/>
3559<iref item="message/http Media Type" primary="true"/>
3561   The message/http type can be used to enclose a single HTTP request or
3562   response message, provided that it obeys the MIME restrictions for all
3563   "message" types regarding line length and encodings.
3566  <list style="hanging" x:indent="12em">
3567    <t hangText="Type name:">
3568      message
3569    </t>
3570    <t hangText="Subtype name:">
3571      http
3572    </t>
3573    <t hangText="Required parameters:">
3574      none
3575    </t>
3576    <t hangText="Optional parameters:">
3577      version, msgtype
3578      <list style="hanging">
3579        <t hangText="version:">
3580          The HTTP-version number of the enclosed message
3581          (e.g., "1.1"). If not present, the version can be
3582          determined from the first line of the body.
3583        </t>
3584        <t hangText="msgtype:">
3585          The message type &mdash; "request" or "response". If not
3586          present, the type can be determined from the first
3587          line of the body.
3588        </t>
3589      </list>
3590    </t>
3591    <t hangText="Encoding considerations:">
3592      only "7bit", "8bit", or "binary" are permitted
3593    </t>
3594    <t hangText="Security considerations:">
3595      none
3596    </t>
3597    <t hangText="Interoperability considerations:">
3598      none
3599    </t>
3600    <t hangText="Published specification:">
3601      This specification (see <xref target=""/>).
3602    </t>
3603    <t hangText="Applications that use this media type:">
3604    </t>
3605    <t hangText="Additional information:">
3606      <list style="hanging">
3607        <t hangText="Magic number(s):">none</t>
3608        <t hangText="File extension(s):">none</t>
3609        <t hangText="Macintosh file type code(s):">none</t>
3610      </list>
3611    </t>
3612    <t hangText="Person and email address to contact for further information:">
3613      See Authors Section.
3614    </t>
3615    <t hangText="Intended usage:">
3616      COMMON
3617    </t>
3618    <t hangText="Restrictions on usage:">
3619      none
3620    </t>
3621    <t hangText="Author/Change controller:">
3622      IESG
3623    </t>
3624  </list>
3627<section title="Internet Media Type application/http" anchor="">
3628<iref item="Media Type" subitem="application/http" primary="true"/>
3629<iref item="application/http Media Type" primary="true"/>
3631   The application/http type can be used to enclose a pipeline of one or more
3632   HTTP request or response messages (not intermixed).
3635  <list style="hanging" x:indent="12em">
3636    <t hangText="Type name:">
3637      application
3638    </t>
3639    <t hangText="Subtype name:">
3640      http
3641    </t>
3642    <t hangText="Required parameters:">
3643      none
3644    </t>
3645    <t hangText="Optional parameters:">
3646      version, msgtype
3647      <list style="hanging">
3648        <t hangText="version:">
3649          The HTTP-version number of the enclosed messages
3650          (e.g., "1.1"). If not present, the version can be
3651          determined from the first line of the body.
3652        </t>
3653        <t hangText="msgtype:">
3654          The message type &mdash; "request" or "response". If not
3655          present, the type can be determined from the first
3656          line of the body.
3657        </t>
3658      </list>
3659    </t>
3660    <t hangText="Encoding considerations:">
3661      HTTP messages enclosed by this type
3662      are in "binary" format; use of an appropriate
3663      Content-Transfer-Encoding is required when
3664      transmitted via E-mail.
3665    </t>
3666    <t hangText="Security considerations:">
3667      none
3668    </t>
3669    <t hangText="Interoperability considerations:">
3670      none
3671    </t>
3672    <t hangText="Published specification:">
3673      This specification (see <xref target=""/>).
3674    </t>
3675    <t hangText="Applications that use this media type:">
3676    </t>
3677    <t hangText="Additional information:">
3678      <list style="hanging">
3679        <t hangText="Magic number(s):">none</t>
3680        <t hangText="File extension(s):">none</t>
3681        <t hangText="Macintosh file type code(s):">none</t>
3682      </list>
3683    </t>
3684    <t hangText="Person and email address to contact for further information:">
3685      See Authors Section.
3686    </t>
3687    <t hangText="Intended usage:">
3688      COMMON
3689    </t>
3690    <t hangText="Restrictions on usage:">
3691      none
3692    </t>
3693    <t hangText="Author/Change controller:">
3694      IESG
3695    </t>
3696  </list>
3701<section title="Transfer Coding Registry" anchor="transfer.coding.registration">
3703   The registration procedure for HTTP Transfer Codings is now defined by
3704   <xref target="transfer.coding.registry"/> of this document.
3707   The HTTP Transfer Codings Registry located at <eref target=""/>
3708   shall be updated with the registrations below:
3710<texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table">
3711   <ttcol>Name</ttcol>
3712   <ttcol>Description</ttcol>
3713   <ttcol>Reference</ttcol>
3714   <c>chunked</c>
3715   <c>Transfer in a series of chunks</c>
3716   <c>
3717      <xref target="chunked.encoding"/>
3718   </c>
3719   <c>compress</c>
3720   <c>UNIX "compress" program method</c>
3721   <c>
3722      <xref target="compress.coding"/>
3723   </c>
3724   <c>deflate</c>
3725   <c>"deflate" compression mechanism (<xref target="RFC1951"/>) used inside
3726   the "zlib" data format (<xref target="RFC1950"/>)
3727   </c>
3728   <c>
3729      <xref target="deflate.coding"/>
3730   </c>
3731   <c>gzip</c>
3732   <c>Same as GNU zip <xref target="RFC1952"/></c>
3733   <c>
3734      <xref target="gzip.coding"/>
3735   </c>
3739<section title="Upgrade Token Registration" anchor="upgrade.token.registration">
3741   The registration procedure for HTTP Upgrade Tokens &mdash; previously defined
3742   in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/> &mdash; is now defined
3743   by <xref target="upgrade.token.registry"/> of this document.
3746   The HTTP Upgrade Token Registry located at <eref target=""/>
3747   shall be updated with the registration below:
3749<texttable align="left" suppress-title="true">
3750   <ttcol>Value</ttcol>
3751   <ttcol>Description</ttcol>
3752   <ttcol>Reference</ttcol>
3754   <c>HTTP</c>
3755   <c>Hypertext Transfer Protocol</c>
3756   <c><xref target="http.version"/> of this specification</c>
3763<section title="Security Considerations" anchor="security.considerations">
3765   This section is meant to inform application developers, information
3766   providers, and users of the security limitations in HTTP/1.1 as
3767   described by this document. The discussion does not include
3768   definitive solutions to the problems revealed, though it does make
3769   some suggestions for reducing security risks.
3772<section title="Personal Information" anchor="personal.information">
3774   HTTP clients are often privy to large amounts of personal information
3775   (e.g., the user's name, location, mail address, passwords, encryption
3776   keys, etc.), and &SHOULD; be very careful to prevent unintentional
3777   leakage of this information.
3778   We very strongly recommend that a convenient interface be provided
3779   for the user to control dissemination of such information, and that
3780   designers and implementors be particularly careful in this area.
3781   History shows that errors in this area often create serious security
3782   and/or privacy problems and generate highly adverse publicity for the
3783   implementor's company.
3787<section title="Abuse of Server Log Information" anchor="abuse.of.server.log.information">
3789   A server is in the position to save personal data about a user's
3790   requests which might identify their reading patterns or subjects of
3791   interest. This information is clearly confidential in nature and its
3792   handling can be constrained by law in certain countries. People using
3793   HTTP to provide data are responsible for ensuring that
3794   such material is not distributed without the permission of any
3795   individuals that are identifiable by the published results.
3799<section title="Attacks Based On File and Path Names" anchor="attack.pathname">
3801   Implementations of HTTP origin servers &SHOULD; be careful to restrict
3802   the documents returned by HTTP requests to be only those that were
3803   intended by the server administrators. If an HTTP server translates
3804   HTTP URIs directly into file system calls, the server &MUST; take
3805   special care not to serve files that were not intended to be
3806   delivered to HTTP clients. For example, UNIX, Microsoft Windows, and
3807   other operating systems use ".." as a path component to indicate a
3808   directory level above the current one. On such a system, an HTTP
3809   server &MUST; disallow any such construct in the request-target if it
3810   would otherwise allow access to a resource outside those intended to
3811   be accessible via the HTTP server. Similarly, files intended for
3812   reference only internally to the server (such as access control
3813   files, configuration files, and script code) &MUST; be protected from
3814   inappropriate retrieval, since they might contain sensitive
3815   information. Experience has shown that minor bugs in such HTTP server
3816   implementations have turned into security risks.
3820<section title="DNS-related Attacks" anchor="dns.related.attacks">
3822   HTTP clients rely heavily on the Domain Name Service (DNS), and are thus
3823   generally prone to security attacks based on the deliberate misassociation
3824   of IP addresses and DNS names not protected by DNSSec. Clients need to be
3825   cautious in assuming the validity of an IP number/DNS name association unless
3826   the response is protected by DNSSec (<xref target="RFC4033"/>).
3830<section title="Proxies and Caching" anchor="attack.proxies">
3832   By their very nature, HTTP proxies are men-in-the-middle, and
3833   represent an opportunity for man-in-the-middle attacks. Compromise of
3834   the systems on which the proxies run can result in serious security
3835   and privacy problems. Proxies have access to security-related
3836   information, personal information about individual users and
3837   organizations, and proprietary information belonging to users and
3838   content providers. A compromised proxy, or a proxy implemented or
3839   configured without regard to security and privacy considerations,
3840   might be used in the commission of a wide range of potential attacks.
3843   Proxy operators need to protect the systems on which proxies run as
3844   they would protect any system that contains or transports sensitive
3845   information. In particular, log information gathered at proxies often
3846   contains highly sensitive personal information, and/or information
3847   about organizations. Log information needs to be carefully guarded, and
3848   appropriate guidelines for use need to be developed and followed.
3849   (<xref target="abuse.of.server.log.information"/>).
3852   Proxy implementors need to consider the privacy and security
3853   implications of their design and coding decisions, and of the
3854   configuration options they provide to proxy operators (especially the
3855   default configuration).
3858   Users of a proxy need to be aware that proxies are no more trustworthy than
3859   the people who run them; HTTP itself cannot solve this problem.
3862   The judicious use of cryptography, when appropriate, might suffice to
3863   protect against a broad range of security and privacy attacks. Such
3864   cryptography is beyond the scope of the HTTP/1.1 specification.
3868<section title="Protocol Element Size Overflows" anchor="attack.protocol.element.size.overflows">
3870   Because HTTP uses mostly textual, character-delimited fields, attackers can
3871   overflow buffers in implementations, and/or perform a Denial of Service
3872   against implementations that accept fields with unlimited lengths.
3875   To promote interoperability, this specification makes specific
3876   recommendations for size limits on request-targets (<xref target="request-target"/>)
3877   and blocks of header fields (<xref target="header.fields"/>). These are
3878   minimum recommendations, chosen to be supportable even by implementations
3879   with limited resources; it is expected that most implementations will choose
3880   substantially higher limits.
3883   This specification also provides a way for servers to reject messages that
3884   have request-targets that are too long (&status-414;) or request entities
3885   that are too large (&status-4xx;).
3888   Other fields (including but not limited to request methods, response status
3889   phrases, header field-names, and body chunks) &SHOULD; be limited by
3890   implementations carefully, so as to not impede interoperability.
3894<section title="Denial of Service Attacks on Proxies" anchor="attack.DoS">
3896   They exist. They are hard to defend against. Research continues.
3897   Beware.
3902<section title="Acknowledgments" anchor="acks">
3904   This document revision builds on the work that went into
3905   <xref target="RFC2616" format="none">RFC 2616</xref> and its predecessors.
3906   See <xref target="RFC2616" x:fmt="of" x:sec="16"/> for detailed
3907   acknowledgements.
3910   Since 1999, many contributors have helped by reporting bugs, asking
3911   smart questions, drafting and reviewing text, and discussing open issues:
3913<?BEGININC acks ?>
3914<t>Adam Barth,
3915Adam Roach,
3916Addison Phillips,
3917Adrian Chadd,
3918Adrien de Croy,
3919Alan Ford,
3920Alan Ruttenberg,
3921Albert Lunde,
3922Alex Rousskov,
3923Alexey Melnikov,
3924Alisha Smith,
3925Amichai Rothman,
3926Amit Klein,
3927Amos Jeffries,
3928Andreas Maier,
3929Andreas Petersson,
3930Anne van Kesteren,
3931Anthony Bryan,
3932Asbjorn Ulsberg,
3933Balachander Krishnamurthy,
3934Barry Leiba,
3935Ben Laurie,
3936Benjamin Niven-Jenkins,
3937Bil Corry,
3938Bill Burke,
3939Bjoern Hoehrmann,
3940Bob Scheifler,
3941Boris Zbarsky,
3942Brett Slatkin,
3943Brian Kell,
3944Brian McBarron,
3945Brian Pane,
3946Brian Smith,
3947Bryce Nesbitt,
3948Cameron Heavon-Jones,
3949Carl Kugler,
3950Carsten Bormann,
3951Charles Fry,
3952Chris Newman,
3953Cyrus Daboo,
3954Dale Robert Anderson,
3955Dan Winship,
3956Daniel Stenberg,
3957Dave Cridland,
3958Dave Crocker,
3959Dave Kristol,
3960David Booth,
3961David Singer,
3962David W. Morris,
3963Diwakar Shetty,
3964Dmitry Kurochkin,
3965Drummond Reed,
3966Duane Wessels,
3967Edward Lee,
3968Eliot Lear,
3969Eran Hammer-Lahav,
3970Eric D. Williams,
3971Eric J. Bowman,
3972Eric Lawrence,
3973Eric Rescorla,
3974Erik Aronesty,
3975Florian Weimer,
3976Frank Ellermann,
3977Fred Bohle,
3978Geoffrey Sneddon,
3979Gervase Markham,
3980Greg Wilkins,
3981Harald Tveit Alvestrand,
3982Harry Halpin,
3983Helge Hess,
3984Henrik Nordstrom,
3985Henry S. Thompson,
3986Henry Story,
3987Herbert van de Sompel,
3988Howard Melman,
3989Hugo Haas,
3990Ian Hickson,
3991Ingo Struck,
3992J. Ross Nicoll,
3993James H. Manger,
3994James Lacey,
3995James M. Snell,
3996Jamie Lokier,
3997Jan Algermissen,
3998Jeff Hodges (for coming up with the term 'effective Request-URI'),
3999Jeff Walden,
4000Jim Luther,
4001Joe D. Williams,
4002Joe Gregorio,
4003Joe Orton,
4004John C. Klensin,
4005John C. Mallery,
4006John Cowan,
4007John Kemp,
4008John Panzer,
4009John Schneider,
4010John Stracke,
4011Jonas Sicking,
4012Jonathan Billington,
4013Jonathan Moore,
4014Jonathan Rees,
4015Jordi Ros,
4016Joris Dobbelsteen,
4017Josh Cohen,
4018Julien Pierre,
4019Jungshik Shin,
4020Justin Chapweske,
4021Justin Erenkrantz,
4022Justin James,
4023Kalvinder Singh,
4024Karl Dubost,
4025Keith Hoffman,
4026Keith Moore,
4027Koen Holtman,
4028Konstantin Voronkov,
4029Kris Zyp,
4030Lisa Dusseault,
4031Maciej Stachowiak,
4032Marc Schneider,
4033Marc Slemko,
4034Mark Baker,
4035Mark Nottingham (Working Group chair),
4036Mark Pauley,
4037Markus Lanthaler,
4038Martin J. Duerst,
4039Martin Thomson,
4040Matt Lynch,
4041Matthew Cox,
4042Max Clark,
4043Michael Burrows,
4044Michael Hausenblas,
4045Mike Amundsen,
4046Mike Belshe,
4047Mike Kelly,
4048Mike Schinkel,
4049Miles Sabin,
4050Mykyta Yevstifeyev,
4051Nathan Rixham,
4052Nicholas Shanks,
4053Nico Williams,
4054Nicolas Alvarez,
4055Nicolas Mailhot,
4056Noah Slater,
4057Pablo Castro,
4058Pat Hayes,
4059Patrick R. McManus,
4060Paul E. Jones,
4061Paul Hoffman,
4062Paul Marquess,
4063Peter Saint-Andre,
4064Peter Watkins,
4065Phil Archer,
4066Phillip Hallam-Baker,
4067Poul-Henning Kamp,
4068Preethi Natarajan,
4069Ray Polk,
4070Reto Bachmann-Gmuer,
4071Richard Cyganiak,
4072Robert Brewer,
4073Robert Collins,
4074Robert O'Callahan,
4075Robert Olofsson,
4076Robert Sayre,
4077Robert Siemer,
4078Robert de Wilde,
4079Roberto Javier Godoy,
4080Ronny Widjaja,
4081S. Mike Dierken,
4082Salvatore Loreto,
4083Sam Johnston,
4084Sam Ruby,
4085Scott Lawrence (for maintaining the original issues list),
4086Sean B. Palmer,
4087Shane McCarron,
4088Stefan Eissing,
4089Stefan Tilkov,
4090Stefanos Harhalakis,
4091Stephane Bortzmeyer,
4092Stephen Farrell,
4093Stuart Williams,
4094Subbu Allamaraju,
4095Sylvain Hellegouarch,
4096Tapan Divekar,
4097Ted Hardie,
4098Thomas Broyer,
4099Thomas Nordin,
4100Thomas Roessler,
4101Tim Morgan,
4102Tim Olsen,
4103Travis Snoozy,
4104Tyler Close,
4105Vincent Murphy,
4106Wenbo Zhu,
4107Werner Baumann,
4108Wilbur Streett,
4109Wilfredo Sanchez Vega,
4110William A. Rowe Jr.,
4111William Chan,
4112Willy Tarreau,
4113Xiaoshu Wang,
4114Yaron Goland,
4115Yngve Nysaeter Pettersen,
4116Yogesh Bang,
4117Yutaka Oiwa,
4118Zed A. Shaw, and
4119Zhong Yu.
4121<?ENDINC acks ?>
4127<references title="Normative References">
4129<reference anchor="ISO-8859-1">
4130  <front>
4131    <title>
4132     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
4133    </title>
4134    <author>
4135      <organization>International Organization for Standardization</organization>
4136    </author>
4137    <date year="1998"/>
4138  </front>
4139  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
4142<reference anchor="Part2">
4143  <front>
4144    <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
4145    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4146      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4147      <address><email></email></address>
4148    </author>
4149    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4150      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
4151      <address><email></email></address>
4152    </author>
4153    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4154      <organization abbrev="HP">Hewlett-Packard Company</organization>
4155      <address><email></email></address>
4156    </author>
4157    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
4158      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4159      <address><email></email></address>
4160    </author>
4161    <author initials="L." surname="Masinter" fullname="Larry Masinter">
4162      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4163      <address><email></email></address>
4164    </author>
4165    <author initials="P." surname="Leach" fullname="Paul J. Leach">
4166      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4167      <address><email></email></address>
4168    </author>
4169    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4170      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4171      <address><email></email></address>
4172    </author>
4173    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4174      <organization abbrev="W3C">World Wide Web Consortium</organization>
4175      <address><email></email></address>
4176    </author>
4177    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4178      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4179      <address><email></email></address>
4180    </author>
4181    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4182  </front>
4183  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
4184  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
4187<reference anchor="Part3">
4188  <front>
4189    <title abbrev="HTTP/1.1">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
4190    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4191      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4192      <address><email></email></address>
4193    </author>
4194    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4195      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
4196      <address><email></email></address>
4197    </author>
4198    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4199      <organization abbrev="HP">Hewlett-Packard Company</organization>
4200      <address><email></email></address>
4201    </author>
4202    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
4203      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4204      <address><email></email></address>
4205    </author>
4206    <author initials="L." surname="Masinter" fullname="Larry Masinter">
4207      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4208      <address><email></email></address>
4209    </author>
4210    <author initials="P." surname="Leach" fullname="Paul J. Leach">
4211      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4212      <address><email></email></address>
4213    </author>
4214    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4215      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4216      <address><email></email></address>
4217    </author>
4218    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4219      <organization abbrev="W3C">World Wide Web Consortium</organization>
4220      <address><email></email></address>
4221    </author>
4222    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4223      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4224      <address><email></email></address>
4225    </author>
4226    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4227  </front>
4228  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p3-payload-&ID-VERSION;"/>
4229  <x:source href="p3-payload.xml" basename="p3-payload"/>
4232<reference anchor="Part6">
4233  <front>
4234    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
4235    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4236      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4237      <address><email></email></address>
4238    </author>
4239    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4240      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
4241      <address><email></email></address>
4242    </author>
4243    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4244      <organization abbrev="HP">Hewlett-Packard Company</organization>
4245      <address><email></email></address>
4246    </author>
4247    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
4248      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4249      <address><email></email></address>
4250    </author>
4251    <author initials="L." surname="Masinter" fullname="Larry Masinter">
4252      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4253      <address><email></email></address>
4254    </author>
4255    <author initials="P." surname="Leach" fullname="Paul J. Leach">
4256      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4257      <address><email></email></address>
4258    </author>
4259    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4260      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4261      <address><email></email></address>
4262    </author>
4263    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4264      <organization abbrev="W3C">World Wide Web Consortium</organization>
4265      <address><email></email></address>
4266    </author>
4267    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
4268      <organization>Rackspace</organization>
4269      <address><email></email></address>
4270    </author>
4271    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4272      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4273      <address><email></email></address>
4274    </author>
4275    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4276  </front>
4277  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
4278  <x:source href="p6-cache.xml" basename="p6-cache"/>
4281<reference anchor="RFC5234">
4282  <front>
4283    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
4284    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
4285      <organization>Brandenburg InternetWorking</organization>
4286      <address>
4287        <email></email>
4288      </address> 
4289    </author>
4290    <author initials="P." surname="Overell" fullname="Paul Overell">
4291      <organization>THUS plc.</organization>
4292      <address>
4293        <email></email>
4294      </address>
4295    </author>
4296    <date month="January" year="2008"/>
4297  </front>
4298  <seriesInfo name="STD" value="68"/>
4299  <seriesInfo name="RFC" value="5234"/>
4302<reference anchor="RFC2119">
4303  <front>
4304    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
4305    <author initials="S." surname="Bradner" fullname="Scott Bradner">
4306      <organization>Harvard University</organization>
4307      <address><email></email></address>
4308    </author>
4309    <date month="March" year="1997"/>
4310  </front>
4311  <seriesInfo name="BCP" value="14"/>
4312  <seriesInfo name="RFC" value="2119"/>
4315<reference anchor="RFC3986">
4316 <front>
4317  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
4318  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
4319    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4320    <address>
4321       <email></email>
4322       <uri></uri>
4323    </address>
4324  </author>
4325  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
4326    <organization abbrev="Day Software">Day Software</organization>
4327    <address>
4328      <email></email>
4329      <uri></uri>
4330    </address>
4331  </author>
4332  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
4333    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
4334    <address>
4335      <email></email>
4336      <uri></uri>
4337    </address>
4338  </author>
4339  <date month='January' year='2005'></date>
4340 </front>
4341 <seriesInfo name="STD" value="66"/>
4342 <seriesInfo name="RFC" value="3986"/>
4345<reference anchor="USASCII">
4346  <front>
4347    <title>Coded Character Set -- 7-bit American Standard Code for Information Interchange</title>
4348    <author>
4349      <organization>American National Standards Institute</organization>
4350    </author>
4351    <date year="1986"/>
4352  </front>
4353  <seriesInfo name="ANSI" value="X3.4"/>
4356<reference anchor="RFC1950">
4357  <front>
4358    <title>ZLIB Compressed Data Format Specification version 3.3</title>
4359    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
4360      <organization>Aladdin Enterprises</organization>
4361      <address><email></email></address>
4362    </author>
4363    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"/>
4364    <date month="May" year="1996"/>
4365  </front>
4366  <seriesInfo name="RFC" value="1950"/>
4367  <!--<annotation>
4368    RFC 1950 is an Informational RFC, thus it might be less stable than
4369    this specification. On the other hand, this downward reference was
4370    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4371    therefore it is unlikely to cause problems in practice. See also
4372    <xref target="BCP97"/>.
4373  </annotation>-->
4376<reference anchor="RFC1951">
4377  <front>
4378    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
4379    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
4380      <organization>Aladdin Enterprises</organization>
4381      <address><email></email></address>
4382    </author>
4383    <date month="May" year="1996"/>
4384  </front>
4385  <seriesInfo name="RFC" value="1951"/>
4386  <!--<annotation>
4387    RFC 1951 is an Informational RFC, thus it might be less stable than
4388    this specification. On the other hand, this downward reference was
4389    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4390    therefore it is unlikely to cause problems in practice. See also
4391    <xref target="BCP97"/>.
4392  </annotation>-->
4395<reference anchor="RFC1952">
4396  <front>
4397    <title>GZIP file format specification version 4.3</title>
4398    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
4399      <organization>Aladdin Enterprises</organization>
4400      <address><email></email></address>
4401    </author>
4402    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
4403      <address><email></email></address>
4404    </author>
4405    <author initials="M." surname="Adler" fullname="Mark Adler">
4406      <address><email></email></address>
4407    </author>
4408    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
4409      <address><email></email></address>
4410    </author>
4411    <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">
4412      <address><email></email></address>
4413    </author>
4414    <date month="May" year="1996"/>
4415  </front>
4416  <seriesInfo name="RFC" value="1952"/>
4417  <!--<annotation>
4418    RFC 1952 is an Informational RFC, thus it might be less stable than
4419    this specification. On the other hand, this downward reference was
4420    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4421    therefore it is unlikely to cause problems in practice. See also
4422    <xref target="BCP97"/>.
4423  </annotation>-->
4428<references title="Informative References">
4430<reference anchor="Nie1997" target="">
4431  <front>
4432    <title>Network Performance Effects of HTTP/1.1, CSS1, and PNG</title>
4433    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen"/>
4434    <author initials="J." surname="Gettys" fullname="J. Gettys"/>
4435    <author initials="E." surname="Prud'hommeaux" fullname="E. Prud'hommeaux"/>
4436    <author initials="H." surname="Lie" fullname="H. Lie"/>
4437    <author initials="C." surname="Lilley" fullname="C. Lilley"/>
4438    <date year="1997" month="September"/>
4439  </front>
4440  <seriesInfo name="ACM" value="Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication SIGCOMM '97"/>
4443<reference anchor="Pad1995" target="">
4444  <front>
4445    <title>Improving HTTP Latency</title>
4446    <author initials="V.N." surname="Padmanabhan" fullname="Venkata N. Padmanabhan"/>
4447    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul"/>
4448    <date year="1995" month="December"/>
4449  </front>
4450  <seriesInfo name="Computer Networks and ISDN Systems" value="v. 28, pp. 25-35"/>
4453<reference anchor='RFC1919'>
4454  <front>
4455    <title>Classical versus Transparent IP Proxies</title>
4456    <author initials='M.' surname='Chatel' fullname='Marc Chatel'>
4457      <address><email></email></address>
4458    </author>
4459    <date year='1996' month='March' />
4460  </front>
4461  <seriesInfo name='RFC' value='1919' />
4464<reference anchor="RFC1945">
4465  <front>
4466    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
4467    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4468      <organization>MIT, Laboratory for Computer Science</organization>
4469      <address><email></email></address>
4470    </author>
4471    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4472      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4473      <address><email></email></address>
4474    </author>
4475    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4476      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
4477      <address><email></email></address>
4478    </author>
4479    <date month="May" year="1996"/>
4480  </front>
4481  <seriesInfo name="RFC" value="1945"/>
4484<reference anchor="RFC2045">
4485  <front>
4486    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
4487    <author initials="N." surname="Freed" fullname="Ned Freed">
4488      <organization>Innosoft International, Inc.</organization>
4489      <address><email></email></address>
4490    </author>
4491    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
4492      <organization>First Virtual Holdings</organization>
4493      <address><email></email></address>
4494    </author>
4495    <date month="November" year="1996"/>
4496  </front>
4497  <seriesInfo name="RFC" value="2045"/>
4500<reference anchor="RFC2047">
4501  <front>
4502    <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
4503    <author initials="K." surname="Moore" fullname="Keith Moore">
4504      <organization>University of Tennessee</organization>
4505      <address><email></email></address>
4506    </author>
4507    <date month="November" year="1996"/>
4508  </front>
4509  <seriesInfo name="RFC" value="2047"/>
4512<reference anchor="RFC2068">
4513  <front>
4514    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
4515    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
4516      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4517      <address><email></email></address>
4518    </author>
4519    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4520      <organization>MIT Laboratory for Computer Science</organization>
4521      <address><email></email></address>
4522    </author>
4523    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4524      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
4525      <address><email></email></address>
4526    </author>
4527    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4528      <organization>MIT Laboratory for Computer Science</organization>
4529      <address><email></email></address>
4530    </author>
4531    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4532      <organization>MIT Laboratory for Computer Science</organization>
4533      <address><email></email></address>
4534    </author>
4535    <date month="January" year="1997"/>
4536  </front>
4537  <seriesInfo name="RFC" value="2068"/>
4540<reference anchor="RFC2145">
4541  <front>
4542    <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
4543    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
4544      <organization>Western Research Laboratory</organization>
4545      <address><email></email></address>
4546    </author>
4547    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4548      <organization>Department of Information and Computer Science</organization>
4549      <address><email></email></address>
4550    </author>
4551    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4552      <organization>MIT Laboratory for Computer Science</organization>
4553      <address><email></email></address>
4554    </author>
4555    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4556      <organization>W3 Consortium</organization>
4557      <address><email></email></address>
4558    </author>
4559    <date month="May" year="1997"/>
4560  </front>
4561  <seriesInfo name="RFC" value="2145"/>
4564<reference anchor="RFC2616">
4565  <front>
4566    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
4567    <author initials="R." surname="Fielding" fullname="R. Fielding">
4568      <organization>University of California, Irvine</organization>
4569      <address><email></email></address>
4570    </author>
4571    <author initials="J." surname="Gettys" fullname="J. Gettys">
4572      <organization>W3C</organization>
4573      <address><email></email></address>
4574    </author>
4575    <author initials="J." surname="Mogul" fullname="J. Mogul">
4576      <organization>Compaq Computer Corporation</organization>
4577      <address><email></email></address>
4578    </author>
4579    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
4580      <organization>MIT Laboratory for Computer Science</organization>
4581      <address><email></email></address>
4582    </author>
4583    <author initials="L." surname="Masinter" fullname="L. Masinter">
4584      <organization>Xerox Corporation</organization>
4585      <address><email></email></address>
4586    </author>
4587    <author initials="P." surname="Leach" fullname="P. Leach">
4588      <organization>Microsoft Corporation</organization>
4589      <address><email></email></address>
4590    </author>
4591    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
4592      <organization>W3C</organization>
4593      <address><email></email></address>
4594    </author>
4595    <date month="June" year="1999"/>
4596  </front>
4597  <seriesInfo name="RFC" value="2616"/>
4600<reference anchor='RFC2817'>
4601  <front>
4602    <title>Upgrading to TLS Within HTTP/1.1</title>
4603    <author initials='R.' surname='Khare' fullname='R. Khare'>
4604      <organization>4K Associates / UC Irvine</organization>
4605      <address><email></email></address>
4606    </author>
4607    <author initials='S.' surname='Lawrence' fullname='S. Lawrence'>
4608      <organization>Agranat Systems, Inc.</organization>
4609      <address><email></email></address>
4610    </author>
4611    <date year='2000' month='May' />
4612  </front>
4613  <seriesInfo name='RFC' value='2817' />
4616<reference anchor='RFC2818'>
4617  <front>
4618    <title>HTTP Over TLS</title>
4619    <author initials='E.' surname='Rescorla' fullname='Eric Rescorla'>
4620      <organization>RTFM, Inc.</organization>
4621      <address><email></email></address>
4622    </author>
4623    <date year='2000' month='May' />
4624  </front>
4625  <seriesInfo name='RFC' value='2818' />
4628<reference anchor='RFC2965'>
4629  <front>
4630    <title>HTTP State Management Mechanism</title>
4631    <author initials='D. M.' surname='Kristol' fullname='David M. Kristol'>
4632      <organization>Bell Laboratories, Lucent Technologies</organization>
4633      <address><email></email></address>
4634    </author>
4635    <author initials='L.' surname='Montulli' fullname='Lou Montulli'>
4636      <organization>, Inc.</organization>
4637      <address><email></email></address>
4638    </author>
4639    <date year='2000' month='October' />
4640  </front>
4641  <seriesInfo name='RFC' value='2965' />
4644<reference anchor='RFC3040'>
4645  <front>
4646    <title>Internet Web Replication and Caching Taxonomy</title>
4647    <author initials='I.' surname='Cooper' fullname='I. Cooper'>
4648      <organization>Equinix, Inc.</organization>
4649    </author>
4650    <author initials='I.' surname='Melve' fullname='I. Melve'>
4651      <organization>UNINETT</organization>
4652    </author>
4653    <author initials='G.' surname='Tomlinson' fullname='G. Tomlinson'>
4654      <organization>CacheFlow Inc.</organization>
4655    </author>
4656    <date year='2001' month='January' />
4657  </front>
4658  <seriesInfo name='RFC' value='3040' />
4661<reference anchor='RFC3864'>
4662  <front>
4663    <title>Registration Procedures for Message Header Fields</title>
4664    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
4665      <organization>Nine by Nine</organization>
4666      <address><email></email></address>
4667    </author>
4668    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
4669      <organization>BEA Systems</organization>
4670      <address><email></email></address>
4671    </author>
4672    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
4673      <organization>HP Labs</organization>
4674      <address><email></email></address>
4675    </author>
4676    <date year='2004' month='September' />
4677  </front>
4678  <seriesInfo name='BCP' value='90' />
4679  <seriesInfo name='RFC' value='3864' />
4682<reference anchor='RFC4033'>
4683  <front>
4684    <title>DNS Security Introduction and Requirements</title>
4685    <author initials='R.' surname='Arends' fullname='R. Arends'/>
4686    <author initials='R.' surname='Austein' fullname='R. Austein'/>
4687    <author initials='M.' surname='Larson' fullname='M. Larson'/>
4688    <author initials='D.' surname='Massey' fullname='D. Massey'/>
4689    <author initials='S.' surname='Rose' fullname='S. Rose'/>
4690    <date year='2005' month='March' />
4691  </front>
4692  <seriesInfo name='RFC' value='4033' />
4695<reference anchor="RFC4288">
4696  <front>
4697    <title>Media Type Specifications and Registration Procedures</title>
4698    <author initials="N." surname="Freed" fullname="N. Freed">
4699      <organization>Sun Microsystems</organization>
4700      <address>
4701        <email></email>
4702      </address>
4703    </author>
4704    <author initials="J." surname="Klensin" fullname="J. Klensin">
4705      <address>
4706        <email></email>
4707      </address>
4708    </author>
4709    <date year="2005" month="December"/>
4710  </front>
4711  <seriesInfo name="BCP" value="13"/>
4712  <seriesInfo name="RFC" value="4288"/>
4715<reference anchor='RFC4395'>
4716  <front>
4717    <title>Guidelines and Registration Procedures for New URI Schemes</title>
4718    <author initials='T.' surname='Hansen' fullname='T. Hansen'>
4719      <organization>AT&amp;T Laboratories</organization>
4720      <address>
4721        <email></email>
4722      </address>
4723    </author>
4724    <author initials='T.' surname='Hardie' fullname='T. Hardie'>
4725      <organization>Qualcomm, Inc.</organization>
4726      <address>
4727        <email></email>
4728      </address>
4729    </author>
4730    <author initials='L.' surname='Masinter' fullname='L. Masinter'>
4731      <organization>Adobe Systems</organization>
4732      <address>
4733        <email></email>
4734      </address>
4735    </author>
4736    <date year='2006' month='February' />
4737  </front>
4738  <seriesInfo name='BCP' value='115' />
4739  <seriesInfo name='RFC' value='4395' />
4742<reference anchor='RFC4559'>
4743  <front>
4744    <title>SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows</title>
4745    <author initials='K.' surname='Jaganathan' fullname='K. Jaganathan'/>
4746    <author initials='L.' surname='Zhu' fullname='L. Zhu'/>
4747    <author initials='J.' surname='Brezak' fullname='J. Brezak'/>
4748    <date year='2006' month='June' />
4749  </front>
4750  <seriesInfo name='RFC' value='4559' />
4753<reference anchor='RFC5226'>
4754  <front>
4755    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
4756    <author initials='T.' surname='Narten' fullname='T. Narten'>
4757      <organization>IBM</organization>
4758      <address><email></email></address>
4759    </author>
4760    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
4761      <organization>Google</organization>
4762      <address><email></email></address>
4763    </author>
4764    <date year='2008' month='May' />
4765  </front>
4766  <seriesInfo name='BCP' value='26' />
4767  <seriesInfo name='RFC' value='5226' />
4770<reference anchor="RFC5322">
4771  <front>
4772    <title>Internet Message Format</title>
4773    <author initials="P." surname="Resnick" fullname="P. Resnick">
4774      <organization>Qualcomm Incorporated</organization>
4775    </author>
4776    <date year="2008" month="October"/>
4777  </front>
4778  <seriesInfo name="RFC" value="5322"/>
4781<reference anchor="RFC6265">
4782  <front>
4783    <title>HTTP State Management Mechanism</title>
4784    <author initials="A." surname="Barth" fullname="Adam Barth">
4785      <organization abbrev="U.C. Berkeley">
4786        University of California, Berkeley
4787      </organization>
4788      <address><email></email></address>
4789    </author>
4790    <date year="2011" month="April" />
4791  </front>
4792  <seriesInfo name="RFC" value="6265"/>
4795<!--<reference anchor='BCP97'>
4796  <front>
4797    <title>Handling Normative References to Standards-Track Documents</title>
4798    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
4799      <address>
4800        <email></email>
4801      </address>
4802    </author>
4803    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
4804      <organization>MIT</organization>
4805      <address>
4806        <email></email>
4807      </address>
4808    </author>
4809    <date year='2007' month='June' />
4810  </front>
4811  <seriesInfo name='BCP' value='97' />
4812  <seriesInfo name='RFC' value='4897' />
4815<reference anchor="Kri2001" target="">
4816  <front>
4817    <title>HTTP Cookies: Standards, Privacy, and Politics</title>
4818    <author initials="D." surname="Kristol" fullname="David M. Kristol"/>
4819    <date year="2001" month="November"/>
4820  </front>
4821  <seriesInfo name="ACM Transactions on Internet Technology" value="Vol. 1, #2"/>
4824<reference anchor="Spe" target="">
4825  <front>
4826    <title>Analysis of HTTP Performance Problems</title>
4827    <author initials="S." surname="Spero" fullname="Simon E. Spero"/>
4828    <date/>
4829  </front>
4832<reference anchor="Tou1998" target="">
4833  <front>
4834  <title>Analysis of HTTP Performance</title>
4835  <author initials="J." surname="Touch" fullname="Joe Touch">
4836    <organization>USC/Information Sciences Institute</organization>
4837    <address><email></email></address>
4838  </author>
4839  <author initials="J." surname="Heidemann" fullname="John Heidemann">
4840    <organization>USC/Information Sciences Institute</organization>
4841    <address><email></email></address>
4842  </author>
4843  <author initials="K." surname="Obraczka" fullname="Katia Obraczka">
4844    <organization>USC/Information Sciences Institute</organization>
4845    <address><email></email></address>
4846  </author>
4847  <date year="1998" month="Aug"/>
4848  </front>
4849  <seriesInfo name="ISI Research Report" value="ISI/RR-98-463"/>
4850  <annotation>(original report dated Aug. 1996)</annotation>
4856<section title="HTTP Version History" anchor="compatibility">
4858   HTTP has been in use by the World-Wide Web global information initiative
4859   since 1990. The first version of HTTP, later referred to as HTTP/0.9,
4860   was a simple protocol for hypertext data transfer across the Internet
4861   with only a single request method (GET) and no metadata.
4862   HTTP/1.0, as defined by <xref target="RFC1945"/>, added a range of request
4863   methods and MIME-like messaging that could include metadata about the data
4864   transferred and modifiers on the request/response semantics. However,
4865   HTTP/1.0 did not sufficiently take into consideration the effects of
4866   hierarchical proxies, caching, the need for persistent connections, or
4867   name-based virtual hosts. The proliferation of incompletely-implemented
4868   applications calling themselves "HTTP/1.0" further necessitated a
4869   protocol version change in order for two communicating applications
4870   to determine each other's true capabilities.
4873   HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent
4874   requirements that enable reliable implementations, adding only
4875   those new features that will either be safely ignored by an HTTP/1.0
4876   recipient or only sent when communicating with a party advertising
4877   conformance with HTTP/1.1.
4880   It is beyond the scope of a protocol specification to mandate
4881   conformance with previous versions. HTTP/1.1 was deliberately
4882   designed, however, to make supporting previous versions easy.
4883   We would expect a general-purpose HTTP/1.1 server to understand
4884   any valid request in the format of HTTP/1.0 and respond appropriately
4885   with an HTTP/1.1 message that only uses features understood (or
4886   safely ignored) by HTTP/1.0 clients.  Likewise, we would expect
4887   an HTTP/1.1 client to understand any valid HTTP/1.0 response.
4890   Since HTTP/0.9 did not support header fields in a request,
4891   there is no mechanism for it to support name-based virtual
4892   hosts (selection of resource by inspection of the Host header
4893   field).  Any server that implements name-based virtual hosts
4894   ought to disable support for HTTP/0.9.  Most requests that
4895   appear to be HTTP/0.9 are, in fact, badly constructed HTTP/1.x
4896   requests wherein a buggy client failed to properly encode
4897   linear whitespace found in a URI reference and placed in
4898   the request-target.
4901<section title="Changes from HTTP/1.0" anchor="changes.from.1.0">
4903   This section summarizes major differences between versions HTTP/1.0
4904   and HTTP/1.1.
4907<section title="Multi-homed Web Servers" anchor="">
4909   The requirements that clients and servers support the Host header
4910   field (<xref target=""/>), report an error if it is
4911   missing from an HTTP/1.1 request, and accept absolute URIs (<xref target="request-target"/>)
4912   are among the most important changes defined by HTTP/1.1.
4915   Older HTTP/1.0 clients assumed a one-to-one relationship of IP
4916   addresses and servers; there was no other established mechanism for
4917   distinguishing the intended server of a request than the IP address
4918   to which that request was directed. The Host header field was
4919   introduced during the development of HTTP/1.1 and, though it was
4920   quickly implemented by most HTTP/1.0 browsers, additional requirements
4921   were placed on all HTTP/1.1 requests in order to ensure complete
4922   adoption.  At the time of this writing, most HTTP-based services
4923   are dependent upon the Host header field for targeting requests.
4927<section title="Keep-Alive Connections" anchor="compatibility.with.http.1.0.persistent.connections">
4929   In HTTP/1.0, each connection is established by the client prior to the
4930   request and closed by the server after sending the response. However, some
4931   implementations implement the explicitly negotiated ("Keep-Alive") version
4932   of persistent connections described in <xref x:sec="19.7.1" x:fmt="of"
4933   target="RFC2068"/>.
4936   Some clients and servers might wish to be compatible with these previous
4937   approaches to persistent connections, by explicitly negotiating for them
4938   with a "Connection: keep-alive" request header field. However, some
4939   experimental implementations of HTTP/1.0 persistent connections are faulty;
4940   for example, if a HTTP/1.0 proxy server doesn't understand Connection, it
4941   will erroneously forward that header to the next inbound server, which
4942   would result in a hung connection.
4945   One attempted solution was the introduction of a Proxy-Connection header,
4946   targeted specifically at proxies. In practice, this was also unworkable,
4947   because proxies are often deployed in multiple layers, bringing about the
4948   same problem discussed above.
4951   As a result, clients are encouraged not to send the Proxy-Connection header
4952   in any requests.
4955   Clients are also encouraged to consider the use of Connection: keep-alive
4956   in requests carefully; while they can enable persistent connections with
4957   HTTP/1.0 servers, clients using them need will need to monitor the
4958   connection for "hung" requests (which indicate that the client ought stop
4959   sending the header), and this mechanism ought not be used by clients at all
4960   when a proxy is being used.
4965<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
4967  Clarify that the string "HTTP" in the HTTP-version ABFN production is case
4968  sensitive. Restrict the version numbers to be single digits due to the fact
4969  that implementations are known to handle multi-digit version numbers
4970  incorrectly.
4971  (<xref target="http.version"/>)
4974  Update use of abs_path production from RFC 1808 to the path-absolute + query
4975  components of RFC 3986. State that the asterisk form is allowed for the OPTIONS
4976  request method only.
4977  (<xref target="request-target"/>)
4980  Require that invalid whitespace around field-names be rejected.
4981  (<xref target="header.fields"/>)
4984  Rules about implicit linear whitespace between certain grammar productions
4985  have been removed; now whitespace is only allowed where specifically
4986  defined in the ABNF.
4987  (<xref target="whitespace"/>)
4990  The NUL octet is no longer allowed in comment and quoted-string
4991  text. The quoted-pair rule no longer allows escaping control characters other than HTAB.
4992  Non-ASCII content in header fields and reason phrase has been obsoleted and
4993  made opaque (the TEXT rule was removed).
4994  (<xref target="field.components"/>)
4997  Empty list elements in list productions have been deprecated.
4998  (<xref target="abnf.extension"/>)
5001  Require recipients to handle bogus Content-Length header fields as errors.
5002  (<xref target="message.body"/>)
5005  Remove reference to non-existent identity transfer-coding value tokens.
5006  (Sections <xref format="counter" target="message.body"/> and
5007  <xref format="counter" target="transfer.codings"/>)
5010  Clarification that the chunk length does not include the count of the octets
5011  in the chunk header and trailer. Furthermore disallowed line folding
5012  in chunk extensions, and deprecate their use.
5013  (<xref target="chunked.encoding"/>)
5016  Registration of Transfer Codings now requires IETF Review
5017  (<xref target="transfer.coding.registry"/>)
5020  Remove hard limit of two connections per server.
5021  Remove requirement to retry a sequence of requests as long it was idempotent.
5022  Remove requirements about when servers are allowed to close connections
5023  prematurely.
5024  (<xref target="persistent.practical"/>)
5027  Remove requirement to retry requests under certain cirumstances when the
5028  server prematurely closes the connection.
5029  (<xref target="message.transmission.requirements"/>)
5032  Change ABNF productions for header fields to only define the field value.
5033  (<xref target="header.field.definitions"/>)
5036  Clarify exactly when close connection options must be sent.
5037  (<xref target="header.connection"/>)
5040  Define the semantics of the "Upgrade" header field in responses other than
5041  101 (this was incorporated from <xref target="RFC2817"/>).
5042  (<xref target="header.upgrade"/>)
5046<section title="Changes from RFC 2817" anchor="changes.from.rfc.2817">
5048  Registration of Upgrade tokens now requires IETF Review
5049  (<xref target="upgrade.token.registry"/>)
5054<?BEGININC p1-messaging.abnf-appendix ?>
5055<section xmlns:x="" title="Collected ABNF" anchor="collected.abnf">
5057<artwork type="abnf" name="p1-messaging.parsed-abnf">
5058<x:ref>BWS</x:ref> = OWS
5060<x:ref>Connection</x:ref> = *( "," OWS ) connection-token *( OWS "," [ OWS
5061 connection-token ] )
5062<x:ref>Content-Length</x:ref> = 1*DIGIT
5064<x:ref>HTTP-message</x:ref> = start-line *( header-field CRLF ) CRLF [ message-body
5065 ]
5066<x:ref>HTTP-name</x:ref> = %x48.54.54.50 ; HTTP
5067<x:ref>HTTP-version</x:ref> = HTTP-name "/" DIGIT "." DIGIT
5068<x:ref>Host</x:ref> = uri-host [ ":" port ]
5070<x:ref>OWS</x:ref> = *( SP / HTAB )
5072<x:ref>RWS</x:ref> = 1*( SP / HTAB )
5074<x:ref>TE</x:ref> = [ ( "," / t-codings ) *( OWS "," [ OWS t-codings ] ) ]
5075<x:ref>Trailer</x:ref> = *( "," OWS ) field-name *( OWS "," [ OWS field-name ] )
5076<x:ref>Transfer-Encoding</x:ref> = *( "," OWS ) transfer-coding *( OWS "," [ OWS
5077 transfer-coding ] )
5079<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [RFC3986], Section 4.1&gt;
5080<x:ref>Upgrade</x:ref> = *( "," OWS ) protocol *( OWS "," [ OWS protocol ] )
5082<x:ref>Via</x:ref> = *( "," OWS ) received-protocol RWS received-by [ RWS comment ]
5083 *( OWS "," [ OWS received-protocol RWS received-by [ RWS comment ] ]
5084 )
5086<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
5087<x:ref>attribute</x:ref> = token
5088<x:ref>authority</x:ref> = &lt;authority, defined in [RFC3986], Section 3.2&gt;
5090<x:ref>chunk</x:ref> = chunk-size [ chunk-ext ] CRLF chunk-data CRLF
5091<x:ref>chunk-data</x:ref> = 1*OCTET
5092<x:ref>chunk-ext</x:ref> = *( ";" chunk-ext-name [ "=" chunk-ext-val ] )
5093<x:ref>chunk-ext-name</x:ref> = token
5094<x:ref>chunk-ext-val</x:ref> = token / quoted-str-nf
5095<x:ref>chunk-size</x:ref> = 1*HEXDIG
5096<x:ref>chunked-body</x:ref> = *chunk last-chunk trailer-part CRLF
5097<x:ref>comment</x:ref> = "(" *( ctext / quoted-cpair / comment ) ")"
5098<x:ref>connection-token</x:ref> = token
5099<x:ref>ctext</x:ref> = OWS / %x21-27 ; '!'-'''
5100 / %x2A-5B ; '*'-'['
5101 / %x5D-7E ; ']'-'~'
5102 / obs-text
5104<x:ref>field-content</x:ref> = *( HTAB / SP / VCHAR / obs-text )
5105<x:ref>field-name</x:ref> = token
5106<x:ref>field-value</x:ref> = *( field-content / obs-fold )
5108<x:ref>header-field</x:ref> = field-name ":" OWS field-value BWS
5109<x:ref>http-URI</x:ref> = "http://" authority path-abempty [ "?" query ]
5110<x:ref>https-URI</x:ref> = "https://" authority path-abempty [ "?" query ]
5112<x:ref>last-chunk</x:ref> = 1*"0" [ chunk-ext ] CRLF
5114<x:ref>message-body</x:ref> = *OCTET
5115<x:ref>method</x:ref> = token
5117<x:ref>obs-fold</x:ref> = CRLF ( SP / HTAB )
5118<x:ref>obs-text</x:ref> = %x80-FF
5120<x:ref>partial-URI</x:ref> = relative-part [ "?" query ]
5121<x:ref>path-abempty</x:ref> = &lt;path-abempty, defined in [RFC3986], Section 3.3&gt;
5122<x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in [RFC3986], Section 3.3&gt;
5123<x:ref>port</x:ref> = &lt;port, defined in [RFC3986], Section 3.2.3&gt;
5124<x:ref>protocol</x:ref> = protocol-name [ "/" protocol-version ]
5125<x:ref>protocol-name</x:ref> = token
5126<x:ref>protocol-version</x:ref> = token
5127<x:ref>pseudonym</x:ref> = token
5129<x:ref>qdtext</x:ref> = OWS / "!" / %x23-5B ; '#'-'['
5130 / %x5D-7E ; ']'-'~'
5131 / obs-text
5132<x:ref>qdtext-nf</x:ref> = HTAB / SP / "!" / %x23-5B ; '#'-'['
5133 / %x5D-7E ; ']'-'~'
5134 / obs-text
5135<x:ref>query</x:ref> = &lt;query, defined in [RFC3986], Section 3.4&gt;
5136<x:ref>quoted-cpair</x:ref> = "\" ( HTAB / SP / VCHAR / obs-text )
5137<x:ref>quoted-pair</x:ref> = "\" ( HTAB / SP / VCHAR / obs-text )
5138<x:ref>quoted-str-nf</x:ref> = DQUOTE *( qdtext-nf / quoted-pair ) DQUOTE
5139<x:ref>quoted-string</x:ref> = DQUOTE *( qdtext / quoted-pair ) DQUOTE
5140<x:ref>qvalue</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
5142<x:ref>reason-phrase</x:ref> = *( HTAB / SP / VCHAR / obs-text )
5143<x:ref>received-by</x:ref> = ( uri-host [ ":" port ] ) / pseudonym
5144<x:ref>received-protocol</x:ref> = [ protocol-name "/" ] protocol-version
5145<x:ref>relative-part</x:ref> = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;
5146<x:ref>request-line</x:ref> = method SP request-target SP HTTP-version CRLF
5147<x:ref>request-target</x:ref> = "*" / absolute-URI / ( path-absolute [ "?" query ] )
5148 / authority
5150<x:ref>special</x:ref> = "(" / ")" / "&lt;" / "&gt;" / "@" / "," / ";" / ":" / "\" /
5151 DQUOTE / "/" / "[" / "]" / "?" / "=" / "{" / "}"
5152<x:ref>start-line</x:ref> = request-line / status-line
5153<x:ref>status-code</x:ref> = 3DIGIT
5154<x:ref>status-line</x:ref> = HTTP-version SP status-code SP reason-phrase CRLF
5156<x:ref>t-codings</x:ref> = "trailers" / ( transfer-extension [ te-params ] )
5157<x:ref>tchar</x:ref> = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*" / "+" / "-" / "." /
5158 "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
5159<x:ref>te-ext</x:ref> = OWS ";" OWS token [ "=" word ]
5160<x:ref>te-params</x:ref> = OWS ";" OWS "q=" qvalue *te-ext
5161<x:ref>token</x:ref> = 1*tchar
5162<x:ref>trailer-part</x:ref> = *( header-field CRLF )
5163<x:ref>transfer-coding</x:ref> = "chunked" / "compress" / "deflate" / "gzip" /
5164 transfer-extension
5165<x:ref>transfer-extension</x:ref> = token *( OWS ";" OWS transfer-parameter )
5166<x:ref>transfer-parameter</x:ref> = attribute BWS "=" BWS value
5168<x:ref>uri-host</x:ref> = &lt;host, defined in [RFC3986], Section 3.2.2&gt;
5170<x:ref>value</x:ref> = word
5172<x:ref>word</x:ref> = token / quoted-string
5175<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
5176; Connection defined but not used
5177; Content-Length defined but not used
5178; HTTP-message defined but not used
5179; Host defined but not used
5180; TE defined but not used
5181; Trailer defined but not used
5182; Transfer-Encoding defined but not used
5183; URI-reference defined but not used
5184; Upgrade defined but not used
5185; Via defined but not used
5186; chunked-body defined but not used
5187; http-URI defined but not used
5188; https-URI defined but not used
5189; partial-URI defined but not used
5190; special defined but not used
5192<?ENDINC p1-messaging.abnf-appendix ?>
5194<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
5196<section title="Since RFC 2616">
5198  Extracted relevant partitions from <xref target="RFC2616"/>.
5202<section title="Since draft-ietf-httpbis-p1-messaging-00">
5204  Closed issues:
5205  <list style="symbols">
5206    <t>
5207      <eref target=""/>:
5208      "HTTP Version should be case sensitive"
5209      (<eref target=""/>)
5210    </t>
5211    <t>
5212      <eref target=""/>:
5213      "'unsafe' characters"
5214      (<eref target=""/>)
5215    </t>
5216    <t>
5217      <eref target=""/>:
5218      "Chunk Size Definition"
5219      (<eref target=""/>)
5220    </t>
5221    <t>
5222      <eref target=""/>:
5223      "Message Length"
5224      (<eref target=""/>)
5225    </t>
5226    <t>
5227      <eref target=""/>:
5228      "Media Type Registrations"
5229      (<eref target=""/>)
5230    </t>
5231    <t>
5232      <eref target=""/>:
5233      "URI includes query"
5234      (<eref target=""/>)
5235    </t>
5236    <t>
5237      <eref target=""/>:
5238      "No close on 1xx responses"
5239      (<eref target=""/>)
5240    </t>
5241    <t>
5242      <eref target=""/>:
5243      "Remove 'identity' token references"
5244      (<eref target=""/>)
5245    </t>
5246    <t>
5247      <eref target=""/>:
5248      "Import query BNF"
5249    </t>
5250    <t>
5251      <eref target=""/>:
5252      "qdtext BNF"
5253    </t>
5254    <t>
5255      <eref target=""/>:
5256      "Normative and Informative references"
5257    </t>
5258    <t>
5259      <eref target=""/>:
5260      "RFC2606 Compliance"
5261    </t>
5262    <t>
5263      <eref target=""/>:
5264      "RFC977 reference"
5265    </t>
5266    <t>
5267      <eref target=""/>:
5268      "RFC1700 references"
5269    </t>
5270    <t>
5271      <eref target=""/>:
5272      "inconsistency in date format explanation"
5273    </t>
5274    <t>
5275      <eref target=""/>:
5276      "Date reference typo"
5277    </t>
5278    <t>
5279      <eref target=""/>:
5280      "Informative references"
5281    </t>
5282    <t>
5283      <eref target=""/>:
5284      "ISO-8859-1 Reference"
5285    </t>
5286    <t>
5287      <eref target=""/>:
5288      "Normative up-to-date references"
5289    </t>
5290  </list>
5293  Other changes:
5294  <list style="symbols">
5295    <t>
5296      Update media type registrations to use RFC4288 template.
5297    </t>
5298    <t>
5299      Use names of RFC4234 core rules DQUOTE and HTAB,
5300      fix broken ABNF for chunk-data
5301      (work in progress on <eref target=""/>)
5302    </t>
5303  </list>
5307<section title="Since draft-ietf-httpbis-p1-messaging-01">
5309  Closed issues:
5310  <list style="symbols">
5311    <t>
5312      <eref target=""/>:
5313      "Bodies on GET (and other) requests"
5314    </t>
5315    <t>
5316      <eref target=""/>:
5317      "Updating to RFC4288"
5318    </t>
5319    <t>
5320      <eref target=""/>:
5321      "Status Code and Reason Phrase"
5322    </t>
5323    <t>
5324      <eref target=""/>:
5325      "rel_path not used"
5326    </t>
5327  </list>
5330  Ongoing work on ABNF conversion (<eref target=""/>):
5331  <list style="symbols">
5332    <t>
5333      Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" ->
5334      "trailer-part").
5335    </t>
5336    <t>
5337      Avoid underscore character in rule names ("http_URL" ->
5338      "http-URL", "abs_path" -> "path-absolute").
5339    </t>
5340    <t>
5341      Add rules for terms imported from URI spec ("absoluteURI", "authority",
5342      "path-absolute", "port", "query", "relativeURI", "host) &mdash; these will
5343      have to be updated when switching over to RFC3986.
5344    </t>
5345    <t>
5346      Synchronize core rules with RFC5234.
5347    </t>
5348    <t>
5349      Get rid of prose rules that span multiple lines.
5350    </t>
5351    <t>
5352      Get rid of unused rules LOALPHA and UPALPHA.
5353    </t>
5354    <t>
5355      Move "Product Tokens" section (back) into Part 1, as "token" is used
5356      in the definition of the Upgrade header field.
5357    </t>
5358    <t>
5359      Add explicit references to BNF syntax and rules imported from other parts of the specification.
5360    </t>
5361    <t>
5362      Rewrite prose rule "token" in terms of "tchar", rewrite prose rule "TEXT".
5363    </t>
5364  </list>
5368<section title="Since draft-ietf-httpbis-p1-messaging-02" anchor="changes.since.02">
5370  Closed issues:
5371  <list style="symbols">
5372    <t>
5373      <eref target=""/>:
5374      "HTTP-date vs. rfc1123-date"
5375    </t>
5376    <t>
5377      <eref target=""/>:
5378      "WS in quoted-pair"
5379    </t>
5380  </list>
5383  Ongoing work on IANA Message Header Field Registration (<eref target=""/>):
5384  <list style="symbols">
5385    <t>
5386      Reference RFC 3984, and update header field registrations for headers defined
5387      in this document.
5388    </t>
5389  </list>
5392  Ongoing work on ABNF conversion (<eref target=""/>):
5393  <list style="symbols">
5394    <t>
5395      Replace string literals when the string really is case-sensitive (HTTP-version).
5396    </t>
5397  </list>
5401<section title="Since draft-ietf-httpbis-p1-messaging-03" anchor="changes.since.03">
5403  Closed issues:
5404  <list style="symbols">
5405    <t>
5406      <eref target=""/>:
5407      "Connection closing"
5408    </t>
5409    <t>
5410      <eref target=""/>:
5411      "Move registrations and registry information to IANA Considerations"
5412    </t>
5413    <t>
5414      <eref target=""/>:
5415      "need new URL for PAD1995 reference"
5416    </t>
5417    <t>
5418      <eref target=""/>:
5419      "IANA Considerations: update HTTP URI scheme registration"
5420    </t>
5421    <t>
5422      <eref target=""/>:
5423      "Cite HTTPS URI scheme definition"
5424    </t>
5425    <t>
5426      <eref target=""/>:
5427      "List-type headers vs Set-Cookie"
5428    </t>
5429  </list>
5432  Ongoing work on ABNF conversion (<eref target=""/>):
5433  <list style="symbols">
5434    <t>
5435      Replace string literals when the string really is case-sensitive (HTTP-Date).
5436    </t>
5437    <t>
5438      Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.
5439    </t>
5440  </list>
5444<section title="Since draft-ietf-httpbis-p1-messaging-04" anchor="changes.since.04">
5446  Closed issues:
5447  <list style="symbols">
5448    <t>
5449      <eref target=""/>:
5450      "Out-of-date reference for URIs"
5451    </t>
5452    <t>
5453      <eref target=""/>:
5454      "RFC 2822 is updated by RFC 5322"
5455    </t>
5456  </list>
5459  Ongoing work on ABNF conversion (<eref target=""/>):
5460  <list style="symbols">
5461    <t>
5462      Use "/" instead of "|" for alternatives.
5463    </t>
5464    <t>
5465      Get rid of RFC822 dependency; use RFC5234 plus extensions instead.
5466    </t>
5467    <t>
5468      Only reference RFC 5234's core rules.
5469    </t>
5470    <t>
5471      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
5472      whitespace ("OWS") and required whitespace ("RWS").
5473    </t>
5474    <t>
5475      Rewrite ABNFs to spell out whitespace rules, factor out
5476      header field value format definitions.
5477    </t>
5478  </list>
5482<section title="Since draft-ietf-httpbis-p1-messaging-05" anchor="changes.since.05">
5484  Closed issues:
5485  <list style="symbols">
5486    <t>
5487      <eref target=""/>:
5488      "Header LWS"
5489    </t>
5490    <t>
5491      <eref target=""/>:
5492      "Sort 1.3 Terminology"
5493    </t>
5494    <t>
5495      <eref target=""/>:
5496      "RFC2047 encoded words"
5497    </t>
5498    <t>
5499      <eref target=""/>:
5500      "Character Encodings in TEXT"
5501    </t>
5502    <t>
5503      <eref target=""/>:
5504      "Line Folding"
5505    </t>
5506    <t>
5507      <eref target=""/>:
5508      "OPTIONS * and proxies"
5509    </t>
5510    <t>
5511      <eref target=""/>:
5512      "reason-phrase BNF"
5513    </t>
5514    <t>
5515      <eref target=""/>:
5516      "Use of TEXT"
5517    </t>
5518    <t>
5519      <eref target=""/>:
5520      "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
5521    </t>
5522    <t>
5523      <eref target=""/>:
5524      "RFC822 reference left in discussion of date formats"
5525    </t>
5526  </list>
5529  Final work on ABNF conversion (<eref target=""/>):
5530  <list style="symbols">
5531    <t>
5532      Rewrite definition of list rules, deprecate empty list elements.
5533    </t>
5534    <t>
5535      Add appendix containing collected and expanded ABNF.
5536    </t>
5537  </list>
5540  Other changes:
5541  <list style="symbols">
5542    <t>
5543      Rewrite introduction; add mostly new Architecture Section.
5544    </t>
5545    <t>
5546      Move definition of quality values from Part 3 into Part 1;
5547      make TE request header field grammar independent of accept-params (defined in Part 3).
5548    </t>
5549  </list>
5553<section title="Since draft-ietf-httpbis-p1-messaging-06" anchor="changes.since.06">
5555  Closed issues:
5556  <list style="symbols">
5557    <t>
5558      <eref target=""/>:
5559      "base for numeric protocol elements"
5560    </t>
5561    <t>
5562      <eref target=""/>:
5563      "comment ABNF"
5564    </t>
5565  </list>
5568  Partly resolved issues:
5569  <list style="symbols">
5570    <t>
5571      <eref target=""/>:
5572      "205 Bodies" (took out language that implied that there might be
5573      methods for which a request body MUST NOT be included)
5574    </t>
5575    <t>
5576      <eref target=""/>:
5577      "editorial improvements around HTTP-date"
5578    </t>
5579  </list>
5583<section title="Since draft-ietf-httpbis-p1-messaging-07" anchor="changes.since.07">
5585  Closed issues:
5586  <list style="symbols">
5587    <t>
5588      <eref target=""/>:
5589      "Repeating single-value headers"
5590    </t>
5591    <t>
5592      <eref target=""/>:
5593      "increase connection limit"
5594    </t>
5595    <t>
5596      <eref target=""/>:
5597      "IP addresses in URLs"
5598    </t>
5599    <t>
5600      <eref target=""/>:
5601      "take over HTTP Upgrade Token Registry"
5602    </t>
5603    <t>
5604      <eref target=""/>:
5605      "CR and LF in chunk extension values"
5606    </t>
5607    <t>
5608      <eref target=""/>:
5609      "HTTP/0.9 support"
5610    </t>
5611    <t>
5612      <eref target=""/>:
5613      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
5614    </t>
5615    <t>
5616      <eref target=""/>:
5617      "move definitions of gzip/deflate/compress to part 1"
5618    </t>
5619    <t>
5620      <eref target=""/>:
5621      "disallow control characters in quoted-pair"
5622    </t>
5623  </list>
5626  Partly resolved issues:
5627  <list style="symbols">
5628    <t>
5629      <eref target=""/>:
5630      "update IANA requirements wrt Transfer-Coding values" (add the
5631      IANA Considerations subsection)
5632    </t>
5633  </list>
5637<section title="Since draft-ietf-httpbis-p1-messaging-08" anchor="changes.since.08">
5639  Closed issues:
5640  <list style="symbols">
5641    <t>
5642      <eref target=""/>:
5643      "header parsing, treatment of leading and trailing OWS"
5644    </t>
5645  </list>
5648  Partly resolved issues:
5649  <list style="symbols">
5650    <t>
5651      <eref target=""/>:
5652      "Placement of 13.5.1 and 13.5.2"
5653    </t>
5654    <t>
5655      <eref target=""/>:
5656      "use of term "word" when talking about header structure"
5657    </t>
5658  </list>
5662<section title="Since draft-ietf-httpbis-p1-messaging-09" anchor="changes.since.09">
5664  Closed issues:
5665  <list style="symbols">
5666    <t>
5667      <eref target=""/>:
5668      "Clarification of the term 'deflate'"
5669    </t>
5670    <t>
5671      <eref target=""/>:
5672      "OPTIONS * and proxies"
5673    </t>
5674    <t>
5675      <eref target=""/>:
5676      "MIME-Version not listed in P1, general header fields"
5677    </t>
5678    <t>
5679      <eref target=""/>:
5680      "IANA registry for content/transfer encodings"
5681    </t>
5682    <t>
5683      <eref target=""/>:
5684      "Case-sensitivity of HTTP-date"
5685    </t>
5686    <t>
5687      <eref target=""/>:
5688      "use of term "word" when talking about header structure"
5689    </t>
5690  </list>
5693  Partly resolved issues:
5694  <list style="symbols">
5695    <t>
5696      <eref target=""/>:
5697      "Term for the requested resource's URI"
5698    </t>
5699  </list>
5703<section title="Since draft-ietf-httpbis-p1-messaging-10" anchor="changes.since.10">
5705  Closed issues:
5706  <list style="symbols">
5707    <t>
5708      <eref target=""/>:
5709      "Connection Closing"
5710    </t>
5711    <t>
5712      <eref target=""/>:
5713      "Delimiting messages with multipart/byteranges"
5714    </t>
5715    <t>
5716      <eref target=""/>:
5717      "Handling multiple Content-Length headers"
5718    </t>
5719    <t>
5720      <eref target=""/>:
5721      "Clarify entity / representation / variant terminology"
5722    </t>
5723    <t>
5724      <eref target=""/>:
5725      "consider removing the 'changes from 2068' sections"
5726    </t>
5727  </list>
5730  Partly resolved issues:
5731  <list style="symbols">
5732    <t>
5733      <eref target=""/>:
5734      "HTTP(s) URI scheme definitions"
5735    </t>
5736  </list>
5740<section title="Since draft-ietf-httpbis-p1-messaging-11" anchor="changes.since.11">
5742  Closed issues:
5743  <list style="symbols">
5744    <t>
5745      <eref target=""/>:
5746      "Trailer requirements"
5747    </t>
5748    <t>
5749      <eref target=""/>:
5750      "Text about clock requirement for caches belongs in p6"
5751    </t>
5752    <t>
5753      <eref target=""/>:
5754      "effective request URI: handling of missing host in HTTP/1.0"
5755    </t>
5756    <t>
5757      <eref target=""/>:
5758      "confusing Date requirements for clients"
5759    </t>
5760  </list>
5763  Partly resolved issues:
5764  <list style="symbols">
5765    <t>
5766      <eref target=""/>:
5767      "Handling multiple Content-Length headers"
5768    </t>
5769  </list>
5773<section title="Since draft-ietf-httpbis-p1-messaging-12" anchor="changes.since.12">
5775  Closed issues:
5776  <list style="symbols">
5777    <t>
5778      <eref target=""/>:
5779      "RFC2145 Normative"
5780    </t>
5781    <t>
5782      <eref target=""/>:
5783      "HTTP(s) URI scheme definitions" (tune the requirements on userinfo)
5784    </t>
5785    <t>
5786      <eref target=""/>:
5787      "define 'transparent' proxy"
5788    </t>
5789    <t>
5790      <eref target=""/>:
5791      "Header Classification"
5792    </t>
5793    <t>
5794      <eref target=""/>:
5795      "Is * usable as a request-uri for new methods?"
5796    </t>
5797    <t>
5798      <eref target=""/>:
5799      "Migrate Upgrade details from RFC2817"
5800    </t>
5801    <t>
5802      <eref target=""/>:
5803      "untangle ABNFs for header fields"
5804    </t>
5805    <t>
5806      <eref target=""/>:
5807      "update RFC 2109 reference"
5808    </t>
5809  </list>
5813<section title="Since draft-ietf-httpbis-p1-messaging-13" anchor="changes.since.13">
5815  Closed issues:
5816  <list style="symbols">
5817    <t>
5818      <eref target=""/>:
5819      "Allow is not in 13.5.2"
5820    </t>
5821    <t>
5822      <eref target=""/>:
5823      "Handling multiple Content-Length headers"
5824    </t>
5825    <t>
5826      <eref target=""/>:
5827      "untangle ABNFs for header fields"
5828    </t>
5829    <t>
5830      <eref target=""/>:
5831      "Content-Length ABNF broken"
5832    </t>
5833  </list>
5837<section title="Since draft-ietf-httpbis-p1-messaging-14" anchor="changes.since.14">
5839  Closed issues:
5840  <list style="symbols">
5841    <t>
5842      <eref target=""/>:
5843      "HTTP-version should be redefined as fixed length pair of DIGIT . DIGIT"
5844    </t>
5845    <t>
5846      <eref target=""/>:
5847      "Recommend minimum sizes for protocol elements"
5848    </t>
5849    <t>
5850      <eref target=""/>:
5851      "Set expectations around buffering"
5852    </t>
5853    <t>
5854      <eref target=""/>:
5855      "Considering messages in isolation"
5856    </t>
5857  </list>
5861<section title="Since draft-ietf-httpbis-p1-messaging-15" anchor="changes.since.15">
5863  Closed issues:
5864  <list style="symbols">
5865    <t>
5866      <eref target=""/>:
5867      "DNS Spoofing / DNS Binding advice"
5868    </t>
5869    <t>
5870      <eref target=""/>:
5871      "move RFCs 2145, 2616, 2817 to Historic status"
5872    </t>
5873    <t>
5874      <eref target=""/>:
5875      "\-escaping in quoted strings"
5876    </t>
5877    <t>
5878      <eref target=""/>:
5879      "'Close' should be reserved in the HTTP header field registry"
5880    </t>
5881  </list>
5885<section title="Since draft-ietf-httpbis-p1-messaging-16" anchor="changes.since.16">
5887  Closed issues:
5888  <list style="symbols">
5889    <t>
5890      <eref target=""/>:
5891      "Document HTTP's error-handling philosophy"
5892    </t>
5893    <t>
5894      <eref target=""/>:
5895      "Explain header registration"
5896    </t>
5897    <t>
5898      <eref target=""/>:
5899      "Revise Acknowledgements Sections"
5900    </t>
5901    <t>
5902      <eref target=""/>:
5903      "Retrying Requests"
5904    </t>
5905    <t>
5906      <eref target=""/>:
5907      "Closing the connection on server error"
5908    </t>
5909  </list>
5913<section title="Since draft-ietf-httpbis-p1-messaging-17" anchor="changes.since.17">
5915  Closed issues:
5916  <list style="symbols">
5917    <t>
5918      <eref target=""/>:
5919      "Clarify 'User Agent'"
5920    </t>
5921    <t>
5922      <eref target=""/>:
5923      "Define non-final responses"
5924    </t>
5925    <t>
5926      <eref target=""/>:
5927      "intended maturity level vs normative references"
5928    </t>
5929    <t>
5930      <eref target=""/>:
5931      "Intermediary rewriting of queries"
5932    </t>
5933    <t>
5934      <eref target=""/>:
5935      "Proxy-Connection and Keep-Alive"
5936    </t>
5937  </list>
5941<section title="Since draft-ietf-httpbis-p1-messaging-18" anchor="changes.since.18">
5943  Closed issues:
5944  <list style="symbols">
5945    <t>
5946      <eref target=""/>:
5947      "Misplaced text on connection handling in p2"
5948    </t>
5949    <t>
5950      <eref target=""/>:
5951      "wording of line folding rule"
5952    </t>
5953    <t>
5954      <eref target=""/>:
5955      "chunk-extensions"
5956    </t>
5957    <t>
5958      <eref target=""/>:
5959      "make IANA policy definitions consistent"
5960    </t>
5961  </list>
Note: See TracBrowser for help on using the repository browser.