Do not alter "name" field of Content-Type header #1409
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
When Content-Type header parser fails, it tries to sanitize the value and then parse it again. One step of the sanitization process was to lowercase its value, which could change the meaning of "name" and "filename" fields as upper and lower case characters represent different things.
SamSaffron
reviewed
Sep 9, 2020
jeremy
pushed a commit
that referenced
this pull request
Mar 14, 2021
When Content-Type header parser fails, it tries to sanitize the value and then parse it again. One step of the sanitization process was to lowercase its value, which could change the meaning of "name" and "filename" fields as upper and lower case characters represent different things.
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.
When Content-Type header parser fails, it tries to sanitize the value
and then parse it again. One step of the sanitization process was to
lowercase its value, which could change the meaning of "name" and
"filename" fields as upper and lower case characters represent
different things.