You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@labs.apache.org by fi...@apache.org on 2007/10/10 01:56:03 UTC

svn commit: r583326 [2/14] - /labs/webarch/trunk/http/draft-fielding-http/

Modified: labs/webarch/trunk/http/draft-fielding-http/p1-messaging.html
URL: http://svn.apache.org/viewvc/labs/webarch/trunk/http/draft-fielding-http/p1-messaging.html?rev=583326&r1=583325&r2=583326&view=diff
==============================================================================
--- labs/webarch/trunk/http/draft-fielding-http/p1-messaging.html (original)
+++ labs/webarch/trunk/http/draft-fielding-http/p1-messaging.html Tue Oct  9 16:56:02 2007
@@ -1,6 +1,9 @@
 <!DOCTYPE html
   PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en"><head profile="http://www.w3.org/2006/03/hcard"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>HTTP/1.1 part 1: URIs, Connections, and Message Framing</title><style type="text/css" title="Xml2Rfc (sans serif)">
+<html lang="en">
+   <head profile="http://www.w3.org/2006/03/hcard">
+      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+      <title>HTTP/1.1 part 1: URIs, Connections, and Message Framing</title><style type="text/css" title="Xml2Rfc (sans serif)">
 a {
   text-decoration: none;
 }
@@ -324,20 +327,539 @@
       content: normal;
     }
 }
-</style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Copyright" href="#rfc.copyright"><link rel="Index" href="#rfc.index"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 Notational Conventions and Generic Grammar" href="#rfc.section.2"><link rel="Chapter" title="3 Protocol Parameters" href="#rfc.section.3"><link rel="Chapter" title="4 HTTP Message" href="#rfc.section.4"><link rel="Chapter" title="5 Connections" href="#rfc.section.5"><link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6"><link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7"><link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8"><link rel="Chapter" href="#rfc.section.9" title="9 References"><link rel="Appendix" title="A Internet Media Type message/http and application/http" href="#rfc.section.A"><link rel="Appendix" title="B Tolerant Applications" href="#rfc.section.B
 "><link rel="Appendix" title="C Conversion of Date Formats" href="#rfc.section.C"><link rel="Appendix" title="D Compatibility with Previous Versions" href="#rfc.section.D"><meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.346, 2007/10/07 13:54:24, XSLT vendor: SAXON 8.5.1 from Saxonica http://www.saxonica.com/"><link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"><meta name="DC.Creator" content="Fielding, R."><meta name="DC.Creator" content="Gettys, J."><meta name="DC.Creator" content="Mogul, J."><meta name="DC.Creator" content="Frystyk, H."><meta name="DC.Creator" content="Masinter, L."><meta name="DC.Creator" content="Leach, P."><meta name="DC.Creator" content="Berners-Lee, T."><meta name="DC.Identifier" content="urn:ietf:id:draft-fielding-http-p1-messaging-00"><meta name="DC.Date.Issued" scheme="ISO8601" content="2007-09"><meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068"><meta name="DC.Relation.Replaces" content
 ="urn:ietf:rfc:2616"><meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2617"><meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the eight-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, updates RFC 2616 and RFC 2617. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."></head><body><table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"><tr><td class="header left">Network Working Group</td><td c
 lass="header right">R. Fielding</td></tr><tr><td class="header left">Internet Draft</td><td class="header right">UC Irvine</td></tr><tr><td class="header left">
