Adding note about CONNECT for #230.

httpwg · Aug 30, 2013 · c68a11f · c68a11f
1 parent 58cbeb8
commit c68a11f
Showing 1 changed file with 20 additions and 0 deletions.
diff --git a/draft-ietf-httpbis-http2.xml b/draft-ietf-httpbis-http2.xml
@@ -2228,6 +2228,13 @@ HTTP2-Settings    = token68
           Connection, Host, Keep-Alive, Proxy-Connection, TE, Transfer-Encoding, and Upgrade.  A
           server MUST treat the presence of any of these header fields as a <xref
           target="StreamErrorHandler">stream error</xref> of type <x:ref>PROTOCOL_ERROR</x:ref>.
+          <list style="hanging">
+            <t hangText="Note:">
+              HTTP/2.0 purposefully does not support upgrade from HTTP/2.0 to another protocol.  The
+              handshake methods described in <xref target="starting"/> are sufficient to negotiate
+              the use of alternative protocols.
+            </t>
+          </list>
         </t>
 
         <section anchor="HttpRequest" title="Request Header Fields">
@@ -2450,8 +2457,21 @@ HTTP2-Settings    = token68
             push a response for <spanx style="verb">www.example.org</spanx>.
           </t>        
         </section>
+
       </section>
 
+      <section title="The CONNECT Method">
+        <t>
+          The HTTP pseudo-method <xref target="RFC2817">CONNECT</xref> is used to convert an
+          HTTP/1.1 connection into a tunnel to a remote host.  CONNECT is primarily used with HTTP
+          proxies to established a TLS session with a server for the purposes of interacting with
+          <spanx style="verb">https</spanx> resources.
+        </t>
+        <t>
+          HTTP/2.0 does not support the CONNECT method.  Servers and intermediaries that receive a
+          CONNECT request MUST reject the request with a 501 (Not Implemented) error.
+        </t>
+      </section>
     </section>
 
     <section anchor="HttpExtra" title="Additional HTTP Requirements/Considerations">