WordPress weirdness in Google Chrome

WordPress weirdness in Google Chrome

Google has recently added a new bug feature in Google Chrome that has made some websites start acting strangely. Symptoms of this change include:

  • Site not rendering properly (no stylesheets, missing images and media)
  • Infinite redirect loops leading to your website not loading.
Website not rendering properly - Google Chrome

Website not rendering properly – Google Chrome

Website having infinite redirects - Google Chrome

Website having infinite redirects – Google Chrome

Never Fear, the Squirrels are Here

If you have been experience this on your website – or your website users have been reporting this to you, never fear. After several reports from Nuttify Champion Clients and some intrepid Googling the web squirrels at Nuttify HQ have found a solution for you.

The problem

Google has implemented a new web protocol where the web browser asks for the secure version of the page. This affects Chrome version 44.0.2403.xx. As Chrome auto updates soon everyone will be affected by this. As almost 50% of web users are on Chrome, this is a fairly serious issue.

Details of a conversation about this here (for the super nerdy). To quote from that page:

Chrome has implemented the Upgrade Insecure Requests specification from the World Wide Web Consortium (W3C).

Hold on – It’s easily fixed

We’ve solved this problem on Nuttify’s Apache servers by adding a few lines to the web server configuration file. Which remove the header request. This means that the web server effectively ignores the header request.

We found this remarkable and simple solution on this Stack Exchange thread

This fix is:

For this to work the Apache module headers.load must be enabled – only your server admin can do this for you.

If you are hosted with another provider

Fear not!

For this problem is also fixable by adding that code to your .htaccess file. We noticed this problem on another Champion Client’s website. They have not yet moved hosting over to the Nuttify Cloud, so we jumped in and added those lines to their .htaccess file and viola! Problem solved.

If it doesn’t work for you – you will need to ask your host to enable mod_headers on Apache. If you are running on nginx then  I’m afraid you’ll have to solve this one yourself, but if you are on nginx, then I’m sure you’re vary capable anyway.

Here’s an example .htaccess file for WordPress with that modification:

 

Like what you see?

Find out how we can build a champion website for you.

Call Nuttify today 1300 688 4391300 688 439
or send us a message