How To use Pi3Web with ASP and Cold Fusion: ASP

ASP 1.0, the one that came with IIS 3.0 is an ISAPI extension. Pi3Web is an ISAPI 2.0 compliant web server, capable of running both ISAPI filters and extensions. Like ASP, the same way Pi3Web is capable of running other ISAPI based scripting programs like Cold Fusion or iHTML, but the last one wasn't tested yet.

The feature to run ASP 1.0 is available with Pi3Web 1.03 and 2.00. For both releases a package is available in the download area at sourceforge.

1.2 Step by step advise

In order to install ASP support for Pi3Web follow these steps:

You must first install IIS 2.0 or 3.0. You will never have to start IIS, but the components need to be present. You can find the setup program for IIS 2.O on the NT installations disk in the i386\inetsrv directory. PWS 1.0 on Windows 95/98 works also.
Then install the ASP support from Microsoft. The installer is a 9 MB file called ASP.exe. After you run ASP.exe you will have IIS 3.0. You can find ASP.exe on the FrontPage 97 CD, the Service Pack 3 CD or at several FTP locations.

Now configure Pi3Web to map all URL's ending with '.asp' to the ASP handler. Add the following path mapping to the existing "Start" handler and then the appropriate new "ASPMapper" object in the Config.pi3 or whatever configuration file you have:

<Object>
        Name Start
        ...
        Mapping Condition="&or(&regexp('*.asp',$U),&regexp('*.asp',$f))" ASPMapper From="/" To="WebRoot\"
        ...
</Object>

<Object>
        Name ASPMapper
        Class PathMapperClass
        PathInfo "No"
        Action "&dbreplace(response,string,ObjectMap,ISAPI)"
        Action "&dbreplace(response,string,PathInfo,&dblookup(response,string,ScriptName))"
        Action "&dbreplace(response,string,PathTranslated,&dblookup(response,string,Path))"
        Action "&dbreplace(response,string,Path,..\\ISAPI\\asp.dll)"
</Object>

The regular expressions in the above mapping allow

to include invokation of ASP scripts in SSI by using the '#exec virtual' directive
to call ASP scripts from each physical subfolder of WebRoot
don't allow QueryString or PathInfo to be passed to the script as part of the mapped URL

If you use a simple directory based mapping, as used for CGI or ISAPI you may

include invokation of ASP scripts in SSI by using the '#exec virtual' directive
to call ASP scripts only from physical subfolders of the mapped directory
pass QueryString or PathInfo to the script as part of the mapped URL

1.3 Important Notes

ASP 2.0 that comes with option pack 4 is intended to run only with IIS 4.0 and the Transaction Server. This is a proprietary ASP and will not run with Pi3Web. This is also true for ASP support in PWS 4.0.
If you have already installed option pack 4 you will have to start at step 2. in the above step by step advise.
When ASP 2.0 (option pack 4) is put on the system it is installed in winnt/sytem32/inetsrv/asp.dll. ASP 1.0 installs itself in winnt/sytem32/inetsrv/asp/asp.dll. Pi3Web can use the older ASP DLL (winnt/sytem32/inetsrv/asp/asp.dll ) and IIS 4.0 can use the newer ASP DLL and it appears that the two can coexist on the same machine.
If any ISAPI extension like the ASP script engine takes to long, it will be timed out by the server. It seems ASP.DLL isn't stable in case of termination by Pi3Web. Because it is a DLL it runs within the process of the server and could easily kill the server (one of the disadvantages of ISAPI). So take care that the timeout value is properly adjusted in ISAPI.cnf:
```
<Object>
        Name ISAPI20
        Class ISAPI20Class
        ExtraHeadersPrefix HTTP_
        AsynchTimeout 90
</Object>
 
```
You can also run asp.dll as a normal ISAPI extension and give the ASP script as PATH_INFO parameter without any extra configuration effort:
```
http://localhost/isapi/asp.dll/welcome.asp
 
```

1. ASP

1.1 Preferences

1.2 Step by step advise

1.3 Important Notes