[
https://issues.apache.org/jira/browse/HTTPCLIENT-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547015#comment-16547015
]
Ryan Schmitt commented on HTTPCLIENT-1934:
------------------------------------------
[~olegk] This patch seems to work. I noticed in the debugger that the
SSLSession instance passed to the HostnameVerifier still shows the proxy
information, not the target information, as the peer host and port, but I don't
know if that's intentional or not.
> 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: [email protected]
For additional commands, e-mail: [email protected]
