From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Supporting git access via smart HTTPS protocol for musl-libc
Date: Tue, 26 Mar 2019 13:57:00 -0400 [thread overview]
Message-ID: <20190326175700.GD23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190326155743.GC2267@homura.localdomain>
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
next prev parent reply other threads:[~2019-03-26 17:57 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 [this message]
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
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=20190326175700.GD23599@brightrain.aerifal.cx \
--to=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).