topic The URL of Mobile App to be the same as URL of Cluster Active Gate in Real User Monitoring

The URL of Mobile App to be the same as URL of Cluster Active Gate

waikeat_chan — Mon, 13 Dec 2021 11:17:21 GMT

If my Cluster AG has the same URL as the URL of mobile application, would it cause any trouble?

Said, for example, the endpoints of the mobile app is on server X, which the URL is https://abcde.com.th:443

Then I have the Cluster AG (server Y) that is on URL https://abcde.com.th:443/e/5226f693-a9b4-4cf6-83df-701985a8a389

Would this cause trouble? The DNS are able to resolve abcde.com.th to both IP of server X and IP of server Y.

Best Regards,

Wai Keat

Re: The URL of Mobile App to be the same as URL of Cluster Active Gate

skrystosik — Mon, 11 Mar 2019 08:25:07 GMT

Cluster Active Gate is receiving incoming requests on port 9999. So theoretically it should work like this (if you have control on DNS configurations). But it this AG will have more functions in the future it will be good to consider new domain (to not do a mess with naming :))

Sebastian

Re: The URL of Mobile App to be the same as URL of Cluster Active Gate

Julius_Loman — Mon, 11 Mar 2019 08:31:23 GMT

You have to set the cluster activegate URL to the URL accessible from mobile devices. This heavily depends on your network architecture (load balancers / application gateways between cluster activegate and the client), so it's difficult to suggest a proper solution without knowing your environment.

Re: The URL of Mobile App to be the same as URL of Cluster Active Gate

waikeat_chan — Mon, 11 Mar 2019 08:39:38 GMT

Yup, we would change the listening port from default 9999 to 443.
As for the consideration of enabling more benefits of Cluster AG, that's a good point, thanks Sebastian.