Bug 5093 - Web Access reports a bad error message for unicode usernames when server is Latin1
Summary: Web Access reports a bad error message for unicode usernames when server is L...
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Peter Åstrand
URL:
Keywords:
Depends on: 4840
Blocks:
  Show dependency tree / graph
 
Reported: 2014-04-15 13:06 CEST by Samuel Mannehed
Modified: 2022-11-15 16:47 CET (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Samuel Mannehed cendio 2014-04-15 13:06:03 CEST 
From bug 4840 comment #12 and #13:

NoVNC doesn't seem to work when logging in to a system with ISO8859-1
usernames. ASCII usernames work fine, I haven't tested other username
encodings.

Here's what Firefox 28 has to say about this:

recv_message, caught exception:
 Util.decodeUTF8@https://sunray.lkpg.cendio.se:300/include/util.js:237
 RFB/init_msg@https://sunray.lkpg.cendio.se:300/include/rfb.js:923
 RFB/handle_message@https://sunray.lkpg.cendio.se:300/include/rfb.js:542
 recv_message@https://sunray.lkpg.cendio.se:300/include/websock.js:220

Here's what Chrome 34.0.1847.116 says:

recv_message, caught exception: URIError: URI malformed
    at decodeURIComponent (native)
    at Object.Util.decodeUTF8 (https://sunray.lkpg.cendio.se:300/include/util.js:237:31)
    at RFB.init_msg (https://sunray.lkpg.cendio.se:300/include/rfb.js:923:24)
    at Object.RFB.handle_message [as message] (https://sunray.lkpg.cendio.se:300/include/rfb.js:542:9)
    at WebSocket.recv_message (https://sunray.lkpg.cendio.se:300/include/websock.js:220:27)
Comment 1 Samuel Mannehed cendio 2018-04-10 13:19:13 CEST 
The usernames must match the server locale. We have decided to document this and improve the error message.
Note You need to log in before you can comment on or make changes to this bug.