Show all posts by user
Need help setting up WordPress? Using cgi? Something else? Post it here.
Re: Reverse proxy: allow only one client - 5 months ago
I got something very close but wasn't sure how to reliably release the association (i.e., hook into a connection closed type of event). Anyway, I think this is much more easily solved further upstream by getting rid of the load balancer and assigning nginx proxies to clients dynamically in the main proxy.by petsneakers - How to...
Re: Reverse proxy: allow only one client - 5 months ago
My use case could be satisfied by something like - If a client makes an upgrade request - Check if there is already an established websocket connection upstream - And if so, return a 503 (I get this would allow multiple clients to make non-websocket requests, that's okay in my case.) Is this something that njs scripting can tackle? Just learning about that now . . . maybe use the filesby petsneakers - How to...
Re: Reverse proxy: allow only one client - 5 months ago
Same question with an incorrect answer: https://stackoverflow.com/questions/75471275/nginx-limit-number-of-ips-connected-to-serverby petsneakers - How to...
Reverse proxy: allow only one client - 5 months ago
This may sound like an odd request :-) Is there a configuration that would limit the number of clients connecting to an nginx reverse proxy to 1? Note: - clients are connecting through a load balancer, the reverse proxy will have access to the client ip address via the `X-Forwarded-For` header. - number of connections should not be limited, just that there should be one originating IP addrby petsneakers - How to...
 |
 |
 |
 |
|