-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set-Cookie headers not proxied back #60
Comments
Only cookie based authorization patterns will be broken. If your auth depends on mutation return auth token to pass in future request's header, it will still work. This is a new feature request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I can pass headers from the client to the proxied endpoint, but headers are not proxied back. In particular set-cookie headers are not proxied back making any authentication graphql broke.
The text was updated successfully, but these errors were encountered: