3 ms·
From the Google bug report (https://crbug.com/505268 https://crbug.com/505268), it looks like WooCommerce was looking explicitly for $_SERVER['HTTP_HTTPS'], and
by geofft 11y ago
From the Google bug report (https://crbug.com/505268 https://crbug.com/505268), it looks like WooCommerce was looking explicitly for $_SERVER['HTTP_HTTPS'], and this code was removed when the Chrome behavior was discovered:
https://github.com/woothemes/woocommerce/issues/8479 https://github.com/woothemes/woocommerce/issues/8479
So "breaking web applications everywhere" is an exaggeration.
It also looks like this is the implementation of the W3 "upgrade-insecure-requests" spec, so "Chrome 44 sending HTTPs header by mistake" is also not true. It's intentional.
http://www.w3.org/TR/upgrade-insecure-requests/ http://www.w3.org/TR/upgrade-insecure-requests/
But it sounds like they're going to implement a different header / propose changes to the spec based on real-world feedback like this.
- deleted 11y ago[deleted]
- tomsommer 11y agoWooCommerce is not the only one doing stupid things with HTTP_HTTPS: https://github.com/search?l=php&q=HTTP_HTTPS&type=Code&utf8=%E2%9C%93 https://github.com/search?l=php&q=HTTP_HTTPS&type=Code&utf8=... Has anyone actually confirmed the problem on a non-WooCommerce site? or a site without bad PHP code?