Thanks for the suggestion. I will consider using the URI instead.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,262527,262530#msg-262530
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello trungaczne,
In your case this is expected behavior. This is because the
$upstream_http_content_type exist only when the upstream already started to
return response to the nginx box. But nginx should determine the caching
policy for current request before any connection to the upstream will
Using "proxy_cache" directive with a variable seems to change that
variable's value.
Tested against a fresh install of nginx 1.9.6 (default configure parameters)
on 2 different Ubuntu:14.04 hosts. DigitalOcean droplets.
The following configuration works as expected: It returns 0/1/2 depending on