What happened to my check_http all of the sudden?

[steve f]

We have been running a check_http to our website and just today it started alerting.  I fixed it but was looking for an explanation of why it failed.

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

I know from the documentation that the -L means Wrap output in HTML link (obsoleted by urlize)
not sure exactly what that means.  If memory servers me correct, way back when I set this check up, the -H didn't work but the -L did.

Can someone school me on the details of what happened?

Thanks,
Steve


 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20111103/be392f03/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at 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