News for hackers. Stuff that matters.
Re:Forcing Wordpress sites to use https even when not directed by geofft on Thursday July 23, 2015 @11:22AM (#9936283)
From the Google bug report (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

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/

But it sounds like they're going to implement a different header / propose changes to the spec based on real-world feedback like this.

Re:Forcing Wordpress sites to use https even when not directed by tomsommer on Thursday July 23, 2015 @02:07PM (#9937447)
WooCommerce is not the only one doing stupid things with HTTP_HTTPS: 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?