Title: same cache for everyone
Last modified: August 27, 2025

---

# same cache for everyone

 *  Resolved [mcdeth](https://wordpress.org/support/users/mcdeth/)
 * (@mcdeth)
 * [9 months, 2 weeks ago](https://wordpress.org/support/topic/same-cache-for-everyone/)
 * Hi, the description says
 * [OSSDL CDN off-linker](https://wordpress.org/plugins/ossdl-cdn-off-linker/) has
   been integrated into WP Super Cache to provide basic CDN support.
 * but OSSDL wasnt updated for 14 years, last support thread was 3y ago and it literally
   says cdn doesnt wrork, isnt it time to assume the other plugin is dead?
 * And main question, can I set in settings to serve same cache for logged in users
   and users with item in cart? Dont cache only users with specific cookie. I’m 
   aware of implications.

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

 *  [Reynier (a11n)](https://wordpress.org/support/users/reynierc/)
 * (@reynierc)
 * [9 months, 2 weeks ago](https://wordpress.org/support/topic/same-cache-for-everyone/#post-18617032)
 * Hi [@mcdeth](https://wordpress.org/support/users/mcdeth/)
 * Thank you for your question and for sharing your concerns regarding OSSDL CDN
   off-linker and caching options.
 * **You are correct:** The [OSSDL CDN off-linker](https://wordpress.org/plugins/ossdl-cdn-off-linker/)
   plugin is no longer actively maintained, the last update was over a decade ago,
   and support activity has also ceased. However, its core functionality is now 
   part of WP Super Cache’s built-in CDN solution, as you may have noticed [in the WP Super Cache description here](https://wordpress.org/plugins/wp-super-cache/#:~:text=OSSDL%20CDN%20off%2Dlinker%20has%20been%20integrated%20into%20WP%20Super%20Cache),
   which is still actively supported.
 * **About your main question: **Yes, it is possible to configure WP Super Cache
   so that the same cached pages are served to logged-in users and users with items
   in their cart, only skipping cache for users with a specific cookie. However,
   this is **not the default or recommended** behavior and must be set up deliberately
   in the plugin’s advanced settings. You’ll see those under **Settings > WP Super
   Cache > Advanced,** shown here:
 * ![](https://i0.wp.com/cldup.com/yCGL6elak7.png?ssl=1)
 * Scrolling down, you’ll also find “Rejected Cookies” settings, which allow you
   to skip caching cookies you specify.
 * ![](https://i0.wp.com/cldup.com/2cvVIeZCZP.png?ssl=1)
 * Though you’ve already mentioned that you’re aware of the implications. I’d still
   wanted to remind about proceeding with caution, as caching logged-in or cart 
   users can expose user-specific content. I sugggest to always test these changes
   carefully in your environment. 🙂
 *  Plugin Support [Stef (a11n)](https://wordpress.org/support/users/erania-pinnera/)
 * (@erania-pinnera)
 * [9 months, 1 week ago](https://wordpress.org/support/topic/same-cache-for-everyone/#post-18628782)
 * Hi there, [@mcdeth](https://wordpress.org/support/users/mcdeth/),
 * Do you have updates about that, do you still need help? We usually close inactive
   threads after one week of no movement, but we want to make sure we’re all set
   before marking it as solved. Thanks!

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

The topic ‘same cache for everyone’ is closed to new replies.

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

 * 2 replies
 * 3 participants
 * Last reply from: [Stef (a11n)](https://wordpress.org/support/users/erania-pinnera/)
 * Last activity: [9 months, 1 week ago](https://wordpress.org/support/topic/same-cache-for-everyone/#post-18628782)
 * Status: resolved