Forum Discussion
F5 LC http health monitor get blocked by F5 ASM
Is there a known issue when we do health monitor using http from F5 LC to server behind F5 ASM?
Attack mentioned per below:
`**Unparsable request content HTTP version not found**`
1 Reply
- crodriguezRet. Employee
Per K10280, ASM's default behavior with respect to HTTP protocol compliance is to flag an HTTP request as bad if it is not using HTTP version 1.0 or higher. By default, the BIG-IP system uses HTTP 0.9 when sending monitor requests. By specifying the HTTP version in the Send String of the monitor, you can force the system to send an HTTP 1.0 or 1.1 request. See K2167 for help with constructing HTTP requests for use with the HTTP or HTTPS health monitor.
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