IIS on Nano Server

Applies To: Windows Server Technical Preview

Overview of IIS on Nano Server

You can install the Internet Information Services (IIS) server role on Nano Server by using the -Packages parameter with Microsoft-NanoServer-IIS-Package. For information about configuring Nano Server, including installing packages, see Get Started with Nano Server.

In this release of Nano Server, the following IIS features are available:

A series of articles on other configurations of IIS (such as using ASP.NET, PHP, and Java), as well as other related content is published at https://iis.net/learn.

Installing IIS on Nano Server

You can install this server role either offline (with the Nano Server off) or online (with the Nano Server running); offline installation is the recommended option.

For offline installation, add the package with the -Packages parameter of New-NanoServerImage, as in this example:

New-NanoServerImage -MediaPath f:\ -BasePath .\Base -TargetPath .\Nano1.vhd -GuestDrivers -Packages Microsoft-NanoServer-IIS-Package

If you have an existing VHD file, you can install IIS offline with DISM.exe by navigating to the directory where the Nano Server VHD is, mount the VHD, and use the Add-Package option. The specific commands are:

1. md mountdir

2. dism\dism /Mount-Image /ImageFile:.\NanoServer.vhd /Index:1 /MountDir:.\mountdir

3. dism\dism /Add-Package /PackagePath:.\packages\Microsoft-NanoServer-IIS-Package.cab /Image:.\mountdir

4. dism\dism /Add-Package /PackagePath:.\packages\en-us\Microsoft-NanoServer-IIS-Package.cab /Image:.\mountdir

5. dism\dism /Unmount-Image /MountDir:.\MountDir /Commit

At this point you can start the Nano Server with IIS.

Installing IIS on Nano Server online

Though offline installation of the server role is recommended, you might need to install it online (with the Nano Server running) in container scenarios. To do this, follow these steps:

1. Copy the Packages folder from the installation media locally to the running Nano Server (for example, to C:\packages).

2. Create a new Unattend.xml file, either on another computer (followed by copying the file to the Nano Server) or remotely on the Nano Server by using Windows PowerShell remoting. To do the latter, use New-Item unattend.xml followed by Psedit unattend.xml to copy and paste this XML content into the XML file you created:

   <?xml version="1.0" encoding="utf-8"?>
   <unattend xmlns="urn:schemas-microsoft-com:unattend">
       <servicing>
           <package action="install">
               <assemblyIdentity name="Microsoft-NanoServer-IIS-Package" version="10.0.10586.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
               <source location="c:\packages\Microsoft-NanoServer-IIS-Package.cab" />
           </package>
           <package action="install">
               <assemblyIdentity name="Microsoft-NanoServer-IIS-Package" version="10.0.10586.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="en-US" />
               <source location="c:\packages\en-us\Microsoft-NanoServer-IIS-Package.cab" />
           </package>
       </servicing>
       <cpi:offlineImage cpi:source="" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
   </unattend>
   

3. In the new XML file you created (or copied), edit C:\packages to the directory you copied the content of Packages to.

4. Switch to the directory with the newly created XML file and run

   dism /online /apply-unattend:.\unattend.xml

   You will receive a 0x80004005 error ("DISM failed. No operation was performed"), but you can safely ignore it. The IIS server role is correctly installed.

5. Confirm that the IIS package and its associated language pack is installed correctly by running:

   dism /online /get-packages

   You should see "Package Identity : Microsoft-NanoServer-IIS-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0" listed twice, once for Release Type : Language Pack and once for Release Type : Feature Pack.

6. Start the W3SVC service either with net start w3svc or by restarting the Nano Server.

Starting IIS

Once IIS is installed and running, it is ready to serve web requests. Verify that IIS is running by browsing the default IIS web page at https://<IP address of Nano Server>. On a physical computer, you can determine the IP address by using the Recovery Console. On a virtual machine, you can get the IP address by using a Windows PowerShell prompt and running:

Get-VM -name <VM name> | Select -ExpandProperty networkadapters | select IPAddresses

If you are not able to access the default IIS web page, double-check the IIS installation by looking for the c:\inetpub directory on the Nano Server.

Enabling and disabling IIS features

A number of IIS features are enabled by default when you install the IIS role (see the table in the "Overview of IIS on Nano Server" section of this topic). You can enable (or disable) additional features in three ways:

