Skip to content
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

S3 Compability: Content-Disposition for GetObject() not working #544

Open
2 tasks done
francis2tm opened this issue Sep 9, 2024 · 0 comments
Open
2 tasks done

S3 Compability: Content-Disposition for GetObject() not working #544

francis2tm opened this issue Sep 9, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@francis2tm
Copy link

francis2tm commented Sep 9, 2024

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

I'm a bit confused if this is a missing feature or a bug, as your docs don't specify if you support Content-Disposition for GetObject(), using AWS'S official rust S3 SDK.

To Reproduce

let presigned_request = state
        .s3_client
        .get_object()
        .bucket("file")
        .key(&file.s3_key)
        .response_content_disposition("attachment; filename=\"hello.txt\"")
        .presigned(PresigningConfig::expires_in(Duration::from_secs(3600)).unwrap())
        .await?;

println!("presigned_request: {:?}", presigned_request.uri());

Produces a valid presigned download URL but the downloaded filename is not the one provided in the content disposition header.

Expected behavior

Downloaded filename is the one provided in the content disposition header.

System information

  • OS: Ubuntu 22.04
  • Supabase CLI: 1.191.3
@francis2tm francis2tm added the bug Something isn't working label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant