Updating hosted images, Making images that have been replaced using the same name update |
Updating hosted images, Making images that have been replaced using the same name update |
SMMorse4 |
Jun 27 2018, 01:22 PM
Post
#1
|
Group: Members Posts: 1 Joined: 27-June 18 Member No.: 26,665 |
I work for a business that hosts images we use for our website and email campaigns on our domain. We've recently revamped most of our images across all platforms, and to make the new images appear when someone opens an older email, we replaced some images(mostly icons and logos) using the same file names. Unfortunately, we've had varying levels of success with this, with some emails displaying the new images while others still displaying the old versions of the images, and even new emails I've coded displaying the old images.
Does anyone know how to force all code that is using images from our repository to display the current versions of the images? |
Christian J |
Jun 27 2018, 07:37 PM
Post
#2
|
. Group: WDG Moderators Posts: 9,653 Joined: 10-August 06 Member No.: 7 |
Does anyone know how to force all code that is using images from our repository to display the current versions of the images? On web pages people sometimes add a query string to an embedded file to prevent caching, such as: CODE foo.jpg?bar=baz Maybe that works in email clients too but I've never tested. Another option might be to discourage caching with the image file's HTTP header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching Of course there's no guarantee email clients will follow any of this (personally I block all third party images in emails). |
Lo-Fi Version | Time is now: 18th April 2024 - 10:17 PM |