Use this dialog box to add or modify wildcard script map ISAPI applications that are executed for every request, regardless of the file name extension. Using wildcard script maps is similar to using ISAPI filters, except that wildcard script maps can be installed on virtual directories as well as Web sites, they have access to the body of a request, they are not event-driven, and the ISAPI extension API has more functionality than the ISAPI filter API. A virtual directory inherits only wildcard script maps from its parent virtual directory or Web site if it doesn’t contain its own wildcard script maps.


Type the name of the executable file (.exe or .dll). The executable file must be located on your Web server's local hard disk.


Click to locate your Web server's local hard disk for the ISAPI application.

Verify that file exists

Select Verify that file exists to instruct the Web server to verify the existence of the requested script file and to ensure that the requesting user has access permission for that script file. If the script does not exist or the user does not have permission, the appropriate warning message is returned to the browser and the script engine is not invoked. This option can be useful for scripts mapped to non-CGI executables, such as the Perl interpreter, that do not send a CGI response if the script is not accessible. Because the script must be opened twice, once by the server and once by the script engine, enabling this option can impact performance.

Related Topics

To learn more about configuring applications and about wildcard application mappings, see the IIS 6.0 online documentation on the Microsoft Windows Server TechCenter.