This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
More intelligent Content-Type parsing #1660
Merged
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
Content-Type is allowed to contain options (`; charset=utf-8`, for instance). We should allow that.
richvdh
force-pushed
the
rav/better_content_type_validation
branch
from
3853ce2
to
b5b3a7e
Compare
|
I don't think the LGTM if it works. |
|
Though if you want to nitpick, the RFC does say:
In this case adding one does have an effect on the recipient :D |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Content-Type is allowed to contain options (
; charset=utf-8, forinstance). We should allow that.