I used Shay Jacoby's solution to route 404s and 500s and it works great on my dev box: http://stackoverflow.com/questions/619895/how-can-i-properly-handle-404s-in-asp-net-mvc/
However, in production, it only routes 500 errors and 404s still get the default iis 404 messages. I think I'm missing something simple, any ideas?
I deployed the code to a local iis7 website and the 500 errors are being redirected. I can't think of what is different in the environments. Production is also iis7 and the code is identical.
Getting Error “CS1026: ) expected” when trying to combing .js files using SquishIt
How to enable/Disable textbox. and also make text box blank on change of value in the drop down list
How to pass data from a jquery dialog back to a controller's action to update the dialog
How do you set or remove generated label styles from the jQuery Validation plugin?
IIS uses the file extension to determine which IIS handler will process the request..
ASP.NET MVC Trouble getting data and related data to the view. (View Model Pattern?)
So, the only way for your app to handle 404's is to have IIS configured to send it directly to your app instead of handling it internally.
Combining ASP.NET MVC and Reverse Proxy with URL Rewrite v2
Which is what you've done..
ASP.NET MVC 2 - Html.EditorFor a nullable type?
You might want to check out this question / answer for a few more details..
How to create the custom authorize filter?