Websockify is a WebSocket to TCP proxy/bridge. This allows a browser to connect to any application/server/service.
Go to file
Ed Schouten d0e1fe6a3c Remove a faulty attribution from the Copyright.
The Copyright notice was copied from another source file, where I only
changed the Copyright line at the top.
2011-06-29 23:48:15 +02:00
debian Add monitoring support to wsproxy. 2011-06-29 11:07:31 +02:00
.gitignore Add Debian package infrastructure and license. 2011-06-28 12:05:50 +02:00
Makefile Add initial version of wsproxy source code. 2011-06-28 11:44:35 +02:00
README.md Add README. 2011-06-28 16:41:31 +02:00
wsproxy.c Remove a faulty attribution from the Copyright. 2011-06-29 23:48:15 +02:00

README.md

wsproxy: WebSockets-to-TCP proxy (for noVNC)

Description

wsproxy is an application that can be run from inetd, which allows noVNC to connect to an unmodified libvncserver. Furthermore, it makes use of the recently added support in noVNC for file names. The file name is used to denote the port number. Say, you connect to:

ws://host:41337/25900

The wsproxy opens a connection to:

vnc://host:25900/

The address to which wsproxy connects, is the same as the address to which the client connected (using getsockname()).

Configuration

wsproxy can be enabled by adding the following line to inetd.conf:

41337 stream tcp nowait nobody /usr/sbin/wsproxy wsproxy 25900 25909

The two parameters of wsproxy denote the minimum and the maximum allowed port numbers. This allows a single wsproxy instance to multiplex connections to multiple VNC servers.