[
https://issues.apache.org/jira/browse/HTTPCLIENT-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423288#comment-17423288
]
Oleg Kalnichevski commented on HTTPCLIENT-2135:
-----------------------------------------------
[~rschmitt] Could you please take a look at
https://github.com/apache/httpcomponents-client/commit/4a316fdaa00150128f6e1abb5f5ff1327683de81
and let me know if the proposed change is OK with you? The main idea is to
enable per-host based TLS configuration similat to per-route connection
configuration introduced earlier. Beside the handshake timeout TlsConfig would
have settings for HTTP protocol negotiation, TLS version, enabled ciphers and
so on.
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
