http socket returning status 0

A user just told me my app stopped working a few weeks back, so I decided to test it myself. The app retrieves a json file with http socket. It keeps getting a status 0 error instead of the 200 code it used to return. I have tried multiple web hosts and the app still gets status code 0 trying to reach any web host I test it with. Any ideas what might be causing this to just start out of nowhere the application hasn’t been changed. Don’t know if a Windows update broke the http socket ( just throwing around ideas )…

I am testing this on WIndows 10 newest patch as of this post. Also the application it was compiled with 2017 R3

Some of the code I am using…

socket1.Secure = True
socket1.SetRequestHeader("Accept", "application/json")
socket1.SetRequestHeader("Content-Type", "application/json; charset=utf-8")
socket1.Yield = true
data = socket1.SendRequest("GET",  "https://www.mywebserver.com/myfile.json", 30)
data = DefineEncoding(data, Encodings.UTF8)

Thanks

is socket1 an httpsocket or httpsecuresocket ?

and you may need to update to using URLConnection so your code uses http/1.1 instead of http/1.0 which is what httpsocket would use
a LOT of web servers will no longer permit http/1.0

@Norman Palardy - Thanks for the reply to its HTTPSecureSocket.

Been away from Xojo for a bit, looking at the docs seems URLConnection came in to being in Xojo 2018 R4, just odd every server just stopped working with the HTTPSecureSocket code at the same time. These apps are freeware, so it looks like the users will be waiting for a while then if it is the http/1.0 issue. Thanks

There was a real rapid shift away from Http/1.0 to 1.1 and this sounds like that symptom

a quick way to tell is to just write a tiny test app that uses url connection to go to the url that httpsocket has issues with
maybe 4 or 5 lines

[quote=473276:@Tony Chamberlain]@Norman Palardy - Thanks for the reply to its HTTPSecureSocket.

Been away from Xojo for a bit, looking at the docs seems URLConnection came in to being in Xojo 2018 R4, just odd every server just stopped working with the HTTPSecureSocket code at the same time. These apps are freeware, so it looks like the users will be waiting for a while then if it is the http/1.0 issue. Thanks[/quote]
You may be able to get away with Xojo.Net.HTTPSocket as well. That was available earlier.