Sun Aug 15 14:32: There was an unexpected error (type=Internal Server Error, status=500). This is what such a page looks like: Whitelabel Error Page This application has no explicit mapping for /error, so you are seeing this as a fallback. This so-called Whitelabel Error Page is nothing more than a white HTML page containing the HTTP status code and a vague error message. When no valid mappings can be found, Spring Boot automatically configures a default fallback error page. This mapping depends on what is set on a ViewResolver class. Particularly, Spring Boot looks for a mapping for the /error endpoint during the start-up. This is the list of all the prerequisites for following the article:īy default, Spring Boot offers a fallback error-handling page, as well as an error-handling response in case of REST requests. Let's see everything required to get started with custom error handling in Spring Boot and Java. Achieving it requires more effort than you might think, and you need to delve into a few essential Spring Boot notions. This is why implementing custom error handling logic is such a common and desirable task. The problem is that this information may be poor or insufficient for the API callers to deal with the error properly.

Specifically, whenever an error occurs, a default response containing some information is returned. REST applications developed in Spring Boot automatically take advantage of its default error handling logic. TL/DR: Let’s take a look at everything required to build custom error handling logic in both Spring Boot Web and Spring Boot Security

Format factory error codes