-        &lt;draft-fielding-http-p1-messaging-00&gt;
-      </td><td class="header right">J. Gettys</td></tr><tr><td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>,
-      <a href="http://tools.ietf.org/html/rfc2616">2616</a>,
-      <a href="http://tools.ietf.org/html/rfc2617">2617</a> (if approved)</td><td class="header right">Compaq/W3C</td></tr><tr><td class="header left">Intended status: Standards Track</td><td class="header right">J. Mogul</td></tr><tr><td class="header left">Expires: March 2008</td><td class="header right">Compaq</td></tr><tr><td class="header left"></td><td class="header right">H. Frystyk</td></tr><tr><td class="header left"></td><td class="header right">W3C/MIT</td></tr><tr><td class="header left"></td><td class="header right">L. Masinter</td></tr><tr><td class="header left"></td><td class="header right">Xerox</td></tr><tr><td class="header left"></td><td class="header right">P. Leach</td></tr><tr><td class="header left"></td><td class="header right">Microsoft</td></tr><tr><td class="header left"></td><td class="header right">T. Berners-Lee</td></tr><tr><td class="header left"></td><td class="header right">W3C/MIT</td></tr><tr><td class="header left"></td><td class="header
  right">September 2007</td></tr></table><p class="title">HTTP/1.1 part 1: URIs, Connections, and Message Framing<br><span class="filename">draft-fielding-http-p1-messaging-00</span></p><h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1><p>This document is an Internet-Draft and is subject to all provisions of section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she become aware will be disclosed, in accordance with RFC 3668.</p><p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.</p><p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use
  Internet-Drafts as reference material or to cite them other than as &#8220;work in progress&#8221;.</p><p>The list of current Internet-Drafts can be accessed at &lt;<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>&gt;.</p><p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.</p><p>This Internet-Draft will expire in March 2008.</p><h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1><p>Copyright © The IETF Trust (2007). All Rights Reserved.</p><h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the eight-part specification that defines
  the protocol referred to as "HTTP/1.1" and, taken together, updates RFC 2616 and RFC 2617. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.</p> <hr class="noprint"><h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1><ul class="toc"><li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc"><li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.purpose">Purpose</a></li><li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li><li class="tocline1">1.3&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li><li class="tocline1">1.4&nbsp;&nbsp;&nbsp;<a href="#intro.overall.operation">Overall Operation</a></li></ul></li><li class="tocline0
 ">2.&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a><ul class="toc"><li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#notation.abnf">Augmented BNF</a></li><li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#basic.rules">Basic Rules</a></li></ul></li><li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul class="toc"><li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#http.version">HTTP Version</a></li><li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#uri">Uniform Resource Identifiers</a><ul class="toc"><li class="tocline1">3.2.1&nbsp;&nbsp;&nbsp;<a href="#general.syntax">General Syntax</a></li><li class="tocline1">3.2.2&nbsp;&nbsp;&nbsp;<a href="#http.url">http URL</a></li><li class="tocline1">3.2.3&nbsp;&nbsp;&nbsp;<a href="#uri.comparison">URI Comparison</a></li></ul></li><li class="tocline1">3.3&nbsp;&nbsp;&nbsp;<a href="#date.time.formats">Date/Time Formats</a><ul class="toc"><li class="to
 cline1">3.3.1&nbsp;&nbsp;&nbsp;<a href="#full.date">Full Date</a></li></ul></li><li class="tocline1">3.4&nbsp;&nbsp;&nbsp;<a href="#transfer.codings">Transfer Codings</a><ul class="toc"><li class="tocline1">3.4.1&nbsp;&nbsp;&nbsp;<a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li></ul></li></ul></li><li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#httpmessage">HTTP Message</a><ul class="toc"><li class="tocline1">4.1&nbsp;&nbsp;&nbsp;<a href="#message.types">Message Types</a></li><li class="tocline1">4.2&nbsp;&nbsp;&nbsp;<a href="#message.headers">Message Headers</a></li><li class="tocline1">4.3&nbsp;&nbsp;&nbsp;<a href="#message.body">Message Body</a></li><li class="tocline1">4.4&nbsp;&nbsp;&nbsp;<a href="#message.length">Message Length</a></li><li class="tocline1">4.5&nbsp;&nbsp;&nbsp;<a href="#general.header.fields">General Header Fields</a></li></ul></li><li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#connections">Connections</a><ul class="toc"><li 
 class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#persistent.connections">Persistent Connections</a><ul class="toc"><li class="tocline1">5.1.1&nbsp;&nbsp;&nbsp;<a href="#persistent.purpose">Purpose</a></li><li class="tocline1">5.1.2&nbsp;&nbsp;&nbsp;<a href="#persistent.overall">Overall Operation</a><ul class="toc"><li class="tocline1">5.1.2.1&nbsp;&nbsp;&nbsp;<a href="#persistent.negotiation">Negotiation</a></li><li class="tocline1">5.1.2.2&nbsp;&nbsp;&nbsp;<a href="#pipelining">Pipelining</a></li></ul></li><li class="tocline1">5.1.3&nbsp;&nbsp;&nbsp;<a href="#persistent.proxy">Proxy Servers</a></li><li class="tocline1">5.1.4&nbsp;&nbsp;&nbsp;<a href="#persistent.practical">Practical Considerations</a></li></ul></li><li class="tocline1">5.2&nbsp;&nbsp;&nbsp;<a href="#message.transmission.requirements">Message Transmission Requirements</a><ul class="toc"><li class="tocline1">5.2.1&nbsp;&nbsp;&nbsp;<a href="#persistent.flow">Persistent Connections and Flow Control</a></li><li c
 lass="tocline1">5.2.2&nbsp;&nbsp;&nbsp;<a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li><li class="tocline1">5.2.3&nbsp;&nbsp;&nbsp;<a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li><li class="tocline1">5.2.4&nbsp;&nbsp;&nbsp;<a href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li></ul></li></ul></li><li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc"><li class="tocline1">6.1&nbsp;&nbsp;&nbsp;<a href="#header.connection">Connection</a></li><li class="tocline1">6.2&nbsp;&nbsp;&nbsp;<a href="#header.content-length">Content-Length</a></li><li class="tocline1">6.3&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a><ul class="toc"><li class="tocline1">6.3.1&nbsp;&nbsp;&nbsp;<a href="#clockless.origin.server.operation">Clockless Origin Server Operation</a></li></ul></li><li class="tocline1">6.4&nbsp;&nbsp;&nbsp;<a href="#heade
 r.te">TE</a></li><li class="tocline1">6.5&nbsp;&nbsp;&nbsp;<a href="#header.trailer">Trailer</a></li><li class="tocline1">6.6&nbsp;&nbsp;&nbsp;<a href="#header.transfer-encoding">Transfer-Encoding</a></li><li class="tocline1">6.7&nbsp;&nbsp;&nbsp;<a href="#header.upgrade">Upgrade</a></li><li class="tocline1">6.8&nbsp;&nbsp;&nbsp;<a href="#header.via">Via</a></li></ul></li><li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul class="toc"><li class="tocline1">7.1&nbsp;&nbsp;&nbsp;<a href="#personal.information">Personal Information</a></li><li class="tocline1">7.2&nbsp;&nbsp;&nbsp;<a href="#abuse.of.server.log.information">Abuse of Server Log Information</a></li><li class="tocline1">7.3&nbsp;&nbsp;&nbsp;<a href="#attack.pathname">Attacks Based On File and Path Names</a></li><li class="tocline1">7.4&nbsp;&nbsp;&nbsp;<a href="#dns.spoofing">DNS Spoofing</a></li><li class="tocline1">7.5&nbsp;&nbsp;&nbsp;<a href="#attack.proxies
 ">Proxies and Caching</a></li><li class="tocline1">7.6&nbsp;&nbsp;&nbsp;<a href="#attack.DoS">Denial of Service Attacks on Proxies</a></li></ul></li><li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li><li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li><li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li><li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.http">Internet Media Type message/http and application/http</a></li><li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#tolerant.applications">Tolerant Applications</a></li><li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li><li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"><li class="tocline1">D.1&nbsp;&nbsp;&nbsp;<a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with H
 TTP/1.0 Persistent Connections</a></li><li class="tocline1">D.2&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li></ul></li><li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li><li class="tocline0"><a href="#rfc.index">Index</a></li></ul><h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1><p id="rfc.section.1.p.1">This document will define aspects of HTTP related to overall network operation, message framing, interaction with transport protocols, and URI schemes. Right now it only includes the extracted relevant sections of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[30]</cite></a> and <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[31]</cite></a>.</p><h2 id="rfc.section.1.1"><a href="#rfc.section.1.1"
 >1.1</a>&nbsp;<a id="intro.purpose" href="#intro.purpose">Purpose</a></h2><p id="rfc.section.1.1.p.1">The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World-Wide Web global information initiative since 1990. The first version of HTTP, referred to as HTTP/0.9, was a simple protocol for raw data transfer across the Internet. HTTP/1.0, as defined by RFC 1945 <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[4]</cite></a>, improved the protocol by allowing messages to be in the format of MIME-like messages, containing metainformation about the data transferred and modifiers on the request/response semantics. However, HTTP/1.0 does not sufficiently take into consideration the effects of hierarchical proxies, caching, the need for persistent connections, or virtual hosts. In addition, the proliferation of incompletely-im
 plemented applications calling themselves "HTTP/1.0" has necessitated a protocol version change in order for two communicating applications to determine each other's true capabilities.</p><p id="rfc.section.1.1.p.2">This specification defines the protocol referred to as "HTTP/1.1". This protocol includes more stringent requirements than HTTP/1.0 in order to ensure reliable implementation of its features.</p><p id="rfc.section.1.1.p.3">Practical information systems require more functionality than simple retrieval, including search, front-end update, and annotation. HTTP allows an open-ended set of methods and headers that indicate the purpose of a request <a href="#RFC2324" id="rfc.xref.RFC2324.1"><cite title="Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)">[32]</cite></a>. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) <a href="#RFC1630" id="rfc.xref.RFC1630.1"><cite title="Universal Resource Identifiers in WWW: A Unifying Syn
 tax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web">[2]</cite></a>, as a location (URL) <a href="#RFC1738" id="rfc.xref.RFC1738.1"><cite title="Uniform Resource Locators (URL)">[3]</cite></a> or name (URN) <a href="#RFC1737" id="rfc.xref.RFC1737.1"><cite title="Functional Requirements for Uniform Resource Names">[17]</cite></a>, for indicating the resource to which a method is to be applied. Messages are passed in a format similar to that used by Internet mail <a href="#RFC822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[7]</cite></a> as defined by the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[5]</cite></a>.</p><p id="rfc.section.1.1.p.4">HTTP is also used as a generic protocol for communication between user agents and proxies/ga
 teways to other Internet systems, including those supported by the SMTP <a href="#RFC821" id="rfc.xref.RFC821.1"><cite title="Simple Mail Transfer Protocol">[13]</cite></a>, NNTP <a href="#RFC977" id="rfc.xref.RFC977.1"><cite title="Network News Transfer Protocol">[11]</cite></a>, FTP <a href="#RFC959" id="rfc.xref.RFC959.1"><cite title="File Transfer Protocol">[15]</cite></a>, Gopher <a href="#RFC1436" id="rfc.xref.RFC1436.1"><cite title="The Internet Gopher Protocol (a distributed document search and retrieval protocol)">[1]</cite></a>, and WAIS <a href="#WAIS" id="rfc.xref.WAIS.1"><cite title="WAIS Interface Protocol Prototype Functional Specification (v1.5)">[8]</cite></a> protocols. In this way, HTTP allows basic hypermedia access to resources available from diverse applications.</p><h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2><p id="rfc.section.1.2.p.1">The key words "MUST", 
 "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[26]</cite></a>.</p><p id="rfc.section.1.2.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."</p><h2 id="rfc.section.1.3"><a hre
 f="#rfc.section.1.3">1.3</a>&nbsp;<a id="intro.terminology" href="#intro.terminology">Terminology</a></h2><p id="rfc.section.1.3.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p><p id="rfc.section.1.3.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>connection</dfn>  </p><dl class="empty"><dd>A transport layer virtual circuit established between two programs for the purpose of communication.</dd></dl><p id="rfc.section.1.3.p.3"> <span id="rfc.iref.m.1"></span>  <dfn>message</dfn>  </p><dl class="empty"><dd>The basic unit of HTTP communication, consisting of a structured sequence of octets matching the syntax defined in <a href="#httpmessage" title="HTTP Message">Section&nbsp;4</a> and transmitted via the connection.</dd></dl><p id="rfc.section.1.3.p.4"> <span id="rfc.iref.r.1"></span>  <dfn>request</dfn>  </p><dl class="empty"><dd>An HTTP request message, as defined in [Part 2].</dd></dl><p 
 id="rfc.section.1.3.p.5"> <span id="rfc.iref.r.2"></span>  <dfn>response</dfn>  </p><dl class="empty"><dd>An HTTP response message, as defined in [Part 2].</dd></dl><p id="rfc.section.1.3.p.6"> <span id="rfc.iref.r.3"></span>  <dfn>resource</dfn>  </p><dl class="empty"><dd>A network data object or service that can be identified by a URI, as defined in <a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;3.2</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or vary in other ways.</dd></dl><p id="rfc.section.1.3.p.7"> <span id="rfc.iref.e.1"></span>  <dfn>entity</dfn>  </p><dl class="empty"><dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of entity-header fields and content in the form of an entity-body, as described in [Part 3].</dd></dl><p id="rfc.section.1.3.p.8"> <span id="rfc.iref.r.4"></span>  <dfn>representation</
 dfn>  </p><dl class="empty"><dd>An entity included with a response that is subject to content negotiation, as described in [Part 3]. There may exist multiple representations associated with a particular response status.</dd></dl><p id="rfc.section.1.3.p.9"> <span id="rfc.iref.c.2"></span>  <dfn>content negotiation</dfn>  </p><dl class="empty"><dd>The mechanism for selecting the appropriate representation when servicing a request, as described in [Part 3]. The representation of entities in any response can be negotiated (including error responses).</dd></dl><p id="rfc.section.1.3.p.10"> <span id="rfc.iref.v.1"></span>  <dfn>variant</dfn>  </p><dl class="empty"><dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations is termed a `varriant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.</dd></dl><p id="rfc.section.1.3.p.11"> <span id="rfc.ir
 ef.c.3"></span>  <dfn>client</dfn>  </p><dl class="empty"><dd>A program that establishes connections for the purpose of sending requests.</dd></dl><p id="rfc.section.1.3.p.12"> <span id="rfc.iref.u.1"></span>  <dfn>user agent</dfn>  </p><dl class="empty"><dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user tools.</dd></dl><p id="rfc.section.1.3.p.13"> <span id="rfc.iref.s.1"></span>  <dfn>server</dfn>  </p><dl class="empty"><dd>An application program that accepts connections in order to service requests by sending back responses. Any given program may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.</dd></dl><p id
 ="rfc.section.1.3.p.14"> <span id="rfc.iref.o.1"></span>  <dfn>origin server</dfn>  </p><dl class="empty"><dd>The server on which a given resource resides or is to be created.</dd></dl><p id="rfc.section.1.3.p.15"> <span id="rfc.iref.p.1"></span>  <dfn>proxy</dfn>  </p><dl class="empty"><dd>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients. Requests are serviced internally or by passing them on, with possible translation, to other servers. A proxy <em class="bcp14">MUST</em> implement both the client and server requirements of this specification. A "transparent proxy" is a proxy that does not modify the request or response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is a proxy that modifies the request or response in order to provide some added service to the user agent, such as group annotation services, media type transformation, protocol reductio
 n, or anonymity filtering. Except where either transparent or non-transparent behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies.</dd></dl><p id="rfc.section.1.3.p.16"> <span id="rfc.iref.g.1"></span>  <dfn>gateway</dfn>  </p><dl class="empty"><dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway.</dd></dl><p id="rfc.section.1.3.p.17"> <span id="rfc.iref.t.1"></span>  <dfn>tunnel</dfn>  </p><dl class="empty"><dd>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered a party to the HTTP communication, though the tunnel may have been initiated by an HTTP request. The tunnel ceases to exist when both ends of the relayed connections are closed.</dd></dl><p id="rfc.section.1.3.p.18"> 
 <span id="rfc.iref.c.4"></span>  <dfn>cache</dfn>  </p><dl class="empty"><dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion. A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.</dd></dl><p id="rfc.section.1.3.p.19"> <span id="rfc.iref.c.5"></span>  <dfn>cacheable</dfn>  </p><dl class="empty"><dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. The rules for determining the cacheability of HTTP responses are defined in [Part 6]. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular request.</dd></dl><p id="rfc.section.1.3.p.20"> <span id="rfc.iref.u.2"></sp
 an>  <span id="rfc.iref.d.1"></span>  <dfn>upstream</dfn>/<dfn>downstream</dfn>  </p><dl class="empty"><dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd></dl><p id="rfc.section.1.3.p.21"> <span id="rfc.iref.i.1"></span>  <span id="rfc.iref.o.2"></span>  <dfn>inbound</dfn>/<dfn>outbound</dfn>  </p><dl class="empty"><dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server", and "outbound" means "traveling toward the user agent"</dd></dl><h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a id="intro.overall.operation" href="#intro.overall.operation">Overall Operation</a></h2><p id="rfc.section.1.4.p.1">The HTTP protocol is a request/response protocol. A client sends a request to the server in the form of a request method, URI, and protocol version, followed by a MIME-like message containing request modifiers, client information, a
 nd possible body content over a connection with a server. The server responds with a status line, including the message's protocol version and a success or error code, followed by a MIME-like message containing server information, entity metainformation, and possible entity-body content. The relationship between HTTP and MIME is described in [Part 3].</p><p id="rfc.section.1.4.p.2">Most HTTP communication is initiated by a user agent and consists of a request to be applied to a resource on some origin server. In the simplest case, this may be accomplished via a single connection (v) between the user agent (UA) and the origin server (O).</p><div id="rfc.figure.u.1"></div><pre class="drawing">       request chain ------------------------&gt;
+</style><link rel="Contents" href="#rfc.toc">
+      <link rel="Author" href="#rfc.authors">
+      <link rel="Copyright" href="#rfc.copyright">
+      <link rel="Index" href="#rfc.index">
+      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
+      <link rel="Chapter" title="2 Notational Conventions and Generic Grammar" href="#rfc.section.2">
+      <link rel="Chapter" title="3 Protocol Parameters" href="#rfc.section.3">
+      <link rel="Chapter" title="4 HTTP Message" href="#rfc.section.4">
+      <link rel="Chapter" title="5 Connections" href="#rfc.section.5">
+      <link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6">
+      <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7">
+      <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8">
+      <link rel="Chapter" href="#rfc.section.9" title="9 References">
+      <link rel="Appendix" title="A Internet Media Type message/http and application/http" href="#rfc.section.A">
+      <link rel="Appendix" title="B Tolerant Applications" href="#rfc.section.B">
+      <link rel="Appendix" title="C Conversion of Date Formats" href="#rfc.section.C">
+      <link rel="Appendix" title="D Compatibility with Previous Versions" href="#rfc.section.D">
+      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.346, 2007/10/07 13:54:24, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
+      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
+      <meta name="DC.Creator" content="Fielding, R.">
+      <meta name="DC.Creator" content="Gettys, J.">
+      <meta name="DC.Creator" content="Mogul, J.">
+      <meta name="DC.Creator" content="Frystyk, H.">
+      <meta name="DC.Creator" content="Masinter, L.">
+      <meta name="DC.Creator" content="Leach, P.">
+      <meta name="DC.Creator" content="Berners-Lee, T.">
+      <meta name="DC.Identifier" content="urn:ietf:id:draft-fielding-http-p1-messaging-00">
+      <meta name="DC.Date.Issued" scheme="ISO8601" content="2007-09">
+      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068">
+      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
+      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2617">
+      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the eight-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, updates RFC 2616 and RFC 2617. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
+   </head>
+   <body>
+      <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
+         <tr>
+            <td class="header left">Network Working Group</td>
+            <td class="header right">R. Fielding</td>
+         </tr>
+         <tr>
+            <td class="header left">Internet Draft</td>
+            <td class="header right">UC Irvine</td>
+         </tr>
+         <tr>
+            <td class="header left">
+               &lt;draft-fielding-http-p1-messaging-00&gt;
+               
+            </td>
+            <td class="header right">J. Gettys</td>
+         </tr>
+         <tr>
+            <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>,
+               <a href="http://tools.ietf.org/html/rfc2616">2616</a>,
+               <a href="http://tools.ietf.org/html/rfc2617">2617</a> (if approved)
+            </td>
+            <td class="header right">Compaq/W3C</td>
+         </tr>
+         <tr>
+            <td class="header left">Intended status: Standards Track</td>
+            <td class="header right">J. Mogul</td>
+         </tr>
+         <tr>
+            <td class="header left">Expires: March 2008</td>
+            <td class="header right">Compaq</td>
+         </tr>
+         <tr>
+            <td class="header left"></td>
+            <td class="header right">H. Frystyk</td>
+         </tr>
+         <tr>
+            <td class="header left"></td>
+            <td class="header right">W3C/MIT</td>
+         </tr>
+         <tr>
+            <td class="header left"></td>
+            <td class="header right">L. Masinter</td>
+         </tr>
+         <tr>
+            <td class="header left"></td>
+            <td class="header right">Xerox</td>
+         </tr>
+         <tr>
+            <td class="header left"></td>
+            <td class="header right">P. Leach</td>
+         </tr>
+         <tr>
+            <td class="header left"></td>
+            <td class="header right">Microsoft</td>
+         </tr>
+         <tr>
+            <td class="header left"></td>
+            <td class="header right">T. Berners-Lee</td>
+         </tr>
+         <tr>
+            <td class="header left"></td>
+            <td class="header right">W3C/MIT</td>
+         </tr>
+         <tr>
+            <td class="header left"></td>
+            <td class="header right">September 2007</td>
+         </tr>
+      </table>
+      <p class="title">HTTP/1.1 part 1: URIs, Connections, and Message Framing<br><span class="filename">draft-fielding-http-p1-messaging-00</span></p>
+      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
+      <p>This document is an Internet-Draft and is subject to all provisions of section 3 of RFC 3667. By submitting this Internet-Draft,
+         each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed,
+         and any of which he or she become aware will be disclosed, in accordance with RFC 3668.
+      </p>
+      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
+         that other groups may also distribute working documents as Internet-Drafts.
+      </p>
+      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
+         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
+         in progress”.
+      </p>
+      <p>The list of current Internet-Drafts can be accessed at &lt;<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>&gt;.
+      </p>
+      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
+      </p>
+      <p>This Internet-Draft will expire in March 2008.</p>
+      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
+      <p>Copyright © The IETF Trust (2007). All Rights Reserved.</p>
+      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
+      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
+         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the
+         eight-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, updates RFC 2616 and RFC
+         2617. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource
+         Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes
+         general security concerns for implementations.
+      </p> 
+      <hr class="noprint">
+      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
+      <ul class="toc">
+         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
+               <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.purpose">Purpose</a></li>
+               <li class="tocline1">1.2&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
+               <li class="tocline1">1.3&nbsp;&nbsp;&nbsp;<a href="#intro.terminology">Terminology</a></li>
+               <li class="tocline1">1.4&nbsp;&nbsp;&nbsp;<a href="#intro.overall.operation">Overall Operation</a></li>
+            </ul>
+         </li>
+         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a><ul class="toc">
+               <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#notation.abnf">Augmented BNF</a></li>
+               <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#basic.rules">Basic Rules</a></li>
+            </ul>
+         </li>
+         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#protocol.parameters">Protocol Parameters</a><ul class="toc">
+               <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#http.version">HTTP Version</a></li>
+               <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#uri">Uniform Resource Identifiers</a><ul class="toc">
+                     <li class="tocline1">3.2.1&nbsp;&nbsp;&nbsp;<a href="#general.syntax">General Syntax</a></li>
+                     <li class="tocline1">3.2.2&nbsp;&nbsp;&nbsp;<a href="#http.url">http URL</a></li>
+                     <li class="tocline1">3.2.3&nbsp;&nbsp;&nbsp;<a href="#uri.comparison">URI Comparison</a></li>
+                  </ul>
+               </li>
+               <li class="tocline1">3.3&nbsp;&nbsp;&nbsp;<a href="#date.time.formats">Date/Time Formats</a><ul class="toc">
+                     <li class="tocline1">3.3.1&nbsp;&nbsp;&nbsp;<a href="#full.date">Full Date</a></li>
+                  </ul>
+               </li>
+               <li class="tocline1">3.4&nbsp;&nbsp;&nbsp;<a href="#transfer.codings">Transfer Codings</a><ul class="toc">
+                     <li class="tocline1">3.4.1&nbsp;&nbsp;&nbsp;<a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li>
+                  </ul>
+               </li>
+            </ul>
+         </li>
+         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#httpmessage">HTTP Message</a><ul class="toc">
+               <li class="tocline1">4.1&nbsp;&nbsp;&nbsp;<a href="#message.types">Message Types</a></li>
+               <li class="tocline1">4.2&nbsp;&nbsp;&nbsp;<a href="#message.headers">Message Headers</a></li>
+               <li class="tocline1">4.3&nbsp;&nbsp;&nbsp;<a href="#message.body">Message Body</a></li>
+               <li class="tocline1">4.4&nbsp;&nbsp;&nbsp;<a href="#message.length">Message Length</a></li>
+               <li class="tocline1">4.5&nbsp;&nbsp;&nbsp;<a href="#general.header.fields">General Header Fields</a></li>
+            </ul>
+         </li>
+         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#connections">Connections</a><ul class="toc">
+               <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#persistent.connections">Persistent Connections</a><ul class="toc">
+                     <li class="tocline1">5.1.1&nbsp;&nbsp;&nbsp;<a href="#persistent.purpose">Purpose</a></li>
+                     <li class="tocline1">5.1.2&nbsp;&nbsp;&nbsp;<a href="#persistent.overall">Overall Operation</a><ul class="toc">
+                           <li class="tocline1">5.1.2.1&nbsp;&nbsp;&nbsp;<a href="#persistent.negotiation">Negotiation</a></li>
+                           <li class="tocline1">5.1.2.2&nbsp;&nbsp;&nbsp;<a href="#pipelining">Pipelining</a></li>
+                        </ul>
+                     </li>
+                     <li class="tocline1">5.1.3&nbsp;&nbsp;&nbsp;<a href="#persistent.proxy">Proxy Servers</a></li>
+                     <li class="tocline1">5.1.4&nbsp;&nbsp;&nbsp;<a href="#persistent.practical">Practical Considerations</a></li>
+                  </ul>
+               </li>
+               <li class="tocline1">5.2&nbsp;&nbsp;&nbsp;<a href="#message.transmission.requirements">Message Transmission Requirements</a><ul class="toc">
+                     <li class="tocline1">5.2.1&nbsp;&nbsp;&nbsp;<a href="#persistent.flow">Persistent Connections and Flow Control</a></li>
+                     <li class="tocline1">5.2.2&nbsp;&nbsp;&nbsp;<a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li>
+                     <li class="tocline1">5.2.3&nbsp;&nbsp;&nbsp;<a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>
+                     <li class="tocline1">5.2.4&nbsp;&nbsp;&nbsp;<a href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li>
+                  </ul>
+               </li>
+            </ul>
+         </li>
+         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
+               <li class="tocline1">6.1&nbsp;&nbsp;&nbsp;<a href="#header.connection">Connection</a></li>
+               <li class="tocline1">6.2&nbsp;&nbsp;&nbsp;<a href="#header.content-length">Content-Length</a></li>
+               <li class="tocline1">6.3&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a><ul class="toc">
+                     <li class="tocline1">6.3.1&nbsp;&nbsp;&nbsp;<a href="#clockless.origin.server.operation">Clockless Origin Server Operation</a></li>
+                  </ul>
+               </li>
+               <li class="tocline1">6.4&nbsp;&nbsp;&nbsp;<a href="#header.te">TE</a></li>
+               <li class="tocline1">6.5&nbsp;&nbsp;&nbsp;<a href="#header.trailer">Trailer</a></li>
+               <li class="tocline1">6.6&nbsp;&nbsp;&nbsp;<a href="#header.transfer-encoding">Transfer-Encoding</a></li>
+               <li class="tocline1">6.7&nbsp;&nbsp;&nbsp;<a href="#header.upgrade">Upgrade</a></li>
+               <li class="tocline1">6.8&nbsp;&nbsp;&nbsp;<a href="#header.via">Via</a></li>
+            </ul>
+         </li>
+         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul class="toc">
+               <li class="tocline1">7.1&nbsp;&nbsp;&nbsp;<a href="#personal.information">Personal Information</a></li>
+               <li class="tocline1">7.2&nbsp;&nbsp;&nbsp;<a href="#abuse.of.server.log.information">Abuse of Server Log Information</a></li>
+               <li class="tocline1">7.3&nbsp;&nbsp;&nbsp;<a href="#attack.pathname">Attacks Based On File and Path Names</a></li>
+               <li class="tocline1">7.4&nbsp;&nbsp;&nbsp;<a href="#dns.spoofing">DNS Spoofing</a></li>
+               <li class="tocline1">7.5&nbsp;&nbsp;&nbsp;<a href="#attack.proxies">Proxies and Caching</a></li>
+               <li class="tocline1">7.6&nbsp;&nbsp;&nbsp;<a href="#attack.DoS">Denial of Service Attacks on Proxies</a></li>
+            </ul>
+         </li>
+         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
+         <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
+         <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
+         <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#internet.media.type.http">Internet Media Type message/http and application/http</a></li>
+         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#tolerant.applications">Tolerant Applications</a></li>
+         <li class="tocline0">C.&nbsp;&nbsp;&nbsp;<a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>
+         <li class="tocline0">D.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">
+               <li class="tocline1">D.1&nbsp;&nbsp;&nbsp;<a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li>
+               <li class="tocline1">D.2&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>
+            </ul>
+         </li>
+         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
+         <li class="tocline0"><a href="#rfc.index">Index</a></li>
+      </ul>
+      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
+      <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to overall network operation, message framing, interaction with transport
+         protocols, and URI schemes. Right now it only includes the extracted relevant sections of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[30]</cite></a> and <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[31]</cite></a>.
+      </p>
+      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.purpose" href="#intro.purpose">Purpose</a></h2>
+      <p id="rfc.section.1.1.p.1">The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
+         systems. HTTP has been in use by the World-Wide Web global information initiative since 1990. The first version of HTTP, referred
+         to as HTTP/0.9, was a simple protocol for raw data transfer across the Internet. HTTP/1.0, as defined by RFC 1945 <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[4]</cite></a>, improved the protocol by allowing messages to be in the format of MIME-like messages, containing metainformation about the
+         data transferred and modifiers on the request/response semantics. However, HTTP/1.0 does not sufficiently take into consideration
+         the effects of hierarchical proxies, caching, the need for persistent connections, or virtual hosts. In addition, the proliferation
+         of incompletely-implemented applications calling themselves "HTTP/1.0" has necessitated a protocol version change in order
+         for two communicating applications to determine each other's true capabilities.
+      </p>
+      <p id="rfc.section.1.1.p.2">This specification defines the protocol referred to as "HTTP/1.1". This protocol includes more stringent requirements than
+         HTTP/1.0 in order to ensure reliable implementation of its features.
+      </p>
+      <p id="rfc.section.1.1.p.3">Practical information systems require more functionality than simple retrieval, including search, front-end update, and annotation.
+         HTTP allows an open-ended set of methods and headers that indicate the purpose of a request <a href="#RFC2324" id="rfc.xref.RFC2324.1"><cite title="Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)">[32]</cite></a>. It builds on the discipline of reference provided by the Uniform Resource Identifier (URI) <a href="#RFC1630" id="rfc.xref.RFC1630.1"><cite title="Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web">[2]</cite></a>, as a location (URL) <a href="#RFC1738" id="rfc.xref.RFC1738.1"><cite title="Uniform Resource Locators (URL)">[3]</cite></a> or name (URN) <a href="#RFC1737" id="rfc.xref.RFC1737.1"><cite title="Functional Requirements for Uniform Resource Names">[17]</cite></a>, for indicating the resource to which a method is to be applied. Messages are passed in a format similar to that used by
+         Internet mail <a href="#RFC822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[7]</cite></a> as defined by the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[5]</cite></a>.
+      </p>
+      <p id="rfc.section.1.1.p.4">HTTP is also used as a generic protocol for communication between user agents and proxies/gateways to other Internet systems,
+         including those supported by the SMTP <a href="#RFC821" id="rfc.xref.RFC821.1"><cite title="Simple Mail Transfer Protocol">[13]</cite></a>, NNTP <a href="#RFC977" id="rfc.xref.RFC977.1"><cite title="Network News Transfer Protocol">[11]</cite></a>, FTP <a href="#RFC959" id="rfc.xref.RFC959.1"><cite title="File Transfer Protocol">[15]</cite></a>, Gopher <a href="#RFC1436" id="rfc.xref.RFC1436.1"><cite title="The Internet Gopher Protocol (a distributed document search and retrieval protocol)">[1]</cite></a>, and WAIS <a href="#WAIS" id="rfc.xref.WAIS.1"><cite title="WAIS Interface Protocol Prototype Functional Specification (v1.5)">[8]</cite></a> protocols. In this way, HTTP allows basic hypermedia access to resources available from diverse applications.
+      </p>
+      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
+      <p id="rfc.section.1.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
+         in this document are to be interpreted as described in RFC 2119 <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[26]</cite></a>.
+      </p>
+      <p id="rfc.section.1.2.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
+      </p>
+      <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="intro.terminology" href="#intro.terminology">Terminology</a></h2>
+      <p id="rfc.section.1.3.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
+      <p id="rfc.section.1.3.p.2"> <span id="rfc.iref.c.1"></span>  <dfn>connection</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>A transport layer virtual circuit established between two programs for the purpose of communication.</dd>
+      </dl>
+      <p id="rfc.section.1.3.p.3"> <span id="rfc.iref.m.1"></span>  <dfn>message</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>The basic unit of HTTP communication, consisting of a structured sequence of octets matching the syntax defined in <a href="#httpmessage" title="HTTP Message">Section&nbsp;4</a> and transmitted via the connection.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.4"> <span id="rfc.iref.r.1"></span>  <dfn>request</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>An HTTP request message, as defined in [Part 2].</dd>
+      </dl>
+      <p id="rfc.section.1.3.p.5"> <span id="rfc.iref.r.2"></span>  <dfn>response</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>An HTTP response message, as defined in [Part 2].</dd>
+      </dl>
+      <p id="rfc.section.1.3.p.6"> <span id="rfc.iref.r.3"></span>  <dfn>resource</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>A network data object or service that can be identified by a URI, as defined in <a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;3.2</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or
+            vary in other ways.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.7"> <span id="rfc.iref.e.1"></span>  <dfn>entity</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of
+            entity-header fields and content in the form of an entity-body, as described in [Part 3].
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.8"> <span id="rfc.iref.r.4"></span>  <dfn>representation</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>An entity included with a response that is subject to content negotiation, as described in [Part 3]. There may exist multiple
+            representations associated with a particular response status.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.9"> <span id="rfc.iref.c.2"></span>  <dfn>content negotiation</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in [Part 3]. The representation
+            of entities in any response can be negotiated (including error responses).
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.10"> <span id="rfc.iref.v.1"></span>  <dfn>variant</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations
+            is termed a `varriant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.11"> <span id="rfc.iref.c.3"></span>  <dfn>client</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>A program that establishes connections for the purpose of sending requests.</dd>
+      </dl>
+      <p id="rfc.section.1.3.p.12"> <span id="rfc.iref.u.1"></span>  <dfn>user agent</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user
+            tools.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.13"> <span id="rfc.iref.s.1"></span>  <dfn>server</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>An application program that accepts connections in order to service requests by sending back responses. Any given program
+            may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the
+            program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as
+            an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.14"> <span id="rfc.iref.o.1"></span>  <dfn>origin server</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>The server on which a given resource resides or is to be created.</dd>
+      </dl>
+      <p id="rfc.section.1.3.p.15"> <span id="rfc.iref.p.1"></span>  <dfn>proxy</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients.
+            Requests are serviced internally or by passing them on, with possible translation, to other servers. A proxy <em class="bcp14">MUST</em> implement both the client and server requirements of this specification. A "transparent proxy" is a proxy that does not modify
+            the request or response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is
+            a proxy that modifies the request or response in order to provide some added service to the user agent, such as group annotation
+            services, media type transformation, protocol reduction, or anonymity filtering. Except where either transparent or non-transparent
+            behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.16"> <span id="rfc.iref.g.1"></span>  <dfn>gateway</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the
+            origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.17"> <span id="rfc.iref.t.1"></span>  <dfn>tunnel</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered
+            a party to the HTTP communication, though the tunnel may have been initiated by an HTTP request. The tunnel ceases to exist
+            when both ends of the relayed connections are closed.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.18"> <span id="rfc.iref.c.4"></span>  <dfn>cache</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.
+            A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent
+            requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.19"> <span id="rfc.iref.c.5"></span>  <dfn>cacheable</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
+            The rules for determining the cacheability of HTTP responses are defined in [Part 6]. Even if a resource is cacheable, there
+            may be additional constraints on whether a cache can use the cached copy for a particular request.
+         </dd>
+      </dl>
+      <p id="rfc.section.1.3.p.20"> <span id="rfc.iref.u.2"></span>  <span id="rfc.iref.d.1"></span>  <dfn>upstream</dfn>/<dfn>downstream</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd>
+      </dl>
+      <p id="rfc.section.1.3.p.21"> <span id="rfc.iref.i.1"></span>  <span id="rfc.iref.o.2"></span>  <dfn>inbound</dfn>/<dfn>outbound</dfn>  
+      </p>
+      <dl class="empty">
+         <dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server",
+            and "outbound" means "traveling toward the user agent"
+         </dd>
+      </dl>
+      <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a>&nbsp;<a id="intro.overall.operation" href="#intro.overall.operation">Overall Operation</a></h2>
+      <p id="rfc.section.1.4.p.1">The HTTP protocol is a request/response protocol. A client sends a request to the server in the form of a request method,
+         URI, and protocol version, followed by a MIME-like message containing request modifiers, client information, and possible
+         body content over a connection with a server. The server responds with a status line, including the message's protocol version
+         and a success or error code, followed by a MIME-like message containing server information, entity metainformation, and possible
+         entity-body content. The relationship between HTTP and MIME is described in [Part 3].
+      </p>
+      <p id="rfc.section.1.4.p.2">Most HTTP communication is initiated by a user agent and consists of a request to be applied to a resource on some origin
+         server. In the simplest case, this may be accomplished via a single connection (v) between the user agent (UA) and the origin
+         server (O).
+      </p>
+      <div id="rfc.figure.u.1"></div><pre class="drawing">       request chain ------------------------&gt;
     UA -------------------v------------------- O
        &lt;----------------------- response chain
