'public_id' in post-upload callback to 'notification_url'

We've been experiencing a bug that does not come up consistently, but is frequent enough that it's had a severely negative impact on several of our users.

We have a webapp that runs on Android 2.3 and does ajax-via-iframe uploads to Cloudinary. However, because the browser does not support any progress events, it is not possible for us to know when an image has completely uploaded until we receive the callback to our server using the 'notification_url' we provide in the upload request.

On Nov 25th and 27th, there were periods of time when the callback to the 'notification_url' contained either an empty body, or missing public_id.

We have a large user base in rural Morocco and their only internet access is via 3G on Android Gingerbread phones. Needless to say, we are actually using that 'notification_url' (and the public_id in the callback) for mission critical processes.

I was wondering if this was a bug that was maybe recently fixed or worked on. Also, maybe what we are experiencing isn't a a bug and we need to change some code on our end.

Thanks for you help!

Tom

Itay Taragano

December 02, 2013 08:45

Hi Tom,

This part of the system was not recently updated.

Please note that if there is an error in the upload, we will sent a notification url with the error details.

We see a few errors on November 25 and 27 (invalid image file, missing file), can this be the situation?

Regarding the empty notification - did you get the notification headers correctly?

Looking forward for your response.

Thanks,

Itay

Anou

December 03, 2013 13:00

I don't have record of the headers, but if I find any bad ones, I'll let you know. Looks like the root cause are on our end, or at least on our user's browser's end. Thanks for looking into this and finding those errors for us!

Comments