$upstream_cache_status

The patch to enable $upstream_cache_status. Possible values:

MISS
EXPIRED expired, request was passed to backend
UPDATING expired, stale response was used due to
proxy/fastcgi_cache_use_stale updating
STALE expired, stale response was used due to
proxy/fastcgi_cache_use_stale
HIT

This is great; looking forward to seeing cache stats in the log.

I apologize I don’t fully understand the updating parameter, and how to
use or when to use it?

Does that mean if active then a stale request will be used, but then
will be updated by nginx?

Thanks,

John

On Wed, Jun 10, 2009 at 10:35:43AM -0500, Resicow wrote:

This is great; looking forward to seeing cache stats in the log.

I apologize I don’t fully understand the updating parameter, and how to
use or when to use it?

Does that mean if active then a stale request will be used, but then
will be updated by nginx?

If a stale cached response is updating by some request, other requests
will
use the stale response.