Re: check_http: Fix for checking http on different virtual port [sf#3442015] (#1026)

Hi,

sorry, I had not seen your reaction last year...

It still does not work. Your validation above was invalid (the 'head -4'
accidently stripped out the error message):

odenbach@situla:/tmp/bp/usr/lib/nagios/plugins$ ./check_http -I lumen1 -p
5033 -H 'uni-paderborn.de:80' -v	 
GET / HTTP/1.1
User-Agent: check_http/v2.1.1 (monitoring-plugins 2.1.1)
Connection: close
Host: uni-paderborn.de:80


CRITICAL - Socket timeout after 10 seconds

If you look at the network traffic in parallel (tcpdump), you can see the
reason:

situla.uni-paderborn.de.37105 > lumen1.uni-paderborn.de.http

So check_http still tries to reach the server at port 80, and not port 5033
as expected.

Does the pull request from above still work? Or should I try to recreate the
patch agains 2.1.1?

Thanks,

Christopher

-- 
Reply to this email on GitHub:
https://github.com/monitoring-plugins/monitoring-plugins/issues/1026#issuecomment-133013078