hi all.. I am trying to configure a reverse proxy which redirects a URL of the form: https://mydomain.com/myapp/abcd/... to: http://myapp:5100/abcd/... with DNS resolution of "myapp" to an IP address at runtime. My current configuration file is: server{ listen 80 default_server; server_name mydomain.com; return 301 https://www.mydomain.com$request_uri; }by squonk - Nginx Mailing List - English
hi all.. I am trying to configure a reverse proxy which redirects a URL of the form: https://mydomain.com/myapp/abcd/... to: http://myapp:5100/abcd/... with DNS resolution of "myapp" to an IP address at runtime. My current configuration file is: server{ listen 80 default_server; server_name mydomain.com; return 301 https://www.mydomain.com$request_uri; }by squonk - How to...
I think i underatand a bit better now. The tree is storing metadata for potentially multiple upstream groups per generation. It seems like a reasonable implementation given the expected short duration of threads referencing data from older generations (hence a shallow tree) and the fact there is only one read from the tree per request. Anyway.. i asked the question so i'll fill in what i find outby squonk - Nginx Mailing List - English
hi.. Just wanted to ensure my understanding of rbtree usage in Grzegorz Nosek's upstream fair load balancer is correct. I believe the rbtree is necessary because when nginx.conf is reloaded workers may continue to reference upstream server metadata from earlier versions aka generations of the nginx.conf file. The rbtree stores the metadata until none of the workers reference it. The extra complby squonk - Nginx Mailing List - English