IIS Custom Errors VS Web.config custom errors

Question

0.00/5 (No votes)

See more:

Hi All,

Can any one explain (with out giving unusefull links...) what is the main difference between IIS custom error tab and web.config custom error section and when we will use IIS custom errors and when we go for web.config custom error?

I came to know by google that .aspx files will not be handled in IIS..is it true?why?

If we have any html page in our application and an error occured in this page which one will handle this?

Thanks
Vinay

Posted 22-Jul-10 19:59pm

sowvin

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rajesh Sajjanar · Answer 1 · 2010-07-22T21:09:00

Hi Vinay,

MSIL

 IIS Custom errors are Error messages for HTTP Errors some of them are as below

200 - OK
400 - Bad request
401 - Access denied
401.1 - Logon failed
403.1 - Execute access forbidden
404.0 - (None) – File or directory not found

Web.Config Custom error messages are of three types

XML

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.web>
<customErrors defaultRedirect="url"
              mode="On|Off|RemoteOnly">
   <error statusCode="500"
          redirect="InternalError.htm"/>
</customErrors>

</system.web>
</configuration>

If Mode is OFF then this specifies that custom errors are disabled. This allows display of detailed ASP.net errors

If Mode is ON then this specifies that custom errors are enabled. If no defaultRedirect is specified, users see a generic ASP.NET error

If Mode is Remote then this specifies that custom errors are shown only to remote clients and ASP.NET errors are shown to the local host. This is the default.

defaultRedirect :Specifies the default URL to direct a browser to if an error occurs. When defaultRedirect is not specified, a generic error is displayed instead