Roger Studner wrote:
I was wondering if anyone has ever discovered how to "redo" the 3.1 SSL
example that went (very tersely) as follows:
Protocol easyhttps = new Protocol("https", new
EasySSLProtocolSocketFactory(), 443);
Protocol.registerProtocol("https", easyhttps);
I tried this:
// SchemeRegistry schemeRegistry = new SchemeRegistry();
// // http scheme
// schemeRegistry.register( new Scheme( "http",
PlainSocketFactory.getSocketFactory(), 80 ) );
// // https scheme
// schemeRegistry.register( new Scheme( "https", new
EasySSLProtocolSocketFactory(), 443 ) );
Try this:
httpclient.getConnectionManager().getSchemeRegistry().register(
new Scheme("https",
new EasySSLProtocolSocketFactory(), 443 ));
But that example failed to take note that you can't even use that
constructor with Scheme :)
Constructor of what?
Oleg
I'm currently using 2 libraries.. one of which depends on httpclient 3.1
and the other on httpclient 4.0 hah.
So if I can find a way to remove the use of 3.1 it'd be great! my
current major sticking point is just telling httpclient 4.0 "go ahead
and accept any SSL from anything, I dont care :)"
Thanks,
Roger
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
