[git-users] Re: Smart HTTP cannot push return code 22

2011-08-13 Thread Thomas Ferris Nicolaisen
I'm not sure if this helps, but here's a Git repository tool that supports 
Smart HTTP authentication out of the box:

http://gitblit.com/index.html

It's still a bit new and fresh, but the author has been very quick the 
couple of bugs I ran into. It's also small enough that you could fix some 
things by yourself (with some Java knowledge).

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/git-users/-/1qVFJuesDPcJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



[git-users] Re: Smart HTTP cannot push return code 22

2011-08-11 Thread Antony
On 11/08/2011 3:55 pm, evilpingus wrote:
 Hello,

 I been trying to switch to GIT from SVN, for couple days allready, but
 cannot overcome this annoying issue with push. I have been googling
 and trying some suggested ways but still no avail, and I am pretty
 desparate as I have been taking too much time with this issue
 allready, so any suggestions, comments would be very very wellcome.
 I succeed with ssh and git protocol, but in my case only option I can
 make it work is Smart HTTP.

 Git repos are located under /var/git/*.git as bare repositories
...
 -Apache
 logs-
 127.0.0.1 - - [11/Aug/2011:16:51:07 +0200] GET /foo.git/info/refs?
 service=git-receive-pack HTTP/1.1 401 727
 127.0.0.1 - test [11/Aug/2011:16:51:07 +0200] GET /foo.git/info/refs?
 service=git-receive-pack HTTP/1.1 200 1511
 127.0.0.1 - test [11/Aug/2011:16:51:07 +0200] GET /foo.git/HEAD HTTP/
 1.1 200 258
 127.0.0.1 - - [11/Aug/2011:16:51:09 +0200] PROPFIND /foo.git/ HTTP/
 1.1 401 727
 127.0.0.1 - test [11/Aug/2011:16:51:09 +0200] PROPFIND /foo.git/ HTTP/
 1.1 405 559
 -Apache logs
 end-

 I get asked for password twice, which is also strange.
 By googling around I found some suggestions that PROPFIND is WebDAV
 command, and this suggests that Git is falling back to old Dumb
 protocol.

Can you fetch, or are both fetch and pull failing?

It looks, to an eye that's never seen a smart HTTP transaction before,
that git's attempting to establish a smart http connection (the GET
requests with the service parameter), then not liking what it's got
back and attempting standard DAV.

Also, there are no requests to /git/, which is what your scriptalias
is set to, so the git-http-backend shouldn't be being called at any
rate.
Looking at the Examples section of man git-http-backend, it looks like
you should have set your remote url to http://localhost/git/foo.git,
not http://localhost/foo.git. Does that help?

Also check the apache error file, if it's separate.

Antony

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



[git-users] Re: Smart HTTP cannot push return code 22

2011-08-11 Thread Antony

 Can you fetch, or are both fetch and pull failing?

 It looks, to an eye that's never seen a smart HTTP transaction before,
 that git's attempting to establish a smart http connection (the GET
 requests with the service parameter), then not liking what it's got
 back and attempting standard DAV.

 Also, there are no requests to /git/, which is what your scriptalias
 is set to, so the git-http-backend shouldn't be being called at any
 rate.
 Looking at the Examples section of man git-http-backend, it looks like
 you should have set your remote url to http://localhost/git/foo.git,
 not http://localhost/foo.git. Does that help?

 Also check the apache error file, if it's separate.

 Antony


Also, if you want a quick response, try the main git mailing list
(g...@vger.kernel.org) or the IRC channel (irc.freenode.net #git).

Antony

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



[git-users] Re: Smart HTTP cannot push return code 22

2011-08-11 Thread evilpingus
Hello,

The case here is that I have to use Smart HTTP because we employ SSO
which works with apache, as our user management works this way. We
have a quite a crowd of developers and access to projects gets managed
within this frame. It seems also to me that speed penalty by using SSL
+ Smart HTTP against GIT or SSH protocol is minimal. Assigning user
name and password to developer is a much easier way to manage them, in
contrast to public key management. I imagine that different scenarios
would play rather better in another environments, but in this case
HTTP is preferred to us.

Sincerely


On Aug 11, 7:21 pm, Konstantin Khomoutov
flatw...@users.sourceforge.net wrote:
 On Thu, 11 Aug 2011 07:55:36 -0700 (PDT)

 evilpingus evilpin...@gmail.com wrote:
  I been trying to switch to GIT from SVN, for couple days allready, but
  cannot overcome this annoying issue with push. I have been googling
  and trying some suggested ways but still no avail, and I am pretty
  desparate as I have been taking too much time with this issue
  allready, so any suggestions, comments would be very very wellcome.
  I succeed with ssh and git protocol, but in my case only option I can
  make it work is Smart HTTP.

  Git repos are located under /var/git/*.git as bare repositories

 [...]
 An obligatory question someone should ask: is there really any
 compelling reason not to use SSH-based access native to Git?
 It seems you're hosting on a POSIX system anyway so there's no problem
 in setting up SSH-server, and user management for accessing the
 repositories could be implemented using a suitable tool such as gitolite
 or gitosis.
 Windows clients also have no problems with SSH access thanks to PuTTY.

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.