great, because it was never meant to work.

It seems stream doesn't support sticky route

http protocol != tcp/udp

With http , nginx running normal

I'm configuring reverse proxy for stunnel vpn

I did the same with ipvs a year ago.

I'm using nginx plus

https://www.nginx.com/blog/nginx-plus-r15-released/#state-sharing

http://nginx.org/en/docs/stream/ngx_stream_zone_sync_module.html
https://docs.nginx.com/nginx/admin-guide/high-availability/zone_sync/
or just parsing http header via njs (js_preload & rebalancing)

The ngx_stream_zone_sync_module module (1.13.8) provides the necessary support for synchronizing contents of shared memory zones between nodes of a cluster. To enable synchronization for a particular zone, a corresponding module must support this feature. Currently, it is possible to synchronize HTTP sticky sessions, information about excessive HTTP requests, and key-value pairs both in http and stream.

Ok, with stream we can use hash loadbalancing method

всем привет. подскажите нжинкс умеет закрывать редирект авторизацией?

     location / {
    rewrite ^/(.*)$ http://example.com permanent;
        try_files $uri $uri/ =404;
        auth_basic "Restricted Content";
        auth_basic_user_file /etc/nginx/.htpasswd;
    }

сейчас отрабатывает 301 и все. суть задачи хочу прикрыть редирект

логично

rewrite phase раньше идёт

делай через проксирование сам на себя

Hello

I config upstream server with backup parameter