For several example drivers for quick internal testing we have added xml or json files under the Skyline DataMiner webpages for example:
C:\Skyline DataMiner\Webpages\ProtocolSimulations\SLC SDF\HTTP\2.0.0.1
We used to be able to run elements pointing to 127.0.0.1:80 with a HTTP Session:
<Request verb=”GET” url=”ProtocolSimulations/SLC SDF/HTTP/1.0.0.1/data.xml”>
This would then successfully return data. This has stopped working in the last few months.
(perhaps related to the http to https change?)
-> 16:27:19 – Get for statusCode () had error : Error : 12029. [ERROR_WINHTTP_CANNOT_CONNECT]
-> 16:27:19 – Continuing get for statusCode ()
-> 16:27:19 – Get for xmlResponseContent () had error : Error : 12029. [ERROR_WINHTTP_CANNOT_CONNECT]
-> 16:27:19 – Continuing get for xmlResponseContent ()
Error : 12029. [ERROR_WINHTTP_CANNOT_CONNECT]
The pages are accessible through a regular browser.
We tried changing 127.0.0.1 to localhost or to the exact PC name to no effect.
We tried with and without bypassproxy.
I’ve had one other colleague on the most recent feature release with the same problem.
Is anyone else experiencing these issues or does anyone know a workaround to get this working again?
Have you tried with the https port 443?
Last time I used it was with “localhost” and port “443” and this works.
Hi Jan,
This might be due to the enhanced security enforced by the ISAPI filter configured in IIS.
If this is just for testing/debugging purposes, I believe you could temporarily disable this in iis.
127.0.0.1 and changing port 80 in to 443 did the trick.
It looks like since the last security changes it’s impossible to use the HTTP (80) in my scenario except by configuration work to IIS.
Thanks!