Add optional VLESS flow parameter#494
Open
SafaSafari wants to merge 1 commit into
Open
Conversation
VLESS outbounds always sent the "xtls-rprx-vision" flow in the request header and wrapped the stream in the Vision parser. The flow was hardcoded, with no way to turn it off. Vision operates on the raw TLS stream and only works with the plain TCP transport; it cannot be used with WebSocket, gRPC or HTTP/2. With the flow forced on, vless outbounds over those transports could not work. Add a `flow` field to VlessOutboundSettings so the choice is left to the user. When empty or absent the outbound sends no addons (addon length 0) and the Vision wrapper is disabled; setting it to "xtls-rprx-vision" restores the previous behaviour.
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.
VLESS outbounds always sent the
xtls-rprx-visionflow in the request header and wrapped the stream in the Vision parser. The flow was hardcoded, with no way to turn it off.Vision operates on the raw TLS stream and only works with the plain TCP transport — it cannot be used with WebSocket, gRPC or HTTP/2 (see Project X docs). With the flow forced on, vless outbounds over those transports could not work at all.
Since enabling Vision is a deployment choice, it is better left to the user. This adds a
flowfield toVlessOutboundSettings:0x00) and the Vision wrapper is disabled — works with any transport;"xtls-rprx-vision"→ restores the previous behaviour.The default is empty (no flow).