Title: stup*d plugin.
Last modified: July 16, 2022

---

# stup*d plugin.

 *  [Fody](https://wordpress.org/support/users/fodisery/)
 * (@fodisery)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/stupd-plugin/)
 * The way you prevent cf prevent cache for logged in user is nonsense:
    if (is_admin()
   || is_user_logged_in() || is_feed()) { header(“Cache-Control: no-cache, must-
   revalidate, max-age=0”); }
 * That code will run on our hosting server, our hosting server know user logged
   in or not checking it via is_user_logged_in()
 * But how CF know this user already logged in or not before hitting our server?
 * If CF know hosting server responded with “Cache-Control: no-cache, must-revalidate,
   max-age=0”. Then it means CF not getting the page from the cache, but from our
   server.
 * It means cacheeverything need to hit our server first to know whether this user
   is logged in or not.
 * Logged in user doesnt just browse ‘wp-admin’ logged in user can also browse other
   page like homepage. So how CF know user browsing homepage is logged user or not
   without requesting from our server first?

The topic ‘stup*d plugin.’ is closed to new replies.

 * ![](https://ps.w.org/wp-cloudflare-cache/assets/icon-256x256.png?rev=3084953)
 * [Cloudflare Page Cache for WordPress](https://wordpress.org/plugins/wp-cloudflare-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-cloudflare-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-cloudflare-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-cloudflare-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-cloudflare-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-cloudflare-cache/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [Fody](https://wordpress.org/support/users/fodisery/)
 * Last activity: [3 years, 10 months ago](https://wordpress.org/support/topic/stupd-plugin/)
 * Status: not resolved