ReadUrl not working correctly

[neil9090]

I don't think it's my machine, but you never know, I am getting a problem with the ReadUrl function

Tried 15.50.0206 beta
::msg readurl("https://my-pc.test/test.txt") // errors with URL not found (works in chrome) HTTPS issue
::msg readurl("http://my-pc.test/test.txt") // works with http

Also;
::msg readurl("http://my-pc/test.txt") // fails <no dot/domain name>
::msg readurl("http://my-pc.test/test.txt") // works
// hosts file adjusted
// 192.168.0.9 my-pc.test

::msg readurl("http://my-pc.local/test.txt") // worked (no adjustment to hosts file)
::msg readurl("https://my-pc.local/test.txt") // fails with url not found HTTPS issue

::msg readurl("http://192.168.0.9/test.txt") // works
::msg readurl("https://192.168.0.9/test.txt") // fails

::msg readurl("https://keep.google.com/") // works

it might be my machine, as when I ping my machine I get a response which is ip6 format, even though the ip 6 is not set for the adapter.

Not sure if it might be something to do with a self signed certificate IIS7 + Windows 7
Chome Messages if I use https://192.168.0.9
The security certificate presented by this website was not issued by a trusted certificate authority.
The security certificate presented by this website was issued for a different website's address.

If I use IE with the server name (not ipaddress)
The security certificate presented by this website was not issued by a trusted certificate authority.

I seem to have two problems,
1) if domain is missing from url request on http request it fails
2) if domain is missing from url request on https request fails, but also fails with local domain/network (or self certificate failure that is valid)

[admin]

Those URLs do not exist acc. to Firefox.

[neil9090]

Those URLs do not exist acc. to Firefox.

Strange, after some windows updates, a reboot and adding ipaddress to hosts file this appears to have resolved it;
strange one, will take it out of the hosts file in a few days...

::msg readurl("https://my-pc/test.txt")
// works now!!

[highend]

Apart from a probably non valid https certificate that just sounds like name resolving problems...

[neil9090]

Apart from a probably non valid https certificate that just sounds like name resolving problems...

Ok looks like the problem was of my own making, I was using a ad blocking application that adjusts the IE proxy setting thus XY was connecting probably via this proxy thus it couldn't see either https or local domain name resolutions.

I knew it was my machine, just stumbled on the issue again after a reboot, just thought I would try IE as Chrome was happy with the URL, IE didn't like it just like XY, so I turned off the ad blocking app, and low and behold it sorted it..

Thanks admin, highend