Re: PROPFIND 405 with git-http-backend and Smart HTTP
- From
- Drew Northup <n1xim.email@gmail.com>
- Date
- Aug 5, 2012, 18:30 UTC
- Message-ID
- <CAM9Z-nnfwuR9UKtoQ1uACOMH3vhZKFxDkjEn5_azpGxd2GGjJQ@mail.gmail.com>
- In-Reply-To
- <1343684368384-7564144.post@n2.nabble.com>
On Mon, Jul 30, 2012 at 5:39 PM, Bo98 <BoEllisAnderson@aol.com> wrote:
Show 13 quoted lines
> > Shawn Pearce wrote >> Maybe you forgot to enable ExecCGI? >> > Whoops, completely forgot about that, but, assuming I did it right, it still > doesn't seem to work. > > Here's what I did: > > <Directory "/usr/libexec/git-core/"> > Options +ExecCGI > Allow From All > </Directory>
Are all directory permissions set right? Is SELINUX enabled, and if so are all of the contexts set correctly? Does your Apache configuration recognize things NOT spelled *.cgi as CGI scripts / programs?
Besides, once you start asking Apache to do things outside of the base Document Root all sorts of interesting possibilities for failure become available.
I am pretty sure that this isn't a Git problem, it is a CGI hosting / configuration problem. An Apache-centric list may be able to help you better and is likely a better place to ask.
-- -Drew Northup -------------------------------------------------------------- "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59