makeImageRequest => additional headers and SVGs?

HI all,

I am trying to use "makeImageRequest" in my app, which generally works fine. Still there are 2 things that I require to be able to utilize it:

1. there is no way to add additional headers to the request. With "makeWebRequest" there is the ":headers" key that can be used to pass additional headers to the webserver. The same key does not work with "makeImageRequest". Is there a particular reason for it? My use case here is that I need to pass authentication credentials that are required.

2. SVG-support. I have found this post: makeImageRequest(): any chance to get support for SVG format? - Discussion - Connect IQ - Garmin Forums but there is no activity since 3 months. Is there hope that svg images will be supported? In fact those are easier to handle than binary formats (like png) in my opinion, as the ressource API already provides support for it. Why are we getting "404" error code when trying to request those image formats?

Thanks!

Talkabout over 2 years ago

Hi,

any chance to get some feedback here? At least something like "not planned, won't work"...

Thanks!

jim_m_58 over 2 years ago in reply to Talkabout

when you do a makeImageRequest, there's a Garmin server in the middle. One of the things it does is when it gets the image, it gets converted into something that can be used by the Garmin device, when it comes to things like size and palette and format. I suspect when the Garmin server is making the actual request, something is lost, or maybe the Garmin server doesn't handle SVG

Talkabout over 2 years ago in reply to jim_m_58

Hi jim_m_58,

yes, I am aware of the proxy server, and this is perfectly fine. Still I would expect the headers to be forwarded and also SVGs to be handled correctly, as those are standard format for web applications. I was hoping that somebody from Garmin would jump in here and clarify why those limitations are in place and if there is a plan to solve them.

Thanks Jim for your response!

Talkabout over 2 years ago

HI all,

is anybody from Garmin reading here and able to answer the questions? Especially the topic about headers not being forwarded via makeImageRequest cause me big trouble...!

Bye

Talkabout over 2 years ago in reply to Talkabout

Brandon.ConnectIQ are you able to help out here?

Thanks!

Matt 3 days ago

Hello,

I do have the exact same issue with the makeImageRequest call.

I'm running a publicly hosted instance of Node Red, which generates QR codes. In order to access the images, it's necessary to pass authentication headers.
Actually I was not aware of the proxy server itself until now, but that's a different story.

In my situation I also receive 404 response codes, when I try to request the images from Node Red via the watch debugger.

Are initial headers like the "Authorization" header actually forwarded correctly, or are they thrown away by the Garmin proxy servers?