-</pre><p id="rfc.section.1.4.p.4">A more complicated situation occurs when one or more intermediaries are present in the request/response chain. There are three common forms of intermediary: proxy, gateway, and tunnel. A proxy is a forwarding agent, receiving requests for a URI in its absolute form, rewriting all or part of the message, and forwarding the reformatted request toward the server identified by the URI. A gateway is a receiving agent, acting as a layer above some other server(s) and, if necessary, translating the requests to the underlying server's protocol. A tunnel acts as a relay point between two connections without changing the messages; tunnels are used when the communication needs to pass through an intermediary (such as a firewall) even when the intermediary cannot understand the contents of the messages.</p><div id="rfc.figure.u.2"></div><pre class="drawing">       request chain --------------------------------------&gt;
+</pre><p id="rfc.section.1.4.p.4">A more complicated situation occurs when one or more intermediaries are present in the request/response chain. There are three
+         common forms of intermediary: proxy, gateway, and tunnel. A proxy is a forwarding agent, receiving requests for a URI in its
+         absolute form, rewriting all or part of the message, and forwarding the reformatted request toward the server identified by
+         the URI. A gateway is a receiving agent, acting as a layer above some other server(s) and, if necessary, translating the requests
+         to the underlying server's protocol. A tunnel acts as a relay point between two connections without changing the messages;
+         tunnels are used when the communication needs to pass through an intermediary (such as a firewall) even when the intermediary
+         cannot understand the contents of the messages.
+      </p>
+      <div id="rfc.figure.u.2"></div><pre class="drawing">       request chain --------------------------------------&gt;
     UA -----v----- A -----v----- B -----v----- C -----v----- O
        &lt;------------------------------------- response chain
