check_http plugin does not add :<port> in Host: header
Harry Metske
harry.metske at flippo.demon.nl
Fri Aug 19 19:09:45 CEST 2005
Hi,
I'am new to this list, so forgive me any stupid questions.
I'm using nagios 1.2 (feb 02 2004) and I'm trying to monitor applications running in WebSphere.
I use the following chech_http command:
check_http -H son1.rf.rabobank.nl -p 2210 -u /w5/dws_syst/PingServlet
This gives a 404 response back, and after diagnosing the WebSphere trace, it appears that in the HTTP Headers sent by nagios, there is only the host name
and not the port number 2210 (son1.rf.rabobank.nl instead of son1.rf.rabobank.nl:2210).
In my opinion nagios should append :2210 in the case to the hostname, other http clients (browsers, JDKs) all do send the proper Host: header , including the :port .
Is there a "hidden feature" or a way to get around it (except from changing the vhost definition on the server) ?
I tried the following command:
check_http -H 'son1.rf.rabobank.nl:2210' -p 2210 -u /w5/dws_syst/PingServlet
But that gives me an "Invalid host name ...." response from the plugin.
This sounds like a bug/restriction in check_http ?
please advise,
regards,
Harry Metske
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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
More information about the Users
mailing list