I have a application (folder with an app pool) running on iis 6 where im trying to setup a custom error page. I in the web config I have a element for the custom error but it never shows up. If I go into IIS and look at the properties of the app I can set a custom error to point to oops.html. It seems that IIS is not using the setting in my web.config for handling the errors.

Here is what I have
in web.config

```
<system.web>
    ...
    <customErrors mode="On" defaultRedirect="/oops.html" redirectMode="ResponseRewrite" />
    ...
</system.web>
<system.webServer>
    ...
    <httpErrors existingResponse="PassThrough" />
    ...
<system.webServer>

```

Address to the app is like this:
www.mysite.com/myappfolder/

the web config is in:
www.mysite.com/myappfolder/

and oops.html is in:
www.mysite.com/myappfolder/oops.html

if it try to go to:
www.mysite.com/myappfolder/NothingReal 
a 404 will be thrown and only when I have configured IIS to redirect to oops.html will I see the page.

What are the rules for specifying the target of customerrors? Should I remove the "/" what about using ~/myappfolder/oops.html? How do I bypass IIS 6 error handling and have all the errors redirect to my page?