-</pre><p id="rfc.section.1.4.p.6">The figure above shows three intermediaries (A, B, and C) between the user agent and origin server. A request or response message that travels the whole chain will pass through four separate connections. This distinction is important because some HTTP communication options may apply only to the connection with the nearest, non-tunnel neighbor, only to the end-points of the chain, or to all connections along the chain. Although the diagram is linear, each participant may be engaged in multiple, simultaneous communications. For example, B may be receiving requests from many clients other than A, and/or forwarding requests to servers other than C, at the same time that it is handling A's request.</p><p id="rfc.section.1.4.p.7">Any party to the communication which is not acting as a tunnel may employ an internal cache for handling requests. The effect of a cache is that the request/response chain is shortened if one of the participants along the
  chain has a cached response applicable to that request. The following illustrates the resulting chain if B has a cached copy of an earlier response from O (via C) for a request which has not been cached by UA or A.</p><div id="rfc.figure.u.3"></div><pre class="drawing">          request chain ----------&gt;
+</pre><p id="rfc.section.1.4.p.6">The figure above shows three intermediaries (A, B, and C) between the user agent and origin server. A request or response
+         message that travels the whole chain will pass through four separate connections. This distinction is important because some
+         HTTP communication options may apply only to the connection with the nearest, non-tunnel neighbor, only to the end-points
+         of the chain, or to all connections along the chain. Although the diagram is linear, each participant may be engaged in multiple,
+         simultaneous communications. For example, B may be receiving requests from many clients other than A, and/or forwarding requests
+         to servers other than C, at the same time that it is handling A's request.
+      </p>
+      <p id="rfc.section.1.4.p.7">Any party to the communication which is not acting as a tunnel may employ an internal cache for handling requests. The effect
+         of a cache is that the request/response chain is shortened if one of the participants along the chain has a cached response
+         applicable to that request. The following illustrates the resulting chain if B has a cached copy of an earlier response from
+         O (via C) for a request which has not been cached by UA or A.
+      </p>
+      <div id="rfc.figure.u.3"></div><pre class="drawing">          request chain ----------&gt;
        UA -----v----- A -----v----- B - - - - - - C - - - - - - O
           &lt;--------- response chain
