[
https://issues.apache.org/jira/browse/GUACAMOLE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877892#comment-17877892
]
Nick Couchman commented on GUACAMOLE-600:
-----------------------------------------
[~mjumper]: Thanks, that helped me narrow down where to look. I did some more
Google research and found some hints on how to handle non-blocking sockets, and
I've submitted a PR that I believe resolves the issue. Now I just need to test
against some hosts that I know aren't going to respond to make sure the timeout
actually works as expected...
> Allow specifying connection timeout
> -----------------------------------
>
> Key: GUACAMOLE-600
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-600
> Project: Guacamole
> Issue Type: New Feature
> Components: Documentation, RDP, SSH, Telnet, VNC
> Reporter: Nick Couchman
> Assignee: Nick Couchman
> Priority: Minor
> Fix For: 1.6.0
>
>
> This came up in a mailing list discussion, specifically related to SSH
> connections, but seems like it would be useful across all of the protocols to
> allow the connection to specify the timeout in making the connection. For
> environments where connections are expected to happen rapidly this can reduce
> delays if something is wrong; for environments that may experience larger
> delays it can avoid errors when the connection is expected to take a longer
> amount of time to establish.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
