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

What are the characteristics of IIS7.0? I believe many inexperienced people don't know what to do about it. Therefore, this article summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

IIS 7.0 is highly integrated with the ASP.NET framework and provides a complete API, thus providing a complete scalability and management interface for the platform. Configuration delegation and a complete diagnostic suite are also provided, which can track requirements and provide advanced logging capabilities. IIS 7. 0 integrates ASP.NET with the request pipeline, which is perhaps the most significant change made by IIS 7.

The modular design of IIS 7.0is also helpful for us to develop custom modules, and the additional functions are easier to implement. This is conducive to the better combination of internally developed functions and IIS, third-party resources and IIS, and even better integration of functions developed by Microsoft and IIS. This is because these modules and add-ons can work as plug-ins for IIS at any time without modifying the core functions of the operating system, so Microsoft's IIS development team can release functional modules outside Microsoft's standard service pack process.

Integrated request pipeline

One of the biggest changes in IIS 7.0is its tight integration with ASP.NET and ASP.NET processes. IIS 7.0provides a unified event pipeline that combines two existing separate pipes, the IIS pipe and the ASP.NET pipe, provided by IIS 6.0and previous versions of IIS. ASP.NET 's HTTP module, which used to listen only for events in the ASP.NET pipeline, can now listen for any request. For backward compatibility, IIS 7.0also provides Classic pipeline mode, which simulates either IIS pipeline of IIS 6.0or ASP.NET pipeline of IIS 6.0. the Classic pipeline mode can also simulate the IIS pipeline of IIS 6.0. for backward compatibility, it also provides the pipeline mode of IIS.

IIS 7. 0 provides a single unified pipeline. Forms authentication and role management provided by ASP.NET are part of the authentication and authorization process, so a request is validated only once. In IIS 7.0, all requests are processed by ASP.NET 's Forms authentication module, not just those files with an .ASPX extension that need to be processed by ASP.NET 's Forms authentication module. For example, the request for www.domain1.com/images/myimage.gif is first passed to ASP.NET 's Forms authentication process, and if some authentication method in the web.config file denies access to the file or folder, users who lack permissions will not be able to view or download the image. Now pass the request to the pipe and exit, and then pass it to the browser that made the request, so there is no need to pass it to the ISAPI process such as ASP.NET. For compatibility reasons, although the ISAPI handler needs to return an exit code when exiting, the request is not actually processed in ISAPI, and if we don't need to consider the compatibility of the legacy code, we don't even need to load the ISAPI handler.

Within the IIS 7.0 pipeline, each process is handled by a separate component. Web sites that need to use these components can load these components separately, and if the site or application does not need to use these components in the pipeline, then there is no need to load these components. At the application level, the site level, and the server level, these components are configurable, and we can delegate the configuration functionality of the component at any of these levels. In addition, we can insert custom components into the pipe, and even reorder the execution order of the components in the pipe. For example, when a request starts to execute, a log trace operation can be triggered, and when the request is finished processing, the log trace is written to a file. The order in which the components are executed is the order in which the components are in the configuration file.

Configurability

Another change in IIS 7.0is that the configuration process of IIS has been integrated into the configuration process of ASP.NET applications, which is a fairly significant change. Now we no longer need to use the IIS registry settings, and metabase, which was originally used as an IIS configuration library, has been replaced by a XML-based configuration file in which both IIS and ASP.NET settings are saved. This not only removes the boundaries between ASP.NET applications and application servers, but also improves the configurability of IIS and simplifies the deployment process of websites and applications. At the same time, it is more convenient to deploy applications on multiple systems in web farm, and the scalability of the configuration is improved. IIS 7.0introduces the concept of shared configuration, in which multiple web servers can use the same physical file as their own configuration file, so that if we make changes to the configuration of web farm, the changes can take effect immediately.

Now, IIS 7.0 saves settings using a file called applicationHost.config. In addition, for a stand-alone Web website or Web application, the configuration options for IIS 7.0 can also be saved in the web.config file along with the ASP.NET settings, of course, the configuration options for IIS 7.0 are saved in the system.webServer section of that file.

1. Use applicationHost.config profile

IIS 7.0uses the file applicationHost.config to save the IIS configuration for the Web server and the integrated model, and the global configuration is now saved in the applicationHost.config file in the% windir%\ system32\ inetsrv\ config directory, which consists of two main sections:

(1) system.applicationHost holds the configuration information of websites, applications, virtual directories and application pools.

(2) other settings and global default settings are saved in this part of system.webServer.

The configuration of the URL location can be saved either in the applicationHost.config file or in web.config. This allows the administrator to set the default settings on the server, and the developer can redefine these settings if necessary. These settings can be inherited by web.config files at the root and application levels. This is important when delegating settings, because IIS administrators can allow developers to control settings at the application level with fine granularity, while IIS administrators can also control settings at the site level.

two。 Scalable configuration architecture

With the new configuration model, IIS 7.0configuration can be easily extended. Now, suppose we need to create a new module for IIS. At this point, you need to indicate the DLL file for the module in the section of the applicationHost.config file, and then declare the module in the applicationHost.config file or in the appropriate web.config file. Configuring a schema for a new module extension is as simple as creating a schema file in the system's inetsrv\ config\ schema directory. You can do this by adding a section to the configuration section of the applicationHost.config file.

Componentization

The scalability of IIS 7.0is not only reflected in the configuration process. Because IIS 7.0 has modified the request processing pipeline, the core server itself has been extended by using native and managed code. This expansibility comes from the componentization of the core functions of IIS. Instead of using ISAPI filters to modify the request process, we can inject the self-developed components directly into the processing pipeline. The self-developed components can be either our own developed components, third-party tools or components, or existing core components provided by Microsoft. So, if you don't like the Windows authentication process, you can not only use the forms authentication process for all files, but you can also choose to ignore all built-in authentication processes and adopt the authentication process we developed. It also means that if you don't need to deal with traditional ASP files, you just need to stop loading the corresponding components. In previous versions of IIS, each component needed to be loaded into memory as a separate DLL, and now there is no need to load extraneous content, thus reducing the overhead of IIS 7.0.

After reading the above, have you mastered the methods of IIS7.0 features? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

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.