Keywords: ASP.NET | HTTP Handlers | AJAX
Abstract: This article provides an in-depth exploration of the core concepts and working mechanisms of .axd files in ASP.NET. .axd files are not actual disk files but registered names for HTTP handlers, primarily used for managing AJAX-related resources. The paper analyzes the two main types, ScriptResource.axd and WebResource.axd, explains their roles in the ASP.NET AJAX Toolkit, and demonstrates their registration mechanisms through web.config configuration examples. Additionally, it discusses the compatibility advantages of the .axd extension in IIS6 and IIS7, as well as how to customize HTTP handlers.
Basic Concepts of .axd Files
In ASP.NET development, .axd files are a common concept, but many developers misunderstand their nature. In reality, .axd is not a physical file stored on the server disk but a registered name for HTTP handlers. This design allows ASP.NET to handle specific types of requests through a unified URL pattern without creating actual files.
Main Types and Functions
ASP.NET framework primarily uses two types of .axd handlers:
- ScriptResource.axd: This is a core component of the ASP.NET AJAX framework. When developers use the ScriptManager control in a web application, the system automatically generates ScriptResource.axd to handle requests for client-side JavaScript resources. It dynamically serves script resources embedded in assemblies to the client, enabling AJAX functionality.
- WebResource.axd: This is a general-purpose resource handler used to extract embedded resources from assemblies, such as images, stylesheets, or script files. Through WebResource.axd, developers can embed resource files into DLLs and access them via URLs at runtime, simplifying deployment.
Working Mechanism and Configuration
These handlers are registered via the web.config file. The following is a typical configuration example showing how .axd handlers are defined in the .NET Framework:
<configuration>
<system.web>
<httpHandlers>
<add path="trace.axd" verb="*" type="System.Web.Handlers.TraceHandler" validate="True" />
<add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
<add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="False"/>
<add path="*.axd" verb="*" type="System.Web.HttpNotFoundHandler" validate="True" />
</httpHandlers>
</system.web>
</configuration>In this configuration, each <add> element defines a handler mapping: the path attribute specifies the URL pattern (e.g., ScriptResource.axd), and the type attribute specifies the handler class. When a client requests a URL matching these patterns, the ASP.NET runtime invokes the corresponding handler to generate the response.
AJAX Integration Example
In ASP.NET AJAX applications, ScriptResource.axd plays a key role. The following code example demonstrates how ScriptManager triggers the use of ScriptResource.axd:
<%@ Page Language="C#" %>
<!DOCTYPE html>
<html>
<head>
<title>AJAX Example</title>
<asp:ScriptManager ID="ScriptManager1" runat="server">
<Scripts>
<asp:ScriptReference Name="MicrosoftAjax.js" />
</Scripts>
</asp:ScriptManager>
</head>
<body>
<!-- Page content -->
</body>
</html>When this page is requested, the ScriptManager generates a reference to ScriptResource.axd, which dynamically serves the MicrosoftAjax.js script file. In the browser developer tools, you can see requests like ScriptResource.axd?d=... containing encrypted resource identifiers.
Compatibility and Customization
The .axd extension has a special advantage in IIS6: by default, IIS6 passes *.axd requests directly to the ASP.NET runtime without additional configuration. This makes it an ideal choice for registering custom HTTP handlers. Developers can add custom handlers in their own web.config, for example:
<add path="CustomHandler.axd" verb="*" type="MyNamespace.CustomHandler, MyAssembly" validate="True" />In IIS7 and later versions, due to the introduction of integrated pipeline mode, all requests are processed through the ASP.NET stack, making extension choices more flexible. However, using .axd still maintains backward compatibility.
Conclusion
.axd files are a significant manifestation of the HTTP handler mechanism in ASP.NET. Through ScriptResource.axd and WebResource.axd, the ASP.NET AJAX framework efficiently manages client-side resources, enhancing the performance and maintainability of web applications. Understanding their working principles helps developers better leverage these features in practical projects, optimizing resource loading and request processing workflows.