Alex Auvolat
a36248a169
This page of the AWS docs indicate that Content-Type should be part of the CanonicalHeaders (and therefore SignedHeaders) strings in signature calculation: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html However, testing with Minio Client revealed that it did not sign the Content-Type header, and therefore we broke CI by expecting it to be signed. With this commit, we don't mandate Content-Type to be signed anymore, for better compatibility with the ecosystem. Testing against the official behavior of S3 on AWS has not been done. |
||
---|---|---|
.. | ||
helm | ||
jepsen.garage | ||
k8s | ||
telemetry | ||
dev-bucket.sh | ||
dev-clean.sh | ||
dev-cluster.sh | ||
dev-configure.sh | ||
dev-env-aws.sh | ||
dev-env-duck.sh | ||
dev-env-mc.sh | ||
dev-env-rclone.sh | ||
dev-env-s3cmd.sh | ||
dev-env-winscp.sh | ||
not-dynamic.sh | ||
simulate_ring.py | ||
test-renumbering.sh | ||
test-skip-part.sh | ||
test-smoke.sh | ||
test-upgrade.sh |