Compliance to aws s3's relaxed query handling behaviour
While s3 docs at https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-query-string-auth.html mention all params must be url encoded, s3's behaviour seems to be relaxed in its enforcement and allows for x-amz-credentials of the form access/<date>/<region>... where the url encoded form of access%2F<date> is expected as the canonical string.
#5 Updated by Dan van der Ster 2 months ago
This was merged and released in nautilus. Do you still plan the backports?
(We saw this in prod, see https://github.com/GoogleContainerTools/jib/issues/1590)