feat: enable h2c support for HTTP masquerade#1505
Open
wellcoming wants to merge 1 commit intoapernet:masterfrom
Open
feat: enable h2c support for HTTP masquerade#1505wellcoming wants to merge 1 commit intoapernet:masterfrom
wellcoming wants to merge 1 commit intoapernet:masterfrom
Conversation
wellcoming
changed the title
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
1 participant
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.
Description
This PR introduces
h2c(HTTP/2 Cleartext) support to the MasqTCPServer.By wrapping the standard HTTP handler with
h2c.NewHandler, the server can now correctly handle both HTTP/1.1 and HTTP/2 requests over non-TLS TCP connections.Motivation & Context
This improvement is crucial for coexistence with other proxy software, specifically Xray.
When configuring Xray's fallback mechanism, it often forwards traffic in either
http/1.1orh2(HTTP/2) format depending on the incoming connection. Previously, withouth2csupport,h2fallback requests from Xray would fail or be malformed because the masquerade server expected standard HTTP/1.1.With this change, Hysteria's masquerade server can now accept
h2fallbacks from Xray, allowing for a robust fallback chain (e.g., Xray -> Hysteria Masq).