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

Changeset 240


Ignore:
Timestamp:
2008-04-09 23:16:47 (6 years ago)
Author:
julian.reschke@gmx.de
Message:

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

Location:
draft-ietf-httpbis/latest
Files:
2 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> 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r237 r240  
    17271727  <x:anchor-alias value="Allow"/> 
    17281728<t> 
    1729       The Allow response-header field lists the set of methods supported 
    1730       by the resource identified by the Request-URI. The purpose of this 
    1731       field is strictly to inform the recipient of valid methods 
     1729      The Allow response-header field lists the set of methods advertised as 
     1730      supported by the resource identified by the Request-URI. The purpose of 
     1731      this field is strictly to inform the recipient of valid methods 
    17321732      associated with the resource. An Allow header field &MUST; be 
    17331733      present in a 405 (Method Not Allowed) response. 
     
    17431743</artwork></figure> 
    17441744<t> 
    1745       This field cannot prevent a client from trying other methods. 
    1746       However, the indications given by the Allow header field value 
    1747       &SHOULD; be followed. The actual set of allowed methods is defined 
     1745      The actual set of allowed methods is defined 
    17481746      by the origin server at the time of each request. 
    17491747</t> 
     
    26472645  Reclassify Allow header as response header, removing the option to 
    26482646  specify it in a PUT request. 
     2647  Relax the server requirement on the contents of the Allow header and 
     2648  remove requirement on clients to always trust the header value. 
    26492649  (<xref target="header.allow"/>) 
    26502650</t> 
     
    27612761  <list style="symbols">  
    27622762    <t> 
     2763      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/24"/>: 
     2764      "Requiring Allow in 405 responses" 
     2765    </t> 
     2766    <t> 
    27632767      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61"/>: 
    27642768      "Redirection vs. Location" 
Note: See TracChangeset for help on using the changeset viewer.