-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PUT vs POST and Zero Byte Files #58
Comments
Same here, I would like to be able to use presigned urls for PUT requests. Any updates on this? |
we abandoned this component and did it on our own using code similar to this
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're using a python / django backend to generate the presigned url as described here: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3.html#S3.Client.generate_presigned_url
We're getting an error from S3 upon upload complaining that the signature doesn't match. We discovered that if we change the bucket loader code to do a PUT instead of a POST that we could get past that error.
New problem though. The files are being created in S3 but they are all zero bytes.
What are we missing here? Our next step is to try the boto3 method to generate a presigned post instead of a presigned url.
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3.html#S3.Client.generate_presigned_post
Hope that works, but it has a bunch of formfields and other return data besides just the URL that I'm not sure the bucket loader component can handle? If anyone has any other suggestions, please comment.
The text was updated successfully, but these errors were encountered: