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

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

fix wierd section nesting -- must have been a paste-o

  • Property svn:eol-style set to native
File size: 222.9 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 "August">
16  <!ENTITY ID-YEAR "2009">
17  <!ENTITY caching-overview       "<xref target='Part6' x:rel='#caching.overview' 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-body            "<xref target='Part3' x:rel='#entity.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26  <!ENTITY entity-header-fields   "<xref target='Part3' x:rel='#entity.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
27  <!ENTITY header-cache-control   "<xref target='Part6' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
28  <!ENTITY header-expect          "<xref target='Part2' x:rel='#header.expect' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
29  <!ENTITY header-pragma          "<xref target='Part6' x:rel='#header.pragma' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
30  <!ENTITY header-warning         "<xref target='Part6' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
31  <!ENTITY idempotent-methods     "<xref target='Part2' x:rel='#idempotent.methods' 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 status-codes           "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
35  <!ENTITY status-100             "<xref target='Part2' x:rel='#status.100' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
36  <!ENTITY status-1xx             "<xref target='Part2' x:rel='#status.1xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
37  <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
38]>
39<?rfc toc="yes" ?>
40<?rfc symrefs="yes" ?>
41<?rfc sortrefs="yes" ?>
42<?rfc compact="yes"?>
43<?rfc subcompact="no" ?>
44<?rfc linkmailto="no" ?>
45<?rfc editing="no" ?>
46<?rfc comments="yes"?>
47<?rfc inline="yes"?>
48<?rfc-ext allow-markup-in-artwork="yes" ?>
49<?rfc-ext include-references-in-index="yes" ?>
50<rfc obsoletes="2616" category="std" x:maturity-level="draft"
51     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"
52     xmlns:x='http://purl.org/net/xml2rfc/ext'>
53<front>
54
55  <title abbrev="HTTP/1.1, Part 1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
56
57  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
58    <organization abbrev="Day Software">Day Software</organization>
59    <address>
60      <postal>
61        <street>23 Corporate Plaza DR, Suite 280</street>
62        <city>Newport Beach</city>
63        <region>CA</region>
64        <code>92660</code>
65        <country>USA</country>
66      </postal>
67      <phone>+1-949-706-5300</phone>
68      <facsimile>+1-949-706-5305</facsimile>
69      <email>fielding@gbiv.com</email>
70      <uri>http://roy.gbiv.com/</uri>
71    </address>
72  </author>
73
74  <author initials="J." surname="Gettys" fullname="Jim Gettys">
75    <organization>One Laptop per Child</organization>
76    <address>
77      <postal>
78        <street>21 Oak Knoll Road</street>
79        <city>Carlisle</city>
80        <region>MA</region>
81        <code>01741</code>
82        <country>USA</country>
83      </postal>
84      <email>jg@laptop.org</email>
85      <uri>http://www.laptop.org/</uri>
86    </address>
87  </author>
88 
89  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
90    <organization abbrev="HP">Hewlett-Packard Company</organization>
91    <address>
92      <postal>
93        <street>HP Labs, Large Scale Systems Group</street>
94        <street>1501 Page Mill Road, MS 1177</street>
95        <city>Palo Alto</city>
96        <region>CA</region>
97        <code>94304</code>
98        <country>USA</country>
99      </postal>
100      <email>JeffMogul@acm.org</email>
101    </address>
102  </author>
103
104  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
105    <organization abbrev="Microsoft">Microsoft Corporation</organization>
106    <address>
107      <postal>
108        <street>1 Microsoft Way</street>
109        <city>Redmond</city>
110        <region>WA</region>
111        <code>98052</code>
112        <country>USA</country>
113      </postal>
114      <email>henrikn@microsoft.com</email>
115    </address>
116  </author>
117
118  <author initials="L." surname="Masinter" fullname="Larry Masinter">
119    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
120    <address>
121      <postal>
122        <street>345 Park Ave</street>
123        <city>San Jose</city>
124        <region>CA</region>
125        <code>95110</code>
126        <country>USA</country>
127      </postal>
128      <email>LMM@acm.org</email>
129      <uri>http://larry.masinter.net/</uri>
130    </address>
131  </author>
132 
133  <author initials="P." surname="Leach" fullname="Paul J. Leach">
134    <organization abbrev="Microsoft">Microsoft Corporation</organization>
135    <address>
136      <postal>
137        <street>1 Microsoft Way</street>
138        <city>Redmond</city>
139        <region>WA</region>
140        <code>98052</code>
141      </postal>
142      <email>paulle@microsoft.com</email>
143    </address>
144  </author>
145   
146  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
147    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
148    <address>
149      <postal>
150        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
151        <street>The Stata Center, Building 32</street>
152        <street>32 Vassar Street</street>
153        <city>Cambridge</city>
154        <region>MA</region>
155        <code>02139</code>
156        <country>USA</country>
157      </postal>
158      <email>timbl@w3.org</email>
159      <uri>http://www.w3.org/People/Berners-Lee/</uri>
160    </address>
161  </author>
162
163  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
164    <organization abbrev="W3C">World Wide Web Consortium</organization>
165    <address>
166      <postal>
167        <street>W3C / ERCIM</street>
168        <street>2004, rte des Lucioles</street>
169        <city>Sophia-Antipolis</city>
170        <region>AM</region>
171        <code>06902</code>
172        <country>France</country>
173      </postal>
174      <email>ylafon@w3.org</email>
175      <uri>http://www.raubacapeu.net/people/yves/</uri>
176    </address>
177  </author>
178
179  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
180    <organization abbrev="greenbytes">greenbytes GmbH</organization>
181    <address>
182      <postal>
183        <street>Hafenweg 16</street>
184        <city>Muenster</city><region>NW</region><code>48155</code>
185        <country>Germany</country>
186      </postal>
187      <phone>+49 251 2807760</phone>
188      <facsimile>+49 251 2807761</facsimile>
189      <email>julian.reschke@greenbytes.de</email>
190      <uri>http://greenbytes.de/tech/webdav/</uri>
191    </address>
192  </author>
193
194  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
195  <workgroup>HTTPbis Working Group</workgroup>
196
197<abstract>
198<t>
199   The Hypertext Transfer Protocol (HTTP) is an application-level
200   protocol for distributed, collaborative, hypertext 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://tools.ietf.org/wg/httpbis/trac/report/11"/>
217    and related documents (including fancy diffs) can be found at
218    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
219  </t>
220  <t>
221    The changes in this draft are summarized in <xref target="changes.since.07"/>.
222  </t>
223</note>
224</front>
225<middle>
226<section title="Introduction" anchor="introduction">
227<t>
228   The Hypertext Transfer Protocol (HTTP) is an application-level
229   request/response protocol that uses extensible semantics and MIME-like
230   message payloads for flexible interaction with network-based hypertext
231   information systems. HTTP relies upon the Uniform Resource Identifier (URI)
232   standard <xref target="RFC3986"/> to indicate request targets and
233   relationships between resources.
234   Messages are passed in a format similar to that used by Internet mail
235   <xref target="RFC5322"/> and the Multipurpose Internet Mail Extensions
236   (MIME) <xref target="RFC2045"/> (see &diff2045entity; for the differences
237   between HTTP and MIME messages).
238</t>
239<t>
240   HTTP is a generic interface protocol for information systems. It is
241   designed to hide the details of how a service is implemented by presenting
242   a uniform interface to clients that is independent of the types of
243   resources provided. Likewise, servers do not need to be aware of each
244   client's purpose: an HTTP request can be considered in isolation rather
245   than being associated with a specific type of client or a predetermined
246   sequence of application steps. The result is a protocol that can be used
247   effectively in many different contexts and for which implementations can
248   evolve independently over time.
249</t>
250<t>
251   HTTP is also designed for use as a generic protocol for translating
252   communication to and from other Internet information systems.
253   HTTP proxies and gateways provide access to alternative information
254   services by translating their diverse protocols into a hypertext
255   format that can be viewed and manipulated by clients in the same way
256   as HTTP services.
257</t>
258<t>
259   One consequence of HTTP flexibility is that the protocol cannot be
260   defined in terms of what occurs behind the interface. Instead, we
261   are limited to defining the syntax of communication, the intent
262   of received communication, and the expected behavior of recipients.
263   If the communication is considered in isolation, then successful
264   actions should be reflected in corresponding changes to the
265   observable interface provided by servers. However, since multiple
266   clients may act in parallel and perhaps at cross-purposes, we
267   cannot require that such changes be observable beyond the scope
268   of a single response.
269</t>
270<t>
271   This document is Part 1 of the seven-part specification of HTTP,
272   defining the protocol referred to as "HTTP/1.1" and obsoleting
273   <xref target="RFC2616"/>.
274   Part 1 describes the architectural elements that are used or
275   referred to in HTTP, defines the "http" and "https" URI schemes,
276   describes overall network operation and connection management,
277   and defines HTTP message framing and forwarding requirements.
278   Our goal is to define all of the mechanisms necessary for HTTP message
279   handling that are independent of message semantics, thereby defining the
280   complete set of requirements for message parsers and
281   message-forwarding intermediaries.
282</t>
283
284<section title="Requirements" anchor="intro.requirements">
285<t>
286   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
287   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
288   document are to be interpreted as described in <xref target="RFC2119"/>.
289</t>
290<t>
291   An implementation is not compliant if it fails to satisfy one or more
292   of the &MUST; or &REQUIRED; level requirements for the protocols it
293   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
294   level and all the &SHOULD; level requirements for its protocols is said
295   to be "unconditionally compliant"; one that satisfies all the &MUST;
296   level requirements but not all the &SHOULD; level requirements for its
297   protocols is said to be "conditionally compliant."
298</t>
299</section>
300
301<section title="Syntax Notation" anchor="notation">
302<iref primary="true" item="Grammar" subitem="ALPHA"/>
303<iref primary="true" item="Grammar" subitem="CR"/>
304<iref primary="true" item="Grammar" subitem="CRLF"/>
305<iref primary="true" item="Grammar" subitem="CTL"/>
306<iref primary="true" item="Grammar" subitem="DIGIT"/>
307<iref primary="true" item="Grammar" subitem="DQUOTE"/>
308<iref primary="true" item="Grammar" subitem="HEXDIG"/>
309<iref primary="true" item="Grammar" subitem="LF"/>
310<iref primary="true" item="Grammar" subitem="OCTET"/>
311<iref primary="true" item="Grammar" subitem="SP"/>
312<iref primary="true" item="Grammar" subitem="VCHAR"/>
313<iref primary="true" item="Grammar" subitem="WSP"/>
314<t>
315   This specification uses the Augmented Backus-Naur Form (ABNF) notation
316   of <xref target="RFC5234"/>.
317</t>
318<t anchor="core.rules">
319  <x:anchor-alias value="ALPHA"/>
320  <x:anchor-alias value="CTL"/>
321  <x:anchor-alias value="CR"/>
322  <x:anchor-alias value="CRLF"/>
323  <x:anchor-alias value="DIGIT"/>
324  <x:anchor-alias value="DQUOTE"/>
325  <x:anchor-alias value="HEXDIG"/>
326  <x:anchor-alias value="LF"/>
327  <x:anchor-alias value="OCTET"/>
328  <x:anchor-alias value="SP"/>
329  <x:anchor-alias value="VCHAR"/>
330  <x:anchor-alias value="WSP"/>
331   The following core rules are included by
332   reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
333   ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
334   DIGIT (decimal 0-9), DQUOTE (double quote),
335   HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
336   OCTET (any 8-bit sequence of data), SP (space),
337   VCHAR (any visible <xref target="USASCII"/> character),
338   and WSP (whitespace).
339</t>
340
341<section title="ABNF Extension: #rule" anchor="notation.abnf">
342  <t>
343    One extension to the ABNF rules of <xref target="RFC5234"/> is used to
344    improve readability.
345  </t>
346  <t>
347    A construct "#" is defined, similar to "*", for defining lists of
348    elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating at least
349    &lt;n&gt; and at most &lt;m&gt; elements, each separated by a single comma
350    (",") and optional whitespace (OWS).   
351  </t>
352  <figure><preamble>
353    Thus,
354</preamble><artwork type="example">
355  1#element =&gt; element *( OWS "," OWS element )
356</artwork></figure>
357  <figure><preamble>
358    and:
359</preamble><artwork type="example">
360  #element =&gt; [ 1#element ]
361</artwork></figure>
362  <figure><preamble>
363    and for n &gt;= 1 and m &gt; 1:
364</preamble><artwork type="example">
365  &lt;n&gt;#&lt;m&gt;element =&gt; element &lt;n-1&gt;*&lt;m-1&gt;( OWS "," OWS element )
366</artwork></figure>
367  <t>
368    For compatibility with legacy list rules, recipients &SHOULD; accept empty
369    list elements. In other words, consumers would follow the list productions:
370  </t>
371<figure><artwork type="example">
372  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
373 
374  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
375</artwork></figure> 
376<t>
377  <xref target="collected.abnf"/> shows the collected ABNF, with the list rules
378  expanded as explained above.
379</t>
380</section>
381
382<section title="Basic Rules" anchor="basic.rules">
383<t anchor="rule.CRLF">
384  <x:anchor-alias value="CRLF"/>
385   HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all
386   protocol elements except the entity-body (see <xref target="tolerant.applications"/> for
387   tolerant applications). The end-of-line marker within an entity-body
388   is defined by its associated media type, as described in &media-types;.
389</t>
390<t anchor="rule.LWS">
391   This specification uses three rules to denote the use of linear
392   whitespace: OWS (optional whitespace), RWS (required whitespace), and
393   BWS ("bad" whitespace).
394</t>
395<t>
396   The OWS rule is used where zero or more linear whitespace characters may
397   appear. OWS &SHOULD; either not be produced or be produced as a single SP
398   character. Multiple OWS characters that occur within field-content &SHOULD;
399   be replaced with a single SP before interpreting the field value or
400   forwarding the message downstream.
401</t>
402<t>
403   RWS is used when at least one linear whitespace character is required to
404   separate field tokens. RWS &SHOULD; be produced as a single SP character.
405   Multiple RWS characters that occur within field-content &SHOULD; be
406   replaced with a single SP before interpreting the field value or
407   forwarding the message downstream.
408</t>
409<t>
410   BWS is used where the grammar allows optional whitespace for historical
411   reasons but senders &SHOULD-NOT; produce it in messages. HTTP/1.1
412   recipients &MUST; accept such bad optional whitespace and remove it before
413   interpreting the field value or forwarding the message downstream.
414</t>
415<t anchor="rule.whitespace">
416  <x:anchor-alias value="BWS"/>
417  <x:anchor-alias value="OWS"/>
418  <x:anchor-alias value="RWS"/>
419  <x:anchor-alias value="obs-fold"/>
420</t>
421<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OWS"/><iref primary="true" item="Grammar" subitem="RWS"/><iref primary="true" item="Grammar" subitem="BWS"/>
422  <x:ref>OWS</x:ref>            = *( [ obs-fold ] <x:ref>WSP</x:ref> )
423                 ; "optional" whitespace
424  <x:ref>RWS</x:ref>            = 1*( [ obs-fold ] <x:ref>WSP</x:ref> )
425                 ; "required" whitespace
426  <x:ref>BWS</x:ref>            = <x:ref>OWS</x:ref>
427                 ; "bad" whitespace
428  <x:ref>obs-fold</x:ref>       = <x:ref>CRLF</x:ref>
429                 ; see <xref target="header.fields"/>
430</artwork></figure>
431<t anchor="rule.token.separators">
432  <x:anchor-alias value="tchar"/>
433  <x:anchor-alias value="token"/>
434   Many HTTP/1.1 header field values consist of words separated by whitespace
435   or special characters. These special characters &MUST; be in a quoted
436   string to be used within a parameter value (as defined in
437   <xref target="transfer.codings"/>).
438</t>
439<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="token"/><iref primary="true" item="Grammar" subitem="tchar"/>
440  <x:ref>tchar</x:ref>          = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*"
441                 / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
442                 / <x:ref>DIGIT</x:ref> / <x:ref>ALPHA</x:ref>
443                 
444  <x:ref>token</x:ref>          = 1*<x:ref>tchar</x:ref>
445</artwork></figure>
446<t anchor="rule.quoted-string">
447  <x:anchor-alias value="quoted-string"/>
448  <x:anchor-alias value="qdtext"/>
449  <x:anchor-alias value="obs-text"/>
450   A string of text is parsed as a single word if it is quoted using
451   double-quote marks.
452</t>
453<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-string"/><iref primary="true" item="Grammar" subitem="qdtext"/><iref primary="true" item="Grammar" subitem="obs-text"/>
454  <x:ref>quoted-string</x:ref>  = <x:ref>DQUOTE</x:ref> *( <x:ref>qdtext</x:ref> / <x:ref>quoted-pair</x:ref> ) <x:ref>DQUOTE</x:ref>
455  <x:ref>qdtext</x:ref>         = <x:ref>OWS</x:ref> / %x21 / %x23-5B / %x5D-7E / <x:ref>obs-text</x:ref>
456                 ; <x:ref>OWS</x:ref> / &lt;<x:ref>VCHAR</x:ref> except <x:ref>DQUOTE</x:ref> and "\"&gt; / <x:ref>obs-text</x:ref> 
457  <x:ref>obs-text</x:ref>       = %x80-FF
458</artwork></figure>
459<t anchor="rule.quoted-pair">
460  <x:anchor-alias value="quoted-pair"/>
461  <x:anchor-alias value="quoted-text"/>
462   The backslash character ("\") &MAY; be used as a single-character
463   quoting mechanism only within quoted-string and comment constructs.
464</t>
465<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="quoted-text"/><iref primary="true" item="Grammar" subitem="quoted-pair"/>
466  <x:ref>quoted-text</x:ref>    = %x01-09 /
467                   %x0B-0C /
468                   %x0E-FF ; Characters excluding NUL, <x:ref>CR</x:ref> and <x:ref>LF</x:ref>
469  <x:ref>quoted-pair</x:ref>    = "\" <x:ref>quoted-text</x:ref>
470</artwork></figure>
471</section>
472
473<section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
474  <x:anchor-alias value="request-header"/>
475  <x:anchor-alias value="response-header"/>
476  <x:anchor-alias value="entity-body"/>
477  <x:anchor-alias value="entity-header"/>
478  <x:anchor-alias value="Cache-Control"/>
479  <x:anchor-alias value="Pragma"/>
480  <x:anchor-alias value="Warning"/>
481<t>
482  The ABNF rules below are defined in other parts:
483</t>
484<figure><!-- Part2--><artwork type="abnf2616">
485  <x:ref>request-header</x:ref>  = &lt;request-header, defined in &request-header-fields;&gt;
486  <x:ref>response-header</x:ref> = &lt;response-header, defined in &response-header-fields;&gt;
487</artwork></figure>
488<figure><!-- Part3--><artwork type="abnf2616">
489  <x:ref>entity-body</x:ref>     = &lt;entity-body, defined in &entity-body;&gt;
490  <x:ref>entity-header</x:ref>   = &lt;entity-header, defined in &entity-header-fields;&gt;
491</artwork></figure>
492<figure><!-- Part6--><artwork type="abnf2616">
493  <x:ref>Cache-Control</x:ref>   = &lt;Cache-Control, defined in &header-pragma;&gt;
494  <x:ref>Pragma</x:ref>          = &lt;Pragma, defined in &header-pragma;&gt;
495  <x:ref>Warning</x:ref>         = &lt;Warning, defined in &header-warning;&gt;
496</artwork></figure>
497</section>
498
499</section>
500</section>
501
502<section title="HTTP architecture" anchor="architecture">
503<t>
504   HTTP was created for the World Wide Web architecture
505   and has evolved over time to support the scalability needs of a worldwide
506   hypertext system. Much of that architecture is reflected in the terminology
507   and syntax productions used to define HTTP.
508</t>
509
510<section title="Client/Server Operation" anchor="operation">
511<iref item="client"/>
512<iref item="server"/>
513<iref item="connection"/>
514<t>
515   HTTP is a request/response protocol that operates by exchanging messages
516   across a reliable transport or session-layer connection. An HTTP client
517   is a program that establishes a connection to a server for the purpose
518   of sending one or more HTTP requests.  An HTTP server is a program that
519   accepts connections in order to service HTTP requests by sending HTTP
520   responses.
521</t>
522<iref item="user agent"/>
523<iref item="origin server"/>
524<t>
525   Note that the terms "client" and "server" refer only to the roles that
526   these programs perform for a particular connection.  The same program
527   may act as a client on some connections and a server on others.  We use
528   the term "user agent" to refer to the program that initiates a request,
529   such as a WWW browser, editor, or spider (web-traversing robot), and
530   the term "origin server" to refer to the program that can originate
531   authoritative responses to a request.
532</t>
533<t>
534   Most HTTP communication consists of a retrieval request (GET) for
535   a representation of some resource identified by a URI.  In the
536   simplest case, this may be accomplished via a single connection (v)
537   between the user agent (UA) and the origin server (O).
538</t>
539<figure><artwork type="drawing">
540       request chain ------------------------&gt;
541    UA -------------------v------------------- O
542       &lt;----------------------- response chain
543</artwork></figure>
544<iref item="message"/>
545<iref item="request"/>
546<iref item="response"/>
547<t>
548   A client sends an HTTP request to the server in the form of a request
549   message (<xref target="request"/>), beginning with a method, URI, and
550   protocol version, followed by MIME-like header fields containing
551   request modifiers, client information, and payload metadata, an empty
552   line, and finally the payload body (if any).
553   The server response (<xref target="response"/>) begins with a status line,
554   including the protocol version, a success or error code, and textual
555   reason phrase, followed by MIME-like header fields containing server
556   information, resource metadata, payload metadata, an empty line, and
557   finally the payload body (if any).
558</t>
559<t>
560   The following example illustrates a typical message exchange for a
561   GET request on the URI "http://www.example.com/hello.txt":
562</t>
563<figure><preamble>
564client request:
565</preamble><artwork  type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
566GET /hello.txt HTTP/1.1
567User-Agent: curl/7.16.3 libcurl/7.16.3 OpenSSL/0.9.7l zlib/1.2.3
568Host: www.example.com
569Accept: */*
570
571</artwork></figure>
572<figure><preamble>
573server response:
574</preamble><artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
575HTTP/1.1 200 OK
576Date: Mon, 27 Jul 2009 12:28:53 GMT
577Server: Apache
578Last-Modified: Wed, 22 Jul 2009 19:15:56 GMT
579ETag: "34aa387-d-1568eb00"
580Accept-Ranges: bytes
581Content-Length: <x:length-of target="exbody"/>
582Vary: Accept-Encoding
583Content-Type: text/plain
584
585<x:span anchor="exbody">Hello World!
586</x:span></artwork></figure>
587</section>
588
589<section title="Intermediaries" anchor="intermediaries">
590<t>
591   A more complicated situation occurs when one or more intermediaries
592   are present in the request/response chain. There are three common
593   forms of intermediary: proxy, gateway, and tunnel.  In some cases,
594   a single intermediary may act as an origin server, proxy, gateway,
595   or tunnel, switching behavior based on the nature of each request.
596</t>
597<figure><artwork type="drawing">
598       request chain --------------------------------------&gt;
599    UA -----v----- A -----v----- B -----v----- C -----v----- O
600       &lt;------------------------------------- response chain
601</artwork></figure>
602<t>
603   The figure above shows three intermediaries (A, B, and C) between the
604   user agent and origin server. A request or response message that
605   travels the whole chain will pass through four separate connections.
606   Some HTTP communication options
607   may apply only to the connection with the nearest, non-tunnel
608   neighbor, only to the end-points of the chain, or to all connections
609   along the chain. Although the diagram is linear, each participant may
610   be engaged in multiple, simultaneous communications. For example, B
611   may be receiving requests from many clients other than A, and/or
612   forwarding requests to servers other than C, at the same time that it
613   is handling A's request.
614</t>
615<t>
616<iref item="upstream"/><iref item="downstream"/>
617<iref item="inbound"/><iref item="outbound"/>
618   We use the terms "upstream" and "downstream" to describe various
619   requirements in relation to the directional flow of a message:
620   all messages flow from upstream to downstream.
621   Likewise, we use the terms "inbound" and "outbound" to refer to
622   directions in relation to the request path: "inbound" means toward
623   the origin server and "outbound" means toward the user agent.
624</t>
625<t><iref item="proxy"/>
626   A proxy is a message forwarding agent that is selected by the
627   client, usually via local configuration rules, to receive requests
628   for some type(s) of absolute URI and attempt to satisfy those
629   requests via translation through the HTTP interface.  Some translations
630   are minimal, such as for proxy requests for "http" URIs, whereas
631   other requests may require translation to and from entirely different
632   application-layer protocols. Proxies are often used to group an
633   organization's HTTP requests through a common intermediary for the
634   sake of security, annotation services, or shared caching.
635</t>
636<t><iref item="gateway"/><iref item="reverse proxy"/>
637   A gateway (a.k.a., reverse proxy) is a receiving agent that acts
638   as a layer above some other server(s) and translates the received
639   requests to the underlying server's protocol.  Gateways are often
640   used for load balancing or partitioning HTTP services across
641   multiple machines.
642   Unlike a proxy, a gateway receives requests as if it were the
643   origin server for the requested resource; the requesting client
644   will not be aware that it is communicating with a gateway.
645   A gateway communicates with the client as if the gateway is the
646   origin server and thus is subject to all of the requirements on
647   origin servers for that connection.  A gateway communicates
648   with inbound servers using any protocol it desires, including
649   private extensions to HTTP that are outside the scope of this
650   specification.
651</t>
652<t><iref item="tunnel"/>
653   A tunnel acts as a blind relay between two connections
654   without changing the messages. Once active, a tunnel is not
655   considered a party to the HTTP communication, though the tunnel may
656   have been initiated by an HTTP request. A tunnel ceases to exist when
657   both ends of the relayed connection are closed. Tunnels are used to
658   extend a virtual connection through an intermediary, such as when
659   transport-layer security is used to establish private communication
660   through a shared firewall proxy.
661</t>
662</section>
663
664<section title="Caches" anchor="caches">
665<iref item="cache"/>
666<t>
667   Any party to HTTP communication that is not acting as a tunnel may
668   employ an internal cache for handling requests.
669   A cache is a local store of previous response messages and the
670   subsystem that controls its message storage, retrieval, and deletion.
671   A cache stores cacheable responses in order to reduce the response
672   time and network bandwidth consumption on future, equivalent
673   requests. Any client or server may include a cache, though a cache
674   cannot be used by a server while it is acting as a tunnel.
675</t>
676<t>
677   The effect of a cache is that the request/response chain is shortened
678   if one of the participants along the chain has a cached response
679   applicable to that request. The following illustrates the resulting
680   chain if B has a cached copy of an earlier response from O (via C)
681   for a request which has not been cached by UA or A.
682</t>
683<figure><artwork type="drawing">
684          request chain ----------&gt;
685       UA -----v----- A -----v----- B - - - - - - C - - - - - - O
686          &lt;--------- response chain
687</artwork></figure>
688<t><iref item="cacheable"/>
689   A response is cacheable if a cache is allowed to store a copy of
690   the response message for use in answering subsequent requests.
691   Even when a response is cacheable, there may be additional
692   constraints placed by the client or by the origin server on when
693   that cached response can be used for a particular request. HTTP
694   requirements for cache behavior and cacheable responses are
695   defined in &caching-overview;
696</t>
697<t>
698   There are a wide variety of architectures and configurations
699   of caches and proxies deployed across the World Wide Web and
700   inside large organizations. These systems include national hierarchies
701   of proxy caches to save transoceanic bandwidth, systems that
702   broadcast or multicast cache entries, organizations that distribute
703   subsets of cached data via optical media, and so on.
704</t>
705</section>
706
707<section title="Transport Independence" anchor="transport-independence">
708<t>
709  HTTP systems are used in a wide variety of environments, from
710  corporate intranets with high-bandwidth links to long-distance
711  communication over low-power radio links and intermittent connectivity.
712</t>
713<t>
714   HTTP communication usually takes place over TCP/IP connections. The
715   default port is TCP 80 (<eref target="http://www.iana.org/assignments/port-numbers"/>), but other ports can be used. This does
716   not preclude HTTP from being implemented on top of any other protocol
717   on the Internet, or on other networks. HTTP only presumes a reliable
718   transport; any protocol that provides such guarantees can be used;
719   the mapping of the HTTP/1.1 request and response structures onto the
720   transport data units of the protocol in question is outside the scope
721   of this specification.
722</t>
723<t>
724   In HTTP/1.0, most implementations used a new connection for each
725   request/response exchange. In HTTP/1.1, a connection may be used for
726   one or more request/response exchanges, although connections may be
727   closed for a variety of reasons (see <xref target="persistent.connections"/>).
728</t>
729</section>
730
731<section title="HTTP Version" anchor="http.version">
732  <x:anchor-alias value="HTTP-Version"/>
733  <x:anchor-alias value="HTTP-Prot-Name"/>
734<t>
735   HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate versions
736   of the protocol. The protocol versioning policy is intended to allow
737   the sender to indicate the format of a message and its capacity for
738   understanding further HTTP communication, rather than the features
739   obtained via that communication. No change is made to the version
740   number for the addition of message components which do not affect
741   communication behavior or which only add to extensible field values.
742   The &lt;minor&gt; number is incremented when the changes made to the
743   protocol add features which do not change the general message parsing
744   algorithm, but which may add to the message semantics and imply
745   additional capabilities of the sender. The &lt;major&gt; number is
746   incremented when the format of a message within the protocol is
747   changed. See <xref target="RFC2145"/> for a fuller explanation.
748</t>
749<t>
750   The version of an HTTP message is indicated by an HTTP-Version field
751   in the first line of the message. HTTP-Version is case-sensitive.
752</t>
753<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-Version"/><iref primary="true" item="Grammar" subitem="HTTP-Prot-Name"/>
754  <x:ref>HTTP-Version</x:ref>   = <x:ref>HTTP-Prot-Name</x:ref> "/" 1*<x:ref>DIGIT</x:ref> "." 1*<x:ref>DIGIT</x:ref>
755  <x:ref>HTTP-Prot-Name</x:ref> = <x:abnf-char-sequence>"HTTP"</x:abnf-char-sequence> ; "HTTP", case-sensitive
756</artwork></figure>
757<t>
758   Note that the major and minor numbers &MUST; be treated as separate
759   integers and that each &MAY; be incremented higher than a single digit.
760   Thus, HTTP/2.4 is a lower version than HTTP/2.13, which in turn is
761   lower than HTTP/12.3. Leading zeros &MUST; be ignored by recipients and
762   &MUST-NOT; be sent.
763</t>
764<t>
765   An application that sends a request or response message that includes
766   HTTP-Version of "HTTP/1.1" &MUST; be at least conditionally compliant
767   with this specification. Applications that are at least conditionally
768   compliant with this specification &SHOULD; use an HTTP-Version of
769   "HTTP/1.1" in their messages, and &MUST; do so for any message that is
770   not compatible with HTTP/1.0. For more details on when to send
771   specific HTTP-Version values, see <xref target="RFC2145"/>.
772</t>
773<t>
774   The HTTP version of an application is the highest HTTP version for
775   which the application is at least conditionally compliant.
776</t>
777<t>
778   Proxy and gateway applications need to be careful when forwarding
779   messages in protocol versions different from that of the application.
780   Since the protocol version indicates the protocol capability of the
781   sender, a proxy/gateway &MUST-NOT; send a message with a version
782   indicator which is greater than its actual version. If a higher
783   version request is received, the proxy/gateway &MUST; either downgrade
784   the request version, or respond with an error, or switch to tunnel
785   behavior.
786</t>
787<t>
788   Due to interoperability problems with HTTP/1.0 proxies discovered
789   since the publication of <xref target="RFC2068"/>, caching proxies &MUST;, gateways
790   &MAY;, and tunnels &MUST-NOT; upgrade the request to the highest version
791   they support. The proxy/gateway's response to that request &MUST; be in
792   the same major version as the request.
793</t>
794<x:note>
795  <t>
796    <x:h>Note:</x:h> Converting between versions of HTTP may involve modification
797    of header fields required or forbidden by the versions involved.
798  </t>
799</x:note>
800</section>
801
802<section title="Uniform Resource Identifiers" anchor="uri">
803<iref primary="true" item="resource"/>
804<t>
805   Uniform Resource Identifiers (URIs) <xref target="RFC3986"/> are used
806   throughout HTTP as the means for identifying resources. URI references
807   are used to target requests, indicate redirects, and define relationships.
808   HTTP does not limit what a resource may be; it merely defines an interface
809   that can be used to interact with a resource via HTTP. More information on
810   the scope of URIs and resources can be found in <xref target="RFC3986"/>.
811</t>
812  <x:anchor-alias value="URI"/>
813  <x:anchor-alias value="URI-reference"/>
814  <x:anchor-alias value="absolute-URI"/>
815  <x:anchor-alias value="relative-part"/>
816  <x:anchor-alias value="authority"/>
817  <x:anchor-alias value="path-abempty"/>
818  <x:anchor-alias value="path-absolute"/>
819  <x:anchor-alias value="port"/>
820  <x:anchor-alias value="query"/>
821  <x:anchor-alias value="uri-host"/>
822  <x:anchor-alias value="partial-URI"/>
823<t>
824   This specification adopts the definitions of "URI-reference",
825   "absolute-URI", "relative-part", "port", "host",
826   "path-abempty", "path-absolute", "query", and "authority" from
827   <xref target="RFC3986"/>. In addition, we define a partial-URI rule for
828   protocol elements that allow a relative URI without a fragment.
829</t>
830<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="URI-reference"/><iref primary="true" item="Grammar" subitem="absolute-URI"/><iref primary="true" item="Grammar" subitem="authority"/><iref primary="true" item="Grammar" subitem="path-absolute"/><iref primary="true" item="Grammar" subitem="port"/><iref primary="true" item="Grammar" subitem="query"/><iref primary="true" item="Grammar" subitem="uri-host"/>
831  <x:ref>URI</x:ref>           = &lt;URI, defined in <xref target="RFC3986" x:fmt="," x:sec="3"/>&gt;
832  <x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in <xref target="RFC3986" x:fmt="," x:sec="4.1"/>&gt;
833  <x:ref>absolute-URI</x:ref>  = &lt;absolute-URI, defined in <xref target="RFC3986" x:fmt="," x:sec="4.3"/>&gt;
834  <x:ref>relative-part</x:ref> = &lt;relative-part, defined in <xref target="RFC3986" x:fmt="," x:sec="4.2"/>&gt;
835  <x:ref>authority</x:ref>     = &lt;authority, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2"/>&gt;
836  <x:ref>path-abempty</x:ref>  = &lt;path-abempty, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
837  <x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in <xref target="RFC3986" x:fmt="," x:sec="3.3"/>&gt;
838  <x:ref>port</x:ref>          = &lt;port, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.3"/>&gt;
839  <x:ref>query</x:ref>         = &lt;query, defined in <xref target="RFC3986" x:fmt="," x:sec="3.4"/>&gt;
840  <x:ref>uri-host</x:ref>      = &lt;host, defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>&gt;
841 
842  <x:ref>partial-URI</x:ref>   = relative-part [ "?" query ]
843</artwork></figure>
844<t>
845   Each protocol element in HTTP that allows a URI reference will indicate in
846   its ABNF production whether the element allows only a URI in absolute form
847   (absolute-URI), any relative reference (relative-ref), or some other subset
848   of the URI-reference grammar. Unless otherwise indicated, URI references
849   are parsed relative to the request target (the default base URI for both
850   the request and its corresponding response).
851</t>
852
853<section title="http URI scheme" anchor="http.uri">
854  <x:anchor-alias value="http-URI"/>
855  <iref item="http URI scheme" primary="true"/>
856  <iref item="URI scheme" subitem="http" primary="true"/>
857<t>
858   The "http" URI scheme is hereby defined for the purpose of minting
859   identifiers according to their association with the hierarchical
860   namespace governed by a potential HTTP origin server listening for
861   TCP connections on a given port.
862   The HTTP server is identified via the generic syntax's
863   <x:ref>authority</x:ref> component, which includes a host
864   identifier and optional TCP port, and the remainder of the URI is
865   considered to be identifying data corresponding to a resource for
866   which that server might provide an HTTP interface.
867</t>
868<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="http-URI"/>
869  <x:ref>http-URI</x:ref> = "http:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
870</artwork></figure>
871<t>
872   The host identifier within an <x:ref>authority</x:ref> component is
873   defined in <xref target="RFC3986" x:fmt="," x:sec="3.2.2"/>.  If host is
874   provided as an IP literal or IPv4 address, then the HTTP server is any
875   listener on the indicated TCP port at that IP address. If host is a
876   registered name, then that name is considered an indirect identifier
877   and the recipient might use a name resolution service, such as DNS,
878   to find the address of a listener for that host.
879   The host &MUST-NOT; be empty; if an "http" URI is received with an
880   empty host, then it &MUST; be rejected as invalid.
881   If the port subcomponent is empty or not given, then TCP port 80 is
882   assumed (the default reserved port for WWW services).
883</t>
884<t>
885   Regardless of the form of host identifier, access to that host is not
886   implied by the mere presence of its name or address. The host may or may
887   not exist and, even when it does exist, may or may not be running an
888   HTTP server or listening to the indicated port. The "http" URI scheme
889   makes use of the delegated nature of Internet names and addresses to
890   establish a naming authority (whatever entity has the ability to place
891   an HTTP server at that Internet name or address) and allows that
892   authority to determine which names are valid and how they might be used.
893</t>
894<t>
895   When an "http" URI is used within a context that calls for access to the
896   indicated resource, a client &MAY; attempt access by resolving
897   the host to an IP address, establishing a TCP connection to that address
898   on the indicated port, and sending an HTTP request message to the server
899   containing the URI's identifying data as described in <xref target="request"/>.
900   If the server responds to that request with a non-interim HTTP response
901   message, as described in <xref target="response"/>, then that response
902   is considered an authoritative answer to the client's request.
903</t>
904<t>
905   Although HTTP is independent of the transport protocol, the "http"
906   scheme is specific to TCP-based services because the name delegation
907   process depends on TCP for establishing authority.
908   An HTTP service based on some other underlying connection protocol
909   would presumably be identified using a different URI scheme, just as
910   the "https" scheme (below) is used for servers that require an SSL/TLS
911   transport layer on a connection. Other protocols may also be used to
912   provide access to "http" identified resources --- it is only the
913   authoritative interface used for mapping the namespace that is
914   specific to TCP.
915</t>
916</section>
917
918<section title="https URI scheme" anchor="https.uri">
919   <x:anchor-alias value="https-URI"/>
920   <iref item="https URI scheme"/>
921   <iref item="URI scheme" subitem="https"/>
922<t>
923   The "https" URI scheme is hereby defined for the purpose of minting
924   identifiers according to their association with the hierarchical
925   namespace governed by a potential HTTP origin server listening for
926   SSL/TLS-secured connections on a given TCP port.
927   The host and port are determined in the same way
928   as for the "http" scheme, except that a default TCP port of 443
929   is assumed if the port subcomponent is empty or not given.
930</t>
931<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="https-URI"/>
932  <x:ref>https-URI</x:ref> = "https:" "//" <x:ref>authority</x:ref> <x:ref>path-abempty</x:ref> [ "?" <x:ref>query</x:ref> ]
933</artwork></figure>
934<t>
935   The primary difference between the "http" and "https" schemes is
936   that interaction with the latter is required to be secured for
937   privacy through the use of strong encryption. The URI cannot be
938   sent in a request until the connection is secure. Likewise, the
939   default for caching is that each response that would be considered
940   "public" under the "http" scheme is instead treated as "private"
941   and thus not eligible for shared caching.
942</t>
943<t>
944   The process for authoritative access to an "https" identified
945   resource is defined in <xref target="RFC2818"/>.
946</t>
947</section>
948
949<section title="http and https URI Normalization and Comparison" anchor="uri.comparison">
950<t>
951   Since the "http" and "https" schemes conform to the URI generic syntax,
952   such URIs are normalized and compared according to the algorithm defined
953   in <xref target="RFC3986" x:fmt="," x:sec="6"/>, using the defaults
954   described above for each scheme.
955</t>
956<t>
957   If the port is equal to the default port for a scheme, the normal
958   form is to elide the port subcomponent. Likewise, an empty path
959   component is equivalent to an absolute path of "/", so the normal
960   form is to provide a path of "/" instead. The scheme and host
961   are case-insensitive and normally provided in lowercase; all
962   other components are compared in a case-sensitive manner.
963   Characters other than those in the "reserved" set are equivalent
964   to their percent-encoded octets (see <xref target="RFC3986"
965   x:fmt="," x:sec="2.1"/>): the normal form is to not encode them.
966</t>
967<t>
968   For example, the following three URIs are equivalent:
969</t>
970<figure><artwork type="example">
971   http://example.com:80/~smith/home.html
972   http://EXAMPLE.com/%7Esmith/home.html
973   http://EXAMPLE.com:/%7esmith/home.html
974</artwork></figure>
975<t>
976   <cref>[[This paragraph does not belong here. --Roy]]</cref>
977   If path-abempty is the empty string (i.e., there is no slash "/"
978   path separator following the authority), then the "http" URI
979   &MUST; be given as "/" when
980   used as a request-target (<xref target="request-target"/>). If a proxy
981   receives a host name which is not a fully qualified domain name, it
982   &MAY; add its domain to the host name it received. If a proxy receives
983   a fully qualified domain name, the proxy &MUST-NOT; change the host
984   name.
985</t>
986</section>
987</section>
988</section>
989
990<section title="HTTP Message" anchor="http.message">
991<x:anchor-alias value="generic-message"/>
992<x:anchor-alias value="message.types"/>
993<x:anchor-alias value="HTTP-message"/>
994<x:anchor-alias value="start-line"/>
995<iref item="header section"/>
996<iref item="headers"/>
997<iref item="header field"/>
998<t>
999   All HTTP/1.1 messages consist of a start-line followed by a sequence of
1000   characters in a format similar to the Internet Message Format
1001   <xref target="RFC5322"/>: zero or more header fields (collectively
1002   referred to as the "headers" or the "header section"), an empty line
1003   indicating the end of the header section, and an optional message-body.
1004</t>
1005<t>
1006   An HTTP message can either be a request from client to server or a
1007   response from server to client.  Syntactically, the two types of message
1008   differ only in the start-line, which is either a Request-Line (for requests)
1009   or a Status-Line (for responses), and in the algorithm for determining
1010   the length of the message-body (<xref target="message.length"/>).
1011   In theory, a client could receive requests and a server could receive
1012   responses, distinguishing them by their different start-line formats,
1013   but in practice servers are implemented to only expect a request
1014   (a response is interpreted as an unknown or invalid request method)
1015   and clients are implemented to only expect a response.
1016</t>
1017<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-message"/>
1018  <x:ref>HTTP-message</x:ref>    = <x:ref>start-line</x:ref>
1019                    *( <x:ref>header-field</x:ref> <x:ref>CRLF</x:ref> )
1020                    <x:ref>CRLF</x:ref>
1021                    [ <x:ref>message-body</x:ref> ]
1022  <x:ref>start-line</x:ref>      = <x:ref>Request-Line</x:ref> / <x:ref>Status-Line</x:ref>
1023</artwork></figure>
1024<t>
1025   Whitespace (WSP) &MUST-NOT; be sent between the start-line and the first
1026   header field. The presence of whitespace might be an attempt to trick a
1027   noncompliant implementation of HTTP into ignoring that field or processing
1028   the next line as a new request, either of which may result in security
1029   issues when implementations within the request chain interpret the
1030   same message differently. HTTP/1.1 servers &MUST; reject such a message
1031   with a 400 (Bad Request) response.
1032</t>
1033
1034<section title="Message Parsing Robustness" anchor="message.robustness">
1035<t>
1036   In the interest of robustness, servers &SHOULD; ignore at least one
1037   empty line received where a Request-Line is expected. In other words, if
1038   the server is reading the protocol stream at the beginning of a
1039   message and receives a CRLF first, it should ignore the CRLF.
1040</t>
1041<t>
1042   Some old HTTP/1.0 client implementations generate an extra CRLF
1043   after a POST request as a lame workaround for some early server
1044   applications that failed to read message-body content that was
1045   not terminated by a line-ending. An HTTP/1.1 client &MUST-NOT;
1046   preface or follow a request with an extra CRLF.  If terminating
1047   the request message-body with a line-ending is desired, then the
1048   client &MUST; include the terminating CRLF octets as part of the
1049   message-body length.
1050</t>
1051<t>
1052   The normal procedure for parsing an HTTP message is to read the
1053   start-line into a structure, read each header field into a hash
1054   table by field name until the empty line, and then use the parsed
1055   data to determine if a message-body is expected.  If a message-body
1056   has been indicated, then it is read as a stream until an amount
1057   of OCTETs equal to the message-length is read or the connection
1058   is closed.  Care must be taken to parse an HTTP message as a sequence
1059   of OCTETs in an encoding that is a superset of US-ASCII.  Attempting
1060   to parse HTTP as a stream of Unicode characters in a character encoding
1061   like UTF-16 may introduce security flaws due to the differing ways
1062   that such parsers interpret invalid characters.
1063</t>
1064</section>
1065
1066<section title="Header Fields" anchor="header.fields">
1067  <x:anchor-alias value="header-field"/>
1068  <x:anchor-alias value="field-content"/>
1069  <x:anchor-alias value="field-name"/>
1070  <x:anchor-alias value="field-value"/>
1071  <x:anchor-alias value="OWS"/>
1072<t>
1073   Each HTTP header field consists of a case-insensitive field name
1074   followed by a colon (":"), optional whitespace, and the field value.
1075</t>
1076<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="header-field"/><iref primary="true" item="Grammar" subitem="field-name"/><iref primary="true" item="Grammar" subitem="field-value"/><iref primary="true" item="Grammar" subitem="field-content"/>
1077  <x:ref>header-field</x:ref>   = <x:ref>field-name</x:ref> ":" OWS [ <x:ref>field-value</x:ref> ] OWS
1078  <x:ref>field-name</x:ref>     = <x:ref>token</x:ref>
1079  <x:ref>field-value</x:ref>    = *( <x:ref>field-content</x:ref> / <x:ref>OWS</x:ref> )
1080  <x:ref>field-content</x:ref>  = *( <x:ref>WSP</x:ref> / <x:ref>VCHAR</x:ref> / <x:ref>obs-text</x:ref> )
1081</artwork></figure>
1082<t>
1083   No whitespace is allowed between the header field name and colon. For
1084   security reasons, any request message received containing such whitespace
1085   &MUST; be rejected with a response code of 400 (Bad Request). A proxy
1086   &MUST; remove any such whitespace from a response message before
1087   forwarding the message downstream.
1088</t>
1089<t>
1090   A field value &MAY; be preceded by optional whitespace (OWS); a single SP is
1091   preferred. The field value does not include any leading or trailing white
1092   space: OWS occurring before the first non-whitespace character of the
1093   field value or after the last non-whitespace character of the field value
1094   is ignored and &SHOULD; be removed without changing the meaning of the header
1095   field.
1096</t>
1097<t>
1098   The order in which header fields with differing field names are
1099   received is not significant. However, it is "good practice" to send
1100   header fields that contain control data first, such as Host on
1101   requests and Date on responses, so that implementations can decide
1102   when not to handle a message as early as possible.  A server &MUST;
1103   wait until the entire header section is received before interpreting
1104   a request message, since later header fields might include conditionals,
1105   authentication credentials, or deliberately misleading duplicate
1106   header fields that would impact request processing.
1107</t>
1108<t>
1109   Multiple header fields with the same field name &MUST-NOT; be
1110   sent in a message unless the entire field value for that
1111   header field is defined as a comma-separated list [i.e., #(values)].
1112   Multiple header fields with the same field name can be combined into
1113   one "field-name: field-value" pair, without changing the semantics of the
1114   message, by appending each subsequent field value to the combined
1115   field value in order, separated by a comma. The order in which
1116   header fields with the same field name are received is therefore
1117   significant to the interpretation of the combined field value;
1118   a proxy &MUST-NOT; change the order of these field values when
1119   forwarding a message.
1120</t>
1121<x:note>
1122  <t>
1123   <x:h>Note:</x:h> the "Set-Cookie" header as implemented in
1124   practice (as opposed to how it is specified in <xref target="RFC2109"/>)
1125   can occur multiple times, but does not use the list syntax, and thus cannot
1126   be combined into a single line. (See Appendix A.2.3 of <xref target="Kri2001"/>
1127   for details.) Also note that the Set-Cookie2 header specified in
1128   <xref target="RFC2965"/> does not share this problem.
1129  </t>
1130</x:note>
1131<t>
1132   Historically, HTTP header field values could be extended over multiple
1133   lines by preceding each extra line with at least one space or horizontal
1134   tab character (line folding). This specification deprecates such line
1135   folding except within the message/http media type
1136   (<xref target="internet.media.type.message.http"/>).
1137   HTTP/1.1 senders &MUST-NOT; produce messages that include line folding
1138   (i.e., that contain any field-content that matches the obs-fold rule) unless
1139   the message is intended for packaging within the message/http media type.
1140   HTTP/1.1 recipients &SHOULD; accept line folding and replace any embedded
1141   obs-fold whitespace with a single SP prior to interpreting the field value
1142   or forwarding the message downstream.
1143</t>
1144<t>
1145   Historically, HTTP has allowed field content with text in the ISO-8859-1
1146   <xref target="ISO-8859-1"/> character encoding and supported other
1147   character sets only through use of <xref target="RFC2047"/> encoding.
1148   In practice, most HTTP header field values use only a subset of the
1149   US-ASCII character encoding <xref target="USASCII"/>. Newly defined
1150   header fields &SHOULD; limit their field values to US-ASCII characters.
1151   Recipients &SHOULD; treat other (obs-text) octets in field content as
1152   opaque data.
1153</t>
1154<t anchor="rule.comment">
1155  <x:anchor-alias value="comment"/>
1156  <x:anchor-alias value="ctext"/>
1157   Comments can be included in some HTTP header fields by surrounding
1158   the comment text with parentheses. Comments are only allowed in
1159   fields containing "comment" as part of their field value definition.
1160</t>
1161<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="comment"/><iref primary="true" item="Grammar" subitem="ctext"/>
1162  <x:ref>comment</x:ref>        = "(" *( <x:ref>ctext</x:ref> / <x:ref>quoted-pair</x:ref> / <x:ref>comment</x:ref> ) ")"
1163  <x:ref>ctext</x:ref>          = <x:ref>OWS</x:ref> / %x21-27 / %x2A-5B / %x5D-7E / <x:ref>obs-text</x:ref>
1164                 ; <x:ref>OWS</x:ref> / &lt;<x:ref>VCHAR</x:ref> except "(", ")", and "\"&gt; / <x:ref>obs-text</x:ref>
1165</artwork></figure>
1166 
1167</section>
1168
1169<section title="Message Body" anchor="message.body">
1170  <x:anchor-alias value="message-body"/>
1171<t>
1172   The message-body (if any) of an HTTP message is used to carry the
1173   entity-body associated with the request or response. The message-body
1174   differs from the entity-body only when a transfer-coding has been
1175   applied, as indicated by the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).
1176</t>
1177<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="message-body"/>
1178  <x:ref>message-body</x:ref> = <x:ref>entity-body</x:ref>
1179               / &lt;entity-body encoded as per <x:ref>Transfer-Encoding</x:ref>&gt;
1180</artwork></figure>
1181<t>
1182   Transfer-Encoding &MUST; be used to indicate any transfer-codings
1183   applied by an application to ensure safe and proper transfer of the
1184   message. Transfer-Encoding is a property of the message, not of the
1185   entity, and thus &MAY; be added or removed by any application along the
1186   request/response chain. (However, <xref target="transfer.codings"/> places restrictions on
1187   when certain transfer-codings may be used.)
1188</t>
1189<t>
1190   The rules for when a message-body is allowed in a message differ for
1191   requests and responses.
1192</t>
1193<t>
1194   The presence of a message-body in a request is signaled by the
1195   inclusion of a Content-Length or Transfer-Encoding header field in
1196   the request's header fields.
1197   When a request message contains both a message-body of non-zero
1198   length and a method that does not define any semantics for that
1199   request message-body, then an origin server &SHOULD; either ignore
1200   the message-body or respond with an appropriate error message
1201   (e.g., 413).  A proxy or gateway, when presented the same request,
1202   &SHOULD; either forward the request inbound with the message-body or
1203   ignore the message-body when determining a response.
1204</t>
1205<t>
1206   For response messages, whether or not a message-body is included with
1207   a message is dependent on both the request method and the response
1208   status code (<xref target="status.code.and.reason.phrase"/>). All responses to the HEAD request method
1209   &MUST-NOT; include a message-body, even though the presence of entity-header
1210   fields might lead one to believe they do. All 1xx
1211   (informational), 204 (No Content), and 304 (Not Modified) responses
1212   &MUST-NOT; include a message-body. All other responses do include a
1213   message-body, although it &MAY; be of zero length.
1214</t>
1215</section>
1216
1217<section title="Message Length" anchor="message.length">
1218<t>
1219   The transfer-length of a message is the length of the message-body as
1220   it appears in the message; that is, after any transfer-codings have
1221   been applied. When a message-body is included with a message, the
1222   transfer-length of that body is determined by one of the following
1223   (in order of precedence):
1224</t>
1225<t>
1226  <list style="numbers">
1227    <x:lt><t>
1228     Any response message which "&MUST-NOT;" include a message-body (such
1229     as the 1xx, 204, and 304 responses and any response to a HEAD
1230     request) is always terminated by the first empty line after the
1231     header fields, regardless of the entity-header fields present in
1232     the message.
1233    </t></x:lt>
1234    <x:lt><t>
1235     If a Transfer-Encoding header field (<xref target="header.transfer-encoding"/>)
1236     is present and the "chunked" transfer-coding (<xref target="transfer.codings"/>)
1237     is used, the transfer-length is defined by the use of this transfer-coding.
1238     If a Transfer-Encoding header field is present and the "chunked" transfer-coding
1239     is not present, the transfer-length is defined by the sender closing the connection.
1240    </t></x:lt>
1241    <x:lt><t>
1242     If a Content-Length header field (<xref target="header.content-length"/>) is present, its
1243     value in OCTETs represents both the entity-length and the
1244     transfer-length. The Content-Length header field &MUST-NOT; be sent
1245     if these two lengths are different (i.e., if a Transfer-Encoding
1246     header field is present). If a message is received with both a
1247     Transfer-Encoding header field and a Content-Length header field,
1248     the latter &MUST; be ignored.
1249    </t></x:lt>
1250    <x:lt><t>
1251     If the message uses the media type "multipart/byteranges", and the
1252     transfer-length is not otherwise specified, then this self-delimiting
1253     media type defines the transfer-length. This media type
1254     &MUST-NOT; be used unless the sender knows that the recipient can parse
1255     it; the presence in a request of a Range header with multiple byte-range
1256     specifiers from a 1.1 client implies that the client can parse
1257     multipart/byteranges responses.
1258    <list style="empty"><t>
1259       A range header might be forwarded by a 1.0 proxy that does not
1260       understand multipart/byteranges; in this case the server &MUST;
1261       delimit the message using methods defined in items 1, 3 or 5 of
1262       this section.
1263    </t></list>
1264    </t></x:lt>
1265    <x:lt><t>
1266     By the server closing the connection. (Closing the connection
1267     cannot be used to indicate the end of a request body, since that
1268     would leave no possibility for the server to send back a response.)
1269    </t></x:lt>
1270  </list>
1271</t>
1272<t>
1273   For compatibility with HTTP/1.0 applications, HTTP/1.1 requests
1274   containing a message-body &MUST; include a valid Content-Length header
1275   field unless the server is known to be HTTP/1.1 compliant. If a
1276   request contains a message-body and a Content-Length is not given,
1277   the server &SHOULD; respond with 400 (Bad Request) if it cannot
1278   determine the length of the message, or with 411 (Length Required) if
1279   it wishes to insist on receiving a valid Content-Length.
1280</t>
1281<t>
1282   All HTTP/1.1 applications that receive entities &MUST; accept the
1283   "chunked" transfer-coding (<xref target="transfer.codings"/>), thus allowing this mechanism
1284   to be used for messages when the message length cannot be determined
1285   in advance.
1286</t>
1287<t>
1288   Messages &MUST-NOT; include both a Content-Length header field and a
1289   transfer-coding. If the message does include a
1290   transfer-coding, the Content-Length &MUST; be ignored.
1291</t>
1292<t>
1293   When a Content-Length is given in a message where a message-body is
1294   allowed, its field value &MUST; exactly match the number of OCTETs in
1295   the message-body. HTTP/1.1 user agents &MUST; notify the user when an
1296   invalid length is received and detected.
1297</t>
1298</section>
1299
1300<section title="General Header Fields" anchor="general.header.fields">
1301  <x:anchor-alias value="general-header"/>
1302<t>
1303   There are a few header fields which have general applicability for
1304   both request and response messages, but which do not apply to the
1305   entity being transferred. These header fields apply only to the
1306   message being transmitted.
1307</t>
1308<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="general-header"/>
1309  <x:ref>general-header</x:ref> = <x:ref>Cache-Control</x:ref>            ; &header-cache-control;
1310                 / <x:ref>Connection</x:ref>               ; <xref target="header.connection"/>
1311                 / <x:ref>Date</x:ref>                     ; <xref target="header.date"/>
1312                 / <x:ref>Pragma</x:ref>                   ; &header-pragma;
1313                 / <x:ref>Trailer</x:ref>                  ; <xref target="header.trailer"/>
1314                 / <x:ref>Transfer-Encoding</x:ref>        ; <xref target="header.transfer-encoding"/>
1315                 / <x:ref>Upgrade</x:ref>                  ; <xref target="header.upgrade"/>
1316                 / <x:ref>Via</x:ref>                      ; <xref target="header.via"/>
1317                 / <x:ref>Warning</x:ref>                  ; &header-warning;
1318</artwork></figure>
1319<t>
1320   General-header field names can be extended reliably only in
1321   combination with a change in the protocol version. However, new or
1322   experimental header fields may be given the semantics of general
1323   header fields if all parties in the communication recognize them to
1324   be general-header fields. Unrecognized header fields are treated as
1325   entity-header fields.
1326</t>
1327</section>
1328</section>
1329
1330<section title="Request" anchor="request">
1331  <x:anchor-alias value="Request"/>
1332<t>
1333   A request message from a client to a server includes, within the
1334   first line of that message, the method to be applied to the resource,
1335   the identifier of the resource, and the protocol version in use.
1336</t>
1337<!--                 Host                      ; should be moved here eventually -->
1338<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Request"/>
1339  <x:ref>Request</x:ref>       = <x:ref>Request-Line</x:ref>              ; <xref target="request-line"/>
1340                  *(( <x:ref>general-header</x:ref>        ; <xref target="general.header.fields"/>
1341                   / <x:ref>request-header</x:ref>         ; &request-header-fields;
1342                   / <x:ref>entity-header</x:ref> ) <x:ref>CRLF</x:ref> ) ; &entity-header-fields;
1343                  <x:ref>CRLF</x:ref>
1344                  [ <x:ref>message-body</x:ref> ]          ; <xref target="message.body"/>
1345</artwork></figure>
1346
1347<section title="Request-Line" anchor="request-line">
1348  <x:anchor-alias value="Request-Line"/>
1349<t>
1350   The Request-Line begins with a method token, followed by the
1351   request-target and the protocol version, and ending with CRLF. The
1352   elements are separated by SP characters. No CR or LF is allowed
1353   except in the final CRLF sequence.
1354</t>
1355<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Request-Line"/>
1356  <x:ref>Request-Line</x:ref>   = <x:ref>Method</x:ref> <x:ref>SP</x:ref> <x:ref>request-target</x:ref> <x:ref>SP</x:ref> <x:ref>HTTP-Version</x:ref> <x:ref>CRLF</x:ref>
1357</artwork></figure>
1358
1359<section title="Method" anchor="method">
1360  <x:anchor-alias value="Method"/>
1361<t>
1362   The Method  token indicates the method to be performed on the
1363   resource identified by the request-target. The method is case-sensitive.
1364</t>
1365<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/><iref primary="true" item="Grammar" subitem="extension-method"/>
1366  <x:ref>Method</x:ref>         = <x:ref>token</x:ref>
1367</artwork></figure>
1368</section>
1369
1370<section title="request-target" anchor="request-target">
1371  <x:anchor-alias value="request-target"/>
1372<t>
1373   The request-target
1374   identifies the resource upon which to apply the request.
1375</t>
1376<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-target"/>
1377  <x:ref>request-target</x:ref> = "*"
1378                 / <x:ref>absolute-URI</x:ref>
1379                 / ( <x:ref>path-absolute</x:ref> [ "?" <x:ref>query</x:ref> ] )
1380                 / <x:ref>authority</x:ref>
1381</artwork></figure>
1382<t>
1383   The four options for request-target are dependent on the nature of the
1384   request. The asterisk "*" means that the request does not apply to a
1385   particular resource, but to the server itself, and is only allowed
1386   when the method used does not necessarily apply to a resource. One
1387   example would be
1388</t>
1389<figure><artwork type="example">
1390  OPTIONS * HTTP/1.1
1391</artwork></figure>
1392<t>
1393   The absolute-URI form is &REQUIRED; when the request is being made to a
1394   proxy. The proxy is requested to forward the request or service it
1395   from a valid cache, and return the response. Note that the proxy &MAY;
1396   forward the request on to another proxy or directly to the server
1397   specified by the absolute-URI. In order to avoid request loops, a
1398   proxy &MUST; be able to recognize all of its server names, including
1399   any aliases, local variations, and the numeric IP address. An example
1400   Request-Line would be:
1401</t>
1402<figure><artwork type="example">
1403  GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
1404</artwork></figure>
1405<t>
1406   To allow for transition to absolute-URIs in all requests in future
1407   versions of HTTP, all HTTP/1.1 servers &MUST; accept the absolute-URI
1408   form in requests, even though HTTP/1.1 clients will only generate
1409   them in requests to proxies.
1410</t>
1411<t>
1412   The authority form is only used by the CONNECT method (&CONNECT;).
1413</t>
1414<t>
1415   The most common form of request-target is that used to identify a
1416   resource on an origin server or gateway. In this case the absolute
1417   path of the URI &MUST; be transmitted (see <xref target="http.uri"/>, path-absolute) as
1418   the request-target, and the network location of the URI (authority) &MUST;
1419   be transmitted in a Host header field. For example, a client wishing
1420   to retrieve the resource above directly from the origin server would
1421   create a TCP connection to port 80 of the host "www.example.org" and send
1422   the lines:
1423</t>
1424<figure><artwork type="example">
1425  GET /pub/WWW/TheProject.html HTTP/1.1
1426  Host: www.example.org
1427</artwork></figure>
1428<t>
1429   followed by the remainder of the Request. Note that the absolute path
1430   cannot be empty; if none is present in the original URI, it &MUST; be
1431   given as "/" (the server root).
1432</t>
1433<t>
1434   If a proxy receives a request without any path in the request-target and
1435   the method specified is capable of supporting the asterisk form of
1436   request-target, then the last proxy on the request chain &MUST; forward the
1437   request with "*" as the final request-target.
1438</t>
1439<figure><preamble>   
1440   For example, the request
1441</preamble><artwork type="example">
1442  OPTIONS http://www.example.org:8001 HTTP/1.1
1443</artwork></figure>
1444<figure><preamble>   
1445  would be forwarded by the proxy as
1446</preamble><artwork type="example">
1447  OPTIONS * HTTP/1.1
1448  Host: www.example.org:8001
1449</artwork>
1450<postamble>
1451   after connecting to port 8001 of host "www.example.org".
1452</postamble>
1453</figure>
1454<t>
1455   The request-target is transmitted in the format specified in
1456   <xref target="http.uri"/>. If the request-target is percent-encoded
1457   (<xref target="RFC3986" x:fmt="," x:sec="2.1"/>), the origin server
1458   &MUST; decode the request-target in order to
1459   properly interpret the request. Servers &SHOULD; respond to invalid
1460   request-targets with an appropriate status code.
1461</t>
1462<t>
1463   A transparent proxy &MUST-NOT; rewrite the "path-absolute" part of the
1464   received request-target when forwarding it to the next inbound server,
1465   except as noted above to replace a null path-absolute with "/".
1466</t>
1467<x:note>
1468  <t>
1469    <x:h>Note:</x:h> The "no rewrite" rule prevents the proxy from changing the
1470    meaning of the request when the origin server is improperly using
1471    a non-reserved URI character for a reserved purpose.  Implementors
1472    should be aware that some pre-HTTP/1.1 proxies have been known to
1473    rewrite the request-target.
1474  </t>
1475</x:note>
1476<t>
1477   HTTP does not place a pre-defined limit on the length of a request-target.
1478   A server &MUST; be prepared to receive URIs of unbounded length and
1479   respond with the 414 (URI Too Long) status if the received
1480   request-target would be longer than the server wishes to handle
1481   (see &status-414;).
1482</t>
1483<t>
1484   Various ad-hoc limitations on request-target length are found in practice.
1485   It is &RECOMMENDED; that all HTTP senders and recipients support
1486   request-target lengths of 8000 or more OCTETs.
1487</t>
1488</section>
1489</section>
1490
1491<section title="The Resource Identified by a Request" anchor="the.resource.identified.by.a.request">
1492<t>
1493   The exact resource identified by an Internet request is determined by
1494   examining both the request-target and the Host header field.
1495</t>
1496<t>
1497   An origin server that does not allow resources to differ by the
1498   requested host &MAY; ignore the Host header field value when
1499   determining the resource identified by an HTTP/1.1 request. (But see
1500   <xref target="changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses"/>
1501   for other requirements on Host support in HTTP/1.1.)
1502</t>
1503<t>
1504   An origin server that does differentiate resources based on the host
1505   requested (sometimes referred to as virtual hosts or vanity host
1506   names) &MUST; use the following rules for determining the requested
1507   resource on an HTTP/1.1 request:
1508  <list style="numbers">
1509    <t>If request-target is an absolute-URI, the host is part of the
1510     request-target. Any Host header field value in the request &MUST; be
1511     ignored.</t>
1512    <t>If the request-target is not an absolute-URI, and the request includes
1513     a Host header field, the host is determined by the Host header
1514     field value.</t>
1515    <t>If the host as determined by rule 1 or 2 is not a valid host on
1516     the server, the response &MUST; be a 400 (Bad Request) error message.</t>
1517  </list>
1518</t>
1519<t>
1520   Recipients of an HTTP/1.0 request that lacks a Host header field &MAY;
1521   attempt to use heuristics (e.g., examination of the URI path for
1522   something unique to a particular host) in order to determine what
1523   exact resource is being requested.
1524</t>
1525</section>
1526
1527</section>
1528
1529
1530<section title="Response" anchor="response">
1531  <x:anchor-alias value="Response"/>
1532<t>
1533   After receiving and interpreting a request message, a server responds
1534   with an HTTP response message.
1535</t>
1536<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Response"/>
1537  <x:ref>Response</x:ref>      = <x:ref>Status-Line</x:ref>               ; <xref target="status-line"/>
1538                  *(( <x:ref>general-header</x:ref>        ; <xref target="general.header.fields"/>
1539                   / <x:ref>response-header</x:ref>        ; &response-header-fields;
1540                   / <x:ref>entity-header</x:ref> ) <x:ref>CRLF</x:ref> )  ; &entity-header-fields;
1541                  <x:ref>CRLF</x:ref>
1542                  [ <x:ref>message-body</x:ref> ]          ; <xref target="message.body"/>
1543</artwork></figure>
1544
1545<section title="Status-Line" anchor="status-line">
1546  <x:anchor-alias value="Status-Line"/>
1547<t>
1548   The first line of a Response message is the Status-Line, consisting
1549   of the protocol version followed by a numeric status code and its
1550   associated textual phrase, with each element separated by SP
1551   characters. No CR or LF is allowed except in the final CRLF sequence.
1552</t>
1553<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Status-Line"/>
1554  <x:ref>Status-Line</x:ref> = <x:ref>HTTP-Version</x:ref> <x:ref>SP</x:ref> <x:ref>Status-Code</x:ref> <x:ref>SP</x:ref> <x:ref>Reason-Phrase</x:ref> <x:ref>CRLF</x:ref>
1555</artwork></figure>
1556
1557<section title="Status Code and Reason Phrase" anchor="status.code.and.reason.phrase">
1558  <x:anchor-alias value="Reason-Phrase"/>
1559  <x:anchor-alias value="Status-Code"/>
1560<t>
1561   The Status-Code element is a 3-digit integer result code of the
1562   attempt to understand and satisfy the request. These codes are fully
1563   defined in &status-codes;.  The Reason Phrase exists for the sole
1564   purpose of providing a textual description associated with the numeric
1565   status code, out of deference to earlier Internet application protocols
1566   that were more frequently used with interactive text clients.
1567   A client &SHOULD; ignore the content of the Reason Phrase.
1568</t>
1569<t>
1570   The first digit of the Status-Code defines the class of response. The
1571   last two digits do not have any categorization role. There are 5
1572   values for the first digit:
1573  <list style="symbols">
1574    <t>
1575      1xx: Informational - Request received, continuing process
1576    </t>
1577    <t>
1578      2xx: Success - The action was successfully received,
1579        understood, and accepted
1580    </t>
1581    <t>
1582      3xx: Redirection - Further action must be taken in order to
1583        complete the request
1584    </t>
1585    <t>
1586      4xx: Client Error - The request contains bad syntax or cannot
1587        be fulfilled
1588    </t>
1589    <t>
1590      5xx: Server Error - The server failed to fulfill an apparently
1591        valid request
1592    </t>
1593  </list>
1594</t>
1595<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"/>
1596  <x:ref>Status-Code</x:ref>    = 3<x:ref>DIGIT</x:ref>
1597  <x:ref>Reason-Phrase</x:ref>  = *( <x:ref>WSP</x:ref> / <x:ref>VCHAR</x:ref> / <x:ref>obs-text</x:ref> )
1598</artwork></figure>
1599</section>
1600</section>
1601
1602</section>
1603
1604
1605<section title="Protocol Parameters" anchor="protocol.parameters">
1606
1607<section title="Date/Time Formats: Full Date" anchor="date.time.formats.full.date">
1608  <x:anchor-alias value="HTTP-date"/>
1609<t>
1610   HTTP applications have historically allowed three different formats
1611   for the representation of date/time stamps:
1612</t>
1613<figure><artwork type="example">
1614  Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
1615  Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
1616  Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
1617</artwork></figure>
1618<t>
1619   The first format is preferred as an Internet standard and represents
1620   a fixed-length subset of that defined by <xref target="RFC1123"/>. The
1621   other formats are described here only for
1622   compatibility with obsolete implementations.
1623   HTTP/1.1 clients and servers that parse the date value &MUST; accept
1624   all three formats (for compatibility with HTTP/1.0), though they &MUST;
1625   only generate the RFC 1123 format for representing HTTP-date values
1626   in header fields. See <xref target="tolerant.applications"/> for further information.
1627</t>
1628<t>
1629   All HTTP date/time stamps &MUST; be represented in Greenwich Mean Time
1630   (GMT), without exception. For the purposes of HTTP, GMT is exactly
1631   equal to UTC (Coordinated Universal Time). This is indicated in the
1632   first two formats by the inclusion of "GMT" as the three-letter
1633   abbreviation for time zone, and &MUST; be assumed when reading the
1634   asctime format. HTTP-date is case sensitive and &MUST-NOT; include
1635   additional whitespace beyond that specifically included as SP in the
1636   grammar.
1637</t>
1638<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-date"/>
1639  <x:ref>HTTP-date</x:ref>    = <x:ref>rfc1123-date</x:ref> / <x:ref>obs-date</x:ref>
1640</artwork></figure>
1641<t anchor="preferred.date.format">
1642  <x:anchor-alias value="rfc1123-date"/>
1643  <x:anchor-alias value="time-of-day"/>
1644  <x:anchor-alias value="hour"/>
1645  <x:anchor-alias value="minute"/>
1646  <x:anchor-alias value="second"/>
1647  <x:anchor-alias value="day-name"/>
1648  <x:anchor-alias value="day"/>
1649  <x:anchor-alias value="month"/>
1650  <x:anchor-alias value="year"/>
1651  <x:anchor-alias value="GMT"/>
1652  Preferred format:
1653</t>
1654<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="rfc1123-date"/><iref primary="true" item="Grammar" subitem="date1"/><iref primary="true" item="Grammar" subitem="time-of-day"/><iref primary="true" item="Grammar" subitem="hour"/><iref primary="true" item="Grammar" subitem="minute"/><iref primary="true" item="Grammar" subitem="second"/><iref primary="true" item="Grammar" subitem="day-name"/><iref primary="true" item="Grammar" subitem="day-name-l"/><iref primary="true" item="Grammar" subitem="day"/><iref primary="true" item="Grammar" subitem="month"/><iref primary="true" item="Grammar" subitem="year"/><iref primary="true" item="Grammar" subitem="GMT"/>
1655  <x:ref>rfc1123-date</x:ref> = <x:ref>day-name</x:ref> "," <x:ref>SP</x:ref> date1 <x:ref>SP</x:ref> <x:ref>time-of-day</x:ref> <x:ref>SP</x:ref> <x:ref>GMT</x:ref>
1656
1657  <x:ref>day-name</x:ref>     = <x:abnf-char-sequence>"Mon"</x:abnf-char-sequence> ; "Mon", case-sensitive
1658               / <x:abnf-char-sequence>"Tue"</x:abnf-char-sequence> ; "Tue", case-sensitive
1659               / <x:abnf-char-sequence>"Wed"</x:abnf-char-sequence> ; "Wed", case-sensitive
1660               / <x:abnf-char-sequence>"Thu"</x:abnf-char-sequence> ; "Thu", case-sensitive
1661               / <x:abnf-char-sequence>"Fri"</x:abnf-char-sequence> ; "Fri", case-sensitive
1662               / <x:abnf-char-sequence>"Sat"</x:abnf-char-sequence> ; "Sat", case-sensitive
1663               / <x:abnf-char-sequence>"Sun"</x:abnf-char-sequence> ; "Sun", case-sensitive
1664               
1665  <x:ref>date1</x:ref>        = <x:ref>day</x:ref> <x:ref>SP</x:ref> <x:ref>month</x:ref> <x:ref>SP</x:ref> <x:ref>year</x:ref>
1666               ; e.g., 02 Jun 1982
1667
1668  <x:ref>day</x:ref>          = 2<x:ref>DIGIT</x:ref>
1669  <x:ref>month</x:ref>        = <x:abnf-char-sequence>"Jan"</x:abnf-char-sequence> ; "Jan", case-sensitive
1670               / <x:abnf-char-sequence>"Feb"</x:abnf-char-sequence> ; "Feb", case-sensitive
1671               / <x:abnf-char-sequence>"Mar"</x:abnf-char-sequence> ; "Mar", case-sensitive
1672               / <x:abnf-char-sequence>"Apr"</x:abnf-char-sequence> ; "Apr", case-sensitive
1673               / <x:abnf-char-sequence>"May"</x:abnf-char-sequence> ; "May", case-sensitive
1674               / <x:abnf-char-sequence>"Jun"</x:abnf-char-sequence> ; "Jun", case-sensitive
1675               / <x:abnf-char-sequence>"Jul"</x:abnf-char-sequence> ; "Jul", case-sensitive
1676               / <x:abnf-char-sequence>"Aug"</x:abnf-char-sequence> ; "Aug", case-sensitive
1677               / <x:abnf-char-sequence>"Sep"</x:abnf-char-sequence> ; "Sep", case-sensitive
1678               / <x:abnf-char-sequence>"Oct"</x:abnf-char-sequence> ; "Oct", case-sensitive
1679               / <x:abnf-char-sequence>"Nov"</x:abnf-char-sequence> ; "Nov", case-sensitive
1680               / <x:abnf-char-sequence>"Dec"</x:abnf-char-sequence> ; "Dec", case-sensitive
1681  <x:ref>year</x:ref>         = 4<x:ref>DIGIT</x:ref>
1682
1683  <x:ref>GMT</x:ref>   = <x:abnf-char-sequence>"GMT"</x:abnf-char-sequence> ; "GMT", case-sensitive
1684
1685  <x:ref>time-of-day</x:ref>  = <x:ref>hour</x:ref> ":" <x:ref>minute</x:ref> ":" <x:ref>second</x:ref>
1686                 ; 00:00:00 - 23:59:59
1687                 
1688  <x:ref>hour</x:ref>         = 2<x:ref>DIGIT</x:ref>               
1689  <x:ref>minute</x:ref>       = 2<x:ref>DIGIT</x:ref>               
1690  <x:ref>second</x:ref>       = 2<x:ref>DIGIT</x:ref>               
1691</artwork></figure>
1692<t>
1693  The semantics of <x:ref>day-name</x:ref>, <x:ref>day</x:ref>,
1694  <x:ref>month</x:ref>, <x:ref>year</x:ref>, and <x:ref>time-of-day</x:ref> are the
1695  same as those defined for the RFC 5322 constructs
1696  with the corresponding name (<xref target="RFC5322" x:fmt="," x:sec="3.3"/>).
1697</t>
1698<t anchor="obsolete.date.formats">
1699  <x:anchor-alias value="obs-date"/>
1700  <x:anchor-alias value="rfc850-date"/>
1701  <x:anchor-alias value="asctime-date"/>
1702  <x:anchor-alias value="date1"/>
1703  <x:anchor-alias value="date2"/>
1704  <x:anchor-alias value="date3"/>
1705  <x:anchor-alias value="rfc1123-date"/>
1706  <x:anchor-alias value="day-name-l"/>
1707  Obsolete formats:
1708</t>
1709<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="obs-date"/>
1710  <x:ref>obs-date</x:ref>     = <x:ref>rfc850-date</x:ref> / <x:ref>asctime-date</x:ref> 
1711</artwork></figure>
1712<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="rfc850-date"/>
1713  <x:ref>rfc850-date</x:ref>  = <x:ref>day-name-l</x:ref> "," <x:ref>SP</x:ref> <x:ref>date2</x:ref> <x:ref>SP</x:ref> <x:ref>time-of-day</x:ref> <x:ref>SP</x:ref> <x:ref>GMT</x:ref>
1714  <x:ref>date2</x:ref>        = <x:ref>day</x:ref> "-" <x:ref>month</x:ref> "-" 2<x:ref>DIGIT</x:ref>
1715                 ; day-month-year (e.g., 02-Jun-82)
1716
1717  <x:ref>day-name-l</x:ref>   = <x:abnf-char-sequence>"Monday"</x:abnf-char-sequence> ; "Monday", case-sensitive
1718         / <x:abnf-char-sequence>"Tuesday"</x:abnf-char-sequence> ; "Tuesday", case-sensitive
1719         / <x:abnf-char-sequence>"Wednesday"</x:abnf-char-sequence> ; "Wednesday", case-sensitive
1720         / <x:abnf-char-sequence>"Thursday"</x:abnf-char-sequence> ; "Thursday", case-sensitive
1721         / <x:abnf-char-sequence>"Friday"</x:abnf-char-sequence> ; "Friday", case-sensitive
1722         / <x:abnf-char-sequence>"Saturday"</x:abnf-char-sequence> ; "Saturday", case-sensitive
1723         / <x:abnf-char-sequence>"Sunday"</x:abnf-char-sequence> ; "Sunday", case-sensitive
1724</artwork></figure>
1725<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="asctime-date"/>
1726  <x:ref>asctime-date</x:ref> = <x:ref>day-name</x:ref> <x:ref>SP</x:ref> <x:ref>date3</x:ref> <x:ref>SP</x:ref> <x:ref>time-of-day</x:ref> <x:ref>SP</x:ref> <x:ref>year</x:ref>
1727  <x:ref>date3</x:ref>        = <x:ref>month</x:ref> <x:ref>SP</x:ref> ( 2<x:ref>DIGIT</x:ref> / ( <x:ref>SP</x:ref> 1<x:ref>DIGIT</x:ref> ))
1728                 ; month day (e.g., Jun  2)
1729</artwork></figure>
1730<x:note>
1731  <t>
1732    <x:h>Note:</x:h> Recipients of date values are encouraged to be robust in
1733    accepting date values that may have been sent by non-HTTP
1734    applications, as is sometimes the case when retrieving or posting
1735    messages via proxies/gateways to SMTP or NNTP.
1736  </t>
1737</x:note>
1738<x:note>
1739  <t>
1740    <x:h>Note:</x:h> HTTP requirements for the date/time stamp format apply only
1741    to their usage within the protocol stream. Clients and servers are
1742    not required to use these formats for user presentation, request
1743    logging, etc.
1744  </t>
1745</x:note>
1746</section>
1747
1748<section title="Transfer Codings" anchor="transfer.codings">
1749  <x:anchor-alias value="transfer-coding"/>
1750  <x:anchor-alias value="transfer-extension"/>
1751<t>
1752   Transfer-coding values are used to indicate an encoding
1753   transformation that has been, can be, or may need to be applied to an
1754   entity-body in order to ensure "safe transport" through the network.
1755   This differs from a content coding in that the transfer-coding is a
1756   property of the message, not of the original entity.
1757</t>
1758<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-coding"/><iref primary="true" item="Grammar" subitem="transfer-extension"/>
1759  <x:ref>transfer-coding</x:ref>         = "chunked" ; <xref target="chunked.encoding"/>
1760                          / "compress" ; <xref target="compress.coding"/>
1761                          / "deflate" ; <xref target="deflate.coding"/>
1762                          / "gzip" ; <xref target="gzip.coding"/>
1763                          / <x:ref>transfer-extension</x:ref>
1764  <x:ref>transfer-extension</x:ref>      = <x:ref>token</x:ref> *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>transfer-parameter</x:ref> )
1765</artwork></figure>
1766<t anchor="rule.parameter">
1767  <x:anchor-alias value="attribute"/>
1768  <x:anchor-alias value="transfer-parameter"/>
1769  <x:anchor-alias value="value"/>
1770   Parameters are in  the form of attribute/value pairs.
1771</t>
1772<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="transfer-parameter"/><iref primary="true" item="Grammar" subitem="attribute"/><iref primary="true" item="Grammar" subitem="value"/><iref primary="true" item="Grammar" subitem="date2"/><iref primary="true" item="Grammar" subitem="date3"/>
1773  <x:ref>transfer-parameter</x:ref>      = <x:ref>attribute</x:ref> <x:ref>BWS</x:ref> "=" <x:ref>BWS</x:ref> <x:ref>value</x:ref>
1774  <x:ref>attribute</x:ref>               = <x:ref>token</x:ref>
1775  <x:ref>value</x:ref>                   = <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref>
1776</artwork></figure>
1777<t>
1778   All transfer-coding values are case-insensitive. HTTP/1.1 uses
1779   transfer-coding values in the TE header field (<xref target="header.te"/>) and in
1780   the Transfer-Encoding header field (<xref target="header.transfer-encoding"/>).
1781</t>
1782<t>
1783   Whenever a transfer-coding is applied to a message-body, the set of
1784   transfer-codings &MUST; include "chunked", unless the message indicates it
1785   is terminated by closing the connection. When the "chunked" transfer-coding
1786   is used, it &MUST; be the last transfer-coding applied to the
1787   message-body. The "chunked" transfer-coding &MUST-NOT; be applied more
1788   than once to a message-body. These rules allow the recipient to
1789   determine the transfer-length of the message (<xref target="message.length"/>).
1790</t>
1791<t>
1792   Transfer-codings are analogous to the Content-Transfer-Encoding values of
1793   MIME, which were designed to enable safe transport of binary data over a
1794   7-bit transport service (<xref target="RFC2045" x:fmt="," x:sec="6"/>).
1795   However, safe transport
1796   has a different focus for an 8bit-clean transfer protocol. In HTTP,
1797   the only unsafe characteristic of message-bodies is the difficulty in
1798   determining the exact body length (<xref target="message.length"/>), or the desire to
1799   encrypt data over a shared transport.
1800</t>
1801<t>
1802   A server which receives an entity-body with a transfer-coding it does
1803   not understand &SHOULD; return 501 (Not Implemented), and close the
1804   connection. A server &MUST-NOT; send transfer-codings to an HTTP/1.0
1805   client.
1806</t>
1807
1808<section title="Chunked Transfer Coding" anchor="chunked.encoding">
1809  <iref item="chunked (Coding Format)"/>
1810  <iref item="Coding Format" subitem="chunked"/>
1811  <x:anchor-alias value="chunk"/>
1812  <x:anchor-alias value="Chunked-Body"/>
1813  <x:anchor-alias value="chunk-data"/>
1814  <x:anchor-alias value="chunk-ext"/>
1815  <x:anchor-alias value="chunk-ext-name"/>
1816  <x:anchor-alias value="chunk-ext-val"/>
1817  <x:anchor-alias value="chunk-size"/>
1818  <x:anchor-alias value="last-chunk"/>
1819  <x:anchor-alias value="trailer-part"/>
1820<t>
1821   The chunked encoding modifies the body of a message in order to
1822   transfer it as a series of chunks, each with its own size indicator,
1823   followed by an &OPTIONAL; trailer containing entity-header fields. This
1824   allows dynamically produced content to be transferred along with the
1825   information necessary for the recipient to verify that it has
1826   received the full message.
1827</t>
1828<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Chunked-Body"/><iref primary="true" item="Grammar" subitem="chunk"/><iref primary="true" item="Grammar" subitem="chunk-size"/><iref primary="true" item="Grammar" subitem="last-chunk"/><iref primary="true" item="Grammar" subitem="chunk-ext"/><iref primary="true" item="Grammar" subitem="chunk-ext-name"/><iref primary="true" item="Grammar" subitem="chunk-ext-val"/><iref primary="true" item="Grammar" subitem="chunk-data"/><iref primary="true" item="Grammar" subitem="trailer-part"/>
1829  <x:ref>Chunked-Body</x:ref>   = *<x:ref>chunk</x:ref>
1830                   <x:ref>last-chunk</x:ref>
1831                   <x:ref>trailer-part</x:ref>
1832                   <x:ref>CRLF</x:ref>
1833 
1834  <x:ref>chunk</x:ref>          = <x:ref>chunk-size</x:ref> *WSP [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
1835                   <x:ref>chunk-data</x:ref> <x:ref>CRLF</x:ref>
1836  <x:ref>chunk-size</x:ref>     = 1*<x:ref>HEXDIG</x:ref>
1837  <x:ref>last-chunk</x:ref>     = 1*("0") *WSP [ <x:ref>chunk-ext</x:ref> ] <x:ref>CRLF</x:ref>
1838 
1839  <x:ref>chunk-ext</x:ref>      = *( ";" *WSP <x:ref>chunk-ext-name</x:ref>
1840                      [ "=" <x:ref>chunk-ext-val</x:ref> ] *WSP )
1841  <x:ref>chunk-ext-name</x:ref> = <x:ref>token</x:ref>
1842  <x:ref>chunk-ext-val</x:ref>  = <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref>
1843  <x:ref>chunk-data</x:ref>     = 1*<x:ref>OCTET</x:ref> ; a sequence of chunk-size octets
1844  <x:ref>trailer-part</x:ref>   = *( <x:ref>entity-header</x:ref> <x:ref>CRLF</x:ref> )
1845</artwork></figure>
1846<t>
1847   The chunk-size field is a string of hex digits indicating the size of
1848   the chunk-data in octets. The chunked encoding is ended by any chunk whose size is
1849   zero, followed by the trailer, which is terminated by an empty line.
1850</t>
1851<t>
1852   The trailer allows the sender to include additional HTTP header
1853   fields at the end of the message. The Trailer header field can be
1854   used to indicate which header fields are included in a trailer (see
1855   <xref target="header.trailer"/>).
1856</t>
1857<t>
1858   A server using chunked transfer-coding in a response &MUST-NOT; use the
1859   trailer for any header fields unless at least one of the following is
1860   true:
1861  <list style="numbers">
1862    <t>the request included a TE header field that indicates "trailers" is
1863     acceptable in the transfer-coding of the  response, as described in
1864     <xref target="header.te"/>; or,</t>
1865
1866    <t>the server is the origin server for the response, the trailer
1867     fields consist entirely of optional metadata, and the recipient
1868     could use the message (in a manner acceptable to the origin server)
1869     without receiving this metadata.  In other words, the origin server
1870     is willing to accept the possibility that the trailer fields might
1871     be silently discarded along the path to the client.</t>
1872  </list>
1873</t>
1874<t>
1875   This requirement prevents an interoperability failure when the
1876   message is being received by an HTTP/1.1 (or later) proxy and
1877   forwarded to an HTTP/1.0 recipient. It avoids a situation where
1878   compliance with the protocol would have necessitated a possibly
1879   infinite buffer on the proxy.
1880</t>
1881<t>
1882   A process for decoding the "chunked" transfer-coding
1883   can be represented in pseudo-code as:
1884</t>
1885<figure><artwork type="code">
1886  length := 0
1887  read chunk-size, chunk-ext (if any) and CRLF
1888  while (chunk-size &gt; 0) {
1889     read chunk-data and CRLF
1890     append chunk-data to entity-body
1891     length := length + chunk-size
1892     read chunk-size and CRLF
1893  }
1894  read entity-header
1895  while (entity-header not empty) {
1896     append entity-header to existing header fields
1897     read entity-header
1898  }
1899  Content-Length := length
1900  Remove "chunked" from Transfer-Encoding
1901</artwork></figure>
1902<t>
1903   All HTTP/1.1 applications &MUST; be able to receive and decode the
1904   "chunked" transfer-coding, and &MUST; ignore chunk-ext extensions
1905   they do not understand.
1906</t>
1907</section>
1908
1909<section title="Compression Codings" anchor="compression.codings">
1910<t>
1911   The codings defined below can be used to compress the payload of a
1912   message.
1913</t>
1914<x:note><t>
1915   <x:h>Note:</x:h> Use of program names for the identification of encoding formats
1916   is not desirable and is discouraged for future encodings. Their
1917   use here is representative of historical practice, not good
1918   design.
1919</t></x:note>
1920<x:note><t>
1921   <x:h>Note:</x:h> For compatibility with previous implementations of HTTP,
1922   applications &SHOULD; consider "x-gzip" and "x-compress" to be
1923   equivalent to "gzip" and "compress" respectively.
1924</t></x:note>
1925
1926<section title="Compress Coding" anchor="compress.coding">
1927<iref item="compress (Coding Format)"/>
1928<iref item="Coding Format" subitem="compress"/>
1929<t>
1930   The "compress" format is produced by the common UNIX file compression
1931   program "compress". This format is an adaptive Lempel-Ziv-Welch
1932   coding (LZW).
1933</t>
1934</section>
1935
1936<section title="Deflate Coding" anchor="deflate.coding">
1937<iref item="deflate (Coding Format)"/>
1938<iref item="Coding Format" subitem="deflate"/>
1939<t>
1940   The "zlib" format is defined in <xref target="RFC1950"/> in combination with
1941   the "deflate" compression mechanism described in <xref target="RFC1951"/>.
1942</t>
1943</section>
1944
1945<section title="Gzip Coding" anchor="gzip.coding">
1946<iref item="gzip (Coding Format)"/>
1947<iref item="Coding Format" subitem="gzip"/>
1948<t>
1949   The "gzip" format is produced by the file compression program
1950   "gzip" (GNU zip), as described in <xref target="RFC1952"/>. This format is a
1951   Lempel-Ziv coding (LZ77) with a 32 bit CRC.
1952</t>
1953</section>
1954
1955</section>
1956
1957<section title="Transfer Coding Registry" anchor="transfer.coding.registry">
1958<t>
1959   The HTTP Transfer Coding Registry defines the name space for the transfer
1960   coding names.
1961</t>
1962<t>
1963   Registrations &MUST; include the following fields:
1964   <list style="symbols">
1965     <t>Name</t>
1966     <t>Description</t>
1967     <t>Pointer to specification text</t>
1968   </list>
1969</t>
1970<t>
1971   Values to be added to this name space require expert review and a specification
1972   (see "Expert Review" and "Specification Required" in
1973   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
1974   conform to the purpose of transfer coding defined in this section.
1975</t>
1976<t>
1977   The registry itself is maintained at
1978   <eref target="http://www.iana.org/assignments/http-parameters"/>.
1979</t>
1980</section>
1981</section>
1982
1983<section title="Product Tokens" anchor="product.tokens">
1984  <x:anchor-alias value="product"/>
1985  <x:anchor-alias value="product-version"/>
1986<t>
1987   Product tokens are used to allow communicating applications to
1988   identify themselves by software name and version. Most fields using
1989   product tokens also allow sub-products which form a significant part
1990   of the application to be listed, separated by whitespace. By
1991   convention, the products are listed in order of their significance
1992   for identifying the application.
1993</t>
1994<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="product"/><iref primary="true" item="Grammar" subitem="product-version"/>
1995  <x:ref>product</x:ref>         = <x:ref>token</x:ref> ["/" <x:ref>product-version</x:ref>]
1996  <x:ref>product-version</x:ref> = <x:ref>token</x:ref>
1997</artwork></figure>
1998<t>
1999   Examples:
2000</t>
2001<figure><artwork type="example">
2002  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
2003  Server: Apache/0.8.4
2004</artwork></figure>
2005<t>
2006   Product tokens &SHOULD; be short and to the point. They &MUST-NOT; be
2007   used for advertising or other non-essential information. Although any
2008   token character &MAY; appear in a product-version, this token &SHOULD;
2009   only be used for a version identifier (i.e., successive versions of
2010   the same product &SHOULD; only differ in the product-version portion of
2011   the product value).
2012</t>
2013</section>
2014
2015<section title="Quality Values" anchor="quality.values">
2016  <x:anchor-alias value="qvalue"/>
2017<t>
2018   Both transfer codings (TE request header, <xref target="header.te"/>)
2019   and content negotiation (&content.negotiation;) use short "floating point"
2020   numbers to indicate the relative importance ("weight") of various
2021   negotiable parameters.  A weight is normalized to a real number in
2022   the range 0 through 1, where 0 is the minimum and 1 the maximum
2023   value. If a parameter has a quality value of 0, then content with
2024   this parameter is `not acceptable' for the client. HTTP/1.1
2025   applications &MUST-NOT; generate more than three digits after the
2026   decimal point. User configuration of these values &SHOULD; also be
2027   limited in this fashion.
2028</t>
2029<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="qvalue"/>
2030  <x:ref>qvalue</x:ref>         = ( "0" [ "." 0*3<x:ref>DIGIT</x:ref> ] )
2031                 / ( "1" [ "." 0*3("0") ] )
2032</artwork></figure>
2033<x:note>
2034  <t>
2035     <x:h>Note:</x:h> "Quality values" is a misnomer, since these values merely represent
2036     relative degradation in desired quality.
2037  </t>
2038</x:note>
2039</section>
2040
2041</section>
2042
2043<section title="Connections" anchor="connections">
2044
2045<section title="Persistent Connections" anchor="persistent.connections">
2046
2047<section title="Purpose" anchor="persistent.purpose">
2048<t>
2049   Prior to persistent connections, a separate TCP connection was
2050   established to fetch each URL, increasing the load on HTTP servers
2051   and causing congestion on the Internet. The use of inline images and
2052   other associated data often require a client to make multiple
2053   requests of the same server in a short amount of time. Analysis of
2054   these performance problems and results from a prototype
2055   implementation are available <xref target="Pad1995"/> <xref target="Spe"/>. Implementation experience and
2056   measurements of actual HTTP/1.1 implementations show good
2057   results <xref target="Nie1997"/>. Alternatives have also been explored, for example,
2058   T/TCP <xref target="Tou1998"/>.
2059</t>
2060<t>
2061   Persistent HTTP connections have a number of advantages:
2062  <list style="symbols">
2063      <t>
2064        By opening and closing fewer TCP connections, CPU time is saved
2065        in routers and hosts (clients, servers, proxies, gateways,
2066        tunnels, or caches), and memory used for TCP protocol control
2067        blocks can be saved in hosts.
2068      </t>
2069      <t>
2070        HTTP requests and responses can be pipelined on a connection.
2071        Pipelining allows a client to make multiple requests without
2072        waiting for each response, allowing a single TCP connection to
2073        be used much more efficiently, with much lower elapsed time.
2074      </t>
2075      <t>
2076        Network congestion is reduced by reducing the number of packets
2077        caused by TCP opens, and by allowing TCP sufficient time to
2078        determine the congestion state of the network.
2079      </t>
2080      <t>
2081        Latency on subsequent requests is reduced since there is no time
2082        spent in TCP's connection opening handshake.
2083      </t>
2084      <t>
2085        HTTP can evolve more gracefully, since errors can be reported
2086        without the penalty of closing the TCP connection. Clients using
2087        future versions of HTTP might optimistically try a new feature,
2088        but if communicating with an older server, retry with old
2089        semantics after an error is reported.
2090      </t>
2091    </list>
2092</t>
2093<t>
2094   HTTP implementations &SHOULD; implement persistent connections.
2095</t>
2096</section>
2097
2098<section title="Overall Operation" anchor="persistent.overall">
2099<t>
2100   A significant difference between HTTP/1.1 and earlier versions of
2101   HTTP is that persistent connections are the default behavior of any
2102   HTTP connection. That is, unless otherwise indicated, the client
2103   &SHOULD; assume that the server will maintain a persistent connection,
2104   even after error responses from the server.
2105</t>
2106<t>
2107   Persistent connections provide a mechanism by which a client and a
2108   server can signal the close of a TCP connection. This signaling takes
2109   place using the Connection header field (<xref target="header.connection"/>). Once a close
2110   has been signaled, the client &MUST-NOT; send any more requests on that
2111   connection.
2112</t>
2113
2114<section title="Negotiation" anchor="persistent.negotiation">
2115<t>
2116   An HTTP/1.1 server &MAY; assume that a HTTP/1.1 client intends to
2117   maintain a persistent connection unless a Connection header including
2118   the connection-token "close" was sent in the request. If the server
2119   chooses to close the connection immediately after sending the
2120   response, it &SHOULD; send a Connection header including the
2121   connection-token close.
2122</t>
2123<t>
2124   An HTTP/1.1 client &MAY; expect a connection to remain open, but would
2125   decide to keep it open based on whether the response from a server
2126   contains a Connection header with the connection-token close. In case
2127   the client does not want to maintain a connection for more than that
2128   request, it &SHOULD; send a Connection header including the
2129   connection-token close.
2130</t>
2131<t>
2132   If either the client or the server sends the close token in the
2133   Connection header, that request becomes the last one for the
2134   connection.
2135</t>
2136<t>
2137   Clients and servers &SHOULD-NOT;  assume that a persistent connection is
2138   maintained for HTTP versions less than 1.1 unless it is explicitly
2139   signaled. See <xref target="compatibility.with.http.1.0.persistent.connections"/> for more information on backward
2140   compatibility with HTTP/1.0 clients.
2141</t>
2142<t>
2143   In order to remain persistent, all messages on the connection &MUST;
2144   have a self-defined message length (i.e., one not defined by closure
2145   of the connection), as described in <xref target="message.length"/>.
2146</t>
2147</section>
2148
2149<section title="Pipelining" anchor="pipelining">
2150<t>
2151   A client that supports persistent connections &MAY; "pipeline" its
2152   requests (i.e., send multiple requests without waiting for each
2153   response). A server &MUST; send its responses to those requests in the
2154   same order that the requests were received.
2155</t>
2156<t>
2157   Clients which assume persistent connections and pipeline immediately
2158   after connection establishment &SHOULD; be prepared to retry their
2159   connection if the first pipelined attempt fails. If a client does
2160   such a retry, it &MUST-NOT; pipeline before it knows the connection is
2161   persistent. Clients &MUST; also be prepared to resend their requests if
2162   the server closes the connection before sending all of the
2163   corresponding responses.
2164</t>
2165<t>
2166   Clients &SHOULD-NOT;  pipeline requests using non-idempotent methods or
2167   non-idempotent sequences of methods (see &idempotent-methods;). Otherwise, a
2168   premature termination of the transport connection could lead to
2169   indeterminate results. A client wishing to send a non-idempotent
2170   request &SHOULD; wait to send that request until it has received the
2171   response status for the previous request.
2172</t>
2173</section>
2174</section>
2175
2176<section title="Proxy Servers" anchor="persistent.proxy">
2177<t>
2178   It is especially important that proxies correctly implement the
2179   properties of the Connection header field as specified in <xref target="header.connection"/>.
2180</t>
2181<t>
2182   The proxy server &MUST; signal persistent connections separately with
2183   its clients and the origin servers (or other proxy servers) that it
2184   connects to. Each persistent connection applies to only one transport
2185   link.
2186</t>
2187<t>
2188   A proxy server &MUST-NOT; establish a HTTP/1.1 persistent connection
2189   with an HTTP/1.0 client (but see <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/>
2190   for information and discussion of the problems with the Keep-Alive header
2191   implemented by many HTTP/1.0 clients).
2192</t>
2193</section>
2194
2195<section title="Practical Considerations" anchor="persistent.practical">
2196<t>
2197   Servers will usually have some time-out value beyond which they will
2198   no longer maintain an inactive connection. Proxy servers might make
2199   this a higher value since it is likely that the client will be making
2200   more connections through the same server. The use of persistent
2201   connections places no requirements on the length (or existence) of
2202   this time-out for either the client or the server.
2203</t>
2204<t>
2205   When a client or server wishes to time-out it &SHOULD; issue a graceful
2206   close on the transport connection. Clients and servers &SHOULD; both
2207   constantly watch for the other side of the transport close, and
2208   respond to it as appropriate. If a client or server does not detect
2209   the other side's close promptly it could cause unnecessary resource
2210   drain on the network.
2211</t>
2212<t>
2213   A client, server, or proxy &MAY; close the transport connection at any
2214   time. For example, a client might have started to send a new request
2215   at the same time that the server has decided to close the "idle"
2216   connection. From the server's point of view, the connection is being
2217   closed while it was idle, but from the client's point of view, a
2218   request is in progress.
2219</t>
2220<t>
2221   This means that clients, servers, and proxies &MUST; be able to recover
2222   from asynchronous close events. Client software &SHOULD; reopen the
2223   transport connection and retransmit the aborted sequence of requests
2224   without user interaction so long as the request sequence is
2225   idempotent (see &idempotent-methods;). Non-idempotent methods or sequences
2226   &MUST-NOT; be automatically retried, although user agents &MAY; offer a
2227   human operator the choice of retrying the request(s). Confirmation by
2228   user-agent software with semantic understanding of the application
2229   &MAY; substitute for user confirmation. The automatic retry &SHOULD-NOT; 
2230   be repeated if the second sequence of requests fails.
2231</t>
2232<t>
2233   Servers &SHOULD; always respond to at least one request per connection,
2234   if at all possible. Servers &SHOULD-NOT;  close a connection in the
2235   middle of transmitting a response, unless a network or client failure
2236   is suspected.
2237</t>
2238<t>
2239   Clients that use persistent connections &SHOULD; limit the number of
2240   simultaneous connections that they maintain to a given server. A
2241   single-user client &SHOULD-NOT; maintain more than 2 connections with
2242   any server or proxy. A proxy &SHOULD; use up to 2*N connections to
2243   another server or proxy, where N is the number of simultaneously
2244   active users. These guidelines are intended to improve HTTP response
2245   times and avoid congestion.
2246</t>
2247</section>
2248</section>
2249
2250<section title="Message Transmission Requirements" anchor="message.transmission.requirements">
2251
2252<section title="Persistent Connections and Flow Control" anchor="persistent.flow">
2253<t>
2254   HTTP/1.1 servers &SHOULD; maintain persistent connections and use TCP's
2255   flow control mechanisms to resolve temporary overloads, rather than
2256   terminating connections with the expectation that clients will retry.
2257   The latter technique can exacerbate network congestion.
2258</t>
2259</section>
2260
2261<section title="Monitoring Connections for Error Status Messages" anchor="persistent.monitor">
2262<t>
2263   An HTTP/1.1 (or later) client sending a message-body &SHOULD; monitor
2264   the network connection for an error status while it is transmitting
2265   the request. If the client sees an error status, it &SHOULD;
2266   immediately cease transmitting the body. If the body is being sent
2267   using a "chunked" encoding (<xref target="transfer.codings"/>), a zero length chunk and
2268   empty trailer &MAY; be used to prematurely mark the end of the message.
2269   If the body was preceded by a Content-Length header, the client &MUST;
2270   close the connection.
2271</t>
2272</section>
2273
2274<section title="Use of the 100 (Continue) Status" anchor="use.of.the.100.status">
2275<t>
2276   The purpose of the 100 (Continue) status (see &status-100;) is to
2277   allow a client that is sending a request message with a request body
2278   to determine if the origin server is willing to accept the request
2279   (based on the request headers) before the client sends the request
2280   body. In some cases, it might either be inappropriate or highly
2281   inefficient for the client to send the body if the server will reject
2282   the message without looking at the body.
2283</t>
2284<t>
2285   Requirements for HTTP/1.1 clients:
2286  <list style="symbols">
2287    <t>
2288        If a client will wait for a 100 (Continue) response before
2289        sending the request body, it &MUST; send an Expect request-header
2290        field (&header-expect;) with the "100-continue" expectation.
2291    </t>
2292    <t>
2293        A client &MUST-NOT; send an Expect request-header field (&header-expect;)
2294        with the "100-continue" expectation if it does not intend
2295        to send a request body.
2296    </t>
2297  </list>
2298</t>
2299<t>
2300   Because of the presence of older implementations, the protocol allows
2301   ambiguous situations in which a client may send "Expect: 100-continue"
2302   without receiving either a 417 (Expectation Failed) status
2303   or a 100 (Continue) status. Therefore, when a client sends this
2304   header field to an origin server (possibly via a proxy) from which it
2305   has never seen a 100 (Continue) status, the client &SHOULD-NOT;  wait
2306   for an indefinite period before sending the request body.
2307</t>
2308<t>
2309   Requirements for HTTP/1.1 origin servers:
2310  <list style="symbols">
2311    <t> Upon receiving a request which includes an Expect request-header
2312        field with the "100-continue" expectation, an origin server &MUST;
2313        either respond with 100 (Continue) status and continue to read
2314        from the input stream, or respond with a final status code. The
2315        origin server &MUST-NOT; wait for the request body before sending
2316        the 100 (Continue) response. If it responds with a final status
2317        code, it &MAY; close the transport connection or it &MAY; continue
2318        to read and discard the rest of the request.  It &MUST-NOT;
2319        perform the requested method if it returns a final status code.
2320    </t>
2321    <t> An origin server &SHOULD-NOT;  send a 100 (Continue) response if
2322        the request message does not include an Expect request-header
2323        field with the "100-continue" expectation, and &MUST-NOT; send a
2324        100 (Continue) response if such a request comes from an HTTP/1.0
2325        (or earlier) client. There is an exception to this rule: for
2326        compatibility with <xref target="RFC2068"/>, a server &MAY; send a 100 (Continue)
2327        status in response to an HTTP/1.1 PUT or POST request that does
2328        not include an Expect request-header field with the "100-continue"
2329        expectation. This exception, the purpose of which is
2330        to minimize any client processing delays associated with an
2331        undeclared wait for 100 (Continue) status, applies only to
2332        HTTP/1.1 requests, and not to requests with any other HTTP-version
2333        value.
2334    </t>
2335    <t> An origin server &MAY; omit a 100 (Continue) response if it has
2336        already received some or all of the request body for the
2337        corresponding request.
2338    </t>
2339    <t> An origin server that sends a 100 (Continue) response &MUST;
2340    ultimately send a final status code, once the request body is
2341        received and processed, unless it terminates the transport
2342        connection prematurely.
2343    </t>
2344    <t> If an origin server receives a request that does not include an
2345        Expect request-header field with the "100-continue" expectation,
2346        the request includes a request body, and the server responds
2347        with a final status code before reading the entire request body
2348        from the transport connection, then the server &SHOULD-NOT;  close
2349        the transport connection until it has read the entire request,
2350        or until the client closes the connection. Otherwise, the client
2351        might not reliably receive the response message. However, this
2352        requirement is not be construed as preventing a server from
2353        defending itself against denial-of-service attacks, or from
2354        badly broken client implementations.
2355      </t>
2356    </list>
2357</t>
2358<t>
2359   Requirements for HTTP/1.1 proxies:
2360  <list style="symbols">
2361    <t> If a proxy receives a request that includes an Expect request-header
2362        field with the "100-continue" expectation, and the proxy
2363        either knows that the next-hop server complies with HTTP/1.1 or
2364        higher, or does not know the HTTP version of the next-hop
2365        server, it &MUST; forward the request, including the Expect header
2366        field.
2367    </t>
2368    <t> If the proxy knows that the version of the next-hop server is
2369        HTTP/1.0 or lower, it &MUST-NOT; forward the request, and it &MUST;
2370        respond with a 417 (Expectation Failed) status.
2371    </t>
2372    <t> Proxies &SHOULD; maintain a cache recording the HTTP version
2373        numbers received from recently-referenced next-hop servers.
2374    </t>
2375    <t> A proxy &MUST-NOT; forward a 100 (Continue) response if the
2376        request message was received from an HTTP/1.0 (or earlier)
2377        client and did not include an Expect request-header field with
2378        the "100-continue" expectation. This requirement overrides the
2379        general rule for forwarding of 1xx responses (see &status-1xx;).
2380    </t>
2381  </list>
2382</t>
2383</section>
2384
2385<section title="Client Behavior if Server Prematurely Closes Connection" anchor="connection.premature">
2386<t>
2387   If an HTTP/1.1 client sends a request which includes a request body,
2388   but which does not include an Expect request-header field with the
2389   "100-continue" expectation, and if the client is not directly
2390   connected to an HTTP/1.1 origin server, and if the client sees the
2391   connection close before receiving any status from the server, the
2392   client &SHOULD; retry the request.  If the client does retry this
2393   request, it &MAY; use the following "binary exponential backoff"
2394   algorithm to be assured of obtaining a reliable response:
2395  <list style="numbers">
2396    <t>
2397      Initiate a new connection to the server
2398    </t>
2399    <t>
2400      Transmit the request-headers
2401    </t>
2402    <t>
2403      Initialize a variable R to the estimated round-trip time to the
2404         server (e.g., based on the time it took to establish the
2405         connection), or to a constant value of 5 seconds if the round-trip
2406         time is not available.
2407    </t>
2408    <t>
2409       Compute T = R * (2**N), where N is the number of previous
2410         retries of this request.
2411    </t>
2412    <t>
2413       Wait either for an error response from the server, or for T
2414         seconds (whichever comes first)
2415    </t>
2416    <t>
2417       If no error response is received, after T seconds transmit the
2418         body of the request.
2419    </t>
2420    <t>
2421       If client sees that the connection is closed prematurely,
2422         repeat from step 1 until the request is accepted, an error
2423         response is received, or the user becomes impatient and
2424         terminates the retry process.
2425    </t>
2426  </list>
2427</t>
2428<t>
2429   If at any point an error status is received, the client
2430  <list style="symbols">
2431      <t>&SHOULD-NOT;  continue and</t>
2432
2433      <t>&SHOULD; close the connection if it has not completed sending the
2434        request message.</t>
2435    </list>
2436</t>
2437</section>
2438</section>
2439</section>
2440
2441
2442<section title="Miscellaneous notes that may disappear" anchor="misc">
2443<section title="Scheme aliases considered harmful" anchor="scheme.aliases">
2444<t>
2445   <cref>TBS: describe why aliases like webcal are harmful.</cref>
2446</t>
2447</section>
2448
2449<section title="Use of HTTP for proxy communication" anchor="http.proxy">
2450<t>
2451   <cref>TBD: Configured to use HTTP to proxy HTTP or other protocols.</cref>
2452</t>
2453</section>
2454
2455<section title="Interception of HTTP for access control" anchor="http.intercept">
2456<t>
2457   <cref>TBD: Interception of HTTP traffic for initiating access control.</cref>
2458</t>
2459</section>
2460
2461<section title="Use of HTTP by other protocols" anchor="http.others">
2462<t>
2463   <cref>TBD: Profiles of HTTP defined by other protocol.
2464   Extensions of HTTP like WebDAV.</cref>
2465</t>
2466
2467</section>
2468<section title="Use of HTTP by media type specification" anchor="http.media">
2469<t>
2470   <cref>TBD: Instructions on composing HTTP requests via hypertext formats.</cref>
2471</t>
2472</section>
2473</section>
2474
2475<section title="Header Field Definitions" anchor="header.field.definitions">
2476<t>
2477   This section defines the syntax and semantics of HTTP/1.1 header fields
2478   related to message framing and transport protocols.
2479</t>
2480<t>
2481   For entity-header fields, both sender and recipient refer to either the
2482   client or the server, depending on who sends and who receives the entity.
2483</t>
2484
2485<section title="Connection" anchor="header.connection">
2486  <iref primary="true" item="Connection header" x:for-anchor=""/>
2487  <iref primary="true" item="Headers" subitem="Connection" x:for-anchor=""/>
2488  <x:anchor-alias value="Connection"/>
2489  <x:anchor-alias value="connection-token"/>
2490  <x:anchor-alias value="Connection-v"/>
2491<t>
2492   The general-header field "Connection" allows the sender to specify
2493   options that are desired for that particular connection and &MUST-NOT;
2494   be communicated by proxies over further connections.
2495</t>
2496<t>
2497   The Connection header's value has the following grammar:
2498</t>
2499<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Connection"/><iref primary="true" item="Grammar" subitem="Connection-v"/><iref primary="true" item="Grammar" subitem="connection-token"/>
2500  <x:ref>Connection</x:ref>       = "Connection" ":" <x:ref>OWS</x:ref> <x:ref>Connection-v</x:ref>
2501  <x:ref>Connection-v</x:ref>     = 1#<x:ref>connection-token</x:ref>
2502  <x:ref>connection-token</x:ref> = <x:ref>token</x:ref>
2503</artwork></figure>
2504<t>
2505   HTTP/1.1 proxies &MUST; parse the Connection header field before a
2506   message is forwarded and, for each connection-token in this field,
2507   remove any header field(s) from the message with the same name as the
2508   connection-token. Connection options are signaled by the presence of
2509   a connection-token in the Connection header field, not by any
2510   corresponding additional header field(s), since the additional header
2511   field may not be sent if there are no parameters associated with that
2512   connection option.
2513</t>
2514<t>
2515   Message headers listed in the Connection header &MUST-NOT; include
2516   end-to-end headers, such as Cache-Control.
2517</t>
2518<t>
2519   HTTP/1.1 defines the "close" connection option for the sender to
2520   signal that the connection will be closed after completion of the
2521   response. For example,
2522</t>
2523<figure><artwork type="example">
2524  Connection: close
2525</artwork></figure>
2526<t>
2527   in either the request or the response header fields indicates that
2528   the connection &SHOULD-NOT;  be considered `persistent' (<xref target="persistent.connections"/>)
2529   after the current request/response is complete.
2530</t>
2531<t>
2532   An HTTP/1.1 client that does not support persistent connections &MUST;
2533   include the "close" connection option in every request message.
2534</t>
2535<t>
2536   An HTTP/1.1 server that does not support persistent connections &MUST;
2537   include the "close" connection option in every response message that
2538   does not have a 1xx (informational) status code.
2539</t>
2540<t>
2541   A system receiving an HTTP/1.0 (or lower-version) message that
2542   includes a Connection header &MUST;, for each connection-token in this
2543   field, remove and ignore any header field(s) from the message with
2544   the same name as the connection-token. This protects against mistaken
2545   forwarding of such header fields by pre-HTTP/1.1 proxies. See <xref target="compatibility.with.http.1.0.persistent.connections"/>.
2546</t>
2547</section>
2548
2549<section title="Content-Length" anchor="header.content-length">
2550  <iref primary="true" item="Content-Length header" x:for-anchor=""/>
2551  <iref primary="true" item="Headers" subitem="Content-Length" x:for-anchor=""/>
2552  <x:anchor-alias value="Content-Length"/>
2553  <x:anchor-alias value="Content-Length-v"/>
2554<t>
2555   The entity-header field "Content-Length" indicates the size of the
2556   entity-body, in number of OCTETs, sent to the recipient or,
2557   in the case of the HEAD method, the size of the entity-body that
2558   would have been sent had the request been a GET.
2559</t>
2560<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/><iref primary="true" item="Grammar" subitem="Content-Length-v"/>
2561  <x:ref>Content-Length</x:ref>   = "Content-Length" ":" <x:ref>OWS</x:ref> 1*<x:ref>Content-Length-v</x:ref>
2562  <x:ref>Content-Length-v</x:ref> = 1*<x:ref>DIGIT</x:ref>
2563</artwork></figure>
2564<t>
2565   An example is
2566</t>
2567<figure><artwork type="example">
2568  Content-Length: 3495
2569</artwork></figure>
2570<t>
2571   Applications &SHOULD; use this field to indicate the transfer-length of
2572   the message-body, unless this is prohibited by the rules in <xref target="message.length"/>.
2573</t>
2574<t>
2575   Any Content-Length greater than or equal to zero is a valid value.
2576   <xref target="message.length"/> describes how to determine the length of a message-body
2577   if a Content-Length is not given.
2578</t>
2579<t>
2580   Note that the meaning of this field is significantly different from
2581   the corresponding definition in MIME, where it is an optional field
2582   used within the "message/external-body" content-type. In HTTP, it
2583   &SHOULD; be sent whenever the message's length can be determined prior
2584   to being transferred, unless this is prohibited by the rules in
2585   <xref target="message.length"/>.
2586</t>
2587</section>
2588
2589<section title="Date" anchor="header.date">
2590  <iref primary="true" item="Date header" x:for-anchor=""/>
2591  <iref primary="true" item="Headers" subitem="Date" x:for-anchor=""/>
2592  <x:anchor-alias value="Date"/>
2593  <x:anchor-alias value="Date-v"/>
2594<t>
2595   The general-header field "Date" represents the date and time at which
2596   the message was originated, having the same semantics as orig-date in
2597   <xref target="RFC5322" x:fmt="of" x:sec="3.6.1"/>. The field value is an
2598   HTTP-date, as described in <xref target="date.time.formats.full.date"/>;
2599   it &MUST; be sent in rfc1123-date format.
2600</t>
2601<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Date"/><iref primary="true" item="Grammar" subitem="Date-v"/>
2602  <x:ref>Date</x:ref>   = "Date" ":" <x:ref>OWS</x:ref> <x:ref>Date-v</x:ref>
2603  <x:ref>Date-v</x:ref> = <x:ref>HTTP-date</x:ref>
2604</artwork></figure>
2605<t>
2606   An example is
2607</t>
2608<figure><artwork type="example">
2609  Date: Tue, 15 Nov 1994 08:12:31 GMT
2610</artwork></figure>
2611<t>
2612   Origin servers &MUST; include a Date header field in all responses,
2613   except in these cases:
2614  <list style="numbers">
2615      <t>If the response status code is 100 (Continue) or 101 (Switching
2616         Protocols), the response &MAY; include a Date header field, at
2617         the server's option.</t>
2618
2619      <t>If the response status code conveys a server error, e.g. 500
2620         (Internal Server Error) or 503 (Service Unavailable), and it is
2621         inconvenient or impossible to generate a valid Date.</t>
2622
2623      <t>If the server does not have a clock that can provide a
2624         reasonable approximation of the current time, its responses
2625         &MUST-NOT; include a Date header field. In this case, the rules
2626         in <xref target="clockless.origin.server.operation"/> &MUST; be followed.</t>
2627  </list>
2628</t>
2629<t>
2630   A received message that does not have a Date header field &MUST; be
2631   assigned one by the recipient if the message will be cached by that
2632   recipient or gatewayed via a protocol which requires a Date. An HTTP
2633   implementation without a clock &MUST-NOT; cache responses without
2634   revalidating them on every use. An HTTP cache, especially a shared
2635   cache, &SHOULD; use a mechanism, such as NTP <xref target="RFC1305"/>, to synchronize its
2636   clock with a reliable external standard.
2637</t>
2638<t>
2639   Clients &SHOULD; only send a Date header field in messages that include
2640   an entity-body, as in the case of the PUT and POST requests, and even
2641   then it is optional. A client without a clock &MUST-NOT; send a Date
2642   header field in a request.
2643</t>
2644<t>
2645   The HTTP-date sent in a Date header &SHOULD-NOT;  represent a date and
2646   time subsequent to the generation of the message. It &SHOULD; represent
2647   the best available approximation of the date and time of message
2648   generation, unless the implementation has no means of generating a
2649   reasonably accurate date and time. In theory, the date ought to
2650   represent the moment just before the entity is generated. In
2651   practice, the date can be generated at any time during the message
2652   origination without affecting its semantic value.
2653</t>
2654
2655<section title="Clockless Origin Server Operation" anchor="clockless.origin.server.operation">
2656<t>
2657   Some origin server implementations might not have a clock available.
2658   An origin server without a clock &MUST-NOT; assign Expires or Last-Modified
2659   values to a response, unless these values were associated
2660   with the resource by a system or user with a reliable clock. It &MAY;
2661   assign an Expires value that is known, at or before server
2662   configuration time, to be in the past (this allows "pre-expiration"
2663   of responses without storing separate Expires values for each
2664   resource).
2665</t>
2666</section>
2667</section>
2668
2669<section title="Host" anchor="header.host">
2670  <iref primary="true" item="Host header" x:for-anchor=""/>
2671  <iref primary="true" item="Headers" subitem="Host" x:for-anchor=""/>
2672  <x:anchor-alias value="Host"/>
2673  <x:anchor-alias value="Host-v"/>
2674<t>
2675   The request-header field "Host" specifies the Internet host and port
2676   number of the resource being requested, as obtained from the original
2677   URI given by the user or referring resource (generally an http URI,
2678   as described in <xref target="http.uri"/>). The Host field value &MUST; represent
2679   the naming authority of the origin server or gateway given by the
2680   original URL. This allows the origin server or gateway to
2681   differentiate between internally-ambiguous URLs, such as the root "/"
2682   URL of a server for multiple host names on a single IP address.
2683</t>
2684<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Host"/><iref primary="true" item="Grammar" subitem="Host-v"/>
2685  <x:ref>Host</x:ref>   = "Host" ":" <x:ref>OWS</x:ref> <x:ref>Host-v</x:ref>
2686  <x:ref>Host-v</x:ref> = <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ; <xref target="http.uri"/>
2687</artwork></figure>
2688<t>
2689   A "host" without any trailing port information implies the default
2690   port for the service requested (e.g., "80" for an HTTP URL). For
2691   example, a request on the origin server for
2692   &lt;http://www.example.org/pub/WWW/&gt; would properly include:
2693</t>
2694<figure><artwork type="example">
2695  GET /pub/WWW/ HTTP/1.1
2696  Host: www.example.org
2697</artwork></figure>
2698<t>
2699   A client &MUST; include a Host header field in all HTTP/1.1 request
2700   messages. If the requested URI does not include an Internet host
2701   name for the service being requested, then the Host header field &MUST;
2702   be given with an empty value. An HTTP/1.1 proxy &MUST; ensure that any
2703   request message it forwards does contain an appropriate Host header
2704   field that identifies the service being requested by the proxy. All
2705   Internet-based HTTP/1.1 servers &MUST; respond with a 400 (Bad Request)
2706   status code to any HTTP/1.1 request message which lacks a Host header
2707   field.
2708</t>
2709<t>
2710   See Sections <xref target="the.resource.identified.by.a.request" format="counter"/>
2711   and <xref target="changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses" format="counter"/>
2712   for other requirements relating to Host.
2713</t>
2714</section>
2715
2716<section title="TE" anchor="header.te">
2717  <iref primary="true" item="TE header" x:for-anchor=""/>
2718  <iref primary="true" item="Headers" subitem="TE" x:for-anchor=""/>
2719  <x:anchor-alias value="TE"/>
2720  <x:anchor-alias value="TE-v"/>
2721  <x:anchor-alias value="t-codings"/>
2722  <x:anchor-alias value="te-params"/>
2723  <x:anchor-alias value="te-ext"/>
2724<t>
2725   The request-header field "TE" indicates what extension transfer-codings
2726   it is willing to accept in the response and whether or not it is
2727   willing to accept trailer fields in a chunked transfer-coding. Its
2728   value may consist of the keyword "trailers" and/or a comma-separated
2729   list of extension transfer-coding names with optional accept
2730   parameters (as described in <xref target="transfer.codings"/>).
2731</t>
2732<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TE"/><iref primary="true" item="Grammar" subitem="TE-v"/><iref primary="true" item="Grammar" subitem="t-codings"/><iref primary="true" item="Grammar" subitem="te-params"/><iref primary="true" item="Grammar" subitem="te-ext"/>
2733  <x:ref>TE</x:ref>        = "TE" ":" <x:ref>OWS</x:ref> <x:ref>TE-v</x:ref>
2734  <x:ref>TE-v</x:ref>      = #<x:ref>t-codings</x:ref>
2735  <x:ref>t-codings</x:ref> = "trailers" / ( <x:ref>transfer-extension</x:ref> [ <x:ref>te-params</x:ref> ] )
2736  <x:ref>te-params</x:ref> = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> *( <x:ref>te-ext</x:ref> )
2737  <x:ref>te-ext</x:ref>    = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ]
2738</artwork></figure>
2739<t>
2740   The presence of the keyword "trailers" indicates that the client is
2741   willing to accept trailer fields in a chunked transfer-coding, as
2742   defined in <xref target="chunked.encoding"/>. This keyword is reserved for use with
2743   transfer-coding values even though it does not itself represent a
2744   transfer-coding.
2745</t>
2746<t>
2747   Examples of its use are:
2748</t>
2749<figure><artwork type="example">
2750  TE: deflate
2751  TE:
2752  TE: trailers, deflate;q=0.5
2753</artwork></figure>
2754<t>
2755   The TE header field only applies to the immediate connection.
2756   Therefore, the keyword &MUST; be supplied within a Connection header
2757   field (<xref target="header.connection"/>) whenever TE is present in an HTTP/1.1 message.
2758</t>
2759<t>
2760   A server tests whether a transfer-coding is acceptable, according to
2761   a TE field, using these rules:
2762  <list style="numbers">
2763    <x:lt>
2764      <t>The "chunked" transfer-coding is always acceptable. If the
2765         keyword "trailers" is listed, the client indicates that it is
2766         willing to accept trailer fields in the chunked response on
2767         behalf of itself and any downstream clients. The implication is
2768         that, if given, the client is stating that either all
2769         downstream clients are willing to accept trailer fields in the
2770         forwarded response, or that it will attempt to buffer the
2771         response on behalf of downstream recipients.
2772      </t><t>
2773         <x:h>Note:</x:h> HTTP/1.1 does not define any means to limit the size of a
2774         chunked response such that a client can be assured of buffering
2775         the entire response.</t>
2776    </x:lt>
2777    <x:lt>
2778      <t>If the transfer-coding being tested is one of the transfer-codings
2779         listed in the TE field, then it is acceptable unless it
2780         is accompanied by a qvalue of 0. (As defined in <xref target="quality.values"/>, a
2781         qvalue of 0 means "not acceptable.")</t>
2782    </x:lt>
2783    <x:lt>
2784      <t>If multiple transfer-codings are acceptable, then the
2785         acceptable transfer-coding with the highest non-zero qvalue is
2786         preferred.  The "chunked" transfer-coding always has a qvalue
2787         of 1.</t>
2788    </x:lt>
2789  </list>
2790</t>
2791<t>
2792   If the TE field-value is empty or if no TE field is present, the only
2793   transfer-coding is "chunked". A message with no transfer-coding is
2794   always acceptable.
2795</t>
2796</section>
2797
2798<section title="Trailer" anchor="header.trailer">
2799  <iref primary="true" item="Trailer header" x:for-anchor=""/>
2800  <iref primary="true" item="Headers" subitem="Trailer" x:for-anchor=""/>
2801  <x:anchor-alias value="Trailer"/>
2802  <x:anchor-alias value="Trailer-v"/>
2803<t>
2804   The general field "Trailer" indicates that the given set of
2805   header fields is present in the trailer of a message encoded with
2806   chunked transfer-coding.
2807</t>
2808<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Trailer"/><iref primary="true" item="Grammar" subitem="Trailer-v"/>
2809  <x:ref>Trailer</x:ref>   = "Trailer" ":" <x:ref>OWS</x:ref> <x:ref>Trailer-v</x:ref>
2810  <x:ref>Trailer-v</x:ref> = 1#<x:ref>field-name</x:ref>
2811</artwork></figure>
2812<t>
2813   An HTTP/1.1 message &SHOULD; include a Trailer header field in a
2814   message using chunked transfer-coding with a non-empty trailer. Doing
2815   so allows the recipient to know which header fields to expect in the
2816   trailer.
2817</t>
2818<t>
2819   If no Trailer header field is present, the trailer &SHOULD-NOT;  include
2820   any header fields. See <xref target="chunked.encoding"/> for restrictions on the use of
2821   trailer fields in a "chunked" transfer-coding.
2822</t>
2823<t>
2824   Message header fields listed in the Trailer header field &MUST-NOT;
2825   include the following header fields:
2826  <list style="symbols">
2827    <t>Transfer-Encoding</t>
2828    <t>Content-Length</t>
2829    <t>Trailer</t>
2830  </list>
2831</t>
2832</section>
2833
2834<section title="Transfer-Encoding" anchor="header.transfer-encoding">
2835  <iref primary="true" item="Transfer-Encoding header" x:for-anchor=""/>
2836  <iref primary="true" item="Headers" subitem="Transfer-Encoding" x:for-anchor=""/>
2837  <x:anchor-alias value="Transfer-Encoding"/>
2838  <x:anchor-alias value="Transfer-Encoding-v"/>
2839<t>
2840   The general-header "Transfer-Encoding" field indicates what (if any)
2841   type of transformation has been applied to the message body in order
2842   to safely transfer it between the sender and the recipient. This
2843   differs from the content-coding in that the transfer-coding is a
2844   property of the message, not of the entity.
2845</t>
2846<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Transfer-Encoding"/><iref primary="true" item="Grammar" subitem="Transfer-Encoding-v"/>
2847  <x:ref>Transfer-Encoding</x:ref>   = "Transfer-Encoding" ":" <x:ref>OWS</x:ref>
2848                        <x:ref>Transfer-Encoding-v</x:ref>
2849  <x:ref>Transfer-Encoding-v</x:ref> = 1#<x:ref>transfer-coding</x:ref>
2850</artwork></figure>
2851<t>
2852   Transfer-codings are defined in <xref target="transfer.codings"/>. An example is:
2853</t>
2854<figure><artwork type="example">
2855  Transfer-Encoding: chunked
2856</artwork></figure>
2857<t>
2858   If multiple encodings have been applied to an entity, the transfer-codings
2859   &MUST; be listed in the order in which they were applied.
2860   Additional information about the encoding parameters &MAY; be provided
2861   by other entity-header fields not defined by this specification.
2862</t>
2863<t>
2864   Many older HTTP/1.0 applications do not understand the Transfer-Encoding
2865   header.
2866</t>
2867</section>
2868
2869<section title="Upgrade" anchor="header.upgrade">
2870  <iref primary="true" item="Upgrade header" x:for-anchor=""/>
2871  <iref primary="true" item="Headers" subitem="Upgrade" x:for-anchor=""/>
2872  <x:anchor-alias value="Upgrade"/>
2873  <x:anchor-alias value="Upgrade-v"/>
2874<t>
2875   The general-header "Upgrade" allows the client to specify what
2876   additional communication protocols it supports and would like to use
2877   if the server finds it appropriate to switch protocols. The server
2878   &MUST; use the Upgrade header field within a 101 (Switching Protocols)
2879   response to indicate which protocol(s) are being switched.
2880</t>
2881<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Upgrade"/><iref primary="true" item="Grammar" subitem="Upgrade-v"/>
2882  <x:ref>Upgrade</x:ref>   = "Upgrade" ":" <x:ref>OWS</x:ref> <x:ref>Upgrade-v</x:ref>
2883  <x:ref>Upgrade-v</x:ref> = 1#<x:ref>product</x:ref>
2884</artwork></figure>
2885<t>
2886   For example,
2887</t>
2888<figure><artwork type="example">
2889  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
2890</artwork></figure>
2891<t>
2892   The Upgrade header field is intended to provide a simple mechanism
2893   for transition from HTTP/1.1 to some other, incompatible protocol. It
2894   does so by allowing the client to advertise its desire to use another
2895   protocol, such as a later version of HTTP with a higher major version
2896   number, even though the current request has been made using HTTP/1.1.
2897   This eases the difficult transition between incompatible protocols by
2898   allowing the client to initiate a request in the more commonly
2899   supported protocol while indicating to the server that it would like
2900   to use a "better" protocol if available (where "better" is determined
2901   by the server, possibly according to the nature of the method and/or
2902   resource being requested).
2903</t>
2904<t>
2905   The Upgrade header field only applies to switching application-layer
2906   protocols upon the existing transport-layer connection. Upgrade
2907   cannot be used to insist on a protocol change; its acceptance and use
2908   by the server is optional. The capabilities and nature of the
2909   application-layer communication after the protocol change is entirely
2910   dependent upon the new protocol chosen, although the first action
2911   after changing the protocol &MUST; be a response to the initial HTTP
2912   request containing the Upgrade header field.
2913</t>
2914<t>
2915   The Upgrade header field only applies to the immediate connection.
2916   Therefore, the upgrade keyword &MUST; be supplied within a Connection
2917   header field (<xref target="header.connection"/>) whenever Upgrade is present in an
2918   HTTP/1.1 message.
2919</t>
2920<t>
2921   The Upgrade header field cannot be used to indicate a switch to a
2922   protocol on a different connection. For that purpose, it is more
2923   appropriate to use a 301, 302, 303, or 305 redirection response.
2924</t>
2925<t>
2926   This specification only defines the protocol name "HTTP" for use by
2927   the family of Hypertext Transfer Protocols, as defined by the HTTP
2928   version rules of <xref target="http.version"/> and future updates to this
2929   specification. Any token can be used as a protocol name; however, it
2930   will only be useful if both the client and server associate the name
2931   with the same protocol.
2932</t>
2933</section>
2934
2935<section title="Via" anchor="header.via">
2936  <iref primary="true" item="Via header" x:for-anchor=""/>
2937  <iref primary="true" item="Headers" subitem="Via" x:for-anchor=""/>
2938  <x:anchor-alias value="protocol-name"/>
2939  <x:anchor-alias value="protocol-version"/>
2940  <x:anchor-alias value="pseudonym"/>
2941  <x:anchor-alias value="received-by"/>
2942  <x:anchor-alias value="received-protocol"/>
2943  <x:anchor-alias value="Via"/>
2944  <x:anchor-alias value="Via-v"/>
2945<t>
2946   The general-header field "Via" &MUST; be used by gateways and proxies to
2947   indicate the intermediate protocols and recipients between the user
2948   agent and the server on requests, and between the origin server and
2949   the client on responses. It is analogous to the "Received" field defined in
2950   <xref target="RFC5322" x:fmt="of" x:sec="3.6.7"/> and is intended to be used for tracking message forwards,
2951   avoiding request loops, and identifying the protocol capabilities of
2952   all senders along the request/response chain.
2953</t>
2954<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Via"/><iref primary="true" item="Grammar" subitem="Via-v"/><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"/>
2955  <x:ref>Via</x:ref>               = "Via" ":" <x:ref>OWS</x:ref> <x:ref>Via-v</x:ref>
2956  <x:ref>Via-v</x:ref>             = 1#( <x:ref>received-protocol</x:ref> <x:ref>RWS</x:ref> <x:ref>received-by</x:ref>
2957                          [ <x:ref>RWS</x:ref> <x:ref>comment</x:ref> ] )
2958  <x:ref>received-protocol</x:ref> = [ <x:ref>protocol-name</x:ref> "/" ] <x:ref>protocol-version</x:ref>
2959  <x:ref>protocol-name</x:ref>     = <x:ref>token</x:ref>
2960  <x:ref>protocol-version</x:ref>  = <x:ref>token</x:ref>
2961  <x:ref>received-by</x:ref>       = ( <x:ref>uri-host</x:ref> [ ":" <x:ref>port</x:ref> ] ) / <x:ref>pseudonym</x:ref>
2962  <x:ref>pseudonym</x:ref>         = <x:ref>token</x:ref>
2963</artwork></figure>
2964<t>
2965   The received-protocol indicates the protocol version of the message
2966   received by the server or client along each segment of the
2967   request/response chain. The received-protocol version is appended to
2968   the Via field value when the message is forwarded so that information
2969   about the protocol capabilities of upstream applications remains
2970   visible to all recipients.
2971</t>
2972<t>
2973   The protocol-name is optional if and only if it would be "HTTP". The
2974   received-by field is normally the host and optional port number of a
2975   recipient server or client that subsequently forwarded the message.
2976   However, if the real host is considered to be sensitive information,
2977   it &MAY; be replaced by a pseudonym. If the port is not given, it &MAY;
2978   be assumed to be the default port of the received-protocol.
2979</t>
2980<t>
2981   Multiple Via field values represents each proxy or gateway that has
2982   forwarded the message. Each recipient &MUST; append its information
2983   such that the end result is ordered according to the sequence of
2984   forwarding applications.
2985</t>
2986<t>
2987   Comments &MAY; be used in the Via header field to identify the software
2988   of the recipient proxy or gateway, analogous to the User-Agent and
2989   Server header fields. However, all comments in the Via field are
2990   optional and &MAY; be removed by any recipient prior to forwarding the
2991   message.
2992</t>
2993<t>
2994   For example, a request message could be sent from an HTTP/1.0 user
2995   agent to an internal proxy code-named "fred", which uses HTTP/1.1 to
2996   forward the request to a public proxy at p.example.net, which completes
2997   the request by forwarding it to the origin server at www.example.com.
2998   The request received by www.example.com would then have the following
2999   Via header field:
3000</t>
3001<figure><artwork type="example">
3002  Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
3003</artwork></figure>
3004<t>
3005   Proxies and gateways used as a portal through a network firewall
3006   &SHOULD-NOT;, by default, forward the names and ports of hosts within
3007   the firewall region. This information &SHOULD; only be propagated if
3008   explicitly enabled. If not enabled, the received-by host of any host
3009   behind the firewall &SHOULD; be replaced by an appropriate pseudonym
3010   for that host.
3011</t>
3012<t>
3013   For organizations that have strong privacy requirements for hiding
3014   internal structures, a proxy &MAY; combine an ordered subsequence of
3015   Via header field entries with identical received-protocol values into
3016   a single such entry. For example,
3017</t>
3018<figure><artwork type="example">
3019  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
3020</artwork></figure>
3021<t>
3022        could be collapsed to
3023</t>
3024<figure><artwork type="example">
3025  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
3026</artwork></figure>
3027<t>
3028   Applications &SHOULD-NOT;  combine multiple entries unless they are all
3029   under the same organizational control and the hosts have already been
3030   replaced by pseudonyms. Applications &MUST-NOT; combine entries which
3031   have different received-protocol values.
3032</t>
3033</section>
3034
3035</section>
3036
3037<section title="IANA Considerations" anchor="IANA.considerations">
3038<section title="Message Header Registration" anchor="message.header.registration">
3039<t>
3040   The Message Header Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> should be updated
3041   with the permanent registrations below (see <xref target="RFC3864"/>):
3042</t>
3043<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
3044<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
3045   <ttcol>Header Field Name</ttcol>
3046   <ttcol>Protocol</ttcol>
3047   <ttcol>Status</ttcol>
3048   <ttcol>Reference</ttcol>
3049
3050   <c>Connection</c>
3051   <c>http</c>
3052   <c>standard</c>
3053   <c>
3054      <xref target="header.connection"/>
3055   </c>
3056   <c>Content-Length</c>
3057   <c>http</c>
3058   <c>standard</c>
3059   <c>
3060      <xref target="header.content-length"/>
3061   </c>
3062   <c>Date</c>
3063   <c>http</c>
3064   <c>standard</c>
3065   <c>
3066      <xref target="header.date"/>
3067   </c>
3068   <c>Host</c>
3069   <c>http</c>
3070   <c>standard</c>
3071   <c>
3072      <xref target="header.host"/>
3073   </c>
3074   <c>TE</c>
3075   <c>http</c>
3076   <c>standard</c>
3077   <c>
3078      <xref target="header.te"/>
3079   </c>
3080   <c>Trailer</c>
3081   <c>http</c>
3082   <c>standard</c>
3083   <c>
3084      <xref target="header.trailer"/>
3085   </c>
3086   <c>Transfer-Encoding</c>
3087   <c>http</c>
3088   <c>standard</c>
3089   <c>
3090      <xref target="header.transfer-encoding"/>
3091   </c>
3092   <c>Upgrade</c>
3093   <c>http</c>
3094   <c>standard</c>
3095   <c>
3096      <xref target="header.upgrade"/>
3097   </c>
3098   <c>Via</c>
3099   <c>http</c>
3100   <c>standard</c>
3101   <c>
3102      <xref target="header.via"/>
3103   </c>
3104</texttable>
3105<!--(END)-->
3106<t>
3107   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
3108</t>
3109</section>
3110
3111<section title="URI Scheme Registration" anchor="uri.scheme.registration">
3112<t>
3113   The entries for the "http" and "https" URI Schemes in the registry located at
3114   <eref target="http://www.iana.org/assignments/uri-schemes.html"/>
3115   should be updated to point to Sections <xref target="http.uri" format="counter"/>
3116   and <xref target="https.uri" format="counter"/> of this document
3117   (see <xref target="RFC4395"/>).
3118</t>
3119</section>
3120
3121<section title="Internet Media Type Registrations" anchor="internet.media.type.http">
3122<t>
3123   This document serves as the specification for the Internet media types
3124   "message/http" and "application/http". The following is to be registered with
3125   IANA (see <xref target="RFC4288"/>).
3126</t>
3127<section title="Internet Media Type message/http" anchor="internet.media.type.message.http">
3128<iref item="Media Type" subitem="message/http" primary="true"/>
3129<iref item="message/http Media Type" primary="true"/>
3130<t>
3131   The message/http type can be used to enclose a single HTTP request or
3132   response message, provided that it obeys the MIME restrictions for all
3133   "message" types regarding line length and encodings.
3134</t>
3135<t>
3136  <list style="hanging" x:indent="12em">
3137    <t hangText="Type name:">
3138      message
3139    </t>
3140    <t hangText="Subtype name:">
3141      http
3142    </t>
3143    <t hangText="Required parameters:">
3144      none
3145    </t>
3146    <t hangText="Optional parameters:">
3147      version, msgtype
3148      <list style="hanging">
3149        <t hangText="version:">
3150          The HTTP-Version number of the enclosed message
3151          (e.g., "1.1"). If not present, the version can be
3152          determined from the first line of the body.
3153        </t>
3154        <t hangText="msgtype:">
3155          The message type -- "request" or "response". If not
3156          present, the type can be determined from the first
3157          line of the body.
3158        </t>
3159      </list>
3160    </t>
3161    <t hangText="Encoding considerations:">
3162      only "7bit", "8bit", or "binary" are permitted
3163    </t>
3164    <t hangText="Security considerations:">
3165      none
3166    </t>
3167    <t hangText="Interoperability considerations:">
3168      none
3169    </t>
3170    <t hangText="Published specification:">
3171      This specification (see <xref target="internet.media.type.message.http"/>).
3172    </t>
3173    <t hangText="Applications that use this media type:">
3174    </t>
3175    <t hangText="Additional information:">
3176      <list style="hanging">
3177        <t hangText="Magic number(s):">none</t>
3178        <t hangText="File extension(s):">none</t>
3179        <t hangText="Macintosh file type code(s):">none</t>
3180      </list>
3181    </t>
3182    <t hangText="Person and email address to contact for further information:">
3183      See Authors Section.
3184    </t>
3185    <t hangText="Intended usage:">
3186      COMMON
3187    </t>
3188    <t hangText="Restrictions on usage:">
3189      none
3190    </t>
3191    <t hangText="Author/Change controller:">
3192      IESG
3193    </t>
3194  </list>
3195</t>
3196</section>
3197<section title="Internet Media Type application/http" anchor="internet.media.type.application.http">
3198<iref item="Media Type" subitem="application/http" primary="true"/>
3199<iref item="application/http Media Type" primary="true"/>
3200<t>
3201   The application/http type can be used to enclose a pipeline of one or more
3202   HTTP request or response messages (not intermixed).
3203</t>
3204<t>
3205  <list style="hanging" x:indent="12em">
3206    <t hangText="Type name:">
3207      application
3208    </t>
3209    <t hangText="Subtype name:">
3210      http
3211    </t>
3212    <t hangText="Required parameters:">
3213      none
3214    </t>
3215    <t hangText="Optional parameters:">
3216      version, msgtype
3217      <list style="hanging">
3218        <t hangText="version:">
3219          The HTTP-Version number of the enclosed messages
3220          (e.g., "1.1"). If not present, the version can be
3221          determined from the first line of the body.
3222        </t>
3223        <t hangText="msgtype:">
3224          The message type -- "request" or "response". If not
3225          present, the type can be determined from the first
3226          line of the body.
3227        </t>
3228      </list>
3229    </t>
3230    <t hangText="Encoding considerations:">
3231      HTTP messages enclosed by this type
3232      are in "binary" format; use of an appropriate
3233      Content-Transfer-Encoding is required when
3234      transmitted via E-mail.
3235    </t>
3236    <t hangText="Security considerations:">
3237      none
3238    </t>
3239    <t hangText="Interoperability considerations:">
3240      none
3241    </t>
3242    <t hangText="Published specification:">
3243      This specification (see <xref target="internet.media.type.application.http"/>).
3244    </t>
3245    <t hangText="Applications that use this media type:">
3246    </t>
3247    <t hangText="Additional information:">
3248      <list style="hanging">
3249        <t hangText="Magic number(s):">none</t>
3250        <t hangText="File extension(s):">none</t>
3251        <t hangText="Macintosh file type code(s):">none</t>
3252      </list>
3253    </t>
3254    <t hangText="Person and email address to contact for further information:">
3255      See Authors Section.
3256    </t>
3257    <t hangText="Intended usage:">
3258      COMMON
3259    </t>
3260    <t hangText="Restrictions on usage:">
3261      none
3262    </t>
3263    <t hangText="Author/Change controller:">
3264      IESG
3265    </t>
3266  </list>
3267</t>
3268</section>
3269</section>
3270
3271<section title="Transfer Coding Registry" anchor="transfer.coding.registration">
3272<t>
3273   The registration procedure for HTTP Transfer Codings is now defined by
3274   <xref target="transfer.coding.registry"/> of this document.
3275</t>
3276<t>
3277   The HTTP Transfer Codings Registry located at <eref target="http://www.iana.org/assignments/http-parameters"/>
3278   should be updated with the registrations below:
3279</t>
3280<texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table">
3281   <ttcol>Name</ttcol>
3282   <ttcol>Description</ttcol>
3283   <ttcol>Reference</ttcol>
3284   <c>chunked</c>
3285   <c>Transfer in a series of chunks</c>
3286   <c>
3287      <xref target="chunked.encoding"/>
3288   </c>
3289   <c>compress</c>
3290   <c>UNIX "compress" program method</c>
3291   <c>
3292      <xref target="compress.coding"/>
3293   </c>
3294   <c>deflate</c>
3295   <c>"zlib" format <xref target="RFC1950"/> with "deflate" compression</c>
3296   <c>
3297      <xref target="deflate.coding"/>
3298   </c>
3299   <c>gzip</c>
3300   <c>Same as GNU zip <xref target="RFC1952"/></c>
3301   <c>
3302      <xref target="gzip.coding"/>
3303   </c>
3304</texttable>
3305</section>
3306
3307</section>
3308
3309<section title="Security Considerations" anchor="security.considerations">
3310<t>
3311   This section is meant to inform application developers, information
3312   providers, and users of the security limitations in HTTP/1.1 as
3313   described by this document. The discussion does not include
3314   definitive solutions to the problems revealed, though it does make
3315   some suggestions for reducing security risks.
3316</t>
3317
3318<section title="Personal Information" anchor="personal.information">
3319<t>
3320   HTTP clients are often privy to large amounts of personal information
3321   (e.g. the user's name, location, mail address, passwords, encryption
3322   keys, etc.), and &SHOULD; be very careful to prevent unintentional
3323   leakage of this information.
3324   We very strongly recommend that a convenient interface be provided
3325   for the user to control dissemination of such information, and that
3326   designers and implementors be particularly careful in this area.
3327   History shows that errors in this area often create serious security
3328   and/or privacy problems and generate highly adverse publicity for the
3329   implementor's company.
3330</t>
3331</section>
3332
3333<section title="Abuse of Server Log Information" anchor="abuse.of.server.log.information">
3334<t>
3335   A server is in the position to save personal data about a user's
3336   requests which might identify their reading patterns or subjects of
3337   interest. This information is clearly confidential in nature and its
3338   handling can be constrained by law in certain countries. People using
3339   HTTP to provide data are responsible for ensuring that
3340   such material is not distributed without the permission of any
3341   individuals that are identifiable by the published results.
3342</t>
3343</section>
3344
3345<section title="Attacks Based On File and Path Names" anchor="attack.pathname">
3346<t>
3347   Implementations of HTTP origin servers &SHOULD; be careful to restrict
3348   the documents returned by HTTP requests to be only those that were
3349   intended by the server administrators. If an HTTP server translates
3350   HTTP URIs directly into file system calls, the server &MUST; take
3351   special care not to serve files that were not intended to be
3352   delivered to HTTP clients. For example, UNIX, Microsoft Windows, and
3353   other operating systems use ".." as a path component to indicate a
3354   directory level above the current one. On such a system, an HTTP
3355   server &MUST; disallow any such construct in the request-target if it
3356   would otherwise allow access to a resource outside those intended to
3357   be accessible via the HTTP server. Similarly, files intended for
3358   reference only internally to the server (such as access control
3359   files, configuration files, and script code) &MUST; be protected from
3360   inappropriate retrieval, since they might contain sensitive
3361   information. Experience has shown that minor bugs in such HTTP server
3362   implementations have turned into security risks.
3363</t>
3364</section>
3365
3366<section title="DNS Spoofing" anchor="dns.spoofing">
3367<t>
3368   Clients using HTTP rely heavily on the Domain Name Service, and are
3369   thus generally prone to security attacks based on the deliberate
3370   mis-association of IP addresses and DNS names. Clients need to be
3371   cautious in assuming the continuing validity of an IP number/DNS name
3372   association.
3373</t>
3374<t>
3375   In particular, HTTP clients &SHOULD; rely on their name resolver for
3376   confirmation of an IP number/DNS name association, rather than
3377   caching the result of previous host name lookups. Many platforms
3378   already can cache host name lookups locally when appropriate, and
3379   they &SHOULD; be configured to do so. It is proper for these lookups to
3380   be cached, however, only when the TTL (Time To Live) information
3381   reported by the name server makes it likely that the cached
3382   information will remain useful.
3383</t>
3384<t>
3385   If HTTP clients cache the results of host name lookups in order to
3386   achieve a performance improvement, they &MUST; observe the TTL
3387   information reported by DNS.
3388</t>
3389<t>
3390   If HTTP clients do not observe this rule, they could be spoofed when
3391   a previously-accessed server's IP address changes. As network
3392   renumbering is expected to become increasingly common <xref target="RFC1900"/>, the
3393   possibility of this form of attack will grow. Observing this
3394   requirement thus reduces this potential security vulnerability.
3395</t>
3396<t>
3397   This requirement also improves the load-balancing behavior of clients
3398   for replicated servers using the same DNS name and reduces the
3399   likelihood of a user's experiencing failure in accessing sites which
3400   use that strategy.
3401</t>
3402</section>
3403
3404<section title="Proxies and Caching" anchor="attack.proxies">
3405<t>
3406   By their very nature, HTTP proxies are men-in-the-middle, and
3407   represent an opportunity for man-in-the-middle attacks. Compromise of
3408   the systems on which the proxies run can result in serious security
3409   and privacy problems. Proxies have access to security-related
3410   information, personal information about individual users and
3411   organizations, and proprietary information belonging to users and
3412   content providers. A compromised proxy, or a proxy implemented or
3413   configured without regard to security and privacy considerations,
3414   might be used in the commission of a wide range of potential attacks.
3415</t>
3416<t>
3417   Proxy operators should protect the systems on which proxies run as
3418   they would protect any system that contains or transports sensitive
3419   information. In particular, log information gathered at proxies often
3420   contains highly sensitive personal information, and/or information
3421   about organizations. Log information should be carefully guarded, and
3422   appropriate guidelines for use developed and followed. (<xref target="abuse.of.server.log.information"/>).
3423</t>
3424<t>
3425   Proxy implementors should consider the privacy and security
3426   implications of their design and coding decisions, and of the
3427   configuration options they provide to proxy operators (especially the
3428   default configuration).
3429</t>
3430<t>
3431   Users of a proxy need to be aware that they are no trustworthier than
3432   the people who run the proxy; HTTP itself cannot solve this problem.
3433</t>
3434<t>
3435   The judicious use of cryptography, when appropriate, may suffice to
3436   protect against a broad range of security and privacy attacks. Such
3437   cryptography is beyond the scope of the HTTP/1.1 specification.
3438</t>
3439</section>
3440
3441<section title="Denial of Service Attacks on Proxies" anchor="attack.DoS">
3442<t>
3443   They exist. They are hard to defend against. Research continues.
3444   Beware.
3445</t>
3446</section>
3447</section>
3448
3449<section title="Acknowledgments" anchor="ack">
3450<t>
3451   HTTP has evolved considerably over the years. It has
3452   benefited from a large and active developer community--the many
3453   people who have participated on the www-talk mailing list--and it is
3454   that community which has been most responsible for the success of
3455   HTTP and of the World-Wide Web in general. Marc Andreessen, Robert
3456   Cailliau, Daniel W. Connolly, Bob Denny, John Franks, Jean-Francois
3457   Groff, Phillip M. Hallam-Baker, Hakon W. Lie, Ari Luotonen, Rob
3458   McCool, Lou Montulli, Dave Raggett, Tony Sanders, and Marc
3459   VanHeyningen deserve special recognition for their efforts in
3460   defining early aspects of the protocol.
3461</t>
3462<t>
3463   This document has benefited greatly from the comments of all those
3464   participating in the HTTP-WG. In addition to those already mentioned,
3465   the following individuals have contributed to this specification:
3466</t>
3467<t>
3468   Gary Adams, Harald Tveit Alvestrand, Keith Ball, Brian Behlendorf,
3469   Paul Burchard, Maurizio Codogno, Mike Cowlishaw, Roman Czyborra,
3470   Michael A. Dolan, Daniel DuBois, David J. Fiander, Alan Freier, Marc Hedlund, Greg Herlihy,
3471   Koen Holtman, Alex Hopmann, Bob Jernigan, Shel Kaphan, Rohit Khare,
3472   John Klensin, Martijn Koster, Alexei Kosut, David M. Kristol,
3473   Daniel LaLiberte, Ben Laurie, Paul J. Leach, Albert Lunde,
3474   John C. Mallery, Jean-Philippe Martin-Flatin, Mitra, David Morris,
3475   Gavin Nicol, Ross Patterson, Bill Perry, Jeffrey Perry, Scott Powers, Owen Rees,
3476   Luigi Rizzo, David Robinson, Marc Salomon, Rich Salz,
3477   Allan M. Schiffman, Jim Seidman, Chuck Shotton, Eric W. Sink,
3478   Simon E. Spero, Richard N. Taylor, Robert S. Thau,
3479   Bill (BearHeart) Weinman, Francois Yergeau, Mary Ellen Zurko,
3480   Josh Cohen.
3481</t>
3482<t>
3483   Thanks to the "cave men" of Palo Alto. You know who you are.
3484</t>
3485<t>
3486   Jim Gettys (the editor of <xref target="RFC2616"/>) wishes particularly
3487   to thank Roy Fielding, the editor of <xref target="RFC2068"/>, along
3488   with John Klensin, Jeff Mogul, Paul Leach, Dave Kristol, Koen
3489   Holtman, John Franks, Josh Cohen, Alex Hopmann, Scott Lawrence, and
3490   Larry Masinter for their help. And thanks go particularly to Jeff
3491   Mogul and Scott Lawrence for performing the "MUST/MAY/SHOULD" audit.
3492</t>
3493<t>
3494   The Apache Group, Anselm Baird-Smith, author of Jigsaw, and Henrik
3495   Frystyk implemented RFC 2068 early, and we wish to thank them for the
3496   discovery of many of the problems that this document attempts to
3497   rectify.
3498</t>
3499<t>
3500   This specification makes heavy use of the augmented BNF and generic
3501   constructs defined by David H. Crocker for <xref target="RFC5234"/>. Similarly, it
3502   reuses many of the definitions provided by Nathaniel Borenstein and
3503   Ned Freed for MIME <xref target="RFC2045"/>. We hope that their inclusion in this
3504   specification will help reduce past confusion over the relationship
3505   between HTTP and Internet mail message formats.
3506</t>
3507</section>
3508
3509</middle>
3510<back>
3511
3512<references title="Normative References">
3513
3514<reference anchor="ISO-8859-1">
3515  <front>
3516    <title>
3517     Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
3518    </title>
3519    <author>
3520      <organization>International Organization for Standardization</organization>
3521    </author>
3522    <date year="1998"/>
3523  </front>
3524  <seriesInfo name="ISO/IEC" value="8859-1:1998"/>
3525</reference>
3526
3527<reference anchor="Part2">
3528  <front>
3529    <title abbrev="HTTP/1.1">HTTP/1.1, part 2: Message Semantics</title>
3530    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3531      <organization abbrev="Day Software">Day Software</organization>
3532      <address><email>fielding@gbiv.com</email></address>
3533    </author>
3534    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3535      <organization>One Laptop per Child</organization>
3536      <address><email>jg@laptop.org</email></address>
3537    </author>
3538    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3539      <organization abbrev="HP">Hewlett-Packard Company</organization>
3540      <address><email>JeffMogul@acm.org</email></address>
3541    </author>
3542    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3543      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3544      <address><email>henrikn@microsoft.com</email></address>
3545    </author>
3546    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3547      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
3548      <address><email>LMM@acm.org</email></address>
3549    </author>
3550    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3551      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3552      <address><email>paulle@microsoft.com</email></address>
3553    </author>
3554    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3555      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3556      <address><email>timbl@w3.org</email></address>
3557    </author>
3558    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3559      <organization abbrev="W3C">World Wide Web Consortium</organization>
3560      <address><email>ylafon@w3.org</email></address>
3561    </author>
3562    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3563      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3564      <address><email>julian.reschke@greenbytes.de</email></address>
3565    </author>
3566    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
3567  </front>
3568  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
3569  <x:source href="p2-semantics.xml" basename="p2-semantics"/>
3570</reference>
3571
3572<reference anchor="Part3">
3573  <front>
3574    <title abbrev="HTTP/1.1">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
3575    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3576      <organization abbrev="Day Software">Day Software</organization>
3577      <address><email>fielding@gbiv.com</email></address>
3578    </author>
3579    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3580      <organization>One Laptop per Child</organization>
3581      <address><email>jg@laptop.org</email></address>
3582    </author>
3583    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3584      <organization abbrev="HP">Hewlett-Packard Company</organization>
3585      <address><email>JeffMogul@acm.org</email></address>
3586    </author>
3587    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3588      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3589      <address><email>henrikn@microsoft.com</email></address>
3590    </author>
3591    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3592      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
3593      <address><email>LMM@acm.org</email></address>
3594    </author>
3595    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3596      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3597      <address><email>paulle@microsoft.com</email></address>
3598    </author>
3599    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3600      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3601      <address><email>timbl@w3.org</email></address>
3602    </author>
3603    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3604      <organization abbrev="W3C">World Wide Web Consortium</organization>
3605      <address><email>ylafon@w3.org</email></address>
3606    </author>
3607    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3608      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3609      <address><email>julian.reschke@greenbytes.de</email></address>
3610    </author>
3611    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
3612  </front>
3613  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p3-payload-&ID-VERSION;"/>
3614  <x:source href="p3-payload.xml" basename="p3-payload"/>
3615</reference>
3616
3617<reference anchor="Part5">
3618  <front>
3619    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
3620    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3621      <organization abbrev="Day Software">Day Software</organization>
3622      <address><email>fielding@gbiv.com</email></address>
3623    </author>
3624    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3625      <organization>One Laptop per Child</organization>
3626      <address><email>jg@laptop.org</email></address>
3627    </author>
3628    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3629      <organization abbrev="HP">Hewlett-Packard Company</organization>
3630      <address><email>JeffMogul@acm.org</email></address>
3631    </author>
3632    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3633      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3634      <address><email>henrikn@microsoft.com</email></address>
3635    </author>
3636    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3637      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
3638      <address><email>LMM@acm.org</email></address>
3639    </author>
3640    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3641      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3642      <address><email>paulle@microsoft.com</email></address>
3643    </author>
3644    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3645      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3646      <address><email>timbl@w3.org</email></address>
3647    </author>
3648    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3649      <organization abbrev="W3C">World Wide Web Consortium</organization>
3650      <address><email>ylafon@w3.org</email></address>
3651    </author>
3652    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3653      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3654      <address><email>julian.reschke@greenbytes.de</email></address>
3655    </author>
3656    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
3657  </front>
3658  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
3659  <x:source href="p5-range.xml" basename="p5-range"/>
3660</reference>
3661
3662<reference anchor="Part6">
3663  <front>
3664    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
3665    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
3666      <organization abbrev="Day Software">Day Software</organization>
3667      <address><email>fielding@gbiv.com</email></address>
3668    </author>
3669    <author initials="J." surname="Gettys" fullname="Jim Gettys">
3670      <organization>One Laptop per Child</organization>
3671      <address><email>jg@laptop.org</email></address>
3672    </author>
3673    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
3674      <organization abbrev="HP">Hewlett-Packard Company</organization>
3675      <address><email>JeffMogul@acm.org</email></address>
3676    </author>
3677    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
3678      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3679      <address><email>henrikn@microsoft.com</email></address>
3680    </author>
3681    <author initials="L." surname="Masinter" fullname="Larry Masinter">
3682      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
3683      <address><email>LMM@acm.org</email></address>
3684    </author>
3685    <author initials="P." surname="Leach" fullname="Paul J. Leach">
3686      <organization abbrev="Microsoft">Microsoft Corporation</organization>
3687      <address><email>paulle@microsoft.com</email></address>
3688    </author>
3689    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3690      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3691      <address><email>timbl@w3.org</email></address>
3692    </author>
3693    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
3694      <organization abbrev="W3C">World Wide Web Consortium</organization>
3695      <address><email>ylafon@w3.org</email></address>
3696    </author>
3697    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
3698      <organization />
3699      <address><email>mnot@mnot.net</email></address>
3700    </author>
3701    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
3702      <organization abbrev="greenbytes">greenbytes GmbH</organization>
3703      <address><email>julian.reschke@greenbytes.de</email></address>
3704    </author>
3705    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
3706  </front>
3707  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
3708  <x:source href="p6-cache.xml" basename="p6-cache"/>
3709</reference>
3710
3711<reference anchor="RFC5234">
3712  <front>
3713    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
3714    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
3715      <organization>Brandenburg InternetWorking</organization>
3716      <address>
3717      <postal>
3718      <street>675 Spruce Dr.</street>
3719      <city>Sunnyvale</city>
3720      <region>CA</region>
3721      <code>94086</code>
3722      <country>US</country></postal>
3723      <phone>+1.408.246.8253</phone>
3724      <email>dcrocker@bbiw.net</email></address> 
3725    </author>
3726    <author initials="P." surname="Overell" fullname="Paul Overell">
3727      <organization>THUS plc.</organization>
3728      <address>
3729      <postal>
3730      <street>1/2 Berkeley Square</street>
3731      <street>99 Berkely Street</street>
3732      <city>Glasgow</city>
3733      <code>G3 7HR</code>
3734      <country>UK</country></postal>
3735      <email>paul.overell@thus.net</email></address>
3736    </author>
3737    <date month="January" year="2008"/>
3738  </front>
3739  <seriesInfo name="STD" value="68"/>
3740  <seriesInfo name="RFC" value="5234"/>
3741</reference>
3742
3743<reference anchor="RFC2119">
3744  <front>
3745    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
3746    <author initials="S." surname="Bradner" fullname="Scott Bradner">
3747      <organization>Harvard University</organization>
3748      <address><email>sob@harvard.edu</email></address>
3749    </author>
3750    <date month="March" year="1997"/>
3751  </front>
3752  <seriesInfo name="BCP" value="14"/>
3753  <seriesInfo name="RFC" value="2119"/>
3754</reference>
3755
3756<reference anchor="RFC3986">
3757 <front>
3758  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
3759  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
3760    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
3761    <address>
3762       <email>timbl@w3.org</email>
3763       <uri>http://www.w3.org/People/Berners-Lee/</uri>
3764    </address>
3765  </author>
3766  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
3767    <organization abbrev="Day Software">Day Software</organization>
3768    <address>
3769      <email>fielding@gbiv.com</email>
3770      <uri>http://roy.gbiv.com/</uri>
3771    </address>
3772  </author>
3773  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
3774    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
3775    <address>
3776      <email>LMM@acm.org</email>
3777      <uri>http://larry.masinter.net/</uri>
3778    </address>
3779  </author>
3780  <date month='January' year='2005'></date>
3781 </front>
3782 <seriesInfo name="RFC" value="3986"/>
3783 <seriesInfo name="STD" value="66"/>
3784</reference>
3785
3786<reference anchor="USASCII">
3787  <front>
3788    <title>Coded Character Set -- 7-bit American Standard Code for Information Interchange</title>
3789    <author>
3790      <organization>American National Standards Institute</organization>
3791    </author>
3792    <date year="1986"/>
3793  </front>
3794  <seriesInfo name="ANSI" value="X3.4"/>
3795</reference>
3796
3797<reference anchor="RFC1950">
3798  <front>
3799    <title>ZLIB Compressed Data Format Specification version 3.3</title>
3800    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
3801      <organization>Aladdin Enterprises</organization>
3802      <address><email>ghost@aladdin.com</email></address>
3803    </author>
3804    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
3805      <organization/>
3806    </author>
3807    <date month="May" year="1996"/>
3808  </front>
3809  <seriesInfo name="RFC" value="1950"/>
3810  <annotation>
3811    RFC 1950 is an Informational RFC, thus it may be less stable than
3812    this specification. On the other hand, this downward reference was
3813    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
3814    therefore it is unlikely to cause problems in practice. See also
3815    <xref target="BCP97"/>.
3816  </annotation>
3817</reference>
3818
3819<reference anchor="RFC1951">
3820  <front>
3821    <title>DEFLATE Compressed Data Format Specification version 1.3</title>
3822    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
3823      <organization>Aladdin Enterprises</organization>
3824      <address><email>ghost@aladdin.com</email></address>
3825    </author>
3826    <date month="May" year="1996"/>
3827  </front>
3828  <seriesInfo name="RFC" value="1951"/>
3829  <annotation>
3830    RFC 1951 is an Informational RFC, thus it may be less stable than
3831    this specification. On the other hand, this downward reference was
3832    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
3833    therefore it is unlikely to cause problems in practice. See also
3834    <xref target="BCP97"/>.
3835  </annotation>
3836</reference>
3837
3838<reference anchor="RFC1952">
3839  <front>
3840    <title>GZIP file format specification version 4.3</title>
3841    <author initials="P." surname="Deutsch" fullname="L. Peter Deutsch">
3842      <organization>Aladdin Enterprises</organization>
3843      <address><email>ghost@aladdin.com</email></address>
3844    </author>
3845    <author initials="J-L." surname="Gailly" fullname="Jean-Loup Gailly">
3846      <organization/>
3847      <address><email>gzip@prep.ai.mit.edu</email></address>
3848    </author>
3849    <author initials="M." surname="Adler" fullname="Mark Adler">
3850      <organization/>
3851      <address><email>madler@alumni.caltech.edu</email></address>
3852    </author>
3853    <author initials="L.P." surname="Deutsch" fullname="L. Peter Deutsch">
3854      <organization/>
3855      <address><email>ghost@aladdin.com</email></address>
3856    </author>
3857    <author initials="G." surname="Randers-Pehrson" fullname="Glenn Randers-Pehrson">
3858      <organization/>
3859      <address><email>randeg@alumni.rpi.edu</email></address>
3860    </author>
3861    <date month="May" year="1996"/>
3862  </front>
3863  <seriesInfo name="RFC" value="1952"/>
3864  <annotation>
3865    RFC 1952 is an Informational RFC, thus it may be less stable than
3866    this specification. On the other hand, this downward reference was
3867    present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
3868    therefore it is unlikely to cause problems in practice. See also
3869    <xref target="BCP97"/>.
3870  </annotation>
3871</reference>
3872
3873</references>
3874
3875<references title="Informative References">
3876
3877<reference anchor="Nie1997" target="http://doi.acm.org/10.1145/263105.263157">
3878  <front>
3879    <title>Network Performance Effects of HTTP/1.1, CSS1, and PNG</title>
3880    <author initials="H.F.." surname="Nielsen" fullname="H.F. Nielsen">
3881      <organization/>
3882    </author>
3883    <author initials="J." surname="Gettys" fullname="J. Gettys">
3884      <organization/>
3885    </author>
3886    <author initials="E." surname="Prud'hommeaux" fullname="E. Prud'hommeaux">
3887      <organization/>
3888    </author>
3889    <author initials="H." surname="Lie" fullname="H. Lie">
3890      <organization/>
3891    </author>
3892    <author initials="C." surname="Lilley" fullname="C. Lilley">
3893      <organization/>
3894    </author>
3895    <date year="1997" month="September"/>
3896  </front>
3897  <seriesInfo name="ACM" value="Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication SIGCOMM '97"/>
3898</reference>
3899
3900<reference anchor="Pad1995" target="http://portal.acm.org/citation.cfm?id=219094">
3901  <front>
3902    <title>Improving HTTP Latency</title>
3903    <author initials="V.N." surname="Padmanabhan" fullname="Venkata N. Padmanabhan">
3904      <organization/>
3905    </author>
3906    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
3907      <organization/>
3908    </author>
3909    <date year="1995" month="December"/>
3910  </front>
3911  <seriesInfo name="Computer Networks and ISDN Systems" value="v. 28, pp. 25-35"/>
3912</reference>
3913
3914<reference anchor="RFC1123">
3915  <front>
3916    <title>Requirements for Internet Hosts - Application and Support</title>
3917    <author initials="R." surname="Braden" fullname="Robert Braden">
3918      <organization>University of Southern California (USC), Information Sciences Institute</organization>
3919      <address><email>Braden@ISI.EDU</email></address>
3920    </author>
3921    <date month="October" year="1989"/>
3922  </front>
3923  <seriesInfo name="STD" value="3"/>
3924  <seriesInfo name="RFC" value="1123"/>
3925</reference>
3926
3927<reference anchor="RFC1305">
3928  <front>
3929    <title>Network Time Protocol (Version 3) Specification, Implementation</title>
3930    <author initials="D." surname="Mills" fullname="David L. Mills">
3931      <organization>University of Delaware, Electrical Engineering Department</organization>
3932      <address><email>mills@udel.edu</email></address>
3933    </author>
3934    <date month="March" year="1992"/>
3935  </front>
3936  <seriesInfo name="RFC" value="1305"/>
3937</reference>
3938
3939<reference anchor="RFC1900">
3940  <front>
3941    <title>Renumbering Needs Work</title>
3942    <author initials="B." surname="Carpenter" fullname="Brian E. Carpenter">
3943      <organization>CERN, Computing and Networks Division</organization>
3944      <address><email>brian@dxcoms.cern.ch</email></address>
3945    </author>
3946    <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
3947      <organization>cisco Systems</organization>
3948      <address><email>yakov@cisco.com</email></address>
3949    </author>
3950    <date month="February" year="1996"/>
3951  </front>
3952  <seriesInfo name="RFC" value="1900"/>
3953</reference>
3954
3955<reference anchor="RFC1945">
3956  <front>
3957    <title abbrev="HTTP/1.0">Hypertext Transfer Protocol -- HTTP/1.0</title>
3958    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
3959      <organization>MIT, Laboratory for Computer Science</organization>
3960      <address><email>timbl@w3.org</email></address>
3961    </author>
3962    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
3963      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
3964      <address><email>fielding@ics.uci.edu</email></address>
3965    </author>
3966    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
3967      <organization>W3 Consortium, MIT Laboratory for Computer Science</organization>
3968      <address><email>frystyk@w3.org</email></address>
3969    </author>
3970    <date month="May" year="1996"/>
3971  </front>
3972  <seriesInfo name="RFC" value="1945"/>
3973</reference>
3974
3975<reference anchor="RFC2045">
3976  <front>
3977    <title abbrev="Internet Message Bodies">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</title>
3978    <author initials="N." surname="Freed" fullname="Ned Freed">
3979      <organization>Innosoft International, Inc.</organization>
3980      <address><email>ned@innosoft.com</email></address>
3981    </author>
3982    <author initials="N.S." surname="Borenstein" fullname="Nathaniel S. Borenstein">
3983      <organization>First Virtual Holdings</organization>
3984      <address><email>nsb@nsb.fv.com</email></address>
3985    </author>
3986    <date month="November" year="1996"/>
3987  </front>
3988  <seriesInfo name="RFC" value="2045"/>
3989</reference>
3990
3991<reference anchor="RFC2047">
3992  <front>
3993    <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
3994    <author initials="K." surname="Moore" fullname="Keith Moore">
3995      <organization>University of Tennessee</organization>
3996      <address><email>moore@cs.utk.edu</email></address>
3997    </author>
3998    <date month="November" year="1996"/>
3999  </front>
4000  <seriesInfo name="RFC" value="2047"/>
4001</reference>
4002
4003<reference anchor="RFC2068">
4004  <front>
4005    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
4006    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
4007      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
4008      <address><email>fielding@ics.uci.edu</email></address>
4009    </author>
4010    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4011      <organization>MIT Laboratory for Computer Science</organization>
4012      <address><email>jg@w3.org</email></address>
4013    </author>
4014    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
4015      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
4016      <address><email>mogul@wrl.dec.com</email></address>
4017    </author>
4018    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4019      <organization>MIT Laboratory for Computer Science</organization>
4020      <address><email>frystyk@w3.org</email></address>
4021    </author>
4022    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
4023      <organization>MIT Laboratory for Computer Science</organization>
4024      <address><email>timbl@w3.org</email></address>
4025    </author>
4026    <date month="January" year="1997"/>
4027  </front>
4028  <seriesInfo name="RFC" value="2068"/>
4029</reference>
4030
4031<reference anchor='RFC2109'>
4032  <front>
4033    <title>HTTP State Management Mechanism</title>
4034    <author initials='D.M.' surname='Kristol' fullname='David M. Kristol'>
4035      <organization>Bell Laboratories, Lucent Technologies</organization>
4036      <address><email>dmk@bell-labs.com</email></address>
4037    </author>
4038    <author initials='L.' surname='Montulli' fullname='Lou Montulli'>
4039      <organization>Netscape Communications Corp.</organization>
4040      <address><email>montulli@netscape.com</email></address>
4041    </author>
4042    <date year='1997' month='February' />
4043  </front>
4044  <seriesInfo name='RFC' value='2109' />
4045</reference>
4046
4047<reference anchor="RFC2145">
4048  <front>
4049    <title abbrev="HTTP Version Numbers">Use and Interpretation of HTTP Version Numbers</title>
4050    <author initials="J.C." surname="Mogul" fullname="Jeffrey C. Mogul">
4051      <organization>Western Research Laboratory</organization>
4052      <address><email>mogul@wrl.dec.com</email></address>
4053    </author>
4054    <author initials="R.T." surname="Fielding" fullname="Roy T. Fielding">
4055      <organization>Department of Information and Computer Science</organization>
4056      <address><email>fielding@ics.uci.edu</email></address>
4057    </author>
4058    <author initials="J." surname="Gettys" fullname="Jim Gettys">
4059      <organization>MIT Laboratory for Computer Science</organization>
4060      <address><email>jg@w3.org</email></address>
4061    </author>
4062    <author initials="H.F." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
4063      <organization>W3 Consortium</organization>
4064      <address><email>frystyk@w3.org</email></address>
4065    </author>
4066    <date month="May" year="1997"/>
4067  </front>
4068  <seriesInfo name="RFC" value="2145"/>
4069</reference>
4070
4071<reference anchor="RFC2616">
4072  <front>
4073    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
4074    <author initials="R." surname="Fielding" fullname="R. Fielding">
4075      <organization>University of California, Irvine</organization>
4076      <address><email>fielding@ics.uci.edu</email></address>
4077    </author>
4078    <author initials="J." surname="Gettys" fullname="J. Gettys">
4079      <organization>W3C</organization>
4080      <address><email>jg@w3.org</email></address>
4081    </author>
4082    <author initials="J." surname="Mogul" fullname="J. Mogul">
4083      <organization>Compaq Computer Corporation</organization>
4084      <address><email>mogul@wrl.dec.com</email></address>
4085    </author>
4086    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
4087      <organization>MIT Laboratory for Computer Science</organization>
4088      <address><email>frystyk@w3.org</email></address>
4089    </author>
4090    <author initials="L." surname="Masinter" fullname="L. Masinter">
4091      <organization>Xerox Corporation</organization>
4092      <address><email>masinter@parc.xerox.com</email></address>
4093    </author>
4094    <author initials="P." surname="Leach" fullname="P. Leach">
4095      <organization>Microsoft Corporation</organization>
4096      <address><email>paulle@microsoft.com</email></address>
4097    </author>
4098    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
4099      <organization>W3C</organization>
4100      <address><email>timbl@w3.org</email></address>
4101    </author>
4102    <date month="June" year="1999"/>
4103  </front>
4104  <seriesInfo name="RFC" value="2616"/>
4105</reference>
4106
4107<reference anchor='RFC2818'>
4108  <front>
4109    <title>HTTP Over TLS</title>
4110    <author initials='E.' surname='Rescorla' fullname='Eric Rescorla'>
4111      <organization>RTFM, Inc.</organization>
4112      <address><email>ekr@rtfm.com</email></address>
4113    </author>
4114    <date year='2000' month='May' />
4115  </front>
4116  <seriesInfo name='RFC' value='2818' />
4117</reference>
4118
4119<reference anchor='RFC2965'>
4120  <front>
4121    <title>HTTP State Management Mechanism</title>
4122    <author initials='D. M.' surname='Kristol' fullname='David M. Kristol'>
4123      <organization>Bell Laboratories, Lucent Technologies</organization>
4124      <address><email>dmk@bell-labs.com</email></address>
4125    </author>
4126    <author initials='L.' surname='Montulli' fullname='Lou Montulli'>
4127      <organization>Epinions.com, Inc.</organization>
4128      <address><email>lou@montulli.org</email></address>
4129    </author>
4130    <date year='2000' month='October' />
4131  </front>
4132  <seriesInfo name='RFC' value='2965' />
4133</reference>
4134
4135<reference anchor='RFC3864'>
4136  <front>
4137    <title>Registration Procedures for Message Header Fields</title>
4138    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
4139      <organization>Nine by Nine</organization>
4140      <address><email>GK-IETF@ninebynine.org</email></address>
4141    </author>
4142    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
4143      <organization>BEA Systems</organization>
4144      <address><email>mnot@pobox.com</email></address>
4145    </author>
4146    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
4147      <organization>HP Labs</organization>
4148      <address><email>JeffMogul@acm.org</email></address>
4149    </author>
4150    <date year='2004' month='September' />
4151  </front>
4152  <seriesInfo name='BCP' value='90' />
4153  <seriesInfo name='RFC' value='3864' />
4154</reference>
4155
4156<reference anchor="RFC4288">
4157  <front>
4158    <title>Media Type Specifications and Registration Procedures</title>
4159    <author initials="N." surname="Freed" fullname="N. Freed">
4160      <organization>Sun Microsystems</organization>
4161      <address>
4162        <email>ned.freed@mrochek.com</email>
4163      </address>
4164    </author>
4165    <author initials="J." surname="Klensin" fullname="J. Klensin">
4166      <organization/>
4167      <address>
4168        <email>klensin+ietf@jck.com</email>
4169      </address>
4170    </author>
4171    <date year="2005" month="December"/>
4172  </front>
4173  <seriesInfo name="BCP" value="13"/>
4174  <seriesInfo name="RFC" value="4288"/>
4175</reference>
4176
4177<reference anchor='RFC4395'>
4178  <front>
4179    <title>Guidelines and Registration Procedures for New URI Schemes</title>
4180    <author initials='T.' surname='Hansen' fullname='T. Hansen'>
4181      <organization>AT&amp;T Laboratories</organization>
4182      <address>
4183        <email>tony+urireg@maillennium.att.com</email>
4184      </address>
4185    </author>
4186    <author initials='T.' surname='Hardie' fullname='T. Hardie'>
4187      <organization>Qualcomm, Inc.</organization>
4188      <address>
4189        <email>hardie@qualcomm.com</email>
4190      </address>
4191    </author>
4192    <author initials='L.' surname='Masinter' fullname='L. Masinter'>
4193      <organization>Adobe Systems</organization>
4194      <address>
4195        <email>LMM@acm.org</email>
4196      </address>
4197    </author>
4198    <date year='2006' month='February' />
4199  </front>
4200  <seriesInfo name='BCP' value='115' />
4201  <seriesInfo name='RFC' value='4395' />
4202</reference>
4203
4204<reference anchor='RFC5226'>
4205  <front>
4206    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
4207    <author initials='T.' surname='Narten' fullname='T. Narten'>
4208      <organization>IBM</organization>
4209      <address><email>narten@us.ibm.com</email></address>
4210    </author>
4211    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
4212      <organization>Google</organization>
4213      <address><email>Harald@Alvestrand.no</email></address>
4214    </author>
4215    <date year='2008' month='May' />
4216  </front>
4217  <seriesInfo name='BCP' value='26' />
4218  <seriesInfo name='RFC' value='5226' />
4219</reference>
4220
4221<reference anchor="RFC5322">
4222  <front>
4223    <title>Internet Message Format</title>
4224    <author initials="P." surname="Resnick" fullname="P. Resnick">
4225      <organization>Qualcomm Incorporated</organization>
4226    </author>
4227    <date year="2008" month="October"/>
4228  </front> 
4229  <seriesInfo name="RFC" value="5322"/>
4230</reference>
4231
4232<reference anchor='BCP97'>
4233  <front>
4234    <title>Handling Normative References to Standards-Track Documents</title>
4235    <author initials='J.' surname='Klensin' fullname='J. Klensin'>
4236      <organization />
4237      <address>
4238        <email>klensin+ietf@jck.com</email>
4239      </address>
4240    </author>
4241    <author initials='S.' surname='Hartman' fullname='S. Hartman'>
4242      <organization>MIT</organization>
4243      <address>
4244        <email>hartmans-ietf@mit.edu</email>
4245      </address>
4246    </author>
4247    <date year='2007' month='June' />
4248  </front>
4249  <seriesInfo name='BCP' value='97' />
4250  <seriesInfo name='RFC' value='4897' />
4251</reference>
4252
4253<reference anchor="Kri2001" target="http://arxiv.org/abs/cs.SE/0105018">
4254  <front>
4255    <title>HTTP Cookies: Standards, Privacy, and Politics</title>
4256    <author initials="D." surname="Kristol" fullname="David M. Kristol">
4257      <organization/>
4258    </author>
4259    <date year="2001" month="November"/>
4260  </front>
4261  <seriesInfo name="ACM Transactions on Internet Technology" value="Vol. 1, #2"/>
4262</reference>
4263
4264<reference anchor="Spe" target="http://sunsite.unc.edu/mdma-release/http-prob.html">
4265  <front>
4266  <title>Analysis of HTTP Performance Problems</title>
4267  <author initials="S." surname="Spero" fullname="Simon E. Spero">
4268    <organization/>
4269  </author>
4270  <date/>
4271  </front>
4272</reference>
4273
4274<reference anchor="Tou1998" target="http://www.isi.edu/touch/pubs/http-perf96/">
4275  <front>
4276  <title>Analysis of HTTP Performance</title>
4277  <author initials="J." surname="Touch" fullname="Joe Touch">
4278    <organization>USC/Information Sciences Institute</organization>
4279    <address><email>touch@isi.edu</email></address>
4280  </author>
4281  <author initials="J." surname="Heidemann" fullname="John Heidemann">
4282    <organization>USC/Information Sciences Institute</organization>
4283    <address><email>johnh@isi.edu</email></address>
4284  </author>
4285  <author initials="K." surname="Obraczka" fullname="Katia Obraczka">
4286    <organization>USC/Information Sciences Institute</organization>
4287    <address><email>katia@isi.edu</email></address>
4288  </author>
4289  <date year="1998" month="Aug"/>
4290  </front>
4291  <seriesInfo name="ISI Research Report" value="ISI/RR-98-463"/>
4292  <annotation>(original report dated Aug. 1996)</annotation>
4293</reference>
4294
4295</references>
4296
4297
4298<section title="Tolerant Applications" anchor="tolerant.applications">
4299<t>
4300   Although this document specifies the requirements for the generation
4301   of HTTP/1.1 messages, not all applications will be correct in their
4302   implementation. We therefore recommend that operational applications
4303   be tolerant of deviations whenever those deviations can be
4304   interpreted unambiguously.
4305</t>
4306<t>
4307   Clients &SHOULD; be tolerant in parsing the Status-Line and servers
4308   tolerant when parsing the Request-Line. In particular, they &SHOULD;
4309   accept any amount of WSP characters between fields, even though
4310   only a single SP is required.
4311</t>
4312<t>
4313   The line terminator for header fields is the sequence CRLF.
4314   However, we recommend that applications, when parsing such headers,
4315   recognize a single LF as a line terminator and ignore the leading CR.
4316</t>
4317<t>
4318   The character set of an entity-body &SHOULD; be labeled as the lowest
4319   common denominator of the character codes used within that body, with
4320   the exception that not labeling the entity is preferred over labeling
4321   the entity with the labels US-ASCII or ISO-8859-1. See &payload;.
4322</t>
4323<t>
4324   Additional rules for requirements on parsing and encoding of dates
4325   and other potential problems with date encodings include:
4326</t>
4327<t>
4328  <list style="symbols">
4329     <t>HTTP/1.1 clients and caches &SHOULD; assume that an RFC-850 date
4330        which appears to be more than 50 years in the future is in fact
4331        in the past (this helps solve the "year 2000" problem).</t>
4332
4333     <t>An HTTP/1.1 implementation &MAY; internally represent a parsed
4334        Expires date as earlier than the proper value, but &MUST-NOT;
4335        internally represent a parsed Expires date as later than the
4336        proper value.</t>
4337
4338     <t>All expiration-related calculations &MUST; be done in GMT. The
4339        local time zone &MUST-NOT; influence the calculation or comparison
4340        of an age or expiration time.</t>
4341
4342     <t>If an HTTP header incorrectly carries a date value with a time
4343        zone other than GMT, it &MUST; be converted into GMT using the
4344        most conservative possible conversion.</t>
4345  </list>
4346</t>
4347</section>
4348
4349<section title="Compatibility with Previous Versions" anchor="compatibility">
4350<t>
4351   HTTP has been in use by the World-Wide Web global information initiative
4352   since 1990. The first version of HTTP, later referred to as HTTP/0.9,
4353   was a simple protocol for hypertext data transfer across the Internet
4354   with only a single method and no metadata.
4355   HTTP/1.0, as defined by <xref target="RFC1945"/>, added a range of request
4356   methods and MIME-like messaging that could include metadata about the data
4357   transferred and modifiers on the request/response semantics. However,
4358   HTTP/1.0 did not sufficiently take into consideration the effects of
4359   hierarchical proxies, caching, the need for persistent connections, or
4360   name-based virtual hosts. The proliferation of incompletely-implemented
4361   applications calling themselves "HTTP/1.0" further necessitated a
4362   protocol version change in order for two communicating applications
4363   to determine each other's true capabilities.
4364</t>
4365<t>
4366   HTTP/1.1 remains compatible with HTTP/1.0 by including more stringent
4367   requirements that enable reliable implementations, adding only
4368   those new features that will either be safely ignored by an HTTP/1.0
4369   recipient or only sent when communicating with a party advertising
4370   compliance with HTTP/1.1.
4371</t>
4372<t>
4373   It is beyond the scope of a protocol specification to mandate
4374   compliance with previous versions. HTTP/1.1 was deliberately
4375   designed, however, to make supporting previous versions easy. It is
4376   worth noting that, at the time of composing this specification
4377   (1996), we would expect commercial HTTP/1.1 servers to:
4378  <list style="symbols">
4379     <t>recognize the format of the Request-Line for HTTP/0.9, 1.0, and
4380        1.1 requests;</t>
4381
4382     <t>understand any valid request in the format of HTTP/0.9, 1.0, or
4383        1.1;</t>
4384
4385     <t>respond appropriately with a message in the same major version
4386        used by the client.</t>
4387  </list>
4388</t>
4389<t>
4390   And we would expect HTTP/1.1 clients to:
4391  <list style="symbols">
4392     <t>recognize the format of the Status-Line for HTTP/1.0 and 1.1
4393        responses;</t>
4394
4395     <t>understand any valid response in the format of HTTP/0.9, 1.0, or
4396        1.1.</t>
4397  </list>
4398</t>
4399<t>
4400   For most implementations of HTTP/1.0, each connection is established
4401   by the client prior to the request and closed by the server after
4402   sending the response. Some implementations implement the Keep-Alive
4403   version of persistent connections described in <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/>.
4404</t>
4405
4406<section title="Changes from HTTP/1.0" anchor="changes.from.1.0">
4407<t>
4408   This section summarizes major differences between versions HTTP/1.0
4409   and HTTP/1.1.
4410</t>
4411
4412<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">
4413<t>
4414   The requirements that clients and servers support the Host request-header,
4415   report an error if the Host request-header (<xref target="header.host"/>) is
4416   missing from an HTTP/1.1 request, and accept absolute URIs (<xref target="request-target"/>)
4417   are among the most important changes defined by this
4418   specification.
4419</t>
4420<t>
4421   Older HTTP/1.0 clients assumed a one-to-one relationship of IP
4422   addresses and servers; there was no other established mechanism for
4423   distinguishing the intended server of a request than the IP address
4424   to which that request was directed. The changes outlined above will
4425   allow the Internet, once older HTTP clients are no longer common, to
4426   support multiple Web sites from a single IP address, greatly
4427   simplifying large operational Web servers, where allocation of many
4428   IP addresses to a single host has created serious problems. The
4429   Internet will also be able to recover the IP addresses that have been
4430   allocated for the sole purpose of allowing special-purpose domain
4431   names to be used in root-level HTTP URLs. Given the rate of growth of
4432   the Web, and the number of servers already deployed, it is extremely
4433   important that all implementations of HTTP (including updates to
4434   existing HTTP/1.0 applications) correctly implement these
4435   requirements:
4436  <list style="symbols">
4437     <t>Both clients and servers &MUST; support the Host request-header.</t>
4438
4439     <t>A client that sends an HTTP/1.1 request &MUST; send a Host header.</t>
4440
4441     <t>Servers &MUST; report a 400 (Bad Request) error if an HTTP/1.1
4442        request does not include a Host request-header.</t>
4443
4444     <t>Servers &MUST; accept absolute URIs.</t>
4445  </list>
4446</t>
4447</section>
4448</section>
4449
4450<section title="Compatibility with HTTP/1.0 Persistent Connections" anchor="compatibility.with.http.1.0.persistent.connections">
4451<t>
4452   Some clients and servers might wish to be compatible with some
4453   previous implementations of persistent connections in HTTP/1.0
4454   clients and servers. Persistent connections in HTTP/1.0 are
4455   explicitly negotiated as they are not the default behavior. HTTP/1.0
4456   experimental implementations of persistent connections are faulty,
4457   and the new facilities in HTTP/1.1 are designed to rectify these
4458   problems. The problem was that some existing 1.0 clients may be
4459   sending Keep-Alive to a proxy server that doesn't understand
4460   Connection, which would then erroneously forward it to the next
4461   inbound server, which would establish the Keep-Alive connection and
4462   result in a hung HTTP/1.0 proxy waiting for the close on the
4463   response. The result is that HTTP/1.0 clients must be prevented from
4464   using Keep-Alive when talking to proxies.
4465</t>
4466<t>
4467   However, talking to proxies is the most important use of persistent
4468   connections, so that prohibition is clearly unacceptable. Therefore,
4469   we need some other mechanism for indicating a persistent connection
4470   is desired, which is safe to use even when talking to an old proxy
4471   that ignores Connection. Persistent connections are the default for
4472   HTTP/1.1 messages; we introduce a new keyword (Connection: close) for
4473   declaring non-persistence. See <xref target="header.connection"/>.
4474</t>
4475<t>
4476   The original HTTP/1.0 form of persistent connections (the Connection:
4477   Keep-Alive and Keep-Alive header) is documented in <xref x:sec="19.7.1" x:fmt="of" target="RFC2068"/>.
4478</t>
4479</section>
4480
4481<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
4482<t>
4483   This specification has been carefully audited to correct and
4484   disambiguate key word usage; RFC 2068 had many problems in respect to
4485   the conventions laid out in <xref target="RFC2119"/>.
4486</t>
4487<t>
4488   Transfer-coding and message lengths all interact in ways that
4489   required fixing exactly when chunked encoding is used (to allow for
4490   transfer encoding that may not be self delimiting); it was important
4491   to straighten out exactly how message lengths are computed. (Sections
4492   <xref target="transfer.codings" format="counter"/>, <xref target="message.length" format="counter"/>,
4493   <xref target="header.content-length" format="counter"/>,
4494   see also <xref target="Part3"/>, <xref target="Part5"/> and <xref target="Part6"/>)
4495</t>
4496<t>
4497   The use and interpretation of HTTP version numbers has been clarified
4498   by <xref target="RFC2145"/>. Require proxies to upgrade requests to highest protocol
4499   version they support to deal with problems discovered in HTTP/1.0
4500   implementations (<xref target="http.version"/>)
4501</t>
4502<t>
4503   Quality Values of zero should indicate that "I don't want something"
4504   to allow clients to refuse a representation. (<xref target="quality.values"/>)
4505</t>
4506<t>
4507   Transfer-coding had significant problems, particularly with
4508   interactions with chunked encoding. The solution is that transfer-codings
4509   become as full fledged as content-codings. This involves
4510   adding an IANA registry for transfer-codings (separate from content
4511   codings), a new header field (TE) and enabling trailer headers in the
4512   future. Transfer encoding is a major performance benefit, so it was
4513   worth fixing <xref target="Nie1997"/>. TE also solves another, obscure, downward
4514   interoperability problem that could have occurred due to interactions
4515   between authentication trailers, chunked encoding and HTTP/1.0
4516   clients.(Section <xref target="transfer.codings" format="counter"/>, <xref target="chunked.encoding" format="counter"/>,
4517   and <xref target="header.te" format="counter"/>)
4518</t>
4519</section>
4520
4521<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
4522<t>
4523  Empty list elements in list productions have been deprecated.
4524  (<xref target="notation.abnf"/>)
4525</t>
4526<t>
4527  Rules about implicit linear whitespace between certain grammar productions
4528  have been removed; now it's only allowed when specifically pointed out
4529  in the ABNF. The NUL character is no longer allowed in comment and quoted-string
4530  text. The quoted-pair rule no longer allows escaping NUL, CR or LF.
4531  Non-ASCII content in header fields and reason phrase has been obsoleted and
4532  made opaque (the TEXT rule was removed)
4533  (<xref target="basic.rules"/>)
4534</t>
4535<t>
4536  Clarify that HTTP-Version is case sensitive.
4537  (<xref target="http.version"/>)
4538</t>
4539<t>
4540  Remove reference to non-existant identity transfer-coding value tokens.
4541  (Sections <xref format="counter" target="transfer.codings"/> and
4542  <xref format="counter" target="message.length"/>)
4543</t>
4544<t>
4545  Clarification that the chunk length does not include
4546  the count of the octets in the chunk header and trailer.
4547  (<xref target="chunked.encoding"/>)
4548</t>
4549<t>
4550  Require that invalid whitespace around field-names be rejected.
4551  (<xref target="header.fields"/>)
4552</t>
4553<t>
4554  Update use of abs_path production from RFC1808 to the path-absolute + query
4555  components of RFC3986.
4556  (<xref target="request-target"/>)
4557</t>
4558<t>
4559  Clarify exactly when close connection options must be sent.
4560  (<xref target="header.connection"/>)
4561</t>
4562</section>
4563</section>
4564
4565<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
4566<figure>
4567<artwork type="abnf" name="p1-messaging.parsed-abnf">
4568<x:ref>BWS</x:ref> = OWS
4569
4570<x:ref>Cache-Control</x:ref> = &lt;Cache-Control, defined in [Part6], Section 3.4&gt;
4571<x:ref>Chunked-Body</x:ref> = *chunk last-chunk trailer-part CRLF
4572<x:ref>Connection</x:ref> = "Connection:" OWS Connection-v
4573<x:ref>Connection-v</x:ref> = *( "," OWS ) connection-token *( OWS "," [ OWS
4574 connection-token ] )
4575<x:ref>Content-Length</x:ref> = "Content-Length:" OWS 1*Content-Length-v
4576<x:ref>Content-Length-v</x:ref> = 1*DIGIT
4577
4578<x:ref>Date</x:ref> = "Date:" OWS Date-v
4579<x:ref>Date-v</x:ref> = HTTP-date
4580
4581<x:ref>GMT</x:ref> = %x47.4D.54 ; GMT
4582
4583<x:ref>HTTP-Prot-Name</x:ref> = %x48.54.54.50 ; HTTP
4584<x:ref>HTTP-Version</x:ref> = HTTP-Prot-Name "/" 1*DIGIT "." 1*DIGIT
4585<x:ref>HTTP-date</x:ref> = rfc1123-date / obs-date
4586<x:ref>HTTP-message</x:ref> = start-line *( header-field CRLF ) CRLF [ message-body
4587 ]
4588<x:ref>Host</x:ref> = "Host:" OWS Host-v
4589<x:ref>Host-v</x:ref> = uri-host [ ":" port ]
4590
4591<x:ref>Method</x:ref> = token
4592
4593<x:ref>OWS</x:ref> = *( [ obs-fold ] WSP )
4594
4595<x:ref>Pragma</x:ref> = &lt;Pragma, defined in [Part6], Section 3.4&gt;
4596
4597<x:ref>RWS</x:ref> = 1*( [ obs-fold ] WSP )
4598<x:ref>Reason-Phrase</x:ref> = *( WSP / VCHAR / obs-text )
4599<x:ref>Request</x:ref> = Request-Line *( ( general-header / request-header /
4600 entity-header ) CRLF ) CRLF [ message-body ]
4601<x:ref>Request-Line</x:ref> = Method SP request-target SP HTTP-Version CRLF
4602<x:ref>Response</x:ref> = Status-Line *( ( general-header / response-header /
4603 entity-header ) CRLF ) CRLF [ message-body ]
4604
4605<x:ref>Status-Code</x:ref> = 3DIGIT
4606<x:ref>Status-Line</x:ref> = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
4607
4608<x:ref>TE</x:ref> = "TE:" OWS TE-v
4609<x:ref>TE-v</x:ref> = [ ( "," / t-codings ) *( OWS "," [ OWS t-codings ] ) ]
4610<x:ref>Trailer</x:ref> = "Trailer:" OWS Trailer-v
4611<x:ref>Trailer-v</x:ref> = *( "," OWS ) field-name *( OWS "," [ OWS field-name ] )
4612<x:ref>Transfer-Encoding</x:ref> = "Transfer-Encoding:" OWS Transfer-Encoding-v
4613<x:ref>Transfer-Encoding-v</x:ref> = *( "," OWS ) transfer-coding *( OWS "," [ OWS
4614 transfer-coding ] )
4615
4616<x:ref>URI</x:ref> = &lt;URI, defined in [RFC3986], Section 3&gt;
4617<x:ref>URI-reference</x:ref> = &lt;URI-reference, defined in [RFC3986], Section 4.1&gt;
4618<x:ref>Upgrade</x:ref> = "Upgrade:" OWS Upgrade-v
4619<x:ref>Upgrade-v</x:ref> = *( "," OWS ) product *( OWS "," [ OWS product ] )
4620
4621<x:ref>Via</x:ref> = "Via:" OWS Via-v
4622<x:ref>Via-v</x:ref> = *( "," OWS ) received-protocol RWS received-by [ RWS comment
4623 ] *( OWS "," [ OWS received-protocol RWS received-by [ RWS comment ]
4624 ] )
4625
4626<x:ref>Warning</x:ref> = &lt;Warning, defined in [Part6], Section 3.6&gt;
4627
4628<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
4629<x:ref>asctime-date</x:ref> = day-name SP date3 SP time-of-day SP year
4630<x:ref>attribute</x:ref> = token
4631<x:ref>authority</x:ref> = &lt;authority, defined in [RFC3986], Section 3.2&gt;
4632
4633<x:ref>chunk</x:ref> = chunk-size *WSP [ chunk-ext ] CRLF chunk-data CRLF
4634<x:ref>chunk-data</x:ref> = 1*OCTET
4635<x:ref>chunk-ext</x:ref> = *( ";" *WSP chunk-ext-name [ "=" chunk-ext-val ] *WSP )
4636<x:ref>chunk-ext-name</x:ref> = token
4637<x:ref>chunk-ext-val</x:ref> = token / quoted-string
4638<x:ref>chunk-size</x:ref> = 1*HEXDIG
4639<x:ref>comment</x:ref> = "(" *( ctext / quoted-pair / comment ) ")"
4640<x:ref>connection-token</x:ref> = token
4641<x:ref>ctext</x:ref> = OWS / %x21-27 ; '!'-'''
4642 / %x2A-5B ; '*'-'['
4643 / %x5D-7E ; ']'-'~'
4644 / obs-text
4645
4646<x:ref>date1</x:ref> = day SP month SP year
4647<x:ref>date2</x:ref> = day "-" month "-" 2DIGIT
4648<x:ref>date3</x:ref> = month SP ( 2DIGIT / ( SP DIGIT ) )
4649<x:ref>day</x:ref> = 2DIGIT
4650<x:ref>day-name</x:ref> = %x4D.6F.6E ; Mon
4651 / %x54.75.65 ; Tue
4652 / %x57.65.64 ; Wed
4653 / %x54.68.75 ; Thu
4654 / %x46.72.69 ; Fri
4655 / %x53.61.74 ; Sat
4656 / %x53.75.6E ; Sun
4657<x:ref>day-name-l</x:ref> = %x4D.6F.6E.64.61.79 ; Monday
4658 / %x54.75.65.73.64.61.79 ; Tuesday
4659 / %x57.65.64.6E.65.73.64.61.79 ; Wednesday
4660 / %x54.68.75.72.73.64.61.79 ; Thursday
4661 / %x46.72.69.64.61.79 ; Friday
4662 / %x53.61.74.75.72.64.61.79 ; Saturday
4663 / %x53.75.6E.64.61.79 ; Sunday
4664
4665<x:ref>entity-body</x:ref> = &lt;entity-body, defined in [Part3], Section 3.2&gt;
4666<x:ref>entity-header</x:ref> = &lt;entity-header, defined in [Part3], Section 3.1&gt;
4667
4668<x:ref>field-content</x:ref> = *( WSP / VCHAR / obs-text )
4669<x:ref>field-name</x:ref> = token
4670<x:ref>field-value</x:ref> = *( field-content / OWS )
4671
4672<x:ref>general-header</x:ref> = Cache-Control / Connection / Date / Pragma / Trailer
4673 / Transfer-Encoding / Upgrade / Via / Warning
4674
4675<x:ref>header-field</x:ref> = field-name ":" OWS [ field-value ] OWS
4676<x:ref>hour</x:ref> = 2DIGIT
4677<x:ref>http-URI</x:ref> = "http://" authority path-abempty [ "?" query ]
4678<x:ref>https-URI</x:ref> = "https://" authority path-abempty [ "?" query ]
4679
4680<x:ref>last-chunk</x:ref> = 1*"0" *WSP [ chunk-ext ] CRLF
4681
4682<x:ref>message-body</x:ref> = entity-body /
4683 &lt;entity-body encoded as per Transfer-Encoding&gt;
4684<x:ref>minute</x:ref> = 2DIGIT
4685<x:ref>month</x:ref> = %x4A.61.6E ; Jan
4686 / %x46.65.62 ; Feb
4687 / %x4D.61.72 ; Mar
4688 / %x41.70.72 ; Apr
4689 / %x4D.61.79 ; May
4690 / %x4A.75.6E ; Jun
4691 / %x4A.75.6C ; Jul
4692 / %x41.75.67 ; Aug
4693 / %x53.65.70 ; Sep
4694 / %x4F.63.74 ; Oct
4695 / %x4E.6F.76 ; Nov
4696 / %x44.65.63 ; Dec
4697
4698<x:ref>obs-date</x:ref> = rfc850-date / asctime-date
4699<x:ref>obs-fold</x:ref> = CRLF
4700<x:ref>obs-text</x:ref> = %x80-FF
4701
4702<x:ref>partial-URI</x:ref> = relative-part [ "?" query ]
4703<x:ref>path-abempty</x:ref> = &lt;path-abempty, defined in [RFC3986], Section 3.3&gt;
4704<x:ref>path-absolute</x:ref> = &lt;path-absolute, defined in [RFC3986], Section 3.3&gt;
4705<x:ref>port</x:ref> = &lt;port, defined in [RFC3986], Section 3.2.3&gt;
4706<x:ref>product</x:ref> = token [ "/" product-version ]
4707<x:ref>product-version</x:ref> = token
4708<x:ref>protocol-name</x:ref> = token
4709<x:ref>protocol-version</x:ref> = token
4710<x:ref>pseudonym</x:ref> = token
4711
4712<x:ref>qdtext</x:ref> = OWS / "!" / %x23-5B ; '#'-'['
4713 / %x5D-7E ; ']'-'~'
4714 / obs-text
4715<x:ref>query</x:ref> = &lt;query, defined in [RFC3986], Section 3.4&gt;
4716<x:ref>quoted-pair</x:ref> = "\" quoted-text
4717<x:ref>quoted-string</x:ref> = DQUOTE *( qdtext / quoted-pair ) DQUOTE
4718<x:ref>quoted-text</x:ref> = %x01-09 / %x0B-0C / %x0E-FF
4719<x:ref>qvalue</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
4720
4721<x:ref>received-by</x:ref> = ( uri-host [ ":" port ] ) / pseudonym
4722<x:ref>received-protocol</x:ref> = [ protocol-name "/" ] protocol-version
4723<x:ref>relative-part</x:ref> = &lt;relative-part, defined in [RFC3986], Section 4.2&gt;
4724<x:ref>request-header</x:ref> = &lt;request-header, defined in [Part2], Section 3&gt;
4725<x:ref>request-target</x:ref> = "*" / absolute-URI / ( path-absolute [ "?" query ] )
4726 / authority
4727<x:ref>response-header</x:ref> = &lt;response-header, defined in [Part2], Section 5&gt;
4728<x:ref>rfc1123-date</x:ref> = day-name "," SP date1 SP time-of-day SP GMT
4729<x:ref>rfc850-date</x:ref> = day-name-l "," SP date2 SP time-of-day SP GMT
4730
4731<x:ref>second</x:ref> = 2DIGIT
4732<x:ref>start-line</x:ref> = Request-Line / Status-Line
4733
4734<x:ref>t-codings</x:ref> = "trailers" / ( transfer-extension [ te-params ] )
4735<x:ref>tchar</x:ref> = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*" / "+" / "-" / "." /
4736 "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
4737<x:ref>te-ext</x:ref> = OWS ";" OWS token [ "=" ( token / quoted-string ) ]
4738<x:ref>te-params</x:ref> = OWS ";" OWS "q=" qvalue *te-ext
4739<x:ref>time-of-day</x:ref> = hour ":" minute ":" second
4740<x:ref>token</x:ref> = 1*tchar
4741<x:ref>trailer-part</x:ref> = *( entity-header CRLF )
4742<x:ref>transfer-coding</x:ref> = "chunked" / "compress" / "deflate" / "gzip" /
4743 transfer-extension
4744<x:ref>transfer-extension</x:ref> = token *( OWS ";" OWS transfer-parameter )
4745<x:ref>transfer-parameter</x:ref> = attribute BWS "=" BWS value
4746
4747<x:ref>uri-host</x:ref> = &lt;host, defined in [RFC3986], Section 3.2.2&gt;
4748
4749<x:ref>value</x:ref> = token / quoted-string
4750
4751<x:ref>year</x:ref> = 4DIGIT
4752</artwork>
4753</figure>
4754<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
4755; Chunked-Body defined but not used
4756; Content-Length defined but not used
4757; HTTP-message defined but not used
4758; Host defined but not used
4759; Request defined but not used
4760; Response defined but not used
4761; TE defined but not used
4762; URI defined but not used
4763; URI-reference defined but not used
4764; http-URI defined but not used
4765; https-URI defined but not used
4766; partial-URI defined but not used
4767</artwork></figure></section>
4768
4769
4770<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
4771
4772<section title="Since RFC2616">
4773<t>
4774  Extracted relevant partitions from <xref target="RFC2616"/>.
4775</t>
4776</section>
4777
4778<section title="Since draft-ietf-httpbis-p1-messaging-00">
4779<t>
4780  Closed issues:
4781  <list style="symbols"> 
4782    <t>
4783      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/1"/>:
4784      "HTTP Version should be case sensitive"
4785      (<eref target="http://purl.org/NET/http-errata#verscase"/>)
4786    </t>
4787    <t>
4788      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/2"/>:
4789      "'unsafe' characters"
4790      (<eref target="http://purl.org/NET/http-errata#unsafe-uri"/>)
4791    </t>
4792    <t>
4793      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/3"/>:
4794      "Chunk Size Definition"
4795      (<eref target="http://purl.org/NET/http-errata#chunk-size"/>)
4796    </t>
4797    <t>
4798      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/4"/>:
4799      "Message Length"
4800      (<eref target="http://purl.org/NET/http-errata#msg-len-chars"/>)
4801    </t>
4802    <t>
4803      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/8"/>:
4804      "Media Type Registrations"
4805      (<eref target="http://purl.org/NET/http-errata#media-reg"/>)
4806    </t>
4807    <t>
4808      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/11"/>:
4809      "URI includes query"
4810      (<eref target="http://purl.org/NET/http-errata#uriquery"/>)
4811    </t>
4812    <t>
4813      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/15"/>:
4814      "No close on 1xx responses"
4815      (<eref target="http://purl.org/NET/http-errata#noclose1xx"/>)
4816    </t>
4817    <t>
4818      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/16"/>:
4819      "Remove 'identity' token references"
4820      (<eref target="http://purl.org/NET/http-errata#identity"/>)
4821    </t>
4822    <t>
4823      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/26"/>:
4824      "Import query BNF"
4825    </t>
4826    <t>
4827      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/31"/>:
4828      "qdtext BNF"
4829    </t>
4830    <t>
4831      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
4832      "Normative and Informative references"
4833    </t>
4834    <t>
4835      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/42"/>:
4836      "RFC2606 Compliance"
4837    </t>
4838    <t>
4839      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/45"/>:
4840      "RFC977 reference"
4841    </t>
4842    <t>
4843      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/46"/>:
4844      "RFC1700 references"
4845    </t>
4846    <t>
4847      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/47"/>:
4848      "inconsistency in date format explanation"
4849    </t>
4850    <t>
4851      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/48"/>:
4852      "Date reference typo"
4853    </t>
4854    <t>
4855      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/65"/>:
4856      "Informative references"
4857    </t>
4858    <t>
4859      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/66"/>:
4860      "ISO-8859-1 Reference"
4861    </t>
4862    <t>
4863      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/86"/>:
4864      "Normative up-to-date references"
4865    </t>
4866  </list>
4867</t>
4868<t>
4869  Other changes:
4870  <list style="symbols"> 
4871    <t>
4872      Update media type registrations to use RFC4288 template.
4873    </t>
4874    <t>
4875      Use names of RFC4234 core rules DQUOTE and WSP,
4876      fix broken ABNF for chunk-data
4877      (work in progress on <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>)
4878    </t>
4879  </list>
4880</t>
4881</section>
4882
4883<section title="Since draft-ietf-httpbis-p1-messaging-01">
4884<t>
4885  Closed issues:
4886  <list style="symbols"> 
4887    <t>
4888      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/19"/>:
4889      "Bodies on GET (and other) requests"
4890    </t>
4891    <t>
4892      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/55"/>:
4893      "Updating to RFC4288"
4894    </t>
4895    <t>
4896      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/57"/>:
4897      "Status Code and Reason Phrase"
4898    </t>
4899    <t>
4900      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/82"/>:
4901      "rel_path not used"
4902    </t>
4903  </list>
4904</t>
4905<t>
4906  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
4907  <list style="symbols"> 
4908    <t>
4909      Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" ->
4910      "trailer-part").
4911    </t>
4912    <t>
4913      Avoid underscore character in rule names ("http_URL" ->
4914      "http-URL", "abs_path" -> "path-absolute").
4915    </t>
4916    <t>
4917      Add rules for terms imported from URI spec ("absoluteURI", "authority",
4918      "path-absolute", "port", "query", "relativeURI", "host) -- these will
4919      have to be updated when switching over to RFC3986.
4920    </t>
4921    <t>
4922      Synchronize core rules with RFC5234.
4923    </t>
4924    <t>
4925      Get rid of prose rules that span multiple lines.
4926    </t>
4927    <t>
4928      Get rid of unused rules LOALPHA and UPALPHA.
4929    </t>
4930    <t>
4931      Move "Product Tokens" section (back) into Part 1, as "token" is used
4932      in the definition of the Upgrade header.
4933    </t>
4934    <t>
4935      Add explicit references to BNF syntax and rules imported from other parts of the specification.
4936    </t>
4937    <t>
4938      Rewrite prose rule "token" in terms of "tchar", rewrite prose rule "TEXT".
4939    </t>
4940  </list>
4941</t>
4942</section>
4943
4944<section title="Since draft-ietf-httpbis-p1-messaging-02" anchor="changes.since.02">
4945<t>
4946  Closed issues:
4947  <list style="symbols"> 
4948    <t>
4949      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/51"/>:
4950      "HTTP-date vs. rfc1123-date"
4951    </t>
4952    <t>
4953      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/64"/>:
4954      "WS in quoted-pair"
4955    </t>
4956  </list>
4957</t>
4958<t>
4959  Ongoing work on IANA Message Header Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
4960  <list style="symbols"> 
4961    <t>
4962      Reference RFC 3984, and update header registrations for headers defined
4963      in this document.
4964    </t>
4965  </list>
4966</t>
4967<t>
4968  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
4969  <list style="symbols"> 
4970    <t>
4971      Replace string literals when the string really is case-sensitive (HTTP-Version).
4972    </t>
4973  </list>
4974</t>
4975</section>
4976
4977<section title="Since draft-ietf-httpbis-p1-messaging-03" anchor="changes.since.03">
4978<t>
4979  Closed issues:
4980  <list style="symbols"> 
4981    <t>
4982      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/28"/>:
4983      "Connection closing"
4984    </t>
4985    <t>
4986      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/97"/>:
4987      "Move registrations and registry information to IANA Considerations"
4988    </t>
4989    <t>
4990      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/120"/>:
4991      "need new URL for PAD1995 reference"
4992    </t>
4993    <t>
4994      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/127"/>:
4995      "IANA Considerations: update HTTP URI scheme registration"
4996    </t>
4997    <t>
4998      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/128"/>:
4999      "Cite HTTPS URI scheme definition"
5000    </t>
5001    <t>
5002      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/129"/>:
5003      "List-type headers vs Set-Cookie"
5004    </t>
5005  </list>
5006</t>
5007<t>
5008  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
5009  <list style="symbols"> 
5010    <t>
5011      Replace string literals when the string really is case-sensitive (HTTP-Date).
5012    </t>
5013    <t>
5014      Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.
5015    </t>
5016  </list>
5017</t>
5018</section>
5019
5020<section title="Since draft-ietf-httpbis-p1-messaging-04" anchor="changes.since.04">
5021<t>
5022  Closed issues:
5023  <list style="symbols"> 
5024    <t>
5025      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/34"/>:
5026      "Out-of-date reference for URIs"
5027    </t>
5028    <t>
5029      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/132"/>:
5030      "RFC 2822 is updated by RFC 5322"
5031    </t>
5032  </list>
5033</t>
5034<t>
5035  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
5036  <list style="symbols"> 
5037    <t>
5038      Use "/" instead of "|" for alternatives.
5039    </t>
5040    <t>
5041      Get rid of RFC822 dependency; use RFC5234 plus extensions instead.
5042    </t>
5043    <t>
5044      Only reference RFC 5234's core rules.
5045    </t>
5046    <t>
5047      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
5048      whitespace ("OWS") and required whitespace ("RWS").
5049    </t>
5050    <t>
5051      Rewrite ABNFs to spell out whitespace rules, factor out
5052      header value format definitions.
5053    </t>
5054  </list>
5055</t>
5056</section>
5057
5058<section title="Since draft-ietf-httpbis-p1-messaging-05" anchor="changes.since.05">
5059<t>
5060  Closed issues:
5061  <list style="symbols"> 
5062    <t>
5063      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/30"/>:
5064      "Header LWS"
5065    </t>
5066    <t>
5067      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/52"/>:
5068      "Sort 1.3 Terminology"
5069    </t>
5070    <t>
5071      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/63"/>:
5072      "RFC2047 encoded words"
5073    </t>
5074    <t>
5075      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/74"/>:
5076      "Character Encodings in TEXT"
5077    </t>
5078    <t>
5079      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/77"/>:
5080      "Line Folding"
5081    </t>
5082    <t>
5083      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/83"/>:
5084      "OPTIONS * and proxies"
5085    </t>
5086    <t>
5087      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/94"/>:
5088      "Reason-Phrase BNF"
5089    </t>
5090    <t>
5091      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/111"/>:
5092      "Use of TEXT"
5093    </t>
5094    <t>
5095      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/118"/>:
5096      "Join "Differences Between HTTP Entities and RFC 2045 Entities"?"
5097    </t>
5098    <t>
5099      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/134"/>:
5100      "RFC822 reference left in discussion of date formats"
5101    </t>
5102  </list>
5103</t>
5104<t>
5105  Final work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
5106  <list style="symbols"> 
5107    <t>
5108      Rewrite definition of list rules, deprecate empty list elements.
5109    </t>
5110    <t>
5111      Add appendix containing collected and expanded ABNF.
5112    </t>
5113  </list>
5114</t>
5115<t>
5116  Other changes:
5117  <list style="symbols"> 
5118    <t>
5119      Rewrite introduction; add mostly new Architecture Section.
5120    </t>
5121    <t>
5122      Move definition of quality values from Part 3 into Part 1;
5123      make TE request header grammar independent of accept-params (defined in Part 3).
5124    </t>
5125  </list>
5126</t>
5127</section>
5128
5129<section title="Since draft-ietf-httpbis-p1-messaging-06" anchor="changes.since.06">
5130<t>
5131  Closed issues:
5132  <list style="symbols"> 
5133    <t>
5134      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/161"/>:
5135      "base for numeric protocol elements"
5136    </t>
5137    <t>
5138      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/162"/>:
5139      "comment ABNF"
5140    </t>
5141  </list>
5142</t>
5143<t>
5144  Partly resolved issues:
5145  <list style="symbols"> 
5146    <t>
5147      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/88"/>:
5148      "205 Bodies" (took out language that implied that there may be
5149      methods for which a request body MUST NOT be included)
5150    </t>
5151    <t>
5152      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/163"/>:
5153      "editorial improvements around HTTP-date"
5154    </t>
5155  </list>
5156</t>
5157</section>
5158
5159<section title="Since draft-ietf-httpbis-p1-messaging-07" anchor="changes.since.07">
5160<t>
5161  Closed issues:
5162  <list style="symbols"> 
5163    <t>
5164      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/93"/>:
5165      "Repeating single-value headers"
5166    </t>
5167    <t>
5168      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/157"/>:
5169      "IP addresses in URLs"
5170    </t>
5171    <t>
5172      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/188"/>:
5173      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
5174    </t>
5175    <t>
5176      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/189"/>:
5177      "move definitions of gzip/deflate/compress to part 1"
5178    </t>
5179  </list>
5180</t>
5181<t>
5182  Partly resolved issues:
5183  <list style="symbols"> 
5184    <t>
5185      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/148"/>:
5186      "update IANA requirements wrt Transfer-Coding values" (add the
5187      IANA Considerations subsection)
5188    </t>
5189  </list>
5190</t>
5191
5192</section>
5193
5194</section>
5195
5196</back>
5197</rfc>
Note: See TracBrowser for help on using the repository browser.