func_exec reports: HTTP2122: cannot find function named force_type (CGI)
Hello,
I just configured my first instance of WS7 (after many years of using WS6.1, WS6.0, WS4, etc.) and have a most peculiar problem.
I configured a mapping for a CGI directory (pretty basic, uri=/cgi-bin and path is a directory on my server owned by the same user as the instance runs as). When I try to run anything within that directory (e.g., http://myserver/cgi-bin/tester.sh) I see the following error in the errors file:
[02/Feb/2007:10:23:14] config ( 5903):for host 192.168.1.100 trying to GET
/cgi-bin/tester.sh, func_exec reports: HTTP2122: cannot find function named force_type
The tester.sh file is trivial:
74# (cd ~/www/cgi-bin;ls -l tester.sh;cat tester.sh)
-rwxr-xr-x1 wwwwww78 Feb 2 10:30 tester.sh
#!/bin/sh
echo"Content-type: text/plain"
echo
echo"This is a test."
exit 0
I've searched through all of the WS7 docs, and I cannot find any reference to "force_type".
Any ideas what I've done wrong?
Thanks,
Bill
[1121 byte] By [
wgkorba] at [2007-11-26 17:07:43]

# 1
FYI, I've discovered that this appears to be a known bug:
Bug ID: 6500715
Synopsis: Incorrect ObjectType fn="force_type" added in object cgi on creation of new cgi directory
Product:
Category: iplanet_web_server
Subcategory: admin_server
State: 10-Fix Delivered
Sub State:
Priority:
Responsible Manager:
Responsible Engineer:
Release:
Integrated in Build: 7.0u1
My only question is, when will 7.0u1 be available? Is there a patch I can get now that will fix this? Not being able to use all of my old CGIs is a huge show-stopper.
Thanks,
Bill
# 2
while you wait for 7.0u1 to be released, you could follow the work around mentioned in the bug - you will need to manually change the line 'force_type' to 'force-type' in the obj.conf or <vs>-obj.conf under https-config
at the end of this step, you will need to run the cli command (pull-config) to bring over this manual change to the admin config repository - http://docs.sun.com/app/docs/doc/819-3283/6n5h03huv?a=view
It is very unfortunate that this issue could not be addressed in 7.0 time frame itself
# 3
Thank you very much for your reply - a work-around is exactly what I was hoping for (well, after a patch, anyway!).
However, that work-around is not mentioned in the bug report as I found it on SunSolve. Perhaps you're looking at an internal version that we don't have access to?
Thanks again,
Bill