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

Content-Disposition not supported in PutObjectAsync #1091

Open
Juulsgaard opened this issue May 28, 2024 · 0 comments
Open

Content-Disposition not supported in PutObjectAsync #1091

Juulsgaard opened this issue May 28, 2024 · 0 comments

Comments

@Juulsgaard
Copy link

Problem

Content-Disposition can't be assigned when calling PutObjectAsync via the SDK

Description

I am trying to achieve a setup using MinIO where all files are public for a simple storage solution on an isolated network.

It's working fine, but I have run into an issue when trying to assign a Content-Disposition to the objects when uploading.
I need Content-Disposition to be set on the object, since I won't be signing any URLs and thus won't be able to assign it there.

According to the S3 docs we should be able to just set the Content-Disposition in the PutObject request, but the .NET SDK is not allowing this.
From what I can see the issue here is that Content-Disposition isn't a valid request header, and it also isn't on the whitelist of additionally supported headers (see HttpRequestMessageBuilder.Request getter).
The error message is "Unsupported signed header: (content-disposition: " and is thrown in the HttpRequestMessageBuilder.Request getter.

Would it be possible to whitelist Content-Disposition so we can assign that header on object creation?

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