Also related to that. In a situation where: * a bucket has 1M files in it * uploads are generally of 200 files at a time * each file name is guaranteed to ma

Also related to that. In a situation where: * a bucket has 1M files in it * uploads are generally of 200 files at a time * each file name is guaranteed to map to a unique content (content-addressable) * some of the files to upload might already be in the bucket It's actually quite expensive to list all of the bucket files to find out if they haven't been uploaded. Especially when the file names are hashes it's hard to filter by prefix as well. (same issue on S3) It would be great if there was a way to just upload the files and get an early 303 response if the entity already exists and has the same SHA1. That way the client can just push all the files without having to build the "new files" list.