Mercurial > hg > nginx
comparison src/http/ngx_http_file_cache.c @ 5992:174512857ccf
Cache: do not inherit last_modified and etag from stale response.
When replacing a stale cache entry, its last_modified and etag could be
inherited from the old entry if the response code is not 200 or 206. Moreover,
etag could be inherited with any response code if it's missing in the new
response. As a result, the cache entry is left with invalid last_modified or
etag which could lead to broken revalidation.
For example, when a file is deleted from backend, its last_modified is copied to
the new 404 cache entry and is used later for revalidation. Once the old file
appears again with its original timestamp, revalidation succeeds and the cached
404 response is sent to client instead of the file.
The problem appeared with etags in 44b9ab7752e3 (1.7.3) and affected
last_modified in 1573fc7875fa (1.7.9).
author | Roman Arutyunyan <arut@nginx.com> |
---|---|
date | Mon, 02 Mar 2015 19:47:13 +0300 |
parents | 3f568dd68af1 |
children | 1fdba317ee6d |
comparison
equal
deleted
inserted
replaced
5991:435ee290c2e1 | 5992:174512857ccf |
---|---|
179 | 179 |
180 r->cache = c; | 180 r->cache = c; |
181 c->file.log = r->connection->log; | 181 c->file.log = r->connection->log; |
182 c->file.fd = NGX_INVALID_FILE; | 182 c->file.fd = NGX_INVALID_FILE; |
183 | 183 |
184 c->last_modified = -1; | |
185 | |
186 return NGX_OK; | 184 return NGX_OK; |
187 } | 185 } |
188 | 186 |
189 | 187 |
190 ngx_int_t | 188 ngx_int_t |