Welcome to WebmasterWorld Guest from 54.226.33.117

Forum Moderators: rogerd & travelin cat

Why is WP Super Cache causing mixed content warning on homepage?

Can't disable the option that seems to be causing it

     
7:59 pm on Oct 1, 2017 (gmt 0)

New User

joined:Oct 1, 2017
posts: 4
votes: 0


WP Super Cache was working fine until I enabled SSL on my blog. It still works fine except for one issue.

With caching set to “On” I get a mixed content warning on the home page. All other pages are fine.

The WP Super Cache plugin has this option:

“Send non-secure (non https) request for homepage”

The box for that option is checked and that seems to be what’s causing the mixed content issue on the home page.

I can uncheck the box to disable it but it automatically re-checks itself when I click the “Update Status” button.

Am I doing something wrong or is this a bug in the plugin? Or perhaps there’s some conflict somewhere that prevents this setting from being disabled?

I appreciate your help. Thanks in advance!
9:01 pm on Oct 1, 2017 (gmt 0)

Moderator from US 

WebmasterWorld Administrator keyplyr is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Sept 26, 2001
posts:10646
votes: 630


You likely have unsecure content cached that is causing the mixed content error. Have you considered uninstalling, then reinstalling the plugin?
9:20 pm on Oct 1, 2017 (gmt 0)

New User

joined:Oct 1, 2017
posts: 4
votes: 0


Thanks for your quick reply. I really appreciate it.

When I run the home page URL through the Qualys SSL Server Test it shows no unsecure content at all with WP Super Cache disabled. The mixed content flags are only displayed when WP Super Cache is enabled. I did try uninstalling and reinstalling the plugin with the same result.

As a test I de-activated WP Super Cache and installed WP Fastest Cache and it passed the SSL Server Test with no warnings. I actually received better speed scores with WP Fastest Cache than I had been receiving with WP Super Cache so I'll probably just keep using that plugin anyway. I was just hoping someone knew what's causing the issue with WP Super Cache in case I decide to go back to it later (and in case there are others having the same issue).

It could well be operator error on my part - something I'm over-looking.

Again, I really appreciate your fast response! Thanks!
9:33 pm on Oct 1, 2017 (gmt 0)

Moderator from US 

WebmasterWorld Administrator keyplyr is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Sept 26, 2001
posts:10646
votes: 630


Well it sounds like you solved the immediate issue, so good job doing that.

Since thousands of WP sites are switching to secure content every day, it's likely that the bug(?) in WP Super Cache will be identified and corrected at some point.
9:44 pm on Oct 1, 2017 (gmt 0)

New User

joined:Oct 1, 2017
posts: 4
votes: 0


I'm sure you're right about that. Overall the transition of this blog from http to https went very smoothly with absolutely zero noticeable change in Google traffic (so far, at least - it's been about a week - fingers crossed!).

Thanks again for your help! Much appreciated!
10:02 pm on Oct 1, 2017 (gmt 0)

Moderator

WebmasterWorld Administrator ergophobe is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Apr 25, 2002
posts:8562
votes: 245


Hmm.... no issues here. I have WP Super Cache running and get an A on the Qualsys tester. I am running Cloudflare too, though, so that might change things.

As for unchecking the box that says "Send non-secure (non https) request for homepage," I believe that only pertains to cache testing and would, for example, show you if your redirects were set up wrong.

In other words, assuming it is checked, then when you hit the Test Cache button, it sends a non-secure request and then you can look at the test output and see whether it properly served up the https version from the cache or not. I *believe* that if your site is being served up as HTTPS, it will automatically check itself and if it is HTTP it will default to unchecked, but you would have to verify that.
10:40 pm on Oct 1, 2017 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month

joined:Sept 25, 2005
posts:1671
votes: 239


As far as I'm aware, the Qualys SSL Server Test does not test for mixed content. As the name implies, it tests your server. No parsing is done.

Whenever you get a mixed content warning, open up the network tab of your browser's developer tools, reload the page and check the console for warnings, or browse the list of downloaded resources to find the offender.
11:28 pm on Oct 1, 2017 (gmt 0)

New User

joined:Oct 1, 2017
posts: 4
votes: 0


Thanks for that. Big help!
4:33 am on Oct 2, 2017 (gmt 0)

Moderator

WebmasterWorld Administrator ergophobe is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Apr 25, 2002
posts:8562
votes: 245


Qualys SSL Server Test does not test for mixed content.


Ha, I didn't even pay attention. I thought the OP said he got a mixed mode error in the Qualsys test.

Anyway, when I switched to https, I did a hunt and find for mixed mode, then switched on WP Super Cache and have no mixed mode issues with it on or off.