Changeset 453 for draft-ietf-httpbis
- Timestamp:
- 28/02/09 04:47:03 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r446 r453 146 146 border-width: 1px; 147 147 } 148 caption { 149 caption-side: bottom; 150 font-weight: bold; 151 font-size: 9pt; 152 margin-top: .5em; 153 } 154 148 155 table.header { 149 156 width: 95%; … … 365 372 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 366 373 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 367 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 1, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">374 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.424, 2009-02-24 16:15:29, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 368 375 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 369 376 <meta name="DC.Creator" content="Fielding, R."> … … 379 386 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-02"> 380 387 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 381 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 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.">388 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 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."> 382 389 </head> 383 390 <body> … … 461 468 <tr> 462 469 <td class="header left"></td> 463 <td class="header right">February 2 0, 2009</td>470 <td class="header right">February 27, 2009</td> 464 471 </tr> 465 472 </table> … … 492 499 </p> 493 500 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 494 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation501 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 495 502 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the 496 503 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part … … 521 528 <li class="tocline1">2.1 <a href="#uri">Uniform Resource Identifiers</a><ul class="toc"> 522 529 <li class="tocline1">2.1.1 <a href="#http.uri">http URI scheme</a></li> 523 <li class="tocline1">2.1.2 <a href="#uri.comparison">URI Comparison</a></li> 524 <li class="tocline1">2.1.3 <a href="#scheme.aliases">Scheme aliases considered harmful</a></li> 530 <li class="tocline1">2.1.2 <a href="#https.uri">https URI scheme</a></li> 531 <li class="tocline1">2.1.3 <a href="#uri.comparison">URI Comparison</a></li> 532 <li class="tocline1">2.1.4 <a href="#scheme.aliases">Scheme aliases considered harmful</a></li> 525 533 </ul> 526 534 </li> … … 670 678 <p id="rfc.section.1.p.3">HTTP is also designed for use as a generic protocol for translating communication to and from other Internet information systems, 671 679 such as USENET news services via NNTP <a href="#RFC3977" id="rfc.xref.RFC3977.1"><cite title="Network News Transfer Protocol (NNTP)">[RFC3977]</cite></a>, file services via FTP <a href="#RFC959" id="rfc.xref.RFC959.1"><cite title="File Transfer Protocol">[RFC959]</cite></a>, Gopher <a href="#RFC1436" id="rfc.xref.RFC1436.1"><cite title="The Internet Gopher Protocol (a distributed document search and retrieval protocol)">[RFC1436]</cite></a>, and WAIS <a href="#WAIS" id="rfc.xref.WAIS.1"><cite title="WAIS Interface Protocol Prototype Functional Specification (v1.5)">[WAIS]</cite></a>. HTTP proxies and gateways provide access to alternative information services by translating their diverse protocols into 672 a hyper mediaformat that can be viewed and manipulated by clients in the same way as HTTP services.673 </p> 674 <p id="rfc.section.1.p.4">One consequence of HTTP flexibility is that we cannot define the protocol in terms of how to implement it behind the interface.675 Instead, we are limited to restricting the syntax of communication, defining the intent of received communication, and the676 expected behavior of recipients. If the communication is considered in isolation, then successful actions should be reflected677 in the observable interface provided by servers. However, since many clients are potentially acting in parallel and perhaps678 at cross-purposes,it would be meaningless to require that such behavior be observable.680 a hypertext format that can be viewed and manipulated by clients in the same way as HTTP services. 681 </p> 682 <p id="rfc.section.1.p.4">One consequence of HTTP flexibility is that the protocol cannot be defined in terms of what occurs behind the interface. Instead, 683 we are limited to defining the syntax of communication, the intent of received communication, and the expected behavior of 684 recipients. If the communication is considered in isolation, then successful actions should be reflected in the observable 685 interface provided by servers. However, since many clients are potentially acting in parallel and perhaps at cross-purposes, 686 it would be meaningless to require that such behavior be observable. 679 687 </p> 680 688 <p id="rfc.section.1.p.5">This document is Part 1 of the seven-part specification of HTTP, defining the protocol referred to as "HTTP/1.1" and obsoleting <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. Part 1 defines the URI schemes specific to HTTP-based resources, overall network operation, transport protocol connection … … 821 829 <div id="rfc.iref.h.1"></div> 822 830 <div id="rfc.iref.u.1"></div> 823 <p id="rfc.section.2.1.1.p.1">The "http" scheme is used to locate network resources via the HTTP protocol. This section defines the syntax and semantics 824 for identifiers using the http or https URI schemes. 825 </p> 831 <p id="rfc.section.2.1.1.p.1">The "http" scheme is used to locate network resources via the HTTP protocol.</p> 826 832 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.30"></span> <a href="#http.uri" class="smpl">http-URI</a> = "http:" "//" <a href="#uri" class="smpl">authority</a> <a href="#uri" class="smpl">path-abempty</a> [ "?" <a href="#uri" class="smpl">query</a> ] 827 833 </pre><p id="rfc.section.2.1.1.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 828 834 listening for TCP connections on that port of that host, and the request-target for the resource is path-absolute (<a href="#request-target" title="request-target">Section 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-target for a resource (<a href="#request-target" title="request-target">Section 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. 829 835 </p> 836 <div id="rfc.iref.h.2"></div> 837 <div id="rfc.iref.u.2"></div> 838 <h3 id="rfc.section.2.1.2"><a href="#rfc.section.2.1.2">2.1.2</a> <a id="https.uri" href="#https.uri">https URI scheme</a></h3> 839 <p id="rfc.section.2.1.2.p.1"> <span class="comment">[rfc.comment.1: TBD: Define and explain purpose of https scheme.]</span> 840 </p> 830 841 <dl class="empty"> 831 <dd> < span id="rfc.iref.h.2"></span> <span id="rfc.iref.u.2"></span> <b>Note:</b> the "https" scheme is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>.842 <dd> <b>Note:</b> the "https" scheme is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>. 832 843 </dd> 833 844 </dl> 834 <h3 id="rfc.section.2.1. 2"><a href="#rfc.section.2.1.2">2.1.2</a> <a id="uri.comparison" href="#uri.comparison">URI Comparison</a></h3>835 <p id="rfc.section.2.1. 2.p.1">When comparing two URIs to decide if they match or not, a client <em class="bcp14">SHOULD</em> use a case-sensitive octet-by-octet comparison of the entire URIs, with these exceptions:845 <h3 id="rfc.section.2.1.3"><a href="#rfc.section.2.1.3">2.1.3</a> <a id="uri.comparison" href="#uri.comparison">URI Comparison</a></h3> 846 <p id="rfc.section.2.1.3.p.1">When comparing two URIs to decide if they match or not, a client <em class="bcp14">SHOULD</em> use a case-sensitive octet-by-octet comparison of the entire URIs, with these exceptions: 836 847 </p> 837 848 <ul> … … 841 852 <li>Comparisons of scheme names <em class="bcp14">MUST</em> be case-insensitive; 842 853 </li> 843 <li>An empty path-absolute is equivalent to an path-absolute of "/".</li> 854 <li>An empty path-absolute is equivalent to a path-absolute of "/".</li> 855 <li>Characters other than those in the "reserved" set are equivalent to their percent-encoded octets (see <a href="#RFC3986" id="rfc.xref.RFC3986.16"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>). 856 </li> 844 857 </ul> 845 <p id="rfc.section.2.1.2.p.2">Characters other than those in the "reserved" set (see <a href="#RFC3986" id="rfc.xref.RFC3986.16"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.2">Section 2.2</a>) are equivalent to their ""%" <a href="#core.rules" class="smpl">HEXDIG</a> <a href="#core.rules" class="smpl">HEXDIG</a>" encoding. 846 </p> 847 <p id="rfc.section.2.1.2.p.3">For example, the following three URIs are equivalent:</p> 858 <p id="rfc.section.2.1.3.p.2">For example, the following three URIs are equivalent:</p> 848 859 <div id="rfc.figure.u.14"></div><pre class="text"> http://example.com:80/~smith/home.html 849 860 http://EXAMPLE.com/%7Esmith/home.html 850 861 http://EXAMPLE.com:/%7esmith/home.html 851 </pre><h3 id="rfc.section.2.1. 3"><a href="#rfc.section.2.1.3">2.1.3</a> <a id="scheme.aliases" href="#scheme.aliases">Scheme aliases considered harmful</a></h3>862 </pre><h3 id="rfc.section.2.1.4"><a href="#rfc.section.2.1.4">2.1.4</a> <a id="scheme.aliases" href="#scheme.aliases">Scheme aliases considered harmful</a></h3> 852 863 <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="intro.overall.operation" href="#intro.overall.operation">Overall Operation</a></h2> 853 864 <p id="rfc.section.2.2.p.1">HTTP is a request/response protocol. A client sends a request to the server in the form of a request method, URI, and protocol … … 910 921 </p> 911 922 <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="http.proxy" href="#http.proxy">Use of HTTP for proxy communication</a></h2> 912 <p id="rfc.section.2.3.p.1"> <span class="comment">[rfc.comment. 1: TBD: Configured to use HTTP to proxy HTTP or other protocols.]</span>923 <p id="rfc.section.2.3.p.1"> <span class="comment">[rfc.comment.2: TBD: Configured to use HTTP to proxy HTTP or other protocols.]</span> 913 924 </p> 914 925 <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a> <a id="http.intercept" href="#http.intercept">Interception of HTTP for access control</a></h2> 915 <p id="rfc.section.2.4.p.1"> <span class="comment">[rfc.comment. 2: TBD: Interception of HTTP traffic for initiating access control.]</span>926 <p id="rfc.section.2.4.p.1"> <span class="comment">[rfc.comment.3: TBD: Interception of HTTP traffic for initiating access control.]</span> 916 927 </p> 917 928 <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a> <a id="http.others" href="#http.others">Use of HTTP by other protocols</a></h2> 918 <p id="rfc.section.2.5.p.1"> <span class="comment">[rfc.comment. 3: TBD: Profiles of HTTP defined by other protocol. Extensions of HTTP like WebDAV.]</span>929 <p id="rfc.section.2.5.p.1"> <span class="comment">[rfc.comment.4: TBD: Profiles of HTTP defined by other protocol. Extensions of HTTP like WebDAV.]</span> 919 930 </p> 920 931 <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a> <a id="http.media" href="#http.media">Use of HTTP by media type specification</a></h2> 921 <p id="rfc.section.2.6.p.1"> <span class="comment">[rfc.comment. 4: TBD: Instructions on composing HTTP requests via hypertext formats.]</span>932 <p id="rfc.section.2.6.p.1"> <span class="comment">[rfc.comment.5: TBD: Instructions on composing HTTP requests via hypertext formats.]</span> 922 933 </p> 923 934 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> … … 1302 1313 <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span> <a href="#method" class="smpl">Method</a> = <a href="#rule.token.separators" class="smpl">token</a> 1303 1314 </pre><h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a> <a id="request-target" href="#request-target">request-target</a></h3> 1304 <p id="rfc.section.5.1.2.p.1">The request-target is a Uniform Resource Identifier (<a href="#uri" title="Uniform Resource Identifiers">Section 2.1</a>) and identifies the resource upon which to apply the request. 1305 </p> 1315 <p id="rfc.section.5.1.2.p.1">The request-target identifies the resource upon which to apply the request.</p> 1306 1316 <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.76"></span> <a href="#request-target" class="smpl">request-target</a> = "*" 1307 1317 / <a href="#uri" class="smpl">absolute-URI</a> … … 1341 1351 Host: www.example.org:8001 1342 1352 </pre> <p>after connecting to port 8001 of host "www.example.org".</p> 1343 <p id="rfc.section.5.1.2.p.15">The request-target is transmitted in the format specified in <a href="#http.uri" title="http URI scheme">Section 2.1.1</a>. If the request-target is encoded using the "% <a href="#core.rules" class="smpl">HEXDIG</a> <a href="#core.rules" class="smpl">HEXDIG</a>" encoding (<a href="#RFC3986" id="rfc.xref.RFC3986.17"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.4">Section 2.4</a>), the origin server <em class="bcp14">MUST</em> decode the request-target in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid request-targets with an appropriate status code.1353 <p id="rfc.section.5.1.2.p.15">The request-target is transmitted in the format specified in <a href="#http.uri" title="http URI scheme">Section 2.1.1</a>. If the request-target is percent-encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.17"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>), the origin server <em class="bcp14">MUST</em> decode the request-target in order to properly interpret the request. Servers <em class="bcp14">SHOULD</em> respond to invalid request-targets with an appropriate status code. 1344 1354 </p> 1345 1355 <p id="rfc.section.5.1.2.p.16">A transparent proxy <em class="bcp14">MUST NOT</em> rewrite the "path-absolute" part of the received request-target when forwarding it to the next inbound server, except as noted … … 1353 1363 </dd> 1354 1364 </dl> 1355 <p id="rfc.section.5.1.2.p.18">HTTP does not place a pre-defined limit on the length of a request-target. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the 414 ( Request-target too Long) status if the received1356 request-targetwould be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 Request-target Too Long">Section 8.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).1365 <p id="rfc.section.5.1.2.p.18">HTTP does not place a pre-defined limit on the length of a request-target. A server <em class="bcp14">MUST</em> be prepared to receive URIs of unbounded length and respond with the 414 (URI Too Long) status if the received request-target 1366 would be longer than the server wishes to handle (see <a href="p2-semantics.html#status.414" title="414 Request-target Too Long">Section 8.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). 1357 1367 </p> 1358 1368 <p id="rfc.section.5.1.2.p.19">Various ad-hoc limitations on request-target length are found in practice. It is <em class="bcp14">RECOMMENDED</em> that all HTTP senders and recipients support request-target lengths of 8000 or more OCTETs. … … 2156 2166 <h2 id="rfc.references.1"><a href="#rfc.section.12.1" id="rfc.section.12.1">12.1</a> Normative References 2157 2167 </h2> 2158 <table summary="Normative References"> 2168 <table summary="Normative References"> 2159 2169 <tr> 2160 2170 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> … … 2182 2192 </tr> 2183 2193 <tr> 2184 <td class="reference"><b id="RFC2045">[RFC2045]</b></td>2185 <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC 2045, November 1996.2186 </td>2187 </tr>2188 <tr>2189 2194 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 2190 2195 <td class="top"><a title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. … … 2208 2213 <h2 id="rfc.references.2"><a href="#rfc.section.12.2" id="rfc.section.12.2">12.2</a> Informative References 2209 2214 </h2> 2210 <table summary="Informative References"> 2215 <table summary="Informative References"> 2211 2216 <tr> 2212 2217 <td class="reference"><b id="Kri2001">[Kri2001]</b></td> … … 2248 2253 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 2249 2254 <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC 1945, May 1996. 2255 </td> 2256 </tr> 2257 <tr> 2258 <td class="reference"><b id="RFC2045">[RFC2045]</b></td> 2259 <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC 2045, November 1996. 2250 2260 </td> 2251 2261 </tr> … … 3140 3150 <li class="indline1">Host header <a class="iref" href="#rfc.iref.h.6"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">9.1</a>, <a class="iref" href="#rfc.xref.header.host.2">B.1.1</a></li> 3141 3151 <li class="indline1">http URI scheme <a class="iref" href="#rfc.iref.h.1"><b>2.1.1</b></a></li> 3142 <li class="indline1">https URI scheme <a class="iref" href="#rfc.iref.h.2">2.1. 1</a></li>3152 <li class="indline1">https URI scheme <a class="iref" href="#rfc.iref.h.2">2.1.2</a></li> 3143 3153 </ul> 3144 3154 </li> … … 3220 3230 <li class="indline1"><em>RFC1900</em> <a class="iref" href="#rfc.xref.RFC1900.1">2.1.1</a>, <a class="iref" href="#rfc.xref.RFC1900.2">10.4</a>, <a class="iref" href="#RFC1900"><b>12.2</b></a></li> 3221 3231 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> 3222 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#rfc.xref.RFC2045.1">1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">3.3</a>, <a class="iref" href="#rfc.xref.RFC2045.3">11</a>, <a class="iref" href="#RFC2045"><b>12. 1</b></a></li>3232 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#rfc.xref.RFC2045.1">1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">3.3</a>, <a class="iref" href="#rfc.xref.RFC2045.3">11</a>, <a class="iref" href="#RFC2045"><b>12.2</b></a></li> 3223 3233 <li class="indline1"><em>RFC2047</em> <a class="iref" href="#rfc.xref.RFC2047.1">4.2</a>, <a class="iref" href="#RFC2047"><b>12.2</b></a></li> 3224 3234 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">7.1.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">7.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.5">11</a>, <a class="iref" href="#RFC2068"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.6">B</a>, <a class="iref" href="#rfc.xref.RFC2068.7">B.2</a><ul class="ind"> … … 3230 3240 <li class="indline1"><em>RFC2145</em> <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">B.3</a></li> 3231 3241 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">E.1</a></li> 3232 <li class="indline1"><em>RFC2818</em> <a class="iref" href="#rfc.xref.RFC2818.1">2.1. 1</a>, <a class="iref" href="#RFC2818"><b>12.2</b></a></li>3242 <li class="indline1"><em>RFC2818</em> <a class="iref" href="#rfc.xref.RFC2818.1">2.1.2</a>, <a class="iref" href="#RFC2818"><b>12.2</b></a></li> 3233 3243 <li class="indline1"><em>RFC2965</em> <a class="iref" href="#rfc.xref.RFC2965.1">4.2</a>, <a class="iref" href="#RFC2965"><b>12.2</b></a></li> 3234 3244 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">9.1</a>, <a class="iref" href="#RFC3864"><b>12.2</b></a></li> 3235 3245 <li class="indline1"><em>RFC3977</em> <a class="iref" href="#rfc.xref.RFC3977.1">1</a>, <a class="iref" href="#RFC3977"><b>12.2</b></a></li> 3236 <li class="indline1"><em>RFC3986</em> <a class="iref" href="#rfc.xref.RFC3986.1">1</a>, <a class="iref" href="#rfc.xref.RFC3986.2">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.3">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.4">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.5">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.6">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.7">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.8">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.9">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.10">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.11">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.12">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.13">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.14">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.15">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.16">2.1.2</a>, <a class="iref" href="#rfc.xref.RFC3986.17">5.1.2</a>, <a class="iref" href="#RFC3986"><b>12.1</b></a><ul class="ind"> 3237 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.RFC3986.16">2.1.2</a></li> 3238 <li class="indline1"><em>Section 2.4</em> <a class="iref" href="#rfc.xref.RFC3986.17">5.1.2</a></li> 3246 <li class="indline1"><em>RFC3986</em> <a class="iref" href="#rfc.xref.RFC3986.1">1</a>, <a class="iref" href="#rfc.xref.RFC3986.2">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.3">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.4">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.5">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.6">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.7">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.8">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.9">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.10">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.11">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.12">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.13">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.14">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.15">2.1</a>, <a class="iref" href="#rfc.xref.RFC3986.16">2.1.3</a>, <a class="iref" href="#rfc.xref.RFC3986.17">5.1.2</a>, <a class="iref" href="#RFC3986"><b>12.1</b></a><ul class="ind"> 3247 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.RFC3986.16">2.1.3</a>, <a class="iref" href="#rfc.xref.RFC3986.17">5.1.2</a></li> 3239 3248 <li class="indline1"><em>Section 3.2.3</em> <a class="iref" href="#rfc.xref.RFC3986.13">2.1</a></li> 3240 3249 <li class="indline1"><em>Section 3.2.2</em> <a class="iref" href="#rfc.xref.RFC3986.15">2.1</a></li> … … 3283 3292 <ul class="ind"> 3284 3293 <li class="indline1">http <a class="iref" href="#rfc.iref.u.1"><b>2.1.1</b></a></li> 3285 <li class="indline1">https <a class="iref" href="#rfc.iref.u.2">2.1. 1</a></li>3294 <li class="indline1">https <a class="iref" href="#rfc.iref.u.2">2.1.2</a></li> 3286 3295 </ul> 3287 3296 </li>
Note: See TracChangeset
for help on using the changeset viewer.