Sorry for the late reply, but the wheels of the corporate engine grind slowly.... Here is the config section where I am trying to initiate the custom 404. I do notice it is in the system.web section, not the system.webserver.
This used to go to a page that handles landing pages(i.e. http://domain.com/landingpagename) where the 404 filter was redirecting their to check for a landing page and pushed back to the 404 page if it could not find one by taking the last part of the URI.
Even after changing this to just go to the 404 page, it is still re-directing to the landing page. Is this cached somewhere?
<customErrors mode="On" defaultRedirect="~/error.aspx">
<error statusCode="404" redirect="~/404.aspx" />
I also noticed there is a catch all of any unhandled exception in the same parent tag...
<add type="UnhandledExceptionModule" name="UnhandledExceptionModule" />
But I think this is only for uncaught application exceptions, not 404s.
My problem is that it is still returning a 302 because of the re-direct and not a straight 404. So as far as Search engines are concerned they are soft 404s because content is still being served up. I tried uploading a screen shot but received an error on the editor(Error#2038).
Where in IIS can I find if I am in classic pipeline or integrated?
Thanks in advance, I am stumped a little here.