From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14024 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Supporting git access via smart HTTPS protocol for musl-libc Date: Tue, 26 Mar 2019 13:57:00 -0400 Message-ID: <20190326175700.GD23599@brightrain.aerifal.cx> References: <20190326013706.GV23599@brightrain.aerifal.cx> <20190326015434.GB8855@localhost> <20190326025937.GW23599@brightrain.aerifal.cx> <20190326100245.GA1900@localhost> <20190326150430.GY23599@brightrain.aerifal.cx> <20190326150901.GA2267@homura.localdomain> <20190326151344.GB23599@brightrain.aerifal.cx> <20190326154304.GB2267@homura.localdomain> <20190326154700.GC23599@brightrain.aerifal.cx> <20190326155743.GC2267@homura.localdomain> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="85159"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-14040-gllmg-musl=m.gmane.org@lists.openwall.com Tue Mar 26 18:57:14 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 1h8qK2-000M1f-F9 for gllmg-musl@m.gmane.org; Tue, 26 Mar 2019 18:57:14 +0100 Original-Received: (qmail 9354 invoked by uid 550); 26 Mar 2019 17:57:12 -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 9336 invoked from network); 26 Mar 2019 17:57:12 -0000 Content-Disposition: inline In-Reply-To: <20190326155743.GC2267@homura.localdomain> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:14024 Archived-At: On Tue, Mar 26, 2019 at 11:57:43AM -0400, Drew DeVault wrote: > On 2019-03-26 11:47 AM, Rich Felker wrote: > > I don't see why thttpd is making it difficult. It makes routing with > > haproxy difficult only because haproxy is more pedantic than any web > > browser is about headers, but I don't want to use haproxy routing > > anyway. > > Does thttpd even have routing at all? As far as I can tell it is not > capable of sourcing routes from anywhere other than the filesystem. This > makes conditionally dispatching requests to git difficult. Perhaps I > misunderstand how this kind of thing could be configured with thttpd? If configured to do so, when foo/bar does not exist but foo/ does, it will exec foo/index.cgi with access to the full path requested. This suffices for cgit paths so it should suffice for git http protocol too. > > I'd love to have a modern one with the same type of design. > > Unfortunately all the modern ones are hideous. > > The design is what's antiquted. Well we disagree on this. I consider handling of all requests via the filesystem, using a single-task poll() loop, and exec'ing a cgi child process per dynamic request, to be the reasonable design from a standpoint of both proper isolation and decent efficiency. The whole "persistent task to handle dynamic content" thing was a mistake and is a lot more error-prone *and* resource-costly unless you're using awful language runtimes that are slow to startup. > > > I'd vote in favor of switching to nginx, in the > > > > nginx doesn't even support cgi. It just forwards to another server for > > cgi. It's also horribly bloated and enterprise-ey. In 5-10 years it > > will go exactly the same way Apache did. Watch for them to have their > > own Tomcat but for whatever language displaces Java... > > I agree on all of these points, but I'd like to draw attention to the > fact that 5-10 years from now is 5-10 years from now. That's plenty of > time to come up with a better httpd, and in the meanwhile nginx has yet > to go the Apache way. It's already bad, just not *as bad*. And it's much worse than what we have now, so there's no reason to switch to it. Rich