[
https://issues.apache.org/jira/browse/HTTPCLIENT-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17415741#comment-17415741
]
Ryan Schmitt commented on HTTPCLIENT-2135:
------------------------------------------
{{ConnectionConfig}} looks great! Can we also move {{connectionTimeToLive}}
from the connection manager to {{ConnectionConfig}}? It would be great if I
could easily configure TLS connections to live longer than plaintext
connections.
Additionally, I noticed another bug in 5.2 involving connection attempt
failures. Previously, when a connection attempt to a given hostname failed, the
client would try again using a _different_ IP address. This no longer seems to
occur. The relevant integration test uses HTTP, so we can discount the TLS
layer.
> 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: [email protected]
For additional commands, e-mail: [email protected]
