From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14035 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Assaf Gordon Newsgroups: gmane.linux.lib.musl.general Subject: Re: Supporting git access via smart HTTPS protocol for musl-libc Date: Wed, 27 Mar 2019 11:41:39 -0600 Message-ID: <22456013-02e6-4a45-7b0b-585afbaf46f2@gmail.com> References: <20190326151344.GB23599@brightrain.aerifal.cx> <20190326154304.GB2267@homura.localdomain> <20190326154700.GC23599@brightrain.aerifal.cx> <20190326155743.GC2267@homura.localdomain> <20190326175700.GD23599@brightrain.aerifal.cx> <20190326220225.GE23599@brightrain.aerifal.cx> <20190326235835.GF23599@brightrain.aerifal.cx> <20190327001542.GG23599@brightrain.aerifal.cx> <20190327053933.GA2518@localhost> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="218193"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 Cc: dalias@libc.org To: musl@lists.openwall.com, vlse Original-X-From: musl-return-14051-gllmg-musl=m.gmane.org@lists.openwall.com Wed Mar 27 18:41:56 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1h9CYm-000ugU-3W for gllmg-musl@m.gmane.org; Wed, 27 Mar 2019 18:41:56 +0100 Original-Received: (qmail 3379 invoked by uid 550); 27 Mar 2019 17:41:54 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 3361 invoked from network); 27 Mar 2019 17:41:53 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=KsthY7aM37+IExWPHTSbftQ2Kwa5LXOPGIQ0uaJOGtg=; b=kTQy5zAQvIxb4umNYgEFAxBgMKMLRg8xEzRgfdqHSE3JGqELWW86gQc+R1D71YhXKA /Zq6cWvjQpYLMhM/cL9Gn1+oom+nc4mPVYvTK6HWI78QPIWgyK6VIw6cQGWcEs3ydo0R cr4xBrgEp2CoqdM1g6RVMRDezyxVpZyhfH2OkGjkLO53m7sa3OgQkVe066NwtU4miEgr 42S+zrpFbZ91H1bFQDswx4tuyaWv1dapMe6+0iVRhOgz5rwJayz9ZTr+kjLQZYog3OGc mBppFntMOJztxxxt72LxN1ZrZDSvvoAfrzx5u9p0OmeXAaBFVRcTn3URCue2WBReE0nR ZmIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=KsthY7aM37+IExWPHTSbftQ2Kwa5LXOPGIQ0uaJOGtg=; b=X375f61M1tk67jVNk13L334MiNbO53SW/9I0dsQYzRpYoc5kuiFO8bZe2MUFo4RqwR q6e+zgqqqLIkfT4kPeerveMUHrkIjSY/ghjfKsBmvgBjvVyP2b64MgZr4WWjtjOJ7PrT IrB1q3I0zAkDLie1MYhebtI+RlF+/jCaIxDa20SfMhC/QxnlTFQVT6MKNBdsnXz8tsHY K9dAk+rMhF3GBRRj6ahKzgAE3bbk9WNZdQHD/4QcHELOHpertC2s7sXDslBrDrFbNTSQ FLar777dp2nvVuIqpv4dgBVlGU3oyJTsVJGRW0bO37HtS0gECAtDNPjx8XGZ4XHohrnC 7Vog== X-Gm-Message-State: APjAAAViJ2EnkGKMEuJEHC7J3K9d04RreOd6irVVfuTXGcPB8/cFFEwn zj2XRqkbYltsliwhBoOEQ7o= X-Google-Smtp-Source: APXvYqz4ZWwhIKpcPng5rMkIDp5BrOTtjw37ljdhYASP/OZSQ/gx8Qc0x2fm+taniU8yYcQ3/R3lTQ== X-Received: by 2002:a63:fd06:: with SMTP id d6mr13485835pgh.183.1553708501359; Wed, 27 Mar 2019 10:41:41 -0700 (PDT) In-Reply-To: Content-Language: en-US Xref: news.gmane.org gmane.linux.lib.musl.general:14035 Archived-At: More details: >>>>>> [...] I suspect thttpd is doing something broken with >>>>>> the POST request since the git clone breaks during that. >>>>> >>>>> The same happened to me with busybox, and was solved by forcing: >>>>> >>>>>      export HTTP_CONTENT_ENCODING=gzip >>>>> >>>> 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. [...] > Digging further, it seems that in this case the "git fetch" > command sent POST data which is *not* compressed. > Forcing "CONTENT_ENCODING=gzip" always or for all POST request > is not sufficient. The git program (at least version 2.11.0) does send the CONTENT_ENCODING header if the POST data is gzipped. In the case of "busybox httpd" webserver, it simply does not pass this header on to the CGI program - hence all these problems: https://git.busybox.net/busybox/tree/networking/httpd.c#n1443 Possibly thttpd behaves the same (while nginx/apache do pass all headers, and there's no problem with them). regards, - assaf