fix(curl): trim HTTP response header values#1675
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
JoshuaMoelans
approved these changes
Apr 28, 2026
mujacica
approved these changes
Apr 28, 2026
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
3 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.
Fixes the CURL transport to trim whitespace around response header values (other transports parse HTTP headers correctly).
For example,
Retry-After: 60\r\nwas stored as" 60\r\n". While this was harmless for existing numeric rate-limit headers becausestrtoll()ignores whitespace, it breaks string-valued headers. For example, TUSLocation:Location: /foo/bar\r\nwould be stored as" /foo/bar\r\n", which is not a valid location.Extracted from:
#skip-changelog