Share via

Initial Settings (Compact 2013)

  • Article

3/26/2014

The ASP interpreter processes a file with an .asp extension when it is requested by the client browser, assuming that the following conditions outlined in the following sections 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 http://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.

These additional conditions must be met for the ASP interpreter to process .asp files when requested by the client browser:

  • The httpisapi, httpextn, and httpasp components must be included when building the web server. If they are not, the web server returns the 501 – Not Implemented status code and an error message informing the user of the problem.
  • The JScript.dll or VBScript.dll file must be set up properly on the device. If the requested script language is not present on the device or has not been initialized, the web server returns an error.

See Also

Concepts

Active Server Pages Application Development
Web Server Implementation Details