Jeff on Nostr: Latest version of my `check_https_go` tool now allows you to configure which HTTP ...
Latest version of my `check_https_go` tool now allows you to configure which HTTP status codes you consider as 'valid'. Very useful for those of you who need to ensure that `418` is considered valid (it really should be a 2XX code).
Previously all 200-series codes were considered valid—and this is still the default—but I found a situation where I needed to catch an issue where `204 No Content` was being returned, so now you can specify exactly which codes pass or fail.
https://exchange.icinga.com/JeffAlyanak/check_https_go
Previously all 200-series codes were considered valid—and this is still the default—but I found a situation where I needed to catch an issue where `204 No Content` was being returned, so now you can specify exactly which codes pass or fail.
https://exchange.icinga.com/JeffAlyanak/check_https_go