Forum Discussion
Question about healthchecks
- Mar 10, 2026
The issue was due to the return code returned by my app in the process of healthcheck -- 302 instead of 200. Adding 302 is the list of allowed responses fixed the issue. Thank you all.
I don't see any option to configure the http health check's tis settings (though I could swear it was previously an option). It could be worth exploring meeting in the middle and leveraging instead a TCP health check? You can drop in custom send/receive payloads to do more introspection than a simple connection check (but even that is better than no checking at all).
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com