Parents (Total: 62)

The searched file hash is included in 62 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
FileSize	24256
MD5	24827469AFD902150A57E5605D8CFDE6
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 <openstack-devel@lists.alioth.debian.org>
PackageName	websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-10
SHA-1	06417F3B096CD6A542D5884706E5D4BF9F4D72EF
SHA-256	A172E1E5A0491350A2132533847CD5E48B4CFE73022C243F86A2D2861C2123CB

Key	Value
FileSize	32028
MD5	F8128856DCCECA01E1C95301FA31554E
PackageDescription	WebSockets support for any application/server - Python 2 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 2 module.
PackageMaintainer	Debian OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-10
SHA-1	07EC0CF334E9E1D2F559E5FE88D3F041FF37E916
SHA-256	AFF60A057C7A3DFBCBFEB1DB334E4AB8C67FC50EF172FE63AA07B870DAF0F93D

Key	Value
FileSize	24122
MD5	0BA565F58823E72B46D71634117E3C80
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	PKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-7+deb9u1
SHA-1	0E444D4A6D2D75C2E0D284538325327E7E51D36F
SHA-256	737FFEAB9225EF2D08B4F2351282C7C3112A035DD66A2E01F498D7B2E0D4E331

Key	Value
FileSize	32108
MD5	6DE9F5A4AFF92DD4D5E99AF669B41ACF
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 <openstack-devel@lists.alioth.debian.org>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-10
SHA-1	15F49C84E46B3608C39F85E88822ED14F736D057
SHA-256	8F46C39BA1DFE8A033E3F30B17FAE96B0B922770268EABC6DB71A8E91C31A649

Key	Value
FileSize	24776
MD5	8CCBDDCB1E34DA877F37229929DCEC30
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 <openstack-devel@lists.alioth.debian.org>
PackageName	websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-10
SHA-1	18923569C1FA50E45D8796519146B8F9E216F2ED
SHA-256	D1E6FFFF9EAD6F799ABFAE17F6B273ED61A8B6287762227C16AC55977DEAAFDD

Key	Value
FileSize	31838
MD5	2AE223F1B54D31EA6DACD95234D203F7
PackageDescription	WebSockets support for any application/server - Python 2 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 2 module.
PackageMaintainer	PKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-7+deb9u1
SHA-1	1D12FDB21A85349EBBB622B47DA7FD20CE309433
SHA-256	C0874E46488B8D9024B6CB73F2925A7D9C404781BCB828262711DCB7EF27FF44

Key	Value
FileSize	24356
MD5	396CC1590CCC21A2A694DAF40C4BA0CA
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 <openstack-devel@lists.alioth.debian.org>
PackageName	websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-10
SHA-1	1DE0E2E002361F296C662738E9CB7A58D57A3685
SHA-256	7A1BDF3386E650C5D352E1BD41A09752471925D53DDDCB98C0F15A7FD3807238

Key	Value
FileSize	32028
MD5	D40604B55CE8683ECD2AF0DFB7EAB524
PackageDescription	WebSockets support for any application/server - Python 2 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 2 module.
PackageMaintainer	Debian OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-10
SHA-1	1E1F8E3F7A68601CF2A41DB2E83EC38BB19A6382
SHA-256	0D0C9F50BE05B65204DB1141BA2AF5B233D630888F5D0057BCAB1F1B54F58838

Key	Value
FileSize	29028
MD5	DBF32D0A8D42373FBE64A284A5B42F8D
PackageDescription	WebSockets support for any application/server - shared files 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 common files for Python 2 and 3 modules.
PackageMaintainer	PKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	websockify-common
PackageSection	python
PackageVersion	0.8.0+dfsg1-7+deb9u1
SHA-1	22CBDC28E8103F8A808B04EE11509A24A958F7C1
SHA-256	E29B5FA1D01FC97E5873E1F18ACC328349B6DC59A0A80FFE057D2B3B554D1B48