Bizzycola

If you supply the Authorization header in the playground, it will still be sent with the websocket request, just not as an HTTP header. Rather, it will be send as...

@CDRayn You _kind of_ can pass headers in on page load if you manually invoke playground, within the init method: ``` GraphQLPlayground.init(root, { endpoint: "urltographqlhere", headers: { Authorization: `Bearer jwttokenhere`,...

@tonyabracadabra Yea, playground seems to send the Authorization header as the socket init payload when connecting subscriptions. When receiving the payload, it was received as `{"Authorization": "Bearer ..."}`. in ASP.Net...

Websockets cannot send headers, the spec doesn't allow it and browsers don't support it. When you connect a subscription, rather than sending Authorization as a header, Playground sends it with...

@lanwin That could be a viable way to handle it. I've not tested if Playground includes any headers other than Authorization in the payload so could be worth a try....

I'll take a look at this, but it's all run clientside so I might have to add something in the build process to modify the HTML based on an env,...

I'll have a look into how these work and see if I can add an option for it.

The only comment I have here for an uncertainty is what to do if no input is supplied. To prevent breaking anything, it seems the best idea would be to...