Ignore:
Timestamp:
Mar 11, 2008, 1:43:48 AM (12 years ago)
Author:
julian.reschke@…
Message:

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

File:
1 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>
Note: See TracChangeset for help on using the changeset viewer.