That makes sense. Thanks so much for all your help.by helliax - Nginx Mailing List - English
Thanks for heads up, Maxim. In what cases would it go into an infinite loop if I left it outside? I had thought that "location /" would catch all requests, and setting proxy_intercept_errors off at the last handler would break the chain by returning whatever upstream setC returned?by helliax - Nginx Mailing List - English
I think i got it. I had to add the following directive under the server { } heading: recursive_error_pages on; I'm checking the access logs, and I'm seeing the third one now (ipA : ipB : ipC), and it's also returning the file correctly. I hope this is the right way.by helliax - Nginx Mailing List - English
I currently have a setup where I have 3 upstream sets (directives?), and it will fallback in a chain. So if it gets a 404 from setA, it'll go to setB. If setB also has a 404, then setC. The config is: upstream setA { server ipA:port } upstream setB { server ipB:port } upstream setC { server ipC:port } server { listen 80; server_name localhoby helliax - Nginx Mailing List - English