Add configurable host overrides for exported client links#3814
Open
MrTeeett wants to merge 2 commits intoMHSanaei:mainfrom
Open
Add configurable host overrides for exported client links#3814MrTeeett wants to merge 2 commits intoMHSanaei:mainfrom
MrTeeett wants to merge 2 commits intoMHSanaei:mainfrom
Conversation
|
Useful feature. I'm glad someone developed it. 😁 |
0dc4df2 to
f0f98c7
Compare
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.
What is the pull request?
This pull request introduces configurable host overrides for exported client links and JSON subscriptions.
Previously, the exported client links derived the host from inbound.listen or the HTTP request host header. In setups using wildcard listen addresses (0.0.0.0 / ::), reverse proxies, CDNs, or NAT, this could result in incorrect or inconsistent host values in generated links.
This change adds a deterministic host resolution mechanism with the following priority:
All link generators (vmess, vless, trojan, shadowsocks) and JSON subscription exports now use this unified resolution logic.
The new field is optional and backward compatible.
Which part of the application is affected by the change?
Type of Changes
Screenshots