top | item 39473825

(no title)

jakebsky | 2 years ago

Thanks for Caddy, Matt! Some of us on the team have been using Caddy for years, for many of our projects. Because it's so simple, sufficiently high performance, and has lots of nice features.

The on-demand TLS certificates with an "ask" endpoint is especially useful for the PDS use-case. Because there's generally a wildcard DNS name that is used to give each new user a domain handle (@alice.example.com) but we don't want to be vulnerable to a TLS certificate DoS/rate limit situation.

discuss

order

mholt|2 years ago

Great reasons -- glad to hear that! Let me know if you encounter any hiccups or have feedback.

Love the fresh federated model btw!

charcircuit|2 years ago

Even if it may be simple in some areas, it doesn't handle edge cases such as https://github.com/caddyserver/caddy/issues/1632 in other areas out of the box unlike other server software.

Lutger|2 years ago

That is a bit unfair, as it is intentionally not doing so. You may disagree with it, sure, but as it stands I think your comment implies oversight or immaturity, which is evidently not the case reading the discussion on the issue you linked.

nyolfen|2 years ago

you have been repeatedly posting this incredibly niche complaint for years at this point

nativeit|2 years ago

Not for nothing, but when accessed from this HN app on an iPhone, Apple’s website with a trailing dot does not render correctly.