Open krosaen opened 8 years ago
Amazon's docs say that, for multipart uploads, the ETag "will not necessarily be an MD5 hash of the object data." They don't actually say what it will be, just that it isn't the md5.
So, we don't have a confident way to know that the mp3s have not changed.
One option is to just look at file size and last-modified time for files that don't have usable ETags. This seems a little dangerous because the file contents could change without changing the size and we wouldn't know to push the update. Maybe we could disable it by default, but let users enable it through config if they understand the risk.
Thanks for the additional details, Spencer, makes sense—I can certainly give something like you suggest a try if the redeployment of the mp3s really becomes a hassle.
When deploying a lektor site that hosts a podcast each mp3 file is re-uploaded each time:
I'm guessing this is due to, as the code states,
so perhaps this is a feature request—is there a way to set the etag field for larger objects?