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
MinioException: Minio API responded with message=The request signature we calculated does not match the signature you provided. Check your key and signing method
The minio server contains the following go function to create a signature based on signed headers.
// Trim leading and trailing spaces and replace sequential spaces with one space, following Trimall()// in http://docs.aws.amazon.com/general/latest/gr/sigv4-create-canonical-request.htmlfuncsignV4TrimAll(inputstring) string {
// Compress adjacent spaces (a space is determined by// unicode.IsSpace() internally here) to one space and returnreturnstrings.Join(strings.Fields(input), " ")
}
The minio-dotnet library however calcucates the siganture without removing additional spaces.
If that is true, then this issue needs to be opened in the other libs aswell as I think at least minio-go and minio-js don't have anything related to trimAll, too.
The text was updated successfully, but these errors were encountered:
WolfspiritM
changed the title
Signature invalid if metadata contains two spaces
Signature invalid if metadata contains two consecutive spaces
Jan 18, 2019
S3 Spec requires canonicalized header string to have all extra
spaces trimmed down to a single space. This PR fixesminio#277, where
metadata with extra spaces in the value was causing a signature
verification mismatch.
S3 Spec requires canonicalized header string to have all extra
spaces trimmed down to a single space. This PR fixes#277, where
metadata with extra spaces in the value was causing a signature
verification mismatch.
Hi,
When using MetaData that contains two consecutive spaces the signature doesn't match with the calulcated server signature.
The minio server contains the following go function to create a signature based on signed headers.
The minio-dotnet library however calcucates the siganture without removing additional spaces.
If that is true, then this issue needs to be opened in the other libs aswell as I think at least minio-go and minio-js don't have anything related to trimAll, too.
The text was updated successfully, but these errors were encountered: