Re: push fails with return code 22

2017-04-28 Thread Andrew Watson
You are the best Peff. It was indeed the hierarchy. So just had to change document root. Thanks a bunch. On Fri, Apr 28, 2017 at 11:34 AM, Jeff King <p...@peff.net> wrote: > On Fri, Apr 28, 2017 at 11:28:14AM -0400, Andrew Watson wrote: > >> $ GIT_CURL_VERBOS

Re: push fails with return code 22

2017-04-28 Thread Andrew Watson
t;17-54defc6469818" < Accept-Ranges: bytes < Content-Length: 23 < * Connection #0 to host git.site.domain.com left intact warning: You appear to have cloned an empty repository. Content length is again 0. On Fri, Apr 28, 2017 at 11:20 AM, Jeff King <p...@peff.net> wrote: > O

Re: push fails with return code 22

2017-04-28 Thread Andrew Watson
.conf just to be safe. I'm not sure what /info/refs is supposed to look like, but it is empty. Could that be the issue? Do you see anything in my apache configuration that looks wrong? Andrew On Thu, Apr 27, 2017 at 4:18 PM, Jeff King <p...@peff.net> wrote: > On Thu, Apr 27, 2017 at 02:37

push fails with return code 22

2017-04-27 Thread Andrew Watson
Hi, I'm trying to setup git with Smart HTTP so we can move off of SVN. I've used the blog post: https://git-scm.com/blog/2010/03/04/smart-http.html I'm getting "error: Cannot access URL ... return code 22" when I try to push. Clone works fine. I verified authentication by replacing my LDAP