W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2008


From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Mon, 07 Jul 2008 15:25:57 +0200
To: Julian Reschke <julian.reschke@gmx.de>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1215437157.20418.84.camel@henriknordstrom.net>
On mån, 2008-07-07 at 13:18 +0200, Julian Reschke wrote:
> Hi,
> it seems to me that in Part2, Section 8.9:
> "8.9 CONNECT
> This specification reserves the method name CONNECT for use with a proxy 
> that can dynamically switch to being a tunnel (e.g. SSL tunneling 
> [Luo1998])." -- 
> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-latest.html#CONNECT>
> we really should refer to RFC2817.


> Or am I missing something subtle here?


RFC2817 didn't exist at the time RFC2068 or RFC2616 was written. At the
time CONNECT was only specified by the Netscape informal specifications.

And the world still plays by the Netscape specifications, not RFC2817.
But the differences regarding CONNECT is only in intent of the method,
not functional specification so it doesn't really matter.


Received on Monday, 7 July 2008 13:26:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:13:36 UTC