hc-httpclient-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Claassen <ma...@donnell.com>
Subject RE: HTTPClient ntlm smart card
Date Thu, 28 Jun 2012 14:36:39 GMT
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:matthew.young@forsakringskassan.se] 
Sent: Thursday, June 28, 2012 1:38 AM
To: httpclient-users@hc.apache.org
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: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org
For additional commands, e-mail: httpclient-users-help@hc.apache.org


Mime
View raw message