Could you give a little more information on what you are trying to do?
Sure. I was trying to use jQuery to do an AJAX request to our Solarwinds server. The server is in a different domain, so JSON runs into the same origin policy. JSONP would get around this (I only need to do get requests for this application) but Solarwinds doesn't speak JSONP.
Using JSONP though, I can see that my HTTP request is formatted properly because I can see the expected response in the response header using Chrome dev tools.
So what I was looking to do was to add the "access-control-allow-origin * " line to the IIS web.config on the Solarwinds server, but when I do, it renders the solarwinds web interface inoperable until I remove the line.
The ultimate goal was just to create way to include basic information from Solarwinds within another application. I was hoping for an all client-side solution, but I couldn't get past this issue, unfortunately.
That helps. So in this scenario, there are three relevant servers:
1. The Orion web server. ASP.NET, IIS. Typically on port 80.
2. The Information Service. Running on the same server as #1, but not in IIS. It's hosted by SolarWinds.InformationService.ServiceV3.exe and the REST API is on port 17778. This API is implemented using WCF's WebHttpBinding.
3. Your own application server.
Can you write a simple server-side proxy (to run on #3) for the SolarWinds REST API? That would work around this problem.
That was kind of the conclusion I came to. I'm in the process of figuring out a server-side proxy, as I've never had to do one of those before.
Thanks for the feedback!