websockify 0.6.1+dfsg1-1ubuntu1 source package in Ubuntu

Changelog

websockify (0.6.1+dfsg1-1ubuntu1) xenial; urgency=medium

  * Fix hanging nova-novncproxy and can't be restarted (LP: #1715254)
    - [PATCH] Make websockify respect SIGTERM
    - [PATCH] Remove additional signal calls in websockify that
      causes novnc to hang.

 -- Seyeong Kim <email address hidden>  Mon, 23 Oct 2017 18:31:40 +0900

Upload details

Uploaded by:
Seyeong Kim on 2017-10-27
Sponsored by:
Corey Bryant
Uploaded to:
Xenial
Original maintainer:
PKG OpenStack
Architectures:
any
Section:
python
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Xenial updates on 2017-11-15 universe python

Downloads

File Size SHA-256 Checksum
websockify_0.6.1+dfsg1.orig.tar.gz 111.7 KiB 8243a6ee8722e20695cc5ca1c9568a777c2c579f3d2117d3e9e2d680e9cdfd4f
websockify_0.6.1+dfsg1-1ubuntu1.debian.tar.xz 11.0 KiB 4b1de035c20505bcfb8f37f4f32f27e9aa16ae99105414dee577196cff9ef1e9
websockify_0.6.1+dfsg1-1ubuntu1.dsc 2.0 KiB baec55b7e02890175a31284dfb603ab03c4c8ed0258b104b5a82193d64a13912

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.

websockify-dbgsym: debug symbols for package websockify

 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.