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

Cannot set ResponseContentDisposition header with CloudFront presigned url #1342

Open
rick2ricks opened this issue Nov 29, 2023 · 0 comments

Comments

@rick2ricks
Copy link

Hello,

This might be a problem with boto3 or some misconfiguration on my S3 and CloudFront distribution, but maybe someone here knows about this issue. 

When I pass { "ResponseContentDisposition": 'inline; filename="teste.jpg"' to S3Storage url method without using a custom domain ( CloudFront ) , the presigned url works as intended and opens the file in another browser tab, but when I try the same with a custom domain, the parameters are added to the url but CloudFront does not add the content disposition header.

Is it the expected behaviour? If so, how can I use both "content disposition" header set  dynamically when generating the file url with my custom domain?

Thanks

@rick2ricks rick2ricks changed the title Cannot set ResponseContentDisposition header with cloud front presigned url Cannot set ResponseContentDisposition header with CloudFront presigned url Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant