Skip to content

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

@1var0

Description

@1var0

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions