The steps for the IIS7 site to start and process the request are shown below:
Steps 1 through 6, is to process the application startup, after the boot is good, no longer need to go this step.
The 8 steps in the above diagram are as follows:
- When the client browser starts HTTP requests for a Web server's resources, HTTP.sys intercepts the request.
- HTTP.sys contacts is to obtain information from the configuration store.
- was requested configuration information from the Configuration Storage Center. ApplicationHost.config.
- The WWW service accepts configuration information, which refers to similar application pool configuration information, site configuration information, and so on.
- The WWW service uses configuration information to configure HTTP.sys processing policies.
- Was starts a worker process for the "application pool to which" request was made.
- The worker process processes the request and returns a response to HTTP.sys.
- The client receives the processing result information.
What if it is handled in the W3WP.exe process?? The managed piping pattern for the application pool of IIS 7 is divided into two types: classic and integrated. In both modes, the processing strategy is not communicated.
The author of this article: Guo Hongjun HTTP://BLOG.JOYCODE.COM/GHJ
IIS 6 and the schema of managed piping in IIS7 Classic mode
Prior to IIS7, ASP.net was added to IIS as an IIS ISAPI extension, in fact including ASP and PHP, all in the same way (PHP uses two configurations in IIS, except for the IIS ISAPI extension side Type, also includes the CGI way, the System Manager can choose the PHP program execution Way), therefore the client's HTTP request to IIS will be processed first through IIS, then IIS according to the request content type, if is the HTML static webpage to be handled by IIS, if not, according to the request The content type, which is assigned to the respective IIS ISAPI extension, and if the requested content type is asp.net, it is assigned to the IIS ISAPI extension that handles the ASP.net, which is the ASPNet_isapi.dll. The diagram below is a schematic diagram of this architecture.
The Classic mode of the managed piping mode of the IIS 7 application pool works as well. This mode is compatible with IIS 6 to reduce the cost of upgrades.
IIS6 execution architecture diagram, and IIS7 application pool configuration as a classic mode of execution architecture diagram