Changeset 206 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 09/02/08 22:03:01 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r205 r206 633 633 quoted-string = <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>> 634 634 token = <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>> 635 </pre><p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p> 636 <div id="rfc.figure.u.3"></div><pre class="inline"> absoluteURI = <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>> 637 Accept = <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>> 638 Accept-Charset = 639 <Accept-Charset, defined in <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a>> 640 Accept-Encoding = 641 <Accept-Encoding, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a>> 642 Accept-Language = 643 <Accept-Language, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a>> 644 Accept-Ranges = <Accept-Ranges, defined in <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 6.1</a>> 645 Age = <Age, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a>> 646 Authorization = <Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a>> 647 delta-seconds = <delta-seconds, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a>> 648 ETag = <ETag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a>> 649 fragment = <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>> 650 HTTP-date = <HTTP-date, 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#full.date" title="Full Date">Section 3.3.1</a>> 651 Host = <Host, 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#header.host" title="Host">Section 8.4</a>> 652 If-Match = <If-Match, defined in <a href="#Part4" id="rfc.xref.Part4.2"><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>> 653 If-Modified-Since = 654 <If-Modified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.3"><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>> 655 If-None-Match = <If-None-Match, defined in <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 7.4</a>> 656 If-Range = <If-Range, defined in <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 6.3</a>> 657 If-Unmodified-Since = 658 <If-Unmodified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 7.5</a>> 659 product = <product, 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#product.tokens" title="Product Tokens">Section 3.5</a>> 660 Proxy-Authenticate = 661 <Proxy-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a>> 662 Proxy-Authorization = 663 <Proxy-Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.3"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a>> 664 Range = <Range, defined in <a href="#Part5" id="rfc.xref.Part5.3"><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>> 665 relativeURI = <relativeURI, 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#general.syntax" title="General Syntax">Section 3.2.1</a>> 666 TE = <TE, 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#header.upgrade" title="Upgrade">Section 8.8</a>> 667 Vary = <Vary, defined in <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.vary" title="Vary">Section 16.5</a>> 668 WWW-Authenticate = 669 <WWW-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a>> 635 670 </pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="method" href="#method">Method</a></h1> 636 671 <p id="rfc.section.3.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> 637 <div id="rfc.figure.u. 3"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span> Method = "OPTIONS" ; <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section 8.2</a>672 <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span> Method = "OPTIONS" ; <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section 8.2</a> 638 673 | "GET" ; <a href="#GET" id="rfc.xref.GET.1" title="GET">Section 8.3</a> 639 674 | "HEAD" ; <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section 8.4</a> … … 655 690 method invocation. 656 691 </p> 657 <div id="rfc.figure.u. 4"></div><pre class="inline"><span id="rfc.iref.g.3"></span> request-header = Accept ; <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>658 | Accept-Charset ; <a href="#Part3" id="rfc.xref.Part3. 2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a>659 | Accept-Encoding ; <a href="#Part3" id="rfc.xref.Part3. 3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a>660 | Accept-Language ; <a href="#Part3" id="rfc.xref.Part3. 4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a>661 | Authorization ; <a href="#Part7" id="rfc.xref.Part7. 1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a>692 <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.3"></span> request-header = Accept ; <a href="#Part3" id="rfc.xref.Part3.5"><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> 693 | Accept-Charset ; <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a> 694 | Accept-Encoding ; <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a> 695 | Accept-Language ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a> 696 | Authorization ; <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> 662 697 | Expect ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section 10.2</a> 663 698 | From ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section 10.3</a> 664 | Host ; <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#header.host" title="Host">Section 8.4</a>665 | If-Match ; <a href="#Part4" id="rfc.xref.Part4. 1"><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>666 | If-Modified-Since ; <a href="#Part4" id="rfc.xref.Part4. 2"><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>667 | If-None-Match ; <a href="#Part4" id="rfc.xref.Part4. 3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 7.4</a>668 | If-Range ; <a href="#Part5" id="rfc.xref.Part5. 1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 6.3</a>669 | If-Unmodified-Since ; <a href="#Part4" id="rfc.xref.Part4. 4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 7.5</a>699 | Host ; <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#header.host" title="Host">Section 8.4</a> 700 | If-Match ; <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> 701 | If-Modified-Since ; <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> 702 | If-None-Match ; <a href="#Part4" id="rfc.xref.Part4.8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 7.4</a> 703 | If-Range ; <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 6.3</a> 704 | If-Unmodified-Since ; <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 7.5</a> 670 705 | Max-Forwards ; <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section 10.5</a> 671 | Proxy-Authorization ; <a href="#Part7" id="rfc.xref.Part7. 2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a>672 | Range ; <a href="#Part5" id="rfc.xref.Part5. 2"><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>706 | Proxy-Authorization ; <a href="#Part7" id="rfc.xref.Part7.6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a> 707 | Range ; <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> 673 708 | Referer ; <a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section 10.6</a> 674 | TE ; <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#header.upgrade" title="Upgrade">Section 8.8</a>709 | TE ; <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#header.upgrade" title="Upgrade">Section 8.8</a> 675 710 | User-Agent ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section 10.9</a> 676 711 </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 … … 686 721 are presented below. The reason phrases listed here are only recommendations -- they <em class="bcp14">MAY</em> be replaced by local equivalents without affecting the protocol. 687 722 </p> 688 <div id="rfc.figure.u. 5"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> Status-Code =723 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> Status-Code = 689 724 "100" ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section 9.1.1</a>: Continue 690 725 | "101" ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section 9.1.2</a>: Switching Protocols … … 742 777 the Request-URI. 743 778 </p> 744 <div id="rfc.figure.u. 6"></div><pre class="inline"><span id="rfc.iref.g.7"></span> response-header = Accept-Ranges ; <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 6.1</a>745 | Age ; <a href="#Part6" id="rfc.xref.Part6. 1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a>746 | ETag ; <a href="#Part4" id="rfc.xref.Part4. 5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a>779 <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.7"></span> response-header = Accept-Ranges ; <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 6.1</a> 780 | Age ; <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a> 781 | ETag ; <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a> 747 782 | Location ; <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section 10.4</a> 748 | Proxy-Authenticate ; <a href="#Part7" id="rfc.xref.Part7. 3"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a>783 | Proxy-Authenticate ; <a href="#Part7" id="rfc.xref.Part7.7"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a> 749 784 | Retry-After ; <a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section 10.7</a> 750 785 | Server ; <a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section 10.8</a> 751 | Vary ; <a href="#Part6" id="rfc.xref.Part6. 2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a>752 | WWW-Authenticate ; <a href="#Part7" id="rfc.xref.Part7. 4"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a>786 | Vary ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a> 787 | WWW-Authenticate ; <a href="#Part7" id="rfc.xref.Part7.8"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a> 753 788 </pre><p id="rfc.section.6.p.3">Response-header field names can be extended reliably only in combination with a change in the protocol version. However, new 754 789 or experimental header fields <em class="bcp14">MAY</em> be given the semantics of response-header fields if all parties in the communication recognize them to be response-header … … 758 793 <p id="rfc.section.7.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer an entity if not otherwise restricted by the request method or response status code. An entity consists of entity-header 759 794 fields and an entity-body, although some responses will only include the entity-headers. HTTP entity-body and entity-header 760 fields are defined in <a href="#Part3" id="rfc.xref.Part3. 5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.761 </p> 762 <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.1 0"><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 ensure795 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>. 796 </p> 797 <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 ensure 763 798 safe and proper transfer of the message. 764 799 </p> … … 836 871 </p> 837 872 <p id="rfc.section.8.3.p.3">The semantics of the GET method change to a "partial GET" if the request message includes a Range header field. A partial 838 GET requests that only part of the entity be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5. 4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed873 GET requests that only part of the entity be transferred, as described in <a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. The partial GET method is intended to reduce unnecessary network usage by allowing partially-retrieved entities to be completed 839 874 without transferring data already held by the client. 840 875 </p> 841 <p id="rfc.section.8.3.p.4">The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching described in <a href="#Part6" id="rfc.xref.Part6. 3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.876 <p id="rfc.section.8.3.p.4">The response to a GET request is cacheable if and only if it meets the requirements for HTTP caching described in <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. 842 877 </p> 843 878 <p id="rfc.section.8.3.p.5">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section 12.2</a> for security considerations when used for forms. … … 924 959 </p> 925 960 <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 926 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.1 1"><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 the961 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 the 927 962 client to limit the length of the request chain, which is useful for testing a chain of proxies forwarding messages in an 928 963 infinite loop. … … 957 992 <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 958 993 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 959 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.1 2"><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.994 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.19"><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. 960 995 </p> 961 996 <div id="rfc.iref.24"></div> 962 997 <div id="rfc.iref.s.2"></div> 963 998 <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a> <a id="status.101" href="#status.101">101 Switching Protocols</a></h3> 964 <p id="rfc.section.9.1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5. 5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined999 <p id="rfc.section.9.1.2.p.1">The server understands and is willing to comply with the client's request, via the Upgrade message header field (<a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.8"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>), for a change in the application protocol being used on this connection. The server will switch protocols to those defined 965 1000 by the response's Upgrade header field immediately after the empty line which terminates the 101 response. 966 1001 </p> … … 997 1032 </p> 998 1033 <p id="rfc.section.9.2.2.p.2">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity tag for the requested variant just created, 999 see <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a> of <a href="#Part4" id="rfc.xref.Part4. 6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.1034 see <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a> of <a href="#Part4" id="rfc.xref.Part4.11"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. 1000 1035 </p> 1001 1036 <div id="rfc.iref.27"></div> … … 1041 1076 <h3 id="rfc.section.9.2.7"><a href="#rfc.section.9.2.7">9.2.7</a> <a id="status.206" href="#status.206">206 Partial Content</a></h3> 1042 1077 <p id="rfc.section.9.2.7.p.1">The server has fulfilled the partial GET request for the resource and the enclosed entity is a partial representation as defined 1043 in <a href="#Part5" id="rfc.xref.Part5. 6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.1078 in <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>. 1044 1079 </p> 1045 1080 <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a> <a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2> … … 1057 1092 <h3 id="rfc.section.9.3.1"><a href="#rfc.section.9.3.1">9.3.1</a> <a id="status.300" href="#status.300">300 Multiple Choices</a></h3> 1058 1093 <p id="rfc.section.9.3.1.p.1">The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven 1059 negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3. 6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that1094 negotiation information (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that 1060 1095 location. 1061 1096 </p> … … 1119 1154 <h3 id="rfc.section.9.3.5"><a href="#rfc.section.9.3.5">9.3.5</a> <a id="status.304" href="#status.304">304 Not Modified</a></h3> 1120 1155 <p id="rfc.section.9.3.5.p.1">The response to the request has not been modified since the conditions indicated by the client's conditional GET request, 1121 as defined in <a href="#Part4" id="rfc.xref.Part4. 7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.1156 as defined in <a href="#Part4" id="rfc.xref.Part4.12"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. 1122 1157 </p> 1123 1158 <div id="rfc.iref.37"></div> … … 1166 1201 <div id="rfc.iref.s.19"></div> 1167 1202 <h3 id="rfc.section.9.4.2"><a href="#rfc.section.9.4.2">9.4.2</a> <a id="status.401" href="#status.401">401 Unauthorized</a></h3> 1168 <p id="rfc.section.9.4.2.p.1">The request requires user authentication (see <a href="#Part7" id="rfc.xref.Part7. 5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).1203 <p id="rfc.section.9.4.2.p.1">The request requires user authentication (see <a href="#Part7" id="rfc.xref.Part7.9"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>). 1169 1204 </p> 1170 1205 <div id="rfc.iref.42"></div> … … 1213 1248 <div id="rfc.iref.s.25"></div> 1214 1249 <h3 id="rfc.section.9.4.8"><a href="#rfc.section.9.4.8">9.4.8</a> <a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h3> 1215 <p id="rfc.section.9.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="#Part7" id="rfc.xref.Part7. 6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).1250 <p id="rfc.section.9.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="#Part7" id="rfc.xref.Part7.10"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>). 1216 1251 </p> 1217 1252 <div id="rfc.iref.48"></div> … … 1256 1291 <h3 id="rfc.section.9.4.13"><a href="#rfc.section.9.4.13">9.4.13</a> <a id="status.412" href="#status.412">412 Precondition Failed</a></h3> 1257 1292 <p id="rfc.section.9.4.13.p.1">The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server, as 1258 defined in <a href="#Part4" id="rfc.xref.Part4. 8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.1293 defined in <a href="#Part4" id="rfc.xref.Part4.13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. 1259 1294 </p> 1260 1295 <div id="rfc.iref.53"></div> … … 1284 1319 <div id="rfc.iref.s.34"></div> 1285 1320 <h3 id="rfc.section.9.4.17"><a href="#rfc.section.9.4.17">9.4.17</a> <a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3> 1286 <p id="rfc.section.9.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5. 7"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource.1321 <p id="rfc.section.9.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 6.4</a> of <a href="#Part5" id="rfc.xref.Part5.10"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource. 1287 1322 </p> 1288 1323 <div id="rfc.iref.57"></div> … … 1339 1374 <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 1340 1375 is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described 1341 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</a> of <a href="#Part1" id="rfc.xref.Part1. 13"><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.1376 in <a href="p1-messaging.html#http.version" title="HTTP Version">Section 3.1</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>, 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. 1342 1377 </p> 1343 1378 <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> … … 1352 1387 of this field is strictly to inform the recipient of valid methods associated with the resource. An Allow header field <em class="bcp14">MUST</em> be present in a 405 (Method Not Allowed) response. 1353 1388 </p> 1354 <div id="rfc.figure.u. 7"></div><pre class="inline"><span id="rfc.iref.g.9"></span> Allow = "Allow" ":" #Method1389 <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.9"></span> Allow = "Allow" ":" #Method 1355 1390 </pre><p id="rfc.section.10.1.p.3">Example of use:</p> 1356 <div id="rfc.figure.u. 8"></div><pre class="text"> Allow: GET, HEAD, PUT1391 <div id="rfc.figure.u.9"></div><pre class="text"> Allow: GET, HEAD, PUT 1357 1392 </pre><p id="rfc.section.10.1.p.5">This field cannot prevent a client from trying other methods. However, the indications given by the Allow header field value <em class="bcp14">SHOULD</em> be followed. The actual set of allowed methods is defined by the origin server at the time of each request. 1358 1393 </p> … … 1367 1402 <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> 1368 1403 <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> 1369 <div id="rfc.figure.u. 9"></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> Expect = "Expect" ":" 1#expectation1404 <div id="rfc.figure.u.10"></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> Expect = "Expect" ":" 1#expectation 1370 1405 1371 1406 expectation = "100-continue" | expectation-extension … … 1386 1421 </p> 1387 1422 <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> 1388 <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. 14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status.1423 <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.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the use of the 100 (Continue) status. 1389 1424 </p> 1390 1425 <div id="rfc.iref.f.1"></div> … … 1393 1428 <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/rfc2822#section-3.4">Section 3.4</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</cite></a>: 1394 1429 </p> 1395 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.14"></span> From = "From" ":" mailbox 1430 <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.14"></span> From = "From" ":" mailbox 1431 1432 mailbox = <mailbox, defined in <a href="#RFC2822" id="rfc.xref.RFC2822.2"><cite title="Internet Message Format">[RFC2822]</cite></a>, <a href="http://tools.ietf.org/html/rfc2822#section-3.4">Section 3.4</a>> 1396 1433 </pre><p id="rfc.section.10.3.p.3">An example is:</p> 1397 <div id="rfc.figure.u.1 1"></div><pre class="text"> From: webmaster@example.org1434 <div id="rfc.figure.u.12"></div><pre class="text"> From: webmaster@example.org 1398 1435 </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 1399 1436 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 … … 1415 1452 URI. 1416 1453 </p> 1417 <div id="rfc.figure.u.1 2"></div><pre class="inline"><span id="rfc.iref.g.15"></span> Location = "Location" ":" absoluteURI [ "#" fragment ]1454 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.15"></span> Location = "Location" ":" absoluteURI [ "#" fragment ] 1418 1455 </pre><p id="rfc.section.10.4.p.3">An example is:</p> 1419 <div id="rfc.figure.u.1 3"></div><pre class="text"> Location: http://www.example.org/pub/WWW/People.html1456 <div id="rfc.figure.u.14"></div><pre class="text"> Location: http://www.example.org/pub/WWW/People.html 1420 1457 </pre><p id="rfc.section.10.4.p.5"> </p> 1421 1458 <dl class="empty"> 1422 <dd> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3. 7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the request.1459 <dd> <b>Note:</b> The Content-Location header field (<a href="p3-payload.html#header.content-location" title="Content-Location">Section 6.7</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) differs from Location in that the Content-Location identifies the original location of the entity enclosed in the request. 1423 1460 It is therefore possible for a response to contain header fields for both Location and Content-Location. 1424 1461 </dd> … … 1438 1475 useful when the client is attempting to trace a request chain which appears to be failing or looping in mid-chain. 1439 1476 </p> 1440 <div id="rfc.figure.u.1 4"></div><pre class="inline"><span id="rfc.iref.g.16"></span> Max-Forwards = "Max-Forwards" ":" 1*DIGIT1477 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span> Max-Forwards = "Max-Forwards" ":" 1*DIGIT 1441 1478 </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> 1442 1479 <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). … … 1453 1490 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. 1454 1491 </p> 1455 <div id="rfc.figure.u.1 5"></div><pre class="inline"><span id="rfc.iref.g.17"></span> Referer = "Referer" ":" ( absoluteURI | relativeURI )1492 <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span> Referer = "Referer" ":" ( absoluteURI | relativeURI ) 1456 1493 </pre><p id="rfc.section.10.6.p.3">Example:</p> 1457 <div id="rfc.figure.u.1 6"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html1494 <div id="rfc.figure.u.17"></div><pre class="text"> Referer: http://www.example.org/hypertext/Overview.html 1458 1495 </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. 1459 1496 </p> … … 1466 1503 the time of the response. 1467 1504 </p> 1468 <div id="rfc.figure.u.1 7"></div><pre class="inline"><span id="rfc.iref.g.18"></span> Retry-After = "Retry-After" ":" ( HTTP-date | delta-seconds )1505 <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.18"></span> Retry-After = "Retry-After" ":" ( HTTP-date | delta-seconds ) 1469 1506 </pre><p id="rfc.section.10.7.p.3">Two examples of its use are</p> 1470 <div id="rfc.figure.u.1 8"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT1507 <div id="rfc.figure.u.19"></div><pre class="text"> Retry-After: Fri, 31 Dec 1999 23:59:59 GMT 1471 1508 Retry-After: 120 1472 1509 </pre><p id="rfc.section.10.7.p.5">In the latter example, the delay is 2 minutes.</p> … … 1475 1512 <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> 1476 1513 <p id="rfc.section.10.8.p.1">The Server response-header field contains information about the software used by the origin server to handle the request. 1477 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. 15"><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 significance1514 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.22"><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 1478 1515 for identifying the application. 1479 1516 </p> 1480 <div id="rfc.figure.u. 19"></div><pre class="inline"><span id="rfc.iref.g.19"></span> Server = "Server" ":" 1*( product | comment )1517 <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.19"></span> Server = "Server" ":" 1*( product | comment ) 1481 1518 </pre><p id="rfc.section.10.8.p.3">Example:</p> 1482 <div id="rfc.figure.u.2 0"></div><pre class="text"> Server: CERN/3.0 libwww/2.171483 </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. 16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).1519 <div id="rfc.figure.u.21"></div><pre class="text"> Server: CERN/3.0 libwww/2.17 1520 </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.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 1484 1521 </p> 1485 1522 <dl class="empty"> … … 1494 1531 <p id="rfc.section.10.9.p.1">The User-Agent request-header field contains information about the user agent originating the request. This is for statistical 1495 1532 purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses 1496 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. 17"><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, the1533 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.24"><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 1497 1534 product tokens are listed in order of their significance for identifying the application. 1498 1535 </p> 1499 <div id="rfc.figure.u.2 1"></div><pre class="inline"><span id="rfc.iref.g.20"></span> User-Agent = "User-Agent" ":" 1*( product | comment )1536 <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.20"></span> User-Agent = "User-Agent" ":" 1*( product | comment ) 1500 1537 </pre><p id="rfc.section.10.9.p.3">Example:</p> 1501 <div id="rfc.figure.u.2 2"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b31538 <div id="rfc.figure.u.23"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1502 1539 </pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 1503 1540 <p id="rfc.section.11.p.1"> <span class="comment">[rfc.comment.1: TBD.]</span> … … 1675 1712 </p> 1676 1713 <p id="rfc.section.A.2.p.4">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly 1677 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. 18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section 10.8</a>)1714 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.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section 10.8</a>) 1678 1715 </p> 1679 1716 <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> Change Log (to be removed by RFC Editor before publication) … … 1706 1743 <p id="rfc.section.B.2.p.2">Other changes: </p> 1707 1744 <ul> 1708 <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4. 9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>1745 <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.14"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> 1709 1746 </li> 1710 1747 </ul> … … 1906 1943 </li> 1907 1944 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 1908 <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"> 4</a>, <a class="iref" href="#rfc.xref.Part1.9">4</a>, <a class="iref" href="#rfc.xref.Part1.10">7</a>, <a class="iref" href="#rfc.xref.Part1.11">8.8</a>, <a class="iref" href="#rfc.xref.Part1.12">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.13">9.5.6</a>, <a class="iref" href="#rfc.xref.Part1.14">10.2</a>, <a class="iref" href="#rfc.xref.Part1.15">10.8</a>, <a class="iref" href="#rfc.xref.Part1.16">10.8</a>, <a class="iref" href="#rfc.xref.Part1.17">10.9</a>, <a class="iref" href="#Part1"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part1.18">A.2</a><ul class="ind">1945 <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">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.20">9.5.6</a>, <a class="iref" href="#rfc.xref.Part1.21">10.2</a>, <a class="iref" href="#rfc.xref.Part1.22">10.8</a>, <a class="iref" href="#rfc.xref.Part1.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.9</a>, <a class="iref" href="#Part1"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part1.25">A.2</a><ul class="ind"> 1909 1946 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.2">2</a></li> 1910 1947 <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> 1911 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part1.13">9.5.6</a></li> 1912 <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part1.15">10.8</a>, <a class="iref" href="#rfc.xref.Part1.17">10.9</a></li> 1913 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.10">7</a></li> 1914 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.12">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.14">10.2</a></li> 1915 <li class="indline1"><em>Section 8.4</em> <a class="iref" href="#rfc.xref.Part1.8">4</a></li> 1916 <li class="indline1"><em>Section 8.8</em> <a class="iref" href="#rfc.xref.Part1.9">4</a></li> 1917 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part1.11">8.8</a>, <a class="iref" href="#rfc.xref.Part1.16">10.8</a>, <a class="iref" href="#rfc.xref.Part1.18">A.2</a></li> 1948 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part1.20">9.5.6</a></li> 1949 <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> 1950 <li class="indline1"><em>Section 3.3.1</em> <a class="iref" href="#rfc.xref.Part1.10">2</a></li> 1951 <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.22">10.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.9</a></li> 1952 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.17">7</a></li> 1953 <li class="indline1"><em>Section 7.2.3</em> <a class="iref" href="#rfc.xref.Part1.19">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.21">10.2</a></li> 1954 <li class="indline1"><em>Section 8.4</em> <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.15">4</a></li> 1955 <li class="indline1"><em>Section 8.8</em> <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.16">4</a></li> 1956 <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.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.25">A.2</a></li> 1918 1957 </ul> 1919 1958 </li> 1920 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1"> 4</a>, <a class="iref" href="#rfc.xref.Part3.2">4</a>, <a class="iref" href="#rfc.xref.Part3.3">4</a>, <a class="iref" href="#rfc.xref.Part3.4">4</a>, <a class="iref" href="#rfc.xref.Part3.5">7</a>, <a class="iref" href="#rfc.xref.Part3.6">9.3.1</a>, <a class="iref" href="#rfc.xref.Part3.7">10.4</a>, <a class="iref" href="#Part3"><b>14.1</b></a><ul class="ind">1921 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part3. 6">9.3.1</a></li>1922 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part3.1"> 4</a></li>1923 <li class="indline1"><em>Section 6.2</em> <a class="iref" href="#rfc.xref.Part3.2"> 4</a></li>1924 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part3.3"> 4</a></li>1925 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part3.4"> 4</a></li>1926 <li class="indline1"><em>Section 6.7</em> <a class="iref" href="#rfc.xref.Part3. 7">10.4</a></li>1959 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">2</a>, <a class="iref" href="#rfc.xref.Part3.2">2</a>, <a class="iref" href="#rfc.xref.Part3.3">2</a>, <a class="iref" href="#rfc.xref.Part3.4">2</a>, <a class="iref" href="#rfc.xref.Part3.5">4</a>, <a class="iref" href="#rfc.xref.Part3.6">4</a>, <a class="iref" href="#rfc.xref.Part3.7">4</a>, <a class="iref" href="#rfc.xref.Part3.8">4</a>, <a class="iref" href="#rfc.xref.Part3.9">7</a>, <a class="iref" href="#rfc.xref.Part3.10">9.3.1</a>, <a class="iref" href="#rfc.xref.Part3.11">10.4</a>, <a class="iref" href="#Part3"><b>14.1</b></a><ul class="ind"> 1960 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part3.10">9.3.1</a></li> 1961 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part3.1">2</a>, <a class="iref" href="#rfc.xref.Part3.5">4</a></li> 1962 <li class="indline1"><em>Section 6.2</em> <a class="iref" href="#rfc.xref.Part3.2">2</a>, <a class="iref" href="#rfc.xref.Part3.6">4</a></li> 1963 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part3.3">2</a>, <a class="iref" href="#rfc.xref.Part3.7">4</a></li> 1964 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part3.4">2</a>, <a class="iref" href="#rfc.xref.Part3.8">4</a></li> 1965 <li class="indline1"><em>Section 6.7</em> <a class="iref" href="#rfc.xref.Part3.11">10.4</a></li> 1927 1966 </ul> 1928 1967 </li> 1929 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1"> 4</a>, <a class="iref" href="#rfc.xref.Part4.2">4</a>, <a class="iref" href="#rfc.xref.Part4.3">4</a>, <a class="iref" href="#rfc.xref.Part4.4">4</a>, <a class="iref" href="#rfc.xref.Part4.5">6</a>, <a class="iref" href="#rfc.xref.Part4.6">9.2.2</a>, <a class="iref" href="#rfc.xref.Part4.7">9.3.5</a>, <a class="iref" href="#rfc.xref.Part4.8">9.4.13</a>, <a class="iref" href="#Part4"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part4.9">B.2</a><ul class="ind">1930 <li class="indline1"><em>Section 7.1</em> <a class="iref" href="#rfc.xref.Part4. 5">6</a>, <a class="iref" href="#rfc.xref.Part4.6">9.2.2</a></li>1931 <li class="indline1"><em>Section 7.2</em> <a class="iref" href="#rfc.xref.Part4. 1">4</a></li>1932 <li class="indline1"><em>Section 7.3</em> <a class="iref" href="#rfc.xref.Part4. 2">4</a></li>1933 <li class="indline1"><em>Section 7.4</em> <a class="iref" href="#rfc.xref.Part4. 3">4</a></li>1934 <li class="indline1"><em>Section 7.5</em> <a class="iref" href="#rfc.xref.Part4. 4">4</a></li>1968 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">2</a>, <a class="iref" href="#rfc.xref.Part4.2">2</a>, <a class="iref" href="#rfc.xref.Part4.3">2</a>, <a class="iref" href="#rfc.xref.Part4.4">2</a>, <a class="iref" href="#rfc.xref.Part4.5">2</a>, <a class="iref" href="#rfc.xref.Part4.6">4</a>, <a class="iref" href="#rfc.xref.Part4.7">4</a>, <a class="iref" href="#rfc.xref.Part4.8">4</a>, <a class="iref" href="#rfc.xref.Part4.9">4</a>, <a class="iref" href="#rfc.xref.Part4.10">6</a>, <a class="iref" href="#rfc.xref.Part4.11">9.2.2</a>, <a class="iref" href="#rfc.xref.Part4.12">9.3.5</a>, <a class="iref" href="#rfc.xref.Part4.13">9.4.13</a>, <a class="iref" href="#Part4"><b>14.1</b></a>, <a class="iref" href="#rfc.xref.Part4.14">B.2</a><ul class="ind"> 1969 <li class="indline1"><em>Section 7.1</em> <a class="iref" href="#rfc.xref.Part4.1">2</a>, <a class="iref" href="#rfc.xref.Part4.10">6</a>, <a class="iref" href="#rfc.xref.Part4.11">9.2.2</a></li> 1970 <li class="indline1"><em>Section 7.2</em> <a class="iref" href="#rfc.xref.Part4.2">2</a>, <a class="iref" href="#rfc.xref.Part4.6">4</a></li> 1971 <li class="indline1"><em>Section 7.3</em> <a class="iref" href="#rfc.xref.Part4.3">2</a>, <a class="iref" href="#rfc.xref.Part4.7">4</a></li> 1972 <li class="indline1"><em>Section 7.4</em> <a class="iref" href="#rfc.xref.Part4.4">2</a>, <a class="iref" href="#rfc.xref.Part4.8">4</a></li> 1973 <li class="indline1"><em>Section 7.5</em> <a class="iref" href="#rfc.xref.Part4.5">2</a>, <a class="iref" href="#rfc.xref.Part4.9">4</a></li> 1935 1974 </ul> 1936 1975 </li> 1937 <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1"> 4</a>, <a class="iref" href="#rfc.xref.Part5.2">4</a>, <a class="iref" href="#rfc.xref.Part5.3">6</a>, <a class="iref" href="#rfc.xref.Part5.4">8.3</a>, <a class="iref" href="#rfc.xref.Part5.5">9.1.2</a>, <a class="iref" href="#rfc.xref.Part5.6">9.2.7</a>, <a class="iref" href="#rfc.xref.Part5.7">9.4.17</a>, <a class="iref" href="#Part5"><b>14.1</b></a><ul class="ind">1938 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part5. 3">6</a></li>1939 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part5. 1">4</a></li>1940 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part5. 2">4</a>, <a class="iref" href="#rfc.xref.Part5.4">8.3</a>, <a class="iref" href="#rfc.xref.Part5.5">9.1.2</a>, <a class="iref" href="#rfc.xref.Part5.7">9.4.17</a></li>1976 <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.2">2</a>, <a class="iref" href="#rfc.xref.Part5.3">2</a>, <a class="iref" href="#rfc.xref.Part5.4">4</a>, <a class="iref" href="#rfc.xref.Part5.5">4</a>, <a class="iref" href="#rfc.xref.Part5.6">6</a>, <a class="iref" href="#rfc.xref.Part5.7">8.3</a>, <a class="iref" href="#rfc.xref.Part5.8">9.1.2</a>, <a class="iref" href="#rfc.xref.Part5.9">9.2.7</a>, <a class="iref" href="#rfc.xref.Part5.10">9.4.17</a>, <a class="iref" href="#Part5"><b>14.1</b></a><ul class="ind"> 1977 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.6">6</a></li> 1978 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part5.2">2</a>, <a class="iref" href="#rfc.xref.Part5.4">4</a></li> 1979 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part5.3">2</a>, <a class="iref" href="#rfc.xref.Part5.5">4</a>, <a class="iref" href="#rfc.xref.Part5.7">8.3</a>, <a class="iref" href="#rfc.xref.Part5.8">9.1.2</a>, <a class="iref" href="#rfc.xref.Part5.10">9.4.17</a></li> 1941 1980 </ul> 1942 1981 </li> 1943 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1"> 6</a>, <a class="iref" href="#rfc.xref.Part6.2">6</a>, <a class="iref" href="#rfc.xref.Part6.3">8.3</a>, <a class="iref" href="#Part6"><b>14.1</b></a><ul class="ind">1944 <li class="indline1"><em>Section 16.1</em> <a class="iref" href="#rfc.xref.Part6.1"> 6</a></li>1945 <li class="indline1"><em>Section 16.5</em> <a class="iref" href="#rfc.xref.Part6. 2">6</a></li>1982 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">2</a>, <a class="iref" href="#rfc.xref.Part6.2">2</a>, <a class="iref" href="#rfc.xref.Part6.3">2</a>, <a class="iref" href="#rfc.xref.Part6.4">6</a>, <a class="iref" href="#rfc.xref.Part6.5">6</a>, <a class="iref" href="#rfc.xref.Part6.6">8.3</a>, <a class="iref" href="#Part6"><b>14.1</b></a><ul class="ind"> 1983 <li class="indline1"><em>Section 16.1</em> <a class="iref" href="#rfc.xref.Part6.1">2</a>, <a class="iref" href="#rfc.xref.Part6.2">2</a>, <a class="iref" href="#rfc.xref.Part6.4">6</a></li> 1984 <li class="indline1"><em>Section 16.5</em> <a class="iref" href="#rfc.xref.Part6.3">2</a>, <a class="iref" href="#rfc.xref.Part6.5">6</a></li> 1946 1985 </ul> 1947 1986 </li> 1948 <li class="indline1"><em>Part7</em> <a class="iref" href="#rfc.xref.Part7.1"> 4</a>, <a class="iref" href="#rfc.xref.Part7.2">4</a>, <a class="iref" href="#rfc.xref.Part7.3">6</a>, <a class="iref" href="#rfc.xref.Part7.4">6</a>, <a class="iref" href="#rfc.xref.Part7.5">9.4.2</a>, <a class="iref" href="#rfc.xref.Part7.6">9.4.8</a>, <a class="iref" href="#Part7"><b>14.1</b></a><ul class="ind">1949 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.Part7.1"> 4</a></li>1950 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part7. 3">6</a></li>1951 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part7. 2">4</a></li>1952 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part7.4"> 6</a></li>1987 <li class="indline1"><em>Part7</em> <a class="iref" href="#rfc.xref.Part7.1">2</a>, <a class="iref" href="#rfc.xref.Part7.2">2</a>, <a class="iref" href="#rfc.xref.Part7.3">2</a>, <a class="iref" href="#rfc.xref.Part7.4">2</a>, <a class="iref" href="#rfc.xref.Part7.5">4</a>, <a class="iref" href="#rfc.xref.Part7.6">4</a>, <a class="iref" href="#rfc.xref.Part7.7">6</a>, <a class="iref" href="#rfc.xref.Part7.8">6</a>, <a class="iref" href="#rfc.xref.Part7.9">9.4.2</a>, <a class="iref" href="#rfc.xref.Part7.10">9.4.8</a>, <a class="iref" href="#Part7"><b>14.1</b></a><ul class="ind"> 1988 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.Part7.1">2</a>, <a class="iref" href="#rfc.xref.Part7.5">4</a></li> 1989 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part7.2">2</a>, <a class="iref" href="#rfc.xref.Part7.7">6</a></li> 1990 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part7.3">2</a>, <a class="iref" href="#rfc.xref.Part7.6">4</a></li> 1991 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part7.4">2</a>, <a class="iref" href="#rfc.xref.Part7.8">6</a></li> 1953 1992 </ul> 1954 1993 </li> … … 1965 2004 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>14.1</b></a></li> 1966 2005 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li> 1967 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#rfc.xref.RFC2822.1">10.3</a>, <a class="iref" href="# RFC2822"><b>14.2</b></a><ul class="ind">1968 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.RFC2822.1">10.3</a> </li>2006 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#rfc.xref.RFC2822.1">10.3</a>, <a class="iref" href="#rfc.xref.RFC2822.2">10.3</a>, <a class="iref" href="#RFC2822"><b>14.2</b></a><ul class="ind"> 2007 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.RFC2822.1">10.3</a>, <a class="iref" href="#rfc.xref.RFC2822.2">10.3</a></li> 1969 2008 </ul> 1970 2009 </li>
Note: See TracChangeset
for help on using the changeset viewer.