-</pre><p id="rfc.section.1.4.p.9">Not all responses are usefully cacheable, and some requests may contain modifiers which place special requirements on cache behavior. HTTP requirements for cache behavior and cacheable responses are defined in [Part 6].</p><p id="rfc.section.1.4.p.10">In fact, there are a wide variety of architectures and configurations of caches and proxies currently being experimented with or deployed across the World Wide Web. These systems include national hierarchies of proxy caches to save transoceanic bandwidth, systems that broadcast or multicast cache entries, organizations that distribute subsets of cached data via CD-ROM, and so on. HTTP systems are used in corporate intranets over high-bandwidth links, and for access via PDAs with low-power radio links and intermittent connectivity. The goal of HTTP/1.1 is to support the wide diversity of configurations already deployed while introducing protocol constructs that meet the needs of those who build 
 web applications that require high reliability and, failing that, at least reliable indications of failure.</p><p id="rfc.section.1.4.p.11">HTTP communication usually takes place over TCP/IP connections. The default port is TCP 80 <a href="#RFC1700" id="rfc.xref.RFC1700.1"><cite title="Assigned Numbers">[16]</cite></a>, but other ports can be used. This does not preclude HTTP from being implemented on top of any other protocol on the Internet, or on other networks. HTTP only presumes a reliable transport; any protocol that provides such guarantees can be used; the mapping of the HTTP/1.1 request and response structures onto the transport data units of the protocol in question is outside the scope of this specification.</p><p id="rfc.section.1.4.p.12">In HTTP/1.0, most implementations used a new connection for each request/response exchange. In HTTP/1.1, a connection may be used for one or more request/response exchanges, although connections may be closed for a variety of re
 asons (see <a href="#persistent.connections" title="Persistent Connections">Section&nbsp;5.1</a>).</p><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="notation.abnf" href="#notation.abnf">Augmented BNF</a></h2><p id="rfc.section.2.1.p.1">All of the mechanisms specified in this document are described in both prose and an augmented Backus-Naur Form (BNF) similar to that used by RFC 822 <a href="#RFC822" id="rfc.xref.RFC822.2"><cite title="Standard for the format of ARPA Internet text messages">[7]</cite></a>. Implementors will need to be familiar with the notation in order to understand this specification. The augmented BNF includes the following constructs:</p><p id="rfc.section.2.1.p.2">name = definition </p><dl class="empty"><dd>The name of a rule is simply the name itself (without any enclosing "&lt;" and "&
 gt;") and is separated from its definition by the equal "=" character. White space is only significant in that indentation of continuation lines is used to indicate a rule definition that spans more than one line. Certain basic rules are in uppercase, such as SP, LWS, HT, CRLF, DIGIT, ALPHA, etc. Angle brackets are used within definitions whenever their presence will facilitate discerning the use of rule names.</dd></dl><p id="rfc.section.2.1.p.3">"literal" </p><dl class="empty"><dd>Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive.</dd></dl><p id="rfc.section.2.1.p.4">rule1 | rule2 </p><dl class="empty"><dd>Elements separated by a bar ("|") are alternatives, e.g., "yes | no" will accept yes or no.</dd></dl><p id="rfc.section.2.1.p.5">(rule1 rule2) </p><dl class="empty"><dd>Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo | bar) elem)" allows the token sequences "elem foo elem" and "elem bar elem".
 </dd></dl><p id="rfc.section.2.1.p.6">*rule </p><dl class="empty"><dd>The character "*" preceding an element indicates repetition. The full form is "&lt;n&gt;*&lt;m&gt;element" indicating at least &lt;n&gt; and at most &lt;m&gt; occurrences of element. Default values are 0 and infinity so that "*(element)" allows any number, including zero; "1*element" requires at least one; and "1*2element" allows one or two.</dd></dl><p id="rfc.section.2.1.p.7">[rule] </p><dl class="empty"><dd>Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)".</dd></dl><p id="rfc.section.2.1.p.8">N rule </p><dl class="empty"><dd>Specific repetition: "&lt;n&gt;(element)" is equivalent to "&lt;n&gt;*&lt;n&gt;(element)"; that is, exactly &lt;n&gt; occurrences of (element). Thus 2DIGIT is a 2-digit number, and 3ALPHA is a string of three alphabetic characters.</dd></dl><p id="rfc.section.2.1.p.9">#rule </p><dl class="empty"><dd>A construct "#" is defined, similar to "*", for
  defining lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating at least &lt;n&gt; and at most &lt;m&gt; elements, each separated by one or more commas (",") and <em class="bcp14">OPTIONAL</em> linear white space (LWS). This makes the usual form of lists very easy; a rule such as</dd><dd>( *LWS element *( *LWS "," *LWS element ))</dd><dd>can be shown as</dd><dd>1#element</dd><dd>Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is, "(element), , (element) " is permitted, but counts as only two elements. Therefore, where at least one element is required, at least one non-null element <em class="bcp14">MUST</em> be present. Default values are 0 and infinity so that "#element" allows any number, including zero; "1#element" requires at least one; and "1#2element" allows one or two.</dd></dl><p id="rfc.section.2.1.p.10">; comment </p><dl class="empty"><dd>A semi-colon, set off some distan
 ce to the right of rule text, starts a comment that continues to the end of line. This is a simple way of including useful notes in parallel with the specifications.</dd></dl><p id="rfc.section.2.1.p.11">implied *LWS </p><dl class="empty"><dd>The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included between any two adjacent words (token or quoted-string), and between adjacent words and separators, without changing the interpretation of a field. At least one delimiter (LWS and/or separators) <em class="bcp14">MUST</em> exist between any two tokens (for the definition of "token" below), since they would otherwise be interpreted as a single token.</dd></dl><h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="basic.rules" href="#basic.rules">Basic Rules</a></h2><p id="rfc.section.2.2.p.1">The following rules are used throughout this specification to describe basic parsing constructs. The U
 S-ASCII coded character set is defined by ANSI X3.4-1986 <a href="#USASCII" id="rfc.xref.USASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[18]</cite></a>.</p><div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>    OCTET          = &lt;any 8-bit sequence of data&gt;
