Making request with mixed case headers can mess up request #157
Conversation
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
I.e. when making a request with "Content-Type": "application/multipart", the content type will not be matched correctly and the serializer for "application/json" will be incorrectly applied to the body. The same problem happens for the "accept" header, if the content type is parsed correctly, but "Accept" in the params uses an uppercase "A". The workaround for those issues for now is to simply use only lowercase headers, and no atoms.
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.
I.e. when making a request with "Content-Type": "application/multipart",
the content type will not be matched correctly and the serializer for
"application/json" will be incorrectly applied to the body.
The same problem happens for the "accept" header, if the content type
is parsed correctly, but "Accept" in the params uses an uppercase "A".
The workaround for those issues for now is to simply use only lowercase
headers, and no atoms.