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.
Has anyone actually confirmed the problem on a non-WooCommerce site? or a site without bad PHP code?
Usually, yes. But CGI has some headers that don't get that prefix, things like "CONTENT_LENGTH".
It looks to me like whoever added the HTTPS variable feature to Apache implemented it as an unprefixed header rather than a proper CGI variable, for some reason, and that's the issue.
That, or it is a CGI var, but some error in Apache allows HTTP headers to set it.
But I definitely defer to your wisdom as I'm just a user who hasn't done pure CGI in 15 years. As somebody who works on PHP, you are probably infinitely more qualified
I'd just like to say that this, indeed, appears to be the case. Apache bug most likely.
For a header called "HTTPS" to be turned into $_SERVER['HTTPS'] as opposed to $_SERVER['HTTP_HTTPS'] would require quite an impressive misconfiguration of the web server which also requires additional work compared to default settings (including possibly even patching PHP itself depending on SAPI).