Complete
over 4 years ago

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

Connect version 4.20 broke local http access?

Getting several reports of functionality no longer working, it looks like Android Garmin connect app version 4.20 may have broken web request to local host via urls like http://127.0.0.1:17580/sgv.json?count=3

Horsetooth
Parents
  • over 4 years ago

    One more vote for reconsidering the fix. Unencrypted http connections should be allowed to IP addresses. I'm all for https on the big wild internet, but in some cases it just does not make any sense.

    In my specific case, an option to allow https connection without certificate validation would probably also work, but again, it should not be necessary. Https connections to numeric IP addresses just doesn't make much sense.

    I've been working on a Hue app for a few days using the simulator without any problems. Then, when testing it on the watch, I'm hit with a big fat hammer. It's not working, and it's not going to work because of some policy that's not even being explained. Not in the documentation (which is a bit incomplete, on a more general note), and not here in the discussion. No reasoning behind the decision to only allow http access to 127.0.0.1, despite lots of comments asking for a reconsideration, or at least an explanation.

    This really took away a lot of the joy of my brand new top tier Garmin watch.

Comment
  • over 4 years ago

    One more vote for reconsidering the fix. Unencrypted http connections should be allowed to IP addresses. I'm all for https on the big wild internet, but in some cases it just does not make any sense.

    In my specific case, an option to allow https connection without certificate validation would probably also work, but again, it should not be necessary. Https connections to numeric IP addresses just doesn't make much sense.

    I've been working on a Hue app for a few days using the simulator without any problems. Then, when testing it on the watch, I'm hit with a big fat hammer. It's not working, and it's not going to work because of some policy that's not even being explained. Not in the documentation (which is a bit incomplete, on a more general note), and not here in the discussion. No reasoning behind the decision to only allow http access to 127.0.0.1, despite lots of comments asking for a reconsideration, or at least an explanation.

    This really took away a lot of the joy of my brand new top tier Garmin watch.

Children