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.
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.
And it's probably not niche if dozens of users are posting about it for years.
https://news.ycombinator.com./
If you want a link to a page with a link like this you can click on the github issue I referenced in my original comment as there are links there like that.
If you want a more natural page that is less meta with such a link
https://jameswillia.ms/posts/shortest-urls.html
>Also, the term ‘FQDN’ does not always imply the dot at the end?
Yes, but if there is not a . at the end then there is ambiguity of if it is a FQDN or not.