Parents (Total: 21)

The searched file hash is included in 21 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
FileSize	31854
MD5	C3741666DCDD47B85419207955F7FF84
PackageDescription	WebSockets support for any application/server - Python 3 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. . This package provides the Python 3 module.
PackageMaintainer	PKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-7+deb9u1
SHA-1	00B59044FE7291A69C5AAA7D9BBCB380E199EF85
SHA-256	FD59ACC7C2D3F5635D0B688E4A4FAFACD50859F796B6B5FB465CEFBA19EB691E

Key	Value
MD5	DB09C39BB8A0189FF72D99021BCD32F7
PackageArch	noarch
PackageDescription	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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-websockify
PackageRelease	lp151.3.1
PackageVersion	0.8.0
SHA-1	04802349D9C99421A4CBC848A2355FBC7C95058F
SHA-256	8922CF3793F9DD886B716A8FB305FC3C6464ACB8E19C508263BFA5DE70A78E33

Key	Value
FileSize	31856
MD5	05B6F70461BAEEDA273334398AB4C322
PackageDescription	WebSockets support for any application/server - Python 3 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. . This package provides the Python 3 module.
PackageMaintainer	PKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-7+deb9u1
SHA-1	309B698B8F3D914AECA10166AC34EB46B1D95ADC
SHA-256	A170C3272DF5EBC7BB8179B14F70E9418C96ACC52552A5C26C65CFDD6747FB3C

Key	Value
MD5	4F31DEAAC26BFCEFB52E7C32A9B8FA19
PackageArch	noarch
PackageDescription	Python WSGI based adapter for the Websockets protocol - Python 3 version
PackageMaintainer	Fedora Project
PackageName	python3-websockify
PackageRelease	16.fc32
PackageVersion	0.8.0
SHA-1	326D6FE42417074D5F82AEB29058E6D803717827
SHA-256	8ED02159913D07AE6443EA4C96AB99EFFD3A00FE9FDA5B97EC6B1ED033FF9A7B

Key	Value
FileSize	31852
MD5	DBD06CE5B9FB011E13E20724BA72723F
PackageDescription	WebSockets support for any application/server - Python 3 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. . This package provides the Python 3 module.
PackageMaintainer	PKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-7+deb9u1
SHA-1	3332DEB374FCB38B5C404201880AA9B84CA99655
SHA-256	F3C7DA60969B8B85BF961CFA1CC0B8F4956A07AD2EE26A277FDA9A23EDD39F81

Key	Value
FileSize	31854
MD5	AE08971CF170E76B06E25B48C3386070
PackageDescription	WebSockets support for any application/server - Python 3 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. . This package provides the Python 3 module.
PackageMaintainer	PKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-7+deb9u1
SHA-1	337221C35665F0FE780AA5948233174ECE912902
SHA-256	CF6AB2B011F1DFB9276F0341C20989204BFBC35582A797F31F5761FB1B3E3BD7

Key	Value
MD5	DAB76404FBED3F21F8369FE381668251
PackageArch	noarch
PackageDescription	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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-websockify
PackageRelease	lp152.4.4
PackageVersion	0.8.0
SHA-1	49003762CC7E0611CD97E8CCA4DC9058692954C5
SHA-256	BBE77D11D6B4CE04C1E59CAC5409DF23BC95BC715DE5BDE6AFB061894CCD7DA3

Key	Value
MD5	756C9921C8A01F7D3A1AEC0D23838266
PackageArch	noarch
PackageDescription	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.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-websockify
PackageRelease	lp150.1.3
PackageVersion	0.8.0
SHA-1	6ACF1B6A6B6CF57D6152375CF0AC08DBA083E6FE
SHA-256	2E9FA7F0287C6A4FA88A4463C88B7E8730C7174196EDA061A666B4CAE840FA68

Key	Value
MD5	ECEA19BEF3AD7B3AC2921676BE999242
PackageArch	noarch
PackageDescription	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.
PackageName	python3-websockify
PackageRelease	lp150.1.1
PackageVersion	0.8.0
SHA-1	77AB224FD5CA9BF28C6E5E7DBB6EE683AE4B3563
SHA-256	96C03E8BDA62792F4B14350F03B649CA3B28E91204681BA57853A7DBF75B5376

Key	Value
FileSize	31856
MD5	9D3B0D3CE15B203DEC198E7ED2F5F7B2
PackageDescription	WebSockets support for any application/server - Python 3 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. . This package provides the Python 3 module.
PackageMaintainer	PKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-7+deb9u1
SHA-1	8C027862719C69DAF52F6EAEDD9DA92E89CEB6F8
SHA-256	E1E3C89304FB90F22285FD231C2BC235DBED63C8A2497E2BBC63B9520FD66750