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

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

Move text about closing connections on error from P2 to P1 (see #302)

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 242.5 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 "February">
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 an HTTP <x:dfn>response</x:dfn>
435   message, beginning with a status line that
436   includes the protocol version, a success or error code, and textual
437   reason phrase (<xref target="status.line"/>),
438   followed by MIME-like header fields containing server
439   information, resource metadata, and payload metadata
440   (<xref target="header.fields"/>),
441   an empty line to indicate the end of the header section, and finally
442   a message body containing the payload body (if any,
443   <xref target="message.body"/>).
446   Note that 1xx responses (&status-1xx;) are not final; therefore, a server
447   can send zero or more 1xx responses, followed by exactly one final response
448   (with any other status code).
451   The following example illustrates a typical message exchange for a
452   GET request on the URI "":
455client request:
456</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
457GET /hello.txt HTTP/1.1
458User-Agent: curl/7.16.3 libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3
460Accept: */*
464server response:
465</preamble><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
466HTTP/1.1 200 OK
467Date: Mon, 27 Jul 2009 12:28:53 GMT
468Server: Apache
469Last-Modified: Wed, 22 Jul 2009 19:15:56 GMT
470ETag: "34aa387-d-1568eb00"
471Accept-Ranges: bytes
472Content-Length: <x:length-of target="exbody"/>
473Vary: Accept-Encoding
474Content-Type: text/plain
476<x:span anchor="exbody">Hello World!
480<section title="Connections and Transport Independence" anchor="transport-independence">
482   HTTP messaging is independent of the underlying transport or
483   session-layer connection protocol(s).  HTTP only presumes a reliable
484   transport with in-order delivery of requests and the corresponding
485   in-order delivery of responses.  The mapping of HTTP request and
486   response structures onto the data units of the underlying transport
487   protocol is outside the scope of this specification.
490   The specific connection protocols to be used for an interaction
491   are determined by client configuration and the target resource's URI.
492   For example, the "http" URI scheme
493   (<xref target="http.uri"/>) indicates a default connection of TCP
494   over IP, with a default TCP port of 80, but the client might be
495   configured to use a proxy via some other connection port or protocol
496   instead of using the defaults.
499   A connection might be used for multiple HTTP request/response exchanges,
500   as defined in <xref target="persistent.connections"/>.
504<section title="Intermediaries" anchor="intermediaries">
505<iref primary="true" item="intermediary"/>
507   HTTP enables the use of intermediaries to satisfy requests through
508   a chain of connections.  There are three common forms of HTTP
509   <x:dfn>intermediary</x:dfn>: proxy, gateway, and tunnel.  In some cases,
510   a single intermediary might act as an origin server, proxy, gateway,
511   or tunnel, switching behavior based on the nature of each request.
513<figure><artwork type="drawing">
514         &gt;             &gt;             &gt;             &gt;
515    <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>
516               &lt;             &lt;             &lt;             &lt;
519   The figure above shows three intermediaries (A, B, and C) between the
520   user agent and origin server. A request or response message that
521   travels the whole chain will pass through four separate connections.
522   Some HTTP communication options
523   might apply only to the connection with the nearest, non-tunnel
524   neighbor, only to the end-points of the chain, or to all connections
525   along the chain. Although the diagram is linear, each participant might
526   be engaged in multiple, simultaneous communications. For example, B
527   might be receiving requests from many clients other than A, and/or
528   forwarding requests to servers other than C, at the same time that it
529   is handling A's request.
532<iref primary="true" item="upstream"/><iref primary="true" item="downstream"/>
533<iref primary="true" item="inbound"/><iref primary="true" item="outbound"/>
534   We use the terms "<x:dfn>upstream</x:dfn>" and "<x:dfn>downstream</x:dfn>"
535   to describe various requirements in relation to the directional flow of a
536   message: all messages flow from upstream to downstream.
537   Likewise, we use the terms inbound and outbound to refer to
538   directions in relation to the request path:
539   "<x:dfn>inbound</x:dfn>" means toward the origin server and
540   "<x:dfn>outbound</x:dfn>" means toward the user agent.
542<t><iref primary="true" item="proxy"/>
543   A "<x:dfn>proxy</x:dfn>" is a message forwarding agent that is selected by the
544   client, usually via local configuration rules, to receive requests
545   for some type(s) of absolute URI and attempt to satisfy those
546   requests via translation through the HTTP interface.  Some translations
547   are minimal, such as for proxy requests for "http" URIs, whereas
548   other requests might require translation to and from entirely different
549   application-layer protocols. Proxies are often used to group an
550   organization's HTTP requests through a common intermediary for the
551   sake of security, annotation services, or shared caching.
554<iref primary="true" item="transforming proxy"/>
555<iref primary="true" item="non-transforming proxy"/>
556   An HTTP-to-HTTP proxy is called a "<x:dfn>transforming proxy</x:dfn>" if it is designed
557   or configured to modify request or response messages in a semantically
558   meaningful way (i.e., modifications, beyond those required by normal
559   HTTP processing, that change the message in a way that would be
560   significant to the original sender or potentially significant to
561   downstream recipients).  For example, a transforming proxy might be
562   acting as a shared annotation server (modifying responses to include
563   references to a local annotation database), a malware filter, a
564   format transcoder, or an intranet-to-Internet privacy filter.  Such
565   transformations are presumed to be desired by the client (or client
566   organization) that selected the proxy and are beyond the scope of
567   this specification.  However, when a proxy is not intended to transform
568   a given message, we use the term "<x:dfn>non-transforming proxy</x:dfn>" to target
569   requirements that preserve HTTP message semantics. See &status-203; and
570   &header-warning; for status and warning codes related to transformations.
572<t><iref primary="true" item="gateway"/><iref primary="true" item="reverse proxy"/>
573<iref primary="true" item="accelerator"/>
574   A "<x:dfn>gateway</x:dfn>" (a.k.a., "<x:dfn>reverse proxy</x:dfn>")
575   is a receiving agent that acts
576   as a layer above some other server(s) and translates the received
577   requests to the underlying server's protocol.  Gateways are often
578   used to encapsulate legacy or untrusted information services, to
579   improve server performance through "<x:dfn>accelerator</x:dfn>" caching, and to
580   enable partitioning or load-balancing of HTTP services across
581   multiple machines.
584   A gateway behaves as an origin server on its outbound connection and
585   as a user agent on its inbound connection.
586   All HTTP requirements applicable to an origin server
587   also apply to the outbound communication of a gateway.
588   A gateway communicates with inbound servers using any protocol that
589   it desires, including private extensions to HTTP that are outside
590   the scope of this specification.  However, an HTTP-to-HTTP gateway
591   that wishes to interoperate with third-party HTTP servers &MUST;
592   conform to HTTP user agent requirements on the gateway's inbound
593   connection and &MUST; implement the Connection
594   (<xref target="header.connection"/>) and Via (<xref target="header.via"/>)
595   header fields for both connections.
597<t><iref primary="true" item="tunnel"/>
598   A "<x:dfn>tunnel</x:dfn>" acts as a blind relay between two connections
599   without changing the messages. Once active, a tunnel is not
600   considered a party to the HTTP communication, though the tunnel might
601   have been initiated by an HTTP request. A tunnel ceases to exist when
602   both ends of the relayed connection are closed. Tunnels are used to
603   extend a virtual connection through an intermediary, such as when
604   transport-layer security is used to establish private communication
605   through a shared firewall proxy.
607<t><iref primary="true" item="interception proxy"/><iref primary="true" item="transparent proxy"/>
608<iref primary="true" item="captive portal"/>
609   In addition, there may exist network intermediaries that are not
610   considered part of the HTTP communication but nevertheless act as
611   filters or redirecting agents (usually violating HTTP semantics,
612   causing security problems, and otherwise making a mess of things).
613   Such a network intermediary, often referred to as an "<x:dfn>interception proxy</x:dfn>"
614   <xref target="RFC3040"/>, "<x:dfn>transparent proxy</x:dfn>" <xref target="RFC1919"/>,
615   or "<x:dfn>captive portal</x:dfn>",
616   differs from an HTTP proxy because it has not been selected by the client.
617   Instead, the network intermediary redirects outgoing TCP port 80 packets
618   (and occasionally other common port traffic) to an internal HTTP server.
619   Interception proxies are commonly found on public network access points,
620   as a means of enforcing account subscription prior to allowing use of
621   non-local Internet services, and within corporate firewalls to enforce
622   network usage policies.
623   They are indistinguishable from a man-in-the-middle attack.
626   HTTP is defined as a stateless protocol, meaning that each request message
627   can be understood in isolation.  Many implementations depend on HTTP's
628   stateless design in order to reuse proxied connections or dynamically
629   load balance requests across multiple servers.  Hence, servers &MUST-NOT;
630   assume that two requests on the same connection are from the same user
631   agent unless the connection is secured and specific to that agent.
632   Some non-standard HTTP extensions (e.g., <xref target="RFC4559"/>) have
633   been known to violate this requirement, resulting in security and
634   interoperability problems.
638<section title="Caches" anchor="caches">
639<iref primary="true" item="cache"/>
641   A "<x:dfn>cache</x:dfn>" is a local store of previous response messages and the
642   subsystem that controls its message storage, retrieval, and deletion.
643   A cache stores cacheable responses in order to reduce the response
644   time and network bandwidth consumption on future, equivalent
645   requests. Any client or server &MAY; employ a cache, though a cache
646   cannot be used by a server while it is acting as a tunnel.
649   The effect of a cache is that the request/response chain is shortened
650   if one of the participants along the chain has a cached response
651   applicable to that request. The following illustrates the resulting
652   chain if B has a cached copy of an earlier response from O (via C)
653   for a request which has not been cached by UA or A.
655<figure><artwork type="drawing">
656            &gt;             &gt;
657       UA =========== A =========== B - - - - - - C - - - - - - O
658                  &lt;             &lt;
660<t><iref primary="true" item="cacheable"/>
661   A response is "<x:dfn>cacheable</x:dfn>" if a cache is allowed to store a copy of
662   the response message for use in answering subsequent requests.
663   Even when a response is cacheable, there might be additional
664   constraints placed by the client or by the origin server on when
665   that cached response can be used for a particular request. HTTP
666   requirements for cache behavior and cacheable responses are
667   defined in &caching-overview;. 
670   There are a wide variety of architectures and configurations
671   of caches and proxies deployed across the World Wide Web and
672   inside large organizations. These systems include national hierarchies
673   of proxy caches to save transoceanic bandwidth, systems that
674   broadcast or multicast cache entries, organizations that distribute
675   subsets of cached data via optical media, and so on.
679<section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
681   This specification targets conformance criteria according to the role of
682   a participant in HTTP communication.  Hence, HTTP requirements are placed
683   on senders, recipients, clients, servers, user agents, intermediaries,
684   origin servers, proxies, gateways, or caches, depending on what behavior
685   is being constrained by the requirement.
688   An implementation is considered conformant if it complies with all of the
689   requirements associated with the roles it partakes in HTTP.
692   Senders &MUST-NOT; generate protocol elements that do not match the grammar
693   defined by the ABNF rules for those protocol elements.
696   Unless otherwise noted, recipients &MAY; attempt to recover a usable
697   protocol element from an invalid construct.  HTTP does not define
698   specific error handling mechanisms except when they have a direct impact
699   on security, since different applications of the protocol require
700   different error handling strategies.  For example, a Web browser might
701   wish to transparently recover from a response where the Location header
702   field doesn't parse according to the ABNF, whereas a systems control
703   client might consider any form of error recovery to be dangerous.
707<section title="Protocol Versioning" anchor="http.version">
708  <x:anchor-alias value="HTTP-Version"/>
709  <x:anchor-alias value="HTTP-Prot-Name"/>
711   HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate
712   versions of the protocol. This specification defines version "1.1".
713   The protocol version as a whole indicates the sender's conformance
714   with the set of requirements laid out in that version's corresponding
715   specification of HTTP.
718   The version of an HTTP message is indicated by an HTTP-Version field
719   in the first line of the message. HTTP-Version is case-sensitive.
721<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-Version"/><iref primary="true" item="Grammar" subitem="HTTP-Prot-Name"/>
722  <x:ref>HTTP-Version</x:ref>   = <x:ref>HTTP-Prot-Name</x:ref> "/" <x:ref>DIGIT</x:ref> "." <x:ref>DIGIT</x:ref>
723  <x:ref>HTTP-Prot-Name</x:ref> = <x:abnf-char-sequence>"HTTP"</x:abnf-char-sequence> ; "HTTP", case-sensitive
726   The HTTP version number consists of two decimal digits separated by a "."
727   (period or decimal point).  The first digit ("major version") indicates the
728   HTTP messaging syntax, whereas the second digit ("minor version") indicates
729   the highest minor version to which the sender is
730   conformant and able to understand for future communication.  The minor
731   version advertises the sender's communication capabilities even when the
732   sender is only using a backwards-compatible subset of the protocol,
733   thereby letting the recipient know that more advanced features can
734   be used in response (by servers) or in future requests (by clients).
737   When an HTTP/1.1 message is sent to an HTTP/1.0 recipient
738   <xref target="RFC1945"/> or a recipient whose version is unknown,
739   the HTTP/1.1 message is constructed such that it can be interpreted
740   as a valid HTTP/1.0 message if all of the newer features are ignored.
741   This specification places recipient-version requirements on some
742   new features so that a conformant sender will only use compatible
743   features until it has determined, through configuration or the
744   receipt of a message, that the recipient supports HTTP/1.1.
747   The interpretation of an HTTP header field does not change
748   between minor versions of the same major version, though the default
749   behavior of a recipient in the absence of such a field can change.
750   Unless specified otherwise, header fields defined in HTTP/1.1 are
751   defined for all versions of HTTP/1.x.  In particular, the Host and
752   Connection header fields ought to be implemented by all HTTP/1.x
753   implementations whether or not they advertise conformance with HTTP/1.1.
756   New header fields can be defined such that, when they are
757   understood by a recipient, they might override or enhance the
758   interpretation of previously defined header fields.  When an
759   implementation receives an unrecognized header field, the recipient
760   &MUST; ignore that header field for local processing regardless of
761   the message's HTTP version.  An unrecognized header field received
762   by a proxy &MUST; be forwarded downstream unless the header field's
763   field-name is listed in the message's Connection header-field
764   (see <xref target="header.connection"/>).
765   These requirements allow HTTP's functionality to be enhanced without
766   requiring prior update of deployed intermediaries.
769   Intermediaries that process HTTP messages (i.e., all intermediaries
770   other than those acting as tunnels) &MUST; send their own HTTP-Version
771   in forwarded messages.  In other words, they &MUST-NOT; blindly
772   forward the first line of an HTTP message without ensuring that the
773   protocol version in that message matches a version to which that
774   intermediary is conformant for both the receiving and
775   sending of messages.  Forwarding an HTTP message without rewriting
776   the HTTP-Version might result in communication errors when downstream
777   recipients use the message sender's version to determine what features
778   are safe to use for later communication with that sender.
781   An HTTP client &SHOULD; send a request version equal to the highest
782   version to which the client is conformant and
783   whose major version is no higher than the highest version supported
784   by the server, if this is known.  An HTTP client &MUST-NOT; send a
785   version to which it is not conformant.
788   An HTTP client &MAY; send a lower request version if it is known that
789   the server incorrectly implements the HTTP specification, but only
790   after the client has attempted at least one normal request and determined
791   from the response status or header fields (e.g., Server) that the
792   server improperly handles higher request versions.
795   An HTTP server &SHOULD; send a response version equal to the highest
796   version to which the server is conformant and
797   whose major version is less than or equal to the one received in the
798   request.  An HTTP server &MUST-NOT; send a version to which it is not
799   conformant.  A server &MAY; send a 505 (HTTP
800   Version Not Supported) response if it cannot send a response using the
801   major version used in the client's request.
804   An HTTP server &MAY; send an HTTP/1.0 response to an HTTP/1.0 request
805   if it is known or suspected that the client incorrectly implements the
806   HTTP specification and is incapable of correctly processing later
807   version responses, such as when a client fails to parse the version
808   number correctly or when an intermediary is known to blindly forward
809   the HTTP-Version even when it doesn't conform to the given minor
810   version of the protocol. Such protocol downgrades &SHOULD-NOT; be
811   performed unless triggered by specific client attributes, such as when
812   one or more of the request header fields (e.g., User-Agent) uniquely
813   match the values sent by a client known to be in error.
816   The intention of HTTP's versioning design is that the major number
817   will only be incremented if an incompatible message syntax is
818   introduced, and that the minor number will only be incremented when
819   changes made to the protocol have the effect of adding to the message
820   semantics or implying additional capabilities of the sender.  However,
821   the minor version was not incremented for the changes introduced between
822   <xref target="RFC2068"/> and <xref target="RFC2616"/>, and this revision
823   is specifically avoiding any such changes to the protocol.
827<section title="Uniform Resource Identifiers" anchor="uri">
828<iref primary="true" item="resource"/>
830   Uniform Resource Identifiers (URIs) <xref target="RFC3986"/> are used
831   throughout HTTP as the means for identifying resources. URI references
832   are used to target requests, indicate redirects, and define relationships.
833   HTTP does not limit what a resource might be; it merely defines an interface
834   that can be used to interact with a resource via HTTP. More information on
835   the scope of URIs and resources can be found in <xref target="RFC3986"/>.
837  <x:anchor-alias value="URI-reference"/>
838  <x:anchor-alias value="absolute-URI"/>
839  <x:anchor-alias value="relative-part"/>
840  <x:anchor-alias value="authority"/>
841  <x:anchor-alias value="path-abempty"/>
842  <x:anchor-alias value="path-absolute"/>
843  <x:anchor-alias value="port"/>
844  <x:anchor-alias value="query"/>
845  <x:anchor-alias value="uri-host"/>
846  <x:anchor-alias value="partial-URI"/>
848   This specification adopts the definitions of "URI-reference",
849   "absolute-URI", "relative-part", "port", "host",
850   "path-abempty", "path-absolute", "query", and "authority" from the
851   URI generic syntax <xref target="RFC3986"/>.
852   In addition, we define a partial-URI rule for protocol elements
853   that allow a relative URI but not a fragment.
855<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"/>
856  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in <xref target="RFC3986" x:fmt="," x:sec="4.1"/>&gt;
857  <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in <xref target="RFC3986" x:fmt="," x:sec="4.3"/>&gt;
858  <x:ref>relative-part</x:ref> = &lt;relative-part, defined in <xref target="RFC3986" x:fmt="," x:sec="4.2"/>&gt;
859  <x:ref>authority</x:ref>     = &lt;authority, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2"/>&gt;
860  <x:ref>path-abempty</x:ref>  = &lt;path-abempty, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
861  <x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
862  <x:ref>port</x:ref>          = &lt;port, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.3"/>&gt;
863  <x:ref>query</x:ref>         = &lt;query, defined in <xref target="RFC3986" x:fmt="," x:sec="3.4"/>&gt;
864  <x:ref>uri-host</x:ref>      = &lt;host, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>&gt;
866  <x:ref>partial-URI</x:ref>   = relative-part [ "?" query ]
869   Each protocol element in HTTP that allows a URI reference will indicate
870   in its ABNF production whether the element allows any form of reference
871   (URI-reference), only a URI in absolute form (absolute-URI), only the
872   path and optional query components, or some combination of the above.
873   Unless otherwise indicated, URI references are parsed relative to the
874   effective request URI, which defines the default base URI for references
875   in both the request and its corresponding response.
878<section title="http URI scheme" anchor="http.uri">
879  <x:anchor-alias value="http-URI"/>
880  <iref item="http URI scheme" primary="true"/>
881  <iref item="URI scheme" subitem="http" primary="true"/>
883   The "http" URI scheme is hereby defined for the purpose of minting
884   identifiers according to their association with the hierarchical
885   namespace governed by a potential HTTP origin server listening for
886   TCP connections on a given port.
888<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http-URI"/>
889  <x:ref>http-URI</x:ref> = "http:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
892   The HTTP origin server is identified by the generic syntax's
893   <x:ref>authority</x:ref> component, which includes a host identifier
894   and optional TCP port (<xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>).
895   The remainder of the URI, consisting of both the hierarchical path
896   component and optional query component, serves as an identifier for
897   a potential resource within that origin server's name space.
900   If the host identifier is provided as an IP literal or IPv4 address,
901   then the origin server is any listener on the indicated TCP port at
902   that IP address. If host is a registered name, then that name is
903   considered an indirect identifier and the recipient might use a name
904   resolution service, such as DNS, to find the address of a listener
905   for that host.
906   The host &MUST-NOT; be empty; if an "http" URI is received with an
907   empty host, then it &MUST; be rejected as invalid.
908   If the port subcomponent is empty or not given, then TCP port 80 is
909   assumed (the default reserved port for WWW services).
912   Regardless of the form of host identifier, access to that host is not
913   implied by the mere presence of its name or address. The host might or might
914   not exist and, even when it does exist, might or might not be running an
915   HTTP server or listening to the indicated port. The "http" URI scheme
916   makes use of the delegated nature of Internet names and addresses to
917   establish a naming authority (whatever entity has the ability to place
918   an HTTP server at that Internet name or address) and allows that
919   authority to determine which names are valid and how they might be used.
922   When an "http" URI is used within a context that calls for access to the
923   indicated resource, a client &MAY; attempt access by resolving
924   the host to an IP address, establishing a TCP connection to that address
925   on the indicated port, and sending an HTTP request message
926   (<xref target="http.message"/>) containing the URI's identifying data
927   (<xref target="message.routing"/>) to the server.
928   If the server responds to that request with a non-interim HTTP response
929   message, as described in &status-code-reasonphr;, then that response
930   is considered an authoritative answer to the client's request.
933   Although HTTP is independent of the transport protocol, the "http"
934   scheme is specific to TCP-based services because the name delegation
935   process depends on TCP for establishing authority.
936   An HTTP service based on some other underlying connection protocol
937   would presumably be identified using a different URI scheme, just as
938   the "https" scheme (below) is used for servers that require an SSL/TLS
939   transport layer on a connection. Other protocols might also be used to
940   provide access to "http" identified resources &mdash; it is only the
941   authoritative interface used for mapping the namespace that is
942   specific to TCP.
945   The URI generic syntax for authority also includes a deprecated
946   userinfo subcomponent (<xref target="RFC3986" x:fmt="," x:sec="3.2.1"/>)
947   for including user authentication information in the URI.  Some
948   implementations make use of the userinfo component for internal
949   configuration of authentication information, such as within command
950   invocation options, configuration files, or bookmark lists, even
951   though such usage might expose a user identifier or password.
952   Senders &MUST-NOT; include a userinfo subcomponent (and its "@"
953   delimiter) when transmitting an "http" URI in a message.  Recipients
954   of HTTP messages that contain a URI reference &SHOULD; parse for the
955   existence of userinfo and treat its presence as an error, likely
956   indicating that the deprecated subcomponent is being used to obscure
957   the authority for the sake of phishing attacks.
961<section title="https URI scheme" anchor="https.uri">
962   <x:anchor-alias value="https-URI"/>
963   <iref item="https URI scheme"/>
964   <iref item="URI scheme" subitem="https"/>
966   The "https" URI scheme is hereby defined for the purpose of minting
967   identifiers according to their association with the hierarchical
968   namespace governed by a potential HTTP origin server listening for
969   SSL/TLS-secured connections on a given TCP port.
972   All of the requirements listed above for the "http" scheme are also
973   requirements for the "https" scheme, except that a default TCP port
974   of 443 is assumed if the port subcomponent is empty or not given,
975   and the TCP connection &MUST; be secured for privacy through the
976   use of strong encryption prior to sending the first HTTP request.
978<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="https-URI"/>
979  <x:ref>https-URI</x:ref> = "https:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
982   Unlike the "http" scheme, responses to "https" identified requests
983   are never "public" and thus &MUST-NOT; be reused for shared caching.
984   They can, however, be reused in a private cache if the message is
985   cacheable by default in HTTP or specifically indicated as such by
986   the Cache-Control header field (&header-cache-control;).
989   Resources made available via the "https" scheme have no shared
990   identity with the "http" scheme even if their resource identifiers
991   indicate the same authority (the same host listening to the same
992   TCP port).  They are distinct name spaces and are considered to be
993   distinct origin servers.  However, an extension to HTTP that is
994   defined to apply to entire host domains, such as the Cookie protocol
995   <xref target="RFC6265"/>, can allow information
996   set by one service to impact communication with other services
997   within a matching group of host domains.
1000   The process for authoritative access to an "https" identified
1001   resource is defined in <xref target="RFC2818"/>.
1005<section title="http and https URI Normalization and Comparison" anchor="uri.comparison">
1007   Since the "http" and "https" schemes conform to the URI generic syntax,
1008   such URIs are normalized and compared according to the algorithm defined
1009   in <xref target="RFC3986" x:fmt="," x:sec="6"/>, using the defaults
1010   described above for each scheme.
1013   If the port is equal to the default port for a scheme, the normal
1014   form is to elide the port subcomponent. Likewise, an empty path
1015   component is equivalent to an absolute path of "/", so the normal
1016   form is to provide a path of "/" instead. The scheme and host
1017   are case-insensitive and normally provided in lowercase; all
1018   other components are compared in a case-sensitive manner.
1019   Characters other than those in the "reserved" set are equivalent
1020   to their percent-encoded octets (see <xref target="RFC3986"
1021   x:fmt="," x:sec="2.1"/>): the normal form is to not encode them.
1024   For example, the following three URIs are equivalent:
1026<figure><artwork type="example">
1035<section title="Message Format" anchor="http.message">
1036<x:anchor-alias value="generic-message"/>
1037<x:anchor-alias value="message.types"/>
1038<x:anchor-alias value="HTTP-message"/>
1039<x:anchor-alias value="start-line"/>
1040<iref item="header section"/>
1041<iref item="headers"/>
1042<iref item="header field"/>
1044   All HTTP/1.1 messages consist of a start-line followed by a sequence of
1045   octets in a format similar to the Internet Message Format
1046   <xref target="RFC5322"/>: zero or more header fields (collectively
1047   referred to as the "headers" or the "header section"), an empty line
1048   indicating the end of the header section, and an optional message-body.
1050<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-message"/>
1051  <x:ref>HTTP-message</x:ref>    = <x:ref>start-line</x:ref>
1052                    *( <x:ref>header-field</x:ref> <x:ref>CRLF</x:ref> )
1053                    <x:ref>CRLF</x:ref>
1054                    [ <x:ref>message-body</x:ref> ]
1057   The normal procedure for parsing an HTTP message is to read the
1058   start-line into a structure, read each header field into a hash
1059   table by field name until the empty line, and then use the parsed
1060   data to determine if a message-body is expected.  If a message-body
1061   has been indicated, then it is read as a stream until an amount
1062   of octets equal to the message-body length is read or the connection
1063   is closed.
1066   Recipients &MUST; parse an HTTP message as a sequence of octets in an
1067   encoding that is a superset of US-ASCII <xref target="USASCII"/>.
1068   Parsing an HTTP message as a stream of Unicode characters, without regard
1069   for the specific encoding, creates security vulnerabilities due to the
1070   varying ways that string processing libraries handle invalid multibyte
1071   character sequences that contain the octet LF (%x0A).  String-based
1072   parsers can only be safely used within protocol elements after the element
1073   has been extracted from the message, such as within a header field-value
1074   after message parsing has delineated the individual fields.
1077   An HTTP message can be parsed as a stream for incremental processing or
1078   forwarding downstream.  However, recipients cannot rely on incremental
1079   delivery of partial messages, since some implementations will buffer or
1080   delay message forwarding for the sake of network efficiency, security
1081   checks, or payload transformations.
1084<section title="Start Line" anchor="start.line">
1085  <x:anchor-alias value="Start-Line"/>
1087   An HTTP message can either be a request from client to server or a
1088   response from server to client.  Syntactically, the two types of message
1089   differ only in the start-line, which is either a Request-Line (for requests)
1090   or a Status-Line (for responses), and in the algorithm for determining
1091   the length of the message-body (<xref target="message.body"/>).
1092   In theory, a client could receive requests and a server could receive
1093   responses, distinguishing them by their different start-line formats,
1094   but in practice servers are implemented to only expect a request
1095   (a response is interpreted as an unknown or invalid request method)
1096   and clients are implemented to only expect a response.
1098<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="start-line"/>
1099  <x:ref>start-line</x:ref>      = <x:ref>Request-Line</x:ref> / <x:ref>Status-Line</x:ref>
1104   Implementations &MUST-NOT; send whitespace between the start-line and
1105   the first header field. The presence of such whitespace in a request
1106   might be an attempt to trick a server into ignoring that field or
1107   processing the line after it as a new request, either of which might
1108   result in a security vulnerability if other implementations within
1109   the request chain interpret the same message differently.
1110   Likewise, the presence of such whitespace in a response might be
1111   ignored by some clients or cause others to cease parsing.
1114<section title="Request-Line" anchor="request.line">
1115  <x:anchor-alias value="Request"/>
1116  <x:anchor-alias value="Request-Line"/>
1118   The Request-Line begins with a method token, followed by a single
1119   space (SP), the request-target, another single space (SP), the
1120   protocol version, and ending with CRLF.
1122<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Request-Line"/>
1123  <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>
1126<section title="Method" anchor="method">
1127  <x:anchor-alias value="Method"/>
1129   The Method token indicates the request method to be performed on the
1130   target resource. The request method is case-sensitive.
1132<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/>
1133  <x:ref>Method</x:ref>         = <x:ref>token</x:ref>
1136   See &method; for further information, such as the list of methods defined
1137   by this specification, the IANA registry, and considerations for new methods.
1141<section title="request-target" anchor="request-target">
1142  <x:anchor-alias value="request-target"/>
1144   The request-target identifies the target resource upon which to apply
1145   the request.  The four options for request-target are described in
1146   <xref target="request-target-types"/>.
1148<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-target"/>
1149  <x:ref>request-target</x:ref> = "*"
1150                 / <x:ref>absolute-URI</x:ref>
1151                 / ( <x:ref>path-absolute</x:ref> [ "?" <x:ref>query</x:ref> ] )
1152                 / <x:ref>authority</x:ref>
1155   HTTP does not place a pre-defined limit on the length of a request-target.
1156   A server &MUST; be prepared to receive URIs of unbounded length and
1157   respond with the 414 (URI Too Long) status code if the received
1158   request-target would be longer than the server wishes to handle
1159   (see &status-414;).
1162   Various ad-hoc limitations on request-target length are found in practice.
1163   It is &RECOMMENDED; that all HTTP senders and recipients support
1164   request-target lengths of 8000 or more octets.
1167  <t>
1168    <x:h>Note:</x:h> Fragments (<xref target="RFC3986" x:fmt="," x:sec="3.5"/>)
1169    are not part of the request-target and thus will not be transmitted
1170    in an HTTP request.
1171  </t>
1176<section title="Response Status-Line" anchor="status.line">
1177  <x:anchor-alias value="Response"/>
1178  <x:anchor-alias value="Status-Line"/>
1180   The first line of a Response message is the Status-Line, consisting
1181   of the protocol version, a space (SP), the status code, another space,
1182   a possibly-empty textual phrase describing the status code, and
1183   ending with CRLF.
1185<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Status-Line"/>
1186  <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>
1189<section title="Status Code" anchor="status.code">
1190  <x:anchor-alias value="Status-Code"/>
1192   The Status-Code element is a 3-digit integer result code of the attempt to
1193   understand and satisfy the request. See &status-code-reasonphr; for
1194   further information, such as the list of status codes defined by this
1195   specification, the IANA registry, and considerations for new status codes.
1197<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Status-Code"/>
1198  <x:ref>Status-Code</x:ref>    = 3<x:ref>DIGIT</x:ref>
1202<section title="Reason Phrase" anchor="reason.phrase">
1203  <x:anchor-alias value="Reason-Phrase"/>
1205   The Reason Phrase exists for the sole purpose of providing a textual
1206   description associated with the numeric status code, out of deference to
1207   earlier Internet application protocols that were more frequently used with
1208   interactive text clients. A client &SHOULD; ignore the content of the Reason
1209   Phrase.
1211<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Reason-Phrase"/>
1212  <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> )
1218<section title="Header Fields" anchor="header.fields">
1219  <x:anchor-alias value="header-field"/>
1220  <x:anchor-alias value="field-content"/>
1221  <x:anchor-alias value="field-name"/>
1222  <x:anchor-alias value="field-value"/>
1223  <x:anchor-alias value="OWS"/>
1225   Each HTTP header field consists of a case-insensitive field name
1226   followed by a colon (":"), optional whitespace, and the field value.
1228<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"/>
1229  <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>
1230  <x:ref>field-name</x:ref>     = <x:ref>token</x:ref>
1231  <x:ref>field-value</x:ref>    = *( <x:ref>field-content</x:ref> / <x:ref>obs-fold</x:ref> )
1232  <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> )
1235   The field-name token labels the corresponding field-value as having the
1236   semantics defined by that header field.  For example, the Date header field
1237   is defined in &header-date; as containing the origination
1238   timestamp for the message in which it appears.
1241   HTTP header fields are fully extensible: there is no limit on the
1242   introduction of new field names, each presumably defining new semantics,
1243   or on the number of header fields used in a given message.  Existing
1244   fields are defined in each part of this specification and in many other
1245   specifications outside the standards process.
1246   New header fields can be introduced without changing the protocol version
1247   if their defined semantics allow them to be safely ignored by recipients
1248   that do not recognize them.
1251   New HTTP header fields &SHOULD; be registered with IANA according
1252   to the procedures in &cons-new-header-fields;.
1253   Unrecognized header fields &MUST; be forwarded by a proxy unless the
1254   field-name is listed in the Connection header field
1255   (<xref target="header.connection"/>) or the proxy is specifically
1256   configured to block or otherwise transform such fields.
1257   Unrecognized header fields &SHOULD; be ignored by other recipients.
1260   The order in which header fields with differing field names are
1261   received is not significant. However, it is "good practice" to send
1262   header fields that contain control data first, such as Host on
1263   requests and Date on responses, so that implementations can decide
1264   when not to handle a message as early as possible.  A server &MUST;
1265   wait until the entire header section is received before interpreting
1266   a request message, since later header fields might include conditionals,
1267   authentication credentials, or deliberately misleading duplicate
1268   header fields that would impact request processing.
1271   Multiple header fields with the same field name &MUST-NOT; be
1272   sent in a message unless the entire field value for that
1273   header field is defined as a comma-separated list [i.e., #(values)].
1274   Multiple header fields with the same field name can be combined into
1275   one "field-name: field-value" pair, without changing the semantics of the
1276   message, by appending each subsequent field value to the combined
1277   field value in order, separated by a comma. The order in which
1278   header fields with the same field name are received is therefore
1279   significant to the interpretation of the combined field value;
1280   a proxy &MUST-NOT; change the order of these field values when
1281   forwarding a message.
1284  <t>
1285   <x:h>Note:</x:h> The "Set-Cookie" header field as implemented in
1286   practice can occur multiple times, but does not use the list syntax, and
1287   thus cannot be combined into a single line (<xref target="RFC6265"/>). (See Appendix A.2.3 of <xref target="Kri2001"/>
1288   for details.) Also note that the Set-Cookie2 header field specified in
1289   <xref target="RFC2965"/> does not share this problem.
1290  </t>
1293<section title="Whitespace" anchor="whitespace">
1294<t anchor="rule.LWS">
1295   This specification uses three rules to denote the use of linear
1296   whitespace: OWS (optional whitespace), RWS (required whitespace), and
1297   BWS ("bad" whitespace).
1299<t anchor="rule.OWS">
1300   The OWS rule is used where zero or more linear whitespace octets might
1301   appear. OWS &SHOULD; either not be produced or be produced as a single
1302   SP. Multiple OWS octets that occur within field-content &SHOULD; either
1303   be replaced with a single SP or transformed to all SP octets (each
1304   octet other than SP replaced with SP) before interpreting the field value
1305   or forwarding the message downstream.
1307<t anchor="rule.RWS">
1308   RWS is used when at least one linear whitespace octet is required to
1309   separate field tokens. RWS &SHOULD; be produced as a single SP.
1310   Multiple RWS octets that occur within field-content &SHOULD; either
1311   be replaced with a single SP or transformed to all SP octets before
1312   interpreting the field value or forwarding the message downstream.
1314<t anchor="rule.BWS">
1315   BWS is used where the grammar allows optional whitespace for historical
1316   reasons but senders &SHOULD-NOT; produce it in messages. HTTP/1.1
1317   recipients &MUST; accept such bad optional whitespace and remove it before
1318   interpreting the field value or forwarding the message downstream.
1320<t anchor="rule.whitespace">
1321  <x:anchor-alias value="BWS"/>
1322  <x:anchor-alias value="OWS"/>
1323  <x:anchor-alias value="RWS"/>
1324  <x:anchor-alias value="obs-fold"/>
1326<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"/>
1327  <x:ref>OWS</x:ref>            = *( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> / obs-fold )
1328                 ; "optional" whitespace
1329  <x:ref>RWS</x:ref>            = 1*( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> / obs-fold )
1330                 ; "required" whitespace
1331  <x:ref>BWS</x:ref>            = <x:ref>OWS</x:ref>
1332                 ; "bad" whitespace
1333  <x:ref>obs-fold</x:ref>       = <x:ref>CRLF</x:ref> ( <x:ref>SP</x:ref> / <x:ref>HTAB</x:ref> )
1334                 ; obsolete line folding
1335                 ; see <xref target="field.parsing"/>
1339<section title="Field Parsing" anchor="field.parsing">
1341   No whitespace is allowed between the header field-name and colon.
1342   In the past, differences in the handling of such whitespace have led to
1343   security vulnerabilities in request routing and response handling.
1344   Any received request message that contains whitespace between a header
1345   field-name and colon &MUST; be rejected with a response code of 400
1346   (Bad Request).  A proxy &MUST; remove any such whitespace from a response
1347   message before forwarding the message downstream.
1350   A field value &MAY; be preceded by optional whitespace (OWS); a single SP is
1351   preferred. The field value does not include any leading or trailing white
1352   space: OWS occurring before the first non-whitespace octet of the
1353   field value or after the last non-whitespace octet of the field value
1354   is ignored and &SHOULD; be removed before further processing (as this does
1355   not change the meaning of the header field).
1358   Historically, HTTP header field values could be extended over multiple
1359   lines by preceding each extra line with at least one space or horizontal
1360   tab (obs-fold). This specification deprecates such line
1361   folding except within the message/http media type
1362   (<xref target=""/>).
1363   HTTP senders &MUST-NOT; produce messages that include line folding
1364   (i.e., that contain any field-content that matches the obs-fold rule) unless
1365   the message is intended for packaging within the message/http media type.
1366   HTTP recipients &SHOULD; accept line folding and replace any embedded
1367   obs-fold whitespace with either a single SP or a matching number of SP
1368   octets (to avoid buffer copying) prior to interpreting the field value or
1369   forwarding the message downstream.
1372   Historically, HTTP has allowed field content with text in the ISO-8859-1
1373   <xref target="ISO-8859-1"/> character encoding and supported other
1374   character sets only through use of <xref target="RFC2047"/> encoding.
1375   In practice, most HTTP header field values use only a subset of the
1376   US-ASCII character encoding <xref target="USASCII"/>. Newly defined
1377   header fields &SHOULD; limit their field values to US-ASCII octets.
1378   Recipients &SHOULD; treat other (obs-text) octets in field content as
1379   opaque data.
1383<section title="Field Length" anchor="field.length">
1385   HTTP does not place a pre-defined limit on the length of header fields,
1386   either in isolation or as a set. A server &MUST; be prepared to receive
1387   request header fields of unbounded length and respond with a 4xx status
1388   code if the received header field(s) would be longer than the server wishes
1389   to handle.
1392   A client that receives response headers that are longer than it wishes to
1393   handle can only treat it as a server error.
1396   Various ad-hoc limitations on header length are found in practice. It is
1397   &RECOMMENDED; that all HTTP senders and recipients support messages whose
1398   combined header fields have 4000 or more octets.
1402<section title="Field value components" anchor="field.components">
1403<t anchor="rule.token.separators">
1404  <x:anchor-alias value="tchar"/>
1405  <x:anchor-alias value="token"/>
1406  <x:anchor-alias value="special"/>
1407  <x:anchor-alias value="word"/>
1408   Many HTTP/1.1 header field values consist of words (token or quoted-string)
1409   separated by whitespace or special characters. These special characters
1410   &MUST; be in a quoted string to be used within a parameter value (as defined
1411   in <xref target="transfer.codings"/>).
1413<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"/>
1414  <x:ref>word</x:ref>           = <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref>
1416  <x:ref>token</x:ref>          = 1*<x:ref>tchar</x:ref>
1418  IMPORTANT: when editing "tchar" make sure that "special" is updated accordingly!!!
1419 -->
1420  <x:ref>tchar</x:ref>          = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*"
1421                 / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
1422                 / <x:ref>DIGIT</x:ref> / <x:ref>ALPHA</x:ref>
1423                 ; any <x:ref>VCHAR</x:ref>, except <x:ref>special</x:ref>
1425  <x:ref>special</x:ref>        = "(" / ")" / "&lt;" / ">" / "@" / ","
1426                 / ";" / ":" / "\" / DQUOTE / "/" / "["
1427                 / "]" / "?" / "=" / "{" / "}"
1429<t anchor="rule.quoted-string">
1430  <x:anchor-alias value="quoted-string"/>
1431  <x:anchor-alias value="qdtext"/>
1432  <x:anchor-alias value="obs-text"/>
1433   A string of text is parsed as a single word if it is quoted using
1434   double-quote marks.
1436<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"/>
1437  <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>
1438  <x:ref>qdtext</x:ref>         = <x:ref>OWS</x:ref> / %x21 / %x23-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1439  <x:ref>obs-text</x:ref>       = %x80-FF
1441<t anchor="rule.quoted-pair">
1442  <x:anchor-alias value="quoted-pair"/>
1443   The backslash octet ("\") can be used as a single-octet
1444   quoting mechanism within quoted-string constructs:
1446<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-pair"/>
1447  <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> )
1450   Recipients that process the value of the quoted-string &MUST; handle a
1451   quoted-pair as if it were replaced by the octet following the backslash.
1454   Senders &SHOULD-NOT; escape octets in quoted-strings that do not require
1455   escaping (i.e., other than DQUOTE and the backslash octet).
1457<t anchor="rule.comment">
1458  <x:anchor-alias value="comment"/>
1459  <x:anchor-alias value="ctext"/>
1460   Comments can be included in some HTTP header fields by surrounding
1461   the comment text with parentheses. Comments are only allowed in
1462   fields containing "comment" as part of their field value definition.
1464<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="comment"/><iref primary="true" item="Grammar" subitem="ctext"/>
1465  <x:ref>comment</x:ref>        = "(" *( <x:ref>ctext</x:ref> / <x:ref>quoted-cpair</x:ref> / <x:ref>comment</x:ref> ) ")"
1466  <x:ref>ctext</x:ref>          = <x:ref>OWS</x:ref> / %x21-27 / %x2A-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1468<t anchor="rule.quoted-cpair">
1469  <x:anchor-alias value="quoted-cpair"/>
1470   The backslash octet ("\") can be used as a single-octet
1471   quoting mechanism within comment constructs:
1473<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-cpair"/>
1474  <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> )
1477   Senders &SHOULD-NOT; escape octets in comments that do not require escaping
1478   (i.e., other than the backslash octet "\" and the parentheses "(" and ")").
1482<section title="ABNF list extension: #rule" anchor="abnf.extension">
1484  A #rule extension to the ABNF rules of <xref target="RFC5234"/> is used to
1485  improve readability in the definitions of some header field values.
1488  A construct "#" is defined, similar to "*", for defining comma-delimited
1489  lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating
1490  at least &lt;n&gt; and at most &lt;m&gt; elements, each separated by a single
1491  comma (",") and optional whitespace (OWS).   
1494  Thus,
1495</preamble><artwork type="example">
1496  1#element =&gt; element *( OWS "," OWS element )
1499  and:
1500</preamble><artwork type="example">
1501  #element =&gt; [ 1#element ]
1504  and for n &gt;= 1 and m &gt; 1:
1505</preamble><artwork type="example">
1506  &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
1509  For compatibility with legacy list rules, recipients &SHOULD; accept empty
1510  list elements. In other words, consumers would follow the list productions:
1512<figure><artwork type="example">
1513  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
1515  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
1518  Note that empty elements do not contribute to the count of elements present,
1519  though.
1522  For example, given these ABNF productions:
1524<figure><artwork type="example">
1525  example-list      = 1#example-list-elmt
1526  example-list-elmt = token ; see <xref target="field.components"/>
1529  Then these are valid values for example-list (not including the double
1530  quotes, which are present for delimitation only):
1532<figure><artwork type="example">
1533  "foo,bar"
1534  "foo ,bar,"
1535  "foo , ,bar,charlie   "
1538  But these values would be invalid, as at least one non-empty element is
1539  required:
1541<figure><artwork type="example">
1542  ""
1543  ","
1544  ",   ,"
1547  <xref target="collected.abnf"/> shows the collected ABNF, with the list rules
1548  expanded as explained above.
1553<section title="Message Body" anchor="message.body">
1554  <x:anchor-alias value="message-body"/>
1556   The message-body (if any) of an HTTP message is used to carry the
1557   payload body associated with the request or response.
1559<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-body"/>
1560  <x:ref>message-body</x:ref> = *OCTET
1563   The message-body differs from the payload body only when a transfer-coding
1564   has been applied, as indicated by the Transfer-Encoding header field
1565   (<xref target="header.transfer-encoding"/>).  If more than one
1566   Transfer-Encoding header field is present in a message, the multiple
1567   field-values &MUST; be combined into one field-value, according to the
1568   algorithm defined in <xref target="header.fields"/>, before determining
1569   the message-body length.
1572   When one or more transfer-codings are applied to a payload in order to
1573   form the message-body, the Transfer-Encoding header field &MUST; contain
1574   the list of transfer-codings applied. Transfer-Encoding is a property of
1575   the message, not of the payload, and thus &MAY; be added or removed by
1576   any implementation along the request/response chain under the constraints
1577   found in <xref target="transfer.codings"/>.
1580   If a message is received that has multiple Content-Length header fields
1581   (<xref target="header.content-length"/>) with field-values consisting
1582   of the same decimal value, or a single Content-Length header field with
1583   a field value containing a list of identical decimal values (e.g.,
1584   "Content-Length: 42, 42"), indicating that duplicate Content-Length
1585   header fields have been generated or combined by an upstream message
1586   processor, then the recipient &MUST; either reject the message as invalid
1587   or replace the duplicated field-values with a single valid Content-Length
1588   field containing that decimal value prior to determining the message-body
1589   length.
1592   The rules for when a message-body is allowed in a message differ for
1593   requests and responses.
1596   The presence of a message-body in a request is signaled by the
1597   inclusion of a Content-Length or Transfer-Encoding header field in
1598   the request's header fields, even if the request method does not
1599   define any use for a message-body.  This allows the request
1600   message framing algorithm to be independent of method semantics.
1603   For response messages, whether or not a message-body is included with
1604   a message is dependent on both the request method and the response
1605   status code (<xref target="status.code"/>).
1606   Responses to the HEAD request method never include a message-body
1607   because the associated response header fields (e.g., Transfer-Encoding,
1608   Content-Length, etc.) only indicate what their values would have been
1609   if the request method had been GET.  All 1xx (Informational), 204 (No Content),
1610   and 304 (Not Modified) responses &MUST-NOT; include a message-body.
1611   All other responses do include a message-body, although the body
1612   &MAY; be of zero length.
1615   The length of the message-body is determined by one of the following
1616   (in order of precedence):
1619  <list style="numbers">
1620    <x:lt><t>
1621     Any response to a HEAD request and any response with a status
1622     code of 100-199, 204, or 304 is always terminated by the first
1623     empty line after the header fields, regardless of the header
1624     fields present in the message, and thus cannot contain a message-body.
1625    </t></x:lt>
1626    <x:lt><t>
1627     If a Transfer-Encoding header field is present
1628     and the "chunked" transfer-coding (<xref target="transfer.codings"/>)
1629     is the final encoding, the message-body length is determined by reading
1630     and decoding the chunked data until the transfer-coding indicates the
1631     data is complete.
1632    </t>
1633    <t>
1634     If a Transfer-Encoding header field is present in a response and the
1635     "chunked" transfer-coding is not the final encoding, the message-body
1636     length is determined by reading the connection until it is closed by
1637     the server.
1638     If a Transfer-Encoding header field is present in a request and the
1639     "chunked" transfer-coding is not the final encoding, the message-body
1640     length cannot be determined reliably; the server &MUST; respond with
1641     the 400 (Bad Request) status code and then close the connection.
1642    </t>
1643    <t>
1644     If a message is received with both a Transfer-Encoding header field
1645     and a Content-Length header field, the Transfer-Encoding overrides
1646     the Content-Length.
1647     Such a message might indicate an attempt to perform request or response
1648     smuggling (bypass of security-related checks on message routing or content)
1649     and thus ought to be handled as an error.  The provided Content-Length &MUST;
1650     be removed, prior to forwarding the message downstream, or replaced with
1651     the real message-body length after the transfer-coding is decoded.
1652    </t></x:lt>
1653    <x:lt><t>
1654     If a message is received without Transfer-Encoding and with either
1655     multiple Content-Length header fields having differing field-values or
1656     a single Content-Length header field having an invalid value, then the
1657     message framing is invalid and &MUST; be treated as an error to
1658     prevent request or response smuggling.
1659     If this is a request message, the server &MUST; respond with
1660     a 400 (Bad Request) status code and then close the connection.
1661     If this is a response message received by a proxy, the proxy
1662     &MUST; discard the received response, send a 502 (Bad Gateway)
1663     status code as its downstream response, and then close the connection.
1664     If this is a response message received by a user-agent, it &MUST; be
1665     treated as an error by discarding the message and closing the connection.
1666    </t></x:lt>
1667    <x:lt><t>
1668     If a valid Content-Length header field
1669     is present without Transfer-Encoding, its decimal value defines the
1670     message-body length in octets.  If the actual number of octets sent in
1671     the message is less than the indicated Content-Length, the recipient
1672     &MUST; consider the message to be incomplete and treat the connection
1673     as no longer usable.
1674     If the actual number of octets sent in the message is more than the indicated
1675     Content-Length, the recipient &MUST; only process the message-body up to the
1676     field value's number of octets; the remainder of the message &MUST; either
1677     be discarded or treated as the next message in a pipeline.  For the sake of
1678     robustness, a user-agent &MAY; attempt to detect and correct such an error
1679     in message framing if it is parsing the response to the last request on
1680     a connection and the connection has been closed by the server.
1681    </t></x:lt>
1682    <x:lt><t>
1683     If this is a request message and none of the above are true, then the
1684     message-body length is zero (no message-body is present).
1685    </t></x:lt>
1686    <x:lt><t>
1687     Otherwise, this is a response message without a declared message-body
1688     length, so the message-body length is determined by the number of octets
1689     received prior to the server closing the connection.
1690    </t></x:lt>
1691  </list>
1694   Since there is no way to distinguish a successfully completed,
1695   close-delimited message from a partially-received message interrupted
1696   by network failure, implementations &SHOULD; use encoding or
1697   length-delimited messages whenever possible.  The close-delimiting
1698   feature exists primarily for backwards compatibility with HTTP/1.0.
1701   A server &MAY; reject a request that contains a message-body but
1702   not a Content-Length by responding with 411 (Length Required).
1705   Unless a transfer-coding other than "chunked" has been applied,
1706   a client that sends a request containing a message-body &SHOULD;
1707   use a valid Content-Length header field if the message-body length
1708   is known in advance, rather than the "chunked" encoding, since some
1709   existing services respond to "chunked" with a 411 (Length Required)
1710   status code even though they understand the chunked encoding.  This
1711   is typically because such services are implemented via a gateway that
1712   requires a content-length in advance of being called and the server
1713   is unable or unwilling to buffer the entire request before processing.
1716   A client that sends a request containing a message-body &MUST; include a
1717   valid Content-Length header field if it does not know the server will
1718   handle HTTP/1.1 (or later) requests; such knowledge can be in the form
1719   of specific user configuration or by remembering the version of a prior
1720   received response.
1724<section anchor="incomplete.messages" title="Handling Incomplete Messages">
1726   Request messages that are prematurely terminated, possibly due to a
1727   cancelled connection or a server-imposed time-out exception, &MUST;
1728   result in closure of the connection; sending an HTTP/1.1 error response
1729   prior to closing the connection is &OPTIONAL;.
1732   Response messages that are prematurely terminated, usually by closure
1733   of the connection prior to receiving the expected number of octets or by
1734   failure to decode a transfer-encoded message-body, &MUST; be recorded
1735   as incomplete.  A response that terminates in the middle of the header
1736   block (before the empty line is received) cannot be assumed to convey the
1737   full semantics of the response and &MUST; be treated as an error.
1740   A message-body that uses the chunked transfer encoding is
1741   incomplete if the zero-sized chunk that terminates the encoding has not
1742   been received.  A message that uses a valid Content-Length is incomplete
1743   if the size of the message-body received (in octets) is less than the
1744   value given by Content-Length.  A response that has neither chunked
1745   transfer encoding nor Content-Length is terminated by closure of the
1746   connection, and thus is considered complete regardless of the number of
1747   message-body octets received, provided that the header block was received
1748   intact.
1751   A user agent &MUST-NOT; render an incomplete response message-body as if
1752   it were complete (i.e., some indication must be given to the user that an
1753   error occurred).  Cache requirements for incomplete responses are defined
1754   in &cache-incomplete;.
1757   A server &MUST; read the entire request message-body or close
1758   the connection after sending its response, since otherwise the
1759   remaining data on a persistent connection would be misinterpreted
1760   as the next request.  Likewise,
1761   a client &MUST; read the entire response message-body if it intends
1762   to reuse the same connection for a subsequent request.  Pipelining
1763   multiple requests on a connection is described in <xref target="pipelining"/>.
1767<section title="Message Parsing Robustness" anchor="message.robustness">
1769   Older HTTP/1.0 client implementations might send an extra CRLF
1770   after a POST request as a lame workaround for some early server
1771   applications that failed to read message-body content that was
1772   not terminated by a line-ending. An HTTP/1.1 client &MUST-NOT;
1773   preface or follow a request with an extra CRLF.  If terminating
1774   the request message-body with a line-ending is desired, then the
1775   client &MUST; include the terminating CRLF octets as part of the
1776   message-body length.
1779   In the interest of robustness, servers &SHOULD; ignore at least one
1780   empty line received where a Request-Line is expected. In other words, if
1781   the server is reading the protocol stream at the beginning of a
1782   message and receives a CRLF first, it &SHOULD; ignore the CRLF.
1783   Likewise, although the line terminator for the start-line and header
1784   fields is the sequence CRLF, we recommend that recipients recognize a
1785   single LF as a line terminator and ignore any CR.
1788   When a server listening only for HTTP request messages, or processing
1789   what appears from the start-line to be an HTTP request message,
1790   receives a sequence of octets that does not match the HTTP-message
1791   grammar aside from the robustness exceptions listed above, the
1792   server &MUST; respond with an HTTP/1.1 400 (Bad Request) response. 
1797<section title="Message Routing" anchor="message.routing">
1799   In most cases, the user agent is provided a URI reference
1800   from which it determines an absolute URI for identifying the target
1801   resource.  When a request to the resource is initiated, all or part
1802   of that URI is used to construct the HTTP request-target.
1805<section title="Types of Request Target" anchor="request-target-types">
1807   The proper format choice of the four options available to request-target
1808   depends on the method being requested and if the request is being made to
1809   a proxy.
1811<t anchor="origin-form"><iref item="origin form (of request-target)"/>
1812   The most common form of request-target is that used when making
1813   a request to an origin server ("origin form") to access a resource
1814   identified by an "http" (<xref target="http.uri"/>) or
1815   "https" (<xref target="https.uri"/>) URI.
1816   In this case, the absolute path and query components of the URI
1817   &MUST; be transmitted as the request-target and the authority component
1818   (excluding any userinfo) &MUST; be transmitted in a Host header field.
1819   For example, a client wishing to retrieve a representation of the resource
1820   identified as
1822<figure><artwork x:indent-with="  ">
1826   directly from the origin server would open (or reuse) a TCP connection
1827   to port 80 of the host "" and send the lines:
1829<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
1830GET /where?q=now HTTP/1.1
1834   followed by the remainder of the request. Note that the origin form
1835   of request-target always starts with an absolute path. If the target
1836   resource's URI path is empty, then an absolute path of "/" &MUST; be
1837   provided in the request-target.
1840   If the request-target is percent-encoded
1841   (<xref target="RFC3986" x:fmt="," x:sec="2.1"/>), the origin server
1842   &MUST; decode the request-target in order to
1843   properly interpret the request. Servers &SHOULD; respond to invalid
1844   request-targets with an appropriate status code.
1846<t anchor="absolute-URI-form"><iref item="absolute-URI form (of request-target)"/>
1847   The "absolute-URI" form of request-target is &REQUIRED; when the request
1848   is being made to a proxy.  The proxy is requested to either forward the
1849   request or service it from a valid cache, and then return the response.
1850   Note that the proxy &MAY; forward the request on to another proxy or
1851   directly to the server specified by the absolute-URI.
1852   In order to avoid request loops, a proxy that forwards requests to other
1853   proxies &MUST; be able to recognize and exclude all of its own server
1854   names, including any aliases, local variations, or literal IP addresses.
1855   An example Request-Line would be:
1857<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
1858GET HTTP/1.1
1861   To allow for transition to absolute-URIs in all requests in future
1862   versions of HTTP, all HTTP/1.1 servers &MUST; accept the absolute-URI
1863   form in requests, even though HTTP/1.1 clients will only generate
1864   them in requests to proxies.
1867   If a proxy receives a host name that is not a fully qualified domain
1868   name, it &MAY; add its domain to the host name it received. If a proxy
1869   receives a fully qualified domain name, the proxy &MUST-NOT; change
1870   the host name.
1872<t anchor="authority-form"><iref item="authority form (of request-target)"/>
1873   The "authority form" of request-target, which &MUST-NOT; be used
1874   with any request method other than CONNECT, is used to establish a
1875   tunnel through one or more proxies (&CONNECT;).  For example,
1877<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
1880<t anchor="asterix-form"><iref item="asterisk form (of request-target)"/>
1881   The asterisk ("*") form of request-target, which &MUST-NOT; be used
1882   with any request method other than OPTIONS, means that the request
1883   applies to the server as a whole (the listening process) rather than
1884   to a specific named resource at that server.  For example,
1886<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
1887OPTIONS * HTTP/1.1
1890   If a proxy receives an OPTIONS request with an absolute-URI form of
1891   request-target in which the URI has an empty path and no query component,
1892   then the last proxy on the request chain &MUST; use a request-target
1893   of "*" when it forwards the request to the indicated origin server.
1896   For example, the request
1897</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
1901  would be forwarded by the final proxy as
1902</preamble><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
1903OPTIONS * HTTP/1.1
1907   after connecting to port 8001 of host "".
1911   A non-transforming proxy &MUST-NOT; rewrite the "path-absolute" and "query"
1912   parts of the received request-target when forwarding it to the next inbound
1913   server, except as noted above to replace a null path-absolute with "/" or
1914   "*".
1918<section title="The Resource Identified by a Request" anchor="">
1920   The exact resource identified by an Internet request is determined by
1921   examining both the request-target and the Host header field.
1924   An origin server that does not allow resources to differ by the
1925   requested host &MAY; ignore the Host header field value when
1926   determining the resource identified by an HTTP/1.1 request. (But see
1927   <xref target=""/>
1928   for other requirements on Host support in HTTP/1.1.)
1931   An origin server that does differentiate resources based on the host
1932   requested (sometimes referred to as virtual hosts or vanity host
1933   names) &MUST; use the following rules for determining the requested
1934   resource on an HTTP/1.1 request:
1935  <list style="numbers">
1936    <t>If request-target is an absolute-URI, the host is part of the
1937     request-target. Any Host header field value in the request &MUST; be
1938     ignored.</t>
1939    <t>If the request-target is not an absolute-URI, and the request includes
1940     a Host header field, the host is determined by the Host header
1941     field value.</t>
1942    <t>If the host as determined by rule 1 or 2 is not a valid host on
1943     the server, the response &MUST; be a 400 (Bad Request) error message.</t>
1944  </list>
1947   Recipients of an HTTP/1.0 request that lacks a Host header field &MAY;
1948   attempt to use heuristics (e.g., examination of the URI path for
1949   something unique to a particular host) in order to determine what
1950   exact resource is being requested.
1954<section title="Effective Request URI" anchor="effective.request.uri">
1955  <iref primary="true" item="effective request URI"/>
1956  <iref primary="true" item="target resource"/>
1958   HTTP requests often do not carry the absolute URI (<xref target="RFC3986" x:fmt="," x:sec="4.3"/>)
1959   for the target resource; instead, the URI needs to be inferred from the
1960   request-target, Host header field, and connection context. The result of
1961   this process is called the "effective request URI".  The "target resource"
1962   is the resource identified by the effective request URI.
1965   If the request-target is an absolute-URI, then the effective request URI is
1966   the request-target.
1969   If the request-target uses the origin form or the asterisk form,
1970   and the Host header field is present, then the effective request URI is
1971   constructed by concatenating
1974  <list style="symbols">
1975    <t>
1976      the scheme name: "http" if the request was received over an insecure
1977      TCP connection, or "https" when received over a SSL/TLS-secured TCP
1978      connection,
1979    </t>
1980    <t>
1981      the octet sequence "://",
1982    </t>
1983    <t>
1984      the authority component, as specified in the Host header field
1985      (<xref target=""/>), and
1986    </t>
1987    <t>
1988      the request-target obtained from the Request-Line, unless the
1989      request-target is just the asterisk "*".
1990    </t>
1991  </list>
1994   If the request-target uses the origin form or the asterisk form,
1995   and the Host header field is not present, then the effective request URI is
1996   undefined.
1999   Otherwise, when request-target uses the authority form, the effective
2000   request URI is undefined.
2004   Example 1: the effective request URI for the message
2006<artwork type="example" x:indent-with="  ">
2007GET /pub/WWW/TheProject.html HTTP/1.1
2011  (received over an insecure TCP connection) is "http", plus "://", plus the
2012  authority component "", plus the request-target
2013  "/pub/WWW/TheProject.html", thus
2014  "".
2019   Example 2: the effective request URI for the message
2021<artwork type="example" x:indent-with="  ">
2022OPTIONS * HTTP/1.1
2026  (received over an SSL/TLS secured TCP connection) is "https", plus "://", plus the
2027  authority component "", thus "".
2031   Effective request URIs are compared using the rules described in
2032   <xref target="uri.comparison"/>, except that empty path components &MUST-NOT;
2033   be treated as equivalent to an absolute path of "/".
2039<section title="Protocol Parameters" anchor="protocol.parameters">
2041<section title="Transfer Codings" anchor="transfer.codings">
2042  <x:anchor-alias value="transfer-coding"/>
2043  <x:anchor-alias value="transfer-extension"/>
2045   Transfer-coding values are used to indicate an encoding
2046   transformation that has been, can be, or might need to be applied to a
2047   payload body in order to ensure "safe transport" through the network.
2048   This differs from a content coding in that the transfer-coding is a
2049   property of the message rather than a property of the representation
2050   that is being transferred.
2052<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-coding"/><iref primary="true" item="Grammar" subitem="transfer-extension"/>
2053  <x:ref>transfer-coding</x:ref>         = "chunked" ; <xref target="chunked.encoding"/>
2054                          / "compress" ; <xref target="compress.coding"/>
2055                          / "deflate" ; <xref target="deflate.coding"/>
2056                          / "gzip" ; <xref target="gzip.coding"/>
2057                          / <x:ref>transfer-extension</x:ref>
2058  <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> )
2060<t anchor="rule.parameter">
2061  <x:anchor-alias value="attribute"/>
2062  <x:anchor-alias value="transfer-parameter"/>
2063  <x:anchor-alias value="value"/>
2064   Parameters are in the form of attribute/value pairs.
2066<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"/>
2067  <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>
2068  <x:ref>attribute</x:ref>               = <x:ref>token</x:ref>
2069  <x:ref>value</x:ref>                   = <x:ref>word</x:ref>
2072   All transfer-coding values are case-insensitive. HTTP/1.1 uses
2073   transfer-coding values in the TE header field (<xref target="header.te"/>) and in
2074   the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).
2077   Transfer-codings are analogous to the Content-Transfer-Encoding values of
2078   MIME, which were designed to enable safe transport of binary data over a
2079   7-bit transport service (<xref target="RFC2045" x:fmt="," x:sec="6"/>).
2080   However, safe transport
2081   has a different focus for an 8bit-clean transfer protocol. In HTTP,
2082   the only unsafe characteristic of message-bodies is the difficulty in
2083   determining the exact message body length (<xref target="message.body"/>),
2084   or the desire to encrypt data over a shared transport.
2087   A server that receives a request message with a transfer-coding it does
2088   not understand &SHOULD; respond with 501 (Not Implemented) and then
2089   close the connection. A server &MUST-NOT; send transfer-codings to an HTTP/1.0
2090   client.
2093<section title="Chunked Transfer Coding" anchor="chunked.encoding">
2094  <iref item="chunked (Coding Format)"/>
2095  <iref item="Coding Format" subitem="chunked"/>
2096  <x:anchor-alias value="chunk"/>
2097  <x:anchor-alias value="Chunked-Body"/>
2098  <x:anchor-alias value="chunk-data"/>
2099  <x:anchor-alias value="chunk-ext"/>
2100  <x:anchor-alias value="chunk-ext-name"/>
2101  <x:anchor-alias value="chunk-ext-val"/>
2102  <x:anchor-alias value="chunk-size"/>
2103  <x:anchor-alias value="last-chunk"/>
2104  <x:anchor-alias value="trailer-part"/>
2105  <x:anchor-alias value="quoted-str-nf"/>
2106  <x:anchor-alias value="qdtext-nf"/>
2108   The chunked encoding modifies the body of a message in order to
2109   transfer it as a series of chunks, each with its own size indicator,
2110   followed by an &OPTIONAL; trailer containing header fields. This
2111   allows dynamically produced content to be transferred along with the
2112   information necessary for the recipient to verify that it has
2113   received the full message.
2115<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"/>
2116  <x:ref>Chunked-Body</x:ref>   = *<x:ref>chunk</x:ref>
2117                   <x:ref>last-chunk</x:ref>
2118                   <x:ref>trailer-part</x:ref>
2119                   <x:ref>CRLF</x:ref>
2121  <x:ref>chunk</x:ref>          = <x:ref>chunk-size</x:ref> [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
2122                   <x:ref>chunk-data</x:ref> <x:ref>CRLF</x:ref>
2123  <x:ref>chunk-size</x:ref>     = 1*<x:ref>HEXDIG</x:ref>
2124  <x:ref>last-chunk</x:ref>     = 1*("0") [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
2126  <x:ref>chunk-ext</x:ref>      = *( ";" <x:ref>chunk-ext-name</x:ref>
2127                      [ "=" <x:ref>chunk-ext-val</x:ref> ] )
2128  <x:ref>chunk-ext-name</x:ref> = <x:ref>token</x:ref>
2129  <x:ref>chunk-ext-val</x:ref>  = <x:ref>token</x:ref> / <x:ref>quoted-str-nf</x:ref>
2130  <x:ref>chunk-data</x:ref>     = 1*<x:ref>OCTET</x:ref> ; a sequence of chunk-size octets
2131  <x:ref>trailer-part</x:ref>   = *( <x:ref>header-field</x:ref> <x:ref>CRLF</x:ref> )
2133  <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>
2134                 ; like <x:ref>quoted-string</x:ref>, but disallowing line folding
2135  <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>
2138   The chunk-size field is a string of hex digits indicating the size of
2139   the chunk-data in octets. The chunked encoding is ended by any chunk whose size is
2140   zero, followed by the trailer, which is terminated by an empty line.
2143   The trailer allows the sender to include additional HTTP header
2144   fields at the end of the message. The Trailer header field can be
2145   used to indicate which header fields are included in a trailer (see
2146   <xref target="header.trailer"/>).
2149   A server using chunked transfer-coding in a response &MUST-NOT; use the
2150   trailer for any header fields unless at least one of the following is
2151   true:
2152  <list style="numbers">
2153    <t>the request included a TE header field that indicates "trailers" is
2154     acceptable in the transfer-coding of the  response, as described in
2155     <xref target="header.te"/>; or,</t>
2157    <t>the trailer fields consist entirely of optional metadata, and the
2158    recipient could use the message (in a manner acceptable to the server where
2159    the field originated) without receiving it. In other words, the server that
2160    generated the header (often but not always the origin server) is willing to
2161    accept the possibility that the trailer fields might be silently discarded
2162    along the path to the client.</t>
2163  </list>
2166   This requirement prevents an interoperability failure when the
2167   message is being received by an HTTP/1.1 (or later) proxy and
2168   forwarded to an HTTP/1.0 recipient. It avoids a situation where
2169   conformance with the protocol would have necessitated a possibly
2170   infinite buffer on the proxy.
2173   A process for decoding the "chunked" transfer-coding
2174   can be represented in pseudo-code as:
2176<figure><artwork type="code">
2177  length := 0
2178  read chunk-size, chunk-ext (if any) and CRLF
2179  while (chunk-size &gt; 0) {
2180     read chunk-data and CRLF
2181     append chunk-data to decoded-body
2182     length := length + chunk-size
2183     read chunk-size and CRLF
2184  }
2185  read header-field
2186  while (header-field not empty) {
2187     append header-field to existing header fields
2188     read header-field
2189  }
2190  Content-Length := length
2191  Remove "chunked" from Transfer-Encoding
2194   All HTTP/1.1 applications &MUST; be able to receive and decode the
2195   "chunked" transfer-coding and &MUST; ignore chunk-ext extensions
2196   they do not understand.
2199   Since "chunked" is the only transfer-coding required to be understood
2200   by HTTP/1.1 recipients, it plays a crucial role in delimiting messages
2201   on a persistent connection.  Whenever a transfer-coding is applied to
2202   a payload body in a request, the final transfer-coding applied &MUST;
2203   be "chunked".  If a transfer-coding is applied to a response payload
2204   body, then either the final transfer-coding applied &MUST; be "chunked"
2205   or the message &MUST; be terminated by closing the connection. When the
2206   "chunked" transfer-coding is used, it &MUST; be the last transfer-coding
2207   applied to form the message-body. The "chunked" transfer-coding &MUST-NOT;
2208   be applied more than once in a message-body.
2212<section title="Compression Codings" anchor="compression.codings">
2214   The codings defined below can be used to compress the payload of a
2215   message.
2218   <x:h>Note:</x:h> Use of program names for the identification of encoding formats
2219   is not desirable and is discouraged for future encodings. Their
2220   use here is representative of historical practice, not good
2221   design.
2224   <x:h>Note:</x:h> For compatibility with previous implementations of HTTP,
2225   applications &SHOULD; consider "x-gzip" and "x-compress" to be
2226   equivalent to "gzip" and "compress" respectively.
2229<section title="Compress Coding" anchor="compress.coding">
2230<iref item="compress (Coding Format)"/>
2231<iref item="Coding Format" subitem="compress"/>
2233   The "compress" format is produced by the common UNIX file compression
2234   program "compress". This format is an adaptive Lempel-Ziv-Welch
2235   coding (LZW).
2239<section title="Deflate Coding" anchor="deflate.coding">
2240<iref item="deflate (Coding Format)"/>
2241<iref item="Coding Format" subitem="deflate"/>
2243   The "deflate" format is defined as the "deflate" compression mechanism
2244   (described in <xref target="RFC1951"/>) used inside the "zlib"
2245   data format (<xref target="RFC1950"/>).
2248  <t>
2249    <x:h>Note:</x:h> Some incorrect implementations send the "deflate"
2250    compressed data without the zlib wrapper.
2251   </t>
2255<section title="Gzip Coding" anchor="gzip.coding">
2256<iref item="gzip (Coding Format)"/>
2257<iref item="Coding Format" subitem="gzip"/>
2259   The "gzip" format is produced by the file compression program
2260   "gzip" (GNU zip), as described in <xref target="RFC1952"/>. This format is a
2261   Lempel-Ziv coding (LZ77) with a 32 bit CRC.
2267<section title="Transfer Coding Registry" anchor="transfer.coding.registry">
2269   The HTTP Transfer Coding Registry defines the name space for the transfer
2270   coding names.
2273   Registrations &MUST; include the following fields:
2274   <list style="symbols">
2275     <t>Name</t>
2276     <t>Description</t>
2277     <t>Pointer to specification text</t>
2278   </list>
2281   Names of transfer codings &MUST-NOT; overlap with names of content codings
2282   (&content-codings;), unless the encoding transformation is identical (as it
2283   is the case for the compression codings defined in
2284   <xref target="compression.codings"/>).
2287   Values to be added to this name space require a specification
2288   (see "Specification Required" in <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
2289   conform to the purpose of transfer coding defined in this section.
2292   The registry itself is maintained at
2293   <eref target=""/>.
2298<section title="Product Tokens" anchor="product.tokens">
2299  <x:anchor-alias value="product"/>
2300  <x:anchor-alias value="product-version"/>
2302   Product tokens are used to allow communicating applications to
2303   identify themselves by software name and version. Most fields using
2304   product tokens also allow sub-products which form a significant part
2305   of the application to be listed, separated by whitespace. By
2306   convention, the products are listed in order of their significance
2307   for identifying the application.
2309<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="product"/><iref primary="true" item="Grammar" subitem="product-version"/>
2310  <x:ref>product</x:ref>         = <x:ref>token</x:ref> ["/" <x:ref>product-version</x:ref>]
2311  <x:ref>product-version</x:ref> = <x:ref>token</x:ref>
2314   Examples:
2316<figure><artwork type="example">
2317  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
2318  Server: Apache/0.8.4
2321   Product tokens &SHOULD; be short and to the point. They &MUST-NOT; be
2322   used for advertising or other non-essential information. Although any
2323   token octet &MAY; appear in a product-version, this token &SHOULD;
2324   only be used for a version identifier (i.e., successive versions of
2325   the same product &SHOULD; only differ in the product-version portion of
2326   the product value).
2330<section title="Quality Values" anchor="quality.values">
2331  <x:anchor-alias value="qvalue"/>
2333   Both transfer codings (TE request header field, <xref target="header.te"/>)
2334   and content negotiation (&content.negotiation;) use short "floating point"
2335   numbers to indicate the relative importance ("weight") of various
2336   negotiable parameters.  A weight is normalized to a real number in
2337   the range 0 through 1, where 0 is the minimum and 1 the maximum
2338   value. If a parameter has a quality value of 0, then content with
2339   this parameter is "not acceptable" for the client. HTTP/1.1
2340   applications &MUST-NOT; generate more than three digits after the
2341   decimal point. User configuration of these values &SHOULD; also be
2342   limited in this fashion.
2344<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="qvalue"/>
2345  <x:ref>qvalue</x:ref>         = ( "0" [ "." 0*3<x:ref>DIGIT</x:ref> ] )
2346                 / ( "1" [ "." 0*3("0") ] )
2349  <t>
2350     <x:h>Note:</x:h> "Quality values" is a misnomer, since these values merely represent
2351     relative degradation in desired quality.
2352  </t>
2358<section title="Connections" anchor="connections">
2360<section title="Persistent Connections" anchor="persistent.connections">
2362<section title="Purpose" anchor="persistent.purpose">
2364   Prior to persistent connections, a separate TCP connection was
2365   established for each request, increasing the load on HTTP servers
2366   and causing congestion on the Internet. The use of inline images and
2367   other associated data often requires a client to make multiple
2368   requests of the same server in a short amount of time. Analysis of
2369   these performance problems and results from a prototype
2370   implementation are available <xref target="Pad1995"/> <xref target="Spe"/>. Implementation experience and
2371   measurements of actual HTTP/1.1 implementations show good
2372   results <xref target="Nie1997"/>. Alternatives have also been explored, for example,
2373   T/TCP <xref target="Tou1998"/>.
2376   Persistent HTTP connections have a number of advantages:
2377  <list style="symbols">
2378      <t>
2379        By opening and closing fewer TCP connections, CPU time is saved
2380        in routers and hosts (clients, servers, proxies, gateways,
2381        tunnels, or caches), and memory used for TCP protocol control
2382        blocks can be saved in hosts.
2383      </t>
2384      <t>
2385        HTTP requests and responses can be pipelined on a connection.
2386        Pipelining allows a client to make multiple requests without
2387        waiting for each response, allowing a single TCP connection to
2388        be used much more efficiently, with much lower elapsed time.
2389      </t>
2390      <t>
2391        Network congestion is reduced by reducing the number of packets
2392        caused by TCP opens, and by allowing TCP sufficient time to
2393        determine the congestion state of the network.
2394      </t>
2395      <t>
2396        Latency on subsequent requests is reduced since there is no time
2397        spent in TCP's connection opening handshake.
2398      </t>
2399      <t>
2400        HTTP can evolve more gracefully, since errors can be reported
2401        without the penalty of closing the TCP connection. Clients using
2402        future versions of HTTP might optimistically try a new feature,
2403        but if communicating with an older server, retry with old
2404        semantics after an error is reported.
2405      </t>
2406    </list>
2409   HTTP implementations &SHOULD; implement persistent connections.
2413<section title="Overall Operation" anchor="persistent.overall">
2415   A significant difference between HTTP/1.1 and earlier versions of
2416   HTTP is that persistent connections are the default behavior of any
2417   HTTP connection. That is, unless otherwise indicated, the client
2418   &SHOULD; assume that the server will maintain a persistent connection,
2419   even after error responses from the server.
2422   Persistent connections provide a mechanism by which a client and a
2423   server can signal the close of a TCP connection. This signaling takes
2424   place using the Connection header field (<xref target="header.connection"/>). Once a close
2425   has been signaled, the client &MUST-NOT; send any more requests on that
2426   connection.
2429<section title="Negotiation" anchor="persistent.negotiation">
2431   An HTTP/1.1 server &MAY; assume that a HTTP/1.1 client intends to
2432   maintain a persistent connection unless a Connection header field including
2433   the connection-token "close" was sent in the request. If the server
2434   chooses to close the connection immediately after sending the
2435   response, it &SHOULD; send a Connection header field including the
2436   connection-token "close".
2439   An HTTP/1.1 client &MAY; expect a connection to remain open, but would
2440   decide to keep it open based on whether the response from a server
2441   contains a Connection header field with the connection-token close. In case
2442   the client does not want to maintain a connection for more than that
2443   request, it &SHOULD; send a Connection header field including the
2444   connection-token close.
2447   If either the client or the server sends the close token in the
2448   Connection header field, that request becomes the last one for the
2449   connection.
2452   Clients and servers &SHOULD-NOT;  assume that a persistent connection is
2453   maintained for HTTP versions less than 1.1 unless it is explicitly
2454   signaled. See <xref target="compatibility.with.http.1.0.persistent.connections"/> for more information on backward
2455   compatibility with HTTP/1.0 clients.
2458   In order to remain persistent, all messages on the connection &MUST;
2459   have a self-defined message length (i.e., one not defined by closure
2460   of the connection), as described in <xref target="message.body"/>.
2464<section title="Pipelining" anchor="pipelining">
2466   A client that supports persistent connections &MAY; "pipeline" its
2467   requests (i.e., send multiple requests without waiting for each
2468   response). A server &MUST; send its responses to those requests in the
2469   same order that the requests were received.
2472   Clients which assume persistent connections and pipeline immediately
2473   after connection establishment &SHOULD; be prepared to retry their
2474   connection if the first pipelined attempt fails. If a client does
2475   such a retry, it &MUST-NOT; pipeline before it knows the connection is
2476   persistent. Clients &MUST; also be prepared to resend their requests if
2477   the server closes the connection before sending all of the
2478   corresponding responses.
2481   Clients &SHOULD-NOT; pipeline requests using non-idempotent request methods or
2482   non-idempotent sequences of request methods (see &idempotent-methods;). Otherwise, a
2483   premature termination of the transport connection could lead to
2484   indeterminate results. A client wishing to send a non-idempotent
2485   request &SHOULD; wait to send that request until it has received the
2486   response status line for the previous request.
2491<section title="Proxy Servers" anchor="persistent.proxy">
2493   It is especially important that proxies correctly implement the
2494   properties of the Connection header field as specified in <xref target="header.connection"/>.
2497   The proxy server &MUST; signal persistent connections separately with
2498   its clients and the origin servers (or other proxy servers) that it
2499   connects to. Each persistent connection applies to only one transport
2500   link.
2503   A proxy server &MUST-NOT; establish a HTTP/1.1 persistent connection
2504   with an HTTP/1.0 client (but see <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/>
2505   for information and discussion of the problems with the Keep-Alive header field
2506   implemented by many HTTP/1.0 clients).
2509<section title="End-to-end and Hop-by-hop Header Fields" anchor="end-to-end.and.hop-by-hop.header-fields">
2511  <cref anchor="TODO-end-to-end" source="jre">
2512    Restored from <eref target=""/>.
2513    See also <eref target=""/>.
2514  </cref>
2517   For the purpose of defining the behavior of caches and non-caching
2518   proxies, we divide HTTP header fields into two categories:
2519  <list style="symbols">
2520      <t>End-to-end header fields, which are  transmitted to the ultimate
2521        recipient of a request or response. End-to-end header fields in
2522        responses MUST be stored as part of a cache entry and &MUST; be
2523        transmitted in any response formed from a cache entry.</t>
2525      <t>Hop-by-hop header fields, which are meaningful only for a single
2526        transport-level connection, and are not stored by caches or
2527        forwarded by proxies.</t>
2528  </list>
2531   The following HTTP/1.1 header fields are hop-by-hop header fields:
2532  <list style="symbols">
2533      <t>Connection</t>
2534      <t>Keep-Alive</t>
2535      <t>Proxy-Authenticate</t>
2536      <t>Proxy-Authorization</t>
2537      <t>TE</t>
2538      <t>Trailer</t>
2539      <t>Transfer-Encoding</t>
2540      <t>Upgrade</t>
2541  </list>
2544   All other header fields defined by HTTP/1.1 are end-to-end header fields.
2547   Other hop-by-hop header fields &MUST; be listed in a Connection header field
2548   (<xref target="header.connection"/>).
2552<section title="Non-modifiable Header Fields" anchor="non-modifiable.header-fields">
2554  <cref anchor="TODO-non-mod-headers" source="jre">
2555    Restored from <eref target=""/>.
2556    See also <eref target=""/>.
2557  </cref>
2560   Some features of HTTP/1.1, such as Digest Authentication, depend on the
2561   value of certain end-to-end header fields. A non-transforming proxy &SHOULD-NOT;
2562   modify an end-to-end header field unless the definition of that header field requires
2563   or specifically allows that.
2566   A non-transforming proxy &MUST-NOT; modify any of the following fields in a
2567   request or response, and it &MUST-NOT; add any of these fields if not
2568   already present:
2569  <list style="symbols">
2570    <t>Allow</t>
2571    <t>Content-Location</t>
2572    <t>Content-MD5</t>
2573    <t>ETag</t>
2574    <t>Last-Modified</t>
2575    <t>Server</t>
2576  </list>
2579   A non-transforming proxy &MUST-NOT; modify any of the following fields in a
2580   response:
2581  <list style="symbols">
2582    <t>Expires</t>
2583  </list>
2586   but it &MAY; add any of these fields if not already present. If an
2587   Expires header field is added, it &MUST; be given a field-value identical to
2588   that of the Date header field in that response.
2591   A proxy &MUST-NOT; modify or add any of the following fields in a
2592   message that contains the no-transform cache-control directive, or in
2593   any request:
2594  <list style="symbols">
2595    <t>Content-Encoding</t>
2596    <t>Content-Range</t>
2597    <t>Content-Type</t>
2598  </list>
2601   A transforming proxy &MAY; modify or add these fields to a message
2602   that does not include no-transform, but if it does so, it &MUST; add a
2603   Warning 214 (Transformation applied) if one does not already appear
2604   in the message (see &header-warning;).
2607  <t>
2608    <x:h>Warning:</x:h> Unnecessary modification of end-to-end header fields might
2609    cause authentication failures if stronger authentication
2610    mechanisms are introduced in later versions of HTTP. Such
2611    authentication mechanisms &MAY; rely on the values of header fields
2612    not listed here.
2613  </t>
2616   A non-transforming proxy &MUST; preserve the message payload (&payload;),
2617   though it &MAY; change the message-body through application or removal
2618   of a transfer-coding (<xref target="transfer.codings"/>).
2624<section title="Practical Considerations" anchor="persistent.practical">
2626   Servers will usually have some time-out value beyond which they will
2627   no longer maintain an inactive connection. Proxy servers might make
2628   this a higher value since it is likely that the client will be making
2629   more connections through the same server. The use of persistent
2630   connections places no requirements on the length (or existence) of
2631   this time-out for either the client or the server.
2634   When a client or server wishes to time-out it &SHOULD; issue a graceful
2635   close on the transport connection. Clients and servers &SHOULD; both
2636   constantly watch for the other side of the transport close, and
2637   respond to it as appropriate. If a client or server does not detect
2638   the other side's close promptly it could cause unnecessary resource
2639   drain on the network.
2642   A client, server, or proxy &MAY; close the transport connection at any
2643   time. For example, a client might have started to send a new request
2644   at the same time that the server has decided to close the "idle"
2645   connection. From the server's point of view, the connection is being
2646   closed while it was idle, but from the client's point of view, a
2647   request is in progress.
2650   Clients (including proxies) &SHOULD; limit the number of simultaneous
2651   connections that they maintain to a given server (including proxies).
2654   Previous revisions of HTTP gave a specific number of connections as a
2655   ceiling, but this was found to be impractical for many applications. As a
2656   result, this specification does not mandate a particular maximum number of
2657   connections, but instead encourages clients to be conservative when opening
2658   multiple connections.
2661   In particular, while using multiple connections avoids the "head-of-line
2662   blocking" problem (whereby a request that takes significant server-side
2663   processing and/or has a large payload can block subsequent requests on the
2664   same connection), each connection used consumes server resources (sometimes
2665   significantly), and furthermore using multiple connections can cause
2666   undesirable side effects in congested networks.
2669   Note that servers might reject traffic that they deem abusive, including an
2670   excessive number of connections from a client.
2674<section title="Retrying Requests" anchor="persistent.retrying.requests">
2676   Senders can close the transport connection at any time. Therefore,
2677   clients, servers, and proxies &MUST; be able to recover
2678   from asynchronous close events. Client software &MAY; reopen the
2679   transport connection and retransmit the aborted sequence of requests
2680   without user interaction so long as the request sequence is
2681   idempotent (see &idempotent-methods;). Non-idempotent request methods or sequences
2682   &MUST-NOT; be automatically retried, although user agents &MAY; offer a
2683   human operator the choice of retrying the request(s). Confirmation by
2684   user-agent software with semantic understanding of the application
2685   &MAY; substitute for user confirmation. The automatic retry &SHOULD-NOT;
2686   be repeated if the second sequence of requests fails.
2692<section title="Message Transmission Requirements" anchor="message.transmission.requirements">
2694<section title="Persistent Connections and Flow Control" anchor="persistent.flow">
2696   HTTP/1.1 servers &SHOULD; maintain persistent connections and use TCP's
2697   flow control mechanisms to resolve temporary overloads, rather than
2698   terminating connections with the expectation that clients will retry.
2699   The latter technique can exacerbate network congestion.
2703<section title="Monitoring Connections for Error Status Messages" anchor="persistent.monitor">
2705   An HTTP/1.1 (or later) client sending a message-body &SHOULD; monitor
2706   the network connection for an error status code while it is transmitting
2707   the request. If the client sees an error status code, it &SHOULD;
2708   immediately cease transmitting the body. If the body is being sent
2709   using a "chunked" encoding (<xref target="transfer.codings"/>), a zero length chunk and
2710   empty trailer &MAY; be used to prematurely mark the end of the message.
2711   If the body was preceded by a Content-Length header field, the client &MUST;
2712   close the connection.
2716<section title="Use of the 100 (Continue) Status" anchor="use.of.the.100.status">
2718   The purpose of the 100 (Continue) status code (see &status-100;) is to
2719   allow a client that is sending a request message with a request body
2720   to determine if the origin server is willing to accept the request
2721   (based on the request header fields) before the client sends the request
2722   body. In some cases, it might either be inappropriate or highly
2723   inefficient for the client to send the body if the server will reject
2724   the message without looking at the body.
2727   Requirements for HTTP/1.1 clients:
2728  <list style="symbols">
2729    <t>
2730        If a client will wait for a 100 (Continue) response before
2731        sending the request body, it &MUST; send an Expect header
2732        field (&header-expect;) with the "100-continue" expectation.
2733    </t>
2734    <t>
2735        A client &MUST-NOT; send an Expect header field (&header-expect;)
2736        with the "100-continue" expectation if it does not intend
2737        to send a request body.
2738    </t>
2739  </list>
2742   Because of the presence of older implementations, the protocol allows
2743   ambiguous situations in which a client might send "Expect: 100-continue"
2744   without receiving either a 417 (Expectation Failed)
2745   or a 100 (Continue) status code. Therefore, when a client sends this
2746   header field to an origin server (possibly via a proxy) from which it
2747   has never seen a 100 (Continue) status code, the client &SHOULD-NOT; 
2748   wait for an indefinite period before sending the request body.
2751   Requirements for HTTP/1.1 origin servers:
2752  <list style="symbols">
2753    <t> Upon receiving a request which includes an Expect header
2754        field with the "100-continue" expectation, an origin server &MUST;
2755        either respond with 100 (Continue) status code and continue to read
2756        from the input stream, or respond with a final status code. The
2757        origin server &MUST-NOT; wait for the request body before sending
2758        the 100 (Continue) response. If it responds with a final status
2759        code, it &MAY; close the transport connection or it &MAY; continue
2760        to read and discard the rest of the request.  It &MUST-NOT;
2761        perform the request method if it returns a final status code.
2762    </t>
2763    <t> An origin server &SHOULD-NOT;  send a 100 (Continue) response if
2764        the request message does not include an Expect header
2765        field with the "100-continue" expectation, and &MUST-NOT; send a
2766        100 (Continue) response if such a request comes from an HTTP/1.0
2767        (or earlier) client. There is an exception to this rule: for
2768        compatibility with <xref target="RFC2068"/>, a server &MAY; send a 100 (Continue)
2769        status code in response to an HTTP/1.1 PUT or POST request that does
2770        not include an Expect header field with the "100-continue"
2771        expectation. This exception, the purpose of which is
2772        to minimize any client processing delays associated with an
2773        undeclared wait for 100 (Continue) status code, applies only to
2774        HTTP/1.1 requests, and not to requests with any other HTTP-version
2775        value.
2776    </t>
2777    <t> An origin server &MAY; omit a 100 (Continue) response if it has
2778        already received some or all of the request body for the
2779        corresponding request.
2780    </t>
2781    <t> An origin server that sends a 100 (Continue) response &MUST;
2782        ultimately send a final status code, once the request body is
2783        received and processed, unless it terminates the transport
2784        connection prematurely.
2785    </t>
2786    <t> If an origin server receives a request that does not include an
2787        Expect header field with the "100-continue" expectation,
2788        the request includes a request body, and the server responds
2789        with a final status code before reading the entire request body
2790        from the transport connection, then the server &SHOULD-NOT;  close
2791        the transport connection until it has read the entire request,
2792        or until the client closes the connection. Otherwise, the client
2793        might not reliably receive the response message. However, this
2794        requirement ought not be construed as preventing a server from
2795        defending itself against denial-of-service attacks, or from
2796        badly broken client implementations.
2797      </t>
2798    </list>
2801   Requirements for HTTP/1.1 proxies:
2802  <list style="symbols">
2803    <t> If a proxy receives a request that includes an Expect header
2804        field with the "100-continue" expectation, and the proxy
2805        either knows that the next-hop server complies with HTTP/1.1 or
2806        higher, or does not know the HTTP version of the next-hop
2807        server, it &MUST; forward the request, including the Expect header
2808        field.
2809    </t>
2810    <t> If the proxy knows that the version of the next-hop server is
2811        HTTP/1.0 or lower, it &MUST-NOT; forward the request, and it &MUST;
2812        respond with a 417 (Expectation Failed) status code.
2813    </t>
2814    <t> Proxies &SHOULD; maintain a record of the HTTP version
2815        numbers received from recently-referenced next-hop servers.
2816    </t>
2817    <t> A proxy &MUST-NOT; forward a 100 (Continue) response if the
2818        request message was received from an HTTP/1.0 (or earlier)
2819        client and did not include an Expect header field with
2820        the "100-continue" expectation. This requirement overrides the
2821        general rule for forwarding of 1xx responses (see &status-1xx;).
2822    </t>
2823  </list>
2827<section title="Closing Connections on Error" anchor="closing.connections.on.error">
2829   If the client is sending data, a server implementation using TCP
2830   &SHOULD; be careful to ensure that the client acknowledges receipt of
2831   the packet(s) containing the response, before the server closes the
2832   input connection. If the client continues sending data to the server
2833   after the close, the server's TCP stack will send a reset packet to
2834   the client, which might erase the client's unacknowledged input buffers
2835   before they can be read and interpreted by the HTTP application.
2843<section title="Miscellaneous notes that might disappear" anchor="misc">
2844<section title="Scheme aliases considered harmful" anchor="scheme.aliases">
2846   <cref anchor="TBD-aliases-harmful">describe why aliases like webcal are harmful.</cref>
2850<section title="Use of HTTP for proxy communication" anchor="http.proxy">
2852   <cref anchor="TBD-proxy-other">Configured to use HTTP to proxy HTTP or other protocols.</cref>
2856<section title="Interception of HTTP for access control" anchor="http.intercept">
2858   <cref anchor="TBD-intercept">Interception of HTTP traffic for initiating access control.</cref>
2862<section title="Use of HTTP by other protocols" anchor="http.others">
2864   <cref anchor="TBD-profiles">Profiles of HTTP defined by other protocol.
2865   Extensions of HTTP like WebDAV.</cref>
2869<section title="Use of HTTP by media type specification" anchor="">
2871   <cref anchor="TBD-hypertext">Instructions on composing HTTP requests via hypertext formats.</cref>
2876<section title="Header Field Definitions" anchor="header.field.definitions">
2878   This section defines the syntax and semantics of HTTP header fields
2879   related to message origination, framing, and routing.
2881<texttable align="left">
2882  <ttcol>Header Field Name</ttcol>
2883  <ttcol>Defined in...</ttcol>
2885  <c>Connection</c> <c><xref target="header.connection"/></c>
2886  <c>Content-Length</c> <c><xref target="header.content-length"/></c>
2887  <c>Host</c> <c><xref target=""/></c>
2888  <c>TE</c> <c><xref target="header.te"/></c>
2889  <c>Trailer</c> <c><xref target="header.trailer"/></c>
2890  <c>Transfer-Encoding</c> <c><xref target="header.transfer-encoding"/></c>
2891  <c>Upgrade</c> <c><xref target="header.upgrade"/></c>
2892  <c>Via</c> <c><xref target="header.via"/></c>
2895<section title="Connection" anchor="header.connection">
2896  <iref primary="true" item="Connection header field" x:for-anchor=""/>
2897  <iref primary="true" item="Header Fields" subitem="Connection" x:for-anchor=""/>
2898  <x:anchor-alias value="Connection"/>
2899  <x:anchor-alias value="connection-token"/>
2901   The "Connection" header field allows the sender to specify
2902   options that are desired only for that particular connection.
2903   Such connection options &MUST; be removed or replaced before the
2904   message can be forwarded downstream by a proxy or gateway.
2905   This mechanism also allows the sender to indicate which HTTP
2906   header fields used in the message are only intended for the
2907   immediate recipient ("hop-by-hop"), as opposed to all recipients
2908   on the chain ("end-to-end"), enabling the message to be
2909   self-descriptive and allowing future connection-specific extensions
2910   to be deployed in HTTP without fear that they will be blindly
2911   forwarded by previously deployed intermediaries.
2914   The Connection header field's value has the following grammar:
2916<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="connection-token"/>
2917  <x:ref>Connection</x:ref>       = 1#<x:ref>connection-token</x:ref>
2918  <x:ref>connection-token</x:ref> = <x:ref>token</x:ref>
2921   A proxy or gateway &MUST; parse a received Connection
2922   header field before a message is forwarded and, for each
2923   connection-token in this field, remove any header field(s) from
2924   the message with the same name as the connection-token, and then
2925   remove the Connection header field itself or replace it with the
2926   sender's own connection options for the forwarded message.
2929   A sender &MUST-NOT; include field-names in the Connection header
2930   field-value for fields that are defined as expressing constraints
2931   for all recipients in the request or response chain, such as the
2932   Cache-Control header field (&header-cache-control;).
2935   The connection options do not have to correspond to a header field
2936   present in the message, since a connection-specific header field
2937   might not be needed if there are no parameters associated with that
2938   connection option.  Recipients that trigger certain connection
2939   behavior based on the presence of connection options &MUST; do so
2940   based on the presence of the connection-token rather than only the
2941   presence of the optional header field.  In other words, if the
2942   connection option is received as a header field but not indicated
2943   within the Connection field-value, then the recipient &MUST; ignore
2944   the connection-specific header field because it has likely been
2945   forwarded by an intermediary that is only partially conformant.
2948   When defining new connection options, specifications ought to
2949   carefully consider existing deployed header fields and ensure
2950   that the new connection-token does not share the same name as
2951   an unrelated header field that might already be deployed.
2952   Defining a new connection-token essentially reserves that potential
2953   field-name for carrying additional information related to the
2954   connection option, since it would be unwise for senders to use
2955   that field-name for anything else.
2958   HTTP/1.1 defines the "close" connection option for the sender to
2959   signal that the connection will be closed after completion of the
2960   response. For example,
2962<figure><artwork type="example">
2963  Connection: close
2966   in either the request or the response header fields indicates that
2967   the connection &SHOULD-NOT;  be considered "persistent" (<xref target="persistent.connections"/>)
2968   after the current request/response is complete.
2971   An HTTP/1.1 client that does not support persistent connections &MUST;
2972   include the "close" connection option in every request message.
2975   An HTTP/1.1 server that does not support persistent connections &MUST;
2976   include the "close" connection option in every response message that
2977   does not have a 1xx (Informational) status code.
2981<section title="Content-Length" anchor="header.content-length">
2982  <iref primary="true" item="Content-Length header field" x:for-anchor=""/>
2983  <iref primary="true" item="Header Fields" subitem="Content-Length" x:for-anchor=""/>
2984  <x:anchor-alias value="Content-Length"/>
2986   The "Content-Length" header field indicates the size of the
2987   message-body, in decimal number of octets, for any message other than
2988   a response to a HEAD request or a response with a status code of 304.
2989   In the case of a response to a HEAD request, Content-Length indicates
2990   the size of the payload body (not including any potential transfer-coding)
2991   that would have been sent had the request been a GET.
2992   In the case of a 304 (Not Modified) response to a GET request,
2993   Content-Length indicates the size of the payload body (not including
2994   any potential transfer-coding) that would have been sent in a 200 (OK)
2995   response.
2997<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/>
2998  <x:ref>Content-Length</x:ref> = 1*<x:ref>DIGIT</x:ref>
3001   An example is
3003<figure><artwork type="example">
3004  Content-Length: 3495
3007   Implementations &SHOULD; use this field to indicate the message-body
3008   length when no transfer-coding is being applied and the
3009   payload's body length can be determined prior to being transferred.
3010   <xref target="message.body"/> describes how recipients determine the length
3011   of a message-body.
3014   Any Content-Length greater than or equal to zero is a valid value.
3017   Note that the use of this field in HTTP is significantly different from
3018   the corresponding definition in MIME, where it is an optional field
3019   used within the "message/external-body" content-type.
3023<section title="Host" anchor="">
3024  <iref primary="true" item="Host header field" x:for-anchor=""/>
3025  <iref primary="true" item="Header Fields" subitem="Host" x:for-anchor=""/>
3026  <x:anchor-alias value="Host"/>
3028   The "Host" header field in a request provides the host and port
3029   information from the target resource's URI, enabling the origin
3030   server to distinguish between resources while servicing requests
3031   for multiple host names on a single IP address.  Since the Host
3032   field-value is critical information for handling a request, it
3033   &SHOULD; be sent as the first header field following the Request-Line.
3035<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Host"/>
3036  <x:ref>Host</x:ref> = <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ; <xref target="http.uri"/>
3039   A client &MUST; send a Host header field in all HTTP/1.1 request
3040   messages.  If the target resource's URI includes an authority
3041   component, then the Host field-value &MUST; be identical to that
3042   authority component after excluding any userinfo (<xref target="http.uri"/>).
3043   If the authority component is missing or undefined for the target
3044   resource's URI, then the Host header field &MUST; be sent with an
3045   empty field-value.
3048   For example, a GET request to the origin server for
3049   &lt;; would begin with:
3051<figure><artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
3052GET /pub/WWW/ HTTP/1.1
3056   The Host header field &MUST; be sent in an HTTP/1.1 request even
3057   if the request-target is in the form of an absolute-URI, since this
3058   allows the Host information to be forwarded through ancient HTTP/1.0
3059   proxies that might not have implemented Host.
3062   When an HTTP/1.1 proxy receives a request with a request-target in
3063   the form of an absolute-URI, the proxy &MUST; ignore the received
3064   Host header field (if any) and instead replace it with the host
3065   information of the request-target.  When a proxy forwards a request,
3066   it &MUST; generate the Host header field based on the received
3067   absolute-URI rather than the received Host.
3070   Since the Host header field acts as an application-level routing
3071   mechanism, it is a frequent target for malware seeking to poison
3072   a shared cache or redirect a request to an unintended server.
3073   An interception proxy is particularly vulnerable if it relies on
3074   the Host header field value for redirecting requests to internal
3075   servers, or for use as a cache key in a shared cache, without
3076   first verifying that the intercepted connection is targeting a
3077   valid IP address for that host.
3080   A server &MUST; respond with a 400 (Bad Request) status code to
3081   any HTTP/1.1 request message that lacks a Host header field and
3082   to any request message that contains more than one Host header field
3083   or a Host header field with an invalid field-value.
3086   See Sections <xref target="" format="counter"/>
3087   and <xref target="" format="counter"/>
3088   for other requirements relating to Host.
3092<section title="TE" anchor="header.te">
3093  <iref primary="true" item="TE header field" x:for-anchor=""/>
3094  <iref primary="true" item="Header Fields" subitem="TE" x:for-anchor=""/>
3095  <x:anchor-alias value="TE"/>
3096  <x:anchor-alias value="t-codings"/>
3097  <x:anchor-alias value="te-params"/>
3098  <x:anchor-alias value="te-ext"/>
3100   The "TE" header field indicates what extension transfer-codings
3101   the client is willing to accept in the response, and whether or not it is
3102   willing to accept trailer fields in a chunked transfer-coding.
3105   Its value consists of the keyword "trailers" and/or a comma-separated
3106   list of extension transfer-coding names with optional accept
3107   parameters (as described in <xref target="transfer.codings"/>).
3109<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"/>
3110  <x:ref>TE</x:ref>        = #<x:ref>t-codings</x:ref>
3111  <x:ref>t-codings</x:ref> = "trailers" / ( <x:ref>transfer-extension</x:ref> [ <x:ref>te-params</x:ref> ] )
3112  <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> )
3113  <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> ]
3116   The presence of the keyword "trailers" indicates that the client is
3117   willing to accept trailer fields in a chunked transfer-coding, as
3118   defined in <xref target="chunked.encoding"/>. This keyword is reserved for use with
3119   transfer-coding values even though it does not itself represent a
3120   transfer-coding.
3123   Examples of its use are:
3125<figure><artwork type="example">
3126  TE: deflate
3127  TE:
3128  TE: trailers, deflate;q=0.5
3131   The TE header field only applies to the immediate connection.
3132   Therefore, the keyword &MUST; be supplied within a Connection header
3133   field (<xref target="header.connection"/>) whenever TE is present in an HTTP/1.1 message.
3136   A server tests whether a transfer-coding is acceptable, according to
3137   a TE field, using these rules:
3138  <list style="numbers">
3139    <x:lt>
3140      <t>The "chunked" transfer-coding is always acceptable. If the
3141         keyword "trailers" is listed, the client indicates that it is
3142         willing to accept trailer fields in the chunked response on
3143         behalf of itself and any downstream clients. The implication is
3144         that, if given, the client is stating that either all
3145         downstream clients are willing to accept trailer fields in the
3146         forwarded response, or that it will attempt to buffer the
3147         response on behalf of downstream recipients.
3148      </t><t>
3149         <x:h>Note:</x:h> HTTP/1.1 does not define any means to limit the size of a
3150         chunked response such that a client can be assured of buffering
3151         the entire response.</t>
3152    </x:lt>
3153    <x:lt>
3154      <t>If the transfer-coding being tested is one of the transfer-codings
3155         listed in the TE field, then it is acceptable unless it
3156         is accompanied by a qvalue of 0. (As defined in <xref target="quality.values"/>, a
3157         qvalue of 0 means "not acceptable".)</t>
3158    </x:lt>
3159    <x:lt>
3160      <t>If multiple transfer-codings are acceptable, then the
3161         acceptable transfer-coding with the highest non-zero qvalue is
3162         preferred.  The "chunked" transfer-coding always has a qvalue
3163         of 1.</t>
3164    </x:lt>
3165  </list>
3168   If the TE field-value is empty or if no TE field is present, the only
3169   acceptable transfer-coding is "chunked". A message with no transfer-coding is
3170   always acceptable.
3174<section title="Trailer" anchor="header.trailer">
3175  <iref primary="true" item="Trailer header field" x:for-anchor=""/>
3176  <iref primary="true" item="Header Fields" subitem="Trailer" x:for-anchor=""/>
3177  <x:anchor-alias value="Trailer"/>
3179   The "Trailer" header field indicates that the given set of
3180   header fields is present in the trailer of a message encoded with
3181   chunked transfer-coding.
3183<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Trailer"/>
3184  <x:ref>Trailer</x:ref> = 1#<x:ref>field-name</x:ref>
3187   An HTTP/1.1 message &SHOULD; include a Trailer header field in a
3188   message using chunked transfer-coding with a non-empty trailer. Doing
3189   so allows the recipient to know which header fields to expect in the
3190   trailer.
3193   If no Trailer header field is present, the trailer &SHOULD-NOT;  include
3194   any header fields. See <xref target="chunked.encoding"/> for restrictions on the use of
3195   trailer fields in a "chunked" transfer-coding.
3198   Message header fields listed in the Trailer header field &MUST-NOT;
3199   include the following header fields:
3200  <list style="symbols">
3201    <t>Transfer-Encoding</t>
3202    <t>Content-Length</t>
3203    <t>Trailer</t>
3204  </list>
3208<section title="Transfer-Encoding" anchor="header.transfer-encoding">
3209  <iref primary="true" item="Transfer-Encoding header field" x:for-anchor=""/>
3210  <iref primary="true" item="Header Fields" subitem="Transfer-Encoding" x:for-anchor=""/>
3211  <x:anchor-alias value="Transfer-Encoding"/>
3213   The "Transfer-Encoding" header field indicates what transfer-codings
3214   (if any) have been applied to the message body. It differs from
3215   Content-Encoding (&content-codings;) in that transfer-codings are a property
3216   of the message (and therefore are removed by intermediaries), whereas
3217   content-codings are not.
3219<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Transfer-Encoding"/>
3220  <x:ref>Transfer-Encoding</x:ref> = 1#<x:ref>transfer-coding</x:ref>
3223   Transfer-codings are defined in <xref target="transfer.codings"/>. An example is:
3225<figure><artwork type="example">
3226  Transfer-Encoding: chunked
3229   If multiple encodings have been applied to a representation, the transfer-codings
3230   &MUST; be listed in the order in which they were applied.
3231   Additional information about the encoding parameters &MAY; be provided
3232   by other header fields not defined by this specification.
3235   Many older HTTP/1.0 applications do not understand the Transfer-Encoding
3236   header field.
3240<section title="Upgrade" anchor="header.upgrade">
3241  <iref primary="true" item="Upgrade header field" x:for-anchor=""/>
3242  <iref primary="true" item="Header Fields" subitem="Upgrade" x:for-anchor=""/>
3243  <x:anchor-alias value="Upgrade"/>
3245   The "Upgrade" header field allows the client to specify what
3246   additional communication protocols it would like to use, if the server
3247   chooses to switch protocols. Servers can use it to indicate what protocols
3248   they are willing to switch to.
3250<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Upgrade"/>
3251  <x:ref>Upgrade</x:ref> = 1#<x:ref>product</x:ref>
3254   For example,
3256<figure><artwork type="example">
3257  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
3260   The Upgrade header field is intended to provide a simple mechanism
3261   for transitioning from HTTP/1.1 to some other, incompatible protocol. It
3262   does so by allowing the client to advertise its desire to use another
3263   protocol, such as a later version of HTTP with a higher major version
3264   number, even though the current request has been made using HTTP/1.1.
3265   This eases the difficult transition between incompatible protocols by
3266   allowing the client to initiate a request in the more commonly
3267   supported protocol while indicating to the server that it would like
3268   to use a "better" protocol if available (where "better" is determined
3269   by the server, possibly according to the nature of the request method
3270   or target resource).
3273   The Upgrade header field only applies to switching application-layer
3274   protocols upon the existing transport-layer connection. Upgrade
3275   cannot be used to insist on a protocol change; its acceptance and use
3276   by the server is optional. The capabilities and nature of the
3277   application-layer communication after the protocol change is entirely
3278   dependent upon the new protocol chosen, although the first action
3279   after changing the protocol &MUST; be a response to the initial HTTP
3280   request containing the Upgrade header field.
3283   The Upgrade header field only applies to the immediate connection.
3284   Therefore, the upgrade keyword &MUST; be supplied within a Connection
3285   header field (<xref target="header.connection"/>) whenever Upgrade is present in an
3286   HTTP/1.1 message.
3289   The Upgrade header field cannot be used to indicate a switch to a
3290   protocol on a different connection. For that purpose, it is more
3291   appropriate to use a 3xx redirection response (&status-3xx;).
3294   Servers &MUST; include the "Upgrade" header field in 101 (Switching
3295   Protocols) responses to indicate which protocol(s) are being switched to,
3296   and &MUST; include it in 426 (Upgrade Required) responses to indicate
3297   acceptable protocols to upgrade to. Servers &MAY; include it in any other
3298   response to indicate that they are willing to upgrade to one of the
3299   specified protocols.
3302   This specification only defines the protocol name "HTTP" for use by
3303   the family of Hypertext Transfer Protocols, as defined by the HTTP
3304   version rules of <xref target="http.version"/> and future updates to this
3305   specification. Additional tokens can be registered with IANA using the
3306   registration procedure defined below. 
3309<section title="Upgrade Token Registry" anchor="upgrade.token.registry">
3311   The HTTP Upgrade Token Registry defines the name space for product
3312   tokens used to identify protocols in the Upgrade header field.
3313   Each registered token is associated with contact information and
3314   an optional set of specifications that details how the connection
3315   will be processed after it has been upgraded.
3318   Registrations are allowed on a First Come First Served basis as
3319   described in <xref target="RFC5226" x:sec="4.1" x:fmt="of"/>. The
3320   specifications need not be IETF documents or be subject to IESG review.
3321   Registrations are subject to the following rules:
3322  <list style="numbers">
3323    <t>A token, once registered, stays registered forever.</t>
3324    <t>The registration &MUST; name a responsible party for the
3325       registration.</t>
3326    <t>The registration &MUST; name a point of contact.</t>
3327    <t>The registration &MAY; name a set of specifications associated with that
3328       token. Such specifications need not be publicly available.</t>
3329    <t>The responsible party &MAY; change the registration at any time.
3330       The IANA will keep a record of all such changes, and make them
3331       available upon request.</t>
3332    <t>The responsible party for the first registration of a "product"
3333       token &MUST; approve later registrations of a "version" token
3334       together with that "product" token before they can be registered.</t>
3335    <t>If absolutely required, the IESG &MAY; reassign the responsibility
3336       for a token. This will normally only be used in the case when a
3337       responsible party cannot be contacted.</t>
3338  </list>
3345<section title="Via" anchor="header.via">
3346  <iref primary="true" item="Via header field" x:for-anchor=""/>
3347  <iref primary="true" item="Header Fields" subitem="Via" x:for-anchor=""/>
3348  <x:anchor-alias value="protocol-name"/>
3349  <x:anchor-alias value="protocol-version"/>
3350  <x:anchor-alias value="pseudonym"/>
3351  <x:anchor-alias value="received-by"/>
3352  <x:anchor-alias value="received-protocol"/>
3353  <x:anchor-alias value="Via"/>
3355   The "Via" header field &MUST; be sent by a proxy or gateway to
3356   indicate the intermediate protocols and recipients between the user
3357   agent and the server on requests, and between the origin server and
3358   the client on responses. It is analogous to the "Received" field
3359   used by email systems (<xref target="RFC5322" x:fmt="of" x:sec="3.6.7"/>)
3360   and is intended to be used for tracking message forwards,
3361   avoiding request loops, and identifying the protocol capabilities of
3362   all senders along the request/response chain.
3364<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"/>
3365  <x:ref>Via</x:ref>               = 1#( <x:ref>received-protocol</x:ref> <x:ref>RWS</x:ref> <x:ref>received-by</x:ref>
3366                          [ <x:ref>RWS</x:ref> <x:ref>comment</x:ref> ] )
3367  <x:ref>received-protocol</x:ref> = [ <x:ref>protocol-name</x:ref> "/" ] <x:ref>protocol-version</x:ref>
3368  <x:ref>protocol-name</x:ref>     = <x:ref>token</x:ref>
3369  <x:ref>protocol-version</x:ref>  = <x:ref>token</x:ref>
3370  <x:ref>received-by</x:ref>       = ( <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ) / <x:ref>pseudonym</x:ref>
3371  <x:ref>pseudonym</x:ref>         = <x:ref>token</x:ref>
3374   The received-protocol indicates the protocol version of the message
3375   received by the server or client along each segment of the
3376   request/response chain. The received-protocol version is appended to
3377   the Via field value when the message is forwarded so that information
3378   about the protocol capabilities of upstream applications remains
3379   visible to all recipients.
3382   The protocol-name is excluded if and only if it would be "HTTP". The
3383   received-by field is normally the host and optional port number of a
3384   recipient server or client that subsequently forwarded the message.
3385   However, if the real host is considered to be sensitive information,
3386   it &MAY; be replaced by a pseudonym. If the port is not given, it &MAY;
3387   be assumed to be the default port of the received-protocol.
3390   Multiple Via field values represent each proxy or gateway that has
3391   forwarded the message. Each recipient &MUST; append its information
3392   such that the end result is ordered according to the sequence of
3393   forwarding applications.
3396   Comments &MAY; be used in the Via header field to identify the software
3397   of each recipient, analogous to the User-Agent and Server header fields.
3398   However, all comments in the Via field are optional and &MAY; be removed
3399   by any recipient prior to forwarding the message.
3402   For example, a request message could be sent from an HTTP/1.0 user
3403   agent to an internal proxy code-named "fred", which uses HTTP/1.1 to
3404   forward the request to a public proxy at, which completes
3405   the request by forwarding it to the origin server at
3406   The request received by would then have the following
3407   Via header field:
3409<figure><artwork type="example">
3410  Via: 1.0 fred, 1.1 (Apache/1.1)
3413   A proxy or gateway used as a portal through a network firewall
3414   &SHOULD-NOT; forward the names and ports of hosts within the firewall
3415   region unless it is explicitly enabled to do so. If not enabled, the
3416   received-by host of any host behind the firewall &SHOULD; be replaced
3417   by an appropriate pseudonym for that host.
3420   For organizations that have strong privacy requirements for hiding
3421   internal structures, a proxy or gateway &MAY; combine an ordered
3422   subsequence of Via header field entries with identical received-protocol
3423   values into a single such entry. For example,
3425<figure><artwork type="example">
3426  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
3429  could be collapsed to
3431<figure><artwork type="example">
3432  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
3435   Senders &SHOULD-NOT; combine multiple entries unless they are all
3436   under the same organizational control and the hosts have already been
3437   replaced by pseudonyms. Senders &MUST-NOT; combine entries which
3438   have different received-protocol values.
3444<section title="IANA Considerations" anchor="IANA.considerations">
3446<section title="Header Field Registration" anchor="header.field.registration">
3448   The Message Header Field Registry located at <eref target=""/> shall be updated
3449   with the permanent registrations below (see <xref target="RFC3864"/>):
3451<?BEGININC p1-messaging.iana-headers ?>
3452<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
3453<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
3454   <ttcol>Header Field Name</ttcol>
3455   <ttcol>Protocol</ttcol>
3456   <ttcol>Status</ttcol>
3457   <ttcol>Reference</ttcol>
3459   <c>Connection</c>
3460   <c>http</c>
3461   <c>standard</c>
3462   <c>
3463      <xref target="header.connection"/>
3464   </c>
3465   <c>Content-Length</c>
3466   <c>http</c>
3467   <c>standard</c>
3468   <c>
3469      <xref target="header.content-length"/>
3470   </c>
3471   <c>Host</c>
3472   <c>http</c>
3473   <c>standard</c>
3474   <c>
3475      <xref target=""/>
3476   </c>
3477   <c>TE</c>
3478   <c>http</c>
3479   <c>standard</c>
3480   <c>
3481      <xref target="header.te"/>
3482   </c>
3483   <c>Trailer</c>
3484   <c>http</c>
3485   <c>standard</c>
3486   <c>
3487      <xref target="header.trailer"/>
3488   </c>
3489   <c>Transfer-Encoding</c>
3490   <c>http</c>
3491   <c>standard</c>
3492   <c>
3493      <xref target="header.transfer-encoding"/>
3494   </c>
3495   <c>Upgrade</c>
3496   <c>http</c>
3497   <c>standard</c>
3498   <c>
3499      <xref target="header.upgrade"/>
3500   </c>
3501   <c>Via</c>
3502   <c>http</c>
3503   <c>standard</c>
3504   <c>
3505      <xref target="header.via"/>
3506   </c>
3509<?ENDINC p1-messaging.iana-headers ?>
3511   Furthermore, the header field name "Close" shall be registered as "reserved", as its use as
3512   HTTP header field would be in conflict with the use of the "close" connection
3513   option for the "Connection" header field (<xref target="header.connection"/>).
3515<texttable align="left" suppress-title="true">
3516   <ttcol>Header Field Name</ttcol>
3517   <ttcol>Protocol</ttcol>
3518   <ttcol>Status</ttcol>
3519   <ttcol>Reference</ttcol>
3521   <c>Close</c>
3522   <c>http</c>
3523   <c>reserved</c>
3524   <c>
3525      <xref target="header.field.registration"/>
3526   </c>
3529   The change controller is: "IETF ( - Internet Engineering Task Force".
3533<section title="URI Scheme Registration" anchor="uri.scheme.registration">
3535   The entries for the "http" and "https" URI Schemes in the registry located at
3536   <eref target=""/>
3537   shall be updated to point to Sections <xref target="http.uri" format="counter"/>
3538   and <xref target="https.uri" format="counter"/> of this document
3539   (see <xref target="RFC4395"/>).
3543<section title="Internet Media Type Registrations" anchor="">
3545   This document serves as the specification for the Internet media types
3546   "message/http" and "application/http". The following is to be registered with
3547   IANA (see <xref target="RFC4288"/>).
3549<section title="Internet Media Type message/http" anchor="">
3550<iref item="Media Type" subitem="message/http" primary="true"/>
3551<iref item="message/http Media Type" primary="true"/>
3553   The message/http type can be used to enclose a single HTTP request or
3554   response message, provided that it obeys the MIME restrictions for all
3555   "message" types regarding line length and encodings.
3558  <list style="hanging" x:indent="12em">
3559    <t hangText="Type name:">
3560      message
3561    </t>
3562    <t hangText="Subtype name:">
3563      http
3564    </t>
3565    <t hangText="Required parameters:">
3566      none
3567    </t>
3568    <t hangText="Optional parameters:">
3569      version, msgtype
3570      <list style="hanging">
3571        <t hangText="version:">
3572          The HTTP-Version number of the enclosed message
3573          (e.g., "1.1"). If not present, the version can be
3574          determined from the first line of the body.
3575        </t>
3576        <t hangText="msgtype:">
3577          The message type &mdash; "request" or "response". If not
3578          present, the type can be determined from the first
3579          line of the body.
3580        </t>
3581      </list>
3582    </t>
3583    <t hangText="Encoding considerations:">
3584      only "7bit", "8bit", or "binary" are permitted
3585    </t>
3586    <t hangText="Security considerations:">
3587      none
3588    </t>
3589    <t hangText="Interoperability considerations:">
3590      none
3591    </t>
3592    <t hangText="Published specification:">
3593      This specification (see <xref target=""/>).
3594    </t>
3595    <t hangText="Applications that use this media type:">
3596    </t>
3597    <t hangText="Additional information:">
3598      <list style="hanging">
3599        <t hangText="Magic number(s):">none</t>
3600        <t hangText="File extension(s):">none</t>
3601        <t hangText="Macintosh file type code(s):">none</t>
3602      </list>
3603    </t>
3604    <t hangText="Person and email address to contact for further information:">
3605      See Authors Section.
3606    </t>
3607    <t hangText="Intended usage:">
3608      COMMON
3609    </t>
3610    <t hangText="Restrictions on usage:">
3611      none
3612    </t>
3613    <t hangText="Author/Change controller:">
3614      IESG
3615    </t>
3616  </list>
3619<section title="Internet Media Type application/http" anchor="">
3620<iref item="Media Type" subitem="application/http" primary="true"/>
3621<iref item="application/http Media Type" primary="true"/>
3623   The application/http type can be used to enclose a pipeline of one or more
3624   HTTP request or response messages (not intermixed).
3627  <list style="hanging" x:indent="12em">
3628    <t hangText="Type name:">
3629      application
3630    </t>
3631    <t hangText="Subtype name:">
3632      http
3633    </t>
3634    <t hangText="Required parameters:">
3635      none
3636    </t>
3637    <t hangText="Optional parameters:">
3638      version, msgtype
3639      <list style="hanging">
3640        <t hangText="version:">
3641          The HTTP-Version number of the enclosed messages
3642          (e.g., "1.1"). If not present, the version can be
3643          determined from the first line of the body.
3644        </t>
3645        <t hangText="msgtype:">
3646          The message type &mdash; "request" or "response". If not
3647          present, the type can be determined from the first
3648          line of the body.
3649        </t>
3650      </list>
3651    </t>
3652    <t hangText="Encoding considerations:">
3653      HTTP messages enclosed by this type
3654      are in "binary" format; use of an appropriate
3655      Content-Transfer-Encoding is required when
3656      transmitted via E-mail.
3657    </t>
3658    <t hangText="Security considerations:">
3659      none
3660    </t>
3661    <t hangText="Interoperability considerations:">
3662      none
3663    </t>
3664    <t hangText="Published specification:">
3665      This specification (see <xref target=""/>).
3666    </t>
3667    <t hangText="Applications that use this media type:">
3668    </t>
3669    <t hangText="Additional information:">
3670      <list style="hanging">
3671        <t hangText="Magic number(s):">none</t>
3672        <t hangText="File extension(s):">none</t>
3673        <t hangText="Macintosh file type code(s):">none</t>
3674      </list>
3675    </t>
3676    <t hangText="Person and email address to contact for further information:">
3677      See Authors Section.
3678    </t>
3679    <t hangText="Intended usage:">
3680      COMMON
3681    </t>
3682    <t hangText="Restrictions on usage:">
3683      none
3684    </t>
3685    <t hangText="Author/Change controller:">
3686      IESG
3687    </t>
3688  </list>
3693<section title="Transfer Coding Registry" anchor="transfer.coding.registration">
3695   The registration procedure for HTTP Transfer Codings is now defined by
3696   <xref target="transfer.coding.registry"/> of this document.
3699   The HTTP Transfer Codings Registry located at <eref target=""/>
3700   shall be updated with the registrations below:
3702<texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table">
3703   <ttcol>Name</ttcol>
3704   <ttcol>Description</ttcol>
3705   <ttcol>Reference</ttcol>
3706   <c>chunked</c>
3707   <c>Transfer in a series of chunks</c>
3708   <c>
3709      <xref target="chunked.encoding"/>
3710   </c>
3711   <c>compress</c>
3712   <c>UNIX "compress" program method</c>
3713   <c>
3714      <xref target="compress.coding"/>
3715   </c>
3716   <c>deflate</c>
3717   <c>"deflate" compression mechanism (<xref target="RFC1951"/>) used inside
3718   the "zlib" data format (<xref target="RFC1950"/>)
3719   </c>
3720   <c>
3721      <xref target="deflate.coding"/>
3722   </c>
3723   <c>gzip</c>
3724   <c>Same as GNU zip <xref target="RFC1952"/></c>
3725   <c>
3726      <xref target="gzip.coding"/>
3727   </c>
3731<section title="Upgrade Token Registration" anchor="upgrade.token.registration">
3733   The registration procedure for HTTP Upgrade Tokens &mdash; previously defined
3734   in <xref target="RFC2817" x:fmt="of" x:sec="7.2"/> &mdash; is now defined
3735   by <xref target="upgrade.token.registry"/> of this document.
3738   The HTTP Status Code Registry located at <eref target=""/>
3739   shall be updated with the registration below:
3741<texttable align="left" suppress-title="true">
3742   <ttcol>Value</ttcol>
3743   <ttcol>Description</ttcol>
3744   <ttcol>Reference</ttcol>
3746   <c>HTTP</c>
3747   <c>Hypertext Transfer Protocol</c>
3748   <c><xref target="http.version"/> of this specification</c>
3755<section title="Security Considerations" anchor="security.considerations">
3757   This section is meant to inform application developers, information
3758   providers, and users of the security limitations in HTTP/1.1 as
3759   described by this document. The discussion does not include
3760   definitive solutions to the problems revealed, though it does make
3761   some suggestions for reducing security risks.
3764<section title="Personal Information" anchor="personal.information">
3766   HTTP clients are often privy to large amounts of personal information
3767   (e.g., the user's name, location, mail address, passwords, encryption
3768   keys, etc.), and &SHOULD; be very careful to prevent unintentional
3769   leakage of this information.
3770   We very strongly recommend that a convenient interface be provided
3771   for the user to control dissemination of such information, and that
3772   designers and implementors be particularly careful in this area.
3773   History shows that errors in this area often create serious security
3774   and/or privacy problems and generate highly adverse publicity for the
3775   implementor's company.
3779<section title="Abuse of Server Log Information" anchor="abuse.of.server.log.information">
3781   A server is in the position to save personal data about a user's
3782   requests which might identify their reading patterns or subjects of
3783   interest. This information is clearly confidential in nature and its
3784   handling can be constrained by law in certain countries. People using
3785   HTTP to provide data are responsible for ensuring that
3786   such material is not distributed without the permission of any
3787   individuals that are identifiable by the published results.
3791<section title="Attacks Based On File and Path Names" anchor="attack.pathname">
3793   Implementations of HTTP origin servers &SHOULD; be careful to restrict
3794   the documents returned by HTTP requests to be only those that were
3795   intended by the server administrators. If an HTTP server translates
3796   HTTP URIs directly into file system calls, the server &MUST; take
3797   special care not to serve files that were not intended to be
3798   delivered to HTTP clients. For example, UNIX, Microsoft Windows, and
3799   other operating systems use ".." as a path component to indicate a
3800   directory level above the current one. On such a system, an HTTP
3801   server &MUST; disallow any such construct in the request-target if it
3802   would otherwise allow access to a resource outside those intended to
3803   be accessible via the HTTP server. Similarly, files intended for
3804   reference only internally to the server (such as access control
3805   files, configuration files, and script code) &MUST; be protected from
3806   inappropriate retrieval, since they might contain sensitive
3807   information. Experience has shown that minor bugs in such HTTP server
3808   implementations have turned into security risks.
3812<section title="DNS-related Attacks" anchor="dns.related.attacks">
3814   HTTP clients rely heavily on the Domain Name Service (DNS), and are thus
3815   generally prone to security attacks based on the deliberate misassociation
3816   of IP addresses and DNS names not protected by DNSSec. Clients need to be
3817   cautious in assuming the validity of an IP number/DNS name association unless
3818   the response is protected by DNSSec (<xref target="RFC4033"/>).
3822<section title="Proxies and Caching" anchor="attack.proxies">
3824   By their very nature, HTTP proxies are men-in-the-middle, and
3825   represent an opportunity for man-in-the-middle attacks. Compromise of
3826   the systems on which the proxies run can result in serious security
3827   and privacy problems. Proxies have access to security-related
3828   information, personal information about individual users and
3829   organizations, and proprietary information belonging to users and
3830   content providers. A compromised proxy, or a proxy implemented or
3831   configured without regard to security and privacy considerations,
3832   might be used in the commission of a wide range of potential attacks.
3835   Proxy operators need to protect the systems on which proxies run as
3836   they would protect any system that contains or transports sensitive
3837   information. In particular, log information gathered at proxies often
3838   contains highly sensitive personal information, and/or information
3839   about organizations. Log information needs to be carefully guarded, and
3840   appropriate guidelines for use need to be developed and followed.
3841   (<xref target="abuse.of.server.log.information"/>).
3844   Proxy implementors need to consider the privacy and security
3845   implications of their design and coding decisions, and of the
3846   configuration options they provide to proxy operators (especially the
3847   default configuration).
3850   Users of a proxy need to be aware that proxies are no more trustworthy than
3851   the people who run them; HTTP itself cannot solve this problem.
3854   The judicious use of cryptography, when appropriate, might suffice to
3855   protect against a broad range of security and privacy attacks. Such
3856   cryptography is beyond the scope of the HTTP/1.1 specification.
3860<section title="Protocol Element Size Overflows" anchor="attack.protocol.element.size.overflows">
3862   Because HTTP uses mostly textual, character-delimited fields, attackers can
3863   overflow buffers in implementations, and/or perform a Denial of Service
3864   against implementations that accept fields with unlimited lengths.
3867   To promote interoperability, this specification makes specific
3868   recommendations for size limits on request-targets (<xref target="request-target"/>)
3869   and blocks of header fields (<xref target="header.fields"/>). These are
3870   minimum recommendations, chosen to be supportable even by implementations
3871   with limited resources; it is expected that most implementations will choose
3872   substantially higher limits.
3875   This specification also provides a way for servers to reject messages that
3876   have request-targets that are too long (&status-414;) or request entities
3877   that are too large (&status-4xx;).
3880   Other fields (including but not limited to request methods, response status
3881   phrases, header field-names, and body chunks) &SHOULD; be limited by
3882   implementations carefully, so as to not impede interoperability.
3886<section title="Denial of Service Attacks on Proxies" anchor="attack.DoS">
3888   They exist. They are hard to defend against. Research continues.
3889   Beware.
3894<section title="Acknowledgments" anchor="acks">
3896   This document revision builds on the work that went into
3897   <xref target="RFC2616" format="none">RFC 2616</xref> and its predecessors.
3898   See <xref target="RFC2616" x:fmt="of" x:sec="16"/> for detailed
3899   acknowledgements.
3902   Since 1999, many contributors have helped by reporting bugs, asking
3903   smart questions, drafting and reviewing text, and discussing open issues:
3905<?BEGININC acks ?>
3906<t>Adam Barth,
3907Adam Roach,
3908Addison Phillips,
3909Adrian Chadd,
3910Adrien de Croy,
3911Alan Ford,
3912Alan Ruttenberg,
3913Albert Lunde,
3914Alex Rousskov,
3915Alexey Melnikov,
3916Alisha Smith,
3917Amichai Rothman,
3918Amit Klein,
3919Amos Jeffries,
3920Andreas Maier,
3921Andreas Petersson,
3922Anne van Kesteren,
3923Anthony Bryan,
3924Asbjorn Ulsberg,
3925Balachander Krishnamurthy,
3926Barry Leiba,
3927Ben Laurie,
3928Benjamin Niven-Jenkins,
3929Bil Corry,
3930Bill Burke,
3931Bjoern Hoehrmann,
3932Bob Scheifler,
3933Boris Zbarsky,
3934Brett Slatkin,
3935Brian Kell,
3936Brian McBarron,
3937Brian Pane,
3938Brian Smith,
3939Bryce Nesbitt,
3940Cameron Heavon-Jones,
3941Carl Kugler,
3942Charles Fry,
3943Chris Newman,
3944Cyrus Daboo,
3945Dale Robert Anderson,
3946Dan Winship,
3947Daniel Stenberg,
3948Dave Cridland,
3949Dave Crocker,
3950Dave Kristol,
3951David Booth,
3952David Singer,
3953David W. Morris,
3954Diwakar Shetty,
3955Dmitry Kurochkin,
3956Drummond Reed,
3957Duane Wessels,
3958Edward Lee,
3959Eliot Lear,
3960Eran Hammer-Lahav,
3961Eric D. Williams,
3962Eric J. Bowman,
3963Eric Lawrence,
3964Erik Aronesty,
3965Florian Weimer,
3966Frank Ellermann,
3967Fred Bohle,
3968Geoffrey Sneddon,
3969Gervase Markham,
3970Greg Wilkins,
3971Harald Tveit Alvestrand,
3972Harry Halpin,
3973Helge Hess,
3974Henrik Nordstrom,
3975Henry S. Thompson,
3976Henry Story,
3977Herbert van de Sompel,
3978Howard Melman,
3979Hugo Haas,
3980Ian Hickson,
3981Ingo Struck,
3982J. Ross Nicoll,
3983James H. Manger,
3984James Lacey,
3985James M. Snell,
3986Jamie Lokier,
3987Jan Algermissen,
3988Jeff Hodges (for coming up with the term 'effective Request-URI'),
3989Jeff Walden,
3990Jim Luther,
3991Joe D. Williams,
3992Joe Gregorio,
3993Joe Orton,
3994John C. Klensin,
3995John C. Mallery,
3996John Cowan,
3997John Kemp,
3998John Panzer,
3999John Schneider,
4000John Stracke,
4001Jonas Sicking,
4002Jonathan Moore,
4003Jonathan Rees,
4004Jordi Ros,
4005Joris Dobbelsteen,
4006Josh Cohen,
4007Julien Pierre,
4008Jungshik Shin,
4009Justin Chapweske,
4010Justin Erenkrantz,
4011Justin James,
4012Kalvinder Singh,
4013Karl Dubost,
4014Keith Hoffman,
4015Keith Moore,
4016Koen Holtman,
4017Konstantin Voronkov,
4018Kris Zyp,
4019Lisa Dusseault,
4020Maciej Stachowiak,
4021Marc Schneider,
4022Marc Slemko,
4023Mark Baker,
4024Mark Nottingham (Working Group chair),
4025Mark Pauley,
4026Markus Lanthaler,
4027Martin J. Duerst,
4028Martin Thomson,
4029Matt Lynch,
4030Matthew Cox,
4031Max Clark,
4032Michael Burrows,
4033Michael Hausenblas,
4034Mike Amundsen,
4035Mike Kelly,
4036Mike Schinkel,
4037Miles Sabin,
4038Mykyta Yevstifeyev,
4039Nathan Rixham,
4040Nicholas Shanks,
4041Nico Williams,
4042Nicolas Alvarez,
4043Noah Slater,
4044Pablo Castro,
4045Pat Hayes,
4046Patrick R. McManus,
4047Paul E. Jones,
4048Paul Hoffman,
4049Paul Marquess,
4050Peter Saint-Andre,
4051Peter Watkins,
4052Phil Archer,
4053Phillip Hallam-Baker,
4054Poul-Henning Kamp,
4055Preethi Natarajan,
4056Ray Polk,
4057Reto Bachmann-Gmuer,
4058Richard Cyganiak,
4059Robert Brewer,
4060Robert Collins,
4061Robert O'Callahan,
4062Robert Olofsson,
4063Robert Sayre,
4064Robert Siemer,
4065Robert de Wilde,
4066Roberto Javier Godoy,
4067Ronny Widjaja,
4068S. Mike Dierken,
4069Salvatore Loreto,
4070Sam Johnston,
4071Sam Ruby,
4072Scott Lawrence (for maintaining the original issues list),
4073Sean B. Palmer,
4074Shane McCarron,
4075Stefan Eissing,
4076Stefan Tilkov,
4077Stefanos Harhalakis,
4078Stephane Bortzmeyer,
4079Stuart Williams,
4080Subbu Allamaraju,
4081Sylvain Hellegouarch,
4082Tapan Divekar,
4083Thomas Broyer,
4084Thomas Nordin,
4085Thomas Roessler,
4086Tim Morgan,
4087Tim Olsen,
4088Travis Snoozy,
4089Tyler Close,
4090Vincent Murphy,
4091Wenbo Zhu,
4092Werner Baumann,
4093Wilbur Streett,
4094Wilfredo Sanchez Vega,
4095William A. Rowe Jr.,
4096William Chan,
4097Willy Tarreau,
4098Xiaoshu Wang,
4099Yaron Goland,
4100Yngve Nysaeter Pettersen,
4101Yogesh Bang,
4102Yutaka Oiwa,
4103Zed A. Shaw, and
4104Zhong Yu.
4106<?ENDINC acks ?>
4112<references title="Normative References">
4114<reference anchor="ISO-8859-1">
4115  <front>
4116    <title>
4117     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
4118    </title>
4119    <author>
4120      <organization>International Organization for Standardization</organization>
4121    </author>
4122    <date year="1998"/>
4123  </front>
4124  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
4127<reference anchor="Part2">
4128  <front>
4129    <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
4130    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4131      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4132      <address><email></email></address>
4133    </author>
4134    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4135      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
4136      <address><email></email></address>
4137    </author>
4138    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4139      <organization abbrev="HP">Hewlett-Packard Company</organization>
4140      <address><email></email></address>
4141    </author>
4142    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
4143      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4144      <address><email></email></address>
4145    </author>
4146    <author initials="L." surname="Masinter" fullname="Larry Masinter">
4147      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4148      <address><email></email></address>
4149    </author>
4150    <author initials="P." surname="Leach" fullname="Paul J. Leach">
4151      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4152      <address><email></email></address>
4153    </author>
4154    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4155      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4156      <address><email></email></address>
4157    </author>
4158    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4159      <organization abbrev="W3C">World Wide Web Consortium</organization>
4160      <address><email></email></address>
4161    </author>
4162    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4163      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4164      <address><email></email></address>
4165    </author>
4166    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4167  </front>
4168  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
4169  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
4172<reference anchor="Part3">
4173  <front>
4174    <title abbrev="HTTP/1.1">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
4175    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4176      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4177      <address><email></email></address>
4178    </author>
4179    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4180      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
4181      <address><email></email></address>
4182    </author>
4183    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4184      <organization abbrev="HP">Hewlett-Packard Company</organization>
4185      <address><email></email></address>
4186    </author>
4187    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
4188      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4189      <address><email></email></address>
4190    </author>
4191    <author initials="L." surname="Masinter" fullname="Larry Masinter">
4192      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4193      <address><email></email></address>
4194    </author>
4195    <author initials="P." surname="Leach" fullname="Paul J. Leach">
4196      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4197      <address><email></email></address>
4198    </author>
4199    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4200      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4201      <address><email></email></address>
4202    </author>
4203    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4204      <organization abbrev="W3C">World Wide Web Consortium</organization>
4205      <address><email></email></address>
4206    </author>
4207    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4208      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4209      <address><email></email></address>
4210    </author>
4211    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4212  </front>
4213  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p3-payload-&ID-VERSION;"/>
4214  <x:source href="p3-payload.xml" basename="p3-payload"/>
4217<reference anchor="Part6">
4218  <front>
4219    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
4220    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
4221      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4222      <address><email></email></address>
4223    </author>
4224    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4225      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
4226      <address><email></email></address>
4227    </author>
4228    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4229      <organization abbrev="HP">Hewlett-Packard Company</organization>
4230      <address><email></email></address>
4231    </author>
4232    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
4233      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4234      <address><email></email></address>
4235    </author>
4236    <author initials="L." surname="Masinter" fullname="Larry Masinter">
4237      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
4238      <address><email></email></address>
4239    </author>
4240    <author initials="P." surname="Leach" fullname="Paul J. Leach">
4241      <organization abbrev="Microsoft">Microsoft Corporation</organization>
4242      <address><email></email></address>
4243    </author>
4244    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4245      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4246      <address><email></email></address>
4247    </author>
4248    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
4249      <organization abbrev="W3C">World Wide Web Consortium</organization>
4250      <address><email></email></address>
4251    </author>
4252    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
4253      <organization>Rackspace</organization>
4254      <address><email></email></address>
4255    </author>
4256    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
4257      <organization abbrev="greenbytes">greenbytes GmbH</organization>
4258      <address><email></email></address>
4259    </author>
4260    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
4261  </front>
4262  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
4263  <x:source href="p6-cache.xml" basename="p6-cache"/>
4266<reference anchor="RFC5234">
4267  <front>
4268    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
4269    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
4270      <organization>Brandenburg InternetWorking</organization>
4271      <address>
4272        <email></email>
4273      </address> 
4274    </author>
4275    <author initials="P." surname="Overell" fullname="Paul Overell">
4276      <organization>THUS plc.</organization>
4277      <address>
4278        <email></email>
4279      </address>
4280    </author>
4281    <date month="January" year="2008"/>
4282  </front>
4283  <seriesInfo name="STD" value="68"/>
4284  <seriesInfo name="RFC" value="5234"/>
4287<reference anchor="RFC2119">
4288  <front>
4289    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
4290    <author initials="S." surname="Bradner" fullname="Scott Bradner">
4291      <organization>Harvard University</organization>
4292      <address><email></email></address>
4293    </author>
4294    <date month="March" year="1997"/>
4295  </front>
4296  <seriesInfo name="BCP" value="14"/>
4297  <seriesInfo name="RFC" value="2119"/>
4300<reference anchor="RFC3986">
4301 <front>
4302  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
4303  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
4304    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
4305    <address>
4306       <email></email>
4307       <uri></uri>
4308    </address>
4309  </author>
4310  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
4311    <organization abbrev="Day Software">Day Software</organization>
4312    <address>
4313      <email></email>
4314      <uri></uri>
4315    </address>
4316  </author>
4317  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
4318    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
4319    <address>
4320      <email></email>
4321      <uri></uri>
4322    </address>
4323  </author>
4324  <date month='January' year='2005'></date>
4325 </front>
4326 <seriesInfo name="STD" value="66"/>
4327 <seriesInfo name="RFC" value="3986"/>
4330<reference anchor="USASCII">
4331  <front>
4332    <title>Coded Character Set -- 7-bit American Standard Code for Information Interchange</title>
4333    <author>
4334      <organization>American National Standards Institute</organization>
4335    </author>
4336    <date year="1986"/>
4337  </front>
4338  <seriesInfo name="ANSI" value="X3.4"/>
4341<reference anchor="RFC1950">
4342  <front>
4343    <title>ZLIB Compressed Data Format Specification version 3.3</title>
4344    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
4345      <organization>Aladdin Enterprises</organization>
4346      <address><email></email></address>
4347    </author>
4348    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly"/>
4349    <date month="May" year="1996"/>
4350  </front>
4351  <seriesInfo name="RFC" value="1950"/>
4352  <!--<annotation>
4353    RFC 1950 is an Informational RFC, thus it might be less stable than
4354    this specification. On the other hand, this downward reference was
4355    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4356    therefore it is unlikely to cause problems in practice. See also
4357    <xref target="BCP97"/>.
4358  </annotation>-->
4361<reference anchor="RFC1951">
4362  <front>
4363    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
4364    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
4365      <organization>Aladdin Enterprises</organization>
4366      <address><email></email></address>
4367    </author>
4368    <date month="May" year="1996"/>
4369  </front>
4370  <seriesInfo name="RFC" value="1951"/>
4371  <!--<annotation>
4372    RFC 1951 is an Informational RFC, thus it might be less stable than
4373    this specification. On the other hand, this downward reference was
4374    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4375    therefore it is unlikely to cause problems in practice. See also
4376    <xref target="BCP97"/>.
4377  </annotation>-->
4380<reference anchor="RFC1952">
4381  <front>
4382    <title>GZIP file format specification version 4.3</title>
4383    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
4384      <organization>Aladdin Enterprises</organization>
4385      <address><email></email></address>
4386    </author>
4387    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
4388      <address><email></email></address>
4389    </author>
4390    <author initials="M." surname="Adler" fullname="Mark Adler">
4391      <address><email></email></address>
4392    </author>
4393    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
4394      <address><email></email></address>
4395    </author>
4396    <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">
4397      <address><email></email></address>
4398    </author>
4399    <date month="May" year="1996"/>
4400  </front>
4401  <seriesInfo name="RFC" value="1952"/>
4402  <!--<annotation>
4403    RFC 1952 is an Informational RFC, thus it might be less stable than
4404    this specification. On the other hand, this downward reference was
4405    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
4406    therefore it is unlikely to cause problems in practice. See also
4407    <xref target="BCP97"/>.
4408  </annotation>-->
4413<references title="Informative References">
4415<reference anchor="Nie1997" target="">
4416  <front>
4417    <title>Network Performance Effects of HTTP/1.1, CSS1, and PNG</title>
4418    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen"/>
4419    <author initials="J." surname="Gettys" fullname="J. Gettys"/>
4420    <author initials="E." surname="Prud'hommeaux" fullname="E. Prud'hommeaux"/>
4421    <author initials="H." surname="Lie" fullname="H. Lie"/>
4422    <author initials="C." surname="Lilley" fullname="C. Lilley"/>
4423    <date year="1997" month="September"/>
4424  </front>
4425  <seriesInfo name="ACM" value="Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication SIGCOMM '97"/>
4428<reference anchor="Pad1995" target="">
4429  <front>
4430    <title>Improving HTTP Latency</title>
4431    <author initials="V.N." surname="Padmanabhan" fullname="Venkata N. Padmanabhan"/>
4432    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul"/>
4433    <date year="1995" month="December"/>
4434  </front>
4435  <seriesInfo name="Computer Networks and ISDN Systems" value="v. 28, pp. 25-35"/>
4438<reference anchor='RFC1919'>
4439  <front>
4440    <title>Classical versus Transparent IP Proxies</title>
4441    <author initials='M.' surname='Chatel' fullname='Marc Chatel'>
4442      <address><email></email></address>
4443    </author>
4444    <date year='1996' month='March' />
4445  </front>
4446  <seriesInfo name='RFC' value='1919' />
4449<reference anchor="RFC1945">
4450  <front>
4451    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
4452    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4453      <organization>MIT, Laboratory for Computer Science</organization>
4454      <address><email></email></address>
4455    </author>
4456    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4457      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4458      <address><email></email></address>
4459    </author>
4460    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4461      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
4462      <address><email></email></address>
4463    </author>
4464    <date month="May" year="1996"/>
4465  </front>
4466  <seriesInfo name="RFC" value="1945"/>
4469<reference anchor="RFC2045">
4470  <front>
4471    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
4472    <author initials="N." surname="Freed" fullname="Ned Freed">
4473      <organization>Innosoft International, Inc.</organization>
4474      <address><email></email></address>
4475    </author>
4476    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
4477      <organization>First Virtual Holdings</organization>
4478      <address><email></email></address>
4479    </author>
4480    <date month="November" year="1996"/>
4481  </front>
4482  <seriesInfo name="RFC" value="2045"/>
4485<reference anchor="RFC2047">
4486  <front>
4487    <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
4488    <author initials="K." surname="Moore" fullname="Keith Moore">
4489      <organization>University of Tennessee</organization>
4490      <address><email></email></address>
4491    </author>
4492    <date month="November" year="1996"/>
4493  </front>
4494  <seriesInfo name="RFC" value="2047"/>
4497<reference anchor="RFC2068">
4498  <front>
4499    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
4500    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
4501      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4502      <address><email></email></address>
4503    </author>
4504    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4505      <organization>MIT Laboratory for Computer Science</organization>
4506      <address><email></email></address>
4507    </author>
4508    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4509      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
4510      <address><email></email></address>
4511    </author>
4512    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4513      <organization>MIT Laboratory for Computer Science</organization>
4514      <address><email></email></address>
4515    </author>
4516    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4517      <organization>MIT Laboratory for Computer Science</organization>
4518      <address><email></email></address>
4519    </author>
4520    <date month="January" year="1997"/>
4521  </front>
4522  <seriesInfo name="RFC" value="2068"/>
4525<reference anchor="RFC2145">
4526  <front>
4527    <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
4528    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
4529      <organization>Western Research Laboratory</organization>
4530      <address><email></email></address>
4531    </author>
4532    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4533      <organization>Department of Information and Computer Science</organization>
4534      <address><email></email></address>
4535    </author>
4536    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4537      <organization>MIT Laboratory for Computer Science</organization>
4538      <address><email></email></address>
4539    </author>
4540    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4541      <organization>W3 Consortium</organization>
4542      <address><email></email></address>
4543    </author>
4544    <date month="May" year="1997"/>
4545  </front>
4546  <seriesInfo name="RFC" value="2145"/>
4549<reference anchor="RFC2616">
4550  <front>
4551    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
4552    <author initials="R." surname="Fielding" fullname="R. Fielding">
4553      <organization>University of California, Irvine</organization>
4554      <address><email></email></address>
4555    </author>
4556    <author initials="J." surname="Gettys" fullname="J. Gettys">
4557      <organization>W3C</organization>
4558      <address><email></email></address>
4559    </author>
4560    <author initials="J." surname="Mogul" fullname="J. Mogul">
4561      <organization>Compaq Computer Corporation</organization>
4562      <address><email></email></address>
4563    </author>
4564    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
4565      <organization>MIT Laboratory for Computer Science</organization>
4566      <address><email></email></address>
4567    </author>
4568    <author initials="L." surname="Masinter" fullname="L. Masinter">
4569      <organization>Xerox Corporation</organization>
4570      <address><email></email></address>
4571    </author>
4572    <author initials="P." surname="Leach" fullname="P. Leach">
4573      <organization>Microsoft Corporation</organization>
4574      <address><email></email></address>
4575    </author>
4576    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
4577      <organization>W3C</organization>
4578      <address><email></email></address>
4579    </author>
4580    <date month="June" year="1999"/>
4581  </front>
4582  <seriesInfo name="RFC" value="2616"/>
4585<reference anchor='RFC2817'>
4586  <front>
4587    <title>Upgrading to TLS Within HTTP/1.1</title>
4588    <author initials='R.' surname='Khare' fullname='R. Khare'>
4589      <organization>4K Associates / UC Irvine</organization>
4590      <address><email></email></address>
4591    </author>
4592    <author initials='S.' surname='Lawrence' fullname='S. Lawrence'>
4593      <organization>Agranat Systems, Inc.</organization>
4594      <address><email></email></address>
4595    </author>
4596    <date year='2000' month='May' />
4597  </front>
4598  <seriesInfo name='RFC' value='2817' />
4601<reference anchor='RFC2818'>
4602  <front>
4603    <title>HTTP Over TLS</title>
4604    <author initials='E.' surname='Rescorla' fullname='Eric Rescorla'>
4605      <organization>RTFM, Inc.</organization>
4606      <address><email></email></address>
4607    </author>
4608    <date year='2000' month='May' />
4609  </front>
4610  <seriesInfo name='RFC' value='2818' />
4613<reference anchor='RFC2965'>
4614  <front>
4615    <title>HTTP State Management Mechanism</title>
4616    <author initials='D. M.' surname='Kristol' fullname='David M. Kristol'>
4617      <organization>Bell Laboratories, Lucent Technologies</organization>
4618      <address><email></email></address>
4619    </author>
4620    <author initials='L.' surname='Montulli' fullname='Lou Montulli'>
4621      <organization>, Inc.</organization>
4622      <address><email></email></address>
4623    </author>
4624    <date year='2000' month='October' />
4625  </front>
4626  <seriesInfo name='RFC' value='2965' />
4629<reference anchor='RFC3040'>
4630  <front>
4631    <title>Internet Web Replication and Caching Taxonomy</title>
4632    <author initials='I.' surname='Cooper' fullname='I. Cooper'>
4633      <organization>Equinix, Inc.</organization>
4634    </author>
4635    <author initials='I.' surname='Melve' fullname='I. Melve'>
4636      <organization>UNINETT</organization>
4637    </author>
4638    <author initials='G.' surname='Tomlinson' fullname='G. Tomlinson'>
4639      <organization>CacheFlow Inc.</organization>
4640    </author>
4641    <date year='2001' month='January' />
4642  </front>
4643  <seriesInfo name='RFC' value='3040' />
4646<reference anchor='RFC3864'>
4647  <front>
4648    <title>Registration Procedures for Message Header Fields</title>
4649    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
4650      <organization>Nine by Nine</organization>
4651      <address><email></email></address>
4652    </author>
4653    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
4654      <organization>BEA Systems</organization>
4655      <address><email></email></address>
4656    </author>
4657    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
4658      <organization>HP Labs</organization>
4659      <address><email></email></address>
4660    </author>
4661    <date year='2004' month='September' />
4662  </front>
4663  <seriesInfo name='BCP' value='90' />
4664  <seriesInfo name='RFC' value='3864' />
4667<reference anchor='RFC4033'>
4668  <front>
4669    <title>DNS Security Introduction and Requirements</title>
4670    <author initials='R.' surname='Arends' fullname='R. Arends'/>
4671    <author initials='R.' surname='Austein' fullname='R. Austein'/>
4672    <author initials='M.' surname='Larson' fullname='M. Larson'/>
4673    <author initials='D.' surname='Massey' fullname='D. Massey'/>
4674    <author initials='S.' surname='Rose' fullname='S. Rose'/>
4675    <date year='2005' month='March' />
4676  </front>
4677  <seriesInfo name='RFC' value='4033' />
4680<reference anchor="RFC4288">
4681  <front>
4682    <title>Media Type Specifications and Registration Procedures</title>
4683    <author initials="N." surname="Freed" fullname="N. Freed">
4684      <organization>Sun Microsystems</organization>
4685      <address>
4686        <email></email>
4687      </address>
4688    </author>
4689    <author initials="J." surname="Klensin" fullname="J. Klensin">
4690      <address>
4691        <email></email>
4692      </address>
4693    </author>
4694    <date year="2005" month="December"/>
4695  </front>
4696  <seriesInfo name="BCP" value="13"/>
4697  <seriesInfo name="RFC" value="4288"/>
4700<reference anchor='RFC4395'>
4701  <front>
4702    <title>Guidelines and Registration Procedures for New URI Schemes</title>
4703    <author initials='T.' surname='Hansen' fullname='T. Hansen'>
4704      <organization>AT&amp;T Laboratories</organization>
4705      <address>
4706        <email></email>
4707      </address>
4708    </author>
4709    <author initials='T.' surname='Hardie' fullname='T. Hardie'>
4710      <organization>Qualcomm, Inc.</organization>
4711      <address>
4712        <email></email>
4713      </address>
4714    </author>
4715    <author initials='L.' surname='Masinter' fullname='L. Masinter'>
4716      <organization>Adobe Systems</organization>
4717      <address>
4718        <email></email>
4719      </address>
4720    </author>
4721    <date year='2006' month='February' />
4722  </front>
4723  <seriesInfo name='BCP' value='115' />
4724  <seriesInfo name='RFC' value='4395' />
4727<reference anchor='RFC4559'>
4728  <front>
4729    <title>SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows</title>
4730    <author initials='K.' surname='Jaganathan' fullname='K. Jaganathan'/>
4731    <author initials='L.' surname='Zhu' fullname='L. Zhu'/>
4732    <author initials='J.' surname='Brezak' fullname='J. Brezak'/>
4733    <date year='2006' month='June' />
4734  </front>
4735  <seriesInfo name='RFC' value='4559' />
4738<reference anchor='RFC5226'>
4739  <front>
4740    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
4741    <author initials='T.' surname='Narten' fullname='T. Narten'>
4742      <organization>IBM</organization>
4743      <address><email></email></address>
4744    </author>
4745    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
4746      <organization>Google</organization>
4747      <address><email></email></address>
4748    </author>
4749    <date year='2008' month='May' />
4750  </front>
4751  <seriesInfo name='BCP' value='26' />
4752  <seriesInfo name='RFC' value='5226' />
4755<reference anchor="RFC5322">
4756  <front>
4757    <title>Internet Message Format</title>
4758    <author initials="P." surname="Resnick" fullname="P. Resnick">
4759      <organization>Qualcomm Incorporated</organization>
4760    </author>
4761    <date year="2008" month="October"/>
4762  </front>
4763  <seriesInfo name="RFC" value="5322"/>
4766<reference anchor="RFC6265">
4767  <front>
4768    <title>HTTP State Management Mechanism</title>
4769    <author initials="A." surname="Barth" fullname="Adam Barth">
4770      <organization abbrev="U.C. Berkeley">
4771        University of California, Berkeley
4772      </organization>
4773      <address><email></email></address>
4774    </author>
4775    <date year="2011" month="April" />
4776  </front>
4777  <seriesInfo name="RFC" value="6265"/>
4780<!--<reference anchor='BCP97'>
4781  <front>
4782    <title>Handling Normative References to Standards-Track Documents</title>
4783    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
4784      <address>
4785        <email></email>
4786      </address>
4787    </author>
4788    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
4789      <organization>MIT</organization>
4790      <address>
4791        <email></email>
4792      </address>
4793    </author>
4794    <date year='2007' month='June' />
4795  </front>
4796  <seriesInfo name='BCP' value='97' />
4797  <seriesInfo name='RFC' value='4897' />
4800<reference anchor="Kri2001" target="">
4801  <front>
4802    <title>HTTP Cookies: Standards, Privacy, and Politics</title>
4803    <author initials="D." surname="Kristol" fullname="David M. Kristol"/>
4804    <date year="2001" month="November"/>
4805  </front>
4806  <seriesInfo name="ACM Transactions on Internet Technology" value="Vol. 1, #2"/>
4809<reference anchor="Spe" target="">
4810  <front>
4811    <title>Analysis of HTTP Performance Problems</title>
4812    <author initials="S." surname="Spero" fullname="Simon E. Spero"/>
4813    <date/>
4814  </front>
4817<reference anchor="Tou1998" target="">
4818  <front>
4819  <title>Analysis of HTTP Performance</title>
4820  <author initials="J." surname="Touch" fullname="Joe Touch">
4821    <organization>USC/Information Sciences Institute</organization>
4822    <address><email></email></address>
4823  </author>
4824  <author initials="J." surname="Heidemann" fullname="John Heidemann">
4825    <organization>USC/Information Sciences Institute</organization>
4826    <address><email></email></address>
4827  </author>
4828  <author initials="K." surname="Obraczka" fullname="Katia Obraczka">
4829    <organization>USC/Information Sciences Institute</organization>
4830    <address><email></email></address>
4831  </author>
4832  <date year="1998" month="Aug"/>
4833  </front>
4834  <seriesInfo name="ISI Research Report" value="ISI/RR-98-463"/>
4835  <annotation>(original report dated Aug. 1996)</annotation>
4841<section title="HTTP Version History" anchor="compatibility">
4843   HTTP has been in use by the World-Wide Web global information initiative
4844   since 1990. The first version of HTTP, later referred to as HTTP/0.9,
4845   was a simple protocol for hypertext data transfer across the Internet
4846   with only a single request method (GET) and no metadata.
4847   HTTP/1.0, as defined by <xref target="RFC1945"/>, added a range of request
4848   methods and MIME-like messaging that could include metadata about the data
4849   transferred and modifiers on the request/response semantics. However,
4850   HTTP/1.0 did not sufficiently take into consideration the effects of
4851   hierarchical proxies, caching, the need for persistent connections, or
4852   name-based virtual hosts. The proliferation of incompletely-implemented
4853   applications calling themselves "HTTP/1.0" further necessitated a
4854   protocol version change in order for two communicating applications
4855   to determine each other's true capabilities.
4858   HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent
4859   requirements that enable reliable implementations, adding only
4860   those new features that will either be safely ignored by an HTTP/1.0
4861   recipient or only sent when communicating with a party advertising
4862   conformance with HTTP/1.1.
4865   It is beyond the scope of a protocol specification to mandate
4866   conformance with previous versions. HTTP/1.1 was deliberately
4867   designed, however, to make supporting previous versions easy.
4868   We would expect a general-purpose HTTP/1.1 server to understand
4869   any valid request in the format of HTTP/1.0 and respond appropriately
4870   with an HTTP/1.1 message that only uses features understood (or
4871   safely ignored) by HTTP/1.0 clients.  Likewise, we would expect
4872   an HTTP/1.1 client to understand any valid HTTP/1.0 response.
4875   Since HTTP/0.9 did not support header fields in a request,
4876   there is no mechanism for it to support name-based virtual
4877   hosts (selection of resource by inspection of the Host header
4878   field).  Any server that implements name-based virtual hosts
4879   ought to disable support for HTTP/0.9.  Most requests that
4880   appear to be HTTP/0.9 are, in fact, badly constructed HTTP/1.x
4881   requests wherein a buggy client failed to properly encode
4882   linear whitespace found in a URI reference and placed in
4883   the request-target.
4886<section title="Changes from HTTP/1.0" anchor="changes.from.1.0">
4888   This section summarizes major differences between versions HTTP/1.0
4889   and HTTP/1.1.
4892<section title="Multi-homed Web Servers" anchor="">
4894   The requirements that clients and servers support the Host header
4895   field (<xref target=""/>), report an error if it is
4896   missing from an HTTP/1.1 request, and accept absolute URIs (<xref target="request-target"/>)
4897   are among the most important changes defined by HTTP/1.1.
4900   Older HTTP/1.0 clients assumed a one-to-one relationship of IP
4901   addresses and servers; there was no other established mechanism for
4902   distinguishing the intended server of a request than the IP address
4903   to which that request was directed. The Host header field was
4904   introduced during the development of HTTP/1.1 and, though it was
4905   quickly implemented by most HTTP/1.0 browsers, additional requirements
4906   were placed on all HTTP/1.1 requests in order to ensure complete
4907   adoption.  At the time of this writing, most HTTP-based services
4908   are dependent upon the Host header field for targeting requests.
4912<section title="Keep-Alive Connections" anchor="compatibility.with.http.1.0.persistent.connections">
4914   In HTTP/1.0, each connection is established by the client prior to the
4915   request and closed by the server after sending the response. However, some
4916   implementations implement the explicitly negotiated ("Keep-Alive") version
4917   of persistent connections described in <xref x:sec="19.7.1" x:fmt="of"
4918   target="RFC2068"/>.
4921   Some clients and servers might wish to be compatible with these previous
4922   approaches to persistent connections, by explicitly negotiating for them
4923   with a "Connection: keep-alive" request header field. However, some
4924   experimental implementations of HTTP/1.0 persistent connections are faulty;
4925   for example, if a HTTP/1.0 proxy server doesn't understand Connection, it
4926   will erroneously forward that header to the next inbound server, which
4927   would result in a hung connection.
4930   One attempted solution was the introduction of a Proxy-Connection header,
4931   targeted specifically at proxies. In practice, this was also unworkable,
4932   because proxies are often deployed in multiple layers, bringing about the
4933   same problem discussed above.
4936   As a result, clients are encouraged not to send the Proxy-Connection header
4937   in any requests.
4940   Clients are also encouraged to consider the use of Connection: keep-alive
4941   in requests carefully; while they can enable persistent connections with
4942   HTTP/1.0 servers, clients using them need will need to monitor the
4943   connection for "hung" requests (which indicate that the client ought stop
4944   sending the header), and this mechanism ought not be used by clients at all
4945   when a proxy is being used.
4950<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
4952  Empty list elements in list productions have been deprecated.
4953  (<xref target="abnf.extension"/>)
4956  Rules about implicit linear whitespace between certain grammar productions
4957  have been removed; now whitespace is only allowed where specifically
4958  defined in the ABNF.
4959  (<xref target="whitespace"/>)
4962  Clarify that the string "HTTP" in the HTTP-Version ABFN production is case
4963  sensitive. Restrict the version numbers to be single digits due to the fact
4964  that implementations are known to handle multi-digit version numbers
4965  incorrectly.
4966  (<xref target="http.version"/>)
4969  Require that invalid whitespace around field-names be rejected.
4970  (<xref target="header.fields"/>)
4973  The NUL octet is no longer allowed in comment and quoted-string
4974  text. The quoted-pair rule no longer allows escaping control characters other than HTAB.
4975  Non-ASCII content in header fields and reason phrase has been obsoleted and
4976  made opaque (the TEXT rule was removed).
4977  (<xref target="field.components"/>)
4980  Require recipients to handle bogus Content-Length header fields as errors.
4981  (<xref target="message.body"/>)
4984  Remove reference to non-existent identity transfer-coding value tokens.
4985  (Sections <xref format="counter" target="message.body"/> and
4986  <xref format="counter" target="transfer.codings"/>)
4989  Update use of abs_path production from RFC 1808 to the path-absolute + query
4990  components of RFC 3986. State that the asterisk form is allowed for the OPTIONS
4991  request method only.
4992  (<xref target="request-target"/>)
4995  Clarification that the chunk length does not include the count of the octets
4996  in the chunk header and trailer. Furthermore disallowed line folding
4997  in chunk extensions.
4998  (<xref target="chunked.encoding"/>)
5001  Remove hard limit of two connections per server.
5002  Remove requirement to retry a sequence of requests as long it was idempotent.
5003  Remove requirements about when servers are allowed to close connections
5004  prematurely.
5005  (<xref target="persistent.practical"/>)
5008  Remove requirement to retry requests under certain cirumstances when the
5009  server prematurely closes the connection.
5010  (<xref target="message.transmission.requirements"/>)
5013  Change ABNF productions for header fields to only define the field value.
5014  (<xref target="header.field.definitions"/>)
5017  Clarify exactly when close connection options must be sent.
5018  (<xref target="header.connection"/>)
5021  Define the semantics of the "Upgrade" header field in responses other than
5022  101 (this was incorporated from <xref target="RFC2817"/>).
5023  (<xref target="header.upgrade"/>)
5028<?BEGININC p1-messaging.abnf-appendix ?>
5029<section xmlns:x="" title="Collected ABNF" anchor="collected.abnf">
5031<artwork type="abnf" name="p1-messaging.parsed-abnf">
5032<x:ref>BWS</x:ref> = OWS
5034<x:ref>Chunked-Body</x:ref> = *chunk last-chunk trailer-part CRLF
5035<x:ref>Connection</x:ref> = *( "," OWS ) connection-token *( OWS "," [ OWS
5036 connection-token ] )
5037<x:ref>Content-Length</x:ref> = 1*DIGIT
5039<x:ref>HTTP-Prot-Name</x:ref> = %x48.54.54.50 ; HTTP
5040<x:ref>HTTP-Version</x:ref> = HTTP-Prot-Name "/" DIGIT "." DIGIT
5041<x:ref>HTTP-message</x:ref> = start-line *( header-field CRLF ) CRLF [ message-body
5042 ]
5043<x:ref>Host</x:ref> = uri-host [ ":" port ]
5045<x:ref>Method</x:ref> = token
5047<x:ref>OWS</x:ref> = *( SP / HTAB / obs-fold )
5049<x:ref>RWS</x:ref> = 1*( SP / HTAB / obs-fold )
5050<x:ref>Reason-Phrase</x:ref> = *( HTAB / SP / VCHAR / obs-text )
5051<x:ref>Request-Line</x:ref> = Method SP request-target SP HTTP-Version CRLF
5053<x:ref>Status-Code</x:ref> = 3DIGIT
5054<x:ref>Status-Line</x:ref> = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
5056<x:ref>TE</x:ref> = [ ( "," / t-codings ) *( OWS "," [ OWS t-codings ] ) ]
5057<x:ref>Trailer</x:ref> = *( "," OWS ) field-name *( OWS "," [ OWS field-name ] )
5058<x:ref>Transfer-Encoding</x:ref> = *( "," OWS ) transfer-coding *( OWS "," [ OWS
5059 transfer-coding ] )
5061<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [RFC3986], Section 4.1&gt;
5062<x:ref>Upgrade</x:ref> = *( "," OWS ) product *( OWS "," [ OWS product ] )
5064<x:ref>Via</x:ref> = *( "," OWS ) received-protocol RWS received-by [ RWS comment ]
5065 *( OWS "," [ OWS received-protocol RWS received-by [ RWS comment ] ]
5066 )
5068<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
5069<x:ref>attribute</x:ref> = token
5070<x:ref>authority</x:ref> = &lt;authority, defined in [RFC3986], Section 3.2&gt;
5072<x:ref>chunk</x:ref> = chunk-size [ chunk-ext ] CRLF chunk-data CRLF
5073<x:ref>chunk-data</x:ref> = 1*OCTET
5074<x:ref>chunk-ext</x:ref> = *( ";" chunk-ext-name [ "=" chunk-ext-val ] )
5075<x:ref>chunk-ext-name</x:ref> = token
5076<x:ref>chunk-ext-val</x:ref> = token / quoted-str-nf
5077<x:ref>chunk-size</x:ref> = 1*HEXDIG
5078<x:ref>comment</x:ref> = "(" *( ctext / quoted-cpair / comment ) ")"
5079<x:ref>connection-token</x:ref> = token
5080<x:ref>ctext</x:ref> = OWS / %x21-27 ; '!'-'''
5081 / %x2A-5B ; '*'-'['
5082 / %x5D-7E ; ']'-'~'
5083 / obs-text
5085<x:ref>field-content</x:ref> = *( HTAB / SP / VCHAR / obs-text )
5086<x:ref>field-name</x:ref> = token
5087<x:ref>field-value</x:ref> = *( field-content / obs-fold )
5089<x:ref>header-field</x:ref> = field-name ":" OWS field-value BWS
5090<x:ref>http-URI</x:ref> = "http://" authority path-abempty [ "?" query ]
5091<x:ref>https-URI</x:ref> = "https://" authority path-abempty [ "?" query ]
5093<x:ref>last-chunk</x:ref> = 1*"0" [ chunk-ext ] CRLF
5095<x:ref>message-body</x:ref> = *OCTET
5097<x:ref>obs-fold</x:ref> = CRLF ( SP / HTAB )
5098<x:ref>obs-text</x:ref> = %x80-FF
5100<x:ref>partial-URI</x:ref> = relative-part [ "?" query ]
5101<x:ref>path-abempty</x:ref> = &lt;path-abempty, defined in [RFC3986], Section 3.3&gt;
5102<x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in [RFC3986], Section 3.3&gt;
5103<x:ref>port</x:ref> = &lt;port, defined in [RFC3986], Section 3.2.3&gt;
5104<x:ref>product</x:ref> = token [ "/" product-version ]
5105<x:ref>product-version</x:ref> = token
5106<x:ref>protocol-name</x:ref> = token
5107<x:ref>protocol-version</x:ref> = token
5108<x:ref>pseudonym</x:ref> = token
5110<x:ref>qdtext</x:ref> = OWS / "!" / %x23-5B ; '#'-'['
5111 / %x5D-7E ; ']'-'~'
5112 / obs-text
5113<x:ref>qdtext-nf</x:ref> = HTAB / SP / "!" / %x23-5B ; '#'-'['
5114 / %x5D-7E ; ']'-'~'
5115 / obs-text
5116<x:ref>query</x:ref> = &lt;query, defined in [RFC3986], Section 3.4&gt;
5117<x:ref>quoted-cpair</x:ref> = "\" ( HTAB / SP / VCHAR / obs-text )
5118<x:ref>quoted-pair</x:ref> = "\" ( HTAB / SP / VCHAR / obs-text )
5119<x:ref>quoted-str-nf</x:ref> = DQUOTE *( qdtext-nf / quoted-pair ) DQUOTE
5120<x:ref>quoted-string</x:ref> = DQUOTE *( qdtext / quoted-pair ) DQUOTE
5121<x:ref>qvalue</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
5123<x:ref>received-by</x:ref> = ( uri-host [ ":" port ] ) / pseudonym
5124<x:ref>received-protocol</x:ref> = [ protocol-name "/" ] protocol-version
5125<x:ref>relative-part</x:ref> = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;
5126<x:ref>request-target</x:ref> = "*" / absolute-URI / ( path-absolute [ "?" query ] )
5127 / authority
5129<x:ref>special</x:ref> = "(" / ")" / "&lt;" / "&gt;" / "@" / "," / ";" / ":" / "\" /
5130 DQUOTE / "/" / "[" / "]" / "?" / "=" / "{" / "}"
5131<x:ref>start-line</x:ref> = Request-Line / Status-Line
5133<x:ref>t-codings</x:ref> = "trailers" / ( transfer-extension [ te-params ] )
5134<x:ref>tchar</x:ref> = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*" / "+" / "-" / "." /
5135 "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
5136<x:ref>te-ext</x:ref> = OWS ";" OWS token [ "=" word ]
5137<x:ref>te-params</x:ref> = OWS ";" OWS "q=" qvalue *te-ext
5138<x:ref>token</x:ref> = 1*tchar
5139<x:ref>trailer-part</x:ref> = *( header-field CRLF )
5140<x:ref>transfer-coding</x:ref> = "chunked" / "compress" / "deflate" / "gzip" /
5141 transfer-extension
5142<x:ref>transfer-extension</x:ref> = token *( OWS ";" OWS transfer-parameter )
5143<x:ref>transfer-parameter</x:ref> = attribute BWS "=" BWS value
5145<x:ref>uri-host</x:ref> = &lt;host, defined in [RFC3986], Section 3.2.2&gt;
5147<x:ref>value</x:ref> = word
5149<x:ref>word</x:ref> = token / quoted-string
5152<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
5153; Chunked-Body defined but not used
5154; Connection defined but not used
5155; Content-Length defined but not used
5156; HTTP-message defined but not used
5157; Host defined but not used
5158; TE defined but not used
5159; Trailer defined but not used
5160; Transfer-Encoding defined but not used
5161; URI-reference defined but not used
5162; Upgrade defined but not used
5163; Via defined but not used
5164; http-URI defined but not used
5165; https-URI defined but not used
5166; partial-URI defined but not used
5167; special defined but not used
5169<?ENDINC p1-messaging.abnf-appendix ?>
5171<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
5173<section title="Since RFC 2616">
5175  Extracted relevant partitions from <xref target="RFC2616"/>.
5179<section title="Since draft-ietf-httpbis-p1-messaging-00">
5181  Closed issues:
5182  <list style="symbols">
5183    <t>
5184      <eref target=""/>:
5185      "HTTP Version should be case sensitive"
5186      (<eref target=""/>)
5187    </t>
5188    <t>
5189      <eref target=""/>:
5190      "'unsafe' characters"
5191      (<eref target=""/>)
5192    </t>
5193    <t>
5194      <eref target=""/>:
5195      "Chunk Size Definition"
5196      (<eref target=""/>)
5197    </t>
5198    <t>
5199      <eref target=""/>:
5200      "Message Length"
5201      (<eref target=""/>)
5202    </t>
5203    <t>
5204      <eref target=""/>:
5205      "Media Type Registrations"
5206      (<eref target=""/>)
5207    </t>
5208    <t>
5209      <eref target=""/>:
5210      "URI includes query"
5211      (<eref target=""/>)
5212    </t>
5213    <t>
5214      <eref target=""/>:
5215      "No close on 1xx responses"
5216      (<eref target=""/>)
5217    </t>
5218    <t>
5219      <eref target=""/>:
5220      "Remove 'identity' token references"
5221      (<eref target=""/>)
5222    </t>
5223    <t>
5224      <eref target=""/>:
5225      "Import query BNF"
5226    </t>
5227    <t>
5228      <eref target=""/>:
5229      "qdtext BNF"
5230    </t>
5231    <t>
5232      <eref target=""/>:
5233      "Normative and Informative references"
5234    </t>
5235    <t>
5236      <eref target=""/>:
5237      "RFC2606 Compliance"
5238    </t>
5239    <t>
5240      <eref target=""/>:
5241      "RFC977 reference"
5242    </t>
5243    <t>
5244      <eref target=""/>:
5245      "RFC1700 references"
5246    </t>
5247    <t>
5248      <eref target=""/>:
5249      "inconsistency in date format explanation"
5250    </t>
5251    <t>
5252      <eref target=""/>:
5253      "Date reference typo"
5254    </t>
5255    <t>
5256      <eref target=""/>:
5257      "Informative references"
5258    </t>
5259    <t>
5260      <eref target=""/>:
5261      "ISO-8859-1 Reference"
5262    </t>
5263    <t>
5264      <eref target=""/>:
5265      "Normative up-to-date references"
5266    </t>
5267  </list>
5270  Other changes:
5271  <list style="symbols">
5272    <t>
5273      Update media type registrations to use RFC4288 template.
5274    </t>
5275    <t>
5276      Use names of RFC4234 core rules DQUOTE and HTAB,
5277      fix broken ABNF for chunk-data
5278      (work in progress on <eref target=""/>)
5279    </t>
5280  </list>
5284<section title="Since draft-ietf-httpbis-p1-messaging-01">
5286  Closed issues:
5287  <list style="symbols">
5288    <t>
5289      <eref target=""/>:
5290      "Bodies on GET (and other) requests"
5291    </t>
5292    <t>
5293      <eref target=""/>:
5294      "Updating to RFC4288"
5295    </t>
5296    <t>
5297      <eref target=""/>:
5298      "Status Code and Reason Phrase"
5299    </t>
5300    <t>
5301      <eref target=""/>:
5302      "rel_path not used"
5303    </t>
5304  </list>
5307  Ongoing work on ABNF conversion (<eref target=""/>):
5308  <list style="symbols">
5309    <t>
5310      Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" ->
5311      "trailer-part").
5312    </t>
5313    <t>
5314      Avoid underscore character in rule names ("http_URL" ->
5315      "http-URL", "abs_path" -> "path-absolute").
5316    </t>
5317    <t>
5318      Add rules for terms imported from URI spec ("absoluteURI", "authority",
5319      "path-absolute", "port", "query", "relativeURI", "host) &mdash; these will
5320      have to be updated when switching over to RFC3986.
5321    </t>
5322    <t>
5323      Synchronize core rules with RFC5234.
5324    </t>
5325    <t>
5326      Get rid of prose rules that span multiple lines.
5327    </t>
5328    <t>
5329      Get rid of unused rules LOALPHA and UPALPHA.
5330    </t>
5331    <t>
5332      Move "Product Tokens" section (back) into Part 1, as "token" is used
5333      in the definition of the Upgrade header field.
5334    </t>
5335    <t>
5336      Add explicit references to BNF syntax and rules imported from other parts of the specification.
5337    </t>
5338    <t>
5339      Rewrite prose rule "token" in terms of "tchar", rewrite prose rule "TEXT".
5340    </t>
5341  </list>
5345<section title="Since draft-ietf-httpbis-p1-messaging-02" anchor="changes.since.02">
5347  Closed issues:
5348  <list style="symbols">
5349    <t>
5350      <eref target=""/>:
5351      "HTTP-date vs. rfc1123-date"
5352    </t>
5353    <t>
5354      <eref target=""/>:
5355      "WS in quoted-pair"
5356    </t>
5357  </list>
5360  Ongoing work on IANA Message Header Field Registration (<eref target=""/>):
5361  <list style="symbols">
5362    <t>
5363      Reference RFC 3984, and update header field registrations for headers defined
5364      in this document.
5365    </t>
5366  </list>
5369  Ongoing work on ABNF conversion (<eref target=""/>):
5370  <list style="symbols">
5371    <t>
5372      Replace string literals when the string really is case-sensitive (HTTP-Version).
5373    </t>
5374  </list>
5378<section title="Since draft-ietf-httpbis-p1-messaging-03" anchor="changes.since.03">
5380  Closed issues:
5381  <list style="symbols">
5382    <t>
5383      <eref target=""/>:
5384      "Connection closing"
5385    </t>
5386    <t>
5387      <eref target=""/>:
5388      "Move registrations and registry information to IANA Considerations"
5389    </t>
5390    <t>
5391      <eref target=""/>:
5392      "need new URL for PAD1995 reference"
5393    </t>
5394    <t>
5395      <eref target=""/>:
5396      "IANA Considerations: update HTTP URI scheme registration"
5397    </t>
5398    <t>
5399      <eref target=""/>:
5400      "Cite HTTPS URI scheme definition"
5401    </t>
5402    <t>
5403      <eref target=""/>:
5404      "List-type headers vs Set-Cookie"
5405    </t>
5406  </list>
5409  Ongoing work on ABNF conversion (<eref target=""/>):
5410  <list style="symbols">
5411    <t>
5412      Replace string literals when the string really is case-sensitive (HTTP-Date).
5413    </t>
5414    <t>
5415      Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.
5416    </t>
5417  </list>
5421<section title="Since draft-ietf-httpbis-p1-messaging-04" anchor="changes.since.04">
5423  Closed issues:
5424  <list style="symbols">
5425    <t>
5426      <eref target=""/>:
5427      "Out-of-date reference for URIs"
5428    </t>
5429    <t>
5430      <eref target=""/>:
5431      "RFC 2822 is updated by RFC 5322"
5432    </t>
5433  </list>
5436  Ongoing work on ABNF conversion (<eref target=""/>):
5437  <list style="symbols">
5438    <t>
5439      Use "/" instead of "|" for alternatives.
5440    </t>
5441    <t>
5442      Get rid of RFC822 dependency; use RFC5234 plus extensions instead.
5443    </t>
5444    <t>
5445      Only reference RFC 5234's core rules.
5446    </t>
5447    <t>
5448      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
5449      whitespace ("OWS") and required whitespace ("RWS").
5450    </t>
5451    <t>
5452      Rewrite ABNFs to spell out whitespace rules, factor out
5453      header field value format definitions.
5454    </t>
5455  </list>
5459<section title="Since draft-ietf-httpbis-p1-messaging-05" anchor="changes.since.05">
5461  Closed issues:
5462  <list style="symbols">
5463    <t>
5464      <eref target=""/>:
5465      "Header LWS"
5466    </t>
5467    <t>
5468      <eref target=""/>:
5469      "Sort 1.3 Terminology"
5470    </t>
5471    <t>
5472      <eref target=""/>:
5473      "RFC2047 encoded words"
5474    </t>
5475    <t>
5476      <eref target=""/>:
5477      "Character Encodings in TEXT"
5478    </t>
5479    <t>
5480      <eref target=""/>:
5481      "Line Folding"
5482    </t>
5483    <t>
5484      <eref target=""/>:
5485      "OPTIONS * and proxies"
5486    </t>
5487    <t>
5488      <eref target=""/>:
5489      "Reason-Phrase BNF"
5490    </t>
5491    <t>
5492      <eref target=""/>:
5493      "Use of TEXT"
5494    </t>
5495    <t>
5496      <eref target=""/>:
5497      "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
5498    </t>
5499    <t>
5500      <eref target=""/>:
5501      "RFC822 reference left in discussion of date formats"
5502    </t>
5503  </list>
5506  Final work on ABNF conversion (<eref target=""/>):
5507  <list style="symbols">
5508    <t>
5509      Rewrite definition of list rules, deprecate empty list elements.
5510    </t>
5511    <t>
5512      Add appendix containing collected and expanded ABNF.
5513    </t>
5514  </list>
5517  Other changes:
5518  <list style="symbols">
5519    <t>
5520      Rewrite introduction; add mostly new Architecture Section.
5521    </t>
5522    <t>
5523      Move definition of quality values from Part 3 into Part 1;
5524      make TE request header field grammar independent of accept-params (defined in Part 3).
5525    </t>
5526  </list>
5530<section title="Since draft-ietf-httpbis-p1-messaging-06" anchor="changes.since.06">
5532  Closed issues:
5533  <list style="symbols">
5534    <t>
5535      <eref target=""/>:
5536      "base for numeric protocol elements"
5537    </t>
5538    <t>
5539      <eref target=""/>:
5540      "comment ABNF"
5541    </t>
5542  </list>
5545  Partly resolved issues:
5546  <list style="symbols">
5547    <t>
5548      <eref target=""/>:
5549      "205 Bodies" (took out language that implied that there might be
5550      methods for which a request body MUST NOT be included)
5551    </t>
5552    <t>
5553      <eref target=""/>:
5554      "editorial improvements around HTTP-date"
5555    </t>
5556  </list>
5560<section title="Since draft-ietf-httpbis-p1-messaging-07" anchor="changes.since.07">
5562  Closed issues:
5563  <list style="symbols">
5564    <t>
5565      <eref target=""/>:
5566      "Repeating single-value headers"
5567    </t>
5568    <t>
5569      <eref target=""/>:
5570      "increase connection limit"
5571    </t>
5572    <t>
5573      <eref target=""/>:
5574      "IP addresses in URLs"
5575    </t>
5576    <t>
5577      <eref target=""/>:
5578      "take over HTTP Upgrade Token Registry"
5579    </t>
5580    <t>
5581      <eref target=""/>:
5582      "CR and LF in chunk extension values"
5583    </t>
5584    <t>
5585      <eref target=""/>:
5586      "HTTP/0.9 support"
5587    </t>
5588    <t>
5589      <eref target=""/>:
5590      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
5591    </t>
5592    <t>
5593      <eref target=""/>:
5594      "move definitions of gzip/deflate/compress to part 1"
5595    </t>
5596    <t>
5597      <eref target=""/>:
5598      "disallow control characters in quoted-pair"
5599    </t>
5600  </list>
5603  Partly resolved issues:
5604  <list style="symbols">
5605    <t>
5606      <eref target=""/>:
5607      "update IANA requirements wrt Transfer-Coding values" (add the
5608      IANA Considerations subsection)
5609    </t>
5610  </list>
5614<section title="Since draft-ietf-httpbis-p1-messaging-08" anchor="changes.since.08">
5616  Closed issues:
5617  <list style="symbols">
5618    <t>
5619      <eref target=""/>:
5620      "header parsing, treatment of leading and trailing OWS"
5621    </t>
5622  </list>
5625  Partly resolved issues:
5626  <list style="symbols">
5627    <t>
5628      <eref target=""/>:
5629      "Placement of 13.5.1 and 13.5.2"
5630    </t>
5631    <t>
5632      <eref target=""/>:
5633      "use of term "word" when talking about header structure"
5634    </t>
5635  </list>
5639<section title="Since draft-ietf-httpbis-p1-messaging-09" anchor="changes.since.09">
5641  Closed issues:
5642  <list style="symbols">
5643    <t>
5644      <eref target=""/>:
5645      "Clarification of the term 'deflate'"
5646    </t>
5647    <t>
5648      <eref target=""/>:
5649      "OPTIONS * and proxies"
5650    </t>
5651    <t>
5652      <eref target=""/>:
5653      "MIME-Version not listed in P1, general header fields"
5654    </t>
5655    <t>
5656      <eref target=""/>:
5657      "IANA registry for content/transfer encodings"
5658    </t>
5659    <t>
5660      <eref target=""/>:
5661      "Case-sensitivity of HTTP-date"
5662    </t>
5663    <t>
5664      <eref target=""/>:
5665      "use of term "word" when talking about header structure"
5666    </t>
5667  </list>
5670  Partly resolved issues:
5671  <list style="symbols">
5672    <t>
5673      <eref target=""/>:
5674      "Term for the requested resource's URI"
5675    </t>
5676  </list>
5680<section title="Since draft-ietf-httpbis-p1-messaging-10" anchor="changes.since.10">
5682  Closed issues:
5683  <list style="symbols">
5684    <t>
5685      <eref target=""/>:
5686      "Connection Closing"
5687    </t>
5688    <t>
5689      <eref target=""/>:
5690      "Delimiting messages with multipart/byteranges"
5691    </t>
5692    <t>
5693      <eref target=""/>:
5694      "Handling multiple Content-Length headers"
5695    </t>
5696    <t>
5697      <eref target=""/>:
5698      "Clarify entity / representation / variant terminology"
5699    </t>
5700    <t>
5701      <eref target=""/>:
5702      "consider removing the 'changes from 2068' sections"
5703    </t>
5704  </list>
5707  Partly resolved issues:
5708  <list style="symbols">
5709    <t>
5710      <eref target=""/>:
5711      "HTTP(s) URI scheme definitions"
5712    </t>
5713  </list>
5717<section title="Since draft-ietf-httpbis-p1-messaging-11" anchor="changes.since.11">
5719  Closed issues:
5720  <list style="symbols">
5721    <t>
5722      <eref target=""/>:
5723      "Trailer requirements"
5724    </t>
5725    <t>
5726      <eref target=""/>:
5727      "Text about clock requirement for caches belongs in p6"
5728    </t>
5729    <t>
5730      <eref target=""/>:
5731      "effective request URI: handling of missing host in HTTP/1.0"
5732    </t>
5733    <t>
5734      <eref target=""/>:
5735      "confusing Date requirements for clients"
5736    </t>
5737  </list>
5740  Partly resolved issues:
5741  <list style="symbols">
5742    <t>
5743      <eref target=""/>:
5744      "Handling multiple Content-Length headers"
5745    </t>
5746  </list>
5750<section title="Since draft-ietf-httpbis-p1-messaging-12" anchor="changes.since.12">
5752  Closed issues:
5753  <list style="symbols">
5754    <t>
5755      <eref target=""/>:
5756      "RFC2145 Normative"
5757    </t>
5758    <t>
5759      <eref target=""/>:
5760      "HTTP(s) URI scheme definitions" (tune the requirements on userinfo)
5761    </t>
5762    <t>
5763      <eref target=""/>:
5764      "define 'transparent' proxy"
5765    </t>
5766    <t>
5767      <eref target=""/>:
5768      "Header Classification"
5769    </t>
5770    <t>
5771      <eref target=""/>:
5772      "Is * usable as a request-uri for new methods?"
5773    </t>
5774    <t>
5775      <eref target=""/>:
5776      "Migrate Upgrade details from RFC2817"
5777    </t>
5778    <t>
5779      <eref target=""/>:
5780      "untangle ABNFs for header fields"
5781    </t>
5782    <t>
5783      <eref target=""/>:
5784      "update RFC 2109 reference"
5785    </t>
5786  </list>
5790<section title="Since draft-ietf-httpbis-p1-messaging-13" anchor="changes.since.13">
5792  Closed issues:
5793  <list style="symbols">
5794    <t>
5795      <eref target=""/>:
5796      "Allow is not in 13.5.2"
5797    </t>
5798    <t>
5799      <eref target=""/>:
5800      "Handling multiple Content-Length headers"
5801    </t>
5802    <t>
5803      <eref target=""/>:
5804      "untangle ABNFs for header fields"
5805    </t>
5806    <t>
5807      <eref target=""/>:
5808      "Content-Length ABNF broken"
5809    </t>
5810  </list>
5814<section title="Since draft-ietf-httpbis-p1-messaging-14" anchor="changes.since.14">
5816  Closed issues:
5817  <list style="symbols">
5818    <t>
5819      <eref target=""/>:
5820      "HTTP-Version should be redefined as fixed length pair of DIGIT . DIGIT"
5821    </t>
5822    <t>
5823      <eref target=""/>:
5824      "Recommend minimum sizes for protocol elements"
5825    </t>
5826    <t>
5827      <eref target=""/>:
5828      "Set expectations around buffering"
5829    </t>
5830    <t>
5831      <eref target=""/>:
5832      "Considering messages in isolation"
5833    </t>
5834  </list>
5838<section title="Since draft-ietf-httpbis-p1-messaging-15" anchor="changes.since.15">
5840  Closed issues:
5841  <list style="symbols">
5842    <t>
5843      <eref target=""/>:
5844      "DNS Spoofing / DNS Binding advice"
5845    </t>
5846    <t>
5847      <eref target=""/>:
5848      "move RFCs 2145, 2616, 2817 to Historic status"
5849    </t>
5850    <t>
5851      <eref target=""/>:
5852      "\-escaping in quoted strings"
5853    </t>
5854    <t>
5855      <eref target=""/>:
5856      "'Close' should be reserved in the HTTP header field registry"
5857    </t>
5858  </list>
5862<section title="Since draft-ietf-httpbis-p1-messaging-16" anchor="changes.since.16">
5864  Closed issues:
5865  <list style="symbols">
5866    <t>
5867      <eref target=""/>:
5868      "Document HTTP's error-handling philosophy"
5869    </t>
5870    <t>
5871      <eref target=""/>:
5872      "Explain header registration"
5873    </t>
5874    <t>
5875      <eref target=""/>:
5876      "Revise Acknowledgements Sections"
5877    </t>
5878    <t>
5879      <eref target=""/>:
5880      "Retrying Requests"
5881    </t>
5882    <t>
5883      <eref target=""/>:
5884      "Closing the connection on server error"
5885    </t>
5886  </list>
5890<section title="Since draft-ietf-httpbis-p1-messaging-17" anchor="changes.since.17">
5892  Closed issues:
5893  <list style="symbols">
5894    <t>
5895      <eref target=""/>:
5896      "Clarify 'User Agent'"
5897    </t>
5898    <t>
5899      <eref target=""/>:
5900      "Define non-final responses"
5901    </t>
5902    <t>
5903      <eref target=""/>:
5904      "intended maturity level vs normative references"
5905    </t>
5906    <t>
5907      <eref target=""/>:
5908      "Intermediary rewriting of queries"
5909    </t>
5910    <t>
5911      <eref target=""/>:
5912      "Proxy-Connection and Keep-Alive"
5913    </t>
5914  </list>
5918<section title="Since draft-ietf-httpbis-p1-messaging-18" anchor="changes.since.18">
5920  Closed issues:
5921  <list style="symbols">
5922    <t>
5923      <eref target=""/>:
5924      "Misplaced text on connection handling in p2"
5925    </t>
5926  </list>
Note: See TracBrowser for help on using the repository browser.