> Hi Samuli, > > (I'd prefer to be referred to as JJK in minutes ;-) ) > > I'll try to remember that next time, JJK ;)
> >> Discussed potential problems with disfunctional proxy servers: >> >> <http://sourceforge.net/tracker/?func=detail&atid=454722&aid=1840041&group_id=48978> >> >> RFC2817 clearly states that proxies need to use this syntax: >> >> CONNECT host:port/ >> >> >> > that is not entirely correct: > > 5.2 Requesting a Tunnel with CONNECT > > A CONNECT method requests that a proxy establish a tunnel connection > on its behalf. The Request-URI portion of the Request-Line is always > an 'authority' as defined by URI Generic Syntax [2], which is to say > the host name and port number destination of the requested connection > separated by a colon: > > CONNECT server.example.com:80 HTTP/1.1 > Host: server.example.com:80 > > Other HTTP mechanisms can be used normally with the CONNECT method -- > except end-to-end protocol Upgrade requests, of course, since the > tunnel must be established first. > > > the "other HTTP mechanisms" seems to be implemented by some (reverse?) > proxy servers ; there are numerous hits in google if you look closely. > Still don't know how relevant they are, however > I sent mail to the bug author - so far no response. -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
