From: Jeff King <peff@peff.net>
To: Davide Baldini <baldiniebaldini@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Fail to push over HTTP with MySQL authentication (Apache2)
Date: Sat, 29 Dec 2012 16:01:28 -0500 [thread overview]
Message-ID: <20121229210128.GB21058@sigill.intra.peff.net> (raw)
In-Reply-To: <50DF4A78.5000206@gmail.com>
On Sat, Dec 29, 2012 at 08:54:32PM +0100, Davide Baldini wrote:
> SETUP:
> -----
> [...]
> Git repository has been configured as:
> cd /var/www/public/GT_rulesets/GT00.git
> git init --bare
> mv hooks/post-update.sample hooks/post-update
> git update server-info
> chmode 777 /var/www/public/GT_rulesets/GT00.git # for testing.
Should this last line be a "chmod -R"? Git init will create many
subdirectories, and you want to make sure they are all writable for
push.
> _ Git:
> Git can fetch the repository without problems:
> git clone http://username:password@greatturn.org:8081/GT00.git
>
> Pushing the locally fetched repository back to the remote one doesn't
> work:
> [...]
> > 87.19.240.177 - - [29/Dec/2012:16:43:26 +0100] "PROPFIND /GT00.git/ HTTP/1.1" 401 767 "-" "git/1.7.8.3"
If fetch is working and push is not, I'd suspect WebDAV configuration
problems (and indeed, your credentials seem fine, but the PROPFIND is
returning a 401). Fetch works over stock HTTP and does not use WebDAV at
all. There is some documentation on setting up DAV here:
https://github.com/git/git/blob/master/Documentation/howto/setup-git-server-over-http.txt
but I have no idea if it is up-to-date or not.
However, before trying to investigate that avenue, have you considered
using git's smart-http backend instead of WebDAV? It's significantly
more efficient. You can get details and example apache configuration
from "git help http-backend".
-Peff
next prev parent reply other threads:[~2012-12-29 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 19:54 Fail to push over HTTP with MySQL authentication (Apache2) Davide Baldini
2012-12-29 21:01 ` Jeff King [this message]
2012-12-30 0:27 ` Davide Baldini
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121229210128.GB21058@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=baldiniebaldini@gmail.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).