[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371332#comment-17371332
 ] 

Torsten Krah commented on HTTPCLIENT-2091:
------------------------------------------

Imho that commit is a breaking change and should not be / should not have been 
considered for a minor version upgrade. Before it was infinite and now all 
consumers of this library faces timeout exception for operations which takes 
more than 3 minutes like Dave stated already.

I am coming from here 
[https://github.com/bmuschko/gradle-docker-plugin/issues/1022] where the plugin 
integrated a new docker-java version which itself upgraded to 
httpcomponents-core from 5.0 to 5.0.3 and now we're facing those timeout 
problems where we had no issues before - at least highly unexpected as a change 
in a minor version change.

And I can't fix that myself because first docker-java must make changes and 
release them, than gradle-docker-plugin must adapt to those and release them 
and than as a consumer / user I can configure those timeout to be infinite or 
longer like before - not just 3 minutes like now.

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to