+</pre><p id="rfc.section.1.4.p.9">Not all responses are usefully cacheable, and some requests may contain modifiers which place special requirements on cache
+         behavior. HTTP requirements for cache behavior and cacheable responses are defined in [Part 6].
+      </p>
+      <p id="rfc.section.1.4.p.10">In fact, there are a wide variety of architectures and configurations of caches and proxies currently being experimented with
+         or deployed across the World Wide Web. These systems include national hierarchies of proxy caches to save transoceanic bandwidth,
+         systems that broadcast or multicast cache entries, organizations that distribute subsets of cached data via CD-ROM, and so
+         on. HTTP systems are used in corporate intranets over high-bandwidth links, and for access via PDAs with low-power radio links
+         and intermittent connectivity. The goal of HTTP/1.1 is to support the wide diversity of configurations already deployed while
+         introducing protocol constructs that meet the needs of those who build web applications that require high reliability and,
+         failing that, at least reliable indications of failure.
+      </p>
+      <p id="rfc.section.1.4.p.11">HTTP communication usually takes place over TCP/IP connections. The default port is TCP 80 <a href="#RFC1700" id="rfc.xref.RFC1700.1"><cite title="Assigned Numbers">[16]</cite></a>, but other ports can be used. This does not preclude HTTP from being implemented on top of any other protocol on the Internet,
+         or on other networks. HTTP only presumes a reliable transport; any protocol that provides such guarantees can be used; the
+         mapping of the HTTP/1.1 request and response structures onto the transport data units of the protocol in question is outside
+         the scope of this specification.
+      </p>
+      <p id="rfc.section.1.4.p.12">In HTTP/1.0, most implementations used a new connection for each request/response exchange. In HTTP/1.1, a connection may
+         be used for one or more request/response exchanges, although connections may be closed for a variety of reasons (see <a href="#persistent.connections" title="Persistent Connections">Section&nbsp;5.1</a>).
+      </p>
+      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1>
+      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="notation.abnf" href="#notation.abnf">Augmented BNF</a></h2>
+      <p id="rfc.section.2.1.p.1">All of the mechanisms specified in this document are described in both prose and an augmented Backus-Naur Form (BNF) similar
+         to that used by RFC 822 <a href="#RFC822" id="rfc.xref.RFC822.2"><cite title="Standard for the format of ARPA Internet text messages">[7]</cite></a>. Implementors will need to be familiar with the notation in order to understand this specification. The augmented BNF includes
+         the following constructs:
+      </p>
+      <p id="rfc.section.2.1.p.2">name = definition </p>
+      <dl class="empty">
+         <dd>The name of a rule is simply the name itself (without any enclosing "&lt;" and "&gt;") and is separated from its definition by the
+            equal "=" character. White space is only significant in that indentation of continuation lines is used to indicate a rule
+            definition that spans more than one line. Certain basic rules are in uppercase, such as SP, LWS, HT, CRLF, DIGIT, ALPHA, etc.
+            Angle brackets are used within definitions whenever their presence will facilitate discerning the use of rule names.
+         </dd>
+      </dl>
+      <p id="rfc.section.2.1.p.3">"literal" </p>
+      <dl class="empty">
+         <dd>Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive.</dd>
+      </dl>
+      <p id="rfc.section.2.1.p.4">rule1 | rule2 </p>
+      <dl class="empty">
+         <dd>Elements separated by a bar ("|") are alternatives, e.g., "yes | no" will accept yes or no.</dd>
+      </dl>
+      <p id="rfc.section.2.1.p.5">(rule1 rule2) </p>
+      <dl class="empty">
+         <dd>Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo | bar) elem)" allows the token sequences
+            "elem foo elem" and "elem bar elem".
+         </dd>
+      </dl>
+      <p id="rfc.section.2.1.p.6">*rule </p>
+      <dl class="empty">
+         <dd>The character "*" preceding an element indicates repetition. The full form is "&lt;n&gt;*&lt;m&gt;element" indicating at least &lt;n&gt; and
+            at most &lt;m&gt; occurrences of element. Default values are 0 and infinity so that "*(element)" allows any number, including zero;
+            "1*element" requires at least one; and "1*2element" allows one or two.
+         </dd>
+      </dl>
+      <p id="rfc.section.2.1.p.7">[rule] </p>
+      <dl class="empty">
+         <dd>Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)".</dd>
+      </dl>
+      <p id="rfc.section.2.1.p.8">N rule </p>
+      <dl class="empty">
+         <dd>Specific repetition: "&lt;n&gt;(element)" is equivalent to "&lt;n&gt;*&lt;n&gt;(element)"; that is, exactly &lt;n&gt; occurrences of (element). Thus
+            2DIGIT is a 2-digit number, and 3ALPHA is a string of three alphabetic characters.
+         </dd>
+      </dl>
+      <p id="rfc.section.2.1.p.9">#rule </p>
+      <dl class="empty">
+         <dd>A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "&lt;n&gt;#&lt;m&gt;element" indicating at
+            least &lt;n&gt; and at most &lt;m&gt; elements, each separated by one or more commas (",") and <em class="bcp14">OPTIONAL</em> linear white space (LWS). This makes the usual form of lists very easy; a rule such as
+         </dd>
+         <dd>( *LWS element *( *LWS "," *LWS element ))</dd>
+         <dd>can be shown as</dd>
+         <dd>1#element</dd>
+         <dd>Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is,
+            "(element), , (element) " is permitted, but counts as only two elements. Therefore, where at least one element is required,
+            at least one non-null element <em class="bcp14">MUST</em> be present. Default values are 0 and infinity so that "#element" allows any number, including zero; "1#element" requires at
+            least one; and "1#2element" allows one or two.
+         </dd>
+      </dl>
+      <p id="rfc.section.2.1.p.10">; comment </p>
+      <dl class="empty">
+         <dd>A semi-colon, set off some distance to the right of rule text, starts a comment that continues to the end of line. This is
+            a simple way of including useful notes in parallel with the specifications.
+         </dd>
+      </dl>
+      <p id="rfc.section.2.1.p.11">implied *LWS </p>
+      <dl class="empty">
+         <dd>The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included
+            between any two adjacent words (token or quoted-string), and between adjacent words and separators, without changing the interpretation
+            of a field. At least one delimiter (LWS and/or separators) <em class="bcp14">MUST</em> exist between any two tokens (for the definition of "token" below), since they would otherwise be interpreted as a single
+            token.
+         </dd>
+      </dl>
+      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="basic.rules" href="#basic.rules">Basic Rules</a></h2>
+      <p id="rfc.section.2.2.p.1">The following rules are used throughout this specification to describe basic parsing constructs. The US-ASCII coded character
+         set is defined by ANSI X3.4-1986 <a href="#USASCII" id="rfc.xref.USASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[18]</cite></a>.
+      </p>
+      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>    OCTET          = &lt;any 8-bit sequence of data&gt;
     CHAR           = &lt;any US-ASCII character (octets 0 - 127)&gt;
     UPALPHA        = &lt;any US-ASCII uppercase letter "A".."Z"&gt;
     LOALPHA        = &lt;any US-ASCII lowercase letter "a".."z"&gt;
