Skip to content

PUT vs POST and Zero Byte Files #58

Open
@justinkhill-emorysolutions

Description

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions