On Tue, Dec 14, 2004 at 10:19:48AM -0500, Justin Miller wrote: > I suppose I might try setting up a web server/proxy on one of my home > machines, and trying it that way. Then I'd have direct access to the > proxy itself... something I could control.
This is how CONNECT works: - Stunnel (in your case) makes a TCP connection to the proxy. - Stunnel says "CONNECT ...". - The proxy makes a TCP connection to the target specified in "CONNECT ..." Assume this is successful. - The proxy replies to Stunnel's "CONNECT ..." with a 2xx status code. (Just like in regular HTTP.) From this point onwards, the proxy simply copies data back and forth between its two TCP connections. - Upon seeing the 2xx, Stunnel starts talking SSL over its TCP connection. > > I suppose you can "telnet your-proxy port-whatever" then type "CONNECT ..." > > by hand to see if your proxy supports that protocol. So I think your first order of business should be to determine if your proxy supports CONNECT properly. The proxy you set up at home might, but the one you have to use might not. HTH. -- Ng Pheng Siong <[EMAIL PROTECTED]> http://sandbox.rulemaker.net/ngps -+- M2Crypto, ZServerSSL for Zope, Blog http://www.sqlcrypt.com -+- Database Engine with Transparent AES Encryption ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
