-
Notifications
You must be signed in to change notification settings - Fork 321
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
No support for sub-protocols #36
Comments
Can you elaborate on what sub-protocol you are referring to? |
I think I have the same issue here. |
Yes, I have got the same issue. Using a python websocket library to connect with this server the connection drops with an error like this: Traceback (most recent call last): If I check the headers array, my client is not receiving that 'sec-websocket-protocol'. |
Thanks to this great script, I got a websocket server up and running very quickly, so thank a lot for this!
Unfortunately one of the web clients that needs to connect to this, has a sub-protocol defined when setting up the websocket connection.
Is there any support for this in this websocket server?
The text was updated successfully, but these errors were encountered: