Cloudinary offers to invalidate several different URL conventions that are used for different purposes. Let's make sure that the URLs being used on your site match those your account is configured to invalidate.
The three different URL conventions for signed and non-signed URLs are as follows:
1. (Default) Using no version at all for non-foldered images and including `v1` for foldered images
- Note if using an SDK to generate the URL, `v1` is automatically added to the URL by default for foldered images
- Images not in folders, e.g. https://res.cloudinary.com/demo/image/upload/sample.jpg
- Images in folders, e.g. https://res.cloudinary.com/demo/image/upload/v1/folder1/folder2/sample.jpg .
2. Include no versions for everything
- Images not in folders, e.g. https://res.cloudinary.com/demo/image/upload/sample.jpg
- Images in folders, e.g. https://res.cloudinary.com/demo/image/upload/folder1/folder2/sample.jpg
3. Include the full version value `v1515617850` for both foldered and non-foldered.
- Images not in folders, e.g. https://res.cloudinary.com/demo/image/upload/v1515617850/sample.jpg
- Images in folders, e.g. https://res.cloudinary.com/demo/image/upload/v1525209117/folder1/folder2/sample.jpg
What do the different options mean
Note the following applies to all options
- Automatically invalidate the URL convention being used when deleting/replacing an existing image.
- It can take a few minutes (up to an hour) for the invalidation to fully propagate throughout the CDN
- To invalidate the previous version, the parameter
invalidateshould be explicitly defined in the API call (as it is not automatically applied to everything). - By default, when deleting or renaming a resource through the Media Library, it is automatically invalidated based on the settings configured in the account.
Option 1
- Our SDKs automatically include the `v1` component for foldered images.
- No version is included for non-foldered images.
Option 2
- Exactly the same as option 1 but without the `v1` component for foldered images
- This option is relevant to those who do not use our SDK.
Option 3
- Referred to as "cache-busting", by including the version in the delivery URL, the CDNs cached version is bypassed and forces an immediate delivery of the newest assets. In this particular case, the invalidation is unnecessary as the full version is being used to bypass the cache.
Your account can be configured to invalidate the URL conventions mentioned above. Please let us know which URL convention is being used and whether it will be signed or unsigned so that we can make sure your account is invalidating the correct URLs. Open a ticket here.
Comments
0 comments
Article is closed for comments.