带有小部件的 IE 安全警告
我正在创建一个使用 Facebook Connect 和 fbml 标签的 ASP.NET 应用程序。它还使用 LinkedIn 小部件。当我在任何浏览器中运行此应用程序时，没有任何警告并且一切正常。然而，在 IE 中，会出现这样的消息：
Security Warning:
The current webpage is trying to open a site in your Trusted sites list. Do you want to allow this?
Current site:http://www.facebook.com
Trusted site:http://localhost
（LinkedIn.com 也是如此）。我知道如何从客户的角度解决此问题并停止显示安全警告。但是，是否可以确保此消息不会出现，因为它可能会让不知道如何抑制此警告的用户感到厌烦？我还没有尝试将其上传到我的虚拟主机，因此不确定生产中的每个人是否都会出现此消息。但是，我总是在本地计算机上获取它。
（我的页面都没有使用 SSL，所以我不认为这是问题所在。我尝试使用 FB 的 HTTPS url，但这没有什么区别）。
谢谢
I'm creating an ASP.NET application which uses Facebook Connect and fbml tags. It also uses the LinkedIn widget. When I run this app in any browser, there are no warnings and everything works. However, in IE, a message like this comes up:
Security Warning:
The current webpage is trying to open a site in your Trusted sites list. Do you want to allow this?
Current site:http://www.facebook.com
Trusted site:http://localhost
(same for LinkedIn.com). I know how to fix this from a client perspective and to stop the security warning showing up. However, is it possible to ensure this message doesn't come up as it could be off putting for users who don't know how to suppress this warning? I haven't tried uploading it to my webhost, so not sure if this message will appear for everyone in production. However, I always get it on my local machine.
(None of my pages use SSL, so I don't think that's the issue. I tried using FB's HTTPS urls but that didn't make a difference).
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我多次遇到过 IE 消息。虽然这里的情况可能并非如此，但我总是检查 Firebug 以查看是否有任何请求发送到 Https（使用 Net 选项卡）。如果可能的情况是您引用的某些内容本身正在调用其他内容。
如果您正在提供 https 页面，然后通过 http 获取图像，您通常会收到该消息。
可能没有帮助，但这是我在这种情况下做的第一件事。
I have come across the IE message many times. Whilst this might not be the case here I always check in Firebug to see if any requests are going to Https (using Net tab). If may be the case that something you are referencing is itself making a call to something else.
Often you get that message if you are serving an https page and then going to fetch an image over http.
Might not help but is the first thing I do in this situation.