[
https://issues.apache.org/jira/browse/HTTPCLIENT-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141975#comment-17141975
]
Dave Moten commented on HTTPCLIENT-2090:
----------------------------------------
Ok, but do the SocketConfig settings apparently vary even though I don't set
them?
To demonstrate this I started a socket server on localhost:1234 that accepted a
connection and slept forever. I then changed the code above so that the
setProxy line is commented out and changed the HttpHost to
"https://localhost:1234";. When I check the breakpoint there is a socket timeout
set on sslsocket just before startHandshake is called.
I repeated the above with the setProxy line enabled and went to
"https://google.com";. When I check the breakpoint mentioned there is no socket
timeout set on sslsocket just before startHandshake is called.
You think this is OS/JRE specific? Seems odd.
> Read timeout not applied for SSLHandshake when using proxy
> ----------------------------------------------------------
>
> Key: HTTPCLIENT-2090
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2090
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 4.5.12
> Reporter: Dave Moten
> Priority: Minor
>
> When I make a connection to an https endpoint without proxy I've confirmed
> that read timeouts as specified in the RequestConfig part of the client are
> applied by putting a breakpoint against the startHandshake line in
> SSLConnectionSocketFactory:394 (I viewed the expression
> sslsock.getSoTimeout()).
> However, when I make a connection to an https endpoint (e.g.
> https://google.com) via our corporate proxy I can see via the same breakpoint
> that sslsock.getSoTimeout() returns 0.
> Here's the test code that when debugged showed the problem:
> {{RequestConfig requestConfig = RequestConfig
> .custom()
> .setConnectionRequestTimeout(10000)
> .setConnectTimeout(10000)
> .setSocketTimeout(5000)
> .build();
> HttpClient client = HttpClientBuilder
> .create()
> .setDefaultRequestConfig(requestConfig)
> .setProxy(HttpHost.create("http://proxy:8080";)) //
> .build();
> HttpGet get = new HttpGet("https://google.com";);
> client.execute(get);}}
> By the way the consequence of this has been hangs in our production
> environment talking to Microsoft's EWS service which seemed to be flaky last
> week.
> I have a workaround described by Li Changshu in HTTPCLIENT-1478 involving
> setting a pooling connection manager but I would like the library to behave
> consistently when using a proxy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
