[GH-ISSUE #3086] [Feature Request]

gitea-mirror commented

2026-05-05 13:35:22 -06:00

Owner

Copy link

Originally created by @touchmii on GitHub (Sep 1, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3086

Describe the feature request

能否通过定义path路由到不同的端口，类似nginx的location，目前的locations配置好想没有这个作用。

想要实现通过访问vhost端口加定义路径就能替代subdomain的作用直接路径到指定服务，如下面的配置
访问 x.x.x.x:80/web1 可以替代 web1.domain.com:80的效果，虽然可以使用nginx反向代理来实现，但是
配置多个服务还是不太方便，想要使用path主要是考虑想走cdn，这样只需一个域名即可。

[web1]
type = http
local_ip = 127.0.0.1
local_port = 8080
#remote_port = 17400
#subdomain = web1
#locations = /web1
path = /web1

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @touchmii on GitHub (Sep 1, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3086 ### Describe the feature request 能否通过定义path路由到不同的端口，类似nginx的location，目前的locations配置好想没有这个作用。想要实现通过访问vhost端口加定义路径就能替代subdomain的作用直接路径到指定服务，如下面的配置访问 x.x.x.x:80/web1 可以替代 web1.domain.com:80的效果，虽然可以使用nginx反向代理来实现，但是配置多个服务还是不太方便，想要使用path主要是考虑想走cdn，这样只需一个域名即可。 [web1] type = http local_ip = 127.0.0.1 local_port = 8080 #remote_port = 17400 #subdomain = web1 #locations = /web1 path = /web1 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:35:22 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:35:25 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Oct 2, 2022):

Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Oct 2, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified