Skip to content

getSignedUrl #583

@jacksonStone

Description

@jacksonStone

I've found this issue: #57 which has a comment indicating that CORs related features are not supported. Is this still the case?

So when using the AWS SDK, I want to preform direct downloads using the getSignedUrl. I have used the putBucketCors api command and updated everything accordingly on a bucket I've created.

S3.putBucketCors({ Bucket: <bucket_name>, CORSConfiguration: { CORSRules: [ { AllowedMethods: ["GET"], AllowedOrigins: ["*"], AllowedHeaders: ["*"], MaxAgeSeconds: 60 }, ] }})

However, I still get a: No 'Access-Control-Allow-Origin' header is present on the requested resource. When I attempt to make a request to the signed URL.

When I have an identical bucket configuration on my personal AWS account, I am able to preform direct downloads as expected, however when running this in docker, it seems the bucket cors configuration is not respected.

Is direct upload and download still unsupported behavior?

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