![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 206 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 09/02/08 22:03:01 (15 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/latest/p3-payload.html (modified) (35 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r205 r206 587 587 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="Augmented BNF">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.1"><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.2"><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> 588 588 </p> 589 <div id="rfc.figure.u.1"></div><pre class="inline"> ALPHA = <ALPHA, defined in <a href="#Part1" id="rfc.xref.Part1.3"><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>> 590 DIGIT = <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>> 591 OCTET = <OCTET, defined in <a href="#Part1" id="rfc.xref.Part1.5"><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>> 592 </pre><div id="rfc.figure.u.2"></div><pre class="inline"> 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>> 593 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>> 589 <div id="rfc.figure.u.1"></div><pre class="inline"> ALPHA = <ALPHA, defined in <a href="#Part1" id="rfc.xref.Part1.3"><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>> 590 DIGIT = <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>> 591 OCTET = <OCTET, defined in <a href="#Part1" id="rfc.xref.Part1.5"><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>> 592 </pre><div id="rfc.figure.u.2"></div><pre class="inline"> 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>> 593 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>> 594 </pre><p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p> 595 <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>> 596 Allow = <Allow, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>> 597 Content-Length = <Content-Length, 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#header.content-length" title="Content-Length">Section 8.2</a>> 598 Content-Range = <Content-Range, 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.content-range" title="Content-Range">Section 6.2</a>> 599 Expires = <Expires, 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.expires" title="Expires">Section 16.3</a>> 600 Last-Modified = <Last-Modified, 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.last-modified" title="Last-Modified">Section 7.6</a>> 601 message-header = <message-header, 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#message.headers" title="Message Headers">Section 4.2</a>> 602 relativeURI = <relativeURI, 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>> 594 603 </pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> 595 604 <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a id="character.sets" href="#character.sets">Character Sets</a></h2> … … 611 620 Set registry (<<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>>). 612 621 </p> 613 <div id="rfc.figure.u. 3"></div><pre class="inline"><span id="rfc.iref.g.1"></span> charset = token622 <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.1"></span> charset = token 614 623 </pre><p id="rfc.section.3.1.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA 615 624 Character Set registry <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry. … … 634 643 decoded by the recipient. 635 644 </p> 636 <div id="rfc.figure.u. 4"></div><pre class="inline"><span id="rfc.iref.g.2"></span> content-coding = token645 <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.2"></span> content-coding = token 637 646 </pre><p id="rfc.section.3.2.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section 6.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section 6.5</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding 638 647 mechanism will be required to remove the encoding. … … 678 687 <p id="rfc.section.3.3.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section 6.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section 6.1</a>) header fields in order to provide open and extensible data typing and type negotiation. 679 688 </p> 680 <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> media-type = type "/" subtype *( ";" parameter )689 <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> media-type = type "/" subtype *( ";" parameter ) 681 690 type = token 682 691 subtype = token 683 692 </pre><p id="rfc.section.3.3.p.3">Parameters <em class="bcp14">MAY</em> follow the type/subtype in the form of attribute/value pairs. 684 693 </p> 685 <div id="rfc.figure.u. 6"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span> parameter = attribute "=" value694 <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span> parameter = attribute "=" value 686 695 attribute = token 687 696 value = token | quoted-string … … 721 730 </p> 722 731 <p id="rfc.section.3.3.2.p.2">In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. The one exception 723 is the "multipart/byteranges" type (<a href="p5-range.html#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a> of <a href="#Part5" id="rfc.xref.Part5. 1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) when it appears in a 206 (Partial Content) response.732 is the "multipart/byteranges" type (<a href="p5-range.html#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) when it appears in a 206 (Partial Content) response. 724 733 </p> 725 734 <p id="rfc.section.3.3.2.p.3">In general, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. If an application receives … … 736 745 a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. 737 746 </p> 738 <div id="rfc.figure.u. 7"></div><pre class="inline"><span id="rfc.iref.g.10"></span> qvalue = ( "0" [ "." 0*3DIGIT ] )747 <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.10"></span> qvalue = ( "0" [ "." 0*3DIGIT ] ) 739 748 | ( "1" [ "." 0*3("0") ] ) 740 749 </pre><p id="rfc.section.3.4.p.3">"Quality values" is a misnomer, since these values merely represent relative degradation in desired quality.</p> … … 746 755 <p id="rfc.section.3.5.p.2">The syntax and registry of HTTP language tags is the same as that defined by <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags: 747 756 </p> 748 <div id="rfc.figure.u. 8"></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> language-tag = primary-tag *( "-" subtag )757 <div id="rfc.figure.u.9"></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> language-tag = primary-tag *( "-" subtag ) 749 758 primary-tag = 1*8ALPHA 750 759 subtag = 1*8ALPHA … … 752 761 by the IANA. Example tags include: 753 762 </p> 754 <div id="rfc.figure.u. 9"></div><pre class="text"> en, en-US, en-cockney, i-cherokee, x-pig-latin763 <div id="rfc.figure.u.10"></div><pre class="text"> en, en-US, en-cockney, i-cherokee, x-pig-latin 755 764 </pre><p id="rfc.section.3.5.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country 756 765 code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered … … 768 777 by the request. 769 778 </p> 770 <div id="rfc.figure.u.1 0"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> entity-header = Allow ; <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>779 <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> entity-header = Allow ; <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a> 771 780 | Content-Encoding ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section 6.5</a> 772 781 | Content-Language ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section 6.6</a> 773 | Content-Length ; <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.content-length" title="Content-Length">Section 8.2</a>782 | Content-Length ; <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#header.content-length" title="Content-Length">Section 8.2</a> 774 783 | Content-Location ; <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section 6.7</a> 775 784 | Content-MD5 ; <a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section 6.8</a> 776 | Content-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.content-range" title="Content-Range">Section 6.2</a>785 | Content-Range ; <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.content-range" title="Content-Range">Section 6.2</a> 777 786 | Content-Type ; <a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section 6.9</a> 778 | Expires ; <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.expires" title="Expires">Section 16.3</a>779 | Last-Modified ; <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.last-modified" title="Last-Modified">Section 7.6</a>787 | Expires ; <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.expires" title="Expires">Section 16.3</a> 788 | Last-Modified ; <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.last-modified" title="Last-Modified">Section 7.6</a> 780 789 | extension-header 781 790 … … 786 795 <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <a id="entity.body" href="#entity.body">Entity Body</a></h2> 787 796 <p id="rfc.section.4.2.p.1">The entity-body (if any) sent with an HTTP request or response is in a format and encoding defined by the entity-header fields.</p> 788 <div id="rfc.figure.u.1 1"></div><pre class="inline"><span id="rfc.iref.g.16"></span> entity-body = *OCTET789 </pre><p id="rfc.section.4.2.p.3">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. 9"><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 ensure797 <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.16"></span> entity-body = *OCTET 798 </pre><p id="rfc.section.4.2.p.3">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.13"><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 790 799 safe and proper transfer of the message. 791 800 </p> … … 794 803 and Content-Encoding. These define a two-layer, ordered encoding model: 795 804 </p> 796 <div id="rfc.figure.u.1 2"></div><pre class="text"> entity-body := Content-Encoding( Content-Type( data ) )805 <div id="rfc.figure.u.13"></div><pre class="text"> entity-body := Content-Encoding( Content-Type( data ) ) 797 806 </pre><p id="rfc.section.4.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content 798 807 codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There … … 804 813 </p> 805 814 <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a> <a id="entity.length" href="#entity.length">Entity Length</a></h3> 806 <p id="rfc.section.4.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</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> defines how the transfer-length of a message-body is determined.815 <p id="rfc.section.4.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</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> defines how the transfer-length of a message-body is determined. 807 816 </p> 808 817 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1> … … 849 858 </ol> 850 859 <p id="rfc.section.5.1.p.4">HTTP/1.1 includes the following request-header fields for enabling server-driven negotiation through description of user agent 851 capabilities and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section 6.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section 6.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section 6.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section 6.4</a>), and User-Agent (<a href="p2-semantics.html#header.user-agent" title="User-Agent">Section 10.9</a> of <a href="#Part2" id="rfc.xref.Part2. 2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including information outside the request-header fields or within extension860 capabilities and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section 6.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section 6.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section 6.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section 6.4</a>), and User-Agent (<a href="p2-semantics.html#header.user-agent" title="User-Agent">Section 10.9</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including information outside the request-header fields or within extension 852 861 header fields not defined by this specification. 853 862 </p> 854 <p id="rfc.section.5.1.p.5">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a> of <a href="#Part6" id="rfc.xref.Part6. 2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation.863 <p id="rfc.section.5.1.p.5">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation. 855 864 </p> 856 865 <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2> … … 898 907 for an in-line image. 899 908 </p> 900 <div id="rfc.figure.u.1 3"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> Accept = "Accept" ":"909 <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> Accept = "Accept" ":" 901 910 #( media-range [ accept-params ] ) 902 911 … … 922 931 </dl> 923 932 <p id="rfc.section.6.1.p.5">The example</p> 924 <div id="rfc.figure.u.1 4"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic933 <div id="rfc.figure.u.15"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic 925 934 </pre><p id="rfc.section.6.1.p.7"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in 926 935 quality." … … 931 940 </p> 932 941 <p id="rfc.section.6.1.p.9">A more elaborate example is</p> 933 <div id="rfc.figure.u.1 5"></div><pre class="text"> Accept: text/plain; q=0.5, text/html,942 <div id="rfc.figure.u.16"></div><pre class="text"> Accept: text/plain; q=0.5, text/html, 934 943 text/x-dvi; q=0.8, text/x-c 935 944 </pre><p id="rfc.section.6.1.p.11">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then … … 939 948 to a given type, the most specific reference has precedence. For example, 940 949 </p> 941 <div id="rfc.figure.u.1 6"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */*950 <div id="rfc.figure.u.17"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */* 942 951 </pre><p id="rfc.section.6.1.p.14">have the following precedence:</p> 943 <div id="rfc.figure.u.1 7"></div><pre class="text"> 1) text/html;level=1952 <div id="rfc.figure.u.18"></div><pre class="text"> 1) text/html;level=1 944 953 2) text/html 945 954 3) text/* … … 948 957 which matches that type. For example, 949 958 </p> 950 <div id="rfc.figure.u.1 8"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,959 <div id="rfc.figure.u.19"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, 951 960 text/html;level=2;q=0.4, */*;q=0.5 952 961 </pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p> 953 <div id="rfc.figure.u. 19"></div><pre class="text"> text/html;level=1 = 1962 <div id="rfc.figure.u.20"></div><pre class="text"> text/html;level=1 = 1 954 963 text/html = 0.7 955 964 text/plain = 0.3 … … 967 976 to a server which is capable of representing documents in those character sets. 968 977 </p> 969 <div id="rfc.figure.u.2 0"></div><pre class="inline"><span id="rfc.iref.g.21"></span> Accept-Charset = "Accept-Charset" ":"978 <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.21"></span> Accept-Charset = "Accept-Charset" ":" 970 979 1#( ( charset | "*" ) [ ";" "q" "=" qvalue ] ) 971 980 </pre><p id="rfc.section.6.2.p.3">Character set values are described in <a href="#character.sets" title="Character Sets">Section 3.1</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset. The default value is q=1. An 972 981 example is 973 982 </p> 974 <div id="rfc.figure.u.2 1"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.8983 <div id="rfc.figure.u.22"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 975 984 </pre><p id="rfc.section.6.2.p.5">The special value "*", if present in the Accept-Charset field, matches every character set (including ISO-8859-1) which is 976 985 not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets … … 986 995 <p id="rfc.section.6.3.p.1">The Accept-Encoding request-header field is similar to Accept, but restricts the content-codings (<a href="#content.codings" title="Content Codings">Section 3.2</a>) that are acceptable in the response. 987 996 </p> 988 <div id="rfc.figure.u.2 2"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> Accept-Encoding = "Accept-Encoding" ":"997 <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> Accept-Encoding = "Accept-Encoding" ":" 989 998 #( codings [ ";" "q" "=" qvalue ] ) 990 999 codings = ( content-coding | "*" ) 991 1000 </pre><p id="rfc.section.6.3.p.3">Examples of its use are:</p> 992 <div id="rfc.figure.u.2 3"></div><pre class="text"> Accept-Encoding: compress, gzip1001 <div id="rfc.figure.u.24"></div><pre class="text"> Accept-Encoding: compress, gzip 993 1002 Accept-Encoding: 994 1003 Accept-Encoding: * … … 1032 1041 as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 3.5</a>. 1033 1042 </p> 1034 <div id="rfc.figure.u.2 4"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> Accept-Language = "Accept-Language" ":"1043 <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> Accept-Language = "Accept-Language" ":" 1035 1044 1#( language-range [ ";" "q" "=" qvalue ] ) 1036 1045 language-range = ( ( 1*8ALPHA *( "-" 1*8ALPHA ) ) | "*" ) … … 1038 1047 that range. The quality value defaults to "q=1". For example, 1039 1048 </p> 1040 <div id="rfc.figure.u.2 5"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.71049 <div id="rfc.figure.u.26"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.7 1041 1050 </pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English." A language-range matches a language-tag 1042 1051 if it exactly equals the tag, or if it exactly equals a prefix of the tag such that the first tag character following the … … 1076 1085 without losing the identity of its underlying media type. 1077 1086 </p> 1078 <div id="rfc.figure.u.2 6"></div><pre class="inline"><span id="rfc.iref.g.26"></span> Content-Encoding = "Content-Encoding" ":" 1#content-coding1087 <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.26"></span> Content-Encoding = "Content-Encoding" ":" 1#content-coding 1079 1088 </pre><p id="rfc.section.6.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section 3.2</a>. An example of its use is 1080 1089 </p> 1081 <div id="rfc.figure.u.2 7"></div><pre class="text"> Content-Encoding: gzip1090 <div id="rfc.figure.u.28"></div><pre class="text"> Content-Encoding: gzip 1082 1091 </pre><p id="rfc.section.6.5.p.5">The content-coding is a characteristic of the entity identified by the Request-URI. Typically, the entity-body is stored with 1083 1092 this encoding and is only decoded before rendering or analogous usage. However, a non-transparent proxy <em class="bcp14">MAY</em> modify the content-coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control … … 1096 1105 Note that this might not be equivalent to all the languages used within the entity-body. 1097 1106 </p> 1098 <div id="rfc.figure.u.2 8"></div><pre class="inline"><span id="rfc.iref.g.27"></span> Content-Language = "Content-Language" ":" 1#language-tag1107 <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.27"></span> Content-Language = "Content-Language" ":" 1#language-tag 1099 1108 </pre><p id="rfc.section.6.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section 3.5</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate entities according to the user's 1100 1109 own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is 1101 1110 </p> 1102 <div id="rfc.figure.u. 29"></div><pre class="text"> Content-Language: da1111 <div id="rfc.figure.u.30"></div><pre class="text"> Content-Language: da 1103 1112 </pre><p id="rfc.section.6.6.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean 1104 1113 that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language … … 1108 1117 simultaneously in the original Maori and English versions, would call for 1109 1118 </p> 1110 <div id="rfc.figure.u.3 0"></div><pre class="text"> Content-Language: mi, en1119 <div id="rfc.figure.u.31"></div><pre class="text"> Content-Language: mi, en 1111 1120 </pre><p id="rfc.section.6.6.p.8">However, just because multiple languages are present within an entity does not mean that it is intended for multiple linguistic 1112 1121 audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended … … 1123 1132 accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned. 1124 1133 </p> 1125 <div id="rfc.figure.u.3 1"></div><pre class="inline"><span id="rfc.iref.g.28"></span> Content-Location = "Content-Location" ":"1134 <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.28"></span> Content-Location = "Content-Location" ":" 1126 1135 ( absoluteURI | relativeURI ) 1127 1136 </pre><p id="rfc.section.6.7.p.3">The value of Content-Location also defines the base URI for the entity.</p> … … 1131 1140 <p id="rfc.section.6.7.p.5">A cache cannot assume that an entity with a Content-Location different from the URI used to retrieve it can be used to respond 1132 1141 to later requests on that Content-Location URI. However, the Content-Location can be used to differentiate between multiple 1133 entities retrieved from a single requested resource, as described in <a href="p6-cache.html#caching.negotiated.responses" title="Caching Negotiated Responses">Section 8</a> of <a href="#Part6" id="rfc.xref.Part6. 3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.1142 entities retrieved from a single requested resource, as described in <a href="p6-cache.html#caching.negotiated.responses" title="Caching Negotiated Responses">Section 8</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. 1134 1143 </p> 1135 1144 <p id="rfc.section.6.7.p.6">If the Content-Location is a relative URI, the relative URI is interpreted relative to the Request-URI.</p> … … 1142 1151 attacks.) 1143 1152 </p> 1144 <div id="rfc.figure.u.3 2"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span> Content-MD5 = "Content-MD5" ":" md5-digest1153 <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span> Content-MD5 = "Content-MD5" ":" md5-digest 1145 1154 md5-digest = <base64 of 128 bit MD5 digest as per <a href="#RFC1864" id="rfc.xref.RFC1864.2"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>> 1146 1155 </pre><p id="rfc.section.6.8.p.3">The Content-MD5 header field <em class="bcp14">MAY</em> be generated by an origin server or client to function as an integrity check of the entity-body. Only origin servers or clients <em class="bcp14">MAY</em> generate the Content-MD5 header field; proxies and gateways <em class="bcp14">MUST NOT</em> generate it, as this would defeat its value as an end-to-end integrity check. Any recipient of the entity-body, including … … 1179 1188 the HEAD method, the media type that would have been sent had the request been a GET. 1180 1189 </p> 1181 <div id="rfc.figure.u.3 3"></div><pre class="inline"><span id="rfc.iref.g.31"></span> Content-Type = "Content-Type" ":" media-type1190 <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.31"></span> Content-Type = "Content-Type" ":" media-type 1182 1191 </pre><p id="rfc.section.6.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section 3.3</a>. An example of the field is 1183 1192 </p> 1184 <div id="rfc.figure.u.3 4"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-41193 <div id="rfc.figure.u.35"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-4 1185 1194 </pre><p id="rfc.section.6.9.p.5">Further discussion of methods for identifying the media type of an entity is provided in <a href="#type" title="Type">Section 4.2.1</a>. 1186 1195 </p> … … 1398 1407 environments. 1399 1408 </p> 1400 <div id="rfc.figure.u.3 5"></div><pre class="inline"><span id="rfc.iref.g.32"></span> MIME-Version = "MIME-Version" ":" 1*DIGIT "." 1*DIGIT1409 <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.32"></span> MIME-Version = "MIME-Version" ":" 1*DIGIT "." 1*DIGIT 1401 1410 </pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this 1402 1411 document and not the MIME specification. … … 1430 1439 </p> 1431 1440 <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2> 1432 <p id="rfc.section.A.5.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 8.7</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>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.1441 <p id="rfc.section.A.5.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 8.7</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>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol. 1433 1442 </p> 1434 1443 <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> … … 1452 1461 in <a href="#RFC1806" id="rfc.xref.RFC1806.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header">[RFC1806]</cite></a>. 1453 1462 </p> 1454 <div id="rfc.figure.u.3 6"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span> content-disposition = "Content-Disposition" ":"1463 <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span> content-disposition = "Content-Disposition" ":" 1455 1464 disposition-type *( ";" disposition-parm ) 1456 1465 disposition-type = "attachment" | disp-extension-token … … 1460 1469 disp-extension-parm = token "=" ( token | quoted-string ) 1461 1470 </pre><p id="rfc.section.B.1.p.3">An example is</p> 1462 <div id="rfc.figure.u.3 7"></div><pre class="text"> Content-Disposition: attachment; filename="fname.ext"1471 <div id="rfc.figure.u.38"></div><pre class="text"> Content-Disposition: attachment; filename="fname.ext" 1463 1472 </pre><p id="rfc.section.B.1.p.5">The receiving user agent <em class="bcp14">SHOULD NOT</em> respect any directory path information present in the filename-parm parameter, which is the only parameter believed to apply 1464 1473 to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only. … … 1473 1482 <p id="rfc.section.C.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 1474 1483 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 1475 computed. (<a href="#entity.length" title="Entity Length">Section 4.2.2</a>, see also <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="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1484 computed. (<a href="#entity.length" title="Entity Length">Section 4.2.2</a>, see also <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="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1476 1485 </p> 1477 1486 <p id="rfc.section.C.1.p.2">Charset wildcarding is introduced to avoid explosion of character set names in accept headers. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section 6.2</a>) … … 1667 1676 </li> 1668 1677 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 1669 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">2</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.1</a>, <a class="iref" href="#rfc.xref.Part1.9">4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">4.2.2</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.11">A.5</a>, <a class="iref" href="#rfc.xref.Part1.12">C.1</a><ul class="ind">1678 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">2</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">4.1</a>, <a class="iref" href="#rfc.xref.Part1.13">4.2</a>, <a class="iref" href="#rfc.xref.Part1.14">4.2.2</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.15">A.5</a>, <a class="iref" href="#rfc.xref.Part1.16">C.1</a><ul class="ind"> 1670 1679 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a></li> 1671 1680 <li class="indline1"><em>Section 2.2</em> <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></li> 1672 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.9">4.2</a></li> 1673 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.10">4.2.2</a></li> 1674 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.8">4.1</a></li> 1675 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.11">A.5</a></li> 1681 <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.11">2</a></li> 1682 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.10">2</a></li> 1683 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.13">4.2</a></li> 1684 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.14">4.2.2</a></li> 1685 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.12">4.1</a></li> 1686 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.15">A.5</a></li> 1676 1687 </ul> 1677 1688 </li> 1678 <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1"> 4.1</a>, <a class="iref" href="#rfc.xref.Part2.2">5.1</a>, <a class="iref" href="#Part2"><b>10.1</b></a><ul class="ind">1679 <li class="indline1"><em>Section 10.1</em> <a class="iref" href="#rfc.xref.Part2.1"> 4.1</a></li>1680 <li class="indline1"><em>Section 10.9</em> <a class="iref" href="#rfc.xref.Part2. 2">5.1</a></li>1689 <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">2</a>, <a class="iref" href="#rfc.xref.Part2.2">4.1</a>, <a class="iref" href="#rfc.xref.Part2.3">5.1</a>, <a class="iref" href="#Part2"><b>10.1</b></a><ul class="ind"> 1690 <li class="indline1"><em>Section 10.1</em> <a class="iref" href="#rfc.xref.Part2.1">2</a>, <a class="iref" href="#rfc.xref.Part2.2">4.1</a></li> 1691 <li class="indline1"><em>Section 10.9</em> <a class="iref" href="#rfc.xref.Part2.3">5.1</a></li> 1681 1692 </ul> 1682 1693 </li> 1683 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1"> 4.1</a>, <a class="iref" href="#Part4"><b>10.1</b></a><ul class="ind">1684 <li class="indline1"><em>Section 7.6</em> <a class="iref" href="#rfc.xref.Part4.1"> 4.1</a></li>1694 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">2</a>, <a class="iref" href="#rfc.xref.Part4.2">4.1</a>, <a class="iref" href="#Part4"><b>10.1</b></a><ul class="ind"> 1695 <li class="indline1"><em>Section 7.6</em> <a class="iref" href="#rfc.xref.Part4.1">2</a>, <a class="iref" href="#rfc.xref.Part4.2">4.1</a></li> 1685 1696 </ul> 1686 1697 </li> 1687 <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1"> 3.3.2</a>, <a class="iref" href="#rfc.xref.Part5.2">4.1</a>, <a class="iref" href="#Part5"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part5.3">C.1</a><ul class="ind">1688 <li class="indline1"><em>Section 6.2</em> <a class="iref" href="#rfc.xref.Part5. 2">4.1</a></li>1689 <li class="indline1"><em>Section A</em> <a class="iref" href="#rfc.xref.Part5. 1">3.3.2</a></li>1698 <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.2">3.3.2</a>, <a class="iref" href="#rfc.xref.Part5.3">4.1</a>, <a class="iref" href="#Part5"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part5.4">C.1</a><ul class="ind"> 1699 <li class="indline1"><em>Section 6.2</em> <a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.3">4.1</a></li> 1700 <li class="indline1"><em>Section A</em> <a class="iref" href="#rfc.xref.Part5.2">3.3.2</a></li> 1690 1701 </ul> 1691 1702 </li> 1692 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1"> 4.1</a>, <a class="iref" href="#rfc.xref.Part6.2">5.1</a>, <a class="iref" href="#rfc.xref.Part6.3">6.7</a>, <a class="iref" href="#Part6"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part6.4">C.1</a><ul class="ind">1693 <li class="indline1"><em>Section 8</em> <a class="iref" href="#rfc.xref.Part6. 3">6.7</a></li>1694 <li class="indline1"><em>Section 16.3</em> <a class="iref" href="#rfc.xref.Part6.1"> 4.1</a></li>1695 <li class="indline1"><em>Section 16.5</em> <a class="iref" href="#rfc.xref.Part6. 2">5.1</a></li>1703 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">2</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a>, <a class="iref" href="#rfc.xref.Part6.3">5.1</a>, <a class="iref" href="#rfc.xref.Part6.4">6.7</a>, <a class="iref" href="#Part6"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part6.5">C.1</a><ul class="ind"> 1704 <li class="indline1"><em>Section 8</em> <a class="iref" href="#rfc.xref.Part6.4">6.7</a></li> 1705 <li class="indline1"><em>Section 16.3</em> <a class="iref" href="#rfc.xref.Part6.1">2</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a></li> 1706 <li class="indline1"><em>Section 16.5</em> <a class="iref" href="#rfc.xref.Part6.3">5.1</a></li> 1696 1707 </ul> 1697 1708 </li>
Note: See TracChangeset
for help on using the changeset viewer.
