Yes - GSLB site persistence is still required, even if you use 307 redirects from UAGs. The 307 redirect does not replace GSLB site persistence; it solves a different problem.
Even when using 307 redirect headers from UAGs, GSLB site persistence is still required. The 307 redirect ensures application-level session pinning, while GSLB persistence ensures DNS-level site consistency. Without GSLB site persistence, clients may be redirected back to a different site on subsequent DNS lookups, causing session instability.
-------------------------------------------
Original Message:
Sent: Jun 05, 2025 02:38 AM
From: alex-tyatyukhin
Subject: NSX ALB. GSLB site persistence + 307 redirect headers
Hi all,
I'm just planning to load balance my horizon infra and have a question about GSLB site persistence + 307 redirect headers.
I have two datacenters and want to build active/active VDI infra with single namespace.
Without enabling 307 redirect headers from UAGs GSLB site persistence is strongly recommended to be used.
But what if I use 307 redirect headers from UAGs? Each of UAGs sends its own 307 redirect header to clients (site1.company.com:portX or site2.company.com:portX) GSLB site persistence is still required?