Mobile wordpress site serving stale cached homepage

What is the name of the domain?

carculturetv.com

What is the issue you’re encountering

The mobile version of the site is showing an old either cached or stale version.

What steps have you taken to resolve the issue?

The site is running on wordpress using both cloudflare and quic.cloud cdn connections with the litespeed cache plugin. I have purged everything multiple times from all three services including the cache in the server cpanel. Tried different browsers and devices and had others try on their devices.

For the life of me I can not figure out why it won’t update properly. And once in a great while it will show the desktop version of the menu and not the humburger.

Also the site is using tagdiv builder and on the mobile edit when saving it does say “Invalid data Current state has involved an issue.” for the headers. But unsure what that could be from.

May I ask how “mobile” is different?
Is mobile user recognized via user-agent, therefrom the Webpage is served via sub-domain as m.example.com?
I can see Website uses responsive Web design, however have to ask.

Did you prior Cloudflare had something configured already?

I can see quic cache being presented - when on desktop:

x-qc-cache: hit

But on mobile phone, or desktop but with mobile User-agent:

x-qc-cache: miss

That’s at least for CSS and JS.

However, origin LiteSpeed Cache:

Page cached by LiteSpeed Cache 6.5.2 on 2024-10-31 00:07:06

Allright, my assumption was wrong, “mobile” is not served via sub-domain, but the content is different :thinking:

Altough, unproxied so something is odd here without Cloudflare cache. Might be needs to refresh at origin first, then Cloudflare would follow. Or you’d have to implement a way to Purge Cache at Cloudflare (if it is kept at Cloudflare) from WordPress LiteSpeed Cache (via plugin?). Are you using a plugin for this or not?

Origin for now doesn’t set and send any HTTP cache-control headers.

If LiteSpeed is generating you HTML documents and serving them, wonder if you’ve had Browser Cache TTL left on default 4hours at Cloudflare or something else set to? :thinking:

1 Like

I have cloudflare set to respect existing headers as I’ve seen that be suggested everywhere for this problem already.

And since I’ve purged everywhere I am at a loss.

So the way wordpress and LiteCache setup the CDNs is through Quic.cloud which then also goes through cloudflare. All three have caches setup and all three are purged when changes are made. I believe almost everything is setup to be proxied on cloudflare minus the cnames to quic.cloud which setup as DNS only which I assume is for passthrough purposes between the two CDNs.

Any other suggestions from anyone before this closes automatically?

I am afraid combining multiple CDNs or proxies sometimes knows to have some issues with caching, and takes more in-deep overview for troubleshooting :thinking:

I’d go by disabling one by one and then from scratch, enable one by one and test to see where is the conflict and a “catch” to tune-up if possible.

Once you purge the cache, Cloudflare asks Quic.Cloud for new file, since Quic is not flushed, then Quic asks Litespeed, if Litepseed nor cleared at origin, the request for Cloudflare which would be served to the Website visitor would again be cached no matter what I am afraid since it’ll respect the origin cache headers.
Not sure what Quic does here, and if Litespeed updates the file requested from Quic, then Cloudflare should follow.
If Quic detects Cloudflare as “same visitor since before”, it’ll serve the “old” cache, and not go and check for new one?

It’s a bit complex I am afraid.

Ye, should be so Cloudflare doesn’t cache it, rather the resources are served directly from Quic, and not over and from Cloudflare.

This topic was automatically closed after 15 days. New replies are no longer allowed.