Hi Robie Thx for checking.
The problem with the host header set by -H parameter is that it automatically applies the port, if a port is used with the -p parameter. $ /usr/lib/nagios/plugins/check_http -I 127.0.0.1 -H www.example.com -p 8083 -v GET / HTTP/1.1 User-Agent: check_http/v2.2 (monitoring-plugins 2.2) Connection: close Host: www.example.com:8083 (this can cause problems depending on the infrastructure, e.g. using load balancers forwarding the requested host header to the backend) To get rid of the port in the Host header, the workaround using -k and defining the "Host" header again has worked in the past. But it seems that by using a combination of -H and -k "Host" the previous behaviour can be established again: $ /usr/lib/nagios/plugins/check_http -I 127.0.0.1 -p 8083 -k "Host: www.example.com" -H www.example.com -v |more GET / HTTP/1.1 User-Agent: check_http/v2.2 (monitoring-plugins 2.2) Connection: close Host: www.example.com So it's strange, that the "Host" header is ignored when using -k - but in combination with -H it works. I can live with that workaround but if you want to report it upstream let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940525 Title: check_http regression, 2.2 ignores -k Host header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
