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

Allow paths in remote_addr for websocket connections #362

Open
madhavajay opened this issue May 17, 2024 · 1 comment
Open

Allow paths in remote_addr for websocket connections #362

madhavajay opened this issue May 17, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@madhavajay
Copy link

Feature Proposed

[client]
remote_addr = "hostname.com/rathole"

Use Case
Currently websocket connections throw an error if you use a path.

ERROR handle{service=domain}: rathole::client: Failed to run the control channel: invalid port value. Retry in 1.

Since kubernetes won't easily allow a tcp port and we need to share the main 80/433 http port, we need to host rathole on a sub path.

Is this an easy change?

@madhavajay madhavajay added the enhancement New feature or request label May 17, 2024
@PterX
Copy link

PterX commented Aug 19, 2024

good idea

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

No branches or pull requests

2 participants