[
https://issues.apache.org/jira/browse/HTTPCLIENT-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144447#comment-17144447
]
Dave Moten commented on HTTPCLIENT-2091:
----------------------------------------
> Alternatively we could make SocketConfig have a finite socket timeout by
> default and drop this special logic altogether.
I'm a big fan of this as long as it doesn't kick in for the request socket
timeout (a long response time for an application request is completely
plausible and should be supported).
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
