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

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

lowercase 'request' in 'effective request URI'

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