Re:The long life of Apache httpd 2.4
by mikepurvis on Saturday May 20, 2023 @08:11AM
(#36011238)
The only time in the last ten years that I've reached for Apache was when I needed to put an LDAP auth reverse proxy on something— it looked like it was possible to do it with nginx, but would require running a separate script or dealing with Lua or something. On Apache it was batteries-included and a few lines of pasted-in config file.
I'd love to be shown a better way on that, but Apache did rack up a W for that one use case.
Re:The long life of Apache httpd 2.4
by grepfru_it on Saturday May 20, 2023 @10:18AM
(#36012123)
Traefik, bruv
Caddy, hands down the most sane webserver config for a reverse proxy.
Re:The long life of Apache httpd 2.4
by mikepurvis on Saturday May 20, 2023 @05:12PM
(#36015677)
Thanks! That does look pretty reasonable: https://authp.github.io/docs/authenticate/ldap/ldap
I often find random parts of nginx hidden behind their paywall, and then I'll reach for Apache. Especially when creating load balancers
Re:The long life of Apache httpd 2.4
by paulddraper on Saturday May 20, 2023 @04:05PM
(#36015084)
If you're on Linux, you could use haproxy
I got the Caddy part quite wrong. Let me correct myself.
> Since then https://github.com/mholt/caddy-webdav has come out for Caddy.
It turns out that Matt Holt published the WebDAV plugin a short time before the launch of Caddy 2. I didn't know this. I only found out about the plugin later.
> Caddy 2, my go-to HTTP server, lacked a WebDAV plugin at the time.
It wasn't, and it didn't. This was in 2019, and Caddy 2 launched in 2020. I was still only using Caddy 1 when I tested nginx and then Apache. Caddy 1 actually had an unofficial WebDAV plugin, https://github.com/hacdias/caddy-v1-webdav, which I remember finding a compatibility reason to not use.
While setting up Apache 2.4, I came to like certain things about it. For example, https://httpd.apache.org/docs/2.4/mod/mod_macro.html. Configuration seems in general less footgun-y than that of nginx (see https://news.ycombinator.com/item?id=30435282). I have also adopted https://tcl.apache.org/rivet/ and use it on the LAN server where someone else might reach for PHP. It is admittedly quite niche.