Hi Jan, On Mon, May 25, 2009 at 4:00 PM, Jan Wagner <[email protected]> wrote: > Hi there, > > > $ /usr/lib/nagios/plugins/check_http -H www.tcen.ru -I www.tcen.ru > HTTP OK HTTP/1.1 200 OK - 5974 bytes in 0,778 seconds | > time=0,778018s;;;0,000000 size=5974B;;;0 > $ dpkg -l | grep nagios-plugins-basic > ii nagios-plugins-basic 1.4.12-5 Plugins for > the nagios network monitoring an > > Actually I didn't got, what the problem exactly is. Maybe anybody can come > around with much better examples/configs so that I can reproduce the issue. > > Thanks and with kind regards, Jan. > -- > Never write mail to <[email protected]>, you have been warned! >
The problem is that some webservers are configured so that www1.wowhead.com and www1.wowhead.com:80 are different virtual hosts. As you can see if you test with both of the hostnames I just provided, www1.wowhead.com returns a 200 code. Where as www1.wowhead.com:80 does a 302 redirect to www.wowhead.com instead of giving you a 200 code. By default, the plugin automatically adds the header: Host: www1.wowhead.com:80 Ideally it would be nice to be able to provide a flag to not include the port number in the host. -- - Brian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
