Too much caching, way too much caching

Hi,

For about 3 months now, my site is caching way too much. I have disabled cache from admin. Also I have cleared cache from admin. Again, I have cleared the 3  cache folders on Cpanel: cache, cache_public and tmp. I also cleared browser cache. All I have to do is browse few pages and caching will resume. 

(1) When site caches, users can't log out. They have to clear cache in browser first.

(2) After user clears browser cache and logs out, if he logs in again, the user must clear cache again else he will see the previous page like he is guest who has not logged in. (Cos of cache).

Cache on all pages, not log out/ login issue only

My web host says they have disabled cache on the server. I can't tell what to do next. Pls assist.

The purpose of caching is to speed things up.  Sounds like you have other issues going on.

Hi geek_girl thanks for the reply,

I understand caching will help speed up the site. I disabled the cache to help identify the problem. So far, disabling caching hasn't help. I would like to know of anything possible I should look at to help me identify the problem described.

Go to your admin, and cache and settings.  Turn off cache and compression for JS files.  Clear the caches, clear the /cache and /cache.public leaving the .htaccess file in place for each directory, clear your browser cache and then test.

I suspect that you have the reverse proxy installed for your site. You need to properly configure it to consider when a user is logged in or disable at all.

 Thank you Alex. I do not know reverse proxy on the site. I will ask my host provider about it

 I did all that long before I posted the problem. Thanks for concern

 Hi Alex, my host has disabled reverse proxy and installed ngix rather. But the problem still persist. Still too much caching on the site. The hosting provider says they have no settings that will cause that much caching. I have still disabled cache from the admin. What else can I consider please?

Most probably then Nginx isn't configured properly, Nginx can be used as reverse proxy, and maybe it's used this way in your situration. Also Nginx can send headers to instruct browser to cache your pages. So I still think that the problem is still in the server configuration.