4 ms·
If you know the file hash beforehand, you can encode that into the signed URL. But if you’re saying clients will upload the wrong file, then that’s not really
by orf 4y ago
If you know the file hash beforehand, you can encode that into the signed URL.
But if you’re saying clients will upload the wrong file, then that’s not really AWS’s fault is it?
If you’re saying the file itself is corrupted, I’m not sure how? The upload should fail if the content length is incorrect, and s3 doesn’t make the contents visible unless the upload completes.
- gw98 4y agoIt's the eventual consistency nature of the problem. You have to check and you can't guarantee. Don't expect the clients to work properly either. Edge notoriously started uploading zero byte files when already open in MS office a few months back. Also network connections time out, users close browser tabs etc etc.