You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
rick2ricks
changed the title
Cannot set ResponseContentDisposition header with cloud front presigned url
Cannot set ResponseContentDisposition header with CloudFront presigned url
Nov 29, 2023
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
The text was updated successfully, but these errors were encountered: