Does not work with Cloudflare Cache Everything Page rule

It’s not a matter of the plugin support at this point. The plugin does not handle the ability to cache, it just flushes the cache when you post.

Have you opened a ticket at DreamHost? This is something that has to be fixed there.

Dreamhost seems not interested in doing that.

They do (we do) but getting info and help from CF has been pulling teeth :/

I’ll make an internal ticket to loop back to this.

Quick Edit: Ticket made and I’m working on it. This MAY be a false ‘miss’ and if so, it’s an easy fix.

• This reply was modified 3 years, 3 months ago by Ipstenu (Mika Epstein).

Okay good news/bad news!

Good news? It’s a false miss. You’re absolutely being cached.

Bad news? It’s a timing issue with when that check happens, and I’m going to see if I can fix this for everyone.

(The longer explanation is that we have a pretty binary way of checking if something’s cached, and Cloudflare is ‘in the way’ of it. The check happens and Varnish says “Oh CF didn’t cache so I will!” but since CF actually has the cache the second time, Varnish … caches the miss, even though it totally did cache :sigh: I’ll figure it out.)

Sorry about the followup .. I looked into your site and you’ve got some extra caching plugins in there (WP Rocket, which absolutely can be used with DreamPress but may not be configured right).

Would you be willing to open a support ticket with DreamHost and then link to this thread asking if it can be assigned to me? I’ll put it on my docket for Monday and see if we can bang this out.

We’ve tested on four other people on CloudFlare and they’re all fine, so something is unique about your site that is going to need some server level digging, which I’m not sure you want to do on public channels ??

Hi Mike @ipstenu
Thanks for looking into this and apologies for the late reply. I think it has something to do with Cloudflare’s Edge Cache TTL.
https://blog.cloudflare.com/edge-cache-expire-ttl-easiest-way-to-override/
So in the Cache everything page rule I have set, it has Edge Cache TTL as 1 month.
So the varnish x-cache is always MISS. When I remove Edge Cache setting, the varnish cache gets HIT.
However, the Cloudflare cache ratio decreases significantly.

As for the WP-Rocket, they have Hosting compatibility:
https://docs.wp-rocket.me/article/670-hosting-compatibility
Wherein, WP-Rocket plugin removes its Page Caching in favor of Varnish. It does for many hosting services that has server-side caching.

Can you confirm, if this should be the default behavior? Or should Varnish still have HIT despite using Edge Cache TTL?

Can you confirm, if this should be the default behavior? Or should Varnish still have HIT despite using Edge Cache TTL?

I THINK, and I have to say that as Cloudflare’s not responded to my attempts to reach out yet, that is correct and it’s actually a false miss. Or rather, it’s a miss, but it’s okay.

The best I’ve been able to determine, since you’re getting cached on CF, that cache is hit before Varnish. The first hit to your site would be non-cached on Varnish (and CF) because it has to have the hit to cache. The second hit goes to CF and not Varnish, so per Varnish that’s actually okay because it doesn’t matter. You’ve got CF so you don’t need to double cache.

I’m trying to sort out how to get Edge to actually show up as a proper cache, since it’s okay, but it’s an uphill fight, and I may need to loop in my Varnish contact and see if Tor’s got any more muscle to get CF to help us unpack things.

But. In this case, it certainly seems like you’re just fine, and it’s a race condition that’s actually working like it should.