feat: add trusted-proxy-header for vless/trojan listener - #3081
Open
MakostaDev wants to merge 2 commits into
Open
feat: add trusted-proxy-header for vless/trojan listener#3081MakostaDev wants to merge 2 commits into
trusted-proxy-header for vless/trojan listener#3081MakostaDev wants to merge 2 commits 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.
Adding a
trusted-proxy-headeroption for the vless/trojan listeners, allowing mihomo to read the real client IP when it sits behind a reverse proxy (e.g. Nginx/Caddy) that terminates TLS in front of mihomo and forwards the original client IP via a header such asX-Forwarded-For.The Hysteria2 Realm listener already implements this, so the logic was moved into common utils and reused here.
However, this currently only applies to the
WS/gRPC/xHTTPtransports