Ubuntu
websockify package

websockify 0.5.1+dfsg1-3 source package in Ubuntu

Changelog

websockify (0.5.1+dfsg1-3) unstable; urgency=low


  * Fixes the shell wrapper for rebind. Thanks to Philipp Hahn
    <email address hidden> for reporting and his fix (Closes: #726304).
  * Cleans correctly, and allow 2 builds in a raw.

 -- Thomas Goirand <email address hidden>  Sun, 08 Dec 2013 06:20:11 +0000

Upload details

Uploaded by:
PKG OpenStack
Uploaded to:
Sid
Original maintainer:
PKG OpenStack
Architectures:
any
Section:
misc
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Trusty release universe python

Downloads

File Size SHA-256 Checksum
websockify_0.5.1+dfsg1-3.dsc 2.1 KiB 5059fe2f288e786302c693e4e2afbee55e9e362ead2394be98ed077b06b85ba7
websockify_0.5.1+dfsg1.orig.tar.xz 88.5 KiB 83e51114370fbc6febcfffaf17a3fa51d804e2d08536db428c338e2234b17811
websockify_0.5.1+dfsg1-3.debian.tar.gz 10.7 KiB f6c011f1a31b7ed06f792b72c9c2459c0795b16aac4aa9b33b18fc0a6539c233

Available diffs

No changes file available.

Binary packages built by this source

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.