Not a perl question, but....
Well, there was this same question a few days ago, you could try looking around, but anyway, before you can get an answer about why your http server don't run cgi scripts we should need to know,
- Which server are you running.
- Which error are you getting ?
- What have you configured so far
Get that info back and then we can help you.
Dreams they just disapear into the shadows,
then they become true....
| [reply] |
The question was mine yesterday. I tried the suggestions but am back for more help. I am running the Apache Http sever under windows.xp. So far I have just tried a simple "Hello World" script.
#!/usr/bin/perl
print "Content-type:text/html";
print "<html><head><title>Test Page</title></head>";
print "<body>\n";
print "Hello, world!\n";
print "</body></html>\n";
it is a .pl file in my cgi-bin directory. When I load this page through a web browser, it diplays the shebang line and the print commands and the \n's
I have change the options, the addhandler and the scriptalias
| [reply] |
You probably want to put a <code> </code> around your code in the first instance ;-}
Also you will need to read in the Apache Documentation with reference to the ExecCGI option. It is also important with Apache that you have the shebang line correct ... If you are still having difficulties you will probably want to find Some Apache specific forum to ask the question
/J\
| [reply] |
The Apache web site offers some specific Windows help at:
http://httpd.apache.org/docs/windows.html
When running CGI scripts, the method Apache uses to find the interpreter for the script is configurable using the ScriptInterpreterSource directive. Quoting from that source:
"Syntax: ScriptInterpreterSource registry|script
Default: ScriptInterpreterSource script
Context: directory, .htaccess
Status: core (Windows only)
This directive is used to control how Apache 1.3.5 and later finds the interpreter used to run CGI scripts. The DEFAULT technique is to use the interpreter pointed to by the #! line in the script. HOWEVER, setting ScriptInterpreterSource registry will cause the Windows Registry to be searched using the script file extension (e.g., .pl) as a search key."
That Apache Windows site also notes that if you still have a question or problem, post it to the comp.infosystems.www.servers.ms-windows newsgroup, where many Apache users and several contributions are more than willing to answer new and obscure questions about using Apache on Windows.
| [reply] |
