Not sure if you that was a question or not. With 4.2, one line is all it is: new org.apache.http.conn.ssl.SSLSocketFactory(HttpsURLConnection.getDefaultSSLSocketFactory());
HttpClient will then use the "native" socket factory to create its sockets. So, if you can get HttpsURLConnection to work, HttpClient should work as well. You can look at the source for org.apache.http.conn.ssl.SSLSocketFactory. It has (perhaps always has) been a wrapper for a javax.net.ssl.SSLSocketFactory anyway. In 4.1 and before, it would create and configure its own. In 4.2, you have the additional ability to assign it directly. It really was not much of a change. Does that answer your question? -----Original Message----- From: Matthew Young [mailto:[email protected]] Sent: Thursday, June 28, 2012 1:38 AM To: [email protected] Subject: RE: HTTPClient ntlm smart card Building the SSLSocketFactory I got from your previous posts (with 4.2), more how the SSLSocketFactory gets injected into the HTTPClient. ;-) -- View this message in context: http://old.nabble.com/HTTPClient-ntlm-smart-card-tp34070660p34084430.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
