[ https://issues.apache.org/jira/browse/HTTPCLIENT-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433351#comment-17433351 ]
Oleg Kalnichevski commented on HTTPCLIENT-2135: ----------------------------------------------- > Other than the connectionTimeToLive feature request I think this can be > resolved. [~rschmitt] I added TTL setting to the ConnectionConfig per your request. I also updated the examples to make use of the new APIs. Please take a look: https://github.com/apache/httpcomponents-client/commit/a02455acb31ad7e676130d46d6a04bd97b76e957 https://github.com/apache/httpcomponents-client/commit/ffc8cd7585f13689170bae1e1b894f649b6581a7 Oleg > TLS handshake timeouts cannot be controlled through RequestConfig > ----------------------------------------------------------------- > > Key: HTTPCLIENT-2135 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2135 > Project: HttpComponents HttpClient > Issue Type: Bug > Components: HttpClient (classic) > Affects Versions: 5.0.3 > Reporter: Ryan Schmitt > Priority: Major > Fix For: 5.2-alpha1 > > > Apparently as a consequence of HTTPCLIENT-2091 and/or HTTPCLIENT-2099, TLS > handshake timeouts can no longer be specified through any of the three > {{RequestConfig}} timeout parameters (connect, connection request, response). > The only way to limit TLS handshake duration is through low-level socket > configuration (socket timeout), which of course affects more than just TLS > handshakes. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org