28/10/10 07:21:37 (12 years ago)

clarify proxy requirements wrt not-understood methods (see #226)

1 edited


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

    r1066 r1068  
    403403      <meta name="dct.creator" content="Reschke, J. F.">
    404404      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    405       <meta name="dct.issued" scheme="ISO8601" content="2010-10-27">
     405      <meta name="dct.issued" scheme="ISO8601" content="2010-10-28">
    406406      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    407407      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields.">
    434434            </tr>
    435435            <tr>
    436                <td class="left">Expires: April 30, 2011</td>
     436               <td class="left">Expires: May 1, 2011</td>
    437437               <td class="right">HP</td>
    438438            </tr>
    487487            <tr>
    488488               <td class="left"></td>
    489                <td class="right">October 27, 2010</td>
     489               <td class="right">October 28, 2010</td>
    490490            </tr>
    491491         </tbody>
    514514         in progress”.
    515515      </p>
    516       <p>This Internet-Draft will expire on April 30, 2011.</p>
     516      <p>This Internet-Draft will expire on May 1, 2011.</p>
    517517      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    518518      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    16021602      <div id="rfc.figure.u.15"></div><pre class="text">  Allow: GET, HEAD, PUT
    16031603</pre><p id="rfc.section.9.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    1604       <p id="rfc.section.9.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
    1605          means of communicating with the origin server.
     1604      <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field -- it does not need to understand all the methods specified in order to handle them according
     1605         to the generic message handling rules.
    16061606      </p>
    16071607      <div id="rfc.iref.e.1"></div>
    26742674      <ul>
    26752675         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/88">http://tools.ietf.org/wg/httpbis/trac/ticket/88</a>&gt;: "205 Bodies"
     2676         </li>
     2677         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/226">http://tools.ietf.org/wg/httpbis/trac/ticket/226</a>&gt;: "proxies not supporting certain methods"
    26762678         </li>
    26772679         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/239">http://tools.ietf.org/wg/httpbis/trac/ticket/239</a>&gt;: "Migrate CONNECT from RFC2817 to p2"
Note: See TracChangeset for help on using the changeset viewer.