Summary: | Web Access disconnects with "unknown message type" | ||
---|---|---|---|
Product: | ThinLinc | Reporter: | Pierre Ossman <ossman> |
Component: | Web Access | Assignee: | Bugzilla mail exporter <bugzilla-qa> |
Status: | CLOSED WORKSFORME | ||
Severity: | Normal | CC: | astrand |
Priority: | P2 | ||
Version: | trunk | ||
Target Milestone: | 4.16.0 | ||
Hardware: | PC | ||
OS: | Unknown | ||
See Also: | https://www.cendio.com/bugzilla/show_bug.cgi?id=6091 | ||
Acceptance Criteria: |
Sometimes get this as well:
> Uncaught RangeError: Invalid typed array length
> at new Uint8Array (native)
> at RFB._negotiate_server_init (https://eudemo.thinlinc.com:300/include/rfb.js:911:30)
> at RFB._init_msg (https://eudemo.thinlinc.com:300/include/rfb.js:1041:33)
> util.js:220 Msg: Unsupported tight subencoding received, filter: 255
> Util.Error @ util.js:220
Today Web Access disconnected after a few seconds of simply showing the profile chooser. The xinit.log showed: > unknown message type 80 > > Tue Oct 24 15:30:14 2017 > VNCSConnST: tl-shadow-notify: CloseAuthenticatedConnection > Connections: closed: 127.0.0.1::38480 (unknown message type) Could not reproduce multiple times. We've not seen this occur again in years, so let's assume it got fixed somewhere along the way. |
The HTML seems to be getting some protocol stuff screwed up in some cases and gets thrown out by the server with this error: > Connections: closed: 127.0.0.1::58200 (unknown message type) Not sure what the triggering condition is at this point.