How do I setup X2 for cgi scripts?

usalabs · - Joined: 14 Nov 2005 Posts: 18

I have installed activeperl, and set the interpreter for perl.exe but the only 'type' settings are 'Standard, PHP style, and Activeperl ISAPI', I've tried using perl.exe on standard, (with extensions pl, and cgi) it threw an error 500 at me, when I try to execute a cgi script, the same with PHP style, then I tried the 'perlis.dll with the type 'Activeperl ISAPI' and every cgi script shows:-

Content-type: text/html

'D:\websites\forum\admin\adm.cgi' script produced no output

Is there anything that should go in the MIME section?, such as 'application/x-httpd-pl' and 'application/x-httpd-cgi' for it to work.

I've used PHP sucessfully, without the MIME setting.

TRUSTAbyss · - Joined: 29 Oct 2003 Posts: 3752 Location: USA, GA

PHP already sends the Content MIME Type, while Perl does not. You have to manually tell Perl that it is to be used as HTML. Use "Standard" if you're not using Perl as an ISAPI module.

Example code:

aprelium · - Joined: 22 Mar 2002 Posts: 6800

usalabs,

We strongly recommend that you do not use Perl ISAPI unless you are ready to tweak your scripts to work with it (most scripts will work fine with it but some of them won't unless you modify them).

So we suggest that you install Perl support as explained in http://www.aprelium.com/abyssws/perl.html .

If you receive Error 500, this usually means that your script contains an error (or has a problem). In such a case, inspect the cgi.log file for a detailed error report.
_________________
Support Team
Aprelium - http://www.aprelium.com

usalabs · - Joined: 14 Nov 2005 Posts: 18

aprelium · - Joined: 22 Mar 2002 Posts: 6800

usalabs · - Joined: 14 Nov 2005 Posts: 18

Well, after paying a lot of bucks for a professional server installation engineer, to try and figure out the errors, he tried 50 cgi scripts with various Abyss configurations, and using the same configuration on IIS6, he came to the conclusion that cgi does not work in Abyss, every one of those 50 cgi scripts caused an internal server error, he said "1 or 2, possibily 3 scripts could be bad, but not all 50", he then tried all 50 scripts using IIS6 using the same perl interpreter, and every one of the 50 cgi scripts worked.

I may have discovered a serious flaw in the core of X2.

rrinc · - Joined: 24 Feb 2006 Posts: 725 Location: Arkansas, USA

Are you using an up to date version of Perl and Abyss? Have you followed the instructions on the Aperlium website?
_________________
-Blake | New Server :D
SaveTheInternet
Soy hispanohablante. Puedes contactarme por mensajes privados.

aprelium · - Joined: 22 Mar 2002 Posts: 6800

usalabs · - Joined: 14 Nov 2005 Posts: 18

I have zipped up a folder containing a few scripts that form an entire program, and (for security reasons), I removed certain details (such as usernames, passwords, etc etc) from the X2 config file, and pasted it as an rtf file for attachment.

The 2 files have been emailed to Aprelium

aprelium · - Joined: 22 Mar 2002 Posts: 6800

usalabs,

We have reviewed your configuration and it seems that the whole issue was caused by a partially bad declaration of the Perl interpreter: In your configuration you have entered "cgi pl" (C G I <space> P L) as the extension handled by Perl. This is not exactly what you should put there.

So please delete that extension, and enter cgi (C G I) as the first extension, next add pl (P L) as the second one. Do not put them on the same line and at the same time. Otherwise Abyss Web Server will consider that files such as "test.cgi pl" are the only ones to be handled by Perl while "test.cgi" will be ignored and not processed (because ".cgi pl" is different from ".cgi" and ".pl").

So we suggest that you review the extensions part in http://www.aprelium.com/abyssws/perl.html :