>That is a bit unfair, as it is intentionally not doing so.

That doesn't change my point. I am pointing out a an easy pitfall Caddy users can fall in since it is not automatically handled for them as it is with other server software, nor is it pointed out in the documentation fkr Caddy. Simple server software would avoid these pitfalls automatically for users. So while it now be simple to get https working, properly configuring the server is now more complex to get right.

An intentional pitfall doesn't mean it isn't a pitfall.

Is it possible you're vonfusing that user with me? I used to be relatively vocal about this issue on HN. For reference, that's not me.

And it's probably not niche if dozens of users are posting about it for years.

I have only brought this up once before on HN and it was over 2 years ago. Not adopting a new project because it is missing something niche is an extremely common reason why people stick with tried and true, mature software. I do not see anything wrong with pointing out niche issues because to some people these issues are important. Because it's broken out of the box it is allowing people who aren't aware of this problem to continue to setup broken sites. Even caddyserver.com. is broken.