An LTM Specialist is troubleshooting an HTTP monitor. The pool member is accessible directly through a browser, but the HTTP monitor is marking the pool member as down.
GET / HTTP/1.1 -
HTTP/1.1 400 Bad Request -
DatE. Tue, 23 Oct 2012 21:39:07 GTM
Server: Apache/2.2.22 (FreeBSD) PHP/5.4.4
mod_ssl/2.2.22 OpenSSL/0.9.8q DAV/2
Content-LengtH. 226 -
Connection: close -
Content-TypE. text/html; charset=iso-8859-1
Which issue is the pool member having?
The pool member is rejecting the request because it is invalid. The response code 400 Bad Request indicates that the server is rejecting the HTTP request made by the monitor, likely due to an issue with the form of the request.
B - Correct The pool member is accessible directly through a browser, indicating it's functional and accepting requests. The HTTP monitor response is a 400 Bad Request, suggesting the pool member deliberately rejected the request due to perceived invalidity. The monitor send string is simple and should be accepted by most servers, further suggesting the issue lies with the specific content of the request or its interpretation by the server.