[jira] [Closed] (GUACAMOLE-1562) "uuid" property of Guacamole.ChainedTunnel may not be initialized

["Mike Jumper (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GUACAMOLE-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Jumper closed GUACAMOLE-1562.
----------------------------------
    Fix Version/s: 1.6.0
       Resolution: Fixed

> "uuid" property of Guacamole.ChainedTunnel may not be initialized
> -----------------------------------------------------------------
>
>                 Key: GUACAMOLE-1562
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1562
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-common-js
>            Reporter: Mike Jumper
>            Assignee: Mike Jumper
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> Depending on timing, the {{commit_tunnel()}} function of {{Guacamole.ChainedTunnel}} may be invoked before the tunnel UUID is received. If this occurs, the {{onuuid}} handler will be correctly invoked, but only the {{uuid}} property of the underlying tunnel will be updated, leaving the {{uuid}} property of the {{Guacamole.ChainedTunnel}} as {{null}}.
> Additionally, if the tunnel-internal "ping" instruction specific to the WebSocket tunnel is sent and handled prior to receiving the UUID, the server response to that ping may be incorrectly interpreted as the UUID, causing similar trouble.
> For things like out-of-band file uploads to work correctly, the tunnel UUID needs to always be correctly set.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)