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

Ryan Schmitt commented on HTTPCLIENT-2135:
------------------------------------------

bq. The multi-home connect logic is still there. It just got moved into a 
separate support class [1]

Nah, there's something screwy here. The logic in {{MultihomeSocketConnector}} 
appears to be doing what it's supposed to be doing, but the connection retries 
on the known good address are failing nevertheless, with a 
{{java.net.SocketException}}. Fortunately, the classic client is pretty easy to 
step through in a debugger, so I'll try to see what's going on.

> 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

Reply via email to