Make sure headers are always lowercase to avoid duplicate headers#307
Open
LJ1102 wants to merge 1 commit intoAutomattic:masterfrom
Open
Make sure headers are always lowercase to avoid duplicate headers#307LJ1102 wants to merge 1 commit intoAutomattic:masterfrom
LJ1102 wants to merge 1 commit intoAutomattic:masterfrom
Conversation
Some methods inject headers like 'Content-Length' or 'Content-Type', however in cases where the user provides headers that are not the exact same casing(eg. 'Content-type' instead of 'Content-Type') both headers were sent, in cases where their content did not match this resulted in S3 resetting the connection without a clear error message.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Some methods inject headers like 'Content-Length' or 'Content-Type',
however when the user provided headers were not the exact
same casing(eg. 'Content-type' instead of 'Content-Type') both headers
were sent, in cases where their content did not match this resulted in S3
resetting the connection without a clear error message.