hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1160) LayeredSchemeSocketFactory.createLayeredSocket() should have access to HttpParams
Date Thu, 26 Jan 2012 14:46:41 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193868#comment-13193868

Oleg Kalnichevski commented on HTTPCLIENT-1160:

Long time, no speak.

There is no good reason. What we can do is to deprecate LayeredSchemeSocketFactory interface
and create a new one (say, LayeringSchemeSocketFactory or some such) and provide a compatibility
layer for LayeredSchemeSocketFactory similar to that for LayeredSocketFactory.

> LayeredSchemeSocketFactory.createLayeredSocket() should have access to HttpParams
> ---------------------------------------------------------------------------------
>                 Key: HTTPCLIENT-1160
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1160
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpConn
>    Affects Versions: 4.1.2
>            Reporter: Steffen Pingel
> We use a custom implementation of LayeredSchemeSocketFactory that manages a keystore
location through HttpParams. That allows us to use different keystores on a per connection
> When a proxy is used LayeredSchemeSocketFactory.createLayeredSocket() is invoked which
does not have a parameter that passes the HttpParams along. In consequence certificate authentication
fails in our implementation. Is there a reason why all other factory methods in the super
class have an HttpParams parameter except for LayeredSchemeSocketFactory.createLayeredSocket()?
> The downstream bug is here:
> 369805: certificate authentication with custom keystore fails behind proxy
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=369805
> Any input would be greatly appreciated.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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

View raw message