> Why would you manipulate nginx cache files from php directly (or even if you do so why not run the nginx and phpfpm under same user then)?

Yeah... For example: with php-fpm you can run each site with its own uid/gid (pool configuration), and with address on which to accept FastCGI requests
So, create a new pool file with the right user:group ... and send the specific purge request.

-----Original Message-----
From: nginx [mailto:nginx-bounces@nginx.org] On Behalf Of Reinis Rozitis
Sent: Thursday, March 9, 2017 8:24 PM
To: nginx@nginx.org
Subject: RE: RE: Fastcgi_cache permissions

> thanks for the reply. The use case that I have is when php-fpm is
> running as a user different than the nginx one. In this case the
> permissions being set as 0700 basically deny any manipulation of the
> cached files from php scripts. Everytime you try something like this you get permission denied.

Why would you manipulate nginx cache files from php directly (or even if you do so why not run the nginx and phpfpm under same user then)?

If you want to purge the request (only valid reason which comes to my mind) you should configure fastcgi_cache_purge ( http://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_cache_purge ). The drawback is that's only for the commercial version.

As an alternative you could use a third party module http://labs.frickle.com/nginx_ngx_cache_purge/
I'm not 100% sure about the compability with the newest nginx releases but you can contact the author about that (he is also in this list).

rr

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx