I've loaded the script in ASCII, CHMOD'd the correct permissions in the cgi-bin directory and the script executes with a 200 in the log. The problem is nothing happens. However, I can run "Hello World" scripts in the cgi-bin. I'm perplexed.
All I've got is FTP access to this server which is apparently Linux running Apache. I'd like to tell the client that this host is clueless, but I'm not sure how to troubleshoot this. My suspicion is that the cgi-bin wasn't set up properly. However, how could I go about proving that?
I had a similar problem awhile back using a FormMail script. Had no troubles until we changed web hosting companys. They provided a cgi-bin that just wouldn't execute the script. I FTPed the script myself, and did everything that you had mentioned (ASCII transfer, permissions etc..)
The script only worked when one of the technical support guys downloaded the file and installed it himself into the CGI-Bin.
To this day, I don't know why the script wouldn't execute via my FTP.
Can anyone explain why this happened?
Cheers,
Chad
As you may be able to tell I'm in over my head here ;)
I just got a cryptic message from the host saying something to the effect that they will try to exclude my script filename on their configuration. Let's see if they can't fix some of this... <grrr...>
I'm not sure what to make of this, but the host got the script to work. Essentially they told me that their Perl Handler settings were not compatible with the script I was using. They said that because my script contained "__END__" that it was not compatible with their Perl Handler. I'm not really sure about the details of this. Somehow they couldn't bypass the Perl Handler to process my script, so their solution was to change my script's filename to any extention but ".cgi" or ".pl".
The script does work now, but does this sound like there may be setup problems on their side? I get the feeling they're kludging about a bit...