Request headers to stitched GraphQL API endpoints

[lightstrike]

Does Hasura include URIs in request headers to stitched GraphQL API endpoints? We're specifically looking for when Hasura acts as proxy to WPGraphQL requests. We want to pass a custom header that will be used along with the URI value on the WPGraphQL side.

[dsandip]

@lightstrike Could you please provide an example of the URIs you are looking to include in the request to your remote schema? Also, please check out this section on adding custom headers in the request to your remote schema: https://hasura.io/docs/latest/graphql/core/remote-schemas/adding-schema.html#step-2-merge-remote-schema. Does this work for your use-case?

[lightstrike]

Hi @dsandip, we want to include the origin of the request to Hasura, ie. if we made a request from www.example.com/shop, that URI would be included as a header for the stitched GraphQL service to utilize in a mutation.

[motleydev]

@lightstrike It should be possible to cofigure per this documentation. Can you confirm if this solves the problem for you? https://hasura.io/docs/latest/graphql/core/remote-schemas/auth/remote-schema-forward-auth.html#passing-headers-from-hasura-to-your-remote-schema