Your message dated Fri, 12 Apr 2013 09:00:12 +0000
with message-id <e1uqzq8-00021n...@franck.debian.org>
and subject line Bug#701822: fixed in websockify 0.3.0+dfsg1-1
has caused the Debian Bug report #701822,
regarding ITP: websockify -- WebSockets support for any application/server
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
701822: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand <z...@debian.org>
* Package name : websockify
Version : 0.3.0
Upstream Author : Joel Martin <git...@martintribe.org>
* URL : https://github.com/kanaka/websockify
* License : GPL-3
Programming Lang: Python
Description : 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.
--- End Message ---
--- Begin Message ---
Source: websockify
Source-Version: 0.3.0+dfsg1-1
We believe that the bug you reported is fixed in the latest version of
websockify, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 701...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand <z...@debian.org> (supplier of updated websockify package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 23 Feb 2013 01:22:51 +0800
Source: websockify
Binary: websockify
Architecture: source amd64
Version: 0.3.0+dfsg1-1
Distribution: experimental
Urgency: low
Maintainer: PKG OpenStack <openstack-de...@lists.alioth.debian.org>
Changed-By: Thomas Goirand <z...@debian.org>
Description:
websockify - WebSockets support for any application/server
Closes: 701822
Changes:
websockify (0.3.0+dfsg1-1) experimental; urgency=low
.
* Initial release. (Closes: #701822).
Checksums-Sha1:
a12b2de5bf1d1cd8ac2c418123e40d0f4dfd8067 1518 websockify_0.3.0+dfsg1-1.dsc
8045fce43a59fe676e652da008595015c0f7e0b0 84008
websockify_0.3.0+dfsg1.orig.tar.xz
038f31b779f1e25ef881f37b37ecc5c16bf4af0e 8999
websockify_0.3.0+dfsg1-1.debian.tar.gz
8b4753c0f74692b1939c6afd5b75569e6feb445a 35240
websockify_0.3.0+dfsg1-1_amd64.deb
Checksums-Sha256:
c3ad907174536a36f4e4a8cf8b2aef6b04b8a10e76054e62e0c364d019ec8421 1518
websockify_0.3.0+dfsg1-1.dsc
c5abffa75d68b9044673fc6d92a9c7330d708c486928e6c45ebbf6ac0d63c6b3 84008
websockify_0.3.0+dfsg1.orig.tar.xz
49c3c98c5d61ba6d5c42eb81e8eb2a2dfdfa3116f00247be019eb5afb7c1d346 8999
websockify_0.3.0+dfsg1-1.debian.tar.gz
b51de259f56d1b165c1c50b9fdaa88d169ae4146dcbde133f547c702114deb92 35240
websockify_0.3.0+dfsg1-1_amd64.deb
Files:
13a3f92ed1ad5156f73c9a01e7d9b9a8 1518 python optional
websockify_0.3.0+dfsg1-1.dsc
f629d909ad7a5bd4c577de4fb06d7496 84008 python optional
websockify_0.3.0+dfsg1.orig.tar.xz
15f4ad644121ce773198ced0b86f8c32 8999 python optional
websockify_0.3.0+dfsg1-1.debian.tar.gz
194f1dfc200ef3dd72ab917bda9e8117 35240 python optional
websockify_0.3.0+dfsg1-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlFlhRoACgkQl4M9yZjvmkkrEwCeLk8kcrWldEcUvGO+FLAEy1k5
S/EAn3p9trhclcfEq7VA/cQSHXBtWvxm
=coJX
-----END PGP SIGNATURE-----
--- End Message ---
