Define which errors are real errors
In some cases, a 302 might not be an error, so an ability to give a whitelist would be great.
-
Lukas Bestle commented
Really cool :).
-
Yes, but handling redirect at each run would double the number of request, this is not cool. I think the best would be to follow the redirection once, store the end URL, notice the user, and direcly request the end URL after. WDYT ?
-
Lukas Bestle commented
But let's say I have a website, which has a homepage named /en (and /de for German etc.).
Now I am in Beta and /en will return a 404 (so it's just not accessible).
But when deploying, updown will send me a mail "WUAH! http://lu-x.me/ redirects to /en! Error!".
So it might be a bit unflexible. I don't know. :) -
Yeah, I consider redirect as errors because you should monitor the end point. But I'll add more details so people understand what's happening.