Browser Caching & Logged in Pages

Hello
you can check the check box “Don’t cache the page for logged in Users” from general settings once its done purge all cache then it will never cache from logged in users
Thanks

I’m having this same issue and was just about to post…

The issue isn’t the server caching. The server caching works fine. (And doesn’t cache for logged in users.)

The problem is that the browser has already cached the logged out version of the page. So when the user logs in, the browser just pulls the from the local cache and doesn’t make the request to the server.

It looks like what we need is a way to set nocache options on certain pages. Or a way to exclude specified pages from the browser based cache settings.

Is there a way to do this? This issue is actually preventing my users from logging in and purchasing!

I am having the exact same problem as described by @zherbert.

I look forward to finding a resolution to this issue!

yes you can exclude specific pages that can not be cached
goto Page Cache->Never cache the following pages: type the page name here and save the settings at the end don’t forget to purge the cache
thanks

I have used Page Cache->Never cache the following pages to keep specific pages from being cached & also have the Don’t cache pages for logged in users option checked.

However, the problem continues – when the user logs in and goes to a page they viewed when not logged in, it looks like they’ve been logged out, because it still shows the cached, logged out version of the page.

The problem isn’t PAGE caching. Page caching works great. Everyone is happy with page caching.

The problem is BROWSER caching. And how those two features work together.

Browser caching effectively negates the “don’t cache pages for logged in users” feature.

Because by the time the user has logged in, the browser has already cached that page and so the user NEVER GETS the logged in version.

What we need is a way to tell the BROWSER cache to not apply to certain pages. Or really, to be able to give a list of pages to send NOCACHE tags to the browser. Part of a “total cache” solution should be the ability to tell the BROWSER to never cache certain things.

I’m a little baffled that this hasn’t come up before. Because this is an absolutely showstopping issue. What’s the point in improving performance on your site, if the solution is going to prevent your customers from logging in or submitting orders??

hey zherbert
which version of w3tc you used? latest version can cause more load on CPU
even there is .html files are not created in page_enhanced directory
Please let me know

• This reply was modified 7 years, 6 months ago by Prince_Dhaval.

I’m sorry, I don’t know how else to explain this… The issue is with browser caching. Not server caching.

I’m on the latest version, but that doesn’t matter. It isn’t about CPU load or directories.

Do you actually work for W3 Edge?

At this point, I have to assume that the needed feature doesn’t exist.

I’ll go ahead and make a separate thread to warn other users against using W3TC on membership sites until the feature is added. And I’ll also send a message to W3 Edge directly to make them aware of the issue so that it can be addressed in a future version.

You are right at your point
but i am talking about the different scenario may be you are not aware of that
Thanks