Chrome 中的混合内容错误；网站不包含混合内容；清除缓存并重新打开 Chrome 无法解决
我收到来自 Google Chrome 的混合内容警告。它不会在 Firefox 或资源管理器中显示。
我从运行 Vista、Apache2.2.16、mod_ssl2.2.16、OpenSSL0.9.8 和 PHP5.3.3 的本地主机上的测试服务器打开该站点。所有内容均由 apache 强制通过 https。我正在使用自签名证书。
整个源代码包含在index.html 中。上面写着：
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<h1>Hello</h1>
</html>
首先，我用 ctrl-shift-j 验证没有混合内容。然后，我尝试以不同的组合，关闭 Chrome 并重新打开，清除缓存，然后重新启动服务器。
有人可以告诉我如何摆脱警告吗？谢谢，金博
I am getting a mixed content warning from Google Chrome. It does not show in Firefox or Explorer.
I'm opening the site from a test server on localhost running Vista, Apache2.2.16, mod_ssl2.2.16, OpenSSL0.9.8, and PHP5.3.3. All content is forced through https by apache. I am using a self-signed certificate.
The entire source code is contained in index.html. It reads:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<h1>Hello</h1>
</html>
First, I verified with ctrl-shift-j that there is no mixed content. Then, I tried, in varying combinations, closing Chrome and reopening, clearing the cache, and restarting the server.
Can someone please tell me how to get rid of the warning? Thanks, Jimbo
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我尝试通过 https://127.0.0.1 而不是 localhost 访问该网站，并且没有出现混合内容警告。我不明白为什么会发生错误，但我很确定当网站实际发布时这不会成为问题。谢谢大家。 ——金博
I tried accessing the site through https://127.0.0.1 instead of localhost and it worked without a mixed-content warning. I don't understand why the error occurs, but I'm pretty sure this won't be an issue when the site is actually published. Thanks all. --Jimbo
目前这只是理论，但我发现即使没有混合内容，如果某个时候在会话期间域上已经遇到混合内容，我也会在 Chrome 中收到“混合内容”警告。
（这里还提到：为什么 Chrome 会报告安全/不安全警告，而其他浏览器却没有报告安全/不安全警告？，并在此处报告为错误：http://code.google.com/p/chromium/issues/detail?id=24152)
This is just theory for now, but I am finding that I get the "mixed content" warning in Chrome even when there is no mixed content, if sometime during the session mixed content was already encountered on the domain.
(Also mentioned here: Why is Chrome reporting a secure / non secure warning when no other browsers aren't?, and reported as a bug here: http://code.google.com/p/chromium/issues/detail?id=24152)