> From: steve f [mailto:a31mod...@hotmail.com] > Sent: Thursday, November 03, 2011 11:34 AM > Subject: [Nagios-users] What happened to my check_http all of the sudden?
> The check was check_http -L www.somesite.com -c 30 -w 15, which was running > with no problem. Today we switched over > content to Akamai and as soon as we did, this check starting alerting a > warning as follows : > <A HREF="http://www.somesite.com:80/" target="_blank">HTTP WARNING: HTTP/1.0 > 400 > Bad Request - 402 bytes in 0.061 second response time > </A>|time=0.061278s;15.000 > 000;30.000000;0.000000 size=402B;;;0 > I switched the check to the following check_http -H www.somesite.com -c > 30 -w 15 > and everything went back to green > HTTP OK: HTTP/1.1 200 OK - 40004 bytes in 0.247 second response time > |time=0.246 > 539s;15.000000;30.000000;0.000000 size=40004B;;;0 -H and -L are not even remotely related to each other. -H is followed by the hostname you're checking and specifies a virtual hostname to check. It is used to generate the "Host" header in the HTTP request, and in the absence of a "-I" parameter it is also used to determine the address to send your request to. -L is a standalone parameter. In your original config, -L and "www.somesite.com" have no relationship to each other, becaus -L does not take a parameter. It is used to wrap your URL in HTML to make it a clickable link in your plugin output. It is a strictly cosmetic option that does not affect how your check is run in any way. Since you had not included a hostname to check in your configuration, your HTTP requests probably never had a valid "Host" header, and Akamai barfed on those requests in a way your local server did not.
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null