Changeset 369 for draft-ietf-httpbis
- Timestamp:
- 13/11/08 19:41:14 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r367 r369 522 522 </li> 523 523 <li class="tocline0">2. <a href="#notation">Notational Conventions and Generic Grammar</a><ul class="toc"> 524 <li class="tocline1">2.1 <a href="#notation.abnf">ABNF Extensions</a><ul class="toc"> 525 <li class="tocline1">2.1.1 <a href="#rfc.section.2.1.1">#rule</a></li> 526 <li class="tocline1">2.1.2 <a href="#implied.LWS">implied *LWS</a></li> 527 </ul> 528 </li> 524 <li class="tocline1">2.1 <a href="#notation.abnf">ABNF Extension: #rule</a></li> 529 525 <li class="tocline1">2.2 <a href="#basic.rules">Basic Rules</a></li> 530 526 <li class="tocline1">2.3 <a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li> … … 756 752 </p> 757 753 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1> 758 <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="notation.abnf" href="#notation.abnf">ABNF Extensions</a></h2> 759 <p id="rfc.section.2.1.p.1">Two extensions to the ABNF rules of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> are used to improve readability.<span class="comment">[rfc.comment.1: The current plan is to remove these extensions prior to the last call draft.]</span> 760 </p> 761 <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a> #rule 762 </h3> 763 <p id="rfc.section.2.1.1.p.1">A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "<n>#<m>element" indicating at 764 least <n> and at most <m> elements, each separated by one or more commas (",") and <em class="bcp14">OPTIONAL</em> linear white space (LWS). This makes the usual form of lists very easy; a rule such as 765 </p> 766 <div id="rfc.figure.u.4"></div><pre class="text"> ( *<a href="#rule.LWS" class="smpl">LWS</a> element *( *<a href="#rule.LWS" class="smpl">LWS</a> "," *<a href="#rule.LWS" class="smpl">LWS</a> element ))</pre><p id="rfc.section.2.1.1.p.2">can be shown as </p> 767 <div id="rfc.figure.u.5"></div><pre class="text"> 1#element</pre><p id="rfc.section.2.1.1.p.3">Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is, 754 <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="notation.abnf" href="#notation.abnf">ABNF Extension: #rule</a></h2> 755 <p id="rfc.section.2.1.p.1">One extension to the ABNF rules of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> is used to improve readability. 756 </p> 757 <p id="rfc.section.2.1.p.2">A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "<n>#<m>element" indicating at 758 least <n> and at most <m> elements, each separated by one or more commas (",") and <em class="bcp14">OPTIONAL</em> linear white space (OWS). This makes the usual form of lists very easy; a rule such as 759 </p> 760 <div id="rfc.figure.u.4"></div><pre class="text"> ( *<a href="#rule.whitespace" class="smpl">OWS</a> element *( *<a href="#rule.whitespace" class="smpl">OWS</a> "," *<a href="#rule.whitespace" class="smpl">OWS</a> element ))</pre><p id="rfc.section.2.1.p.3">can be shown as </p> 761 <div id="rfc.figure.u.5"></div><pre class="text"> 1#element</pre><p id="rfc.section.2.1.p.4">Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is, 768 762 "(element), , (element) " is permitted, but counts as only two elements. Therefore, where at least one element is required, 769 763 at least one non-null element <em class="bcp14">MUST</em> be present. Default values are 0 and infinity so that "#element" allows any number, including zero; "1#element" requires at 770 764 least one; and "1#2element" allows one or two. 771 </p>772 <div id="rfc.iref.i.1"></div>773 <h3 id="rfc.section.2.1.2"><a href="#rfc.section.2.1.2">2.1.2</a> <a id="implied.LWS" href="#implied.LWS">implied *LWS</a></h3>774 <p id="rfc.section.2.1.2.p.1">The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included775 between any two adjacent words (token or quoted-string), and between adjacent words and separators, without changing the interpretation776 of a field. At least one delimiter (LWS and/or separators) <em class="bcp14">MUST</em> exist between any two tokens (for the definition of "token" below), since they would otherwise be interpreted as a single777 token.778 765 </p> 779 766 <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="basic.rules" href="#basic.rules">Basic Rules</a></h2> … … 790 777 </div> 791 778 <div id="rule.LWS"> 792 <p id="rfc.section.2.2.p.3"> HTTP/1.1 header field values can be folded onto multiple lines if the continuation line begins with a space or horizontal 793 tab. All linear white space, including folding, has the same semantics as SP. A recipient <em class="bcp14">MAY</em> replace any linear white space with a single SP before interpreting the field value or forwarding the message downstream. 779 <p id="rfc.section.2.2.p.3">All linear white space (LWS) in header field-values has the same semantics as SP. A recipient <em class="bcp14">MAY</em> replace any such linear white space with a single SP before interpreting the field value or forwarding the message downstream. 794 780 </p> 795 781 </div> 796 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.1"></span> <a href="#rule.LWS" class="smpl">LWS</a> = [<a href="#core.rules" class="smpl">CRLF</a>] 1*<a href="#core.rules" class="smpl">WSP</a> 797 </pre><div id="rule.whitespace"> 798 <p id="rfc.section.2.2.p.5"> </p> 782 <p id="rfc.section.2.2.p.4">Historically, HTTP/1.1 header field values allow linear white space folding across multiple lines. However, this specification 783 deprecates its use; senders <em class="bcp14">MUST NOT</em> produce messages that include LWS folding (i.e., use the obs-fold rule), except within the message/http media type (<a href="#internet.media.type.message.http" title="Internet Media Type message/http">Section 9.3.1</a>). Receivers <em class="bcp14">SHOULD</em> still parse folded linear white space. 784 </p> 785 <p id="rfc.section.2.2.p.5">This specification uses three rules to denote the use of linear white space; BWS ("Bad" White Space), OWS (Optional White 786 Space), and RWS (Required White Space). 787 </p> 788 <p id="rfc.section.2.2.p.6">"Bad" white space is allowed by the BNF, but senders <em class="bcp14">SHOULD NOT</em> produce it in messages. Receivers <em class="bcp14">MUST</em> accept it in incoming messages. 789 </p> 790 <p id="rfc.section.2.2.p.7">Required white space is used when at least one linear white space character is required to separate field tokens. In all such 791 cases, a single SP character <em class="bcp14">SHOULD</em> be used. 792 </p> 793 <div id="rule.whitespace"> 794 <p id="rfc.section.2.2.p.8"> </p> 799 795 </div> 800 <div id="rfc.figure.u. 7"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span> <a href="#rule.whitespace" class="smpl">OWS</a> = *( [ obs-fold ] <a href="#core.rules" class="smpl">WSP</a> )796 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span> <a href="#rule.whitespace" class="smpl">OWS</a> = *( [ obs-fold ] <a href="#core.rules" class="smpl">WSP</a> ) 801 797 ; "optional" white space 802 798 <a href="#rule.whitespace" class="smpl">RWS</a> = 1*( [ obs-fold ] <a href="#core.rules" class="smpl">WSP</a> ) … … 805 801 ; "bad" white space 806 802 <a href="#rule.whitespace" class="smpl">obs-fold</a> = <a href="#core.rules" class="smpl">CRLF</a> 807 ; <span class="comment">[rfc.comment.2: to be explained: do not produce]</span>808 803 </pre><div id="rule.TEXT"> 809 <p id="rfc.section.2.2.p. 7"> The TEXT rule is only used for descriptive field contents and values that are not intended to be interpreted by the message804 <p id="rfc.section.2.2.p.10"> The TEXT rule is only used for descriptive field contents and values that are not intended to be interpreted by the message 810 805 parser. Words of *TEXT <em class="bcp14">MAY</em> contain characters from character sets other than ISO-8859-1 <a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a> only when encoded according to the rules of <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[RFC2047]</cite></a>. 811 806 </p> 812 807 </div> 813 <div id="rfc.figure.u. 8"></div><pre class="inline"><span id="rfc.iref.g.5"></span> <a href="#rule.TEXT" class="smpl">TEXT</a> = %x20-7E / %x80-FF / <a href="#rule.LWS" class="smpl">LWS</a>814 ; any <a href="#core.rules" class="smpl">OCTET</a> except <a href="#core.rules" class="smpl">CTL</a>s, but including <a href="#rule. LWS" class="smpl">LWS</a>815 </pre><p id="rfc.section.2.2.p. 9">A CRLF is allowed in the definition of TEXT only as part of a header field continuation. It is expected that the folding LWS808 <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.4"></span> <a href="#rule.TEXT" class="smpl">TEXT</a> = %x20-7E / %x80-FF / <a href="#rule.whitespace" class="smpl">OWS</a> 809 ; any <a href="#core.rules" class="smpl">OCTET</a> except <a href="#core.rules" class="smpl">CTL</a>s, but including <a href="#rule.whitespace" class="smpl">OWS</a> 810 </pre><p id="rfc.section.2.2.p.12">A CRLF is allowed in the definition of TEXT only as part of a header field continuation. It is expected that the folding LWS 816 811 will be replaced with a single SP before interpretation of the TEXT value. 817 812 </p> 818 813 <div id="rule.token.separators"> 819 <p id="rfc.section.2.2.p.1 0"> Many HTTP/1.1 header field values consist of words separated by LWS or special characters. These special characters <em class="bcp14">MUST</em> be in a quoted string to be used within a parameter value (as defined in <a href="#transfer.codings" title="Transfer Codings">Section 3.4</a>).814 <p id="rfc.section.2.2.p.13"> Many HTTP/1.1 header field values consist of words separated by LWS or special characters. These special characters <em class="bcp14">MUST</em> be in a quoted string to be used within a parameter value (as defined in <a href="#transfer.codings" title="Transfer Codings">Section 3.4</a>). 820 815 </p> 821 816 </div> 822 <div id="rfc.figure.u. 9"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span> <a href="#rule.token.separators" class="smpl">separators</a> = "(" / ")" / "<" / ">" / "@"817 <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span> <a href="#rule.token.separators" class="smpl">separators</a> = "(" / ")" / "<" / ">" / "@" 823 818 / "," / ";" / ":" / "\" / <a href="#core.rules" class="smpl">DQUOTE</a> 824 819 / "/" / "[" / "]" / "?" / "=" … … 832 827 <a href="#rule.token.separators" class="smpl">token</a> = 1*<a href="#rule.token.separators" class="smpl">tchar</a> 833 828 </pre><div id="rule.comment"> 834 <p id="rfc.section.2.2.p.1 2"> Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed829 <p id="rfc.section.2.2.p.15"> Comments can be included in some HTTP header fields by surrounding the comment text with parentheses. Comments are only allowed 835 830 in fields containing "comment" as part of their field value definition. In all other fields, parentheses are considered part 836 831 of the field value. 837 832 </p> 838 833 </div> 839 <div id="rfc.figure.u. 10"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#rule.comment" class="smpl">comment</a> = "(" *( <a href="#rule.comment" class="smpl">ctext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> / <a href="#rule.comment" class="smpl">comment</a> ) ")"834 <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span> <a href="#rule.comment" class="smpl">comment</a> = "(" *( <a href="#rule.comment" class="smpl">ctext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> / <a href="#rule.comment" class="smpl">comment</a> ) ")" 840 835 <a href="#rule.comment" class="smpl">ctext</a> = <any <a href="#rule.TEXT" class="smpl">TEXT</a> excluding "(" and ")"> 841 836 </pre><div id="rule.quoted-string"> 842 <p id="rfc.section.2.2.p.1 4"> A string of text is parsed as a single word if it is quoted using double-quote marks.</p>837 <p id="rfc.section.2.2.p.17"> A string of text is parsed as a single word if it is quoted using double-quote marks.</p> 843 838 </div> 844 <div id="rfc.figure.u.1 1"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span> <a href="#rule.quoted-string" class="smpl">quoted-string</a> = ( <a href="#core.rules" class="smpl">DQUOTE</a> *(<a href="#rule.quoted-string" class="smpl">qdtext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> ) <a href="#core.rules" class="smpl">DQUOTE</a> )839 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span> <a href="#rule.quoted-string" class="smpl">quoted-string</a> = ( <a href="#core.rules" class="smpl">DQUOTE</a> *(<a href="#rule.quoted-string" class="smpl">qdtext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> ) <a href="#core.rules" class="smpl">DQUOTE</a> ) 845 840 <a href="#rule.quoted-string" class="smpl">qdtext</a> = <any <a href="#rule.TEXT" class="smpl">TEXT</a> excluding <a href="#core.rules" class="smpl">DQUOTE</a> and "\"> 846 841 </pre><div id="rule.quoted-pair"> 847 <p id="rfc.section.2.2.p.1 6"> The backslash character ("\") <em class="bcp14">MAY</em> be used as a single-character quoting mechanism only within quoted-string and comment constructs.842 <p id="rfc.section.2.2.p.19"> The backslash character ("\") <em class="bcp14">MAY</em> be used as a single-character quoting mechanism only within quoted-string and comment constructs. 848 843 </p> 849 844 </div> 850 <div id="rfc.figure.u.1 2"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span> <a href="#rule.quoted-pair" class="smpl">quoted-text</a> = %x01-09 /845 <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span> <a href="#rule.quoted-pair" class="smpl">quoted-text</a> = %x01-09 / 851 846 %x0B-0C / 852 847 %x0E-FF ; Characters excluding NUL, <a href="#core.rules" class="smpl">CR</a> and <a href="#core.rules" class="smpl">LF</a> … … 854 849 </pre><h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h2> 855 850 <p id="rfc.section.2.3.p.1">The ABNF rules below are defined in other parts:</p> 856 <div id="rfc.figure.u.1 3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">request-header</a> = <request-header, 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#request.header.fields" title="Request Header Fields">Section 4</a>>851 <div id="rfc.figure.u.12"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">request-header</a> = <request-header, 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#request.header.fields" title="Request Header Fields">Section 4</a>> 857 852 <a href="#abnf.dependencies" class="smpl">response-header</a> = <response-header, defined in <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#response.header.fields" title="Response Header Fields">Section 6</a>> 858 </pre><div id="rfc.figure.u.1 4"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">accept-params</a> = <accept-params, 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" title="Accept">Section 6.1</a>>853 </pre><div id="rfc.figure.u.13"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">accept-params</a> = <accept-params, 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" title="Accept">Section 6.1</a>> 859 854 <a href="#abnf.dependencies" class="smpl">entity-body</a> = <entity-body, 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#entity.body" title="Entity Body">Section 4.2</a>> 860 855 <a href="#abnf.dependencies" class="smpl">entity-header</a> = <entity-header, 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>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a>> 861 </pre><div id="rfc.figure.u.1 5"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, 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.pragma" title="Pragma">Section 16.4</a>>856 </pre><div id="rfc.figure.u.14"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, 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.pragma" title="Pragma">Section 16.4</a>> 862 857 <a href="#abnf.dependencies" class="smpl">Pragma</a> = <Pragma, 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.pragma" title="Pragma">Section 16.4</a>> 863 858 <a href="#abnf.dependencies" class="smpl">Warning</a> = <Warning, defined in <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.warning" title="Warning">Section 16.6</a>> … … 873 868 </p> 874 869 <p id="rfc.section.3.1.p.2">The version of an HTTP message is indicated by an HTTP-Version field in the first line of the message. HTTP-Version is case-sensitive.</p> 875 <div id="rfc.figure.u.1 6"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span> <a href="#http.version" class="smpl">HTTP-Version</a> = <a href="#http.version" class="smpl">HTTP-Prot-Name</a> "/" 1*<a href="#core.rules" class="smpl">DIGIT</a> "." 1*<a href="#core.rules" class="smpl">DIGIT</a>870 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> <a href="#http.version" class="smpl">HTTP-Version</a> = <a href="#http.version" class="smpl">HTTP-Prot-Name</a> "/" 1*<a href="#core.rules" class="smpl">DIGIT</a> "." 1*<a href="#core.rules" class="smpl">DIGIT</a> 876 871 <a href="#http.version" class="smpl">HTTP-Prot-Name</a> = %x48.54.54.50 ; "HTTP", case-sensitive 877 872 </pre><p id="rfc.section.3.1.p.4">Note that the major and minor numbers <em class="bcp14">MUST</em> be treated as separate integers and that each <em class="bcp14">MAY</em> be incremented higher than a single digit. Thus, HTTP/2.4 is a lower version than HTTP/2.13, which in turn is lower than HTTP/12.3. … … 904 899 "abs_path", "query", and "authority" from that specification: 905 900 </p> 906 <div id="rfc.figure.u.1 7"></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><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#general.syntax" class="smpl">absoluteURI</a> = <absoluteURI, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.2"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3">Section 3</a>>901 <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.16"></span><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><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span> <a href="#general.syntax" class="smpl">absoluteURI</a> = <absoluteURI, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.2"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3">Section 3</a>> 907 902 <a href="#general.syntax" class="smpl">authority</a> = <authority, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.3"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3.2">Section 3.2</a>> 908 903 <a href="#general.syntax" class="smpl">fragment</a> = <fragment, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.4"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-4.1">Section 4.1</a>> … … 926 921 and semantics for http URLs. 927 922 </p> 928 <div id="rfc.figure.u.1 8"></div><pre class="inline"><span id="rfc.iref.g.24"></span> <a href="#http.url" class="smpl">http-URL</a> = "http:" "//" <a href="#general.syntax" class="smpl">uri-host</a> [ ":" <a href="#general.syntax" class="smpl">port</a> ]923 <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.23"></span> <a href="#http.url" class="smpl">http-URL</a> = "http:" "//" <a href="#general.syntax" class="smpl">uri-host</a> [ ":" <a href="#general.syntax" class="smpl">port</a> ] 929 924 [ <a href="#general.syntax" class="smpl">path-absolute</a> [ "?" <a href="#general.syntax" class="smpl">query</a> ]] 930 925 </pre><p id="rfc.section.3.2.2.p.3">If the port is empty or not given, port 80 is assumed. The semantics are that the identified resource is located at the server … … 949 944 </p> 950 945 <p id="rfc.section.3.2.3.p.3">For example, the following three URIs are equivalent:</p> 951 <div id="rfc.figure.u.1 9"></div><pre class="text"> http://example.com:80/~smith/home.html946 <div id="rfc.figure.u.18"></div><pre class="text"> http://example.com:80/~smith/home.html 952 947 http://EXAMPLE.com/%7Esmith/home.html 953 948 http://EXAMPLE.com:/%7esmith/home.html … … 955 950 <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a> <a id="full.date" href="#full.date">Full Date</a></h3> 956 951 <p id="rfc.section.3.3.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p> 957 <div id="rfc.figure.u. 20"></div><pre class="text"> Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123952 <div id="rfc.figure.u.19"></div><pre class="text"> Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123 958 953 Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 959 954 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format … … 970 965 time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional LWS beyond that specifically included as SP in the grammar. 971 966 </p> 972 <div id="rfc.figure.u.2 1"></div><pre class="inline"><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span><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> <a href="#full.date" class="smpl">HTTP-date</a> = <a href="#full.date" class="smpl">rfc1123-date</a> / <a href="#full.date" class="smpl">obsolete-date</a>967 <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span> <a href="#full.date" class="smpl">HTTP-date</a> = <a href="#full.date" class="smpl">rfc1123-date</a> / <a href="#full.date" class="smpl">obsolete-date</a> 973 968 <a href="#full.date" class="smpl">obsolete-date</a> = <a href="#full.date" class="smpl">rfc850-date</a> / <a href="#full.date" class="smpl">asctime-date</a> 974 969 <a href="#full.date" class="smpl">rfc1123-date</a> = <a href="#full.date" class="smpl">wkday</a> "," <a href="#core.rules" class="smpl">SP</a> date1 <a href="#core.rules" class="smpl">SP</a> time <a href="#core.rules" class="smpl">SP</a> GMT … … 1029 1024 is a property of the message, not of the original entity. 1030 1025 </p> 1031 <div id="rfc.figure.u.2 2"></div><pre class="inline"><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span> <a href="#transfer.codings" class="smpl">transfer-coding</a> = "chunked" / <a href="#transfer.codings" class="smpl">transfer-extension</a>1026 <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span> <a href="#transfer.codings" class="smpl">transfer-coding</a> = "chunked" / <a href="#transfer.codings" class="smpl">transfer-extension</a> 1032 1027 <a href="#transfer.codings" class="smpl">transfer-extension</a> = <a href="#rule.token.separators" class="smpl">token</a> *( <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#transfer.codings" class="smpl">parameter</a> ) 1033 1028 </pre><div id="rule.parameter"> 1034 1029 <p id="rfc.section.3.4.p.3"> Parameters are in the form of attribute/value pairs.</p> 1035 1030 </div> 1036 <div id="rfc.figure.u.2 3"></div><pre class="inline"><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span> <a href="#transfer.codings" class="smpl">parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a>1031 <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span> <a href="#transfer.codings" class="smpl">parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a> 1037 1032 <a href="#rule.parameter" class="smpl">attribute</a> = <a href="#rule.token.separators" class="smpl">token</a> 1038 1033 <a href="#rule.parameter" class="smpl">value</a> = <a href="#rule.token.separators" class="smpl">token</a> / <a href="#rule.quoted-string" class="smpl">quoted-string</a> … … 1059 1054 necessary for the recipient to verify that it has received the full message. 1060 1055 </p> 1061 <div id="rfc.figure.u.2 4"></div><pre class="inline"><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span> <a href="#chunked.transfer.encoding" class="smpl">Chunked-Body</a> = *<a href="#chunked.transfer.encoding" class="smpl">chunk</a>1056 <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span> <a href="#chunked.transfer.encoding" class="smpl">Chunked-Body</a> = *<a href="#chunked.transfer.encoding" class="smpl">chunk</a> 1062 1057 <a href="#chunked.transfer.encoding" class="smpl">last-chunk</a> 1063 1058 <a href="#chunked.transfer.encoding" class="smpl">trailer-part</a> … … 1096 1091 </p> 1097 1092 <p id="rfc.section.3.4.1.p.7">A process for decoding the "chunked" transfer-coding can be represented in pseudo-code as:</p> 1098 <div id="rfc.figure.u.2 5"></div><pre class="text"> length := 01093 <div id="rfc.figure.u.24"></div><pre class="text"> length := 0 1099 1094 read chunk-size, chunk-ext (if any) and CRLF 1100 1095 while (chunk-size > 0) { … … 1118 1113 space. By convention, the products are listed in order of their significance for identifying the application. 1119 1114 </p> 1120 <div id="rfc.figure.u.2 6"></div><pre class="inline"><span id="rfc.iref.g.51"></span><span id="rfc.iref.g.52"></span> <a href="#product.tokens" class="smpl">product</a> = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]1115 <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span> <a href="#product.tokens" class="smpl">product</a> = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>] 1121 1116 <a href="#product.tokens" class="smpl">product-version</a> = <a href="#rule.token.separators" class="smpl">token</a> 1122 1117 </pre><p id="rfc.section.3.5.p.3">Examples:</p> 1123 <div id="rfc.figure.u.2 7"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b31118 <div id="rfc.figure.u.26"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1124 1119 Server: Apache/0.8.4 1125 1120 </pre><p id="rfc.section.3.5.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token character <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value). … … 1128 1123 <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a id="message.types" href="#message.types">Message Types</a></h2> 1129 1124 <p id="rfc.section.4.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p> 1130 <div id="rfc.figure.u.2 8"></div><pre class="inline"><span id="rfc.iref.g.53"></span> <a href="#message.types" class="smpl">HTTP-message</a> = <a href="#request" class="smpl">Request</a> / <a href="#response" class="smpl">Response</a> ; HTTP/1.1 messages1125 <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.52"></span> <a href="#message.types" class="smpl">HTTP-message</a> = <a href="#request" class="smpl">Request</a> / <a href="#response" class="smpl">Response</a> ; HTTP/1.1 messages 1131 1126 </pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section 5</a>) and Response (<a href="#response" title="Response">Section 6</a>) messages use the generic message format of <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header 1132 1127 fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header 1133 1128 fields, and possibly a message-body. 1134 1129 </p> 1135 <div id="rfc.figure.u.2 9"></div><pre class="inline"><span id="rfc.iref.g.54"></span><span id="rfc.iref.g.55"></span> <a href="#message.types" class="smpl">generic-message</a> = <a href="#message.types" class="smpl">start-line</a>1130 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.53"></span><span id="rfc.iref.g.54"></span> <a href="#message.types" class="smpl">generic-message</a> = <a href="#message.types" class="smpl">start-line</a> 1136 1131 *(<a href="#message.headers" class="smpl">message-header</a> <a href="#core.rules" class="smpl">CRLF</a>) 1137 1132 <a href="#core.rules" class="smpl">CRLF</a> … … 1151 1146 forms. 1152 1147 </p> 1153 <div id="rfc.figure.u. 30"></div><pre class="inline"><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span> <a href="#message.headers" class="smpl">message-header</a> = <a href="#message.headers" class="smpl">field-name</a> ":" [ <a href="#message.headers" class="smpl">field-value</a> ]1148 <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span> <a href="#message.headers" class="smpl">message-header</a> = <a href="#message.headers" class="smpl">field-name</a> ":" [ <a href="#message.headers" class="smpl">field-value</a> ] 1154 1149 <a href="#message.headers" class="smpl">field-name</a> = <a href="#rule.token.separators" class="smpl">token</a> 1155 <a href="#message.headers" class="smpl">field-value</a> = *( <a href="#message.headers" class="smpl">field-content</a> / <a href="#rule. LWS" class="smpl">LWS</a> )1150 <a href="#message.headers" class="smpl">field-value</a> = *( <a href="#message.headers" class="smpl">field-content</a> / <a href="#rule.whitespace" class="smpl">OWS</a> ) 1156 1151 <a href="#message.headers" class="smpl">field-content</a> = <field content> 1157 1152 ; the <a href="#core.rules" class="smpl">OCTET</a>s making up the field-value 1158 1153 ; and consisting of either *<a href="#rule.TEXT" class="smpl">TEXT</a> or combinations 1159 1154 ; of <a href="#rule.token.separators" class="smpl">token</a>, <a href="#rule.token.separators" class="smpl">separators</a>, and <a href="#rule.quoted-string" class="smpl">quoted-string</a> 1160 </pre><p id="rfc.section.4.2.p.3"> <span class="comment">[rfc.comment. 3: whitespace between field-name and colon is an error and MUST NOT be accepted]</span>1155 </pre><p id="rfc.section.4.2.p.3"> <span class="comment">[rfc.comment.1: whitespace between field-name and colon is an error and MUST NOT be accepted]</span> 1161 1156 </p> 1162 1157 <p id="rfc.section.4.2.p.4">The field-content does not include any leading or trailing LWS: linear white space occurring before the first non-whitespace … … 1184 1179 header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.2" title="Transfer-Encoding">Section 8.7</a>). 1185 1180 </p> 1186 <div id="rfc.figure.u.3 1"></div><pre class="inline"><span id="rfc.iref.g.60"></span> <a href="#message.body" class="smpl">message-body</a> = <a href="#abnf.dependencies" class="smpl">entity-body</a>1181 <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.59"></span> <a href="#message.body" class="smpl">message-body</a> = <a href="#abnf.dependencies" class="smpl">entity-body</a> 1187 1182 / <entity-body encoded as per <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>> 1188 1183 </pre><p id="rfc.section.4.3.p.3">Transfer-Encoding <em class="bcp14">MUST</em> be used to indicate any transfer-codings applied by an application to ensure safe and proper transfer of the message. Transfer-Encoding … … 1252 1247 to the entity being transferred. These header fields apply only to the message being transmitted. 1253 1248 </p> 1254 <div id="rfc.figure.u.3 2"></div><pre class="inline"><span id="rfc.iref.g.61"></span> <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a> ; <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.cache-control" title="Cache-Control">Section 16.2</a>1249 <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.60"></span> <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a> ; <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.cache-control" title="Cache-Control">Section 16.2</a> 1255 1250 / <a href="#header.connection" class="smpl">Connection</a> ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section 8.1</a> 1256 1251 / <a href="#header.date" class="smpl">Date</a> ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section 8.3</a> … … 1269 1264 resource, the identifier of the resource, and the protocol version in use. 1270 1265 </p> 1271 <div id="rfc.figure.u.3 3"></div><pre class="inline"><span id="rfc.iref.g.62"></span> <a href="#request" class="smpl">Request</a> = <a href="#request-line" class="smpl">Request-Line</a> ; <a href="#request-line" title="Request-Line">Section 5.1</a>1266 <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.61"></span> <a href="#request" class="smpl">Request</a> = <a href="#request-line" class="smpl">Request-Line</a> ; <a href="#request-line" title="Request-Line">Section 5.1</a> 1272 1267 *(( <a href="#general.header.fields" class="smpl">general-header</a> ; <a href="#general.header.fields" title="General Header Fields">Section 4.5</a> 1273 1268 / <a href="#abnf.dependencies" class="smpl">request-header</a> ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> … … 1279 1274 elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence. 1280 1275 </p> 1281 <div id="rfc.figure.u.3 4"></div><pre class="inline"><span id="rfc.iref.g.63"></span> <a href="#request-line" class="smpl">Request-Line</a> = <a href="#method" class="smpl">Method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-uri" class="smpl">Request-URI</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">CRLF</a>1276 <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.62"></span> <a href="#request-line" class="smpl">Request-Line</a> = <a href="#method" class="smpl">Method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-uri" class="smpl">Request-URI</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">CRLF</a> 1282 1277 </pre><h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a> <a id="method" href="#method">Method</a></h3> 1283 1278 <p id="rfc.section.5.1.1.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p> 1284 <div id="rfc.figure.u.3 5"></div><pre class="inline"><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span> <a href="#method" class="smpl">Method</a> = <a href="#rule.token.separators" class="smpl">token</a>1279 <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span> <a href="#method" class="smpl">Method</a> = <a href="#rule.token.separators" class="smpl">token</a> 1285 1280 </pre><h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a> <a id="request-uri" href="#request-uri">Request-URI</a></h3> 1286 1281 <p id="rfc.section.5.1.2.p.1">The Request-URI is a Uniform Resource Identifier (<a href="#uri" title="Uniform Resource Identifiers">Section 3.2</a>) and identifies the resource upon which to apply the request. 1287 1282 </p> 1288 <div id="rfc.figure.u.3 6"></div><pre class="inline"><span id="rfc.iref.g.66"></span> <a href="#request-uri" class="smpl">Request-URI</a> = "*"1283 <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.65"></span> <a href="#request-uri" class="smpl">Request-URI</a> = "*" 1289 1284 / <a href="#general.syntax" class="smpl">absoluteURI</a> 1290 1285 / ( <a href="#general.syntax" class="smpl">path-absolute</a> [ "?" <a href="#general.syntax" class="smpl">query</a> ] ) … … 1294 1289 apply to a resource. One example would be 1295 1290 </p> 1296 <div id="rfc.figure.u.3 7"></div><pre class="text"> OPTIONS * HTTP/1.11291 <div id="rfc.figure.u.36"></div><pre class="text"> OPTIONS * HTTP/1.1 1297 1292 </pre><p id="rfc.section.5.1.2.p.5">The absoluteURI form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache, 1298 1293 and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absoluteURI. In order to avoid request … … 1300 1295 Request-Line would be: 1301 1296 </p> 1302 <div id="rfc.figure.u.3 8"></div><pre class="text"> GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.11297 <div id="rfc.figure.u.37"></div><pre class="text"> GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1 1303 1298 </pre><p id="rfc.section.5.1.2.p.7">To allow for transition to absoluteURIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absoluteURI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies. 1304 1299 </p> … … 1309 1304 server would create a TCP connection to port 80 of the host "www.example.org" and send the lines: 1310 1305 </p> 1311 <div id="rfc.figure.u.3 9"></div><pre class="text"> GET /pub/WWW/TheProject.html HTTP/1.11306 <div id="rfc.figure.u.38"></div><pre class="text"> GET /pub/WWW/TheProject.html HTTP/1.1 1312 1307 Host: www.example.org 1313 1308 </pre><p id="rfc.section.5.1.2.p.11">followed by the remainder of the Request. Note that the absolute path cannot be empty; if none is present in the original … … 1347 1342 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="response" href="#response">Response</a></h1> 1348 1343 <p id="rfc.section.6.p.1">After receiving and interpreting a request message, a server responds with an HTTP response message.</p> 1349 <div id="rfc.figure.u. 40"></div><pre class="inline"><span id="rfc.iref.g.67"></span> <a href="#response" class="smpl">Response</a> = <a href="#status-line" class="smpl">Status-Line</a> ; <a href="#status-line" title="Status-Line">Section 6.1</a>1344 <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.66"></span> <a href="#response" class="smpl">Response</a> = <a href="#status-line" class="smpl">Status-Line</a> ; <a href="#status-line" title="Status-Line">Section 6.1</a> 1350 1345 *(( <a href="#general.header.fields" class="smpl">general-header</a> ; <a href="#general.header.fields" title="General Header Fields">Section 4.5</a> 1351 1346 / <a href="#abnf.dependencies" class="smpl">response-header</a> ; <a href="#Part2" id="rfc.xref.Part2.9"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> … … 1358 1353 CRLF sequence. 1359 1354 </p> 1360 <div id="rfc.figure.u.4 1"></div><pre class="inline"><span id="rfc.iref.g.68"></span> <a href="#status-line" class="smpl">Status-Line</a> = <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> <a href="#core.rules" class="smpl">CRLF</a>1355 <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.67"></span> <a href="#status-line" class="smpl">Status-Line</a> = <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> <a href="#core.rules" class="smpl">CRLF</a> 1361 1356 </pre><h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a> <a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3> 1362 1357 <p id="rfc.section.6.1.1.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes … … 1375 1370 <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li> 1376 1371 </ul> 1377 <div id="rfc.figure.u.4 2"></div><pre class="inline"><span id="rfc.iref.g.69"></span><span id="rfc.iref.g.70"></span><span id="rfc.iref.g.71"></span> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = 3<a href="#core.rules" class="smpl">DIGIT</a>1372 <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.68"></span><span id="rfc.iref.g.69"></span><span id="rfc.iref.g.70"></span> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = 3<a href="#core.rules" class="smpl">DIGIT</a> 1378 1373 <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> = *<<a href="#rule.TEXT" class="smpl">TEXT</a>, excluding <a href="#core.rules" class="smpl">CR</a>, <a href="#core.rules" class="smpl">LF</a>> 1379 1374 </pre><h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="connections" href="#connections">Connections</a></h1> … … 1567 1562 </p> 1568 1563 <p id="rfc.section.8.1.p.2">The Connection header's value has the following grammar:</p> 1569 <div id="rfc.figure.u.4 3"></div><pre class="inline"><span id="rfc.iref.g.72"></span><span id="rfc.iref.g.73"></span><span id="rfc.iref.g.74"></span> <a href="#header.connection" class="smpl">Connection</a> = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a>1564 <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.71"></span><span id="rfc.iref.g.72"></span><span id="rfc.iref.g.73"></span> <a href="#header.connection" class="smpl">Connection</a> = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a> 1570 1565 <a href="#header.connection" class="smpl">Connection-v</a> = 1#<a href="#header.connection" class="smpl">connection-token</a> 1571 1566 <a href="#header.connection" class="smpl">connection-token</a> = <a href="#rule.token.separators" class="smpl">token</a> … … 1580 1575 of the response. For example, 1581 1576 </p> 1582 <div id="rfc.figure.u.4 4"></div><pre class="text"> Connection: close1577 <div id="rfc.figure.u.43"></div><pre class="text"> Connection: close 1583 1578 </pre><p id="rfc.section.8.1.p.8">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered `persistent' (<a href="#persistent.connections" title="Persistent Connections">Section 7.1</a>) after the current request/response is complete. 1584 1579 </p> … … 1596 1591 or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET. 1597 1592 </p> 1598 <div id="rfc.figure.u.4 5"></div><pre class="inline"><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span> <a href="#header.content-length" class="smpl">Content-Length</a> = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a>1593 <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span> <a href="#header.content-length" class="smpl">Content-Length</a> = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a> 1599 1594 <a href="#header.content-length" class="smpl">Content-Length-v</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> 1600 1595 </pre><p id="rfc.section.8.2.p.3">An example is</p> 1601 <div id="rfc.figure.u.4 6"></div><pre class="text"> Content-Length: 34951596 <div id="rfc.figure.u.45"></div><pre class="text"> Content-Length: 3495 1602 1597 </pre><p id="rfc.section.8.2.p.5">Applications <em class="bcp14">SHOULD</em> use this field to indicate the transfer-length of the message-body, unless this is prohibited by the rules in <a href="#message.length" title="Message Length">Section 4.4</a>. 1603 1598 </p> … … 1614 1609 as orig-date in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as described in <a href="#full.date" title="Full Date">Section 3.3.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 1615 1610 </p> 1616 <div id="rfc.figure.u.4 7"></div><pre class="inline"><span id="rfc.iref.g.77"></span><span id="rfc.iref.g.78"></span> <a href="#header.date" class="smpl">Date</a> = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a>1611 <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span> <a href="#header.date" class="smpl">Date</a> = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a> 1617 1612 <a href="#header.date" class="smpl">Date-v</a> = <a href="#full.date" class="smpl">HTTP-date</a> 1618 1613 </pre><p id="rfc.section.8.3.p.3">An example is</p> 1619 <div id="rfc.figure.u.4 8"></div><pre class="text"> Date: Tue, 15 Nov 1994 08:12:31 GMT1614 <div id="rfc.figure.u.47"></div><pre class="text"> Date: Tue, 15 Nov 1994 08:12:31 GMT 1620 1615 </pre><p id="rfc.section.8.3.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases: 1621 1616 </p> … … 1653 1648 a single IP address. 1654 1649 </p> 1655 <div id="rfc.figure.u.4 9"></div><pre class="inline"><span id="rfc.iref.g.79"></span><span id="rfc.iref.g.80"></span> <a href="#header.host" class="smpl">Host</a> = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a>1650 <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.78"></span><span id="rfc.iref.g.79"></span> <a href="#header.host" class="smpl">Host</a> = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a> 1656 1651 <a href="#header.host" class="smpl">Host-v</a> = <a href="#general.syntax" class="smpl">uri-host</a> [ ":" <a href="#general.syntax" class="smpl">port</a> ] ; <a href="#http.url" title="http URL">Section 3.2.2</a> 1657 1652 </pre><p id="rfc.section.8.4.p.3">A "host" without any trailing port information implies the default port for the service requested (e.g., "80" for an HTTP 1658 1653 URL). For example, a request on the origin server for <http://www.example.org/pub/WWW/> would properly include: 1659 1654 </p> 1660 <div id="rfc.figure.u. 50"></div><pre class="text"> GET /pub/WWW/ HTTP/1.11655 <div id="rfc.figure.u.49"></div><pre class="text"> GET /pub/WWW/ HTTP/1.1 1661 1656 Host: www.example.org 1662 1657 </pre><p id="rfc.section.8.4.p.5">A client <em class="bcp14">MUST</em> include a Host header field in all HTTP/1.1 request messages. If the requested URI does not include an Internet host name … … 1673 1668 and/or a comma-separated list of extension transfer-coding names with optional accept parameters (as described in <a href="#transfer.codings" title="Transfer Codings">Section 3.4</a>). 1674 1669 </p> 1675 <div id="rfc.figure.u.5 1"></div><pre class="inline"><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span> <a href="#header.te" class="smpl">TE</a> = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a>1670 <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span> <a href="#header.te" class="smpl">TE</a> = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a> 1676 1671 <a href="#header.te" class="smpl">TE-v</a> = #<a href="#header.te" class="smpl">t-codings</a> 1677 1672 <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( <a href="#transfer.codings" class="smpl">transfer-extension</a> [ <a href="#abnf.dependencies" class="smpl">accept-params</a> ] ) … … 1680 1675 </p> 1681 1676 <p id="rfc.section.8.5.p.4">Examples of its use are:</p> 1682 <div id="rfc.figure.u.5 2"></div><pre class="text"> TE: deflate1677 <div id="rfc.figure.u.51"></div><pre class="text"> TE: deflate 1683 1678 TE: 1684 1679 TE: trailers, deflate;q=0.5 … … 1717 1712 chunked transfer-coding. 1718 1713 </p> 1719 <div id="rfc.figure.u.5 3"></div><pre class="inline"><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span> <a href="#header.trailer" class="smpl">Trailer</a> = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a>1714 <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span> <a href="#header.trailer" class="smpl">Trailer</a> = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a> 1720 1715 <a href="#header.trailer" class="smpl">Trailer-v</a> = 1#<a href="#message.headers" class="smpl">field-name</a> 1721 1716 </pre><p id="rfc.section.8.6.p.3">An HTTP/1.1 message <em class="bcp14">SHOULD</em> include a Trailer header field in a message using chunked transfer-coding with a non-empty trailer. Doing so allows the recipient … … 1738 1733 transfer-coding is a property of the message, not of the entity. 1739 1734 </p> 1740 <div id="rfc.figure.u.5 4"></div><pre class="inline"><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span> <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a>1735 <div id="rfc.figure.u.53"></div><pre class="inline"><span id="rfc.iref.g.85"></span><span id="rfc.iref.g.86"></span> <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> 1741 1736 <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a> 1742 1737 </pre><p id="rfc.section.8.7.p.3">Transfer-codings are defined in <a href="#transfer.codings" title="Transfer Codings">Section 3.4</a>. An example is: 1743 1738 </p> 1744 <div id="rfc.figure.u.5 5"></div><pre class="text"> Transfer-Encoding: chunked1739 <div id="rfc.figure.u.54"></div><pre class="text"> Transfer-Encoding: chunked 1745 1740 </pre><p id="rfc.section.8.7.p.5">If multiple encodings have been applied to an entity, the transfer-codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other entity-header fields not defined by this specification. 1746 1741 </p> … … 1752 1747 to use if the server finds it appropriate to switch protocols. The server <em class="bcp14">MUST</em> use the Upgrade header field within a 101 (Switching Protocols) response to indicate which protocol(s) are being switched. 1753 1748 </p> 1754 <div id="rfc.figure.u.5 6"></div><pre class="inline"><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span> <a href="#header.upgrade" class="smpl">Upgrade</a> = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a>1749 <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.87"></span><span id="rfc.iref.g.88"></span> <a href="#header.upgrade" class="smpl">Upgrade</a> = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a> 1755 1750 <a href="#header.upgrade" class="smpl">Upgrade-v</a> = 1#<a href="#product.tokens" class="smpl">product</a> 1756 1751 </pre><p id="rfc.section.8.8.p.3">For example,</p> 1757 <div id="rfc.figure.u.5 7"></div><pre class="text"> Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x111752 <div id="rfc.figure.u.56"></div><pre class="text"> Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11 1758 1753 </pre><p id="rfc.section.8.8.p.5">The Upgrade header field is intended to provide a simple mechanism for transition from HTTP/1.1 to some other, incompatible 1759 1754 protocol. It does so by allowing the client to advertise its desire to use another protocol, such as a later version of HTTP … … 1784 1779 of all senders along the request/response chain. 1785 1780 </p> 1786 <div id="rfc.figure.u.5 8"></div><pre class="inline"><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span><span id="rfc.iref.g.94"></span><span id="rfc.iref.g.95"></span><span id="rfc.iref.g.96"></span> <a href="#header.via" class="smpl">Via</a> = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a>1781 <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.89"></span><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span><span id="rfc.iref.g.94"></span><span id="rfc.iref.g.95"></span> <a href="#header.via" class="smpl">Via</a> = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a> 1787 1782 <a href="#header.via" class="smpl">Via-v</a> = 1#( <a href="#header.via" class="smpl">received-protocol</a> <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#header.via" class="smpl">received-by</a> [ <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#rule.comment" class="smpl">comment</a> ] ) 1788 1783 <a href="#header.via" class="smpl">received-protocol</a> = [ <a href="#header.via" class="smpl">protocol-name</a> "/" ] <a href="#header.via" class="smpl">protocol-version</a> … … 1808 1803 server at www.example.com. The request received by www.example.com would then have the following Via header field: 1809 1804 </p> 1810 <div id="rfc.figure.u.5 9"></div><pre class="text"> Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)1805 <div id="rfc.figure.u.58"></div><pre class="text"> Via: 1.0 fred, 1.1 p.example.net (Apache/1.1) 1811 1806 </pre><p id="rfc.section.8.9.p.9">Proxies and gateways used as a portal through a network firewall <em class="bcp14">SHOULD NOT</em>, by default, forward the names and ports of hosts within the firewall region. This information <em class="bcp14">SHOULD</em> only be propagated if explicitly enabled. If not enabled, the received-by host of any host behind the firewall <em class="bcp14">SHOULD</em> be replaced by an appropriate pseudonym for that host. 1812 1807 </p> … … 1814 1809 For example, 1815 1810 </p> 1816 <div id="rfc.figure.u. 60"></div><pre class="text"> Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy1811 <div id="rfc.figure.u.59"></div><pre class="text"> Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy 1817 1812 </pre><p id="rfc.section.8.9.p.12">could be collapsed to</p> 1818 <div id="rfc.figure.u.6 1"></div><pre class="text"> Via: 1.0 ricky, 1.1 mertz, 1.0 lucy1813 <div id="rfc.figure.u.60"></div><pre class="text"> Via: 1.0 ricky, 1.1 mertz, 1.0 lucy 1819 1814 </pre><p id="rfc.section.8.9.p.14">Applications <em class="bcp14">SHOULD NOT</em> combine multiple entries unless they are all under the same organizational control and the hosts have already been replaced 1820 1815 by pseudonyms. Applications <em class="bcp14">MUST NOT</em> combine entries which have different received-protocol values. … … 2563 2558 </dd> 2564 2559 </dl> 2565 <p id="rfc.section.D.p.16"> <span id="rfc.iref.g.9 7"></span> <dfn>gateway</dfn>2560 <p id="rfc.section.D.p.16"> <span id="rfc.iref.g.96"></span> <dfn>gateway</dfn> 2566 2561 </p> 2567 2562 <dl class="empty"> … … 2599 2594 <dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd> 2600 2595 </dl> 2601 <p id="rfc.section.D.p.21"> <span id="rfc.iref.i. 2"></span> <span id="rfc.iref.o.2"></span> <dfn>inbound</dfn>/<dfn>outbound</dfn>2596 <p id="rfc.section.D.p.21"> <span id="rfc.iref.i.1"></span> <span id="rfc.iref.o.2"></span> <dfn>inbound</dfn>/<dfn>outbound</dfn> 2602 2597 </p> 2603 2598 <dl class="empty"> … … 2796 2791 </li> 2797 2792 <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind"> 2798 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.9 7">D</a></li>2793 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.96">D</a></li> 2799 2794 <li class="indline1"><tt>Grammar</tt> 2800 2795 <ul class="ind"> 2801 <li class="indline1"><tt>absoluteURI</tt> <a class="iref" href="#rfc.iref.g.17"><b>3.2.1</b></a></li> 2802 <li class="indline1"><tt>asctime-date</tt> <a class="iref" href="#rfc.iref.g.29"><b>3.3.1</b></a></li> 2803 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.40"><b>3.4</b></a></li> 2804 <li class="indline1"><tt>authority</tt> <a class="iref" href="#rfc.iref.g.18"><b>3.2.1</b></a></li> 2805 <li class="indline1"><tt>BWS</tt> <a class="iref" href="#rfc.iref.g.4"><b>2.2</b></a></li> 2806 <li class="indline1"><tt>chunk</tt> <a class="iref" href="#rfc.iref.g.43"><b>3.4.1</b></a></li> 2807 <li class="indline1"><tt>chunk-data</tt> <a class="iref" href="#rfc.iref.g.49"><b>3.4.1</b></a></li> 2808 <li class="indline1"><tt>chunk-ext</tt> <a class="iref" href="#rfc.iref.g.46"><b>3.4.1</b></a></li> 2809 <li class="indline1"><tt>chunk-ext-name</tt> <a class="iref" href="#rfc.iref.g.47"><b>3.4.1</b></a></li> 2810 <li class="indline1"><tt>chunk-ext-val</tt> <a class="iref" href="#rfc.iref.g.48"><b>3.4.1</b></a></li> 2811 <li class="indline1"><tt>chunk-size</tt> <a class="iref" href="#rfc.iref.g.44"><b>3.4.1</b></a></li> 2812 <li class="indline1"><tt>Chunked-Body</tt> <a class="iref" href="#rfc.iref.g.42"><b>3.4.1</b></a></li> 2813 <li class="indline1"><tt>comment</tt> <a class="iref" href="#rfc.iref.g.9"><b>2.2</b></a></li> 2814 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g.72"><b>8.1</b></a></li> 2815 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g.74"><b>8.1</b></a></li> 2816 <li class="indline1"><tt>Connection-v</tt> <a class="iref" href="#rfc.iref.g.73"><b>8.1</b></a></li> 2817 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g.75"><b>8.2</b></a></li> 2818 <li class="indline1"><tt>Content-Length-v</tt> <a class="iref" href="#rfc.iref.g.76"><b>8.2</b></a></li> 2819 <li class="indline1"><tt>ctext</tt> <a class="iref" href="#rfc.iref.g.10"><b>2.2</b></a></li> 2820 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.77"><b>8.3</b></a></li> 2821 <li class="indline1"><tt>Date-v</tt> <a class="iref" href="#rfc.iref.g.78"><b>8.3</b></a></li> 2822 <li class="indline1"><tt>date1</tt> <a class="iref" href="#rfc.iref.g.30"><b>3.3.1</b></a></li> 2823 <li class="indline1"><tt>date2</tt> <a class="iref" href="#rfc.iref.g.31"><b>3.3.1</b></a></li> 2824 <li class="indline1"><tt>date3</tt> <a class="iref" href="#rfc.iref.g.32"><b>3.3.1</b></a></li> 2825 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.70"><b>6.1.1</b></a></li> 2826 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.65"><b>5.1.1</b></a></li> 2827 <li class="indline1"><tt>field-content</tt> <a class="iref" href="#rfc.iref.g.59"><b>4.2</b></a></li> 2828 <li class="indline1"><tt>field-name</tt> <a class="iref" href="#rfc.iref.g.57"><b>4.2</b></a></li> 2829 <li class="indline1"><tt>field-value</tt> <a class="iref" href="#rfc.iref.g.58"><b>4.2</b></a></li> 2830 <li class="indline1"><tt>general-header</tt> <a class="iref" href="#rfc.iref.g.61"><b>4.5</b></a></li> 2831 <li class="indline1"><tt>generic-message</tt> <a class="iref" href="#rfc.iref.g.54"><b>4.1</b></a></li> 2832 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.79"><b>8.4</b></a></li> 2833 <li class="indline1"><tt>Host-v</tt> <a class="iref" href="#rfc.iref.g.80"><b>8.4</b></a></li> 2834 <li class="indline1"><tt>HTTP-date</tt> <a class="iref" href="#rfc.iref.g.25"><b>3.3.1</b></a></li> 2835 <li class="indline1"><tt>HTTP-message</tt> <a class="iref" href="#rfc.iref.g.53"><b>4.1</b></a></li> 2836 <li class="indline1"><tt>HTTP-Prot-Name</tt> <a class="iref" href="#rfc.iref.g.16"><b>3.1</b></a></li> 2837 <li class="indline1"><tt>http-URL</tt> <a class="iref" href="#rfc.iref.g.24"><b>3.2.2</b></a></li> 2838 <li class="indline1"><tt>HTTP-Version</tt> <a class="iref" href="#rfc.iref.g.15"><b>3.1</b></a></li> 2839 <li class="indline1"><tt>last-chunk</tt> <a class="iref" href="#rfc.iref.g.45"><b>3.4.1</b></a></li> 2840 <li class="indline1"><tt>LWS</tt> <a class="iref" href="#rfc.iref.g.1"><b>2.2</b></a></li> 2841 <li class="indline1"><tt>message-body</tt> <a class="iref" href="#rfc.iref.g.60"><b>4.3</b></a></li> 2842 <li class="indline1"><tt>message-header</tt> <a class="iref" href="#rfc.iref.g.56"><b>4.2</b></a></li> 2843 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.64"><b>5.1.1</b></a></li> 2844 <li class="indline1"><tt>month</tt> <a class="iref" href="#rfc.iref.g.36"><b>3.3.1</b></a></li> 2845 <li class="indline1"><tt>obsolete-date</tt> <a class="iref" href="#rfc.iref.g.27"><b>3.3.1</b></a></li> 2846 <li class="indline1"><tt>OWS</tt> <a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li> 2847 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.39"><b>3.4</b></a></li> 2848 <li class="indline1"><tt>path-absolute</tt> <a class="iref" href="#rfc.iref.g.19"><b>3.2.1</b></a></li> 2849 <li class="indline1"><tt>port</tt> <a class="iref" href="#rfc.iref.g.20"><b>3.2.1</b></a></li> 2850 <li class="indline1"><tt>product</tt> <a class="iref" href="#rfc.iref.g.51"><b>3.5</b></a></li> 2851 <li class="indline1"><tt>product-version</tt> <a class="iref" href="#rfc.iref.g.52"><b>3.5</b></a></li> 2852 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.93"><b>8.9</b></a></li> 2853 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.94"><b>8.9</b></a></li> 2854 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.96"><b>8.9</b></a></li> 2855 <li class="indline1"><tt>qdtext</tt> <a class="iref" href="#rfc.iref.g.12"><b>2.2</b></a></li> 2856 <li class="indline1"><tt>query</tt> <a class="iref" href="#rfc.iref.g.21"><b>3.2.1</b></a></li> 2857 <li class="indline1"><tt>quoted-pair</tt> <a class="iref" href="#rfc.iref.g.14"><b>2.2</b></a></li> 2858 <li class="indline1"><tt>quoted-string</tt> <a class="iref" href="#rfc.iref.g.11"><b>2.2</b></a></li> 2859 <li class="indline1"><tt>quoted-text</tt> <a class="iref" href="#rfc.iref.g.13"><b>2.2</b></a></li> 2860 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.71"><b>6.1.1</b></a></li> 2861 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.95"><b>8.9</b></a></li> 2862 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.92"><b>8.9</b></a></li> 2863 <li class="indline1"><tt>relativeURI</tt> <a class="iref" href="#rfc.iref.g.22"><b>3.2.1</b></a></li> 2864 <li class="indline1"><tt>Request</tt> <a class="iref" href="#rfc.iref.g.62"><b>5</b></a></li> 2865 <li class="indline1"><tt>Request-Line</tt> <a class="iref" href="#rfc.iref.g.63"><b>5.1</b></a></li> 2866 <li class="indline1"><tt>Request-URI</tt> <a class="iref" href="#rfc.iref.g.66"><b>5.1.2</b></a></li> 2867 <li class="indline1"><tt>Response</tt> <a class="iref" href="#rfc.iref.g.67"><b>6</b></a></li> 2868 <li class="indline1"><tt>rfc1123-date</tt> <a class="iref" href="#rfc.iref.g.26"><b>3.3.1</b></a></li> 2869 <li class="indline1"><tt>rfc850-date</tt> <a class="iref" href="#rfc.iref.g.28"><b>3.3.1</b></a></li> 2870 <li class="indline1"><tt>RWS</tt> <a class="iref" href="#rfc.iref.g.3"><b>2.2</b></a></li> 2871 <li class="indline1"><tt>separators</tt> <a class="iref" href="#rfc.iref.g.8"><b>2.2</b></a></li> 2872 <li class="indline1"><tt>start-line</tt> <a class="iref" href="#rfc.iref.g.55"><b>4.1</b></a></li> 2873 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.69"><b>6.1.1</b></a></li> 2874 <li class="indline1"><tt>Status-Line</tt> <a class="iref" href="#rfc.iref.g.68"><b>6.1</b></a></li> 2875 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g.83"><b>8.5</b></a></li> 2876 <li class="indline1"><tt>tchar</tt> <a class="iref" href="#rfc.iref.g.7"><b>2.2</b></a></li> 2877 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.81"><b>8.5</b></a></li> 2878 <li class="indline1"><tt>TE-v</tt> <a class="iref" href="#rfc.iref.g.82"><b>8.5</b></a></li> 2879 <li class="indline1"><tt>TEXT</tt> <a class="iref" href="#rfc.iref.g.5"><b>2.2</b></a></li> 2880 <li class="indline1"><tt>time</tt> <a class="iref" href="#rfc.iref.g.33"><b>3.3.1</b></a></li> 2881 <li class="indline1"><tt>token</tt> <a class="iref" href="#rfc.iref.g.6"><b>2.2</b></a></li> 2882 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g.84"><b>8.6</b></a></li> 2883 <li class="indline1"><tt>trailer-part</tt> <a class="iref" href="#rfc.iref.g.50"><b>3.4.1</b></a></li> 2884 <li class="indline1"><tt>Trailer-v</tt> <a class="iref" href="#rfc.iref.g.85"><b>8.6</b></a></li> 2885 <li class="indline1"><tt>transfer-coding</tt> <a class="iref" href="#rfc.iref.g.37"><b>3.4</b></a></li> 2886 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g.86"><b>8.7</b></a></li> 2887 <li class="indline1"><tt>Transfer-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.87"><b>8.7</b></a></li> 2888 <li class="indline1"><tt>transfer-extension</tt> <a class="iref" href="#rfc.iref.g.38"><b>3.4</b></a></li> 2889 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g.88"><b>8.8</b></a></li> 2890 <li class="indline1"><tt>Upgrade-v</tt> <a class="iref" href="#rfc.iref.g.89"><b>8.8</b></a></li> 2891 <li class="indline1"><tt>uri-host</tt> <a class="iref" href="#rfc.iref.g.23"><b>3.2.1</b></a></li> 2892 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.41"><b>3.4</b></a></li> 2893 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.90"><b>8.9</b></a></li> 2894 <li class="indline1"><tt>Via-v</tt> <a class="iref" href="#rfc.iref.g.91"><b>8.9</b></a></li> 2895 <li class="indline1"><tt>weekday</tt> <a class="iref" href="#rfc.iref.g.35"><b>3.3.1</b></a></li> 2896 <li class="indline1"><tt>wkday</tt> <a class="iref" href="#rfc.iref.g.34"><b>3.3.1</b></a></li> 2796 <li class="indline1"><tt>absoluteURI</tt> <a class="iref" href="#rfc.iref.g.16"><b>3.2.1</b></a></li> 2797 <li class="indline1"><tt>asctime-date</tt> <a class="iref" href="#rfc.iref.g.28"><b>3.3.1</b></a></li> 2798 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.39"><b>3.4</b></a></li> 2799 <li class="indline1"><tt>authority</tt> <a class="iref" href="#rfc.iref.g.17"><b>3.2.1</b></a></li> 2800 <li class="indline1"><tt>BWS</tt> <a class="iref" href="#rfc.iref.g.3"><b>2.2</b></a></li> 2801 <li class="indline1"><tt>chunk</tt> <a class="iref" href="#rfc.iref.g.42"><b>3.4.1</b></a></li> 2802 <li class="indline1"><tt>chunk-data</tt> <a class="iref" href="#rfc.iref.g.48"><b>3.4.1</b></a></li> 2803 <li class="indline1"><tt>chunk-ext</tt> <a class="iref" href="#rfc.iref.g.45"><b>3.4.1</b></a></li> 2804 <li class="indline1"><tt>chunk-ext-name</tt> <a class="iref" href="#rfc.iref.g.46"><b>3.4.1</b></a></li> 2805 <li class="indline1"><tt>chunk-ext-val</tt> <a class="iref" href="#rfc.iref.g.47"><b>3.4.1</b></a></li> 2806 <li class="indline1"><tt>chunk-size</tt> <a class="iref" href="#rfc.iref.g.43"><b>3.4.1</b></a></li> 2807 <li class="indline1"><tt>Chunked-Body</tt> <a class="iref" href="#rfc.iref.g.41"><b>3.4.1</b></a></li> 2808 <li class="indline1"><tt>comment</tt> <a class="iref" href="#rfc.iref.g.8"><b>2.2</b></a></li> 2809 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g.71"><b>8.1</b></a></li> 2810 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g.73"><b>8.1</b></a></li> 2811 <li class="indline1"><tt>Connection-v</tt> <a class="iref" href="#rfc.iref.g.72"><b>8.1</b></a></li> 2812 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g.74"><b>8.2</b></a></li> 2813 <li class="indline1"><tt>Content-Length-v</tt> <a class="iref" href="#rfc.iref.g.75"><b>8.2</b></a></li> 2814 <li class="indline1"><tt>ctext</tt> <a class="iref" href="#rfc.iref.g.9"><b>2.2</b></a></li> 2815 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.76"><b>8.3</b></a></li> 2816 <li class="indline1"><tt>Date-v</tt> <a class="iref" href="#rfc.iref.g.77"><b>8.3</b></a></li> 2817 <li class="indline1"><tt>date1</tt> <a class="iref" href="#rfc.iref.g.29"><b>3.3.1</b></a></li> 2818 <li class="indline1"><tt>date2</tt> <a class="iref" href="#rfc.iref.g.30"><b>3.3.1</b></a></li> 2819 <li class="indline1"><tt>date3</tt> <a class="iref" href="#rfc.iref.g.31"><b>3.3.1</b></a></li> 2820 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.69"><b>6.1.1</b></a></li> 2821 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.64"><b>5.1.1</b></a></li> 2822 <li class="indline1"><tt>field-content</tt> <a class="iref" href="#rfc.iref.g.58"><b>4.2</b></a></li> 2823 <li class="indline1"><tt>field-name</tt> <a class="iref" href="#rfc.iref.g.56"><b>4.2</b></a></li> 2824 <li class="indline1"><tt>field-value</tt> <a class="iref" href="#rfc.iref.g.57"><b>4.2</b></a></li> 2825 <li class="indline1"><tt>general-header</tt> <a class="iref" href="#rfc.iref.g.60"><b>4.5</b></a></li> 2826 <li class="indline1"><tt>generic-message</tt> <a class="iref" href="#rfc.iref.g.53"><b>4.1</b></a></li> 2827 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.78"><b>8.4</b></a></li> 2828 <li class="indline1"><tt>Host-v</tt> <a class="iref" href="#rfc.iref.g.79"><b>8.4</b></a></li> 2829 <li class="indline1"><tt>HTTP-date</tt> <a class="iref" href="#rfc.iref.g.24"><b>3.3.1</b></a></li> 2830 <li class="indline1"><tt>HTTP-message</tt> <a class="iref" href="#rfc.iref.g.52"><b>4.1</b></a></li> 2831 <li class="indline1"><tt>HTTP-Prot-Name</tt> <a class="iref" href="#rfc.iref.g.15"><b>3.1</b></a></li> 2832 <li class="indline1"><tt>http-URL</tt> <a class="iref" href="#rfc.iref.g.23"><b>3.2.2</b></a></li> 2833 <li class="indline1"><tt>HTTP-Version</tt> <a class="iref" href="#rfc.iref.g.14"><b>3.1</b></a></li> 2834 <li class="indline1"><tt>last-chunk</tt> <a class="iref" href="#rfc.iref.g.44"><b>3.4.1</b></a></li> 2835 <li class="indline1"><tt>message-body</tt> <a class="iref" href="#rfc.iref.g.59"><b>4.3</b></a></li> 2836 <li class="indline1"><tt>message-header</tt> <a class="iref" href="#rfc.iref.g.55"><b>4.2</b></a></li> 2837 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.63"><b>5.1.1</b></a></li> 2838 <li class="indline1"><tt>month</tt> <a class="iref" href="#rfc.iref.g.35"><b>3.3.1</b></a></li> 2839 <li class="indline1"><tt>obsolete-date</tt> <a class="iref" href="#rfc.iref.g.26"><b>3.3.1</b></a></li> 2840 <li class="indline1"><tt>OWS</tt> <a class="iref" href="#rfc.iref.g.1"><b>2.2</b></a></li> 2841 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.38"><b>3.4</b></a></li> 2842 <li class="indline1"><tt>path-absolute</tt> <a class="iref" href="#rfc.iref.g.18"><b>3.2.1</b></a></li> 2843 <li class="indline1"><tt>port</tt> <a class="iref" href="#rfc.iref.g.19"><b>3.2.1</b></a></li> 2844 <li class="indline1"><tt>product</tt> <a class="iref" href="#rfc.iref.g.50"><b>3.5</b></a></li> 2845 <li class="indline1"><tt>product-version</tt> <a class="iref" href="#rfc.iref.g.51"><b>3.5</b></a></li> 2846 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.92"><b>8.9</b></a></li> 2847 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.93"><b>8.9</b></a></li> 2848 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.95"><b>8.9</b></a></li> 2849 <li class="indline1"><tt>qdtext</tt> <a class="iref" href="#rfc.iref.g.11"><b>2.2</b></a></li> 2850 <li class="indline1"><tt>query</tt> <a class="iref" href="#rfc.iref.g.20"><b>3.2.1</b></a></li> 2851 <li class="indline1"><tt>quoted-pair</tt> <a class="iref" href="#rfc.iref.g.13"><b>2.2</b></a></li> 2852 <li class="indline1"><tt>quoted-string</tt> <a class="iref" href="#rfc.iref.g.10"><b>2.2</b></a></li> 2853 <li class="indline1"><tt>quoted-text</tt> <a class="iref" href="#rfc.iref.g.12"><b>2.2</b></a></li> 2854 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.70"><b>6.1.1</b></a></li> 2855 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.94"><b>8.9</b></a></li> 2856 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.91"><b>8.9</b></a></li> 2857 <li class="indline1"><tt>relativeURI</tt> <a class="iref" href="#rfc.iref.g.21"><b>3.2.1</b></a></li> 2858 <li class="indline1"><tt>Request</tt> <a class="iref" href="#rfc.iref.g.61"><b>5</b></a></li> 2859 <li class="indline1"><tt>Request-Line</tt> <a class="iref" href="#rfc.iref.g.62"><b>5.1</b></a></li> 2860 <li class="indline1"><tt>Request-URI</tt> <a class="iref" href="#rfc.iref.g.65"><b>5.1.2</b></a></li> 2861 <li class="indline1"><tt>Response</tt> <a class="iref" href="#rfc.iref.g.66"><b>6</b></a></li> 2862 <li class="indline1"><tt>rfc1123-date</tt> <a class="iref" href="#rfc.iref.g.25"><b>3.3.1</b></a></li> 2863 <li class="indline1"><tt>rfc850-date</tt> <a class="iref" href="#rfc.iref.g.27"><b>3.3.1</b></a></li> 2864 <li class="indline1"><tt>RWS</tt> <a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li> 2865 <li class="indline1"><tt>separators</tt> <a class="iref" href="#rfc.iref.g.7"><b>2.2</b></a></li> 2866 <li class="indline1"><tt>start-line</tt> <a class="iref" href="#rfc.iref.g.54"><b>4.1</b></a></li> 2867 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.68"><b>6.1.1</b></a></li> 2868 <li class="indline1"><tt>Status-Line</tt> <a class="iref" href="#rfc.iref.g.67"><b>6.1</b></a></li> 2869 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g.82"><b>8.5</b></a></li> 2870 <li class="indline1"><tt>tchar</tt> <a class="iref" href="#rfc.iref.g.6"><b>2.2</b></a></li> 2871 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.80"><b>8.5</b></a></li> 2872 <li class="indline1"><tt>TE-v</tt> <a class="iref" href="#rfc.iref.g.81"><b>8.5</b></a></li> 2873 <li class="indline1"><tt>TEXT</tt> <a class="iref" href="#rfc.iref.g.4"><b>2.2</b></a></li> 2874 <li class="indline1"><tt>time</tt> <a class="iref" href="#rfc.iref.g.32"><b>3.3.1</b></a></li> 2875 <li class="indline1"><tt>token</tt> <a class="iref" href="#rfc.iref.g.5"><b>2.2</b></a></li> 2876 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g.83"><b>8.6</b></a></li> 2877 <li class="indline1"><tt>trailer-part</tt> <a class="iref" href="#rfc.iref.g.49"><b>3.4.1</b></a></li> 2878 <li class="indline1"><tt>Trailer-v</tt> <a class="iref" href="#rfc.iref.g.84"><b>8.6</b></a></li> 2879 <li class="indline1"><tt>transfer-coding</tt> <a class="iref" href="#rfc.iref.g.36"><b>3.4</b></a></li> 2880 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g.85"><b>8.7</b></a></li> 2881 <li class="indline1"><tt>Transfer-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.86"><b>8.7</b></a></li> 2882 <li class="indline1"><tt>transfer-extension</tt> <a class="iref" href="#rfc.iref.g.37"><b>3.4</b></a></li> 2883 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g.87"><b>8.8</b></a></li> 2884 <li class="indline1"><tt>Upgrade-v</tt> <a class="iref" href="#rfc.iref.g.88"><b>8.8</b></a></li> 2885 <li class="indline1"><tt>uri-host</tt> <a class="iref" href="#rfc.iref.g.22"><b>3.2.1</b></a></li> 2886 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.40"><b>3.4</b></a></li> 2887 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.89"><b>8.9</b></a></li> 2888 <li class="indline1"><tt>Via-v</tt> <a class="iref" href="#rfc.iref.g.90"><b>8.9</b></a></li> 2889 <li class="indline1"><tt>weekday</tt> <a class="iref" href="#rfc.iref.g.34"><b>3.3.1</b></a></li> 2890 <li class="indline1"><tt>wkday</tt> <a class="iref" href="#rfc.iref.g.33"><b>3.3.1</b></a></li> 2897 2891 </ul> 2898 2892 </li> … … 2919 2913 </li> 2920 2914 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 2921 <li class="indline1">implied *LWS <a class="iref" href="#rfc.iref.i.1"><b>2.1.2</b></a></li> 2922 <li class="indline1">inbound <a class="iref" href="#rfc.iref.i.2">D</a></li> 2915 <li class="indline1">inbound <a class="iref" href="#rfc.iref.i.1">D</a></li> 2923 2916 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">2.2</a>, <a class="iref" href="#ISO-8859-1"><b>12.1</b></a></li> 2924 2917 </ul> -
draft-ietf-httpbis/latest/p1-messaging.xml
r368 r369 488 488 <t> 489 489 Historically, HTTP/1.1 header field values allow linear white space folding across 490 multiple lines. However, this specification deprecates its use; senders MUST NOT490 multiple lines. However, this specification deprecates its use; senders &MUST-NOT; 491 491 produce messages that include LWS folding (i.e., use the obs-fold rule), except 492 within the message/http media type <xref target="internet.media.type.message.http"/>. 493 Receivers SHOULD still parse folded linear white space. 494 </t> 495 <t> 496 This specification uses three rules to denote the use of linear white space; 497 BWS ("Bad" White Space), OWS (Optional White Space), and RWS (Required White Space). 498 </t> 499 <t> 500 "Bad" white space is allowed by the BNF, but senders SHOULD NOT produce it in messages. 501 Receivers MUST accept it in incoming messages. 502 </t> 503 492 within the message/http media type (<xref target="internet.media.type.message.http"/>). 493 Receivers &SHOULD; still parse folded linear white space. 494 </t> 495 <t> 496 This specification uses three rules to denote the use of linear white space; 497 BWS ("Bad" White Space), OWS (Optional White Space), and RWS (Required White Space). 498 </t> 499 <t> 500 "Bad" white space is allowed by the BNF, but senders &SHOULD-NOT; produce it in messages. 501 Receivers &MUST; accept it in incoming messages. 502 </t> 503 <t> 504 Required white space is used when at least one linear white space character 505 is required to separate field tokens. In all such cases, a single SP character 506 &SHOULD; be used. 507 </t> 504 508 <t anchor="rule.whitespace"> 505 509 <x:anchor-alias value="BWS"/> … … 507 511 <x:anchor-alias value="RWS"/> 508 512 <x:anchor-alias value="obs-fold"/> 509 510 513 </t> 511 514 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OWS"/><iref primary="true" item="Grammar" subitem="RWS"/><iref primary="true" item="Grammar" subitem="BWS"/> … … 517 520 ; "bad" white space 518 521 <x:ref>obs-fold</x:ref> = <x:ref>CRLF</x:ref> 519 ; <cref>to be explained: do not produce</cref>520 522 </artwork></figure> 521 523 <t anchor="rule.TEXT"> … … 528 530 </t> 529 531 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TEXT"/> 530 <x:ref>TEXT</x:ref> = %x20-7E / %x80-FF / <x:ref> LWS</x:ref>531 ; any <x:ref>OCTET</x:ref> except <x:ref>CTL</x:ref>s, but including <x:ref> LWS</x:ref>532 <x:ref>TEXT</x:ref> = %x20-7E / %x80-FF / <x:ref>OWS</x:ref> 533 ; any <x:ref>OCTET</x:ref> except <x:ref>CTL</x:ref>s, but including <x:ref>OWS</x:ref> 532 534 </artwork></figure> 533 535 <t> … … 1196 1198 <x:ref>message-header</x:ref> = <x:ref>field-name</x:ref> ":" [ <x:ref>field-value</x:ref> ] 1197 1199 <x:ref>field-name</x:ref> = <x:ref>token</x:ref> 1198 <x:ref>field-value</x:ref> = *( <x:ref>field-content</x:ref> / <x:ref> LWS</x:ref> )1200 <x:ref>field-value</x:ref> = *( <x:ref>field-content</x:ref> / <x:ref>OWS</x:ref> ) 1199 1201 <x:ref>field-content</x:ref> = <field content> 1200 1202 ; the <x:ref>OCTET</x:ref>s making up the field-value
Note: See TracChangeset
for help on using the changeset viewer.