Ignore:
Timestamp:
Apr 9, 2008, 11:16:47 PM (12 years ago)
Author:
julian.reschke@…
Message:

Resolve #24: relax requirements for contents of Allow header (closes #24).

File:
1 edited

Legend:

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

    r237 r240  
    447447         <tr>
    448448            <td class="header left"></td>
    449             <td class="header right">April 3, 2008</td>
     449            <td class="header right">April 9, 2008</td>
    450450         </tr>
    451451      </table>
     
    13831383      <div id="rfc.iref.h.2"></div>
    13841384      <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>
    1385       <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
    1386          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.
     1385      <p id="rfc.section.10.1.p.1">The Allow response-header field lists the set of methods advertised as supported by the resource identified by the Request-URI.
     1386         The purpose of this field is strictly to inform the recipient of valid methods associated with the resource. An Allow header
     1387         field <em class="bcp14">MUST</em> be present in a 405 (Method Not Allowed) response.
    13871388      </p>
    13881389      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.allow" class="smpl">Allow</a>   = "Allow" ":" #<a href="#method" class="smpl">Method</a>
    13891390</pre><p id="rfc.section.10.1.p.3">Example of use:</p>
    13901391      <div id="rfc.figure.u.14"></div><pre class="text">       Allow: GET, HEAD, PUT
    1391 </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.
    1392       </p>
     1392</pre><p id="rfc.section.10.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    13931393      <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
    13941394         means of communicating with the origin server.
     
    17121712         was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section&nbsp;9.3.6</a>)
    17131713      </p>
    1714       <p id="rfc.section.A.2.p.4">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>)
     1714      <p id="rfc.section.A.2.p.4">Reclassify Allow header as response header, removing the option to specify it in a PUT request. Relax the server requirement
     1715         on the contents of the Allow header and remove requirement on clients to always trust the header value. (<a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section&nbsp;10.1</a>)
    17151716      </p>
    17161717      <p id="rfc.section.A.2.p.5">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications
     
    17721773      <p id="rfc.section.B.4.p.1">Closed issues: </p>
    17731774      <ul>
     1775         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/24">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/24</a>&gt;: "Requiring Allow in 405 responses"
     1776         </li>
    17741777         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61</a>&gt;: "Redirection vs. Location"
    17751778         </li>
Note: See TracChangeset for help on using the changeset viewer.