I'm not sure whether this is a bug or not, and I'll investigate properly later but wanted to record it for now.
Just had a case where a user uploaded a file to Aeva Media, I downloaded it, and subsequently (minutes later) the file was updated, but every time I hit the download, I was still getting the cached earlier download.
I'm not sure off hand what headers are sent but it seems we may have to use the cache control headers to validate the time of last update.
Just had a case where a user uploaded a file to Aeva Media, I downloaded it, and subsequently (minutes later) the file was updated, but every time I hit the download, I was still getting the cached earlier download.
I'm not sure off hand what headers are sent but it seems we may have to use the cache control headers to validate the time of last update.