Shulou(Shulou.com)06/02 Report--

This article mainly explains "how to build the HTTP module and processor of ASP.NET". Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to build the HTTP module and processor of ASP.NET.

At the beginning of the Internet era, the needs of clients were very limited; .htm files could meet their needs. However, over time, the expansion of client requirements goes beyond the functionality contained in .htm files or static files. Developers need to extend or extend the functions of the Web server. Web server vendors have designed different solutions, but they all follow the same theme of "inserting certain components into the Web server." All Web server supplement technologies allow developers to build and insert components to enhance the functionality of the Web server. Microsoft proposed ISAPI (Internet server API), Netscape proposed NSAPI (Netscape server API) and so on.

ISAPI is an important technology that allows us to enhance the capabilities of ISAPI-compatible Web servers (IIS is an ISAPI-compatible Web server). We use the following components to do this:

ISAPI extension

ISAPI filter

ISAPI extensions are implemented using Win32 dynamic link libraries. You can think of the ISAPI extension as a normal application. The target of the ISAPI extension is to process http requests. This means that you have to call them to activate them. You can think of the ISAPI filter as just a filter. Each time the client sends a request to the server, the request goes through a filter. Instead of specifying a filter in the request, the client simply sends the request to the Web server, which then passes the request to the relevant filter. Next, the filter may modify the request, perform some login operations, and so on.

Because of the complexity of these components, implementing them is very difficult. Developers have to develop these components using Cmax Cure +, but for many people, using it is simply a byword for pain.

So what does ASP.NET provide to implement these functions? ASP.NET provides HttpHandler (HTTP processor) and HttpModule (HTTP module).

Before delving into the details of these components, it is valuable to understand how http requests are processed as they pass through the HTTP module and HTTP handlers.

Set up a sample application

I set up some of the following C# projects to demonstrate the different components of the application:

NewHandler (HTTP processor)

Webapp (demo HTTP handler)

SecurityModules (HTTP module)

Webapp2 (demo HTTP module)

The installation steps for these applications:

Unlock all the code in the attached zip file.

Create two virtual directories webapp and webapp2; to point them to the actual physical directories of the Webapp and Webapp2 applications.

Copy the Newhandler.dll file from the NewHandler project to the bin directory of the webapp application.

Copy the SecurityModules.dll file from the SecurityModules project to the bin directory of the webapp2 application.

At this point, I believe you have a deeper understanding of "how to build the HTTP module and processor of ASP.NET". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.