Parents (Total: 18)

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

Key	Value
FileSize	23240
MD5	8997CFF4D6203E91A3EB74483DB22E1F
PackageDescription	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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	websockify
PackageSection	python
PackageVersion	0.9.0+dfsg1-3
SHA-1	06531DE49B816FF37AE7701DB8CA15568FBE4734
SHA-256	59F06541EA4E4A58610375FBDC06F49371079AD10E24E489E843B8D9B07CBA50

Key	Value
FileSize	23516
MD5	3624843B1AE67C949D107A63A8AE6684
PackageDescription	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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	websockify
PackageSection	python
PackageVersion	0.9.0+dfsg1-3
SHA-1	2AEC04EB7F622960FDFAD24A7247FF90D7C3F236
SHA-256	8A8F95FD9EA80E82A9BA70F065A15B3FB71185F2AD55C3E533D977EBA28F08D2

Key	Value
FileSize	44124
MD5	DA3EEB4505A7B98C5E8A046CD26481B0
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	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.9.0+dfsg1-3
SHA-1	2EC74072ED4FA7A70B2EFC457181A2709DDC7A11
SHA-256	54FC6BA3F297433122814A209F3C5A5D8362F9EFF55C4099448E700EA7F07C4B

Key	Value
FileSize	44120
MD5	BF15F73A241201AC7412F47566BCF8E0
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	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.9.0+dfsg1-3
SHA-1	40C73E3AAAA238938CBCF5B18BFFBF5D1F30DBA1
SHA-256	E45F227DFEADD65D899DD16AFC108E77FE56116CE2FFC0E55C5632EBDDCBEE2A

Key	Value
FileSize	44120
MD5	FE8410F9641722493CAAE8BAF843FF95
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	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.9.0+dfsg1-3
SHA-1	572355A8ED06C43F8337F349D553D46FE44FC8D6
SHA-256	E0A467488BA2B8A79404E95701577965219C888B806AF978FF3CAA0F682810BC

Key	Value
FileSize	23484
MD5	4E13CAC1DF687FCA3957E0628C997ACE
PackageDescription	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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	websockify
PackageSection	python
PackageVersion	0.9.0+dfsg1-3
SHA-1	5FE6694A8A5D40FDC0C351B5FD2CB9BAEF2047E2
SHA-256	B6D55EDA78E7E329EDFB74FF34B7F79A8AF9F87C7931219F4974425461198F9A

Key	Value
FileSize	23620
MD5	80BCF96135C9BE358C1D5601DBCB93B2
PackageDescription	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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	websockify
PackageSection	python
PackageVersion	0.9.0+dfsg1-3
SHA-1	63470C6A9EE420B174B643AFA3999533DEB7C8CF
SHA-256	E39FF004F1ED8CD51A36D69FEF78579045EAB440C568D5D8260A4BE8E167F4B9

Key	Value
FileSize	23856
MD5	F49493F90369B7991CDC03F532384B16
PackageDescription	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.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	websockify
PackageSection	python
PackageVersion	0.9.0+dfsg1-3
SHA-1	6E5B73D819DDD27D53A07C7D8979FDEBEE7307CD
SHA-256	C0A1C014CAE740CAA8A19DDDA0F1D82F12B928B56AF83395390B436692CB8609

Key	Value
FileSize	44120
MD5	C130535EC85204C616249490EE36DA37
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	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.9.0+dfsg1-3
SHA-1	7EFFF2A8DCEA96E67D39C221FBB8ABC16702D782
SHA-256	F063C8CA71231557FF3CA2A5D3B887E43916609B6D64D606A9E654E7559DDB9E

Key	Value
FileSize	44120
MD5	B47E6C4CCCE5E2ED4197FB0A81467654
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	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.9.0+dfsg1-3
SHA-1	95ABF36BA7F872E31F725704E969DC35DB237B1A
SHA-256	B97EF522A4D76F60AF3814CA4FF98BDEFC17637C562E9A44D4232849684C9BA9