-
Notifications
You must be signed in to change notification settings - Fork 83
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
Expecting wrong websocket subprotocol from client #72
Comments
Confusingly enough, the sub-protocol used by the deprecated subscription-transport-ws library is called graphql-ws while the subprotocol used by the new graphql-ws library is called graphql-transport-ws. Only the old library/sub-protocol is supported by django-channels-graphql-ws |
@stam @jerome-labonte-udem any solution for this problem? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The socket server closes websocket connections from the graphql-ws client library:
While the subprotocol used by this library is not graphql-ws but
graphql-transport-ws
:https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md#communication
The text was updated successfully, but these errors were encountered: