[GH-ISSUE #3965] [Feature Request] 可配置 Websockets 路径

gitea-mirror commented

2026-05-05 14:02:12 -06:00

Owner

Copy link

Originally created by @fanthos on GitHub (Feb 1, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/3965

Describe the feature request

根据代码描述，FrpWebsocketPath是固定的/~!frp。希望将这个放到配置文件中，可以使用反向代理（如nginx）在同一个端口使用多个frp后端。

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 @fanthos on GitHub (Feb 1, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/3965 ### Describe the feature request 根据代码描述，`FrpWebsocketPath`是固定的`/~!frp`。希望将这个放到配置文件中，可以使用反向代理（如nginx）在同一个端口使用多个frp后端。 ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [X] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:02:12 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:02:15 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Feb 21, 2024):

这样的参数暴露的越多，对之后的维护负担就越重，所以目前倾向于尽量不对用户暴露非必要的一些参数。

这个场景中，建议可以可以考虑通过 host 实现端口复用。

@fatedier commented on GitHub (Feb 21, 2024): 这样的参数暴露的越多，对之后的维护负担就越重，所以目前倾向于尽量不对用户暴露非必要的一些参数。这个场景中，建议可以可以考虑通过 host 实现端口复用。

gitea-mirror commented

2026-05-05 14:02:17 -06:00

Author

Owner

Copy link

@fanthos commented on GitHub (Feb 22, 2024):

之前考虑过使用host进行复用，但是如果前面有cdn或者其他反代服务时候，host不能随意改。

@fanthos commented on GitHub (Feb 22, 2024): 之前考虑过使用host进行复用，但是如果前面有cdn或者其他反代服务时候，host不能随意改。

gitea-mirror commented

2026-05-05 14:02:18 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Mar 15, 2024):

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

@github-actions[bot] commented on GitHub (Mar 15, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:46:49 -06:00

[PR #3146] [MERGED] bump version #4688

No Branch/Tag specified