Feature Request: Renew Cache Should Not Happen On Guest Request

  • Hi,

    I have a feature request which is slightly related to this issue. When recaching of a site must happen, it should not do so on a random guest request.

    Picture this. If there is a plugin like Jetpack Bruteforce Protection and a visitor with a blacklisted IP triggers the renewal of the cache, you end up with a broken cached page which moans about your IP being banned.

    When a cache must be renewed, it should rather be queued somewhere and, I don’t know, a cronjob should make a local request to cache the new version.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Emre Vona

    (@emrevona)

    I didn’t fully understand the situation. Who sees broken pages? banned person? Or visitors who came later?

    Thread Starter alduinwf

    (@alduinwf)

    The visitors who come later see the broken “you are banned” page when the banned visitor triggered the cache.

    Plugin Author Emre Vona

    (@emrevona)

    ow! this is too bad. can you replicate the problem on a test site please?

    Thread Starter alduinwf

    (@alduinwf)

    I’m trying to doctor a simplified test case for development purposes. Hang on…

    Plugin Author Emre Vona

    (@emrevona)

    thank you. please let me know. I want to see the banned page.

    Thread Starter alduinwf

    (@alduinwf)

    Hi,

    I did not have the chance to create a test case yet, but it happened again, although not with googlebot.

    Here’s the cached html that was generated and is delivered to guests (ie. not logged in):

    https://paste.mozilla.org/Eod7O4Ra

    I fixed that on the live site now…

    Plugin Author Emre Vona

    (@emrevona)

    it is not a banned page. I need to see the banned page to exclude it.

    Thread Starter alduinwf

    (@alduinwf)

    I don’t quite understand? It is the homepage and a banned IP address triggered renewal of the cache. If you look at the bottom of the HTML, it says there is a problem with the IP 23.22.35.162, which is some crawler or whatever hosted at Amazon AWS.

    And this error page is delivered to any visitor until a new cache is created.

    Plugin Author Emre Vona

    (@emrevona)

    Please contact us via email: https://www.wpfastestcache.com/contact-us/

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Feature Request: Renew Cache Should Not Happen On Guest Request’ is closed to new replies.