Discussion: Preserving Empty HTTP Header Values vs. Dropping Them#133
Merged
RRQM merged 1 commit intoRRQM:masterfrom Apr 30, 2026
Merged
Discussion: Preserving Empty HTTP Header Values vs. Dropping Them#133RRQM merged 1 commit intoRRQM:masterfrom
RRQM merged 1 commit intoRRQM:masterfrom
Conversation
👷 Deploy request for touchsocket pending review.Visit the deploys page to approve it
|
Owner
|
非常感谢您的贡献! |
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.
This PR changes the behavior of header parsing in
HttpBase:X-Test:) are droppedDiscussion
null""undefined''net/http)""""Benefits:
Drawbacks:
X-Test:as valid when it should be considered missing)So, a decision needs to be made here.