Support » Plugin: Preload Fullpage Cache » Not working with LiteSpeed Cache

  • rafaucau

    (@rafaucau)


    I tried this plugin on a site that uses LiteSpeed Cache and unfortunately the posts after publishing and first visit returns a x-litespeed-cache: miss header.

    It’s as if the LiteSpeed server ignores writing to the cache if it sees that the request is not from a real user. Maybe you need to improve the User-Agent or add other headers?

    • This topic was modified 3 months ago by rafaucau.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Pothi Kalimuthu

    (@pothi)

    I confirm that the plugin doesn’t work with LSWS and its cache plugin as of this writing. I will look into it.

    Plugin Author Pothi Kalimuthu

    (@pothi)

    Unfortunately, I couldn’t figure out what has gone wrong when working with LiteSpeed server / plugin. I turned on debugging on the LiteSpeed plugin and simulated the headers (within preload fullpage cache plugin) from a real world browser too. No luck so far. Since, the cached content isn’t stored within WP filesystem, it is hard to troubleshoot. I will leave this issue open. If there are any further ideas to try out, please let me know. I have an OpenLiteSpeed server to test drive for now*.

    For others, this plugin still works with WP Super Cache and WP Rocket plugins. I will update the plugin README file to reflect the incompatibility for now.

    Thanks.

    Thread Starter rafaucau

    (@rafaucau)

    I asked on LiteSpeed support. Maybe they can give some suggestions.
    https://wordpress.org/support/topic/how-to-preload-cache-after-publishing-a-post/

    Plugin Author Pothi Kalimuthu

    (@pothi)

    Ok. As mentioned in the other thread, the cache is cleared very late in the hierarchy of events / hooks / actions, after the plugin tries to preload a post.

    In order to replicate, I turned on debugging on LSWS server, visited an existing post (to generate the cache), updated the post to trigger pre-loading. What I saw in the LSWS server log is… the request from this plugin gets through at first (I could see a “hit” in the response header. Then, LSWS clear the cache.

    Since, a caching plugin (such as LiteSpeed Cache) has more control over the order of actions / hooks, this plugin (preload fullpage cache) is unlikely to override such order.

    I saw a not-so-practical workaround. Please see this… https://wordpress.stackexchange.com/q/56266/9584

    • This reply was modified 3 months ago by Pothi Kalimuthu. Reason: Fixed the link to the other post
Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.