On Sat, Sep 28, 2002 at 05:49:52AM +0800, Ihsan Junaidi Ibrahim wrote:
I finally found the cause of the problem. PHP 4.2.3. I commented
the LoadModule and AddModule clauses in httpd.conf and bam!, all
CGIs and Perls work as healthy as they can be. Solved a problem
only to bring
Hello all,
Saturday, September 28, 2002, 5:49:52 AM, freebsd-questions wrote:
Hello all,
I finally found the cause of the problem. PHP 4.2.3. I commented the
LoadModule and AddModule clauses in httpd.conf and bam!, all CGIs and Perls
work as healthy as they can be.
, September 26, 2002 07:49 AM
Subject: Re: Apache CGI problem
Hello all,
Personally, the only time I've ever seen error 500 is when either the
script had syntax errors, the permissions were set incorrectly, or the
script was transferred as a binary file when it should've been
transferred
On Thu, Sep 26, 2002 at 03:15:00AM +0800, Ihsan Junaidi Ibrahim wrote:
Weird problem I'm having here. I can't execute any script in
ScriptAlias directory. 500 Internal Server Error always came
out. I'm pretty sure the scripts are all right. I ran them on
shell, they executed
Hello all,
Unix wrote:
Is your apache server doing virtual hosting
Could you provide me your httpd.conf file
OK, here's the file plus the offending virtual hosts. These are the two hosts
that use the cgi-bin. Yes I use virtual hosting. I do a local lan-based sites
using local name
On Fri, 27 Sep 2002, Ihsan Junaidi Ibrahim wrote:
Hello all,
Error 500 : Internal server error.
Internal Server Error usually means your script has crashed, or it hasn't
produced a complete output. What does apache's error-log say?
Fer
--
Thank you for your
Hello all,
Thursday, September 26, 2002, 9:02:45 AM, freebsd-questions wrote:
I think the problem may be with your scripts. Make sure the scripts
are sending the correct HTTP headers to Apache before trying to print
any output. For example:
#!/usr/bin/perl
print Content-type:
Hello all,
Personally, the only time I've ever seen error 500 is when either the
script had syntax errors, the permissions were set incorrectly, or the
script was transferred as a binary file when it should've been
transferred as ASCII. If you're sure that all three of those issues
don't