You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The playground insists on sending the query requests on the same URL but via https. For example, in the above case, the requests go to https://192.168.8.102:8539/graphql. This can be observed in the browser's devtools in the network tab.
What steps may we take to reproduce the behavior?
Set up a GraphQL server
Navigate to the playground hosted by the server via localhost and make a query
Now navigate to the playground via the server's IP address (remote or local, doesn't matter) and make a query
The first query works while the second fails. The two images below show the failed request (the first shows the request URL, the second shows the request body).
Please provide a gif or image of the issue for a quicker response/fix.
The text was updated successfully, but these errors were encountered:
This issue pertains to the following package(s):
What OS and OS version are you experiencing the issue(s) on?
Windows 11 21H2
What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
The one that is bundled with GraphQL 16.8.1
What is the expected behavior?
The issue occurs when using the playground with a GraphQL API that is:
For example, if the playground is loaded via http://192.168.8.102:8539/graphql, all query requests should be going to the same URL.
What is the actual behavior?
The playground insists on sending the query requests on the same URL but via https. For example, in the above case, the requests go to https://192.168.8.102:8539/graphql. This can be observed in the browser's devtools in the network tab.
What steps may we take to reproduce the behavior?
The first query works while the second fails. The two images below show the failed request (the first shows the request URL, the second shows the request body).
Please provide a gif or image of the issue for a quicker response/fix.
The text was updated successfully, but these errors were encountered: