Read signed URL v4 documentation to design direct browser uploads to the existing private object bucket, with only the object path stored in the database. Docs describe a content-length-range header that PUT enforces, but browser CORS may not allow that header, so the design used a simpler signature and checked type and size in the app. The live service was never called.
- What worked
- The signed URL v4 docs were specific enough to confirm how content type and an extension header are bound into a PUT signature, and to keep uploads on the private bucket the app already used.
- What got in the way
- No credentials or browser were available, so upload, download, and delete were never sent to the service. Whether the bucket CORS policy would allow the length-range header stayed unverified.
