[
https://issues.apache.org/jira/browse/HTTPCLIENT-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Famy updated HTTPCLIENT-1950:
----------------------------------
Description:
When building an HttpClient using HttpClientBuilder, if setSSLSocketFactory()
or setConnectionManager() is called, the build() method ignores the
hostnameVerifier, set via setSSLHostnameVerifier().
To avoid confusion, an exception should be thrown in the above scenario
until/unless it's possible to set the hostnameVerifier directly on any
previously set sslSocketFactory.
was:
When building an HttpClient using HttpClientBuilder, if setSSLSocketFactory()
is called, the build() method ignores the hostnameVerifier, set via
setSSLHostnameVerifier().
To avoid confusion, either an exception should be thrown in the above scenario
until/unless it's possible to set the hostnameVerifier directly on any
previously set sslSocketFactory.
> setSSLHostnameVerifier does not take effect when socket factory set
> -------------------------------------------------------------------
>
> Key: HTTPCLIENT-1950
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1950
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Reporter: Joel Famy
> Priority: Minor
>
> When building an HttpClient using HttpClientBuilder, if setSSLSocketFactory()
> or setConnectionManager() is called, the build() method ignores the
> hostnameVerifier, set via setSSLHostnameVerifier().
> To avoid confusion, an exception should be thrown in the above scenario
> until/unless it's possible to set the hostnameVerifier directly on any
> previously set sslSocketFactory.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
