When testing a virtual host on a newly installed Access Gateway, we are sent to www.ca.com instead of the expected login page. As this configuration has been copied from a working system, we're unsure why it is not working the same as in the other environment.
The host name used in the testing was resolving to a load balancer IP address. We don't know where the load balancer was sending our requests, but it was not to the Access Gateway we were troubleshooting as the requests never showed up in the agent trace log for the virtual host being tested.
When we updated the local HOSTS file on the client machine to point the test host name to the Access Gateway IP instead of the load balancer, our requests began working as expected and showing in the expected logs. Load balancer team will need to check and update their configuration to point to the correct hosts.