Repository navigation
Filter control characters in encoded HTTP/1 output lines - #725
Merged
arturobernalg merged 1 commit intoOct 22, 2026
Merged
Conversation
ok2c
reviewed
Oct 21, 2026
arturobernalg
force-pushed
the
http1-encoded-control-characters
branch
from
October 21, 2026 13:54
8a5fdc8 to
857d162
Compare
ok2c
approved these changes
Oct 21, 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
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.
Prevent control characters from being emitted in HTTP/1 output lines when an explicit charset encoder is configured.
Apply the same filtering as the default encoding path in both classic and async session output buffers, without affecting binary output or introducing additional overhead in the default path.