-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Subscription with Hasura Server #79
Comments
You are not communicating with this library. Our sub-protocol is You are communicating with Make sure that you use this library (or implement the Protocol) both server and client side. |
Hasura's built in subscriptions solution is As this library offers a fundamentally different Protocol, you cannot use their lib and this one interchangeably. |
How can we make it compatible with Hasura ? |
Yap, the server engine from Hasura has to implement this Protocol. I am most certainly bias, but this Protocol feels more reliable and secure than Apollo's; I am even actively working on making it a part of the standard together with the brilliant guys from the official GraphQL over HTTP Work Group. I would've be happy to push a PR, given enough time; however, their server implementation is written in Haskell which I am not familiar with. 😅 Maybe open an issue at their repo? See what they think about this? |
Closing in favour of hasura/graphql-engine#6264. |
Actual Behaviour
Hello,
I have the error :
WebSocket connection to 'the url' failed: Error during WebSocket handshake: 'Sec-WebSocket-Protocol' header value 'graphql-ws' in response does not match any of sent values
Debug Information
I work with Hasura on Heroku.
I just interface graphql-ws with Apollo with your code.
Further Information
Everything was working with ws client from Apollo.
But I had to change because of security issues that your kind work strive to resolve.
The text was updated successfully, but these errors were encountered: