![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 357 for draft-ietf-httpbis
- Timestamp:
- 13/11/08 01:33:44 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 6 edited
-
p1-messaging.html (modified) (1 diff)
-
p1-messaging.xml (modified) (1 diff)
-
p2-semantics.html (modified) (1 diff)
-
p2-semantics.xml (modified) (1 diff)
-
p3-payload.html (modified) (31 diffs)
-
p3-payload.xml (modified) (34 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r354 r357 2741 2741 <li>Get rid of RFC822 dependency; use RFC5234 plus extensions instead.</li> 2742 2742 <li>Only reference RFC 5234's core rules.</li> 2743 <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS"), but do 2744 not use them yet. 2745 </li> 2746 <li>Rewrite header ABNFs to spell out whitespace rules, factor out value format definitions.</li> 2743 <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li> 2744 <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li> 2747 2745 </ul> 2748 2746 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> -
draft-ietf-httpbis/latest/p1-messaging.xml
r354 r357 4663 4663 <t> 4664 4664 Introduce new ABNF rules for "bad" whitespace ("BWS"), optional 4665 whitespace ("OWS") and required whitespace ("RWS"), but do not use 4666 them yet. 4667 </t> 4668 <t> 4669 Rewrite header ABNFs to spell out whitespace rules, factor out 4670 value format definitions. 4665 whitespace ("OWS") and required whitespace ("RWS"). 4666 </t> 4667 <t> 4668 Rewrite ABNFs to spell out whitespace rules, factor out 4669 header value format definitions. 4671 4670 </t> 4672 4671 </list> -
draft-ietf-httpbis/latest/p2-semantics.html
r356 r357 2332 2332 <ul> 2333 2333 <li>Use "/" instead of "|" for alternatives.</li> 2334 <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS"), but do 2335 not use them yet. 2336 </li> 2337 <li>Rewrite header ABNFs to spell out whitespace rules, factor out value format definitions.</li> 2334 <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li> 2335 <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li> 2338 2336 </ul> 2339 2337 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> -
draft-ietf-httpbis/latest/p2-semantics.xml
r356 r357 3350 3350 <t> 3351 3351 Introduce new ABNF rules for "bad" whitespace ("BWS"), optional 3352 whitespace ("OWS") and required whitespace ("RWS"), but do not use 3353 them yet. 3354 </t> 3355 <t> 3356 Rewrite header ABNFs to spell out whitespace rules, factor out 3357 value format definitions. 3352 whitespace ("OWS") and required whitespace ("RWS"). 3353 </t> 3354 <t> 3355 Rewrite ABNFs to spell out whitespace rules, factor out 3356 header value format definitions. 3358 3357 </t> 3359 3358 </list> -
draft-ietf-httpbis/latest/p3-payload.html
r345 r357 484 484 <tr> 485 485 <td class="header left"></td> 486 <td class="header right">November 1 1, 2008</td>486 <td class="header right">November 13, 2008</td> 487 487 </tr> 488 488 </table> … … 631 631 </p> 632 632 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1> 633 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="A ugmented BNF">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.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>633 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="ABNF Extensions">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.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> 634 634 </p> 635 635 <div id="rfc.figure.u.1"></div><pre class="inline"> <a href="#notation" class="smpl">ALPHA</a> = <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>> … … 638 638 </pre><div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#notation" class="smpl">quoted-string</a> = <quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 639 639 <a href="#notation" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 640 <a href="#notation" class="smpl">BWS</a> = <BWS, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 641 <a href="#notation" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 642 <a href="#notation" class="smpl">RWS</a> = <RWS, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> 640 643 </pre><div id="abnf.dependencies"> 641 644 <p id="rfc.section.2.p.4"> The ABNF rules below are defined in other parts:</p> 642 645 </div> 643 <div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absoluteURI</a> = <absoluteURI, defined in <a href="#Part1" id="rfc.xref.Part1. 8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>>644 <a href="#abnf.dependencies" class="smpl">Content-Length</a> = <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>>645 <a href="#abnf.dependencies" class="smpl">relativeURI</a> = <relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.1 0"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>>646 <a href="#abnf.dependencies" class="smpl">message-header</a> = <message-header, defined in <a href="#Part1" id="rfc.xref.Part1.1 1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>>646 <div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absoluteURI</a> = <absoluteURI, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>> 647 <a href="#abnf.dependencies" class="smpl">Content-Length</a> = <Content-Length, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 8.2</a>> 648 <a href="#abnf.dependencies" class="smpl">relativeURI</a> = <relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>> 649 <a href="#abnf.dependencies" class="smpl">message-header</a> = <message-header, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>> 647 650 </pre><div id="rfc.figure.u.4"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Last-Modified</a> = <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>> 648 651 </pre><div id="rfc.figure.u.5"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Content-Range</a> = <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>> … … 736 739 <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. 737 740 </p> 738 <div id="rfc.figure.u.9"></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> <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( ";"<a href="#rule.parameter" class="smpl">parameter</a> )739 <a href="#media.types" class="smpl">type</a> 740 <a href="#media.types" class="smpl">subtype</a> 741 <div id="rfc.figure.u.9"></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> <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#notation" class="smpl">OWS</a> ";" <a href="#notation" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> ) 742 <a href="#media.types" class="smpl">type</a> = <a href="#notation" class="smpl">token</a> 743 <a href="#media.types" class="smpl">subtype</a> = <a href="#notation" class="smpl">token</a> 741 744 </pre><div id="rule.parameter"> 742 745 <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. … … 833 836 <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> <a href="#entity.header.fields" class="smpl">entity-header</a> = <a href="#header.content-encoding" class="smpl">Content-Encoding</a> ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section 6.5</a> 834 837 / <a href="#header.content-language" class="smpl">Content-Language</a> ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section 6.6</a> 835 / <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <a href="#Part1" id="rfc.xref.Part1.1 2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 8.2</a>838 / <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 8.2</a> 836 839 / <a href="#header.content-location" class="smpl">Content-Location</a> ; <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section 6.7</a> 837 840 / <a href="#header.content-md5" class="smpl">Content-MD5</a> ; <a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section 6.8</a> … … 849 852 <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> 850 853 <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span> <a href="#entity.body" class="smpl">entity-body</a> = *<a href="#notation" class="smpl">OCTET</a> 851 </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.1 3"><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 ensure854 </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.16"><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 852 855 safe and proper transfer of the message. 853 856 </p> … … 866 869 </p> 867 870 <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> 868 <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 4"><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.871 <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.17"><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. 869 872 </p> 870 873 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1> … … 956 959 <div id="rfc.iref.h.1"></div> 957 960 <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="header.accept" href="#header.accept">Accept</a></h2> 958 <p id="rfc.section.6.1.p.1">The Accept request-header field can be used to specify certain media types which are acceptable for the response. Accept headers959 can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of a request960 for an in-line image.961 </p> 962 <div id="rfc.figure.u.17"></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> <a href="#header.accept" class="smpl">Accept</a> = "Accept" ":"963 961 <p id="rfc.section.6.1.p.1">The request-header field "Accept" can be used to specify certain media types which are acceptable for the response. Accept 962 headers can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of 963 a request for an in-line image. 964 </p> 965 <div id="rfc.figure.u.17"></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> <a href="#header.accept" class="smpl">Accept</a> = "Accept" BWS ":" OWS <a href="#header.accept" class="smpl">Accept-v</a> 966 <a href="#header.accept" class="smpl">Accept-v</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] ) 964 967 965 968 <a href="#header.accept" class="smpl">media-range</a> = ( "*/*" … … 984 987 </dl> 985 988 <p id="rfc.section.6.1.p.5">The example</p> 986 <div id="rfc.figure.u.18"></div><pre class="text"> 989 <div id="rfc.figure.u.18"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic 987 990 </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 988 991 quality." … … 993 996 </p> 994 997 <p id="rfc.section.6.1.p.9">A more elaborate example is</p> 995 <div id="rfc.figure.u.19"></div><pre class="text"> 996 998 <div id="rfc.figure.u.19"></div><pre class="text"> Accept: text/plain; q=0.5, text/html, 999 text/x-dvi; q=0.8, text/x-c 997 1000 </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 998 1001 send the text/x-dvi entity, and if that does not exist, send the text/plain entity." … … 1001 1004 to a given type, the most specific reference has precedence. For example, 1002 1005 </p> 1003 <div id="rfc.figure.u.20"></div><pre class="text"> 1006 <div id="rfc.figure.u.20"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */* 1004 1007 </pre><p id="rfc.section.6.1.p.14">have the following precedence:</p> 1005 1008 <div id="rfc.figure.u.21"></div><pre class="text"> 1) text/html;level=1 … … 1010 1013 which matches that type. For example, 1011 1014 </p> 1012 <div id="rfc.figure.u.22"></div><pre class="text"> 1013 1015 <div id="rfc.figure.u.22"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, 1016 text/html;level=2;q=0.4, */*;q=0.5 1014 1017 </pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p> 1015 1018 <div id="rfc.figure.u.23"></div><pre class="text"> text/html;level=1 = 1 … … 1025 1028 <div id="rfc.iref.h.2"></div> 1026 1029 <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h2> 1027 <p id="rfc.section.6.2.p.1">The Accept-Charset request-header fieldcan be used to indicate what character sets are acceptable for the response. This1030 <p id="rfc.section.6.2.p.1">The request-header field "Accept-Charset" can be used to indicate what character sets are acceptable for the response. This 1028 1031 field allows clients capable of understanding more comprehensive or special-purpose character sets to signal that capability 1029 1032 to a server which is capable of representing documents in those character sets. 1030 1033 </p> 1031 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.21"></span> <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset" ":" 1032 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" ) [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] ) 1034 <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset" BWS ":" OWS 1035 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> 1036 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" ) [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] ) 1033 1037 </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 1034 1038 example is 1035 1039 </p> 1036 <div id="rfc.figure.u.25"></div><pre class="text"> 1040 <div id="rfc.figure.u.25"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 1037 1041 </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 1038 1042 not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets … … 1046 1050 <div id="rfc.iref.h.3"></div> 1047 1051 <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a> <a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h2> 1048 <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. 1049 </p> 1050 <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding" ":" 1052 <p id="rfc.section.6.3.p.1">The request-header field "Accept-Encoding" 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. 1053 </p> 1054 <div id="rfc.figure.u.26"></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> <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> = "Accept-Encoding" BWS ":" OWS 1055 <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> 1056 <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> = 1051 1057 #( <a href="#header.accept-encoding" class="smpl">codings</a> [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] ) 1052 <a href="#header.accept-encoding" class="smpl">codings</a> = ( <a href="#content.codings" class="smpl">content-coding</a> / "*" )1058 <a href="#header.accept-encoding" class="smpl">codings</a> = ( <a href="#content.codings" class="smpl">content-coding</a> / "*" ) 1053 1059 </pre><p id="rfc.section.6.3.p.3">Each codings value <em class="bcp14">MAY</em> be given an associated quality value which represents the preference for that encoding. The default value is q=1. 1054 1060 </p> 1055 1061 <p id="rfc.section.6.3.p.4">Examples of its use are:</p> 1056 <div id="rfc.figure.u.27"></div><pre class="text"> 1057 1058 1059 1060 1062 <div id="rfc.figure.u.27"></div><pre class="text"> Accept-Encoding: compress, gzip 1063 Accept-Encoding: 1064 Accept-Encoding: * 1065 Accept-Encoding: compress;q=0.5, gzip;q=1.0 1066 Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0 1061 1067 </pre><p id="rfc.section.6.3.p.6">A server tests whether a content-coding is acceptable, according to an Accept-Encoding field, using these rules: </p> 1062 1068 <ol> … … 1093 1099 <div id="rfc.iref.h.4"></div> 1094 1100 <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a> <a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h2> 1095 <p id="rfc.section.6.4.p.1">The Accept-Language request-header fieldis similar to Accept, but restricts the set of natural languages that are preferred1101 <p id="rfc.section.6.4.p.1">The request-header field "Accept-Language" is similar to Accept, but restricts the set of natural languages that are preferred 1096 1102 as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 3.5</a>. 1097 1103 </p> 1098 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> <a href="#header.accept-language" class="smpl">Accept-Language</a> = "Accept-Language" ":" 1104 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span> <a href="#header.accept-language" class="smpl">Accept-Language</a> = "Accept-Language" BWS ":" OWS 1105 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> 1106 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> = 1099 1107 1#( <a href="#header.accept-language" class="smpl">language-range</a> [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] ) 1100 <a href="#header.accept-language" class="smpl">language-range</a> =1108 <a href="#header.accept-language" class="smpl">language-range</a> = 1101 1109 <language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>> 1102 1110 </pre><p id="rfc.section.6.4.p.3">Each language-range can be given an associated quality value which represents an estimate of the user's preference for the 1103 1111 languages specified by that range. The quality value defaults to "q=1". For example, 1104 1112 </p> 1105 <div id="rfc.figure.u.29"></div><pre class="text"> 1113 <div id="rfc.figure.u.29"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.7 1106 1114 </pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English."</p> 1107 1115 <p id="rfc.section.6.4.p.6">For matching, the "Basic Filtering" matching scheme, defined in <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, is used: … … 1142 1150 <div id="rfc.iref.h.5"></div> 1143 1151 <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a> <a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2> 1144 <p id="rfc.section.6.5.p.1">The Content-Encoding entity-header field is used as a modifier to the media-type. When present, its value indicates what additional 1145 content codings have been applied to the entity-body, and thus what decoding mechanisms must be applied in order to obtain 1146 the media-type referenced by the Content-Type header field. Content-Encoding is primarily used to allow a document to be compressed 1147 without losing the identity of its underlying media type. 1148 </p> 1149 <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.26"></span> <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = "Content-Encoding" ":" 1#<a href="#content.codings" class="smpl">content-coding</a> 1152 <p id="rfc.section.6.5.p.1">The entity-header field "Content-Encoding" is used as a modifier to the media-type. When present, its value indicates what 1153 additional content codings have been applied to the entity-body, and thus what decoding mechanisms must be applied in order 1154 to obtain the media-type referenced by the Content-Type header field. Content-Encoding is primarily used to allow a document 1155 to be compressed without losing the identity of its underlying media type. 1156 </p> 1157 <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span> <a href="#header.content-encoding" class="smpl">Content-Encoding</a> = "Content-Encoding" BWS ":" OWS <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> 1158 <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = 1#<a href="#content.codings" class="smpl">content-coding</a> 1150 1159 </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 1151 1160 </p> 1152 <div id="rfc.figure.u.31"></div><pre class="text"> 1161 <div id="rfc.figure.u.31"></div><pre class="text"> Content-Encoding: gzip 1153 1162 </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 1154 1163 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 … … 1164 1173 <div id="rfc.iref.h.6"></div> 1165 1174 <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a> <a id="header.content-language" href="#header.content-language">Content-Language</a></h2> 1166 <p id="rfc.section.6.6.p.1">The Content-Language entity-header fielddescribes the natural language(s) of the intended audience for the enclosed entity.1175 <p id="rfc.section.6.6.p.1">The entity-header field "Content-Language" describes the natural language(s) of the intended audience for the enclosed entity. 1167 1176 Note that this might not be equivalent to all the languages used within the entity-body. 1168 1177 </p> 1169 <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.27"></span> <a href="#header.content-language" class="smpl">Content-Language</a> = "Content-Language" ":" 1#<a href="#language.tags" class="smpl">language-tag</a> 1178 <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span> <a href="#header.content-language" class="smpl">Content-Language</a> = "Content-Language" BWS ":" OWS <a href="#header.content-language" class="smpl">Content-Language-v</a> 1179 <a href="#header.content-language" class="smpl">Content-Language-v</a> = 1#<a href="#language.tags" class="smpl">language-tag</a> 1170 1180 </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 1171 1181 own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is 1172 1182 </p> 1173 <div id="rfc.figure.u.33"></div><pre class="text"> 1183 <div id="rfc.figure.u.33"></div><pre class="text"> Content-Language: da 1174 1184 </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 1175 1185 that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language … … 1179 1189 simultaneously in the original Maori and English versions, would call for 1180 1190 </p> 1181 <div id="rfc.figure.u.34"></div><pre class="text"> 1191 <div id="rfc.figure.u.34"></div><pre class="text"> Content-Language: mi, en 1182 1192 </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 1183 1193 audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended … … 1189 1199 <div id="rfc.iref.h.7"></div> 1190 1200 <h2 id="rfc.section.6.7"><a href="#rfc.section.6.7">6.7</a> <a id="header.content-location" href="#header.content-location">Content-Location</a></h2> 1191 <p id="rfc.section.6.7.p.1">The Content-Location entity-header field<em class="bcp14">MAY</em> be used to supply the resource location for the entity enclosed in the message when that entity is accessible from a location1201 <p id="rfc.section.6.7.p.1">The entity-header field "Content-Location" <em class="bcp14">MAY</em> be used to supply the resource location for the entity enclosed in the message when that entity is accessible from a location 1192 1202 separate from the requested resource's URI. A server <em class="bcp14">SHOULD</em> provide a Content-Location for the variant corresponding to the response entity; especially in the case where a resource has 1193 1203 multiple entities associated with it, and those entities actually have separate locations by which they might be individually 1194 1204 accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned. 1195 1205 </p> 1196 <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.28"></span> <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location" ":" 1197 ( <a href="#abnf.dependencies" class="smpl">absoluteURI</a> / <a href="#abnf.dependencies" class="smpl">relativeURI</a> ) 1206 <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span> <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location" BWS ":" OWS 1207 <a href="#header.content-location" class="smpl">Content-Location-v</a> 1208 <a href="#header.content-location" class="smpl">Content-Location-v</a> = 1209 <a href="#abnf.dependencies" class="smpl">absoluteURI</a> / <a href="#abnf.dependencies" class="smpl">relativeURI</a> 1198 1210 </pre><p id="rfc.section.6.7.p.3">The value of Content-Location also defines the base URI for the entity.</p> 1199 1211 <p id="rfc.section.6.7.p.4">The Content-Location value is not a replacement for the original requested URI; it is only a statement of the location of … … 1209 1221 <div id="rfc.iref.h.8"></div> 1210 1222 <h2 id="rfc.section.6.8"><a href="#rfc.section.6.8">6.8</a> <a id="header.content-md5" href="#header.content-md5">Content-MD5</a></h2> 1211 <p id="rfc.section.6.8.p.1">The Content-MD5 entity-header field, as defined in <a href="#RFC1864" id="rfc.xref.RFC1864.1"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>, is an MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) of the entity-body.1223 <p id="rfc.section.6.8.p.1">The entity-header field "Content-MD5", as defined in <a href="#RFC1864" id="rfc.xref.RFC1864.1"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>, is an MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) of the entity-body. 1212 1224 (Note: a MIC is good for detecting accidental modification of the entity-body in transit, but is not proof against malicious 1213 1225 attacks.) 1214 1226 </p> 1215 <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g. 29"></span><span id="rfc.iref.g.30"></span> <a href="#header.content-md5" class="smpl">Content-MD5</a> = "Content-MD5" ":" <a href="#header.content-md5" class="smpl">md5-digest</a>1216 <a href="#header.content-md5" class="smpl"> md5-digest</a>= <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>>1227 <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span> <a href="#header.content-md5" class="smpl">Content-MD5</a> = "Content-MD5" BWS ":" OWS <a href="#header.content-md5" class="smpl">Content-MD5-v</a> 1228 <a href="#header.content-md5" class="smpl">Content-MD5-v</a> = <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>> 1217 1229 </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 1218 1230 gateways and proxies, <em class="bcp14">MAY</em> check that the digest value in this header field matches that of the entity-body as received. … … 1247 1259 <div id="rfc.iref.h.9"></div> 1248 1260 <h2 id="rfc.section.6.9"><a href="#rfc.section.6.9">6.9</a> <a id="header.content-type" href="#header.content-type">Content-Type</a></h2> 1249 <p id="rfc.section.6.9.p.1">The Content-Type entity-header fieldindicates the media type of the entity-body sent to the recipient or, in the case of1261 <p id="rfc.section.6.9.p.1">The entity-header field "Content-Type" indicates the media type of the entity-body sent to the recipient or, in the case of 1250 1262 the HEAD method, the media type that would have been sent had the request been a GET. 1251 1263 </p> 1252 <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.31"></span> <a href="#header.content-type" class="smpl">Content-Type</a> = "Content-Type" ":" <a href="#media.types" class="smpl">media-type</a> 1264 <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span> <a href="#header.content-type" class="smpl">Content-Type</a> = "Content-Type" BWS ":" OWS <a href="#header.content-type" class="smpl">Content-Type-v</a> 1265 <a href="#header.content-type" class="smpl">Content-Type-v</a> = <a href="#media.types" class="smpl">media-type</a> 1253 1266 </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 1254 1267 </p> 1255 <div id="rfc.figure.u.38"></div><pre class="text"> 1268 <div id="rfc.figure.u.38"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-4 1256 1269 </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>. 1257 1270 </p> … … 1575 1588 environments. 1576 1589 </p> 1577 <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.32"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = "MIME-Version" ":" 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a> 1590 <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span> <a href="#mime-version" class="smpl">MIME-Version</a> = "MIME-Version" BWS ":" OWS <a href="#mime-version" class="smpl">MIME-Version-v</a> 1591 <a href="#mime-version" class="smpl">MIME-Version-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a> 1578 1592 </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 1579 1593 document and not the MIME specification. … … 1607 1621 </p> 1608 1622 <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> 1609 <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 5"><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.1623 <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.18"><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. 1610 1624 </p> 1611 1625 <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> … … 1629 1643 in <a href="#RFC2183" id="rfc.xref.RFC2183.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>. 1630 1644 </p> 1631 <div id="rfc.figure.u.40"></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> <a href="#content-disposition" class="smpl">content-disposition</a> = "Content-Disposition" ":" 1632 <a href="#content-disposition" class="smpl">disposition-type</a> *( ";" <a href="#content-disposition" class="smpl">disposition-parm</a> ) 1645 <div id="rfc.figure.u.40"></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> <a href="#content-disposition" class="smpl">content-disposition</a> = "Content-Disposition" BWS ":" OWS 1646 <a href="#content-disposition" class="smpl">content-disposition-v</a> 1647 <a href="#content-disposition" class="smpl">content-disposition-v</a> = <a href="#content-disposition" class="smpl">disposition-type</a> *( ";" <a href="#content-disposition" class="smpl">disposition-parm</a> ) 1633 1648 <a href="#content-disposition" class="smpl">disposition-type</a> = "attachment" / <a href="#content-disposition" class="smpl">disp-extension-token</a> 1634 1649 <a href="#content-disposition" class="smpl">disposition-parm</a> = <a href="#content-disposition" class="smpl">filename-parm</a> / <a href="#content-disposition" class="smpl">disp-extension-parm</a> … … 1637 1652 <a href="#content-disposition" class="smpl">disp-extension-parm</a> = <a href="#notation" class="smpl">token</a> "=" ( <a href="#notation" class="smpl">token</a> / <a href="#notation" class="smpl">quoted-string</a> ) 1638 1653 </pre><p id="rfc.section.B.1.p.3">An example is</p> 1639 <div id="rfc.figure.u.41"></div><pre class="text"> 1654 <div id="rfc.figure.u.41"></div><pre class="text"> Content-Disposition: attachment; filename="fname.ext" 1640 1655 </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 1641 1656 to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only. … … 1650 1665 <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 1651 1666 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 1652 computed. (<a href="#entity.length" title="Entity Length">Section 4.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.1 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#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>).1667 computed. (<a href="#entity.length" title="Entity Length">Section 4.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#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>). 1653 1668 </p> 1654 1669 <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.3" title="Accept-Charset">Section 6.2</a>) … … 1747 1762 <ul> 1748 1763 <li>Use "/" instead of "|" for alternatives.</li> 1764 <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li> 1765 <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li> 1749 1766 </ul> 1750 1767 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> … … 1792 1809 <li class="indline1">compress <a class="iref" href="#rfc.iref.c.1">3.2</a></li> 1793 1810 <li class="indline1">Content-Base header <a class="iref" href="#rfc.iref.c.9"><b>C.1</b></a></li> 1794 <li class="indline1">Content-Disposition header <a class="iref" href="#rfc.xref.content-disposition.1">7.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">8.2</a>, <a class="iref" href="#rfc.iref.c.7"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c. 22">B.1</a></li>1811 <li class="indline1">Content-Disposition header <a class="iref" href="#rfc.xref.content-disposition.1">7.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">8.2</a>, <a class="iref" href="#rfc.iref.c.7"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c.32">B.1</a></li> 1795 1812 <li class="indline1">Content-Encoding header <a class="iref" href="#rfc.xref.header.content-encoding.1">3.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.c.2"><b>6.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">6.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">7.1</a></li> 1796 1813 <li class="indline1">Content-Language header <a class="iref" href="#rfc.xref.header.content-language.1">4.1</a>, <a class="iref" href="#rfc.iref.c.3"><b>6.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">7.1</a></li> … … 1810 1827 <ul class="ind"> 1811 1828 <li class="indline1"><tt>Accept</tt> <a class="iref" href="#rfc.iref.g.17"><b>6.1</b></a></li> 1812 <li class="indline1"><tt>Accept-Charset</tt> <a class="iref" href="#rfc.iref.g.21"><b>6.2</b></a></li> 1813 <li class="indline1"><tt>Accept-Encoding</tt> <a class="iref" href="#rfc.iref.g.22"><b>6.3</b></a></li> 1814 <li class="indline1"><tt>accept-extension</tt> <a class="iref" href="#rfc.iref.g.20"><b>6.1</b></a></li> 1815 <li class="indline1"><tt>Accept-Language</tt> <a class="iref" href="#rfc.iref.g.24"><b>6.4</b></a></li> 1816 <li class="indline1"><tt>accept-params</tt> <a class="iref" href="#rfc.iref.g.19"><b>6.1</b></a></li> 1829 <li class="indline1"><tt>Accept-Charset</tt> <a class="iref" href="#rfc.iref.g.22"><b>6.2</b></a></li> 1830 <li class="indline1"><tt>Accept-Charset-v</tt> <a class="iref" href="#rfc.iref.g.23"><b>6.2</b></a></li> 1831 <li class="indline1"><tt>Accept-Encoding</tt> <a class="iref" href="#rfc.iref.g.24"><b>6.3</b></a></li> 1832 <li class="indline1"><tt>Accept-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.25"><b>6.3</b></a></li> 1833 <li class="indline1"><tt>accept-extension</tt> <a class="iref" href="#rfc.iref.g.21"><b>6.1</b></a></li> 1834 <li class="indline1"><tt>Accept-Language</tt> <a class="iref" href="#rfc.iref.g.27"><b>6.4</b></a></li> 1835 <li class="indline1"><tt>Accept-Language-v</tt> <a class="iref" href="#rfc.iref.g.28"><b>6.4</b></a></li> 1836 <li class="indline1"><tt>accept-params</tt> <a class="iref" href="#rfc.iref.g.20"><b>6.1</b></a></li> 1837 <li class="indline1"><tt>Accept-v</tt> <a class="iref" href="#rfc.iref.g.18"><b>6.1</b></a></li> 1817 1838 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.8"><b>3.3</b></a></li> 1818 1839 <li class="indline1"><tt>charset</tt> <a class="iref" href="#rfc.iref.g.1"><b>3.1</b></a></li> 1819 <li class="indline1"><tt>codings</tt> <a class="iref" href="#rfc.iref.g.2 3"><b>6.3</b></a></li>1840 <li class="indline1"><tt>codings</tt> <a class="iref" href="#rfc.iref.g.26"><b>6.3</b></a></li> 1820 1841 <li class="indline1"><tt>content-coding</tt> <a class="iref" href="#rfc.iref.g.2"><b>3.2</b></a></li> 1821 <li class="indline1"><tt>content-disposition</tt> <a class="iref" href="#rfc.iref.g.33"><b>B.1</b></a></li> 1822 <li class="indline1"><tt>Content-Encoding</tt> <a class="iref" href="#rfc.iref.g.26"><b>6.5</b></a></li> 1823 <li class="indline1"><tt>Content-Language</tt> <a class="iref" href="#rfc.iref.g.27"><b>6.6</b></a></li> 1824 <li class="indline1"><tt>Content-Location</tt> <a class="iref" href="#rfc.iref.g.28"><b>6.7</b></a></li> 1825 <li class="indline1"><tt>Content-MD5</tt> <a class="iref" href="#rfc.iref.g.29"><b>6.8</b></a></li> 1826 <li class="indline1"><tt>Content-Type</tt> <a class="iref" href="#rfc.iref.g.31"><b>6.9</b></a></li> 1827 <li class="indline1"><tt>disp-extension-parm</tt> <a class="iref" href="#rfc.iref.g.38"><b>B.1</b></a></li> 1828 <li class="indline1"><tt>disp-extension-token</tt> <a class="iref" href="#rfc.iref.g.37"><b>B.1</b></a></li> 1829 <li class="indline1"><tt>disposition-parm</tt> <a class="iref" href="#rfc.iref.g.35"><b>B.1</b></a></li> 1830 <li class="indline1"><tt>disposition-type</tt> <a class="iref" href="#rfc.iref.g.34"><b>B.1</b></a></li> 1842 <li class="indline1"><tt>content-disposition</tt> <a class="iref" href="#rfc.iref.g.42"><b>B.1</b></a></li> 1843 <li class="indline1"><tt>content-disposition-v</tt> <a class="iref" href="#rfc.iref.g.43"><b>B.1</b></a></li> 1844 <li class="indline1"><tt>Content-Encoding</tt> <a class="iref" href="#rfc.iref.g.30"><b>6.5</b></a></li> 1845 <li class="indline1"><tt>Content-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.31"><b>6.5</b></a></li> 1846 <li class="indline1"><tt>Content-Language</tt> <a class="iref" href="#rfc.iref.g.32"><b>6.6</b></a></li> 1847 <li class="indline1"><tt>Content-Language-v</tt> <a class="iref" href="#rfc.iref.g.33"><b>6.6</b></a></li> 1848 <li class="indline1"><tt>Content-Location</tt> <a class="iref" href="#rfc.iref.g.34"><b>6.7</b></a></li> 1849 <li class="indline1"><tt>Content-Location-v</tt> <a class="iref" href="#rfc.iref.g.35"><b>6.7</b></a></li> 1850 <li class="indline1"><tt>Content-MD5</tt> <a class="iref" href="#rfc.iref.g.36"><b>6.8</b></a></li> 1851 <li class="indline1"><tt>Content-MD5-v</tt> <a class="iref" href="#rfc.iref.g.37"><b>6.8</b></a></li> 1852 <li class="indline1"><tt>Content-Type</tt> <a class="iref" href="#rfc.iref.g.38"><b>6.9</b></a></li> 1853 <li class="indline1"><tt>Content-Type-v</tt> <a class="iref" href="#rfc.iref.g.39"><b>6.9</b></a></li> 1854 <li class="indline1"><tt>disp-extension-parm</tt> <a class="iref" href="#rfc.iref.g.48"><b>B.1</b></a></li> 1855 <li class="indline1"><tt>disp-extension-token</tt> <a class="iref" href="#rfc.iref.g.47"><b>B.1</b></a></li> 1856 <li class="indline1"><tt>disposition-parm</tt> <a class="iref" href="#rfc.iref.g.45"><b>B.1</b></a></li> 1857 <li class="indline1"><tt>disposition-type</tt> <a class="iref" href="#rfc.iref.g.44"><b>B.1</b></a></li> 1831 1858 <li class="indline1"><tt>entity-body</tt> <a class="iref" href="#rfc.iref.g.16"><b>4.2</b></a></li> 1832 1859 <li class="indline1"><tt>entity-header</tt> <a class="iref" href="#rfc.iref.g.14"><b>4.1</b></a></li> 1833 1860 <li class="indline1"><tt>extension-header</tt> <a class="iref" href="#rfc.iref.g.15"><b>4.1</b></a></li> 1834 <li class="indline1"><tt>filename-parm</tt> <a class="iref" href="#rfc.iref.g. 36"><b>B.1</b></a></li>1835 <li class="indline1"><tt>language-range</tt> <a class="iref" href="#rfc.iref.g.2 5"><b>6.4</b></a></li>1861 <li class="indline1"><tt>filename-parm</tt> <a class="iref" href="#rfc.iref.g.46"><b>B.1</b></a></li> 1862 <li class="indline1"><tt>language-range</tt> <a class="iref" href="#rfc.iref.g.29"><b>6.4</b></a></li> 1836 1863 <li class="indline1"><tt>language-tag</tt> <a class="iref" href="#rfc.iref.g.11"><b>3.5</b></a></li> 1837 <li class="indline1"><tt>md5-digest</tt> <a class="iref" href="#rfc.iref.g.30"><b>6.8</b></a></li> 1838 <li class="indline1"><tt>media-range</tt> <a class="iref" href="#rfc.iref.g.18"><b>6.1</b></a></li> 1864 <li class="indline1"><tt>media-range</tt> <a class="iref" href="#rfc.iref.g.19"><b>6.1</b></a></li> 1839 1865 <li class="indline1"><tt>media-type</tt> <a class="iref" href="#rfc.iref.g.4"><b>3.3</b></a></li> 1840 <li class="indline1"><tt>MIME-Version</tt> <a class="iref" href="#rfc.iref.g.32"><b>A.1</b></a></li> 1866 <li class="indline1"><tt>MIME-Version</tt> <a class="iref" href="#rfc.iref.g.40"><b>A.1</b></a></li> 1867 <li class="indline1"><tt>MIME-Version-v</tt> <a class="iref" href="#rfc.iref.g.41"><b>A.1</b></a></li> 1841 1868 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.7"><b>3.3</b></a></li> 1842 1869 <li class="indline1"><tt>primary-tag</tt> <a class="iref" href="#rfc.iref.g.12"><b>3.5</b></a></li> … … 1860 1887 <li class="indline1">Alternate <a class="iref" href="#rfc.iref.h.12"><b>C.1</b></a></li> 1861 1888 <li class="indline1">Content-Base <a class="iref" href="#rfc.iref.h.18"><b>C.1</b></a></li> 1862 <li class="indline1">Content-Disposition <a class="iref" href="#rfc.xref.content-disposition.1">7.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">8.2</a>, <a class="iref" href="#rfc.iref.h.11"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c. 22">B.1</a></li>1889 <li class="indline1">Content-Disposition <a class="iref" href="#rfc.xref.content-disposition.1">7.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">8.2</a>, <a class="iref" href="#rfc.iref.h.11"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c.32">B.1</a></li> 1863 1890 <li class="indline1">Content-Encoding <a class="iref" href="#rfc.xref.header.content-encoding.1">3.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.h.5"><b>6.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">6.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">7.1</a></li> 1864 1891 <li class="indline1">Content-Language <a class="iref" href="#rfc.xref.header.content-language.1">4.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>6.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">7.1</a></li> … … 1890 1917 </li> 1891 1918 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 1892 <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">1919 <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">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a>, <a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.15">4.1</a>, <a class="iref" href="#rfc.xref.Part1.16">4.2</a>, <a class="iref" href="#rfc.xref.Part1.17">4.2.2</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.18">A.5</a>, <a class="iref" href="#rfc.xref.Part1.19">C.1</a><ul class="ind"> 1893 1920 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a></li> 1894 <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>1895 <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.10">2</a></li>1896 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.1 1">2</a></li>1897 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.1 3">4.2</a></li>1898 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.1 4">4.2.2</a></li>1899 <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>1900 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.1 5">A.5</a></li>1921 <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>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a></li> 1922 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a></li> 1923 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.14">2</a></li> 1924 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.16">4.2</a></li> 1925 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.17">4.2.2</a></li> 1926 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.15">4.1</a></li> 1927 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.18">A.5</a></li> 1901 1928 </ul> 1902 1929 </li> -
draft-ietf-httpbis/latest/p3-payload.xml
r345 r357 257 257 <x:anchor-alias value="quoted-string"/> 258 258 <x:anchor-alias value="token"/> 259 <x:anchor-alias value="BWS"/> 260 <x:anchor-alias value="OWS"/> 261 <x:anchor-alias value="RWS"/> 259 262 <t> 260 263 This specification uses the ABNF syntax defined in ¬ation-abnf; and … … 271 274 <x:ref>quoted-string</x:ref> = <quoted-string, defined in &basic-rules;> 272 275 <x:ref>token</x:ref> = <token, defined in &basic-rules;> 276 <x:ref>BWS</x:ref> = <BWS, defined in &basic-rules;> 277 <x:ref>OWS</x:ref> = <OWS, defined in &basic-rules;> 278 <x:ref>RWS</x:ref> = <RWS, defined in &basic-rules;> 273 279 </artwork></figure> 274 280 <t anchor="abnf.dependencies"> … … 462 468 </t> 463 469 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="media-type"/><iref primary="true" item="Grammar" subitem="type"/><iref primary="true" item="Grammar" subitem="subtype"/> 464 <x:ref>media-type</x:ref> = <x:ref>type</x:ref> "/" <x:ref>subtype</x:ref> *( ";"<x:ref>parameter</x:ref> )465 <x:ref>type</x:ref> 466 <x:ref>subtype</x:ref> 470 <x:ref>media-type</x:ref> = <x:ref>type</x:ref> "/" <x:ref>subtype</x:ref> *( <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>parameter</x:ref> ) 471 <x:ref>type</x:ref> = <x:ref>token</x:ref> 472 <x:ref>subtype</x:ref> = <x:ref>token</x:ref> 467 473 </artwork></figure> 468 474 <t anchor="rule.parameter"> … … 914 920 <iref primary="true" item="Headers" subitem="Accept" x:for-anchor=""/> 915 921 <x:anchor-alias value="Accept"/> 922 <x:anchor-alias value="Accept-v"/> 916 923 <x:anchor-alias value="accept-extension"/> 917 924 <x:anchor-alias value="accept-params"/> 918 925 <x:anchor-alias value="media-range"/> 919 926 <t> 920 The Accept request-header fieldcan be used to specify certain media927 The request-header field "Accept" can be used to specify certain media 921 928 types which are acceptable for the response. Accept headers can be 922 929 used to indicate that the request is specifically limited to a small … … 924 931 image. 925 932 </t> 926 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept"/><iref primary="true" item="Grammar" subitem=" media-range"/><iref primary="true" item="Grammar" subitem="accept-params"/><iref primary="true" item="Grammar" subitem="accept-extension"/>927 <x:ref>Accept</x:ref> = "Accept" ":"928 933 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept"/><iref primary="true" item="Grammar" subitem="Accept-v"/><iref primary="true" item="Grammar" subitem="media-range"/><iref primary="true" item="Grammar" subitem="accept-params"/><iref primary="true" item="Grammar" subitem="accept-extension"/> 934 <x:ref>Accept</x:ref> = "Accept" BWS ":" OWS <x:ref>Accept-v</x:ref> 935 <x:ref>Accept-v</x:ref> = #( <x:ref>media-range</x:ref> [ <x:ref>accept-params</x:ref> ] ) 929 936 930 937 <x:ref>media-range</x:ref> = ( "*/*" … … 964 971 </t> 965 972 <figure><artwork type="example"> 966 973 Accept: audio/*; q=0.2, audio/basic 967 974 </artwork></figure> 968 975 <t> … … 981 988 </t> 982 989 <figure><artwork type="example"> 983 984 990 Accept: text/plain; q=0.5, text/html, 991 text/x-dvi; q=0.8, text/x-c 985 992 </artwork></figure> 986 993 <t> … … 996 1003 </t> 997 1004 <figure><artwork type="example"> 998 1005 Accept: text/*, text/html, text/html;level=1, */* 999 1006 </artwork></figure> 1000 1007 <t> … … 1013 1020 </t> 1014 1021 <figure><artwork type="example"> 1015 1016 1022 Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, 1023 text/html;level=2;q=0.4, */*;q=0.5 1017 1024 </artwork></figure> 1018 1025 <t> … … 1039 1046 <iref primary="true" item="Headers" subitem="Accept-Charset" x:for-anchor=""/> 1040 1047 <x:anchor-alias value="Accept-Charset"/> 1041 <t> 1042 The Accept-Charset request-header field can be used to indicate what 1048 <x:anchor-alias value="Accept-Charset-v"/> 1049 <t> 1050 The request-header field "Accept-Charset" can be used to indicate what 1043 1051 character sets are acceptable for the response. This field allows 1044 1052 clients capable of understanding more comprehensive or special-purpose … … 1046 1054 capable of representing documents in those character sets. 1047 1055 </t> 1048 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Charset"/> 1049 <x:ref>Accept-Charset</x:ref> = "Accept-Charset" ":" 1050 1#( ( <x:ref>charset</x:ref> / "*" ) [ ";" "q" "=" <x:ref>qvalue</x:ref> ] ) 1056 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Charset"/><iref primary="true" item="Grammar" subitem="Accept-Charset-v"/> 1057 <x:ref>Accept-Charset</x:ref> = "Accept-Charset" BWS ":" OWS 1058 <x:ref>Accept-Charset-v</x:ref> 1059 <x:ref>Accept-Charset-v</x:ref> = 1#( ( <x:ref>charset</x:ref> / "*" ) [ ";" "q" "=" <x:ref>qvalue</x:ref> ] ) 1051 1060 </artwork></figure> 1052 1061 <t> … … 1056 1065 </t> 1057 1066 <figure><artwork type="example"> 1058 1067 Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 1059 1068 </artwork></figure> 1060 1069 <t> … … 1080 1089 <iref primary="true" item="Headers" subitem="Accept-Encoding" x:for-anchor=""/> 1081 1090 <x:anchor-alias value="Accept-Encoding"/> 1091 <x:anchor-alias value="Accept-Encoding-v"/> 1082 1092 <x:anchor-alias value="codings"/> 1083 1093 <t> 1084 The Accept-Encoding request-header fieldis similar to Accept, but1094 The request-header field "Accept-Encoding" is similar to Accept, but 1085 1095 restricts the content-codings (<xref target="content.codings"/>) that are acceptable in 1086 1096 the response. 1087 1097 </t> 1088 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Encoding"/><iref primary="true" item="Grammar" subitem="codings"/> 1089 <x:ref>Accept-Encoding</x:ref> = "Accept-Encoding" ":" 1098 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Encoding"/><iref primary="true" item="Grammar" subitem="Accept-Encoding-v"/><iref primary="true" item="Grammar" subitem="codings"/> 1099 <x:ref>Accept-Encoding</x:ref> = "Accept-Encoding" BWS ":" OWS 1100 <x:ref>Accept-Encoding-v</x:ref> 1101 <x:ref>Accept-Encoding-v</x:ref> = 1090 1102 #( <x:ref>codings</x:ref> [ ";" "q" "=" <x:ref>qvalue</x:ref> ] ) 1091 <x:ref>codings</x:ref> = ( <x:ref>content-coding</x:ref> / "*" )1103 <x:ref>codings</x:ref> = ( <x:ref>content-coding</x:ref> / "*" ) 1092 1104 </artwork></figure> 1093 1105 <t> … … 1099 1111 </t> 1100 1112 <figure><artwork type="example"> 1101 1102 1103 1104 1105 1113 Accept-Encoding: compress, gzip 1114 Accept-Encoding: 1115 Accept-Encoding: * 1116 Accept-Encoding: compress;q=0.5, gzip;q=1.0 1117 Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0 1106 1118 </artwork></figure> 1107 1119 <t> … … 1162 1174 <iref primary="true" item="Headers" subitem="Accept-Language" x:for-anchor=""/> 1163 1175 <x:anchor-alias value="Accept-Language"/> 1176 <x:anchor-alias value="Accept-Language-v"/> 1164 1177 <x:anchor-alias value="language-range"/> 1165 1178 <t> 1166 The Accept-Language request-header fieldis similar to Accept, but1179 The request-header field "Accept-Language" is similar to Accept, but 1167 1180 restricts the set of natural languages that are preferred as a 1168 1181 response to the request. Language tags are defined in <xref target="language.tags"/>. 1169 1182 </t> 1170 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Language"/><iref primary="true" item="Grammar" subitem="language-range"/> 1171 <x:ref>Accept-Language</x:ref> = "Accept-Language" ":" 1183 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Language"/><iref primary="true" item="Grammar" subitem="Accept-Language-v"/><iref primary="true" item="Grammar" subitem="language-range"/> 1184 <x:ref>Accept-Language</x:ref> = "Accept-Language" BWS ":" OWS 1185 <x:ref>Accept-Language-v</x:ref> 1186 <x:ref>Accept-Language-v</x:ref> = 1172 1187 1#( <x:ref>language-range</x:ref> [ ";" "q" "=" <x:ref>qvalue</x:ref> ] ) 1173 <x:ref>language-range</x:ref> =1188 <x:ref>language-range</x:ref> = 1174 1189 <language-range, defined in <xref target="RFC4647" x:fmt="," x:sec="2.1"/>> 1175 1190 </artwork></figure> … … 1181 1196 </t> 1182 1197 <figure><artwork type="example"> 1183 1198 Accept-Language: da, en-gb;q=0.8, en;q=0.7 1184 1199 </artwork></figure> 1185 1200 <t> … … 1252 1267 <iref primary="true" item="Headers" subitem="Content-Encoding" x:for-anchor=""/> 1253 1268 <x:anchor-alias value="Content-Encoding"/> 1254 <t> 1255 The Content-Encoding entity-header field is used as a modifier to the 1269 <x:anchor-alias value="Content-Encoding-v"/> 1270 <t> 1271 The entity-header field "Content-Encoding" is used as a modifier to the 1256 1272 media-type. When present, its value indicates what additional content 1257 1273 codings have been applied to the entity-body, and thus what decoding … … 1261 1277 the identity of its underlying media type. 1262 1278 </t> 1263 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Encoding"/> 1264 <x:ref>Content-Encoding</x:ref> = "Content-Encoding" ":" 1#<x:ref>content-coding</x:ref> 1279 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Encoding"/><iref primary="true" item="Grammar" subitem="Content-Encoding-v"/> 1280 <x:ref>Content-Encoding</x:ref> = "Content-Encoding" BWS ":" OWS <x:ref>Content-Encoding-v</x:ref> 1281 <x:ref>Content-Encoding-v</x:ref> = 1#<x:ref>content-coding</x:ref> 1265 1282 </artwork></figure> 1266 1283 <t> … … 1268 1285 </t> 1269 1286 <figure><artwork type="example"> 1270 1287 Content-Encoding: gzip 1271 1288 </artwork></figure> 1272 1289 <t> … … 1300 1317 <iref primary="true" item="Headers" subitem="Content-Language" x:for-anchor=""/> 1301 1318 <x:anchor-alias value="Content-Language"/> 1302 <t> 1303 The Content-Language entity-header field describes the natural 1319 <x:anchor-alias value="Content-Language-v"/> 1320 <t> 1321 The entity-header field "Content-Language" describes the natural 1304 1322 language(s) of the intended audience for the enclosed entity. Note 1305 1323 that this might not be equivalent to all the languages used within 1306 1324 the entity-body. 1307 1325 </t> 1308 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Language"/> 1309 <x:ref>Content-Language</x:ref> = "Content-Language" ":" 1#<x:ref>language-tag</x:ref> 1326 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Language"/><iref primary="true" item="Grammar" subitem="Content-Language-v"/> 1327 <x:ref>Content-Language</x:ref> = "Content-Language" BWS ":" OWS <x:ref>Content-Language-v</x:ref> 1328 <x:ref>Content-Language-v</x:ref> = 1#<x:ref>language-tag</x:ref> 1310 1329 </artwork></figure> 1311 1330 <t> … … 1317 1336 </t> 1318 1337 <figure><artwork type="example"> 1319 1338 Content-Language: da 1320 1339 </artwork></figure> 1321 1340 <t> … … 1332 1351 </t> 1333 1352 <figure><artwork type="example"> 1334 1353 Content-Language: mi, en 1335 1354 </artwork></figure> 1336 1355 <t> … … 1352 1371 <iref primary="true" item="Headers" subitem="Content-Location" x:for-anchor=""/> 1353 1372 <x:anchor-alias value="Content-Location"/> 1354 <t> 1355 The Content-Location entity-header field &MAY; be used to supply the 1373 <x:anchor-alias value="Content-Location-v"/> 1374 <t> 1375 The entity-header field "Content-Location" &MAY; be used to supply the 1356 1376 resource location for the entity enclosed in the message when that 1357 1377 entity is accessible from a location separate from the requested … … 1363 1383 for the particular variant which is returned. 1364 1384 </t> 1365 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Location"/> 1366 <x:ref>Content-Location</x:ref> = "Content-Location" ":" 1367 ( <x:ref>absoluteURI</x:ref> / <x:ref>relativeURI</x:ref> ) 1385 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Location"/><iref primary="true" item="Grammar" subitem="Content-Location-v"/> 1386 <x:ref>Content-Location</x:ref> = "Content-Location" BWS ":" OWS 1387 <x:ref>Content-Location-v</x:ref> 1388 <x:ref>Content-Location-v</x:ref> = 1389 <x:ref>absoluteURI</x:ref> / <x:ref>relativeURI</x:ref> 1368 1390 </artwork></figure> 1369 1391 <t> … … 1400 1422 <iref primary="true" item="Headers" subitem="Content-MD5" x:for-anchor=""/> 1401 1423 <x:anchor-alias value="Content-MD5"/> 1402 <x:anchor-alias value=" md5-digest"/>1403 <t> 1404 The Content-MD5 entity-header field, as defined in <xref target="RFC1864"/>, is1424 <x:anchor-alias value="Content-MD5-v"/> 1425 <t> 1426 The entity-header field "Content-MD5", as defined in <xref target="RFC1864"/>, is 1405 1427 an MD5 digest of the entity-body for the purpose of providing an 1406 1428 end-to-end message integrity check (MIC) of the entity-body. (Note: a … … 1408 1430 in transit, but is not proof against malicious attacks.) 1409 1431 </t> 1410 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-MD5"/><iref primary="true" item="Grammar" subitem=" md5-digest"/>1411 <x:ref>Content-MD5</x:ref> = "Content-MD5" ":" <x:ref>md5-digest</x:ref>1412 <x:ref> md5-digest</x:ref>= <base64 of 128 bit MD5 digest as per <xref target="RFC1864"/>>1432 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-MD5"/><iref primary="true" item="Grammar" subitem="Content-MD5-v"/> 1433 <x:ref>Content-MD5</x:ref> = "Content-MD5" BWS ":" OWS <x:ref>Content-MD5-v</x:ref> 1434 <x:ref>Content-MD5-v</x:ref> = <base64 of 128 bit MD5 digest as per <xref target="RFC1864"/>> 1413 1435 </artwork></figure> 1414 1436 <t> … … 1475 1497 <iref primary="true" item="Headers" subitem="Content-Type" x:for-anchor=""/> 1476 1498 <x:anchor-alias value="Content-Type"/> 1477 <t> 1478 The Content-Type entity-header field indicates the media type of the 1499 <x:anchor-alias value="Content-Type-v"/> 1500 <t> 1501 The entity-header field "Content-Type" indicates the media type of the 1479 1502 entity-body sent to the recipient or, in the case of the HEAD method, 1480 1503 the media type that would have been sent had the request been a GET. 1481 1504 </t> 1482 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Type"/> 1483 <x:ref>Content-Type</x:ref> = "Content-Type" ":" <x:ref>media-type</x:ref> 1505 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Type"/><iref primary="true" item="Grammar" subitem="Content-Type-v"/> 1506 <x:ref>Content-Type</x:ref> = "Content-Type" BWS ":" OWS <x:ref>Content-Type-v</x:ref> 1507 <x:ref>Content-Type-v</x:ref> = <x:ref>media-type</x:ref> 1484 1508 </artwork></figure> 1485 1509 <t> … … 1487 1511 </t> 1488 1512 <figure><artwork type="example"> 1489 1513 Content-Type: text/html; charset=ISO-8859-4 1490 1514 </artwork></figure> 1491 1515 <t> … … 2356 2380 <iref primary="true" item="Headers" subitem="MIME-Version" x:for-anchor=""/> 2357 2381 <x:anchor-alias value="MIME-Version"/> 2382 <x:anchor-alias value="MIME-Version-v"/> 2358 2383 <t> 2359 2384 HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages &MAY; … … 2365 2390 possible) when exporting HTTP messages to strict MIME environments. 2366 2391 </t> 2367 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="MIME-Version"/> 2368 <x:ref>MIME-Version</x:ref> = "MIME-Version" ":" 1*<x:ref>DIGIT</x:ref> "." 1*<x:ref>DIGIT</x:ref> 2392 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="MIME-Version"/><iref primary="true" item="Grammar" subitem="MIME-Version-v"/> 2393 <x:ref>MIME-Version</x:ref> = "MIME-Version" BWS ":" OWS <x:ref>MIME-Version-v</x:ref> 2394 <x:ref>MIME-Version-v</x:ref> = 1*<x:ref>DIGIT</x:ref> "." 1*<x:ref>DIGIT</x:ref> 2369 2395 </artwork></figure> 2370 2396 <t> … … 2479 2505 <iref item="Content-Disposition header" primary="true" x:for-anchor=""/> 2480 2506 <x:anchor-alias value="content-disposition"/> 2507 <x:anchor-alias value="content-disposition-v"/> 2481 2508 <x:anchor-alias value="disposition-type"/> 2482 2509 <x:anchor-alias value="disposition-parm"/> … … 2490 2517 from the definition of Content-Disposition in <xref target="RFC2183"/>. 2491 2518 </t> 2492 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-disposition"/><iref primary="true" item="Grammar" subitem="disposition-type"/><iref primary="true" item="Grammar" subitem="disposition-parm"/><iref primary="true" item="Grammar" subitem="filename-parm"/><iref primary="true" item="Grammar" subitem="disp-extension-token"/><iref primary="true" item="Grammar" subitem="disp-extension-parm"/> 2493 <x:ref>content-disposition</x:ref> = "Content-Disposition" ":" 2494 <x:ref>disposition-type</x:ref> *( ";" <x:ref>disposition-parm</x:ref> ) 2519 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-disposition"/><iref primary="true" item="Grammar" subitem="content-disposition-v"/><iref primary="true" item="Grammar" subitem="disposition-type"/><iref primary="true" item="Grammar" subitem="disposition-parm"/><iref primary="true" item="Grammar" subitem="filename-parm"/><iref primary="true" item="Grammar" subitem="disp-extension-token"/><iref primary="true" item="Grammar" subitem="disp-extension-parm"/> 2520 <x:ref>content-disposition</x:ref> = "Content-Disposition" BWS ":" OWS 2521 <x:ref>content-disposition-v</x:ref> 2522 <x:ref>content-disposition-v</x:ref> = <x:ref>disposition-type</x:ref> *( ";" <x:ref>disposition-parm</x:ref> ) 2495 2523 <x:ref>disposition-type</x:ref> = "attachment" / <x:ref>disp-extension-token</x:ref> 2496 2524 <x:ref>disposition-parm</x:ref> = <x:ref>filename-parm</x:ref> / <x:ref>disp-extension-parm</x:ref> … … 2503 2531 </t> 2504 2532 <figure><artwork type="example"> 2505 2533 Content-Disposition: attachment; filename="fname.ext" 2506 2534 </artwork></figure> 2507 2535 <t> … … 2720 2748 Use "/" instead of "|" for alternatives. 2721 2749 </t> 2750 <t> 2751 Introduce new ABNF rules for "bad" whitespace ("BWS"), optional 2752 whitespace ("OWS") and required whitespace ("RWS"). 2753 </t> 2754 <t> 2755 Rewrite ABNFs to spell out whitespace rules, factor out 2756 header value format definitions. 2757 </t> 2722 2758 </list> 2723 2759 </t>
Note: See TracChangeset
for help on using the changeset viewer.
