Forum Discussion
Hi Brad,
Thank you for the quick reply. We have tried that, and the issue is that the cert on the server is set up for subject of DNS: webmail.corp.com which does not resolve to 10.1.1.1. Thus the server rejects the URI, and lets us know 10.1.1.1 is not a valid host name.
This situation is sort of like an SNI monitor but not entirely. I have tried using the EAV SNI monitors on Dev Central but can't format them appropriately for this particular URI. One of the issues is escaping out the & which I just placed the entire URL in quotes but you can also place the & in single quotes '&'. I need to not only be able to specify SNI, Response, and URI, but the Node and port as well.
A side from writing my own EAV for this, I was hoping a standard https monitor could be manipulated to work.
I'm at a loss on how to construct this appropriately.
Cheers,
Don