* Possible Bug in git-http-push
@ 2015-04-10 11:15 Stefan
2015-04-10 16:55 ` Thomas Braun
0 siblings, 1 reply; 3+ messages in thread
From: Stefan @ 2015-04-10 11:15 UTC (permalink / raw)
To: git
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
Thanks
Stefan
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Possible Bug in git-http-push
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
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Braun @ 2015-04-10 16:55 UTC (permalink / raw)
To: Stefan, git; +Cc: msysGit, bugs
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
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Possible Bug in git-http-push
2015-04-10 16:55 ` Thomas Braun
@ 2015-04-12 10:24 ` bugs
0 siblings, 0 replies; 3+ messages in thread
From: bugs @ 2015-04-12 10:24 UTC (permalink / raw)
To: Thomas Braun, git; +Cc: msysGit
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-04-12 10:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).