anytls: protocol version 2 #1936
Merged
Conversation
This file contains 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.
fix: stream close
Fix potential deadlock issues
Update Default Padding Schme
Updated to a more scientific scenario
Protocol version 2
中文说明
The main purpose of this protocol update is to handle tunnel jamming issues and server status feedback. Improve proxy behavior in complex network situations such as #1891.
With this design, the timeout behavior of the AnyTLS proxy will be the same as that of traditional 1:1 proxy such as Shadowsocks, i.e., the proxy software is responsible for the timeout when opening the “user-to-proxy” connection, and the original user agent is responsible for the timeout after opening it.
Since this PR also implements a negotiation mechanism, the v2 feature should only be enabled if both your server and client support version 2. Otherwise, both ends will run according to version 1. Therefore, it will not cause compatibility issues.