HTTP status code for makeImageRequest

Hi,

I was hoping to allow my image server to be a little more communicative...

Specifically, I wanted to send back a custom HTTP status code of 499 when the generated image would be too big to show on the intended watch.

Trouble is, when I use Communications.makeImageRequest the 499 error code always becomes a 404 by the time it reaches my widget.

Is there any way at all to get Communications.makeImageRequest to return the custom error? Or some other way for me to distinguish failure reasons with makeImageRequest?

Thanks,

Top Replies

dpawlyk over 3 years ago in reply to sabeard +1

Yes, that explains it.

All Replies

0 dpawlyk over 3 years ago

Why not scale the image? (Or don't offer images that are too big.)

0 9635560 over 3 years ago in reply to dpawlyk

The image has to be pixel-perfect and it has an absolute minimum size where it can be drawn at.

(OK, it's a bar code... if bars are not an integer multiple of one pixel wide the world will probably end, or at least an angel will die somewhere.)

0 dpawlyk over 3 years ago in reply to 9635560

You could return an image that says "too big".

0 9635560 over 3 years ago in reply to dpawlyk

In seven languages #sigh#

Yes, that's one approach, but it would be so much easier if I could just use the existing HTTP status code mechanism.

0 dpawlyk over 3 years ago in reply to 9635560

(Seven languages doesn't seem that hard to do.)

The http code isn't really an IQ question.

What is your website written in?

www.php.net/.../function.http-response-code.php

0 9635560 over 3 years ago in reply to dpawlyk

No, it absolutely is an IQ question! The HTTP Status code stuff is built and uses standard HTTP behaviour that is allowed, allowable and supported!

I can see in Charles that my HTTP status code is being correctly generated and set and sent.

It's just not getting passed through Connect.

(But for reference, the site is in Symfony / PHP)

0 dpawlyk over 3 years ago in reply to 9635560

I used the following in my webpage and my IQ app reports 499 as the result.

http_response_code(499):

My website returns JSON. Maybe, it won't work for the image call.

=====================

Make two calls: one with a JSON response/status. And another with the image call.

0 9635560 over 3 years ago in reply to dpawlyk

You are of course correct that I could do it via a second JSON call, but...

This is really a very simplistic service - somebody puts in a value that gets converted to a barcode or QR code and spat back at them. By supplying their device shape and dimensions as part of the request, I can pre-calculate the optimal response size and so on.

While it is ever so, ever so easy to provide a service that calculates the sizes and says what is possible, it is doubling up all three of the workload, the number of comms calls and the code overhead for the Garmin side.

At the moment, I am reduced to assuming that any 404 is because the image cannot fit the available space, but that's kinda rough.

An alternative would be to return a 10x10 pixel (or similar) fail image and then programmatically deduce that there is too much data if the returned image is only ten pixels.

Kinda hacky though...

0 dpawlyk over 3 years ago in reply to 9635560

I like it!

I don't think the double call things would be too bad.

0 9635560 over 3 years ago in reply to dpawlyk

It’s not that it’s hard, just totally unnecessary.