[spring-server] fix: handle graphql request with charset coding #425
Conversation
This file contains 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
dariuszkuc
added
type: bug
tapaderster
approved these changes
Oct 11, 2019
…coding In our default GraphQL route we were explicitly checking if `Content-Type` header is just `application/json`. If request was also specifying charset, e.g. `application/json;charset=UTF-8` our logic would fail to match it and result in HTTP 400 (Bad Request) response.
Codecov Report
@@ Coverage Diff @@
## master #425 +/- ##
===========================================
+ Coverage 97.8% 97.8% +<.01%
Complexity 325 325
===========================================
Files 105 105
Lines 1228 1230 +2
Branches 202 202
===========================================
+ Hits 1201 1203 +2
Misses 7 7
Partials 20 20
Continue to review full report at Codecov.
|
dariuszkuc
added a commit
to dariuszkuc/graphql-kotlin
that referenced
this pull request
Aug 5, 2022
…coding (ExpediaGroup#425) In our default GraphQL route we were explicitly checking if `Content-Type` header is just `application/json`. If request was also specifying charset, e.g. `application/json;charset=UTF-8` our logic would fail to match it and result in HTTP 400 (Bad Request) response.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📝 Description
In our default GraphQL route we were explicitly checking if
Content-Typeheader is justapplication/json. If request was also specifying charset, e.g.application/json;charset=UTF-8our logic would fail to match it and result in HTTP 400 (Bad Request) response.