I was constructing a File in the browser and hadn't given it a content type. s3-beam signed the request, but it wasn't valid when it was sent to S3. It would be good to add a client side assert that the File has a not null content-type to avoid this (I think).
I was constructing a File in the browser and hadn't given it a content type. s3-beam signed the request, but it wasn't valid when it was sent to S3. It would be good to add a client side assert that the File has a not null content-type to avoid this (I think).