Adding a custom error page in your web application is crucial for your site. Otherwise, when your system fails or a page is not found, your users will see the standard IIS "yellow screen of death". The solution is to add custom error page to your web application.
Follow the steps in this article in order to configure custom error pages in your Sitefinity CMS web application.
To configure the display of custom error pages, follow the procedure:
The <httpErrors> section above handles errors when accessing Sitefinity CMS pages.
IMPORTANT: If you have change the custom response code of the Application status page and you are using custom error pages, in the above example, instead of <httpErrors errorMode="Custom">, you must use <httpErrors errorMode="Custom" existingResponse="PassThrough">.
For more information, see Change the application status page response code.
This is because if the system is upgrading or restarting while a custom error page is requested, Sitefinity CMS will not be able to display the Application Status page properly, which is the expected behavior.
<httpErrors errorMode="Custom" existingResponse="PassThrough">
If you plan to use any Sitefinity CMS page as a custom error page, you must change the response status explicitly. The default is 200, instead of 400 and this is misleading for the search engines and SEO practice.
To do this, perform the following:
NotFoundStatusCodeSetter : System.Web.UI.UserControl
"404 Not Found"
Response.StatusCode = 404;
The code above sets the response statues code to 404 only on the frontend. This is handled by the IsDesignMode method. You must add the status code at a latest possible moment - in this sample, in the Render event.
The proper response status code is displayed when requesting a page that cannot be found.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity