We have a cgi app that was built with an older version of RS - 2011r1 or so. It was compiled as a Intel Mac executable, and has been running for several years without problem on a Mac OS X 10.6.8 Server. (It’s a process that gets called by Kagi to dynamically generate and return a license key and also shove it into our database when an order is placed.)
I’m now trying to set it up an a newly-installed Yosemite (not server) machine. We’ve got Apache running on this machine, and are able to serve a web page to the outside world. We’ve modified the httpd.conf file by uncommenting the line “LoadModule cgi_module libexec/apache2/mod_cgi.so”.
The first thing this cgi app does when it’s launched is to create a log file (if necessary), and write to it. If I execute it from a command line, it does this as it should. However, when I call its url (e.g., http://myhost.mydomain.com/cgi-bin/My_App.cgi) from an outside machine or even from the machine itself, Apache doesn’t seem to trigger the app to run.
I’m guessing that this may be due to the newer version of Apache that ships with Yosemite, and that I might have to make some additional changes to httpd.conf, but would appreciate any suggestions.
Since nobody is replying, I guess I’ll keep doing so myself…
In looking through the apache log file, it appears that Apache is trying to run the .cgi as a php script. How do I tell it to just execute it rather than trying to interpret it?
I wasn’t suggesting anyone was ignoring me - just always find it amusing when I’m repeatedly posting about my flailing around…
Thanks for the suggestion. I’m pretty sure we’ve got the firewall set up correctly. I’m thinking this is the case as I am able to run a python script (.py) that I made excutable and placed in the same directory.
I made the app readable, writable, and executable by everybody (just as one of my flails). I’ve also made apache run under the standard “_www” account and group, as well as by the user/group of the administrative account that currently owns the app and lib folder. I even tried code signing them both just in case Yosemite requires that - still no joy
to the directives for the CGI-Executables directory. This wasn’t the case in the older version of Apache running on our 10.6.8 machine, as afar as I can tell.