Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In my web site, I am currently custom handling two HTTP errors: 404 Not Found and 403 Forbidden. This “handling” consists of redirecting the user to a custom error page specific to the particular error. Are there any other HTTP (or, in fact, other kinds) errors that occur often enough to warrant a custom redirect and page?
If you want to be relatively thorough, you can consider handling these two:
401: Unauthorized. You didn’t recognize the login attempt. (Contrast with 403, where they do authenticate successfully but don’t have permission to see the resource they asked for.)
500: Server Error. Something went wrong server-side and you couldn’t recover from it.
If you expect to get a lot of traffic, perhaps also consider handling 503: