Recently I got a call from a customer who had issues with a new UAG deployment in a existing environment.
The problem they faced was: HTTP 400 Error
According to the Omnissa Documentation, the Changes in Host Header Validation could be a valid point to start.
But…
The host Header Validation looks good… domain name filled in, ip-address filled in… no issue here (but?)
When we go to the command line interface, we do a : adminreset –allowedHostHeader uag1.example.com,uag-lb.example.com
And what happens next, the interface says : updated [NULL}, to uag1.example.com,uag-lb.example.com
So for some reason, the information in the backend of the UAG is corrupted or something, representing the data in de UAG but not working resulting in a HTTP 400 error.
I think this has to do in my situation the host was not in FQDN!
So whenever this issue occurs, please try to update the allowd hosts headers through the commandline to verify if the information is correct!