ahh!
> At the time that nginx is deciding "should this request be served from
> cache or sent to upstream?", $upstream_http_content_type cannot have
> a value.
>
now I figured out the reason. thank you Francis.
___
nginx mailing list
nginx@nginx.org
htt
On Fri, Nov 30, 2018 at 11:32:39AM -0200, Jorge Pereira wrote:
Hi there,
> I sent the wrong snip. the correct is using
> $upstream_http_content_type as can be seen below. basically, always
$upstream_http_content_type is the http Content-Type header sent by
upstream in response to the request fro
Hi Francis,
I sent the wrong snip. the correct is using
$upstream_http_content_type as can be seen below. basically, always
when I use "proxy_cache_bypass $no_cache;" that impact the value of
"map $upstream_http_content_type $no_cache" I didn't understand
what is the reason. thanks for any su
On Thu, Nov 29, 2018 at 09:51:13PM -0200, Jorge Pereira wrote:
Hi there,
> I am using the nginx/1.12.0 and I am trying to use the below config.
> but, the below "map" by "$upstream_http_content_type" is always
> matching with default value "1". but, if I remove "proxy_cache_bypass"
> then the map
Hi,
I am using the nginx/1.12.0 and I am trying to use the below config.
but, the below "map" by "$upstream_http_content_type" is always
matching with default value "1". but, if I remove "proxy_cache_bypass"
then the map it works. therefore, I need the "proxy_cache_bypass "
capability.
http {
i