You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Ryan Schmitt (JIRA)" <ji...@apache.org> on 2018/07/19 16:08:00 UTC
[jira] [Closed] (HTTPCLIENT-1934) H2TlsStrategy does not handle
proxy connections correctly
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Schmitt closed HTTPCLIENT-1934.
------------------------------------
> H2TlsStrategy does not handle proxy connections correctly
> ---------------------------------------------------------
>
> Key: HTTPCLIENT-1934
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1934
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Affects Versions: 5.0 Beta1
> Reporter: Ryan Schmitt
> Assignee: Oleg Kalnichevski
> Priority: Major
> Fix For: 5.0 Beta2
>
>
> I'm setting up a CloseableHttpAsyncClient with an AsyncClientConnectionManager that sets up an H2TlsStrategy for the https scheme. In my integration tests, I have one test that calls a target host, [https://localhost:8444/,] over a proxy located at 127.0.0.7:8900. This mostly works: the client sends a CONNECT request to 127.0.0.7:8900 to set up a tunnel, and then sends a ClientHello to the target via the tunnel.
> The problem is that my HostnameVerifier is getting called back with the wrong hostname: instead of the target hostname ("localhost"), it is getting called back with the proxy hostname ("127.0.0.7"), and this then causes hostname verification to fail.
--
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