-
-
Notifications
You must be signed in to change notification settings - Fork 13k
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 multiple HTTP proxies on different ports #2501
Comments
I don't know this scenarios, maybe it's not a common feature. |
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close. |
bump |
I'm running many http proxies on the same host with no problem. Just use type=http(s) and different ports for each service. remember to set vhost in frps |
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close. |
bump |
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close. |
bump |
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close. |
bump |
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close. |
bump |
@green-codes, yes, but can't you only have one vhost? Doesn't that mean that all of the proxies would go to the same port? |
It's not necessary to always set type |
Yes, however you do need type |
We want to support this scenario in frp v2 since it's very different with current architecture. |
The solution you want
The ability to have multiple HTTP proxies on different remote ports.
Alternatives considered
Giving the HTTPS type proxy the same options as HTTP type proxies, but that would still only allow 2 remote ports.
How to implement this function
Remove
vhost_http_port
and replace it withremote_port
on the client, like with TCP proxies.Application scenarios of this function
Anything requiring multiple HTTP proxies on different ports, (e.g. a Synapse server)
The text was updated successfully, but these errors were encountered: