hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Weber (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HTTPCLIENT-634) HostConfiguration socketFactory is ignored
Date Sat, 17 Feb 2007 16:48:05 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473939

Roland Weber commented on HTTPCLIENT-634:

HttpClient has been working that way since the 2.0 days. It has been re-iterated time and
again, even as recently as two weeks ago with Sebastian:

I am not in favor of changing the behavior that late in the release cycle. Different SSL connection
algorithms can be used by aliasing the protocol, or am I wrong there?
We could move the HostConfiguration update code of the HttpClient class to a dedicated protected
method. That would make it easy to override without changing the default behavior.


> HostConfiguration socketFactory is ignored
> ------------------------------------------
>                 Key: HTTPCLIENT-634
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-634
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient
>    Affects Versions: Nightly Builds
>         Environment: Windows, Eclipse, Java 1.5
>            Reporter: John Kristian
>         Attachments: HostConfiguration.patch
> HostConfiguration doesn't use its host.protocol to execute an HttpMethod with an absolute
URL.  It should, if the Protocol's scheme is the same as the method's URL scheme.
> This bug makes it difficult to integrate a specialized SSL connection algorithm (in a
SecureProtocolSocketFactory) with a module implemented on top of HttpClient.  The latter module
must not execute methods with absolute URLs.  Of course, this is difficult when one doesn't
control that module.  For example, I recently tried to integrate SSL certificate-based client
authentication with XFire.  XFire provides a reasonable API for replacing its HttpClient,
but one must hack its source code to prevent it from executing methods with absolute URLs.
> Protocol.registerProtocol is a possible answer, but it can't support two or more SSL
connection algorithms for one HTTPS host and port.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message