* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 232


Ignore:
Timestamp:
2008-03-11 01:43:48 (7 years ago)
Author:
julian.reschke@gmx.de
Message:

Resolve #105: Reclassify Allow header as response header (closes #105).

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r230 r232  
    447447         <tr> 
    448448            <td class="header left"></td> 
    449             <td class="header right">March 8, 2008</td> 
     449            <td class="header right">March 11, 2008</td> 
    450450         </tr> 
    451451      </table> 
     
    783783      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#response.header.fields" class="smpl">response-header</a> = <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a>           ; <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 6.1</a> 
    784784                  | <a href="#abnf.dependencies" class="smpl">Age</a>                     ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a> 
     785                  | <a href="#header.allow" class="smpl">Allow</a>                   ; <a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;10.1</a> 
    785786                  | <a href="#abnf.dependencies" class="smpl">ETag</a>                    ; <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a> 
    786787                  | <a href="#header.location" class="smpl">Location</a>                ; <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;10.4</a> 
     
    13881389      <div id="rfc.iref.h.2"></div> 
    13891390      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h2> 
    1390       <p id="rfc.section.10.1.p.1">The Allow entity-header field lists the set of methods supported by the resource identified by the Request-URI. The purpose 
     1391      <p id="rfc.section.10.1.p.1">The Allow response-header field lists the set of methods supported by the resource identified by the Request-URI. The purpose 
    13911392         of this field is strictly to inform the recipient of valid methods associated with the resource. An Allow header field <em class="bcp14">MUST</em> be present in a 405 (Method Not Allowed) response. 
    13921393      </p> 
     
    13961397</pre><p id="rfc.section.10.1.p.5">This field cannot prevent a client from trying other methods. However, the indications given by the Allow header field value <em class="bcp14">SHOULD</em> be followed. The actual set of allowed methods is defined by the origin server at the time of each request. 
    13971398      </p> 
    1398       <p id="rfc.section.10.1.p.6">The Allow header field <em class="bcp14">MAY</em> be provided with a PUT request to recommend the methods to be supported by the new or modified resource. The server is not 
    1399          required to support these methods and <em class="bcp14">SHOULD</em> include an Allow header in the response giving the actual supported methods. 
    1400       </p> 
    1401       <p id="rfc.section.10.1.p.7">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other 
     1399      <p id="rfc.section.10.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field even if it does not understand all the methods specified, since the user agent might have other 
    14021400         means of communicating with the origin server. 
    14031401      </p> 
     
    17161714         user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">9.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">9.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">9.3.8</a> ) 
    17171715      </p> 
    1718       <p id="rfc.section.A.2.p.3">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications 
     1716      <p id="rfc.section.A.2.p.3">Reclassify Allow header as response header, removing the option to specify it in a PUT request. (<a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;10.1</a>) 
     1717      </p> 
     1718      <p id="rfc.section.A.2.p.4">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications 
    17191719         as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;10.4</a>) 
    17201720      </p> 
    1721       <p id="rfc.section.A.2.p.4">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly 
     1721      <p id="rfc.section.A.2.p.5">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly 
    17221722         in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section&nbsp;10.8</a>) 
    17231723      </p> 
     
    17721772      <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-02 
    17731773      </h2> 
     1774      <p id="rfc.section.B.4.p.1">Closed issues: </p> 
     1775      <ul> 
     1776         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header" 
     1777         </li> 
     1778      </ul> 
    17741779      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 
    17751780      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the 
     
    18581863            </li> 
    18591864            <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> 
    1860                   <li class="indline1">Allow header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.allow.1">3</a>, <a class="iref" href="#rfc.iref.a.1"><b>10.1</b></a></li> 
     1865                  <li class="indline1">Allow header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.allow.1">3</a>, <a class="iref" href="#rfc.xref.header.allow.2">6</a>, <a class="iref" href="#rfc.iref.a.1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.header.allow.3">A.2</a></li> 
    18611866               </ul> 
    18621867            </li> 
     
    19091914                  <li class="indline1">Headers&nbsp;&nbsp; 
    19101915                     <ul class="ind"> 
    1911                         <li class="indline1">Allow&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.allow.1">3</a>, <a class="iref" href="#rfc.iref.h.2"><b>10.1</b></a></li> 
     1916                        <li class="indline1">Allow&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.allow.1">3</a>, <a class="iref" href="#rfc.xref.header.allow.2">6</a>, <a class="iref" href="#rfc.iref.h.2"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.header.allow.3">A.2</a></li> 
    19121917                        <li class="indline1">Expect&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.expect.1">4</a>, <a class="iref" href="#rfc.xref.header.expect.2">9.4.18</a>, <a class="iref" href="#rfc.iref.h.3"><b>10.2</b></a></li> 
    19131918                        <li class="indline1">From&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.from.1">4</a>, <a class="iref" href="#rfc.iref.h.4"><b>10.3</b></a></li> 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r229 r232  
    555555  <x:ref>response-header</x:ref> = <x:ref>Accept-Ranges</x:ref>           ; &header-accept-ranges; 
    556556                  | <x:ref>Age</x:ref>                     ; &header-age; 
     557                  | <x:ref>Allow</x:ref>                   ; <xref target="header.allow"/> 
    557558                  | <x:ref>ETag</x:ref>                    ; &header-etag; 
    558559                  | <x:ref>Location</x:ref>                ; <xref target="header.location"/> 
     
    17331734  <x:anchor-alias value="Allow"/> 
    17341735<t> 
    1735       The Allow entity-header field lists the set of methods supported 
     1736      The Allow response-header field lists the set of methods supported 
    17361737      by the resource identified by the Request-URI. The purpose of this 
    17371738      field is strictly to inform the recipient of valid methods 
     
    17531754      &SHOULD; be followed. The actual set of allowed methods is defined 
    17541755      by the origin server at the time of each request. 
    1755 </t> 
    1756 <t> 
    1757       The Allow header field &MAY; be provided with a PUT request to 
    1758       recommend the methods to be supported by the new or modified 
    1759       resource. The server is not required to support these methods and 
    1760       &SHOULD; include an Allow header in the response giving the actual 
    1761       supported methods. 
    17621756</t> 
    17631757<t> 
     
    26492643  <xref format="counter" target="status.302"/> and 
    26502644  <xref format="counter" target="status.307"/> ) 
     2645</t> 
     2646<t> 
     2647  Reclassify Allow header as response header, removing the option to 
     2648  specify it in a PUT request. 
     2649  (<xref target="header.allow"/>) 
    26512650</t> 
    26522651<t> 
     
    27592758<section title="Since draft-ietf-httpbis-p2-semantics-02"> 
    27602759<t> 
     2760  Closed issues: 
     2761  <list style="symbols">  
     2762    <t> 
     2763      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105"/>: 
     2764      "Classification for Allow header" 
     2765    </t> 
     2766  </list> 
    27612767</t> 
    27622768</section> 
  • draft-ietf-httpbis/latest/p3-payload.html

    r230 r232  
    445445         <tr> 
    446446            <td class="header left"></td> 
    447             <td class="header right">March 8, 2008</td> 
     447            <td class="header right">March 11, 2008</td> 
    448448         </tr> 
    449449      </table> 
     
    601601  <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; 
    602602  <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; 
    603 </pre><div id="rfc.figure.u.4"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Allow</a>          = &lt;Allow, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>&gt; 
    604 </pre><div id="rfc.figure.u.5"></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; 
    605 </pre><div id="rfc.figure.u.6"></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; 
    606 </pre><div id="rfc.figure.u.7"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Expires</a>        = &lt;Expires, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 16.3</a>&gt; 
     603</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; 
     604</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; 
     605</pre><div id="rfc.figure.u.6"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Expires</a>        = &lt;Expires, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 16.3</a>&gt; 
    607606</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> 
    608607      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="character.sets" href="#character.sets">Character Sets</a></h2> 
     
    626625         </p> 
    627626      </div> 
    628       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#notation" class="smpl">token</a> 
     627      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#notation" class="smpl">token</a> 
    629628</pre><p id="rfc.section.3.1.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA 
    630629         Character Set registry <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry. 
     
    649648         decoded by the recipient. 
    650649      </p> 
    651       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#notation" class="smpl">token</a> 
     650      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#notation" class="smpl">token</a> 
    652651</pre><p id="rfc.section.3.2.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;6.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;6.5</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding 
    653652         mechanism will be required to remove the encoding. 
     
    693692      <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. 
    694693      </p> 
    695       <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <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> ) 
     694      <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> ) 
    696695  <a href="#media.types" class="smpl">type</a>           = <a href="#notation" class="smpl">token</a> 
    697696  <a href="#media.types" class="smpl">subtype</a>        = <a href="#notation" class="smpl">token</a> 
     
    700699         </p> 
    701700      </div> 
    702       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  <a href="#rule.parameter" class="smpl">parameter</a>               = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a> 
     701      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  <a href="#rule.parameter" class="smpl">parameter</a>               = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a> 
    703702  <a href="#rule.parameter" class="smpl">attribute</a>               = <a href="#notation" class="smpl">token</a> 
    704703  <a href="#rule.parameter" class="smpl">value</a>                   = <a href="#notation" class="smpl">token</a> | <a href="#notation" class="smpl">quoted-string</a> 
     
    753752         a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. 
    754753      </p> 
    755       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#quality.values" class="smpl">qvalue</a>         = ( "0" [ "." 0*3<a href="#notation" class="smpl">DIGIT</a> ] ) 
     754      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#quality.values" class="smpl">qvalue</a>         = ( "0" [ "." 0*3<a href="#notation" class="smpl">DIGIT</a> ] ) 
    756755                 | ( "1" [ "." 0*3("0") ] ) 
    757756</pre><p id="rfc.section.3.4.p.3">"Quality values" is a misnomer, since these values merely represent relative degradation in desired quality.</p> 
     
    763762      <p id="rfc.section.3.5.p.2">The syntax and registry of HTTP language tags is the same as that defined by <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags: 
    764763      </p> 
    765       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span>  <a href="#language.tags" class="smpl">language-tag</a>  = <a href="#language.tags" class="smpl">primary-tag</a> *( "-" <a href="#language.tags" class="smpl">subtag</a> ) 
     764      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span>  <a href="#language.tags" class="smpl">language-tag</a>  = <a href="#language.tags" class="smpl">primary-tag</a> *( "-" <a href="#language.tags" class="smpl">subtag</a> ) 
    766765  <a href="#language.tags" class="smpl">primary-tag</a>   = 1*8<a href="#notation" class="smpl">ALPHA</a> 
    767766  <a href="#language.tags" class="smpl">subtag</a>        = 1*8<a href="#notation" class="smpl">ALPHA</a> 
     
    769768         by the IANA. Example tags include: 
    770769      </p> 
    771       <div id="rfc.figure.u.14"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin 
     770      <div id="rfc.figure.u.13"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin 
    772771</pre><p id="rfc.section.3.5.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country 
    773772         code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered 
     
    785784         by the request. 
    786785      </p> 
    787       <div id="rfc.figure.u.15"></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="#abnf.dependencies" class="smpl">Allow</a>                    ; <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a> 
    788                  | <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> 
     786      <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> 
    789787                 | <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> 
    790788                 | <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> 
     
    803801      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="entity.body" href="#entity.body">Entity Body</a></h2> 
    804802      <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> 
    805       <div id="rfc.figure.u.16"></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> 
     803      <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> 
    806804</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 
    807805         safe and proper transfer of the message. 
     
    811809         and Content-Encoding. These define a two-layer, ordered encoding model: 
    812810      </p> 
    813       <div id="rfc.figure.u.17"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) ) 
     811      <div id="rfc.figure.u.16"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) ) 
    814812</pre><p id="rfc.section.4.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content 
    815813         codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There 
     
    866864      </ol> 
    867865      <p id="rfc.section.5.1.p.4">HTTP/1.1 includes the following request-header fields for enabling server-driven negotiation through description of user agent 
    868          capabilities and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;6.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;6.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;6.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;6.4</a>), and User-Agent (<a href="p2-semantics.html#header.user-agent" title="User-Agent">Section 10.9</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including information outside the request-header fields or within extension 
     866         capabilities and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section&nbsp;6.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section&nbsp;6.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section&nbsp;6.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;6.4</a>), and User-Agent (<a href="p2-semantics.html#header.user-agent" title="User-Agent">Section 10.9</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including information outside the request-header fields or within extension 
    869867         header fields not defined by this specification. 
    870868      </p> 
     
    915913         for an in-line image. 
    916914      </p> 
    917       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  <a href="#header.accept" class="smpl">Accept</a>         = "Accept" ":" 
     915      <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" ":" 
    918916                   #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] ) 
    919917   
     
    939937      </dl> 
    940938      <p id="rfc.section.6.1.p.5">The example</p> 
    941       <div id="rfc.figure.u.19"></div><pre class="text">    Accept: audio/*; q=0.2, audio/basic 
     939      <div id="rfc.figure.u.18"></div><pre class="text">    Accept: audio/*; q=0.2, audio/basic 
    942940</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 
    943941         quality." 
     
    948946      </p> 
    949947      <p id="rfc.section.6.1.p.9">A more elaborate example is</p> 
    950       <div id="rfc.figure.u.20"></div><pre class="text">    Accept: text/plain; q=0.5, text/html, 
     948      <div id="rfc.figure.u.19"></div><pre class="text">    Accept: text/plain; q=0.5, text/html, 
    951949            text/x-dvi; q=0.8, text/x-c 
    952950</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 
     
    956954         to a given type, the most specific reference has precedence. For example, 
    957955      </p> 
    958       <div id="rfc.figure.u.21"></div><pre class="text">    Accept: text/*, text/html, text/html;level=1, */* 
     956      <div id="rfc.figure.u.20"></div><pre class="text">    Accept: text/*, text/html, text/html;level=1, */* 
    959957</pre><p id="rfc.section.6.1.p.14">have the following precedence:</p> 
    960       <div id="rfc.figure.u.22"></div><pre class="text">    1) text/html;level=1 
     958      <div id="rfc.figure.u.21"></div><pre class="text">    1) text/html;level=1 
    961959    2) text/html 
    962960    3) text/* 
     
    965963         which matches that type. For example, 
    966964      </p> 
    967       <div id="rfc.figure.u.23"></div><pre class="text">    Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, 
     965      <div id="rfc.figure.u.22"></div><pre class="text">    Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, 
    968966            text/html;level=2;q=0.4, */*;q=0.5 
    969967</pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p> 
    970       <div id="rfc.figure.u.24"></div><pre class="text">    text/html;level=1         = 1 
     968      <div id="rfc.figure.u.23"></div><pre class="text">    text/html;level=1         = 1 
    971969    text/html                 = 0.7 
    972970    text/plain                = 0.3 
     
    984982         to a server which is capable of representing documents in those character sets. 
    985983      </p> 
    986       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.21"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset" ":" 
     984      <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" ":" 
    987985          1#( ( <a href="#rule.charset" class="smpl">charset</a> | "*" ) [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] ) 
    988986</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 
    989987         example is 
    990988      </p> 
    991       <div id="rfc.figure.u.26"></div><pre class="text">   Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 
     989      <div id="rfc.figure.u.25"></div><pre class="text">   Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 
    992990</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 
    993991         not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets 
     
    10031001      <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. 
    10041002      </p> 
    1005       <div id="rfc.figure.u.27"></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" ":" 
     1003      <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" ":" 
    10061004                     #( <a href="#header.accept-encoding" class="smpl">codings</a> [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] ) 
    10071005  <a href="#header.accept-encoding" class="smpl">codings</a>          = ( <a href="#content.codings" class="smpl">content-coding</a> | "*" ) 
    10081006</pre><p id="rfc.section.6.3.p.3">Examples of its use are:</p> 
    1009       <div id="rfc.figure.u.28"></div><pre class="text">    Accept-Encoding: compress, gzip 
     1007      <div id="rfc.figure.u.27"></div><pre class="text">    Accept-Encoding: compress, gzip 
    10101008    Accept-Encoding: 
    10111009    Accept-Encoding: * 
     
    10491047         as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.5</a>. 
    10501048      </p> 
    1051       <div id="rfc.figure.u.29"></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" ":" 
     1049      <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" ":" 
    10521050                    1#( <a href="#header.accept-language" class="smpl">language-range</a> [ ";" "q" "=" <a href="#quality.values" class="smpl">qvalue</a> ] ) 
    10531051  <a href="#header.accept-language" class="smpl">language-range</a>  = ( ( 1*8<a href="#notation" class="smpl">ALPHA</a> *( "-" 1*8<a href="#notation" class="smpl">ALPHA</a> ) ) | "*" ) 
     
    10551053         that range. The quality value defaults to "q=1". For example, 
    10561054      </p> 
    1057       <div id="rfc.figure.u.30"></div><pre class="text">    Accept-Language: da, en-gb;q=0.8, en;q=0.7 
     1055      <div id="rfc.figure.u.29"></div><pre class="text">    Accept-Language: da, en-gb;q=0.8, en;q=0.7 
    10581056</pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English." A language-range matches a language-tag 
    10591057         if it exactly equals the tag, or if it exactly equals a prefix of the tag such that the first tag character following the 
     
    10931091         without losing the identity of its underlying media type. 
    10941092      </p> 
    1095       <div id="rfc.figure.u.31"></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> 
     1093      <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> 
    10961094</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 
    10971095      </p> 
    1098       <div id="rfc.figure.u.32"></div><pre class="text">    Content-Encoding: gzip 
     1096      <div id="rfc.figure.u.31"></div><pre class="text">    Content-Encoding: gzip 
    10991097</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 
    11001098         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 
     
    11131111         Note that this might not be equivalent to all the languages used within the entity-body. 
    11141112      </p> 
    1115       <div id="rfc.figure.u.33"></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> 
     1113      <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> 
    11161114</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 
    11171115         own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is 
    11181116      </p> 
    1119       <div id="rfc.figure.u.34"></div><pre class="text">    Content-Language: da 
     1117      <div id="rfc.figure.u.33"></div><pre class="text">    Content-Language: da 
    11201118</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 
    11211119         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language 
     
    11251123         simultaneously in the original Maori and English versions, would call for 
    11261124      </p> 
    1127       <div id="rfc.figure.u.35"></div><pre class="text">    Content-Language: mi, en 
     1125      <div id="rfc.figure.u.34"></div><pre class="text">    Content-Language: mi, en 
    11281126</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 
    11291127         audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended 
     
    11401138         accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned. 
    11411139      </p> 
    1142       <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.28"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = "Content-Location" ":" 
     1140      <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" ":" 
    11431141                    ( <a href="#abnf.dependencies" class="smpl">absoluteURI</a> | <a href="#abnf.dependencies" class="smpl">relativeURI</a> ) 
    11441142</pre><p id="rfc.section.6.7.p.3">The value of Content-Location also defines the base URI for the entity.</p> 
     
    11591157         attacks.) 
    11601158      </p> 
    1161       <div id="rfc.figure.u.37"></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> 
     1159      <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> 
    11621160  <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; 
    11631161</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 
     
    11961194         the HEAD method, the media type that would have been sent had the request been a GET. 
    11971195      </p> 
    1198       <div id="rfc.figure.u.38"></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> 
     1196      <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> 
    11991197</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 
    12001198      </p> 
    1201       <div id="rfc.figure.u.39"></div><pre class="text">    Content-Type: text/html; charset=ISO-8859-4 
     1199      <div id="rfc.figure.u.38"></div><pre class="text">    Content-Type: text/html; charset=ISO-8859-4 
    12021200</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>. 
    12031201      </p> 
     
    14151413         environments. 
    14161414      </p> 
    1417       <div id="rfc.figure.u.40"></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> 
     1415      <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> 
    14181416</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 
    14191417         document and not the MIME specification. 
     
    14691467         in <a href="#RFC1806" id="rfc.xref.RFC1806.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header">[RFC1806]</cite></a>. 
    14701468      </p> 
    1471       <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span>  <a href="#content-disposition" class="smpl">content-disposition</a> = "Content-Disposition" ":" 
     1469      <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" ":" 
    14721470                        <a href="#content-disposition" class="smpl">disposition-type</a> *( ";" <a href="#content-disposition" class="smpl">disposition-parm</a> ) 
    14731471  <a href="#content-disposition" class="smpl">disposition-type</a> = "attachment" | <a href="#content-disposition" class="smpl">disp-extension-token</a> 
     
    14771475  <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> ) 
    14781476</pre><p id="rfc.section.B.1.p.3">An example is</p> 
    1479       <div id="rfc.figure.u.42"></div><pre class="text">     Content-Disposition: attachment; filename="fname.ext" 
     1477      <div id="rfc.figure.u.41"></div><pre class="text">     Content-Disposition: attachment; filename="fname.ext" 
    14801478</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 
    14811479         to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only. 
     
    15501548      <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a>&nbsp;Since draft-ietf-httpbis-p3-payload-02 
    15511549      </h2> 
     1550      <p id="rfc.section.D.4.p.1">Closed issues: </p> 
     1551      <ul> 
     1552         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105</a>&gt;: "Classification for Allow header" 
     1553         </li> 
     1554      </ul> 
    15521555      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 
    15531556      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the 
     
    16941697                     </ul> 
    16951698                  </li> 
    1696                   <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2</a>, <a class="iref" href="#rfc.xref.Part2.2">4.1</a>, <a class="iref" href="#rfc.xref.Part2.3">5.1</a>, <a class="iref" href="#Part2"><b>10.1</b></a><ul class="ind"> 
    1697                         <li class="indline1"><em>Section 10.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2</a>, <a class="iref" href="#rfc.xref.Part2.2">4.1</a></li> 
    1698                         <li class="indline1"><em>Section 10.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.3">5.1</a></li> 
     1699                  <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">5.1</a>, <a class="iref" href="#Part2"><b>10.1</b></a><ul class="ind"> 
     1700                        <li class="indline1"><em>Section 10.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">5.1</a></li> 
    16991701                     </ul> 
    17001702                  </li> 
  • draft-ietf-httpbis/latest/p3-payload.xml

    r229 r232  
    1919  <!ENTITY caching-neg-resp         "<xref target='Part6' x:rel='#caching.negotiated.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    2020  <!ENTITY header-transfer-encoding "<xref target='Part1' x:rel='#header.transfer-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    21   <!ENTITY header-allow             "<xref target='Part2' x:rel='#header.allow' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    2221  <!ENTITY header-content-length    "<xref target='Part1' x:rel='#header.content-length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
    2322  <!ENTITY header-content-range     "<xref target='Part5' x:rel='#header.content-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 
     
    293292  <x:ref>message-header</x:ref> = &lt;message-header, defined in &message-headers;&gt; 
    294293</artwork></figure> 
    295 <figure><!--Part2--><artwork type="abnf2616"> 
    296   <x:ref>Allow</x:ref>          = &lt;Allow, defined in &header-allow;&gt; 
    297 </artwork></figure> 
    298294<figure><!--Part4--><artwork type="abnf2616"> 
    299295  <x:ref>Last-Modified</x:ref>  = &lt;Last-Modified, defined in &header-last-modified;&gt; 
     
    669665</t> 
    670666<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="entity-header"/><iref primary="true" item="Grammar" subitem="extension-header"/> 
    671   <x:ref>entity-header</x:ref>  = <x:ref>Allow</x:ref>                    ; &header-allow; 
    672                  | <x:ref>Content-Encoding</x:ref>         ; <xref target="header.content-encoding"/> 
     667  <x:ref>entity-header</x:ref>  = <x:ref>Content-Encoding</x:ref>         ; <xref target="header.content-encoding"/> 
    673668                 | <x:ref>Content-Language</x:ref>         ; <xref target="header.content-language"/> 
    674669                 | <x:ref>Content-Length</x:ref>           ; &header-content-length; 
     
    25032498<section title="Since draft-ietf-httpbis-p3-payload-02"> 
    25042499<t> 
     2500  Closed issues: 
     2501  <list style="symbols">  
     2502    <t> 
     2503      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/105"/>: 
     2504      "Classification for Allow header" 
     2505    </t> 
     2506  </list> 
    25052507</t> 
    25062508</section> 
Note: See TracChangeset for help on using the changeset viewer.