Case insensitive multipart request header lookup #518
Merged
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.
Treat
Content-Type
andContent-Disposition
header names as caseinsensitive when parsing the parts of multipart requests. These names
were previously treated as case sensitive which causes parsing problems
when attempting to parse requests that may use all lower case header
names.
I hit this problem yesterday when trying to process a multipart request
composed with a library that sends all the part header field names as
lower case. Most libraries use the expected camel case for the header names, but
RFC 2616 and RFC 7230 both say the header field names are case insensitive so
I made this small change to address it.