• Using the IISAdministration module for Windows PowerShell remotely

• Using AppCmd.exe remotely

• Manually editing the IIS configuration store

This topic will detail using the IISAdministration module. For examples of using AppCmd.exe, see IISModules Overview. For general information about the IISAdminstration module, see IISAdministration PowerShell Cmdlets.

Each feature of IIS exists as a set of configuration elements. For example, the Windows authentication feature comprises these elements:

The full set of these configuration elements for all of the IIS features available in this release is included in Appendix 1 of this topic.

The IISAdministration module of Windows PowerShell allows you to easily add or remove these configuration elements to the applicationhost.config file. Here are three examples using this method: one for installing the Windows authentication feature, one for removing the Windows authentication feature, and one for installing the Default Document feature.

Example: installing Windows authentication

1. In a Windows PowerShell remote session console on the Nano Server, import the Windows PowerShell module for IISAdministration with Import-Module IISAdministration.

2. Add the configuration elements to the <globalModules> section with this scriptlet:

   # refresh the in-memory image of the config
   Reset-IISServerManager -Confirm:$false
   
   $section = Get-IISConfigSection "system.webServer/globalModules"
   $collection = Get-IISConfigCollection -ConfigElement  $section
   New-IISConfigCollectionElement $collection -ConfigAttribute @{"name"="WindowsAuthenticationModule";"image"="%windir%\System32\inetsrv\authsspi.dll"}
   

3. Add the configuration elements to the <modules> section with this scriptlet:

   $section = Get-IISConfigSection "system.webServer/modules"
   $collection = Get-IISConfigCollection -ConfigElement  $section
   New-IISConfigCollectionElement $collection -ConfigAttribute @{"name"="WindowsAuthenticationModule"}
   

4. Add the configuration elements to the <windowsAuthentication> section with this scriptlet. You might find it helpful to view the IIS schema file (%windir%\system32\inetsrv\config\schema\iis_schema.xml) to see how to navigate through the XML.

   # delay writes for the New-, Set-* calls, since we're writing to the same section multiple times and we don't want to have to
   # keep calling Get-IISConfigSection to get a fresh copy.
       Start-IISCommitDelay
   
   $section = Get-IISConfigSection "system.webServer/security/authentication/windowsAuthentication"
   
   Set-IISConfigAttributeValue -ConfigElement $section -AttributeName "enabled" -AttributeValue $false
   
   Set-IISConfigAttributeValue -ConfigElement $section –AttributeName "authPersistNonNTLM" -AttributeValue $true
   
   $collection = Get-IISConfigElement -ConfigElement $section –ChildElementName "providers" | Get-IISConfigCollection
   
   New-IISConfigCollectionElement -ConfigCollection $collection –ConfigAttribute @{"value"="Negotiate"}
   
   New-IISConfigCollectionElement -ConfigCollection $collection -ConfigAttribute @{"value"="NTLM"} 
   
   # commit the changes to disk 
   Stop-IISCommitDelay
   

Example: uninstalling Windows authentication

To uninstall a feature, delete the <globalModules> and <modules> elements, and then delete the contents of the <windowsAuthentication> section (in this example). To do this with Windows PowerShell, pipe commands transfer the output of one cmdlet to following cmdlets.

The exact operations required might vary for different features. For example, for Windows authentication, the <windowsAuthentication> section has five attributes and two child elements. Deleting the two collection elements and the providers element is adequate for uninstalling the feature, but you could delete all five aReplaceThisText

ttributes and the <extendedProtection> element as well.

1. In a Windows PowerShell remote session console on the Nano Server, import the Windows PowerShell module for IISAdministration with Import-Module IISAdministration.

2. Run this scriptlet:

   Get-IISConfigSection "system.webServer/globalModules" | Get-IISConfigCollection | `
       Remove-IISConfigCollectionElement -ConfigAttribute @{"name"="WindowsAuthenticationModule"} -Confirm:$false
   
   Get-IISConfigSection "system.webServer/modules" | Get-IISConfigCollection | `
       Remove-IISConfigCollectionElement -ConfigAttribute @{"name"="WindowsAuthenticationModule"} -Confirm:$false
   

