Carlos E. R. wrote:
On 12/10/2018 08.32, Per Jessen wrote:
The reason it does not work is - in comparison to http, when you are using https, you first need an encrypted connection. This can only be established if the site you are visiting can be properly identified and provided it has a certificate to match the name. For a default vhost you would need a certificate to match all the (otherwise unmatched) possible names and addresses.
For my illustration :-)
You say all possible names and addresses. So if I were to set up a site on my dynamic address, it would not work, because being dynamic the address is subject to change, right?
For http, it would work just fine. For https, the problem would be the same.
Or would be it possible to do, when the IP changes:
· change the certificate on the fly · update the dns to point to the new IP
The IP address is irrelevant for the certificate. -- Per Jessen, Zürich (19.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org