You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2021/02/26 17:53:00 UTC

[jira] [Commented] (GUACAMOLE-1303) List of error codes leading to reconnects

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

Mike Jumper commented on GUACAMOLE-1303:
----------------------------------------

[~slackfan], please use the mailing list for questions about Guacamole. The bug tracker is meant for tracking bugs and features, not for providing generic support.

http://guacamole.apache.org/support/#mailing-lists

Based on your question, it sounds like dev@ would be the best choice. Be sure to subscribe first or your email will likely not be received.

> List of error codes leading to reconnects
> -----------------------------------------
>
>                 Key: GUACAMOLE-1303
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1303
>             Project: Guacamole
>          Issue Type: Wish
>          Components: guacamole, RDP
>    Affects Versions: 1.3.0
>            Reporter: Alexander Fischer
>            Priority: Minor
>
> In GUACAMOLE-1126 I outlined a situation in which a limited number of reconnects performed by the guacamole-client would be beneficial. There was a suspicion announced that this situation is more likely caused by an improperly evaluated error code returned by the RDP gateway.
> To further investigate on my end, I would like to know the the list of RDP error codes leading to reconnects or - the way around - not leading to reconnects, depending on how this is implemented. Is this list hard coded or configurable and where can I find it?
> Also, I would like to know the procedure to obtain the returned error code, is it available on frontend side or only on backend logs (with debug log level enabled?)? 
> Some rough guidance would be helpful.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)