Ubuntu
websockify package

websockify 0.10.0+dfsg1-2build1 source package in Ubuntu

Changelog

websockify (0.10.0+dfsg1-2build1) jammy; urgency=medium

  * No-change rebuild with Python 3.10 as default version

 -- Graham Inggs <email address hidden>  Thu, 13 Jan 2022 20:39:30 +0000

Upload details

Uploaded by:
Graham Inggs
Uploaded to:
Jammy
Original maintainer:
Debian OpenStack
Architectures:
any
Section:
python
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Jammy release main python

Downloads

File Size SHA-256 Checksum
websockify_0.10.0+dfsg1.orig.tar.xz 44.8 KiB 96c9dd3d2b03973bd17c70f2dc3046964eb42d11dfd61ba6c2d0ccb8848b49f0
websockify_0.10.0+dfsg1-2build1.debian.tar.xz 11.9 KiB 6a6e973f3740f8bed2fadf7323cc31c0e224039fcf3b5445f9fdf36b7fb881a4
websockify_0.10.0+dfsg1-2build1.dsc 2.2 KiB a847cad0d65b1b7a5d4c1e2611e917e11072621f02ffe5aad61f6d0a857cdd0f

View changes file

Binary packages built by this source

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

No description available for python3-websockify in ubuntu kinetic.

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: No summary available for websockify-dbgsym in ubuntu kinetic.

No description available for websockify-dbgsym in ubuntu kinetic.