websockify 0.9.0-0ubuntu2 source package in Ubuntu

Changelog

websockify (0.9.0-0ubuntu2) focal; urgency=medium

  * d/control: Push jwcrypto to Suggests as its not required for
    use of websockify.

 -- James Page <email address hidden>  Fri, 17 Apr 2020 11:40:50 +0100

Upload details

Uploaded by:
James Page
Uploaded to:
Focal
Original maintainer:
Ubuntu Developers
Architectures:
any
Section:
python
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Focal release main python

Downloads

File Size SHA-256 Checksum
websockify_0.9.0.orig.tar.gz 57.1 KiB 6ebfec791dd78be6584fb5fe3bc27f02af54501beddf8457368699f571de13ae
websockify_0.9.0-0ubuntu2.debian.tar.xz 10.5 KiB d4f7c03f8b8603b089dccffc18ef20aae2555690ca5184f53cbefdd6288f93cf
websockify_0.9.0-0ubuntu2.dsc 2.2 KiB d3c176d5f26cdd2c0a232e2a5e6f89cb460d4bbe70af393c622fcfa4fbf8de03

View changes file

Binary packages built by this source

python3-websockify: No summary available for python3-websockify in ubuntu groovy.

No description available for python3-websockify in ubuntu groovy.

websockify: 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.

websockify-dbgsym: debug symbols for websockify