hasura / hasura/graphql-engine
Actions don't forward set-cookie header?
Open
Nobody has claimed this yet.
a/api/graphql
support/needs-more-info
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Trying to port my login/signup flow to Hasura; Noticed that although there's some github / documentation related comments pointing to the fact that remote schemas should forward set-cookie headers, hasura actions don't forward them.
Any plans on adding support for this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Hasura Actions construct and return responses, then compare that behavior with the documented remote-schema handling of set-cookie headers. Reproduce the login/signup flow and verify that Action responses forward the header without breaking existing responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100