• Resolved netpresenter

    (@netpresenter)


    Hi,

    Whenever a blacklisted user or anyone triggers a 403 page by Wordfence, Cloudflare caches this because the page is not seen as a 403 but just a regular WordPress page.

    This is a big issue on all of our sites that use Wordfence, and has been for about 2 years. When is a fix coming for this?

    We also used your form to submit these errors multiple times, but never gotten any response.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hey @netpresenter,

    I can bring this up with the Team. In the meantime, have you considered excluding the 403 URL from the Cloudflare cache? A glance at the Cloudflare docs mentions you can do this in Page Rules.

    Thanks,

    Gerroald

    Thread Starter netpresenter

    (@netpresenter)

    Hi Gerroald,

    The problem is we don’t know what to exclude from the cache, as the URL the visitor reaches stays the same, except the response is the 403 from WordFence. Perhaps you could shed light on what we should exclude from the cache?

    Hey @netpresenter,

    If you’re still experiencing this can you share screenshots of the expanded details of the blocks?

    You might try excluding 403.php. But I think this might be a Cloudflare configuration issue. You might check with them as well.

    Please let me know how it goes after excluding the 403.php.

    Thanks,

    Gerroald

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WordFence 403 gets cached’ is closed to new replies.