Invalidating Thumbnails

tourasia

October 10, 2019 08:28

Hi everyone

We're using cloudinary for quite a while and we're pretty happy with it. Today I noticed a problem with a thumbnail not beeing invalidated in the cache.

We have the issue with this image: https://res.cloudinary.com/tourasia/image/upload/agencies/1188.png
We first uploaded it one week ago on the 3. of october but replaced it on the same day. We did all that with the php api. in the upload i had the invalidate flag set to true. When we replaced the image we did that also with the php api with a destroy and upload request, both with the invalidate flags set to true.

But when I request the image a the following url I still get the old one with the white font: https://res.cloudinary.com/tourasia/image/upload/w_300/agencies/1188.jpg but the font should be black as you can see in the original image above. I also tried to delete and reupload the image in the console without any luck.

For us it's crucial that the image is available at exactly this url, so using the versions in the url is no possibility. According to your documentation the invalidation should be done in a few hours and for us this was not working since last week: https://cloudinary.com/documentation/upload_images#asset_versions

Is there a possibility to invalidate all the already cached thumbnails?

Best regards, David

0

• 

  Eyal Katz Talmon

  October 10, 2019 14:35

  Hi, David. When checking on my side, both links are with the black font, and it looks like the new image is delivered (I do not know exactly how the old image looked like). If you still see the white font on your side, the image is probably still cached on the CDN.

  Looking at your cloud settings, it seems that currently, if an asset resides within a folder, it's URL is invalidated only if the public id is preceded with a `v1` component (even if the invalidate parameter is set to true) -
  https://res.cloudinary.com/tourasia/image/upload/w_300/v1/agencies/1188.jpg
  Since you've mentioned that it's crucial for you that the image will be available through the mentioned URL (without the `v1`), I can change those settings so that invalidation will take effect only to URLs that do not include the version component. Let me know if you'de like me to set it up. 

  Note that this is a cloud configuration and will affect all invalidation. More information about our URL invalidations conventions can be found here (you're currently set to use the first option mentioned in the article).

  Are you using the version component when delivering images? 

  0
• 

  tourasia

  October 10, 2019 14:43

  Hi Eyal
  Thanks for your reply. This is strange, as we still see the old image with white font on white background

  

   

  We don't use the version component at all. So if I understand this corrently we would need to switch to the url convention number 2, right? Is this something I can do by myself?

  After that, the invalidate parameter should work, right?

  0
• 

  Shirly Manor

  October 10, 2019 18:35

  Hi David,

  I manually invalidate this image. Can you please try again and let me know if that helps?

  If you want to globally change your setting on the account to invalidate un-versioned URL. please open a ticket at support@cloudinary.com with your cloud name and 4 last digits of your API Secret and we can do it for you (it only from our end).

  Hope that helps,

  0
• 

  tourasia

  October 17, 2019 13:22

  Dear Shirly

  Sorry for my late reply and thanks for invalidations. This solved our problem and I will contact support to change the general invalidation.

  Best regards
  David

  0

Post is closed for comments.