[HTTPCLIENT-2090] Read timeout not applied for SSLHandshake when using proxy

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 4.5.12
• Component/s: HttpClient (classic)
• Assignee: Unassigned
• Reporter: Dave Moten
• Created: 22/Jun/20 01:34
• Updated: 01/Jul/20 17:52
• Resolved: 22/Jun/20 06:31

Description

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.

Issue Links

• duplicates: HTTPCLIENT-1478 https calls ignore http.socket.timeout during SSL Handshake