From: "François Dagorn" <Francois.Dagorn@univ-rennes1.fr>
To: git@vger.kernel.org
Subject: git-receive-pack missing credentials ?
Date: Mon, 07 Nov 2011 16:33:14 +0100 [thread overview]
Message-ID: <4EB7FA3A.8070908@univ-rennes1.fr> (raw)
Hello all,
I'm experiencing problems when trying to set up a git repository
managed by git-http-backend. I've done the following :
- on the server side
cd /git
mkdir test13
git --bare init .
>>> Initialized empty Git repository in /git/test13
/usr/local/libexec/git-core/git-update-server-info
chown -R apache.apache .
- on the client side
cd (project-directory)
$ git init
$ (add some files)
$ git add .
$ git commit -m 'Initial commit'
git push http://git.istic.smw.fr/test13 master
Username:
Password:
error: Cannot access URL http://git.istic.smw.fr/test13/, return code 22
fatal: git-http-push failed
- apache acces_log
1) ip-address - metheuser [07/Nov/2011:16:17:31 +0100]
"GET /test13/info/refs?service=git- receive-pack HTTP/1.1" 200 - "-" "git/1.7.3.4"
2) ip-address - metheuser [07/Nov/2011:16:17:32 +0100]
"GET /test13/HEAD HTTP/1.1" 200 23 "-" "git/1.7.3.4"
3) ip-address - - [07/Nov/2011:16:17:32 +0100]
"PROPFIND /test13/ HTTP/1.1" 401 492 "-" "git/1.7.3.4"
- what sounds strange to me : the 2 firsts requests are generated by my client side
(wireshark used as a clue) but the third comes from the server side and the users
credentials are missed !
- And also, I was hoping to use smart httpd and so the generated PROPFIND (DAV)
is amazing.
Any help would be appreciated.
Cheers.
François Dagorn
Université de rennes 1
France
next reply other threads:[~2011-11-07 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 15:33 François Dagorn [this message]
2011-11-07 17:02 ` git-receive-pack missing credentials ? Tay Ray Chuan
2011-11-08 8:26 ` François Dagorn
2011-11-08 10:17 ` François Dagorn
2011-11-08 10:50 ` François Dagorn
2011-11-16 17:19 ` Geoff Mets
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=4EB7FA3A.8070908@univ-rennes1.fr \
--to=francois.dagorn@univ-rennes1.fr \
--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.
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).