Kai Schaetzl wrote:
Tech wrote on Mon, 29 Sep 2008 13:01:26 +0800:
Oh, it does print Hello World OK but it also prints the Content line
as text rather than using it as a directive.
This is not a setup problem and not a CentOS problem. Your script is
probably wrong in some code. I assume
On Sep 29, 2008, at 10:11 AM, tech wrote:
Thanks for your reply.
By Content line I meant this line:
print Content-type: text/html\n\n;
I have tried many scripts, they all do this. I have problems with
JavaScript too so I am not sure yet about this just being a Perl or
CGI problem. I
tech wrote:
Kai Schaetzl wrote:
Tech wrote on Mon, 29 Sep 2008 13:01:26 +0800:
Oh, it does print Hello World OK but it also prints the Content
line as text rather than using it as a directive.
This is not a setup problem and not a CentOS problem. Your script is
probably wrong in some code.
Steve Huff wrote:
it would be easier to troubleshoot this problem if you were to post links to
the following:
* your Perl script
* the Apache access and error logs showing what happens when you try to
hit the CGI from a browser
* the relevant Apache configs (vhost, .htaccess, whatever)
tech wrote:
p!--#exec cmd=perl ./cgi-bin/hello.cgi--/p
Do you have server side includes turned on in apache? (in
the Directory section typically)
Are your includes configured with the NoExec option?
nate
___
CentOS mailing list
CentOS@centos.org
On Sep 29, 2008, at 11:32 AM, tech wrote:
Steve Huff wrote:
it would be easier to troubleshoot this problem if you were to
post links to the following:
* your Perl script
* the Apache access and error logs showing what happens when you
try to hit the CGI from a browser
* the relevant
On Mon, Sep 29, 2008 at 12:11:32PM -0400, Tony Schreiner wrote:
On Sep 29, 2008, at 11:32 AM, tech wrote:
html
HEADTITLETech/TITLE
META http-equiv=Content-Type content=text/html; charset=iso-8859-1
/head
body
p!--#exec cmd=perl ./cgi-bin/hello.cgi--/p
/body
/html
Here is the hello.cgi
nate wrote:
Do you have server side includes turned on in apache? (in
the Directory section typically)
Are your includes configured with the NoExec option?
Hi Nate,
Don't think so. I have +Includes and ExecCGI in directory options.
NoExec does not appear anywhere in HTTP.conf or in
tech wrote:
Don't think so. I have +Includes and ExecCGI in directory options.
NoExec does not appear anywhere in HTTP.conf or in perl.conf
Have you tried variations on the path? e.g if your executing
a shell I don't think ./cgi-bin/ would be a valid path, it would
be relative to the file
Stephen Harris wrote:
Right. The O/P is confusing his weasels. He's writing a CGI script
but using an _include_ script. Two totally different things.
Stephen,
Thank you.
I appreciate your time and patience. I now know what to go find to fix this.
I was trying to do this the same way I
nate wrote:
Have you tried variations on the path? e.g if your executing
a shell I don't think ./cgi-bin/ would be a valid path, it would
be relative to the file system itself.
Example from my personal web site:
!--#include virtual=/cgi-bin/multimon-new.cgi --
Nate,
The ./cgi-bin/ is
tech wrote:
The ./cgi-bin/ is under public_html. It is set in http.conf as a CGI
directory. The files are found OK. But, as mentioned, I have been
confusing the proverbial apples and oranges. I will put my CGI tutorial
books away and learn how to call CGI and JavaScripts from HTML to right
nate wrote:
Try calling the cgi directly like my example instead of
executing perl in a shell.
Will do.
Mel
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
13 matches
Mail list logo
