mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 16:15:49 -06:00
[GH-ISSUE #2501] Allow multiple HTTP proxies on different ports #1989
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#1989
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nonnorm on GitHub (Jul 30, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2501
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_portand replace it withremote_porton the client, like with TCP proxies.Application scenarios of this function
Anything requiring multiple HTTP proxies on different ports, (e.g. a Synapse server)
@blizard863 commented on GitHub (Aug 1, 2021):
I don't know this scenarios, maybe it's not a common feature.
@github-actions[bot] commented on GitHub (Sep 1, 2021):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
@nonnorm commented on GitHub (Sep 1, 2021):
bump
@green-codes commented on GitHub (Sep 5, 2021):
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
@github-actions[bot] commented on GitHub (Oct 6, 2021):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
@nonnorm commented on GitHub (Oct 6, 2021):
bump
@github-actions[bot] commented on GitHub (Nov 7, 2021):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
@nonnorm commented on GitHub (Nov 7, 2021):
bump
@github-actions[bot] commented on GitHub (Dec 8, 2021):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
@nonnorm commented on GitHub (Dec 8, 2021):
bump
@github-actions[bot] commented on GitHub (Jan 9, 2022):
Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
@nonnorm commented on GitHub (Jan 9, 2022):
bump
@nonnorm commented on GitHub (Feb 3, 2022):
@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?
@fatedier commented on GitHub (Feb 9, 2022):
It's not necessary to always set type
httpfor your service. Just usetcpinstead.@nonnorm commented on GitHub (Feb 9, 2022):
Yes, however you do need type
httpto set headers, right? My situation is that I have 2httpproxies that need to have different headers set on them.@fatedier commented on GitHub (Feb 9, 2022):
We want to support this scenario in frp v2 since it's very different with current architecture.