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

This article mainly introduces the characteristics of IIS 7.0, the content is comprehensive and rich in knowledge points, and it is helpful for partners who want to understand IIS. The following information is about the features of IIS 7.0.

IIS 7.0 is highly integrated with the ASP.NET framework and provides a complete API that provides complete extensibility and management interfaces for the platform. Configuration delegation and a complete diagnostic suite are also provided, which can trace requirements, as well as advanced logging capabilities. IIS 7.0 integrates ASP.NET with the request pipeline, perhaps the most significant change IIS 7.0 has made.

IIS 7.0's modular design also allows us to develop custom modules, and additional features are easier to implement. Therefore, it is beneficial to better combine the functions developed internally with IIS, and it is also beneficial to better combine the third party resources with IIS, and even beneficial to better combine the functions developed by Microsoft with IIS. This is because these modules and add-ons work as plug-ins to IIS whenever they do not require changes to core operating system functionality, so Microsoft's IIS development team can deliver functional modules outside of Microsoft's standard service pack process.

Integrated request pipeline

One of the biggest changes in IIS 7.0 is that it can be tightly integrated with ASP.NET and ASP.NET processes. IIS 7.0 provides a unified event pipeline that merges two existing separate pipelines, IIS Pipeline and ASP.NET Pipeline, provided by IIS 6.0 and earlier versions of IIS. ASP.NET's HTTP module, which used to listen only for events from ASP.NET pipelines, can now listen for any request. For backward compatibility, IIS 7.0 also provides Classic Pipeline mode, which emulates IIS 6.0 IIS Pipeline or IIS 6.0 ASP.NET Pipeline.

IIS 7.0 provides a single unified pipe. Forms authentication and role management provided by ASP.NET are part of the authentication and authorization process, so a request is authenticated only once. In IIS 7.0, all requests are processed by the ASP.NET Forms authentication module, not just files with the.ASPX extension. For example, a request to www.domain1.com/images/myimage.gif is first passed to the Forms authentication process of ASP.NET, 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. The request is now passed to the pipe and exits, and then to the requesting browser, so there is no need to pass it to ISAPI processes such as ASP.NET. Given compatibility issues, although the ISAPI handler needs to return an exit code when it exits, the request is not actually processed in the ISAPI, and we don't even need to load the ISAPI handler if we don't need to consider legacy code compatibility.

Inside the IIS 7.0 pipeline, each process is handled by a separate component. Websites that need to use these components can load them separately, and if the site or application doesn't need to use them in the pipeline, they don't have to. These components are configurable at the application, site, and server levels, and we can delegate component configuration functionality at any of these levels. In addition, we can insert custom components into the pipeline and even reorder the execution order of components in the pipeline. For example, a log trace operation can be triggered when the request starts executing, and written to a file when the request finishes processing. The order in which components are executed is the order in which they are placed in the configuration file.

configurability of

Another change in IIS 7.0 is that IIS configuration processes have been integrated into ASP.NET application configuration processes, which is a fairly significant change. We no longer need to use IIS registry settings, and metabase has been replaced as an IIS repository by an XML-based configuration file that holds both IIS settings and ASP.NET settings. This not only removes the boundary between ASP.NET applications and application servers, but also improves IIS configurability and simplifies the deployment of Web sites and applications. It is also easier to deploy applications on multiple systems in a web farm and improves configuration scalability. IIS 7.0 introduces 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 the web farm, the changes will take effect immediately.

IIS 7.0 now uses a file named applicationHost.config to save settings. In addition, IIS 7.0 configuration options for a standalone Web site or Web application can be saved in the web.config file along with ASP.NET settings. Of course, IIS 7.0 configuration options are saved in the system.webServer section of that file.

1. Using the applicationHost.config configuration file

IIS 7.0 uses the file applicationHost.config to save IIS configuration for Web servers and integration models. The global configuration is now saved in the applicationHost.config file in the %windir%\system32\inetsrv\config directory, which consists of two main parts:

(1) system.applicationHost This section holds configuration information for websites, applications, virtual directories, and application pools.

(2) system.webServer This section holds other settings and global defaults.

Configuration of URL locations can be saved either in the applicationHost.config file or in web.config. This allows administrators to set default settings on the server, and developers to redefine those settings if necessary. These settings can be inherited at the root and application levels by web.config files. This is important when delegating settings because IIS administrators allow developers to control settings at a very granular level at the application level, while IIS administrators also have control over settings at the site level.

2. Scalable configuration architecture

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

componentized

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

After reading the above contents, do you have a general understanding of the characteristics of IIS 7.0? If you want to know more about related articles, welcome to pay attention to 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.