Egregoros

Signal feed

API Docs
Timeline

Post

Remote status

Context

3
Tom

Tom

@pertho@mastodon.bsd.cafe remote
Open link

Hey #FreeBSD folks! What's your "Go To" web server software?

Poll (single choice)
Apache
1 vote 14.3%
Caddy
2 votes 28.6%
Lighttpd
0 votes 0.0%
Nginx
4 votes 57.1%
Something else (Comment in thread)
0 votes 0.0%
7 votes total · 7 voters Poll ended
Replying to @pertho@mastodon.bsd.cafe
Only 3 Easy Payments of $19.95

Only 3 Easy Payments of $19.95

@feld@friedcheese.us remote
Open link
@pertho @dch I don't use haproxy for redundancy, I use it because it's best-in-class for any TCP proxying/termination, but also for TLS as well. And you can swap in WolfSSL for additional performance/security (seriously, OpenSSL 3.0+ is really REALLY badly performing compared to 1.x)

plus it supports the PROXY protocol if you need it... and it supports things like "just drop certificates in a directory, and it will find them and use them automatically"

can't be beat for that really

Wish Willy wouldn't have caved and imported the QUIC library for HTTP/3 or he'd have been able to keep his "no crashes in production in over 15 years" or whatever message on the official website (AIUI, the crashes that happened were due to QUIC support... I could be wrong though)

Replies

4
Replying to @feld@friedcheese.us
dch :flantifa: :flan_hacker:

dch :flantifa: :flan_hacker:

@dch@bsd.network remote
Open link

@feld @pertho I still have not tried its new ACME cert renewal. It looks more cumbersome than caddy, but HAProxy has to cater for a significantly larger scale.

I have used haproxy for so many things, like dog-legging iSCSI implementations in a cloud env to be able to get pcaps while boxes are booting, it's my favourite unix tool, followed closely by curl.

Replying to @dch@bsd.network
Replying to @feld@friedcheese.us
Replying to @dch@bsd.network