Dangerous conflict with cache plugins?

  • Resolved dampfhammer

    (@dampfhammer)


    9 years, 3 months ago

    I was just wondering why I was still seeing certain pages although I had installed and activated the Private Site plugin and emptied the browser cache.

    Then I realized that it had to do with the site cache. Apparently, the combination of this plugin and some very popular plugins (e.g. WP Fastest Cache) can lead to the dangerous result that protected pages are cached in the server and then available even to anonymous users because the cache delivers the page as it was rendered and intended for a logged-in user.

    I’m not sure if there is really a technical solution to this problem. But I think the least to do is to inform downloaders of this plugin in big red letters that they should NOT combine it with a cache plugin.

    There COULD be a technical solution, if this plugin would set HTTP headers to ensure that pages are never cached, which would admittedly make an installed cache plugin quite useless, but at least prevent unwanted readers from viewing cached content.

    https://www.ads-software.com/plugins/jonradio-private-site/

Viewing 1 replies (of 1 total)
  • Plugin Author David Gewirtz

    (@dgewirtz)

    Caching can always reach out and bite you (in many plugin configurations, not just this one). However, you’re right that more information on caching would be helpful.

    I’m making a note of your idea in my cool ideas list. Thanks!

    –David

    P.S. Marking resolved because caching issues are pretty much indicative of a day in the life of a WordPress site manager.

Viewing 1 replies (of 1 total)
  • The topic ‘Dangerous conflict with cache plugins?’ is closed to new replies.