Changeset 240 for draft-ietf-httpbis/latest/p2-semantics.html

Timestamp:

10/04/08 06:16:47 (15 years ago)

Author:

julian.reschke@…

Message:

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

File:

• draft-ietf-httpbis/latest/p2-semantics.html (modified) (4 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -447 +447 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">April 3, 2008</td>
+            <td class="header right">April 9, 2008</td>
          </tr>
       </table>
@@ -1383 +1383 @@
       <div id="rfc.iref.h.2"></div>
       <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>
-      <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
-         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.
+      <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.
+         The purpose 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.
       </p>
       <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>
 </pre><p id="rfc.section.10.1.p.3">Example of use:</p>
       <div id="rfc.figure.u.14"></div><pre class="text">       Allow: GET, HEAD, PUT
-</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.
-      </p>
+</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>
       <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
          means of communicating with the origin server.
@@ -1712 +1712 @@
          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>)
       </p>
-      <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>)
+      <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
+         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>)
       </p>
       <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
@@ -1772 +1773 @@
       <p id="rfc.section.B.4.p.1">Closed issues: </p>
       <ul>
+         <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"
+         </li>
          <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"
          </li>