Date Options: Please explain in description/FAQ + Impact on browser caching
-
Hi, during “Replace Media Upload” you have this:
Date Options
When replacing the media, do you want to:
( ) Replace the date
(?) Keep the date (18/Aug/2021 23:38)
( ) Set a Custom DateI wish the description and/or the FAQ would have addressed what consequences these options have. Meanwhile I found out myself by trial and error:
“Keep the date” is the default. This can have bad consequences with browser caching! I am not talking about server caching or CDN here. This should specifically also be addressed in FAQ “I replaced a file, but it didn’t change!”.
Environment
– macOS 11.4 Big Sur
– Safari 14.1.1Reproduction I
1) Replace media with “Keep the date”.
2) In normal view mode, access a page which embeds that media, via the menu.
3) The browser shows the old outdated image.
I assume because the HTTP timestamp header for the image file is unchanged (an eTag based on content hashing or comparing the HTTP size header should make clear that the file has indeed changed).
4) A forced page reload then shows the new image. This is insufficient as returning visitors with a browser cache should not get outdated imagery but also the newest like fresh visitors.Reproduction II
1) Replace media with “Replace the date”. (sets it to now)
2) In normal view mode, access a page which embeds that media, via the menu.
3) The browser immediately shows the updated image.Feature Improvement for “Set a Custom Date”
– “Set a Custom Date” by default copies “now” into the field.
– This is not a good init value as it’s redundant to option 1 “Replace the date”.
– I propose the following:(?) Set a Custom Date
[__________] [__] [__] Now | Original– The fields get initializing with the original timestamp.
– Clicking the “Now” or “Original” action link/button update the date/time fields accordingly.
- The topic ‘Date Options: Please explain in description/FAQ + Impact on browser caching’ is closed to new replies.