fix(http): Make Content-Type header case insensitive
#56541
Closed
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
JeanMeche
added
action: review
JoostK
reviewed
Jun 21, 2024
Prior to this change, is the `Content-Type` passed to the `FetchBackend` was lowercase it was overwritten with the default one. fixes angular#56539
JeanMeche
force-pushed
the
http-content-type-insensitive
branch
from
6d00d98
to
97f6761
Compare
JoostK
approved these changes
Jun 21, 2024
AndrewKushnir
approved these changes
Jun 22, 2024
AndrewKushnir
added
action: presubmit
AndrewKushnir
added
action: merge
|
This PR was merged into the repository by commit cc21989. The changes were merged into the following branches: main |
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.
Prior to this change, is the
Content-Typepassed to theFetchBackendwas lowercase it was overwritten with the default one.fixes #56539