- From: sleevi <notifications@github.com>
- Date: Mon, 19 Dec 2016 18:33:34 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 20 December 2016 02:34:06 UTC
What do you mean how SSL works? RFC6125 covers name validation, but it has no relation to the Origin or URL specs. Unlike names in URLs (whose omission of a trailing dot may result in domain suffix search), the names expressed in a certificate are always fully qualified and have an implicit trailing dot. Whether or not an implementation recognizes is implementation dependent, and neither RFC6125 nor the URL spec would likely alter browser behavior here, since the name matching is typically not part of the "browser" managed side (instead it's part of the TLS library / OS) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/issues/132#issuecomment-268138007
Received on Tuesday, 20 December 2016 02:34:06 UTC