Hi All,

Has there been any consideration of providing a configuration directive with the same effect as Apache's CacheStorePrivate directive for reverse proxy caching, such as fastcgi_cache?

http://httpd.apache.org/docs/2.4/mod/mod_cache.html#cachestoreprivate

"Ordinarily, responses with Cache-Control: private header values will not be stored in the cache. The CacheStorePrivate directive allows this behavior to be overridden. CacheStorePrivate On tells the server to attempt to cache the resource even if it contains private header values. Resources requiring authorization will never be cached."

My use case: I have an API which always returns "Cache-Control: private" because the responses contain user data. But, this reverse proxy cache is sitting on my own network, so I consider it to be private. I just don't want any interim caches between my infrastructure and the user's browser to cache the results.

Thoughts? Or anyone have any work-around recommendations?

Maybe use 'map' to determine which responses to cache and which not?

---
nginx for Windows http://nginx-win.ecsds.eu/

I don't understand your suggestion. How would map allow me to override Nginx regarding private responses? AFAIK, Nginx will not store any content that has a "Cache-Control: private" header in the response, and there's no way to tell it to do so.

Then maybe with Lua you could capture the response and change it accordingly.

---
nginx for Windows http://nginx-win.ecsds.eu/