IIS 6.0 F1: New Web Service Extension
Applies To: Windows Server 2008 R2
In an effort to reduce the attack surface of your Web server, IIS 6.0 serves only static content after a default installation. Programmatic functionality provided by IIS APIs (ISAPIs) or Common Gateway Interfaces (CGIs) must be manually enabled by an IIS administrator. ISAPIs and CGIs extend the ability of your Web pages and for this reason ISAPIs and CGIs are referred to here as Web service extensions. For example, in order to run Active Server Pages (ASP) with this version of IIS, the ISAPI Asp.dll must be enabled as a new Web service extension.
Use the options in this dialog box to enable or disable specific ISAPIs or CGIs.
|ISAPI filters are not considered Web service extensions. ISAPI filters are not enabled through this dialog box.|
|For a Web service extension to run, the ISAPI or CGI must be located in the content directory on your server running IIS (for example, LocalDrive:\Inetpub\wwwroot for a default installation).|
Type the friendly name of the ISAPI or CGI (for example, Microsoft® FrontPage® Server Extensions).
This is a list of all of the ISAPIs or CGIs required for the Web service extension to run. For example, FrontPage Server Extensions is composed of five files and all five files need to be enabled before you can begin extending Web pages with FrontPage Server Extensions.
Click to select required files.
Click to remove the currently selected file from the list.
Set extension status to Allowed
Select to allow the Web service extensions to run on your server. Clear this option to prohibit Web service extensions from running on your Web server. For example, by entering Nimda.dll information in this dialog box and then setting the status to Prohibit (status when option is cleared), you prohibit Nimda.dll from running on your Web server.
To learn more about Web service extensions and configuring applications, see the IIS 6.0 online documentation on the Microsoft Windows Server TechCenter.