Changeset 357


Ignore:
Timestamp:
Nov 12, 2008, 5:33:44 PM (11 years ago)
Author:
julian.reschke@…
Message:

Rewrite header ABNFs to spell out whitespace rules, factor out value format definitions. (related to #36)

Location:
draft-ietf-httpbis/latest
Files:
6 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r354 r357  
    27412741         <li>Get rid of RFC822 dependency; use RFC5234 plus extensions instead.</li>
    27422742         <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>
    27472745      </ul>
    27482746      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r354 r357  
    46634663    <t>
    46644664      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.
    46714670    </t>
    46724671  </list>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r356 r357  
    23322332      <ul>
    23332333         <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>
    23382336      </ul>
    23392337      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r356 r357  
    33503350    <t>
    33513351      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.
    33583357    </t>
    33593358  </list>
  • draft-ietf-httpbis/latest/p3-payload.html

    r345 r357  
    484484         <tr>
    485485            <td class="header left"></td>
    486             <td class="header right">November 11, 2008</td>
     486            <td class="header right">November 13, 2008</td>
    487487         </tr>
    488488      </table>
     
    631631      </p>
    632632      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<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="Augmented BNF">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>: <span class="comment">[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;.]</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 &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;.]</span>
    634634      </p>
    635635      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#notation" class="smpl">ALPHA</a>          = &lt;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>&gt;
     
    638638</pre><div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#notation" class="smpl">quoted-string</a>  = &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;
    639639  <a href="#notation" class="smpl">token</a>          = &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;
     640  <a href="#notation" class="smpl">BWS</a>            = &lt;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>&gt;
     641  <a href="#notation" class="smpl">OWS</a>            = &lt;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>&gt;
     642  <a href="#notation" class="smpl">RWS</a>            = &lt;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>&gt;
    640643</pre><div id="abnf.dependencies">
    641644         <p id="rfc.section.2.p.4">                The ABNF rules below are defined in other parts:</p>
    642645      </div>
    643       <div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absoluteURI</a>    = &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;
    644   <a href="#abnf.dependencies" class="smpl">Content-Length</a> = &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;
    645   <a href="#abnf.dependencies" class="smpl">relativeURI</a>    = &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;
    646   <a href="#abnf.dependencies" class="smpl">message-header</a> = &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;
     646      <div id="rfc.figure.u.3"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">absoluteURI</a>    = &lt;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>&gt;
     647  <a href="#abnf.dependencies" class="smpl">Content-Length</a> = &lt;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>&gt;
     648  <a href="#abnf.dependencies" class="smpl">relativeURI</a>    = &lt;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>&gt;
     649  <a href="#abnf.dependencies" class="smpl">message-header</a> = &lt;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>&gt;
    647650</pre><div id="rfc.figure.u.4"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Last-Modified</a>  = &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;
    648651</pre><div id="rfc.figure.u.5"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Content-Range</a>  = &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;
     
    736739      <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.
    737740      </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>           = <a href="#notation" class="smpl">token</a>
    740   <a href="#media.types" class="smpl">subtype</a>        = <a href="#notation" class="smpl">token</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>
    741744</pre><div id="rule.parameter">
    742745         <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.
     
    833836      <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&nbsp;6.5</a>
    834837                 / <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&nbsp;6.6</a>
    835                  / <a href="#abnf.dependencies" class="smpl">Content-Length</a>           ; <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>
     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>
    836839                 / <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&nbsp;6.7</a>
    837840                 / <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&nbsp;6.8</a>
     
    849852      <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>
    850853      <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.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
     854</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
    852855         safe and proper transfer of the message.
    853856      </p>
     
    866869      </p>
    867870      <h3 id="rfc.section.4.2.2"><a href="#rfc.section.4.2.2">4.2.2</a>&nbsp;<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.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> defines how the transfer-length of a message-body is determined.
     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.
    869872      </p>
    870873      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1>
     
    956959      <div id="rfc.iref.h.1"></div>
    957960      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<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 headers
    959          can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of a request
    960          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                   #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] )
     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> ] )
    964967 
    965968  <a href="#header.accept" class="smpl">media-range</a>    = ( "*/*"
     
    984987      </dl>
    985988      <p id="rfc.section.6.1.p.5">The example</p>
    986       <div id="rfc.figure.u.18"></div><pre class="text">    Accept: audio/*; q=0.2, audio/basic
     989      <div id="rfc.figure.u.18"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
    987990</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
    988991         quality."
     
    993996      </p>
    994997      <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">    Accept: text/plain; q=0.5, text/html,
    996             text/x-dvi; q=0.8, text/x-c
     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
    9971000</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
    9981001         send the text/x-dvi entity, and if that does not exist, send the text/plain entity."
     
    10011004         to a given type, the most specific reference has precedence. For example,
    10021005      </p>
    1003       <div id="rfc.figure.u.20"></div><pre class="text">    Accept: text/*, text/html, text/html;level=1, */*
     1006      <div id="rfc.figure.u.20"></div><pre class="text">  Accept: text/*, text/html, text/html;level=1, */*
    10041007</pre><p id="rfc.section.6.1.p.14">have the following precedence:</p>
    10051008      <div id="rfc.figure.u.21"></div><pre class="text">    1) text/html;level=1
     
    10101013         which matches that type. For example,
    10111014      </p>
    1012       <div id="rfc.figure.u.22"></div><pre class="text">    Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    1013             text/html;level=2;q=0.4, */*;q=0.5
     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
    10141017</pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p>
    10151018      <div id="rfc.figure.u.23"></div><pre class="text">    text/html;level=1         = 1
     
    10251028      <div id="rfc.iref.h.2"></div>
    10261029      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<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 field can be used to indicate what character sets are acceptable for the response. This
     1030      <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
    10281031         field allows clients capable of understanding more comprehensive or special-purpose character sets to signal that capability
    10291032         to a server which is capable of representing documents in those character sets.
    10301033      </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> ] )
    10331037</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
    10341038         example is
    10351039      </p>
    1036       <div id="rfc.figure.u.25"></div><pre class="text">   Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
     1040      <div id="rfc.figure.u.25"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    10371041</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
    10381042         not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets
     
    10461050      <div id="rfc.iref.h.3"></div>
    10471051      <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<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&nbsp;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&nbsp;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>  =
    10511057                     #( <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> / "*" )
    10531059</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.
    10541060      </p>
    10551061      <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">    Accept-Encoding: compress, gzip
    1057     Accept-Encoding:
    1058     Accept-Encoding: *
    1059     Accept-Encoding: compress;q=0.5, gzip;q=1.0
    1060     Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
     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
    10611067</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>
    10621068      <ol>
     
    10931099      <div id="rfc.iref.h.4"></div>
    10941100      <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<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 field is similar to Accept, but restricts the set of natural languages that are preferred
     1101      <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
    10961102         as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.5</a>.
    10971103      </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> =
    10991107                    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>    =
    11011109            &lt;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>&gt;
    11021110</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
    11031111         languages specified by that range. The quality value defaults to "q=1". For example,
    11041112      </p>
    1105       <div id="rfc.figure.u.29"></div><pre class="text">    Accept-Language: da, en-gb;q=0.8, en;q=0.7
     1113      <div id="rfc.figure.u.29"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
    11061114</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>
    11071115      <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:
     
    11421150      <div id="rfc.iref.h.5"></div>
    11431151      <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<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>
    11501159</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
    11511160      </p>
    1152       <div id="rfc.figure.u.31"></div><pre class="text">    Content-Encoding: gzip
     1161      <div id="rfc.figure.u.31"></div><pre class="text">  Content-Encoding: gzip
    11531162</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
    11541163         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
     
    11641173      <div id="rfc.iref.h.6"></div>
    11651174      <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<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 field describes 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.
    11671176         Note that this might not be equivalent to all the languages used within the entity-body.
    11681177      </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>
    11701180</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
    11711181         own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is
    11721182      </p>
    1173       <div id="rfc.figure.u.33"></div><pre class="text">    Content-Language: da
     1183      <div id="rfc.figure.u.33"></div><pre class="text">  Content-Language: da
    11741184</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
    11751185         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
     
    11791189         simultaneously in the original Maori and English versions, would call for
    11801190      </p>
    1181       <div id="rfc.figure.u.34"></div><pre class="text">    Content-Language: mi, en
     1191      <div id="rfc.figure.u.34"></div><pre class="text">  Content-Language: mi, en
    11821192</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
    11831193         audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended
     
    11891199      <div id="rfc.iref.h.7"></div>
    11901200      <h2 id="rfc.section.6.7"><a href="#rfc.section.6.7">6.7</a>&nbsp;<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 location
     1201      <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
    11921202         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
    11931203         multiple entities associated with it, and those entities actually have separate locations by which they might be individually
    11941204         accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned.
    11951205      </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>
    11981210</pre><p id="rfc.section.6.7.p.3">The value of Content-Location also defines the base URI for the entity.</p>
    11991211      <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
     
    12091221      <div id="rfc.iref.h.8"></div>
    12101222      <h2 id="rfc.section.6.8"><a href="#rfc.section.6.8">6.8</a>&nbsp;<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.
    12121224         (Note: a MIC is good for detecting accidental modification of the entity-body in transit, but is not proof against malicious
    12131225         attacks.)
    12141226      </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>    = &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;
     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> = &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;
    12171229</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
    12181230         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.
     
    12471259      <div id="rfc.iref.h.9"></div>
    12481260      <h2 id="rfc.section.6.9"><a href="#rfc.section.6.9">6.9</a>&nbsp;<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 field indicates the media type of the entity-body sent to the recipient or, in the case of
     1261      <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
    12501262         the HEAD method, the media type that would have been sent had the request been a GET.
    12511263      </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>
    12531266</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
    12541267      </p>
    1255       <div id="rfc.figure.u.38"></div><pre class="text">    Content-Type: text/html; charset=ISO-8859-4
     1268      <div id="rfc.figure.u.38"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
    12561269</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>.
    12571270      </p>
     
    15751588         environments.
    15761589      </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>
    15781592</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
    15791593         document and not the MIME specification.
     
    16071621      </p>
    16081622      <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<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.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol.
     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.
    16101624      </p>
    16111625      <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a>&nbsp;<a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2>
     
    16291643         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>.
    16301644      </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> )
    16331648  <a href="#content-disposition" class="smpl">disposition-type</a> = "attachment" / <a href="#content-disposition" class="smpl">disp-extension-token</a>
    16341649  <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>
     
    16371652  <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> )
    16381653</pre><p id="rfc.section.B.1.p.3">An example is</p>
    1639       <div id="rfc.figure.u.41"></div><pre class="text">     Content-Disposition: attachment; filename="fname.ext"
     1654      <div id="rfc.figure.u.41"></div><pre class="text">   Content-Disposition: attachment; filename="fname.ext"
    16401655</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
    16411656         to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only.
     
    16501665      <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
    16511666         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&nbsp;4.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1667         computed. (<a href="#entity.length" title="Entity Length">Section&nbsp;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>).
    16531668      </p>
    16541669      <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&nbsp;6.2</a>)
     
    17471762      <ul>
    17481763         <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>
    17491766      </ul>
    17501767      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
     
    17921809                  <li class="indline1">compress&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1">3.2</a></li>
    17931810                  <li class="indline1">Content-Base header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.9"><b>C.1</b></a></li>
    1794                   <li class="indline1">Content-Disposition header&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    17951812                  <li class="indline1">Content-Encoding header&nbsp;&nbsp;<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>
    17961813                  <li class="indline1">Content-Language header&nbsp;&nbsp;<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>
     
    18101827                     <ul class="ind">
    18111828                        <li class="indline1"><tt>Accept</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>6.1</b></a></li>
    1812                         <li class="indline1"><tt>Accept-Charset</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>6.2</b></a></li>
    1813                         <li class="indline1"><tt>Accept-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>6.3</b></a></li>
    1814                         <li class="indline1"><tt>accept-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>6.1</b></a></li>
    1815                         <li class="indline1"><tt>Accept-Language</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.24"><b>6.4</b></a></li>
    1816                         <li class="indline1"><tt>accept-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>6.1</b></a></li>
     1829                        <li class="indline1"><tt>Accept-Charset</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>6.2</b></a></li>
     1830                        <li class="indline1"><tt>Accept-Charset-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>6.2</b></a></li>
     1831                        <li class="indline1"><tt>Accept-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.24"><b>6.3</b></a></li>
     1832                        <li class="indline1"><tt>Accept-Encoding-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.25"><b>6.3</b></a></li>
     1833                        <li class="indline1"><tt>accept-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>6.1</b></a></li>
     1834                        <li class="indline1"><tt>Accept-Language</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>6.4</b></a></li>
     1835                        <li class="indline1"><tt>Accept-Language-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>6.4</b></a></li>
     1836                        <li class="indline1"><tt>accept-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>6.1</b></a></li>
     1837                        <li class="indline1"><tt>Accept-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>6.1</b></a></li>
    18171838                        <li class="indline1"><tt>attribute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>3.3</b></a></li>
    18181839                        <li class="indline1"><tt>charset</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>3.1</b></a></li>
    1819                         <li class="indline1"><tt>codings</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>6.3</b></a></li>
     1840                        <li class="indline1"><tt>codings</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>6.3</b></a></li>
    18201841                        <li class="indline1"><tt>content-coding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>3.2</b></a></li>
    1821                         <li class="indline1"><tt>content-disposition</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.33"><b>B.1</b></a></li>
    1822                         <li class="indline1"><tt>Content-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>6.5</b></a></li>
    1823                         <li class="indline1"><tt>Content-Language</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>6.6</b></a></li>
    1824                         <li class="indline1"><tt>Content-Location</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>6.7</b></a></li>
    1825                         <li class="indline1"><tt>Content-MD5</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>6.8</b></a></li>
    1826                         <li class="indline1"><tt>Content-Type</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.31"><b>6.9</b></a></li>
    1827                         <li class="indline1"><tt>disp-extension-parm</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.38"><b>B.1</b></a></li>
    1828                         <li class="indline1"><tt>disp-extension-token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.37"><b>B.1</b></a></li>
    1829                         <li class="indline1"><tt>disposition-parm</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.35"><b>B.1</b></a></li>
    1830                         <li class="indline1"><tt>disposition-type</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.34"><b>B.1</b></a></li>
     1842                        <li class="indline1"><tt>content-disposition</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.42"><b>B.1</b></a></li>
     1843                        <li class="indline1"><tt>content-disposition-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.43"><b>B.1</b></a></li>
     1844                        <li class="indline1"><tt>Content-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>6.5</b></a></li>
     1845                        <li class="indline1"><tt>Content-Encoding-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.31"><b>6.5</b></a></li>
     1846                        <li class="indline1"><tt>Content-Language</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.32"><b>6.6</b></a></li>
     1847                        <li class="indline1"><tt>Content-Language-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.33"><b>6.6</b></a></li>
     1848                        <li class="indline1"><tt>Content-Location</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.34"><b>6.7</b></a></li>
     1849                        <li class="indline1"><tt>Content-Location-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.35"><b>6.7</b></a></li>
     1850                        <li class="indline1"><tt>Content-MD5</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.36"><b>6.8</b></a></li>
     1851                        <li class="indline1"><tt>Content-MD5-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.37"><b>6.8</b></a></li>
     1852                        <li class="indline1"><tt>Content-Type</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.38"><b>6.9</b></a></li>
     1853                        <li class="indline1"><tt>Content-Type-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.39"><b>6.9</b></a></li>
     1854                        <li class="indline1"><tt>disp-extension-parm</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.48"><b>B.1</b></a></li>
     1855                        <li class="indline1"><tt>disp-extension-token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.47"><b>B.1</b></a></li>
     1856                        <li class="indline1"><tt>disposition-parm</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.45"><b>B.1</b></a></li>
     1857                        <li class="indline1"><tt>disposition-type</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.44"><b>B.1</b></a></li>
    18311858                        <li class="indline1"><tt>entity-body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>4.2</b></a></li>
    18321859                        <li class="indline1"><tt>entity-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>4.1</b></a></li>
    18331860                        <li class="indline1"><tt>extension-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>4.1</b></a></li>
    1834                         <li class="indline1"><tt>filename-parm</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.36"><b>B.1</b></a></li>
    1835                         <li class="indline1"><tt>language-range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.25"><b>6.4</b></a></li>
     1861                        <li class="indline1"><tt>filename-parm</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.46"><b>B.1</b></a></li>
     1862                        <li class="indline1"><tt>language-range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>6.4</b></a></li>
    18361863                        <li class="indline1"><tt>language-tag</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>3.5</b></a></li>
    1837                         <li class="indline1"><tt>md5-digest</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>6.8</b></a></li>
    1838                         <li class="indline1"><tt>media-range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>6.1</b></a></li>
     1864                        <li class="indline1"><tt>media-range</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>6.1</b></a></li>
    18391865                        <li class="indline1"><tt>media-type</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>3.3</b></a></li>
    1840                         <li class="indline1"><tt>MIME-Version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.32"><b>A.1</b></a></li>
     1866                        <li class="indline1"><tt>MIME-Version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.40"><b>A.1</b></a></li>
     1867                        <li class="indline1"><tt>MIME-Version-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.41"><b>A.1</b></a></li>
    18411868                        <li class="indline1"><tt>parameter</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>3.3</b></a></li>
    18421869                        <li class="indline1"><tt>primary-tag</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>3.5</b></a></li>
     
    18601887                        <li class="indline1">Alternate&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.12"><b>C.1</b></a></li>
    18611888                        <li class="indline1">Content-Base&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.18"><b>C.1</b></a></li>
    1862                         <li class="indline1">Content-Disposition&nbsp;&nbsp;<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&nbsp;&nbsp;<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>
    18631890                        <li class="indline1">Content-Encoding&nbsp;&nbsp;<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>
    18641891                        <li class="indline1">Content-Language&nbsp;&nbsp;<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>
     
    18901917            </li>
    18911918            <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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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">
    18931920                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2</a></li>
    1894                         <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>
    1895                         <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>
    1896                         <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.11">2</a></li>
    1897                         <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.13">4.2</a></li>
    1898                         <li class="indline1"><em>Section 4.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.14">4.2.2</a></li>
    1899                         <li class="indline1"><em>Section 8.2</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.15">A.5</a></li>
     1921                        <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>, <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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.14">2</a></li>
     1924                        <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.16">4.2</a></li>
     1925                        <li class="indline1"><em>Section 4.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.17">4.2.2</a></li>
     1926                        <li class="indline1"><em>Section 8.2</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.18">A.5</a></li>
    19011928                     </ul>
    19021929                  </li>
  • draft-ietf-httpbis/latest/p3-payload.xml

    r345 r357  
    257257  <x:anchor-alias value="quoted-string"/>
    258258  <x:anchor-alias value="token"/>
     259  <x:anchor-alias value="BWS"/>
     260  <x:anchor-alias value="OWS"/>
     261  <x:anchor-alias value="RWS"/>
    259262<t>
    260263  This specification uses the ABNF syntax defined in &notation-abnf; and
     
    271274  <x:ref>quoted-string</x:ref>  = &lt;quoted-string, defined in &basic-rules;&gt;
    272275  <x:ref>token</x:ref>          = &lt;token, defined in &basic-rules;&gt;
     276  <x:ref>BWS</x:ref>            = &lt;BWS, defined in &basic-rules;&gt;
     277  <x:ref>OWS</x:ref>            = &lt;OWS, defined in &basic-rules;&gt;
     278  <x:ref>RWS</x:ref>            = &lt;RWS, defined in &basic-rules;&gt;
    273279</artwork></figure>
    274280<t anchor="abnf.dependencies">
     
    462468</t>
    463469<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>           = <x:ref>token</x:ref>
    466   <x:ref>subtype</x:ref>        = <x:ref>token</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>
    467473</artwork></figure>
    468474<t anchor="rule.parameter">
     
    914920  <iref primary="true" item="Headers" subitem="Accept" x:for-anchor=""/>
    915921  <x:anchor-alias value="Accept"/>
     922  <x:anchor-alias value="Accept-v"/>
    916923  <x:anchor-alias value="accept-extension"/>
    917924  <x:anchor-alias value="accept-params"/>
    918925  <x:anchor-alias value="media-range"/>
    919926<t>
    920    The Accept request-header field can be used to specify certain media
     927   The request-header field "Accept" can be used to specify certain media
    921928   types which are acceptable for the response. Accept headers can be
    922929   used to indicate that the request is specifically limited to a small
     
    924931   image.
    925932</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                   #( <x:ref>media-range</x:ref> [ <x:ref>accept-params</x:ref> ] )
     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> ] )
    929936 
    930937  <x:ref>media-range</x:ref>    = ( "*/*"
     
    964971</t>
    965972<figure><artwork type="example">
    966     Accept: audio/*; q=0.2, audio/basic
     973  Accept: audio/*; q=0.2, audio/basic
    967974</artwork></figure>
    968975<t>
     
    981988</t>
    982989<figure><artwork type="example">
    983     Accept: text/plain; q=0.5, text/html,
    984             text/x-dvi; q=0.8, text/x-c
     990  Accept: text/plain; q=0.5, text/html,
     991          text/x-dvi; q=0.8, text/x-c
    985992</artwork></figure>
    986993<t>
     
    9961003</t>
    9971004<figure><artwork type="example">
    998     Accept: text/*, text/html, text/html;level=1, */*
     1005  Accept: text/*, text/html, text/html;level=1, */*
    9991006</artwork></figure>
    10001007<t>
     
    10131020</t>
    10141021<figure><artwork type="example">
    1015     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
     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
    10171024</artwork></figure>
    10181025<t>
     
    10391046  <iref primary="true" item="Headers" subitem="Accept-Charset" x:for-anchor=""/>
    10401047  <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
    10431051   character sets are acceptable for the response. This field allows
    10441052   clients capable of understanding more comprehensive or special-purpose
     
    10461054   capable of representing documents in those character sets.
    10471055</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> ] )
    10511060</artwork></figure>
    10521061<t>
     
    10561065</t>
    10571066<figure><artwork type="example">
    1058    Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
     1067  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    10591068</artwork></figure>
    10601069<t>
     
    10801089  <iref primary="true" item="Headers" subitem="Accept-Encoding" x:for-anchor=""/>
    10811090  <x:anchor-alias value="Accept-Encoding"/>
     1091  <x:anchor-alias value="Accept-Encoding-v"/>
    10821092  <x:anchor-alias value="codings"/>
    10831093<t>
    1084    The Accept-Encoding request-header field is similar to Accept, but
     1094   The request-header field "Accept-Encoding" is similar to Accept, but
    10851095   restricts the content-codings (<xref target="content.codings"/>) that are acceptable in
    10861096   the response.
    10871097</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>  =
    10901102                     #( <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> / "*" )
    10921104</artwork></figure>
    10931105<t>
     
    10991111</t>
    11001112<figure><artwork type="example">
    1101     Accept-Encoding: compress, gzip
    1102     Accept-Encoding:
    1103     Accept-Encoding: *
    1104     Accept-Encoding: compress;q=0.5, gzip;q=1.0
    1105     Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0
     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
    11061118</artwork></figure>
    11071119<t>
     
    11621174  <iref primary="true" item="Headers" subitem="Accept-Language" x:for-anchor=""/>
    11631175  <x:anchor-alias value="Accept-Language"/>
     1176  <x:anchor-alias value="Accept-Language-v"/>
    11641177  <x:anchor-alias value="language-range"/>
    11651178<t>
    1166    The Accept-Language request-header field is similar to Accept, but
     1179   The request-header field "Accept-Language" is similar to Accept, but
    11671180   restricts the set of natural languages that are preferred as a
    11681181   response to the request. Language tags are defined in <xref target="language.tags"/>.
    11691182</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> =
    11721187                    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>    =
    11741189            &lt;language-range, defined in <xref target="RFC4647" x:fmt="," x:sec="2.1"/>&gt;
    11751190</artwork></figure>
     
    11811196</t>
    11821197<figure><artwork type="example">
    1183     Accept-Language: da, en-gb;q=0.8, en;q=0.7
     1198  Accept-Language: da, en-gb;q=0.8, en;q=0.7
    11841199</artwork></figure>
    11851200<t>
     
    12521267  <iref primary="true" item="Headers" subitem="Content-Encoding" x:for-anchor=""/>
    12531268  <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
    12561272   media-type. When present, its value indicates what additional content
    12571273   codings have been applied to the entity-body, and thus what decoding
     
    12611277   the identity of its underlying media type.
    12621278</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>
    12651282</artwork></figure>
    12661283<t>
     
    12681285</t>
    12691286<figure><artwork type="example">
    1270     Content-Encoding: gzip
     1287  Content-Encoding: gzip
    12711288</artwork></figure>
    12721289<t>
     
    13001317  <iref primary="true" item="Headers" subitem="Content-Language" x:for-anchor=""/>
    13011318  <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
    13041322   language(s) of the intended audience for the enclosed entity. Note
    13051323   that this might not be equivalent to all the languages used within
    13061324   the entity-body.
    13071325</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>
    13101329</artwork></figure>
    13111330<t>
     
    13171336</t>
    13181337<figure><artwork type="example">
    1319     Content-Language: da
     1338  Content-Language: da
    13201339</artwork></figure>
    13211340<t>
     
    13321351</t>
    13331352<figure><artwork type="example">
    1334     Content-Language: mi, en
     1353  Content-Language: mi, en
    13351354</artwork></figure>
    13361355<t>
     
    13521371  <iref primary="true" item="Headers" subitem="Content-Location" x:for-anchor=""/>
    13531372  <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
    13561376   resource location for the entity enclosed in the message when that
    13571377   entity is accessible from a location separate from the requested
     
    13631383   for the particular variant which is returned.
    13641384</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>
    13681390</artwork></figure>
    13691391<t>
     
    14001422  <iref primary="true" item="Headers" subitem="Content-MD5" x:for-anchor=""/>
    14011423  <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"/>, is
     1424  <x:anchor-alias value="Content-MD5-v"/>
     1425<t>
     1426   The entity-header field "Content-MD5", as defined in <xref target="RFC1864"/>, is
    14051427   an MD5 digest of the entity-body for the purpose of providing an
    14061428   end-to-end message integrity check (MIC) of the entity-body. (Note: a
     
    14081430   in transit, but is not proof against malicious attacks.)
    14091431</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>    = &lt;base64 of 128 bit MD5 digest as per <xref target="RFC1864"/>&gt;
     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> = &lt;base64 of 128 bit MD5 digest as per <xref target="RFC1864"/>&gt;
    14131435</artwork></figure>
    14141436<t>
     
    14751497  <iref primary="true" item="Headers" subitem="Content-Type" x:for-anchor=""/>
    14761498  <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
    14791502   entity-body sent to the recipient or, in the case of the HEAD method,
    14801503   the media type that would have been sent had the request been a GET.
    14811504</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>
    14841508</artwork></figure>
    14851509<t>
     
    14871511</t>
    14881512<figure><artwork type="example">
    1489     Content-Type: text/html; charset=ISO-8859-4
     1513  Content-Type: text/html; charset=ISO-8859-4
    14901514</artwork></figure>
    14911515<t>
     
    23562380  <iref primary="true" item="Headers" subitem="MIME-Version" x:for-anchor=""/>
    23572381  <x:anchor-alias value="MIME-Version"/>
     2382  <x:anchor-alias value="MIME-Version-v"/>
    23582383<t>
    23592384   HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages &MAY;
     
    23652390   possible) when exporting HTTP messages to strict MIME environments.
    23662391</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>
    23692395</artwork></figure>
    23702396<t>
     
    24792505<iref item="Content-Disposition header" primary="true" x:for-anchor=""/>
    24802506  <x:anchor-alias value="content-disposition"/>
     2507  <x:anchor-alias value="content-disposition-v"/>
    24812508  <x:anchor-alias value="disposition-type"/>
    24822509  <x:anchor-alias value="disposition-parm"/>
     
    24902517   from the definition of Content-Disposition in <xref target="RFC2183"/>.
    24912518</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> )
    24952523  <x:ref>disposition-type</x:ref> = "attachment" / <x:ref>disp-extension-token</x:ref>
    24962524  <x:ref>disposition-parm</x:ref> = <x:ref>filename-parm</x:ref> / <x:ref>disp-extension-parm</x:ref>
     
    25032531</t>
    25042532<figure><artwork type="example">
    2505      Content-Disposition: attachment; filename="fname.ext"
     2533   Content-Disposition: attachment; filename="fname.ext"
    25062534</artwork></figure>
    25072535<t>
     
    27202748      Use "/" instead of "|" for alternatives.
    27212749    </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>
    27222758  </list>
    27232759</t>
Note: See TracChangeset for help on using the changeset viewer.