Contents
How to setup a 404 and 500 error page?
Some requirements: Should support files and media items. Should return the proper response status codes (i.e. 404, 500). Should support the use of content items that represent the friendly page (such as a site map).
How to avoid a 404 error in Sitecore?
Patch MediaRequestHandler to use Server.TransferRequest to avoid the error Error executing child request. Added a controller rendering to Sitecore to change the status code. Added a processor to handle the ItemNotFoundUrl setting, load the item, and set to the context item.
How can I force my website to return a 404?
Have a 404 processor in the mvc.getPageItem pipeline to force URL’s that map to items to return a 404 when appropriate. Do make sure to configure the ItemNotFoundURL setting to the 404 page item URL within your site. Set the existingResponse attribute to “Auto” to give your website control over how status codes get handled.
What do I need to set the 404 to?
There are two critical properties that must be set in your rendering: one obviously being the Response.StatusCode to 404, and the other to set Response.TrySkipIisCustomErrors to true.
How to setup 404 error page for missing files and media items?
When navigating to a url such as www.website.com/missing.pdf and www.website.com/-/media/missing.pdf you will either receive the IIS 404 Server Error message or a Sitecore document not found page. What is a solid approach to handling these scenarios?
What should I do if I get an HTTP 500 error?
The httpErrors configuration at the top of this post will give you sufficient handling of HTTP 500 error codes, since HTTP 500 status codes are typically thrown when something terrible has happened. The following will log any uncaught errors but still obey your configuration (while technically allowing you to override those settings as well).
How can I properly handle 404 in ASP.NET?
ASP.NET MVC doesn’t support custom 404 pages very well. Custom controller factory, catch-all route, base controller class with HandleUnknownAction – argh! IIS custom error pages are better alternative so far: