Closed AllenEllis closed 4 years ago
Well, now this one works. I guess it is nice that the code is resilient - I watched it notice the corrupt data and request it again. So perhaps this is a legitimate error and people should just try again later?
I notice plenty of people experiencing it in the logs though. Will attempt to look through the logs for another example.
Now I'm inclined to think that this is exactly what the error indicates: DataUSA is having a hiccup and the only recourse is to try later.
I was online last light when a bunch of people were getting this error - I was too, and even from other servers and home IP address. Not a single error of this since last night, so unless there's an indication that my code is at fault, I'm going to call this a server problem at their end and close it.
I assumed this error would only appear if DataUSA was overloaded with requests. Someone reported that it can be consistently reproduced by searching for "Inman, SC"
https://everysinglemonth.org/index.php?action=process&city_name=Inman%2C+SC&city=16000US4535755