Canonical HTTPS detection not working

Hi @swinggraphics,

Thanks for letting us acknowledge this issue.

From my understanding on this topic, W3TC isn’t biased towards the scheme set and will cache the page as it encounters it.
Therefore, HTTP and HTTPS might get mixed. This can, without rewriting the source, caused mixed scheme issues and hence retention thereof.

I’m glad you’ve found a resolution thus far. In any case, I recommend forcing users to the HTTPS version of your site (through .htaccess) if you serve both. This, in the end, is better for SEO also.

If you have any more remarks or find things that might help others, feel free to let us know!

All I know is that when I changed SEO Framework’s settings, W3TC’s URLs also got fixed. Is SEOF rewriting URLs by searching generated code, or modifying the site URL? I am not serving mixed content at all; it’s only because SEOF incorrectly outputs http.

Hi @swinggraphics, just to add my 2 cents, have you tried the .htaccess fix?

# BEGIN Force http to https
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*) https://%{HTTP_HOST}/$1 [R=301,L] 
</IfModule>
# END Force http to https

This should force SSL no matter what plugins you use. Let us know, how it went!

Hi @swinggraphics,

TSF only adjusts the URLs between these HTML comments:

<!-- Start The SEO Framework by Sybre Waaijer -->
...
<!-- End The SEO Framework by Sybre Waaijer | 0.00159s -->

If anything else changes, then there’s a bug; or, something else likes to use TSF’s scheme settings, oddly enough.

That said, feel free to share annotations of what changes undesirably, and I’ll investigate.

@lebaux That doesn’t solve mixed content errors or the fact that the source code of the page contains http urls when they should all be https.

Somehow, SEOF is misreading http vs https when it autodetects, and some weird interplay between SEOF and W3TC is causing this problem. So far, all seems well having explicitly set the SEOF option to https. Probably too difficult to troubleshoot.

Hi @swinggraphics,

I’ll mark this issue for investigation. Patches will be brought with TSF 3.0.0 if anything requires fixing.

In the meantime, setting the Canonical Scheme selection to HTTPS seems to work great for anyone else encountering this issue ??

If you find any more issues, feel free to let us know.

Enjoy your weekend! ??

Hi, @swinggraphics,

I’ve looked into this issue, and no compatibility issues with W3TC have been found.

The SEO Framework’s canonical URL setting only affects URLs that The SEO Framework creates. It doesn’t affect any other URL.

If there are issues with the URLs generated by W3TC, you should contact their support.