When dealing with web applications running over HTTP/S, we will come across a series of problems that we can roughly separate into two groups:
- client errors (4xx status codes)
- server errors (5xx status codes)
Yes, 404 Not Found may be the most infamous of them all, but there are a number of others errors you surely experienced at some point or another, such as 403 Forbidden on the client side; or 500 Internal Server Error and 502 Bad Gateway, to mention a few on the server-side.
For more information see the full list of HTTP status codes.
Why Setting Custom Errors?
Let’s admit this—with all certainty, errors will happen; but you can make your web application look less generic by customizing the error messages that the user will receive whenever a forbidden page has been requested, or the server is temporarily unavailable.
This not only makes errors more enticing but also provides more useful information to your clients about what’s going and how can it be addressed.
How to Set Custom Errors
You can set global custom error pages if you are an advanced user, and Snapt One makes their management a breeze—you won’t need to adjust web server settings, but simply set it the paths up at the Snapt One UI itself.
Balancer > Adv. Configuration > HTTP Error Management
Go under the Custom Error Pages tab, and you will have a list of the errors for which you can set a custom HTML file.
When setting a custom error page, make sure that the paths exist and that they follow the correct standard.
The following errors are supported by Snapt One:
- Error 400 Bad Request
- Error 403 Forbidden
- Error 408 Request Timeout
- Error 500 Internal Server Error
- Error 502 Bad Gateway
- Error 503 Service Unavailable
- Error 504 Gateway Timeout