Page Caching Issue With Wordfence

  • bward

    (@bward)


    4 years ago

    We are noticing pages that have been cached are not recorded in the Wordfence plugin. I reached out to their support and they explained our caching plugin (Cache Enabler) is running before Wordfence can log the visit and potentially block the visitor.

    We are currently using the Advanced Configuration. We removed that from .htacess and same result.

    We also moved Wordfence’s .htacess configuration to the top of our .htacess file, then WordPress, then Cache Enabler, and no change.

    Is there any other configuration we can change so we can use Wordfence properly with this caching plugin?

    Thanks so much.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Anonymous User 16850768

    (@anonymized-16850768)

    If using the advanced configuration that allows the server to deliver the cached pages then WordPress will be entirely bypassed. This means even Cache Enabler isn’t initiated during the request.

    If using the default configuration Cache Enabler uses the advanced-cache.php drop-in to deliver a cached page. This does occur before any plugins are initiated. To get a better idea of the issue to see what solutions are available, can you please let me know what request data Wordfence is checking? Is this able to be done on the server through the .htaccess file?

    Thread Starter bward

    (@bward)

    Thanks for the follow up.

    I did not catch your question about Wordfence. If you are asking where I saw that Wordfence was not logging traffic, that was in their Live Traffic setting. I have 30 days of data stored.

    As an example, while browsing in private mode, I do not see my traffic generate within the Live Traffic display of Wordfence on cached pages.

    Now if I visit a page I excluded in Cache Enabler, then yes, I do see the IP/visit in Live Traffic.

    I have also tested these results against the actual server logs. I see visits from bad bots, but not in Wordfence. This is why I initially reached out to them.

    Concerning the .htaccess file, this is what Wordfence adds by default, we have this at the top of the file, WordPress config is second and Cache Enabler advanced config is last.

    # Wordfence WAF
<Files ".user.ini">
<IfModule mod_authz_core.c>
	Require all denied
</IfModule>
<IfModule !mod_authz_core.c>
	Order deny,allow
	Deny from all
</IfModule>
</Files>
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Page Caching Issue With Wordfence’ is closed to new replies.