404 when version is removed

Michel Prado

March 17, 2018 21:47

Any idea why this works:

 

http://res.cloudinary.com/catinodeh/image/upload/c_fit,w_200/v1521322356/c34bb435-b0e1-4cab-abcc-27b13005698c.png

 

but not this:

 

http://res.cloudinary.com/catinodeh/image/upload/c_fit,w_200/c34bb435-b0e1-4cab-abcc-27b13005698c.png

0

• 

  Shirly Manor

  March 18, 2018 00:03

  This may happen when trying to access a derived version of an image before it's fully loaded into your Cloudinary account. When a 404 error is returned, Cloudinary caches it for a while. After the caching has passed, Cloudinary will try to re-access the file (now it's working). For more information:
  http://support.cloudinary.com/entries/26928358-I-m-getting-a-404-not-found-for-my-transformed-image-while-other-versions-of-that-image-work

  If it's possible to please make sure that the resources (and their derivatives) won't be accessed before the original is fully loaded into your Cloudinary account, the images will work seamlessly without any caching of 404 errors.

   

  0
• 

  Michel Prado

  March 18, 2018 00:54

  How do I know if a resource has been fully loaded ? How do I force it to be ? (delete it and re-upload it ? )

  0
• 

  Shirly Manor

  March 20, 2018 01:12

  Hi Michel

  Looking at our logs and I saw that in the last 30 days an image named: 4cb97a17-c2ad-4fa0-806d-35c6c7643636
  Uploaded on February 25th 2018, 15:24:07.408 (and uploaded again on March 6th 2018, 23:22:33.388)

  However, We saw 404 errors since February 19th 2018, 18:41:31.417
  Also, we saw Rename to c34bb435-b0e1-4cab-abcc-27b13005698c on March 17th 2018, 21:06:25.901

  The best practice is when uploading an image to wait for the response (UploadResult) and then create the transformed image.

  Thanks

  0

Post is closed for comments.