You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2002/07/19 00:19:19 UTC
DO NOT REPLY [Bug 10970] New: -
Client side certificate support with HTTPS
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10970>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10970
Client side certificate support with HTTPS
Summary: Client side certificate support with HTTPS
Product: Commons
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: HttpClient
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: jsdever@sympatico.ca
It's not too hard, as long as you configure the keystore
correctly. BUT if you want more control over things, or are hampered by the
US-export JSSE (!!), we need a bit more configuration however.
Since the export version of JSSE doesn't allow the configuration of what
SSLSocketFactory.getDefault() returns, we need to add an attribute to
HttpConnection to specify another SSLSocketFactory. That we, we can hook into
things that way.
Bill Cutshall posted a partial solution on March 28th under the subject "Re:
[httpclient] Proxy and release questions.", but that change needs to be
propagated into HttpConnectionManager and HttpMultiClient. The feature was
also requested on 3rd July by Ortwin Gluck under the topic "[httpclient]
Volunteering to make SSL socket factory more flexible"
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>