Parents (Total: 48)

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

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	30052
MD5	BACF7EE03D7D96DC1EAB9BE1AF1E735A
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	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-10ubuntu2
SHA-1	0942F94BAE37B68459DEDD97C76FE440B40D8101
SHA-256	62380043F3FC5A6E4811E5FC2DDA2593CD7090B5CBD5886CB999E2A6301F5A38

Key	Value
FileSize	21168
MD5	B0C100131663E169C6B9714255971671
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	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-9
SHA-1	140A34C8FED128FBFEE1ACF99B690DC936F3DA5D
SHA-256	20F427EDF98CF857A1728F4B543761DE4424BCF820BDDFCF500546D69B9706EF

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	37836
MD5	471A0AE03FA0E044A6C564402981FC27
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	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.9.0-0ubuntu2
SHA-1	181034B150E79B90EE4EF48A18AC74287F469057
SHA-256	159B95B83E222A1104821FC5865D0D665C556F5CD72A88F73A08CBE4DB2BDAA9

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	30140
MD5	27CA936ABE0D92894A4C2DB1FE1DF869
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	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python3-websockify
PackageSection	python
PackageVersion	0.8.0+dfsg1-9
SHA-1	1D7C867D1796646FE8F1F7CC06FD8E5D2DD9150A
SHA-256	662E6F3518F3CA802EF9EAD38E67F4A65F58025DAF6CCC293BE162FA062758E6

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