hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chaithanya Kanumolu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1689) HttpClientBuilder ignores SSLContext if HttpClientConnectionManager is not null
Date Sun, 11 Oct 2015 08:15:05 GMT

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

Chaithanya Kanumolu commented on HTTPCLIENT-1689:

Ok, so you mean to say HttpClientConnectionManager & SSLSocketFactory are mutually exclusive?

In that case this is not a bug anymore.

But, can we treat this change as improvement?  Or do see any issue doing that way?

The reason I am asking this is, shortly most of the servers industry is moving away from TLS1.0
SSL Version.  And for every such move clients fail to connect to server.

And the only way for them, is to change their code, modifying the way HttpClientConnectionManager
is created.  But if we can allow them to supply "https.protocols" System properties apart
from HttpClientConnectionManager, we could help him.

Right now "https.protocols" system property and HttpClientConnectionManager are mutually exclusive.

> HttpClientBuilder ignores SSLContext if HttpClientConnectionManager is not null
> -------------------------------------------------------------------------------
>                 Key: HTTPCLIENT-1689
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1689
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpCache
>    Affects Versions: 4.5
>         Environment: N/A
>            Reporter: Chaithanya Kanumolu
>            Priority: Minor

This message was sent by Atlassian JIRA

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

View raw message