You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The big issue with Purging the proxy cache or fastcgi cache is that the caches are stored by the nginx worker process that run as nobody and all go in one place and the cPanel UI run as the user ..so the cPanel plugin wont be able to write to or delete the cache. even there is no separation between the files for each domain ..its all some a/b/xxxxxxx files owned by nobody etc. The only real solution is to use the PURGE method https://stackoverflow.com/questions/25857508/what-is-the-http-method-purge and this requires lot of support from application too . Even for the redis cache there is no purge per user unless the plugin nginx helper is used which selectively purge .
As root we can always rm -rf proxycache_dir/* and FLUSHALL/FLUSHDB in redis
Just need to think how to get this done right with such obstructions
Many clients have requested a 'purge cache' option, which would need to be applied to both nginx proxy caches and redis cache.
The text was updated successfully, but these errors were encountered: