I'm trying to understand if either of these options is technically feasible for an options paper.Cache and cookies go hand-in-hand when it comes to web browsing. I cannot find a way of using Javascript to implement either solution. My problem is if the IP address allocated from the HGTM expires (15 minute TTL) mid customer session the browser can & should query the GTM again for the IP address, the GTM can easily allocate out an IP for the alternative data centre breaking session affinity as LTMs in each are only aware of application nodes in the same data centre.Ĭan I use Javascript to force the browser to query the GTM at the start of the customer session, ensuring that as long as the customer session finishes in 15 minutes there will be no chance of a data centre switch mid-session.Ĭould I use Javascript to stop the browser doing a DNS look-up inside a customer session & just do the look-up in between customer sessions? The F5 LTM will use the jsession cookie to implement session affinity. In each data centre, an F5 Local Traffic Manager (LTM) will balance load across the web application nodes. There is no way to implement session affinity in the GTM. The IP address it allocates will have a Time To Live (TTL). It will allocate an IP address in a round-robin way so long as it knows the F5 LTMs (red arrows GTM to LTM) are responding as available.

An F5 Global Traffic Manager (GTM) acts as a glorified DNS, it's job is to allocate an IP for either data centre (red arrow browser to GTM). The web application will be split across two data centres. The web application is used to service customers. I am writing a web application that runs in a private network using Microsoft Edge as the browser.

Clear microsoft edge cache