I've been trying to understand why this API call to Open-Meteo fails with HTTPRequest, even though the same URL succeeds in a browser window as well as curl'ing from the command prompt.

load("http.js");
const url = "https://geocoding-api.open-meteo.com/v1/search?name=Canton&format=json";
const req = new HTTPRequest();
var response = req.Get(url);


Result:

!JavaScript http.js line 147: Error: Unable to read status


And this gets logged to the Terminal Server:

TLS ERROR 'Received TLS alert message: Internal error' (-15) setting attribute 6001
TLS ERROR 'Received TLS alert message: Internal error' (-15) setting session active

|15 þ ù ú codefenix ú ù ú ConstructiveChaos BBS ú ú ù þ þ
|08 þ þ ù (https/telnet/ssh)://conchaos.synchro.net ú ù þ
|07
---
þ Synchronet þ -=[ ConstructiveChaos BBS | conchaos.synchro.net ]=-

Re: HTTPRequest Error: Unable to read status
By: Codefenix to All on Tue Aug 05 2025 04:33 pm

I've been trying to understand why this API call to Open-Meteo fails with HTTPRequest, even though the same URL succeeds in a browser window as well as curl'ing from the command prompt.

load("http.js");
const url = "https://geocoding-api.open-meteo.com/v1/search?name=Canton&format=json"; const req = new HTTPRequest();
var response = req.Get(url);

Result:

!JavaScript http.js line 147: Error: Unable to read status

And this gets logged to the Terminal Server:

TLS ERROR 'Received TLS alert message: Internal error' (-15) setting attribute 6001
TLS ERROR 'Received TLS alert message: Internal error' (-15) setting session active

Does it work if you using HTTP instead of HTTPS?
--
digital man (rob)

Steven Wright quote #33:
Everyone has a photographic memory; some just don't have film.
Norco, CA WX: 87.7øF, 41.0% humidity, 14 mph WSW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: HTTPRequest Error: Unable to read status
By: Digital Man to Codefenix on Tue Aug 05 2025 04:22 pm

Does it work if you using HTTP instead of HTTPS? --

No, but standard HTTP doesn't seem to be working at all with open-meteo.com. Not in browsers, not via curl, not with HTTPRequest. Not sure whether it's a temporary thing, or if they simply chose to disable it.

Shouldn't HTTPRequest handle HTTPS anyway? I tend to point my requests towards HTTPS URLs if I have the option. Seems odd that HTTPRequest calls to open-meteo.com are failing when it works fine in browsers and via curl.

|15 þ ù ú codefenix ú ù ú ConstructiveChaos BBS ú ú ù þ þ
|08 þ þ ù (https/telnet/ssh)://conchaos.synchro.net ú ù þ
|07
---
þ Synchronet þ -=[ ConstructiveChaos BBS | conchaos.synchro.net ]=-

Re: HTTPRequest Error: Unable to read status
By: Codefenix to Digital Man on Tue Aug 05 2025 08:20 pm

Re: HTTPRequest Error: Unable to read status
By: Digital Man to Codefenix on Tue Aug 05 2025 04:22 pm

Does it work if you using HTTP instead of HTTPS? --

No, but standard HTTP doesn't seem to be working at all with open-meteo.com. Not in browsers, not via curl, not with HTTPRequest. Not sure whether it's a temporary thing, or if they simply chose to disable it.

Shouldn't HTTPRequest handle HTTPS anyway?

Maybe, probably? I don't know that I've tried. It may require touching second-base first.

I tend to point my requests
towards HTTPS URLs if I have the option. Seems odd that HTTPRequest calls to open-meteo.com are failing when it works fine in browsers and via curl.

Try a different known-working HTTPS URL (e.g. https://www.synchro.net) with HTTPRequest to confirm that it's working as expected. If it doesn't work, then the problem is with HTTPS specifically. If it does work, then there's something unique about the requirements of open-meteo.com.
--
digital man (rob)

Synchronet/BBS Terminology Definition #72:
SEXYZ = Synchronet External X/Y/ZMODEM file transfer protocol driver
Norco, CA WX: 72.5øF, 64.0% humidity, 1 mph WNW wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: HTTPRequest Error: Unable to read status
By: Digital Man to Codefenix on Tue Aug 05 2025 09:44 pm

Try a different known-working HTTPS URL (e.g. https://www.synchro.net) with HTTPRequest to confirm that it's working as expected. If it doesn't work, then the problem is with HTTPS specifically. If it does work, then there's something unique about the requirements of open-meteo.com.

Yeah, other HTTPS APIs work fine, like those at https://api.weather.gov as well as https://nominatim.openstreetmap.org. HTTPRequest returns status 200 from those.

|15 þ ù ú codefenix ú ù ú ConstructiveChaos BBS ú ú ù þ þ
|08 þ þ ù (https/telnet/ssh)://conchaos.synchro.net ú ù þ
|07
---
þ Synchronet þ -=[ ConstructiveChaos BBS | conchaos.synchro.net ]=-

Re: HTTPRequest Error: Unable to read status
By: Codefenix to Digital Man on Wed Aug 06 2025 08:10 am

Re: HTTPRequest Error: Unable to read status
By: Digital Man to Codefenix on Tue Aug 05 2025 09:44 pm

Try a different known-working HTTPS URL (e.g. https://www.synchro.net) with HTTPRequest to confirm that it's working as expected. If it doesn't work, then the problem is with HTTPS specifically. If it does work, then there's something unique about the requirements of open-meteo.com.

Yeah, other HTTPS APIs work fine, like those at https://api.weather.gov as well as https://nominatim.openstreetmap.org. HTTPRequest returns status 200 from those.

Okay, good know. Maybe there's some introspection/debug option you can enable in the HTTPRequest implementation to get more insight into what the issue might be.
--
digital man (rob)

This Is Spinal Tap quote #25:
Viv Savage: Have... a good... time... all the time. That's my philosophy. Norco, CA WX: 86.1øF, 47.0% humidity, 2 mph W wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net