-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix duplicate headers being sent to remote schema #2118
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
Conversation
following is the order of precedence of headers now: conf headers > resolved userinfo vars > client headers
|
Deploy preview for hasura-docs ready! Built with commit 25a118e |
|
Review app for commit 51fc1bf deployed to Heroku: https://hge-ci-pull-2118.herokuapp.com |
|
Review app for commit de84ff0 deployed to Heroku: https://hge-ci-pull-2118.herokuapp.com |
de84ff0 to
9a1a4e1
Compare
|
Review app for commit c9c73fe deployed to Heroku: https://hge-ci-pull-2118.herokuapp.com |
rikinsk-zz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docs LGTM
|
Review app for commit 25a118e deployed to Heroku: https://hge-ci-pull-2118.herokuapp.com |
|
Review app https://hge-ci-pull-2118.herokuapp.com is deleted |
Description
In some cases,
x-hasura-*headers and configured headers were sent with multiple values to remote schema.Following is the order of precedence of headers now:
conf headers > resolved userinfo vars > client headers
Affected components
Related Issues
Solution and Design
Remove duplicates by merging them in a map. The order of precedence is:
conf headers > resolved userinfo vars > client headers
Steps to test and verify
Limitations, known bugs & workarounds