Custom Error Pages Asp.net Web.config
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Implementing a Custom Error page on an ASP.Net website up vote 8 down vote favorite 2 I have an ASP.Net website and I want to use a custom error page. I put the following code in my web.config The problem is when i go to a URL that does not exist is still uses the 404 error page specified in IIS Manager. Question: How can I make it use the error.aspx page I have created? Why do the settings in IIS Manager override the web.config? asp.net web-config custom-error-pages custom-errors share|improve this question edited Mar 1 '10 at 2:37 Çağdaş Tekin 13.3k23654 asked Jan 29 '10 at 10:58 Yeodave 6631614 I am using IIS 6 on Server 2003. –Yeodave Jan 29 '10 at 11:13 add a comment| 3 Answers 3 active oldest votes up vote 18 down vote Try this way, almost same.. but that's what I did, and working. or try to change the 404 error page from IIS settings, if required urgently. share|improve this answer edited Feb 12 '12 at 11:17 Alex Peta 1,1491124 answered Jan 29 '10 at 11:18 Hrushikesh 378111 If I have the tag outside of the tags I get a
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Configuration File Syntax ASP.NET Configuration Settings http://stackoverflow.com/questions/2161413/implementing-a-custom-error-page-on-an-asp-net-website TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Recommended Version This documentation is archived and is not being maintained. customErrors Element (ASP.NET Settings Schema) .NET Framework 3.0 Other Versions https://msdn.microsoft.com/en-us/library/h0hfz6fc(v=vs.85).aspx Visual Studio 2010 .NET Framework 4 Visual Studio 2008 .NET Framework 3.5 .NET Framework 2.0 .NET Framework 1.1 Provides information about custom error messages for an ASP.NET application. The customErrors element can be defined at any level in the application file hierarchy. Copy Attributes and Elements The following sections describe attributes, child elements, and parent elements. Attributes Attribute Description defaultRedirect Optional attribute. Specifies the default URL to direct a browser to, if an error occurs. When this attribute is not specified, a generic error is displayed instead. The URL can be absolute (for example, www.contoso.com/ErrorPage.htm) or relative. A relative URL, such as /ErrorPage.htm, is relative to the Web.config file that specified the URL for this attribute, not to the Web page in which the error occurred. A URL starting with a tilde (~), such as ~/ErrorPage.htm, indicates that the specified URL is relative to the root path of the application. mode Required attribute. Specifies whether custom errors are enabled, disabled, or shown only to remote clients. This attribute can be one of th
your web site. The custom errors can be set or overridden on a site wide or directory-by-directory basis. While some web.config sections require that the directory is set as an application, this isn't one https://www.stokia.com/support/misc/web-config-custom-httperrors.aspx of them. A simple web.config with a httpErrors section may be placed in any directory, and the directory does NOT need to be set as an application. What are http errors? HTTP errors are returned to the client when something goes wrong on the server. Error status codes are returned if the requested file isn't found (404), or due to coding errors in the web page (500), custom error and due to temporary issues such as failed database connections (500). The most common errors are 404 (file not found) and 500 (application) errors. Custom 404 and 500 errors are typically used to provide a friendlier error message to your users. Custom 404 and 500 errors could also redirect the user to the default (or any) page, and are sometimes used to notify the web site administrator of custom error pages problems on the web site. If you wish to configure custom errors for your site, or even just for a single directory in your site, please follow the directions on this page. 400 Error (bad request) 401 Error (unauthorized) 403 Error (forbidden) 404 Error (not found) 500 Error (internal server error) How it's done Example custom HTTP errors. Comments are enclosed in and are not required. Capture and return specific error types Using Custom Errors Use a text editor to create a file named web.config Save the web.config file with the appropriate content Place the web.config file in the directory that you wish to modify Detailed web.config content If there isn't an existing web.config in the directory, your new web.config should look something like this