Bug #9603
closed
Setting called websockets_encrypt does not work correctly
Description
When you set websockets_encrypt to false (via settings or even installer) and leave the websockets_ssl_cert/key settings as is (they default to puppet cert/key), console will not work. The flag not to encrypt the communication will be passed to the HTML5 component correctly, but the websockify program will be always spawned with certificates, therefore dropping non-secured connection.
Updated by Lukas Zapletal about 10 years ago
- Subject changed from Websocketify spawner does not honor websockets_encrypt setting to Setting called websockets_encrypt does not work correctly
It's more complex, filed a patch already. Initially I set the Category to CR, but it did not seem like a good fit. Console could be better (as it can be bug in websocketify). Anyway, thanks :-)
Updated by Dominic Cleal about 10 years ago
That's OK, I usually use the CR category for console related things. Web Interface gets over-used :)
Updated by
Updated by Lukas Zapletal almost 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 97c34475c9e674db6443b28e03a5e4d94d585f2e.
Updated by