Shell-Cgi on windows (Coldfusion and PERL)
I'm running SJSWS 7.o on Win Server 2003. I have configured it to work with CFMX 7 as well as shell-cgi. I require both for new development and supporting legacy PERL programs.
My problem is this. If I limit the shell-cgi to a single directory all works fine, but if I set the shell-cgi to the entire document root, the coldfusion files will not work. It should be possible to serve both file types from the same directories. Is there something I'm missing in the configuration or will I have to limit the the shell-cgi to a single directory.
Again, any help would be appreciated
# 1
The better solution would be to enable CGI as a file type for the entire virtual-server. This way, you will instruct the server to treat all files with certain extensions as CGI programs, regardless of which directory they reside in.
Note : If you are on windows, you also have to create a mime-type for shellcgi (magnus-internal/shellcgi).
# 2
That was what I originally tried to do to no avail.
By creating a shellcgi directory and modifying the <vi-s-id>_conf.conf file (i.e adding - NameTrans fn="pfx2dir" from="/cgi-bin", dir="<dir_path>" name="shellcgi", which the system did not add) the perl and cgi files worked within that directory, but CF files would not and if I modified the directory to the entire document root, PERL and CGI would work, but again CF would not.
I removed the directory and made sure the cgi as file type was selected. CF worked but no cgi or perl.
I checked the mime types and there was an entry for cgi and shellcgi, but both were referencing the same file types (cgi, exe, pl). I deleted the magnus-internal/cgi mime type and everything works as it should.
Thanks for the help...
null
# 3
And the saga continues...
NOTE: Running on Win Server 2003
Basic Perl scripts work fine. But if the script calls a template file, it crashes. It's looking for the template files in the same directory as the perl.exe instead of the same directory as the calling perl file.
If I enter the fully qualified directory (i.e. root:/webserver/..) it will work, but that would be a lot of code to modify... ALOT. Is there a way to create a mapping so that the perl will see the template?
Again, any input would be appreciated...
Message was edited by:
tbugler_01
