Iis isapi extension of ASP. NET

ASP.net request processing in IIS 7

The IIS7 site starts and processes the request as follows:

Steps 1 to 6 are to process application startup. After the application is started, you do not need to perform this step again.

The eight steps are as follows:

1. When the client browser initiates an HTTP request for a WEB server resource, HTTP. sys intercepts the request.

2. HTTP. sys contacts WAS to obtain information from the configuration store.

3. WAS requests configuration information from the configuration storage center. ApplicationHost. config.

4. the WWW Service receives the configuration information, which is similar to the application pool configuration information and site configuration information.

5. Use the configuration information of the WWW Service to configure the HTTP. sys processing policy.

6. WAS starts a worker process for the application pool to which the request was made.

7. The worker process processes the request and returns a response to HTTP. sys.

8. The client receives the processing result information.

What if the W3WP.exe process is processed ?? The managed pipeline mode of the application pool of IIS 7 is divided into two types: Classic and integration. In these two modes, the processing policies are different.

Architecture of managed pipelines in IIS 6 and IIS7 in Classic Mode

Before IIS7, ASP. NET is added to IIS in the form of iis isapi extension. In fact, both ASP and PHP are configured in the same way. (PHP adopts two configuration methods in IIS, in addition to the iis isapi extension method and CGI method, the system administrator can select the PHP program execution method). Therefore, the client will first process the HTTP request to IIS through IIS, then, IIS handles HTML static Web Pages Based on the required content type. If not, it assigns them to their respective iis isapi extension based on the required content type; if the requested content type is ASP. NET.. net iis isapi extension, that is, aspnet_isapi.dll. This is the architecture.

The classic mode of the managed pipeline mode of the IIS 7 Application pool also works. This mode is compatible with IIS 6 to reduce the upgrade cost.

Managed pipeline mode integration mode of IIS 7 Application pool

IIS 7 is fully integrated. NET, the processing order of the architecture is significantly different (for example), the main reason is ASP. NET from the IIS plug-in (ISAPI extension) role, enter the IIS core, and can also use ASP. the NET module is responsible for handling many types of IIS 7 Requirements. These ASP. the NET module cannot only process ASP. NET web applications, such as ASP, PHP, or static HTML web pages. NET has become a part of IIS 7, so ASP, PHP, or static HTML web pages can also use Forms Authentication) or Output Cache and other ASP.. NET 2.0 (but the setting value of IIS 7 must be modified ). Because IIS 7 allows you to use ASP.. net api development and add modules, so ASP. NET web developers will be more likely to expand the functions of IIS 7 and website applications, and even can independently. NET Program for managing IIS 7 (for example, program-controlled IIS 7 to build a website or virtual directory ).

The preceding section describes the iis isapi extension of ASP. NET.

1. Analysis on PageBase and MasterPage of ASP. NET
2. XML Web Service Method of ASP. NET
3. Detailed description of ASP. NET environment deployment
4. Implement ASP. NET globalization
5. Solve the Problem of ASP. net ajax script errors