I would suggest you make a plain staic 404 handler for non aspx pages. To handle this in a requestHandler you need to route all requests through .NET.

Hi Chris,

I have found a working solution, which requires the umbraco requestHandler to be modified and raises a IIS error, so i can handle all errors using one single error page. I will post my solution tonight, as i have to get my daughter from daycare now.

Cheers,
André

So, a little late, but here is my - simplified (using a custom asp.net error page) - solution for 4.0.21:

requestHandler.cs

In requestHandler.cs (part of the source distribution and located in the umbraco.presentation project) you have to comment out the content (and only the content, not the if-statement itself) of the following if-statement appearing in the constructor:

if (currentPage == null) 

and put something like this into this if statement:

HttpException ex;
ex = new HttpException(404, "Requested document was not found");
throw ex;

This raises a HttpExcepton with 404 error code that will be handled by IIS configured error management.

web.config

Of course you have to set up the by modifying the "customErrors" element of your web.config like this:

<customErrors mode="On" redirectMode="ResponseRewrite" defaultRedirect="~/ErrorPages/PageNotFound.aspx" />

and add the errorpage's virtual path to the "umbracoReservedUrls" appSettings element, so umbraco won't try to handle your errorpage.

Your error page

Your error page holds all your your logic to set the appropriate error codes and redirection targets. Basically it may looks like this:

protected void Page_Load(object sender, EventArgs e)
{
    if (Context.Error != null)
    {
        Response.StatusCode = your_specific_error_code;
        Response.RedirectLocation = your_specific_redirection_target;
    }
}

So, that's it.

is working on a reply...