Hi, the default behavior of this package is working great! I have an issue where if someone enters a really long url by mistake, I get the standard IIS 404 error. Similar to this issue: http://stackoverflow.com/questions/14364281/trying-to-figure-out-a-strange-behavior-using-mvc-4-custom-error-pages-sometime

Is there a setting/way to tweak the setup so that I can add something like a catchall route and forward it to the fake error controller?

Hope this makes sense.

Thanks!

DL

I'm getting a NullReferenceException appearing when HttpContext.Current.Error is null. It only seems to happen for me when I do a request to a Web-Api controller that requires authentication, and the user hasn't yet authenticated via forms auth. Adding in a check for null values on currentError appears to resolve the problem and Web-Api then returns the correct 401 response.

CustomErrorHandlingModule.cs#L98

I'll try to submit a pull request after I work out how to use git.

Per this StackOverflow answer, my understanding is that my error views (404.cshtml, etc) should pick up the standard _ViewStart.cshtml and thus be rendered within my _Layout.cshtml like all my other views, but this is not working.

If I add the contents of _ViewStart.cshtml to my error view manually, I do get my error view rendered within my _Layout.cshtml as expected:

@model WorldDomination.Web.Mvc.ErrorViewModel

@{
    Layout = "~/Views/Shared/_Layout.cshtml";
}

@{
    ViewBag.Title = "401";
}

<h2>401</h2>

Looking at the error views in the sample project, I see they are written as full HTML documents, but this goes against the rest of the Asp.Net MVC convention. Instead, error views should pick up _ViewStart.cshtml (if present).

Here is a suggested fix to CustomErrorHandlingModule.RenderCustomErrorView(). Pass in true instead of false for the runViewStartPages value:

var view = new RazorView(controllerContext, viewPath, null, true, null);