How to Install and Uninstall websockify Package on Ubuntu 16.04 LTS (Xenial Xerus)

Last updated: October 06,2024

1. Install "websockify" package

Here is a brief guide to show you how to install websockify on Ubuntu 16.04 LTS (Xenial Xerus)

$ sudo apt update $ sudo apt install websockify

2. Uninstall "websockify" package

Please follow the instructions below to uninstall websockify on Ubuntu 16.04 LTS (Xenial Xerus):

$ sudo apt remove websockify $ sudo apt autoclean && sudo apt autoremove

3. Information about the websockify package on Ubuntu 16.04 LTS (Xenial Xerus)

Package: websockify
Architecture: amd64
Version: 0.6.1+dfsg1-1ubuntu1
Priority: optional
Section: universe/python
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: PKG OpenStack
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 143
Depends: python-numpy, python (<< 2.8), python (>= 2.7~), python:any (>= 2.7.5-5~), libc6 (>= 2.4)
Breaks: novnc (<< 1:0.4+dfsg+1-6)
Replaces: novnc (<< 1:0.4+dfsg+1-6)
Filename: pool/universe/w/websockify/websockify_0.6.1+dfsg1-1ubuntu1_amd64.deb
Size: 37978
MD5sum: 8b42a1d51593fa05062f761157d0f9da
SHA1: bd34e689b79db6cd86420873e394a1268a05f1b9
SHA256: 0352d53d6bb435603c36b5ec16f9202072cb868f6ce7b3f66e19bc52bea8ed3b
SHA512: 35ca4f5f01f8bc5a58a77d5bacbf1a98e461d936804a643a4793df60f7874543ddccda1364056c620477515f6ecd7aaeb62123fe0c10492cb76965ff08880358
Homepage: https://pypi.python.org/pypi/websockify
Description-en: WebSockets support for any application/server
websockify was formerly named wsproxy and was part of the noVNC project.
.
At the most basic level, websockify just translates WebSockets traffic to
normal socket traffic. Websockify accepts the WebSockets handshake, parses it,
and then begins forwarding traffic between the client and the target in both
directions.
.
Websockify supports all versions of the WebSockets protocol (Hixie and HyBi).
The older Hixie versions of the protocol only support UTF-8 text payloads. In
order to transport binary data over UTF-8 an encoding must used to encapsulate
the data within UTF-8.
.
With Hixie clients, Websockify uses base64 to encode all traffic to and from
the client. This does not affect the data between websockify and the server.
.
With HyBi clients, websockify negotiates whether to base64 encode traffic to
and from the client via the subprotocol header (Sec-WebSocket-Protocol). The
valid subprotocol values are 'binary' and 'base64' and if the client sends
both then the server (the Python implementation) will prefer 'binary'. The
'binary' subprotocol indicates that the data will be sent raw using binary
WebSocket frames. Some HyBi clients (such as the Flash fallback and older
Chrome and iOS versions) do not support binary data which is why the
negotiation is necessary.
Description-md5: 337cbf4b14d9c875bd13ec09c109dd7e

Package: websockify
Priority: optional
Section: universe/python
Installed-Size: 173
Maintainer: Ubuntu Developers
Original-Maintainer: PKG OpenStack
Architecture: amd64
Version: 0.6.1+dfsg1-1
Replaces: novnc (<< 1:0.4+dfsg+1-6)
Depends: python-numpy, python (<< 2.8), python (>= 2.7~), python:any (>= 2.7.5-5~), libc6 (>= 2.4)
Breaks: novnc (<< 1:0.4+dfsg+1-6)
Filename: pool/universe/w/websockify/websockify_0.6.1+dfsg1-1_amd64.deb
Size: 37614
MD5sum: e6b76af5f30edb9d58240d5ae5893048
SHA1: fd469cca61c22b9e1860d4b22fcc59bc61ec09e1
SHA256: a7c220d11b45c65defbdb3d83975788b61e57bbef196f77d03c546e64b8d4427
Description-en: WebSockets support for any application/server
websockify was formerly named wsproxy and was part of the noVNC project.
.
At the most basic level, websockify just translates WebSockets traffic to
normal socket traffic. Websockify accepts the WebSockets handshake, parses it,
and then begins forwarding traffic between the client and the target in both
directions.
.
Websockify supports all versions of the WebSockets protocol (Hixie and HyBi).
The older Hixie versions of the protocol only support UTF-8 text payloads. In
order to transport binary data over UTF-8 an encoding must used to encapsulate
the data within UTF-8.
.
With Hixie clients, Websockify uses base64 to encode all traffic to and from
the client. This does not affect the data between websockify and the server.
.
With HyBi clients, websockify negotiates whether to base64 encode traffic to
and from the client via the subprotocol header (Sec-WebSocket-Protocol). The
valid subprotocol values are 'binary' and 'base64' and if the client sends
both then the server (the Python implementation) will prefer 'binary'. The
'binary' subprotocol indicates that the data will be sent raw using binary
WebSocket frames. Some HyBi clients (such as the Flash fallback and older
Chrome and iOS versions) do not support binary data which is why the
negotiation is necessary.
Description-md5: 337cbf4b14d9c875bd13ec09c109dd7e
Homepage: https://pypi.python.org/pypi/websockify
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu