4 ms·
A practical implementation of this would probably want to do a couple things: 1. As you mention, make sure they can't overwrite files 2. Have a content type w
by foota 10y ago
A practical implementation of this would probably want to do a couple things:
1. As you mention, make sure they can't overwrite files
2. Have a content type whitelist on the requestUploadURL function
3. Maybe authentication to keep track of who is submitting these requests?
Assuming that you're okay allowing someone to upload files with a given content-type to your bucket is there anything I'm missing?
- mnutt 10y agoFor #1, I would probably disallow writing to arbitrary paths and instead generate a path prefix using a UUID and return that to the client to ensure that every upload is unique.