I'm using AzureBlobCache to store crops generated by ImageProcessor for my media that is stored on AzureBlobstorage
It all works fine EXCEPT that the crops in the cache container on AzureBlobStorage are being deleted after 365days.
Requesting crops after they've been deleted from the cache container, will re-create them, which probably works well enough for most applications.
However, this is causing me some grief, as I have applications that use references to the crop URLs which is not being updated by that process of crop re-generation, resulting in broken image links, and discovering/updating those URL references later is an expensive process.
I know there is a maxDays setting, but I understood that to be the days before a CDN must refresh its copy, not days before the crop is deleted from the cache container.
Does anyone know if there is any way to stop this behavior, and not have the cache container crops deleted after some expiry period ?
AzureBlobCache - deleting images are 365days
I'm using AzureBlobCache to store crops generated by ImageProcessor for my media that is stored on AzureBlobstorage
It all works fine EXCEPT that the crops in the cache container on AzureBlobStorage are being deleted after 365days.
Requesting crops after they've been deleted from the cache container, will re-create them, which probably works well enough for most applications.
However, this is causing me some grief, as I have applications that use references to the crop URLs which is not being updated by that process of crop re-generation, resulting in broken image links, and discovering/updating those URL references later is an expensive process.
I know there is a maxDays setting, but I understood that to be the days before a CDN must refresh its copy, not days before the crop is deleted from the cache container.
Does anyone know if there is any way to stop this behavior, and not have the cache container crops deleted after some expiry period ?
is working on a reply...