Purge Entire Cache action uses wrong purge method

[akansc]

The module seems to have 2 purge modes:

The GET PURGE/url method works fine when saving single posts and whatnot, however, the the "Purge Entire Cache" seem to execute the unlink_recursive function which of course fails on a shared hosting server due to insufficient permissions.

Allowing shared hosting users to reach and manipulate the global fcgi cache is not an option and would be considered as a security issue.

The PURGE/* wildcard is supported since the 2.4 that was released in 2016, that would still work with all your nginx examples:
https://github.com/nginx-modules/ngx_cache_purge/releases

[qcybb]

@gagan0123

I was disappointed to see this wasn't included in the latest update. I'm also effected by the issue above.

Are there any plans to add the PURGE/* now this it's supported?

https://github.com/nginx-modules/ngx_cache_purge/releases/tag/2.4