Ignore:
Timestamp:
Oct 27, 2010, 4:46:12 AM (9 years ago)
Author:
julian.reschke@…
Message:

Note that we now define CONNECT (see #239)

File:
1 edited

Legend:

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

    r1065 r1066  
    23382338      <p id="rfc.section.A.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;7.5</a>)
    23392339      </p>
    2340       <p id="rfc.section.A.p.3">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
     2340      <p id="rfc.section.A.p.3">Take over definition of CONNECT method from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.3" title="CONNECT">Section&nbsp;7.9</a>)
     2341      </p>
     2342      <p id="rfc.section.A.p.4">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
    23412343         user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">8.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">8.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.4" title="307 Temporary Redirect">8.3.8</a>)
    23422344      </p>
    2343       <p id="rfc.section.A.p.4">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource
     2345      <p id="rfc.section.A.p.5">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource
    23442346         must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
    23452347         was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;8.3.6</a>)
    23462348      </p>
    2347       <p id="rfc.section.A.p.5">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement
     2349      <p id="rfc.section.A.p.6">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement
    23482350         on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;9.1</a>)
    23492351      </p>
    2350       <p id="rfc.section.A.p.6">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
     2352      <p id="rfc.section.A.p.7">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
    23512353         symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate.
    23522354         (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.4</a>)
    23532355      </p>
    2354       <p id="rfc.section.A.p.7">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.6</a>)
    2355       </p>
    2356       <p id="rfc.section.A.p.8">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated
     2356      <p id="rfc.section.A.p.8">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.6</a>)
     2357      </p>
     2358      <p id="rfc.section.A.p.9">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated
    23572359         correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.37"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;9.8</a>)
    23582360      </p>
     
    27422744            </li>
    27432745            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    2744                   <li class="indline1">CONNECT method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.CONNECT.1">2</a>, <a class="iref" href="#rfc.iref.c.1"><b>7.9</b></a>, <a class="iref" href="#rfc.xref.CONNECT.2">10.1</a></li>
     2746                  <li class="indline1">CONNECT method&nbsp;&nbsp;<a class="iref" href="#rfc.xref.CONNECT.1">2</a>, <a class="iref" href="#rfc.iref.c.1"><b>7.9</b></a>, <a class="iref" href="#rfc.xref.CONNECT.2">10.1</a>, <a class="iref" href="#rfc.xref.CONNECT.3">A</a></li>
    27452747               </ul>
    27462748            </li>
     
    28232825                  <li class="indline1">Methods&nbsp;&nbsp;
    28242826                     <ul class="ind">
    2825                         <li class="indline1">CONNECT&nbsp;&nbsp;<a class="iref" href="#rfc.xref.CONNECT.1">2</a>, <a class="iref" href="#rfc.iref.m.8"><b>7.9</b></a>, <a class="iref" href="#rfc.xref.CONNECT.2">10.1</a></li>
     2827                        <li class="indline1">CONNECT&nbsp;&nbsp;<a class="iref" href="#rfc.xref.CONNECT.1">2</a>, <a class="iref" href="#rfc.iref.m.8"><b>7.9</b></a>, <a class="iref" href="#rfc.xref.CONNECT.2">10.1</a>, <a class="iref" href="#rfc.xref.CONNECT.3">A</a></li>
    28262828                        <li class="indline1">DELETE&nbsp;&nbsp;<a class="iref" href="#rfc.xref.DELETE.1">2</a>, <a class="iref" href="#rfc.iref.m.6"><b>7.7</b></a>, <a class="iref" href="#rfc.xref.DELETE.2">10.1</a></li>
    28272829                        <li class="indline1">GET&nbsp;&nbsp;<a class="iref" href="#rfc.xref.GET.1">2</a>, <a class="iref" href="#rfc.iref.m.2"><b>7.3</b></a>, <a class="iref" href="#rfc.xref.GET.2">10.1</a></li>
     
    29272929                     </ul>
    29282930                  </li>
    2929                   <li class="indline1"><em>RFC2817</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">10.2</a>, <a class="iref" href="#RFC2817"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.2">A</a><ul class="ind">
     2931                  <li class="indline1"><em>RFC2817</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">10.2</a>, <a class="iref" href="#RFC2817"><b>13.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.2">A</a>, <a class="iref" href="#rfc.xref.RFC2817.3">A</a><ul class="ind">
    29302932                        <li class="indline1"><em>Section 7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">10.2</a>, <a class="iref" href="#rfc.xref.RFC2817.2">A</a></li>
    29312933                     </ul>
Note: See TracChangeset for help on using the changeset viewer.