HTTPS Header Header with Chrome Version 44.0.2403.xx

I'm afraid, since I installed the new version of Chrome 44.0.2403.xx.

My initial problem was that some stylesheets on my website were uploaded via https, but my site was only http.

I use wordpress, so I searched inside the main function to find where HTTPS was added to the URL.

The offender is the is_ssl() function. The Wordpress base is an HTTPS check against the $_SERVER['HTTPS'] variable, and mine is 1.

I found out that the latest version of Google Chrome sends the HTTPs = 1 header.

How can I prevent this header from causing problems on my website?

+5
source share
6 answers

To solve my problem, I included mod_header on the server and added this rule to my appache2.conf file:

 <IfModule mod_headers.c> RequestHeader unset HTTPS </IfModule> 
+3
source

The header sent by Google Chrome HTTPS: 1 translates to $_SERVER['HTTP_HTTPS'] on the server side. If you encounter this problem and want a temporary fix, add the following to the wp-config.php file:

 // Chrome 44 HTTPS:1 header issue temporary fix $_SERVER['HTTP_HTTPS'] = 0; 

UPDATE 2015-07-29

from chrome version 44.0.2403.107, the HTTPS header has been removed and replaced with the Upgrade-Insecure-Requests: 1 header.

+2
source

If you can’t change the configuration of your server or just for testing purposes, you can use this chrome plugin Change headers for Google Chrome ™ , go to the plugin and add an action (Modify) with a name (HTTPS) and a value (0), do not forget to enable his.

To do this, your Wordpress site will work as it should.

+1
source

I had the same problem and decided to add the following code to the end of the functions.php file:

 function https_chrome44fix() { $_SERVER['HTTPS'] = false; } add_action('init', 'https_chrome44fix',0); 
+1
source

Do you use WooCommerce in your WordPress? Is WooCommerce updated to the latest version 2.3.13 ?

According to this article, there is a problem with Google Chrome HTTPS: 1

I also ran into this problem, but decided after updating WooCommerce to the latest version 2.3.13 .

0
source

This plugin, available on GitHub, can save you a ton of problems until the next version of Chrome is released.

This basically causes HTTPS to be false. A fix for Google Chrome will be available in the next release, which is scheduled for July 27, 2015. Until then, the plugin should help.

You can view it on GitHub: https://goo.gl/D54cWv

Greetings

0
source

All Articles