This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bug/Feature Request - 307 Redirect handling for ConnectIQ Web Requests

Former Member
Former Member
Hi there,

First time on the forums so point me in the right direction if this is wrong place to raise issues

I'm attempting to develop a Nest thermostat app using ConnectIQ but am hindered by the fact that the Nest API requires that a client handle 307 redirects. Web requests are sent from a Connect IQ device (In my case a fenix 3 watch) to google via the Garmin Connect App (In my case a Sumsung s6). I would expect the Connect App to automatically handle 307 redirects but unfortunately this is not the case. More critically, instead of returning a 307 response to the watch/device it sends a 401 with no response body... This makes it impossible to manually handle the redirect.

Please add automatic 307 handling, or failing that send the 307 back to the device so that it can be manually handled.
  • This is primarily a forum, provided and maintained by Garmin, as a place for users to discuss with each other their thoughts on and experiences (including issues) with Garmin wearable fitness products and cycling computers. It is not provided as a means to engage Garmin staff directly, reports faults with the expectation of attention and remediation by the company, or submit service requests.

    If you want to make a suggestion to Garmin for changes and/or additions to product functionality, try here:
    http://www.garmin.com/contactUs/ideas/
  • Here's the Connect IQ developer's forum, and it's the place you want to post for something CIQ related

    https://forums.garmin.com/forumdisplay.php?479-Connect-IQ

    Garmin CIQ folks as well as 3rd party developers are there to help. (the Garmin folks all have .ConnectIQ at the end of their forum names) The Garmin folks can help if GCM is acting oddly with CIQ.