CGI / pl SCRIPT wanting to download not exercute.

[pittbull]

Hi,

I have installed Suse10.2 and setup apache2 to host some family domains/websites without pulling out to much of my hair.

the problem i am having is some of my cgi scripts run and others that used to work don't anymore they want to download.

i have set permissions to 755 via command line for the scripts in question.
Aswell as checking and re-checking the locations and paths were correct.

on a html page When you click the link " in this case a localhost/directory/filename.pl " the file wants to download and fails.

( yes the file does live at the correct path )

i have other cgi / pl files that work fine.. both locally and via internet.
can anyone please give me some direction to look for a answer.

thank you
John

[gogalthorp]

What language are the failing scripts written in?? The scripts that run??

[pittbull]

Blosxom works and so does a environmental checker. 100% perl ( i think )


Sorry i couldnt find what language these were made in and did not know how to find out.

formmail for Matts script archive Doesnt.

a Addon to Blosxom doesnt... recieved this answer from the author..


__________________________________________________ _______________
That's always strange when that happens.

Often I find it is caused by one of two things:

1. The permissions on the script are not set to execute.
2. The script is not sending the correct header information-- some browser are more fussy about getting the correct header so if you switched browsers that could be why you noticed it.


__________________________________________________ _______________

The 1st answer is: The file is in the cgi-bin and not in sub directory and the file has been set by " chmod 755 filename.cgi/pl " or " chmod 755 *.cgi/pl "
in the command line loged in as root.

i have changed broswer because the computer was running windows and apache.but even accessing the file via local intranet or internet the same thing happens ( IE6, IE7, Firefox, )

[gogalthorp]

Most likely perl from the extension but that is no gaurentee. You might look at the first few line of the scripts and see what is different between the ones that work and those that don't. There may be something like a path that is hard coded. Also there might be version confilicts in the base language used (perl?) and what you have installed. Or a missing library, or one that can't be found.