I am now working on a client that has IE9 as the default browser and also Chrome installed. When I navigate to that page manually via either IE9 or Chrome the page loads with now problems, however when I fire up eValid (now using the default IE9 browser) the page fails with an 'object not supported' error. This also happens when I set eValid to start as a Chrome agent.
I have checked with our architect and he reckons eValid is not coming through as the right browser in this instance as they have code to detect IE9 or whatever and then send the xml in a different format. I have tested this theory by browsing to http://www.useragentstring.com after starting eValid and according to that it is definitely connecting as IE9 or whatever I command eValid to start up as.
So could you please explain to me again how this mechanism works as I need to argue this statement in the upcoming debate tommorrow with the architect.