On second thought, I do not understand why this happens. I thought it is some side effect of the CORS trickery we do to get nice loading bars and performance metrics, but the actual thumbnail displayed by MediaViewer is created normally via an <img> tag and should have the exact same caching headers an article thumbnail does. So even if the AJAX request for the image is cached, the <img> that is displayed should not be.

Dan, do you remember the browser/OS you used?

In T78745#852378, @Tgr wrote:

On second thought, I do not understand why this happens. I thought it is some side effect of the CORS trickery we do to get nice loading bars and performance metrics, but the actual thumbnail displayed by MediaViewer is created normally via an <img> tag and should have the exact same caching headers an article thumbnail does. So even if the AJAX request for the image is cached, the <img> that is displayed should not be.

We have ongoing issues with browser caching causing old image versions being shown for normal images on file description pages/articles.

In T78745#852379, @Bawolff wrote:

In T78745#852378, @Tgr wrote:

On second thought, I do not understand why this happens. I thought it is some side effect of the CORS trickery we do to get nice loading bars and performance metrics, but the actual thumbnail displayed by MediaViewer is created normally via an <img> tag and should have the exact same caching headers an article thumbnail does. So even if the AJAX request for the image is cached, the <img> that is displayed should not be.

We have ongoing issues with browser caching causing old image versions being shown for normal images on file description pages/articles.

Is there a task for that? A mailing list thread?

The related task is T38380