Mixed Content: The page at 'xxx' was loaded over HTTPS, but requested an insecure resource 'xxx'.
HTTPS The 39 an at xxx was
2023-09-27 14:21:28 时间
HTTPS页面里动态的引入HTTP资源,比如引入一个js文件,会被直接block掉的.在HTTPS页面里通过AJAX的方式请求HTTP资源,也会被直接block掉的。
Mixed Content: The page at 'xxx' was loaded over HTTPS, but requested an insecure resource 'xxx'. This request has been blocked; the content must be served over HTTPS.
解决办法:
页面的head中加入:
<meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests">
意思是自动将http的不安全请求升级为https
相关文章
- nginx 之 https 证书配置
- [转] Nginx 配置 SSL 证书 + 搭建 HTTPS 网站教程
- 如何在阿里云申请免费的HTTPS证书
- Python 域名转IP(可包含http、https)
- This request has been blocked; the content must be served over HTTPS.
- 【Charles】+抓取https请求抓不到 / 乱码
- Harbor配置https认证
- 【已解决】Https请求——基础连接已经关闭 发送时发生错误
- https Full Handshake
- Charles如何抓取HTTPS请求-移动端+PC端
- nginx配置https
- 维基百科默认HTTPS后 多数国家都能用了…
- linux 内核升级4.19 内核网站地址 https://www.kernel.org/
- [转]git clone出现 fatal: unable to access 'https://github.com/...'的解决办法(亲测有效)
- nginx 代理https后,应用redirect https变成http --转
- [转]局域网共享一键修复 18.5.8 https://zhuanlan.zhihu.com/p/24178142
- 【Google Chrome】 Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource问题解决