Bug: httpErrors errorMode="Detailed" not respected for Classic ASP

Hi,

I think I have found a bug regarding in the IIS Error Pages system.

Note:

• I am not using .NET Error Pages - this is set to Off 

The problem:

When a custom error page is setup for the 500.100 (Classic ASP) response code, IIS always sends a custom error page even whenerrorMode is set to Detailed.  The only way to get IIS to send the error is to explicitely remove the entry in the web.config.

EG:

<remove statusCode="500" subStatusCode="100"/>
or
<clear/>

Note - the following does not work (which works for all other codes):

<remove statusCode="500" subStatusCode="-1"/>

My scenario:

• Website running .NET 2.0 - Classic pipeline
• Feature Delegation on Error Pages set to read/write
• Error page setup in IIS as follows (due to the feature delegation above, these entries arenotin the web.config):
  • 404 - /path/to/404.htm - ExecuteURL
  • 500 - /path/to/500.htm - ExecuteURL
  • 500.100 - /path/to/500.htm - ExecuteUrl

Turning off Custom Errors:

In order to turn off the custom errors, all I need to do is load my web.config and set the following:

<system.webServer>
<httpErrors errorMode="Detailed"/>
</system.webServer>

This works successfully for all codes except Classic ASP 500 errors (status code 500.100).

The only way I can get the proper Classic ASP error is to setup the following:

<system.webServer>

<httpErrors errorMode="Detailed">

<clear/>

OR

<remove statusCode="500" subStatusCode="100"/>

</httpErrors>

</system.webServer>

Is this a bug?