I am using the basic Home Linux package from 1&1 and have never been able to get Perl CGIs to run with the .cgi extension. Trying to run install.cgi from the Fileman setup was no exception, so I changed the file extension to .pl. This loaded the installation page, but when I submitted the direct path information, it once again called install.cgi. I then went in to install.dat and changed all intances of .cgi to .pl, taking care to include the .cgi and not just "cgi" by itself. This resulted in the following error on the install.pl page:
I tried this several times, including going through one instance at a time and replacing, just to make sure there was no obvious way this was going to break the script. However, all was to no avail. I have also tried many times altering my .htaccess file to include the CGI handler (AddHandler cgi-script .cgi), but this modification only results in an internal server error. I am in the process of trying several alternatives scripts I found at http://www.hotscripts.com/search/8040012-1.html (EFileMan at http://www.efileman.de/, for example, looks particularly promising, though I have not yet had occasion to test it). I would very much like to at least test Fileman out, but it appears that the .cgi extension is going to make that impossible. Does anyone know first of all how to get the .cgi extension to work on 1&1's Linux systems? (I've combed the Web hundreds of times and never been able find a solution other than modifying the .htaccess file as I suggested I have already tried.) And if not, does anybody have any ideas on how to modify the install files so that they will run using the .pl extension instead?
An error occured:
install.dat appears to be corrupted. Please make sure you transfer the file in BINARY mode when using FTP. Otherwise you may have a corrupted file, and you should try downloading a new file from Gossamer Threads. If you need assistance, please visit: http://gossamer-threads.com/scripts/support/
I tried this several times, including going through one instance at a time and replacing, just to make sure there was no obvious way this was going to break the script. However, all was to no avail. I have also tried many times altering my .htaccess file to include the CGI handler (AddHandler cgi-script .cgi), but this modification only results in an internal server error. I am in the process of trying several alternatives scripts I found at http://www.hotscripts.com/search/8040012-1.html (EFileMan at http://www.efileman.de/, for example, looks particularly promising, though I have not yet had occasion to test it). I would very much like to at least test Fileman out, but it appears that the .cgi extension is going to make that impossible. Does anyone know first of all how to get the .cgi extension to work on 1&1's Linux systems? (I've combed the Web hundreds of times and never been able find a solution other than modifying the .htaccess file as I suggested I have already tried.) And if not, does anybody have any ideas on how to modify the install files so that they will run using the .pl extension instead?
Re: [mrrena] ".cgi" extension fouling the waters