OK, thanks. I'll set the Ubuntu bug task to Invalid then, but feel free
to reopen if there's more information available that suggests that
there's an action that can be taken in Ubuntu.
** Changed in: monitoring-plugins (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
Or you can close this bug issue. I don't think that it's actually
something Ubuntu/Canonical can do in this case. I might check with
upstream but the workaround (combination of the two) works for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for explaining your use case.
I think that whether this is a bug or not depends on upstream's position
on combining -k with attempting to override the Host: header. If you'd
like to check with upstream, then please feel free to do that and link
to that conversation from here. Until
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I used "nc -l 4007" to examine what the plugin was actually sending, and
I can confirm that the Host: header doesn't appear when testing
check_http on 20.04.
However, I'm not sure this is really a bug. check_http