Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 26 Mar 2019 20:15:42 -0400
From: Rich Felker <>
Subject: Re: Supporting git access via smart HTTPS protocol for

On Tue, Mar 26, 2019 at 07:58:35PM -0400, Rich Felker wrote:
> 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 (
> > ).
> > 
> > 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.

Anyway, for now this is vaguely working, but it's a hack and it's
experimental and might break. Users interested in testing can clone:

It might go up and down while I'm hacking on getting it right, but I
intend for the URL to be permanent in the long term.


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.