$upstream_cache_status is EXPIRED?

CJ Ess zxcvbn4038 at gmail.com
Thu Sep 24 18:16:05 UTC 2015


I'm experimenting with fastcgi caching - I've added $upstream_cache_status
to the access log, and I can see that periodically there will be a small
cluster of EXPIRED requests for an object.

Does EXPIRED imply that the object was fetched from origin each time?
..or that the requests were queued while a request to origin was made?
..or that the expired object was served while an update was fetched?
..or something else?

I can understand any of those cases, I just want to be able to explain how
many origin fetches were actually done.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20150924/3c435a11/attachment.html>

More information about the nginx mailing list