One of our clients receives this error when attempting to access our app. The error message is:
"You attempted to reach
xxx.foo.com, but instead you actually reached a server identifying itself as
yyy.bar.com. This may be caused by a misconfiguration on the server or by something more serious ... "
The only request in our application that goes to
I have been unable to duplicate this issue locally, and no other users are reporting this issue. I'm convinced it is a setting on the client's machine, but after trolling around in Chrome's content settings/certificate management pages, I am unable to figure out what might be causing this to only happen to one specific client.
(Note, all of the client's machines are affected. Maybe its some antivirus configuration, or a problem with their router?)