When I first fetch an image via Cloudinary media optimizer URL, I get a 404. This is fine because the image was not available on my server in the first place. After I fixed the issue on my server, I still get a 404 via the Cloudinary URL. I assume this is because the 404 is cached on Cloudinary.
Finally, I tried to invalidate the cache (both via the Media Optimizer API and dashboard). However, I still get a 404 with the Cloudinary URL. The response header contains the following:
Resource not found on media source: ....
I don't think the cache invalidation is working here as the image is available on the media source and can be accessed directly.
Please sign in to leave a comment.