[GH-ISSUE #3366] [Feature Request] does http_proxy support also public proxy without cradentials?

gitea-mirror commented

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

Owner

Copy link

Originally created by @zaalgol on GitHub (Mar 18, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3366

Describe the feature request

frp provides a options using a proxy.
the pattern in the configuration is http_proxy = http://user:pwd@192.168.1.128:8080

But what about using a public proxy that doesn't require username and password?
I can use it like this: http_proxy = http://192.168.1.128: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 @zaalgol on GitHub (Mar 18, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3366 ### Describe the feature request frp provides a options using a proxy. the pattern in the configuration is `http_proxy = http://user:pwd@192.168.1.128:8080` But what about using a public proxy that doesn't require username and password? I can use it like this: `http_proxy = http://192.168.1.128:8080`? ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [X] Others

gitea-mirror

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

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:44:13 -06:00

Author

Owner

Copy link

@Becods commented on GitHub (Mar 19, 2023):

Practice is the sole criterion for testing truth.

@Becods commented on GitHub (Mar 19, 2023): Practice is the sole criterion for testing truth.

gitea-mirror commented

2026-05-05 13:44:14 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Apr 19, 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 (Apr 19, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified