[ http://issues.apache.org/jira/browse/HTTPCLIENT-601?page=all ]
Oleg Kalnichevski resolved HTTPCLIENT-601.
------------------------------------------
Resolution: Fixed
File committed to the SVN trunk. Many thanks, Mark
Oleg
> SecureProtocolFactoryWrapper class for using the socket factory created by
> Java Web Start
> -----------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-601
> URL: http://issues.apache.org/jira/browse/HTTPCLIENT-601
> Project: HttpComponents HttpClient
> Issue Type: New Feature
> Components: Contrib
> Affects Versions: 3.0.1
> Environment: Java 5.0, Windows XP
> Reporter: Mark Claassen
> Fix For: 3.1 Beta 1
>
> Attachments: SocketFactoryWrapper.java
>
>
> As smartcards and SSL are becoming more and more prevelant, Java Web Start
> has started to become better equiped to handle these situations. When
> running an app within webstart, it can access the browser's keystore, which
> (at least in our case) accessed the users smartcard to make the SSL
> connection.
> I wanted to start using HttpClient, but needed a way to do so while still
> mainaining access to the browser's keystore.
> My initial tests show that getting the default socket factory from the
> java.net.HttpURLConnection and wrapping it in a class that implements
> org.apache.commons.httpclient.protocol.SecureProtocolSocketFactory is
> sufficient.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
