[GH-ISSUE #3396] [Feature Request] tcpmux文档使用疑惑

gitea-mirror commented

2026-05-05 13:45:09 -06:00

Owner

Copy link

Originally created by @alkaid-ops on GitHub (Apr 10, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3396

Describe the feature request

通过上面的配置，frps 如果接收到 HTTP CONNECT 请求内容:
CONNECT test1 HTTP/1.1\r\n\r\n
该连接将会被路由到 proxy1 。

我是初学者可能有些误区:

http connect 是 http 1.1 建立tcp隧道的特殊请求
type tcpmux 是不是 listen同端口，根据Host的不同进行路由的tcp转发？(类似ningx hostname)
我该怎样使用测试它？

curl 和浏览器直接访问我看到了连接和关闭怎么看有没有被frp route到frpc那边
我用tcpmux代理nginx\ssh\squid都没成功，我该如何使用它？
[proxy1]
type = tcpmux
multiplexer = httpconnect
custom_domains = nginx
local_port = 80
[proxy2]
type = tcpmux
multiplexer = httpconnect
custom_domains = ssh
local_port = 22
[proxy3]
type = tcpmux
multiplexer = httpconnect
custom_domains = squid
local_port = 8080

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 @alkaid-ops on GitHub (Apr 10, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3396 ### Describe the feature request 通过[上面的](https://gofrp.org/docs/features/tcpmux/)配置，frps 如果接收到 HTTP CONNECT 请求内容: CONNECT test1 HTTP/1.1\r\n\r\n 该连接将会被路由到 proxy1 。我是初学者可能有些误区: 1. http connect 是 http 1.1 建立tcp隧道的特殊请求 2. type tcpmux 是不是 listen同端口，根据Host的不同进行路由的tcp转发？(类似ningx hostname) 3. 我该怎样使用测试它？ ![image](https://user-images.githubusercontent.com/52811347/230940325-4fbdd248-869f-47bd-b94f-847f40146157.png) curl 和浏览器直接访问我看到了连接和关闭怎么看有没有被frp route到frpc那边 4. 我用tcpmux代理nginx\ssh\squid都没成功，我该如何使用它？ [proxy1] type = tcpmux multiplexer = httpconnect custom_domains = nginx local_port = 80 [proxy2] type = tcpmux multiplexer = httpconnect custom_domains = ssh local_port = 22 [proxy3] type = tcpmux multiplexer = httpconnect custom_domains = squid local_port = 8080 ### Describe alternatives you've considered _No response_ ### Affected area - [X] 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:45:09 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:45:12 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Apr 11, 2023):

你可以先从网上检索一些关于 CONNECT 代理方式的文章，学习一下。

@fatedier commented on GitHub (Apr 11, 2023): 你可以先从网上检索一些关于 CONNECT 代理方式的文章，学习一下。

gitea-mirror commented

2026-05-05 13:45:13 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (May 12, 2023):

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 (May 12, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified