From: Jeff King <peff@peff.net>
To: Andrew Watson <andwatsresearch@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: push fails with return code 22
Date: Thu, 27 Apr 2017 16:18:04 -0400 [thread overview]
Message-ID: <20170427201804.3abt5ht6dkwwqo4r@sigill.intra.peff.net> (raw)
In-Reply-To: <CAH6sfJUn99ezs-uZuYVj15qOeMv79ji7r0Ldvoreef0z3LzG8Q@mail.gmail.com>
On Thu, Apr 27, 2017 at 02:37:19PM -0400, Andrew Watson wrote:
> 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 not sure how that post will have aged. You might check your setup
against the documentation in "git help http-backend", which is kept more
up to date.
> My system is CentOS 7 which reports git version 1.8.3.1 and Apache
> 2.4.6. I also tried on Ubuntu 16.04 with git 2.7.4 and Apache 2.4.18.
>
> Using GIT_CURL_VERBOSE I can see it fail after a PROPFIND.
That means the client isn't using smart-http. PROPFIND is part of the
"dumb" http push-over-webdav.
So the problem is likely in the very first request Git makes to
/info/refs/?service=git-receive-pack. The response there is what the
client uses to decide whether the server understands smart-http or not.
> My stackoverflow post with all the debug info I could think of is
> here: http://stackoverflow.com/questions/43643152/git-push-results-in-return-code-22
I notice the response for that first request has:
Content-Length: 0
Content-Type: text/plain; charset=UTF-8
which implies to me that the git-http-backend CGI isn't being run.
-Peff
next prev parent reply other threads:[~2017-04-27 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 18:37 push fails with return code 22 Andrew Watson
2017-04-27 20:18 ` Jeff King [this message]
2017-04-28 15:09 ` Andrew Watson
2017-04-28 15:20 ` Jeff King
2017-04-28 15:28 ` Andrew Watson
2017-04-28 15:34 ` Jeff King
2017-04-28 15:48 ` Andrew Watson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170427201804.3abt5ht6dkwwqo4r@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=andwatsresearch@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).