[BUG] (Maybe?) Issue With HTTP GET Timeout & connectivity Check

aidanmacgregor

New member
So I am trying to set up internet connection detection, trying to determine if I am connected to a specific public WiFi network (BT WiFI UK)
There are 2 ways to load the login page with"
https://btwifi.com:8443" And "https://192.168.23.21:8443"

The "BT WiFi" URL works in Connectivity Check & HTTP GET

The ”192.168.23.21:8443" works only in HTTP GET (Suspect this is due to no DNS record on non BT DNS servers OR SSL Error)

HTTP GET returns this error when not connected to a BT WiFi Hotspot (as expected but the timeout is 10000 ms when only set as 1 second timeout,

So is it possible to use connectivity check on the IP even with SSL or DNS error?

OR is it possible to correct the timeout for the HTTP Response?
 

aidanmacgregor

New member
Ok so the soloution it seems (i wasnt sure if to would work this way) but using the BT WiFi URL still works with diffrent DNS, not sure if I will use this as it may add a few seconds of latency to logging in, Will need to test

still wondering about the timeout option being ignored in HTTP Request :)
 
Top