-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSL by default, failover to plain #140
Comments
One slight complication with this for now, is that ws4py is using
There's a fix for ws4py in Lawouach/WebSocket-for-Python#283, but I wonder if it might otherwise be worth looking at migrating to another websocket library that is kept more up to date, as ws4py hasn't had a release since 2018? |
@Tenzer ws4py was the only one I found that I could make work - specifically, I had to exclude default headers in order to make it work back on webOS 2.x IIRC. You'll find this in the code where exclude_headers=['Origin'] IIRC, which was always being sent by ws4py (it IS part of the spec, so you can't blame them). This is in itself a bit of a hack, and was likely due to a bug in the webOS web socket server libraries and may now have been fixed. |
Is there any workaround with this? I tried @cmer 's suggestion of rolling back to Python 3.6 but got the following error: % brew install [email protected] |
The problem only exists with Python 3.12, so try version 3.11 for now. |
That worked! Thank you! |
I'm sorry, but the real fix is Not all of us can afford to use ancient versions of python. |
Some devices will support SSL, some will not, of those which do, some may support plaintext. It makes most sense for us to take the most secure option and failover to the least secure option.
The text was updated successfully, but these errors were encountered: