Data

Tools

Indexes

Applications

Experiments

Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / novnc/websockify-js issues and pull requests

#34 - [Question]Is it possible for one websocket to proxy multiple tcpsockets？

Issue - State: closed - Opened by guozanhua about 1 year ago - 1 comment

#33 - https://github.com/novnc/websockify-js/pull/24#issue-810366986

Issue - State: closed - Opened by Mobsterz over 1 year ago
Labels: invalid

#32 - Add WEBIRC command

Pull Request - State: closed - Opened by jyonxo about 2 years ago - 1 comment

#30 - `protocols.indexOf('binary') >= 0` error

Issue - State: closed - Opened by alexchandel over 3 years ago - 1 comment
Labels: duplicate

#29 - Compatibility with `ws` > 1.0, security issues

Issue - State: open - Opened by alexchandel almost 4 years ago - 5 comments

#28 - WebSocket client disconnected :1005

Issue - State: open - Opened by toby63 about 4 years ago - 4 comments

#27 - how can i make a rtsp stream to websoket

Issue - State: closed - Opened by Nidheeshv0312 about 4 years ago - 1 comment

#26 - Token support in wstelnet.js ?

Issue - State: open - Opened by donalod over 8 years ago

#24 - Update wstelnet.js

Pull Request - State: closed - Opened by sebps over 4 years ago - 1 comment

#23 - Fix a couple of typos in README

Pull Request - State: closed - Opened by gamtiq almost 5 years ago - 1 comment

#22 - Remove unnecessary char that looks like a typo

Pull Request - State: closed - Opened by sandvige over 5 years ago - 1 comment

#21 - how to encrypted WebSocket connections (wss://) on win server?

Issue - State: closed - Opened by vwater over 5 years ago - 2 comments

#20 - novnc安装在windows7 X86系统上的访问问题！

Issue - State: closed - Opened by BeiJing-LiChenXing over 5 years ago - 4 comments

#19 - Websocket Error Network Error 12029 IE11 issue Working on Chrome, Firefox

Issue - State: open - Opened by shahasachin over 5 years ago - 3 comments

#18 - debug with vscode

Issue - State: closed - Opened by goodwinfame over 6 years ago - 1 comment

#17 - Error: ENOENT, chmod with npm install websockify

Issue - State: closed - Opened by websocketdev almost 12 years ago - 3 comments

#16 - Recent breaking changes to websockets/ws break websockify.js

Issue - State: closed - Opened by samfrances about 8 years ago - 1 comment

#15 - WSS:// works on Chrome and Safari, but not IE, Edge, or Firefox

Issue - State: closed - Opened by reillychase almost 8 years ago - 2 comments

#13 - Accessing readyState of WebSocket Directly

Issue - State: open - Opened by bmcdorman almost 12 years ago - 2 comments

#12 - Exception for big data

Issue - State: open - Opened by staran01 almost 12 years ago

#11 - websock.send_string doesn't convert to utf8

Issue - State: open - Opened by imuli about 11 years ago - 2 comments

#10 - quasi- Node.js net.Server, consumeable Websockify

Issue - State: open - Opened by rektide almost 11 years ago - 1 comment

#9 - case 109 incorrect in keysym.js file should be case 173

Issue - State: open - Opened by WebSockit2me over 10 years ago - 1 comment

#7 - Expose javascript API

Issue - State: open - Opened by kevinhikaruevans almost 9 years ago

#6 - Several Issues noted in VT100.js

Issue - State: open - Opened by markehack almost 9 years ago

#5 - Dependencies broken when JX packaging in Windows

Issue - State: open - Opened by PhilTee over 8 years ago

#4 - Stream-like websock.js

Issue - State: open - Opened by ishitatsuyuki about 8 years ago - 3 comments

#3 - websockify.js : Server disconnected (code: 1006)

Issue - State: open - Opened by jude90 almost 8 years ago - 6 comments

#2 - node package needs updated in npm

Issue - State: open - Opened by opatomic almost 7 years ago - 6 comments

#1 - Remove all non-JavaScript from the tree

Pull Request - State: closed - Opened by CendioOssman about 6 years ago - 1 comment