• Resolved sarangsss29

    (@sarangsss29)


    Now that Page Rules are deprecated, I have implemented Cache Rules instead of Page Rule.

    Edit: using this link https://gist.github.com/isaumya/af10e4855ac83156cc210b7148135fa2

    Now, within Super Page Cache plugin, do we still need to enable Page Caching? Because enabling that option, it automatically creates a Page Rule at Cloudflare, which is not the intended way now. Is there a way to not allow the super page cache create page rule in CF? Also, at first I could not see the Page Rule, when I visited the dashboard again after some time, I could see it. Which could be an issue if someone does not keep tab on the Page Rule section.

    Is it recommended enabling Fallback Caching? Are there any added benefits of it? Will the cache hit ratio increase?

    • This topic was modified 4 months, 3 weeks ago by sarangsss29.
Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    In the guide it is already mentioned that if you are using the cache rule, you need to deactivate the page rule added by the plugin.

    Fallback cache is there to work as a fallback when the page is not cached in CDN edge but it does not increase cache HIT ratio.

    Thread Starter sarangsss29

    (@sarangsss29)

    Thanks for the reply @isaumya I meant Page caching within the plugin, not Page rule.

    Enabled page caching and disabled page rule.

    Anyway, I have followed the tutorial but the cache hit is quite low like around 65% despite enabling “Sort Query Strings” Also followed the suggestions from here for litespeed server: https://www.ads-software.com/support/topic/using-litespeed-cache-super-page-cache/

    Disabled all other page caching and Guest Mode, and only enabled optimization. But kept Cache crawler from LiteSpeed cache thinking it would warm up the cache.

    APO had like 95% cache hit. But for some reason, APO does not work with LiteSpeed server.

    Any suggestions in increasing the cache hit ratio?

    Edit: I have put https://www.example.com in the first cache rule called hostname because my website starts with www. With non-www, it did not seem to work. Can I put *example.com instead? Could this be an issue?

    • This reply was modified 4 months, 2 weeks ago by sarangsss29.
    Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    Please share your site URL so I can see if everything is working properly on your website. Cache HIT ratio depends on many things. If the item is not being requested by users Cloudflare will delete the item from cache. But first please share your website URL.

    Thread Starter sarangsss29

    (@sarangsss29)

    Plugin Contributor iSaumya

    (@isaumya)

    Ok. I can see that the page caching is working properly on your website.

    Thread Starter sarangsss29

    (@sarangsss29)

    How to increase the cache hit ratio?

    Plugin Contributor iSaumya

    (@isaumya)

    You should give this a read before you try anything about increasing cache HIT ratio: https://acnam.com/untold-truths-of-cloudflare-cdn/#cloudflare-cache-creation-replication-storage

    If you have good traffic on your website, Cloudflare will keep the items in cache.

    Diiamo

    (@luislu)

    @isaumya hi, same question here. If use the cache rule, and deactivate the page rule added by the plugin, then the plugin TEST CACHE will fail.

    Plugin Contributor iSaumya

    (@isaumya)

    No “Test Cache” will still work like normal. Nothing will fail.

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.