@@ -350,31 +872,138 @@
     SP             = &lt;US-ASCII SP, space (32)&gt;
     HT             = &lt;US-ASCII HT, horizontal-tab (9)&gt;
     &lt;"&gt;            = &lt;US-ASCII double-quote mark (34)&gt;
-</pre><p id="rfc.section.2.2.p.3">HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;B</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described in [Part 3].</p><div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.13"></span>    CRLF           = CR LF
-</pre><p id="rfc.section.2.2.p.5">HTTP/1.1 header field values can be folded onto multiple lines if the continuation line begins with a space or horizontal tab. All linear white space, including folding, has the same semantics as SP. A recipient <em class="bcp14">MAY</em> replace any linear white space with a single SP before interpreting the field value or forwarding the message downstream.</p><div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.14"></span>    LWS            = [CRLF] 1*( SP | HT )
-</pre><p id="rfc.section.2.2.p.7">The TEXT rule is only used for descriptive field contents and values that are not intended to be interpreted by the message parser. Words of *TEXT <em class="bcp14">MAY</em> contain characters from character sets other than ISO-8859-1 <a href="#ISO-8859" id="rfc.xref.ISO-8859.1"><cite title="Information technology - 8-bit single byte coded graphic - character sets">[19]</cite></a> only when encoded according to the rules of RFC 2047 <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[12]</cite></a>.</p><div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.15"></span>    TEXT           = &lt;any OCTET except CTLs,
+</pre><p id="rfc.section.2.2.p.3">HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;B</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described
+         in [Part 3].
+      </p>
+      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.13"></span>    CRLF           = CR LF
+</pre><p id="rfc.section.2.2.p.5">HTTP/1.1 header field values can be folded onto multiple lines if the continuation line begins with a space or horizontal
+         tab. All linear white space, including folding, has the same semantics as SP. A recipient <em class="bcp14">MAY</em> replace any linear white space with a single SP before interpreting the field value or forwarding the message downstream.
+      </p>
+      <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.14"></span>    LWS            = [CRLF] 1*( SP | HT )
+</pre><p id="rfc.section.2.2.p.7">The TEXT rule is only used for descriptive field contents and values that are not intended to be interpreted by the message
+         parser. Words of *TEXT <em class="bcp14">MAY</em> contain characters from character sets other than ISO-8859-1 <a href="#ISO-8859" id="rfc.xref.ISO-8859.1"><cite title="Information technology - 8-bit single byte coded graphic - character sets">[19]</cite></a> only when encoded according to the rules of RFC 2047 <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[12]</cite></a>.
+      </p>
+      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.15"></span>    TEXT           = &lt;any OCTET except CTLs,
                      but including LWS&gt;
-</pre><p id="rfc.section.2.2.p.9">A CRLF is allowed in the definition of TEXT only as part of a header field continuation. It is expected that the folding LWS will be replaced with a single SP before interpretation of the TEXT value.</p><p id="rfc.section.2.2.p.10">Hexadecimal numeric characters are used in several protocol elements.</p><div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.16"></span>    HEX            = "A" | "B" | "C" | "D" | "E" | "F"
+</pre><p id="rfc.section.2.2.p.9">A CRLF is allowed in the definition of TEXT only as part of a header field continuation. It is expected that the folding LWS
+         will be replaced with a single SP before interpretation of the TEXT value.
+      </p>
+      <p id="rfc.section.2.2.p.10">Hexadecimal numeric characters are used in several protocol elements.</p>
+      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.16"></span>    HEX            = "A" | "B" | "C" | "D" | "E" | "F"
                    | "a" | "b" | "c" | "d" | "e" | "f" | DIGIT
-</pre><p id="rfc.section.2.2.p.12">Many HTTP/1.1 header field values consist of words separated by LWS or special characters. These special characters <em class="bcp14">MUST</em> be in a quoted string to be used within a parameter value (as defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.4</a>).</p><div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>    token          = 1*&lt;any CHAR except CTLs or separators&gt;
+</pre><p id="rfc.section.2.2.p.12">Many HTTP/1.1 header field values consist of words separated by LWS or special characters. These special characters <em class="bcp14">MUST</em> be in a quoted string to be used within a parameter value (as defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.4</a>).
+      </p>
+      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>    token          = 1*&lt;any CHAR except CTLs or separators&gt;
     separators     = "(" | ")" | "&lt;" | "&gt;" | "@"
                    | "," | ";" | ":" | "\" | &lt;"&gt;
                    | "/" | "[" | "]" | "?" | "="
                    | "{" | "}" | SP | HT
-</pre><p id="rfc.section.2.2.p.14">Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed in fields containing "comment" as part of their field value definition. In all other fields, parentheses are considered part of the field value.</p><div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>    comment        = "(" *( ctext | quoted-pair | comment ) ")"
+</pre><p id="rfc.section.2.2.p.14">Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed
+         in fields containing "comment" as part of their field value definition. In all other fields, parentheses are considered part
+         of the field value.
+      </p>

[... 1426 lines stripped ...]


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@labs.apache.org
For additional commands, e-mail: commits-help@labs.apache.org