Ubuntu
websockify package

websockify 0.6.1+dfsg1-1 source package in Ubuntu

Changelog

websockify (0.6.1+dfsg1-1) unstable; urgency=high

  * New upstream release (LP: #1447675).
  * Switching to gz compression for the orig.tar.
  * Added dh-python as build-depends.

 -- Thomas Goirand <email address hidden>  Mon, 15 Jun 2015 18:04:28 +0200

Upload details

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

See full publishing history Publishing

Series Pocket Published Component Section
Xenial release universe python

Downloads

File Size SHA-256 Checksum
websockify_0.6.1+dfsg1-1.dsc 2.0 KiB 4c12e7dbf965a6a8ed80a3dfd8c191811ddfd425d117ba3072d43e82230f7520
websockify_0.6.1+dfsg1.orig.tar.gz 111.7 KiB 8243a6ee8722e20695cc5ca1c9568a777c2c579f3d2117d3e9e2d680e9cdfd4f
websockify_0.6.1+dfsg1-1.debian.tar.xz 9.5 KiB a35ecad249567abb92887be367d0f0d057ace6f8f2a77b4f01aee8da227c9b29

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.

websockify-dbgsym: No summary available for websockify-dbgsym in ubuntu yakkety.

No description available for websockify-dbgsym in ubuntu yakkety.