The Web Application Mapping Properties Page

This dialog allows you to map a certain web document type to a desired script processor that can handle the corresponding script type.

Mapping

Extension

You can set the web document extension to be mapped to this script processor.

You can configure wildcard script maps by setting the extension field to: * .

Script Processor

You can set the script processor file for the new web application mapping. The file can be from the installation package or external.

This field is of Formatted Type and can be edited with the Smart Edit Control.

Behavior

Script engine

Select this option 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.

Check that file exists

Select this 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 send a CGI response if the script is not accessible.

Because the script will be opened twice, once by the server and once by the script engine, there is some performance cost to enabling this option.

HTTP Verbs

Allows you to set the HTTP verbs that should be passed to an application.

These verbs are: GET, POST, HEAD, TRACE, PUT, DELETE, OPTIONS.

For a detailed explanation of these HTTP/1.1 methods please see: HTTP Methods article.