Always I get a 404 when I upload an image (an asynchronous process where I copy).
we have an asynchronous process where we copy the image in this one, all normal, the problem is that the URL we have generated it, before that the copy is finished. we supposed that one time the copy's over (asynchronous process ) it would answer us later, but not, because if we call an image for example "https://res.cloudinary.com/image.bmp" and this not respond (404) because at the moment haven't loaded but in seconds it'll load and once it loads I should "https://res.cloudinary.com/image.bmp" respond to us with the correct image but not, always it is 404, even if it has already been loaded.
I consider that is a bug of Cloudinary, is normal that not load an image that hasn't been copied, but this one should respond once this has been copied.
apparently, if I do a request HTTP to an URL of an image of Cloudinary that in the future I'll use, but hasn't been copied yet, and I already made the HTTP request before your copy. this one does not respond again (it will always be 404) unless you make another request for the same picture but with a different dimension for example "https://res.cloudinary.com/q_61,w_250/image.bmp" (the new one responds, the old one does not respond again never)
-
Official comment
Hi David,
You are accessing the wrong URL. You need to have your cloud name in it
For example:
https://res.cloudinary.com/demo/image/upload/sample
where demo is the cloud name and upload is your method to upload an image.In order to better understand the issue, I need some more information.
Please confirm which version of our SDK you're using, as well as:
- A sample of your code showing where the error occurs.
- The value you're passing as parameters (for example, the transformation options)
- The error stack trace from your code, or the exact error message you see returned by our API
Looking forward to your response.
Regards
Akshay
Post is closed for comments.
Comments
1 comment