Changed the check for content-type json to allow for charsets to be s… #252
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
|
|
|
Hi @bkwint, Thank you for raising this PR. We will review it soon and provide you with feedback. @tasso94 or @danielkelemen, can you take over this review? Best, |
|
@danielkelemen, this might be a good chance to get to know the codebase a little better. WDYT? |
Sure, I can take it over. |
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.
Current code does not allow for proper header settings in the Content-Type. If Content-Type is set to "application/json; charset=utf-8" the task will not be properly forwarded to the handler callback. By changing the code to only check the start o the Content-Type we accept any charsets that are send.