From: Drew Northup <n1xim.email@gmail.com>
To: Bo98 <BoEllisAnderson@aol.com>
Cc: git@vger.kernel.org, Shawn Pearce <spearce@spearce.org>
Subject: Re: PROPFIND 405 with git-http-backend and Smart HTTP
Date: Sun, 5 Aug 2012 14:30:51 -0400 [thread overview]
Message-ID: <CAM9Z-nnfwuR9UKtoQ1uACOMH3vhZKFxDkjEn5_azpGxd2GGjJQ@mail.gmail.com> (raw)
In-Reply-To: <1343684368384-7564144.post@n2.nabble.com>
On Mon, Jul 30, 2012 at 5:39 PM, Bo98 <BoEllisAnderson@aol.com> wrote:
>
> 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
next prev parent reply other threads:[~2012-08-05 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-29 18:52 PROPFIND 405 with git-http-backend and Smart HTTP Bo98
2012-07-30 1:00 ` Shawn Pearce
2012-07-30 8:40 ` Bo98
2012-07-30 16:37 ` Shawn Pearce
2012-07-30 20:30 ` Bo98
2012-07-30 20:42 ` Shawn Pearce
2012-07-30 21:39 ` Bo98
2012-08-05 18:30 ` Drew Northup [this message]
2014-08-14 10:23 ` lpicquet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM9Z-nnfwuR9UKtoQ1uACOMH3vhZKFxDkjEn5_azpGxd2GGjJQ@mail.gmail.com \
--to=n1xim.email@gmail.com \
--cc=BoEllisAnderson@aol.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).