[charcircuit]

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.

[napkin]

Curious. What is the use case here? I’ve spent tens of thousands of hours of my life on the Internet and a lot of that as a sysadm and I’ve not once heard of people accessing or linking to sites this way.

[charcircuit]

Personally, I just want to properly handle this edge case and it would bother me if my sites didn't handle it correctly. There are advantages for using FQDNs since they are not ambiguous there are extra optimizations that can be done. I don't want my sites to be problematic for people who want to use them so I make sure my sites properly handle them. Usually handling FQDNs is easy as it just works out if the box on most server software.

[napkin]

Can you provide a URL to a page containing a link of this style? I’ll concede that it’s useful to someone if I see it! The term ‘FQDN’ does not always imply the dot at the end?

[charcircuit]

Do you just want a link?

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.