Great. Thanks. Much appreciated.by msingla - Nginx Mailing List - English
Thanks for the code. This seems to solve the problem. Is this change safe for production? Is it possible that this change will break something else? Is it possible to include it in a future release/patch? Thanksby msingla - Nginx Mailing List - English
Is it possible to support use of variable to point to an upstream while using fastcgi_pass? Currently, something like following does not work and throws "no port in upstream" error. Replacing the variable with the name of upstream directly works as expected. upstream xyz_backend { server 192.168.56.102:9000; server 192.168.56.103:9000; } server{ ..... set $var_backendby msingla - Ideas and Feature Requests
Looks like the links I posted are about using variables in fastcgi_pass directive for hostname or socket, not for upstream name. When I tried similar configuration, I got "no port in upstream" error in log.by msingla - Nginx Mailing List - English
Also found another one with a bug reported and fixed against that patch. http://web.archiveorange.com/archive/v/yKUXMz3KPVtsrCYTvFzIby msingla - Nginx Mailing List - English
I am also interested in this functionality. It seems like this feature was included at some point. Look at this thread from 2008. http://nginx.org/pipermail/nginx/2008-December/008751.htmlby msingla - Nginx Mailing List - English