mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #1490] 关于frps和frpc之间通信协议的问题 #1175
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#1175
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 @IITII on GitHub (Oct 31, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1490
疑问:
@zhaoyc1990 commented on GitHub (Nov 1, 2019):
@IITII
frps 和 frpc 之间的通信用的 tcp 协议, frpc.ini 配置文件的type 比如:tcp http https stcp 是访问者和frps 通信的协议,也可以理解为访问者和frpc 通信的协议,frps 只是中间的桥梁,桥梁结构是tcp协议
哪里表不达意,请指出 @fatedier
@fatedier commented on GitHub (Nov 1, 2019):
@zhaoyc1990 描述的基本差不多,目前是分为两种连接,控制连接和工作连接,控制连接是传输 frpc 和 frps 自身的控制协议,主要基于 tcp。工作连接是转发用户的请求,那么用户请求是什么样,协议就是什么样,加密之类的只是在这个上面包了一层,对请求方和接收方无感。
@IITII commented on GitHub (Nov 1, 2019):
@zhaoyc1990 @fatedier

所以具体的话,应该更类似与下面的哪一种工作方式?(配置的话,采取最简单的 http 内网穿透,不考虑其他异常)
@fatedier commented on GitHub (Nov 1, 2019):
第一种,因为 HTTP 底层还是 TCP,对于 frp 来说,其实在 frpc 和 frps 之间传输数据是不需要感知到协议的。
加密和解密,对用户透明,你的理解没问题。
@IITII commented on GitHub (Nov 2, 2019):
那行,非常感谢!
@fatedier @zhaoyc1990