[GH-ISSUE #4702] [Feature Request] 在frpc而不是frps上为http、https类型代理配置端口号,为同域名在多端口上提供多个http/https服务支持 #3709

Closed
opened 2026-05-05 14:22:47 -06:00 by gitea-mirror · 14 comments
Owner

Originally created by @Halo-Michael on GitHub (Mar 7, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4702

Describe the feature request

需求:对于映射到frps的唯一域名,能够在不同的多个端口号上同时提供http/https类型的穿透服务,即:访问指向frps服务器的域名a.com时,通过添加端口号,例如访问https://a.com:443、https://a.com:8443能够分别访问frpc服务器上端口号不同的两个独立的https服务
目前http、https类型穿透是在frps上配置端口号,即对于同一域名,只能在65535个端口中选择唯一端口提供http/https服务。希望可以添加同域名多http/https服务支持。

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 @Halo-Michael on GitHub (Mar 7, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4702 ### Describe the feature request 需求:对于映射到frps的唯一域名,能够在不同的多个端口号上同时提供http/https类型的穿透服务,即:访问指向frps服务器的域名a.com时,通过添加端口号,例如访问https://a.com:443、https://a.com:8443能够分别访问frpc服务器上端口号不同的两个独立的https服务。 目前http、https类型穿透是在frps上配置端口号,即对于同一域名,只能在65535个端口中选择唯一端口提供http/https服务。希望可以添加同域名多http/https服务支持。 ### 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 14:22:47 -06:00
Author
Owner

@xqzr commented on GitHub (Mar 8, 2025):

使用 TCP 类型

<!-- gh-comment-id:2708153498 --> @xqzr commented on GitHub (Mar 8, 2025): 使用 TCP 类型
Author
Owner

@Halo-Michael commented on GitHub (Mar 8, 2025):

使用 TCP 类型

使用tcp类型无法使用http/https类型的各种功能插件

<!-- gh-comment-id:2708162611 --> @Halo-Michael commented on GitHub (Mar 8, 2025): > 使用 TCP 类型 使用tcp类型无法使用http/https类型的各种功能插件
Author
Owner

@Halo-Michael commented on GitHub (Mar 22, 2025):

依然有此需求。比如我在服务器上运行多个提供http/https的服务,依靠端口号来指向不同的服务,并且需要使用subdomain这种功能来分流,达到单服务器通过子域名复用的目的。
并且我觉得没有什么理由frp一个实例只能提供一组http/https服务

<!-- gh-comment-id:2745260246 --> @Halo-Michael commented on GitHub (Mar 22, 2025): 依然有此需求。比如我在服务器上运行多个提供http/https的服务,依靠端口号来指向不同的服务,并且需要使用subdomain这种功能来分流,达到单服务器通过子域名复用的目的。 并且我觉得没有什么理由frp一个实例只能提供一组http/https服务
Author
Owner

@github-actions[bot] commented on GitHub (Apr 6, 2025):

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

<!-- gh-comment-id:2781153037 --> @github-actions[bot] commented on GitHub (Apr 6, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Author
Owner

@Halo-Michael commented on GitHub (Apr 6, 2025):

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

Still in need

<!-- gh-comment-id:2781467759 --> @Halo-Michael commented on GitHub (Apr 6, 2025): > Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close. Still in need
Author
Owner

@github-actions[bot] commented on GitHub (Apr 21, 2025):

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

<!-- gh-comment-id:2817420818 --> @github-actions[bot] commented on GitHub (Apr 21, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Author
Owner

@Halo-Michael commented on GitHub (Apr 22, 2025):

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

Still in need

<!-- gh-comment-id:2820124459 --> @Halo-Michael commented on GitHub (Apr 22, 2025): > Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close. Still in need
Author
Owner

@lvyc1234 commented on GitHub (Apr 22, 2025):

I also think a domain name should support multiple ports to route different HTTP/HTTPS services. I tried to use the routeByHTTPUser field to control different routes, but it didn't take effect. I couldn't route different HTTP services in this way. Hope future versions can support it, thanks

<!-- gh-comment-id:2820432381 --> @lvyc1234 commented on GitHub (Apr 22, 2025): I also think a domain name should support multiple ports to route different HTTP/HTTPS services. I tried to use the routeByHTTPUser field to control different routes, but it didn't take effect. I couldn't route different HTTP services in this way. Hope future versions can support it, thanks
Author
Owner

@taoliujun commented on GitHub (Apr 29, 2025):

need too.

<!-- gh-comment-id:2837852623 --> @taoliujun commented on GitHub (Apr 29, 2025): need too.
Author
Owner

@github-actions[bot] commented on GitHub (May 14, 2025):

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

<!-- gh-comment-id:2878275101 --> @github-actions[bot] commented on GitHub (May 14, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Author
Owner

@Halo-Michael commented on GitHub (May 14, 2025):

Still in need

<!-- gh-comment-id:2878283686 --> @Halo-Michael commented on GitHub (May 14, 2025): Still in need
Author
Owner

@github-actions[bot] commented on GitHub (May 29, 2025):

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

<!-- gh-comment-id:2917917952 --> @github-actions[bot] commented on GitHub (May 29, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Author
Owner

@Halo-Michael commented on GitHub (May 29, 2025):

Still in need

<!-- gh-comment-id:2918123348 --> @Halo-Michael commented on GitHub (May 29, 2025): Still in need
Author
Owner

@github-actions[bot] commented on GitHub (Jun 13, 2025):

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

<!-- gh-comment-id:2968638975 --> @github-actions[bot] commented on GitHub (Jun 13, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#3709
No description provided.