Ignore:
Timestamp:
Feb 2, 2008, 5:40:24 AM (12 years ago)
Author:
julian.reschke@…
Message:

Get rid of duplicate BNF rule names ("host" -> "uri-host", "trailer" -> "trailer-part"), avoid underscore character in rule names ("http_URL" -> "http-URL", "abs_path" -> "path-absolute"), add rules for terms imported from URI spec ("absoluteURI", "authority", "path-absolute", "port", "query", "relativeURI", "host) -- these will have to be updated when switching over to RFC3986; addresses #36.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r182 r185  
    10171017         a scheme name followed by a colon. For definitive information on URL syntax and semantics, see "Uniform Resource Identifiers
    10181018         (URI): Generic Syntax and Semantics," <a href="#RFC2396" id="rfc.xref.RFC2396.1"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a> (which replaces <a href="#RFC1738" id="rfc.xref.RFC1738.3"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> and <a href="#RFC1808" id="rfc.xref.RFC1808.2"><cite title="Relative Uniform Resource Locators">[RFC1808]</cite></a>). This specification adopts the definitions of "URI-reference", "absoluteURI", "relativeURI", "port", "host", "abs_path",
    1019          "query", and "authority" from that specification.
    1020       </p>
    1021       <p id="rfc.section.3.2.1.p.2">HTTP does not place any a priori limit on the length of a URI. Servers <em class="bcp14">MUST</em> be able to handle the URI of any resource they serve, and <em class="bcp14">SHOULD</em> be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server <em class="bcp14">SHOULD</em> return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see <a href="p2-semantics.html#status.414" title="414 Request-URI Too Long">Section 9.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
    1022       </p>
    1023       <p id="rfc.section.3.2.1.p.3"> </p>
     1019         "query", and "authority" from that specification:
     1020      </p>
     1021      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span>  absoluteURI   = &lt;absoluteURI, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.2"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3">Section 3</a>&gt;
     1022  authority     = &lt;authority, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.3"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3.2">Section 3.2</a>&gt;
     1023  path-absolute = &lt;abs_path, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.4"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3">Section 3</a>&gt;
     1024  port          = &lt;port, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.5"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3.2.2">Section 3.2.2</a>&gt;
     1025  query         = &lt;query, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.6"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3.4">Section 3.4</a>&gt;
     1026  relativeURI   = &lt;relativeURI, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.7"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-5">Section 5</a>&gt;
     1027  uri-host      = &lt;host, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.8"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3.2.2">Section 3.2.2</a>&gt;
     1028</pre><p id="rfc.section.3.2.1.p.3">HTTP does not place any a priori limit on the length of a URI. Servers <em class="bcp14">MUST</em> be able to handle the URI of any resource they serve, and <em class="bcp14">SHOULD</em> be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server <em class="bcp14">SHOULD</em> return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see <a href="p2-semantics.html#status.414" title="414 Request-URI Too Long">Section 9.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
     1029      </p>
     1030      <p id="rfc.section.3.2.1.p.4"> </p>
    10241031      <dl class="empty">
    10251032         <dd> <b>Note:</b> Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations
     
    10311038         and semantics for http URLs.
    10321039      </p>
    1033       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  http_URL = "http:" "//" host [ ":" port ] [ abs_path [ "?" query ]]
     1040      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  http-URL = "http:" "//" uri-host [ ":" port ]
     1041             [ path-absolute [ "?" query ]]
    10341042</pre><p id="rfc.section.3.2.2.p.3">If the port is empty or not given, port 80 is assumed. The semantics are that the identified resource is located at the server
    1035          listening for TCP connections on that port of that host, and the Request-URI for the resource is abs_path (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>). The use of IP addresses in URLs <em class="bcp14">SHOULD</em> be avoided whenever possible (see <a href="#RFC1900" id="rfc.xref.RFC1900.1"><cite title="Renumbering Needs Work">[RFC1900]</cite></a>). If the abs_path is not present in the URL, it <em class="bcp14">MUST</em> be given as "/" when used as a Request-URI for a resource (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>). If a proxy receives a host name which is not a fully qualified domain name, it <em class="bcp14">MAY</em> add its domain to the host name it received. If a proxy receives a fully qualified domain name, the proxy <em class="bcp14">MUST NOT</em> change the host name.
     1043         listening for TCP connections on that port of that host, and the Request-URI for the resource is path-absolute (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>). The use of IP addresses in URLs <em class="bcp14">SHOULD</em> be avoided whenever possible (see <a href="#RFC1900" id="rfc.xref.RFC1900.1"><cite title="Renumbering Needs Work">[RFC1900]</cite></a>). If the path-absolute is not present in the URL, it <em class="bcp14">MUST</em> be given as "/" when used as a Request-URI for a resource (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>). If a proxy receives a host name which is not a fully qualified domain name, it <em class="bcp14">MAY</em> add its domain to the host name it received. If a proxy receives a fully qualified domain name, the proxy <em class="bcp14">MUST NOT</em> change the host name.
    10361044      </p>
    10371045      <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="uri.comparison" href="#uri.comparison">URI Comparison</a></h3>
     
    10441052         <li>Comparisons of scheme names <em class="bcp14">MUST</em> be case-insensitive;
    10451053         </li>
    1046          <li>An empty abs_path is equivalent to an abs_path of "/".</li>
     1054         <li>An empty path-absolute is equivalent to an path-absolute of "/".</li>
    10471055      </ul>
    1048       <p id="rfc.section.3.2.3.p.2">Characters other than those in the "reserved" set (see <a href="#RFC2396" id="rfc.xref.RFC2396.2"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>) are equivalent to their ""%" HEX HEX" encoding.
     1056      <p id="rfc.section.3.2.3.p.2">Characters other than those in the "reserved" set (see <a href="#RFC2396" id="rfc.xref.RFC2396.9"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>) are equivalent to their ""%" HEX HEX" encoding.
    10491057      </p>
    10501058      <p id="rfc.section.3.2.3.p.3">For example, the following three URIs are equivalent:</p>
    1051       <div id="rfc.figure.u.15"></div><pre class="text">   http://example.com:80/~smith/home.html
     1059      <div id="rfc.figure.u.16"></div><pre class="text">   http://example.com:80/~smith/home.html
    10521060   http://EXAMPLE.com/%7Esmith/home.html
    10531061   http://EXAMPLE.com:/%7esmith/home.html
     
    10551063      <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;<a id="full.date" href="#full.date">Full Date</a></h3>
    10561064      <p id="rfc.section.3.3.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p>
    1057       <div id="rfc.figure.u.16"></div><pre class="text">   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 822, updated by RFC 1123
     1065      <div id="rfc.figure.u.17"></div><pre class="text">   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 822, updated by RFC 1123
    10581066   Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    10591067   Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
     
    10701078         time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional LWS beyond that specifically included as SP in the grammar.
    10711079      </p>
    1072       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span>  HTTP-date    = rfc1123-date | rfc850-date | asctime-date
     1080      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span>  HTTP-date    = rfc1123-date | rfc850-date | asctime-date
    10731081  rfc1123-date = wkday "," SP date1 SP time SP "GMT"
    10741082  rfc850-date  = weekday "," SP date2 SP time SP "GMT"
     
    10971105         is a property of the message, not of the original entity.
    10981106      </p>
    1099       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span>  transfer-coding         = "chunked" | transfer-extension
     1107      <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span>  transfer-coding         = "chunked" | transfer-extension
    11001108  transfer-extension      = token *( ";" parameter )
    11011109</pre><p id="rfc.section.3.4.p.3">Parameters are in the form of attribute/value pairs.</p>
    1102       <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span>  parameter               = attribute "=" value
     1110      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span>  parameter               = attribute "=" value
    11031111  attribute               = token
    11041112  value                   = token | quoted-string
     
    11251133         necessary for the recipient to verify that it has received the full message.
    11261134      </p>
    1127       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span>  Chunked-Body   = *chunk
     1135      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span><span id="rfc.iref.g.52"></span><span id="rfc.iref.g.53"></span><span id="rfc.iref.g.54"></span><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span>  Chunked-Body   = *chunk
    11281136                   last-chunk
    1129                    trailer
     1137                   trailer-part
    11301138                   CRLF
    11311139 
     
    11391147  chunk-ext-val  = token | quoted-string
    11401148  chunk-data     = 1*OCTET ; a sequence of chunk-size octets
    1141   trailer        = *(entity-header CRLF)
     1149  trailer-part   = *(entity-header CRLF)
    11421150</pre><p id="rfc.section.3.4.1.p.3">The chunk-size field is a string of hex digits indicating the size of the chunk-data in octets. The chunked encoding is ended
    11431151         by any chunk whose size is zero, followed by the trailer, which is terminated by an empty line.
     
    11621170      </p>
    11631171      <p id="rfc.section.3.4.1.p.7">A process for decoding the "chunked" transfer-coding can be represented in pseudo-code as:</p>
    1164       <div id="rfc.figure.u.21"></div><pre class="text">    length := 0
     1172      <div id="rfc.figure.u.22"></div><pre class="text">    length := 0
    11651173    read chunk-size, chunk-extension (if any) and CRLF
    11661174    while (chunk-size &gt; 0) {
     
    11821190      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="message.types" href="#message.types">Message Types</a></h2>
    11831191      <p id="rfc.section.4.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p>
    1184       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  HTTP-message   = Request | Response     ; HTTP/1.1 messages
     1192      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.59"></span>  HTTP-message   = Request | Response     ; HTTP/1.1 messages
    11851193</pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section&nbsp;5</a>) and Response (<a href="#response" title="Response">Section&nbsp;6</a>) messages use the generic message format of <a href="#RFC2822" id="rfc.xref.RFC2822.2"><cite title="Internet Message Format">[RFC2822]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header
    11861194         fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header
    11871195         fields, and possibly a message-body.
    11881196      </p>
    1189       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.53"></span><span id="rfc.iref.g.54"></span>  generic-message = start-line
     1197      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span>  generic-message = start-line
    11901198                    *(message-header CRLF)
    11911199                    CRLF
     
    12051213         forms.
    12061214      </p>
    1207       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span>  message-header = field-name ":" [ field-value ]
     1215      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span>  message-header = field-name ":" [ field-value ]
    12081216  field-name     = token
    12091217  field-value    = *( field-content | LWS )
     
    12291237         header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.2" title="Transfer-Encoding">Section&nbsp;8.7</a>).
    12301238      </p>
    1231       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.59"></span>  message-body = entity-body
     1239      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.66"></span>  message-body = entity-body
    12321240               | &lt;entity-body encoded as per Transfer-Encoding&gt;
    12331241</pre><p id="rfc.section.4.3.p.3">Transfer-Encoding <em class="bcp14">MUST</em> be used to indicate any transfer-codings applied by an application to ensure safe and proper transfer of the message. Transfer-Encoding
     
    12961304         to the entity being transferred. These header fields apply only to the message being transmitted.
    12971305      </p>
    1298       <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.60"></span>  general-header = Cache-Control            ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 15.2</a>
     1306      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.67"></span>  general-header = Cache-Control            ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 15.2</a>
    12991307                 | Connection               ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section&nbsp;8.1</a>
    13001308                 | Date                     ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;8.3</a>
     
    13131321         resource, the identifier of the resource, and the protocol version in use.
    13141322      </p>
    1315       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.61"></span>  Request       = Request-Line              ; <a href="#request-line" title="Request-Line">Section&nbsp;5.1</a>
     1323      <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.68"></span>  Request       = Request-Line              ; <a href="#request-line" title="Request-Line">Section&nbsp;5.1</a>
    13161324                  *(( general-header        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    13171325                   | request-header         ; <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a>
     
    13231331         elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence.
    13241332      </p>
    1325       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.62"></span>  Request-Line   = Method SP Request-URI SP HTTP-Version CRLF
     1333      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.69"></span>  Request-Line   = Method SP Request-URI SP HTTP-Version CRLF
    13261334</pre><h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a id="method" href="#method">Method</a></h3>
    13271335      <p id="rfc.section.5.1.1.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p>
    1328       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span>  Method         = token
     1336      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.70"></span><span id="rfc.iref.g.71"></span>  Method         = token
    13291337</pre><h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a id="request-uri" href="#request-uri">Request-URI</a></h3>
    13301338      <p id="rfc.section.5.1.2.p.1">The Request-URI is a Uniform Resource Identifier (<a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;3.2</a>) and identifies the resource upon which to apply the request.
    13311339      </p>
    1332       <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.65"></span>  Request-URI    = "*"
     1340      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.72"></span>  Request-URI    = "*"
    13331341                 | absoluteURI
    1334                  | ( abs_path [ "?" query ] )
     1342                 | ( path-absolute [ "?" query ] )
    13351343                 | authority
    13361344</pre><p id="rfc.section.5.1.2.p.3">The four options for Request-URI are dependent on the nature of the request. The asterisk "*" means that the request does
     
    13381346         apply to a resource. One example would be
    13391347      </p>
    1340       <div id="rfc.figure.u.31"></div><pre class="text">    OPTIONS * HTTP/1.1
     1348      <div id="rfc.figure.u.32"></div><pre class="text">    OPTIONS * HTTP/1.1
    13411349</pre><p id="rfc.section.5.1.2.p.5">The absoluteURI form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache,
    13421350         and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absoluteURI. In order to avoid request
     
    13441352         Request-Line would be:
    13451353      </p>
    1346       <div id="rfc.figure.u.32"></div><pre class="text">    GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
     1354      <div id="rfc.figure.u.33"></div><pre class="text">    GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
    13471355</pre><p id="rfc.section.5.1.2.p.7">To allow for transition to absoluteURIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absoluteURI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies.
    13481356      </p>
     
    13501358      </p>
    13511359      <p id="rfc.section.5.1.2.p.9">The most common form of Request-URI is that used to identify a resource on an origin server or gateway. In this case the absolute
    1352          path of the URI <em class="bcp14">MUST</em> be transmitted (see <a href="#general.syntax" title="General Syntax">Section&nbsp;3.2.1</a>, abs_path) as the Request-URI, and the network location of the URI (authority) <em class="bcp14">MUST</em> be transmitted in a Host header field. For example, a client wishing to retrieve the resource above directly from the origin
     1360         path of the URI <em class="bcp14">MUST</em> be transmitted (see <a href="#general.syntax" title="General Syntax">Section&nbsp;3.2.1</a>, path-absolute) as the Request-URI, and the network location of the URI (authority) <em class="bcp14">MUST</em> be transmitted in a Host header field. For example, a client wishing to retrieve the resource above directly from the origin
    13531361         server would create a TCP connection to port 80 of the host "www.example.org" and send the lines:
    13541362      </p>
    1355       <div id="rfc.figure.u.33"></div><pre class="text">    GET /pub/WWW/TheProject.html HTTP/1.1
     1363      <div id="rfc.figure.u.34"></div><pre class="text">    GET /pub/WWW/TheProject.html HTTP/1.1
    13561364    Host: www.example.org
    13571365</pre><p id="rfc.section.5.1.2.p.11">followed by the remainder of the Request. Note that the absolute path cannot be empty; if none is present in the original
    13581366         URI, it <em class="bcp14">MUST</em> be given as "/" (the server root).
    13591367      </p>
    1360       <p id="rfc.section.5.1.2.p.12">The Request-URI is transmitted in the format specified in <a href="#general.syntax" title="General Syntax">Section&nbsp;3.2.1</a>. If the Request-URI is encoded using the "% HEX HEX" encoding <a href="#RFC2396" id="rfc.xref.RFC2396.3"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, the origin server <em class="bcp14">MUST</em> decode the Request-URI in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid Request-URIs with an appropriate status code.
    1361       </p>
    1362       <p id="rfc.section.5.1.2.p.13">A transparent proxy <em class="bcp14">MUST NOT</em> rewrite the "abs_path" part of the received Request-URI when forwarding it to the next inbound server, except as noted above
    1363          to replace a null abs_path with "/".
     1368      <p id="rfc.section.5.1.2.p.12">The Request-URI is transmitted in the format specified in <a href="#general.syntax" title="General Syntax">Section&nbsp;3.2.1</a>. If the Request-URI is encoded using the "% HEX HEX" encoding <a href="#RFC2396" id="rfc.xref.RFC2396.10"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, the origin server <em class="bcp14">MUST</em> decode the Request-URI in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid Request-URIs with an appropriate status code.
     1369      </p>
     1370      <p id="rfc.section.5.1.2.p.13">A transparent proxy <em class="bcp14">MUST NOT</em> rewrite the "path-absolute" part of the received Request-URI when forwarding it to the next inbound server, except as noted
     1371         above to replace a null path-absolute with "/".
    13641372      </p>
    13651373      <p id="rfc.section.5.1.2.p.14"> </p>
     
    13911399      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="response" href="#response">Response</a></h1>
    13921400      <p id="rfc.section.6.p.1">After receiving and interpreting a request message, a server responds with an HTTP response message.</p>
    1393       <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.66"></span>  Response      = Status-Line               ; <a href="#status-line" title="Status-Line">Section&nbsp;6.1</a>
     1401      <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.73"></span>  Response      = Status-Line               ; <a href="#status-line" title="Status-Line">Section&nbsp;6.1</a>
    13941402                  *(( general-header        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    13951403                   | response-header        ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a>
     
    14021410         CRLF sequence.
    14031411      </p>
    1404       <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.67"></span>  Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
     1412      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.74"></span>  Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
    14051413</pre><h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3>
    14061414      <p id="rfc.section.6.1.1.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes
     
    14181426         <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li>
    14191427      </ul>
    1420       <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.68"></span><span id="rfc.iref.g.69"></span><span id="rfc.iref.g.70"></span>  Status-Code    = 3DIGIT
     1428      <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span>  Status-Code    = 3DIGIT
    14211429  Reason-Phrase  = *&lt;TEXT, excluding CR, LF&gt;
    14221430</pre><h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="connections" href="#connections">Connections</a></h1>
     
    16091617      </p>
    16101618      <p id="rfc.section.8.1.p.2">The Connection header has the following grammar:</p>
    1611       <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.71"></span><span id="rfc.iref.g.72"></span>  Connection = "Connection" ":" 1#(connection-token)
     1619      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.78"></span><span id="rfc.iref.g.79"></span>  Connection = "Connection" ":" 1#(connection-token)
    16121620  connection-token  = token
    16131621</pre><p id="rfc.section.8.1.p.4">HTTP/1.1 proxies <em class="bcp14">MUST</em> parse the Connection header field before a message is forwarded and, for each connection-token in this field, remove any header
     
    16211629         of the response. For example,
    16221630      </p>
    1623       <div id="rfc.figure.u.38"></div><pre class="text">    Connection: close
     1631      <div id="rfc.figure.u.39"></div><pre class="text">    Connection: close
    16241632</pre><p id="rfc.section.8.1.p.8">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered `persistent' (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;7.1</a>) after the current request/response is complete.
    16251633      </p>
     
    16371645         or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET.
    16381646      </p>
    1639       <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.73"></span>  Content-Length    = "Content-Length" ":" 1*DIGIT
     1647      <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.80"></span>  Content-Length    = "Content-Length" ":" 1*DIGIT
    16401648</pre><p id="rfc.section.8.2.p.3">An example is</p>
    1641       <div id="rfc.figure.u.40"></div><pre class="text">    Content-Length: 3495
     1649      <div id="rfc.figure.u.41"></div><pre class="text">    Content-Length: 3495
    16421650</pre><p id="rfc.section.8.2.p.5">Applications <em class="bcp14">SHOULD</em> use this field to indicate the transfer-length of the message-body, unless this is prohibited by the rules in <a href="#message.length" title="Message Length">Section&nbsp;4.4</a>.
    16431651      </p>
     
    16541662         as orig-date in <a href="http://tools.ietf.org/html/rfc2822#section-3.6.1">Section 3.6.1</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.4"><cite title="Internet Message Format">[RFC2822]</cite></a>. The field value is an HTTP-date, as described in <a href="#full.date" title="Full Date">Section&nbsp;3.3.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    16551663      </p>
    1656       <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.74"></span>  Date  = "Date" ":" HTTP-date
     1664      <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.81"></span>  Date  = "Date" ":" HTTP-date
    16571665</pre><p id="rfc.section.8.3.p.3">An example is</p>
    1658       <div id="rfc.figure.u.42"></div><pre class="text">    Date: Tue, 15 Nov 1994 08:12:31 GMT
     1666      <div id="rfc.figure.u.43"></div><pre class="text">    Date: Tue, 15 Nov 1994 08:12:31 GMT
    16591667</pre><p id="rfc.section.8.3.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
    16601668      </p>
     
    16921700         a single IP address.
    16931701      </p>
    1694       <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.75"></span>  Host = "Host" ":" host [ ":" port ] ; <a href="#http.url" title="http URL">Section&nbsp;3.2.2</a>
     1702      <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.82"></span>  Host = "Host" ":" uri-host [ ":" port ] ; <a href="#http.url" title="http URL">Section&nbsp;3.2.2</a>
    16951703</pre><p id="rfc.section.8.4.p.3">A "host" without any trailing port information implies the default port for the service requested (e.g., "80" for an HTTP
    16961704         URL). For example, a request on the origin server for &lt;http://www.example.org/pub/WWW/&gt; would properly include:
    16971705      </p>
    1698       <div id="rfc.figure.u.44"></div><pre class="text">    GET /pub/WWW/ HTTP/1.1
     1706      <div id="rfc.figure.u.45"></div><pre class="text">    GET /pub/WWW/ HTTP/1.1
    16991707    Host: www.example.org
    17001708</pre><p id="rfc.section.8.4.p.5">A client <em class="bcp14">MUST</em> include a Host header field in all HTTP/1.1 request messages. If the requested URI does not include an Internet host name
     
    17111719         and/or a comma-separated list of extension transfer-coding names with optional accept parameters (as described in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.4</a>).
    17121720      </p>
    1713       <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span>  TE        = "TE" ":" #( t-codings )
     1721      <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span>  TE        = "TE" ":" #( t-codings )
    17141722  t-codings = "trailers" | ( transfer-extension [ accept-params ] )
    17151723</pre><p id="rfc.section.8.5.p.3">The presence of the keyword "trailers" indicates that the client is willing to accept trailer fields in a chunked transfer-coding,
     
    17171725      </p>
    17181726      <p id="rfc.section.8.5.p.4">Examples of its use are:</p>
    1719       <div id="rfc.figure.u.46"></div><pre class="text">    TE: deflate
     1727      <div id="rfc.figure.u.47"></div><pre class="text">    TE: deflate
    17201728    TE:
    17211729    TE: trailers, deflate;q=0.5
     
    17541762         with chunked transfer-coding.
    17551763      </p>
    1756       <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.78"></span>  Trailer  = "Trailer" ":" 1#field-name
     1764      <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.85"></span>  Trailer  = "Trailer" ":" 1#field-name
    17571765</pre><p id="rfc.section.8.6.p.3">An HTTP/1.1 message <em class="bcp14">SHOULD</em> include a Trailer header field in a message using chunked transfer-coding with a non-empty trailer. Doing so allows the recipient
    17581766         to know which header fields to expect in the trailer.
     
    17741782         transfer-coding is a property of the message, not of the entity.
    17751783      </p>
    1776       <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.79"></span>  Transfer-Encoding       = "Transfer-Encoding" ":" 1#transfer-coding
     1784      <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.86"></span>  Transfer-Encoding       = "Transfer-Encoding" ":" 1#transfer-coding
    17771785</pre><p id="rfc.section.8.7.p.3">Transfer-codings are defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.4</a>. An example is:
    17781786      </p>
    1779       <div id="rfc.figure.u.49"></div><pre class="text">  Transfer-Encoding: chunked
     1787      <div id="rfc.figure.u.50"></div><pre class="text">  Transfer-Encoding: chunked
    17801788</pre><p id="rfc.section.8.7.p.5">If multiple encodings have been applied to an entity, the transfer-codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other entity-header fields not defined by this specification.
    17811789      </p>
     
    17871795         to use if the server finds it appropriate to switch protocols. The server <em class="bcp14">MUST</em> use the Upgrade header field within a 101 (Switching Protocols) response to indicate which protocol(s) are being switched.
    17881796      </p>
    1789       <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.80"></span>  Upgrade        = "Upgrade" ":" 1#product
     1797      <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.87"></span>  Upgrade        = "Upgrade" ":" 1#product
    17901798</pre><p id="rfc.section.8.8.p.3">For example,</p>
    1791       <div id="rfc.figure.u.51"></div><pre class="text">    Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
     1799      <div id="rfc.figure.u.52"></div><pre class="text">    Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
    17921800</pre><p id="rfc.section.8.8.p.5">The Upgrade header field is intended to provide a simple mechanism for transition from HTTP/1.1 to some other, incompatible
    17931801         protocol. It does so by allowing the client to advertise its desire to use another protocol, such as a later version of HTTP
     
    18181826         of all senders along the request/response chain.
    18191827      </p>
    1820       <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span><span id="rfc.iref.g.86"></span>  Via =  "Via" ":" 1#( received-protocol received-by [ comment ] )
     1828      <div id="rfc.figure.u.53"></div><pre class="inline"><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span>  Via =  "Via" ":" 1#( received-protocol received-by [ comment ] )
    18211829  received-protocol = [ protocol-name "/" ] protocol-version
    18221830  protocol-name     = token
    18231831  protocol-version  = token
    1824   received-by       = ( host [ ":" port ] ) | pseudonym
     1832  received-by       = ( uri-host [ ":" port ] ) | pseudonym
    18251833  pseudonym         = token
    18261834</pre><p id="rfc.section.8.9.p.3">The received-protocol indicates the protocol version of the message received by the server or client along each segment of
     
    18411849         server at www.example.com. The request received by www.example.com would then have the following Via header field:
    18421850      </p>
    1843       <div id="rfc.figure.u.53"></div><pre class="text">    Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
     1851      <div id="rfc.figure.u.54"></div><pre class="text">    Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
    18441852</pre><p id="rfc.section.8.9.p.9">Proxies and gateways used as a portal through a network firewall <em class="bcp14">SHOULD NOT</em>, by default, forward the names and ports of hosts within the firewall region. This information <em class="bcp14">SHOULD</em> only be propagated if explicitly enabled. If not enabled, the received-by host of any host behind the firewall <em class="bcp14">SHOULD</em> be replaced by an appropriate pseudonym for that host.
    18451853      </p>
     
    18471855         For example,
    18481856      </p>
    1849       <div id="rfc.figure.u.54"></div><pre class="text">    Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
     1857      <div id="rfc.figure.u.55"></div><pre class="text">    Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
    18501858</pre><p id="rfc.section.8.9.p.12">could be collapsed to</p>
    1851       <div id="rfc.figure.u.55"></div><pre class="text">    Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
     1859      <div id="rfc.figure.u.56"></div><pre class="text">    Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
    18521860</pre><p id="rfc.section.8.9.p.14">Applications <em class="bcp14">SHOULD NOT</em> combine multiple entries unless they are all under the same organizational control and the hosts have already been replaced
    18531861         by pseudonyms. Applications <em class="bcp14">MUST NOT</em> combine entries which have different received-protocol values.
     
    23812389      <p id="rfc.section.D.4.p.3">Clarification that the chunk length does not include the count of the octets in the chunk header and trailer. (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.4.1</a>)
    23822390      </p>
    2383       <p id="rfc.section.D.4.p.4">Fix BNF to add query, as the abs_path production in <a href="http://tools.ietf.org/html/rfc2396#section-3">Section 3</a> of <a href="#RFC2396" id="rfc.xref.RFC2396.4"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a> doesn't define it. (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>)
     2391      <p id="rfc.section.D.4.p.4">Fix BNF to add query, as the abs_path production in <a href="http://tools.ietf.org/html/rfc2396#section-3">Section 3</a> of <a href="#RFC2396" id="rfc.xref.RFC2396.11"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a> doesn't define it. (<a href="#request-uri" title="Request-URI">Section&nbsp;5.1.2</a>)
    23842392      </p>
    23852393      <p id="rfc.section.D.4.p.5">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.7" title="Connection">Section&nbsp;8.1</a>)
     
    24472455         </li>
    24482456         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/82</a>&gt;: "rel_path not used"
     2457         </li>
     2458      </ul>
     2459      <p id="rfc.section.E.3.p.2">Other changes: </p>
     2460      <ul>
     2461         <li>Get rid of duplicate BNF rule names ("host" -&gt; "uri-host", "trailer" -&gt; "trailer-part"), avoid underscore character in rule
     2462            names ("http_URL" -&gt; "http-URL", "abs_path" -&gt; "path-absolute"), add rules for terms imported from URI spec ("absoluteURI",
     2463            "authority", "path-absolute", "port", "query", "relativeURI", "host) -- these will have to be updated when switching over
     2464            to RFC3986 (work in progress on &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;)
    24492465         </li>
    24502466      </ul>
     
    25082524                  <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
    25092525                     <ul class="ind">
     2526                        <li class="indline1"><tt>absoluteURI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>3.2.1</b></a></li>
    25102527                        <li class="indline1"><tt>ALPHA</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>2.2</b></a></li>
    2511                         <li class="indline1"><tt>asctime-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>3.3.1</b></a></li>
    2512                         <li class="indline1"><tt>attribute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.41"><b>3.4</b></a></li>
     2528                        <li class="indline1"><tt>asctime-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.37"><b>3.3.1</b></a></li>
     2529                        <li class="indline1"><tt>attribute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.48"><b>3.4</b></a></li>
     2530                        <li class="indline1"><tt>authority</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>3.2.1</b></a></li>
    25132531                        <li class="indline1"><tt>CHAR</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>2.2</b></a></li>
    2514                         <li class="indline1"><tt>chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.44"><b>3.4.1</b></a></li>
    2515                         <li class="indline1"><tt>chunk-data</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.50"><b>3.4.1</b></a></li>
    2516                         <li class="indline1"><tt>chunk-ext-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.48"><b>3.4.1</b></a></li>
    2517                         <li class="indline1"><tt>chunk-ext-val</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.49"><b>3.4.1</b></a></li>
    2518                         <li class="indline1"><tt>chunk-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.47"><b>3.4.1</b></a></li>
    2519                         <li class="indline1"><tt>chunk-size</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.45"><b>3.4.1</b></a></li>
    2520                         <li class="indline1"><tt>Chunked-Body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.43"><b>3.4.1</b></a></li>
     2532                        <li class="indline1"><tt>chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.51"><b>3.4.1</b></a></li>
     2533                        <li class="indline1"><tt>chunk-data</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.57"><b>3.4.1</b></a></li>
     2534                        <li class="indline1"><tt>chunk-ext-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.55"><b>3.4.1</b></a></li>
     2535                        <li class="indline1"><tt>chunk-ext-val</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.56"><b>3.4.1</b></a></li>
     2536                        <li class="indline1"><tt>chunk-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.54"><b>3.4.1</b></a></li>
     2537                        <li class="indline1"><tt>chunk-size</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.52"><b>3.4.1</b></a></li>
     2538                        <li class="indline1"><tt>Chunked-Body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.50"><b>3.4.1</b></a></li>
    25212539                        <li class="indline1"><tt>comment</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>2.2</b></a></li>
    2522                         <li class="indline1"><tt>Connection</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.71"><b>8.1</b></a></li>
    2523                         <li class="indline1"><tt>connection-token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.72"><b>8.1</b></a></li>
    2524                         <li class="indline1"><tt>Content-Length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.73"><b>8.2</b></a></li>
     2540                        <li class="indline1"><tt>Connection</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.78"><b>8.1</b></a></li>
     2541                        <li class="indline1"><tt>connection-token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.79"><b>8.1</b></a></li>
     2542                        <li class="indline1"><tt>Content-Length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.80"><b>8.2</b></a></li>
    25252543                        <li class="indline1"><tt>CR</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>2.2</b></a></li>
    25262544                        <li class="indline1"><tt>CRLF</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>2.2</b></a></li>
    25272545                        <li class="indline1"><tt>ctext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>2.2</b></a></li>
    25282546                        <li class="indline1"><tt>CTL</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>2.2</b></a></li>
    2529                         <li class="indline1"><tt>Date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.74"><b>8.3</b></a></li>
    2530                         <li class="indline1"><tt>date1</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.31"><b>3.3.1</b></a></li>
    2531                         <li class="indline1"><tt>date2</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.32"><b>3.3.1</b></a></li>
    2532                         <li class="indline1"><tt>date3</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.33"><b>3.3.1</b></a></li>
     2547                        <li class="indline1"><tt>Date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.81"><b>8.3</b></a></li>
     2548                        <li class="indline1"><tt>date1</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.38"><b>3.3.1</b></a></li>
     2549                        <li class="indline1"><tt>date2</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.39"><b>3.3.1</b></a></li>
     2550                        <li class="indline1"><tt>date3</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.40"><b>3.3.1</b></a></li>
    25332551                        <li class="indline1"><tt>DIGIT</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>2.2</b></a></li>
    25342552                        <li class="indline1"><tt>DQUOTE</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>2.2</b></a></li>
    2535                         <li class="indline1"><tt>extension-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.69"><b>6.1.1</b></a></li>
    2536                         <li class="indline1"><tt>extension-method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.64"><b>5.1.1</b></a></li>
    2537                         <li class="indline1"><tt>field-content</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.58"><b>4.2</b></a></li>
    2538                         <li class="indline1"><tt>field-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.56"><b>4.2</b></a></li>
    2539                         <li class="indline1"><tt>field-value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.57"><b>4.2</b></a></li>
    2540                         <li class="indline1"><tt>general-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.60"><b>4.5</b></a></li>
    2541                         <li class="indline1"><tt>generic-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.53"><b>4.1</b></a></li>
     2553                        <li class="indline1"><tt>extension-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.76"><b>6.1.1</b></a></li>
     2554                        <li class="indline1"><tt>extension-method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.71"><b>5.1.1</b></a></li>
     2555                        <li class="indline1"><tt>field-content</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.65"><b>4.2</b></a></li>
     2556                        <li class="indline1"><tt>field-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.63"><b>4.2</b></a></li>
     2557                        <li class="indline1"><tt>field-value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.64"><b>4.2</b></a></li>
     2558                        <li class="indline1"><tt>general-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.67"><b>4.5</b></a></li>
     2559                        <li class="indline1"><tt>generic-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.60"><b>4.1</b></a></li>
    25422560                        <li class="indline1"><tt>HEX</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>2.2</b></a></li>
    2543                         <li class="indline1"><tt>Host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.75"><b>8.4</b></a></li>
     2561                        <li class="indline1"><tt>Host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.82"><b>8.4</b></a></li>
    25442562                        <li class="indline1"><tt>HTAB</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>2.2</b></a></li>
    2545                         <li class="indline1"><tt>HTTP-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>3.3.1</b></a></li>
    2546                         <li class="indline1"><tt>HTTP-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.52"><b>4.1</b></a></li>
     2563                        <li class="indline1"><tt>HTTP-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.34"><b>3.3.1</b></a></li>
     2564                        <li class="indline1"><tt>HTTP-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.59"><b>4.1</b></a></li>
     2565                        <li class="indline1"><tt>http-URL</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.33"><b>3.2.2</b></a></li>
    25472566                        <li class="indline1"><tt>HTTP-Version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.25"><b>3.1</b></a></li>
    2548                         <li class="indline1"><tt>http_URL</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>3.2.2</b></a></li>
    2549                         <li class="indline1"><tt>last-chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.46"><b>3.4.1</b></a></li>
     2567                        <li class="indline1"><tt>last-chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.53"><b>3.4.1</b></a></li>
    25502568                        <li class="indline1"><tt>LF</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>2.2</b></a></li>
    25512569                        <li class="indline1"><tt>LOALPHA</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>2.2</b></a></li>
    25522570                        <li class="indline1"><tt>LWS</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>2.2</b></a></li>
    2553                         <li class="indline1"><tt>message-body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.59"><b>4.3</b></a></li>
    2554                         <li class="indline1"><tt>message-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.55"><b>4.2</b></a></li>
    2555                         <li class="indline1"><tt>Method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.63"><b>5.1.1</b></a></li>
    2556                         <li class="indline1"><tt>month</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.37"><b>3.3.1</b></a></li>
     2571                        <li class="indline1"><tt>message-body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.66"><b>4.3</b></a></li>
     2572                        <li class="indline1"><tt>message-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.62"><b>4.2</b></a></li>
     2573                        <li class="indline1"><tt>Method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.70"><b>5.1.1</b></a></li>
     2574                        <li class="indline1"><tt>month</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.44"><b>3.3.1</b></a></li>
    25572575                        <li class="indline1"><tt>OCTET</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li>
    2558                         <li class="indline1"><tt>parameter</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.40"><b>3.4</b></a></li>
    2559                         <li class="indline1"><tt>protocol-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.83"><b>8.9</b></a></li>
    2560                         <li class="indline1"><tt>protocol-version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.84"><b>8.9</b></a></li>
    2561                         <li class="indline1"><tt>pseudonym</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.86"><b>8.9</b></a></li>
     2576                        <li class="indline1"><tt>parameter</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.47"><b>3.4</b></a></li>
     2577                        <li class="indline1"><tt>path-absolute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>3.2.1</b></a></li>
     2578                        <li class="indline1"><tt>port</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>3.2.1</b></a></li>
     2579                        <li class="indline1"><tt>protocol-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.90"><b>8.9</b></a></li>
     2580                        <li class="indline1"><tt>protocol-version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.91"><b>8.9</b></a></li>
     2581                        <li class="indline1"><tt>pseudonym</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.93"><b>8.9</b></a></li>
    25622582                        <li class="indline1"><tt>qdtext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>2.2</b></a></li>
     2583                        <li class="indline1"><tt>query</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>3.2.1</b></a></li>
    25632584                        <li class="indline1"><tt>quoted-pair</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.24"><b>2.2</b></a></li>
    25642585                        <li class="indline1"><tt>quoted-string</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>2.2</b></a></li>
    2565                         <li class="indline1"><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.70"><b>6.1.1</b></a></li>
    2566                         <li class="indline1"><tt>received-by</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.85"><b>8.9</b></a></li>
    2567                         <li class="indline1"><tt>received-protocol</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.82"><b>8.9</b></a></li>
    2568                         <li class="indline1"><tt>Request</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.61"><b>5</b></a></li>
    2569                         <li class="indline1"><tt>Request-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.62"><b>5.1</b></a></li>
    2570                         <li class="indline1"><tt>Request-URI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.65"><b>5.1.2</b></a></li>
    2571                         <li class="indline1"><tt>Response</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.66"><b>6</b></a></li>
    2572                         <li class="indline1"><tt>rfc1123-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>3.3.1</b></a></li>
    2573                         <li class="indline1"><tt>rfc850-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>3.3.1</b></a></li>
     2586                        <li class="indline1"><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.77"><b>6.1.1</b></a></li>
     2587                        <li class="indline1"><tt>received-by</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.92"><b>8.9</b></a></li>
     2588                        <li class="indline1"><tt>received-protocol</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.89"><b>8.9</b></a></li>
     2589                        <li class="indline1"><tt>relativeURI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.31"><b>3.2.1</b></a></li>
     2590                        <li class="indline1"><tt>Request</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.68"><b>5</b></a></li>
     2591                        <li class="indline1"><tt>Request-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.69"><b>5.1</b></a></li>
     2592                        <li class="indline1"><tt>Request-URI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.72"><b>5.1.2</b></a></li>
     2593                        <li class="indline1"><tt>Response</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.73"><b>6</b></a></li>
     2594                        <li class="indline1"><tt>rfc1123-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.35"><b>3.3.1</b></a></li>
     2595                        <li class="indline1"><tt>rfc850-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.36"><b>3.3.1</b></a></li>
    25742596                        <li class="indline1"><tt>separators</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>2.2</b></a></li>
    25752597                        <li class="indline1"><tt>SP</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>2.2</b></a></li>
    2576                         <li class="indline1"><tt>start-line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.54"><b>4.1</b></a></li>
    2577                         <li class="indline1"><tt>Status-Code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.68"><b>6.1.1</b></a></li>
    2578                         <li class="indline1"><tt>Status-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.67"><b>6.1</b></a></li>
    2579                         <li class="indline1"><tt>t-codings</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.77"><b>8.5</b></a></li>
    2580                         <li class="indline1"><tt>TE</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.76"><b>8.5</b></a></li>
     2598                        <li class="indline1"><tt>start-line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.61"><b>4.1</b></a></li>
     2599                        <li class="indline1"><tt>Status-Code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.75"><b>6.1.1</b></a></li>
     2600                        <li class="indline1"><tt>Status-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.74"><b>6.1</b></a></li>
     2601                        <li class="indline1"><tt>t-codings</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.84"><b>8.5</b></a></li>
     2602                        <li class="indline1"><tt>TE</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.83"><b>8.5</b></a></li>
    25812603                        <li class="indline1"><tt>TEXT</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>2.2</b></a></li>
    2582                         <li class="indline1"><tt>time</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.34"><b>3.3.1</b></a></li>
     2604                        <li class="indline1"><tt>time</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.41"><b>3.3.1</b></a></li>
    25832605                        <li class="indline1"><tt>token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>2.2</b></a></li>
    2584                         <li class="indline1"><tt>trailer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.51"><b>3.4.1</b></a></li>
    2585                         <li class="indline1"><tt>Trailer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.78"><b>8.6</b></a></li>
    2586                         <li class="indline1"><tt>transfer-coding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.38"><b>3.4</b></a></li>
    2587                         <li class="indline1"><tt>Transfer-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.79"><b>8.7</b></a></li>
    2588                         <li class="indline1"><tt>transfer-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.39"><b>3.4</b></a></li>
     2606                        <li class="indline1"><tt>Trailer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.85"><b>8.6</b></a></li>
     2607                        <li class="indline1"><tt>trailer-part</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.58"><b>3.4.1</b></a></li>
     2608                        <li class="indline1"><tt>transfer-coding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.45"><b>3.4</b></a></li>
     2609                        <li class="indline1"><tt>Transfer-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.86"><b>8.7</b></a></li>
     2610                        <li class="indline1"><tt>transfer-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.46"><b>3.4</b></a></li>
    25892611                        <li class="indline1"><tt>UPALPHA</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>2.2</b></a></li>
    2590                         <li class="indline1"><tt>Upgrade</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.80"><b>8.8</b></a></li>
    2591                         <li class="indline1"><tt>value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.42"><b>3.4</b></a></li>
    2592                         <li class="indline1"><tt>Via</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.81"><b>8.9</b></a></li>
    2593                         <li class="indline1"><tt>weekday</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.36"><b>3.3.1</b></a></li>
    2594                         <li class="indline1"><tt>wkday</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.35"><b>3.3.1</b></a></li>
     2612                        <li class="indline1"><tt>Upgrade</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.87"><b>8.8</b></a></li>
     2613                        <li class="indline1"><tt>uri-host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.32"><b>3.2.1</b></a></li>
     2614                        <li class="indline1"><tt>value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.49"><b>3.4</b></a></li>
     2615                        <li class="indline1"><tt>Via</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.88"><b>8.9</b></a></li>
     2616                        <li class="indline1"><tt>weekday</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.43"><b>3.3.1</b></a></li>
     2617                        <li class="indline1"><tt>wkday</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.42"><b>3.3.1</b></a></li>
    25952618                     </ul>
    25962619                  </li>
     
    26982721                  <li class="indline1"><em>RFC2145</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2145.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2145.2">3.1</a>, <a class="iref" href="#RFC2145"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">D.3</a></li>
    26992722                  <li class="indline1"><em>RFC2324</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2324.1">1.1</a>, <a class="iref" href="#RFC2324"><b>12.2</b></a></li>
    2700                   <li class="indline1"><em>RFC2396</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.2">3.2.3</a>, <a class="iref" href="#rfc.xref.RFC2396.3">5.1.2</a>, <a class="iref" href="#RFC2396"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2396.4">D.4</a><ul class="ind">
    2701                         <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.4">D.4</a></li>
     2723                  <li class="indline1"><em>RFC2396</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.2">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.3">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.4">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.5">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.6">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.7">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.8">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.9">3.2.3</a>, <a class="iref" href="#rfc.xref.RFC2396.10">5.1.2</a>, <a class="iref" href="#RFC2396"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2396.11">D.4</a><ul class="ind">
     2724                        <li class="indline1"><em>Section 3.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.5">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.8">3.2.1</a></li>
     2725                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.3">3.2.1</a></li>
     2726                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.6">3.2.1</a></li>
     2727                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.2">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.4">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.11">D.4</a></li>
     2728                        <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2396.7">3.2.1</a></li>
    27022729                     </ul>
    27032730                  </li>
Note: See TracChangeset for help on using the changeset viewer.