Ubuntu
websockify package

websockify 0.5.1+dfsg1-3ubuntu0.14.04.1 source package in Ubuntu

Changelog

websockify (0.5.1+dfsg1-3ubuntu0.14.04.1) trusty; urgency=medium

  * Fixup handling of child processes to avoid zombies (LP: #1350352):
    - d/p/avoid-zombies.patch,
      d/p/handle-multiprocessing.patch: Cherry picked fixes from upstream
      VCS to handle signals to child processes correctly.
 -- James Page <email address hidden>   Thu, 31 Jul 2014 14:40:12 +0100

Upload details

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

See full publishing history Publishing

Series Pocket Published Component Section
Trusty updates universe python

Downloads

File Size SHA-256 Checksum
websockify_0.5.1+dfsg1.orig.tar.xz 88.5 KiB 83e51114370fbc6febcfffaf17a3fa51d804e2d08536db428c338e2234b17811
websockify_0.5.1+dfsg1-3ubuntu0.14.04.1.debian.tar.xz 11.0 KiB e52b314ecbc331b2d0f21e992661c4b7084923426e88d8ef5c61671249541ae3
websockify_0.5.1+dfsg1-3ubuntu0.14.04.1.dsc 2.3 KiB 525b54fb3140956ccd204541bcf6cd7befeba7069d5ce3e2768f3880ddc2aaf0

View changes file

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.