Expand valid JSON content types #16
Open
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
Before the library required that the content-type of a JSON request to be "application/json", however by the spec, mime-subtypes of application json (Those ending in `+json` like `application/vnd.api+json` are also valid json types.
cibernox
force-pushed
the
expand-valid-json-content-headers
branch
from
c0357a3 to
60ebc67
Compare
4 tasks
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.
Before the library required that the content-type of a JSON request to be
"application/json", however by the spec, mime-subtypes of application json
(Those ending in
+jsonlikeapplication/vnd.api+jsonare also valid json types.