What you need to know in each version of IIS

& http: //www.aliyun.com/zixun/aggregation/37954.html "> nbsp; currently used in the market on the IIS version is estimated to be> = 6. Therefore, we mainly to explain the following three versions

Second, IIS6 request process

It can be seen from the figure that all the requests are intercepted by the http.sys component in the server and it will look for which Application Pool the Application belongs to based on the Metabase in IIS if the Application Pool does not exist. Otherwise, the Request will be sent directly to the corresponding Application Pool Queue.

Each Application Pool corresponds to a Worker Process: w3wp.exe. Maintaining Application Pool and w3wp mappings in IIS Metabase. Based on such a mapping, the WAS (Web Administrative service) passes the request that exists in an Application Pool Queue to the corresponding worker process (or create such a process if it is not). When the worker process is initialized, load the ASP.NET ISAPI.

In the meantime, within w3wp.exe, ASP.NET is added to IIS as an IIS ISAPI extension (in fact, ASP and PHP are included in the same way), and ASP.NET ISAPI loads the CLR. Thus creating a managed runtime for the ASP.NET Application. Two important dlls are loaded during initial CLR use: AppManagerAppDomainFactory and ISAPIRuntime. Create an Application Domain for Application through the Create method of AppManagerAppDomainFactory; Process Request through ISAPIRuntime ProcessRequest, and then drag the process into ASP.NET Http Runtime Pipeline

Note: ISAPI, meaning: Internet Server Application Program Interface.

Third, IIS7 working process

HTTP.sys snooping intercepts client requests to begin processing.

HTTP.sys contacts WAS through configuration information for relevant information.

WAS requests the configuration storage center for configuration information. applicationHost.config.

WWW service receives configuration information, configuration information refers to similar application pool configuration information, site configuration information and so on.

The WWW service uses the configuration information to configure the HTTP.sys handling policy.

WAS opens the W3WP Worker Process for the application pool corresponding to this request.

After the W3WP Worker Process processes the response, it returns Response to HTTP.sys.

The client receives the Response content.

Note: We call 3-6 for the initialization configuration process, the configuration is completed, the subsequent request directly to the seventh step.Of course, IIS was restarted, it over.

Third, IIS7 program pool hosting pipeline mode

W3WP.exe process in IIS7 how to work, depending on IIS7 application pool hosting pipeline mode is what, IIS7 There are two modes: the classic mode and integrated mode

We all know the classic meaning, is a way that has been used (for everyone to remember), IIS7 classic mode W3WP.exe way of working is IIS6 processing.

Namely: IIS ISAPI extension, that is, aspnet_isapi.dll

IIS7 integration mode is a great improvement, so that IIS integrated. NET function (not relying on the previous version of IIS aspnet_ISPAI.DLL), which means that all requests for HTTP Request to go through. NET to deal with (including html, php, etc.) , But also because many of the features of .NET have become part of IIS 7. Performance has also been improved.

Fourth, IIS8 and IIS7 What are the different places

1. IIS 8.0 can only run on> = Windows Server 2012 and Windows 8 platforms;

2. IIS 8.0 Application initialization is included in IIS 8.0 IIS 7.5 Application Initialization (RC) is used as a takeover module;

3. IIS 8.0 Administration Tools has been updated for ASP.net 4.5 features. Not yet in IIS 7.5;

4. IIS 8.0 integrates SSL authentication support. IIS 7.5 has not;

5. IIS 8.0 CPU throttling has been updated and includes additional throttling options, while IIS 7.5 has not changed;

6. IIS 8.0 integrates dynamic IP address limiting capabilities

7. IIS 8.0 integrated FTP attempt to login restrictions.

8. IIS 8.0 multicore extension on NUMA;

Original link: http: //www.cnblogs.com/humble/p/3917895.html