[GH-ISSUE #3341] [Feature Request] Support Basic Auth in Service Health Check

gitea-mirror commented

2026-05-05 13:43:32 -06:00

Owner

Copy link

Originally created by @MisteryMonster on GitHub (Mar 3, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3341

Describe the feature request

I have host a service with Basic Auth I need a load-balancing. but Service Health Check don't support Basic Auth so health check won't work, maybe is returning a HTTP 400 Unauthorized error.

Describe alternatives you've considered

Or supporting different HTTP response code in Service Health Check.

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @MisteryMonster on GitHub (Mar 3, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3341 ### Describe the feature request I have host a service with Basic Auth I need a load-balancing. but Service Health Check don't support Basic Auth so health check won't work, maybe is returning a HTTP 400 Unauthorized error. ### Describe alternatives you've considered Or supporting different HTTP response code in Service Health Check. ### Affected area - [ ] Docs - [ ] Installation - [X] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:43:32 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:43:34 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Mar 3, 2023):

You can use tcp probe if you don't care about the response code.

@fatedier commented on GitHub (Mar 3, 2023): You can use `tcp` probe if you don't care about the response code.

gitea-mirror commented

2026-05-05 13:43:35 -06:00

Author

Owner

Copy link

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

No Branch/Tag specified