QuestionQ62

VerifiedIdentify and Resolve Application Issues

An LTM Specialist is troubleshooting an HTTP monitor. The pool member is directly accessible through a browser, but the HTTP monitor is marking that pool member 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 problem does the pool member have?

Explanation

An HTTP/1.1 request must include a Host header. The monitor request lacks that required header, so the server returns 400 Bad Request, indicating that it is rejecting an invalid request rather than being unavailable.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!