From: vlse <vlse@veera.biz>
To: musl@lists.openwall.com
Cc: dalias@libc.org
Subject: Re: Supporting git access via smart HTTPS protocol for musl-libc
Date: Wed, 27 Mar 2019 11:09:35 +0530 [thread overview]
Message-ID: <20190327053933.GA2518@localhost> (raw)
In-Reply-To: <20190327001542.GG23599@brightrain.aerifal.cx>
On Tue, Mar 26, 2019 at 08:15:42PM -0400, Rich Felker wrote:
> 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 (
> > > 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.
>
> 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:
>
> https://git.musl-libc.org/git/musl
>
> 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.
>
> Rich
Hi,
I am using git-2.0.2 version.
Following works:
git clone https://git.musl-libc.org/git/musl
cd musl
git pull
git fetch
git fsck --full
shows no error
This does not works:
mkdir musl.git
cd musl.git
git init
git remote add -t master -m master origin https://git.musl-libc.org/git/musl
git fetch
git-fetch gives errors:
fatal: protocol error: bad line length character: erro
Running 'GIT_TRACE=2 git fetch' outputs:
trace: built-in: git 'fetch'
trace: run_command: 'git-remote-https' 'origin' 'https://git.musl-libc.org/git/musl'
trace: run_command: 'rev-list' '--objects' '--stdin' '--not' '--all' '--quiet'
trace: run_command: 'fetch-pack' '--stateless-rpc' '--stdin' '--lock-pack' '--include-tag' '--thin' 'https://git.musl-libc.org/git/musl/'
trace: exec: 'git' 'fetch-pack' '--stateless-rpc' '--stdin' '--lock-pack' '--include-tag' '--thin' 'https://git.musl-libc.org/git/musl/'
trace: built-in: git 'fetch-pack' '--stateless-rpc' '--stdin' '--lock-pack' '--include-tag' '--thin' 'https://git.musl-libc.org/git/musl/'
fatal: protocol error: bad line length character: erro
fatal: The remote end hung up unexpectedly
Regards,
Veera
next prev parent reply other threads:[~2019-03-27 5:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190324103306.GB1830@localhost>
[not found] ` <20190326003411.GC1872@localhost>
2019-03-26 1:09 ` vlse
2019-03-26 1:17 ` A. Wilcox
2019-03-26 1:37 ` Rich Felker
2019-03-26 1:54 ` vlse
2019-03-26 2:59 ` Rich Felker
2019-03-26 10:02 ` vlse
2019-03-26 10:36 ` Laurent Bercot
2019-03-26 15:04 ` Rich Felker
2019-03-26 15:09 ` Drew DeVault
2019-03-26 15:13 ` Rich Felker
2019-03-26 15:43 ` Drew DeVault
2019-03-26 15:47 ` Rich Felker
2019-03-26 15:57 ` Drew DeVault
2019-03-26 17:57 ` Rich Felker
2019-03-26 20:32 ` A. Wilcox
2019-03-26 20:39 ` Assaf Gordon
2019-03-26 22:02 ` Rich Felker
2019-03-26 22:32 ` Assaf Gordon
2019-03-26 23:58 ` Rich Felker
2019-03-27 0:15 ` Rich Felker
2019-03-27 5:39 ` vlse [this message]
2019-03-27 17:26 ` Assaf Gordon
2019-03-27 17:41 ` Assaf Gordon
2019-04-03 6:42 ` vlse
2019-03-26 10:19 ` Jens Gustedt
2019-03-26 10:30 ` vlse
2019-03-26 14:59 ` Rich Felker
2019-03-26 1:43 ` vlse
2019-03-26 2:29 ` A. Wilcox
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190327053933.GA2518@localhost \
--to=vlse@veera.biz \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).