This repository was archived by the owner on Oct 25, 2021. It is now read-only.
Make content type checking less strict#24
Closed
symm wants to merge 1 commit intographql-java:masterfrom
symm:less-strict-content-type
Closed
Make content type checking less strict#24symm wants to merge 1 commit intographql-java:masterfrom symm:less-strict-content-type
symm wants to merge 1 commit intographql-java:masterfrom
symm:less-strict-content-type
Conversation
Contributor
|
I think #13 already solves this. |
Author
|
Thanks @marceloverdijk I opened this smaller change because I saw no activity on that PR since 27 Jun. Happy if either gets merged as long as it gets fixed :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thanks for making
graphql-java-spring👍I've run into an issue when a doing a query with a content-type of
application/json;charset=UTF-8. The GraphQLController rejects the request because strict matching does not like the;charset=UTF-8on the endThis PR updates both controllers to be less strict when checking the incoming content type.