fix(fetch): allow UTF-8 in Location header#30904
Merged
mxschmitt merged 2 commits intoMay 21, 2024
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
yury-s
reviewed
May 20, 2024
yury-s
approved these changes
May 20, 2024
mxschmitt
force-pushed
the
bugfix/fetch-allow-utf8-location-header
branch
from
190dd78 to
b8470e8
Compare
mxschmitt
commented
May 20, 2024
This comment has been minimized.
This comment has been minimized.
Signed-off-by: Max Schmitt <max@schmitt.mx>
Contributor
Test results for "tests 1"1 failed 2 flaky27016 passed, 610 skipped Merge workflow run. |
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
2 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.
This brings up the discussion if we want to post-process all the headers as UTF-8 as well.
Fixes #30903 (comment)