In first release cache will cache upstream responses on disk.
Will we be able to disable this (or enable it, depending on how you look
at it) on a “location” by “location” block basis? For some of our
dynamic content serving cached data would break the client so we’d
definitely not want it to cache (despite our cache headers that
specifically tell the browser to cache it - because its ok for the
browser to cache what we dynamically send it - but NOT for nginx to send
the same response back to other browsers). Yet for other content
(location matches) we would likely want to use this.
Thanks!
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
On Sun, May 04, 2008 at 12:39:34PM -0700, Rt Ibmer wrote:
In first release cache will cache upstream responses on disk.
Will we be able to disable this (or enable it, depending on how you look at it) on a “location” by “location” block basis? For some of our dynamic content serving cached data would break the client so we’d definitely not want it to cache (despite our cache headers that specifically tell the browser to cache it - because its ok for the browser to cache what we dynamically send it - but NOT for nginx to send the same response back to other browsers). Yet for other content (location matches) we would likely want to use this.
Yes, of course, the most directives can be set on http, server, and
location levels.
Igor S. wrote:
On Sun, May 04, 2008 at 12:39:34PM -0700, Rt Ibmer wrote:
In first release cache will cache upstream responses on disk.
Will there be a memory cache as well?