ScriptMaps Metabase Property
The ScriptMaps property specifies the file name extensions of applications used for script processor mappings. The list string is written in the following format:
"Extension, ScriptProcessor, Flags, IncludedVerbs"
Where Extension is the file name extension, such as .htm, ScriptProcessor is the full path to the DLL, Flags is the integer value corresponding to the requested behavior described in the Bitmask Table, and IncludedVerbs is a list of the verbs that a particular ISAPI DLL processes.
For example, to specify the file extension for the ISAPI "Test.dll" with a file extension of ".htm", you might provide the following list (string):
".htm,C:\Windows40\System32\Inetsrv\Test.dll,5,GET, HEAD, POST"
Note IIS allows an "*" in place of the file name extension, which effectively routes all requests though the designated ScriptProcessor. This feature is useful when applying a custom ISAPI extension that will handle requests from all file types.
In IIS version 4.0 and earlier, the syntax was to list excluded verbs rather than included verbs. In version 5.0 and later, if no verbs are listed, a value of "all verbs" is assumed. You should list the verbs you want your ISAPI filter or extension to handle.
|Attribute Name||Attribute Value|
XML Data Type
WMI Data Type
ADSI Data Type
ABO Data Type
ABO Metabase Identifier
You can configure this property at the following locations in the IIS metabase.
|Metabase Path||IIS Admin Object Type|
Scripts are allowed to run in directories given Script permission. If this value is not set, then the script can only be run in directories that are flagged for Execute permission.
The server attempts to access the PATH_INFO portion of the URL, as a file, before starting the scripting engine. If the file can't be opened, or doesn't exist, an error is returned to the client.
For general code examples, see Code Examples to Configure Metabase Properties.
Contribuições da comunidade