From: Drew DeVault <sir@cmpwn.com>
To: musl@lists.openwall.com
Subject: Re: Supporting git access via smart HTTPS protocol for musl-libc
Date: Tue, 26 Mar 2019 11:43:04 -0400 [thread overview]
Message-ID: <20190326154304.GB2267@homura.localdomain> (raw)
In-Reply-To: <20190326151344.GB23599@brightrain.aerifal.cx>
On 2019-03-26 11:13 AM, Rich Felker wrote:
> The problem is that I don't know how to hook up the smart git http
> backend via cgi. Maybe you're suggesting running it on a separate
> httpd with haproxy doing the routing, but that's not compatible with
> TLS-layer (rather than HTTP-layer) use of haproxy, and the latter does
> not work with thttpd's cgi conformance issues, nor do I want to
> introduce further dependency on haproxy, which is a big hammer. I'd
> rather move in the opposite direction towards something like a
> non-broken version of stunnel.
After a more detailed study of thttpd, I understand why this is
difficult. Honestly, thttpd seems like a really antiquated and
inflexible httpd. I'd vote in favor of switching to nginx, in the
interest of having good before having perfect, with a plan to perhaps
port OpenBSD httpd or something similar.
However, the other suggestion of busybox httpd + git-http-backend seems
reasonable to me. It sounds like you were hoping to keep thttpd in play,
though, which seems folly to me.
next prev parent reply other threads:[~2019-03-26 15:43 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 [this message]
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
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=20190326154304.GB2267@homura.localdomain \
--to=sir@cmpwn.com \
--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).