3. Run this scriptlet:

   Start-IISCommitDelay
   
   $section = Get-IISConfigSection   "system.webServer/security/authentication/windowsAuthentication"
   
   Remove-IISConfigAttribute -ConfigElement $section -AttributeName "enabled" -confirm:$false
   
   Remove-IISConfigAttribute -ConfigElement $section -AttributeName "authPersistNonNTLM"
   
   Get-IISConfigElement -ConfigElement $section -ChildElementName "providers" | Remove-IISConfigElement -Confirm:$false
   
   # commit the changes to disk
   Stop-IISCommitDelay
   

Example: Installing Default Document

Though Default Document is installed by default, it makes a good example because it includes further elements such as StaticFile in the <handlers> section. In addition to adding elements to <globalModules> and <modules> as in the Windows authentication example, you must also add or modify these additional elements. Before installing or uninstalling any IIS features, refer to the detailed elements in the Appendix to note all elements that you must modify.

1. In a Windows PowerShell remote session console on the Nano Server, import the Windows PowerShell module for IISAdministration with Import-Module IISAdministration.

2. Add the required elements to <globalModules> and <modules> with scriptlets similar to the ones in Steps 2 and 3 of the Windows authentication example.

3. Add or modify the StaticFile element in the <handlers> section and add additional elements that <defaultDocument> requires with this scriptlet:

   # refresh the in-memory image of the config
   Reset-IISServerManager -Confirm:$false
   
   # delay writes until we're done working with this section
   Start-IISCommitDelay
   
   $collection = Get-IISConfigSection "system.webServer/handlers" | Get-IISConfigCollection 
   $element = Get-IISConfigCollectionElement $collection -ConfigAttribute @{"name"="StaticFile"}
   
   if($element -eq $null)
   {
       # we didn't find the element, so create it
       New-IISConfigCollectionElement $collection -ConfigAttribute @{"name"="StaticFile";"path"="*"; `
           "verb"="*";"modules"="DefaultDocumentModule";"resourceType"="Either";"requireAccess"="Read"}
   }
   else
   {
       # we found the element, so read the modules attribute
       $modules = Get-IISConfigAttributeValue -ConfigElement $element -AttributeName "modules"
   
       if(-not $modules.Contains("DefaultDocumentModule"))
       {
           $modules = "$modules,DefaultDocumentModule"
           Set-IISConfigAttributeValue -ConfigElement $element -AttributeName "modules" -AttributeValue $modules
       }
   }
   
   # now commit the changes to disk
   Stop-IISCommitDelay
   

Other common IIS configuration tasks

Creating websites

Use this cmdlet:

PS D:\> New-IISSite -Name TestSite -BindingInformation "*:80:TestSite" -PhysicalPath c:\test

You can then run Get-IISSite to verify the state of the site (returns the web site name, ID, state, physical path, and bindings).

Deleting web sites

Run Remove-IISSite -Name TestSite -Confirm:$false.

Creating virtual directories

You can create virtual directories by using the IISServerManager object returned by Get-IISServerManager, which exposes the .NET Microsoft.Web.Administration.ServerManager API. In this example, these commands access the "Default Web Site" element of the Sites collection and the root application element ("/") of the Applications section. They then call the Add() method of the VirtualDirectories collection for that application element to create the new directory:

PS C:\> $sm = Get-IISServerManager
PS C:\> $sm.Sites["Default Web Site"].Applications["/"].VirtualDirectories.Add("/DemoVirtualDir1", "c:\test\virtualDirectory1")
PS C:\> $sm.Sites["Default Web Site"].Applications["/"].VirtualDirectories.Add("/DemoVirtualDir2", "c:\test\virtualDirectory2")
PS C:\> $sm.CommitChanges()

Creating application pools

Similarly you can use Get-IISServerManager to create application pools:

PS C:\> $sm = Get-IISServerManager
PS C:\> $sm.ApplicationPools.Add("DemoAppPool")

Configuring HTTPS and certificates

Use the Certoc.exe utility to import certificates, as in this example, which shows configuring HTTPS for a website on a Nano Server:

1. On another computer that is not running Nano Server, create a certificate (using your own certificate name and password), and then export it to c:\temp\test.pfx.

   $newCert = New-SelfSignedCertificate -DnsName "www.foo.bar.com" -CertStoreLocation cert:\LocalMachine\my

   $mypwd = ConvertTo-SecureString -String "YOUR_PFX_PASSWD" -Force -AsPlainText

   Export-PfxCertificate -FilePath c:\temp\test.pfx -Cert $newCert -Password $mypwd

2. Copy the test.pfx file to the Nano Server computer.

3. On the Nano Server, import the certificate to the "My" store with this command:

   certoc.exe -ImportPFX -p YOUR_PFX_PASSWD My c:\temp\test.pfx

4. Retrieve the thumbprint of this new certificate (in this example, 61E71251294B2A7BB8259C2AC5CF7BA622777E73) with Get-ChildItem Cert:\LocalMachine\my.

5. Add the HTTPS binding to the Default Web Site (or whatever website you want to add the binding to) by using these Windows PowerShell commands:

   $certificate = get-item Cert:\LocalMachine\my\61E71251294B2A7BB8259C2AC5CF7BA622777E73
   # Use your actual thumbprint instead of this example
   $hash = $certificate.GetCertHash()
   
   Import-Module IISAdministration
   $sm = Get-IISServerManager
   $sm.Sites["Default Web Site"].Bindings.Add("*:443:", $hash, "My", "0")    # My is the certificate store name
   $sm.CommitChanges()
   

   You could also use Server Name Indication (SNI) with a specific host name with this syntax: $sm.Sites["Default Web Site"].Bindings.Add("*:443:www.foo.bar.com", $hash, "My", "Sni".

Appendix 1: Elements of HTTP features

Each feature of IIS exists as a set of configuration elements. This appendix lists the configuration elements for all of the features in this release of Nano Server

Common HTTP features

Default document

<globalModules>

<add name="DefaultDocumentModule" image="%windir%\System32\inetsrv\defdoc.dll" />

<modules>

<add name="DefaultDocumentModule" lockItem="true" />

<handlers>

<add name="StaticFile" path="*" verb="*" modules="DefaultDocumentModule" resourceType="EiSecther" requireAccess="Read" />

<defaultDocument>

<defaultDocument enabled="true">
    <files>
        <add value="Default.htm" />
        <add value="Default.asp" />
        <add value="index.htm" />
        <add value="index.html" />
        <add value="iisstart.htm" />
    </files>
</defaultDocument>

The StaticFile <handlers> entry might already be present; if so, just add "DefaultDocumentModule" to the <modules> attribute, separated by a comma.

Directory browsing

<globalModules>

<add name="DirectoryListingModule" image="%windir%\System32\inetsrv\dirlist.dll" />

<modules>

<add name="DirectoryListingModule" lockItem="true" />

<handlers>

<add name="StaticFile" path="*" verb="*" modules="DirectoryListingModule" resourceType="Either" requireAccess="Read" />

The StaticFile <handlers> entry might already be present; if so, just add "DirectoryListingModule" to the <modules> attribute, separated by a comma.

HTTP errors

<globalModules>

<add name="CustomErrorModule" image="%windir%\System32\inetsrv\custerr.dll" />

<modules>

<add name="CustomErrorModule" lockItem="true" />

<httpErrors>

<httpErrors lockAttributes="allowAbsolutePathsWhenDelegated,defaultPath">
    <error statusCode="401"    prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="401.htm" />
    <error statusCode="403" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="403.htm" />
    <error statusCode="404" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="404.htm" />
    <error statusCode="405" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="405.htm" />
    <error statusCode="406" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="406.htm" />
    <error statusCode="412" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="412.htm" />
    <error statusCode="500" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="500.htm" />
    <error statusCode="501" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="501.htm" />
    <error statusCode="502" prefixLanguageFilePath="%SystemDrive%\inetpub\custerr" path="502.htm" />
</httpErrors>

Static content

<globalModules>

<add name="StaticFileModule" image="%windir%\System32\inetsrv\static.dll" />

<modules>

<add name="StaticFileModule" lockItem="true" />

<handlers>

<add name="StaticFile" path="*" verb="*" modules="StaticFileModule" resourceType="Either" requireAccess="Read" />

The StaticFile <handlers> entry might already be present; if so, just add "StaticFileModule" to the <modules> attribute, separated by a comma.

HTTP redirection

<globalModules>

<add name="HttpRedirectionModule" image="%windir%\System32\inetsrv\redirect.dll" />

<modules>

<add name="HttpRedirectionModule" lockItem="true" />

<httpRedirect>

<httpRedirect enabled="false" />

Health and diagnostics

HTTP logging

<globalModules>

<add name="HttpLoggingModule" image="%windir%\System32\inetsrv\loghttp.dll" />

<modules>

<add name="HttpLoggingModule" lockItem="true" />

<httpLogging>

<httpLogging dontLog="false" />

Custom logging

<globalModules>

<add name="CustomLoggingModule" image="%windir%\System32\inetsrv\logcust.dll" />

<modules>

<add name="CustomLoggingModule" lockItem="true" />

Request monitor

<globalModules>

<add name="RequestMonitorModule" image="%windir%\System32\inetsrv\iisreqs.dll" />

Tracing

<globalModules>

<add name="TracingModule" image="%windir%\System32\inetsrv\iisetw.dll" />
<add name="FailedRequestsTracingModule" image="%windir%\System32\inetsrv\iisfreb.dll" />

<modules>

<add name="FailedRequestsTracingModule" lockItem="true" />

<traceProviderDefinitions>

<traceProviderDefinitions>
    <add name="WWW Server" guid="{3a2a4e84-4c21-4981-ae10-3fda0d9b0f83}">
        <areas>
            <clear />
            <add name="Authentication" value="2" />
            <add name="Security" value="4" />
            <add name="Filter" value="8" />
            <add name="StaticFile" value="16" />
            <add name="CGI" value="32" />
            <add name="Compression" value="64" />
            <add name="Cache" value="128" />
            <add name="RequestNotifications" value="256" />
            <add name="Module" value="512" />
            <add name="FastCGI" value="4096" />
            <add name="WebSocket" value="16384" />
        </areas>
    </add>
    <add name="ISAPI Extension" guid="{a1c2040e-8840-4c31-ba11-9871031a19ea}">
        <areas>
            <clear />
        </areas>
    </add>
</traceProviderDefinitions>

Performance

Static content compression

<globalModules>

<add name="StaticCompressionModule" image="%windir%\System32\inetsrv\compstat.dll" />

<modules>

<add name="StaticCompressionModule" lockItem="true" />

<httpCompression>

<httpCompression directory="%SystemDrive%\inetpub\temp\IIS Temporary Compressed Files">
    <scheme name="gzip" dll="%Windir%\system32\inetsrv\gzip.dll" />
    <staticTypes>
        <add mimeType="text/*" enabled="true" />
        <add mimeType="message/*" enabled="true" />
        <add mimeType="application/javascript" enabled="true" />
        <add mimeType="application/atom+xml" enabled="true" />
        <add mimeType="application/xaml+xml" enabled="true" />
        <add mimeType="*/*" enabled="false" />
    </staticTypes>
</httpCompression>

Dynamic content compression

<globalModules>

<add name="DynamicCompressionModule" image="%windir%\System32\inetsrv\compdyn.dll" />

<modules>

<add name="DynamicCompressionModule" lockItem="true" />

<httpCompression>

<httpCompression directory="%SystemDrive%\inetpub\temp\IIS Temporary Compressed Files">
    <scheme name="gzip" dll="%Windir%\system32\inetsrv\gzip.dll" />
    <dynamicTypes>
        <add mimeType="text/*" enabled="true" />
        <add mimeType="message/*" enabled="true" />
        <add mimeType="application/x-javascript" enabled="true" />
        <add mimeType="application/javascript" enabled="true" />
        <add mimeType="*/*" enabled="false" />
    </dynamicTypes>
</httpCompression>

Security

Request filtering

<globalModules>

<add name="RequestFilteringModule" image="%windir%\System32\inetsrv\modrqflt.dll" />

<modules>

<add name="RequestFilteringModule" lockItem="true" />

<requestFiltering>

<requestFiltering>
    <fileExtensions allowUnlisted="true" applyToWebDAV="true" />
    <verbs allowUnlisted="true" applyToWebDAV="true" />
    <hiddenSegments applyToWebDAV="true">
        <add segment="web.config" />
    </hiddenSegments>
</requestFiltering>

Basic authentication

<globalModules>

<add name="BasicAuthenticationModule" image="%windir%\System32\inetsrv\authbas.dll" />

<modules>

<add name="WindowsAuthenticationModule" lockItem="true" />

<basicAuthentication>

<basicAuthentication enabled="false" />

Client certificate mapping authentication

<globalModules>

<add name="CertificateMappingAuthentication
Module" image="%windir%\System32\inetsrv\authcert.dll" />

<modules>

<add name="CertificateMappingAuthenticationModule" lockItem="true" />

<clientCertificateMappingAuthentication>

<clientCertificateMappingAuthentication enabled="false" />

Digest authentication

<globalModules>

<add name="DigestAuthenticationModule" image="%windir%\System32\inetsrv\authmd5.dll" />

<modules>

<add name="DigestAuthenticationModule" lockItem="true" />

<other>

<digestAuthentication enabled="false" />

IIS client certificate mapping authentication

<globalModules>

<add name="CertificateMappingAuthenticationModule" image="%windir%\System32\inetsrv\authcert.dll" />>

<modules>

<add name="CertificateMappingAuthenticationModule" lockItem="true" />

<clientCertificateMappingAuthentication>

<clientCertificateMappingAuthentication enabled="false" />

IP and domain restrictions

<globalModules>

<add name="IpRestrictionModule" image="%windir%\System32\inetsrv\iprestr.dll" />
<add name="DynamicIpRestrictionModule" image="%windir%\System32\inetsrv\diprestr.dll" />

<modules>

<add name="IpRestrictionModule" lockItem="true" />
<add name="DynamicIpRestrictionModule" lockItem="true" />

<ipSecurity>

<ipSecurity allowUnlisted="true" />

URL authorization

<globalModules>

<add name="UrlAuthorizationModule" image="%windir%\System32\inetsrv\urlauthz.dll" />

<modules>

<add name="UrlAuthorizationModule" lockItem="true" />

<authorization>

<authorization>
    <add accessType="Allow" users="*" />
</authorization>

Windows authentication

<globalModules>

<add name="WindowsAuthenticationModule" image="%windir%\System32\inetsrv\authsspi.dll" />

<modules>

<add name="WindowsAuthenticationModule" lockItem="true" />

<windowsAuthentication>

<windowsAuthentication enabled="false" authPersistNonNTLM="true">
    <providers>
        <add value="Negotiate" />
        <add value="NTLM" />
    </providers>
</windowsAuthentication>

Application development

Application initialization

<globalModules>

<add name="ApplicationInitializationModule" image="%windir%\System32\inetsrv\warmup.dll" />>

<modules>

<add name="ApplicationInitializationModule" lockItem="true" />

CGI

<globalModules>

<add name="CgiModule" image="%windir%\System32\inetsrv\cgi.dll" />
<add name="FastCgiModule" image="%windir%\System32\inetsrv\iisfcgi.dll" />

<modules>

<add name="CgiModule" lockItem="true" />
<add name="FastCgiModule" lockItem="true" />

<handlers>

<add name="CGI-exe" path="*.exe" verb="*" modules="CgiModule" resourceType="File" requireAccess="Execute" allowPathInfo="true" />

ISAPI extensions

<globalModules>

<add name="IsapiModule" image="%windir%\System32\inetsrv\isapi.dll" />

<modules>

<add name="IsapiModule" lockItem="true" />

<handlers>

<add name="ISAPI-dll" path="*.dll" verb="*" modules="IsapiModule" resourceType="File" requireAccess="Execute" allowPathInfo="true" />

ISAPI filters

<globalModules>

<add name="IsapiFilterModule" image="%windir%\System32\inetsrv\filter.dll" />

<modules>

<add name="IsapiFilterModule" lockItem="true" />

Server-side includes

<globalModules>

<add name="ServerSideIncludeModule" image="%windir%\System32\inetsrv\iis_ssi.dll" />

<modules>

<add name="ServerSideIncludeModule" lockItem="true" />

<handlers>

<add name="SSINC-stm" path="*.stm" verb="GET,HEAD,POST" modules="ServerSideIncludeModule" resourceType="File" />
<add name="SSINC-shtm" path="*.shtm" verb="GET,HEAD,POST" modules="ServerSideIncludeModule" resourceType="File" />
<add name="SSINC-shtml" path="*.shtml" verb="GET,HEAD,POST" modules="ServerSideIncludeModule" resourceType="File" />

<serverSideInclude>

<serverSideInclude ssiExecDisable="false" />

WebSocket protocol

<globalModules>

<add name="WebSocketModule" image="%windir%\System32\inetsrv\iiswsock.dll" />

<modules>

<add name="WebSocketModule" lockItem="true" />