We are seeing an issue in AEM Author when replacing existing DAM assets with a new file that has the same name.
Below are the steps followed that lead to the issue:
Navigate to /content/dam/
Click Create → upload an image file that has the same name as an existing file
When prompted that a file already exists → select Replace
The file gets replaced successfully in DAM
However, on pages where the image is used via DAM reference (for example as /content/dam/...image.png), the updated image does not reflect in the component rendering. The page still displays the old image even though the DAM asset has been replaced.
Upon inspecting the network request of the image in the page, we see the following cache headers applied:
cache-control: private, max-age=43200, immutable
This behavior is observed in Author instance and seems to happen specifically for asset URLs referenced directly from /content/dam/....
It appears that the browser is serving the cached version due to the immutable directive, so the updated file is not fetched unless the URL changes or cache is manually cleared.
Could someone help with guidance on how to reduce the cache timing or clear the cache?
@arunpatidar
