Changeset 274


Ignore:
Timestamp:
Jul 7, 2008, 7:29:10 AM (11 years ago)
Author:
julian.reschke@…
Message:

Resolve #119: refer to RFC2817 for CONNECT method (closes #119).

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r272 r274  
    477477         <tr>
    478478            <td class="header left"></td>
    479             <td class="header right">July 6, 2008</td>
     479            <td class="header right">July 7, 2008</td>
    480480         </tr>
    481481      </table>
     
    10301030      <h2 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a>&nbsp;<a id="CONNECT" href="#CONNECT">CONNECT</a></h2>
    10311031      <p id="rfc.section.8.9.p.1">This specification reserves the method name CONNECT for use with a proxy that can dynamically switch to being a tunnel (e.g.
    1032          SSL tunneling <a href="#Luo1998" id="rfc.xref.Luo1998.1"><cite title="Tunneling TCP based protocols through Web proxy servers">[Luo1998]</cite></a>).
     1032         SSL tunneling <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>).
    10331033      </p>
    10341034      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="status.codes" href="#status.codes">Status Code Definitions</a></h1>
     
    16591659      </div>
    16601660      <h2 id="rfc.section.11.2"><a href="#rfc.section.11.2">11.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
    1661       <p id="rfc.section.11.2.p.1">The registration procedure for HTTP Status Codes -- previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> -- is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;5.1</a> of this document.
     1661      <p id="rfc.section.11.2.p.1">The registration procedure for HTTP Status Codes -- previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> -- is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;5.1</a> of this document.
    16621662      </p>
    16631663      <p id="rfc.section.11.2.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; should be updated with the registrations below:
     
    20942094      <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References
    20952095      </h2>
    2096       <table summary="Informative References">               
    2097          <tr>
    2098             <td class="reference"><b id="Luo1998">[Luo1998]</b></td>
    2099             <td class="top">Luotonen, A., “<a href="http://tools.ietf.org/html/draft-luotonen-web-proxy-tunneling-01">Tunneling TCP based protocols through Web proxy servers</a>”, Internet-Draft&nbsp;draft-luotonen-web-proxy-tunneling-01 (work in progress), August&nbsp;1998.
    2100             </td>
    2101          </tr>
     2096      <table summary="Informative References">             
    21022097         <tr>
    21032098            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
     
    21812176      </p>
    21822177      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    2183       <p id="rfc.section.A.2.p.1">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;5.1</a>)
     2178      <p id="rfc.section.A.2.p.1">This document takes over the Status Code Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;5.1</a>)
    21842179      </p>
    21852180      <p id="rfc.section.A.2.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;8.5</a>)
     
    22772272      </ul>
    22782273      <h2 id="rfc.section.B.5"><a href="#rfc.section.B.5">B.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p2-semantics-03</a></h2>
    2279       <p id="rfc.section.B.5.p.1">Ongoing work on Method Registry (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/72">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
     2274      <p id="rfc.section.B.5.p.1">Closed issues: </p>
     2275      <ul>
     2276         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/119">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/119</a>&gt;: "Description of CONNECT should refer to RFC2817"
     2277         </li>
     2278      </ul>
     2279      <p id="rfc.section.B.5.p.2">Ongoing work on Method Registry (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/72">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/72</a>&gt;):
    22802280      </p>
    22812281      <ul>
     
    24352435                  <li class="indline1">LINK method&nbsp;&nbsp;<a class="iref" href="#rfc.iref.l.2"><b>A.1</b></a></li>
    24362436                  <li class="indline1">Location header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.location.1">6</a>, <a class="iref" href="#rfc.xref.header.location.2">8.5</a>, <a class="iref" href="#rfc.iref.l.1"><b>10.4</b></a>, <a class="iref" href="#rfc.xref.header.location.3">11.3</a>, <a class="iref" href="#rfc.xref.header.location.4">A.2</a></li>
    2437                   <li class="indline1"><em>Luo1998</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Luo1998.1">8.9</a>, <a class="iref" href="#Luo1998"><b>14.2</b></a></li>
    24382437               </ul>
    24392438            </li>
     
    25272526                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>14.1</b></a></li>
    25282527                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li>
    2529                   <li class="indline1"><em>RFC2817</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">11.2</a>, <a class="iref" href="#RFC2817"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.2">A.2</a><ul class="ind">
    2530                         <li class="indline1"><em>Section 7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">11.2</a>, <a class="iref" href="#rfc.xref.RFC2817.2">A.2</a></li>
     2528                  <li class="indline1"><em>RFC2817</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">8.9</a>, <a class="iref" href="#rfc.xref.RFC2817.2">11.2</a>, <a class="iref" href="#RFC2817"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.3">A.2</a><ul class="ind">
     2529                        <li class="indline1"><em>Section 7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.2">11.2</a>, <a class="iref" href="#rfc.xref.RFC2817.3">A.2</a></li>
    25312530                     </ul>
    25322531                  </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r272 r274  
    975975   This specification reserves the method name CONNECT for use with a
    976976   proxy that can dynamically switch to being a tunnel (e.g. SSL
    977    tunneling <xref target="Luo1998"/>).
     977   tunneling <xref target="RFC2817"/>).
    978978</t>
    979979</section>
     
    29072907
    29082908<references title="Informative References">
    2909 
    2910 <reference anchor="Luo1998">
    2911   <front>
    2912     <title>Tunneling TCP based protocols through Web proxy servers</title>
    2913     <author initials="A." surname="Luotonen" fullname="A. Luotonen">
    2914       <organization/>
    2915     </author>
    2916     <date year="1998" month="August"/>
    2917   </front>
    2918   <seriesInfo name="Internet-Draft" value="draft-luotonen-web-proxy-tunneling-01"/>
    2919 </reference>
    29202909
    29212910<reference anchor="RFC1945">
     
    33183307<section title="Since draft-ietf-httpbis-p2-semantics-03" anchor="changes.since.03">
    33193308<t>
     3309  Closed issues:
     3310  <list style="symbols">
     3311    <t>
     3312      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/119"/>:
     3313      "Description of CONNECT should refer to RFC2817"
     3314    </t>
     3315  </list>
     3316</t>
     3317<t>
    33203318  Ongoing work on Method Registry (<eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/72"/>):
    33213319  <list style="symbols">
Note: See TracChangeset for help on using the changeset viewer.