Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.

When a user requests a non-existing page, the servlet container (Tomcat) or application server displays a 404 error page and returns the error code 404. You can configure what happens in the case of a 404 in the web.xml configuration file in the container.

A common solution is to create a custom error page that looks like the rest of your site, tells the visitor in clear terms that the page was not found, and provides some alternative ways to continue such as navigation and a search box.

<error-page>
   <error-code>404</error-code>
   <location>/error/404.html</location>
</error-page>

404 is not the only HTTP error code. You can set up landing pages for any of them the same way. See also How to setup a custom 404 handler on the wiki.

  • No labels