Detect JSON content-type with parameters - #350
Merged
Merged
Conversation
bajtos
force-pushed
the
fix/json-body-detection
branch
from
September 13, 2016 13:29
428ae60 to
60e0574
Compare
Contributor
|
LGTM |
Fix the detection of JSON content type used to decide whether sloppy
coercion should be applied, so that it correctly supports values with
parameters. For example:
application/json;charset=UTF-8
bajtos
force-pushed
the
fix/json-body-detection
branch
from
September 14, 2016 09:09
60e0574 to
42855c5
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix the detection of JSON content type used to decide whether sloppy
coercion should be applied, so that it correctly supports values with
parameters. For example:
Connect to #267
@richardpringle please review
cc @ebourmalo