Hi Sanju,
Welcome to AOLserver.
the item after the GET or POST should be what the cgi script names
should look like, and the item after that is where they should live.
I just tried the following and it worked. My cgi's all end with .cgi,
and I want them to work from the pageroot down:
ns_param map "GET /*.cgi /"
ns_param map "POST /*.cgi /"
Let me know if you're still having trouble.
/s.
-----Original Message-----
From: AOLserver Discussion [mailto:[EMAIL PROTECTED]] On Behalf
Of Sanjivendra Nath
Sent: Sunday, August 19, 2001 10:09 AM
To: [EMAIL PROTECTED]
Subject: [AOLSERVER] correction! sorry RE: [AOLSERVER] "ns_parm cgi
/usr/local/aolserver/server/server1/pages" invalid? workaround?
My mapping is:
ns_param map "GET / /usr/local/aolserver/server/server1/pages"
ns_param map "POST / /usr/local/aolserver/server/server1/pages"
-----Original Message-----
From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf
Of Sanjivendra Nath
Sent: Sunday, August 19, 2001 9:09 AM
To: [EMAIL PROTECTED]
Subject: [AOLSERVER] "ns_parm cgi
/usr/local/aolserver/server/server1/pages" invalid? workaround?
I have a cgi app. under apache that works perfectly.
However, all the cgi calls are of the following form:
http://www.foo.com/foo1.cgi?name1=arg1
Each subsequent page is generated with embedded hyperlinks of this form.
It is possible to convert it all to the form:
(http://www.foo.com/cgi-bin/foo1.cgi?name1=arg1 - however, doing so
could be painful and would probably require getting my awk/sed or perl
book out.)
So, I tried to map config.tcl with the entry:
ns_parm cgi /usr/local/aolserver/server/server1/pages (I realize that
the documentation somewhere says not to do this, but is there another
workaround?)
This seems to work, except the gif/jpg files don't show up.
The server log says: "execv() error....". Is the nscgi module getting
confused?
Of course, for fun, I put in the following mapping:
ns_section "ns/server/${servername}/adp"
ns_parm map "/*.gif"
ns_parm map "/*.jpg"
The execv error goes away, the access.log says status code is 200 (ie.
page was served OK), but the link is still broken.
This is my first foray into AOLserver, as you can tell. I'm probably
violating some fundamentals, but my app. works in apache when I
configure it to use cgi at the / level. Can I do this with AOLServer
without too much pain?
Thanks,
Sanju.