Connect version 4.20 broke local http access?

Could this not be implemented with an intentional flag indicating an http only interface? Or, perhaps a user-defined exception list? 

I have a direct WIFI connection from the phone to a Gopro that has a fixed IP address of 10.5.5.9 used in my app. Commands are sent to this device such as:

http://10.5.5.9/gp/gpControl/status  

...in order to control it. So, since only a localhost IP of 127.0.0.1 will be allowed, I do not believe this would work for me. 

Could this not be implemented with an intentional flag indicating an http only interface? Or, perhaps a user-defined exception list? 

I have a direct WIFI connection from the phone to a Gopro that has a fixed IP address of 10.5.5.9 used in my app. Commands are sent to this device such as:

http://10.5.5.9/gp/gpControl/status  

...in order to control it. So, since only a localhost IP of 127.0.0.1 will be allowed, I do not believe this would work for me. 

agreed. i am very dissappointed Garmin (as a company) did not respond to the simple solution i proposed to fix all use cases. 

Yeah, for me and my phone this could work... but, I can't really expect the couple thousand of download's users to do this. Many of them could barely configure their WIFI. :)

Mostly this utility was for me and I just posted it up because I'm nice and hoped others might find value. If Garmin wants to make things so painful, I just won't bother with their platform I suppose. 

Once plain text to localhost is allowed, the door would  be open to salvage http connectivity to LAN addresses by running a (custom) proxy app on the phone that has it's own network-security-config. Wasteful and cumbersome, but for sufficiently exotic but mission-critical use cases it might be good enough.