implement --response-code functionality about http-checks HOT 9 OPEN

@agoddard something to consider in implementing this would be its behavior with respect to the --redirect-ok flag. May require additional documentation (e.g. you cannot use --redirect-ok when doing --response-code 301) and the already noted caveats for --redirect-ok.

from http-checks.

Maybe it can be a single code or an array, and when it is an array the order matters, so then you can say "when I hit this redirecting URL with redirect-ok, I want to know that the place I end up gives me a 200" and then of providing an Array, then "when I hit this redirecting URL, I should get a 302 on the way to the 200" [302,200]

from http-checks.

@jspaleta I wonder if we could implement this one as a metric tag + metric threshold check?

from http-checks.

@agoddard is there an internal ref for this one?

from http-checks.

I'm wondering if --redirect-ok and the proposed --reponse-code implementation are necessarily mutually exclusive? What if I want to configure a check to expect a response-code from it's final destination, even if that's after following a redirect?

from http-checks.

Should --response-code be --response-codes (plural)? Then perhaps you could pair --redirect-ok with --response-codes 301,202, meaning any number of 301 redirects and a 202 response code are acceptable result for the check?

from http-checks.