That was me on StackOverflow, providing the answer there too since I had
discovered one to share.
> On Feb 1, 2015, at 4:30 PM, Eric Covener wrote:
>
> On Sun, Feb 1, 2015 at 1:17 PM, James Cook wrote:
>> /Library/Server/Web/Data/CGI-Executables
>
>
> It seems like this was answered on stac
On Sun, Feb 1, 2015 at 1:17 PM, James Cook wrote:
> /Library/Server/Web/Data/CGI-Executables
It seems like this was answered on stackoverflow, where you found an
included configuration file with the paths involved.
--
Eric Covener
cove...@gmail.com
This one is a big shortcoming on Apple's part and OS X Server.
Under the heading of Work with Apache, OS X Server Documentation shows cgi as
served from /Library/WebServer/CGI-Executables/. And sure enough, there's a
CGI-Executables folder right where they said it should be.
In OS X Server's H
A thorough search of the server turns up just two files named precisely
httpd.conf. Their paths are
/private/etc/apache2
/private/etc/apache2/original
Both have the desired path in them /Library/WebServer/CGI-Executables
There are variations on the name, all with suffixes such as
On Sun, Feb 1, 2015 at 12:06 PM, James Cook wrote:
> What would cause Apache to ignore the httpd.conf assigned path and how can I
> correct it?
Most times it's the user looking at the wrong configuration file
(completely wrong httpd.conf, overridden Include, looking at unused
virtual host). Wha
I'm trying to resolve a path error on my cgi-bin.
What I've discovered is that Apache is looking for it in the wrong place.
The error log shows:
script not found or unable to stat:
/Library/Server/Web/Data/CGI-Executables
But my httpd.conf file has:
ScriptAliasMatch ^/cgi-bin/(
