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

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

Work on referencing ABNF rules adopted from other parts (done for P2 and P3); relates to #36.

  • Property svn:eol-style set to native
File size: 181.0 KB
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
14  <!ENTITY ID-VERSION "latest">
15  <!ENTITY ID-MONTH "February">
16  <!ENTITY ID-YEAR "2008">
17  <!ENTITY caching                "<xref target='Part6' x:rel='#caching' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
18  <!ENTITY payload                "<xref target='Part3' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
19  <!ENTITY media-types            "<xref target='Part3' x:rel='#media.types' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY content-codings        "<xref target='Part3' x:rel='#content.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY CONNECT                "<xref target='Part2' x:rel='#CONNECT' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY content.negotiation    "<xref target='Part3' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY diff2045entity         "<xref target='Part3' x:rel='#differences.between.http.entities.and.rfc.2045.entities' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
24  <!ENTITY entity                 "<xref target='Part3' x:rel='#entity' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
25  <!ENTITY entity-header-fields   "<xref target='Part3' x:rel='#entity.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26  <!ENTITY header-cache-control   "<xref target='Part6' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
27  <!ENTITY header-expect          "<xref target='Part2' x:rel='#header.expect' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
28  <!ENTITY header-pragma          "<xref target='Part6' x:rel='#header.pragma' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
29  <!ENTITY header-warning         "<xref target='Part6' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
30  <!ENTITY idempotent-methods     "<xref target='Part2' x:rel='#idempotent.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
31  <!ENTITY qvalue                 "<xref target='Part3' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
32  <!ENTITY request-header-fields  "<xref target='Part2' x:rel='#request.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
33  <!ENTITY response-header-fields "<xref target='Part2' x:rel='#response.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
34  <!ENTITY method                 "<xref target='Part2' x:rel='#method' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
35  <!ENTITY status-codes           "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
36  <!ENTITY status-100             "<xref target='Part2' x:rel='#status.100' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
37  <!ENTITY status-1xx             "<xref target='Part2' x:rel='#status.1xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
38  <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
39]>
40<?rfc toc="yes" ?>
41<?rfc symrefs="yes" ?>
42<?rfc sortrefs="yes" ?>
43<?rfc compact="yes"?>
44<?rfc subcompact="no" ?>
45<?rfc linkmailto="no" ?>
46<?rfc editing="no" ?>
47<?rfc comments="yes"?>
48<?rfc inline="yes"?>
49<?rfc-ext allow-markup-in-artwork="yes" ?>
50<?rfc-ext include-references-in-index="yes" ?>
51<rfc obsoletes="2616" category="std"
52     ipr="full3978" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"
53     xmlns:x='http://purl.org/net/xml2rfc/ext'>
54<front>
55
56  <title abbrev="HTTP/1.1, Part 1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
57
58  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
59    <organization abbrev="Day Software">Day Software</organization>
60    <address>
61      <postal>
62        <street>23 Corporate Plaza DR, Suite 280</street>
63        <city>Newport Beach</city>
64        <region>CA</region>
65        <code>92660</code>
66        <country>USA</country>
67      </postal>
68      <phone>+1-949-706-5300</phone>
69      <facsimile>+1-949-706-5305</facsimile>
70      <email>fielding@gbiv.com</email>
71      <uri>http://roy.gbiv.com/</uri>
72    </address>
73  </author>
74
75  <author initials="J." surname="Gettys" fullname="Jim Gettys">
76    <organization>One Laptop per Child</organization>
77    <address>
78      <postal>
79        <street>21 Oak Knoll Road</street>
80        <city>Carlisle</city>
81        <region>MA</region>
82        <code>01741</code>
83        <country>USA</country>
84      </postal>
85      <email>jg@laptop.org</email>
86      <uri>http://www.laptop.org/</uri>
87    </address>
88  </author>
89 
90  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
91    <organization abbrev="HP">Hewlett-Packard Company</organization>
92    <address>
93      <postal>
94        <street>HP Labs, Large Scale Systems Group</street>
95        <street>1501 Page Mill Road, MS 1177</street>
96        <city>Palo Alto</city>
97        <region>CA</region>
98        <code>94304</code>
99        <country>USA</country>
100      </postal>
101      <email>JeffMogul@acm.org</email>
102    </address>
103  </author>
104
105  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
106    <organization abbrev="Microsoft">Microsoft Corporation</organization>
107    <address>
108      <postal>
109        <street>1 Microsoft Way</street>
110        <city>Redmond</city>
111        <region>WA</region>
112        <code>98052</code>
113        <country>USA</country>
114      </postal>
115      <email>henrikn@microsoft.com</email>
116    </address>
117  </author>
118
119  <author initials="L." surname="Masinter" fullname="Larry Masinter">
120    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
121    <address>
122      <postal>
123        <street>345 Park Ave</street>
124        <city>San Jose</city>
125        <region>CA</region>
126        <code>95110</code>
127        <country>USA</country>
128      </postal>
129      <email>LMM@acm.org</email>
130      <uri>http://larry.masinter.net/</uri>
131    </address>
132  </author>
133 
134  <author initials="P." surname="Leach" fullname="Paul J. Leach">
135    <organization abbrev="Microsoft">Microsoft Corporation</organization>
136    <address>
137      <postal>
138        <street>1 Microsoft Way</street>
139        <city>Redmond</city>
140        <region>WA</region>
141        <code>98052</code>
142      </postal>
143      <email>paulle@microsoft.com</email>
144    </address>
145  </author>
146   
147  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
148    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
149    <address>
150      <postal>
151        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
152        <street>The Stata Center, Building 32</street>
153        <street>32 Vassar Street</street>
154        <city>Cambridge</city>
155        <region>MA</region>
156        <code>02139</code>
157        <country>USA</country>
158      </postal>
159      <email>timbl@w3.org</email>
160      <uri>http://www.w3.org/People/Berners-Lee/</uri>
161    </address>
162  </author>
163
164  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
165    <organization abbrev="W3C">World Wide Web Consortium</organization>
166    <address>
167      <postal>
168        <street>W3C / ERCIM</street>
169        <street>2004, rte des Lucioles</street>
170        <city>Sophia-Antipolis</city>
171        <region>AM</region>
172        <code>06902</code>
173        <country>France</country>
174      </postal>
175      <email>ylafon@w3.org</email>
176      <uri>http://www.raubacapeu.net/people/yves/</uri>
177    </address>
178  </author>
179
180  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
181    <organization abbrev="greenbytes">greenbytes GmbH</organization>
182    <address>
183      <postal>
184        <street>Hafenweg 16</street>
185        <city>Muenster</city><region>NW</region><code>48155</code>
186        <country>Germany</country>
187      </postal>
188      <phone>+49 251 2807760</phone>   
189      <facsimile>+49 251 2807761</facsimile>   
190      <email>julian.reschke@greenbytes.de</email>       
191      <uri>http://greenbytes.de/tech/webdav/</uri>     
192    </address>
193  </author>
194
195  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
196
197<abstract>
198<t>
199   The Hypertext Transfer Protocol (HTTP) is an application-level
200   protocol for distributed, collaborative, hypermedia information
201   systems. HTTP has been in use by the World Wide Web global information
202   initiative since 1990. This document is Part 1 of the seven-part specification
203   that defines the protocol referred to as "HTTP/1.1" and, taken together,
204   obsoletes RFC 2616.  Part 1 provides an overview of HTTP and
205   its associated terminology, defines the "http" and "https" Uniform
206   Resource Identifier (URI) schemes, defines the generic message syntax
207   and parsing requirements for HTTP message frames, and describes
208   general security concerns for implementations.
209</t>
210</abstract>
211
212<note title="Editorial Note (To be removed by RFC Editor)">
213  <t>
214    Discussion of this draft should take place on the HTTPBIS working group
215    mailing list (ietf-http-wg@w3.org). The current issues list is
216    at <eref target="http://www.tools.ietf.org/wg/httpbis/trac/report/11"/>
217    and related documents (including fancy diffs) can be found at
218    <eref target="http://www.tools.ietf.org/wg/httpbis/"/>.
219  </t>
220  <t>
221    This draft incorporates those issue resolutions that were either
222    collected in the original RFC2616 errata list (<eref target="http://purl.org/NET/http-errata"/>),
223    or which were agreed upon on the mailing list between October 2006 and
224    November 2007 (as published in "draft-lafon-rfc2616bis-03").
225  </t>
226</note>
227</front>
228<middle>
229<section title="Introduction" anchor="introduction">
230<t>
231   The Hypertext Transfer Protocol (HTTP) is an application-level
232   protocol for distributed, collaborative, hypermedia information
233   systems. HTTP has been in use by the World-Wide Web global
234   information initiative since 1990. The first version of HTTP, commonly
235   referred to as HTTP/0.9, was a simple protocol for raw data transfer
236   across the Internet with only a single method and no metadata.
237   HTTP/1.0, as defined by <xref target="RFC1945"/>, improved
238   the protocol by allowing messages to be in the format of MIME-like
239   messages, containing metadata about the data transferred and
240   modifiers on the request/response semantics. However, HTTP/1.0 did
241   not sufficiently take into consideration the effects of hierarchical
242   proxies, caching, the need for persistent connections, or name-based
243   virtual hosts. In addition, the proliferation of incompletely-implemented
244   applications calling themselves "HTTP/1.0" necessitated a
245   protocol version change in order for two communicating applications
246   to determine each other's true capabilities.
247</t>
248<t>
249   This document is Part 1 of the seven-part specification that defines
250   the protocol referred to as "HTTP/1.1", obsoleting <xref target="RFC2616"/>.
251   HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent
252   requirements that enable reliable implementations and adding only
253   those new features that will either be safely ignored by an HTTP/1.0
254   recipient or only sent when communicating with a party advertising
255   compliance with HTTP/1.1.
256   Part 1 defines those aspects of HTTP/1.1 related to overall network
257   operation, message framing, interaction with transport protocols, and
258   URI schemes.
259</t>
260<t>
261   This document is currently disorganized in order to minimize the changes
262   between drafts and enable reviewers to see the smaller errata changes.
263   The next draft will reorganize the sections to better reflect the content.
264   In particular, the sections will be organized according to the typical
265   process of deciding when to use HTTP (URI schemes), overall network operation,
266   connection management, message framing, and generic message parsing.
267   The current mess reflects how widely dispersed these topics and associated
268   requirements had become in <xref target="RFC2616"/>.
269</t>
270
271<section title="Purpose" anchor="intro.purpose">
272<t>
273   Practical information systems require more functionality than simple
274   retrieval, including search, front-end update, and annotation. HTTP
275   allows an open-ended set of methods and headers that indicate the
276   purpose of a request <xref target="RFC2324"/>. It builds on the discipline of reference
277   provided by the Uniform Resource Identifier (URI) <xref target="RFC1630"/>, as a location
278   (URL) <xref target="RFC1738"/> or name (URN) <xref target="RFC1737"/>, for indicating the resource to which a
279   method is to be applied. Messages are passed in a format similar to
280   that used by Internet mail <xref target="RFC2822"/> as defined by the Multipurpose
281   Internet Mail Extensions (MIME) <xref target="RFC2045"/>.
282</t>
283<t>
284   HTTP is also used as a generic protocol for communication between
285   user agents and proxies/gateways to other Internet systems, including
286   those supported by the SMTP <xref target="RFC2821"/>, NNTP <xref target="RFC3977"/>, FTP <xref target="RFC959"/>, Gopher <xref target="RFC1436"/>,
287   and WAIS <xref target="WAIS"/> protocols. In this way, HTTP allows basic hypermedia
288   access to resources available from diverse applications.
289</t>
290</section>
291
292<section title="Requirements" anchor="intro.requirements">
293<t>
294   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
295   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
296   document are to be interpreted as described in <xref target="RFC2119"/>.
297</t>
298<t>
299   An implementation is not compliant if it fails to satisfy one or more
300   of the &MUST; or &REQUIRED; level requirements for the protocols it
301   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
302   level and all the &SHOULD; level requirements for its protocols is said
303   to be "unconditionally compliant"; one that satisfies all the &MUST;
304   level requirements but not all the &SHOULD; level requirements for its
305   protocols is said to be "conditionally compliant."
306</t>
307</section>
308
309<section title="Terminology" anchor="intro.terminology">
310<t>
311   This specification uses a number of terms to refer to the roles
312   played by participants in, and objects of, the HTTP communication.
313</t>
314<t>
315  <iref item="connection"/>
316  <x:dfn>connection</x:dfn>
317  <list>
318    <t>
319      A transport layer virtual circuit established between two programs
320      for the purpose of communication.
321    </t>
322  </list>
323</t>
324<t>
325  <iref item="message"/>
326  <x:dfn>message</x:dfn>
327  <list>
328    <t>
329      The basic unit of HTTP communication, consisting of a structured
330      sequence of octets matching the syntax defined in <xref target="http.message"/> and
331      transmitted via the connection.
332    </t>
333  </list>
334</t>
335<t>
336  <iref item="request"/>
337  <x:dfn>request</x:dfn>
338  <list>
339    <t>
340      An HTTP request message, as defined in <xref target="request"/>.
341    </t>
342  </list>
343</t>
344<t>
345  <iref item="response"/>
346  <x:dfn>response</x:dfn>
347  <list>
348    <t>
349      An HTTP response message, as defined in <xref target="response"/>.
350    </t>
351  </list>
352</t>
353<t>
354  <iref item="resource"/>
355  <x:dfn>resource</x:dfn>
356  <list>
357    <t>
358      A network data object or service that can be identified by a URI,
359      as defined in <xref target="uri"/>. Resources may be available in multiple
360      representations (e.g. multiple languages, data formats, size, and
361      resolutions) or vary in other ways.
362    </t>
363  </list>
364</t>
365<t>
366  <iref item="entity"/>
367  <x:dfn>entity</x:dfn>
368  <list>
369    <t>
370      The information transferred as the payload of a request or
371      response. An entity consists of metainformation in the form of
372      entity-header fields and content in the form of an entity-body, as
373      described in &entity;.
374    </t>
375  </list>
376</t>
377<t>
378  <iref item="representation"/>
379  <x:dfn>representation</x:dfn>
380  <list>
381    <t>
382      An entity included with a response that is subject to content
383      negotiation, as described in &content.negotiation;. There may exist multiple
384      representations associated with a particular response status.
385    </t>
386  </list>
387</t>
388<t>
389  <iref item="content negotiation"/>
390  <x:dfn>content negotiation</x:dfn>
391  <list>
392    <t>
393      The mechanism for selecting the appropriate representation when
394      servicing a request, as described in &content.negotiation;. The
395      representation of entities in any response can be negotiated
396      (including error responses).
397    </t>
398  </list>
399</t>
400<t>
401  <iref item="variant"/>
402  <x:dfn>variant</x:dfn>
403  <list>
404    <t>
405      A resource may have one, or more than one, representation(s)
406      associated with it at any given instant. Each of these
407      representations is termed a `variant'.  Use of the term `variant'
408      does not necessarily imply that the resource is subject to content
409      negotiation.
410    </t>
411  </list>
412</t>
413<t>
414  <iref item="client"/>
415  <x:dfn>client</x:dfn>
416  <list>
417    <t>
418      A program that establishes connections for the purpose of sending
419      requests.
420    </t>
421  </list>
422</t>
423<t>
424  <iref item="user agent"/>
425  <x:dfn>user agent</x:dfn>
426  <list>
427    <t>
428      The client which initiates a request. These are often browsers,
429      editors, spiders (web-traversing robots), or other end user tools.
430    </t>
431  </list>
432</t>
433<t>
434  <iref item="server"/>
435  <x:dfn>server</x:dfn>
436  <list>
437    <t>
438      An application program that accepts connections in order to
439      service requests by sending back responses. Any given program may
440      be capable of being both a client and a server; our use of these
441      terms refers only to the role being performed by the program for a
442      particular connection, rather than to the program's capabilities
443      in general. Likewise, any server may act as an origin server,
444      proxy, gateway, or tunnel, switching behavior based on the nature
445      of each request.
446    </t>
447  </list>
448</t>
449<t>
450  <iref item="origin server"/>
451  <x:dfn>origin server</x:dfn>
452  <list>
453    <t>
454      The server on which a given resource resides or is to be created.
455    </t>
456  </list>
457</t>
458<t>
459  <iref item="proxy"/>
460  <x:dfn>proxy</x:dfn>
461  <list>
462    <t>
463      An intermediary program which acts as both a server and a client
464      for the purpose of making requests on behalf of other clients.
465      Requests are serviced internally or by passing them on, with
466      possible translation, to other servers. A proxy &MUST; implement
467      both the client and server requirements of this specification. A
468      "transparent proxy" is a proxy that does not modify the request or
469      response beyond what is required for proxy authentication and
470      identification. A "non-transparent proxy" is a proxy that modifies
471      the request or response in order to provide some added service to
472      the user agent, such as group annotation services, media type
473      transformation, protocol reduction, or anonymity filtering. Except
474      where either transparent or non-transparent behavior is explicitly
475      stated, the HTTP proxy requirements apply to both types of
476      proxies.
477    </t>
478  </list>
479</t>
480<t>
481  <iref item="gateway"/>
482  <x:dfn>gateway</x:dfn>
483  <list>
484    <t>
485      A server which acts as an intermediary for some other server.
486      Unlike a proxy, a gateway receives requests as if it were the
487      origin server for the requested resource; the requesting client
488      may not be aware that it is communicating with a gateway.
489    </t>
490  </list>
491</t>
492<t>
493  <iref item="tunnel"/>
494  <x:dfn>tunnel</x:dfn>
495  <list>
496    <t>
497      An intermediary program which is acting as a blind relay between
498      two connections. Once active, a tunnel is not considered a party
499      to the HTTP communication, though the tunnel may have been
500      initiated by an HTTP request. The tunnel ceases to exist when both
501      ends of the relayed connections are closed.
502    </t>
503  </list>
504</t>
505<t>
506  <iref item="cache"/>
507  <x:dfn>cache</x:dfn>
508  <list>
509    <t>
510      A program's local store of response messages and the subsystem
511      that controls its message storage, retrieval, and deletion. A
512      cache stores cacheable responses in order to reduce the response
513      time and network bandwidth consumption on future, equivalent
514      requests. Any client or server may include a cache, though a cache
515      cannot be used by a server that is acting as a tunnel.
516    </t>
517  </list>
518</t>
519<t>
520  <iref item="cacheable"/>
521  <x:dfn>cacheable</x:dfn>
522  <list>
523    <t>
524      A response is cacheable if a cache is allowed to store a copy of
525      the response message for use in answering subsequent requests. The
526      rules for determining the cacheability of HTTP responses are
527      defined in &caching;. Even if a resource is cacheable, there may
528      be additional constraints on whether a cache can use the cached
529      copy for a particular request.
530    </t>
531  </list>
532</t>
533<t>
534  <iref item="upstream"/>
535  <iref item="downstream"/>
536  <x:dfn>upstream</x:dfn>/<x:dfn>downstream</x:dfn>
537  <list>
538    <t>
539      Upstream and downstream describe the flow of a message: all
540      messages flow from upstream to downstream.
541    </t>
542  </list>
543</t>
544<t>
545  <iref item="inbound"/>
546  <iref item="outbound"/>
547  <x:dfn>inbound</x:dfn>/<x:dfn>outbound</x:dfn>
548  <list>
549    <t>
550      Inbound and outbound refer to the request and response paths for
551      messages: "inbound" means "traveling toward the origin server",
552      and "outbound" means "traveling toward the user agent"
553    </t>
554  </list>
555</t>
556</section>
557
558<section title="Overall Operation" anchor="intro.overall.operation">
559<t>
560   HTTP is a request/response protocol. A client sends a
561   request to the server in the form of a request method, URI, and
562   protocol version, followed by a MIME-like message containing request
563   modifiers, client information, and possible body content over a
564   connection with a server. The server responds with a status line,
565   including the message's protocol version and a success or error code,
566   followed by a MIME-like message containing server information, entity
567   metainformation, and possible entity-body content. The relationship
568   between HTTP and MIME is described in &diff2045entity;.
569</t>
570<t>
571   Most HTTP communication is initiated by a user agent and consists of
572   a request to be applied to a resource on some origin server. In the
573   simplest case, this may be accomplished via a single connection (v)
574   between the user agent (UA) and the origin server (O).
575</t>
576<figure><artwork type="drawing">
577       request chain ------------------------&gt;
578    UA -------------------v------------------- O
579       &lt;----------------------- response chain
580</artwork></figure>
581<t>
582   A more complicated situation occurs when one or more intermediaries
583   are present in the request/response chain. There are three common
584   forms of intermediary: proxy, gateway, and tunnel. A proxy is a
585   forwarding agent, receiving requests for a URI in its absolute form,
586   rewriting all or part of the message, and forwarding the reformatted
587   request toward the server identified by the URI. A gateway is a
588   receiving agent, acting as a layer above some other server(s) and, if
589   necessary, translating the requests to the underlying server's
590   protocol. A tunnel acts as a relay point between two connections
591   without changing the messages; tunnels are used when the
592   communication needs to pass through an intermediary (such as a
593   firewall) even when the intermediary cannot understand the contents
594   of the messages.
595</t>
596<figure><artwork type="drawing">
597       request chain --------------------------------------&gt;
598    UA -----v----- A -----v----- B -----v----- C -----v----- O
599       &lt;------------------------------------- response chain
600</artwork></figure>
601<t>
602   The figure above shows three intermediaries (A, B, and C) between the
603   user agent and origin server. A request or response message that
604   travels the whole chain will pass through four separate connections.
605   This distinction is important because some HTTP communication options
606   may apply only to the connection with the nearest, non-tunnel
607   neighbor, only to the end-points of the chain, or to all connections
608   along the chain. Although the diagram is linear, each participant may
609   be engaged in multiple, simultaneous communications. For example, B
610   may be receiving requests from many clients other than A, and/or
611   forwarding requests to servers other than C, at the same time that it
612   is handling A's request.
613</t>
614<t>
615   Any party to the communication which is not acting as a tunnel may
616   employ an internal cache for handling requests. The effect of a cache
617   is that the request/response chain is shortened if one of the
618   participants along the chain has a cached response applicable to that
619   request. The following illustrates the resulting chain if B has a
620   cached copy of an earlier response from O (via C) for a request which
621   has not been cached by UA or A.
622</t>
623<figure><artwork type="drawing">
624          request chain ----------&gt;
625       UA -----v----- A -----v----- B - - - - - - C - - - - - - O
626          &lt;--------- response chain
627</artwork></figure>
628<t>
629   Not all responses are usefully cacheable, and some requests may
630   contain modifiers which place special requirements on cache behavior.
631   HTTP requirements for cache behavior and cacheable responses are
632   defined in &caching;.
633</t>
634<t>
635   In fact, there are a wide variety of architectures and configurations
636   of caches and proxies currently being experimented with or deployed
637   across the World Wide Web. These systems include national hierarchies
638   of proxy caches to save transoceanic bandwidth, systems that
639   broadcast or multicast cache entries, organizations that distribute
640   subsets of cached data via CD-ROM, and so on. HTTP systems are used
641   in corporate intranets over high-bandwidth links, and for access via
642   PDAs with low-power radio links and intermittent connectivity. The
643   goal of HTTP/1.1 is to support the wide diversity of configurations
644   already deployed while introducing protocol constructs that meet the
645   needs of those who build web applications that require high
646   reliability and, failing that, at least reliable indications of
647   failure.
648</t>
649<t>
650   HTTP communication usually takes place over TCP/IP connections. The
651   default port is TCP 80 (<eref target="http://www.iana.org/assignments/port-numbers"/>), but other ports can be used. This does
652   not preclude HTTP from being implemented on top of any other protocol
653   on the Internet, or on other networks. HTTP only presumes a reliable
654   transport; any protocol that provides such guarantees can be used;
655   the mapping of the HTTP/1.1 request and response structures onto the
656   transport data units of the protocol in question is outside the scope
657   of this specification.
658</t>
659<t>
660   In HTTP/1.0, most implementations used a new connection for each
661   request/response exchange. In HTTP/1.1, a connection may be used for
662   one or more request/response exchanges, although connections may be
663   closed for a variety of reasons (see <xref target="persistent.connections"/>).
664</t>
665</section>
666</section>
667
668<section title="Notational Conventions and Generic Grammar" anchor="notation">
669
670<section title="Augmented BNF" anchor="notation.abnf">
671<t>
672   All of the mechanisms specified in this document are described in
673   both prose and an augmented Backus-Naur Form (BNF) similar to that
674   used by <xref target="RFC822ABNF"/>. Implementors will need to be familiar with the
675   notation in order to understand this specification. The augmented BNF
676   includes the following constructs:
677</t>
678<t>
679   name = definition
680  <list>
681    <t>
682      The name of a rule is simply the name itself (without any
683      enclosing "&lt;" and "&gt;") and is separated from its definition by the
684      equal "=" character. White space is only significant in that
685      indentation of continuation lines is used to indicate a rule
686      definition that spans more than one line. Certain basic rules are
687      in uppercase, such as SP, LWS, HTAB, CRLF, DIGIT, ALPHA, etc. Angle
688      brackets are used within definitions whenever their presence will
689      facilitate discerning the use of rule names.
690    </t>
691  </list>
692</t>
693<t>
694   "literal"
695  <list>
696    <t>
697      Quotation marks surround literal text. Unless stated otherwise,
698      the text is case-insensitive.
699    </t>
700  </list>
701</t>
702<t>
703   rule1 | rule2
704  <list>
705    <t>
706      Elements separated by a bar ("|") are alternatives, e.g., "yes |
707      no" will accept yes or no.
708    </t>
709  </list>
710</t>
711<t>
712   (rule1 rule2)
713  <list>
714    <t>
715      Elements enclosed in parentheses are treated as a single element.
716      Thus, "(elem (foo | bar) elem)" allows the token sequences "elem
717      foo elem" and "elem bar elem".
718    </t>
719  </list>
720</t>
721<t>
722   *rule
723  <list>
724    <t>
725      The character "*" preceding an element indicates repetition. The
726      full form is "&lt;n&gt;*&lt;m&gt;element" indicating at least &lt;n&gt; and at most
727      &lt;m&gt; occurrences of element. Default values are 0 and infinity so
728      that "*(element)" allows any number, including zero; "1*element"
729      requires at least one; and "1*2element" allows one or two.
730    </t>
731  </list>
732</t>
733<t>
734   [rule]
735  <list>
736    <t>
737      Square brackets enclose optional elements; "[foo bar]" is
738      equivalent to "*1(foo bar)".
739    </t>
740  </list>
741</t>
742<t>
743   N rule
744  <list>
745    <t>
746      Specific repetition: "&lt;n&gt;(element)" is equivalent to
747      "&lt;n&gt;*&lt;n&gt;(element)"; that is, exactly &lt;n&gt; occurrences of (element).
748      Thus 2DIGIT is a 2-digit number, and 3ALPHA is a string of three
749      alphabetic characters.
750    </t>
751  </list>
752</t>
753<t>
754   #rule
755  <list>
756    <t>
757      A construct "#" is defined, similar to "*", for defining lists of
758      elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating at least
759      &lt;n&gt; and at most &lt;m&gt; elements, each separated by one or more commas
760      (",") and &OPTIONAL; linear white space (LWS). This makes the usual
761      form of lists very easy; a rule such as
762    </t>
763    <t>
764         ( *LWS element *( *LWS "," *LWS element ))
765    </t>
766    <t>
767      can be shown as
768    </t>
769    <t>
770         1#element
771    </t>
772    <t>
773      Wherever this construct is used, null elements are allowed, but do
774      not contribute to the count of elements present. That is,
775      "(element), , (element) " is permitted, but counts as only two
776      elements. Therefore, where at least one element is required, at
777      least one non-null element &MUST; be present. Default values are 0
778      and infinity so that "#element" allows any number, including zero;
779      "1#element" requires at least one; and "1#2element" allows one or
780      two.
781    </t>
782  </list>
783</t>
784<t>
785   ; comment
786  <list>
787    <t>
788      A semi-colon, set off some distance to the right of rule text,
789      starts a comment that continues to the end of line. This is a
790      simple way of including useful notes in parallel with the
791      specifications.
792    </t>
793  </list>
794</t>
795<t>
796   implied *LWS
797  <list>
798    <t>
799      The grammar described by this specification is word-based. Except
800      where noted otherwise, linear white space (LWS) can be included
801      between any two adjacent words (token or quoted-string), and
802      between adjacent words and separators, without changing the
803      interpretation of a field. At least one delimiter (LWS and/or
804      separators) &MUST; exist between any two tokens (for the definition
805      of "token" below), since they would otherwise be interpreted as a
806      single token.
807    </t>
808  </list>
809</t>
810</section>
811
812<section title="Basic Rules" anchor="basic.rules">
813<x:anchor-alias value="OCTET"/>
814<x:anchor-alias value="CHAR"/>
815<x:anchor-alias value="ALPHA"/>
816<x:anchor-alias value="DIGIT"/>
817<x:anchor-alias value="CTL"/>
818<x:anchor-alias value="CR"/>
819<x:anchor-alias value="LF"/>
820<x:anchor-alias value="SP"/>
821<x:anchor-alias value="HTAB"/>
822<x:anchor-alias value="CRLF"/>
823<x:anchor-alias value="LWS"/>
824<x:anchor-alias value="TEXT"/>
825<x:anchor-alias value="HEX"/>
826<x:anchor-alias value="token"/>
827<x:anchor-alias value="separators"/>
828<x:anchor-alias value="comment"/>
829<x:anchor-alias value="ctext"/>
830<x:anchor-alias value="quoted-string"/>
831<x:anchor-alias value="qdtext"/>
832<x:anchor-alias value="quoted-pair"/>
833<t>
834   The following rules are used throughout this specification to
835   describe basic parsing constructs. The US-ASCII coded character set
836   is defined by ANSI X3.4-1986 <xref target="USASCII"/>.
837</t>
838<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OCTET"/><iref primary="true" item="Grammar" subitem="CHAR"/><iref primary="true" item="Grammar" subitem="ALPHA"/><iref primary="true" item="Grammar" subitem="DIGIT"/><iref primary="true" item="Grammar" subitem="CTL"/><iref primary="true" item="Grammar" subitem="CR"/><iref primary="true" item="Grammar" subitem="LF"/><iref primary="true" item="Grammar" subitem="SP"/><iref primary="true" item="Grammar" subitem="HTAB"/><iref primary="true" item="Grammar" subitem="DQUOTE"/>
839  OCTET          = %x00-FF
840                   ; any 8-bit sequence of data
841  CHAR           = %x01-7F
842                   ; any US-ASCII character, excluding NUL
843  ALPHA          = %x41-5A | %x61-7A
844                   ; A-Z | a-z
845  DIGIT          = %x30-39
846                   ; any US-ASCII digit "0".."9"
847  CTL            = %x00-1F | %x7F
848                   ; (octets 0 - 31) and DEL (127)
849  CR             = %x0D
850                   ; US-ASCII CR, carriage return (13)
851  LF             = %x0A
852                   ; US-ASCII LF, linefeed (10)
853  SP             = %x20
854                   ; US-ASCII SP, space (32)
855  HTAB           = %x09
856                   ; US-ASCII HT, horizontal-tab (9)
857  DQUOTE         = %x22
858                   ; US-ASCII double-quote mark (34)
859</artwork></figure>
860<t>
861   HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all
862   protocol elements except the entity-body (see <xref target="tolerant.applications"/> for
863   tolerant applications). The end-of-line marker within an entity-body
864   is defined by its associated media type, as described in &media-types;.
865</t>
866<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="CRLF"/>
867  CRLF           = CR LF
868</artwork></figure>
869<t>
870   HTTP/1.1 header field values can be folded onto multiple lines if the
871   continuation line begins with a space or horizontal tab. All linear
872   white space, including folding, has the same semantics as SP. A
873   recipient &MAY; replace any linear white space with a single SP before
874   interpreting the field value or forwarding the message downstream.
875</t>
876<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="LWS"/>
877  LWS            = [CRLF] 1*( SP | HTAB )
878</artwork></figure>
879<t>
880   The TEXT rule is only used for descriptive field contents and values
881   that are not intended to be interpreted by the message parser. Words
882   of *TEXT &MAY; contain characters from character sets other than ISO-8859-1
883   <xref target="ISO-8859-1"/> only when encoded according to the rules of
884   <xref target="RFC2047"/>.
885</t>
886<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TEXT"/>
887  TEXT           = &lt;any OCTET except CTLs, but including LWS&gt;
888</artwork></figure>
889<t>
890   A CRLF is allowed in the definition of TEXT only as part of a header
891   field continuation. It is expected that the folding LWS will be
892   replaced with a single SP before interpretation of the TEXT value.
893</t>
894<t>
895   Hexadecimal numeric characters are used in several protocol elements.
896</t>
897<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HEX"/>
898  HEX            = "A" | "B" | "C" | "D" | "E" | "F"
899                 | "a" | "b" | "c" | "d" | "e" | "f" | DIGIT
900</artwork></figure>
901<t>
902   Many HTTP/1.1 header field values consist of words separated by LWS
903   or special characters. These special characters &MUST; be in a quoted
904   string to be used within a parameter value (as defined in
905   <xref target="transfer.codings"/>).
906</t>
907<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="token"/><iref primary="true" item="Grammar" subitem="separators"/>
908  token          = 1*&lt;any CHAR except CTLs or separators&gt;
909  separators     = "(" | ")" | "&lt;" | "&gt;" | "@"
910                 | "," | ";" | ":" | "\" | DQUOTE
911                 | "/" | "[" | "]" | "?" | "="
912                 | "{" | "}" | SP | HTAB
913</artwork></figure>
914<t>
915   Comments can be included in some HTTP header fields by surrounding
916   the comment text with parentheses. Comments are only allowed in
917   fields containing "comment" as part of their field value definition.
918   In all other fields, parentheses are considered part of the field
919   value.
920</t>
921<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="comment"/><iref primary="true" item="Grammar" subitem="ctext"/>
922  comment        = "(" *( ctext | quoted-pair | comment ) ")"
923  ctext          = &lt;any TEXT excluding "(" and ")"&gt;
924</artwork></figure>
925<t>
926   A string of text is parsed as a single word if it is quoted using
927   double-quote marks.
928</t>
929<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-string"/><iref primary="true" item="Grammar" subitem="qdtext"/>
930  quoted-string  = ( DQUOTE *(qdtext | quoted-pair ) DQUOTE )
931  qdtext         = &lt;any TEXT excluding DQUOTE and "\">
932</artwork></figure>
933<t>
934   The backslash character ("\") &MAY; be used as a single-character
935   quoting mechanism only within quoted-string and comment constructs.
936</t>
937<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-pair"/>
938  quoted-pair    = "\" CHAR
939</artwork></figure>
940</section>
941</section>
942
943<section title="Protocol Parameters" anchor="protocol.parameters">
944
945<section title="HTTP Version" anchor="http.version">
946<t>
947   HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate versions
948   of the protocol. The protocol versioning policy is intended to allow
949   the sender to indicate the format of a message and its capacity for
950   understanding further HTTP communication, rather than the features
951   obtained via that communication. No change is made to the version
952   number for the addition of message components which do not affect
953   communication behavior or which only add to extensible field values.
954   The &lt;minor&gt; number is incremented when the changes made to the
955   protocol add features which do not change the general message parsing
956   algorithm, but which may add to the message semantics and imply
957   additional capabilities of the sender. The &lt;major&gt; number is
958   incremented when the format of a message within the protocol is
959   changed. See <xref target="RFC2145"/> for a fuller explanation.
960</t>
961<t>
962   The version of an HTTP message is indicated by an HTTP-Version field
963   in the first line of the message. HTTP-Version is case-sensitive.
964</t>
965<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-Version"/>
966  HTTP-Version   = "HTTP" "/" 1*DIGIT "." 1*DIGIT
967</artwork></figure>
968<t>
969   Note that the major and minor numbers &MUST; be treated as separate
970   integers and that each &MAY; be incremented higher than a single digit.
971   Thus, HTTP/2.4 is a lower version than HTTP/2.13, which in turn is
972   lower than HTTP/12.3. Leading zeros &MUST; be ignored by recipients and
973   &MUST-NOT; be sent.
974</t>
975<t>
976   An application that sends a request or response message that includes
977   HTTP-Version of "HTTP/1.1" &MUST; be at least conditionally compliant
978   with this specification. Applications that are at least conditionally
979   compliant with this specification &SHOULD; use an HTTP-Version of
980   "HTTP/1.1" in their messages, and &MUST; do so for any message that is
981   not compatible with HTTP/1.0. For more details on when to send
982   specific HTTP-Version values, see <xref target="RFC2145"/>.
983</t>
984<t>
985   The HTTP version of an application is the highest HTTP version for
986   which the application is at least conditionally compliant.
987</t>
988<t>
989   Proxy and gateway applications need to be careful when forwarding
990   messages in protocol versions different from that of the application.
991   Since the protocol version indicates the protocol capability of the
992   sender, a proxy/gateway &MUST-NOT; send a message with a version
993   indicator which is greater than its actual version. If a higher
994   version request is received, the proxy/gateway &MUST; either downgrade
995   the request version, or respond with an error, or switch to tunnel
996   behavior.
997</t>
998<t>
999   Due to interoperability problems with HTTP/1.0 proxies discovered
1000   since the publication of <xref target="RFC2068"/>, caching proxies &MUST;, gateways
1001   &MAY;, and tunnels &MUST-NOT; upgrade the request to the highest version
1002   they support. The proxy/gateway's response to that request &MUST; be in
1003   the same major version as the request.
1004</t>
1005<t>
1006  <list>
1007    <t>
1008      <x:h>Note:</x:h> Converting between versions of HTTP may involve modification
1009      of header fields required or forbidden by the versions involved.
1010    </t>
1011  </list>
1012</t>
1013</section>
1014
1015<section title="Uniform Resource Identifiers" anchor="uri">
1016<t>
1017   URIs have been known by many names: WWW addresses, Universal Document
1018   Identifiers, Universal Resource Identifiers <xref target="RFC1630"/>, and finally the
1019   combination of Uniform Resource Locators (URL) <xref target="RFC1738"/> and Names (URN)
1020   <xref target="RFC1737"/>. As far as HTTP is concerned, Uniform Resource Identifiers are
1021   simply formatted strings which identify--via name, location, or any
1022   other characteristic--a resource.
1023</t>
1024
1025<section title="General Syntax" anchor="general.syntax">
1026<t>
1027   URIs in HTTP can be represented in absolute form or relative to some
1028   known base URI <xref target="RFC1808"/>, depending upon the context of their use. The two
1029   forms are differentiated by the fact that absolute URIs always begin
1030   with a scheme name followed by a colon. For definitive information on
1031   URL syntax and semantics, see "Uniform Resource Identifiers (URI):
1032   Generic Syntax and Semantics," <xref target="RFC2396"/> (which replaces <xref target="RFC1738"/>
1033   and <xref target="RFC1808"/>). This specification adopts the
1034   definitions of "URI-reference", "absoluteURI", "fragment", "relativeURI", "port",
1035   "host", "abs_path", "query", and "authority" from that specification:
1036</t>
1037<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="absoluteURI"/><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="relativeURI"/><iref primary="true" item="Grammar" subitem="uri-host"/>
1038  absoluteURI   = &lt;absoluteURI, defined in <xref target="RFC2396" x:fmt="," x:sec="3"/>>
1039  authority     = &lt;authority, defined in <xref target="RFC2396" x:fmt="," x:sec="3.2"/>>
1040  fragment      = &lt;fragment, defined in <xref target="RFC2396" x:fmt="," x:sec="4.1"/>>
1041  path-absolute = &lt;abs_path, defined in <xref target="RFC2396" x:fmt="," x:sec="3"/>>
1042  port          = &lt;port, defined in <xref target="RFC2396" x:fmt="," x:sec="3.2.2"/>>
1043  query         = &lt;query, defined in <xref target="RFC2396" x:fmt="," x:sec="3.4"/>>
1044  relativeURI   = &lt;relativeURI, defined in <xref target="RFC2396" x:fmt="," x:sec="5"/>>
1045  uri-host      = &lt;host, defined in <xref target="RFC2396" x:fmt="," x:sec="3.2.2"/>>
1046</artwork></figure>
1047<t>
1048   HTTP does not place any a priori limit on the length of
1049   a URI. Servers &MUST; be able to handle the URI of any resource they
1050   serve, and &SHOULD; be able to handle URIs of unbounded length if they
1051   provide GET-based forms that could generate such URIs. A server
1052   &SHOULD; return 414 (Request-URI Too Long) status if a URI is longer
1053   than the server can handle (see &status-414;).
1054</t>
1055<t>
1056  <list>
1057    <t>
1058      <x:h>Note:</x:h> Servers ought to be cautious about depending on URI lengths
1059      above 255 bytes, because some older client or proxy
1060      implementations might not properly support these lengths.
1061    </t>
1062  </list>
1063</t>
1064</section>
1065
1066<section title="http URL" anchor="http.url">
1067<t>
1068   The "http" scheme is used to locate network resources via the HTTP
1069   protocol. This section defines the scheme-specific syntax and
1070   semantics for http URLs.
1071</t>
1072<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http-URL"/>
1073  http-URL = "http:" "//" uri-host [ ":" port ]
1074             [ path-absolute [ "?" query ]]
1075</artwork></figure>
1076<t>
1077   If the port is empty or not given, port 80 is assumed. The semantics
1078   are that the identified resource is located at the server listening
1079   for TCP connections on that port of that host, and the Request-URI
1080   for the resource is path-absolute (<xref target="request-uri"/>). The use of IP addresses
1081   in URLs &SHOULD; be avoided whenever possible (see <xref target="RFC1900"/>). If
1082   the path-absolute is not present in the URL, it &MUST; be given as "/" when
1083   used as a Request-URI for a resource (<xref target="request-uri"/>). If a proxy
1084   receives a host name which is not a fully qualified domain name, it
1085   &MAY; add its domain to the host name it received. If a proxy receives
1086   a fully qualified domain name, the proxy &MUST-NOT; change the host
1087   name.
1088</t>
1089</section>
1090
1091<section title="URI Comparison" anchor="uri.comparison">
1092<t>
1093   When comparing two URIs to decide if they match or not, a client
1094   &SHOULD; use a case-sensitive octet-by-octet comparison of the entire
1095   URIs, with these exceptions:
1096  <list style="symbols">
1097    <t>A port that is empty or not given is equivalent to the default
1098        port for that URI-reference;</t>
1099    <t>Comparisons of host names &MUST; be case-insensitive;</t>
1100    <t>Comparisons of scheme names &MUST; be case-insensitive;</t>
1101    <t>An empty path-absolute is equivalent to an path-absolute of "/".</t>
1102  </list>
1103</t>
1104<t>
1105   Characters other than those in the "reserved" set (see
1106   <xref target="RFC2396"/>) are equivalent to their ""%" HEX HEX" encoding.
1107</t>
1108<t>
1109   For example, the following three URIs are equivalent:
1110</t>
1111<figure><artwork type="example">
1112   http://example.com:80/~smith/home.html
1113   http://EXAMPLE.com/%7Esmith/home.html
1114   http://EXAMPLE.com:/%7esmith/home.html
1115</artwork></figure>
1116</section>
1117</section>
1118
1119<section title="Date/Time Formats" anchor="date.time.formats">
1120<section title="Full Date" anchor="full.date">
1121<t>
1122   HTTP applications have historically allowed three different formats
1123   for the representation of date/time stamps:
1124</t>
1125<figure><artwork type="example">
1126   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 822, updated by RFC 1123
1127   Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
1128   Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
1129</artwork></figure>
1130<t>
1131   The first format is preferred as an Internet standard and represents
1132   a fixed-length subset of that defined by <xref target="RFC1123"/> (an update to
1133   <xref target="RFC822"/>). The other formats are described here only for
1134   compatibility with obsolete implementations.
1135   HTTP/1.1 clients and servers that parse the date value &MUST; accept
1136   all three formats (for compatibility with HTTP/1.0), though they &MUST;
1137   only generate the RFC 1123 format for representing HTTP-date values
1138   in header fields. See <xref target="tolerant.applications"/> for further information.
1139</t>
1140<t><list><t>
1141      <x:h>Note:</x:h> Recipients of date values are encouraged to be robust in
1142      accepting date values that may have been sent by non-HTTP
1143      applications, as is sometimes the case when retrieving or posting
1144      messages via proxies/gateways to SMTP or NNTP.
1145</t></list></t>
1146<t>
1147   All HTTP date/time stamps &MUST; be represented in Greenwich Mean Time
1148   (GMT), without exception. For the purposes of HTTP, GMT is exactly
1149   equal to UTC (Coordinated Universal Time). This is indicated in the
1150   first two formats by the inclusion of "GMT" as the three-letter
1151   abbreviation for time zone, and &MUST; be assumed when reading the
1152   asctime format. HTTP-date is case sensitive and &MUST-NOT; include
1153   additional LWS beyond that specifically included as SP in the
1154   grammar.
1155</t>
1156<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-date"/><iref primary="true" item="Grammar" subitem="rfc1123-date"/><iref primary="true" item="Grammar" subitem="rfc850-date"/><iref primary="true" item="Grammar" subitem="asctime-date"/><iref primary="true" item="Grammar" subitem="date1"/><iref primary="true" item="Grammar" subitem="date2"/><iref primary="true" item="Grammar" subitem="date3"/><iref primary="true" item="Grammar" subitem="time"/><iref primary="true" item="Grammar" subitem="wkday"/><iref primary="true" item="Grammar" subitem="weekday"/><iref primary="true" item="Grammar" subitem="month"/>
1157  HTTP-date    = rfc1123-date | rfc850-date | asctime-date
1158  rfc1123-date = wkday "," SP date1 SP time SP "GMT"
1159  rfc850-date  = weekday "," SP date2 SP time SP "GMT"
1160  asctime-date = wkday SP date3 SP time SP 4DIGIT
1161  date1        = 2DIGIT SP month SP 4DIGIT
1162                 ; day month year (e.g., 02 Jun 1982)
1163  date2        = 2DIGIT "-" month "-" 2DIGIT
1164                 ; day-month-year (e.g., 02-Jun-82)
1165  date3        = month SP ( 2DIGIT | ( SP 1DIGIT ))
1166                 ; month day (e.g., Jun  2)
1167  time         = 2DIGIT ":" 2DIGIT ":" 2DIGIT
1168                 ; 00:00:00 - 23:59:59
1169  wkday        = "Mon" | "Tue" | "Wed"
1170               | "Thu" | "Fri" | "Sat" | "Sun"
1171  weekday      = "Monday" | "Tuesday" | "Wednesday"
1172               | "Thursday" | "Friday" | "Saturday" | "Sunday"
1173  month        = "Jan" | "Feb" | "Mar" | "Apr"
1174               | "May" | "Jun" | "Jul" | "Aug"
1175               | "Sep" | "Oct" | "Nov" | "Dec"
1176</artwork></figure>
1177<t>
1178      <x:h>Note:</x:h> HTTP requirements for the date/time stamp format apply only
1179      to their usage within the protocol stream. Clients and servers are
1180      not required to use these formats for user presentation, request
1181      logging, etc.
1182</t>
1183</section>
1184</section>
1185
1186<section title="Transfer Codings" anchor="transfer.codings">
1187<t>
1188   Transfer-coding values are used to indicate an encoding
1189   transformation that has been, can be, or may need to be applied to an
1190   entity-body in order to ensure "safe transport" through the network.
1191   This differs from a content coding in that the transfer-coding is a
1192   property of the message, not of the original entity.
1193</t>
1194<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-coding"/><iref primary="true" item="Grammar" subitem="transfer-extension"/>
1195  transfer-coding         = "chunked" | transfer-extension
1196  transfer-extension      = token *( ";" parameter )
1197</artwork></figure>
1198<t>
1199   Parameters are in  the form of attribute/value pairs.
1200</t>
1201<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="parameter"/><iref primary="true" item="Grammar" subitem="attribute"/><iref primary="true" item="Grammar" subitem="value"/>
1202  parameter               = attribute "=" value
1203  attribute               = token
1204  value                   = token | quoted-string
1205</artwork></figure>
1206<t>
1207   All transfer-coding values are case-insensitive. HTTP/1.1 uses
1208   transfer-coding values in the TE header field (<xref target="header.te"/>) and in
1209   the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).
1210</t>
1211<t>
1212   Whenever a transfer-coding is applied to a message-body, the set of
1213   transfer-codings &MUST; include "chunked", unless the message is
1214   terminated by closing the connection. When the "chunked" transfer-coding
1215   is used, it &MUST; be the last transfer-coding applied to the
1216   message-body. The "chunked" transfer-coding &MUST-NOT; be applied more
1217   than once to a message-body. These rules allow the recipient to
1218   determine the transfer-length of the message (<xref target="message.length"/>).
1219</t>
1220<t>
1221   Transfer-codings are analogous to the Content-Transfer-Encoding
1222   values of MIME <xref target="RFC2045"/>, which were designed to enable safe transport of
1223   binary data over a 7-bit transport service. However, safe transport
1224   has a different focus for an 8bit-clean transfer protocol. In HTTP,
1225   the only unsafe characteristic of message-bodies is the difficulty in
1226   determining the exact body length (<xref target="message.length"/>), or the desire to
1227   encrypt data over a shared transport.
1228</t>
1229<t>
1230   The Internet Assigned Numbers Authority (IANA) acts as a registry for
1231   transfer-coding value tokens. Initially, the registry contains the
1232   following tokens: "chunked" (<xref target="chunked.transfer.encoding"/>),
1233   "gzip", "compress", and "deflate" (&content-codings;).
1234</t>
1235<t>
1236   New transfer-coding value tokens &SHOULD; be registered in the same way
1237   as new content-coding value tokens (&content-codings;).
1238</t>
1239<t>
1240   A server which receives an entity-body with a transfer-coding it does
1241   not understand &SHOULD; return 501 (Not Implemented), and close the
1242   connection. A server &MUST-NOT; send transfer-codings to an HTTP/1.0
1243   client.
1244</t>
1245
1246<section title="Chunked Transfer Coding" anchor="chunked.transfer.encoding">
1247<t>
1248   The chunked encoding modifies the body of a message in order to
1249   transfer it as a series of chunks, each with its own size indicator,
1250   followed by an &OPTIONAL; trailer containing entity-header fields. This
1251   allows dynamically produced content to be transferred along with the
1252   information necessary for the recipient to verify that it has
1253   received the full message.
1254</t>
1255<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-extension"/><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"/>
1256  Chunked-Body   = *chunk
1257                   last-chunk
1258                   trailer-part
1259                   CRLF
1260 
1261  chunk          = chunk-size [ chunk-extension ] CRLF
1262                   chunk-data CRLF
1263  chunk-size     = 1*HEX
1264  last-chunk     = 1*("0") [ chunk-extension ] CRLF
1265 
1266  chunk-extension= *( ";" chunk-ext-name [ "=" chunk-ext-val ] )
1267  chunk-ext-name = token
1268  chunk-ext-val  = token | quoted-string
1269  chunk-data     = 1*OCTET ; a sequence of chunk-size octets
1270  trailer-part   = *(entity-header CRLF)
1271</artwork></figure>
1272<t>
1273   The chunk-size field is a string of hex digits indicating the size of
1274   the chunk-data in octets. The chunked encoding is ended by any chunk whose size is
1275   zero, followed by the trailer, which is terminated by an empty line.
1276</t>
1277<t>
1278   The trailer allows the sender to include additional HTTP header
1279   fields at the end of the message. The Trailer header field can be
1280   used to indicate which header fields are included in a trailer (see
1281   <xref target="header.trailer"/>).
1282</t>
1283<t>
1284   A server using chunked transfer-coding in a response &MUST-NOT; use the
1285   trailer for any header fields unless at least one of the following is
1286   true:
1287  <list style="numbers">
1288    <t>the request included a TE header field that indicates "trailers" is
1289     acceptable in the transfer-coding of the  response, as described in
1290     <xref target="header.te"/>; or,</t>
1291
1292    <t>the server is the origin server for the response, the trailer
1293     fields consist entirely of optional metadata, and the recipient
1294     could use the message (in a manner acceptable to the origin server)
1295     without receiving this metadata.  In other words, the origin server
1296     is willing to accept the possibility that the trailer fields might
1297     be silently discarded along the path to the client.</t>
1298  </list>
1299</t>
1300<t>
1301   This requirement prevents an interoperability failure when the
1302   message is being received by an HTTP/1.1 (or later) proxy and
1303   forwarded to an HTTP/1.0 recipient. It avoids a situation where
1304   compliance with the protocol would have necessitated a possibly
1305   infinite buffer on the proxy.
1306</t>
1307<t>
1308   A process for decoding the "chunked" transfer-coding
1309   can be represented in pseudo-code as:
1310</t>
1311<figure><artwork type="code">
1312    length := 0
1313    read chunk-size, chunk-extension (if any) and CRLF
1314    while (chunk-size &gt; 0) {
1315       read chunk-data and CRLF
1316       append chunk-data to entity-body
1317       length := length + chunk-size
1318       read chunk-size and CRLF
1319    }
1320    read entity-header
1321    while (entity-header not empty) {
1322       append entity-header to existing header fields
1323       read entity-header
1324    }
1325    Content-Length := length
1326    Remove "chunked" from Transfer-Encoding
1327</artwork></figure>
1328<t>
1329   All HTTP/1.1 applications &MUST; be able to receive and decode the
1330   "chunked" transfer-coding, and &MUST; ignore chunk-extension extensions
1331   they do not understand.
1332</t>
1333</section>
1334</section>
1335
1336<section title="Product Tokens" anchor="product.tokens">
1337<t>
1338   Product tokens are used to allow communicating applications to
1339   identify themselves by software name and version. Most fields using
1340   product tokens also allow sub-products which form a significant part
1341   of the application to be listed, separated by white space. By
1342   convention, the products are listed in order of their significance
1343   for identifying the application.
1344</t>
1345<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="product"/><iref primary="true" item="Grammar" subitem="product-version"/>
1346  product         = token ["/" product-version]
1347  product-version = token
1348</artwork></figure>
1349<t>
1350   Examples:
1351</t>
1352<figure><artwork type="example">
1353    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
1354    Server: Apache/0.8.4
1355</artwork></figure>
1356<t>
1357   Product tokens &SHOULD; be short and to the point. They &MUST-NOT; be
1358   used for advertising or other non-essential information. Although any
1359   token character &MAY; appear in a product-version, this token &SHOULD;
1360   only be used for a version identifier (i.e., successive versions of
1361   the same product &SHOULD; only differ in the product-version portion of
1362   the product value).
1363</t>
1364</section>
1365
1366</section>
1367
1368<section title="HTTP Message" anchor="http.message">
1369
1370<section title="Message Types" anchor="message.types">
1371<t>
1372   HTTP messages consist of requests from client to server and responses
1373   from server to client.
1374</t>
1375<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-message"/>
1376  HTTP-message   = Request | Response     ; HTTP/1.1 messages
1377</artwork></figure>
1378<t>
1379   Request (<xref target="request"/>) and Response (<xref target="response"/>) messages use the generic
1380   message format of <xref target="RFC2822"/> for transferring entities (the payload
1381   of the message). Both types of message consist of a start-line, zero
1382   or more header fields (also known as "headers"), an empty line (i.e.,
1383   a line with nothing preceding the CRLF) indicating the end of the
1384   header fields, and possibly a message-body.
1385</t>
1386<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="generic-message"/><iref primary="true" item="Grammar" subitem="start-line"/>
1387  generic-message = start-line
1388                    *(message-header CRLF)
1389                    CRLF
1390                    [ message-body ]
1391  start-line      = Request-Line | Status-Line
1392</artwork></figure>
1393<t>
1394   In the interest of robustness, servers &SHOULD; ignore any empty
1395   line(s) received where a Request-Line is expected. In other words, if
1396   the server is reading the protocol stream at the beginning of a
1397   message and receives a CRLF first, it should ignore the CRLF.
1398</t>
1399<t>
1400   Certain buggy HTTP/1.0 client implementations generate extra CRLF's
1401   after a POST request. To restate what is explicitly forbidden by the
1402   BNF, an HTTP/1.1 client &MUST-NOT; preface or follow a request with an
1403   extra CRLF.
1404</t>
1405</section>
1406
1407<section title="Message Headers" anchor="message.headers">
1408<t>
1409   HTTP header fields, which include general-header (<xref target="general.header.fields"/>),
1410   request-header (&request-header-fields;), response-header (&response-header-fields;), and
1411   entity-header (&entity-header-fields;) fields, follow the same generic format as
1412   that given in <xref target="RFC2822" x:fmt="of" x:sec="2.1"/>. Each header field consists
1413   of a name followed by a colon (":") and the field value. Field names
1414   are case-insensitive. The field value &MAY; be preceded by any amount
1415   of LWS, though a single SP is preferred. Header fields can be
1416   extended over multiple lines by preceding each extra line with at
1417   least one SP or HTAB. Applications ought to follow "common form", where
1418   one is known or indicated, when generating HTTP constructs, since
1419   there might exist some implementations that fail to accept anything
1420   beyond the common forms.
1421</t>
1422<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-header"/><iref primary="true" item="Grammar" subitem="field-name"/><iref primary="true" item="Grammar" subitem="field-value"/><iref primary="true" item="Grammar" subitem="field-content"/>
1423  message-header = field-name ":" [ field-value ]
1424  field-name     = token
1425  field-value    = *( field-content | LWS )
1426  field-content  = &lt;field content&gt;
1427                   ; the OCTETs making up the field-value
1428                   ; and consisting of either *TEXT or combinations
1429                   ; of token, separators, and quoted-string
1430</artwork></figure>
1431<t>
1432   The field-content does not include any leading or trailing LWS:
1433   linear white space occurring before the first non-whitespace
1434   character of the field-value or after the last non-whitespace
1435   character of the field-value. Such leading or trailing LWS &MAY; be
1436   removed without changing the semantics of the field value. Any LWS
1437   that occurs between field-content &MAY; be replaced with a single SP
1438   before interpreting the field value or forwarding the message
1439   downstream.
1440</t>
1441<t>
1442   The order in which header fields with differing field names are
1443   received is not significant. However, it is "good practice" to send
1444   general-header fields first, followed by request-header or response-header
1445   fields, and ending with the entity-header fields.
1446</t>
1447<t>
1448   Multiple message-header fields with the same field-name &MAY; be
1449   present in a message if and only if the entire field-value for that
1450   header field is defined as a comma-separated list [i.e., #(values)].
1451   It &MUST; be possible to combine the multiple header fields into one
1452   "field-name: field-value" pair, without changing the semantics of the
1453   message, by appending each subsequent field-value to the first, each
1454   separated by a comma. The order in which header fields with the same
1455   field-name are received is therefore significant to the
1456   interpretation of the combined field value, and thus a proxy &MUST-NOT;
1457   change the order of these field values when a message is forwarded.
1458</t>
1459</section>
1460
1461<section title="Message Body" anchor="message.body">
1462<t>
1463   The message-body (if any) of an HTTP message is used to carry the
1464   entity-body associated with the request or response. The message-body
1465   differs from the entity-body only when a transfer-coding has been
1466   applied, as indicated by the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).
1467</t>
1468<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-body"/>
1469  message-body = entity-body
1470               | &lt;entity-body encoded as per Transfer-Encoding&gt;
1471</artwork></figure>
1472<t>
1473   Transfer-Encoding &MUST; be used to indicate any transfer-codings
1474   applied by an application to ensure safe and proper transfer of the
1475   message. Transfer-Encoding is a property of the message, not of the
1476   entity, and thus &MAY; be added or removed by any application along the
1477   request/response chain. (However, <xref target="transfer.codings"/> places restrictions on
1478   when certain transfer-codings may be used.)
1479</t>
1480<t>
1481   The rules for when a message-body is allowed in a message differ for
1482   requests and responses.
1483</t>
1484<t>
1485   The presence of a message-body in a request is signaled by the
1486   inclusion of a Content-Length or Transfer-Encoding header field in
1487   the request's message-headers. A message-body &MUST-NOT; be included in
1488   a request if the specification of the request method (&method;)
1489   explicitly disallows an entity-body in requests.
1490   When a request message contains both a message-body of non-zero
1491   length and a method that does not define any semantics for that
1492   request message-body, then an origin server &SHOULD; either ignore
1493   the message-body or respond with an appropriate error message
1494   (e.g., 413).  A proxy or gateway, when presented the same request,
1495   &SHOULD; either forward the request inbound with the message-body or
1496   ignore the message-body when determining a response.
1497</t>
1498<t>
1499   For response messages, whether or not a message-body is included with
1500   a message is dependent on both the request method and the response
1501   status code (<xref target="status.code.and.reason.phrase"/>). All responses to the HEAD request method
1502   &MUST-NOT; include a message-body, even though the presence of entity-header
1503   fields might lead one to believe they do. All 1xx
1504   (informational), 204 (No Content), and 304 (Not Modified) responses
1505   &MUST-NOT; include a message-body. All other responses do include a
1506   message-body, although it &MAY; be of zero length.
1507</t>
1508</section>
1509
1510<section title="Message Length" anchor="message.length">
1511<t>
1512   The transfer-length of a message is the length of the message-body as
1513   it appears in the message; that is, after any transfer-codings have
1514   been applied. When a message-body is included with a message, the
1515   transfer-length of that body is determined by one of the following
1516   (in order of precedence):
1517</t>
1518<t>
1519  <list style="numbers">
1520    <x:lt><t>
1521     Any response message which "&MUST-NOT;" include a message-body (such
1522     as the 1xx, 204, and 304 responses and any response to a HEAD
1523     request) is always terminated by the first empty line after the
1524     header fields, regardless of the entity-header fields present in
1525     the message.
1526    </t></x:lt>
1527    <x:lt><t>
1528     If a Transfer-Encoding header field (<xref target="header.transfer-encoding"/>)
1529     is present, then the transfer-length is
1530     defined by use of the "chunked" transfer-coding (<xref target="transfer.codings"/>),
1531     unless the message is terminated by closing the connection.
1532    </t></x:lt>
1533    <x:lt><t>
1534     If a Content-Length header field (<xref target="header.content-length"/>) is present, its
1535     decimal value in OCTETs represents both the entity-length and the
1536     transfer-length. The Content-Length header field &MUST-NOT; be sent
1537     if these two lengths are different (i.e., if a Transfer-Encoding
1538     header field is present). If a message is received with both a
1539     Transfer-Encoding header field and a Content-Length header field,
1540     the latter &MUST; be ignored.
1541    </t></x:lt>
1542    <x:lt><t>
1543     If the message uses the media type "multipart/byteranges", and the
1544     transfer-length is not otherwise specified, then this self-delimiting
1545     media type defines the transfer-length. This media type
1546     &MUST-NOT; be used unless the sender knows that the recipient can parse
1547     it; the presence in a request of a Range header with multiple byte-range
1548     specifiers from a 1.1 client implies that the client can parse
1549     multipart/byteranges responses.
1550    <list style="empty"><t>
1551       A range header might be forwarded by a 1.0 proxy that does not
1552       understand multipart/byteranges; in this case the server &MUST;
1553       delimit the message using methods defined in items 1, 3 or 5 of
1554       this section.
1555    </t></list>
1556    </t></x:lt>
1557    <x:lt><t>
1558     By the server closing the connection. (Closing the connection
1559     cannot be used to indicate the end of a request body, since that
1560     would leave no possibility for the server to send back a response.)
1561    </t></x:lt>
1562  </list>
1563</t>
1564<t>
1565   For compatibility with HTTP/1.0 applications, HTTP/1.1 requests
1566   containing a message-body &MUST; include a valid Content-Length header
1567   field unless the server is known to be HTTP/1.1 compliant. If a
1568   request contains a message-body and a Content-Length is not given,
1569   the server &SHOULD; respond with 400 (Bad Request) if it cannot
1570   determine the length of the message, or with 411 (Length Required) if
1571   it wishes to insist on receiving a valid Content-Length.
1572</t>
1573<t>
1574   All HTTP/1.1 applications that receive entities &MUST; accept the
1575   "chunked" transfer-coding (<xref target="transfer.codings"/>), thus allowing this mechanism
1576   to be used for messages when the message length cannot be determined
1577   in advance.
1578</t>
1579<t>
1580   Messages &MUST-NOT; include both a Content-Length header field and a
1581   transfer-coding. If the message does include a
1582   transfer-coding, the Content-Length &MUST; be ignored.
1583</t>
1584<t>
1585   When a Content-Length is given in a message where a message-body is
1586   allowed, its field value &MUST; exactly match the number of OCTETs in
1587   the message-body. HTTP/1.1 user agents &MUST; notify the user when an
1588   invalid length is received and detected.
1589</t>
1590</section>
1591
1592<section title="General Header Fields" anchor="general.header.fields">
1593<t>
1594   There are a few header fields which have general applicability for
1595   both request and response messages, but which do not apply to the
1596   entity being transferred. These header fields apply only to the
1597   message being transmitted.
1598</t>
1599<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="general-header"/>
1600  general-header = Cache-Control            ; &header-cache-control;
1601                 | Connection               ; <xref target="header.connection"/>
1602                 | Date                     ; <xref target="header.date"/>
1603                 | Pragma                   ; &header-pragma;
1604                 | Trailer                  ; <xref target="header.trailer"/>
1605                 | Transfer-Encoding        ; <xref target="header.transfer-encoding"/>
1606                 | Upgrade                  ; <xref target="header.upgrade"/>
1607                 | Via                      ; <xref target="header.via"/>
1608                 | Warning                  ; &header-warning;
1609</artwork></figure>
1610<t>
1611   General-header field names can be extended reliably only in
1612   combination with a change in the protocol version. However, new or
1613   experimental header fields may be given the semantics of general
1614   header fields if all parties in the communication recognize them to
1615   be general-header fields. Unrecognized header fields are treated as
1616   entity-header fields.
1617</t>
1618</section>
1619</section>
1620
1621<section title="Request" anchor="request">
1622<t>
1623   A request message from a client to a server includes, within the
1624   first line of that message, the method to be applied to the resource,
1625   the identifier of the resource, and the protocol version in use.
1626</t>
1627<!--                 Host                      ; should be moved here eventually -->
1628<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Request"/>
1629  Request       = Request-Line              ; <xref target="request-line"/>
1630                  *(( general-header        ; <xref target="general.header.fields"/>
1631                   | request-header         ; &request-header-fields;
1632                   | entity-header ) CRLF)  ; &entity-header-fields;
1633                  CRLF
1634                  [ message-body ]          ; <xref target="message.body"/>
1635</artwork></figure>
1636
1637<section title="Request-Line" anchor="request-line">
1638<t>
1639   The Request-Line begins with a method token, followed by the
1640   Request-URI and the protocol version, and ending with CRLF. The
1641   elements are separated by SP characters. No CR or LF is allowed
1642   except in the final CRLF sequence.
1643</t>
1644<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Request-Line"/>
1645  Request-Line   = Method SP Request-URI SP HTTP-Version CRLF
1646</artwork></figure>
1647
1648<section title="Method" anchor="method">
1649<t>
1650   The Method  token indicates the method to be performed on the
1651   resource identified by the Request-URI. The method is case-sensitive.
1652</t>
1653<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/><iref primary="true" item="Grammar" subitem="extension-method"/>
1654  Method         = token
1655</artwork></figure>
1656</section>
1657
1658<section title="Request-URI" anchor="request-uri">
1659<t>
1660   The Request-URI is a Uniform Resource Identifier (<xref target="uri"/>) and
1661   identifies the resource upon which to apply the request.
1662</t>
1663<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Request-URI"/>
1664  Request-URI    = "*"
1665                 | absoluteURI
1666                 | ( path-absolute [ "?" query ] )
1667                 | authority
1668</artwork></figure>
1669<t>
1670   The four options for Request-URI are dependent on the nature of the
1671   request. The asterisk "*" means that the request does not apply to a
1672   particular resource, but to the server itself, and is only allowed
1673   when the method used does not necessarily apply to a resource. One
1674   example would be
1675</t>
1676<figure><artwork type="example">
1677    OPTIONS * HTTP/1.1
1678</artwork></figure>
1679<t>
1680   The absoluteURI form is &REQUIRED; when the request is being made to a
1681   proxy. The proxy is requested to forward the request or service it
1682   from a valid cache, and return the response. Note that the proxy &MAY;
1683   forward the request on to another proxy or directly to the server
1684   specified by the absoluteURI. In order to avoid request loops, a
1685   proxy &MUST; be able to recognize all of its server names, including
1686   any aliases, local variations, and the numeric IP address. An example
1687   Request-Line would be:
1688</t>
1689<figure><artwork type="example">
1690    GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
1691</artwork></figure>
1692<t>
1693   To allow for transition to absoluteURIs in all requests in future
1694   versions of HTTP, all HTTP/1.1 servers &MUST; accept the absoluteURI
1695   form in requests, even though HTTP/1.1 clients will only generate
1696   them in requests to proxies.
1697</t>
1698<t>
1699   The authority form is only used by the CONNECT method (&CONNECT;).
1700</t>
1701<t>
1702   The most common form of Request-URI is that used to identify a
1703   resource on an origin server or gateway. In this case the absolute
1704   path of the URI &MUST; be transmitted (see <xref target="general.syntax"/>, path-absolute) as
1705   the Request-URI, and the network location of the URI (authority) &MUST;
1706   be transmitted in a Host header field. For example, a client wishing
1707   to retrieve the resource above directly from the origin server would
1708   create a TCP connection to port 80 of the host "www.example.org" and send
1709   the lines:
1710</t>
1711<figure><artwork type="example">
1712    GET /pub/WWW/TheProject.html HTTP/1.1
1713    Host: www.example.org
1714</artwork></figure>
1715<t>
1716   followed by the remainder of the Request. Note that the absolute path
1717   cannot be empty; if none is present in the original URI, it &MUST; be
1718   given as "/" (the server root).
1719</t>
1720<t>
1721   The Request-URI is transmitted in the format specified in
1722   <xref target="general.syntax"/>. If the Request-URI is encoded using the "% HEX HEX" encoding
1723   <xref target="RFC2396"/>, the origin server &MUST; decode the Request-URI in order to
1724   properly interpret the request. Servers &SHOULD; respond to invalid
1725   Request-URIs with an appropriate status code.
1726</t>
1727<t>
1728   A transparent proxy &MUST-NOT; rewrite the "path-absolute" part of the
1729   received Request-URI when forwarding it to the next inbound server,
1730   except as noted above to replace a null path-absolute with "/".
1731</t>
1732<t>
1733  <list><t>
1734      <x:h>Note:</x:h> The "no rewrite" rule prevents the proxy from changing the
1735      meaning of the request when the origin server is improperly using
1736      a non-reserved URI character for a reserved purpose.  Implementors
1737      should be aware that some pre-HTTP/1.1 proxies have been known to
1738      rewrite the Request-URI.
1739  </t></list>
1740</t>
1741</section>
1742</section>
1743
1744<section title="The Resource Identified by a Request" anchor="the.resource.identified.by.a.request">
1745<t>
1746   The exact resource identified by an Internet request is determined by
1747   examining both the Request-URI and the Host header field.
1748</t>
1749<t>
1750   An origin server that does not allow resources to differ by the
1751   requested host &MAY; ignore the Host header field value when
1752   determining the resource identified by an HTTP/1.1 request. (But see
1753   <xref target="changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses"/>
1754   for other requirements on Host support in HTTP/1.1.)
1755</t>
1756<t>
1757   An origin server that does differentiate resources based on the host
1758   requested (sometimes referred to as virtual hosts or vanity host
1759   names) &MUST; use the following rules for determining the requested
1760   resource on an HTTP/1.1 request:
1761  <list style="numbers">
1762    <t>If Request-URI is an absoluteURI, the host is part of the
1763     Request-URI. Any Host header field value in the request &MUST; be
1764     ignored.</t>
1765    <t>If the Request-URI is not an absoluteURI, and the request includes
1766     a Host header field, the host is determined by the Host header
1767     field value.</t>
1768    <t>If the host as determined by rule 1 or 2 is not a valid host on
1769     the server, the response &MUST; be a 400 (Bad Request) error message.</t>
1770  </list>
1771</t>
1772<t>
1773   Recipients of an HTTP/1.0 request that lacks a Host header field &MAY;
1774   attempt to use heuristics (e.g., examination of the URI path for
1775   something unique to a particular host) in order to determine what
1776   exact resource is being requested.
1777</t>
1778</section>
1779
1780</section>
1781
1782
1783<section title="Response" anchor="response">
1784<t>
1785   After receiving and interpreting a request message, a server responds
1786   with an HTTP response message.
1787</t>
1788<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Response"/>
1789  Response      = Status-Line               ; <xref target="status-line"/>
1790                  *(( general-header        ; <xref target="general.header.fields"/>
1791                   | response-header        ; &response-header-fields;
1792                   | entity-header ) CRLF)  ; &entity-header-fields;
1793                  CRLF
1794                  [ message-body ]          ; <xref target="message.body"/>
1795</artwork></figure>
1796
1797<section title="Status-Line" anchor="status-line">
1798<t>
1799   The first line of a Response message is the Status-Line, consisting
1800   of the protocol version followed by a numeric status code and its
1801   associated textual phrase, with each element separated by SP
1802   characters. No CR or LF is allowed except in the final CRLF sequence.
1803</t>
1804<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Status-Line"/>
1805  Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
1806</artwork></figure>
1807
1808<section title="Status Code and Reason Phrase" anchor="status.code.and.reason.phrase">
1809<t>
1810   The Status-Code element is a 3-digit integer result code of the
1811   attempt to understand and satisfy the request. These codes are fully
1812   defined in &status-codes;.  The Reason Phrase exists for the sole
1813   purpose of providing a textual description associated with the numeric
1814   status code, out of deference to earlier Internet application protocols
1815   that were more frequently used with interactive text clients.
1816   A client &SHOULD; ignore the content of the Reason Phrase.
1817</t>
1818<t>
1819   The first digit of the Status-Code defines the class of response. The
1820   last two digits do not have any categorization role. There are 5
1821   values for the first digit:
1822  <list style="symbols">
1823    <t>
1824      1xx: Informational - Request received, continuing process
1825    </t>
1826    <t>
1827      2xx: Success - The action was successfully received,
1828        understood, and accepted
1829    </t>
1830    <t>
1831      3xx: Redirection - Further action must be taken in order to
1832        complete the request
1833    </t>
1834    <t>
1835      4xx: Client Error - The request contains bad syntax or cannot
1836        be fulfilled
1837    </t>
1838    <t>
1839      5xx: Server Error - The server failed to fulfill an apparently
1840        valid request
1841    </t>
1842  </list>
1843</t>
1844<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Status-Code"/><iref primary="true" item="Grammar" subitem="extension-code"/><iref primary="true" item="Grammar" subitem="Reason-Phrase"/>
1845  Status-Code    = 3DIGIT
1846  Reason-Phrase  = *&lt;TEXT, excluding CR, LF&gt;
1847</artwork></figure>
1848</section>
1849</section>
1850
1851</section>
1852
1853
1854<section title="Connections" anchor="connections">
1855
1856<section title="Persistent Connections" anchor="persistent.connections">
1857
1858<section title="Purpose" anchor="persistent.purpose">
1859<t>
1860   Prior to persistent connections, a separate TCP connection was
1861   established to fetch each URL, increasing the load on HTTP servers
1862   and causing congestion on the Internet. The use of inline images and
1863   other associated data often require a client to make multiple
1864   requests of the same server in a short amount of time. Analysis of
1865   these performance problems and results from a prototype
1866   implementation are available <xref target="Pad1995"/> <xref target="Spe"/>. Implementation experience and
1867   measurements of actual HTTP/1.1 (<xref target="RFC2068" x:fmt="none">RFC 2068</xref>) implementations show good
1868   results <xref target="Nie1997"/>. Alternatives have also been explored, for example,
1869   T/TCP <xref target="Tou1998"/>.
1870</t>
1871<t>
1872   Persistent HTTP connections have a number of advantages:
1873  <list style="symbols">
1874      <t>
1875        By opening and closing fewer TCP connections, CPU time is saved
1876        in routers and hosts (clients, servers, proxies, gateways,
1877        tunnels, or caches), and memory used for TCP protocol control
1878        blocks can be saved in hosts.
1879      </t>
1880      <t>
1881        HTTP requests and responses can be pipelined on a connection.
1882        Pipelining allows a client to make multiple requests without
1883        waiting for each response, allowing a single TCP connection to
1884        be used much more efficiently, with much lower elapsed time.
1885      </t>
1886      <t>
1887        Network congestion is reduced by reducing the number of packets
1888        caused by TCP opens, and by allowing TCP sufficient time to
1889        determine the congestion state of the network.
1890      </t>
1891      <t>
1892        Latency on subsequent requests is reduced since there is no time
1893        spent in TCP's connection opening handshake.
1894      </t>
1895      <t>
1896        HTTP can evolve more gracefully, since errors can be reported
1897        without the penalty of closing the TCP connection. Clients using
1898        future versions of HTTP might optimistically try a new feature,
1899        but if communicating with an older server, retry with old
1900        semantics after an error is reported.
1901      </t>
1902    </list>
1903</t>
1904<t>
1905   HTTP implementations &SHOULD; implement persistent connections.
1906</t>
1907</section>
1908
1909<section title="Overall Operation" anchor="persistent.overall">
1910<t>
1911   A significant difference between HTTP/1.1 and earlier versions of
1912   HTTP is that persistent connections are the default behavior of any
1913   HTTP connection. That is, unless otherwise indicated, the client
1914   &SHOULD; assume that the server will maintain a persistent connection,
1915   even after error responses from the server.
1916</t>
1917<t>
1918   Persistent connections provide a mechanism by which a client and a
1919   server can signal the close of a TCP connection. This signaling takes
1920   place using the Connection header field (<xref target="header.connection"/>). Once a close
1921   has been signaled, the client &MUST-NOT; send any more requests on that
1922   connection.
1923</t>
1924
1925<section title="Negotiation" anchor="persistent.negotiation">
1926<t>
1927   An HTTP/1.1 server &MAY; assume that a HTTP/1.1 client intends to
1928   maintain a persistent connection unless a Connection header including
1929   the connection-token "close" was sent in the request. If the server
1930   chooses to close the connection immediately after sending the
1931   response, it &SHOULD; send a Connection header including the
1932   connection-token close.
1933</t>
1934<t>
1935   An HTTP/1.1 client &MAY; expect a connection to remain open, but would
1936   decide to keep it open based on whether the response from a server
1937   contains a Connection header with the connection-token close. In case
1938   the client does not want to maintain a connection for more than that
1939   request, it &SHOULD; send a Connection header including the
1940   connection-token close.
1941</t>
1942<t>
1943   If either the client or the server sends the close token in the
1944   Connection header, that request becomes the last one for the
1945   connection.
1946</t>
1947<t>
1948   Clients and servers &SHOULD-NOT;  assume that a persistent connection is
1949   maintained for HTTP versions less than 1.1 unless it is explicitly
1950   signaled. See <xref target="compatibility.with.http.1.0.persistent.connections"/> for more information on backward
1951   compatibility with HTTP/1.0 clients.
1952</t>
1953<t>
1954   In order to remain persistent, all messages on the connection &MUST;
1955   have a self-defined message length (i.e., one not defined by closure
1956   of the connection), as described in <xref target="message.length"/>.
1957</t>
1958</section>
1959
1960<section title="Pipelining" anchor="pipelining">
1961<t>
1962   A client that supports persistent connections &MAY; "pipeline" its
1963   requests (i.e., send multiple requests without waiting for each
1964   response). A server &MUST; send its responses to those requests in the
1965   same order that the requests were received.
1966</t>
1967<t>
1968   Clients which assume persistent connections and pipeline immediately
1969   after connection establishment &SHOULD; be prepared to retry their
1970   connection if the first pipelined attempt fails. If a client does
1971   such a retry, it &MUST-NOT; pipeline before it knows the connection is
1972   persistent. Clients &MUST; also be prepared to resend their requests if
1973   the server closes the connection before sending all of the
1974   corresponding responses.
1975</t>
1976<t>
1977   Clients &SHOULD-NOT;  pipeline requests using non-idempotent methods or
1978   non-idempotent sequences of methods (see &idempotent-methods;). Otherwise, a
1979   premature termination of the transport connection could lead to
1980   indeterminate results. A client wishing to send a non-idempotent
1981   request &SHOULD; wait to send that request until it has received the
1982   response status for the previous request.
1983</t>
1984</section>
1985</section>
1986
1987<section title="Proxy Servers" anchor="persistent.proxy">
1988<t>
1989   It is especially important that proxies correctly implement the
1990   properties of the Connection header field as specified in <xref target="header.connection"/>.
1991</t>
1992<t>
1993   The proxy server &MUST; signal persistent connections separately with
1994   its clients and the origin servers (or other proxy servers) that it
1995   connects to. Each persistent connection applies to only one transport
1996   link.
1997</t>
1998<t>
1999   A proxy server &MUST-NOT; establish a HTTP/1.1 persistent connection
2000   with an HTTP/1.0 client (but see <xref target="RFC2068"/> for information and
2001   discussion of the problems with the Keep-Alive header implemented by
2002   many HTTP/1.0 clients).
2003</t>
2004</section>
2005
2006<section title="Practical Considerations" anchor="persistent.practical">
2007<t>
2008   Servers will usually have some time-out value beyond which they will
2009   no longer maintain an inactive connection. Proxy servers might make
2010   this a higher value since it is likely that the client will be making
2011   more connections through the same server. The use of persistent
2012   connections places no requirements on the length (or existence) of
2013   this time-out for either the client or the server.
2014</t>
2015<t>
2016   When a client or server wishes to time-out it &SHOULD; issue a graceful
2017   close on the transport connection. Clients and servers &SHOULD; both
2018   constantly watch for the other side of the transport close, and
2019   respond to it as appropriate. If a client or server does not detect
2020   the other side's close promptly it could cause unnecessary resource
2021   drain on the network.
2022</t>
2023<t>
2024   A client, server, or proxy &MAY; close the transport connection at any
2025   time. For example, a client might have started to send a new request
2026   at the same time that the server has decided to close the "idle"
2027   connection. From the server's point of view, the connection is being
2028   closed while it was idle, but from the client's point of view, a
2029   request is in progress.
2030</t>
2031<t>
2032   This means that clients, servers, and proxies &MUST; be able to recover
2033   from asynchronous close events. Client software &SHOULD; reopen the
2034   transport connection and retransmit the aborted sequence of requests
2035   without user interaction so long as the request sequence is
2036   idempotent (see &idempotent-methods;). Non-idempotent methods or sequences
2037   &MUST-NOT; be automatically retried, although user agents &MAY; offer a
2038   human operator the choice of retrying the request(s). Confirmation by
2039   user-agent software with semantic understanding of the application
2040   &MAY; substitute for user confirmation. The automatic retry &SHOULD-NOT; 
2041   be repeated if the second sequence of requests fails.
2042</t>
2043<t>
2044   Servers &SHOULD; always respond to at least one request per connection,
2045   if at all possible. Servers &SHOULD-NOT;  close a connection in the
2046   middle of transmitting a response, unless a network or client failure
2047   is suspected.
2048</t>
2049<t>
2050   Clients that use persistent connections &SHOULD; limit the number of
2051   simultaneous connections that they maintain to a given server. A
2052   single-user client &SHOULD-NOT; maintain more than 2 connections with
2053   any server or proxy. A proxy &SHOULD; use up to 2*N connections to
2054   another server or proxy, where N is the number of simultaneously
2055   active users. These guidelines are intended to improve HTTP response
2056   times and avoid congestion.
2057</t>
2058</section>
2059</section>
2060
2061<section title="Message Transmission Requirements" anchor="message.transmission.requirements">
2062
2063<section title="Persistent Connections and Flow Control" anchor="persistent.flow">
2064<t>
2065   HTTP/1.1 servers &SHOULD; maintain persistent connections and use TCP's
2066   flow control mechanisms to resolve temporary overloads, rather than
2067   terminating connections with the expectation that clients will retry.
2068   The latter technique can exacerbate network congestion.
2069</t>
2070</section>
2071
2072<section title="Monitoring Connections for Error Status Messages" anchor="persistent.monitor">
2073<t>
2074   An HTTP/1.1 (or later) client sending a message-body &SHOULD; monitor
2075   the network connection for an error status while it is transmitting
2076   the request. If the client sees an error status, it &SHOULD;
2077   immediately cease transmitting the body. If the body is being sent
2078   using a "chunked" encoding (<xref target="transfer.codings"/>), a zero length chunk and
2079   empty trailer &MAY; be used to prematurely mark the end of the message.
2080   If the body was preceded by a Content-Length header, the client &MUST;
2081   close the connection.
2082</t>
2083</section>
2084
2085<section title="Use of the 100 (Continue) Status" anchor="use.of.the.100.status">
2086<t>
2087   The purpose of the 100 (Continue) status (see &status-100;) is to
2088   allow a client that is sending a request message with a request body
2089   to determine if the origin server is willing to accept the request
2090   (based on the request headers) before the client sends the request
2091   body. In some cases, it might either be inappropriate or highly
2092   inefficient for the client to send the body if the server will reject
2093   the message without looking at the body.
2094</t>
2095<t>
2096   Requirements for HTTP/1.1 clients:
2097  <list style="symbols">
2098    <t>
2099        If a client will wait for a 100 (Continue) response before
2100        sending the request body, it &MUST; send an Expect request-header
2101        field (&header-expect;) with the "100-continue" expectation.
2102    </t>
2103    <t>
2104        A client &MUST-NOT; send an Expect request-header field (&header-expect;)
2105        with the "100-continue" expectation if it does not intend
2106        to send a request body.
2107    </t>
2108  </list>
2109</t>
2110<t>
2111   Because of the presence of older implementations, the protocol allows
2112   ambiguous situations in which a client may send "Expect: 100-continue"
2113   without receiving either a 417 (Expectation Failed) status
2114   or a 100 (Continue) status. Therefore, when a client sends this
2115   header field to an origin server (possibly via a proxy) from which it
2116   has never seen a 100 (Continue) status, the client &SHOULD-NOT;  wait
2117   for an indefinite period before sending the request body.
2118</t>
2119<t>
2120   Requirements for HTTP/1.1 origin servers:
2121  <list style="symbols">
2122    <t> Upon receiving a request which includes an Expect request-header
2123        field with the "100-continue" expectation, an origin server &MUST;
2124        either respond with 100 (Continue) status and continue to read
2125        from the input stream, or respond with a final status code. The
2126        origin server &MUST-NOT; wait for the request body before sending
2127        the 100 (Continue) response. If it responds with a final status
2128        code, it &MAY; close the transport connection or it &MAY; continue
2129        to read and discard the rest of the request.  It &MUST-NOT;
2130        perform the requested method if it returns a final status code.
2131    </t>
2132    <t> An origin server &SHOULD-NOT;  send a 100 (Continue) response if
2133        the request message does not include an Expect request-header
2134        field with the "100-continue" expectation, and &MUST-NOT; send a
2135        100 (Continue) response if such a request comes from an HTTP/1.0
2136        (or earlier) client. There is an exception to this rule: for
2137        compatibility with <xref target="RFC2068"/>, a server &MAY; send a 100 (Continue)
2138        status in response to an HTTP/1.1 PUT or POST request that does
2139        not include an Expect request-header field with the "100-continue"
2140        expectation. This exception, the purpose of which is
2141        to minimize any client processing delays associated with an
2142        undeclared wait for 100 (Continue) status, applies only to
2143        HTTP/1.1 requests, and not to requests with any other HTTP-version
2144        value.
2145    </t>
2146    <t> An origin server &MAY; omit a 100 (Continue) response if it has
2147        already received some or all of the request body for the
2148        corresponding request.
2149    </t>
2150    <t> An origin server that sends a 100 (Continue) response &MUST;
2151    ultimately send a final status code, once the request body is
2152        received and processed, unless it terminates the transport
2153        connection prematurely.
2154    </t>
2155    <t> If an origin server receives a request that does not include an
2156        Expect request-header field with the "100-continue" expectation,
2157        the request includes a request body, and the server responds
2158        with a final status code before reading the entire request body
2159        from the transport connection, then the server &SHOULD-NOT;  close
2160        the transport connection until it has read the entire request,
2161        or until the client closes the connection. Otherwise, the client
2162        might not reliably receive the response message. However, this
2163        requirement is not be construed as preventing a server from
2164        defending itself against denial-of-service attacks, or from
2165        badly broken client implementations.
2166      </t>
2167    </list>
2168</t>
2169<t>
2170   Requirements for HTTP/1.1 proxies:
2171  <list style="symbols">
2172    <t> If a proxy receives a request that includes an Expect request-header
2173        field with the "100-continue" expectation, and the proxy
2174        either knows that the next-hop server complies with HTTP/1.1 or
2175        higher, or does not know the HTTP version of the next-hop
2176        server, it &MUST; forward the request, including the Expect header
2177        field.
2178    </t>
2179    <t> If the proxy knows that the version of the next-hop server is
2180        HTTP/1.0 or lower, it &MUST-NOT; forward the request, and it &MUST;
2181        respond with a 417 (Expectation Failed) status.
2182    </t>
2183    <t> Proxies &SHOULD; maintain a cache recording the HTTP version
2184        numbers received from recently-referenced next-hop servers.
2185    </t>
2186    <t> A proxy &MUST-NOT; forward a 100 (Continue) response if the
2187        request message was received from an HTTP/1.0 (or earlier)
2188        client and did not include an Expect request-header field with
2189        the "100-continue" expectation. This requirement overrides the
2190        general rule for forwarding of 1xx responses (see &status-1xx;).
2191    </t>
2192  </list>
2193</t>
2194</section>
2195
2196<section title="Client Behavior if Server Prematurely Closes Connection" anchor="connection.premature">
2197<t>
2198   If an HTTP/1.1 client sends a request which includes a request body,
2199   but which does not include an Expect request-header field with the
2200   "100-continue" expectation, and if the client is not directly
2201   connected to an HTTP/1.1 origin server, and if the client sees the
2202   connection close before receiving any status from the server, the
2203   client &SHOULD; retry the request.  If the client does retry this
2204   request, it &MAY; use the following "binary exponential backoff"
2205   algorithm to be assured of obtaining a reliable response:
2206  <list style="numbers">
2207    <t>
2208      Initiate a new connection to the server
2209    </t>
2210    <t>
2211      Transmit the request-headers
2212    </t>
2213    <t>
2214      Initialize a variable R to the estimated round-trip time to the
2215         server (e.g., based on the time it took to establish the
2216         connection), or to a constant value of 5 seconds if the round-trip
2217         time is not available.
2218    </t>
2219    <t>
2220       Compute T = R * (2**N), where N is the number of previous
2221         retries of this request.
2222    </t>
2223    <t>
2224       Wait either for an error response from the server, or for T
2225         seconds (whichever comes first)
2226    </t>
2227    <t>
2228       If no error response is received, after T seconds transmit the
2229         body of the request.
2230    </t>
2231    <t>
2232       If client sees that the connection is closed prematurely,
2233         repeat from step 1 until the request is accepted, an error
2234         response is received, or the user becomes impatient and
2235         terminates the retry process.
2236    </t>
2237  </list>
2238</t>
2239<t>
2240   If at any point an error status is received, the client
2241  <list style="symbols">
2242      <t>&SHOULD-NOT;  continue and</t>
2243
2244      <t>&SHOULD; close the connection if it has not completed sending the
2245        request message.</t>
2246    </list>
2247</t>
2248</section>
2249</section>
2250</section>
2251
2252
2253<section title="Header Field Definitions" anchor="header.fields">
2254<t>
2255   This section defines the syntax and semantics of HTTP/1.1 header fields
2256   related to message framing and transport protocols.
2257</t>
2258<t>
2259   For entity-header fields, both sender and recipient refer to either the
2260   client or the server, depending on who sends and who receives the entity.
2261</t>
2262
2263<section title="Connection" anchor="header.connection">
2264  <iref primary="true" item="Connection header" x:for-anchor=""/>
2265  <iref primary="true" item="Headers" subitem="Connection" x:for-anchor=""/>
2266<t>
2267   The Connection general-header field allows the sender to specify
2268   options that are desired for that particular connection and &MUST-NOT;
2269   be communicated by proxies over further connections.
2270</t>
2271<t>
2272   The Connection header has the following grammar:
2273</t>
2274<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="connection-token"/>
2275  Connection = "Connection" ":" 1#(connection-token)
2276  connection-token  = token
2277</artwork></figure>
2278<t>
2279   HTTP/1.1 proxies &MUST; parse the Connection header field before a
2280   message is forwarded and, for each connection-token in this field,
2281   remove any header field(s) from the message with the same name as the
2282   connection-token. Connection options are signaled by the presence of
2283   a connection-token in the Connection header field, not by any
2284   corresponding additional header field(s), since the additional header
2285   field may not be sent if there are no parameters associated with that
2286   connection option.
2287</t>
2288<t>
2289   Message headers listed in the Connection header &MUST-NOT; include
2290   end-to-end headers, such as Cache-Control.
2291</t>
2292<t>
2293   HTTP/1.1 defines the "close" connection option for the sender to
2294   signal that the connection will be closed after completion of the
2295   response. For example,
2296</t>
2297<figure><artwork type="example">
2298    Connection: close
2299</artwork></figure>
2300<t>
2301   in either the request or the response header fields indicates that
2302   the connection &SHOULD-NOT;  be considered `persistent' (<xref target="persistent.connections"/>)
2303   after the current request/response is complete.
2304</t>
2305<t>
2306   An HTTP/1.1 client that does not support persistent connections &MUST;
2307   include the "close" connection option in every request message.
2308</t>
2309<t>
2310   An HTTP/1.1 server that does not support persistent connections &MUST;
2311   include the "close" connection option in every response message that
2312   does not have a 1xx (informational) status code.
2313</t>
2314<t>
2315   A system receiving an HTTP/1.0 (or lower-version) message that
2316   includes a Connection header &MUST;, for each connection-token in this
2317   field, remove and ignore any header field(s) from the message with
2318   the same name as the connection-token. This protects against mistaken
2319   forwarding of such header fields by pre-HTTP/1.1 proxies. See <xref target="compatibility.with.http.1.0.persistent.connections"/>.
2320</t>
2321</section>
2322
2323<section title="Content-Length" anchor="header.content-length">
2324  <iref primary="true" item="Content-Length header" x:for-anchor=""/>
2325  <iref primary="true" item="Headers" subitem="Content-Length" x:for-anchor=""/>
2326<t>
2327   The Content-Length entity-header field indicates the size of the
2328   entity-body, in decimal number of OCTETs, sent to the recipient or,
2329   in the case of the HEAD method, the size of the entity-body that
2330   would have been sent had the request been a GET.
2331</t>
2332<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/>
2333  Content-Length    = "Content-Length" ":" 1*DIGIT
2334</artwork></figure>
2335<t>
2336   An example is
2337</t>
2338<figure><artwork type="example">
2339    Content-Length: 3495
2340</artwork></figure>
2341<t>
2342   Applications &SHOULD; use this field to indicate the transfer-length of
2343   the message-body, unless this is prohibited by the rules in <xref target="message.length"/>.
2344</t>
2345<t>
2346   Any Content-Length greater than or equal to zero is a valid value.
2347   <xref target="message.length"/> describes how to determine the length of a message-body
2348   if a Content-Length is not given.
2349</t>
2350<t>
2351   Note that the meaning of this field is significantly different from
2352   the corresponding definition in MIME, where it is an optional field
2353   used within the "message/external-body" content-type. In HTTP, it
2354   &SHOULD; be sent whenever the message's length can be determined prior
2355   to being transferred, unless this is prohibited by the rules in
2356   <xref target="message.length"/>.
2357</t>
2358</section>
2359
2360<section title="Date" anchor="header.date">
2361  <iref primary="true" item="Date header" x:for-anchor=""/>
2362  <iref primary="true" item="Headers" subitem="Date" x:for-anchor=""/>
2363<t>
2364   The Date general-header field represents the date and time at which
2365   the message was originated, having the same semantics as orig-date in
2366   <xref target="RFC2822" x:fmt="of" x:sec="3.6.1"/>. The field value is an HTTP-date, as described in <xref target="full.date"/>;
2367   it &MUST; be sent in rfc1123-date format.
2368</t>
2369<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Date"/>
2370  Date  = "Date" ":" HTTP-date
2371</artwork></figure>
2372<t>
2373   An example is
2374</t>
2375<figure><artwork type="example">
2376    Date: Tue, 15 Nov 1994 08:12:31 GMT
2377</artwork></figure>
2378<t>
2379   Origin servers &MUST; include a Date header field in all responses,
2380   except in these cases:
2381  <list style="numbers">
2382      <t>If the response status code is 100 (Continue) or 101 (Switching
2383         Protocols), the response &MAY; include a Date header field, at
2384         the server's option.</t>
2385
2386      <t>If the response status code conveys a server error, e.g. 500
2387         (Internal Server Error) or 503 (Service Unavailable), and it is
2388         inconvenient or impossible to generate a valid Date.</t>
2389
2390      <t>If the server does not have a clock that can provide a
2391         reasonable approximation of the current time, its responses
2392         &MUST-NOT; include a Date header field. In this case, the rules
2393         in <xref target="clockless.origin.server.operation"/> &MUST; be followed.</t>
2394  </list>
2395</t>
2396<t>
2397   A received message that does not have a Date header field &MUST; be
2398   assigned one by the recipient if the message will be cached by that
2399   recipient or gatewayed via a protocol which requires a Date. An HTTP
2400   implementation without a clock &MUST-NOT; cache responses without
2401   revalidating them on every use. An HTTP cache, especially a shared
2402   cache, &SHOULD; use a mechanism, such as NTP <xref target="RFC1305"/>, to synchronize its
2403   clock with a reliable external standard.
2404</t>
2405<t>
2406   Clients &SHOULD; only send a Date header field in messages that include
2407   an entity-body, as in the case of the PUT and POST requests, and even
2408   then it is optional. A client without a clock &MUST-NOT; send a Date
2409   header field in a request.
2410</t>
2411<t>
2412   The HTTP-date sent in a Date header &SHOULD-NOT;  represent a date and
2413   time subsequent to the generation of the message. It &SHOULD; represent
2414   the best available approximation of the date and time of message
2415   generation, unless the implementation has no means of generating a
2416   reasonably accurate date and time. In theory, the date ought to
2417   represent the moment just before the entity is generated. In
2418   practice, the date can be generated at any time during the message
2419   origination without affecting its semantic value.
2420</t>
2421
2422<section title="Clockless Origin Server Operation" anchor="clockless.origin.server.operation">
2423<t>
2424   Some origin server implementations might not have a clock available.
2425   An origin server without a clock &MUST-NOT; assign Expires or Last-Modified
2426   values to a response, unless these values were associated
2427   with the resource by a system or user with a reliable clock. It &MAY;
2428   assign an Expires value that is known, at or before server
2429   configuration time, to be in the past (this allows "pre-expiration"
2430   of responses without storing separate Expires values for each
2431   resource).
2432</t>
2433</section>
2434</section>
2435
2436<section title="Host" anchor="header.host">
2437  <iref primary="true" item="Host header" x:for-anchor=""/>
2438  <iref primary="true" item="Headers" subitem="Host" x:for-anchor=""/>
2439<t>
2440   The Host request-header field specifies the Internet host and port
2441   number of the resource being requested, as obtained from the original
2442   URI given by the user or referring resource (generally an HTTP URL,
2443   as described in <xref target="http.url"/>). The Host field value &MUST; represent
2444   the naming authority of the origin server or gateway given by the
2445   original URL. This allows the origin server or gateway to
2446   differentiate between internally-ambiguous URLs, such as the root "/"
2447   URL of a server for multiple host names on a single IP address.
2448</t>
2449<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Host"/>
2450  Host = "Host" ":" uri-host [ ":" port ] ; <xref target="http.url"/>
2451</artwork></figure>
2452<t>
2453   A "host" without any trailing port information implies the default
2454   port for the service requested (e.g., "80" for an HTTP URL). For
2455   example, a request on the origin server for
2456   &lt;http://www.example.org/pub/WWW/&gt; would properly include:
2457</t>
2458<figure><artwork type="example">
2459    GET /pub/WWW/ HTTP/1.1
2460    Host: www.example.org
2461</artwork></figure>
2462<t>
2463   A client &MUST; include a Host header field in all HTTP/1.1 request
2464   messages. If the requested URI does not include an Internet host
2465   name for the service being requested, then the Host header field &MUST;
2466   be given with an empty value. An HTTP/1.1 proxy &MUST; ensure that any
2467   request message it forwards does contain an appropriate Host header
2468   field that identifies the service being requested by the proxy. All
2469   Internet-based HTTP/1.1 servers &MUST; respond with a 400 (Bad Request)
2470   status code to any HTTP/1.1 request message which lacks a Host header
2471   field.
2472</t>
2473<t>
2474   See Sections <xref target="the.resource.identified.by.a.request" format="counter"/>
2475   and <xref target="changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" format="counter"/>
2476   for other requirements relating to Host.
2477</t>
2478</section>
2479
2480<section title="TE" anchor="header.te">
2481  <iref primary="true" item="TE header" x:for-anchor=""/>
2482  <iref primary="true" item="Headers" subitem="TE" x:for-anchor=""/>
2483<t>
2484   The TE request-header field indicates what extension transfer-codings
2485   it is willing to accept in the response and whether or not it is
2486   willing to accept trailer fields in a chunked transfer-coding. Its
2487   value may consist of the keyword "trailers" and/or a comma-separated
2488   list of extension transfer-coding names with optional accept
2489   parameters (as described in <xref target="transfer.codings"/>).
2490</t>
2491<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TE"/><iref primary="true" item="Grammar" subitem="t-codings"/>
2492  TE        = "TE" ":" #( t-codings )
2493  t-codings = "trailers" | ( transfer-extension [ accept-params ] )
2494</artwork></figure>
2495<t>
2496   The presence of the keyword "trailers" indicates that the client is
2497   willing to accept trailer fields in a chunked transfer-coding, as
2498   defined in <xref target="chunked.transfer.encoding"/>. This keyword is reserved for use with
2499   transfer-coding values even though it does not itself represent a
2500   transfer-coding.
2501</t>
2502<t>
2503   Examples of its use are:
2504</t>
2505<figure><artwork type="example">
2506    TE: deflate
2507    TE:
2508    TE: trailers, deflate;q=0.5
2509</artwork></figure>
2510<t>
2511   The TE header field only applies to the immediate connection.
2512   Therefore, the keyword &MUST; be supplied within a Connection header
2513   field (<xref target="header.connection"/>) whenever TE is present in an HTTP/1.1 message.
2514</t>
2515<t>
2516   A server tests whether a transfer-coding is acceptable, according to
2517   a TE field, using these rules:
2518  <list style="numbers">
2519    <x:lt>
2520      <t>The "chunked" transfer-coding is always acceptable. If the
2521         keyword "trailers" is listed, the client indicates that it is
2522         willing to accept trailer fields in the chunked response on
2523         behalf of itself and any downstream clients. The implication is
2524         that, if given, the client is stating that either all
2525         downstream clients are willing to accept trailer fields in the
2526         forwarded response, or that it will attempt to buffer the
2527         response on behalf of downstream recipients.
2528      </t><t>
2529         <x:h>Note:</x:h> HTTP/1.1 does not define any means to limit the size of a
2530         chunked response such that a client can be assured of buffering
2531         the entire response.</t>
2532    </x:lt>
2533    <x:lt>
2534      <t>If the transfer-coding being tested is one of the transfer-codings
2535         listed in the TE field, then it is acceptable unless it
2536         is accompanied by a qvalue of 0. (As defined in &qvalue;, a
2537         qvalue of 0 means "not acceptable.")</t>
2538    </x:lt>
2539    <x:lt>
2540      <t>If multiple transfer-codings are acceptable, then the
2541         acceptable transfer-coding with the highest non-zero qvalue is
2542         preferred.  The "chunked" transfer-coding always has a qvalue
2543         of 1.</t>
2544    </x:lt>
2545  </list>
2546</t>
2547<t>
2548   If the TE field-value is empty or if no TE field is present, the only
2549   transfer-coding  is "chunked". A message with no transfer-coding is
2550   always acceptable.
2551</t>
2552</section>
2553
2554<section title="Trailer" anchor="header.trailer">
2555  <iref primary="true" item="Trailer header" x:for-anchor=""/>
2556  <iref primary="true" item="Headers" subitem="Trailer" x:for-anchor=""/>
2557<t>
2558   The Trailer general field value indicates that the given set of
2559   header fields is present in the trailer of a message encoded with
2560   chunked transfer-coding.
2561</t>
2562<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Trailer"/>
2563  Trailer  = "Trailer" ":" 1#field-name
2564</artwork></figure>
2565<t>
2566   An HTTP/1.1 message &SHOULD; include a Trailer header field in a
2567   message using chunked transfer-coding with a non-empty trailer. Doing
2568   so allows the recipient to know which header fields to expect in the
2569   trailer.
2570</t>
2571<t>
2572   If no Trailer header field is present, the trailer &SHOULD-NOT;  include
2573   any header fields. See <xref target="chunked.transfer.encoding"/> for restrictions on the use of
2574   trailer fields in a "chunked" transfer-coding.
2575</t>
2576<t>
2577   Message header fields listed in the Trailer header field &MUST-NOT;
2578   include the following header fields:
2579  <list style="symbols">
2580    <t>Transfer-Encoding</t>
2581    <t>Content-Length</t>
2582    <t>Trailer</t>
2583  </list>
2584</t>
2585</section>
2586
2587<section title="Transfer-Encoding" anchor="header.transfer-encoding">
2588  <iref primary="true" item="Transfer-Encoding header" x:for-anchor=""/>
2589  <iref primary="true" item="Headers" subitem="Transfer-Encoding" x:for-anchor=""/>
2590<t>
2591   The Transfer-Encoding general-header field indicates what (if any)
2592   type of transformation has been applied to the message body in order
2593   to safely transfer it between the sender and the recipient. This
2594   differs from the content-coding in that the transfer-coding is a
2595   property of the message, not of the entity.
2596</t>
2597<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Transfer-Encoding"/>
2598  Transfer-Encoding       = "Transfer-Encoding" ":" 1#transfer-coding
2599</artwork></figure>
2600<t>
2601   Transfer-codings are defined in <xref target="transfer.codings"/>. An example is:
2602</t>
2603<figure><artwork type="example">
2604  Transfer-Encoding: chunked
2605</artwork></figure>
2606<t>
2607   If multiple encodings have been applied to an entity, the transfer-codings
2608   &MUST; be listed in the order in which they were applied.
2609   Additional information about the encoding parameters &MAY; be provided
2610   by other entity-header fields not defined by this specification.
2611</t>
2612<t>
2613   Many older HTTP/1.0 applications do not understand the Transfer-Encoding
2614   header.
2615</t>
2616</section>
2617
2618<section title="Upgrade" anchor="header.upgrade">
2619  <iref primary="true" item="Upgrade header" x:for-anchor=""/>
2620  <iref primary="true" item="Headers" subitem="Upgrade" x:for-anchor=""/>
2621<t>
2622   The Upgrade general-header allows the client to specify what
2623   additional communication protocols it supports and would like to use
2624   if the server finds it appropriate to switch protocols. The server
2625   &MUST; use the Upgrade header field within a 101 (Switching Protocols)
2626   response to indicate which protocol(s) are being switched.
2627</t>
2628<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Upgrade"/>
2629  Upgrade        = "Upgrade" ":" 1#product
2630</artwork></figure>
2631<t>
2632   For example,
2633</t>
2634<figure><artwork type="example">
2635    Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
2636</artwork></figure>
2637<t>
2638   The Upgrade header field is intended to provide a simple mechanism
2639   for transition from HTTP/1.1 to some other, incompatible protocol. It
2640   does so by allowing the client to advertise its desire to use another
2641   protocol, such as a later version of HTTP with a higher major version
2642   number, even though the current request has been made using HTTP/1.1.
2643   This eases the difficult transition between incompatible protocols by
2644   allowing the client to initiate a request in the more commonly
2645   supported protocol while indicating to the server that it would like
2646   to use a "better" protocol if available (where "better" is determined
2647   by the server, possibly according to the nature of the method and/or
2648   resource being requested).
2649</t>
2650<t>
2651   The Upgrade header field only applies to switching application-layer
2652   protocols upon the existing transport-layer connection. Upgrade
2653   cannot be used to insist on a protocol change; its acceptance and use
2654   by the server is optional. The capabilities and nature of the
2655   application-layer communication after the protocol change is entirely
2656   dependent upon the new protocol chosen, although the first action
2657   after changing the protocol &MUST; be a response to the initial HTTP
2658   request containing the Upgrade header field.
2659</t>
2660<t>
2661   The Upgrade header field only applies to the immediate connection.
2662   Therefore, the upgrade keyword &MUST; be supplied within a Connection
2663   header field (<xref target="header.connection"/>) whenever Upgrade is present in an
2664   HTTP/1.1 message.
2665</t>
2666<t>
2667   The Upgrade header field cannot be used to indicate a switch to a
2668   protocol on a different connection. For that purpose, it is more
2669   appropriate to use a 301, 302, 303, or 305 redirection response.
2670</t>
2671<t>
2672   This specification only defines the protocol name "HTTP" for use by
2673   the family of Hypertext Transfer Protocols, as defined by the HTTP
2674   version rules of <xref target="http.version"/> and future updates to this
2675   specification. Any token can be used as a protocol name; however, it
2676   will only be useful if both the client and server associate the name
2677   with the same protocol.
2678</t>
2679</section>
2680
2681<section title="Via" anchor="header.via">
2682  <iref primary="true" item="Via header" x:for-anchor=""/>
2683  <iref primary="true" item="Headers" subitem="Via" x:for-anchor=""/>
2684<t>
2685   The Via general-header field &MUST; be used by gateways and proxies to
2686   indicate the intermediate protocols and recipients between the user
2687   agent and the server on requests, and between the origin server and
2688   the client on responses. It is analogous to the "Received" field of
2689   <xref target="RFC2822"/> and is intended to be used for tracking message forwards,
2690   avoiding request loops, and identifying the protocol capabilities of
2691   all senders along the request/response chain.
2692</t>
2693<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"/>
2694  Via =  "Via" ":" 1#( received-protocol received-by [ comment ] )
2695  received-protocol = [ protocol-name "/" ] protocol-version
2696  protocol-name     = token
2697  protocol-version  = token
2698  received-by       = ( uri-host [ ":" port ] ) | pseudonym
2699  pseudonym         = token
2700</artwork></figure>
2701<t>
2702   The received-protocol indicates the protocol version of the message
2703   received by the server or client along each segment of the
2704   request/response chain. The received-protocol version is appended to
2705   the Via field value when the message is forwarded so that information
2706   about the protocol capabilities of upstream applications remains
2707   visible to all recipients.
2708</t>
2709<t>
2710   The protocol-name is optional if and only if it would be "HTTP". The
2711   received-by field is normally the host and optional port number of a
2712   recipient server or client that subsequently forwarded the message.
2713   However, if the real host is considered to be sensitive information,
2714   it &MAY; be replaced by a pseudonym. If the port is not given, it &MAY;
2715   be assumed to be the default port of the received-protocol.
2716</t>
2717<t>
2718   Multiple Via field values represents each proxy or gateway that has
2719   forwarded the message. Each recipient &MUST; append its information
2720   such that the end result is ordered according to the sequence of
2721   forwarding applications.
2722</t>
2723<t>
2724   Comments &MAY; be used in the Via header field to identify the software
2725   of the recipient proxy or gateway, analogous to the User-Agent and
2726   Server header fields. However, all comments in the Via field are
2727   optional and &MAY; be removed by any recipient prior to forwarding the
2728   message.
2729</t>
2730<t>
2731   For example, a request message could be sent from an HTTP/1.0 user
2732   agent to an internal proxy code-named "fred", which uses HTTP/1.1 to
2733   forward the request to a public proxy at p.example.net, which completes
2734   the request by forwarding it to the origin server at www.example.com.
2735   The request received by www.example.com would then have the following
2736   Via header field:
2737</t>
2738<figure><artwork type="example">
2739    Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
2740</artwork></figure>
2741<t>
2742   Proxies and gateways used as a portal through a network firewall
2743   &SHOULD-NOT;, by default, forward the names and ports of hosts within
2744   the firewall region. This information &SHOULD; only be propagated if
2745   explicitly enabled. If not enabled, the received-by host of any host
2746   behind the firewall &SHOULD; be replaced by an appropriate pseudonym
2747   for that host.
2748</t>
2749<t>
2750   For organizations that have strong privacy requirements for hiding
2751   internal structures, a proxy &MAY; combine an ordered subsequence of
2752   Via header field entries with identical received-protocol values into
2753   a single such entry. For example,
2754</t>
2755<figure><artwork type="example">
2756    Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
2757</artwork></figure>
2758<t>
2759        could be collapsed to
2760</t>
2761<figure><artwork type="example">
2762    Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
2763</artwork></figure>
2764<t>
2765   Applications &SHOULD-NOT;  combine multiple entries unless they are all
2766   under the same organizational control and the hosts have already been
2767   replaced by pseudonyms. Applications &MUST-NOT; combine entries which
2768   have different received-protocol values.
2769</t>
2770</section>
2771
2772</section>
2773
2774<section title="IANA Considerations" anchor="IANA.considerations">
2775<t>
2776   <cref>TBD.</cref>
2777</t>
2778</section>
2779
2780<section title="Security Considerations" anchor="security.considerations">
2781<t>
2782   This section is meant to inform application developers, information
2783   providers, and users of the security limitations in HTTP/1.1 as
2784   described by this document. The discussion does not include
2785   definitive solutions to the problems revealed, though it does make
2786   some suggestions for reducing security risks.
2787</t>
2788
2789<section title="Personal Information" anchor="personal.information">
2790<t>
2791   HTTP clients are often privy to large amounts of personal information
2792   (e.g. the user's name, location, mail address, passwords, encryption
2793   keys, etc.), and &SHOULD; be very careful to prevent unintentional
2794   leakage of this information.
2795   We very strongly recommend that a convenient interface be provided
2796   for the user to control dissemination of such information, and that
2797   designers and implementors be particularly careful in this area.
2798   History shows that errors in this area often create serious security
2799   and/or privacy problems and generate highly adverse publicity for the
2800   implementor's company.
2801</t>
2802</section>
2803
2804<section title="Abuse of Server Log Information" anchor="abuse.of.server.log.information">
2805<t>
2806   A server is in the position to save personal data about a user's
2807   requests which might identify their reading patterns or subjects of
2808   interest. This information is clearly confidential in nature and its
2809   handling can be constrained by law in certain countries. People using
2810   HTTP to provide data are responsible for ensuring that
2811   such material is not distributed without the permission of any
2812   individuals that are identifiable by the published results.
2813</t>
2814</section>
2815
2816<section title="Attacks Based On File and Path Names" anchor="attack.pathname">
2817<t>
2818   Implementations of HTTP origin servers &SHOULD; be careful to restrict
2819   the documents returned by HTTP requests to be only those that were
2820   intended by the server administrators. If an HTTP server translates
2821   HTTP URIs directly into file system calls, the server &MUST; take
2822   special care not to serve files that were not intended to be
2823   delivered to HTTP clients. For example, UNIX, Microsoft Windows, and
2824   other operating systems use ".." as a path component to indicate a
2825   directory level above the current one. On such a system, an HTTP
2826   server &MUST; disallow any such construct in the Request-URI if it
2827   would otherwise allow access to a resource outside those intended to
2828   be accessible via the HTTP server. Similarly, files intended for
2829   reference only internally to the server (such as access control
2830   files, configuration files, and script code) &MUST; be protected from
2831   inappropriate retrieval, since they might contain sensitive
2832   information. Experience has shown that minor bugs in such HTTP server
2833   implementations have turned into security risks.
2834</t>
2835</section>
2836
2837<section title="DNS Spoofing" anchor="dns.spoofing">
2838<t>
2839   Clients using HTTP rely heavily on the Domain Name Service, and are
2840   thus generally prone to security attacks based on the deliberate
2841   mis-association of IP addresses and DNS names. Clients need to be
2842   cautious in assuming the continuing validity of an IP number/DNS name
2843   association.
2844</t>
2845<t>
2846   In particular, HTTP clients &SHOULD; rely on their name resolver for
2847   confirmation of an IP number/DNS name association, rather than
2848   caching the result of previous host name lookups. Many platforms
2849   already can cache host name lookups locally when appropriate, and
2850   they &SHOULD; be configured to do so. It is proper for these lookups to
2851   be cached, however, only when the TTL (Time To Live) information
2852   reported by the name server makes it likely that the cached
2853   information will remain useful.
2854</t>
2855<t>
2856   If HTTP clients cache the results of host name lookups in order to
2857   achieve a performance improvement, they &MUST; observe the TTL
2858   information reported by DNS.
2859</t>
2860<t>
2861   If HTTP clients do not observe this rule, they could be spoofed when
2862   a previously-accessed server's IP address changes. As network
2863   renumbering is expected to become increasingly common <xref target="RFC1900"/>, the
2864   possibility of this form of attack will grow. Observing this
2865   requirement thus reduces this potential security vulnerability.
2866</t>
2867<t>
2868   This requirement also improves the load-balancing behavior of clients
2869   for replicated servers using the same DNS name and reduces the
2870   likelihood of a user's experiencing failure in accessing sites which
2871   use that strategy.
2872</t>
2873</section>
2874
2875<section title="Proxies and Caching" anchor="attack.proxies">
2876<t>
2877   By their very nature, HTTP proxies are men-in-the-middle, and
2878   represent an opportunity for man-in-the-middle attacks. Compromise of
2879   the systems on which the proxies run can result in serious security
2880   and privacy problems. Proxies have access to security-related
2881   information, personal information about individual users and
2882   organizations, and proprietary information belonging to users and
2883   content providers. A compromised proxy, or a proxy implemented or
2884   configured without regard to security and privacy considerations,
2885   might be used in the commission of a wide range of potential attacks.
2886</t>
2887<t>
2888   Proxy operators should protect the systems on which proxies run as
2889   they would protect any system that contains or transports sensitive
2890   information. In particular, log information gathered at proxies often
2891   contains highly sensitive personal information, and/or information
2892   about organizations. Log information should be carefully guarded, and
2893   appropriate guidelines for use developed and followed. (<xref target="abuse.of.server.log.information"/>).
2894</t>
2895<t>
2896   Proxy implementors should consider the privacy and security
2897   implications of their design and coding decisions, and of the
2898   configuration options they provide to proxy operators (especially the
2899   default configuration).
2900</t>
2901<t>
2902   Users of a proxy need to be aware that they are no trustworthier than
2903   the people who run the proxy; HTTP itself cannot solve this problem.
2904</t>
2905<t>
2906   The judicious use of cryptography, when appropriate, may suffice to
2907   protect against a broad range of security and privacy attacks. Such
2908   cryptography is beyond the scope of the HTTP/1.1 specification.
2909</t>
2910</section>
2911
2912<section title="Denial of Service Attacks on Proxies" anchor="attack.DoS">
2913<t>
2914   They exist. They are hard to defend against. Research continues.
2915   Beware.
2916</t>
2917</section>
2918</section>
2919
2920<section title="Acknowledgments" anchor="ack">
2921<t>
2922   This specification makes heavy use of the augmented BNF and generic
2923   constructs defined by David H. Crocker for <xref target="RFC822ABNF"/>. Similarly, it
2924   reuses many of the definitions provided by Nathaniel Borenstein and
2925   Ned Freed for MIME <xref target="RFC2045"/>. We hope that their inclusion in this
2926   specification will help reduce past confusion over the relationship
2927   between HTTP and Internet mail message formats.
2928</t>
2929<t>
2930   HTTP has evolved considerably over the years. It has
2931   benefited from a large and active developer community--the many
2932   people who have participated on the www-talk mailing list--and it is
2933   that community which has been most responsible for the success of
2934   HTTP and of the World-Wide Web in general. Marc Andreessen, Robert
2935   Cailliau, Daniel W. Connolly, Bob Denny, John Franks, Jean-Francois
2936   Groff, Phillip M. Hallam-Baker, Hakon W. Lie, Ari Luotonen, Rob
2937   McCool, Lou Montulli, Dave Raggett, Tony Sanders, and Marc
2938   VanHeyningen deserve special recognition for their efforts in
2939   defining early aspects of the protocol.
2940</t>
2941<t>
2942   This document has benefited greatly from the comments of all those
2943   participating in the HTTP-WG. In addition to those already mentioned,
2944   the following individuals have contributed to this specification:
2945</t>
2946<t>
2947   Gary Adams, Harald Tveit Alvestrand, Keith Ball, Brian Behlendorf,
2948   Paul Burchard, Maurizio Codogno, Mike Cowlishaw, Roman Czyborra,
2949   Michael A. Dolan, Daniel DuBois, David J. Fiander, Alan Freier, Marc Hedlund, Greg Herlihy,
2950   Koen Holtman, Alex Hopmann, Bob Jernigan, Shel Kaphan, Rohit Khare,
2951   John Klensin, Martijn Koster, Alexei Kosut, David M. Kristol,
2952   Daniel LaLiberte, Ben Laurie, Paul J. Leach, Albert Lunde,
2953   John C. Mallery, Jean-Philippe Martin-Flatin, Mitra, David Morris,
2954   Gavin Nicol, Ross Patterson, Bill Perry, Jeffrey Perry, Scott Powers, Owen Rees,
2955   Luigi Rizzo, David Robinson, Marc Salomon, Rich Salz,
2956   Allan M. Schiffman, Jim Seidman, Chuck Shotton, Eric W. Sink,
2957   Simon E. Spero, Richard N. Taylor, Robert S. Thau,
2958   Bill (BearHeart) Weinman, Francois Yergeau, Mary Ellen Zurko,
2959   Josh Cohen.
2960</t>
2961<t>
2962   Thanks to the "cave men" of Palo Alto. You know who you are.
2963</t>
2964<t>
2965   Jim Gettys (the editor of <xref target="RFC2616"/>) wishes particularly
2966   to thank Roy Fielding, the editor of <xref target="RFC2068"/>, along
2967   with John Klensin, Jeff Mogul, Paul Leach, Dave Kristol, Koen
2968   Holtman, John Franks, Josh Cohen, Alex Hopmann, Scott Lawrence, and
2969   Larry Masinter for their help. And thanks go particularly to Jeff
2970   Mogul and Scott Lawrence for performing the "MUST/MAY/SHOULD" audit.
2971</t>
2972<t>
2973   The Apache Group, Anselm Baird-Smith, author of Jigsaw, and Henrik
2974   Frystyk implemented RFC 2068 early, and we wish to thank them for the
2975   discovery of many of the problems that this document attempts to
2976   rectify.
2977</t>
2978</section>
2979
2980</middle>
2981<back>
2982
2983<references title="Normative References">
2984
2985<reference anchor="ISO-8859-1">
2986  <front>
2987    <title>
2988     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
2989    </title>
2990    <author>
2991      <organization>International Organization for Standardization</organization>
2992    </author>
2993    <date year="1998"/>
2994  </front>
2995  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
2996</reference>
2997
2998<reference anchor="Part2">
2999  <front>
3000    <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
3001    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3002      <organization abbrev="Day Software">Day Software</organization>
3003      <address><email>fielding@gbiv.com</email></address>
3004    </author>
3005    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3006      <organization>One Laptop per Child</organization>
3007      <address><email>jg@laptop.org</email></address>
3008    </author>
3009    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3010      <organization abbrev="HP">Hewlett-Packard Company</organization>
3011      <address><email>JeffMogul@acm.org</email></address>
3012    </author>
3013    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3014      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3015      <address><email>henrikn@microsoft.com</email></address>
3016    </author>
3017    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3018      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
3019      <address><email>LMM@acm.org</email></address>
3020    </author>
3021    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3022      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3023      <address><email>paulle@microsoft.com</email></address>
3024    </author>
3025    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3026      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3027      <address><email>timbl@w3.org</email></address>
3028    </author>
3029    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3030      <organization abbrev="W3C">World Wide Web Consortium</organization>
3031      <address><email>ylafon@w3.org</email></address>
3032    </author>
3033    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3034      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3035      <address><email>julian.reschke@greenbytes.de</email></address>
3036    </author>
3037    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
3038  </front>
3039  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
3040  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
3041</reference>
3042
3043<reference anchor="Part3">
3044  <front>
3045    <title abbrev="HTTP/1.1">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
3046    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3047      <organization abbrev="Day Software">Day Software</organization>
3048      <address><email>fielding@gbiv.com</email></address>
3049    </author>
3050    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3051      <organization>One Laptop per Child</organization>
3052      <address><email>jg@laptop.org</email></address>
3053    </author>
3054    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3055      <organization abbrev="HP">Hewlett-Packard Company</organization>
3056      <address><email>JeffMogul@acm.org</email></address>
3057    </author>
3058    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3059      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3060      <address><email>henrikn@microsoft.com</email></address>
3061    </author>
3062    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3063      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
3064      <address><email>LMM@acm.org</email></address>
3065    </author>
3066    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3067      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3068      <address><email>paulle@microsoft.com</email></address>
3069    </author>
3070    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3071      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3072      <address><email>timbl@w3.org</email></address>
3073    </author>
3074    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3075      <organization abbrev="W3C">World Wide Web Consortium</organization>
3076      <address><email>ylafon@w3.org</email></address>
3077    </author>
3078    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3079      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3080      <address><email>julian.reschke@greenbytes.de</email></address>
3081    </author>
3082    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
3083  </front>
3084  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p3-payload-&ID-VERSION;"/>
3085  <x:source href="p3-payload.xml" basename="p3-payload"/>
3086</reference>
3087
3088<reference anchor="Part5">
3089  <front>
3090    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
3091    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3092      <organization abbrev="Day Software">Day Software</organization>
3093      <address><email>fielding@gbiv.com</email></address>
3094    </author>
3095    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3096      <organization>One Laptop per Child</organization>
3097      <address><email>jg@laptop.org</email></address>
3098    </author>
3099    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3100      <organization abbrev="HP">Hewlett-Packard Company</organization>
3101      <address><email>JeffMogul@acm.org</email></address>
3102    </author>
3103    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3104      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3105      <address><email>henrikn@microsoft.com</email></address>
3106    </author>
3107    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3108      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
3109      <address><email>LMM@acm.org</email></address>
3110    </author>
3111    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3112      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3113      <address><email>paulle@microsoft.com</email></address>
3114    </author>
3115    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3116      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3117      <address><email>timbl@w3.org</email></address>
3118    </author>
3119    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3120      <organization abbrev="W3C">World Wide Web Consortium</organization>
3121      <address><email>ylafon@w3.org</email></address>
3122    </author>
3123    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3124      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3125      <address><email>julian.reschke@greenbytes.de</email></address>
3126    </author>
3127    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
3128  </front>
3129  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
3130  <x:source href="p5-range.xml" basename="p5-range"/>
3131</reference>
3132
3133<reference anchor="Part6">
3134  <front>
3135    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
3136    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3137      <organization abbrev="Day Software">Day Software</organization>
3138      <address><email>fielding@gbiv.com</email></address>
3139    </author>
3140    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3141      <organization>One Laptop per Child</organization>
3142      <address><email>jg@laptop.org</email></address>
3143    </author>
3144    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3145      <organization abbrev="HP">Hewlett-Packard Company</organization>
3146      <address><email>JeffMogul@acm.org</email></address>
3147    </author>
3148    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3149      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3150      <address><email>henrikn@microsoft.com</email></address>
3151    </author>
3152    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3153      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
3154      <address><email>LMM@acm.org</email></address>
3155    </author>
3156    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3157      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3158      <address><email>paulle@microsoft.com</email></address>
3159    </author>
3160    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3161      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3162      <address><email>timbl@w3.org</email></address>
3163    </author>
3164    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3165      <organization abbrev="W3C">World Wide Web Consortium</organization>
3166      <address><email>ylafon@w3.org</email></address>
3167    </author>
3168    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3169      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3170      <address><email>julian.reschke@greenbytes.de</email></address>
3171    </author>
3172    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
3173  </front>
3174  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
3175  <x:source href="p6-cache.xml" basename="p6-cache"/>
3176</reference>
3177
3178<reference anchor="RFC822ABNF">
3179  <front>
3180    <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
3181    <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
3182      <organization>University of Delaware, Dept. of Electrical Engineering</organization>
3183      <address><email>DCrocker@UDel-Relay</email></address>
3184    </author>
3185    <date month="August" day="13" year="1982"/>
3186  </front>
3187  <seriesInfo name="STD" value="11"/>
3188  <seriesInfo name="RFC" value="822"/>
3189</reference>
3190
3191<reference anchor="RFC2045">
3192  <front>
3193    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
3194    <author initials="N." surname="Freed" fullname="Ned Freed">
3195      <organization>Innosoft International, Inc.</organization>
3196      <address><email>ned@innosoft.com</email></address>
3197    </author>
3198    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
3199      <organization>First Virtual Holdings</organization>
3200      <address><email>nsb@nsb.fv.com</email></address>
3201    </author>
3202    <date month="November" year="1996"/>
3203  </front>
3204  <seriesInfo name="RFC" value="2045"/>
3205</reference>
3206
3207<reference anchor="RFC2047">
3208  <front>
3209    <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
3210    <author initials="K." surname="Moore" fullname="Keith Moore">
3211      <organization>University of Tennessee</organization>
3212      <address><email>moore@cs.utk.edu</email></address>
3213    </author>
3214    <date month="November" year="1996"/>
3215  </front>
3216  <seriesInfo name="RFC" value="2047"/>
3217</reference>
3218
3219<reference anchor="RFC2119">
3220  <front>
3221    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
3222    <author initials="S." surname="Bradner" fullname="Scott Bradner">
3223      <organization>Harvard University</organization>
3224      <address><email>sob@harvard.edu</email></address>
3225    </author>
3226    <date month="March" year="1997"/>
3227  </front>
3228  <seriesInfo name="BCP" value="14"/>
3229  <seriesInfo name="RFC" value="2119"/>
3230</reference>
3231
3232<reference anchor="RFC2396">
3233  <front>
3234    <title abbrev="URI Generic Syntax">Uniform Resource Identifiers (URI): Generic Syntax</title>
3235    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3236      <organization abbrev="MIT/LCS">World Wide Web Consortium</organization>
3237      <address><email>timbl@w3.org</email></address>
3238    </author>
3239    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
3240      <organization abbrev="U.C. Irvine">Department of Information and Computer Science</organization>
3241      <address><email>fielding@ics.uci.edu</email></address>
3242    </author>
3243    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3244      <organization abbrev="Xerox Corporation">Xerox PARC</organization>
3245      <address><email>masinter@parc.xerox.com</email></address>
3246    </author>
3247    <date month="August" year="1998"/>
3248  </front>
3249  <seriesInfo name="RFC" value="2396"/>
3250</reference>
3251
3252<reference anchor="USASCII">
3253  <front>
3254    <title>Coded Character Set -- 7-bit American Standard Code for Information Interchange</title>
3255    <author>
3256      <organization>American National Standards Institute</organization>
3257    </author>
3258    <date year="1986"/>
3259  </front>
3260  <seriesInfo name="ANSI" value="X3.4"/>
3261</reference>
3262
3263</references>
3264
3265<references title="Informative References">
3266
3267<reference anchor="Nie1997" target="http://doi.acm.org/10.1145/263105.263157">
3268  <front>
3269    <title>Network Performance Effects of HTTP/1.1, CSS1, and PNG</title>
3270    <author initials="H.F.." surname="Nielsen" fullname="H.F. Nielsen">
3271      <organization/>
3272    </author>
3273    <author initials="J." surname="Gettys" fullname="J. Gettys">
3274      <organization/>
3275    </author>
3276    <author initials="E." surname="Prud'hommeaux" fullname="E. Prud'hommeaux">
3277      <organization/>
3278    </author>
3279    <author initials="H." surname="Lie" fullname="H. Lie">
3280      <organization/>
3281    </author>
3282    <author initials="C." surname="Lilley" fullname="C. Lilley">
3283      <organization/>
3284    </author>
3285    <date year="1997" month="September"/>
3286  </front>
3287  <seriesInfo name="ACM" value="Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication SIGCOMM '97"/>
3288</reference>
3289
3290<reference anchor="Pad1995">
3291  <front>
3292    <title>Improving HTTP Latency</title>
3293    <author initials="V.N." surname="Padmanabhan" fullname="Venkata N. Padmanabhan">
3294      <organization/>
3295    </author>
3296    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
3297      <organization/>
3298    </author>
3299    <date year="1995" month="December"/>
3300  </front>
3301  <seriesInfo name="Computer Networks and ISDN Systems" value="v. 28, pp. 25-35"/>
3302  <annotation>
3303    Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994,
3304    which is available at <eref target="http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html"/>.
3305  </annotation>
3306</reference>
3307
3308<reference anchor="RFC822">
3309  <front>
3310    <title abbrev="Standard for ARPA Internet Text Messages">Standard for the format of ARPA Internet text messages</title>
3311    <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
3312      <organization>University of Delaware, Dept. of Electrical Engineering</organization>
3313      <address><email>DCrocker@UDel-Relay</email></address>
3314    </author>
3315    <date month="August" day="13" year="1982"/>
3316  </front>
3317  <seriesInfo name="STD" value="11"/>
3318  <seriesInfo name="RFC" value="822"/>
3319</reference>
3320
3321<reference anchor="RFC959">
3322  <front>
3323    <title abbrev="File Transfer Protocol">File Transfer Protocol</title>
3324    <author initials="J." surname="Postel" fullname="J. Postel">
3325      <organization>Information Sciences Institute (ISI)</organization>
3326    </author>
3327    <author initials="J." surname="Reynolds" fullname="J. Reynolds">
3328      <organization/>
3329    </author>
3330    <date month="October" year="1985"/>
3331  </front>
3332  <seriesInfo name="STD" value="9"/>
3333  <seriesInfo name="RFC" value="959"/>
3334</reference>
3335
3336<reference anchor="RFC1123">
3337  <front>
3338    <title>Requirements for Internet Hosts - Application and Support</title>
3339    <author initials="R." surname="Braden" fullname="Robert Braden">
3340      <organization>University of Southern California (USC), Information Sciences Institute</organization>
3341      <address><email>Braden@ISI.EDU</email></address>
3342    </author>
3343    <date month="October" year="1989"/>
3344  </front>
3345  <seriesInfo name="STD" value="3"/>
3346  <seriesInfo name="RFC" value="1123"/>
3347</reference>
3348
3349<reference anchor="RFC1305">
3350  <front>
3351    <title>Network Time Protocol (Version 3) Specification, Implementation</title>
3352    <author initials="D." surname="Mills" fullname="David L. Mills">
3353      <organization>University of Delaware, Electrical Engineering Department</organization>
3354      <address><email>mills@udel.edu</email></address>
3355    </author>
3356    <date month="March" year="1992"/>
3357  </front>
3358  <seriesInfo name="RFC" value="1305"/>
3359</reference>
3360
3361<reference anchor="RFC1436">
3362  <front>
3363    <title abbrev="Gopher">The Internet Gopher Protocol (a distributed document search and retrieval protocol)</title>
3364    <author initials="F." surname="Anklesaria" fullname="Farhad Anklesaria">
3365      <organization>University of Minnesota, Computer and Information Services</organization>
3366      <address><email>fxa@boombox.micro.umn.edu</email></address>
3367    </author>
3368    <author initials="M." surname="McCahill" fullname="Mark McCahill">
3369      <organization>University of Minnesota, Computer and Information Services</organization>
3370      <address><email>mpm@boombox.micro.umn.edu</email></address>
3371    </author>
3372    <author initials="P." surname="Lindner" fullname="Paul Lindner">
3373      <organization>University of Minnesota, Computer and Information Services</organization>
3374      <address><email>lindner@boombox.micro.umn.edu</email></address>
3375    </author>
3376    <author initials="D." surname="Johnson" fullname="David Johnson">
3377      <organization>University of Minnesota, Computer and Information Services</organization>
3378      <address><email>dmj@boombox.micro.umn.edu</email></address>
3379    </author>
3380    <author initials="D." surname="Torrey" fullname="Daniel Torrey">
3381      <organization>University of Minnesota, Computer and Information Services</organization>
3382      <address><email>daniel@boombox.micro.umn.edu</email></address>
3383    </author>
3384    <author initials="B." surname="Alberti" fullname="Bob Alberti">
3385      <organization>University of Minnesota, Computer and Information Services</organization>
3386      <address><email>alberti@boombox.micro.umn.edu</email></address>
3387    </author>
3388    <date month="March" year="1993"/>
3389  </front>
3390  <seriesInfo name="RFC" value="1436"/>
3391</reference>
3392
3393<reference anchor="RFC1630">
3394  <front>
3395    <title abbrev="URIs in WWW">Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web</title>
3396    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3397      <organization>CERN, World-Wide Web project</organization>
3398      <address><email>timbl@info.cern.ch</email></address>
3399    </author>
3400    <date month="June" year="1994"/>
3401  </front>
3402  <seriesInfo name="RFC" value="1630"/>
3403</reference>
3404
3405<reference anchor="RFC1737">
3406  <front>
3407    <title abbrev="Requirements for Uniform Resource Names">Functional Requirements for Uniform Resource Names</title>
3408    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3409      <organization>Xerox Palo Alto Research Center</organization>
3410      <address><email>masinter@parc.xerox.com</email></address>
3411    </author>
3412    <author initials="K." surname="Sollins" fullname="Karen Sollins">
3413      <organization>MIT Laboratory for Computer Science</organization>
3414      <address><email>sollins@lcs.mit.edu</email></address>
3415    </author>
3416    <date month="December" year="1994"/>
3417  </front>
3418  <seriesInfo name="RFC" value="1737"/>
3419</reference>
3420
3421<reference anchor="RFC1738">
3422  <front>
3423    <title>Uniform Resource Locators (URL)</title>
3424    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3425      <organization>CERN, World-Wide Web project</organization>
3426      <address><email>timbl@info.cern.ch</email></address>
3427    </author>
3428    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3429      <organization>Xerox PARC</organization>
3430      <address><email>masinter@parc.xerox.com</email></address>
3431    </author>
3432    <author initials="M." surname="McCahill" fullname="Mark McCahill">
3433      <organization>University of Minnesota, Computer and Information Services</organization>
3434      <address><email>mpm@boombox.micro.umn.edu</email></address>
3435    </author>
3436    <date month="December" year="1994"/>
3437  </front>
3438  <seriesInfo name="RFC" value="1738"/>
3439</reference>
3440
3441<reference anchor="RFC1808">
3442  <front>
3443    <title>Relative Uniform Resource Locators</title>
3444    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
3445      <organization>University of California Irvine, Department of Information and Computer Science</organization>
3446      <address><email>fielding@ics.uci.edu</email></address>
3447    </author>
3448    <date month="June" year="1995"/>
3449  </front>
3450  <seriesInfo name="RFC" value="1808"/>
3451</reference>
3452
3453<reference anchor="RFC1900">
3454  <front>
3455    <title>Renumbering Needs Work</title>
3456    <author initials="B." surname="Carpenter" fullname="Brian E. Carpenter">
3457      <organization>CERN, Computing and Networks Division</organization>
3458      <address><email>brian@dxcoms.cern.ch</email></address>
3459    </author>
3460    <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
3461      <organization>cisco Systems</organization>
3462      <address><email>yakov@cisco.com</email></address>
3463    </author>
3464    <date month="February" year="1996"/>
3465  </front>
3466  <seriesInfo name="RFC" value="1900"/>
3467</reference>
3468
3469<reference anchor="RFC1945">
3470  <front>
3471    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
3472    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3473      <organization>MIT, Laboratory for Computer Science</organization>
3474      <address><email>timbl@w3.org</email></address>
3475    </author>
3476    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
3477      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
3478      <address><email>fielding@ics.uci.edu</email></address>
3479    </author>
3480    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
3481      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
3482      <address><email>frystyk@w3.org</email></address>
3483    </author>
3484    <date month="May" year="1996"/>
3485  </front>
3486  <seriesInfo name="RFC" value="1945"/>
3487</reference>
3488
3489<reference anchor="RFC2068">
3490  <front>
3491    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
3492    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
3493      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
3494      <address><email>fielding@ics.uci.edu</email></address>
3495    </author>
3496    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3497      <organization>MIT Laboratory for Computer Science</organization>
3498      <address><email>jg@w3.org</email></address>
3499    </author>
3500    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3501      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
3502      <address><email>mogul@wrl.dec.com</email></address>
3503    </author>
3504    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
3505      <organization>MIT Laboratory for Computer Science</organization>
3506      <address><email>frystyk@w3.org</email></address>
3507    </author>
3508    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3509      <organization>MIT Laboratory for Computer Science</organization>
3510      <address><email>timbl@w3.org</email></address>
3511    </author>
3512    <date month="January" year="1997"/>
3513  </front>
3514  <seriesInfo name="RFC" value="2068"/>
3515</reference>
3516
3517<reference anchor="RFC2145">
3518  <front>
3519    <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
3520    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
3521      <organization>Western Research Laboratory</organization>
3522      <address><email>mogul@wrl.dec.com</email></address>
3523    </author>
3524    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
3525      <organization>Department of Information and Computer Science</organization>
3526      <address><email>fielding@ics.uci.edu</email></address>
3527    </author>
3528    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3529      <organization>MIT Laboratory for Computer Science</organization>
3530      <address><email>jg@w3.org</email></address>
3531    </author>
3532    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
3533      <organization>W3 Consortium</organization>
3534      <address><email>frystyk@w3.org</email></address>
3535    </author>
3536    <date month="May" year="1997"/>
3537  </front>
3538  <seriesInfo name="RFC" value="2145"/>
3539</reference>
3540
3541<reference anchor="RFC2324">
3542  <front>
3543    <title abbrev="HTCPCP/1.0">Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</title>
3544    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3545      <organization>Xerox Palo Alto Research Center</organization>
3546      <address><email>masinter@parc.xerox.com</email></address>
3547    </author>
3548    <date month="April" day="1" year="1998"/>
3549  </front>
3550  <seriesInfo name="RFC" value="2324"/>
3551</reference>
3552
3553<reference anchor="RFC2616">
3554  <front>
3555    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
3556    <author initials="R." surname="Fielding" fullname="R. Fielding">
3557      <organization>University of California, Irvine</organization>
3558      <address><email>fielding@ics.uci.edu</email></address>
3559    </author>
3560    <author initials="J." surname="Gettys" fullname="J. Gettys">
3561      <organization>W3C</organization>
3562      <address><email>jg@w3.org</email></address>
3563    </author>
3564    <author initials="J." surname="Mogul" fullname="J. Mogul">
3565      <organization>Compaq Computer Corporation</organization>
3566      <address><email>mogul@wrl.dec.com</email></address>
3567    </author>
3568    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
3569      <organization>MIT Laboratory for Computer Science</organization>
3570      <address><email>frystyk@w3.org</email></address>
3571    </author>
3572    <author initials="L." surname="Masinter" fullname="L. Masinter">
3573      <organization>Xerox Corporation</organization>
3574      <address><email>masinter@parc.xerox.com</email></address>
3575    </author>
3576    <author initials="P." surname="Leach" fullname="P. Leach">
3577      <organization>Microsoft Corporation</organization>
3578      <address><email>paulle@microsoft.com</email></address>
3579    </author>
3580    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
3581      <organization>W3C</organization>
3582      <address><email>timbl@w3.org</email></address>
3583    </author>
3584    <date month="June" year="1999"/>
3585  </front>
3586  <seriesInfo name="RFC" value="2616"/>
3587</reference>
3588
3589<reference anchor="RFC2821">
3590  <front>
3591    <title>Simple Mail Transfer Protocol</title>
3592    <author initials="J." surname="Klensin" fullname="J. Klensin">
3593      <organization>AT&amp;T Laboratories</organization>
3594      <address><email>klensin@research.att.com</email></address>
3595    </author>
3596    <date year="2001" month="April"/>
3597  </front>
3598  <seriesInfo name="RFC" value="2821"/>
3599</reference>
3600
3601<reference anchor="RFC2822">
3602  <front>
3603    <title>Internet Message Format</title>
3604    <author initials="P." surname="Resnick" fullname="P. Resnick">
3605      <organization>QUALCOMM Incorporated</organization>
3606    </author>
3607    <date year="2001" month="April"/>
3608  </front> 
3609  <seriesInfo name="RFC" value="2822"/>
3610</reference>
3611
3612<reference anchor='RFC3977'>
3613  <front>
3614    <title>Network News Transfer Protocol (NNTP)</title>
3615    <author initials='C.' surname='Feather' fullname='C. Feather'>
3616      <organization>THUS plc</organization>
3617      <address><email>clive@demon.net</email></address>
3618    </author>
3619    <date year='2006' month='October' />
3620  </front>
3621  <seriesInfo name="RFC" value="3977"/>
3622</reference>
3623
3624<reference anchor="RFC4288">
3625  <front>
3626    <title>Media Type Specifications and Registration Procedures</title>
3627    <author initials="N." surname="Freed" fullname="N. Freed">
3628      <organization>Sun Microsystems</organization>
3629      <address>
3630        <email>ned.freed@mrochek.com</email>
3631      </address>
3632    </author>
3633    <author initials="J." surname="Klensin" fullname="J. Klensin">
3634      <organization/>
3635      <address>
3636        <email>klensin+ietf@jck.com</email>
3637      </address>
3638    </author>
3639    <date year="2005" month="December"/>
3640  </front>
3641  <seriesInfo name="BCP" value="13"/>
3642  <seriesInfo name="RFC" value="4288"/>
3643</reference>
3644
3645<reference anchor="Spe" target="http://sunsite.unc.edu/mdma-release/http-prob.html">
3646  <front>
3647  <title>Analysis of HTTP Performance Problems</title>
3648  <author initials="S." surname="Spero" fullname="Simon E. Spero">
3649    <organization/>
3650  </author>
3651  <date/>
3652  </front>
3653</reference>
3654
3655<reference anchor="Tou1998" target="http://www.isi.edu/touch/pubs/http-perf96/">
3656  <front>
3657  <title>Analysis of HTTP Performance</title>
3658  <author initials="J." surname="Touch" fullname="Joe Touch">
3659    <organization>USC/Information Sciences Institute</organization>
3660    <address><email>touch@isi.edu</email></address>
3661  </author>
3662  <author initials="J." surname="Heidemann" fullname="John Heidemann">
3663    <organization>USC/Information Sciences Institute</organization>
3664    <address><email>johnh@isi.edu</email></address>
3665  </author>
3666  <author initials="K." surname="Obraczka" fullname="Katia Obraczka">
3667    <organization>USC/Information Sciences Institute</organization>
3668    <address><email>katia@isi.edu</email></address>
3669  </author>
3670  <date year="1998" month="Aug"/>
3671  </front>
3672  <seriesInfo name="ISI Research Report" value="ISI/RR-98-463"/>
3673  <annotation>(original report dated Aug. 1996)</annotation>
3674</reference>
3675
3676<reference anchor="WAIS">
3677  <front>
3678    <title>WAIS Interface Protocol Prototype Functional Specification (v1.5)</title>
3679    <author initials="F." surname="Davis" fullname="F. Davis">
3680      <organization>Thinking Machines Corporation</organization>
3681    </author>
3682    <author initials="B." surname="Kahle" fullname="B. Kahle">
3683      <organization>Thinking Machines Corporation</organization>
3684    </author>
3685    <author initials="H." surname="Morris" fullname="H. Morris">
3686      <organization>Thinking Machines Corporation</organization>
3687    </author>
3688    <author initials="J." surname="Salem" fullname="J. Salem">
3689      <organization>Thinking Machines Corporation</organization>
3690    </author>
3691    <author initials="T." surname="Shen" fullname="T. Shen">
3692      <organization>Thinking Machines Corporation</organization>
3693    </author>
3694    <author initials="R." surname="Wang" fullname="R. Wang">
3695      <organization>Thinking Machines Corporation</organization>
3696    </author>
3697    <author initials="J." surname="Sui" fullname="J. Sui">
3698      <organization>Thinking Machines Corporation</organization>
3699    </author>
3700    <author initials="M." surname="Grinbaum" fullname="M. Grinbaum">
3701      <organization>Thinking Machines Corporation</organization>
3702    </author>
3703    <date month="April" year="1990"/>
3704  </front>
3705  <seriesInfo name="Thinking Machines Corporation" value=""/>
3706</reference>
3707
3708</references>
3709
3710
3711<section title="Internet Media Types" anchor="internet.media.type.http">
3712<t>
3713   In addition to defining HTTP/1.1, this document serves
3714   as the specification for the Internet media type "message/http" and
3715   "application/http". The following is to be registered with IANA <xref target="RFC4288"/>.
3716</t>
3717<section title="Internet Media Type message/http" anchor="internet.media.type.message.http">
3718<iref item="Media Type" subitem="message/http" primary="true"/>
3719<iref item="message/http Media Type" primary="true"/>
3720<t>
3721   The message/http type can be used to enclose a single HTTP request or
3722   response message, provided that it obeys the MIME restrictions for all
3723   "message" types regarding line length and encodings.
3724</t>
3725<t>
3726  <list style="hanging" x:indent="12em">
3727    <t hangText="Type name:">
3728      message
3729    </t>
3730    <t hangText="Subtype name:">
3731      http
3732    </t>
3733    <t hangText="Required parameters:">
3734      none
3735    </t>
3736    <t hangText="Optional parameters:">
3737      version, msgtype
3738      <list style="hanging">
3739        <t hangText="version:">
3740          The HTTP-Version number of the enclosed message
3741          (e.g., "1.1"). If not present, the version can be
3742          determined from the first line of the body.
3743        </t>
3744        <t hangText="msgtype:">
3745          The message type -- "request" or "response". If not
3746          present, the type can be determined from the first
3747          line of the body.
3748        </t>
3749      </list>
3750    </t>
3751    <t hangText="Encoding considerations:">
3752      only "7bit", "8bit", or "binary" are permitted
3753    </t>
3754    <t hangText="Security considerations:">
3755      none
3756    </t>
3757    <t hangText="Interoperability considerations:">
3758      none
3759    </t>
3760    <t hangText="Published specification:">
3761      This specification (see <xref target="internet.media.type.message.http"/>).
3762    </t>
3763    <t hangText="Applications that use this media type:">
3764    </t>
3765    <t hangText="Additional information:">
3766      <list style="hanging">
3767        <t hangText="Magic number(s):">none</t>
3768        <t hangText="File extension(s):">none</t>
3769        <t hangText="Macintosh file type code(s):">none</t>
3770      </list>
3771    </t>
3772    <t hangText="Person and email address to contact for further information:">
3773      See Authors Section.
3774    </t>
3775                <t hangText="Intended usage:">
3776                  COMMON
3777    </t>
3778                <t hangText="Restrictions on usage:">
3779                  none
3780    </t>
3781    <t hangText="Author/Change controller:">
3782      IESG
3783    </t>
3784  </list>
3785</t>
3786</section>
3787<section title="Internet Media Type application/http" anchor="internet.media.type.application.http">
3788<iref item="Media Type" subitem="application/http" primary="true"/>
3789<iref item="application/http Media Type" primary="true"/>
3790<t>
3791   The application/http type can be used to enclose a pipeline of one or more
3792   HTTP request or response messages (not intermixed).
3793</t>
3794<t>
3795  <list style="hanging" x:indent="12em">
3796    <t hangText="Type name:">
3797      application
3798    </t>
3799    <t hangText="Subtype name:">
3800      http
3801    </t>
3802    <t hangText="Required parameters:">
3803      none
3804    </t>
3805    <t hangText="Optional parameters:">
3806      version, msgtype
3807      <list style="hanging">
3808        <t hangText="version:">
3809          The HTTP-Version number of the enclosed messages
3810          (e.g., "1.1"). If not present, the version can be
3811          determined from the first line of the body.
3812        </t>
3813        <t hangText="msgtype:">
3814          The message type -- "request" or "response". If not
3815          present, the type can be determined from the first
3816          line of the body.
3817        </t>
3818      </list>
3819    </t>
3820    <t hangText="Encoding considerations:">
3821      HTTP messages enclosed by this type
3822      are in "binary" format; use of an appropriate
3823      Content-Transfer-Encoding is required when
3824      transmitted via E-mail.
3825    </t>
3826    <t hangText="Security considerations:">
3827      none
3828    </t>
3829    <t hangText="Interoperability considerations:">
3830      none
3831    </t>
3832    <t hangText="Published specification:">
3833      This specification (see <xref target="internet.media.type.application.http"/>).
3834    </t>
3835    <t hangText="Applications that use this media type:">
3836    </t>
3837    <t hangText="Additional information:">
3838      <list style="hanging">
3839        <t hangText="Magic number(s):">none</t>
3840        <t hangText="File extension(s):">none</t>
3841        <t hangText="Macintosh file type code(s):">none</t>
3842      </list>
3843    </t>
3844    <t hangText="Person and email address to contact for further information:">
3845      See Authors Section.
3846    </t>
3847                <t hangText="Intended usage:">
3848                  COMMON
3849    </t>
3850                <t hangText="Restrictions on usage:">
3851                  none
3852    </t>
3853    <t hangText="Author/Change controller:">
3854      IESG
3855    </t>
3856  </list>
3857</t>
3858</section>
3859</section>
3860
3861<section title="Tolerant Applications" anchor="tolerant.applications">
3862<t>
3863   Although this document specifies the requirements for the generation
3864   of HTTP/1.1 messages, not all applications will be correct in their
3865   implementation. We therefore recommend that operational applications
3866   be tolerant of deviations whenever those deviations can be
3867   interpreted unambiguously.
3868</t>
3869<t>
3870   Clients &SHOULD; be tolerant in parsing the Status-Line and servers
3871   tolerant when parsing the Request-Line. In particular, they &SHOULD;
3872   accept any amount of SP or HTAB characters between fields, even though
3873   only a single SP is required.
3874</t>
3875<t>
3876   The line terminator for message-header fields is the sequence CRLF.
3877   However, we recommend that applications, when parsing such headers,
3878   recognize a single LF as a line terminator and ignore the leading CR.
3879</t>
3880<t>
3881   The character set of an entity-body &SHOULD; be labeled as the lowest
3882   common denominator of the character codes used within that body, with
3883   the exception that not labeling the entity is preferred over labeling
3884   the entity with the labels US-ASCII or ISO-8859-1. See &payload;.
3885</t>
3886<t>
3887   Additional rules for requirements on parsing and encoding of dates
3888   and other potential problems with date encodings include:
3889</t>
3890<t>
3891  <list style="symbols">
3892     <t>HTTP/1.1 clients and caches &SHOULD; assume that an RFC-850 date
3893        which appears to be more than 50 years in the future is in fact
3894        in the past (this helps solve the "year 2000" problem).</t>
3895
3896     <t>An HTTP/1.1 implementation &MAY; internally represent a parsed
3897        Expires date as earlier than the proper value, but &MUST-NOT;
3898        internally represent a parsed Expires date as later than the
3899        proper value.</t>
3900
3901     <t>All expiration-related calculations &MUST; be done in GMT. The
3902        local time zone &MUST-NOT; influence the calculation or comparison
3903        of an age or expiration time.</t>
3904
3905     <t>If an HTTP header incorrectly carries a date value with a time
3906        zone other than GMT, it &MUST; be converted into GMT using the
3907        most conservative possible conversion.</t>
3908  </list>
3909</t>
3910</section>
3911
3912<section title="Conversion of Date Formats" anchor="conversion.of.date.formats">
3913<t>
3914   HTTP/1.1 uses a restricted set of date formats (<xref target="full.date"/>) to
3915   simplify the process of date comparison. Proxies and gateways from
3916   other protocols &SHOULD; ensure that any Date header field present in a
3917   message conforms to one of the HTTP/1.1 formats and rewrite the date
3918   if necessary.
3919</t>
3920</section>
3921
3922<section title="Compatibility with Previous Versions" anchor="compatibility">
3923<t>
3924   It is beyond the scope of a protocol specification to mandate
3925   compliance with previous versions. HTTP/1.1 was deliberately
3926   designed, however, to make supporting previous versions easy. It is
3927   worth noting that, at the time of composing this specification
3928   (1996), we would expect commercial HTTP/1.1 servers to:
3929  <list style="symbols">
3930     <t>recognize the format of the Request-Line for HTTP/0.9, 1.0, and
3931        1.1 requests;</t>
3932
3933     <t>understand any valid request in the format of HTTP/0.9, 1.0, or
3934        1.1;</t>
3935
3936     <t>respond appropriately with a message in the same major version
3937        used by the client.</t>
3938  </list>
3939</t>
3940<t>
3941   And we would expect HTTP/1.1 clients to:
3942  <list style="symbols">
3943     <t>recognize the format of the Status-Line for HTTP/1.0 and 1.1
3944        responses;</t>
3945
3946     <t>understand any valid response in the format of HTTP/0.9, 1.0, or
3947        1.1.</t>
3948  </list>
3949</t>
3950<t>
3951   For most implementations of HTTP/1.0, each connection is established
3952   by the client prior to the request and closed by the server after
3953   sending the response. Some implementations implement the Keep-Alive
3954   version of persistent connections described in <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/>.
3955</t>
3956
3957<section title="Changes from HTTP/1.0" anchor="changes.from.1.0">
3958<t>
3959   This section summarizes major differences between versions HTTP/1.0
3960   and HTTP/1.1.
3961</t>
3962
3963<section title="Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses" anchor="changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">
3964<t>
3965   The requirements that clients and servers support the Host request-header,
3966   report an error if the Host request-header (<xref target="header.host"/>) is
3967   missing from an HTTP/1.1 request, and accept absolute URIs (<xref target="request-uri"/>)
3968   are among the most important changes defined by this
3969   specification.
3970</t>
3971<t>
3972   Older HTTP/1.0 clients assumed a one-to-one relationship of IP
3973   addresses and servers; there was no other established mechanism for
3974   distinguishing the intended server of a request than the IP address
3975   to which that request was directed. The changes outlined above will
3976   allow the Internet, once older HTTP clients are no longer common, to
3977   support multiple Web sites from a single IP address, greatly
3978   simplifying large operational Web servers, where allocation of many
3979   IP addresses to a single host has created serious problems. The
3980   Internet will also be able to recover the IP addresses that have been
3981   allocated for the sole purpose of allowing special-purpose domain
3982   names to be used in root-level HTTP URLs. Given the rate of growth of
3983   the Web, and the number of servers already deployed, it is extremely
3984   important that all implementations of HTTP (including updates to
3985   existing HTTP/1.0 applications) correctly implement these
3986   requirements:
3987  <list style="symbols">
3988     <t>Both clients and servers &MUST; support the Host request-header.</t>
3989
3990     <t>A client that sends an HTTP/1.1 request &MUST; send a Host header.</t>
3991
3992     <t>Servers &MUST; report a 400 (Bad Request) error if an HTTP/1.1
3993        request does not include a Host request-header.</t>
3994
3995     <t>Servers &MUST; accept absolute URIs.</t>
3996  </list>
3997</t>
3998</section>
3999</section>
4000
4001<section title="Compatibility with HTTP/1.0 Persistent Connections" anchor="compatibility.with.http.1.0.persistent.connections">
4002<t>
4003   Some clients and servers might wish to be compatible with some
4004   previous implementations of persistent connections in HTTP/1.0
4005   clients and servers. Persistent connections in HTTP/1.0 are
4006   explicitly negotiated as they are not the default behavior. HTTP/1.0
4007   experimental implementations of persistent connections are faulty,
4008   and the new facilities in HTTP/1.1 are designed to rectify these
4009   problems. The problem was that some existing 1.0 clients may be
4010   sending Keep-Alive to a proxy server that doesn't understand
4011   Connection, which would then erroneously forward it to the next
4012   inbound server, which would establish the Keep-Alive connection and
4013   result in a hung HTTP/1.0 proxy waiting for the close on the
4014   response. The result is that HTTP/1.0 clients must be prevented from
4015   using Keep-Alive when talking to proxies.
4016</t>
4017<t>
4018   However, talking to proxies is the most important use of persistent
4019   connections, so that prohibition is clearly unacceptable. Therefore,
4020   we need some other mechanism for indicating a persistent connection
4021   is desired, which is safe to use even when talking to an old proxy
4022   that ignores Connection. Persistent connections are the default for
4023   HTTP/1.1 messages; we introduce a new keyword (Connection: close) for
4024   declaring non-persistence. See <xref target="header.connection"/>.
4025</t>
4026<t>
4027   The original HTTP/1.0 form of persistent connections (the Connection:
4028   Keep-Alive and Keep-Alive header) is documented in <xref target="RFC2068"/>.
4029</t>
4030</section>
4031
4032<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
4033<t>
4034   This specification has been carefully audited to correct and
4035   disambiguate key word usage; RFC 2068 had many problems in respect to
4036   the conventions laid out in <xref target="RFC2119"/>.
4037</t>
4038<t>
4039   Transfer-coding and message lengths all interact in ways that
4040   required fixing exactly when chunked encoding is used (to allow for
4041   transfer encoding that may not be self delimiting); it was important
4042   to straighten out exactly how message lengths are computed. (Sections
4043   <xref target="transfer.codings" format="counter"/>, <xref target="message.length" format="counter"/>,
4044   <xref target="header.content-length" format="counter"/>,
4045   see also <xref target="Part3"/>, <xref target="Part5"/> and <xref target="Part6"/>)
4046</t>
4047<t>
4048   The use and interpretation of HTTP version numbers has been clarified
4049   by <xref target="RFC2145"/>. Require proxies to upgrade requests to highest protocol
4050   version they support to deal with problems discovered in HTTP/1.0
4051   implementations (<xref target="http.version"/>)
4052</t>
4053<t>
4054   Transfer-coding had significant problems, particularly with
4055   interactions with chunked encoding. The solution is that transfer-codings
4056   become as full fledged as content-codings. This involves
4057   adding an IANA registry for transfer-codings (separate from content
4058   codings), a new header field (TE) and enabling trailer headers in the
4059   future. Transfer encoding is a major performance benefit, so it was
4060   worth fixing <xref target="Nie1997"/>. TE also solves another, obscure, downward
4061   interoperability problem that could have occurred due to interactions
4062   between authentication trailers, chunked encoding and HTTP/1.0
4063   clients.(Section <xref target="transfer.codings" format="counter"/>, <xref target="chunked.transfer.encoding" format="counter"/>,
4064   and <xref target="header.te" format="counter"/>)
4065</t>
4066</section>
4067
4068<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
4069<t>
4070  The CHAR rule does not allow the NUL character anymore (this affects
4071  the comment and quoted-string rules).
4072  (<xref target="basic.rules"/>)
4073</t>
4074<t>
4075  Clarify that HTTP-Version is case sensitive.
4076  (<xref target="http.version"/>)
4077</t>
4078<t>
4079  Remove reference to non-existant identity transfer-coding value tokens.
4080  (Sections <xref format="counter" target="transfer.codings"/> and
4081  <xref format="counter" target="message.length"/>)
4082</t>
4083<t>
4084  Clarification that the chunk length does not include
4085  the count of the octets in the chunk header and trailer.
4086  (<xref target="chunked.transfer.encoding"/>)
4087</t>
4088<t>
4089  Fix BNF to add query, as the abs_path production in
4090  <xref x:sec="3" x:fmt="of" target="RFC2396"/> doesn't define it.
4091  (<xref target="request-uri"/>)
4092</t>
4093<t>
4094  Clarify exactly when close connection options must be sent.
4095  (<xref target="header.connection"/>)
4096</t>
4097</section>
4098</section>
4099
4100<section title="Change Log (to be removed by RFC Editor before publication)">
4101
4102<section title="Since RFC2616">
4103<t>
4104  Extracted relevant partitions from <xref target="RFC2616"/>.
4105</t>
4106</section>
4107
4108<section title="Since draft-ietf-httpbis-p1-messaging-00">
4109<t>
4110  Closed issues:
4111  <list style="symbols"> 
4112    <t>
4113      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/1"/>:
4114      "HTTP Version should be case sensitive"
4115      (<eref target="http://purl.org/NET/http-errata#verscase"/>)
4116    </t>
4117    <t>
4118      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/2"/>:
4119      "'unsafe' characters"
4120      (<eref target="http://purl.org/NET/http-errata#unsafe-uri"/>)
4121    </t>
4122    <t>
4123      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/3"/>:
4124      "Chunk Size Definition"
4125      (<eref target="http://purl.org/NET/http-errata#chunk-size"/>)
4126    </t>
4127    <t>
4128      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/4"/>:
4129      "Message Length"
4130      (<eref target="http://purl.org/NET/http-errata#msg-len-chars"/>)
4131    </t>
4132    <t>
4133      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/8"/>:
4134      "Media Type Registrations"
4135      (<eref target="http://purl.org/NET/http-errata#media-reg"/>)
4136    </t>
4137    <t>
4138      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/11"/>:
4139      "URI includes query"
4140      (<eref target="http://purl.org/NET/http-errata#uriquery"/>)
4141    </t>
4142    <t>
4143      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/15"/>:
4144      "No close on 1xx responses"
4145      (<eref target="http://purl.org/NET/http-errata#noclose1xx"/>)
4146    </t>
4147    <t>
4148      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/16"/>:
4149      "Remove 'identity' token references"
4150      (<eref target="http://purl.org/NET/http-errata#identity"/>)
4151    </t>
4152    <t>
4153      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/26"/>:
4154      "Import query BNF"
4155    </t>
4156    <t>
4157      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/31"/>:
4158      "qdtext BNF"
4159    </t>
4160    <t>
4161      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
4162      "Normative and Informative references"
4163    </t>
4164    <t>
4165      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/42"/>:
4166      "RFC2606 Compliance"
4167    </t>
4168    <t>
4169      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/45"/>:
4170      "RFC977 reference"
4171    </t>
4172    <t>
4173      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46"/>:
4174      "RFC1700 references"
4175    </t>
4176    <t>
4177      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/47"/>:
4178      "inconsistency in date format explanation"
4179    </t>
4180    <t>
4181      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/48"/>:
4182      "Date reference typo"
4183    </t>
4184    <t>
4185      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/65"/>:
4186      "Informative references"
4187    </t>
4188    <t>
4189      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66"/>:
4190      "ISO-8859-1 Reference"
4191    </t>
4192    <t>
4193      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86"/>:
4194      "Normative up-to-date references"
4195    </t>
4196  </list>
4197</t>
4198<t>
4199  Other changes:
4200  <list style="symbols"> 
4201    <t>
4202      Update media type registrations to use RFC4288 template.
4203    </t>
4204    <t>
4205      Use names of RFC4234 core rules DQUOTE and HTAB,
4206      fix broken ABNF for chunk-data
4207      (work in progress on <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>)
4208    </t>
4209  </list>
4210</t>
4211</section>
4212
4213<section title="Since draft-ietf-httpbis-p1-messaging-01">
4214<t>
4215  Closed issues:
4216  <list style="symbols"> 
4217    <t>
4218      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/19"/>:
4219      "Bodies on GET (and other) requests"
4220    </t>
4221    <t>
4222      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/55"/>:
4223      "Updating to RFC4288"
4224    </t>
4225    <t>
4226      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/57"/>:
4227      "Status Code and Reason Phrase"
4228    </t>
4229    <t>
4230      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82"/>:
4231      "rel_path not used"
4232    </t>
4233  </list>
4234</t>
4235<t>
4236  Ongoing work on ABNF conversion (<eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
4237  <list style="symbols"> 
4238    <t>
4239      Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" ->
4240      "trailer-part").
4241    </t>
4242    <t>
4243      Avoid underscore character in rule names ("http_URL" ->
4244      "http-URL", "abs_path" -> "path-absolute").
4245    </t>
4246    <t>
4247      Add rules for terms imported from URI spec ("absoluteURI", "authority",
4248      "path-absolute", "port", "query", "relativeURI", "host) -- these will
4249      have to be updated when switching over to RFC3986.
4250    </t>
4251    <t>
4252      Synchronize core rules with RFC5234 (this includes a change to CHAR
4253      which now excludes NUL).
4254    </t>
4255    <t>
4256      Get rid of prose rules that span multiple lines.
4257    </t>
4258    <t>
4259      Get rid of unused rules LOALPHA and UPALPHA.
4260    </t>
4261    <t>
4262      Move "Product Tokens" section (back) into Part 1, as "token" is used
4263      in the definition of the Upgrade header.
4264    </t>
4265  </list>
4266</t>
4267</section>
4268
4269</section>
4270
4271</back>
4272</rfc>
Note: See TracBrowser for help on using the repository browser.