fix(headers): trim trailing CRLF in normalized header values#7456
Merged
jasonsaayman merged 1 commit intoaxios:v1.xfrom Mar 1, 2026
Merged
Conversation
Contributor
Author
|
Quick follow-up: this is a narrow normalization fix with targeted regression tests for trailing CR/LF header values. If maintainers want any style or scope adjustment, I can update immediately. |
jasonsaayman
approved these changes
Mar 1, 2026
Member
jasonsaayman
left a comment
There was a problem hiding this comment.
Hi 👋
This PR LGTM 🔥 !
Thanks for your contribution to axios
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
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.
Summary
\r/\nfrom normalized header values inAxiosHeadersnull/falseand array valuesWhy
Issue #7455 reports response header values containing trailing carriage-return characters (
\r) after upgrade.Testing
npm run test:mocha -- test/unit/core/AxiosHeaders.jsFixes #7455