Cache Enabler Creating Issues with Canonicalization

  • Trace

    (@diesel12)


    6 years ago

    Our domain is a wordpress multisite installation that is forced to use https:// via the wpmu domain mapping plugin. As such, navigating to the https:// version will redirect to https://.

    When we enable cache enabler, navigating to https:// no longer redirects to https://… UNTIL we clear cache, at which time the first attempt to https:// will redirect to https:// but all subsequent attempts to https:// do not redirect and stay at https://. This behavior is repeatable and only occurs with cache enabler enabled. Have attempted to troubleshoot by changing to 2017 theme and disabling all plugins to no avail.

    Anyone have any thoughts on this?

Viewing 4 replies - 1 through 4 (of 4 total)
  • codyarsenault

    (@codyarsenault)

    Do you have a link to the plugin you’re referring to? Also, is it required that the plugin handle the HTTP to HTTPS redirect? We’ve seen some mixed content issues in the past and the following redirect rule in .htaccess resolved the issue:

    RewriteCond %{HTTP:X-Forwarded-Proto} !=https
RewriteRule (.*) https://%{HTTP_HOST}/$1 [R=302,L]
    Thread Starter Trace

    (@diesel12)

    I am able to recreate the issue when using the code above in my .htaccess with the domain mapping plugin turned off, so it seems that regardless of whether the https directive is coming from the domain mapping plugin or from the redirect snippet in.htaccess, the canonicalization issue occurs as soon as cache enabler is turned on with https redirects working for one page load after cache is cleared and then failing on subsequent page loads.

    This is the domain mapping plugin: https://premium.wpmudev.org/project/domain-mapping/

    • This reply was modified 6 years ago by Trace.

    Did you also add the redirection snippet at the top of your .htaccess file? We’re using this plugin on many HTTPS-based sites that have HTTP to HTTPS redirects however have yet to experience this issue. Do you perhaps have some additional rules in your .htaccess that might interfere?

    Thread Starter Trace

    (@diesel12)

    Thank you for the follow up! I was incorrect in that I thought the .htaccess code was also resulting in the same issue as I had incorrectly NOT put it above the existing .htaccess code per your suggestion. We ended up going a different direction plugin wise but appreciate your help!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Cache Enabler Creating Issues with Canonicalization’ is closed to new replies.