Some backround info for context..
I'm writing a simple weather forecast reader in JS which makes use of multiple APIs for determining location data and then forecast data based on that location.
For US cities, the weather.gov API takes a specified latitude and longitude as URL parameters, and gives you a forecast URL for that area. Since the average person walking around typically doesn't have latitude and longitude coordinates commited to memory, I decided to use another API, geocode.maps.co, to return the latitude and longitude for a specified city.
I have all of this working. However whenever I make the HTTPRequest call to geocode.maps.co, SBBS logs TLS errors to error.log like this one:
term 33736 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
This happens on *successful* HTTPRequest calls to this API. The HTTPRequest is getting the response from the API containing the json data for the specified input, but it's logging a TLS error at the same time. The calls are placed in a try/catch block, but the catch does not get hit in this scenario.
To the user, it appears nothing is wrong whatsoever. But to me, I see TLS errors logged every time someone uses the functionality to query location data. None of the other APIs I'm using are leading to this outcome; just this one.
Which leads me to my question: is there a way I can suppress those TLS errors, or am I stuck with them cluttering the error.log file?
For the moment, yeah, but I'm sure there's a solution.
|New York, USA
|13 (0 / 13)