Ok, thanks for pointing that out. Things are working for me now with an error_page handler for 301s only, so I'll stick with this setup for now. Icoby zappa - Nginx Mailing List - English
Btw, why is it you don't recomment using the error_page method?by zappa - Nginx Mailing List - English
Unfortunately I'm not able to change the behaviour of the upstream servers, these are a closed-source commercial product and come as-is. I'll look into the proxy_redirect to see if I can preserve the server to redirect to in some way, something like a GET argument or cookie. I just found out about the Lua module as well. I'm pretty fluent at Lua so I'll see if the module offers the tools toby zappa - Nginx Mailing List - English
Hello, I'm trying to configure Nginx to access a cluster of application servers using a simple proxy with multiple application servers in the upstream. The application servers use a REST api for object storage and retrieval, and use 301 redirects among the nodes of the cluster for load balancing. A client can connect to server A, then get a redirect to server B, where the request will be handleby zappa - Nginx Mailing List - English
![]() |
![]() |
![]() |
![]() |
![]() |