fredrik.widlund at qbrick.com
Wed Feb 24 12:20:16 MSK 2010
Explicitly purging the cache would not work in this scenario though.
Why is this not doable? I'm even considering adding support for this myself into Nginx, since we really need it and also since it seemed kind of natural?
This could of course be an optional feature, but it would be interesting to know what this breaks?
From: merlin corey [mailto:merlincorey at dc949.org]
Sent: den 24 februari 2010 02:36
To: nginx at nginx.org
Subject: Re: reverse proxy_
On Tue, Feb 16, 2010 at 8:07 AM, Fredrik Widlund
<fredrik.widlund at qbrick.com> wrote:
> Hi Maxim,
> Thanks for the answer! Are there currently any plans to add support for this in the near future?
> Kind regards,
> Fredrik Widlund
It's not really doable as far as I understand things, at least not in
a general, portable way that satisfies all backends.
What you CAN do is you use ngx_cache_purge to have the backend inform
nginx when content has changed. This is the only method that is
general enough for any backend, but it of course requires you to do
nginx mailing list
nginx at nginx.org
More information about the nginx