Can I use a "hogehoge.com" certificate without a hostname when I use SSL with SNI?
You are currently registered in two domains.
1. domain1.com
2. www.domain2.com
At this time, "www.domain2.com" recognizes successfully, but "domain1.com" recognizes the previously loaded certificate and results in an error.
The environment is
httpd-2.2.15-39
openssl-1.0.1e-30
mod_ssl-2.2.15-39
Yes.
OS is centos 6.6
LoadModule ssl_module modules/mod_ssl.so
Listen 443
SSLPassPhraseDialog builtin
SSLSessionCache shmcb: /var/cache/mod_ssl/scache (512000)
SSLSessionCacheTimeout 300
SSLMutex default
SSLRandomSeed startup file: /dev/urandom256
SSLRandomSeed connect builtin
SSLCryptoDevice builtin
NameVirtualHost*:443
SSLStrictSNIVHostCheckoff
<VirtualHost*:443>
ServerName domain1.com:443
DocumentRoot "/home/data/domain1.com/public_html"
SSLEngine on
SSLProtocol all-SSLv2-SSLv3
SSLCipherSuite ALL: !ADH: !EXPORT: !SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
SSLCertificateFile/home/config/ssl_key/domain1.com/server.crt
SSLCertificateKeyFile/home/config/ssl_key/domain1.com/server.key
SSLCACertificateFile/home/config/ssl_key/domain1.com/ca-bundle.crt
</VirtualHost>
<VirtualHost*:443>
ServerName www.domain2.com:443
DocumentRoot "/home/data/domain2.com/public_html"
SSLEngine on
SSLProtocol all-SSLv2-SSLv3
SSLCipherSuite ALL: !ADH: !EXPORT: !SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW
SSLCertificateFile/home/config/ssl_key/www.domain2.com/server.crt
SSLCertificateKeyFile/home/config/ssl_key/www.domain2.com/server.key
SSLCACertificateFile/home/config/ssl_key/www.domain2.com/ca-bundle.crt
</VirtualHost>
Would this article be helpful?
https://blog.apar.jp/linux/378/
http://e-garakuta.net/techinfo/doku.php/linux/apache-sni
SNIs don't seem to have any specific restrictions on hostnames, but there are a few things to keep in mind when using them.
Also, if possible, it may be clearer if you have installed an OS or an Apache HTTPD deployment, or if you have an httpd.conf or a conf file that you are referring to it.I hope it will be helpful.
Only one certificate is valid because NameVirtualHost*:443 is not configured.Or is your browser not compatible?
If irtNameVirtualHost*:443 」 is not configured, dhttpd-t で displays the following error:
[warn]_default_VirtualHost overlap on port 443, the first has precedence
© 2024 OneMinuteCode. All rights reserved.