Add/Edit Application Extension Mapping
Use the Add/Edit Application Extension Mappings dialog box to add or modify the mapping between a file name extension and the program or interpreter that processes those files. Use the Browse button to search for the appropriate executable file for the application on your local hard disk or a network.
In the Method Exclusions box, type the names of any HTTP methods that should not be passed to an application. For example, you might want to prohibit the HTTP PUT or DELETE methods. Separate method names with a comma (,).
Select the Script Engine check box when you want the application to run in a directory without Execute permissions. This setting is intended primarily for script-based applications such as ASP and IDC that are mapped to an interpreter. For a script-mapped application to run, either the Script or Execute access check box must be selected for the directory in which the application is located. To allow only script-mapped applications to run, use the Script access. To allow both script-mapped applications and executable files (.exe and .dll) to run, use the Execute access.
Select the Check that File Exists option 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 like the Perl interpreter that do not know to send a CGI response if the script is not accessible. Because the script will get opened twice, once by the server and once by the script engine, there is some performance cost to enabling this option.