Initial Settings
A version of this page is also available for
4/8/2010
The ASP interpreter processes a file with an .asp extension when it is requested by the client browser, assuming that the following conditions are met:
- The virtual root where the ASP file is located must have the permissions set to HSE_URL_FLAGS_EXECUTE or HSE_URL_FLAGS_SCRIPT. If this is not the case, the Web Server returns the 403 – Forbidden status code, along with an Access Denied message.
- If Asp.dll is missing or corrupt, the Web Server returns the 500 – Internal Server Error, status code to the client browser.
You can map a virtual path to a specific ASP file instead of a directory. For example, a client browser could request https://www.computername.com/directory and be mapped to a specific ASP file, such as Finance.asp. Using the functionality is identical to mapping virtual paths to ISAPI extensions. For more information, see ISAPI Extensions.
Like ISAPI dynamic-link libraries (DLLs), the Web Server keeps Asp.dll and any libraries that ASP loads — including JScript.dll, VBScript.dll, and any DLLs that contain COM objects that were created on the page — in a cache. The Web Server unloads the DLLs in this cache automatically if they have not been used for 30 minutes. This delay is defined by a setting in the system registry.