News for hackers. Stuff that matters.
Re:Forcing Wordpress sites to use https even when not directed by jbverschoor on Thursday July 23, 2015 @11:02AM (#9936130)
Chrome isn't breaking the applications. The applications are breaking the applications
Re:Forcing Wordpress sites to use https even when not directed by ajross on Thursday July 23, 2015 @11:07AM (#9936181)
This is a web browser. Bug-for-bug compatibility with 2+ decade old content servers is a fundamental requirement.

Yes, standards are great. But you can't break sites.

Re:Forcing Wordpress sites to use https even when not directed by Cakez0r on Thursday July 23, 2015 @11:21AM (#9936273)
I'd say it's more like a courtesy than a fundamental requirement. Obviously Chrome has overstepped the mark here, but you can't just perpetually support entrenched bugs otherwise you end up with a browser like internet explorer.
Re:Forcing Wordpress sites to use https even when not directed by ajross on Thursday July 23, 2015 @12:42PM (#9936877)
Everything is relative, and surely there are some misfeatures that simply can't be handled gracefully. But broadly, no: if some user wants to hit a archived site from 1995 using Chrome 44, I think virtually everyone would expect that to work and not fail.

To take your extrapolation in the other direction: you're arguing that if we want to hit old stuff that we need to do it in a VM running Windows 98 and IE4.

[deleted]
Re:Forcing Wordpress sites to use https even when not directed by detaro on Thursday July 23, 2015 @11:09AM (#9936195)
Shouldn't a header called HTTPS end up in $_SERVER['HTTP_HTTPS'] and not 'HTTPS'?
Re:Forcing Wordpress sites to use https even when not directed by dangrossman on Thursday July 23, 2015 @11:13AM (#9936218)
It depends on the web server and runtime environment in use. WooCommerce for example examines both of those variables, as either or both might be set.
Re:Forcing Wordpress sites to use https even when not directed by zodiakzz on Thursday July 23, 2015 @11:12AM (#9936212)
Yup and this sounds like a massive security hole in PHP if you can change $_SERVER elements like 'REMOTE_ADDR' with headers.
Re:Forcing Wordpress sites to use https even when not directed by nolok on Thursday July 23, 2015 @12:14PM (#9936685)
It's not in PHP, its in Apache. Apache's the one in charge of reading the request and passing to PHP the server variables, it's the one who made the contract that HTTPS means the request was made over HTTPS, it's the one who send to the called handler the value of HTTPS and it's also the one who put the wrong value in it.

It wrongly put the browser-sent header in there overwriting it's own variable (or creating it when it shouldn't).

Re:Forcing Wordpress sites to use https even when not directed by Cakez0r on Thursday July 23, 2015 @11:17AM (#9936247)
Sounds more like a language issue.

    $_SERVER is an array containing information such as headers, paths, and script locations.

    You may or may not find any of the following elements in $_SERVER.
    'HTTPS'
    Set to a non-empty value if the script was queried through the HTTPS protocol.
https://secure.php.net/manual/en/reserved.variables.server.p...
Re:Forcing Wordpress sites to use https even when not directed by TazeTSchnitzel on Thursday July 23, 2015 @12:54PM (#9936964)
That's not an issue with PHP itself. $_SERVER maps directly to CGI variables (or equivalents provided by the web server in non-CGI environments).
Re:Forcing Wordpress sites to use https even when not directed by detaro on Thursday July 23, 2015 @11:21AM (#9936272)
But then the environments violate that specification if they set this variable off a random HTTP header?
Re:Forcing Wordpress sites to use https even when not directed by Cakez0r on Thursday July 23, 2015 @11:24AM (#9936304)
If the language spec says that $_SERVER['HTTPS'] is an indicator of whether the request was made over HTTPS, then it should ensure that it adheres to its own spec (I.E. not overwrite $_SERVER['HTTPS'] with the value from a header, if it's present).
Re:Forcing Wordpress sites to use https even when not directed by nolok on Thursday July 23, 2015 @12:10PM (#9936656)
It does. The problem is in Apache, not the language.

Apache's says to look into the HTTPS variable (that it adds itself before passing the call to the handler) to know if the call was made over https, but then it overwrite that variable with the browser-sent header if there is one (or more exactly, it uses the same variable name for that header and it's own HTTPS indicator; so it overwrites if both are present, and if only the header is present then it creates it when it shouldn't -- the issue in this post).