In IIS 6.0, there are two settings that have always puzzled me. Although they have been used in projects, I always feel that I have a vague understanding of them, that is, "application ". Program Extension and wildcard application ing ".
A few days ago, using the gap between projects, I checked some information on the Internet, combined with the applications in my project, I had some preliminary understanding of these two settings, and now I have sorted them out, discuss with you:
-
- In "application extension", you can set the request processing method for a specific extension, for example. aspx ,. ascx ,. asmx ,. ashx is set to "C: \ WINDOWS \ microsoft.net \ framework \ v2.0.50727 \ aspnet_isapi.dll. You can add a new extension, such as. Happy, to c: \ windows \ microsoft.net \ framework \ v2.0.50727 \ aspnet_isapi.dll.
-
- In "application extension", when adding a new ing, the extension name column cannot be entered directly. * ", but can only be filled in the form of". specific extensions such as aspx, which are useful for "wildcard application ing. Insert a "wildcard application ing". For example, if you insert "c: \ windows \ microsoft.net \ framework \ v2.0.50727 \ aspnet_isapi.dll", all requests with extension names are forwarded by "C: \ windows \ microsoft.net \ framework \ v2.0.50727 \ aspnet_isapi.dll.
- when we add corresponding. happy extension ing, or simply adding "wildcard application ing", directly enter "http: // localhost/webapplication1/haha" in the address bar. "Happy" still reports an error because "C: \ WINDOWS \ microsoft.net \ framework \ v2.0.50727 \ aspnet_isapi.dll" is not provided by default. happy request processing, so we still need. the config file is added for processing. the handler of the happy request, for example:
of course, Specifically, the webapplication1.myhandler class needs to be written by ourselves. You can implement the ihttphandler interface.
