We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I'm using this against an endpoint that enforces authorisation in all requests. This is straightforward in the plain HTTP connections but WebSocket works differently - see here for example: https://www.apollographql.com/docs/graphql-subscriptions/authentication/
It would be really helpful if the WebSocketEndpoint constructor allowed a dictionary to be passed that could be used in the connection_init message.
WebSocketEndpoint
connection_init
I have forked the project and implemented this (with a test) so if you think it would be useful I can create a pull request for you.
Cheers, Ray
The text was updated successfully, but these errors were encountered:
sure, send a patch. I didn't write the websocket myself, I thought it was all handled in the ws_options.
ws_options
Sorry, something went wrong.
I initially thought it would be that way too. Pull request is now added.
Thanks.
barbieri
No branches or pull requests
Hi,
I'm using this against an endpoint that enforces authorisation in all requests. This is straightforward in the plain HTTP connections but WebSocket works differently - see here for example: https://www.apollographql.com/docs/graphql-subscriptions/authentication/
It would be really helpful if the
WebSocketEndpoint
constructor allowed a dictionary to be passed that could be used in theconnection_init
message.I have forked the project and implemented this (with a test) so if you think it would be useful I can create a pull request for you.
Cheers,
Ray
The text was updated successfully, but these errors were encountered: