fix: respect TLSSecure setting for VLESS in Clash export#55
Open
tianlang0704 wants to merge 1 commit into
Open
fix: respect TLSSecure setting for VLESS in Clash export#55tianlang0704 wants to merge 1 commit into
tianlang0704 wants to merge 1 commit into
Conversation
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.
Summary
Problem
When converting VLESS nodes to Clash format, the TLS field was hardcoded to true regardless of the input actual TLS setting. This caused VLESS nodes without TLS to incorrectly have TLS enabled in the output.
Solution
Use the TLSSecure property from the parsed proxy node, consistent with how VMess and other proxy types handle TLS.