Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solution option to solve #1326 problem #1327

Merged
merged 1 commit into from
Dec 7, 2019
Merged

Solution option to solve #1326 problem #1327

merged 1 commit into from
Dec 7, 2019

Conversation

vanym
Copy link
Contributor

@vanym vanym commented Nov 16, 2019

Add try catch to decodeUTF8 function to solve #1326

@CendioOssman
Copy link
Member

Hmm... This change will assume it is ISO 8859-1 if the decoding fails. This is correct in some cases, but not all. So I'm not sure this is the correct place to put that code.

Copy link
Member

@samhed samhed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just like @CendioOssman said, we don't always want to make this assumption. Currently, however, there are only two places where we use decodeUTF8(), both for desktopName. Could you place your try-catches in _negotiate_server_init() and _handleDesktopName() in core/rfb.js instead?

@samhed samhed added the bug label Dec 5, 2019
@samhed samhed added this to the v1.2.0 milestone Dec 5, 2019
@samhed
Copy link
Member

samhed commented Dec 7, 2019

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants