I think that part of the power and challenge of using nginx’s caching is that 
there are many different ways 
of achieving the same or similar results, but some of the approaches will be 
more awkward than others. 

I think that it might help if you could express what the issue is that you are 
trying to solve, 
as opposed to the mechanism that you are wanting to use to solve your problem, 
for example,
“Don’t cache personalized pages” or “don’t cache pages where the user is 
outside the US” or 
“don’t cache pages if the user has logged in” or ...

> On Feb 14, 2018, at 4:44 PM, Friscia, Michael <michael.fris...@yale.edu> 
> wrote:
> 
> Maybe that’s the problem, I want to disable cache if the response header is 
> true but not do anything if it is false. I can change my logic in creating 
> this header to only have it on pages where cache should be disabled if it is 
> not possible to use an IF statement around it. I will post my config here 
> once I get rid of the sensitive things, but the confusing thing is that it 
> worked, then it stopped working. 
> 
> 
> 
> ___________________________________________
> 
> Michael Friscia
> 
> Office of Communications
> Yale School of Medicine
> 
> (203) 737-7932 – office
> (203) 931-5381 – mobile
> 
> http://web.yale.edu
> 
> 
> 
> 
> On 2/14/18, 4:39 PM, "nginx on behalf of webopsx" <nginx-boun...@nginx.org on 
> behalf of nginx-fo...@forum.nginx.org> wrote:
> 
>    Hi,
> 
>    The map is processed on each request and should be very consistent. 
> 
>    I thought you wanted to disable cache on the existence of a response 
> header,
>    not a request header.
> 
>    Otherwise I think we need more information to understand, such as how are
>    you testing? Perhaps paste your full configuration here after removing any
>    sensitive text.
> 
>    Posted at Nginx Forum: 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__forum.nginx.org_read.php-3F2-2C278558-2C278576-23msg-2D278576&d=DwICAg&c=cjytLXgP8ixuoHflwc-poQ&r=wvXEDjvtDPcv7AlldT5UvDx32KXBEM6um_lS023SJrs&m=x0V3h5hp-I18hCxDQuN0U7f_JYUQYISVWlygl1QK-FU&s=sUMR29LFjCI97P-LSb-RwuojlvhtDhvfRiX_YAio19E&e=
> 
>    _______________________________________________
>    nginx mailing list
>    nginx@nginx.org
>    
> https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman.nginx.org_mailman_listinfo_nginx&d=DwICAg&c=cjytLXgP8ixuoHflwc-poQ&r=wvXEDjvtDPcv7AlldT5UvDx32KXBEM6um_lS023SJrs&m=x0V3h5hp-I18hCxDQuN0U7f_JYUQYISVWlygl1QK-FU&s=833NZxJsLHFd1YlQmOtXp22oR4K0OXPS-xz0mYs6r04&e=
> 
> 
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx

Reply via email to