Changeset 425 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 21/11/08 20:25:09 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.html
r424 r425 638 638 </p> 639 639 <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a> <a id="notation" href="#notation">Syntax Notation</a></h2> 640 <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</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>. 640 <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</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>. The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#section-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG 641 (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character), 642 and WSP (whitespace). 641 643 </p> 642 644 <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a> <a id="core.rules" href="#core.rules">Core Rules</a></h3> 643 645 <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.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>: 644 646 </p> 645 <div id="rfc.figure.u.1"></div><pre class="inline"> <a href="#core.rules" 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 1.2.2</a>> 646 <a href="#core.rules" class="smpl">DIGIT</a> = <DIGIT, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>> 647 <a href="#core.rules" class="smpl">OCTET</a> = <OCTET, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>> 648 </pre><div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#core.rules" 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 1.2.2</a>> 649 <a href="#core.rules" 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 1.2.2</a>> 650 <a href="#core.rules" class="smpl">OWS</a> = <OWS, 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 1.2.2</a>> 647 <div id="rfc.figure.u.1"></div><pre class="inline"> <a href="#core.rules" class="smpl">quoted-string</a> = <quoted-string, 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 1.2.2</a>> 648 <a href="#core.rules" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>> 649 <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>> 651 650 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> 652 651 <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> 653 <div id="rfc.figure.u. 3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, 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#uri" title="Uniform Resource Identifiers">Section 2.1</a>>654 <a href="#abnf.dependencies" class="smpl">Content-Length</a> = <Content-Length, 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#header.content-length" title="Content-Length">Section 8.2</a>>655 <a href="#abnf.dependencies" class="smpl">message-header</a> = <message-header, 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#message.headers" title="Message Headers">Section 4.2</a>>656 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, 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#uri" title="Uniform Resource Identifiers">Section 2.1</a>>657 </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 6.6</a>>658 </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 5.2</a>>659 </pre><div id="rfc.figure.u. 6"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Expires</a> = <Expires, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 15.3</a>>652 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">absolute-URI</a> = <absolute-URI, 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#uri" title="Uniform Resource Identifiers">Section 2.1</a>> 653 <a href="#abnf.dependencies" class="smpl">Content-Length</a> = <Content-Length, 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#header.content-length" title="Content-Length">Section 8.2</a>> 654 <a href="#abnf.dependencies" class="smpl">message-header</a> = <message-header, 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#message.headers" title="Message Headers">Section 4.2</a>> 655 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, 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#uri" title="Uniform Resource Identifiers">Section 2.1</a>> 656 </pre><div id="rfc.figure.u.3"></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 6.6</a>> 657 </pre><div id="rfc.figure.u.4"></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 5.2</a>> 658 </pre><div id="rfc.figure.u.5"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">Expires</a> = <Expires, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 15.3</a>> 660 659 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> 661 660 <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="character.sets" href="#character.sets">Character Sets</a></h2> … … 679 678 </p> 680 679 </div> 681 <div id="rfc.figure.u. 7"></div><pre class="inline"><span id="rfc.iref.g.1"></span> <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a>680 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.1"></span> <a href="#rule.charset" class="smpl">charset</a> = <a href="#core.rules" class="smpl">token</a> 682 681 </pre><p id="rfc.section.2.1.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA 683 682 Character Set registry <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry. … … 702 701 decoded by the recipient. 703 702 </p> 704 <div id="rfc.figure.u. 8"></div><pre class="inline"><span id="rfc.iref.g.2"></span> <a href="#content.codings" class="smpl">content-coding</a> = <a href="#core.rules" class="smpl">token</a>703 <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.2"></span> <a href="#content.codings" class="smpl">content-coding</a> = <a href="#core.rules" class="smpl">token</a> 705 704 </pre><p id="rfc.section.2.2.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section 5.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section 5.5</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding 706 705 mechanism will be required to remove the encoding. … … 746 745 <p id="rfc.section.2.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 5.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section 5.1</a>) header fields in order to provide open and extensible data typing and type negotiation. 747 746 </p> 748 <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="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )747 <div id="rfc.figure.u.8"></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="#core.rules" class="smpl">OWS</a> ";" <a href="#core.rules" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> ) 749 748 <a href="#media.types" class="smpl">type</a> = <a href="#core.rules" class="smpl">token</a> 750 749 <a href="#media.types" class="smpl">subtype</a> = <a href="#core.rules" class="smpl">token</a> … … 753 752 </p> 754 753 </div> 755 <div id="rfc.figure.u. 10"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span> <a href="#rule.parameter" class="smpl">parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a>754 <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span> <a href="#rule.parameter" class="smpl">parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a> 756 755 <a href="#rule.parameter" class="smpl">attribute</a> = <a href="#core.rules" class="smpl">token</a> 757 756 <a href="#rule.parameter" class="smpl">value</a> = <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> … … 809 808 a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. 810 809 </p> 811 <div id="rfc.figure.u.1 1"></div><pre class="inline"><span id="rfc.iref.g.10"></span> <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] )810 <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.10"></span> <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#notation" class="smpl">DIGIT</a> ] ) 812 811 / ( "1" [ "." 0*3("0") ] ) 813 812 </pre><p id="rfc.section.2.4.p.3">"Quality values" is a misnomer, since these values merely represent relative degradation in desired quality.</p> … … 819 818 <p id="rfc.section.2.5.p.2">The syntax and registry of HTTP language tags is the same as that defined by <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags: 820 819 </p> 821 <div id="rfc.figure.u.1 2"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span> <a href="#language.tags" class="smpl">language-tag</a> = <a href="#language.tags" class="smpl">primary-tag</a> *( "-" <a href="#language.tags" class="smpl">subtag</a> )822 <a href="#language.tags" class="smpl">primary-tag</a> = 1*8<a href="# core.rules" class="smpl">ALPHA</a>823 <a href="#language.tags" class="smpl">subtag</a> = 1*8<a href="# core.rules" class="smpl">ALPHA</a>820 <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span> <a href="#language.tags" class="smpl">language-tag</a> = <a href="#language.tags" class="smpl">primary-tag</a> *( "-" <a href="#language.tags" class="smpl">subtag</a> ) 821 <a href="#language.tags" class="smpl">primary-tag</a> = 1*8<a href="#notation" class="smpl">ALPHA</a> 822 <a href="#language.tags" class="smpl">subtag</a> = 1*8<a href="#notation" class="smpl">ALPHA</a> 824 823 </pre><p id="rfc.section.2.5.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language tags is administered 825 824 by the IANA. Example tags include: 826 825 </p> 827 <div id="rfc.figure.u.1 3"></div><pre class="text"> en, en-US, en-cockney, i-cherokee, x-pig-latin826 <div id="rfc.figure.u.12"></div><pre class="text"> en, en-US, en-cockney, i-cherokee, x-pig-latin 828 827 </pre><p id="rfc.section.2.5.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country 829 828 code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered … … 841 840 by the request. 842 841 </p> 843 <div id="rfc.figure.u.1 4"></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 5.5</a>842 <div id="rfc.figure.u.13"></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 5.5</a> 844 843 / <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 5.6</a> 845 / <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <a href="#Part1" id="rfc.xref.Part1.1 3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 8.2</a>844 / <a href="#abnf.dependencies" class="smpl">Content-Length</a> ; <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#header.content-length" title="Content-Length">Section 8.2</a> 846 845 / <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 5.7</a> 847 846 / <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 5.8</a> … … 858 857 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="entity.body" href="#entity.body">Entity Body</a></h2> 859 858 <p id="rfc.section.3.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> 860 <div id="rfc.figure.u.1 5"></div><pre class="inline"><span id="rfc.iref.g.16"></span> <a href="#entity.body" class="smpl">entity-body</a> = *<a href="#core.rules" class="smpl">OCTET</a>861 </pre><p id="rfc.section.3.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 4"><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 ensure859 <div id="rfc.figure.u.14"></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> 860 </pre><p id="rfc.section.3.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.11"><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 862 861 safe and proper transfer of the message. 863 862 </p> … … 866 865 and Content-Encoding. These define a two-layer, ordered encoding model: 867 866 </p> 868 <div id="rfc.figure.u.1 6"></div><pre class="text"> entity-body := Content-Encoding( Content-Type( data ) )867 <div id="rfc.figure.u.15"></div><pre class="text"> entity-body := Content-Encoding( Content-Type( data ) ) 869 868 </pre><p id="rfc.section.3.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content 870 869 codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There … … 876 875 </p> 877 876 <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a> <a id="entity.length" href="#entity.length">Entity Length</a></h3> 878 <p id="rfc.section.3.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 5"><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.877 <p id="rfc.section.3.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.12"><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. 879 878 </p> 880 879 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1> … … 970 969 a request for an in-line image. 971 970 </p> 972 <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> <a href="#header.accept" class="smpl">Accept</a> = "Accept" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a>971 <div id="rfc.figure.u.16"></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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a> 973 972 <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> ] ) 974 973 … … 995 994 </dl> 996 995 <p id="rfc.section.5.1.p.5">The example</p> 997 <div id="rfc.figure.u.1 8"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic996 <div id="rfc.figure.u.17"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic 998 997 </pre><p id="rfc.section.5.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 999 998 quality." … … 1004 1003 </p> 1005 1004 <p id="rfc.section.5.1.p.9">A more elaborate example is</p> 1006 <div id="rfc.figure.u.1 9"></div><pre class="text"> Accept: text/plain; q=0.5, text/html,1005 <div id="rfc.figure.u.18"></div><pre class="text"> Accept: text/plain; q=0.5, text/html, 1007 1006 text/x-dvi; q=0.8, text/x-c 1008 1007 </pre><p id="rfc.section.5.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 … … 1012 1011 to a given type, the most specific reference has precedence. For example, 1013 1012 </p> 1014 <div id="rfc.figure.u. 20"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */*1013 <div id="rfc.figure.u.19"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */* 1015 1014 </pre><p id="rfc.section.5.1.p.14">have the following precedence:</p> 1016 <div id="rfc.figure.u.2 1"></div><pre class="text"> 1) text/html;level=11015 <div id="rfc.figure.u.20"></div><pre class="text"> 1) text/html;level=1 1017 1016 2) text/html 1018 1017 3) text/* … … 1021 1020 which matches that type. For example, 1022 1021 </p> 1023 <div id="rfc.figure.u.2 2"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,1022 <div id="rfc.figure.u.21"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, 1024 1023 text/html;level=2;q=0.4, */*;q=0.5 1025 1024 </pre><p id="rfc.section.5.1.p.18">would cause the following values to be associated:</p> 1026 <div id="rfc.figure.u.2 3"></div><pre class="text"> text/html;level=1 = 11025 <div id="rfc.figure.u.22"></div><pre class="text"> text/html;level=1 = 1 1027 1026 text/html = 0.7 1028 1027 text/plain = 0.3 … … 1040 1039 to a server which is capable of representing documents in those character sets. 1041 1040 </p> 1042 <div id="rfc.figure.u.2 4"></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" ":" <a href="#core.rules" class="smpl">OWS</a>1041 <div id="rfc.figure.u.23"></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" ":" <a href="#core.rules" class="smpl">OWS</a> 1043 1042 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> 1044 1043 <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" ) … … 1047 1046 example is 1048 1047 </p> 1049 <div id="rfc.figure.u.2 5"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.81048 <div id="rfc.figure.u.24"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 1050 1049 </pre><p id="rfc.section.5.2.p.5">The special value "*", if present in the Accept-Charset field, matches every character set (including ISO-8859-1) which is 1051 1050 not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets … … 1061 1060 <p id="rfc.section.5.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 2.2</a>) that are acceptable in the response. 1062 1061 </p> 1063 <div id="rfc.figure.u.2 6"></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" ":" <a href="#core.rules" class="smpl">OWS</a>1062 <div id="rfc.figure.u.25"></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" ":" <a href="#core.rules" class="smpl">OWS</a> 1064 1063 <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> 1065 1064 <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a> = … … 1069 1068 </p> 1070 1069 <p id="rfc.section.5.3.p.4">Examples of its use are:</p> 1071 <div id="rfc.figure.u.2 7"></div><pre class="text"> Accept-Encoding: compress, gzip1070 <div id="rfc.figure.u.26"></div><pre class="text"> Accept-Encoding: compress, gzip 1072 1071 Accept-Encoding: 1073 1072 Accept-Encoding: * … … 1111 1110 as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.5</a>. 1112 1111 </p> 1113 <div id="rfc.figure.u.2 8"></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" ":" <a href="#core.rules" class="smpl">OWS</a>1112 <div id="rfc.figure.u.27"></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" ":" <a href="#core.rules" class="smpl">OWS</a> 1114 1113 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> 1115 1114 <a href="#header.accept-language" class="smpl">Accept-Language-v</a> = … … 1120 1119 languages specified by that range. The quality value defaults to "q=1". For example, 1121 1120 </p> 1122 <div id="rfc.figure.u.2 9"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.71121 <div id="rfc.figure.u.28"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.7 1123 1122 </pre><p id="rfc.section.5.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English."</p> 1124 1123 <p id="rfc.section.5.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: … … 1164 1163 to be compressed without losing the identity of its underlying media type. 1165 1164 </p> 1166 <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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a>1165 <div id="rfc.figure.u.29"></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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> 1167 1166 <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = 1#<a href="#content.codings" class="smpl">content-coding</a> 1168 1167 </pre><p id="rfc.section.5.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section 2.2</a>. An example of its use is 1169 1168 </p> 1170 <div id="rfc.figure.u.3 1"></div><pre class="text"> Content-Encoding: gzip1169 <div id="rfc.figure.u.30"></div><pre class="text"> Content-Encoding: gzip 1171 1170 </pre><p id="rfc.section.5.5.p.5">The content-coding is a characteristic of the entity identified by the request-target. Typically, the entity-body is stored 1172 1171 with 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 … … 1185 1184 Note that this might not be equivalent to all the languages used within the entity-body. 1186 1185 </p> 1187 <div id="rfc.figure.u.3 2"></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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a>1186 <div id="rfc.figure.u.31"></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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a> 1188 1187 <a href="#header.content-language" class="smpl">Content-Language-v</a> = 1#<a href="#language.tags" class="smpl">language-tag</a> 1189 1188 </pre><p id="rfc.section.5.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.5</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate entities according to the user's 1190 1189 own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is 1191 1190 </p> 1192 <div id="rfc.figure.u.3 3"></div><pre class="text"> Content-Language: da1191 <div id="rfc.figure.u.32"></div><pre class="text"> Content-Language: da 1193 1192 </pre><p id="rfc.section.5.6.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean 1194 1193 that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language … … 1198 1197 simultaneously in the original Maori and English versions, would call for 1199 1198 </p> 1200 <div id="rfc.figure.u.3 4"></div><pre class="text"> Content-Language: mi, en1199 <div id="rfc.figure.u.33"></div><pre class="text"> Content-Language: mi, en 1201 1200 </pre><p id="rfc.section.5.6.p.8">However, just because multiple languages are present within an entity does not mean that it is intended for multiple linguistic 1202 1201 audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended … … 1213 1212 accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned. 1214 1213 </p> 1215 <div id="rfc.figure.u.3 5"></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" ":" <a href="#core.rules" class="smpl">OWS</a>1214 <div id="rfc.figure.u.34"></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" ":" <a href="#core.rules" class="smpl">OWS</a> 1216 1215 <a href="#header.content-location" class="smpl">Content-Location-v</a> 1217 1216 <a href="#header.content-location" class="smpl">Content-Location-v</a> = … … 1234 1233 attacks.) 1235 1234 </p> 1236 <div id="rfc.figure.u.3 6"></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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>1235 <div id="rfc.figure.u.35"></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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a> 1237 1236 <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>> 1238 1237 </pre><p id="rfc.section.5.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 … … 1271 1270 the HEAD method, the media type that would have been sent had the request been a GET. 1272 1271 </p> 1273 <div id="rfc.figure.u.3 7"></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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>1272 <div id="rfc.figure.u.36"></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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a> 1274 1273 <a href="#header.content-type" class="smpl">Content-Type-v</a> = <a href="#media.types" class="smpl">media-type</a> 1275 1274 </pre><p id="rfc.section.5.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section 2.3</a>. An example of the field is 1276 1275 </p> 1277 <div id="rfc.figure.u.3 8"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-41276 <div id="rfc.figure.u.37"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-4 1278 1277 </pre><p id="rfc.section.5.9.p.5">Further discussion of methods for identifying the media type of an entity is provided in <a href="#type" title="Type">Section 3.2.1</a>. 1279 1278 </p> … … 1408 1407 <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References 1409 1408 </h2> 1410 <table summary="Normative References"> 1409 <table summary="Normative References"> 1411 1410 <tr> 1412 1411 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> … … 1487 1486 <td class="reference"><b id="RFC4647">[RFC4647]</b></td> 1488 1487 <td class="top"><a title="Yahoo! Inc.">Phillips, A., Ed.</a> and <a title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc4647">Matching of Language Tags</a>”, BCP 47, RFC 4647, September 2006. 1488 </td> 1489 </tr> 1490 <tr> 1491 <td class="reference"><b id="RFC5234">[RFC5234]</b></td> 1492 <td class="top"><a title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD 68, RFC 5234, January 2008. 1489 1493 </td> 1490 1494 </tr> … … 1597 1601 environments. 1598 1602 </p> 1599 <div id="rfc.figure.u.3 9"></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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>1600 <a href="#mime-version" class="smpl">MIME-Version-v</a> = 1*<a href="# core.rules" class="smpl">DIGIT</a> "." 1*<a href="#core.rules" class="smpl">DIGIT</a>1603 <div id="rfc.figure.u.38"></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" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a> 1604 <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> 1601 1605 </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 1602 1606 document and not the MIME specification. … … 1616 1620 </p> 1617 1621 <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2> 1618 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#full.date" title="Full Date">Section 3.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.1 6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.1622 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#full.date" title="Full Date">Section 3.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary. 1619 1623 </p> 1620 1624 <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2> … … 1633 1637 </p> 1634 1638 <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2> 1635 <p id="rfc.section.A.6.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 7"><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.1639 <p id="rfc.section.A.6.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.14"><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. 1636 1640 </p> 1637 1641 <h2 id="rfc.section.A.7"><a href="#rfc.section.A.7">A.7</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> … … 1655 1659 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>. 1656 1660 </p> 1657 <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" ":" <a href="#core.rules" class="smpl">OWS</a>1661 <div id="rfc.figure.u.39"></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" ":" <a href="#core.rules" class="smpl">OWS</a> 1658 1662 <a href="#content-disposition" class="smpl">content-disposition-v</a> 1659 1663 <a href="#content-disposition" class="smpl">content-disposition-v</a> = <a href="#content-disposition" class="smpl">disposition-type</a> … … 1665 1669 <a href="#content-disposition" class="smpl">disp-extension-parm</a> = <a href="#core.rules" class="smpl">token</a> "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> ) 1666 1670 </pre><p id="rfc.section.B.1.p.3">An example is</p> 1667 <div id="rfc.figure.u.4 1"></div><pre class="text"> Content-Disposition: attachment; filename="fname.ext"1671 <div id="rfc.figure.u.40"></div><pre class="text"> Content-Disposition: attachment; filename="fname.ext" 1668 1672 </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 1669 1673 to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only. … … 1678 1682 <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 1679 1683 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 1680 computed. (<a href="#entity.length" title="Entity Length">Section 3.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.1 8"><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>).1684 computed. (<a href="#entity.length" title="Entity Length">Section 3.2.2</a>, see also <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="#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>). 1681 1685 </p> 1682 1686 <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 5.2</a>) … … 1697 1701 </p> 1698 1702 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 1699 <div id="rfc.figure.u.42"></div> <pre class="inline">ALPHA = <ALPHA, defined in [Part1], Section 1.2.2> 1700 Accept = "Accept:" OWS Accept-v 1703 <div id="rfc.figure.u.41"></div> <pre class="inline">Accept = "Accept:" OWS Accept-v 1701 1704 Accept-Charset = "Accept-Charset:" OWS Accept-Charset-v 1702 1705 Accept-Charset-v = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q=" … … 1726 1729 Content-Type = "Content-Type:" OWS Content-Type-v 1727 1730 Content-Type-v = media-type 1728 DIGIT = <DIGIT, defined in [Part1], Section 1.2.2>1729 1731 Expires = <Expires, defined in [Part6], Section 15.3> 1730 1732 Last-Modified = <Last-Modified, defined in [Part4], Section 6.6> 1731 1733 MIME-Version = "MIME-Version:" OWS MIME-Version-v 1732 1734 MIME-Version-v = 1*DIGIT "." 1*DIGIT 1733 OCTET = <OCTET, defined in [Part1], Section 1.2.2>1734 1735 OWS = <OWS, defined in [Part1], Section 1.2.2> 1735 1736 absolute-URI = <absolute-URI, defined in [Part1], Section 2.1> … … 2023 2024 </li> 2024 2025 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> 2025 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2. 1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.1</a>, <a class="iref" href="#rfc.xref.Part1.14">3.2</a>, <a class="iref" href="#rfc.xref.Part1.15">3.2.2</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.16">A.3</a>, <a class="iref" href="#rfc.xref.Part1.17">A.6</a>, <a class="iref" href="#rfc.xref.Part1.18">C.1</a><ul class="ind">2026 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a>, <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.6">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.10">3.1</a>, <a class="iref" href="#rfc.xref.Part1.11">3.2</a>, <a class="iref" href="#rfc.xref.Part1.12">3.2.2</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.13">A.3</a>, <a class="iref" href="#rfc.xref.Part1.14">A.6</a>, <a class="iref" href="#rfc.xref.Part1.15">C.1</a><ul class="ind"> 2026 2027 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 2027 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a> , <a class="iref" href="#rfc.xref.Part1.6">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.7">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.8">1.2.1</a></li>2028 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1. 9">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a></li>2029 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.1 6">A.3</a></li>2030 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1. 11">1.2.2</a></li>2031 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.1 4">3.2</a></li>2032 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.1 5">3.2.2</a></li>2033 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1. 10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.1</a></li>2034 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.1 7">A.6</a></li>2028 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a></li> 2029 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.6">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a></li> 2030 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.13">A.3</a></li> 2031 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a></li> 2032 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.11">3.2</a></li> 2033 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.12">3.2.2</a></li> 2034 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.7">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.10">3.1</a></li> 2035 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.14">A.6</a></li> 2035 2036 </ul> 2036 2037 </li> … … 2095 2096 </ul> 2096 2097 </li> 2098 <li class="indline1"><em>RFC5234</em> <a class="iref" href="#rfc.xref.RFC5234.1">1.2</a>, <a class="iref" href="#RFC5234"><b>9.1</b></a><ul class="ind"> 2099 <li class="indline1"><em>Appendix B.1</em> <a class="iref" href="#rfc.xref.RFC5234.1">1.2</a></li> 2100 </ul> 2101 </li> 2097 2102 <li class="indline1"><em>RFC5322</em> <a class="iref" href="#RFC5322"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC5322.1">A</a></li> 2098 2103 </ul>
Note: See TracChangeset
for help on using the changeset viewer.