Upload image from url error - Resource not found

Saas Saas

December 16, 2019 13:08 Edited

Hi,

I'm trying to upload pictures to Cloudinary from web urls. Most of them work, but I have a few of them that return a "Resource not found" error on upload, even though the url is publicly accessible and is an image. I tried with the API and the web interface.

Example of url that don't work:
- https://logo.clearbit.com/onestock-retail.com
- https://logo.clearbit.com/igloohome.fr

Example of a similar url that works:
- https://logo.clearbit.com/toucantoco.com

But if I had a query parameter on the urls that don't work (ex https://logo.clearbit.com/onestock-retail.com?a=1) it will work.

Any idea what would cause that?

Thx

0

• 

  Aditi Madan

  December 17, 2019 01:01

  Hi,

  I tried fetching these resources to the demo account and I could fetch them successfully. 

  https://res.cloudinary.com/demo/image/fetch/https://logo.clearbit.com/onestock-retail.com

  https://res.cloudinary.com/demo/image/fetch/https://logo.clearbit.com/igloohome.fr

  Maybe you tried fetching them when this was unavailable and it cached a 404 now.

  If you continue seeing the issue then please open a support ticket with your cloud name and I will be able to check further.

  Regards,

  Aditi

  0
• 

  Saas Saas

  December 17, 2019 09:35

  Hi Aditi,

  Thank you for your reply. Yes it seems that it's working fine now.
  So yes, maybe the image was temporary unavailable when we first try to fetch it.

  Follow up questions:
  How long does your cache lasts?
  Is there a way to bust the cache with a query parameter or an API parameter?
  Do we have access to logs of the calls you made to fetch the images, to have a better understanding of the error you got?

  0
• 

  Aditi Madan

  December 18, 2019 00:33

  Hi,

  Fetched resources are cached for 7 days.

  You can delete the fetched resource and re-fetch it or we have automatic fetching/invalidation mechanism which can be set to re-fetch or delete a fetched resource after a certain time period automatically.

  More information here: https://support.cloudinary.com/hc/en-us/articles/205465262-Setting-an-expiration-policy-for-your-Fetch-resources

  The logs are for internal checking but you can always view the network tab to see the error.

  Regards,
  Aditi

  0

Post is closed for comments.