Thanks for you answer. It turned out a monitoring system was doing DNS lookups in the mean time, therefore it appeared that 2 client got the same DNS response.by polder_trash - Nginx Mailing List - English
Alexsamad, I might not have been clear, allow me to try again: * currently 2 NGINX revproxy nodes, 1 active the other on standby in case node 1 fails. * Since I am injecting an authentication header into the request, the HTTPS request has to be offloaded at the node and introduces additional load compared to injecting into non-encrypted requests. * Current peak load ~60 concurrent requestsby polder_trash - Nginx Mailing List - English
Hi, I have been reading the documentation and also searching this forum for a while, but could not find an answer to my question. Currently, I have a 2 NGINX nodes acting as a reverse proxy (in a failover setup using keepalived). The revproxy injects an authentication header, for an online website (transport is https). As the number of users grows, the load on the current machine starts toby polder_trash - Nginx Mailing List - English