Ignore:
Timestamp:
Feb 10, 2008, 12:26:19 PM (12 years ago)
Author:
julian.reschke@…
Message:

Work on referencing ABNF rules adopted from other parts (finished for all parts, also grouped by part); relates to #36.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.html

    r206 r207  
    592592</pre><div id="rfc.figure.u.2"></div><pre class="inline">  quoted-string  = &lt;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>&gt;
    593593  token          = &lt;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>&gt;
    594 </pre><p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     594</pre><div id="abnf.dependencies">
     595         <p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     596      </div>
    595597      <div id="rfc.figure.u.3"></div><pre class="inline">  absoluteURI    = &lt;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>&gt;
    596   Allow          = &lt;Allow, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>&gt;
    597598  Content-Length = &lt;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>&gt;
    598   Content-Range  = &lt;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>&gt;
    599   Expires        = &lt;Expires, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 16.3</a>&gt;
    600   Last-Modified  = &lt;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>&gt;
    601   message-header = &lt;message-header, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>&gt;
    602   relativeURI    = &lt;relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
     599  relativeURI    = &lt;relativeURI, 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#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
     600  message-header = &lt;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>&gt;
     601</pre><div id="rfc.figure.u.4"></div><pre class="inline">  Allow          = &lt;Allow, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>&gt;
     602</pre><div id="rfc.figure.u.5"></div><pre class="inline">  Last-Modified  = &lt;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>&gt;
     603</pre><div id="rfc.figure.u.6"></div><pre class="inline">  Content-Range  = &lt;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>&gt;
     604</pre><div id="rfc.figure.u.7"></div><pre class="inline">  Expires        = &lt;Expires, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 16.3</a>&gt;
    603605</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    604606      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="character.sets" href="#character.sets">Character Sets</a></h2>
     
    620622         Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
    621623      </p>
    622       <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  charset = token
     624      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  charset = token
    623625</pre><p id="rfc.section.3.1.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
    624626         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.
     
    643645         decoded by the recipient.
    644646      </p>
    645       <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  content-coding   = token
     647      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  content-coding   = token
    646648</pre><p id="rfc.section.3.2.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;6.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;6.5</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    647649         mechanism will be required to remove the encoding.
     
    687689      <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&nbsp;6.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;6.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
    688690      </p>
    689       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  media-type     = type "/" subtype *( ";" parameter )
     691      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  media-type     = type "/" subtype *( ";" parameter )
    690692  type           = token
    691693  subtype        = token
    692694</pre><p id="rfc.section.3.3.p.3">Parameters <em class="bcp14">MAY</em> follow the type/subtype in the form of attribute/value pairs.
    693695      </p>
    694       <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  parameter               = attribute "=" value
     696      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  parameter               = attribute "=" value
    695697  attribute               = token
    696698  value                   = token | quoted-string
     
    745747         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.
    746748      </p>
    747       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  qvalue         = ( "0" [ "." 0*3DIGIT ] )
     749      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  qvalue         = ( "0" [ "." 0*3DIGIT ] )
    748750                 | ( "1" [ "." 0*3("0") ] )
    749751</pre><p id="rfc.section.3.4.p.3">"Quality values" is a misnomer, since these values merely represent relative degradation in desired quality.</p>
     
    755757      <p id="rfc.section.3.5.p.2">The syntax and registry of HTTP language tags is the same as that defined by <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags:
    756758      </p>
    757       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span>  language-tag  = primary-tag *( "-" subtag )
     759      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span>  language-tag  = primary-tag *( "-" subtag )
    758760  primary-tag   = 1*8ALPHA
    759761  subtag        = 1*8ALPHA
     
    761763         by the IANA. Example tags include:
    762764      </p>
    763       <div id="rfc.figure.u.10"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin
     765      <div id="rfc.figure.u.14"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin
    764766</pre><p id="rfc.section.3.5.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country
    765767         code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered
     
    777779         by the request.
    778780      </p>
    779       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  entity-header  = Allow                    ; <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>
     781      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  entity-header  = Allow                    ; <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>
    780782                 | Content-Encoding         ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;6.5</a>
    781783                 | Content-Language         ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;6.6</a>
     
    795797      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="entity.body" href="#entity.body">Entity Body</a></h2>
    796798      <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>
    797       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  entity-body    = *OCTET
     799      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  entity-body    = *OCTET
    798800</pre><p id="rfc.section.4.2.p.3">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
    799801         safe and proper transfer of the message.
     
    803805         and Content-Encoding. These define a two-layer, ordered encoding model:
    804806      </p>
    805       <div id="rfc.figure.u.13"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) )
     807      <div id="rfc.figure.u.17"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) )
    806808</pre><p id="rfc.section.4.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content
    807809         codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There
     
    907909         for an in-line image.
    908910      </p>
    909       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  Accept         = "Accept" ":"
     911      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  Accept         = "Accept" ":"
    910912                   #( media-range [ accept-params ] )
    911913 
     
    931933      </dl>
    932934      <p id="rfc.section.6.1.p.5">The example</p>
    933       <div id="rfc.figure.u.15"></div><pre class="text">    Accept: audio/*; q=0.2, audio/basic
     935      <div id="rfc.figure.u.19"></div><pre class="text">    Accept: audio/*; q=0.2, audio/basic
    934936</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
    935937         quality."
     
    940942      </p>
    941943      <p id="rfc.section.6.1.p.9">A more elaborate example is</p>
    942       <div id="rfc.figure.u.16"></div><pre class="text">    Accept: text/plain; q=0.5, text/html,
     944      <div id="rfc.figure.u.20"></div><pre class="text">    Accept: text/plain; q=0.5, text/html,
    943945            text/x-dvi; q=0.8, text/x-c
    944946</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
     
    948950         to a given type, the most specific reference has precedence. For example,
    949951      </p>
    950       <div id="rfc.figure.u.17"></div><pre class="text">    Accept: text/*, text/html, text/html;level=1, */*
     952      <div id="rfc.figure.u.21"></div><pre class="text">    Accept: text/*, text/html, text/html;level=1, */*
    951953</pre><p id="rfc.section.6.1.p.14">have the following precedence:</p>
    952       <div id="rfc.figure.u.18"></div><pre class="text">    1) text/html;level=1
     954      <div id="rfc.figure.u.22"></div><pre class="text">    1) text/html;level=1
    953955    2) text/html
    954956    3) text/*
     
    957959         which matches that type. For example,
    958960      </p>
    959       <div id="rfc.figure.u.19"></div><pre class="text">    Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
     961      <div id="rfc.figure.u.23"></div><pre class="text">    Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    960962            text/html;level=2;q=0.4, */*;q=0.5
    961963</pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p>
    962       <div id="rfc.figure.u.20"></div><pre class="text">    text/html;level=1         = 1
     964      <div id="rfc.figure.u.24"></div><pre class="text">    text/html;level=1         = 1
    963965    text/html                 = 0.7
    964966    text/plain                = 0.3
     
    976978         to a server which is capable of representing documents in those character sets.
    977979      </p>
    978       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.21"></span>  Accept-Charset = "Accept-Charset" ":"
     980      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.21"></span>  Accept-Charset = "Accept-Charset" ":"
    979981          1#( ( charset | "*" ) [ ";" "q" "=" qvalue ] )
    980982</pre><p id="rfc.section.6.2.p.3">Character set values are described in <a href="#character.sets" title="Character Sets">Section&nbsp;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
    981983         example is
    982984      </p>
    983       <div id="rfc.figure.u.22"></div><pre class="text">   Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
     985      <div id="rfc.figure.u.26"></div><pre class="text">   Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    984986</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
    985987         not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets
     
    995997      <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&nbsp;3.2</a>) that are acceptable in the response.
    996998      </p>
    997       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  Accept-Encoding  = "Accept-Encoding" ":"
     999      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  Accept-Encoding  = "Accept-Encoding" ":"
    9981000                     #( codings [ ";" "q" "=" qvalue ] )
    9991001  codings          = ( content-coding | "*" )
    10001002</pre><p id="rfc.section.6.3.p.3">Examples of its use are:</p>
    1001       <div id="rfc.figure.u.24"></div><pre class="text">    Accept-Encoding: compress, gzip
     1003      <div id="rfc.figure.u.28"></div><pre class="text">    Accept-Encoding: compress, gzip
    10021004    Accept-Encoding:
    10031005    Accept-Encoding: *
     
    10411043         as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.5</a>.
    10421044      </p>
    1043       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  Accept-Language = "Accept-Language" ":"
     1045      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  Accept-Language = "Accept-Language" ":"
    10441046                    1#( language-range [ ";" "q" "=" qvalue ] )
    10451047  language-range  = ( ( 1*8ALPHA *( "-" 1*8ALPHA ) ) | "*" )
     
    10471049         that range. The quality value defaults to "q=1". For example,
    10481050      </p>
    1049       <div id="rfc.figure.u.26"></div><pre class="text">    Accept-Language: da, en-gb;q=0.8, en;q=0.7
     1051      <div id="rfc.figure.u.30"></div><pre class="text">    Accept-Language: da, en-gb;q=0.8, en;q=0.7
    10501052</pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English." A language-range matches a language-tag
    10511053         if it exactly equals the tag, or if it exactly equals a prefix of the tag such that the first tag character following the
     
    10851087         without losing the identity of its underlying media type.
    10861088      </p>
    1087       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  Content-Encoding  = "Content-Encoding" ":" 1#content-coding
     1089      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  Content-Encoding  = "Content-Encoding" ":" 1#content-coding
    10881090</pre><p id="rfc.section.6.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;3.2</a>. An example of its use is
    10891091      </p>
    1090       <div id="rfc.figure.u.28"></div><pre class="text">    Content-Encoding: gzip
     1092      <div id="rfc.figure.u.32"></div><pre class="text">    Content-Encoding: gzip
    10911093</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
    10921094         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
     
    11051107         Note that this might not be equivalent to all the languages used within the entity-body.
    11061108      </p>
    1107       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.27"></span>  Content-Language  = "Content-Language" ":" 1#language-tag
     1109      <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.27"></span>  Content-Language  = "Content-Language" ":" 1#language-tag
    11081110</pre><p id="rfc.section.6.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.5</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate entities according to the user's
    11091111         own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is
    11101112      </p>
    1111       <div id="rfc.figure.u.30"></div><pre class="text">    Content-Language: da
     1113      <div id="rfc.figure.u.34"></div><pre class="text">    Content-Language: da
    11121114</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
    11131115         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
     
    11171119         simultaneously in the original Maori and English versions, would call for
    11181120      </p>
    1119       <div id="rfc.figure.u.31"></div><pre class="text">    Content-Language: mi, en
     1121      <div id="rfc.figure.u.35"></div><pre class="text">    Content-Language: mi, en
    11201122</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
    11211123         audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended
     
    11321134         accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned.
    11331135      </p>
    1134       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.28"></span>  Content-Location = "Content-Location" ":"
     1136      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.28"></span>  Content-Location = "Content-Location" ":"
    11351137                    ( absoluteURI | relativeURI )
    11361138</pre><p id="rfc.section.6.7.p.3">The value of Content-Location also defines the base URI for the entity.</p>
     
    11511153         attacks.)
    11521154      </p>
    1153       <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  Content-MD5   = "Content-MD5" ":" md5-digest
     1155      <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  Content-MD5   = "Content-MD5" ":" md5-digest
    11541156  md5-digest    = &lt;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>&gt;
    11551157</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
     
    11881190         the HEAD method, the media type that would have been sent had the request been a GET.
    11891191      </p>
    1190       <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  Content-Type   = "Content-Type" ":" media-type
     1192      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  Content-Type   = "Content-Type" ":" media-type
    11911193</pre><p id="rfc.section.6.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;3.3</a>. An example of the field is
    11921194      </p>
    1193       <div id="rfc.figure.u.35"></div><pre class="text">    Content-Type: text/html; charset=ISO-8859-4
     1195      <div id="rfc.figure.u.39"></div><pre class="text">    Content-Type: text/html; charset=ISO-8859-4
    11941196</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&nbsp;4.2.1</a>.
    11951197      </p>
     
    14071409         environments.
    14081410      </p>
    1409       <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  MIME-Version   = "MIME-Version" ":" 1*DIGIT "." 1*DIGIT
     1411      <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  MIME-Version   = "MIME-Version" ":" 1*DIGIT "." 1*DIGIT
    14101412</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
    14111413         document and not the MIME specification.
     
    14611463         in <a href="#RFC1806" id="rfc.xref.RFC1806.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header">[RFC1806]</cite></a>.
    14621464      </p>
    1463       <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span>  content-disposition = "Content-Disposition" ":"
     1465      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span>  content-disposition = "Content-Disposition" ":"
    14641466                        disposition-type *( ";" disposition-parm )
    14651467  disposition-type = "attachment" | disp-extension-token
     
    14691471  disp-extension-parm = token "=" ( token | quoted-string )
    14701472</pre><p id="rfc.section.B.1.p.3">An example is</p>
    1471       <div id="rfc.figure.u.38"></div><pre class="text">     Content-Disposition: attachment; filename="fname.ext"
     1473      <div id="rfc.figure.u.42"></div><pre class="text">     Content-Disposition: attachment; filename="fname.ext"
    14721474</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
    14731475         to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only.
     
    16791681                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2</a></li>
    16801682                        <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<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>
    1681                         <li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a></li>
    1682                         <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.10">2</a></li>
     1683                        <li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a></li>
     1684                        <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.11">2</a></li>
    16831685                        <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.13">4.2</a></li>
    16841686                        <li class="indline1"><em>Section 4.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.14">4.2.2</a></li>
Note: See TracChangeset for help on using the changeset viewer.