[Bug] Incorrect operation of the “Enable upstream server health checks” function
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 22.6k
- Forks
- 1.5k
- Avg merge
- 4h 30m
- Merged PRs (30d)
- 11
Description
What happened?
When the option “Enable upstream server health checks” is enabled, the WAF starts spamming the backend nginx with requests like safeline.ex.com.
The volume is ~30× the number of normal requests to ex.com.
If the checkbox is disabled, everything works fine — no parasitic traffic, no 444 responses from nginx to non‑existent domains.
How we reproduce?
Enable upstream server health checks
Expected behavior
A function should not behave this way. The number of requests should be increased by a maximum of two times.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce the issue with upstream server health checks enabled and compare backend request volume and hostnames with the option disabled; trace the health-check entry point and request generation. Done means health checks no longer create parasitic requests or 444 responses, and total traffic stays within the expected limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, nginx
- Domain
- backend, networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100