如果您的服务器不支持SNI，那么可以；每个证书需要一个专用 IP 地址。 由于 SSL/TLS 握手发生在发送任何 HTTP 标头（尤其是主机标头）之前，因此 Web 服务器无法知道要发送哪个证书。您可以使用 SAN 或 SAN 在一个 IP/端口上托管多个域/子域一份 href="http://wiki.cacert.org/WildcardCertificates" rel="nofollow">通配符 证书，但您仍然需要至少一个专用 IP。
If your server supports SNI (Server Name Indication), then you don't need a dedicated IP. The browser support for SNI is pretty good these days.
If your server doesn't support SNI, then yes; you need one dedicated IP address per certificate. Since the SSL/TLS handshake happens before any HTTP headers (most notably the host header) are sent, there's no way that the web-server could know which certificate to send. You can host multiple domains/subdomains on one ip/port using a SAN or wildcard certificate certificate but you'd still need at least one dedicated IP.
发布评论
评论（1）
如果您的服务器支持SNI（服务器名称指示），那么您不需要专用IP。目前，浏览器对 SNI 的支持非常好。
如果您的服务器不支持SNI，那么可以；每个证书需要一个专用 IP 地址。
由于 SSL/TLS 握手发生在发送任何 HTTP 标头（尤其是主机标头）之前，因此 Web 服务器无法知道要发送哪个证书。您可以使用 SAN 或 SAN 在一个 IP/端口上托管多个域/子域一份 href="http://wiki.cacert.org/WildcardCertificates" rel="nofollow">通配符 证书，但您仍然需要至少一个专用 IP。
有关详细信息，请参阅 http://blogs.iis.net/thomad/archive/2008/01/25/ssl-certificates-on-sites-with-host-headers.aspx
If your server supports SNI (Server Name Indication), then you don't need a dedicated IP. The browser support for SNI is pretty good these days.
If your server doesn't support SNI, then yes; you need one dedicated IP address per certificate.
Since the SSL/TLS handshake happens before any HTTP headers (most notably the host header) are sent, there's no way that the web-server could know which certificate to send. You can host multiple domains/subdomains on one ip/port using a SAN or wildcard certificate certificate but you'd still need at least one dedicated IP.
For more details, see http://blogs.iis.net/thomad/archive/2008/01/25/ssl-certificates-on-sites-with-host-headers.aspx