Keep ASP.NET Error Pages out of Search Engines
2/7/2012
In a production environment, users should not be presented the default ASP.NET error pagesInstead they should be offered clean, understandable error pages giving them a sensible explanation of the error, along with suggestions to continue their journey on the website.
Besides usability concerns, it's also an important security practice to not leak details about application details to those who might tinker with your application!
Similar articles
ASP.NET Weblogs
Error pages in ASP.NET
In ASP.NET you can retrieve the last unhandled exception via:(HttpContext.Current.)Server.GetLastError() // Server object is available as a property in Page and UserControl context This obviously onl...
ASP.NET Daily Articles
Custom Error Pages In ASP.NET
This tutorial explains how to use custom errors pages to provide better user experience when error occurs and save your reputation.
ASP.NET Daily Articles
Custom Error Pages In ASP.NET
This tutorial explains how to use custom errors pages to provide better user experience when error occurs and save your reputation.
mike's web log
MembershipProvider error in ASP.NET Web Pages
If you use membership in ASP.NET Web Pages, you might get the error "To call this method, the "Membership.Provider" property must be an instance of "ExtendedMembershipProvider":I happened to run acros...
ASP.NET Weblogs
Creating custom error pages in ASP.Net applications
This is going to be another short post regarding ASP.Net and custom error pages. Our goal is to specify a particular page to be displayed on the user's screen when error occurs within our application....