You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2018/11/20 18:12:00 UTC
[jira] [Resolved] (HTTPCLIENT-1950) setSSLHostnameVerifier does not
take effect when socket factory set
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-1950.
-------------------------------------------
Resolution: Won't Fix
The behavior of this method is documented in javadoc
[http://hc.apache.org/httpcomponents-client-4.5.x/httpclient/apidocs/index.html]
This method has been removed in 5.0 but I am not in favor of changing its behavior in 4.x.
Oleg
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org