Forum Discussion
Receive String Not Reconized By Custom HTTP Health Check Monitor
Have you tried running a tcpdump on port 80 to see exactly how the curl request is formed to get the intended result? Then you could edit the send string accordingly.
I have run a tcpdump on this request, and it returns the expected string (picture of Ken pulling out his hair).
What I don't understand is a telnet to this URL, with either a 1.0 or 1.1 HTTP request, fails, but a curl, using a 1.0 or 1.1 HTTP request, returns the correct string. Since the URL for the monitor check is hitting a separate war file, that then hits the application to determine it's availability, is it possible that this is considered a redirect (301) and thus telnet and the health monitor fails? There is no evidence of a redirect, either in telnet, curl, the monitor logs, or in a browser hitting the same URL...
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