You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/07/11 15:20:00 UTC
[jira] [Commented] (HTTPCLIENT-2091) Connect timeout is used
instead of socket timeout after a tls upgrade
[ https://issues.apache.org/jira/browse/HTTPCLIENT-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156014#comment-17156014 ]
ASF subversion and git services commented on HTTPCLIENT-2091:
-------------------------------------------------------------
Commit 5bdcb242f0297c9dca8f6284ed5a4dd062a210b7 in httpcomponents-client's branch refs/heads/master from Carter Kozak
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-client.git;h=5bdcb24 ]
HTTPCLIENT-2099, HTTPCLIENT-2091: SSLConnectionSocketFactory connect timeout fix (#241)
SSLConnectionSocketFactory no longer overrides the socket timeout
with the connect timeout when an unlimited socket timeout is
configured. This matches behavior of HTTPCLIENT-2091.
Note that in scenarios where SocketConfig sets an infinite timeout
and the RequestConfig sets a bounded timeout, this change results
in the connect-timeout no longer applying to the TLS handshake.
This behavior can be retained by setting the expected timeout in
the SocketConfig.
> Connect timeout is used instead of socket timeout after a tls upgrade
> ---------------------------------------------------------------------
>
> Key: HTTPCLIENT-2091
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2091
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (async), HttpClient (classic)
> Affects Versions: 5.0.1
> Reporter: Carter Kozak
> Priority: Major
> Fix For: 5.0.2
>
>
> After a TLS upgrade, the connect timeout is used instead of the configured socket timeout. In some configurations this results in unexpected socket timeouts earlier than expected.
>
> This impacts forward proxies using tunneling (CONNECT approach to pass tls bytes through a proxy server as opposed to individual plain http requests) which time out after the connect timeout is reached.
> This is a regression from hc4 which does not exhibit this issue.
> Some details here, where I thought the issues could be related: https://issues.apache.org/jira/browse/HTTPCLIENT-2090?focusedCommentId=17143321&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17143321
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org