Cache Clear Problems

  • Resolved ch4ye

    (@ch4ye)


    1 year ago

    Hello.

    First of all thank you for the plugin. It speeds up site better than others.

    I have issues with clearing cache.

    1. I use option “Purge HTML pages only”, since most of the time images and such do not need to be cleared. When using purge whole cache, a lot is not being cleared. I think the issue is with cloudflare limit of 1000 urls per minute. I assume clearing cache under that option uses cached HTML pages list to clear cache. But in my case urls amount ends up about 4k. After that, they won’t show up on the list again, since when visited they already show up as hits. It doesn’t help that redirects ends up on the list. Is there a way to prevent redirects being cached, like 404. Because feeds and amp are redirected i had to add */feed* */amp* those rules, otherwise they end up on the list. Would be there a way to split urls in chunks, or from sitemap?
    2. When editing terms (category/tags). Cache is not cleared unlike when updating posts. And when done manually it will only clear first page.
    3. I might as well throw this problem too. Preload goes through paged terms. But in my case urls do not end up with /. And error logs show something like tagpage/2 cannot be cached. It’s clearly missing a /.

    I tried with “Disable cache purging using queue” and without, with the same results.

    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    Inside the plugin settings> other tab if you set Log verbosity to high and then updtae anything you will see the list of URLs that has been purged and the response that you have received by CF API.

    Thread Starter ch4ye

    (@ch4ye)

    Hi,

    Yeah, i went to look at possible solutions and looked up how that cache clear works. Apparently it is 30 urls per api call and up to 1000 per minute. It is okay when there is less requests. But once there is more it reaches limit and that’s that.

    [cloudflare::purge_cache_urls_async] Response for request 0: {“success”:false,”errors”:[{“code”:1134,”message”:”Unable to purge, rate limit reached. Please wait and consider throttling your request speed”}],”messages”:[],”result”:null}

    They are all purged at the same time. I am not sure if there is option in settings to to split it apart over longer period. I couldn’t find anything.

    I managed to fix problem with preload missing slash on paged pages by editing cache_controler.class.php file.

    I did end up finding different issue though. When updating post and changing permalink, it seems to only clear new permalink, leaving old one cached, so it won’t redirect.

    Is there a way currently to queue api calls within limits?

    Plugin Contributor iSaumya

    (@isaumya)

    I am not sure if there is option in settings to to split it apart over longer period. I couldn’t find anything.

    unfortunately that is not possible. You may need to contact Cloudflare to increase yoru API call limit or instead of purging individual URLs, purge the entire domain.

    I did end up finding different issue though. When updating post and changing permalink, it seems to only clear new permalink, leaving old one cached, so it won’t redirect.

    Yes, in this case, either you manually need to purge cache for the old URL or purge the whole domain. When you change permalink, there is no concrete way for a system to know what your old URL was. It only knows the current URL.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cache Clear Problems’ is closed to new replies.