ASP.NET 2.0 Cookbook, 2nd Edition

Introduction

An HTTP handler is a class that intercepts and handles requests for a resource of a given type on a web server. HTTP handlers are a key feature of ASP.NET. For instance, when you request an .aspx file, a built-in HTTP handler intercepts the request and takes charge of loading and executing the .aspx file. ASP.NET also provides built-in HTTP handlers for .asmx, .ascx, .cs, and .vb files, as well as other file types. The <httpHandlers> element of the machine.config file contains a list of the standard HTTP handlers configured for your web server.

Overriding ASP.NET’s Built-in HTTP Handlers

The <httpHandlers> element in machine.config defines how ASP.NET handles requests for all of the standard file extensions found in most ASP.NET applications. These include .aspx, .asmx, .ascx, .cs, .vb, .vbproj, .csproj, .soap, and many others. By placing your own handler settings in web.config, you can override those defined in machine.config. The override maps incoming requests to the appropriate IHttpHandler class you define (see Recipe 20.1’s “Discussion” section for more details). The override can be for a single URL or for all requests with a given extension.

You can extend the built-in handlers provided by ASP.NET or write your own. A custom HTTP handler is useful when you want to handle requests by your application for a given resource on your own. For example, custom handlers are useful for returning binary data, such as the contents of an image file, or for handling the ...