Tagged: Page Cache
September 1, 2020 at 6:36 pm #26341Michael HoganGuest
We’re looking to switch to a new caching plugin for our WP hosted site. We are currently using a “Force Login” plugin so that anyone who visits our website will be automatically redirected to ourwebsite.com/wp-login. Once any users get redirected to the /wp-login page, we have a SAML plugin that will redirect them to an MFA tool we use. The last caching plugin we used didn’t work with any kind of “Force Login” plugin and then pre-load caching option they had would stop working. Does W3 Total Cache work in this kind of environment?
MikeSeptember 1, 2020 at 6:40 pm #26352Jesse OwensKeymaster
I’ve reached out to some of the W3 Total Cache team to get some ideas how to accommodate this type of environment, please allow us a little time to research and get back to you.September 2, 2020 at 10:09 am #26358Marko VasiljevicKeymaster
I’ve checked the Force Login plugin and it appears that it may be adding no-cache headers to prevent caching.
It is not advisable to cache pages to logged-in users. The reason for this is because some secure content may be displayed to the other users that should not have access to this.
Also, please share some more information on what you want to achieve, what do you expect to be cached, and do you want pages also cached for logged in users?
Thanks!September 2, 2020 at 12:01 pm #26372Michael HoganGuest
Sorry, I should’ve specified that we were looking for server-side caching options instead of user caching. We wanted each page on our intranet to be cached on the server via the plugin so that it would increase load times when user’s went to our site. Would a plugin like Force Login cause issues with caching our pages server-side?
Thanks for the info!
MikeSeptember 2, 2020 at 12:55 pm #26377Marko VasiljevicKeymaster
Thank you for the clarification.
In this case, you can use W3 Total Cache for caching. However, once the user is logged in if the option in W3 Total Cache “Don’t cache pages for logged in users” is enabled, then the user will not receive cached pages. In case you want a logged in users to see cached pages, you should disable that option.
Again it’s not recommended to serve cached pages to logged-in users.
If you by any chance run into any kind of issue, please make sure to drop us a note so we can assist you with this.
- The topic ‘Does W3 Total Cache work with a “Force Login” Plugin’ is closed to new replies.