We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello everyone,
I have a problem with the C# package. I keep getting the same error message when transferring data to the IONOS S3 storage:
"Content-MD5 HTTP header is required for Put Object requests with Object Lock parameters"
I have set the MD5 content:
And yet I still get this error message
A colleague pointed it out to me, that the name that was transferred
“X-Amz-Meta-Content-Md5”
would be!?
I told him no, I use “Content-Md5”
Then I debugged the code:
You see the name is an other, as I set. Monio does not use the name given, but uses his own.
My question is why is that? Is that correct? Is this a bug?
The text was updated successfully, but these errors were encountered:
I don't know much about this package, but Content-MD5 is added if WithRetentionConfiguration has been set.
WithRetentionConfiguration
I don't know if there is any other way of setting it, so I will leave it here for someone more deeply into this package to look at it.
Sorry, something went wrong.
No branches or pull requests
Hello everyone,
I have a problem with the C# package.
I keep getting the same error message when transferring data to the IONOS S3 storage:
"Content-MD5 HTTP header is required for Put Object requests with Object Lock parameters"
I have set the MD5 content:
And yet I still get this error message
A colleague pointed it out to me,
that the name that was transferred
“X-Amz-Meta-Content-Md5”
would be!?
I told him no, I use “Content-Md5”
Then I debugged the code:
You see the name is an other, as I set.
Monio does not use the name given, but uses his own.
My question is why is that?
Is that correct?
Is this a bug?
The text was updated successfully, but these errors were encountered: