Hi Maxim, Thank you for all your help. James.by o456092@rtrtr.com - Nginx Mailing List - Russian
Hi Maxim, Thank you for all your help and showing an alternative way to resolve the problem.by o456092@rtrtr.com - Nginx Mailing List - Russian
Hi Maxim, I have just tried - and it works - though more questions raise, how is the round-robin working (though, since I am using cache, I am not too concerned) Also, is there a limit to the number of maximum upstream servers within the block - from the documentation I don't see any indicative of having limits - but this is something I wont have to worry for a long time. nginx.confby o456092@rtrtr.com - Nginx Mailing List - Russian
Hi Maxim, Thanks for pointing this out. You mentioned using: proxy_next_upstream, rather than my current strategy - would you happen to know if this has any limitations? Will this serve the same purpose as the current configuration that I have? Would it perform, better, worse, or the same? Thank you, James.by o456092@rtrtr.com - Nginx Mailing List - Russian
Hi, I have configured NGINX as an HTTP Asset locator, where the assets might found through a series of recursive errors by sequentially a series of different webservers. The problem that "I think" I have ran into, is that NGINX's recursive_error_pages is limited to a depth 11 servers, thus 11 errors 404 or 500 errors- is this a fact? Interesting enough I get a 500 internal server erroby o456092@rtrtr.com - Nginx Mailing List - Russian
Hi, I have configured NGINX as an HTTP Asset locator, where the assets are found through a series of recursive errors. The problem that "I think" I have ran into, is that NGINX's recursive_error_pages is limited to a depth 11 - is this a fact? upstream loc1 { server srv1:8080; } ... upstream loc50 { server srv50:8080; } serverby o456092@rtrtr.com - How to...