Complete

over 5 years ago

We don't plan to open up local HTTP beyond 127.0.0.1/localhost for reasons explained on this thread: https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-version-4-20-broke-local-http-access?CommentId=925854ea-9e90-46d5-83f5-145442790cf5

Unable to use http on 192.168.x.x

I'm trying to use the Hue api, which is over http on internal ips, but my Garmin Forrunner 735xt blocks it .

I realise it's https only in some places for a reason , but It's local traffic and I'm using android, so http is fine.

1503366

1503366 over 5 years ago in reply to peterdedecker

Yep already read all of that. And there's no reason apart from not spending money for Garmin to stop that. Planning to get an Android wear device next as I'm not very impressed with Garmin's support for developers.
- Cancel
- Up 0 Down
- More
- Cancel
peterdedecker over 5 years ago in reply to 1503366

while I concur that it would make a lot more sense to allow http for the private ip address ranges it's unlikely that this change will be implemented, there's a long discussion here https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-version-4-20-broke-local-http-access?CommentId=925854ea-9e90-46d5-83f5-145442790cf5 if you have some time to read.
- Cancel
- Up 0 Down
- More
- Cancel
1503366 over 5 years ago in reply to Rachael.ConnectIQ

Yes, I know. I'm saying that's not okay and you need to fix it please! Thank you!
- Cancel
- Up 0 Down
- More
- Cancel
Rachael.ConnectIQ over 5 years ago

You can't use HTTP on 192.168.x.x. Only HTTP on 127.0.0.1 will work, everything else is restricted.
- Cancel
- Up 0 Down
- More
- Cancel