[
https://issues.apache.org/jira/browse/HTTPCLIENT-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912202#comment-16912202
]
Oleg Kalnichevski commented on HTTPCLIENT-1765:
-----------------------------------------------
[~northfolk28] As I have already said, {{RequestConfig}} applies only _*after*_
the connection has been fully established. Until then {{SocketConfig}} set at
the connection manager level applies. SSL handshake is considered a part of
connection routing, not of request execution, therefore connect timeout apply
in absence socket timeout. This behavior is consistent for both plain HTTP and
HTTPS.
Oleg
> SSLConnectionSocketFactory uses connectTimeout for read timeout
> ---------------------------------------------------------------
>
> Key: HTTPCLIENT-1765
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1765
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 4.5
> Environment: Any
> Reporter: SATISH BURNWAL
> Priority: Major
> Labels: features
>
> SSLConnectionSocketFactory uses connect timeout value for socket.soTimeout as
> well (as per the code in SSLConnectionsocketFactory). Because of this, when
> clients are created with such config (below), read timeout is not taking
> effect.
> RequestConfig.Builder rb = RequestConfig.custom();
> rb.setConnectTimeout(3000);
> rb.setExpectContinueEnabled(true);
> rb.setSocketTimeout(10000);
> rb.setAuthenticationEnabled(true);
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
