See Also: DefaultHttpHandler Members
A System.Web.DefaultHttpHandler object intercepts incoming requests in the HTTP pipeline when both request interception has been configured through Internet Information Services (IIS) 6.0 and no explicit httpHandlers bindings apply to the requested extension.
Request interception can be set up through the wildcard application mapping feature introduced in IIS 6.0. For more information, search the tp://go.microsoft.com/fwlink/?linkid=37118 for information about using wildcard application maps to remap a URL.
The System.Web.DefaultHttpHandler class implements the System.Web.IHttpAsyncHandler interface to provide asynchronous request processing. For general information about HTTP handlers, see HTTP Handlers and HTTP Modules Overview. Additionally, for more information see the following:
About creating asynchronous HTTP handlers, see How to: Create an Asynchronous HTTP Handler.
About registering HTTP handlers, see How to: Register HTTP Handlers.
Classes can derive from the System.Web.DefaultHttpHandler class to provide customized handling of requests. An asynchronous HTTP handler that is derived from the System.Web.DefaultHttpHandler could override the DefaultHttpHandler.BeginProcessRequest(HttpContext, AsyncCallback, object) method to change how requests are processed.
A System.Web.DefaultHttpHandler does not use ASP.NET errors. Existing content that uses IIS errors or a propriety ISAPI custom error mechanism would work unchanged.