cgi-bin access after OSX update

Hi all...


We have an application that we are planing to distribute with a Mac Mini (eg., the application and Mac Mini would be preset for the user - this is an embeded situation).


The software has a cgi-bin web component that allows the user to control the application.


The problem is this... when the user does an OSX upgrade, the Apache /etc/apache2/http.conf file gets overwritten.


On our initial setup, we uncomment the cgi-bin line to allow cgi-bin access. The update recomments that line.


(The update does backup the original configuration file, but that isn't much help.)


It may be possible for our daemon applation (that the web cgi-bin talks to) can detect and repair the configuration file - but that will still fail if the daemon is not running (since the user can no longer load the cgi to start the daemon).


I've reached out to Apple to ask them to change this behavior (normal installs of Apache will recognize that the httpd.conf file has changed and will not update it) - but Apple has responded that they do not intend to change that behavior.


Does anyone have a solution that can address this?


Thanks

Accepted Reply

Ok... I actually found a solution (after almost a year of searching).


Create your own configuration file (whatever.conf) and put it here:


/etc/apache2/other


The default configuration file loads everything in that directory at the end of the script.


YIPPIE!!!

Replies

Ok... I actually found a solution (after almost a year of searching).


Create your own configuration file (whatever.conf) and put it here:


/etc/apache2/other


The default configuration file loads everything in that directory at the end of the script.


YIPPIE!!!

Safari