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

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

Consolidate request-target under message routing. Simplify the
sections on Request Line and Status Line, since what they contain
is defined elsewhere.

Change request-target size limit to request-line size limit, since
that is how it is implemented in practice.

Add SHOULDs for error handling when the method is too long or
embedded whitespace is sent in the request-target.

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 247.3 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>
1121<iref primary="true" item="method"/>
1122<t anchor="method">
1123   The method token indicates the request method to be performed on the
1124   target resource. The request method is case-sensitive.
1126<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="method"/>
1127  <x:ref>method</x:ref>         = <x:ref>token</x:ref>
1130   The methods defined by this specification can be found in
1131   &method;, along with information regarding the HTTP method registry
1132   and considerations for defining new methods.
1134<iref item="request-target"/>
1136   The request-target identifies the target resource upon which to apply
1137   the request, as defined in <xref target="request-target"/>.
1140   No whitespace is allowed inside the method, request-target, and
1141   protocol version.  Hence, recipients typically parse the request-line
1142   into its component parts by splitting on the SP characters.
1145   Unfortunately, some user agents fail to properly encode hypertext
1146   references that have embedded whitespace, sending the characters
1147   directly instead of properly percent-encoding the disallowed characters.
1148   Recipients of an invalid request-line &SHOULD; respond with either a
1149   400 (Bad Request) error or a 301 (Moved Permanently) redirect with the
1150   request-target properly encoded.  Recipients &SHOULD-NOT; attempt to
1151   autocorrect and then process the request without a redirect, since the
1152   invalid request-line might be deliberately crafted to bypass
1153   security filters along the request chain.
1156   HTTP does not place a pre-defined limit on the length of a request-line.
1157   A server that receives a method longer than any that it implements
1158   &SHOULD; respond with either a 404 (Not Allowed), if it is an origin
1159   server, or a 501 (Not Implemented) status code.
1160   A server &MUST; be prepared to receive URIs of unbounded length and
1161   respond with the 414 (URI Too Long) status code if the received
1162   request-target would be longer than the server wishes to handle
1163   (see &status-414;).
1166   Various ad-hoc limitations on request-line length are found in practice.
1167   It is &RECOMMENDED; that all HTTP senders and recipients support, at a
1168   minimum, request-line lengths of up to 8000 octets.
1172<section title="Status Line" anchor="status.line">
1173  <x:anchor-alias value="response"/>
1174  <x:anchor-alias value="status-line"/>
1176   The first line of a response message is the status-line, consisting
1177   of the protocol version, a space (SP), the status code, another space,
1178   a possibly-empty textual phrase describing the status code, and
1179   ending with CRLF.
1181<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-line"/>
1182  <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>
1185<t anchor="status-code">
1186   The status-code element is a 3-digit integer result code of the attempt to
1187   understand and satisfy the request. See &status-code-reasonphr; for
1188   further information, such as the list of status codes defined by this
1189   specification, the IANA registry, and considerations for new status codes.
1191<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="status-code"/>
1192  <x:ref>status-code</x:ref>    = 3<x:ref>DIGIT</x:ref>
1195<t anchor="reason-phrase">  
1196   The reason-phrase element exists for the sole purpose of providing a
1197   textual description associated with the numeric status code, mostly
1198   out of deference to earlier Internet application protocols that were more
1199   frequently used with interactive text clients. A client &SHOULD; ignore
1200   the reason-phrase content.
1202<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="reason-phrase"/>
1203  <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> )
1208<section title="Header Fields" anchor="header.fields">
1209  <x:anchor-alias value="header-field"/>
1210  <x:anchor-alias value="field-content"/>
1211  <x:anchor-alias value="field-name"/>
1212  <x:anchor-alias value="field-value"/>
1213  <x:anchor-alias value="obs-fold"/>
1215   Each HTTP header field consists of a case-insensitive field name
1216   followed by a colon (":"), optional whitespace, and the field value.
1218<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"/>
1219  <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>
1220  <x:ref>field-name</x:ref>     = <x:ref>token</x:ref>
1221  <x:ref>field-value</x:ref>    = *( <x:ref>field-content</x:ref> / <x:ref>obs-fold</x:ref> )
1222  <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> )
1223  <x:ref>obs-fold</x:ref>       = <x:ref>CRLF</x:ref> ( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1224                 ; obsolete line folding
1225                 ; see <xref target="field.parsing"/>
1228   The field-name token labels the corresponding field-value as having the
1229   semantics defined by that header field.  For example, the Date header field
1230   is defined in &header-date; as containing the origination
1231   timestamp for the message in which it appears.
1234   HTTP header fields are fully extensible: there is no limit on the
1235   introduction of new field names, each presumably defining new semantics,
1236   or on the number of header fields used in a given message.  Existing
1237   fields are defined in each part of this specification and in many other
1238   specifications outside the standards process.
1239   New header fields can be introduced without changing the protocol version
1240   if their defined semantics allow them to be safely ignored by recipients
1241   that do not recognize them.
1244   New HTTP header fields &SHOULD; be registered with IANA according
1245   to the procedures in &cons-new-header-fields;.
1246   Unrecognized header fields &MUST; be forwarded by a proxy unless the
1247   field-name is listed in the Connection header field
1248   (<xref target="header.connection"/>) or the proxy is specifically
1249   configured to block or otherwise transform such fields.
1250   Unrecognized header fields &SHOULD; be ignored by other recipients.
1253   The order in which header fields with differing field names are
1254   received is not significant. However, it is "good practice" to send
1255   header fields that contain control data first, such as Host on
1256   requests and Date on responses, so that implementations can decide
1257   when not to handle a message as early as possible.  A server &MUST;
1258   wait until the entire header section is received before interpreting
1259   a request message, since later header fields might include conditionals,
1260   authentication credentials, or deliberately misleading duplicate
1261   header fields that would impact request processing.
1264   Multiple header fields with the same field name &MUST-NOT; be
1265   sent in a message unless the entire field value for that
1266   header field is defined as a comma-separated list [i.e., #(values)].
1267   Multiple header fields with the same field name can be combined into
1268   one "field-name: field-value" pair, without changing the semantics of the
1269   message, by appending each subsequent field value to the combined
1270   field value in order, separated by a comma. The order in which
1271   header fields with the same field name are received is therefore
1272   significant to the interpretation of the combined field value;
1273   a proxy &MUST-NOT; change the order of these field values when
1274   forwarding a message.
1277  <t>
1278   <x:h>Note:</x:h> The "Set-Cookie" header field as implemented in
1279   practice can occur multiple times, but does not use the list syntax, and
1280   thus cannot be combined into a single line (<xref target="RFC6265"/>). (See Appendix A.2.3 of <xref target="Kri2001"/>
1281   for details.) Also note that the Set-Cookie2 header field specified in
1282   <xref target="RFC2965"/> does not share this problem.
1283  </t>
1286<section title="Whitespace" anchor="whitespace">
1287<t anchor="rule.LWS">
1288   This specification uses three rules to denote the use of linear
1289   whitespace: OWS (optional whitespace), RWS (required whitespace), and
1290   BWS ("bad" whitespace).
1292<t anchor="rule.OWS">
1293   The OWS rule is used where zero or more linear whitespace octets might
1294   appear. OWS &SHOULD; either not be produced or be produced as a single
1295   SP. Multiple OWS octets that occur within field-content &SHOULD; either
1296   be replaced with a single SP or transformed to all SP octets (each
1297   octet other than SP replaced with SP) before interpreting the field value
1298   or forwarding the message downstream.
1300<t anchor="rule.RWS">
1301   RWS is used when at least one linear whitespace octet is required to
1302   separate field tokens. RWS &SHOULD; be produced as a single SP.
1303   Multiple RWS octets that occur within field-content &SHOULD; either
1304   be replaced with a single SP or transformed to all SP octets before
1305   interpreting the field value or forwarding the message downstream.
1307<t anchor="rule.BWS">
1308   BWS is used where the grammar allows optional whitespace for historical
1309   reasons but senders &SHOULD-NOT; produce it in messages. HTTP/1.1
1310   recipients &MUST; accept such bad optional whitespace and remove it before
1311   interpreting the field value or forwarding the message downstream.
1313<t anchor="rule.whitespace">
1314  <x:anchor-alias value="BWS"/>
1315  <x:anchor-alias value="OWS"/>
1316  <x:anchor-alias value="RWS"/>
1318<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"/>
1319  <x:ref>OWS</x:ref>            = *( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1320                 ; "optional" whitespace
1321  <x:ref>RWS</x:ref>            = 1*( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1322                 ; "required" whitespace
1323  <x:ref>BWS</x:ref>            = <x:ref>OWS</x:ref>
1324                 ; "bad" whitespace
1328<section title="Field Parsing" anchor="field.parsing">
1330   No whitespace is allowed between the header field-name and colon.
1331   In the past, differences in the handling of such whitespace have led to
1332   security vulnerabilities in request routing and response handling.
1333   Any received request message that contains whitespace between a header
1334   field-name and colon &MUST; be rejected with a response code of 400
1335   (Bad Request).  A proxy &MUST; remove any such whitespace from a response
1336   message before forwarding the message downstream.
1339   A field value &MAY; be preceded by optional whitespace (OWS); a single SP is
1340   preferred. The field value does not include any leading or trailing white
1341   space: OWS occurring before the first non-whitespace octet of the
1342   field value or after the last non-whitespace octet of the field value
1343   is ignored and &SHOULD; be removed before further processing (as this does
1344   not change the meaning of the header field).
1347   Historically, HTTP header field values could be extended over multiple
1348   lines by preceding each extra line with at least one space or horizontal
1349   tab (obs-fold). This specification deprecates such line
1350   folding except within the message/http media type
1351   (<xref target=""/>).
1352   HTTP senders &MUST-NOT; produce messages that include line folding
1353   (i.e., that contain any field-value that matches the obs-fold rule) unless
1354   the message is intended for packaging within the message/http media type.
1355   HTTP recipients &SHOULD; accept line folding and replace any embedded
1356   obs-fold whitespace with either a single SP or a matching number of SP
1357   octets (to avoid buffer copying) prior to interpreting the field value or
1358   forwarding the message downstream.
1361   Historically, HTTP has allowed field content with text in the ISO-8859-1
1362   <xref target="ISO-8859-1"/> character encoding and supported other
1363   character sets only through use of <xref target="RFC2047"/> encoding.
1364   In practice, most HTTP header field values use only a subset of the
1365   US-ASCII character encoding <xref target="USASCII"/>. Newly defined
1366   header fields &SHOULD; limit their field values to US-ASCII octets.
1367   Recipients &SHOULD; treat other (obs-text) octets in field content as
1368   opaque data.
1372<section title="Field Length" anchor="field.length">
1374   HTTP does not place a pre-defined limit on the length of header fields,
1375   either in isolation or as a set. A server &MUST; be prepared to receive
1376   request header fields of unbounded length and respond with a 4xx status
1377   code if the received header field(s) would be longer than the server wishes
1378   to handle.
1381   A client that receives response headers that are longer than it wishes to
1382   handle can only treat it as a server error.
1385   Various ad-hoc limitations on header length are found in practice. It is
1386   &RECOMMENDED; that all HTTP senders and recipients support messages whose
1387   combined header fields have 4000 or more octets.
1391<section title="Field value components" anchor="field.components">
1392<t anchor="rule.token.separators">
1393  <x:anchor-alias value="tchar"/>
1394  <x:anchor-alias value="token"/>
1395  <x:anchor-alias value="special"/>
1396  <x:anchor-alias value="word"/>
1397   Many HTTP/1.1 header field values consist of words (token or quoted-string)
1398   separated by whitespace or special characters. These special characters
1399   &MUST; be in a quoted string to be used within a parameter value (as defined
1400   in <xref target="transfer.codings"/>).
1402<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"/>
1403  <x:ref>word</x:ref>           = <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref>
1405  <x:ref>token</x:ref>          = 1*<x:ref>tchar</x:ref>
1407  IMPORTANT: when editing "tchar" make sure that "special" is updated accordingly!!!
1408 -->
1409  <x:ref>tchar</x:ref>          = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*"
1410                 / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
1411                 / <x:ref>DIGIT</x:ref> / <x:ref>ALPHA</x:ref>
1412                 ; any <x:ref>VCHAR</x:ref>, except <x:ref>special</x:ref>
1414  <x:ref>special</x:ref>        = "(" / ")" / "&lt;" / ">" / "@" / ","
1415                 / ";" / ":" / "\" / DQUOTE / "/" / "["
1416                 / "]" / "?" / "=" / "{" / "}"
1418<t anchor="rule.quoted-string">
1419  <x:anchor-alias value="quoted-string"/>
1420  <x:anchor-alias value="qdtext"/>
1421  <x:anchor-alias value="obs-text"/>
1422   A string of text is parsed as a single word if it is quoted using
1423   double-quote marks.
1425<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"/>
1426  <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>
1427  <x:ref>qdtext</x:ref>         = <x:ref>OWS</x:ref> / %x21 / %x23-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1428  <x:ref>obs-text</x:ref>       = %x80-FF
1430<t anchor="rule.quoted-pair">
1431  <x:anchor-alias value="quoted-pair"/>
1432   The backslash octet ("\") can be used as a single-octet
1433   quoting mechanism within quoted-string constructs:
1435<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-pair"/>
1436  <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> )
1439   Recipients that process the value of the quoted-string &MUST; handle a
1440   quoted-pair as if it were replaced by the octet following the backslash.
1443   Senders &SHOULD-NOT; escape octets in quoted-strings that do not require
1444   escaping (i.e., other than DQUOTE and the backslash octet).
1446<t anchor="rule.comment">
1447  <x:anchor-alias value="comment"/>
1448  <x:anchor-alias value="ctext"/>
1449   Comments can be included in some HTTP header fields by surrounding
1450   the comment text with parentheses. Comments are only allowed in
1451   fields containing "comment" as part of their field value definition.
1453<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="comment"/><iref primary="true" item="Grammar" subitem="ctext"/>
1454  <x:ref>comment</x:ref>        = "(" *( <x:ref>ctext</x:ref> / <x:ref>quoted-cpair</x:ref> / <x:ref>comment</x:ref> ) ")"
1455  <x:ref>ctext</x:ref>          = <x:ref>OWS</x:ref> / %x21-27 / %x2A-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1457<t anchor="rule.quoted-cpair">
1458  <x:anchor-alias value="quoted-cpair"/>
1459   The backslash octet ("\") can be used as a single-octet
1460   quoting mechanism within comment constructs:
1462<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-cpair"/>
1463  <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> )
1466   Senders &SHOULD-NOT; escape octets in comments that do not require escaping
1467   (i.e., other than the backslash octet "\" and the parentheses "(" and ")").
1471<section title="ABNF list extension: #rule" anchor="abnf.extension">
1473  A #rule extension to the ABNF rules of <xref target="RFC5234"/> is used to
1474  improve readability in the definitions of some header field values.
1477  A construct "#" is defined, similar to "*", for defining comma-delimited
1478  lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating
1479  at least &lt;n&gt; and at most &lt;m&gt; elements, each separated by a single
1480  comma (",") and optional whitespace (OWS).   
1483  Thus,
1484</preamble><artwork type="example">
1485  1#element =&gt; element *( OWS "," OWS element )
1488  and:
1489</preamble><artwork type="example">
1490  #element =&gt; [ 1#element ]
1493  and for n &gt;= 1 and m &gt; 1:
1494</preamble><artwork type="example">
1495  &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
1498  For compatibility with legacy list rules, recipients &SHOULD; accept empty
1499  list elements. In other words, consumers would follow the list productions:
1501<figure><artwork type="example">
1502  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
1504  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
1507  Note that empty elements do not contribute to the count of elements present,
1508  though.
1511  For example, given these ABNF productions:
1513<figure><artwork type="example">
1514  example-list      = 1#example-list-elmt
1515  example-list-elmt = token ; see <xref target="field.components"/>
1518  Then these are valid values for example-list (not including the double
1519  quotes, which are present for delimitation only):
1521<figure><artwork type="example">
1522  "foo,bar"
1523  "foo ,bar,"
1524  "foo , ,bar,charlie   "
1527  But these values would be invalid, as at least one non-empty element is
1528  required:
1530<figure><artwork type="example">
1531  ""
1532  ","
1533  ",   ,"
1536  <xref target="collected.abnf"/> shows the collected ABNF, with the list rules
1537  expanded as explained above.
1542<section title="Message Body" anchor="message.body">
1543  <x:anchor-alias value="message-body"/>
1545   The message body (if any) of an HTTP message is used to carry the
1546   payload body of that request or response.  The message body is
1547   identical to the payload body unless a transfer coding has been
1548   applied, as described in <xref target="header.transfer-encoding"/>.
1550<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-body"/>
1551  <x:ref>message-body</x:ref> = *OCTET
1554   The rules for when a message body is allowed in a message differ for
1555   requests and responses.
1558   The presence of a message body in a request is signaled by a
1559   a Content-Length or Transfer-Encoding header field.
1560   Request message framing is independent of method semantics,
1561   even if the method does not define any use for a message body.
1564   The presence of a message body in a response depends on both
1565   the request method to which it is responding and the response
1566   status code (<xref target="status-code"/>).
1567   Responses to the HEAD request method never include a message body
1568   because the associated response header fields (e.g., Transfer-Encoding,
1569   Content-Length, etc.) only indicate what their values would have been
1570   if the request method had been GET.
1571   Successful (2xx) responses to CONNECT switch to tunnel mode instead of
1572   having a message body.
1573   All 1xx (Informational), 204 (No Content), and 304 (Not Modified)
1574   responses &MUST-NOT; include a message body.
1575   All other responses do include a message body, although the body
1576   &MAY; be of zero length.
1579<section title="Transfer-Encoding" anchor="header.transfer-encoding">
1580  <iref primary="true" item="Transfer-Encoding header field" x:for-anchor=""/>
1581  <iref primary="true" item="Header Fields" subitem="Transfer-Encoding" x:for-anchor=""/>
1582  <x:anchor-alias value="Transfer-Encoding"/>
1584   When one or more transfer codings are applied to a payload body in order
1585   to form the message body, a Transfer-Encoding header field &MUST; be sent
1586   in the message and &MUST; contain the list of corresponding
1587   transfer-coding names in the same order that they were applied.
1588   Transfer codings are defined in <xref target="transfer.codings"/>.
1590<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Transfer-Encoding"/>
1591  <x:ref>Transfer-Encoding</x:ref> = 1#<x:ref>transfer-coding</x:ref>
1594   Transfer-Encoding is analogous to the Content-Transfer-Encoding field of
1595   MIME, which was designed to enable safe transport of binary data over a
1596   7-bit transport service (<xref target="RFC2045" x:fmt="," x:sec="6"/>).
1597   However, safe transport has a different focus for an 8bit-clean transfer
1598   protocol. In HTTP's case, Transfer-Encoding is primarily intended to
1599   accurately delimit a dynamically generated payload and to distinguish
1600   payload encodings that are only applied for transport efficiency or
1601   security from those that are characteristics of the target resource.
1604   The "chunked" transfer-coding (<xref target="chunked.encoding"/>)
1605   &MUST; be implemented by all HTTP/1.1 recipients because it plays a
1606   crucial role in delimiting messages when the payload body size is not
1607   known in advance.
1608   When the "chunked" transfer-coding is used, it &MUST; be the last
1609   transfer-coding applied to form the message body and &MUST-NOT;
1610   be applied more than once in a message body.
1611   If any transfer-coding is applied to a request payload body,
1612   the final transfer-coding applied &MUST; be "chunked".
1613   If any transfer-coding is applied to a response payload body, then either
1614   the final transfer-coding applied &MUST; be "chunked" or
1615   the message &MUST; be terminated by closing the connection.
1618   For example,
1619</preamble><artwork type="example">
1620  Transfer-Encoding: gzip, chunked
1622   indicates that the payload body has been compressed using the gzip
1623   coding and then chunked using the chunked coding while forming the
1624   message body.
1627   If more than one Transfer-Encoding header field is present in a message,
1628   the multiple field-values &MUST; be combined into one field-value,
1629   according to the algorithm defined in <xref target="header.fields"/>,
1630   before determining the message body length.
1633   Unlike Content-Encoding (&content-codings;), Transfer-Encoding is a
1634   property of the message, not of the payload, and thus &MAY; be added or
1635   removed by any implementation along the request/response chain.
1636   Additional information about the encoding parameters &MAY; be provided
1637   by other header fields not defined by this specification.
1640   Transfer-Encoding &MAY; be sent in a response to a HEAD request or in a
1641   304 response to a GET request, neither of which includes a message body,
1642   to indicate that the origin server would have applied a transfer coding
1643   to the message body if the request had been an unconditional GET.
1644   This indication is not required, however, because any recipient on
1645   the response chain (including the origin server) can remove transfer
1646   codings when they are not needed.
1649   Transfer-Encoding was added in HTTP/1.1.  It is generally assumed that
1650   implementations advertising only HTTP/1.0 support will not understand
1651   how to process a transfer-encoded payload.
1652   A client &MUST-NOT; send a request containing Transfer-Encoding unless it
1653   knows the server will handle HTTP/1.1 (or later) requests; such knowledge
1654   might be in the form of specific user configuration or by remembering the
1655   version of a prior received response.
1656   A server &MUST-NOT; send a response containing Transfer-Encoding unless
1657   the corresponding request indicates HTTP/1.1 (or later).
1660   A server that receives a request message with a transfer-coding it does
1661   not understand &SHOULD; respond with 501 (Not Implemented) and then
1662   close the connection.
1666<section title="Content-Length" anchor="header.content-length">
1667  <iref primary="true" item="Content-Length header field" x:for-anchor=""/>
1668  <iref primary="true" item="Header Fields" subitem="Content-Length" x:for-anchor=""/>
1669  <x:anchor-alias value="Content-Length"/>
1671   When a message does not have a Transfer-Encoding header field and the
1672   payload body length can be determined prior to being transferred, a
1673   Content-Length header field &SHOULD; be sent to indicate the length of the
1674   payload body that is either present as the message body, for requests
1675   and non-HEAD responses other than 304, or would have been present had
1676   the request been an unconditional GET.  The length is expressed as a
1677   decimal number of octets.
1679<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/>
1680  <x:ref>Content-Length</x:ref> = 1*<x:ref>DIGIT</x:ref>
1683   An example is
1685<figure><artwork type="example">
1686  Content-Length: 3495
1689   In the case of a response to a HEAD request, Content-Length indicates
1690   the size of the payload body (without any potential transfer-coding)
1691   that would have been sent had the request been a GET.
1692   In the case of a 304 (Not Modified) response to a GET request,
1693   Content-Length indicates the size of the payload body (without
1694   any potential transfer-coding) that would have been sent in a 200 (OK)
1695   response.
1698   HTTP's use of Content-Length is significantly different from how it is
1699   used in MIME, where it is an optional field used only within the
1700   "message/external-body" media-type.
1703   Any Content-Length field value greater than or equal to zero is valid.
1704   Since there is no predefined limit to the length of an HTTP payload,
1705   recipients &SHOULD; anticipate potentially large decimal numerals and
1706   prevent parsing errors due to integer conversion overflows
1707   (<xref target="attack.protocol.element.size.overflows"/>).
1710   If a message is received that has multiple Content-Length header fields
1711   (<xref target="header.content-length"/>) with field-values consisting
1712   of the same decimal value, or a single Content-Length header field with
1713   a field value containing a list of identical decimal values (e.g.,
1714   "Content-Length: 42, 42"), indicating that duplicate Content-Length
1715   header fields have been generated or combined by an upstream message
1716   processor, then the recipient &MUST; either reject the message as invalid
1717   or replace the duplicated field-values with a single valid Content-Length
1718   field containing that decimal value prior to determining the message body
1719   length.
1723<section title="Message Body Length" anchor="message.body.length">
1725   The length of a message body is determined by one of the following
1726   (in order of precedence):
1729  <list style="numbers">
1730    <x:lt><t>
1731     Any response to a HEAD request and any response with a status
1732     code of 100-199, 204, or 304 is always terminated by the first
1733     empty line after the header fields, regardless of the header
1734     fields present in the message, and thus cannot contain a message body.
1735    </t></x:lt>
1736    <x:lt><t>
1737     Any successful (2xx) response to a CONNECT request implies that the
1738     connection will become a tunnel immediately after the empty line that
1739     concludes the header fields.  A client &MUST; ignore any Content-Length
1740     or Transfer-Encoding header fields received in such a message.
1741    </t></x:lt>
1742    <x:lt><t>
1743     If a Transfer-Encoding header field is present
1744     and the "chunked" transfer-coding (<xref target="chunked.encoding"/>)
1745     is the final encoding, the message body length is determined by reading
1746     and decoding the chunked data until the transfer-coding indicates the
1747     data is complete.
1748    </t>
1749    <t>
1750     If a Transfer-Encoding header field is present in a response and the
1751     "chunked" transfer-coding is not the final encoding, the message body
1752     length is determined by reading the connection until it is closed by
1753     the server.
1754     If a Transfer-Encoding header field is present in a request and the
1755     "chunked" transfer-coding is not the final encoding, the message body
1756     length cannot be determined reliably; the server &MUST; respond with
1757     the 400 (Bad Request) status code and then close the connection.
1758    </t>
1759    <t>
1760     If a message is received with both a Transfer-Encoding header field
1761     and a Content-Length header field, the Transfer-Encoding overrides
1762     the Content-Length.
1763     Such a message might indicate an attempt to perform request or response
1764     smuggling (bypass of security-related checks on message routing or content)
1765     and thus ought to be handled as an error.  The provided Content-Length &MUST;
1766     be removed, prior to forwarding the message downstream, or replaced with
1767     the real message body length after the transfer-coding is decoded.
1768    </t></x:lt>
1769    <x:lt><t>
1770     If a message is received without Transfer-Encoding and with either
1771     multiple Content-Length header fields having differing field-values or
1772     a single Content-Length header field having an invalid value, then the
1773     message framing is invalid and &MUST; be treated as an error to
1774     prevent request or response smuggling.
1775     If this is a request message, the server &MUST; respond with
1776     a 400 (Bad Request) status code and then close the connection.
1777     If this is a response message received by a proxy, the proxy
1778     &MUST; discard the received response, send a 502 (Bad Gateway)
1779     status code as its downstream response, and then close the connection.
1780     If this is a response message received by a user-agent, it &MUST; be
1781     treated as an error by discarding the message and closing the connection.
1782    </t></x:lt>
1783    <x:lt><t>
1784     If a valid Content-Length header field
1785     is present without Transfer-Encoding, its decimal value defines the
1786     message body length in octets.  If the actual number of octets sent in
1787     the message is less than the indicated Content-Length, the recipient
1788     &MUST; consider the message to be incomplete and treat the connection
1789     as no longer usable.
1790     If the actual number of octets sent in the message is more than the indicated
1791     Content-Length, the recipient &MUST; only process the message body up to the
1792     field value's number of octets; the remainder of the message &MUST; either
1793     be discarded or treated as the next message in a pipeline.  For the sake of
1794     robustness, a user-agent &MAY; attempt to detect and correct such an error
1795     in message framing if it is parsing the response to the last request on
1796     a connection and the connection has been closed by the server.
1797    </t></x:lt>
1798    <x:lt><t>
1799     If this is a request message and none of the above are true, then the
1800     message body length is zero (no message body is present).
1801    </t></x:lt>
1802    <x:lt><t>
1803     Otherwise, this is a response message without a declared message body
1804     length, so the message body length is determined by the number of octets
1805     received prior to the server closing the connection.
1806    </t></x:lt>
1807  </list>
1810   Since there is no way to distinguish a successfully completed,
1811   close-delimited message from a partially-received message interrupted
1812   by network failure, implementations &SHOULD; use encoding or
1813   length-delimited messages whenever possible.  The close-delimiting
1814   feature exists primarily for backwards compatibility with HTTP/1.0.
1817   A server &MAY; reject a request that contains a message body but
1818   not a Content-Length by responding with 411 (Length Required).
1821   Unless a transfer-coding other than "chunked" has been applied,
1822   a client that sends a request containing a message body &SHOULD;
1823   use a valid Content-Length header field if the message body length
1824   is known in advance, rather than the "chunked" encoding, since some
1825   existing services respond to "chunked" with a 411 (Length Required)
1826   status code even though they understand the chunked encoding.  This
1827   is typically because such services are implemented via a gateway that
1828   requires a content-length in advance of being called and the server
1829   is unable or unwilling to buffer the entire request before processing.
1832   A client that sends a request containing a message body &MUST; include a
1833   valid Content-Length header field if it does not know the server will
1834   handle HTTP/1.1 (or later) requests; such knowledge can be in the form
1835   of specific user configuration or by remembering the version of a prior
1836   received response.
1841<section anchor="incomplete.messages" title="Handling Incomplete Messages">
1843   Request messages that are prematurely terminated, possibly due to a
1844   cancelled connection or a server-imposed time-out exception, &MUST;
1845   result in closure of the connection; sending an HTTP/1.1 error response
1846   prior to closing the connection is &OPTIONAL;.
1849   Response messages that are prematurely terminated, usually by closure
1850   of the connection prior to receiving the expected number of octets or by
1851   failure to decode a transfer-encoded message body, &MUST; be recorded
1852   as incomplete.  A response that terminates in the middle of the header
1853   block (before the empty line is received) cannot be assumed to convey the
1854   full semantics of the response and &MUST; be treated as an error.
1857   A message body that uses the chunked transfer encoding is
1858   incomplete if the zero-sized chunk that terminates the encoding has not
1859   been received.  A message that uses a valid Content-Length is incomplete
1860   if the size of the message body received (in octets) is less than the
1861   value given by Content-Length.  A response that has neither chunked
1862   transfer encoding nor Content-Length is terminated by closure of the
1863   connection, and thus is considered complete regardless of the number of
1864   message body octets received, provided that the header block was received
1865   intact.
1868   A user agent &MUST-NOT; render an incomplete response message body as if
1869   it were complete (i.e., some indication must be given to the user that an
1870   error occurred).  Cache requirements for incomplete responses are defined
1871   in &cache-incomplete;.
1874   A server &MUST; read the entire request message body or close
1875   the connection after sending its response, since otherwise the
1876   remaining data on a persistent connection would be misinterpreted
1877   as the next request.  Likewise,
1878   a client &MUST; read the entire response message body if it intends
1879   to reuse the same connection for a subsequent request.  Pipelining
1880   multiple requests on a connection is described in <xref target="pipelining"/>.
1884<section title="Message Parsing Robustness" anchor="message.robustness">
1886   Older HTTP/1.0 client implementations might send an extra CRLF
1887   after a POST request as a lame workaround for some early server
1888   applications that failed to read message body content that was
1889   not terminated by a line-ending. An HTTP/1.1 client &MUST-NOT;
1890   preface or follow a request with an extra CRLF.  If terminating
1891   the request message body with a line-ending is desired, then the
1892   client &MUST; include the terminating CRLF octets as part of the
1893   message body length.
1896   In the interest of robustness, servers &SHOULD; ignore at least one
1897   empty line received where a request-line is expected. In other words, if
1898   the server is reading the protocol stream at the beginning of a
1899   message and receives a CRLF first, it &SHOULD; ignore the CRLF.
1900   Likewise, although the line terminator for the start-line and header
1901   fields is the sequence CRLF, we recommend that recipients recognize a
1902   single LF as a line terminator and ignore any CR.
1905   When a server listening only for HTTP request messages, or processing
1906   what appears from the start-line to be an HTTP request message,
1907   receives a sequence of octets that does not match the HTTP-message
1908   grammar aside from the robustness exceptions listed above, the
1909   server &MUST; respond with an HTTP/1.1 400 (Bad Request) response. 
1914<section title="Transfer Codings" anchor="transfer.codings">
1915  <x:anchor-alias value="transfer-coding"/>
1916  <x:anchor-alias value="transfer-extension"/>
1918   Transfer-coding values are used to indicate an encoding
1919   transformation that has been, can be, or might need to be applied to a
1920   payload body in order to ensure "safe transport" through the network.
1921   This differs from a content coding in that the transfer-coding is a
1922   property of the message rather than a property of the representation
1923   that is being transferred.
1925<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-coding"/><iref primary="true" item="Grammar" subitem="transfer-extension"/>
1926  <x:ref>transfer-coding</x:ref>    = "chunked" ; <xref target="chunked.encoding"/>
1927                     / "compress" ; <xref target="compress.coding"/>
1928                     / "deflate" ; <xref target="deflate.coding"/>
1929                     / "gzip" ; <xref target="gzip.coding"/>
1930                     / <x:ref>transfer-extension</x:ref>
1931  <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> )
1933<t anchor="rule.parameter">
1934  <x:anchor-alias value="attribute"/>
1935  <x:anchor-alias value="transfer-parameter"/>
1936  <x:anchor-alias value="value"/>
1937   Parameters are in the form of attribute/value pairs.
1939<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"/>
1940  <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>
1941  <x:ref>attribute</x:ref>          = <x:ref>token</x:ref>
1942  <x:ref>value</x:ref>              = <x:ref>word</x:ref>
1945   All transfer-coding values are case-insensitive. HTTP/1.1 uses
1946   transfer-coding values in the TE header field (<xref target="header.te"/>) and in
1947   the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).
1950<section title="Chunked Transfer Coding" anchor="chunked.encoding">
1951  <iref item="chunked (Coding Format)"/>
1952  <iref item="Coding Format" subitem="chunked"/>
1953  <x:anchor-alias value="chunk"/>
1954  <x:anchor-alias value="chunked-body"/>
1955  <x:anchor-alias value="chunk-data"/>
1956  <x:anchor-alias value="chunk-ext"/>
1957  <x:anchor-alias value="chunk-ext-name"/>
1958  <x:anchor-alias value="chunk-ext-val"/>
1959  <x:anchor-alias value="chunk-size"/>
1960  <x:anchor-alias value="last-chunk"/>
1961  <x:anchor-alias value="trailer-part"/>
1962  <x:anchor-alias value="quoted-str-nf"/>
1963  <x:anchor-alias value="qdtext-nf"/>
1965   The chunked encoding modifies the body of a message in order to
1966   transfer it as a series of chunks, each with its own size indicator,
1967   followed by an &OPTIONAL; trailer containing header fields. This
1968   allows dynamically produced content to be transferred along with the
1969   information necessary for the recipient to verify that it has
1970   received the full message.
1972<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"/>
1973  <x:ref>chunked-body</x:ref>   = *<x:ref>chunk</x:ref>
1974                   <x:ref>last-chunk</x:ref>
1975                   <x:ref>trailer-part</x:ref>
1976                   <x:ref>CRLF</x:ref>
1978  <x:ref>chunk</x:ref>          = <x:ref>chunk-size</x:ref> [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
1979                   <x:ref>chunk-data</x:ref> <x:ref>CRLF</x:ref>
1980  <x:ref>chunk-size</x:ref>     = 1*<x:ref>HEXDIG</x:ref>
1981  <x:ref>last-chunk</x:ref>     = 1*("0") [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
1983  <x:ref>chunk-ext</x:ref>      = *( ";" <x:ref>chunk-ext-name</x:ref> [ "=" <x:ref>chunk-ext-val</x:ref> ] )
1984  <x:ref>chunk-ext-name</x:ref> = <x:ref>token</x:ref>
1985  <x:ref>chunk-ext-val</x:ref>  = <x:ref>token</x:ref> / <x:ref>quoted-str-nf</x:ref>
1986  <x:ref>chunk-data</x:ref>     = 1*<x:ref>OCTET</x:ref> ; a sequence of chunk-size octets
1987  <x:ref>trailer-part</x:ref>   = *( <x:ref>header-field</x:ref> <x:ref>CRLF</x:ref> )
1989  <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>
1990                 ; like <x:ref>quoted-string</x:ref>, but disallowing line folding
1991  <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>
1994   The chunk-size field is a string of hex digits indicating the size of
1995   the chunk-data in octets. The chunked encoding is ended by any chunk whose size is
1996   zero, followed by the trailer, which is terminated by an empty line.
1999   The trailer allows the sender to include additional HTTP header
2000   fields at the end of the message. The Trailer header field can be
2001   used to indicate which header fields are included in a trailer (see
2002   <xref target="header.trailer"/>).
2005   A server using chunked transfer-coding in a response &MUST-NOT; use the
2006   trailer for any header fields unless at least one of the following is
2007   true:
2008  <list style="numbers">
2009    <t>the request included a TE header field that indicates "trailers" is
2010     acceptable in the transfer-coding of the  response, as described in
2011     <xref target="header.te"/>; or,</t>
2013    <t>the trailer fields consist entirely of optional metadata, and the
2014    recipient could use the message (in a manner acceptable to the server where
2015    the field originated) without receiving it. In other words, the server that
2016    generated the header (often but not always the origin server) is willing to
2017    accept the possibility that the trailer fields might be silently discarded
2018    along the path to the client.</t>
2019  </list>
2022   This requirement prevents an interoperability failure when the
2023   message is being received by an HTTP/1.1 (or later) proxy and
2024   forwarded to an HTTP/1.0 recipient. It avoids a situation where
2025   conformance with the protocol would have necessitated a possibly
2026   infinite buffer on the proxy.
2029   A process for decoding the "chunked" transfer-coding
2030   can be represented in pseudo-code as:
2032<figure><artwork type="code">
2033  length := 0
2034  read chunk-size, chunk-ext (if any) and CRLF
2035  while (chunk-size &gt; 0) {
2036     read chunk-data and CRLF
2037     append chunk-data to decoded-body
2038     length := length + chunk-size
2039     read chunk-size and CRLF
2040  }
2041  read header-field
2042  while (header-field not empty) {
2043     append header-field to existing header fields
2044     read header-field
2045  }
2046  Content-Length := length
2047  Remove "chunked" from Transfer-Encoding
2050   All HTTP/1.1 applications &MUST; be able to receive and decode the
2051   "chunked" transfer-coding and &MUST; ignore chunk-ext extensions
2052   they do not understand.
2055   Use of chunk-ext extensions by senders is deprecated; they &SHOULD-NOT; be
2056   sent and definition of new chunk-extensions is discouraged.
2060<section title="Compression Codings" anchor="compression.codings">
2062   The codings defined below can be used to compress the payload of a
2063   message.
2066   <x:h>Note:</x:h> Use of program names for the identification of encoding formats
2067   is not desirable and is discouraged for future encodings. Their
2068   use here is representative of historical practice, not good
2069   design.
2072   <x:h>Note:</x:h> For compatibility with previous implementations of HTTP,
2073   applications &SHOULD; consider "x-gzip" and "x-compress" to be
2074   equivalent to "gzip" and "compress" respectively.
2077<section title="Compress Coding" anchor="compress.coding">
2078<iref item="compress (Coding Format)"/>
2079<iref item="Coding Format" subitem="compress"/>
2081   The "compress" format is produced by the common UNIX file compression
2082   program "compress". This format is an adaptive Lempel-Ziv-Welch
2083   coding (LZW).
2087<section title="Deflate Coding" anchor="deflate.coding">
2088<iref item="deflate (Coding Format)"/>
2089<iref item="Coding Format" subitem="deflate"/>
2091   The "deflate" format is defined as the "deflate" compression mechanism
2092   (described in <xref target="RFC1951"/>) used inside the "zlib"
2093   data format (<xref target="RFC1950"/>).
2096  <t>
2097    <x:h>Note:</x:h> Some incorrect implementations send the "deflate"
2098    compressed data without the zlib wrapper.
2099   </t>
2103<section title="Gzip Coding" anchor="gzip.coding">
2104<iref item="gzip (Coding Format)"/>
2105<iref item="Coding Format" subitem="gzip"/>
2107   The "gzip" format is produced by the file compression program
2108   "gzip" (GNU zip), as described in <xref target="RFC1952"/>. This format is a
2109   Lempel-Ziv coding (LZ77) with a 32 bit CRC.
2115<section title="Transfer Coding Registry" anchor="transfer.coding.registry">
2117   The HTTP Transfer Coding Registry defines the name space for the transfer
2118   coding names.
2121   Registrations &MUST; include the following fields:
2122   <list style="symbols">
2123     <t>Name</t>
2124     <t>Description</t>
2125     <t>Pointer to specification text</t>
2126   </list>
2129   Names of transfer codings &MUST-NOT; overlap with names of content codings
2130   (&content-codings;), unless the encoding transformation is identical (as it
2131   is the case for the compression codings defined in
2132   <xref target="compression.codings"/>).
2135   Values to be added to this name space require IETF Review (see
2136   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
2137   conform to the purpose of transfer coding defined in this section.
2140   The registry itself is maintained at
2141   <eref target=""/>.
2145<section title="TE" anchor="header.te">
2146  <iref primary="true" item="TE header field" x:for-anchor=""/>
2147  <iref primary="true" item="Header Fields" subitem="TE" x:for-anchor=""/>
2148  <x:anchor-alias value="TE"/>
2149  <x:anchor-alias value="t-codings"/>
2150  <x:anchor-alias value="te-params"/>
2151  <x:anchor-alias value="te-ext"/>
2153   The "TE" header field indicates what extension transfer-codings
2154   the client is willing to accept in the response, and whether or not it is
2155   willing to accept trailer fields in a chunked transfer-coding.
2158   Its value consists of the keyword "trailers" and/or a comma-separated
2159   list of extension transfer-coding names with optional accept
2160   parameters (as described in <xref target="transfer.codings"/>).
2162<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"/>
2163  <x:ref>TE</x:ref>        = #<x:ref>t-codings</x:ref>
2164  <x:ref>t-codings</x:ref> = "trailers" / ( <x:ref>transfer-extension</x:ref> [ <x:ref>te-params</x:ref> ] )
2165  <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> )
2166  <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> ]
2169   The presence of the keyword "trailers" indicates that the client is
2170   willing to accept trailer fields in a chunked transfer-coding, as
2171   defined in <xref target="chunked.encoding"/>. This keyword is reserved for use with
2172   transfer-coding values even though it does not itself represent a
2173   transfer-coding.
2176   Examples of its use are:
2178<figure><artwork type="example">
2179  TE: deflate
2180  TE:
2181  TE: trailers, deflate;q=0.5
2184   The TE header field only applies to the immediate connection.
2185   Therefore, the keyword &MUST; be supplied within a Connection header
2186   field (<xref target="header.connection"/>) whenever TE is present in an HTTP/1.1 message.
2189   A server tests whether a transfer-coding is acceptable, according to
2190   a TE field, using these rules:
2191  <list style="numbers">
2192    <x:lt>
2193      <t>The "chunked" transfer-coding is always acceptable. If the
2194         keyword "trailers" is listed, the client indicates that it is
2195         willing to accept trailer fields in the chunked response on
2196         behalf of itself and any downstream clients. The implication is
2197         that, if given, the client is stating that either all
2198         downstream clients are willing to accept trailer fields in the
2199         forwarded response, or that it will attempt to buffer the
2200         response on behalf of downstream recipients.
2201      </t><t>
2202         <x:h>Note:</x:h> HTTP/1.1 does not define any means to limit the size of a
2203         chunked response such that a client can be assured of buffering
2204         the entire response.</t>
2205    </x:lt>
2206    <x:lt>
2207      <t>If the transfer-coding being tested is one of the transfer-codings
2208         listed in the TE field, then it is acceptable unless it
2209         is accompanied by a qvalue of 0. (As defined in <xref target="quality.values"/>, a
2210         qvalue of 0 means "not acceptable".)</t>
2211    </x:lt>
2212    <x:lt>
2213      <t>If multiple transfer-codings are acceptable, then the
2214         acceptable transfer-coding with the highest non-zero qvalue is
2215         preferred.  The "chunked" transfer-coding always has a qvalue
2216         of 1.</t>
2217    </x:lt>
2218  </list>
2221   If the TE field-value is empty or if no TE field is present, the only
2222   acceptable transfer-coding is "chunked". A message with no transfer-coding is
2223   always acceptable.
2226<section title="Quality Values" anchor="quality.values">
2227  <x:anchor-alias value="qvalue"/>
2229   Both transfer codings (TE request header field, <xref target="header.te"/>)
2230   and content negotiation (&content.negotiation;) use short "floating point"
2231   numbers to indicate the relative importance ("weight") of various
2232   negotiable parameters.  A weight is normalized to a real number in
2233   the range 0 through 1, where 0 is the minimum and 1 the maximum
2234   value. If a parameter has a quality value of 0, then content with
2235   this parameter is "not acceptable" for the client. HTTP/1.1
2236   applications &MUST-NOT; generate more than three digits after the
2237   decimal point. User configuration of these values &SHOULD; also be
2238   limited in this fashion.
2240<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="qvalue"/>
2241  <x:ref>qvalue</x:ref>         = ( "0" [ "." 0*3<x:ref>DIGIT</x:ref> ] )
2242                 / ( "1" [ "." 0*3("0") ] )
2245  <t>
2246     <x:h>Note:</x:h> "Quality values" is a misnomer, since these values merely represent
2247     relative degradation in desired quality.
2248  </t>
2253<section title="Trailer" anchor="header.trailer">
2254  <iref primary="true" item="Trailer header field" x:for-anchor=""/>
2255  <iref primary="true" item="Header Fields" subitem="Trailer" x:for-anchor=""/>
2256  <x:anchor-alias value="Trailer"/>
2258   The "Trailer" header field indicates that the given set of
2259   header fields is present in the trailer of a message encoded with
2260   chunked transfer-coding.
2262<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Trailer"/>
2263  <x:ref>Trailer</x:ref> = 1#<x:ref>field-name</x:ref>
2266   An HTTP/1.1 message &SHOULD; include a Trailer header field in a
2267   message using chunked transfer-coding with a non-empty trailer. Doing
2268   so allows the recipient to know which header fields to expect in the
2269   trailer.
2272   If no Trailer header field is present, the trailer &SHOULD-NOT;  include
2273   any header fields. See <xref target="chunked.encoding"/> for restrictions on the use of
2274   trailer fields in a "chunked" transfer-coding.
2277   Message header fields listed in the Trailer header field &MUST-NOT;
2278   include the following header fields:
2279  <list style="symbols">
2280    <t>Transfer-Encoding</t>
2281    <t>Content-Length</t>
2282    <t>Trailer</t>
2283  </list>
2288<section title="Message Routing" anchor="message.routing">
2290   HTTP request message routing is determined by each client based on the
2291   target resource, the client's proxy configuration, and
2292   establishment or reuse of an inbound connection.  The corresponding
2293   response routing follows the same connection chain back to the client.
2296<section title="Identifying a Target Resource" anchor="target-resource">
2297  <iref primary="true" item="target resource"/>
2298  <iref primary="true" item="target URI"/>
2300   HTTP is used in a wide variety of applications, ranging from
2301   general-purpose computers to home appliances.  In some cases,
2302   communication options are hard-coded in a client's configuration.
2303   However, most HTTP clients rely on the same resource identification
2304   mechanism and configuration techniques as general-purpose Web browsers.
2307   HTTP communication is initiated by a user agent for some purpose.
2308   The purpose is a combination of request semantics, which are defined in
2309   <xref target="Part2"/>, and a target resource upon which to apply those
2310   semantics.  A URI reference (<xref target="uri"/>) is typically used as
2311   an identifier for the target resource, which a user agent would resolve to
2312   its absolute form in order to obtain the target URI.  The target URI
2313   excludes the reference's fragment identifier component, if any,
2314   since fragment identifiers are reserved for client-side processing
2315   (<xref target="RFC3986" x:fmt="," x:sec="3.5"/>).
2318   HTTP intermediaries obtain the request semantics and target URI
2319   from the request-line of an incoming request message.
2323<section title="Connecting Inbound" anchor="connecting.inbound">
2325   Once the target URI is determined, a client needs to decide whether
2326   a network request is necessary to accomplish the desired semantics and,
2327   if so, where that request is to be directed.
2330   If the client has a response cache and the request semantics can be
2331   satisfied by a cache (<xref target="Part6"/>), then the request is
2332   usually directed to the cache first.
2335   If the request is not satisfied by a cache, then a typical client will
2336   check its configuration to determine whether a proxy is to be used to
2337   satisfy the request.  Proxy configuration is implementation-dependent,
2338   but is often based on URI prefix matching, selective authority matching,
2339   or both, and the proxy itself is usually identified by an "http" or
2340   "https" URI.  If a proxy is applicable, the client connects inbound by
2341   establishing (or reusing) a connection to that proxy.
2344   If no proxy is applicable, a typical client will invoke a handler routine,
2345   usually specific to the target URI's scheme, to connect directly
2346   to an authority for the target resource.  How that is accomplished is
2347   dependent on the target URI scheme and defined by its associated
2348   specification, similar to how this specification defines origin server
2349   access for resolution of the "http" (<xref target="http.uri"/>) and
2350   "https" (<xref target="https.uri"/>) schemes.
2354<section title="Request Target" anchor="request-target">
2356   Once an inbound connection is obtained (<xref target="connections"/>),
2357   the client sends an HTTP request message (<xref target="http.message"/>)
2358   with a request-target derived from the target URI.
2359   There are four distinct formats for the request-target, depending on both
2360   the method being requested and whether the request is to a proxy.
2362<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-target"/>
2363  <x:ref>request-target</x:ref> = "*"
2364                 / <x:ref>absolute-URI</x:ref>
2365                 / ( <x:ref>path-absolute</x:ref> [ "?" <x:ref>query</x:ref> ] )
2366                 / <x:ref>authority</x:ref>
2368<t anchor="origin-form"><iref item="origin form (of request-target)"/>
2369   The most common form of request-target is that used when making
2370   a request to an origin server ("origin form") to access a resource
2371   identified by an "http" (<xref target="http.uri"/>) or
2372   "https" (<xref target="https.uri"/>) URI.
2373   In this case, the absolute path and query components of the URI
2374   &MUST; be transmitted as the request-target and the authority component
2375   (excluding any userinfo) &MUST; be transmitted in a Host header field.
2376   For example, a client wishing to retrieve a representation of the resource
2377   identified as
2379<figure><artwork x:indent-with="  ">
2383   directly from the origin server would open (or reuse) a TCP connection
2384   to port 80 of the host "" and send the lines:
2386<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2387GET /where?q=now HTTP/1.1
2391   followed by the remainder of the request. Note that the origin form
2392   of request-target always starts with an absolute path. If the target
2393   resource's URI path is empty, then an absolute path of "/" &MUST; be
2394   provided in the request-target.
2397   If the request-target is percent-encoded
2398   (<xref target="RFC3986" x:fmt="," x:sec="2.1"/>), the origin server
2399   &MUST; decode the request-target in order to
2400   properly interpret the request. Servers &SHOULD; respond to invalid
2401   request-targets with an appropriate status code.
2403<t anchor="absolute-URI-form"><iref item="absolute-URI form (of request-target)"/>
2404   The "absolute-URI" form of request-target is &REQUIRED; when the request
2405   is being made to a proxy.  The proxy is requested to either forward the
2406   request or service it from a valid cache, and then return the response.
2407   Note that the proxy &MAY; forward the request on to another proxy or
2408   directly to the server specified by the absolute-URI.
2409   In order to avoid request loops, a proxy that forwards requests to other
2410   proxies &MUST; be able to recognize and exclude all of its own server
2411   names, including any aliases, local variations, or literal IP addresses.
2412   An example request-line would be:
2414<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2415GET HTTP/1.1
2418   To allow for transition to absolute-URIs in all requests in future
2419   versions of HTTP, all HTTP/1.1 servers &MUST; accept the absolute-URI
2420   form in requests, even though HTTP/1.1 clients will only generate
2421   them in requests to proxies.
2424   If a proxy receives a host name that is not a fully qualified domain
2425   name, it &MAY; add its domain to the host name it received. If a proxy
2426   receives a fully qualified domain name, the proxy &MUST-NOT; change
2427   the host name.
2429<t anchor="authority-form"><iref item="authority form (of request-target)"/>
2430   The "authority form" of request-target, which &MUST-NOT; be used
2431   with any request method other than CONNECT, is used to establish a
2432   tunnel through one or more proxies (&CONNECT;).  For example,
2434<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2437<t anchor="asterix-form"><iref item="asterisk form (of request-target)"/>
2438   The asterisk ("*") form of request-target, which &MUST-NOT; be used
2439   with any request method other than OPTIONS, means that the request
2440   applies to the server as a whole (the listening process) rather than
2441   to a specific named resource at that server.  For example,
2443<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2444OPTIONS * HTTP/1.1
2447   If a proxy receives an OPTIONS request with an absolute-URI form of
2448   request-target in which the URI has an empty path and no query component,
2449   then the last proxy on the request chain &MUST; use a request-target
2450   of "*" when it forwards the request to the indicated origin server.
2453   For example, the request
2454</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2458  would be forwarded by the final proxy as
2459</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2460OPTIONS * HTTP/1.1
2464   after connecting to port 8001 of host "".
2468   A non-transforming proxy &MUST-NOT; rewrite the "path-absolute" and "query"
2469   parts of the received request-target when forwarding it to the next inbound
2470   server, except as noted above to replace a null path-absolute with "/" or
2471   "*".
2475<section title="Host" anchor="">
2476  <iref primary="true" item="Host header field" x:for-anchor=""/>
2477  <iref primary="true" item="Header Fields" subitem="Host" x:for-anchor=""/>
2478  <x:anchor-alias value="Host"/>
2480   The "Host" header field in a request provides the host and port
2481   information from the target resource's URI, enabling the origin
2482   server to distinguish between resources while servicing requests
2483   for multiple host names on a single IP address.  Since the Host
2484   field-value is critical information for handling a request, it
2485   &SHOULD; be sent as the first header field following the request-line.
2487<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Host"/>
2488  <x:ref>Host</x:ref> = <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ; <xref target="http.uri"/>
2491   A client &MUST; send a Host header field in all HTTP/1.1 request
2492   messages.  If the target resource's URI includes an authority
2493   component, then the Host field-value &MUST; be identical to that
2494   authority component after excluding any userinfo (<xref target="http.uri"/>).
2495   If the authority component is missing or undefined for the target
2496   resource's URI, then the Host header field &MUST; be sent with an
2497   empty field-value.
2500   For example, a GET request to the origin server for
2501   &lt;; would begin with:
2503<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
2504GET /pub/WWW/ HTTP/1.1
2508   The Host header field &MUST; be sent in an HTTP/1.1 request even
2509   if the request-target is in the form of an absolute-URI, since this
2510   allows the Host information to be forwarded through ancient HTTP/1.0
2511   proxies that might not have implemented Host.
2514   When an HTTP/1.1 proxy receives a request with a request-target in
2515   the form of an absolute-URI, the proxy &MUST; ignore the received
2516   Host header field (if any) and instead replace it with the host
2517   information of the request-target.  When a proxy forwards a request,
2518   it &MUST; generate the Host header field based on the received
2519   absolute-URI rather than the received Host.
2522   Since the Host header field acts as an application-level routing
2523   mechanism, it is a frequent target for malware seeking to poison
2524   a shared cache or redirect a request to an unintended server.
2525   An interception proxy is particularly vulnerable if it relies on
2526   the Host header field value for redirecting requests to internal
2527   servers, or for use as a cache key in a shared cache, without
2528   first verifying that the intercepted connection is targeting a
2529   valid IP address for that host.
2532   A server &MUST; respond with a 400 (Bad Request) status code to
2533   any HTTP/1.1 request message that lacks a Host header field and
2534   to any request message that contains more than one Host header field
2535   or a Host header field with an invalid field-value.
2538   See Sections <xref target="" format="counter"/>
2539   and <xref target="" format="counter"/>
2540   for other requirements relating to Host.
2544<section title="The Resource Identified by a Request" anchor="">
2546   The exact resource identified by an Internet request is determined by
2547   examining both the request-target and the Host header field.
2550   An origin server that does not allow resources to differ by the
2551   requested host &MAY; ignore the Host header field value when
2552   determining the resource identified by an HTTP/1.1 request. (But see
2553   <xref target=""/>
2554   for other requirements on Host support in HTTP/1.1.)
2557   An origin server that does differentiate resources based on the host
2558   requested (sometimes referred to as virtual hosts or vanity host
2559   names) &MUST; use the following rules for determining the requested
2560   resource on an HTTP/1.1 request:
2561  <list style="numbers">
2562    <t>If request-target is an absolute-URI, the host is part of the
2563     request-target. Any Host header field value in the request &MUST; be
2564     ignored.</t>
2565    <t>If the request-target is not an absolute-URI, and the request includes
2566     a Host header field, the host is determined by the Host header
2567     field value.</t>
2568    <t>If the host as determined by rule 1 or 2 is not a valid host on
2569     the server, the response &MUST; be a 400 (Bad Request) error message.</t>
2570  </list>
2573   Recipients of an HTTP/1.0 request that lacks a Host header field &MAY;
2574   attempt to use heuristics (e.g., examination of the URI path for
2575   something unique to a particular host) in order to determine what
2576   exact resource is being requested.
2580<section title="Effective Request URI" anchor="effective.request.uri">
2581  <iref primary="true" item="effective request URI"/>
2583   HTTP requests often do not carry the absolute URI (<xref target="RFC3986" x:fmt="," x:sec="4.3"/>)
2584   for the target resource; instead, the URI needs to be inferred from the
2585   request-target, Host header field, and connection context. The result of
2586   this process is called the "effective request URI".  The "target resource"
2587   is the resource identified by the effective request URI.
2590   If the request-target is an absolute-URI, then the effective request URI is
2591   the request-target.
2594   If the request-target uses the origin form or the asterisk form,
2595   and the Host header field is present, then the effective request URI is
2596   constructed by concatenating
2599  <list style="symbols">
2600    <t>
2601      the scheme name: "http" if the request was received over an insecure
2602      TCP connection, or "https" when received over a SSL/TLS-secured TCP
2603      connection,
2604    </t>
2605    <t>
2606      the octet sequence "://",
2607    </t>
2608    <t>
2609      the authority component, as specified in the Host header field
2610      (<xref target=""/>), and
2611    </t>
2612    <t>
2613      the request-target obtained from the request-line, unless the
2614      request-target is just the asterisk "*".
2615    </t>
2616  </list>
2619   If the request-target uses the origin form or the asterisk form,
2620   and the Host header field is not present, then the effective request URI is
2621   undefined.
2624   Otherwise, when request-target uses the authority form, the effective
2625   request URI is undefined.
2629   Example 1: the effective request URI for the message
2631<artwork type="example" x:indent-with="  ">
2632GET /pub/WWW/TheProject.html HTTP/1.1
2636  (received over an insecure TCP connection) is "http", plus "://", plus the
2637  authority component "", plus the request-target
2638  "/pub/WWW/TheProject.html", thus
2639  "".
2644   Example 2: the effective request URI for the message
2646<artwork type="example" x:indent-with="  ">
2647OPTIONS * HTTP/1.1
2651  (received over an SSL/TLS secured TCP connection) is "https", plus "://", plus the
2652  authority component "", thus "".
2656   Effective request URIs are compared using the rules described in
2657   <xref target="uri.comparison"/>, except that empty path components &MUST-NOT;
2658   be treated as equivalent to an absolute path of "/".
2662<section title="Associating a Response to a Request" anchor="">
2664   HTTP does not include a request identifier for associating a given
2665   request message with its corresponding one or more response messages.
2666   Hence, it relies on the order of response arrival to correspond exactly
2667   to the order in which requests are made on the same connection.
2668   More than one response message per request only occurs when one or more
2669   informational responses (1xx, see &status-1xx;) precede a final response
2670   to the same request.
2673   A client that uses persistent connections and sends more than one request
2674   per connection &MUST; maintain a list of outstanding requests in the
2675   order sent on that connection and &MUST; associate each received response
2676   message to the highest ordered request that has not yet received a final
2677   (non-1xx) response.
2682<section title="Connections" anchor="connections">
2684<section title="Persistent Connections" anchor="persistent.connections">
2686<section title="Purpose" anchor="persistent.purpose">
2688   Prior to persistent connections, a separate TCP connection was
2689   established for each request, increasing the load on HTTP servers
2690   and causing congestion on the Internet. The use of inline images and
2691   other associated data often requires a client to make multiple
2692   requests of the same server in a short amount of time. Analysis of
2693   these performance problems and results from a prototype
2694   implementation are available <xref target="Pad1995"/> <xref target="Spe"/>. Implementation experience and
2695   measurements of actual HTTP/1.1 implementations show good
2696   results <xref target="Nie1997"/>. Alternatives have also been explored, for example,
2697   T/TCP <xref target="Tou1998"/>.
2700   Persistent HTTP connections have a number of advantages:
2701  <list style="symbols">
2702      <t>
2703        By opening and closing fewer TCP connections, CPU time is saved
2704        in routers and hosts (clients, servers, proxies, gateways,
2705        tunnels, or caches), and memory used for TCP protocol control
2706        blocks can be saved in hosts.
2707      </t>
2708      <t>
2709        HTTP requests and responses can be pipelined on a connection.
2710        Pipelining allows a client to make multiple requests without
2711        waiting for each response, allowing a single TCP connection to
2712        be used much more efficiently, with much lower elapsed time.
2713      </t>
2714      <t>
2715        Network congestion is reduced by reducing the number of packets
2716        caused by TCP opens, and by allowing TCP sufficient time to
2717        determine the congestion state of the network.
2718      </t>
2719      <t>
2720        Latency on subsequent requests is reduced since there is no time
2721        spent in TCP's connection opening handshake.
2722      </t>
2723      <t>
2724        HTTP can evolve more gracefully, since errors can be reported
2725        without the penalty of closing the TCP connection. Clients using
2726        future versions of HTTP might optimistically try a new feature,
2727        but if communicating with an older server, retry with old
2728        semantics after an error is reported.
2729      </t>
2730    </list>
2733   HTTP implementations &SHOULD; implement persistent connections.
2737<section title="Overall Operation" anchor="persistent.overall">
2739   A significant difference between HTTP/1.1 and earlier versions of
2740   HTTP is that persistent connections are the default behavior of any
2741   HTTP connection. That is, unless otherwise indicated, the client
2742   &SHOULD; assume that the server will maintain a persistent connection,
2743   even after error responses from the server.
2746   Persistent connections provide a mechanism by which a client and a
2747   server can signal the close of a TCP connection. This signaling takes
2748   place using the Connection header field (<xref target="header.connection"/>). Once a close
2749   has been signaled, the client &MUST-NOT; send any more requests on that
2750   connection.
2753<section title="Negotiation" anchor="persistent.negotiation">
2755   An HTTP/1.1 server &MAY; assume that a HTTP/1.1 client intends to
2756   maintain a persistent connection unless a Connection header field including
2757   the connection-token "close" was sent in the request. If the server
2758   chooses to close the connection immediately after sending the
2759   response, it &SHOULD; send a Connection header field including the
2760   connection-token "close".
2763   An HTTP/1.1 client &MAY; expect a connection to remain open, but would
2764   decide to keep it open based on whether the response from a server
2765   contains a Connection header field with the connection-token close. In case
2766   the client does not want to maintain a connection for more than that
2767   request, it &SHOULD; send a Connection header field including the
2768   connection-token close.
2771   If either the client or the server sends the close token in the
2772   Connection header field, that request becomes the last one for the
2773   connection.
2776   Clients and servers &SHOULD-NOT;  assume that a persistent connection is
2777   maintained for HTTP versions less than 1.1 unless it is explicitly
2778   signaled. See <xref target="compatibility.with.http.1.0.persistent.connections"/> for more information on backward
2779   compatibility with HTTP/1.0 clients.
2782   In order to remain persistent, all messages on the connection &MUST;
2783   have a self-defined message length (i.e., one not defined by closure
2784   of the connection), as described in <xref target="message.body"/>.
2788<section title="Pipelining" anchor="pipelining">
2790   A client that supports persistent connections &MAY; "pipeline" its
2791   requests (i.e., send multiple requests without waiting for each
2792   response). A server &MUST; send its responses to those requests in the
2793   same order that the requests were received.
2796   Clients which assume persistent connections and pipeline immediately
2797   after connection establishment &SHOULD; be prepared to retry their
2798   connection if the first pipelined attempt fails. If a client does
2799   such a retry, it &MUST-NOT; pipeline before it knows the connection is
2800   persistent. Clients &MUST; also be prepared to resend their requests if
2801   the server closes the connection before sending all of the
2802   corresponding responses.
2805   Clients &SHOULD-NOT; pipeline requests using non-idempotent request methods or
2806   non-idempotent sequences of request methods (see &idempotent-methods;). Otherwise, a
2807   premature termination of the transport connection could lead to
2808   indeterminate results. A client wishing to send a non-idempotent
2809   request &SHOULD; wait to send that request until it has received the
2810   response status line for the previous request.
2815<section title="Proxy Servers" anchor="persistent.proxy">
2817   It is especially important that proxies correctly implement the
2818   properties of the Connection header field as specified in <xref target="header.connection"/>.
2821   The proxy server &MUST; signal persistent connections separately with
2822   its clients and the origin servers (or other proxy servers) that it
2823   connects to. Each persistent connection applies to only one transport
2824   link.
2827   A proxy server &MUST-NOT; establish a HTTP/1.1 persistent connection
2828   with an HTTP/1.0 client (but see <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/>
2829   for information and discussion of the problems with the Keep-Alive header field
2830   implemented by many HTTP/1.0 clients).
2833<section title="End-to-end and Hop-by-hop Header Fields" anchor="end-to-end.and.hop-by-hop.header-fields">
2835  <cref anchor="TODO-end-to-end" source="jre">
2836    Restored from <eref target=""/>.
2837    See also <eref target=""/>.
2838  </cref>
2841   For the purpose of defining the behavior of caches and non-caching
2842   proxies, we divide HTTP header fields into two categories:
2843  <list style="symbols">
2844      <t>End-to-end header fields, which are  transmitted to the ultimate
2845        recipient of a request or response. End-to-end header fields in
2846        responses &MUST; be stored as part of a cache entry and &MUST; be
2847        transmitted in any response formed from a cache entry.</t>
2849      <t>Hop-by-hop header fields, which are meaningful only for a single
2850        transport-level connection, and are not stored by caches or
2851        forwarded by proxies.</t>
2852  </list>
2855   The following HTTP/1.1 header fields are hop-by-hop header fields:
2856  <list style="symbols">
2857      <t>Connection</t>
2858      <t>Keep-Alive</t>
2859      <t>Proxy-Authenticate</t>
2860      <t>Proxy-Authorization</t>
2861      <t>TE</t>
2862      <t>Trailer</t>
2863      <t>Transfer-Encoding</t>
2864      <t>Upgrade</t>
2865  </list>
2868   All other header fields defined by HTTP/1.1 are end-to-end header fields.
2871   Other hop-by-hop header fields &MUST; be listed in a Connection header field
2872   (<xref target="header.connection"/>).
2876<section title="Non-modifiable Header Fields" anchor="non-modifiable.header-fields">
2878  <cref anchor="TODO-non-mod-headers" source="jre">
2879    Restored from <eref target=""/>.
2880    See also <eref target=""/>.
2881  </cref>
2884   Some features of HTTP/1.1, such as Digest Authentication, depend on the
2885   value of certain end-to-end header fields. A non-transforming proxy &SHOULD-NOT;
2886   modify an end-to-end header field unless the definition of that header field requires
2887   or specifically allows that.
2890   A non-transforming proxy &MUST-NOT; modify any of the following fields in a
2891   request or response, and it &MUST-NOT; add any of these fields if not
2892   already present:
2893  <list style="symbols">
2894    <t>Allow</t>
2895    <t>Content-Location</t>
2896    <t>Content-MD5</t>
2897    <t>ETag</t>
2898    <t>Last-Modified</t>
2899    <t>Server</t>
2900  </list>
2903   A non-transforming proxy &MUST-NOT; modify any of the following fields in a
2904   response:
2905  <list style="symbols">
2906    <t>Expires</t>
2907  </list>
2910   but it &MAY; add any of these fields if not already present. If an
2911   Expires header field is added, it &MUST; be given a field-value identical to
2912   that of the Date header field in that response.
2915   A proxy &MUST-NOT; modify or add any of the following fields in a
2916   message that contains the no-transform cache-control directive, or in
2917   any request:
2918  <list style="symbols">
2919    <t>Content-Encoding</t>
2920    <t>Content-Range</t>
2921    <t>Content-Type</t>
2922  </list>
2925   A transforming proxy &MAY; modify or add these fields to a message
2926   that does not include no-transform, but if it does so, it &MUST; add a
2927   Warning 214 (Transformation applied) if one does not already appear
2928   in the message (see &header-warning;).
2931  <t>
2932    <x:h>Warning:</x:h> Unnecessary modification of end-to-end header fields might
2933    cause authentication failures if stronger authentication
2934    mechanisms are introduced in later versions of HTTP. Such
2935    authentication mechanisms &MAY; rely on the values of header fields
2936    not listed here.
2937  </t>
2940   A non-transforming proxy &MUST; preserve the message payload (&payload;),
2941   though it &MAY; change the message body through application or removal
2942   of a transfer-coding (<xref target="transfer.codings"/>).
2948<section title="Practical Considerations" anchor="persistent.practical">
2950   Servers will usually have some time-out value beyond which they will
2951   no longer maintain an inactive connection. Proxy servers might make
2952   this a higher value since it is likely that the client will be making
2953   more connections through the same server. The use of persistent
2954   connections places no requirements on the length (or existence) of
2955   this time-out for either the client or the server.
2958   When a client or server wishes to time-out it &SHOULD; issue a graceful
2959   close on the transport connection. Clients and servers &SHOULD; both
2960   constantly watch for the other side of the transport close, and
2961   respond to it as appropriate. If a client or server does not detect
2962   the other side's close promptly it could cause unnecessary resource
2963   drain on the network.
2966   A client, server, or proxy &MAY; close the transport connection at any
2967   time. For example, a client might have started to send a new request
2968   at the same time that the server has decided to close the "idle"
2969   connection. From the server's point of view, the connection is being
2970   closed while it was idle, but from the client's point of view, a
2971   request is in progress.
2974   Clients (including proxies) &SHOULD; limit the number of simultaneous
2975   connections that they maintain to a given server (including proxies).
2978   Previous revisions of HTTP gave a specific number of connections as a
2979   ceiling, but this was found to be impractical for many applications. As a
2980   result, this specification does not mandate a particular maximum number of
2981   connections, but instead encourages clients to be conservative when opening
2982   multiple connections.
2985   In particular, while using multiple connections avoids the "head-of-line
2986   blocking" problem (whereby a request that takes significant server-side
2987   processing and/or has a large payload can block subsequent requests on the
2988   same connection), each connection used consumes server resources (sometimes
2989   significantly), and furthermore using multiple connections can cause
2990   undesirable side effects in congested networks.
2993   Note that servers might reject traffic that they deem abusive, including an
2994   excessive number of connections from a client.
2998<section title="Retrying Requests" anchor="persistent.retrying.requests">
3000   Senders can close the transport connection at any time. Therefore,
3001   clients, servers, and proxies &MUST; be able to recover
3002   from asynchronous close events. Client software &MAY; reopen the
3003   transport connection and retransmit the aborted sequence of requests
3004   without user interaction so long as the request sequence is
3005   idempotent (see &idempotent-methods;). Non-idempotent request methods or sequences
3006   &MUST-NOT; be automatically retried, although user agents &MAY; offer a
3007   human operator the choice of retrying the request(s). Confirmation by
3008   user-agent software with semantic understanding of the application
3009   &MAY; substitute for user confirmation. The automatic retry &SHOULD-NOT;
3010   be repeated if the second sequence of requests fails.
3016<section title="Message Transmission Requirements" anchor="message.transmission.requirements">
3018<section title="Persistent Connections and Flow Control" anchor="persistent.flow">
3020   HTTP/1.1 servers &SHOULD; maintain persistent connections and use TCP's
3021   flow control mechanisms to resolve temporary overloads, rather than
3022   terminating connections with the expectation that clients will retry.
3023   The latter technique can exacerbate network congestion.
3027<section title="Monitoring Connections for Error Status Messages" anchor="persistent.monitor">
3029   An HTTP/1.1 (or later) client sending a message body &SHOULD; monitor
3030   the network connection for an error status code while it is transmitting
3031   the request. If the client sees an error status code, it &SHOULD;
3032   immediately cease transmitting the body. If the body is being sent
3033   using a "chunked" encoding (<xref target="transfer.codings"/>), a zero length chunk and
3034   empty trailer &MAY; be used to prematurely mark the end of the message.
3035   If the body was preceded by a Content-Length header field, the client &MUST;
3036   close the connection.
3040<section title="Use of the 100 (Continue) Status" anchor="use.of.the.100.status">
3042   The purpose of the 100 (Continue) status code (see &status-100;) is to
3043   allow a client that is sending a request message with a request body
3044   to determine if the origin server is willing to accept the request
3045   (based on the request header fields) before the client sends the request
3046   body. In some cases, it might either be inappropriate or highly
3047   inefficient for the client to send the body if the server will reject
3048   the message without looking at the body.
3051   Requirements for HTTP/1.1 clients:
3052  <list style="symbols">
3053    <t>
3054        If a client will wait for a 100 (Continue) response before
3055        sending the request body, it &MUST; send an Expect header
3056        field (&header-expect;) with the "100-continue" expectation.
3057    </t>
3058    <t>
3059        A client &MUST-NOT; send an Expect header field (&header-expect;)
3060        with the "100-continue" expectation if it does not intend
3061        to send a request body.
3062    </t>
3063  </list>
3066   Because of the presence of older implementations, the protocol allows
3067   ambiguous situations in which a client might send "Expect: 100-continue"
3068   without receiving either a 417 (Expectation Failed)
3069   or a 100 (Continue) status code. Therefore, when a client sends this
3070   header field to an origin server (possibly via a proxy) from which it
3071   has never seen a 100 (Continue) status code, the client &SHOULD-NOT; 
3072   wait for an indefinite period before sending the request body.
3075   Requirements for HTTP/1.1 origin servers:
3076  <list style="symbols">
3077    <t> Upon receiving a request which includes an Expect header
3078        field with the "100-continue" expectation, an origin server &MUST;
3079        either respond with 100 (Continue) status code and continue to read
3080        from the input stream, or respond with a final status code. The
3081        origin server &MUST-NOT; wait for the request body before sending
3082        the 100 (Continue) response. If it responds with a final status
3083        code, it &MAY; close the transport connection or it &MAY; continue
3084        to read and discard the rest of the request.  It &MUST-NOT;
3085        perform the request method if it returns a final status code.
3086    </t>
3087    <t> An origin server &SHOULD-NOT;  send a 100 (Continue) response if
3088        the request message does not include an Expect header
3089        field with the "100-continue" expectation, and &MUST-NOT; send a
3090        100 (Continue) response if such a request comes from an HTTP/1.0
3091        (or earlier) client. There is an exception to this rule: for
3092        compatibility with <xref target="RFC2068"/>, a server &MAY; send a 100 (Continue)
3093        status code in response to an HTTP/1.1 PUT or POST request that does
3094        not include an Expect header field with the "100-continue"
3095        expectation. This exception, the purpose of which is
3096        to minimize any client processing delays associated with an
3097        undeclared wait for 100 (Continue) status code, applies only to
3098        HTTP/1.1 requests, and not to requests with any other HTTP-version
3099        value.
3100    </t>
3101    <t> An origin server &MAY; omit a 100 (Continue) response if it has
3102        already received some or all of the request body for the
3103        corresponding request.
3104    </t>
3105    <t> An origin server that sends a 100 (Continue) response &MUST;
3106        ultimately send a final status code, once the request body is
3107        received and processed, unless it terminates the transport
3108        connection prematurely.
3109    </t>
3110    <t> If an origin server receives a request that does not include an
3111        Expect header field with the "100-continue" expectation,
3112        the request includes a request body, and the server responds
3113        with a final status code before reading the entire request body
3114        from the transport connection, then the server &SHOULD-NOT;  close
3115        the transport connection until it has read the entire request,
3116        or until the client closes the connection. Otherwise, the client
3117        might not reliably receive the response message. However, this
3118        requirement ought not be construed as preventing a server from
3119        defending itself against denial-of-service attacks, or from
3120        badly broken client implementations.
3121      </t>
3122    </list>
3125   Requirements for HTTP/1.1 proxies:
3126  <list style="symbols">
3127    <t> If a proxy receives a request that includes an Expect header
3128        field with the "100-continue" expectation, and the proxy
3129        either knows that the next-hop server complies with HTTP/1.1 or
3130        higher, or does not know the HTTP version of the next-hop
3131        server, it &MUST; forward the request, including the Expect header
3132        field.
3133    </t>
3134    <t> If the proxy knows that the version of the next-hop server is
3135        HTTP/1.0 or lower, it &MUST-NOT; forward the request, and it &MUST;
3136        respond with a 417 (Expectation Failed) status code.
3137    </t>
3138    <t> Proxies &SHOULD; maintain a record of the HTTP version
3139        numbers received from recently-referenced next-hop servers.
3140    </t>
3141    <t> A proxy &MUST-NOT; forward a 100 (Continue) response if the
3142        request message was received from an HTTP/1.0 (or earlier)
3143        client and did not include an Expect header field with
3144        the "100-continue" expectation. This requirement overrides the
3145        general rule for forwarding of 1xx responses (see &status-1xx;).
3146    </t>
3147  </list>
3151<section title="Closing Connections on Error" anchor="closing.connections.on.error">
3153   If the client is sending data, a server implementation using TCP
3154   &SHOULD; be careful to ensure that the client acknowledges receipt of
3155   the packet(s) containing the response, before the server closes the
3156   input connection. If the client continues sending data to the server
3157   after the close, the server's TCP stack will send a reset packet to
3158   the client, which might erase the client's unacknowledged input buffers
3159   before they can be read and interpreted by the HTTP application.
3167<section title="Miscellaneous notes that might disappear" anchor="misc">
3168<section title="Scheme aliases considered harmful" anchor="scheme.aliases">
3170   <cref anchor="TBD-aliases-harmful">describe why aliases like webcal are harmful.</cref>
3174<section title="Use of HTTP for proxy communication" anchor="http.proxy">
3176   <cref anchor="TBD-proxy-other">Configured to use HTTP to proxy HTTP or other protocols.</cref>
3180<section title="Interception of HTTP for access control" anchor="http.intercept">
3182   <cref anchor="TBD-intercept">Interception of HTTP traffic for initiating access control.</cref>
3186<section title="Use of HTTP by other protocols" anchor="http.others">
3188   <cref anchor="TBD-profiles">Profiles of HTTP defined by other protocol.
3189   Extensions of HTTP like WebDAV.</cref>
3193<section title="Use of HTTP by media type specification" anchor="">
3195   <cref anchor="TBD-hypertext">Instructions on composing HTTP requests via hypertext formats.</cref>
3200<section title="Header Field Definitions" anchor="header.field.definitions">
3202   This section defines the syntax and semantics of HTTP header fields
3203   related to message origination, framing, and routing.
3205<texttable align="left">
3206  <ttcol>Header Field Name</ttcol>
3207  <ttcol>Defined in...</ttcol>
3209  <c>Connection</c> <c><xref target="header.connection"/></c>
3210  <c>Content-Length</c> <c><xref target="header.content-length"/></c>
3211  <c>Host</c> <c><xref target=""/></c>
3212  <c>TE</c> <c><xref target="header.te"/></c>
3213  <c>Trailer</c> <c><xref target="header.trailer"/></c>
3214  <c>Transfer-Encoding</c> <c><xref target="header.transfer-encoding"/></c>
3215  <c>Upgrade</c> <c><xref target="header.upgrade"/></c>
3216  <c>Via</c> <c><xref target="header.via"/></c>
3219<section title="Connection" anchor="header.connection">
3220  <iref primary="true" item="Connection header field" x:for-anchor=""/>
3221  <iref primary="true" item="Header Fields" subitem="Connection" x:for-anchor=""/>
3222  <x:anchor-alias value="Connection"/>
3223  <x:anchor-alias value="connection-token"/>
3225   The "Connection" header field allows the sender to specify
3226   options that are desired only for that particular connection.
3227   Such connection options &MUST; be removed or replaced before the
3228   message can be forwarded downstream by a proxy or gateway.
3229   This mechanism also allows the sender to indicate which HTTP
3230   header fields used in the message are only intended for the
3231   immediate recipient ("hop-by-hop"), as opposed to all recipients
3232   on the chain ("end-to-end"), enabling the message to be
3233   self-descriptive and allowing future connection-specific extensions
3234   to be deployed in HTTP without fear that they will be blindly
3235   forwarded by previously deployed intermediaries.
3238   The Connection header field's value has the following grammar:
3240<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="connection-token"/>
3241  <x:ref>Connection</x:ref>       = 1#<x:ref>connection-token</x:ref>
3242  <x:ref>connection-token</x:ref> = <x:ref>token</x:ref>
3245   A proxy or gateway &MUST; parse a received Connection
3246   header field before a message is forwarded and, for each
3247   connection-token in this field, remove any header field(s) from
3248   the message with the same name as the connection-token, and then
3249   remove the Connection header field itself or replace it with the
3250   sender's own connection options for the forwarded message.
3253   A sender &MUST-NOT; include field-names in the Connection header
3254   field-value for fields that are defined as expressing constraints
3255   for all recipients in the request or response chain, such as the
3256   Cache-Control header field (&header-cache-control;).
3259   The connection options do not have to correspond to a header field
3260   present in the message, since a connection-specific header field
3261   might not be needed if there are no parameters associated with that
3262   connection option.  Recipients that trigger certain connection
3263   behavior based on the presence of connection options &MUST; do so
3264   based on the presence of the connection-token rather than only the
3265   presence of the optional header field.  In other words, if the
3266   connection option is received as a header field but not indicated
3267   within the Connection field-value, then the recipient &MUST; ignore
3268   the connection-specific header field because it has likely been
3269   forwarded by an intermediary that is only partially conformant.
3272   When defining new connection options, specifications ought to
3273   carefully consider existing deployed header fields and ensure
3274   that the new connection-token does not share the same name as
3275   an unrelated header field that might already be deployed.
3276   Defining a new connection-token essentially reserves that potential
3277   field-name for carrying additional information related to the
3278   connection option, since it would be unwise for senders to use
3279   that field-name for anything else.
3282   HTTP/1.1 defines the "close" connection option for the sender to
3283   signal that the connection will be closed after completion of the
3284   response. For example,
3286<figure><artwork type="example">
3287  Connection: close
3290   in either the request or the response header fields indicates that
3291   the connection &SHOULD-NOT;  be considered "persistent" (<xref target="persistent.connections"/>)
3292   after the current request/response is complete.
3295   An HTTP/1.1 client that does not support persistent connections &MUST;
3296   include the "close" connection option in every request message.
3299   An HTTP/1.1 server that does not support persistent connections &MUST;
3300   include the "close" connection option in every response message that
3301   does not have a 1xx (Informational) status code.
3305<section title="Upgrade" anchor="header.upgrade">
3306  <iref primary="true" item="Upgrade header field" x:for-anchor=""/>
3307  <iref primary="true" item="Header Fields" subitem="Upgrade" x:for-anchor=""/>
3308  <x:anchor-alias value="Upgrade"/>
3309  <x:anchor-alias value="protocol"/>
3310  <x:anchor-alias value="protocol-name"/>
3311  <x:anchor-alias value="protocol-version"/>
3313   The "Upgrade" header field allows the client to specify what
3314   additional communication protocols it would like to use, if the server
3315   chooses to switch protocols. Servers can use it to indicate what protocols
3316   they are willing to switch to.
3318<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Upgrade"/>
3319  <x:ref>Upgrade</x:ref>          = 1#<x:ref>protocol</x:ref>
3321  <x:ref>protocol</x:ref>         = <x:ref>protocol-name</x:ref> ["/" <x:ref>protocol-version</x:ref>]
3322  <x:ref>protocol-name</x:ref>    = <x:ref>token</x:ref>
3323  <x:ref>protocol-version</x:ref> = <x:ref>token</x:ref>
3326   For example,
3328<figure><artwork type="example">
3329  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
3332   The Upgrade header field is intended to provide a simple mechanism
3333   for transitioning from HTTP/1.1 to some other, incompatible protocol. It
3334   does so by allowing the client to advertise its desire to use another
3335   protocol, such as a later version of HTTP with a higher major version
3336   number, even though the current request has been made using HTTP/1.1.
3337   This eases the difficult transition between incompatible protocols by
3338   allowing the client to initiate a request in the more commonly
3339   supported protocol while indicating to the server that it would like
3340   to use a "better" protocol if available (where "better" is determined
3341   by the server, possibly according to the nature of the request method
3342   or target resource).
3345   The Upgrade header field only applies to switching application-layer
3346   protocols upon the existing transport-layer connection. Upgrade
3347   cannot be used to insist on a protocol change; its acceptance and use
3348   by the server is optional. The capabilities and nature of the
3349   application-layer communication after the protocol change is entirely
3350   dependent upon the new protocol chosen, although the first action
3351   after changing the protocol &MUST; be a response to the initial HTTP
3352   request containing the Upgrade header field.
3355   The Upgrade header field only applies to the immediate connection.
3356   Therefore, the upgrade keyword &MUST; be supplied within a Connection
3357   header field (<xref target="header.connection"/>) whenever Upgrade is present in an
3358   HTTP/1.1 message.
3361   The Upgrade header field cannot be used to indicate a switch to a
3362   protocol on a different connection. For that purpose, it is more
3363   appropriate to use a 3xx redirection response (&status-3xx;).
3366   Servers &MUST; include the "Upgrade" header field in 101 (Switching
3367   Protocols) responses to indicate which protocol(s) are being switched to,
3368   and &MUST; include it in 426 (Upgrade Required) responses to indicate
3369   acceptable protocols to upgrade to. Servers &MAY; include it in any other
3370   response to indicate that they are willing to upgrade to one of the
3371   specified protocols.
3374   This specification only defines the protocol name "HTTP" for use by
3375   the family of Hypertext Transfer Protocols, as defined by the HTTP
3376   version rules of <xref target="http.version"/> and future updates to this
3377   specification. Additional tokens can be registered with IANA using the
3378   registration procedure defined below. 
3381<section title="Upgrade Token Registry" anchor="upgrade.token.registry">
3383   The HTTP Upgrade Token Registry defines the name space for protocol-name
3384   tokens used to identify protocols in the Upgrade header field.
3385   Each registered protocol-name is associated with contact information and
3386   an optional set of specifications that details how the connection
3387   will be processed after it has been upgraded.
3390   Registrations require IETF Review (see
3391   <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>) and are subject to the
3392   following rules:
3393  <list style="numbers">
3394    <t>A protocol-name token, once registered, stays registered forever.</t>
3395    <t>The registration &MUST; name a responsible party for the
3396       registration.</t>
3397    <t>The registration &MUST; name a point of contact.</t>
3398    <t>The registration &MAY; name a set of specifications associated with
3399       that token. Such specifications need not be publicly available.</t>
3400    <t>The registration &SHOULD; name a set of expected "protocol-version"
3401       tokens associated with that token at the time of registration.</t>
3402    <t>The responsible party &MAY; change the registration at any time.
3403       The IANA will keep a record of all such changes, and make them
3404       available upon request.</t>
3405    <t>The IESG &MAY; reassign responsibility for a protocol token.
3406       This will normally only be used in the case when a
3407       responsible party cannot be contacted.</t>
3408  </list>
3415<section title="Via" anchor="header.via">
3416  <iref primary="true" item="Via header field" x:for-anchor=""/>
3417  <iref primary="true" item="Header Fields" subitem="Via" x:for-anchor=""/>
3418  <x:anchor-alias value="pseudonym"/>
3419  <x:anchor-alias value="received-by"/>
3420  <x:anchor-alias value="received-protocol"/>
3421  <x:anchor-alias value="Via"/>
3423   The "Via" header field &MUST; be sent by a proxy or gateway to
3424   indicate the intermediate protocols and recipients between the user
3425   agent and the server on requests, and between the origin server and
3426   the client on responses. It is analogous to the "Received" field
3427   used by email systems (<xref target="RFC5322" x:fmt="of" x:sec="3.6.7"/>)
3428   and is intended to be used for tracking message forwards,
3429   avoiding request loops, and identifying the protocol capabilities of
3430   all senders along the request/response chain.
3432<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"/>
3433  <x:ref>Via</x:ref>               = 1#( <x:ref>received-protocol</x:ref> <x:ref>RWS</x:ref> <x:ref>received-by</x:ref>
3434                          [ <x:ref>RWS</x:ref> <x:ref>comment</x:ref> ] )
3435  <x:ref>received-protocol</x:ref> = [ <x:ref>protocol-name</x:ref> "/" ] <x:ref>protocol-version</x:ref>
3436  <x:ref>received-by</x:ref>       = ( <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ) / <x:ref>pseudonym</x:ref>
3437  <x:ref>pseudonym</x:ref>         = <x:ref>token</x:ref>
3440   The received-protocol indicates the protocol version of the message
3441   received by the server or client along each segment of the
3442   request/response chain. The received-protocol version is appended to
3443   the Via field value when the message is forwarded so that information
3444   about the protocol capabilities of upstream applications remains
3445   visible to all recipients.
3448   The protocol-name is excluded if and only if it would be "HTTP". The
3449   received-by field is normally the host and optional port number of a
3450   recipient server or client that subsequently forwarded the message.
3451   However, if the real host is considered to be sensitive information,
3452   it &MAY; be replaced by a pseudonym. If the port is not given, it &MAY;
3453   be assumed to be the default port of the received-protocol.
3456   Multiple Via field values represent each proxy or gateway that has
3457   forwarded the message. Each recipient &MUST; append its information
3458   such that the end result is ordered according to the sequence of
3459   forwarding applications.
3462   Comments &MAY; be used in the Via header field to identify the software
3463   of each recipient, analogous to the User-Agent and Server header fields.
3464   However, all comments in the Via field are optional and &MAY; be removed
3465   by any recipient prior to forwarding the message.
3468   For example, a request message could be sent from an HTTP/1.0 user
3469   agent to an internal proxy code-named "fred", which uses HTTP/1.1 to
3470   forward the request to a public proxy at, which completes
3471   the request by forwarding it to the origin server at
3472   The request received by would then have the following
3473   Via header field:
3475<figure><artwork type="example">
3476  Via: 1.0 fred, 1.1 (Apache/1.1)
3479   A proxy or gateway used as a portal through a network firewall
3480   &SHOULD-NOT; forward the names and ports of hosts within the firewall
3481   region unless it is explicitly enabled to do so. If not enabled, the
3482   received-by host of any host behind the firewall &SHOULD; be replaced
3483   by an appropriate pseudonym for that host.
3486   For organizations that have strong privacy requirements for hiding
3487   internal structures, a proxy or gateway &MAY; combine an ordered
3488   subsequence of Via header field entries with identical received-protocol
3489   values into a single such entry. For example,
3491<figure><artwork type="example">
3492  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
3495  could be collapsed to
3497<figure><artwork type="example">
3498  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
3501   Senders &SHOULD-NOT; combine multiple entries unless they are all
3502   under the same organizational control and the hosts have already been
3503   replaced by pseudonyms. Senders &MUST-NOT; combine entries which
3504   have different received-protocol values.
3510<section title="IANA Considerations" anchor="IANA.considerations">
3512<section title="Header Field Registration" anchor="header.field.registration">
3514   The Message Header Field Registry located at <eref target=""/> shall be updated
3515   with the permanent registrations below (see <xref target="RFC3864"/>):
3517<?BEGININC p1-messaging.iana-headers ?>
3518<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
3519<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
3520   <ttcol>Header Field Name</ttcol>
3521   <ttcol>Protocol</ttcol>
3522   <ttcol>Status</ttcol>
3523   <ttcol>Reference</ttcol>
3525   <c>Connection</c>
3526   <c>http</c>
3527   <c>standard</c>
3528   <c>
3529      <xref target="header.connection"/>
3530   </c>
3531   <c>Content-Length</c>
3532   <c>http</c>
3533   <c>standard</c>
3534   <c>
3535      <xref target="header.content-length"/>
3536   </c>
3537   <c>Host</c>
3538   <c>http</c>
3539   <c>standard</c>
3540   <c>
3541      <xref target=""/>
3542   </c>
3543   <c>TE</c>
3544   <c>http</c>
3545   <c>standard</c>
3546   <c>
3547      <xref target="header.te"/>
3548   </c>
3549   <c>Trailer</c>
3550   <c>http</c>
3551   <c>standard</c>
3552   <c>
3553      <xref target="header.trailer"/>
3554   </c>
3555   <c>Transfer-Encoding</c>
3556   <c>http</c>
3557   <c>standard</c>
3558   <c>
3559      <xref target="header.transfer-encoding"/>
3560   </c>
3561   <c>Upgrade</c>
3562   <c>http</c>
3563   <c>standard</c>
3564   <c>
3565      <xref target="header.upgrade"/>
3566   </c>
3567   <c>Via</c>
3568   <c>http</c>
3569   <c>standard</c>
3570   <c>
3571      <xref target="header.via"/>
3572   </c>
3575<?ENDINC p1-messaging.iana-headers ?>
3577   Furthermore, the header field name "Close" shall be registered as "reserved", as its use as
3578   HTTP header field would be in conflict with the use of the "close" connection
3579   option for the "Connection" header field (<xref target="header.connection"/>).
3581<texttable align="left" suppress-title="true">
3582   <ttcol>Header Field Name</ttcol>
3583   <ttcol>Protocol</ttcol>
3584   <ttcol>Status</ttcol>
3585   <ttcol>Reference</ttcol>
3587   <c>Close</c>
3588   <c>http</c>
3589   <c>reserved</c>
3590   <c>
3591      <xref target="header.field.registration"/>
3592   </c>
3595   The change controller is: "IETF ( - Internet Engineering Task Force".
3599<section title="URI Scheme Registration" anchor="uri.scheme.registration">
3601   The entries for the "http" and "https" URI Schemes in the registry located at
3602   <eref target=""/>
3603   shall be updated to point to Sections <xref target="http.uri" format="counter"/>
3604   and <xref target="https.uri" format="counter"/> of this document
3605   (see <xref target="RFC4395"/>).
3609<section title="Internet Media Type Registrations" anchor="">
3611   This document serves as the specification for the Internet media types
3612   "message/http" and "application/http". The following is to be registered with
3613   IANA (see <xref target="RFC4288"/>).
3615<section title="Internet Media Type message/http" anchor="">
3616<iref item="Media Type" subitem="message/http" primary="true"/>
3617<iref item="message/http Media Type" primary="true"/>
3619   The message/http type can be used to enclose a single HTTP request or
3620   response message, provided that it obeys the MIME restrictions for all
3621   "message" types regarding line length and encodings.
3624  <list style="hanging" x:indent="12em">
3625    <t hangText="Type name:">
3626      message
3627    </t>
3628    <t hangText="Subtype name:">
3629      http
3630    </t>
3631    <t hangText="Required parameters:">
3632      none
3633    </t>
3634    <t hangText="Optional parameters:">
3635      version, msgtype
3636      <list style="hanging">
3637        <t hangText="version:">
3638          The HTTP-version number of the enclosed message
3639          (e.g., "1.1"). If not present, the version can be
3640          determined from the first line of the body.
3641        </t>
3642        <t hangText="msgtype:">
3643          The message type &mdash; "request" or "response". If not
3644          present, the type can be determined from the first
3645          line of the body.
3646        </t>
3647      </list>
3648    </t>
3649    <t hangText="Encoding considerations:">
3650      only "7bit", "8bit", or "binary" are permitted
3651    </t>
3652    <t hangText="Security considerations:">
3653      none
3654    </t>
3655    <t hangText="Interoperability considerations:">
3656      none
3657    </t>
3658    <t hangText="Published specification:">
3659      This specification (see <xref target=""/>).
3660    </t>
3661    <t hangText="Applications that use this media type:">
3662    </t>
3663    <t hangText="Additional information:">
3664      <list style="hanging">
3665        <t hangText="Magic number(s):">none</t>
3666        <t hangText="File extension(s):">none</t>
3667        <t hangText="Macintosh file type code(s):">none</t>
3668      </list>
3669    </t>
3670    <t hangText="Person and email address to contact for further information:">
3671      See Authors Section.
3672    </t>
3673    <t hangText="Intended usage:">
3674      COMMON
3675    </t>
3676    <t hangText="Restrictions on usage:">
3677      none
3678    </t>
3679    <t hangText="Author/Change controller:">
3680      IESG
3681    </t>
3682  </list>
3685<section title="Internet Media Type application/http" anchor="">
3686<iref item="Media Type" subitem="application/http" primary="true"/>
3687<iref item="application/http Media Type" primary="true"/>
3689   The application/http type can be used to enclose a pipeline of one or more
3690   HTTP request or response messages (not intermixed).
3693  <list style="hanging" x:indent="12em">
3694    <t hangText="Type name:">
3695      application
3696    </t>
3697    <t hangText="Subtype name:">
3698      http
3699    </t>
3700    <t hangText="Required parameters:">
3701      none
3702    </t>
3703    <t hangText="Optional parameters:">
3704      version, msgtype
3705      <list style="hanging">
3706        <t hangText="version:">
3707          The HTTP-version number of the enclosed messages
3708          (e.g., "1.1"). If not present, the version can be
3709          determined from the first line of the body.
3710        </t>
3711        <t hangText="msgtype:">
3712          The message type &mdash; "request" or "response". If not
3713          present, the type can be determined from the first
3714          line of the body.
3715        </t>
3716      </list>
3717    </t>
3718    <t hangText="Encoding considerations:">
3719      HTTP messages enclosed by this type
3720      are in "binary" format; use of an appropriate
3721      Content-Transfer-Encoding is required when
3722      transmitted via E-mail.
3723    </t>
3724    <t hangText="Security considerations:">
3725      none
3726    </t>
3727    <t hangText="Interoperability considerations:">
3728      none
3729    </t>
3730    <t hangText="Published specification:">
3731      This specification (see <xref target=""/>).
3732    </t>
3733    <t hangText="Applications that use this media type:">
3734    </t>
3735    <t hangText="Additional information:">
3736      <list style="hanging">
3737        <t hangText="Magic number(s):">none</t>
3738        <t hangText="File extension(s):">none</t>
3739        <t hangText="Macintosh file type code(s):">none</t>
3740      </list>
3741    </t>
3742    <t hangText="Person and email address to contact for further information:">
3743      See Authors Section.
3744    </t>
3745    <t hangText="Intended usage:">
3746      COMMON
3747    </t>
3748    <t hangText="Restrictions on usage:">
3749      none
3750    </t>
3751    <t hangText="Author/Change controller:">
3752      IESG
3753    </t>
3754  </list>
3759<section title="Transfer Coding Registry" anchor="transfer.coding.registration">
3761   The registration procedure for HTTP Transfer Codings is now defined by
3762   <xref target="transfer.coding.registry"/> of this document.
3765   The HTTP Transfer Codings Registry located at <eref target=""/>
3766   shall be updated with the registrations below:
3768<texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table">
3769   <ttcol>Name</ttcol>
3770   <ttcol>Description</ttcol>
3771   <ttcol>Reference</ttcol>
3772   <c>chunked</c>
3773   <c>Transfer in a series of chunks</c>
3774   <c>
3775      <xref target="chunked.encoding"/>
3776   </c>
3777   <c>compress</c>
3778   <c>UNIX "compress" program method</c>
3779   <c>
3780      <xref target="compress.coding"/>
3781   </c>
3782   <c>deflate</c>
3783   <c>"deflate" compression mechanism (<xref target="RFC1951"/>) used inside
3784   the "zlib" data format (<xref target="RFC1950"/>)
3785   </c>
3786   <c>
3787      <xref target="deflate.coding"/>
3788   </c>
3789   <c>gzip</c>
3790   <c>Same as GNU zip <xref target="RFC1952"/></c>
3791   <c>
3792      <xref target="gzip.coding"/>
3793   </c>
3797<section title="Upgrade Token Registration" anchor="upgrade.token.registration">
3799   The registration procedure for HTTP Upgrade Tokens &mdash; previously defined
3800   in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/> &mdash; is now defined
3801   by <xref target="upgrade.token.registry"/> of this document.
3804   The HTTP Upgrade Token Registry located at <eref target=""/>
3805   shall be updated with the registration below:
3807<texttable align="left" suppress-title="true">
3808   <ttcol>Value</ttcol>
3809   <ttcol>Description</ttcol>
3810   <ttcol>Reference</ttcol>
3812   <c>HTTP</c>
3813   <c>Hypertext Transfer Protocol</c>
3814   <c><xref target="http.version"/> of this specification</c>
3821<section title="Security Considerations" anchor="security.considerations">
3823   This section is meant to inform application developers, information
3824   providers, and users of the security limitations in HTTP/1.1 as
3825   described by this document. The discussion does not include
3826   definitive solutions to the problems revealed, though it does make
3827   some suggestions for reducing security risks.
3830<section title="Personal Information" anchor="personal.information">
3832   HTTP clients are often privy to large amounts of personal information
3833   (e.g., the user's name, location, mail address, passwords, encryption
3834   keys, etc.), and &SHOULD; be very careful to prevent unintentional
3835   leakage of this information.
3836   We very strongly recommend that a convenient interface be provided
3837   for the user to control dissemination of such information, and that
3838   designers and implementors be particularly careful in this area.
3839   History shows that errors in this area often create serious security
3840   and/or privacy problems and generate highly adverse publicity for the
3841   implementor's company.
3845<section title="Abuse of Server Log Information" anchor="abuse.of.server.log.information">
3847   A server is in the position to save personal data about a user's
3848   requests which might identify their reading patterns or subjects of
3849   interest. This information is clearly confidential in nature and its
3850   handling can be constrained by law in certain countries. People using
3851   HTTP to provide data are responsible for ensuring that
3852   such material is not distributed without the permission of any
3853   individuals that are identifiable by the published results.
3857<section title="Attacks Based On File and Path Names" anchor="attack.pathname">
3859   Implementations of HTTP origin servers &SHOULD; be careful to restrict
3860   the documents returned by HTTP requests to be only those that were
3861   intended by the server administrators. If an HTTP server translates
3862   HTTP URIs directly into file system calls, the server &MUST; take
3863   special care not to serve files that were not intended to be
3864   delivered to HTTP clients. For example, UNIX, Microsoft Windows, and
3865   other operating systems use ".." as a path component to indicate a
3866   directory level above the current one. On such a system, an HTTP
3867   server &MUST; disallow any such construct in the request-target if it
3868   would otherwise allow access to a resource outside those intended to
3869   be accessible via the HTTP server. Similarly, files intended for
3870   reference only internally to the server (such as access control
3871   files, configuration files, and script code) &MUST; be protected from
3872   inappropriate retrieval, since they might contain sensitive
3873   information. Experience has shown that minor bugs in such HTTP server
3874   implementations have turned into security risks.
3878<section title="DNS-related Attacks" anchor="dns.related.attacks">
3880   HTTP clients rely heavily on the Domain Name Service (DNS), and are thus
3881   generally prone to security attacks based on the deliberate misassociation
3882   of IP addresses and DNS names not protected by DNSSec. Clients need to be
3883   cautious in assuming the validity of an IP number/DNS name association unless
3884   the response is protected by DNSSec (<xref target="RFC4033"/>).
3888<section title="Proxies and Caching" anchor="attack.proxies">
3890   By their very nature, HTTP proxies are men-in-the-middle, and
3891   represent an opportunity for man-in-the-middle attacks. Compromise of
3892   the systems on which the proxies run can result in serious security
3893   and privacy problems. Proxies have access to security-related
3894   information, personal information about individual users and
3895   organizations, and proprietary information belonging to users and
3896   content providers. A compromised proxy, or a proxy implemented or
3897   configured without regard to security and privacy considerations,
3898   might be used in the commission of a wide range of potential attacks.
3901   Proxy operators need to protect the systems on which proxies run as
3902   they would protect any system that contains or transports sensitive
3903   information. In particular, log information gathered at proxies often
3904   contains highly sensitive personal information, and/or information
3905   about organizations. Log information needs to be carefully guarded, and
3906   appropriate guidelines for use need to be developed and followed.
3907   (<xref target="abuse.of.server.log.information"/>).
3910   Proxy implementors need to consider the privacy and security
3911   implications of their design and coding decisions, and of the
3912   configuration options they provide to proxy operators (especially the
3913   default configuration).
3916   Users of a proxy need to be aware that proxies are no more trustworthy than
3917   the people who run them; HTTP itself cannot solve this problem.
3920   The judicious use of cryptography, when appropriate, might suffice to
3921   protect against a broad range of security and privacy attacks. Such
3922   cryptography is beyond the scope of the HTTP/1.1 specification.
3926<section title="Protocol Element Size Overflows" anchor="attack.protocol.element.size.overflows">
3928   Because HTTP uses mostly textual, character-delimited fields, attackers can
3929   overflow buffers in implementations, and/or perform a Denial of Service
3930   against implementations that accept fields with unlimited lengths.
3933   To promote interoperability, this specification makes specific
3934   recommendations for minimum size limits on request-line
3935   (<xref target="request.line"/>)
3936   and blocks of header fields (<xref target="header.fields"/>). These are
3937   minimum recommendations, chosen to be supportable even by implementations
3938   with limited resources; it is expected that most implementations will
3939   choose substantially higher limits.
3942   This specification also provides a way for servers to reject messages that
3943   have request-targets that are too long (&status-414;) or request entities
3944   that are too large (&status-4xx;).
3947   Other fields (including but not limited to request methods, response status
3948   phrases, header field-names, and body chunks) &SHOULD; be limited by
3949   implementations carefully, so as to not impede interoperability.
3953<section title="Denial of Service Attacks on Proxies" anchor="attack.DoS">
3955   They exist. They are hard to defend against. Research continues.
3956   Beware.
3961<section title="Acknowledgments" anchor="acks">
3963   This document revision builds on the work that went into
3964   <xref target="RFC2616" format="none">RFC 2616</xref> and its predecessors.
3965   See <xref target="RFC2616" x:fmt="of" x:sec="16"/> for detailed
3966   acknowledgements.
3969   Since 1999, many contributors have helped by reporting bugs, asking
3970   smart questions, drafting and reviewing text, and discussing open issues:
3972<?BEGININC acks ?>
3973<t>Adam Barth,
3974Adam Roach,
3975Addison Phillips,
3976Adrian Chadd,
3977Adrien de Croy,
3978Alan Ford,
3979Alan Ruttenberg,
3980Albert Lunde,
3981Alex Rousskov,
3982Alexey Melnikov,
3983Alisha Smith,
3984Amichai Rothman,
3985Amit Klein,
3986Amos Jeffries,
3987Andreas Maier,
3988Andreas Petersson,
3989Anne van Kesteren,
3990Anthony Bryan,
3991Asbjorn Ulsberg,
3992Balachander Krishnamurthy,
3993Barry Leiba,
3994Ben Laurie,
3995Benjamin Niven-Jenkins,
3996Bil Corry,
3997Bill Burke,
3998Bjoern Hoehrmann,
3999Bob Scheifler,
4000Boris Zbarsky,
4001Brett Slatkin,
4002Brian Kell,
4003Brian McBarron,
4004Brian Pane,
4005Brian Smith,
4006Bryce Nesbitt,
4007Cameron Heavon-Jones,
4008Carl Kugler,
4009Carsten Bormann,
4010Charles Fry,
4011Chris Newman,
4012Cyrus Daboo,
4013Dale Robert Anderson,
4014Dan Winship,
4015Daniel Stenberg,
4016Dave Cridland,
4017Dave Crocker,
4018Dave Kristol,
4019David Booth,
4020David Singer,
4021David W. Morris,
4022Diwakar Shetty,
4023Dmitry Kurochkin,
4024Drummond Reed,
4025Duane Wessels,
4026Edward Lee,
4027Eliot Lear,
4028Eran Hammer-Lahav,
4029Eric D. Williams,
4030Eric J. Bowman,
4031Eric Lawrence,
4032Eric Rescorla,
4033Erik Aronesty,
4034Florian Weimer,
4035Frank Ellermann,
4036Fred Bohle,
4037Geoffrey Sneddon,
4038Gervase Markham,
4039Greg Wilkins,
4040Harald Tveit Alvestrand,
4041Harry Halpin,
4042Helge Hess,
4043Henrik Nordstrom,
4044Henry S. Thompson,
4045Henry Story,
4046Herbert van de Sompel,
4047Howard Melman,
4048Hugo Haas,
4049Ian Hickson,
4050Ingo Struck,
4051J. Ross Nicoll,
4052James H. Manger,
4053James Lacey,
4054James M. Snell,
4055Jamie Lokier,
4056Jan Algermissen,
4057Jeff Hodges (for coming up with the term 'effective Request-URI'),
4058Jeff Walden,
4059Jim Luther,
4060Joe D. Williams,
4061Joe Gregorio,
4062Joe Orton,
4063John C. Klensin,
4064John C. Mallery,
4065John Cowan,
4066John Kemp,
4067John Panzer,
4068John Schneider,
4069John Stracke,
4070Jonas Sicking,
4071Jonathan Billington,
4072Jonathan Moore,
4073Jonathan Rees,
4074Jordi Ros,
4075Joris Dobbelsteen,
4076Josh Cohen,
4077Julien Pierre,
4078Jungshik Shin,
4079Justin Chapweske,
4080Justin Erenkrantz,
4081Justin James,
4082Kalvinder Singh,
4083Karl Dubost,
4084Keith Hoffman,
4085Keith Moore,
4086Koen Holtman,
4087Konstantin Voronkov,
4088Kris Zyp,
4089Lisa Dusseault,
4090Maciej Stachowiak,
4091Marc Schneider,
4092Marc Slemko,
4093Mark Baker,
4094Mark Nottingham (Working Group chair),
4095Mark Pauley,
4096Markus Lanthaler,
4097Martin J. Duerst,
4098Martin Thomson,
4099Matt Lynch,
4100Matthew Cox,
4101Max Clark,
4102Michael Burrows,
4103Michael Hausenblas,
4104Mike Amundsen,
4105Mike Belshe,
4106Mike Kelly,
4107Mike Schinkel,
4108Miles Sabin,
4109Mykyta Yevstifeyev,
4110Nathan Rixham,
4111Nicholas Shanks,
4112Nico Williams,
4113Nicolas Alvarez,
4114Nicolas Mailhot,
4115Noah Slater,
4116Pablo Castro,
4117Pat Hayes,
4118Patrick R. McManus,
4119Paul E. Jones,
4120Paul Hoffman,
4121Paul Marquess,
4122Peter Saint-Andre,
4123Peter Watkins,
4124Phil Archer,
4125Phillip Hallam-Baker,
4126Poul-Henning Kamp,
4127Preethi Natarajan,
4128Ray Polk,
4129Reto Bachmann-Gmuer,
4130Richard Cyganiak,
4131Robert Brewer,
4132Robert Collins,
4133Robert O'Callahan,
4134Robert Olofsson,
4135Robert Sayre,
4136Robert Siemer,
4137Robert de Wilde,
4138Roberto Javier Godoy,
4139Ronny Widjaja,
4140S. Mike Dierken,
4141Salvatore Loreto,
4142Sam Johnston,
4143Sam Ruby,
4144Scott Lawrence (for maintaining the original issues list),
4145Sean B. Palmer,
4146Shane McCarron,
4147Stefan Eissing,
4148Stefan Tilkov,
4149Stefanos Harhalakis,
4150Stephane Bortzmeyer,
4151Stephen Farrell,
4152Stuart Williams,
4153Subbu Allamaraju,
4154Sylvain Hellegouarch,
4155Tapan Divekar,
4156Ted Hardie,
4157Thomas Broyer,
4158Thomas Nordin,
4159Thomas Roessler,
4160Tim Morgan,
4161Tim Olsen,
4162Travis Snoozy,
4163Tyler Close,
4164Vincent Murphy,
4165Wenbo Zhu,
4166Werner Baumann,
4167Wilbur Streett,
4168Wilfredo Sanchez Vega,
4169William A. Rowe Jr.,
4170William Chan,
4171Willy Tarreau,
4172Xiaoshu Wang,
4173Yaron Goland,
4174Yngve Nysaeter Pettersen,
4175Yogesh Bang,
4176Yutaka Oiwa,
4177Zed A. Shaw, and
4178Zhong Yu.
4180<?ENDINC acks ?>
4186<references title="Normative References">
4188<reference anchor="ISO-8859-1">
4189  <front>
4190    <title>
4191     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
4192    </title>
4193    <author>
4194      <organization>International Organization for Standardization</organization>
4195    </author>
4196    <date year="1998"/>
4197  </front>
4198  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
4201<reference anchor="Part2">
4202  <front>
4203    <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
4204    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4205      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4206      <address><email></email></address>
4207    </author>
4208    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4209      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
4210      <address><email></email></address>
4211    </author>
4212    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4213      <organization abbrev="HP">Hewlett-Packard Company</organization>
4214      <address><email></email></address>
4215    </author>
4216    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
4217      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4218      <address><email></email></address>
4219    </author>
4220    <author initials="L." surname="Masinter" fullname="Larry Masinter">
4221      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4222      <address><email></email></address>
4223    </author>
4224    <author initials="P." surname="Leach" fullname="Paul J. Leach">
4225      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4226      <address><email></email></address>
4227    </author>
4228    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4229      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4230      <address><email></email></address>
4231    </author>
4232    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4233      <organization abbrev="W3C">World Wide Web Consortium</organization>
4234      <address><email></email></address>
4235    </author>
4236    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4237      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4238      <address><email></email></address>
4239    </author>
4240    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4241  </front>
4242  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
4243  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
4246<reference anchor="Part3">
4247  <front>
4248    <title abbrev="HTTP/1.1">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
4249    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4250      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4251      <address><email></email></address>
4252    </author>
4253    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4254      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
4255      <address><email></email></address>
4256    </author>
4257    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4258      <organization abbrev="HP">Hewlett-Packard Company</organization>
4259      <address><email></email></address>
4260    </author>
4261    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
4262      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4263      <address><email></email></address>
4264    </author>
4265    <author initials="L." surname="Masinter" fullname="Larry Masinter">
4266      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4267      <address><email></email></address>
4268    </author>
4269    <author initials="P." surname="Leach" fullname="Paul J. Leach">
4270      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4271      <address><email></email></address>
4272    </author>
4273    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4274      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4275      <address><email></email></address>
4276    </author>
4277    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4278      <organization abbrev="W3C">World Wide Web Consortium</organization>
4279      <address><email></email></address>
4280    </author>
4281    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4282      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4283      <address><email></email></address>
4284    </author>
4285    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4286  </front>
4287  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p3-payload-&ID-VERSION;"/>
4288  <x:source href="p3-payload.xml" basename="p3-payload"/>
4291<reference anchor="Part6">
4292  <front>
4293    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
4294    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4295      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4296      <address><email></email></address>
4297    </author>
4298    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4299      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
4300      <address><email></email></address>
4301    </author>
4302    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4303      <organization abbrev="HP">Hewlett-Packard Company</organization>
4304      <address><email></email></address>
4305    </author>
4306    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
4307      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4308      <address><email></email></address>
4309    </author>
4310    <author initials="L." surname="Masinter" fullname="Larry Masinter">
4311      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4312      <address><email></email></address>
4313    </author>
4314    <author initials="P." surname="Leach" fullname="Paul J. Leach">
4315      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4316      <address><email></email></address>
4317    </author>
4318    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4319      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4320      <address><email></email></address>
4321    </author>
4322    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4323      <organization abbrev="W3C">World Wide Web Consortium</organization>
4324      <address><email></email></address>
4325    </author>
4326    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
4327      <organization>Rackspace</organization>
4328      <address><email></email></address>
4329    </author>
4330    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4331      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4332      <address><email></email></address>
4333    </author>
4334    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4335  </front>
4336  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
4337  <x:source href="p6-cache.xml" basename="p6-cache"/>
4340<reference anchor="RFC5234">
4341  <front>
4342    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
4343    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
4344      <organization>Brandenburg InternetWorking</organization>
4345      <address>
4346        <email></email>
4347      </address> 
4348    </author>
4349    <author initials="P." surname="Overell" fullname="Paul Overell">
4350      <organization>THUS plc.</organization>
4351      <address>
4352        <email></email>
4353      </address>
4354    </author>
4355    <date month="January" year="2008"/>
4356  </front>
4357  <seriesInfo name="STD" value="68"/>
4358  <seriesInfo name="RFC" value="5234"/>
4361<reference anchor="RFC2119">
4362  <front>
4363    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
4364    <author initials="S." surname="Bradner" fullname="Scott Bradner">
4365      <organization>Harvard University</organization>
4366      <address><email></email></address>
4367    </author>
4368    <date month="March" year="1997"/>
4369  </front>
4370  <seriesInfo name="BCP" value="14"/>
4371  <seriesInfo name="RFC" value="2119"/>
4374<reference anchor="RFC3986">
4375 <front>
4376  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
4377  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
4378    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4379    <address>
4380       <email></email>
4381       <uri></uri>
4382    </address>
4383  </author>
4384  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
4385    <organization abbrev="Day Software">Day Software</organization>
4386    <address>
4387      <email></email>
4388      <uri></uri>
4389    </address>
4390  </author>
4391  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
4392    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
4393    <address>
4394      <email></email>
4395      <uri></uri>
4396    </address>
4397  </author>
4398  <date month='January' year='2005'></date>
4399 </front>
4400 <seriesInfo name="STD" value="66"/>
4401 <seriesInfo name="RFC" value="3986"/>
4404<reference anchor="USASCII">
4405  <front>
4406    <title>Coded Character Set -- 7-bit American Standard Code for Information Interchange</title>
4407    <author>
4408      <organization>American National Standards Institute</organization>
4409    </author>
4410    <date year="1986"/>
4411  </front>
4412  <seriesInfo name="ANSI" value="X3.4"/>
4415<reference anchor="RFC1950">
4416  <front>
4417    <title>ZLIB Compressed Data Format Specification version 3.3</title>
4418    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
4419      <organization>Aladdin Enterprises</organization>
4420      <address><email></email></address>
4421    </author>
4422    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"/>
4423    <date month="May" year="1996"/>
4424  </front>
4425  <seriesInfo name="RFC" value="1950"/>
4426  <!--<annotation>
4427    RFC 1950 is an Informational RFC, thus it might be less stable than
4428    this specification. On the other hand, this downward reference was
4429    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4430    therefore it is unlikely to cause problems in practice. See also
4431    <xref target="BCP97"/>.
4432  </annotation>-->
4435<reference anchor="RFC1951">
4436  <front>
4437    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
4438    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
4439      <organization>Aladdin Enterprises</organization>
4440      <address><email></email></address>
4441    </author>
4442    <date month="May" year="1996"/>
4443  </front>
4444  <seriesInfo name="RFC" value="1951"/>
4445  <!--<annotation>
4446    RFC 1951 is an Informational RFC, thus it might be less stable than
4447    this specification. On the other hand, this downward reference was
4448    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4449    therefore it is unlikely to cause problems in practice. See also
4450    <xref target="BCP97"/>.
4451  </annotation>-->
4454<reference anchor="RFC1952">
4455  <front>
4456    <title>GZIP file format specification version 4.3</title>
4457    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
4458      <organization>Aladdin Enterprises</organization>
4459      <address><email></email></address>
4460    </author>
4461    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
4462      <address><email></email></address>
4463    </author>
4464    <author initials="M." surname="Adler" fullname="Mark Adler">
4465      <address><email></email></address>
4466    </author>
4467    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
4468      <address><email></email></address>
4469    </author>
4470    <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">
4471      <address><email></email></address>
4472    </author>
4473    <date month="May" year="1996"/>
4474  </front>
4475  <seriesInfo name="RFC" value="1952"/>
4476  <!--<annotation>
4477    RFC 1952 is an Informational RFC, thus it might be less stable than
4478    this specification. On the other hand, this downward reference was
4479    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4480    therefore it is unlikely to cause problems in practice. See also
4481    <xref target="BCP97"/>.
4482  </annotation>-->
4487<references title="Informative References">
4489<reference anchor="Nie1997" target="">
4490  <front>
4491    <title>Network Performance Effects of HTTP/1.1, CSS1, and PNG</title>
4492    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen"/>
4493    <author initials="J." surname="Gettys" fullname="J. Gettys"/>
4494    <author initials="E." surname="Prud'hommeaux" fullname="E. Prud'hommeaux"/>
4495    <author initials="H." surname="Lie" fullname="H. Lie"/>
4496    <author initials="C." surname="Lilley" fullname="C. Lilley"/>
4497    <date year="1997" month="September"/>
4498  </front>
4499  <seriesInfo name="ACM" value="Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication SIGCOMM '97"/>
4502<reference anchor="Pad1995" target="">
4503  <front>
4504    <title>Improving HTTP Latency</title>
4505    <author initials="V.N." surname="Padmanabhan" fullname="Venkata N. Padmanabhan"/>
4506    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul"/>
4507    <date year="1995" month="December"/>
4508  </front>
4509  <seriesInfo name="Computer Networks and ISDN Systems" value="v. 28, pp. 25-35"/>
4512<reference anchor='RFC1919'>
4513  <front>
4514    <title>Classical versus Transparent IP Proxies</title>
4515    <author initials='M.' surname='Chatel' fullname='Marc Chatel'>
4516      <address><email></email></address>
4517    </author>
4518    <date year='1996' month='March' />
4519  </front>
4520  <seriesInfo name='RFC' value='1919' />
4523<reference anchor="RFC1945">
4524  <front>
4525    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
4526    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4527      <organization>MIT, Laboratory for Computer Science</organization>
4528      <address><email></email></address>
4529    </author>
4530    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4531      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4532      <address><email></email></address>
4533    </author>
4534    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4535      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
4536      <address><email></email></address>
4537    </author>
4538    <date month="May" year="1996"/>
4539  </front>
4540  <seriesInfo name="RFC" value="1945"/>
4543<reference anchor="RFC2045">
4544  <front>
4545    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
4546    <author initials="N." surname="Freed" fullname="Ned Freed">
4547      <organization>Innosoft International, Inc.</organization>
4548      <address><email></email></address>
4549    </author>
4550    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
4551      <organization>First Virtual Holdings</organization>
4552      <address><email></email></address>
4553    </author>
4554    <date month="November" year="1996"/>
4555  </front>
4556  <seriesInfo name="RFC" value="2045"/>
4559<reference anchor="RFC2047">
4560  <front>
4561    <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
4562    <author initials="K." surname="Moore" fullname="Keith Moore">
4563      <organization>University of Tennessee</organization>
4564      <address><email></email></address>
4565    </author>
4566    <date month="November" year="1996"/>
4567  </front>
4568  <seriesInfo name="RFC" value="2047"/>
4571<reference anchor="RFC2068">
4572  <front>
4573    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
4574    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
4575      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4576      <address><email></email></address>
4577    </author>
4578    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4579      <organization>MIT Laboratory for Computer Science</organization>
4580      <address><email></email></address>
4581    </author>
4582    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4583      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
4584      <address><email></email></address>
4585    </author>
4586    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4587      <organization>MIT Laboratory for Computer Science</organization>
4588      <address><email></email></address>
4589    </author>
4590    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4591      <organization>MIT Laboratory for Computer Science</organization>
4592      <address><email></email></address>
4593    </author>
4594    <date month="January" year="1997"/>
4595  </front>
4596  <seriesInfo name="RFC" value="2068"/>
4599<reference anchor="RFC2145">
4600  <front>
4601    <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
4602    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
4603      <organization>Western Research Laboratory</organization>
4604      <address><email></email></address>
4605    </author>
4606    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4607      <organization>Department of Information and Computer Science</organization>
4608      <address><email></email></address>
4609    </author>
4610    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4611      <organization>MIT Laboratory for Computer Science</organization>
4612      <address><email></email></address>
4613    </author>
4614    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4615      <organization>W3 Consortium</organization>
4616      <address><email></email></address>
4617    </author>
4618    <date month="May" year="1997"/>
4619  </front>
4620  <seriesInfo name="RFC" value="2145"/>
4623<reference anchor="RFC2616">
4624  <front>
4625    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
4626    <author initials="R." surname="Fielding" fullname="R. Fielding">
4627      <organization>University of California, Irvine</organization>
4628      <address><email></email></address>
4629    </author>
4630    <author initials="J." surname="Gettys" fullname="J. Gettys">
4631      <organization>W3C</organization>
4632      <address><email></email></address>
4633    </author>
4634    <author initials="J." surname="Mogul" fullname="J. Mogul">
4635      <organization>Compaq Computer Corporation</organization>
4636      <address><email></email></address>
4637    </author>
4638    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
4639      <organization>MIT Laboratory for Computer Science</organization>
4640      <address><email></email></address>
4641    </author>
4642    <author initials="L." surname="Masinter" fullname="L. Masinter">
4643      <organization>Xerox Corporation</organization>
4644      <address><email></email></address>
4645    </author>
4646    <author initials="P." surname="Leach" fullname="P. Leach">
4647      <organization>Microsoft Corporation</organization>
4648      <address><email></email></address>
4649    </author>
4650    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
4651      <organization>W3C</organization>
4652      <address><email></email></address>
4653    </author>
4654    <date month="June" year="1999"/>
4655  </front>
4656  <seriesInfo name="RFC" value="2616"/>
4659<reference anchor='RFC2817'>
4660  <front>
4661    <title>Upgrading to TLS Within HTTP/1.1</title>
4662    <author initials='R.' surname='Khare' fullname='R. Khare'>
4663      <organization>4K Associates / UC Irvine</organization>
4664      <address><email></email></address>
4665    </author>
4666    <author initials='S.' surname='Lawrence' fullname='S. Lawrence'>
4667      <organization>Agranat Systems, Inc.</organization>
4668      <address><email></email></address>
4669    </author>
4670    <date year='2000' month='May' />
4671  </front>
4672  <seriesInfo name='RFC' value='2817' />
4675<reference anchor='RFC2818'>
4676  <front>
4677    <title>HTTP Over TLS</title>
4678    <author initials='E.' surname='Rescorla' fullname='Eric Rescorla'>
4679      <organization>RTFM, Inc.</organization>
4680      <address><email></email></address>
4681    </author>
4682    <date year='2000' month='May' />
4683  </front>
4684  <seriesInfo name='RFC' value='2818' />
4687<reference anchor='RFC2965'>
4688  <front>
4689    <title>HTTP State Management Mechanism</title>
4690    <author initials='D. M.' surname='Kristol' fullname='David M. Kristol'>
4691      <organization>Bell Laboratories, Lucent Technologies</organization>
4692      <address><email></email></address>
4693    </author>
4694    <author initials='L.' surname='Montulli' fullname='Lou Montulli'>
4695      <organization>, Inc.</organization>
4696      <address><email></email></address>
4697    </author>
4698    <date year='2000' month='October' />
4699  </front>
4700  <seriesInfo name='RFC' value='2965' />
4703<reference anchor='RFC3040'>
4704  <front>
4705    <title>Internet Web Replication and Caching Taxonomy</title>
4706    <author initials='I.' surname='Cooper' fullname='I. Cooper'>
4707      <organization>Equinix, Inc.</organization>
4708    </author>
4709    <author initials='I.' surname='Melve' fullname='I. Melve'>
4710      <organization>UNINETT</organization>
4711    </author>
4712    <author initials='G.' surname='Tomlinson' fullname='G. Tomlinson'>
4713      <organization>CacheFlow Inc.</organization>
4714    </author>
4715    <date year='2001' month='January' />
4716  </front>
4717  <seriesInfo name='RFC' value='3040' />
4720<reference anchor='RFC3864'>
4721  <front>
4722    <title>Registration Procedures for Message Header Fields</title>
4723    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
4724      <organization>Nine by Nine</organization>
4725      <address><email></email></address>
4726    </author>
4727    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
4728      <organization>BEA Systems</organization>
4729      <address><email></email></address>
4730    </author>
4731    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
4732      <organization>HP Labs</organization>
4733      <address><email></email></address>
4734    </author>
4735    <date year='2004' month='September' />
4736  </front>
4737  <seriesInfo name='BCP' value='90' />
4738  <seriesInfo name='RFC' value='3864' />
4741<reference anchor='RFC4033'>
4742  <front>
4743    <title>DNS Security Introduction and Requirements</title>
4744    <author initials='R.' surname='Arends' fullname='R. Arends'/>
4745    <author initials='R.' surname='Austein' fullname='R. Austein'/>
4746    <author initials='M.' surname='Larson' fullname='M. Larson'/>
4747    <author initials='D.' surname='Massey' fullname='D. Massey'/>
4748    <author initials='S.' surname='Rose' fullname='S. Rose'/>
4749    <date year='2005' month='March' />
4750  </front>
4751  <seriesInfo name='RFC' value='4033' />
4754<reference anchor="RFC4288">
4755  <front>
4756    <title>Media Type Specifications and Registration Procedures</title>
4757    <author initials="N." surname="Freed" fullname="N. Freed">
4758      <organization>Sun Microsystems</organization>
4759      <address>
4760        <email></email>
4761      </address>
4762    </author>
4763    <author initials="J." surname="Klensin" fullname="J. Klensin">
4764      <address>
4765        <email></email>
4766      </address>
4767    </author>
4768    <date year="2005" month="December"/>
4769  </front>
4770  <seriesInfo name="BCP" value="13"/>
4771  <seriesInfo name="RFC" value="4288"/>
4774<reference anchor='RFC4395'>
4775  <front>
4776    <title>Guidelines and Registration Procedures for New URI Schemes</title>
4777    <author initials='T.' surname='Hansen' fullname='T. Hansen'>
4778      <organization>AT&amp;T Laboratories</organization>
4779      <address>
4780        <email></email>
4781      </address>
4782    </author>
4783    <author initials='T.' surname='Hardie' fullname='T. Hardie'>
4784      <organization>Qualcomm, Inc.</organization>
4785      <address>
4786        <email></email>
4787      </address>
4788    </author>
4789    <author initials='L.' surname='Masinter' fullname='L. Masinter'>
4790      <organization>Adobe Systems</organization>
4791      <address>
4792        <email></email>
4793      </address>
4794    </author>
4795    <date year='2006' month='February' />
4796  </front>
4797  <seriesInfo name='BCP' value='115' />
4798  <seriesInfo name='RFC' value='4395' />
4801<reference anchor='RFC4559'>
4802  <front>
4803    <title>SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows</title>
4804    <author initials='K.' surname='Jaganathan' fullname='K. Jaganathan'/>
4805    <author initials='L.' surname='Zhu' fullname='L. Zhu'/>
4806    <author initials='J.' surname='Brezak' fullname='J. Brezak'/>
4807    <date year='2006' month='June' />
4808  </front>
4809  <seriesInfo name='RFC' value='4559' />
4812<reference anchor='RFC5226'>
4813  <front>
4814    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
4815    <author initials='T.' surname='Narten' fullname='T. Narten'>
4816      <organization>IBM</organization>
4817      <address><email></email></address>
4818    </author>
4819    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
4820      <organization>Google</organization>
4821      <address><email></email></address>
4822    </author>
4823    <date year='2008' month='May' />
4824  </front>
4825  <seriesInfo name='BCP' value='26' />
4826  <seriesInfo name='RFC' value='5226' />
4829<reference anchor="RFC5322">
4830  <front>
4831    <title>Internet Message Format</title>
4832    <author initials="P." surname="Resnick" fullname="P. Resnick">
4833      <organization>Qualcomm Incorporated</organization>
4834    </author>
4835    <date year="2008" month="October"/>
4836  </front>
4837  <seriesInfo name="RFC" value="5322"/>
4840<reference anchor="RFC6265">
4841  <front>
4842    <title>HTTP State Management Mechanism</title>
4843    <author initials="A." surname="Barth" fullname="Adam Barth">
4844      <organization abbrev="U.C. Berkeley">
4845        University of California, Berkeley
4846      </organization>
4847      <address><email></email></address>
4848    </author>
4849    <date year="2011" month="April" />
4850  </front>
4851  <seriesInfo name="RFC" value="6265"/>
4854<!--<reference anchor='BCP97'>
4855  <front>
4856    <title>Handling Normative References to Standards-Track Documents</title>
4857    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
4858      <address>
4859        <email></email>
4860      </address>
4861    </author>
4862    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
4863      <organization>MIT</organization>
4864      <address>
4865        <email></email>
4866      </address>
4867    </author>
4868    <date year='2007' month='June' />
4869  </front>
4870  <seriesInfo name='BCP' value='97' />
4871  <seriesInfo name='RFC' value='4897' />
4874<reference anchor="Kri2001" target="">
4875  <front>
4876    <title>HTTP Cookies: Standards, Privacy, and Politics</title>
4877    <author initials="D." surname="Kristol" fullname="David M. Kristol"/>
4878    <date year="2001" month="November"/>
4879  </front>
4880  <seriesInfo name="ACM Transactions on Internet Technology" value="Vol. 1, #2"/>
4883<reference anchor="Spe" target="">
4884  <front>
4885    <title>Analysis of HTTP Performance Problems</title>
4886    <author initials="S." surname="Spero" fullname="Simon E. Spero"/>
4887    <date/>
4888  </front>
4891<reference anchor="Tou1998" target="">
4892  <front>
4893  <title>Analysis of HTTP Performance</title>
4894  <author initials="J." surname="Touch" fullname="Joe Touch">
4895    <organization>USC/Information Sciences Institute</organization>
4896    <address><email></email></address>
4897  </author>
4898  <author initials="J." surname="Heidemann" fullname="John Heidemann">
4899    <organization>USC/Information Sciences Institute</organization>
4900    <address><email></email></address>
4901  </author>
4902  <author initials="K." surname="Obraczka" fullname="Katia Obraczka">
4903    <organization>USC/Information Sciences Institute</organization>
4904    <address><email></email></address>
4905  </author>
4906  <date year="1998" month="Aug"/>
4907  </front>
4908  <seriesInfo name="ISI Research Report" value="ISI/RR-98-463"/>
4909  <annotation>(original report dated Aug. 1996)</annotation>
4915<section title="HTTP Version History" anchor="compatibility">
4917   HTTP has been in use by the World-Wide Web global information initiative
4918   since 1990. The first version of HTTP, later referred to as HTTP/0.9,
4919   was a simple protocol for hypertext data transfer across the Internet
4920   with only a single request method (GET) and no metadata.
4921   HTTP/1.0, as defined by <xref target="RFC1945"/>, added a range of request
4922   methods and MIME-like messaging that could include metadata about the data
4923   transferred and modifiers on the request/response semantics. However,
4924   HTTP/1.0 did not sufficiently take into consideration the effects of
4925   hierarchical proxies, caching, the need for persistent connections, or
4926   name-based virtual hosts. The proliferation of incompletely-implemented
4927   applications calling themselves "HTTP/1.0" further necessitated a
4928   protocol version change in order for two communicating applications
4929   to determine each other's true capabilities.
4932   HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent
4933   requirements that enable reliable implementations, adding only
4934   those new features that will either be safely ignored by an HTTP/1.0
4935   recipient or only sent when communicating with a party advertising
4936   conformance with HTTP/1.1.
4939   It is beyond the scope of a protocol specification to mandate
4940   conformance with previous versions. HTTP/1.1 was deliberately
4941   designed, however, to make supporting previous versions easy.
4942   We would expect a general-purpose HTTP/1.1 server to understand
4943   any valid request in the format of HTTP/1.0 and respond appropriately
4944   with an HTTP/1.1 message that only uses features understood (or
4945   safely ignored) by HTTP/1.0 clients.  Likewise, we would expect
4946   an HTTP/1.1 client to understand any valid HTTP/1.0 response.
4949   Since HTTP/0.9 did not support header fields in a request,
4950   there is no mechanism for it to support name-based virtual
4951   hosts (selection of resource by inspection of the Host header
4952   field).  Any server that implements name-based virtual hosts
4953   ought to disable support for HTTP/0.9.  Most requests that
4954   appear to be HTTP/0.9 are, in fact, badly constructed HTTP/1.x
4955   requests wherein a buggy client failed to properly encode
4956   linear whitespace found in a URI reference and placed in
4957   the request-target.
4960<section title="Changes from HTTP/1.0" anchor="changes.from.1.0">
4962   This section summarizes major differences between versions HTTP/1.0
4963   and HTTP/1.1.
4966<section title="Multi-homed Web Servers" anchor="">
4968   The requirements that clients and servers support the Host header
4969   field (<xref target=""/>), report an error if it is
4970   missing from an HTTP/1.1 request, and accept absolute URIs (<xref target="request-target"/>)
4971   are among the most important changes defined by HTTP/1.1.
4974   Older HTTP/1.0 clients assumed a one-to-one relationship of IP
4975   addresses and servers; there was no other established mechanism for
4976   distinguishing the intended server of a request than the IP address
4977   to which that request was directed. The Host header field was
4978   introduced during the development of HTTP/1.1 and, though it was
4979   quickly implemented by most HTTP/1.0 browsers, additional requirements
4980   were placed on all HTTP/1.1 requests in order to ensure complete
4981   adoption.  At the time of this writing, most HTTP-based services
4982   are dependent upon the Host header field for targeting requests.
4986<section title="Keep-Alive Connections" anchor="compatibility.with.http.1.0.persistent.connections">
4988   In HTTP/1.0, each connection is established by the client prior to the
4989   request and closed by the server after sending the response. However, some
4990   implementations implement the explicitly negotiated ("Keep-Alive") version
4991   of persistent connections described in <xref x:sec="19.7.1" x:fmt="of"
4992   target="RFC2068"/>.
4995   Some clients and servers might wish to be compatible with these previous
4996   approaches to persistent connections, by explicitly negotiating for them
4997   with a "Connection: keep-alive" request header field. However, some
4998   experimental implementations of HTTP/1.0 persistent connections are faulty;
4999   for example, if a HTTP/1.0 proxy server doesn't understand Connection, it
5000   will erroneously forward that header to the next inbound server, which
5001   would result in a hung connection.
5004   One attempted solution was the introduction of a Proxy-Connection header,
5005   targeted specifically at proxies. In practice, this was also unworkable,
5006   because proxies are often deployed in multiple layers, bringing about the
5007   same problem discussed above.
5010   As a result, clients are encouraged not to send the Proxy-Connection header
5011   in any requests.
5014   Clients are also encouraged to consider the use of Connection: keep-alive
5015   in requests carefully; while they can enable persistent connections with
5016   HTTP/1.0 servers, clients using them need will need to monitor the
5017   connection for "hung" requests (which indicate that the client ought stop
5018   sending the header), and this mechanism ought not be used by clients at all
5019   when a proxy is being used.
5024<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
5026  Clarify that the string "HTTP" in the HTTP-version ABFN production is case
5027  sensitive. Restrict the version numbers to be single digits due to the fact
5028  that implementations are known to handle multi-digit version numbers
5029  incorrectly.
5030  (<xref target="http.version"/>)
5033  Update use of abs_path production from RFC 1808 to the path-absolute + query
5034  components of RFC 3986. State that the asterisk form is allowed for the OPTIONS
5035  request method only.
5036  (<xref target="request-target"/>)
5039  Require that invalid whitespace around field-names be rejected.
5040  (<xref target="header.fields"/>)
5043  Rules about implicit linear whitespace between certain grammar productions
5044  have been removed; now whitespace is only allowed where specifically
5045  defined in the ABNF.
5046  (<xref target="whitespace"/>)
5049  The NUL octet is no longer allowed in comment and quoted-string
5050  text. The quoted-pair rule no longer allows escaping control characters other than HTAB.
5051  Non-ASCII content in header fields and reason phrase has been obsoleted and
5052  made opaque (the TEXT rule was removed).
5053  (<xref target="field.components"/>)
5056  Empty list elements in list productions have been deprecated.
5057  (<xref target="abnf.extension"/>)
5060  Require recipients to handle bogus Content-Length header fields as errors.
5061  (<xref target="message.body"/>)
5064  Remove reference to non-existent identity transfer-coding value tokens.
5065  (Sections <xref format="counter" target="message.body"/> and
5066  <xref format="counter" target="transfer.codings"/>)
5069  Clarification that the chunk length does not include the count of the octets
5070  in the chunk header and trailer. Furthermore disallowed line folding
5071  in chunk extensions, and deprecate their use.
5072  (<xref target="chunked.encoding"/>)
5075  Registration of Transfer Codings now requires IETF Review
5076  (<xref target="transfer.coding.registry"/>)
5079  Remove hard limit of two connections per server.
5080  Remove requirement to retry a sequence of requests as long it was idempotent.
5081  Remove requirements about when servers are allowed to close connections
5082  prematurely.
5083  (<xref target="persistent.practical"/>)
5086  Remove requirement to retry requests under certain cirumstances when the
5087  server prematurely closes the connection.
5088  (<xref target="message.transmission.requirements"/>)
5091  Change ABNF productions for header fields to only define the field value.
5092  (<xref target="header.field.definitions"/>)
5095  Clarify exactly when close connection options must be sent.
5096  (<xref target="header.connection"/>)
5099  Define the semantics of the "Upgrade" header field in responses other than
5100  101 (this was incorporated from <xref target="RFC2817"/>).
5101  (<xref target="header.upgrade"/>)
5105<section title="Changes from RFC 2817" anchor="changes.from.rfc.2817">
5107  Registration of Upgrade tokens now requires IETF Review
5108  (<xref target="upgrade.token.registry"/>)
5113<?BEGININC p1-messaging.abnf-appendix ?>
5114<section xmlns:x="" title="Collected ABNF" anchor="collected.abnf">
5116<artwork type="abnf" name="p1-messaging.parsed-abnf">
5117<x:ref>BWS</x:ref> = OWS
5119<x:ref>Connection</x:ref> = *( "," OWS ) connection-token *( OWS "," [ OWS
5120 connection-token ] )
5121<x:ref>Content-Length</x:ref> = 1*DIGIT
5123<x:ref>HTTP-message</x:ref> = start-line *( header-field CRLF ) CRLF [ message-body
5124 ]
5125<x:ref>HTTP-name</x:ref> = %x48.54.54.50 ; HTTP
5126<x:ref>HTTP-version</x:ref> = HTTP-name "/" DIGIT "." DIGIT
5127<x:ref>Host</x:ref> = uri-host [ ":" port ]
5129<x:ref>OWS</x:ref> = *( SP / HTAB )
5131<x:ref>RWS</x:ref> = 1*( SP / HTAB )
5133<x:ref>TE</x:ref> = [ ( "," / t-codings ) *( OWS "," [ OWS t-codings ] ) ]
5134<x:ref>Trailer</x:ref> = *( "," OWS ) field-name *( OWS "," [ OWS field-name ] )
5135<x:ref>Transfer-Encoding</x:ref> = *( "," OWS ) transfer-coding *( OWS "," [ OWS
5136 transfer-coding ] )
5138<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [RFC3986], Section 4.1&gt;
5139<x:ref>Upgrade</x:ref> = *( "," OWS ) protocol *( OWS "," [ OWS protocol ] )
5141<x:ref>Via</x:ref> = *( "," OWS ) received-protocol RWS received-by [ RWS comment ]
5142 *( OWS "," [ OWS received-protocol RWS received-by [ RWS comment ] ]
5143 )
5145<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
5146<x:ref>attribute</x:ref> = token
5147<x:ref>authority</x:ref> = &lt;authority, defined in [RFC3986], Section 3.2&gt;
5149<x:ref>chunk</x:ref> = chunk-size [ chunk-ext ] CRLF chunk-data CRLF
5150<x:ref>chunk-data</x:ref> = 1*OCTET
5151<x:ref>chunk-ext</x:ref> = *( ";" chunk-ext-name [ "=" chunk-ext-val ] )
5152<x:ref>chunk-ext-name</x:ref> = token
5153<x:ref>chunk-ext-val</x:ref> = token / quoted-str-nf
5154<x:ref>chunk-size</x:ref> = 1*HEXDIG
5155<x:ref>chunked-body</x:ref> = *chunk last-chunk trailer-part CRLF
5156<x:ref>comment</x:ref> = "(" *( ctext / quoted-cpair / comment ) ")"
5157<x:ref>connection-token</x:ref> = token
5158<x:ref>ctext</x:ref> = OWS / %x21-27 ; '!'-'''
5159 / %x2A-5B ; '*'-'['
5160 / %x5D-7E ; ']'-'~'
5161 / obs-text
5163<x:ref>field-content</x:ref> = *( HTAB / SP / VCHAR / obs-text )
5164<x:ref>field-name</x:ref> = token
5165<x:ref>field-value</x:ref> = *( field-content / obs-fold )
5167<x:ref>header-field</x:ref> = field-name ":" OWS field-value BWS
5168<x:ref>http-URI</x:ref> = "http://" authority path-abempty [ "?" query ]
5169<x:ref>https-URI</x:ref> = "https://" authority path-abempty [ "?" query ]
5171<x:ref>last-chunk</x:ref> = 1*"0" [ chunk-ext ] CRLF
5173<x:ref>message-body</x:ref> = *OCTET
5174<x:ref>method</x:ref> = token
5176<x:ref>obs-fold</x:ref> = CRLF ( SP / HTAB )
5177<x:ref>obs-text</x:ref> = %x80-FF
5179<x:ref>partial-URI</x:ref> = relative-part [ "?" query ]
5180<x:ref>path-abempty</x:ref> = &lt;path-abempty, defined in [RFC3986], Section 3.3&gt;
5181<x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in [RFC3986], Section 3.3&gt;
5182<x:ref>port</x:ref> = &lt;port, defined in [RFC3986], Section 3.2.3&gt;
5183<x:ref>protocol</x:ref> = protocol-name [ "/" protocol-version ]
5184<x:ref>protocol-name</x:ref> = token
5185<x:ref>protocol-version</x:ref> = token
5186<x:ref>pseudonym</x:ref> = token
5188<x:ref>qdtext</x:ref> = OWS / "!" / %x23-5B ; '#'-'['
5189 / %x5D-7E ; ']'-'~'
5190 / obs-text
5191<x:ref>qdtext-nf</x:ref> = HTAB / SP / "!" / %x23-5B ; '#'-'['
5192 / %x5D-7E ; ']'-'~'
5193 / obs-text
5194<x:ref>query</x:ref> = &lt;query, defined in [RFC3986], Section 3.4&gt;
5195<x:ref>quoted-cpair</x:ref> = "\" ( HTAB / SP / VCHAR / obs-text )
5196<x:ref>quoted-pair</x:ref> = "\" ( HTAB / SP / VCHAR / obs-text )
5197<x:ref>quoted-str-nf</x:ref> = DQUOTE *( qdtext-nf / quoted-pair ) DQUOTE
5198<x:ref>quoted-string</x:ref> = DQUOTE *( qdtext / quoted-pair ) DQUOTE
5199<x:ref>qvalue</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
5201<x:ref>reason-phrase</x:ref> = *( HTAB / SP / VCHAR / obs-text )
5202<x:ref>received-by</x:ref> = ( uri-host [ ":" port ] ) / pseudonym
5203<x:ref>received-protocol</x:ref> = [ protocol-name "/" ] protocol-version
5204<x:ref>relative-part</x:ref> = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;
5205<x:ref>request-line</x:ref> = method SP request-target SP HTTP-version CRLF
5206<x:ref>request-target</x:ref> = "*" / absolute-URI / ( path-absolute [ "?" query ] )
5207 / authority
5209<x:ref>special</x:ref> = "(" / ")" / "&lt;" / "&gt;" / "@" / "," / ";" / ":" / "\" /
5210 DQUOTE / "/" / "[" / "]" / "?" / "=" / "{" / "}"
5211<x:ref>start-line</x:ref> = request-line / status-line
5212<x:ref>status-code</x:ref> = 3DIGIT
5213<x:ref>status-line</x:ref> = HTTP-version SP status-code SP reason-phrase CRLF
5215<x:ref>t-codings</x:ref> = "trailers" / ( transfer-extension [ te-params ] )
5216<x:ref>tchar</x:ref> = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*" / "+" / "-" / "." /
5217 "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
5218<x:ref>te-ext</x:ref> = OWS ";" OWS token [ "=" word ]
5219<x:ref>te-params</x:ref> = OWS ";" OWS "q=" qvalue *te-ext
5220<x:ref>token</x:ref> = 1*tchar
5221<x:ref>trailer-part</x:ref> = *( header-field CRLF )
5222<x:ref>transfer-coding</x:ref> = "chunked" / "compress" / "deflate" / "gzip" /
5223 transfer-extension
5224<x:ref>transfer-extension</x:ref> = token *( OWS ";" OWS transfer-parameter )
5225<x:ref>transfer-parameter</x:ref> = attribute BWS "=" BWS value
5227<x:ref>uri-host</x:ref> = &lt;host, defined in [RFC3986], Section 3.2.2&gt;
5229<x:ref>value</x:ref> = word
5231<x:ref>word</x:ref> = token / quoted-string
5234<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
5235; Connection defined but not used
5236; Content-Length defined but not used
5237; HTTP-message defined but not used
5238; Host defined but not used
5239; TE defined but not used
5240; Trailer defined but not used
5241; Transfer-Encoding defined but not used
5242; URI-reference defined but not used
5243; Upgrade defined but not used
5244; Via defined but not used
5245; chunked-body defined but not used
5246; http-URI defined but not used
5247; https-URI defined but not used
5248; partial-URI defined but not used
5249; special defined but not used
5251<?ENDINC p1-messaging.abnf-appendix ?>
5253<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
5255<section title="Since RFC 2616">
5257  Extracted relevant partitions from <xref target="RFC2616"/>.
5261<section title="Since draft-ietf-httpbis-p1-messaging-00">
5263  Closed issues:
5264  <list style="symbols">
5265    <t>
5266      <eref target=""/>:
5267      "HTTP Version should be case sensitive"
5268      (<eref target=""/>)
5269    </t>
5270    <t>
5271      <eref target=""/>:
5272      "'unsafe' characters"
5273      (<eref target=""/>)
5274    </t>
5275    <t>
5276      <eref target=""/>:
5277      "Chunk Size Definition"
5278      (<eref target=""/>)
5279    </t>
5280    <t>
5281      <eref target=""/>:
5282      "Message Length"
5283      (<eref target=""/>)
5284    </t>
5285    <t>
5286      <eref target=""/>:
5287      "Media Type Registrations"
5288      (<eref target=""/>)
5289    </t>
5290    <t>
5291      <eref target=""/>:
5292      "URI includes query"
5293      (<eref target=""/>)
5294    </t>
5295    <t>
5296      <eref target=""/>:
5297      "No close on 1xx responses"
5298      (<eref target=""/>)
5299    </t>
5300    <t>
5301      <eref target=""/>:
5302      "Remove 'identity' token references"
5303      (<eref target=""/>)
5304    </t>
5305    <t>
5306      <eref target=""/>:
5307      "Import query BNF"
5308    </t>
5309    <t>
5310      <eref target=""/>:
5311      "qdtext BNF"
5312    </t>
5313    <t>
5314      <eref target=""/>:
5315      "Normative and Informative references"
5316    </t>
5317    <t>
5318      <eref target=""/>:
5319      "RFC2606 Compliance"
5320    </t>
5321    <t>
5322      <eref target=""/>:
5323      "RFC977 reference"
5324    </t>
5325    <t>
5326      <eref target=""/>:
5327      "RFC1700 references"
5328    </t>
5329    <t>
5330      <eref target=""/>:
5331      "inconsistency in date format explanation"
5332    </t>
5333    <t>
5334      <eref target=""/>:
5335      "Date reference typo"
5336    </t>
5337    <t>
5338      <eref target=""/>:
5339      "Informative references"
5340    </t>
5341    <t>
5342      <eref target=""/>:
5343      "ISO-8859-1 Reference"
5344    </t>
5345    <t>
5346      <eref target=""/>:
5347      "Normative up-to-date references"
5348    </t>
5349  </list>
5352  Other changes:
5353  <list style="symbols">
5354    <t>
5355      Update media type registrations to use RFC4288 template.
5356    </t>
5357    <t>
5358      Use names of RFC4234 core rules DQUOTE and HTAB,
5359      fix broken ABNF for chunk-data
5360      (work in progress on <eref target=""/>)
5361    </t>
5362  </list>
5366<section title="Since draft-ietf-httpbis-p1-messaging-01">
5368  Closed issues:
5369  <list style="symbols">
5370    <t>
5371      <eref target=""/>:
5372      "Bodies on GET (and other) requests"
5373    </t>
5374    <t>
5375      <eref target=""/>:
5376      "Updating to RFC4288"
5377    </t>
5378    <t>
5379      <eref target=""/>:
5380      "Status Code and Reason Phrase"
5381    </t>
5382    <t>
5383      <eref target=""/>:
5384      "rel_path not used"
5385    </t>
5386  </list>
5389  Ongoing work on ABNF conversion (<eref target=""/>):
5390  <list style="symbols">
5391    <t>
5392      Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" ->
5393      "trailer-part").
5394    </t>
5395    <t>
5396      Avoid underscore character in rule names ("http_URL" ->
5397      "http-URL", "abs_path" -> "path-absolute").
5398    </t>
5399    <t>
5400      Add rules for terms imported from URI spec ("absoluteURI", "authority",
5401      "path-absolute", "port", "query", "relativeURI", "host) &mdash; these will
5402      have to be updated when switching over to RFC3986.
5403    </t>
5404    <t>
5405      Synchronize core rules with RFC5234.
5406    </t>
5407    <t>
5408      Get rid of prose rules that span multiple lines.
5409    </t>
5410    <t>
5411      Get rid of unused rules LOALPHA and UPALPHA.
5412    </t>
5413    <t>
5414      Move "Product Tokens" section (back) into Part 1, as "token" is used
5415      in the definition of the Upgrade header field.
5416    </t>
5417    <t>
5418      Add explicit references to BNF syntax and rules imported from other parts of the specification.
5419    </t>
5420    <t>
5421      Rewrite prose rule "token" in terms of "tchar", rewrite prose rule "TEXT".
5422    </t>
5423  </list>
5427<section title="Since draft-ietf-httpbis-p1-messaging-02" anchor="changes.since.02">
5429  Closed issues:
5430  <list style="symbols">
5431    <t>
5432      <eref target=""/>:
5433      "HTTP-date vs. rfc1123-date"
5434    </t>
5435    <t>
5436      <eref target=""/>:
5437      "WS in quoted-pair"
5438    </t>
5439  </list>
5442  Ongoing work on IANA Message Header Field Registration (<eref target=""/>):
5443  <list style="symbols">
5444    <t>
5445      Reference RFC 3984, and update header field registrations for headers defined
5446      in this document.
5447    </t>
5448  </list>
5451  Ongoing work on ABNF conversion (<eref target=""/>):
5452  <list style="symbols">
5453    <t>
5454      Replace string literals when the string really is case-sensitive (HTTP-version).
5455    </t>
5456  </list>
5460<section title="Since draft-ietf-httpbis-p1-messaging-03" anchor="changes.since.03">
5462  Closed issues:
5463  <list style="symbols">
5464    <t>
5465      <eref target=""/>:
5466      "Connection closing"
5467    </t>
5468    <t>
5469      <eref target=""/>:
5470      "Move registrations and registry information to IANA Considerations"
5471    </t>
5472    <t>
5473      <eref target=""/>:
5474      "need new URL for PAD1995 reference"
5475    </t>
5476    <t>
5477      <eref target=""/>:
5478      "IANA Considerations: update HTTP URI scheme registration"
5479    </t>
5480    <t>
5481      <eref target=""/>:
5482      "Cite HTTPS URI scheme definition"
5483    </t>
5484    <t>
5485      <eref target=""/>:
5486      "List-type headers vs Set-Cookie"
5487    </t>
5488  </list>
5491  Ongoing work on ABNF conversion (<eref target=""/>):
5492  <list style="symbols">
5493    <t>
5494      Replace string literals when the string really is case-sensitive (HTTP-Date).
5495    </t>
5496    <t>
5497      Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.
5498    </t>
5499  </list>
5503<section title="Since draft-ietf-httpbis-p1-messaging-04" anchor="changes.since.04">
5505  Closed issues:
5506  <list style="symbols">
5507    <t>
5508      <eref target=""/>:
5509      "Out-of-date reference for URIs"
5510    </t>
5511    <t>
5512      <eref target=""/>:
5513      "RFC 2822 is updated by RFC 5322"
5514    </t>
5515  </list>
5518  Ongoing work on ABNF conversion (<eref target=""/>):
5519  <list style="symbols">
5520    <t>
5521      Use "/" instead of "|" for alternatives.
5522    </t>
5523    <t>
5524      Get rid of RFC822 dependency; use RFC5234 plus extensions instead.
5525    </t>
5526    <t>
5527      Only reference RFC 5234's core rules.
5528    </t>
5529    <t>
5530      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
5531      whitespace ("OWS") and required whitespace ("RWS").
5532    </t>
5533    <t>
5534      Rewrite ABNFs to spell out whitespace rules, factor out
5535      header field value format definitions.
5536    </t>
5537  </list>
5541<section title="Since draft-ietf-httpbis-p1-messaging-05" anchor="changes.since.05">
5543  Closed issues:
5544  <list style="symbols">
5545    <t>
5546      <eref target=""/>:
5547      "Header LWS"
5548    </t>
5549    <t>
5550      <eref target=""/>:
5551      "Sort 1.3 Terminology"
5552    </t>
5553    <t>
5554      <eref target=""/>:
5555      "RFC2047 encoded words"
5556    </t>
5557    <t>
5558      <eref target=""/>:
5559      "Character Encodings in TEXT"
5560    </t>
5561    <t>
5562      <eref target=""/>:
5563      "Line Folding"
5564    </t>
5565    <t>
5566      <eref target=""/>:
5567      "OPTIONS * and proxies"
5568    </t>
5569    <t>
5570      <eref target=""/>:
5571      "reason-phrase BNF"
5572    </t>
5573    <t>
5574      <eref target=""/>:
5575      "Use of TEXT"
5576    </t>
5577    <t>
5578      <eref target=""/>:
5579      "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
5580    </t>
5581    <t>
5582      <eref target=""/>:
5583      "RFC822 reference left in discussion of date formats"
5584    </t>
5585  </list>
5588  Final work on ABNF conversion (<eref target=""/>):
5589  <list style="symbols">
5590    <t>
5591      Rewrite definition of list rules, deprecate empty list elements.
5592    </t>
5593    <t>
5594      Add appendix containing collected and expanded ABNF.
5595    </t>
5596  </list>
5599  Other changes:
5600  <list style="symbols">
5601    <t>
5602      Rewrite introduction; add mostly new Architecture Section.
5603    </t>
5604    <t>
5605      Move definition of quality values from Part 3 into Part 1;
5606      make TE request header field grammar independent of accept-params (defined in Part 3).
5607    </t>
5608  </list>
5612<section title="Since draft-ietf-httpbis-p1-messaging-06" anchor="changes.since.06">
5614  Closed issues:
5615  <list style="symbols">
5616    <t>
5617      <eref target=""/>:
5618      "base for numeric protocol elements"
5619    </t>
5620    <t>
5621      <eref target=""/>:
5622      "comment ABNF"
5623    </t>
5624  </list>
5627  Partly resolved issues:
5628  <list style="symbols">
5629    <t>
5630      <eref target=""/>:
5631      "205 Bodies" (took out language that implied that there might be
5632      methods for which a request body MUST NOT be included)
5633    </t>
5634    <t>
5635      <eref target=""/>:
5636      "editorial improvements around HTTP-date"
5637    </t>
5638  </list>
5642<section title="Since draft-ietf-httpbis-p1-messaging-07" anchor="changes.since.07">
5644  Closed issues:
5645  <list style="symbols">
5646    <t>
5647      <eref target=""/>:
5648      "Repeating single-value headers"
5649    </t>
5650    <t>
5651      <eref target=""/>:
5652      "increase connection limit"
5653    </t>
5654    <t>
5655      <eref target=""/>:
5656      "IP addresses in URLs"
5657    </t>
5658    <t>
5659      <eref target=""/>:
5660      "take over HTTP Upgrade Token Registry"
5661    </t>
5662    <t>
5663      <eref target=""/>:
5664      "CR and LF in chunk extension values"
5665    </t>
5666    <t>
5667      <eref target=""/>:
5668      "HTTP/0.9 support"
5669    </t>
5670    <t>
5671      <eref target=""/>:
5672      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
5673    </t>
5674    <t>
5675      <eref target=""/>:
5676      "move definitions of gzip/deflate/compress to part 1"
5677    </t>
5678    <t>
5679      <eref target=""/>:
5680      "disallow control characters in quoted-pair"
5681    </t>
5682  </list>
5685  Partly resolved issues:
5686  <list style="symbols">
5687    <t>
5688      <eref target=""/>:
5689      "update IANA requirements wrt Transfer-Coding values" (add the
5690      IANA Considerations subsection)
5691    </t>
5692  </list>
5696<section title="Since draft-ietf-httpbis-p1-messaging-08" anchor="changes.since.08">
5698  Closed issues:
5699  <list style="symbols">
5700    <t>
5701      <eref target=""/>:
5702      "header parsing, treatment of leading and trailing OWS"
5703    </t>
5704  </list>
5707  Partly resolved issues:
5708  <list style="symbols">
5709    <t>
5710      <eref target=""/>:
5711      "Placement of 13.5.1 and 13.5.2"
5712    </t>
5713    <t>
5714      <eref target=""/>:
5715      "use of term "word" when talking about header structure"
5716    </t>
5717  </list>
5721<section title="Since draft-ietf-httpbis-p1-messaging-09" anchor="changes.since.09">
5723  Closed issues:
5724  <list style="symbols">
5725    <t>
5726      <eref target=""/>:
5727      "Clarification of the term 'deflate'"
5728    </t>
5729    <t>
5730      <eref target=""/>:
5731      "OPTIONS * and proxies"
5732    </t>
5733    <t>
5734      <eref target=""/>:
5735      "MIME-Version not listed in P1, general header fields"
5736    </t>
5737    <t>
5738      <eref target=""/>:
5739      "IANA registry for content/transfer encodings"
5740    </t>
5741    <t>
5742      <eref target=""/>:
5743      "Case-sensitivity of HTTP-date"
5744    </t>
5745    <t>
5746      <eref target=""/>:
5747      "use of term "word" when talking about header structure"
5748    </t>
5749  </list>
5752  Partly resolved issues:
5753  <list style="symbols">
5754    <t>
5755      <eref target=""/>:
5756      "Term for the requested resource's URI"
5757    </t>
5758  </list>
5762<section title="Since draft-ietf-httpbis-p1-messaging-10" anchor="changes.since.10">
5764  Closed issues:
5765  <list style="symbols">
5766    <t>
5767      <eref target=""/>:
5768      "Connection Closing"
5769    </t>
5770    <t>
5771      <eref target=""/>:
5772      "Delimiting messages with multipart/byteranges"
5773    </t>
5774    <t>
5775      <eref target=""/>:
5776      "Handling multiple Content-Length headers"
5777    </t>
5778    <t>
5779      <eref target=""/>:
5780      "Clarify entity / representation / variant terminology"
5781    </t>
5782    <t>
5783      <eref target=""/>:
5784      "consider removing the 'changes from 2068' sections"
5785    </t>
5786  </list>
5789  Partly resolved issues:
5790  <list style="symbols">
5791    <t>
5792      <eref target=""/>:
5793      "HTTP(s) URI scheme definitions"
5794    </t>
5795  </list>
5799<section title="Since draft-ietf-httpbis-p1-messaging-11" anchor="changes.since.11">
5801  Closed issues:
5802  <list style="symbols">
5803    <t>
5804      <eref target=""/>:
5805      "Trailer requirements"
5806    </t>
5807    <t>
5808      <eref target=""/>:
5809      "Text about clock requirement for caches belongs in p6"
5810    </t>
5811    <t>
5812      <eref target=""/>:
5813      "effective request URI: handling of missing host in HTTP/1.0"
5814    </t>
5815    <t>
5816      <eref target=""/>:
5817      "confusing Date requirements for clients"
5818    </t>
5819  </list>
5822  Partly resolved issues:
5823  <list style="symbols">
5824    <t>
5825      <eref target=""/>:
5826      "Handling multiple Content-Length headers"
5827    </t>
5828  </list>
5832<section title="Since draft-ietf-httpbis-p1-messaging-12" anchor="changes.since.12">
5834  Closed issues:
5835  <list style="symbols">
5836    <t>
5837      <eref target=""/>:
5838      "RFC2145 Normative"
5839    </t>
5840    <t>
5841      <eref target=""/>:
5842      "HTTP(s) URI scheme definitions" (tune the requirements on userinfo)
5843    </t>
5844    <t>
5845      <eref target=""/>:
5846      "define 'transparent' proxy"
5847    </t>
5848    <t>
5849      <eref target=""/>:
5850      "Header Classification"
5851    </t>
5852    <t>
5853      <eref target=""/>:
5854      "Is * usable as a request-uri for new methods?"
5855    </t>
5856    <t>
5857      <eref target=""/>:
5858      "Migrate Upgrade details from RFC2817"
5859    </t>
5860    <t>
5861      <eref target=""/>:
5862      "untangle ABNFs for header fields"
5863    </t>
5864    <t>
5865      <eref target=""/>:
5866      "update RFC 2109 reference"
5867    </t>
5868  </list>
5872<section title="Since draft-ietf-httpbis-p1-messaging-13" anchor="changes.since.13">
5874  Closed issues:
5875  <list style="symbols">
5876    <t>
5877      <eref target=""/>:
5878      "Allow is not in 13.5.2"
5879    </t>
5880    <t>
5881      <eref target=""/>:
5882      "Handling multiple Content-Length headers"
5883    </t>
5884    <t>
5885      <eref target=""/>:
5886      "untangle ABNFs for header fields"
5887    </t>
5888    <t>
5889      <eref target=""/>:
5890      "Content-Length ABNF broken"
5891    </t>
5892  </list>
5896<section title="Since draft-ietf-httpbis-p1-messaging-14" anchor="changes.since.14">
5898  Closed issues:
5899  <list style="symbols">
5900    <t>
5901      <eref target=""/>:
5902      "HTTP-version should be redefined as fixed length pair of DIGIT . DIGIT"
5903    </t>
5904    <t>
5905      <eref target=""/>:
5906      "Recommend minimum sizes for protocol elements"
5907    </t>
5908    <t>
5909      <eref target=""/>:
5910      "Set expectations around buffering"
5911    </t>
5912    <t>
5913      <eref target=""/>:
5914      "Considering messages in isolation"
5915    </t>
5916  </list>
5920<section title="Since draft-ietf-httpbis-p1-messaging-15" anchor="changes.since.15">
5922  Closed issues:
5923  <list style="symbols">
5924    <t>
5925      <eref target=""/>:
5926      "DNS Spoofing / DNS Binding advice"
5927    </t>
5928    <t>
5929      <eref target=""/>:
5930      "move RFCs 2145, 2616, 2817 to Historic status"
5931    </t>
5932    <t>
5933      <eref target=""/>:
5934      "\-escaping in quoted strings"
5935    </t>
5936    <t>
5937      <eref target=""/>:
5938      "'Close' should be reserved in the HTTP header field registry"
5939    </t>
5940  </list>
5944<section title="Since draft-ietf-httpbis-p1-messaging-16" anchor="changes.since.16">
5946  Closed issues:
5947  <list style="symbols">
5948    <t>
5949      <eref target=""/>:
5950      "Document HTTP's error-handling philosophy"
5951    </t>
5952    <t>
5953      <eref target=""/>:
5954      "Explain header registration"
5955    </t>
5956    <t>
5957      <eref target=""/>:
5958      "Revise Acknowledgements Sections"
5959    </t>
5960    <t>
5961      <eref target=""/>:
5962      "Retrying Requests"
5963    </t>
5964    <t>
5965      <eref target=""/>:
5966      "Closing the connection on server error"
5967    </t>
5968  </list>
5972<section title="Since draft-ietf-httpbis-p1-messaging-17" anchor="changes.since.17">
5974  Closed issues:
5975  <list style="symbols">
5976    <t>
5977      <eref target=""/>:
5978      "Clarify 'User Agent'"
5979    </t>
5980    <t>
5981      <eref target=""/>:
5982      "Define non-final responses"
5983    </t>
5984    <t>
5985      <eref target=""/>:
5986      "intended maturity level vs normative references"
5987    </t>
5988    <t>
5989      <eref target=""/>:
5990      "Intermediary rewriting of queries"
5991    </t>
5992    <t>
5993      <eref target=""/>:
5994      "Proxy-Connection and Keep-Alive"
5995    </t>
5996  </list>
6000<section title="Since draft-ietf-httpbis-p1-messaging-18" anchor="changes.since.18">
6002  Closed issues:
6003  <list style="symbols">
6004    <t>
6005      <eref target=""/>:
6006      "message-body in CONNECT response"
6007    </t>
6008    <t>
6009      <eref target=""/>:
6010      "Misplaced text on connection handling in p2"
6011    </t>
6012    <t>
6013      <eref target=""/>:
6014      "wording of line folding rule"
6015    </t>
6016    <t>
6017      <eref target=""/>:
6018      "chunk-extensions"
6019    </t>
6020    <t>
6021      <eref target=""/>:
6022      "make IANA policy definitions consistent"
6023    </t>
6024  </list>
Note: See TracBrowser for help on using the repository browser.