Jul 23, 2002, 7:16 AM
Post #1 of 9
Ok, i've decided to post my post here, in the advance section, just because i really think this is a rare problem not easy to resolve:
perl problem or apache problem??
I'm moreless new in linux world, all i wanted to do was to install apache 2 in suse 8, and run the server.
The problem is this: i can see the html pages, but i cannot execute my perl scripts.
Stop thinking about typical mistakes, all i can get is the error 'premature end of scripts ...' but that's not all.
Two-three hours after i watch by casuality \r\n in a script and i though "that's it, my Content ... \n\n has to be Content ... \r\n\r\n" and it WORKED and everything was allright, all my scripts run perfectly!!!!
I went to sleep but today, oh today, today i have the same problem "premature end ...", the \r\n\r\n was only valid for one day! it begins to self-convert in a rare-case, doesn't it?
I catched my test.pl script (of course 755 - really 777)(of course working in console) and i began to prove things.
The surprise was to comprove that if i let the file empty, this is a blank file called test.pl, the same sentence was shown!! i though, maybe apache is not reading the file? yes yes, if you put localhost/test2.pl then apache says "i can't find this file", so, the only solution is a cache problem, but i really don't think this.
Any bug of apache?
Any mistake of mine in apache conf?
Am i doing any mistake???
Why yesterday everything worked well???????
I guess you wanted to view the complex test.pl i was proving, ok, here there is:
print "Content-type: text/html \r\n\r\n";
$| = 1;
And you can bet 100 euros perl is in /usr/bin/perl