3 ms·
Support for trailing dots got much better in recent years. Some website still completely brake. http://microsoft.com./ http://microsoft.com./ is a 404 for inst
by the_mitsuhiko 3y ago
Support for trailing dots got much better in recent years. Some website still completely brake.
http://microsoft.com./ http://microsoft.com./ is a 404 for instance. http://google.com./ http://google.com./ redirects. https versions often give certificate errors.
- tialaramex 3y agoWhen it comes to certificates, the specification explicitly says that only www.something.example is correct† even if in DNS terms that should be www.something.example. Thus it's misissuance (ie against the rules, you'd need to stop doing it or risk being distrusted) to issue that site a certificate for "www.something.example." instead of (or as well as) "www.something.example" and I'd guess that since we have CT (and thus can see mistakes in almost real time) nobody does that. Of course a web browser could, AFAIK just accept that www.something.example is the correct name to see in the certificate, it seems Firefox at least does that and perhaps all popular browsers do. Unfortunately the web server also needs to understand how this works and the linked site reports that (at least when it was written) Apache httpd doesn't. That wouldn't surprise me, Apache httpd was probably a great web server a quarter century ago, but not today. † I think it's in PKIX somewhere? I might be wrong about exactly where it is, but it's something people have thought about and decided will be settled to work the way it actually does in practice today and too bad if we don't like that.