I tested that theory a few months ago, but alas, that's not it, as 301 does work just fine for www.qwest.com, but not for www.timerwarnercable.com
root@nagios:/usr/lib/nagios/plugins# ./check_http -6 -H www.qwest.com HTTP OK: HTTP/1.1 301 Moved Permanently - 589 bytes in 0.163 second response time |time=0.163363s;;;0.000000 size=589B;;;0 root@nagios:/usr/lib/nagios/plugins# root@nagios:/usr/lib/nagios/plugins# ./check_http -6 -H www.timewarnercable.com CRITICAL - Socket timeout after 10 seconds root@nagios:/usr/lib/nagios/plugins# We may need a NAGIOS developer who understands the check_http code to chime in. Regards, Frank -----Original Message----- From: Help [mailto:help-bounces+frnkblk=iname....@monitoring-plugins.org] On Behalf Of zep Sent: Friday, August 29, 2014 9:15 AM To: help@monitoring-plugins.org Subject: Re: Monitoring IPv6 website On 08/29/2014 09:32 AM, Frank Bulk wrote: > But there is! Try with a typical webbrowser or wget! > > root@nagios:/tmp# wget -6 www.timewarnercable.com > --2014-08-29 08:31:57-- http://www.timewarnercable.com/ > Resolving www.timewarnercable.com... 2001:1998:840:b001::7 > Connecting to www.timewarnercable.com|2001:1998:840:b001::7|:80... > connected. > HTTP request sent, awaiting response... 301 Moved Permanently ---------------------------------------------------^^^^^^^^^^^^^^^ > Location: http://www.timewarnercable.com/en/residential.html > [following] > --2014-08-29 08:31:57-- > http://www.timewarnercable.com/en/residential.html > Reusing existing connection to www.timewarnercable.com:80. > HTTP request sent, awaiting response... 200 OK > Length: 101218 (99K) [text/html] > Saving to: âindex.htmlâ > I think you may have answered your own question. it would seem to me that check_http only considers http response codes in the 200 range to be successful and valid, whereas a redirect to a different server isn't thought to be a successful test/connection. I'd have to play with some web servers to confirm that notion
