Conversation
supportHello, I’m having issue to enable cache for logged in users (customers). I have a big website with other 50k products, website is fine if user is not logged in and cache hit correctly (using cloudflare connected); but whenever customer do the login, website is very slow and pages are not being cached using this plugin. I tried to check if there’s some settings to enable or disable related to enabling cache also to customer logged in, but nothing I found; looking at header this is what i get: cf-cache-status: DYNAMIC cf-edge-cache: no-cache pragma: no-cache priority: server-timing: cfCacheStatus;desc="DYNAMIC" server-timing: cfEdge;dur=9,cfOrigin;dur=5340 server-timing: cfExtPri PHP/8.4.15 x-wp-cf-super-cache: no-cache x-wp-cf-super-cache-cache-control: no-store, no-cache, must-revalidate, max-age=0 x-wp-cf-super-cache-disabled-reason: Logged In x-wp-spc-disk-cache: BYPASS What can I do in order to enable cache also to logged in users?
Hi there, @elettrb3l , Thanks for explaining your issue. Based on what you shared, what you saw is expected behaviour, and WP Super Cache is working correctly. By design, WP Super Cache d oes not cache pages for logged-in users, because logged-in sessions usually contain user-specific, dynamic data (account info, prices, orders, permissions, nonces, etc.). That’s why you’re seeing: x-wp-cf-super-cache-disabled-reason: Logged In cf-cache-status: DYNAMIC no-cache / no-store headers For WooCommerce sites especially, caching logged-in customers at the page level is unsafe and can cause data leakage between users. If logged-in pages are slow, the correct optimisations are: Persistent object caching (Redis / Memcached) for logged-in traffic Database optimisation PHP opcode caching (OPcache) WooCommerce-specific performance tuning Cloudflare page caching and WP Super Cache should only be used for logged-out visitors. Logged-in performance must be handled at the server/object-cache level, not via page cache plugins. Hope that answers your question 🙂
Hi there, @elettrb3l , Thanks for explaining your issue. Based on what you shared, what you saw is expected behaviour, and WP Super Cache is working correctly. By design, WP Super Cache d oes not cache pages for logged-in users, because logged-in sessions usually contain user-specific, dynamic data (account info, prices, orders, permissions, nonces, etc.). That’s why you’re seeing: x-wp-cf-super-cache-disabled-reason: Logged In cf-cache-status: DYNAMIC no-cache / no-store headers For WooCommerce sites especially, caching logged-in customers at the page level is unsafe and can cause data leakage between users. If logged-in pages are slow, the correct optimisations are: Persistent object caching (Redis / Memcached) for logged-in traffic Database optimisation PHP opcode caching (OPcache) WooCommerce-specific performance tuning Cloudflare page caching and WP Super Cache should only be used for logged-out visitors. Logged-in performance must be handled at the server/object-cache level, not via page cache plugins. Hope that answers your question 🙂