-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix cache-control header parsing for JWK (fix #3655) #3676
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
fix cache-control header parsing for JWK (fix #3655) #3676
Conversation
|
Deploy preview for hasura-docs ready! Built with commit 6cd347c |
write a proper parser according to the RFC https://tools.ietf.org/html/rfc7234#section-5.2
63b50e8 to
059c563
Compare
|
Review app for commit 059c563 deployed to Heroku: https://hge-ci-pull-3676.herokuapp.com |
|
Review app for commit 4ea4d1e deployed to Heroku: https://hge-ci-pull-3676.herokuapp.com |
1fa8886 to
337ac8c
Compare
lexi-lambda
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.
Thanks! This looks great. 🙂
|
Review app for commit 6cd347c deployed to Heroku: https://hge-ci-pull-3676.herokuapp.com |
|
Review app https://hge-ci-pull-3676.herokuapp.com is deleted |
write a proper parser according to the RFC https://tools.ietf.org/html/rfc7234#section-5.2
Description
Write a proper parser according to the RFC https://tools.ietf.org/html/rfc7234#section-5.2
TODO: handle extended ASCII setThis is not required as per https://tools.ietf.org/html/rfc7230#section-1.2Affected components
Related Issues
#3655
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
run_sqlauto manages the new metadata through schema diffing?run_sqlauto manages the definitions of metadata on renaming?export_metadata/replace_metadatasupports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
querytypes:argspayload which is not backward compatibleJSONschemaGraphQL API
Schema Generation:
NamedTypeSchema Resolve:-
nullvalue for any input fieldsLogging
JSONschema has changedtypenames have changed