Title: Google mixed content – https requirement
Last modified: February 4, 2017

---

# Google mixed content – https requirement

 *  [dnatelso](https://wordpress.org/support/users/dnatelso/)
 * (@dnatelso)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/google-mixed-content-https-requirement/)
 * Can this cache tool assist in rewriting my URLs when cached or minified so that
   they end up [https://www.seafloridakeys.com](https://www.seafloridakeys.com).
   Right now Chrome is showing a mixed mode site.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [nigro.simone](https://wordpress.org/support/users/nigrosimone/)
 * (@nigrosimone)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/google-mixed-content-https-requirement/#post-8738432)
 * W3tc support ssl and help you to serve the assets with https.
 *  [Kimberly](https://wordpress.org/support/users/amiga500/)
 * (@amiga500)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/google-mixed-content-https-requirement/#post-8738547)
 * You could set things up in your .htaccess (or nginx.conf) file to do these custom
   URL rewrites.
 *  [benoitroubert](https://wordpress.org/support/users/benoitroubert/)
 * (@benoitroubert)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/google-mixed-content-https-requirement/#post-8899523)
 * Maybe I will be able to help you.
 * W3 Total Cache write all its instructions at the beginning of .htaccess file.
 * We had also this kind of problem because our own instructions in .htaccess for
   the http:// ➜ https:// redirection appeared after W3 total Cache job.
 * So pages were constructed with http:// links if the case you asked the page in
   http:// and not [https://](https://wordpress.org/support/topic/google-mixed-content-https-requirement/?output_format=md);
   and only after, was switching to [https://](https://wordpress.org/support/topic/google-mixed-content-https-requirement/?output_format=md).
 * So go see your .htaccess file and put this code below at the beginning of your.
   htaccess file:
 * #######################################################
    # INFOMANIAK ########################################################
   REDIRECT HTTP TO HTTPS TO AVOID DUPLICATE CONTENT # #######################################################
 * RewriteEngine on
    RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteRule (.*)
   [https://www.site.com/$1](https://www.site.com/$1) [R=301,L]
 * ######################################################
 * Hope it will work for you.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Google mixed content – https requirement’ is closed to new replies.

 * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806)
 * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)

 * 3 replies
 * 4 participants
 * Last reply from: [benoitroubert](https://wordpress.org/support/users/benoitroubert/)
 * Last activity: [9 years, 2 months ago](https://wordpress.org/support/topic/google-mixed-content-https-requirement/#post-8899523)
 * Status: not resolved