URGENT: Google Chrome bug with version 44

[RobinKeymaster]

Just so you guys know, there is a known bug with the newest release of Google Chrome that breaks a lot of WordPress sites. The exact symptoms include forcing HTTPS on stylesheets and javascript includes. It is very strange that Google would have rolled out an update that breaks WordPress, but it is a known issue that they are working on.

Don’t bust your head trying to figure it out. Use FireFox or don’t update your browser to 44.

https://spunmonkey.design/chrome-beta-44-causing-problems-with-httpsssl/

[RobinKeymaster]

I have added a fix for this on our PLUS servers and ORG site, and this will be useful for all you standalone users:

add this:

$_SERVER[‘HTTPS’] = false;

to your wp-config file. Google is apparently going to fix this error in three days, but if you don’t want to lose visitors for 3 days, there you go. If, like Henri, you run your entire site on HTTPS already, this probably won’t affect you.

[innerstockParticipant]

Robin would you recommend using https?

Thanks for fast resolving Chrome issue. My site ok now.

[RobinKeymaster]

I don’t think so – Google has said it thinks most people should be doing it, but few sites are doing it yet. In September there are going to be free SSL certificates so maybe in the future it would be worth switching to full HTTPS. I’ll probably post about it later on.

Edit: I’m not too keen on doing this because I think it creates unnecessary overhead. Initial connections to HTTPS websites always include additional slowdown due to the encryption, and it’s totally unnecessary in 99% of the cases. We’ll see as time goes on. I don’t think it’s going to be a relevant issue for the next year at least.

[innerstockParticipant]

Good, I prefer to wait.

[Author]

Posts