Changeset 356 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 13/11/08 00:36:25 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r345 r356 477 477 <tr> 478 478 <td class="header left"></td> 479 <td class="header right">November 1 1, 2008</td>479 <td class="header right">November 13, 2008</td> 480 480 </tr> 481 481 </table> … … 672 672 </p> 673 673 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1> 674 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="A ugmented BNF">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>: <span class="comment">[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>.]</span>674 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="ABNF Extensions">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>: <span class="comment">[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>.]</span> 675 675 </p> 676 676 <div id="rfc.figure.u.1"></div><pre class="inline"> <a href="#notation" class="smpl">DIGIT</a> = <DIGIT, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> … … 678 678 <a href="#notation" class="smpl">quoted-string</a> = <quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 679 679 <a href="#notation" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 680 <a href="#notation" class="smpl">BWS</a> = <BWS, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 681 <a href="#notation" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 682 <a href="#notation" class="smpl">RWS</a> = <RWS, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 680 683 </pre><div id="abnf.dependencies"> 681 684 <p id="rfc.section.2.p.4"> The ABNF rules below are defined in other parts:</p> 682 685 </div> 683 <div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absoluteURI</a> = <absoluteURI, defined in <a href="#Part1" id="rfc.xref.Part1. 8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>>684 <a href="#abnf.dependencies" class="smpl">fragment</a> = <fragment, defined in <a href="#Part1" id="rfc.xref.Part1. 9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>>685 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in <a href="#Part1" id="rfc.xref.Part1.1 0"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a>>686 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.1 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>>687 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in <a href="#Part1" id="rfc.xref.Part1.1 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a>>688 <a href="#abnf.dependencies" class="smpl">relativeURI</a> = <relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.1 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>>689 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, defined in <a href="#Part1" id="rfc.xref.Part1.1 4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>>686 <div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absoluteURI</a> = <absoluteURI, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>> 687 <a href="#abnf.dependencies" class="smpl">fragment</a> = <fragment, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>> 688 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a>> 689 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>> 690 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a>> 691 <a href="#abnf.dependencies" class="smpl">relativeURI</a> = <relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>> 692 <a href="#abnf.dependencies" class="smpl">TE</a> = <TE, defined in <a href="#Part1" id="rfc.xref.Part1.17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>> 690 693 </pre><div id="rfc.figure.u.4"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Accept</a> = <Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a>> 691 694 <a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = … … 759 762 / <a href="#header.expect" class="smpl">Expect</a> ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section 10.2</a> 760 763 / <a href="#header.from" class="smpl">From</a> ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section 10.3</a> 761 / <a href="#abnf.dependencies" class="smpl">Host</a> ; <a href="#Part1" id="rfc.xref.Part1.1 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a>764 / <a href="#abnf.dependencies" class="smpl">Host</a> ; <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 8.4</a> 762 765 / <a href="#abnf.dependencies" class="smpl">If-Match</a> ; <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 7.2</a> 763 766 / <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a> ; <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 7.3</a> … … 769 772 / <a href="#abnf.dependencies" class="smpl">Range</a> ; <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 6.4</a> 770 773 / <a href="#header.referer" class="smpl">Referer</a> ; <a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section 10.6</a> 771 / <a href="#abnf.dependencies" class="smpl">TE</a> ; <a href="#Part1" id="rfc.xref.Part1.1 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>774 / <a href="#abnf.dependencies" class="smpl">TE</a> ; <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a> 772 775 / <a href="#header.user-agent" class="smpl">User-Agent</a> ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section 10.9</a> 773 776 </pre><p id="rfc.section.4.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new … … 865 868 fields are defined in <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 866 869 </p> 867 <p id="rfc.section.7.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1. 17"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure870 <p id="rfc.section.7.p.2">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure 868 871 safe and proper transfer of the message. 869 872 </p> … … 1030 1033 </p> 1031 1034 <p id="rfc.section.8.8.p.2">TRACE allows the client to see what is being received at the other end of the request chain and use that data for testing 1032 or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1. 18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the1035 or diagnostic information. The value of the Via header field (<a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) is of particular interest, since it acts as a trace of the request chain. Use of the Max-Forwards header field allows the 1033 1036 client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an 1034 1037 infinite loop. 1035 1038 </p> 1036 <p id="rfc.section.8.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> contain the entire request message in the entity-body, with a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 9.3.1</a> of <a href="#Part1" id="rfc.xref.Part1. 19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Responses to this method <em class="bcp14">MUST NOT</em> be cached.1039 <p id="rfc.section.8.8.p.3">If the request is valid, the response <em class="bcp14">SHOULD</em> contain the entire request message in the entity-body, with a Content-Type of "message/http" (see <a href="p1-messaging.html#internet.media.type.message.http" title="Internet Media Type message/http">Section 9.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Responses to this method <em class="bcp14">MUST NOT</em> be cached. 1037 1040 </p> 1038 1041 <div id="rfc.iref.c.1"></div> … … 1063 1066 <p id="rfc.section.9.1.1.p.1">The client <em class="bcp14">SHOULD</em> continue with its request. This interim response is used to inform the client that the initial part of the request has been 1064 1067 received and has not yet been rejected by the server. The client <em class="bcp14">SHOULD</em> continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The 1065 server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.2 0"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.1068 server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code. 1066 1069 </p> 1067 1070 <div id="rfc.iref.26"></div> … … 1446 1449 <p id="rfc.section.9.5.6.p.1">The server does not support, or refuses to support, the protocol version that was used in the request message. The server 1447 1450 is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described 1448 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1.2 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server.1451 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, other than with this error message. The response <em class="bcp14">SHOULD</em> contain an entity describing why that version is not supported and what other protocols are supported by that server. 1449 1452 </p> 1450 1453 <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> … … 1456 1459 <div id="rfc.iref.h.2"></div> 1457 1460 <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a> <a id="header.allow" href="#header.allow">Allow</a></h2> 1458 <p id="rfc.section.10.1.p.1">The Allow response-header fieldlists the set of methods advertised as supported by the resource identified by the Request-URI.1461 <p id="rfc.section.10.1.p.1">The response-header field "Allow" lists the set of methods advertised as supported by the resource identified by the Request-URI. 1459 1462 The purpose of this field is strictly to inform the recipient of valid methods associated with the resource. An Allow header 1460 1463 field <em class="bcp14">MUST</em> be present in a 405 (Method Not Allowed) response. 1461 1464 </p> 1462 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span> <a href="#header.allow" class="smpl">Allow</a> = "Allow" ":" #<a href="#method" class="smpl">Method</a> 1465 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#header.allow" class="smpl">Allow</a> = "Allow" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a> 1466 <a href="#header.allow" class="smpl">Allow-v</a> = #<a href="#method" class="smpl">Method</a> 1463 1467 </pre><p id="rfc.section.10.1.p.3">Example of use:</p> 1464 <div id="rfc.figure.u.14"></div><pre class="text"> 1468 <div id="rfc.figure.u.14"></div><pre class="text"> Allow: GET, HEAD, PUT 1465 1469 </pre><p id="rfc.section.10.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p> 1466 1470 <p id="rfc.section.10.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other … … 1470 1474 <div id="rfc.iref.h.3"></div> 1471 1475 <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a> <a id="header.expect" href="#header.expect">Expect</a></h2> 1472 <p id="rfc.section.10.2.p.1">The Expect request-header field is used to indicate that particular server behaviors are required by the client.</p> 1473 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span> <a href="#header.expect" class="smpl">Expect</a> = "Expect" ":" 1#<a href="#header.expect" class="smpl">expectation</a> 1476 <p id="rfc.section.10.2.p.1">The request-header field "Expect" is used to indicate that particular server behaviors are required by the client.</p> 1477 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> <a href="#header.expect" class="smpl">Expect</a> = "Expect" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a> 1478 <a href="#header.expect" class="smpl">Expect-v</a> = 1#<a href="#header.expect" class="smpl">expectation</a> 1474 1479 1475 <a href="#header.expect" class="smpl">expectation</a> = 1476 <a href="#header.expect" class="smpl">expectation-extension</a> = 1480 <a href="#header.expect" class="smpl">expectation</a> = "100-continue" / <a href="#header.expect" class="smpl">expectation-extension</a> 1481 <a href="#header.expect" class="smpl">expectation-extension</a> = <a href="#notation" class="smpl">token</a> [ "=" ( <a href="#notation" class="smpl">token</a> / <a href="#notation" class="smpl">quoted-string</a> ) 1477 1482 *<a href="#header.expect" class="smpl">expect-params</a> ] 1478 <a href="#header.expect" class="smpl">expect-params</a> = 1483 <a href="#header.expect" class="smpl">expect-params</a> = ";" <a href="#notation" class="smpl">token</a> [ "=" ( <a href="#notation" class="smpl">token</a> / <a href="#notation" class="smpl">quoted-string</a> ) ] 1479 1484 </pre><p id="rfc.section.10.2.p.3">A server that does not understand or is unable to comply with any of the expectation values in the Expect field of a request <em class="bcp14">MUST</em> respond with appropriate error status. The server <em class="bcp14">MUST</em> respond with a 417 (Expectation Failed) status if any of the expectations cannot be met or, if there are other problems with 1480 1485 the request, some other 4xx status. … … 1490 1495 </p> 1491 1496 <p id="rfc.section.10.2.p.7">Many older HTTP/1.0 and HTTP/1.1 applications do not understand the Expect header.</p> 1492 <p id="rfc.section.10.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.2 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.1497 <p id="rfc.section.10.2.p.8">See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status. 1493 1498 </p> 1494 1499 <div id="rfc.iref.f.1"></div> 1495 1500 <div id="rfc.iref.h.4"></div> 1496 1501 <h2 id="rfc.section.10.3"><a href="#rfc.section.10.3">10.3</a> <a id="header.from" href="#header.from">From</a></h2> 1497 <p id="rfc.section.10.3.p.1">The From request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>: 1498 </p> 1499 <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.14"></span> <a href="#header.from" class="smpl">From</a> = "From" ":" <a href="#header.from" class="smpl">mailbox</a> 1502 <p id="rfc.section.10.3.p.1">The request-header field "From", if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>: 1503 </p> 1504 <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> <a href="#header.from" class="smpl">From</a> = "From" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a> 1505 <a href="#header.from" class="smpl">From-v</a> = <a href="#header.from" class="smpl">mailbox</a> 1500 1506 1501 1507 <a href="#header.from" class="smpl">mailbox</a> = <mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>> 1502 1508 </pre><p id="rfc.section.10.3.p.3">An example is:</p> 1503 <div id="rfc.figure.u.17"></div><pre class="text"> 1509 <div id="rfc.figure.u.17"></div><pre class="text"> From: webmaster@example.org 1504 1510 </pre><p id="rfc.section.10.3.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed 1505 1511 on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header so that the person responsible for running the robot can be contacted if problems occur on the receiving … … 1516 1522 <div id="rfc.iref.h.5"></div> 1517 1523 <h2 id="rfc.section.10.4"><a href="#rfc.section.10.4">10.4</a> <a id="header.location" href="#header.location">Location</a></h2> 1518 <p id="rfc.section.10.4.p.1">The Location response-header fieldis used for the identification of a new resource or to redirect the recipient to a location1524 <p id="rfc.section.10.4.p.1">The response-header field "Location" is used for the identification of a new resource or to redirect the recipient to a location 1519 1525 other than the Request-URI for completion of the request. For 201 (Created) responses, the Location is that of the new resource 1520 1526 which was created by the request. For 3xx responses, the location <em class="bcp14">SHOULD</em> indicate the server's preferred URI for automatic redirection to the resource. The field value consists of a single absolute 1521 1527 URI. 1522 1528 </p> 1523 <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.15"></span> <a href="#header.location" class="smpl">Location</a> = "Location" ":" <a href="#abnf.dependencies" class="smpl">absoluteURI</a> [ "#" <a href="#abnf.dependencies" class="smpl">fragment</a> ] 1529 <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span> <a href="#header.location" class="smpl">Location</a> = "Location" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a> 1530 <a href="#header.location" class="smpl">Location-v</a> = <a href="#abnf.dependencies" class="smpl">absoluteURI</a> [ "#" <a href="#abnf.dependencies" class="smpl">fragment</a> ] 1524 1531 </pre><p id="rfc.section.10.4.p.3">An example is:</p> 1525 <div id="rfc.figure.u.19"></div><pre class="text"> 1532 <div id="rfc.figure.u.19"></div><pre class="text"> Location: http://www.example.org/pub/WWW/People.html 1526 1533 </pre><p id="rfc.section.10.4.p.5"> </p> 1527 1534 <dl class="empty"> … … 1541 1548 <div id="rfc.iref.h.6"></div> 1542 1549 <h2 id="rfc.section.10.5"><a href="#rfc.section.10.5">10.5</a> <a id="header.max-forwards" href="#header.max-forwards">Max-Forwards</a></h2> 1543 <p id="rfc.section.10.5.p.1">The Max-Forwards request-headerfield provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section 8.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section 8.2</a>) methods to limit the number of proxies or gateways that can forward the request to the next inbound server. This can be1550 <p id="rfc.section.10.5.p.1">The request-header "Max-Forwards" field provides a mechanism with the TRACE (<a href="#TRACE" id="rfc.xref.TRACE.2" title="TRACE">Section 8.8</a>) and OPTIONS (<a href="#OPTIONS" id="rfc.xref.OPTIONS.2" title="OPTIONS">Section 8.2</a>) methods to limit the number of proxies or gateways that can forward the request to the next inbound server. This can be 1544 1551 useful when the client is attempting to trace a request chain which appears to be failing or looping in mid-chain. 1545 1552 </p> 1546 <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.16"></span> <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = "Max-Forwards" ":" 1*<a href="#notation" class="smpl">DIGIT</a> 1553 <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span> <a href="#header.max-forwards" class="smpl">Max-Forwards</a> = "Max-Forwards" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> 1554 <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 1547 1555 </pre><p id="rfc.section.10.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message may be forwarded.</p> 1548 1556 <p id="rfc.section.10.5.p.4">Each proxy or gateway recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1). … … 1554 1562 <div id="rfc.iref.h.7"></div> 1555 1563 <h2 id="rfc.section.10.6"><a href="#rfc.section.10.6">10.6</a> <a id="header.referer" href="#header.referer">Referer</a></h2> 1556 <p id="rfc.section.10.6.p.1">The Referer[sic] request-header field allows the client to specify, for the server's benefit, the address (URI) of the resource1557 from which the Request-URI was obtained (the "referrer", although the header field is misspelled.) The Referer request-header1564 <p id="rfc.section.10.6.p.1">The request-header field "Referer" [sic] allows the client to specify, for the server's benefit, the address (URI) of the 1565 resource from which the Request-URI was obtained (the "referrer", although the header field is misspelled.) The Referer request-header 1558 1566 allows a server to generate lists of back-links to resources for interest, logging, optimized caching, etc. It also allows 1559 1567 obsolete or mistyped links to be traced for maintenance. The Referer field <em class="bcp14">MUST NOT</em> be sent if the Request-URI was obtained from a source that does not have its own URI, such as input from the user keyboard. 1560 1568 </p> 1561 <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.17"></span> <a href="#header.referer" class="smpl">Referer</a> = "Referer" ":" ( <a href="#abnf.dependencies" class="smpl">absoluteURI</a> / <a href="#abnf.dependencies" class="smpl">relativeURI</a> ) 1569 <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.referer" class="smpl">Referer</a> = "Referer" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a> 1570 <a href="#header.referer" class="smpl">Referer-v</a> = <a href="#abnf.dependencies" class="smpl">absoluteURI</a> / <a href="#abnf.dependencies" class="smpl">relativeURI</a> 1562 1571 </pre><p id="rfc.section.10.6.p.3">Example:</p> 1563 <div id="rfc.figure.u.22"></div><pre class="text"> 1572 <div id="rfc.figure.u.22"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html 1564 1573 </pre><p id="rfc.section.10.6.p.5">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the Request-URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 12.2</a> for security considerations. 1565 1574 </p> … … 1567 1576 <div id="rfc.iref.h.8"></div> 1568 1577 <h2 id="rfc.section.10.7"><a href="#rfc.section.10.7">10.7</a> <a id="header.retry-after" href="#header.retry-after">Retry-After</a></h2> 1569 <p id="rfc.section.10.7.p.1">The Retry-After response-headerfield can be used with a 503 (Service Unavailable) response to indicate how long the service1578 <p id="rfc.section.10.7.p.1">The response-header "Retry-After" field can be used with a 503 (Service Unavailable) response to indicate how long the service 1570 1579 is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any 3xx (Redirection) response to indicate the minimum time the user-agent is asked wait before issuing 1571 1580 the redirected request. The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after 1572 1581 the time of the response. 1573 1582 </p> 1574 <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.18"></span> <a href="#header.retry-after" class="smpl">Retry-After</a> = "Retry-After" ":" ( <a href="#abnf.dependencies" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> ) 1583 <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> <a href="#header.retry-after" class="smpl">Retry-After</a> = "Retry-After" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a> 1584 <a href="#header.retry-after" class="smpl">Retry-After-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> 1575 1585 </pre><div id="rule.delta-seconds"> 1576 1586 <p id="rfc.section.10.7.p.3"> Time spans are non-negative decimal integers, representing time in seconds.</p> 1577 1587 </div> 1578 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g. 19"></span> <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#notation" class="smpl">DIGIT</a>1588 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.26"></span> <a href="#rule.delta-seconds" class="smpl">delta-seconds</a> = 1*<a href="#notation" class="smpl">DIGIT</a> 1579 1589 </pre><p id="rfc.section.10.7.p.5">Two examples of its use are</p> 1580 <div id="rfc.figure.u.25"></div><pre class="text"> 1581 1590 <div id="rfc.figure.u.25"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 1591 Retry-After: 120 1582 1592 </pre><p id="rfc.section.10.7.p.7">In the latter example, the delay is 2 minutes.</p> 1583 1593 <div id="rfc.iref.s.43"></div> 1584 1594 <div id="rfc.iref.h.9"></div> 1585 1595 <h2 id="rfc.section.10.8"><a href="#rfc.section.10.8">10.8</a> <a id="header.server" href="#header.server">Server</a></h2> 1586 <p id="rfc.section.10.8.p.1">The Server response-header fieldcontains information about the software used by the origin server to handle the request.1587 The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.2 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance1596 <p id="rfc.section.10.8.p.1">The response-header field "Server" contains information about the software used by the origin server to handle the request. 1597 The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the server and any significant subproducts. The product tokens are listed in order of their significance 1588 1598 for identifying the application. 1589 1599 </p> 1590 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.20"></span> <a href="#header.server" class="smpl">Server</a> = "Server" ":" 1*( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#notation" class="smpl">comment</a> ) 1600 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span> <a href="#header.server" class="smpl">Server</a> = "Server" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a> 1601 <a href="#header.server" class="smpl">Server-v</a> = 1*( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#notation" class="smpl">comment</a> ) 1591 1602 </pre><p id="rfc.section.10.8.p.3">Example:</p> 1592 <div id="rfc.figure.u.27"></div><pre class="text"> 1593 </pre><p id="rfc.section.10.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.2 4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).1603 <div id="rfc.figure.u.27"></div><pre class="text"> Server: CERN/3.0 libwww/2.17 1604 </pre><p id="rfc.section.10.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 1594 1605 </p> 1595 1606 <dl class="empty"> … … 1602 1613 <div id="rfc.iref.h.10"></div> 1603 1614 <h2 id="rfc.section.10.9"><a href="#rfc.section.10.9">10.9</a> <a id="header.user-agent" href="#header.user-agent">User-Agent</a></h2> 1604 <p id="rfc.section.10.9.p.1">The User-Agent request-header fieldcontains information about the user agent originating the request. This is for statistical1615 <p id="rfc.section.10.9.p.1">The request-header field "User-Agent" contains information about the user agent originating the request. This is for statistical 1605 1616 purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses 1606 to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.2 5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the1617 to avoid particular user agent limitations. User agents <em class="bcp14">SHOULD</em> include this field with requests. The field can contain multiple product tokens (<a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a> of <a href="#Part1" id="rfc.xref.Part1.28"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the 1607 1618 product tokens are listed in order of their significance for identifying the application. 1608 1619 </p> 1609 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.21"></span> <a href="#header.user-agent" class="smpl">User-Agent</a> = "User-Agent" ":" 1*( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#notation" class="smpl">comment</a> ) 1620 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span> <a href="#header.user-agent" class="smpl">User-Agent</a> = "User-Agent" <a href="#notation" class="smpl">BWS</a> ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a> 1621 <a href="#header.user-agent" class="smpl">User-Agent-v</a> = 1*( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#notation" class="smpl">comment</a> ) 1610 1622 </pre><p id="rfc.section.10.9.p.3">Example:</p> 1611 <div id="rfc.figure.u.29"></div><pre class="text"> 1623 <div id="rfc.figure.u.29"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1612 1624 </pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 1613 1625 <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a> <a id="method.registration" href="#method.registration">Method Registry</a></h2> … … 2216 2228 </p> 2217 2229 <p id="rfc.section.A.2.p.7">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly 2218 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.2 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 10.8</a>)2230 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section 10.8</a>) 2219 2231 </p> 2220 2232 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> … … 2320 2332 <ul> 2321 2333 <li>Use "/" instead of "|" for alternatives.</li> 2334 <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS"), but do 2335 not use them yet. 2336 </li> 2337 <li>Rewrite header ABNFs to spell out whitespace rules, factor out value format definitions.</li> 2322 2338 </ul> 2323 2339 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> … … 2431 2447 <ul class="ind"> 2432 2448 <li class="indline1"><tt>Allow</tt> <a class="iref" href="#rfc.iref.g.9"><b>10.1</b></a></li> 2433 <li class="indline1"><tt>delta-seconds</tt> <a class="iref" href="#rfc.iref.g.19"><b>10.7</b></a></li> 2434 <li class="indline1"><tt>Expect</tt> <a class="iref" href="#rfc.iref.g.10"><b>10.2</b></a></li> 2435 <li class="indline1"><tt>expect-params</tt> <a class="iref" href="#rfc.iref.g.13"><b>10.2</b></a></li> 2436 <li class="indline1"><tt>expectation</tt> <a class="iref" href="#rfc.iref.g.11"><b>10.2</b></a></li> 2437 <li class="indline1"><tt>expectation-extension</tt> <a class="iref" href="#rfc.iref.g.12"><b>10.2</b></a></li> 2449 <li class="indline1"><tt>Allow-v</tt> <a class="iref" href="#rfc.iref.g.10"><b>10.1</b></a></li> 2450 <li class="indline1"><tt>delta-seconds</tt> <a class="iref" href="#rfc.iref.g.26"><b>10.7</b></a></li> 2451 <li class="indline1"><tt>Expect</tt> <a class="iref" href="#rfc.iref.g.11"><b>10.2</b></a></li> 2452 <li class="indline1"><tt>expect-params</tt> <a class="iref" href="#rfc.iref.g.15"><b>10.2</b></a></li> 2453 <li class="indline1"><tt>Expect-v</tt> <a class="iref" href="#rfc.iref.g.12"><b>10.2</b></a></li> 2454 <li class="indline1"><tt>expectation</tt> <a class="iref" href="#rfc.iref.g.13"><b>10.2</b></a></li> 2455 <li class="indline1"><tt>expectation-extension</tt> <a class="iref" href="#rfc.iref.g.14"><b>10.2</b></a></li> 2438 2456 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.5"><b>5</b></a></li> 2439 2457 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.2"><b>3</b></a></li> 2440 <li class="indline1"><tt>From</tt> <a class="iref" href="#rfc.iref.g.14"><b>10.3</b></a></li> 2441 <li class="indline1"><tt>Location</tt> <a class="iref" href="#rfc.iref.g.15"><b>10.4</b></a></li> 2442 <li class="indline1"><tt>Max-Forwards</tt> <a class="iref" href="#rfc.iref.g.16"><b>10.5</b></a></li> 2458 <li class="indline1"><tt>From</tt> <a class="iref" href="#rfc.iref.g.16"><b>10.3</b></a></li> 2459 <li class="indline1"><tt>From-v</tt> <a class="iref" href="#rfc.iref.g.17"><b>10.3</b></a></li> 2460 <li class="indline1"><tt>Location</tt> <a class="iref" href="#rfc.iref.g.18"><b>10.4</b></a></li> 2461 <li class="indline1"><tt>Location-v</tt> <a class="iref" href="#rfc.iref.g.19"><b>10.4</b></a></li> 2462 <li class="indline1"><tt>Max-Forwards</tt> <a class="iref" href="#rfc.iref.g.20"><b>10.5</b></a></li> 2463 <li class="indline1"><tt>Max-Forwards-v</tt> <a class="iref" href="#rfc.iref.g.21"><b>10.5</b></a></li> 2443 2464 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.1"><b>3</b></a></li> 2444 2465 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.6"><b>5</b></a></li> 2445 <li class="indline1"><tt>Referer</tt> <a class="iref" href="#rfc.iref.g.17"><b>10.6</b></a></li> 2466 <li class="indline1"><tt>Referer</tt> <a class="iref" href="#rfc.iref.g.22"><b>10.6</b></a></li> 2467 <li class="indline1"><tt>Referer-v</tt> <a class="iref" href="#rfc.iref.g.23"><b>10.6</b></a></li> 2446 2468 <li class="indline1"><tt>request-header</tt> <a class="iref" href="#rfc.iref.g.3"><b>4</b></a></li> 2447 2469 <li class="indline1"><tt>response-header</tt> <a class="iref" href="#rfc.iref.g.7"><b>6</b></a></li> 2448 <li class="indline1"><tt>Retry-After</tt> <a class="iref" href="#rfc.iref.g.18"><b>10.7</b></a></li> 2449 <li class="indline1"><tt>Server</tt> <a class="iref" href="#rfc.iref.g.20"><b>10.8</b></a></li> 2470 <li class="indline1"><tt>Retry-After</tt> <a class="iref" href="#rfc.iref.g.24"><b>10.7</b></a></li> 2471 <li class="indline1"><tt>Retry-After-v</tt> <a class="iref" href="#rfc.iref.g.25"><b>10.7</b></a></li> 2472 <li class="indline1"><tt>Server</tt> <a class="iref" href="#rfc.iref.g.27"><b>10.8</b></a></li> 2473 <li class="indline1"><tt>Server-v</tt> <a class="iref" href="#rfc.iref.g.28"><b>10.8</b></a></li> 2450 2474 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.4"><b>5</b></a></li> 2451 <li class="indline1"><tt>User-Agent</tt> <a class="iref" href="#rfc.iref.g.21"><b>10.9</b></a></li> 2475 <li class="indline1"><tt>User-Agent</tt> <a class="iref" href="#rfc.iref.g.29"><b>10.9</b></a></li> 2476 <li class="indline1"><tt>User-Agent-v</tt> <a class="iref" href="#rfc.iref.g.30"><b>10.9</b></a></li> 2452 2477 </ul> 2453 2478 </li> … … 2504 2529 </li> 2505 2530 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 2506 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.15"> 4</a>, <a class="iref" href="#rfc.xref.Part1.16">4</a>, <a class="iref" href="#rfc.xref.Part1.17">7</a>, <a class="iref" href="#rfc.xref.Part1.18">8.8</a>, <a class="iref" href="#rfc.xref.Part1.19">8.8</a>, <a class="iref" href="#rfc.xref.Part1.20">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.21">9.5.6</a>, <a class="iref" href="#rfc.xref.Part1.22">10.2</a>, <a class="iref" href="#rfc.xref.Part1.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.8</a>, <a class="iref" href="#rfc.xref.Part1.25">10.9</a>, <a class="iref" href="#Part1"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part1.26">A.2</a><ul class="ind">2531 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.15">2</a>, <a class="iref" href="#rfc.xref.Part1.16">2</a>, <a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.18">4</a>, <a class="iref" href="#rfc.xref.Part1.19">4</a>, <a class="iref" href="#rfc.xref.Part1.20">7</a>, <a class="iref" href="#rfc.xref.Part1.21">8.8</a>, <a class="iref" href="#rfc.xref.Part1.22">8.8</a>, <a class="iref" href="#rfc.xref.Part1.23">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.24">9.5.6</a>, <a class="iref" href="#rfc.xref.Part1.25">10.2</a>, <a class="iref" href="#rfc.xref.Part1.26">10.8</a>, <a class="iref" href="#rfc.xref.Part1.27">10.8</a>, <a class="iref" href="#rfc.xref.Part1.28">10.9</a>, <a class="iref" href="#Part1"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part1.29">A.2</a><ul class="ind"> 2507 2532 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.2">2</a></li> 2508 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a> </li>2509 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part1.2 1">9.5.6</a></li>2510 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1. 8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a></li>2511 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1.1 1">2</a></li>2512 <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part1.1 2">2</a>, <a class="iref" href="#rfc.xref.Part1.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.25">10.9</a></li>2513 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1. 17">7</a></li>2514 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.2 0">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.22">10.2</a></li>2515 <li class="indline1"><em>Section 8.4</em> <a class="iref" href="#rfc.xref.Part1.1 0">2</a>, <a class="iref" href="#rfc.xref.Part1.15">4</a></li>2516 <li class="indline1"><em>Section 8.8</em> <a class="iref" href="#rfc.xref.Part1.1 4">2</a>, <a class="iref" href="#rfc.xref.Part1.16">4</a></li>2517 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part1. 18">8.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.8</a>, <a class="iref" href="#rfc.xref.Part1.26">A.2</a></li>2518 <li class="indline1"><em>Section 9.3.1</em> <a class="iref" href="#rfc.xref.Part1. 19">8.8</a></li>2533 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a></li> 2534 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part1.24">9.5.6</a></li> 2535 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.16">2</a></li> 2536 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1.14">2</a></li> 2537 <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part1.15">2</a>, <a class="iref" href="#rfc.xref.Part1.26">10.8</a>, <a class="iref" href="#rfc.xref.Part1.28">10.9</a></li> 2538 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.20">7</a></li> 2539 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.23">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.25">10.2</a></li> 2540 <li class="indline1"><em>Section 8.4</em> <a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.18">4</a></li> 2541 <li class="indline1"><em>Section 8.8</em> <a class="iref" href="#rfc.xref.Part1.17">2</a>, <a class="iref" href="#rfc.xref.Part1.19">4</a></li> 2542 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part1.21">8.8</a>, <a class="iref" href="#rfc.xref.Part1.27">10.8</a>, <a class="iref" href="#rfc.xref.Part1.29">A.2</a></li> 2543 <li class="indline1"><em>Section 9.3.1</em> <a class="iref" href="#rfc.xref.Part1.22">8.8</a></li> 2519 2544 </ul> 2520 2545 </li>
Note: See TracChangeset
for help on using the changeset viewer.