Support "no follow redirect" or "max redirect" like option#23
Currently uptimerobot always follow redirect response like 302, and judge the status from final endpoint.
However, we sometimes want to check the first endpoint is just returning 302 response properly.
(And uptimerobot currently supports any response code to check including 3xx responses for pro plan, I guess it could be missleading) .
This suggestion is for solving this situation, by adding “no follow redirect” or “max redirect” option to the check settings.
Many time people who post requests here are thinking, “how can we get UR to do what Nagios or Foo does”. In the case of redirect following ‘check_http’ offer the following options:
-f, --onredirect=<ok|warning|critical|follow|sticky|stickyport>
How to handle redirected pages. sticky is like follow but stick to the
specified IP address. stickyport also ensures port stays the same.‘ok’ = any redirect is a success (stop after first redirect)
‘warning’/‘critical’ = any redirect is a fail (stop after first redirect)
‘follow’ = follow redirect and test first non-redirect response
‘sticky’ = if a redirect changes the domain, that’s a fail
‘stickyport’ if a redurect change the port (e.g. 443 -> 80) that’s a fail
I think UR could offer just ‘follow’, ‘follow sticky’ and ‘no-follow’ for HTTP and Keyword and that would be a great!
In general UR users are going to keep asking for feature until (almost) everything from ‘check_http’ is covered, so for a prediction of future end-user requests, here’s the man page :-)
Hello everybody, we have just released this feature. Please, check out the latest blog post with more details -> https://uptimerobot.com/blog/july-2023-dont-follow-redirects-secondary-e-mail-address/
Enjoy!
This feature is not accessible via API. Any plans for this? This is crucial for us.
Any plan to add this to the API ?