I have two domain names pointing to the same ip, I am currently not using virtual host in my apache configuration. I simply use /var/www/html/ as root of the app. do I need to buy 2 godaddy certificates, one for each domain? It seems that godaddy certificate is tied to a domain, not ip, can someone clarify?
相关问题
- Mechanize getting “Errno::ECONNRESET: Connection r
- Tomcat and SSL Client certificate
- Can we add four protocols to ServicePointManager.S
- .NET Core gives unknown error while processing HTT
- JDK 11. javax.net.ssl.SSLPeerUnverifiedException:
相关文章
- ssl配置问题
- Intermittent “sslv3 alert handshake failure” under
- Making a two way SSL authentication between apache
- decrypt TLS 1.2 AES-GCM packet
- How to use Jetty with Let's Encrypt certificat
- Does the apple push notification distribution cert
- Sending email using php, gmail, and swiftmailer ca
- Can't pip install packages in python 3.6 due t
The SSL certificate has to match whatever host is typed in the browser's URL bar. If you type in a domain name, then the SSL cert has to match the domain name. If people use two different domain names, then you need two different SSL certificates (or one certificate that's valid for multiple domains). If you expect users to type in an IP address in the browser, then the cert would have to match the IP address.
However, in order to buy a certificate for an IP address from a reputable vendor (if the vendor will sign it at all), you need to be the owner of the netblock according publicly held records (e.g. ARIN, RIPE, etc.). See for example the GobalSign FAQ.
That is correct, SSL certificates are tied to a domain, not an IP address. The problem is that people type domain names into their browser address bar, not IP addresses (usually) and it's what you type into the address bar that is validated against the certificate (that is, the certificate validates that what you type into the address bar is what you're actually getting).
It depends on the SSL certificates. Some of them allow to specify more than one domain. Often this is limited to two names (www.example.org and example.org).
If it is exactly the same app on both domains, you should just configure a redirection from seconddomain.com to firstdomain.com - so there is only one domain name to worry about.