you need to purge the private cache copy if it still valid. document is updated accordingly.

Click to expand...

Question 1: how do you purge the private cache copy?
Question 2: how exactly does the EnableCache/DisableCache directives work with regard to .htaccess? Obviously it does not work to disable it through .htaccess if it is enabled globally, but it does not work to enable it through .htaccess if it is globally disabled either? Could need some clarification here.

Sorry for reply late. today have time to test with private cache following this thread.

>Question 1: how do you purge the private cache copy?
same way to purge public cache. both public and private cache have a common cache root.
the easy way to purge cache is
1)delete all sub folders / files under cache root
2)assume cache folder is /lswscache, minimum cache time is 3 minutes
#find /lswscache -type f -mmin +3 -delete
will delete all caches which modified(updated) 3 minutes ago.

>but it does not work to enable it through .htaccess if it is globally disabled either? Could need some clarification here.
did tests --- can enable private cache for particular URL if disabled globally.

Sorry for reply late. today have time to test with private cache following this thread.

>Question 1: how do you purge the private cache copy?
same way to purge public cache. both public and private cache have a common cache root.
the easy way to purge cache is
1)delete all sub folders / files under cache root
2)assume cache folder is /lswscache, minimum cache time is 3 minutes
#find /lswscache -type f -mmin +3 -delete
will delete all caches which modified(updated) 3 minutes ago.

>but it does not work to enable it through .htaccess if it is globally disabled either? Could need some clarification here.
did tests --- can enable private cache for particular URL if disabled globally.

Click to expand...

So what you are saying is that you can have all cache disabled globally in config, and still enable it for particular url/site through CacheEnable private in .htaccess? In other words, the .htaccess overrides only works to enable a globally disabled cache, but not the other way around?