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
Jeff /
npub1kl…8fkuk
2024-04-30 15:53:44
Author Public Key
npub1kl0ma0mkpmajcatt8jhz9w40mw7l2k4m0qhct6fmfkuqf4wt5l3sc8fkukPublished at
2024-04-30 15:53:44Event JSON
{
"id": "507d21d09971d35ba17f688426bedf4154c1bee80d5b372eb6e38a5b61e27741",
"pubkey": "b7dfbebf760efb2c756b3cae22baafdbbdf55abb782f85e93b4db804d5cba7e3",
"created_at": 1714492424,
"kind": 1,
"tags": [
[
"proxy",
"https://social.rights.ninja/users/jeffalyanak/statuses/112360975560420777",
"activitypub"
]
],
"content": "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).\n\nPreviously 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.\n\nhttps://exchange.icinga.com/JeffAlyanak/check_https_go",
"sig": "1ee14fb59c2af9825edde94167408c2e61aba22e1f56896d5584d941bb55d31a4bffd66931ee480e255b632f59fab731232e4b731be4edc4f49bce5758631a75"
}