IIS Modules Overview

Introduction

The IIS 7 and above Web server feature set is componentized into more than thirty independent modules.

A module is either a Win32 DLL (native module) or a .NET 2.0 type contained within an assembly (managed module).

Similar to a set of building blocks, modules are added to the server in order to provide the desired functionality for your applications.

Likewise, all IIS modules can be removed, or replaced with custom modules developed using the IIS C++ APIs, or the familiar ASP.NET 2.0 APIs.

This article describes common IIS module management tasks,

and details each module including its configuration settings and the potential effect a module removal has on the Web server.

The management examples are given using both the graphical IIS Manager and the AppCmd command line tool.

Prerequisites

首先要安装IIS

Getting Started with Modules

In order to add a module to the server, you must perform two steps:

1. Install a module on the server (native modules only).
2. Enable the module in an application.

The first step registers the module globally with the server, making it available within each server worker process.

It is necessary only for native modules due to the trusted nature of native code, and is available only to administrators.

Note:

A native module has unrestricted access to any resource available to the server worker process, just like an ISAPI filter or extension in previous versions.

Because of this unrestricted access, you should install only native modules that come from a trusted source.

The second step enables the module to execute within a particular application and effectively allows the application administrator to control the server features enabled for the application.

This step allows both installed native modules and managed modules to be enabled for each application.

To Install a Native Module

In order to install a native module, it must be registered with the server using one of the options below:

• Manually editing the IIS configuration store. In IIS 7.5 and later you can use the Configuration Editor in the IIS Manager.
• Using the IIS Manager
• Using the AppCmd.exe command line tool

All three of these options result in the module entry being added to the <globalModules> IIS configuration section, which can be set only at the server level.

To examine the contents of this section, open the root configuration file located in %windir%\system32\inetsrv\config\applicationhost.config, and search for the string "<globalModules>".

After a full IIS installation, this section contains an entry for each of the native modules shipped with IIS, specifying a name and the path to the module DLL:

<globalModules>
    <addname="DefaultDocumentModule"image="%windir%\system32\inetsrv\defdoc.dll"/>
    <addname="DirectoryListingModule"image="%windir%\system32\inetsrv\dirlist.dll"/>
    <add name="StaticFileModule"image="%windir%\system32\inetsrv\static.dll"/>
    ...

</globalModules>

All of these modules are described in detail later in this document.

在IIS Manager中，按照如下步骤可以找到对应的Modules

1.打开IIS，在Features View中，找到Management，然后打开Configuration Editor

2.在Configuration Editor中，点击Search

3.输入globalModules进行搜索

3.1搜索页面，有两种视图，默认为Hierarchy View，直接显示出所有的config文件

FlatView，直接列出config文件，看起来比较直观，一下子就看到有几个文件

4.在第三步定位到globalModules的位置后，关闭搜索界面

5.在Configuration Editor下的Section中找到globalModules

6.在显示出来的Collection上的空白处点击一下，右侧出现浏览按钮。最右侧还有一个EditItems的按钮

7.找到对应的Module就可以进行remove

8.左侧的导航栏，可以选中Site处理Site的config；处理Application的config，需要单独选中Application，然后再选择Config Editor

Enabling a Module for an Application

A module must be enabled before it can provide service for a particular application. In order to enable a native module, it must first be installed on the server (see the previous section, To Install a Native Module).

A managed module does not require installation, and can be enabled directly for each application. This allows applications to include their managed modules directly within the application by registering them in the application's web.config file, and providing the implementation in /BIN or /App_Code directories.

To enable a module, do one of the following:

• Manually edit the IIS configuration store, either globally to enable the module for all applications on the server, or in a particular web.config file located within each application for which you would like to enable this module. In IIS 7.5 or above you can use the Configuration Editor.
• Use the IIS Manager
• Use the AppCmd.exe command line tool

All three of these options add the module entry to the <modules> IIS configuration section, which is can be set at both the server level and application level. Examine the contents of this section by opening the root configuration file located in %windir%\system32\inetsrv\config\applicationhost.config, and searching for the string "<modules>".

Unlike native modules, a managed module does not require adding an entry to the <globalModules> configuration section.

After a full IIS installation, the configuration section contains an entry for each of the modules (both managed and native) that shipped with IIS. The entry indicates that all these modules are enabled by default for all applications on the server. Each entry in this section specifies either the name of a native module that was previously installed on the server, or the name and .NET type of a managed module:

Preconditions

There is another attribute on a module entry called precondition. The IIS core engine uses preconditions to determine when to enable a particular module.

Performance reasons, for example, might determine that you only want to execute managed modules for requests that also go to a managed handler.

The precondition in the following example (precondition="managedHandler") only enables the forms authentication module for requests that are also handled by a managed handler, such as requests to .aspx or .asmx files:

<addname="FormsAuthentication"type="System.Web.Security.FormsAuthenticationModule" preCondition="managedHandler" />

If you remove the attribute precondition="managedHandler", Forms Authentication also applies to content that is not served by managed handlers, such as .html, .jpg, .doc, but also for classic ASP (.asp) or PHP (.php) extensions.

See "How to Take Advantage of IIS Integrated Pipeline" for an example of enabling ASP.NET modules to run for all content.

You can also use a shortcut to enable all managed (ASP.NET) modules to run for all requests in your application, regardless of the "managedHandler" precondition.

To enable all managed modules to run for all requests without configuring each module entry to remove the "managedHandler" precondition, use the runAllManagedModulesForAllRequests property in the <modules> section:

<modules runAllManagedModulesForAllRequests="true"/>

When you use this property, the "managedHandler" precondition has no effect and all managed modules run for all requests.

https://autofaccn.readthedocs.io/en/latest/integration/webforms.html

 <system.webServer>
    <!-- This section is used for IIS7 -->
    <modules>
      <add
        name="ContainerDisposal"
        type="Autofac.Integration.Web.ContainerDisposalModule, Autofac.Integration.Web"
        preCondition="managedHandler"/>
      <add
        name="PropertyInjection"
        type="Autofac.Integration.Web.Forms.PropertyInjectionModule, Autofac.Integration.Web"
        preCondition="managedHandler"/>
    </modules>
  </system.webServer>