fm2009修改器 全职高手only发给我一个吧!!谢了1 youareonly...

==thedayaftertomorrowDeleteList.txt Create at
05:36:27==
[hangzhou-jinzhan-.cn]In a , we talked about the problem of using HTTP based resources, such as images, on a secure HTTPS page. Internet Explorer interrupts the download and displays a confirmation dialog whenever it detects the use of mixed content on a secure page.
In IE 7 and ealier, this dialog would cause annoyance to users but generally didn’t cause any other significant problems. This was because it was worded in such a way that most users would click on the Yes button and allow non-secure content to be downloaded.
However, the wording in the IE 8 version of this dialog has changed:
To download the content a user would now have to click on the No button. As we know, most people using the web only
it if at all possible! They will usually go for the Yes button if there is not an OK button.
Some sites are going to find that their secure pages in IE 8 have the following problems:
Any non-secure HTTP
used for analytics data gathering will often be ignored
The page may not display or even work correctly if it relies on non-secure images, CSS or Javascript
Therefore, avoiding mixed content on HTTPS pages is even more important now that IE 8 has been released. It often becomes an issue when using third party services such as or Content Delivery Networks (CDN). For example, we
on our site until .
As mention in the , an IE user you can disable this warning by:
to Tools-&Internet Options-&Security
Select the Security tab
Click on the Internet zone icon at the top of the tab page
Click the Custom Level button
In the Miscellaneous section change Display mixed content to Enable
Repeat steps 1 – 5 for the Local intranet and Trusted sites zones
However, if you are developing a web site you can’t expect your visitors to do this. It is better to fix the cause of the problem so that the warning is not displayed by default in IE 8. The only way to do this warning is to ensure that your HTTPS pages only access embedded resources using the HTTPS protocol. You can do this by following these steps:
Use a sniffer like HttpWatch that . The
is sufficient for this because you only need to see the URLs being accessed.
Access the page causing the problem and click No when you see the security warning dialog.
Any HTTP resources shown
in the HttpWatch window are the s even if they loaded directly from the browser cache and didn’t cause a network round trip:
If you don’t initially see any HTTP based resources, try refreshing the page because a non-secure image may have been retrieved from the
or Firefox image cache
EDIT #1: If you are a web developer trying to track down why your page causes this warning please also take a look
where we cover some javascript snippets that can also trigger this warning. The comments section of both of these posts also contain useful information where people have found and solved related issues.
EDIT #2: Updated instructions to apply the change to all network zones
Ready to get started?114网址导航收藏到: &
(提示:顶到域名世界首页,分享给更多网友)&&
欢迎您就本域名知识点留言评论!
您的姓名:
* 可选项,留空即为匿名发表
评论内容:
剩余字数:& * 按 Ctrl + Enter 直接发送.
域名世界提醒您:评论只需提交一次,请耐心等候,审核后方可显示.
精彩域名知识
域名世界推荐

参考资料

 

随机推荐