Subscriptions didn't work with my GraphQL Server until I added an empty Payload to the connection init.

Question

Subscriptions didn't work with my GraphQL Server until I added an empty Payload to the connection init.

mkuhr opened this issue 3 years ago · comments

mkuhr commented 3 years ago

Navid Kabir · Answer 1 · Mon Sep 13 2021 06:19:20 GMT+0800 (China Standard Time)

What server are you using? Is this standard protocol?

mkuhr · Answer 2 · Mon Sep 13 2021 16:04:47 GMT+0800 (China Standard Time)

it was https://dgraph.io/ and same behaviour on the selfhosted one in docker.
I dont know about subscription ws protocoll standards. had to find out why it wasnt working using wireshark and graphiql.

The difference is in my title. Your Plugin didnt send the empty payload and all graphiql did.

This plugin rocks. Thanks for it

Navid Kabir · Answer 3 · Mon Sep 13 2021 16:13:14 GMT+0800 (China Standard Time)

it was https://dgraph.io/ and same behaviour on the selfhosted one in docker.
I dont know about subscription ws protocoll standards. had to find out why it wasnt working using wireshark and graphiql.

The difference is in my title. Your Plugin didnt send the empty payload and all graphiql did.

This plugin rocks. Thanks for it

I asked because I'm not sure about the subscription WS protocol standards either. 😅
Thanks for the additional information! It helps a lot. It seems like a bug on our end, so we can get it fixed.

This change probably shouldn't affect any other kinds of graphql servers either.