-
jalf authored
Some browsers (Firefox) reject unencrypted ws connections if the hosting page uses https by throwing an exception when you create the websocket object. NoVNC interprets this as binary being unsupported, and falls back to base64. If we instead connect to wss://localhost, the websocket object can be created regardless of whether the hosting page is on http or https.
ec34af8f
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| chrome-app | ||
| web-socket-js | ||
| Orbitron700.ttf | ||
| Orbitron700.woff | ||
| base.css | ||
| base64.js | ||
| black.css | ||
| blue.css | ||
| des.js | ||
| display.js | ||
| input.js | ||
| jsunzip.js | ||
| logo.js | ||
| playback.js | ||
| rfb.js | ||
| ui.js | ||
| util.js | ||
| websock.js | ||
| webutil.js |