3 ms·
I would recommend giving Caddy[0] a try. Most servers/reverse proxies need 10s of options to work more or less well. With Caddy, "correct" is the default, incl
by polyrand 6y ago
I would recommend giving Caddy[0] a try.
Most servers/reverse proxies need 10s of options to work more or less well. With Caddy, "correct" is the default, including having the best SSL management system (so you don't even need certbot) I've seen, and using HTTPS by default. It's true that it has some things missing (rate-limitng and weighted load balancing to name a few) that you can do in Nginx/Traefik/etc, but it's 100% worth it. Caddy also has a great extension system, so those things could easily be created as extensions.
[0] https://caddyserver.com/ https://caddyserver.com/
- bottled_poe 6y agoI downvoted you because changing technology doesn’t inherently solve the concern of security. The other things your mentioned as strengths seem relatively equivalent to other web servers.
- shawabawa3 6y agoUsing Caddy _does_ solve the problem of "Common Nginx misconfigurations that leave your web server open to attack". Currently Caddy's defaults are secure and you don't need to worry about fiddling with settings to keep it that way
- Filligree 6y agoIt also has a lot fewer memory safety CVEs.
- efrecon 6y agoCaddy has a rate limiting plugin. Using it requires building a new Docker image, if necessary. https://github.com/hundertzehn/caddy-ratelimit https://github.com/hundertzehn/caddy-ratelimit
- jakearmitage 6y agoHow slow is it compared to nginx?