Ignore:
Timestamp:
Nov 13, 2008, 10:53:12 AM (11 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 edited

Legend:

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

    r357 r366  
    963963         a request for an in-line image.
    964964      </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>
     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" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a>
    966966  <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> ] )
    967967 
     
    10321032         to a server which is capable of representing documents in those character sets.
    10331033      </p>
    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
     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" ":" <a href="#notation" class="smpl">OWS</a>
    10351035          <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a>
    10361036  <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> ] )
     
    10521052      <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.
    10531053      </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
     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" ":" <a href="#notation" class="smpl">OWS</a>
    10551055                     <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a>
    10561056  <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a>  =
     
    11021102         as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.5</a>.
    11031103      </p>
    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
     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" ":" <a href="#notation" class="smpl">OWS</a>
    11051105                    <a href="#header.accept-language" class="smpl">Accept-Language-v</a>
    11061106  <a href="#header.accept-language" class="smpl">Accept-Language-v</a> =
     
    11551155         to be compressed without losing the identity of its underlying media type.
    11561156      </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>
     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" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a>
    11581158  <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
    11591159</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
     
    11761176         Note that this might not be equivalent to all the languages used within the entity-body.
    11771177      </p>
    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>
     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" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a>
    11791179  <a href="#header.content-language" class="smpl">Content-Language-v</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
    11801180</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
     
    12041204         accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned.
    12051205      </p>
    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
     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" ":" <a href="#notation" class="smpl">OWS</a>
    12071207                    <a href="#header.content-location" class="smpl">Content-Location-v</a>
    12081208  <a href="#header.content-location" class="smpl">Content-Location-v</a> =
     
    12251225         attacks.)
    12261226      </p>
    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>
     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" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>
    12281228  <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;
    12291229</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
     
    12621262         the HEAD method, the media type that would have been sent had the request been a GET.
    12631263      </p>
    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>
     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" ":" <a href="#notation" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>
    12651265  <a href="#header.content-type" class="smpl">Content-Type-v</a> = <a href="#media.types" class="smpl">media-type</a>
    12661266</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
     
    15881588         environments.
    15891589      </p>
    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>
     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" ":" <a href="#notation" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>
    15911591  <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>
    15921592</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
     
    16431643         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>.
    16441644      </p>
    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
     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" ":" <a href="#notation" class="smpl">OWS</a>
    16461646                        <a href="#content-disposition" class="smpl">content-disposition-v</a>
    16471647  <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> )
Note: See TracChangeset for help on using the changeset viewer.