[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190326235835.GF23599@brightrain.aerifal.cx>
Date: Tue, 26 Mar 2019 19:58:35 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Supporting git access via smart HTTPS protocol for
musl-libc
On Tue, Mar 26, 2019 at 04:32:32PM -0600, Assaf Gordon wrote:
> >
> > Thanks for the info. I've been playing with it, but haven't been able
> > to get it to work yet. I suspect thttpd is doing something broken with
> > the POST request since the git clone breaks during that. Going to look
> > at it in more detail later.
>
> The same happened to me with busybox, and was solved by forcing:
>
> export HTTP_CONTENT_ENCODING=gzip
>
> Seems to me (from a cursory look) that "git clone" client always sends
> gzipped (inflate) data, but either doesn't set the HTTP encoding header,
> or the header gets lost somehow.
>
> The git-http-backend uses that header to decide whether to deflate
> the stream or not (
> https://github.com/git/git/blob/master/http-backend.c#L460 ).
>
> That's the first thing I'd try if the GET request worked but the
> following "POST git-update-pack"
> does not.
Amazingly, this works, but only if I do it only for
REQUEST_METHOD=POST. Otherwise it breaks the GET request and it never
makes it to the POST. *sigh* There's got to be some better way to fix
this.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
