Fix: Duplicate Content-Type header when Content-Type header is capitalized. #154
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 a
Content-Type
header exists in aincomingRequest
object that is passed into thefetch
function, we will receive a duplicate lowercasecontent-type
header.Here is where the error occurs in the source code
What my proposed change does is it checks for the capitalized
Content-Type
header, if it exists we create a lowercasecontent-type
header and delete the capitalized one.Alternatively, we could just change the above if statement to: