Comet Cache vs Wordfence caching

  • Resolved wanderer

    (@bluegeek26)


    8 years, 7 months ago

    Three/four questions:

    Should I go ahead and enable Wordfence’s Falcon Engine caching with Comet Cache running at the same time?

    Will Comet Cache have any conflict issues with Wordfence’s Falcon Engine caching?

    Are there any parts of Wordfence that should be disabled when used with Comet Cache?

    I want to use Comet Cache since its main speciality is in caching (and therefore may do an even better job), while all-in-one packages often are more like jack of all trades than specializing in one thing. Here’s a link that may help you answer my questions:

    https://docs.wordfence.com/en/Falcon_Cache?utm_source=plugin&utm_medium=pluginUI&utm_campaign=docsIcon

    They even mention “when you enable Falcon we disable features that don’t work reliably in a cached environment” — so what features in Wordfence might need to be disabled for Comet Cache to work reliably?

Viewing 3 replies - 1 through 3 (of 3 total)

  • I reviewed the Wordfence source code and from what I can tell these are the Wordfence features that get disabled when the Wordfence Falcon Engine cache is enabled:

    – Live Traffic Monitoring
    – Blocking ranges of IP addresses
    – Country blocking will only work on the login page and other dynamic pages

    Also, from my review of the Wordfence source code, it doesn’t look like there is anything in Wordfence that would prevent Comet Cache from working reliably.

    Thread Starter wanderer

    (@bluegeek26)

    Thanks Raam. I appreciate the time you took to check into the Wordfence source code to see whether their disabled features (when their Falcon Engine is activated) might also interfere with the cached environment in Comet Cache (if those features are left enabled).

    To make sure I understood clearly: leaving these Wordfence features enabled is unlikely to cause issues with Comet Cache, even though it’s also a cached environment, correct?

    @bluegeek26 That’s correct. The only “issues” you might have are with Wordfence Live Traffic Monitoring, blocking ranges of IP addresses, and blocking specific countries, since all of those features require visitors to be hitting WordPress directly so that Wordfence can “intercept” those requests and do something with them. When you’re using Comet Cache to cache your website, Comet Cache will intercept the requests first and serve the visitor a cache file, which makes your site faster and reduces the amount of server resources your site uses.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Comet Cache vs Wordfence caching’ is closed to new replies.

Tags