Chrome, HTTPS, and WooCommerce – Oh My!

If you recently started getting errors on your site (and you use WooCommerce), you can thank a new Google Chrome update. We observed it on a few sites while Zach, Amanda, and Josh from our development team jumped into action diagnosing what was happening.

It seems that Chrome is by default sending an HTTPS=1 flag in requests and disrupting sites with this flag.

To address the issue, you have two options:

1. Upgrade WooCommerce to the most recent version (v2.3.13).  We have observed that this corrects the issue with Chrome and HTTPS natively.  If, however, you cannot upgrade WooCommerce, you have one final option.
2. Add a header to your Apache .htaccess file until you can upgrade WooCommerce
   
<IfModule mod_headers.c>
RequestHeader unset HTTPS
</IfModule>


This seems to work in our testing – let us know if you see or observe anything else!