The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Amazon S3 (and probably many others) does not garantee how soon new content is available when you overwrite an existing file and access its URL.
As a result, we have experienced that when changing image style definitions or doing a custom cropping (using other modules), the newly generated images are not available immediately. This causes further issues since we flush our varnish cache, and the derived image URL may be called (and thereby cached) again before S3 serves the new content, resulting in a long time serving of old cached content.
This patch avoids the issue by always making an unique suffix to the file name of the file stored remotely, while keeping the local Drupal URI intact.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | storage-unique_filename_for_styled_images-1936386-1.patch | 892 bytes | esbenvb |
Comments
Comment #1
esbenvb commentedHere's a patch.
IMPORTANT: When porting the patch, remember to include the correct author information as mentioned here: http://drupal.org/user/989064
Comment #2
jbrown commentedThe way I have thought about fixing this is to have an extra column in the storage_instance table called "expires". When an instance is deleted this column would be populated and the record would not be removed until the expires time is reached.
This way the existing mechanism of finding a unique filename would not reuse the filename too soon.
Comment #3
perignon commentedIs this still an issue. At over 2 years ago it's rather old. If this is still valid please reopen. The Storage API is under a lot of rework at the moment so contributions are welcome!