I posted and idea last week to Ideas and Feature Requests: "Finer grained control on caching" (http://forum.nginx.org/read.php?10,217748), but since I'm new to this forum/mailing list I have no idea if anybody saw this. I want to find out if this is an acceptable feature request and if anybody else sees the benefits of this. Short summary: Add a new directive fastcgi_cache_key_sufby attiks - Nginx Mailing List - English
This are getting more complicated since we're also caching by $device (detection done by nginx, based on UA) like this: fastcgi_cache_key "$device$host$key_uri$cookie_OctopusCacheID" but now it's completely impossible to clear the cache for all 'devices' If we could use (the yet to be implemented/accepted) fastcgi_cache_key_suffix we could rewrite it as: fastcgi_cache_key_suffby attiks - Ideas and Feature Requests
I had a closer look to the source of nginx, we probably need a variant for ngx_delete_file that supports wildcardsby attiks - Ideas and Feature Requests
We are using cache for anonymous users and authenticated users, this is done by settings a cookie for authenticated users and using a fastcgi_cache_key like this: fastcgi_cache_key "$host$key_uri$cookie_OctopusCacheID"; The problem is that we are not able to clear the cache for both anonymous users and authenticated users (using ngx_cache_purge), we can clear the cache for anonymous userby attiks - Ideas and Feature Requests