From: Paul Vincent Craven <paul@cravenfamily.com>
To: git@vger.kernel.org
Subject: git over http not re-authenticating after 301 redirect?
Date: Mon, 6 Apr 2009 21:14:42 -0500 [thread overview]
Message-ID: <5591393c0904061914y5ea26812kcfc0d14b52ed4300@mail.gmail.com> (raw)
When I do a git-push from a repository I set up, I get:
craven@craven-desktop:~/docs$ git push
Unable to create branch path
http://username:password@server.simpson.edu/my_repo.git/info
Error: cannot lock existing info/refs
error: failed to push some refs to
'http://username:password@server.simpson.edu/my_repo.git/'
The web log shows:
10.1.21.232 - username [06/Apr/2009:21:24:04 -0500] "PROPFIND
/my_repo.git/ HTTP/1.1" 207 559 "-" "git/1.5.6.3"
10.1.21.232 - username [06/Apr/2009:21:24:04 -0500] "HEAD
/my_repo.git/info/refs HTTP/1.1" 200 - "-" "git/1.5.6.3"
10.1.21.232 - username [06/Apr/2009:21:24:04 -0500] "HEAD
/my_repo.git/objects/info/packs HTTP/1.1" 200 - "-" "git/1.5.6.3"
10.1.21.232 - username [06/Apr/2009:21:24:04 -0500] "MKCOL
/my_repo.git/info HTTP/1.1" 301 383 "-" "git/1.5.6.3"
10.1.21.232 - - [06/Apr/2009:21:24:04 -0500] "MKCOL /my_repo.git/info/
HTTP/1.1" 401 536 "-" "git/1.5.6.3"
Note that after the 301 redirect, I don't seem to have a username sent
anymore. I'm not sure this is the issue, but is seems like a
possibility.
I have the same issue on other computers that have cloned the repository.
The /my_repo.git/info/ directory does exist.
I thought I had this working the first day I set it up, but now it no
longer does. If someone could point me in the correct direction, I'd
appreciate it.
--
Paul Vincent Craven
next reply other threads:[~2009-04-07 2:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 2:14 Paul Vincent Craven [this message]
2009-04-07 7:42 ` git over http not re-authenticating after 301 redirect? Martin Storsjö
2009-04-07 19:25 ` Paul Vincent Craven
2009-04-09 17:20 ` Tay Ray Chuan
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=5591393c0904061914y5ea26812kcfc0d14b52ed4300@mail.gmail.com \
--to=paul@cravenfamily.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.
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).