Possible workarounds for APIs which support only HTTP

Former Member over 5 years ago

Hi All

Understand that makeWebRequest supports only HTTPS and not HTTP.
However, the API I need to access uses only HTTP at this point of time.

Could any kind soul share the possible workarounds?

So far, I am looking into either setting up a Apache server to act as a proxy or using a companion application (Android / iOS) to workaround this. Both seems to be an awful lot of work for a simple application thus trying to find a simpler way.

Thanks!

Top Replies

All Replies

0 dpawlyk over 5 years ago

If it's a public website, it's kind of odd it doesn't already support https:.

It appears https isn't required for the local host (127.1.1.1) or the LAN (e.g. your home network, 192,168.*.). So, the proxy should work.

You might consider looking into using serveo.net as a proxy. That might be easier than writing an app.

0 Former Member over 5 years ago in reply to dpawlyk

Thanks dpawlyk for the suggestion! Will look into serveo.net.

Yes it is a public website in my country (Singapore). Am trying to contact them to see if converting to HTTPS is in the pipelines. Fingers crossed.

0 HerrRiebmann over 5 years ago in reply to dpawlyk

dpawlyk said:
It appears https isn't required for the local host (127.1.1.1) or the LAN (e.g. your home network, 192,168.*.).

No afaik, Garmin allowed localhost (127.0.0.1) only. That way you can communicate with other Apps on your phone.
If you want to communicate with a none SSL secured device in your local network (IoT, HiFi Receiver, TV, etc.) you will have to create a proxy.

0 dpawlyk over 5 years ago in reply to HerrRiebmann

My 1030 can access 192.168.*.* without needing https.

I use my IQ app to download routes from a file server on my local network.

I use my IQ app to access the gexporter file server on my tablet.

0 dpawlyk over 5 years ago in reply to Former Member

It would be kind of embarrassing if it wasn't in the pipeline. It's kind of embarrassing that the don't already use it.

0 jim_m_58 over 5 years ago in reply to dpawlyk

Are you using iOS or Android? There's a difference.

See https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-version-4-20-broke-local-http-access

for the latest with Android

0 dpawlyk over 5 years ago in reply to jim_m_58

iOS.

That's a bug in 4.20 on Android (which means it's supposed to work).

And it was fixed on 4.22

No one is going to set up certificates for their local network (it's a pain to do and has security issues too).

If Garmin requires it, you can say by-by to using these devices to IoT applications. And hello to quite a lot of angry IQ developers.

For non-local sites, https is pretty-much the standard (that makes sense and it's not that hard to do).

0 jim_m_58 over 5 years ago in reply to dpawlyk

On Andrioid with 4.22 her's the statement from Garmin:

"Garmin Connect Mobile 4.22 for Android includes the changes to allow HTTP on 127.0.0.1."

(not access to 192.168.*.* with HTTP)

0 dpawlyk over 5 years ago in reply to jim_m_58

192.168.*.* doesn't appear to work on Android (I just tried it). It works fine on iOS. That's odd.

It's unfortunate it doesn't work on Android.

0 jim_m_58 over 5 years ago in reply to dpawlyk

Again, that's by design. See the bug report I linked to a few posts back.