All of Cloudinary delivered images have the correct expiration headers using the Cache-Control 'max-age' directive (which is the best practice for CDN delivery).
Articles in this section
- Why is my asset returning a 40X error?
- Demo to play with different q_auto levels to save bandwidth when using higher DPR
- Best Practices For Mobile Usage
- How Can I perform bulk operation in the new UI
- Why shouldn't I use `v[0-9]` within folder names?
- CDN Invalidations: URL conventions invalidated for removed or replaced assets
- Why does Google's PageSpeed show that the image is not optimized?
- Why does the Cache-Control header contain both 'public' and 'private'?
- What happens if my notification URL (webhook) fails?
- Why am I seeing a long Time to first byte (TTFB) on WebPageTest.org
Could you elaborate on why it is best practice?
Without Expires, browsers will keep asking cloudinary/akamai if the file has changed based on Last-Modified and Etag.
Since the version ("v1386214311") updates when a new image is uploaded, this should be a perfectly attainable behavior for Cloudinary.
The only thing I can think of that you might be guarding against is if your transformation algorithms change, or you introduce a bug, and you want to make sure the user gets the newest version. If that's the case, it would be nice to see this explained explicitly.
Hmm, now I am doing some more research and folks claim that Cache-Control should be sufficient and achieve what I have described. That's not what I observed in my casual tests in my browser, but maybe I was misreading the chrome dev tools info.
I am having the same problem - I am not seeing the browser cache any of the images served up from Cloudinary. Any inputs on how I can change this?
Yeah, this is a deal breaker for me. We've a bunch of galleries that wait for images loaded before displaying and those requests are slowing down display time significantly. The images are already hashes so I'm not worried about modification. I'd like a way to specify that in the fetch url.
Same for me... Devtools status shows 200 instead of 304 (not modified/cahed). I can understand that it might be related to tracking/pricing on your side, but cashing is very important for us as well.
Is there anyway that I can enable it in the dashboard?
Please sign in to leave a comment.