See CSAPP part of the contents of Web Server, associate often use IIS, so be prepared to understand a little. P9 ~ p15.
IIS7 properties
Integrated pipeline
IIS 7.0 and the ASP.NET request pipeline integration, IIS 7 provides a unified event pipeline, there is a separate two kinds of pipe before -. IIS and ASP.NET pipeline pipeline for backward compatibility, IIS 7 provides Classic pipeline mode, you can simulate pipeline IIS IIS 6.0, ASP.NET pipeline can be simulated with IIS 6.0.
IIS6 Request Process
Browser -> (IIS pipeline) HTTP.SYS -> request processing, judgment is static, or CGI, or ISAPI, if it is ISAPI, but also to distinguish PERL, ASPX, PHP -> (ASP.NET pipeline) ASPNET_ISAPI.dll processing -> returns the results to HTTP.SYS -> back to the browser.
IIS7 request process
Browser -> (Integrated pipe) HTTP.SYS -> request processing, judgment is static, or ASPX, or the ISAPI ->
execution returns to HTTP.SYS After completion of the -> returns to the browser
For .aspx file, ISAPI treatment process is not required.
Configurability
Another variation is IIS7, do not require a separate configuration of IIS, IIS configurations can be configured in the application. IIS7 applicationHost.config named using a File Save Settings, saved to a file web.config, the IIS system.webServer a configuration is saved in the web.config.
Componentization
Developers can develop their own components directly injected into the processing pipeline, you do not need to use an ISAPI filter to modify the requesting process. If you do not like windows authentication, forms authentication may be used, or ignore all of the built-in authentication, we have developed and employed Authentication.