-
Notifications
You must be signed in to change notification settings - Fork 202
Open
Description
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.
Metadata
Metadata
Assignees
Labels
No labels