Nginx doesn't honor Cache-Control: no-cache _request_
is at rambler-co.ru
Mon Aug 3 16:34:39 MSD 2009
On Mon, Aug 03, 2009 at 02:28:56PM +0200, Miros??aw Jaworski wrote:
> On Mon, 2009-08-03 at 15:17 +0400, Igor Sysoev wrote:
> > No, currently nginx ignores the reload because everyone may flush
> > popular and heavy generated pages from your cache.
> > I plan to allow reload only from limited set of addresses.
> Cache-control: no-cache request isn't supposed to revalidate/invalidate
> Logic is fairly trivial - exactly as i showed in my nonexisting
> variable/wrong syntax example - nginx should simply omit checking
> the cache when receiving such request, go for the backend and serve
> backend's response without doing anything to the cache.
RFC does not say that server must not cache this response, it just says
that is must bot use previously cached response.
Anyway, "Cache-control" should be supported from trusted addresses only:
nginx is not generic transit proxy, it's accelerator, it's just part
More information about the nginx