The error messages I posted in my first message were from the 'openssl s_client' command.
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. On Tue, 14 Dec 2004 10:22:52 +0800, Ng Pheng Siong <[EMAIL PROTECTED]> wrote: > On Mon, Dec 13, 2004 at 08:40:25AM -0500, Justin Miller wrote: > > Could one get the error messages I displayed if the proxy I'm trying > > to use doesn't support SSL (the connect method)? > > I suppose you can "telnet your-proxy port-whatever" then type "CONNECT ..." > by hand to see if your proxy supports that protocol. > > Also, you can use "openssl s_client" to talk to your proxy as if it is an > SSL end point and see if it is giving you the same error you're seeing. > > 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] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
