I'm surprised adding the '.' after a website works as well as it does. I would have expected lots of broken vhost configurations because the browser sends the '

I'm surprised adding the '.' after a website works as well as it does. I would have expected lots of broken vhost configurations because the browser sends the '.' at the end and I would have expected TLS errors from some clients. For example if you use erlang you will get a TLS error like: 'TLS client: In state certify at ssl_handshake.erl:1774 generated CLIENT ALERT: Fatal - Handshake Failure\n {bad_cert,hostname_check_failed}' I don't think it is clear from the rfc6125 what TLS clients should be doing. However, if foo.com. resolves the same as foo.com then it makes sense that a certificate for foo.com can be used for foo.com. and vice versa.