无效的安全证书和域名 [英] invalid security certificate and domain names

问题描述

我最近购买了安全证书为www.example.com有效的一个网站，但不是* .example.com的（通配符版本 - 更贵）
我现在的问题是，虽然用户可以键入 http://example.com ，安全版本（启用SSL页）https：//开头的例子.COM引发无效证书例外 - 这是完全可以理解的。

I recently purchased a security certificate for a website valid for www.example.com but not for *.example.com (wildcard version - more expensive) The problem i have now is that although users can type http://example.com , the secure version (ssl enabled pages) https://example.com raises the invalid certificate exception - which is totally understandable.

我如何可以重定向HTTPS流量前www.example.com版本的 的请求实际上打服务器？我试图网址rewritting并没有任何运气重定向。任何想法？

How can i redirect https traffic to the www.example.com version before the request actually hits the server? i tried url rewritting and redirects without any luck. any ideas ?

该网站使用ASP.NET构建和托管的IIS 7的服务器上。

The website is built using ASP.NET and Hosted on an IIS 7 server.

谢谢！

推荐答案

再花几块钱一（〜GoDaddy的$ 30），用于对较短域example.com便宜的证书。

Spend another few bucks for a (~$30 at Godaddy) for a cheap cert for the shorter domain example.com.

这似乎不大可能，用户的显著的用户在打字https://example.com。如果他们在输入地址，他们可能正在使用http：//或没有。您应该能够设置2虚拟主机，一个用于 http://example.com/ ，一个用于HTTP（S）：// www.example.com。重定向一切从example.com到www.example.com

It seems unlikely that a significant number of users users are typing in https://example.com. If they are typing in an address they are probably using http:// or nothing. You should be able to setup 2 virtual hosts, one for http://example.com/, and one for http(s)://www.example.com. Redirect everything from example.com to www.example.com

SSL的首次谈判，所以确实没有什么可以做重定向从https://example.com连接https://www.example.com如果https://example.com具有无效证书。

SSL is negotiated first, so there isn't really anything you can do to redirect connections from https://example.com to https://www.example.com if https://example.com has an invalid certificate.

这篇关于无效的安全证书和域名的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！