Using uppercase UTF-8 in Conent-Type lead to signature verification failure in some third party S3 vendors, i.e. Quobyte. According to W3C charset value here is case-insensitive, so we don't break anything here with this PR, just support non-RFC compliant S3 implementations.
Using uppercase UTF-8 in Conent-Type lead to signature verification failure in some third party S3 vendors, i.e. Quobyte. According to W3C charset value here is case-insensitive, so we don't break anything here with this PR, just support non-RFC compliant S3 implementations.