Re: Regression in 1.14 when following upstream redirects

Hello! On Mon, May 14, 2018 at 01:22:46PM -0400, vedranf wrote: > There is a problem when nginx is configured to try to follow redirects (301) > from upstream server in order to cache responses being directed to, rather > than the short redirect itself. This worked in 1.12 and earlier releases. >

Connection refused

hello list, I have a reverse proxy with nginx front end and I have the backend with nginx some applications in php7 with mariadb, reviewing the log I see a lot of errors like this: 2018/05/09 17:44:58 [error] 14633#14633: *1761 connect() failed (111: Connection refused) while connecting to upstrea

Re: Custom error_page

Ok, I kind of found the answer here http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_intercept_errors then I realized my problem is that I only want to do this for 500,502,503 and 504, I want the upstream server to handle 404 errors on its own. So is there a way to only intercept t

Custom error_page

I’m not sure if I’m using error_page correctly. I’m trying to set this up so that if the upstream server returns a 500, then I show a custom error page. Is this possible? I have a custom error setup that works just fine using the instructions from this site: https://www.digitalocean.com/communit

Regression in 1.14 when following upstream redirects

Hello, There is a problem when nginx is configured to try to follow redirects (301) from upstream server in order to cache responses being directed to, rather than the short redirect itself. This worked in 1.12 and earlier releases. Here is the simplified configuration I use and which used to work

Re: Debugging Nginx Cache Misses: Hitting high number of MISS despite high proxy valid

Quintin, I dont know anything about your context, but your setup looks over simplistic. Here are some things that I learned painfully over a few years of supporting a high traffic retail website 1. Is this a website that's on the internet, and thus exposed to random queries from bots and scra

Re: Debugging Nginx Cache Misses: Hitting high number of MISS despite high proxy valid

I wish I had a lead for you. I’ve never seen that behavoir ___ Michael Friscia Office of Communications Yale School of Medicine (203) 737-7932 - office (203) 931-5381 - mobile http://web.yale.edu From: nginx on behalf of Quintin Par