- 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>
Received on Monday, 7 July 2008 13:26:41 UTC
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. Yes. > Or am I missing something subtle here? No. 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. Regards Henrik
Received on Monday, 7 July 2008 13:26:41 UTC