404 Error Page Redirect Asp.net
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 Default redirect for Error 404 up vote 14 down vote favorite 7 I want to introduce a functionality in my ASP.net website that, whenever a request is received for an unknown URL on my domain, the user is redirected to my error_404.htm page in the root of the application. For example, if the request is http://www.mydomain.com/blahblahblah Then instead of returning the standard 404 error page, I want it to redirect the request to http://www.mydomain.com/error_404.htm Update IIS Version 7.5 and .NET Framework Version 4 Update /blah.aspx redirects but /blah does not asp.net http redirect default share|improve this question edited Jul 18 '13 at 10:06 Nikola 4212 asked Dec 19 '10 at 16:27 Shekhar_Pro 12.7k53773 3 Oh no, please don't. When I've got to the wrong URL, I want to know. I also want the chance to edit what is in my address bar in case I made a typo. Have the error page provide some useful information, but don't redirect. –Quentin Dec 19 '10 at 16:29 1 Do not do this. It's incredibly annoying. –SLaks Dec 19 '10 at 16:30 What version of .net you running and IIS version? –Rippo Dec 19 '10 at 19:09 @Rippo i have mentioned my IIS and .Net version, Please help. –Shekhar_Pro Dec 22 '10 at 10:19 add a comment| 3 Answers 3 active oldest votes up vote 37 down vote accepted +50 This is how you configure a custom 404 error page for both ASP.NET and non-ASP.NET requests: 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 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), http://stackoverflow.com/questions/4483849/default-redirect-for-error-404 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 https://www.stokia.com/support/misc/web-config-custom-httperrors.aspx 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 Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs Forums HomeConfiguration Referencesystem.webServerhttpErrors HTTP Errors 404 Page Not Found
I created a new ASP.NET MVC 5 application using the standard template in Visual Studio. If I run the site and try to navigate to a resource that does not exist e.g. /foo/bar, I'll get the standard ASP.NET 404 page with the following information: Server Error in '/' Application. The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly. Requested URL: /foo/bar Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.33440 Not exactly friendly, is it? In this case the error was raised by ASP.NET MVC because it could not find a matching controller and/or action that matched the specified URL. In order to set up a custom 404 error page add the following to web.config inside