Excluded URL change after refresh?

Hi,

Please provide the LiteSpeed report. Go to LiteSpeed Cache Toolbox –> [5] Report and click “Send to LiteSpeed”. And if possible, please provide us with a way to reproduce the issue you claim.

Thank you.

I hit send to lite speed.

Here is the link to try to recreate the issue: https://flcannabisdeals.org/test-home/

Notice how it sends New in the heading and the gallery. Refresh the page and for me, it shows an older version of the page + the gallery stops working.

Thanks

I’m sorry I meant to tell you to send the report number to me, too.

I’ve played with your test site with Crome, MS Edge, and Firefox. On the surface, I’ve only noticed that the word “NEW” disappear on page refresh. I didn’t notice any other change. With developer tools, I’ve noticed that you’re using both Cloudflare and LSCache for caching. I think Firefox reveals more details behind the scene than the other two browsers. I suggest you run your site with Firefox with the developer tools on. You’ll see a lot more info. I even see a whole bunch of 302 errors. I have a feeling your issue may have something to do how you configure Cloudflare and LSCache for your caching needs. Normally, we do not recommend our users enable the same feature in any other plugin as they use with our plugin, so as to avoid conflicts. With Firefox, I saw the page was served to me from Cloudflare cache; after I refreshed the page, the word “NEW” appeared and there was no more info on caching; then, I hit refresh again, and I saw the page was served from litespeed cache. This may be the cause of your issue.

Regards.

Gotcha the report number is LQKBZMAC

Yes, it is a test URL so only the word “NEW” is different.

In Cloudflare my settings are:
Caching Level: Standard
Browser Cache TTL: 1 day

What I understand from your response is that I have 2 cache systems going and they are messing with each other. Do you recommend setting it to No query strings in cloudflare?

Thanks

Hi,

Yes to your question about the two plugins potentially messing with each other if not configured right.

One thing I can tell you for sure is that dynamic caching by Cloudflare definitely causes known issues with LSCWP. The way I see it, your best shot at troubleshooting this issue is by process of elimination. First, disable Cloudflare caching and see if the problem goes away. If so, then you have two options. 1) Not to user Cloudflare caching anymore; 2) Adjust settings in Cloudflare until the problem is gone.

If, however, the problem persists even when Cloudflare caching is disabled, then we’ll need to look at the LSCWP settings and see which of them might be the cause of the problem. Off the top of my head, the only thing I can suspect is the “Serve Stale” setting under the Purge tab. I see from your report that it is enabled.

Regards.

Got it I will need to troubleshoot with testing different settings.

On Cloudflare I do not see an option to directly disable caching I do see on caching level an option for No query string. Is that the same thing?

Cheers

I’m not really familiar with Cloudflare but I’ve got the following from Google search.

To disable cache in Cloudflare:

– Enter to Page Rules Tab.
– Click to Create page rule.
– Enter you domain name and choose Cache Level option.
– Set BYPASS value and click to Save button.
– Click to SAVE AND DEPLOY.

You can do it!

Thanks, I will need to play around with it.

Should I post here if I need more support or make a new thread?

Hi,

Please make a new topic

Best regards,