Open jasonawant opened 5 months ago
It appears that within Drupal.behaviors.graphQLRenderExplorer here, the fetch request does not use the graphiql supported explorer headers.
It looks like the fetch assigns its own headers.
// Defines a GraphQL fetcher using the fetch API. const graphQLFetcher = graphQLParams => fetch(settings.graphqlRequestUrl, { method: 'post', credentials: 'same-origin', body: JSON.stringify(graphQLParams), headers: { 'Content-Type': 'application/json', }, }).then(response => response.json());
graphiql supports sending custom request headers through its UI as seen in the screen shot below.
Am I looking at this correctly?
It would be sweet to send custom request headers, e.g. Authorization bearer tokens with the request.
It appears that within Drupal.behaviors.graphQLRenderExplorer here, the fetch request does not use the graphiql supported explorer headers.
It looks like the fetch assigns its own headers.
graphiql supports sending custom request headers through its UI as seen in the screen shot below.![image](https://github.com/drupal-graphql/graphql/assets/4835629/34445436-38e1-41b7-b986-079e041eece8)
Am I looking at this correctly?
It would be sweet to send custom request headers, e.g. Authorization bearer tokens with the request.