mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #4573] [Feature Request] ad-hoc or long-lived (persistent) connections to target? #3615
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#3615
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 @ofirc on GitHub (Dec 5, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4573
Describe the feature request
In the typical setup of:
client -> frps -> frpc -> private service (e.g. web server)
Does the frp client (frpc) keep a persistent connection to the (target) private service or is it ad-hoc, i.e. every time the client wants to contact the private service (through frps -> frpc) it will open a new socket (and close it later)?
What's the default, is it configurable via the toml?
Thanks!
Describe alternatives you've considered
No response
Affected area
@fatedier commented on GitHub (Dec 5, 2024):
For
tcpproxy, the connections are 1:1. Forhttpproxy, the default Golang HTTP connection pool is used and it is not configurable.@ofirc commented on GitHub (Dec 10, 2024):
Thanks @fatedier for the prompt response!
@github-actions[bot] commented on GitHub (Dec 25, 2024):
Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.