setting socket timeout in both RequestConfig and SocketConfig works differently for HTTP and HTTPS

Question

I have set socket timeout in SocketConfig and set SocketConfig to connection manager as

connManager.setDefaultSocketConfig(SocketConfig.custom().setSoTimeout(soTimeout).build())

And overwriting the socket timeout value for individual requests by setting it in RequestConfig as

httpRequest.setConfig(RequestConfig.copy(defaultRequestConfig).setSocketTimeout(timeout).build())

Reference link.

For all http requests, the new value set using RequestConfig is overwriting the old value as expected. But for https requests it is always considering the old value which was set in SocketConfig.

I also upgraded httpclient from 4.3.1 to 4.3.6 after learning that this could be an issue in 4.3.1 reference link. But even this didn't help me solving the issue.
Am I missing anything ? Any idea on how I can solve this issue ?

ok2c · Accepted Answer · 2015-01-08 13:26:09Z

5

This is only partially true. RequestConfig represents request level settings, while SocketConfig represents connection level settings. Secure connections need to do a SSL/TLS handshake and establish a secure session before they can be used to execute requests. Therefore, RequestConfig settings can be allied only after HTTPS connection has been fully established. Until then only SocketConfig apply.

answered Jan 8, 2015 at 13:26

ok2c

27.9k5 gold badges66 silver badges74 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Antoniossss Over a year ago

Sounds like a design flaw - without setting default socket config, client can hang forever, despite the fact that dev already took care about eg. extending default timeout period for particular request. IMHO request config (if at least the one from client context) should apply to SLL handshake!) Upvote for splitting SSL from HTTP layers.

ok2c Over a year ago

@Antoniossss: It does. At the SSL handshake time if the connect timeout is finite and the socket timeout is undefined (infinite) the connection timeout applies github.com/apache/httpclient/blob/4.5.x/httpclient/src/main/…

Collectives™ on Stack Overflow

setting socket timeout in both RequestConfig and SocketConfig works differently for HTTP and HTTPS

1 Answer 1

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related