Parents (Total: 24)

The searched file hash is included in 24 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	24096
MD5	8A34B0412EA61846E1C577A090078DB4
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.10.0+dfsg1-2
SHA-1	0CCF6ACA526958BE786F64068A10FE41DA5817D7
SHA-256	C2BFC3373A415FD62FFA7CE90EC4B493A90CE40CB0C5DD9666FD96B99D469E78

Key	Value
FileSize	23656
MD5	F30976359A9269737519F0C1C229FBD0
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.10.0+dfsg1-2
SHA-1	0E095AC4F301724DFF1FC0CCB4CE2377FC12A297
SHA-256	273B04F1C2895B33A46A2118D72FF41E90EDB1FEBA09F6E42B52FE18717DE521

Key	Value
MD5	47297EA569AAFD80B824AFE73683413E
PackageArch	noarch
PackageDescription	Python WSGI based adapter for the Websockets protocol - Python 3 version
PackageMaintainer	CBS <cbs@centos.org>
PackageName	python3-websockify
PackageRelease	1.el8
PackageVersion	0.9.0
SHA-1	1AB8B578F54C24487918B08BA4F25B7362EA8D9C
SHA-256	8E2A8189D4B71FE3223142B52120446F0209914246B4D8F1E3332DFCA8C274AB

Key	Value
FileSize	23672
MD5	7312AECF5A6FD2F54AC135F950609412
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.10.0+dfsg1-2
SHA-1	245CCE6ABEDC2ED29ABCF8369BE56CA4B8165CBC
SHA-256	189BEA38D7F0F95FD586A57B3161AC8B2F52A4242E5E52311F2FC3F32F9257B5

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	23568
MD5	C8A362EA4DDA7669A43092C0B59417A5
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.10.0+dfsg1-2
SHA-1	4DF1E8D17D644E62D26E62EB867A579977D566C5
SHA-256	4713E063EBB90E7CCA0AB0D9BDF73D60F9ECC123F61A26C1C2F2281B667F0884

Key	Value
FileSize	23808
MD5	71D1E7BB59C21A4DDCCE86C8E1174B91
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.10.0+dfsg1-2
SHA-1	56E9CEAB3472D57220A5951385224881C278AE9D
SHA-256	421A03CA75A436E143983C157DCCFF688595238C0742DFB4AB5D9692D6D803C3

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