Cache and versioning on auto mapping
Currently I am using cloudinary's solution to auto-map a S3 bucket fulfilled with images.
The issue I am facing right now is that when I overwrite an image on S3 I cannot see it though cloudinary (and it's visible on the bucket/cdn URL).
I've done some research on image versioning and Cache-Control for S3 and I could not come up with the best solution to solve this.
What should be done? On my cloudinary library the image appears outdated (saying that it was uploaded months ago), like it is not being refreshed.
I could not figure out a way to implement versioning with auto-upload. Should I use upload presets? Is there a way to invalidate the cache automatically on image overwrite?
I've already set some resources to send the Cache-Control header on S3 but it does not work, using custom parameters on the URL does not work as well, adding /v11245141/ on the URL does not have any effect. That seems odd, right? Since if it is a caching problem a different URL should have return a fresh version of the image from s3 bucket.
Post is closed for comments.