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 2023/05/10 18:13:00 UTC

[jira] [Updated] (GUACAMOLE-1571) Error handling issues in stream processing code in angualr frontend

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

Mike Jumper updated GUACAMOLE-1571:
-----------------------------------
    Fix Version/s: 1.6.0
                   1.5.2

> Error handling issues in stream processing code in angualr frontend
> -------------------------------------------------------------------
>
>                 Key: GUACAMOLE-1571
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1571
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-client
>            Reporter: James Muehlner
>            Priority: Minor
>             Fix For: 1.6.0, 1.5.2
>
>
> A few issues have been identified in the stream processing code in the angular frontend:
>  * JSON-formatted errors received from the server during upload streams are not properly handled, leading to error messages not being displayed to the user
>  * The list of translatable upload errors is hardcoded in the JS, meaning that translations cannot be supplied for currently untranslated errors by extensions.  (NOTE: the same issue exists for the client notification system)
>  * In Firefox only, upload streams that are rejected do not contain any response information - the status code is 0 in the XHR, and the response information is blank in the network tab - this is likely related to this issue: [https://stackoverflow.com/questions/20210252/status-code-text-and-all-response-headers-are-null-for-an-xhr-that-has-status-c]
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)