I have no idea. But really the creation of the PageNotFound.aspx page was not intended for configuring IIS to redirect to that page. For urls handled by .NET, our page not found handler automatically responds and it does not re-direct to this page it just makes a server side web request for the page and scrapes its content and then writes the content to the response while keeping the status code as 404. If it did a redirect then the status code would be 200 rather than 404.

Best,

Joe

I see what you mean. I think it must be some IIS 7 configuration but I'm not sure what.

On my local machine using IIS 7 it works 100% of the time and on demo.mojoportal.com the log shows that the PageNotFoundHttpModule did handle the 404 and yet somehow IIS is returning the default 404 page.

It was working fine before I migrated from Win 2003/IIS 6 to Win 2008 IIS 7, and yet it works fine on my local Win 7 /IIS 7 machine. So it seems it must be a configuration difference somewhere.

Best,

Joe