Delivery Tier Error Pages and Error Handling

The delivery tier (HST) provides many ways for dynamic, customizable error pages and error handling. As this topic is quite large and can be addressed in multiple ways, its documentation is split into several separate pages. The first solutions are the easiest but at the same time the most limited. Furthermore, some of the pages are complementary solutions to get the perfect error handling you want. The last solution might be a bridge too far for some developers but for the more advanced developers, who want to have fine-grained control over how to handle exceptions, this is the way to do it.

Correct error handling is of major importance. Setting the correct response headers is very important for, for example, search engines. You do not want a 200 response for a 404 page, as this gets indexed by crawlers as a correct page. You might end up with your error page very highly ranked by search engines.

Note that the HST cannot provide a dynamic error page (for example with a repository based menu) when the HST cannot be started at all, for example because of broken Spring configuration or a repository connection that cannot be established. In this corner case, a

HttpServletResponse.SC_SERVICE_UNAVAILABLE

is sent as response, which boils down to a 503.

Error pages and error handling

1. Handle Error Codes and Exceptions in web.xml
2. Add a Catch-All Sitemap Item that creates a Dynamic 404 Page
3. Simple Exception Handling
4. Advanced Exception Handling