We’re using the httpv2 check to monitor our certificates - which works great.
However, for a small subset of pages, we need to go through an explicit proxy.
When doing so - the certificate age is no longer checked / shown - the check (independent of configured levels) only fails once the certificate actually expires - which obviously caused a short downtime for us.
This is both unexpected and undocumented (as far as i can see) - and i think might be a bug in the httpv2 module.
i suspect it’s caused by the proxy being http - and the help for the check mentions “Not relevant for HTTP connections without TLS.” - which i assume is what applies here (as the connection to the proxy is not https).
The check itself should still be possible though - for example via curl, i get the correct expiration date without problems.
Is this a configuration problem (what flags do i need to set to get this working) - or is it a bug?
(i’m using 2.4.0p26 - if that’s relevant).
