From: bugs@innuce.ch
To: Thomas Braun <thomas.braun@virtuell-zuhause.de>, git@vger.kernel.org
Cc: msysGit <msysgit@googlegroups.com>
Subject: Re: Possible Bug in git-http-push
Date: Sun, 12 Apr 2015 12:24:42 +0200 [thread overview]
Message-ID: <552A47EA.2060909@innuce.ch> (raw)
In-Reply-To: <55280064.5070909@virtuell-zuhause.de>
Am 10.04.2015 um 18:55 schrieb Thomas Braun:
> Am 10.04.2015 um 13:15 schrieb Stefan:
>> Hello List
>>
>> I possibly found a bug in git-http-push:
>>
>> When I push my local repo via http secured with basic authorization,
>> then i get:
>>
>> error: Cannot access URL https://example.ch/example_repo/, return code 22
>> fatal: git-http-push failed
>> Pushing to https://example.ch/example_repo/
>>
>> My server log gives PROPPFIND 401, so i seems that the PROPPFIND-sent
>> by git-http-push does not use supplied username/pw via prompt
>>
>> Pulling works without problems.
>>
>> When I change remote URL to
>> https://user:password@example.ch/example_repo, pushing works.
>>
>> I'm using git version 1.9.5.msysgit.1
> Hi Stefan (CC'ing the msysgit list as this might be windows specific),
>
> can you determine the last version which worked?
>
> And can you create a minimal working example for us to reproduce the
> problem?
>
> We already have a couple of problems with the new curl version together
> with our ancient openssl.
>
> Thomas
>
>
Hi Thomas
I stuck on this problem because i moved my git-server and did some
reconfiguring.
Here an working config
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
[remote "origin"]
url = https://user:passwort@git.example.ch/project
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
And here an non-working one:
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
hideDotFiles = dotGitOnly
[remote "origin"]
url = https://git.example.ch/project
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
Hope this helps
Greetz
Stefan
prev parent reply other threads:[~2015-04-12 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 11:15 Possible Bug in git-http-push Stefan
2015-04-10 16:55 ` Thomas Braun
2015-04-12 10:24 ` bugs [this message]
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=552A47EA.2060909@innuce.ch \
--to=bugs@innuce.ch \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
--cc=thomas.braun@virtuell-zuhause.de \
/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).