What is the reason for having custom headers in Hasura.io?
Why are there custom headers in hasura graphQL endpoint ? Is there any specific reason for its existence ?
I have created two custom headers and tried to access the endpoint from post I was still able to access the endpoint without mentioning the custom headers which I created. so what is the point of having it?
Got an Answer from the Hasura Team,
Optional custom headers are very useful in authentication and authorization.
For example, if you want to pass session variables as headers, so you can pass header with name x-hasura-* where * would be any string to its corresponding value. Hasura graphql engine will only accept headers which start with x-hasura-* .
You can check more about session variables here - https://hasura.io/docs/latest/auth/authorization/roles-variables/#session-variables
- Datasource is undefined when running the Apollo GraphQL server
- How to use Apollo Client with AppSync?
- missing attribute on result, Vue, Apollo and GraphQL
- Android apollo3 schema not found
- Spring webflux and spring boot starter graphql doesn't return nullable field
- How to know which fields were requested in a GraphQL query?
- GraphQL Apollo Client refusing to not use cache in Next.js
- Apollo GraphQL merge cached data
- Apollo Client client.readQuery returning null when data is in the cache
- Using multiple endpoints in Apollo Client
- Error in Angular components shows loading and not loading using if-else
- What is the default Apollo Client query cache TTL?
- ApolloServer 4: Client Can't Connect to Subscriptions?
- Graphql-Access arguments in child resolvers
- React Apollo dynamically create query from state
- Nextjs - access url params on server side
- Angular Apollo use response from refetch query within a mutation
- How to hide an authentication token on Nuxt.js 2?
- Remix (Vite) unable to import from @apollo/client into .tsx files issue
- GraphQL gql Syntax Error: Expected Name, found }
- Execute GraphQL mutation via Apollo on NuxtJS
- is it safe to use context in graphql resolvers to pass variables to nested types
- NestJS Issue with resolver, throwing undefined
- Unsafe array destructuring of a tuple element with an `any` value using Apollo useQuery
- Apollo graphql, how to count the number of arguments of a graphql request and writes log it with morgan library
- Apollo GraphQL Kotlin Codegen Fragment Serializable
- Context is undefined in Apollo RESTDataSource
- Apollo query subscription doesn't have extensions part in Error
- Call one query and wait for it to finish before calling another one
- Apollo is returning data wrong, but is correct in Network inspector