Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] ad-hoc or long-lived (persistent) connections to target? #4573

Closed
3 of 11 tasks
ofirc opened this issue Dec 5, 2024 · 3 comments
Closed
3 of 11 tasks

Comments

@ofirc
Copy link

ofirc commented Dec 5, 2024

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

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
@fatedier
Copy link
Owner

fatedier commented Dec 5, 2024

For tcp proxy, the connections are 1:1. For http proxy, the default Golang HTTP connection pool is used and it is not configurable.

@ofirc
Copy link
Author

ofirc commented Dec 10, 2024

Thanks @fatedier for the prompt response!

Copy link

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

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants