(To) What is the difference between files suffixed with ashx and axd?

In fact, the extension ashx is basically the same as axd. It is used to write web handler and can be used to call the ihttphandler class. the control parsing and page processing process of the aspx page.

The only difference is:The axd extension must be registered in

therefore, in the Add file of the project, the wizard only adds the template of the ashx file, no template for adding the axd file. Why is it that Microsoft is so bored with two suffixes that it is not enough to use all of ashx? Neat and neat. Originally, if your web handler Code is not in the web project, you cannot use ashx because it is not in the web. if it is registered in config, the system does not know which dll library to find the corresponding code.
example:
(namespace. class Name) company. extensions (. DLL file name) " validate =" false "/>
opensearch is available only after registration. axd was originally in company. extensions. DLL , using company. components. httphandler. opensearchhandler class processing.
of course, you must set up

There is a default ing in IIS on the server: ing *. axd to aspnet_isapi.dll. 
In webconfig, the write principle is that IIS will first handle the. axd file, and then hand it to freetextboxcontrols. assemblyresourcehandler, the class named freetextbox for processing instead of letting ASPnet process it. 
 
However, your server provider may remove the asping from. axd to aspnet_isapi.dll for security reasons, so you will be wrong when running on the server. The only thing you can do now is to contact your server provider to restore the ing. 
 
 
Extension:. axd 
Execution file: C: \ WINDOWS \ Microsoft. NET \ framework \ v1.1.4322 \ aspnet_isapi.dll 
 
Restrictions: Get, Head, post, debug 
Script Engine check