Add the ability to disable following redirects
Currently updown.io will follow 302 redirects when checking if a service is up. In the curl commands that are emailed when downtime is detected, this is achieved via the -L flag. It would be good if this could be disabled, so that the actual endpoint given is tested and not the endpoint at the end of the 302(s).
An example of when this might be useful: I have a few endpoints that simply 302 to another endpoint, which I don't maintain / own / have any control over. I'm less interested in whether those endpoints are up, and more interested in whether my endpoints are up.
I've also noticed that when a 302 is followed, the SSL analysis is carried out on the final SSL certificate, not the server that issued the 302. Again, it would be useful if we could disable following 302's so the SSL certificate that I manage on my endpoint (which serves the 302) is monitored instead.
Daniel G
shared this idea
This is now possible, the "contains" attribute can accept an HTTP status and if you specify any of the intermediary redirect status (e.g. 302, 303, 307...) then the monitoring will stop here and consider the check as UP instead of following the redirect.
About the SSL certificate analysis, it is actually always carried on the first endpoint before any redirection, it does not follow them and never has. If you have any counter example please let me know so we can have a look.