Defining custom error pages is a convenient way to show users a friendly page when they encounter an HTTP error such as a 404 Not Found, or a 500 Server Error. Unfortunately ASP.NET handles custom error pages by responding with a 302 Temporary redirect to the error page that was defined. In this post I explain how to create a custom HttpModule that allows you to use custom error pages while preserving the original HTTP status code and avoiding the 302 redirect to the error page. [More]

Configuration inheritance is a very robust feature of ASP.NET that allows you to set configuration settings in the Web.Config of a parent application and have it automatically be applied to all of its child applications. There are certain situations, however, when there are configuration settings that you don't want to apply to a child application. The usual course of action is to override the setting in question in the child application's web.config file, which is ideal if there are only a handful of settings to deal with. This is less than ideal when there are a significant number of settings that need to be overridden, or when you simply want the child application to be largely independent of its parent. [More]