Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Function as a reverse or sni proxy for web servers? #6

Open
1var0 opened this issue Nov 7, 2018 · 0 comments
Open

Function as a reverse or sni proxy for web servers? #6

1var0 opened this issue Nov 7, 2018 · 0 comments

Comments

@1var0
Copy link
Contributor

1var0 commented Nov 7, 2018

With hostname extraction and tcp forwarding already implemented, with a little work it can be made to proxy web services.
Add a new type of relay named tcp. It appears as a single endpoint to clients. While with the already-implemented socks5 proxy, clients get to choose where to connect.
Rules can be configured in the same way, though of the existing conditional rules, it seems only cond domain makes sense here. In the future, if we can write rules concerning client ip addresses, it may also be useful.
Add a new type of egress that's also just a single endpoint. It can be called tcp. Though actually it's kind of redundant, we can't forward tcp connections to anything other than tcp sockets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant