On Thu, Apr 18, 2013 at 09:54:32PM +0200, Matthieu Moy wrote:
> Sebastian Schmidt <[email protected]> writes:
>
> > Why is git not working over HTTPS with basic authentication? I can clone
> > just fine, but when I try to push, it tells me
>
> What are you using on the server? Dumb HTTP works by serving the
> repository files as static pages, which is fundamentally read-only. The
> recommended way is to use smart-HTTP (see man git-http-backend, requires
> Git on the server), and the alternative is to use webdav (much slower).
Yeah, this is definitely dumb http (since http-push is involved at all,
which the original error message showed). Code 22 is curl's "there was
an HTTP error" code, but http-push annoyingly does not output the actual
HTTP error[1]. You can see more by setting GIT_CURL_VERBOSE=1 in the
environment.
Though if you know you did not set up WebDAV on the server, then we can
know that is the problem even without seeing the HTTP code. :)
-Peff
[1] The dumb-http push code is largely unloved and unmaintained at this
point. Yet another reason to move to smart http.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
