Chrome重定向到安全资产



我在chrome上遇到了一个奇怪的行为。我有WP网站http://flytime.hu,它没有SSL,从来没有。如果我尝试登录到网站(/wp-login.php),它试图加载大量的资产(css,脚本)与https协议,但页面本身是加载http.

如果我检查页面源,我可以看到以https开头的url。这在Firefox(或其他浏览器)中不会发生。我不能登录,因为登录重定向到https协议以及(https://flytime.hu/wp-login.php)。

经过这样的尝试后,主站的行为方式相同(由于SSL协议错误而未加载资产)。然后我必须完全重新安装chrome浏览器,以获得主要网站至少回来。清除cookie,缓存和所有这些都没有帮助。

chrome源码(URL: http://flytime.hu/):

<link rel='stylesheet' id='bkb-font-awesome-styles-css'  href='https://flytime.hu/wp-content/plugins/bwl-kb-manager/css/font-awesome.min.css?ver=1.0.7' type='text/css' media='all' />
<link rel='stylesheet' id='bkbm-custom-styles-css'  href='https://flytime.hu/wp-content/plugins/bwl-kb-manager/css/bkbm-custom-styles.css?ver=1.0.7' type='text/css' media='all' />
<link rel='stylesheet' id='contact-form-7-css'  href='https://flytime.hu/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=4.2.1' type='text/css' media='all' />
<link rel='stylesheet' id='blogsynthesis_jss_css-css'  href='https://flytime.hu/wp-content/plugins/jquery-smooth-scroll/css/jss-style.min.css?ver=4.2.2' type='text/css' media='all' />

Firefox源码(URL: http://flytime.hu/):

<link rel='stylesheet' id='bkb-font-awesome-styles-css'  href='http://flytime.hu/wp-content/plugins/bwl-kb-manager/css/font-awesome.min.css?ver=1.0.7' type='text/css' media='all' />
<link rel='stylesheet' id='bkbm-custom-styles-css'  href='http://flytime.hu/wp-content/plugins/bwl-kb-manager/css/bkbm-custom-styles.css?ver=1.0.7' type='text/css' media='all' />
<link rel='stylesheet' id='contact-form-7-css'  href='http://flytime.hu/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=4.2.1' type='text/css' media='all' />
<link rel='stylesheet' id='blogsynthesis_jss_css-css'  href='http://flytime.hu/wp-content/plugins/jquery-smooth-scroll/css/jss-style.min.css?ver=4.2.2' type='text/css' media='all' />

现在在function.php文件上试试。

function https_chromev44fix() {
    $_SERVER['HTTPS'] = false;
}
add_action( 'init', 'https_chromev44fix', 0 );

我有同样的问题。Chrome在版本44.0.2403.89 m的顺序与nginx做https重定向,而不是像我在nginx配置的http。

Chrome升级到版本45.0.2454.12 dev-m然后事情就消失了