Ben McClelland 9816c2fdb3 fix: add gcs compatibility flag to fix s3proxy GCS SigV4 signature mismatch ...

The AWS SDK v2 includes Accept-Encoding in SigV4 signed headers
which causes GCS to return a SignatureDoesNotMatch error because
GCS rewrites that header internally before verifying the signature.

Add a --gcs-compatibility / VGW_S3_GCS_COMPATIBILITY option for the s3proxy
backend that injects two Smithy finalize-layer middlewares: one removes
Accept-Encoding from the request immediately before the Signing step, and
a second restores it after signing so the header is still sent on the wire.

see: https://github.com/aws/aws-sdk-go-v2/issues/1816

This can be removed once GCS fixes this incompatibility.

2026-04-14 10:53:26 -07:00

..

client.go

fix: add gcs compatibility flag to fix s3proxy GCS SigV4 signature mismatch

2026-04-14 10:53:26 -07:00

s3.go

fix: add gcs compatibility flag to fix s3proxy GCS SigV4 signature mismatch

2026-04-14 10:53:26 -07:00