Graphql-playground: Security Consideration: subscriptions.graphql.cool

Created on 25 Jan 2018  路  4Comments  路  Source: graphql/graphql-playground

Hey,

i am using GraphQL Playground HTML in version 1.2.0 (absinthe/graphql-playground). I was wondering why the playground is connecting (by default) to a websocket at wss://subscriptions.graph.cool. Could you please explain why this is necessary?

screenshot_playground

//cc @benwilson512

Most helpful comment

@johannestroeger My apologies for that weird behavior in the playground. That endpoint you can see there was used for testing, if a websocket endpoint is valid. I just removed it and replaced it with the correct value (which is the subscriptionsEndpoint), it will be released today or tomorrow.

All 4 comments

inquiring minds want to know

@johannestroeger My apologies for that weird behavior in the playground. That endpoint you can see there was used for testing, if a websocket endpoint is valid. I just removed it and replaced it with the correct value (which is the subscriptionsEndpoint), it will be released today or tomorrow.

Excellent, glad to hear it!

Fixed in the latest version. Please let us know if you still have that issue, then we reopen it!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

divyenduz picture divyenduz  路  4Comments

DarkLite1 picture DarkLite1  路  3Comments

niklasR picture niklasR  路  3Comments

elektro1103 picture elektro1103  路  4Comments

deathg0d picture deathg0d  路  3Comments