SignatureDoesNotMatch for object keys with special characters in cloudserverclient

[maeldonn]

Problem

Object keys containing special characters (spaces, !, ', *, +,
parentheses, unicode, etc.) cause SignatureDoesNotMatch errors on all
backbeat metadata operations (GetMetadata, PutMetadata, etc.).

The Smithy serializer already percent-encodes path parameters when
building the request URL (e.g., spaces → %20). Then the SigV4 signer
re-encodes the path when computing the canonical URI because
uriEscapePath defaults to true, turning %20 into %2520. The
server computes the signature over the single-encoded path (%20), so
the signatures never match.

Simple alphanumeric keys are unaffected because their encoding is
idempotent.

How to reproduce

Call any backbeat route with a key containing a space:

await client.send(new GetMetadataCommand({
    Bucket: 'my-bucket',
    Key: 'file with spaces.txt',
})); // → SignatureDoesNotMatch

Fix

Default signingEscapePath to false in BackbeatRoutesClient and ProxyBackbeatApisClient constructors. This
tells the SigV4 signer to skip re-encoding the already-encoded path.

Callers can still override with signingEscapePath: true if needed.

Issue: CLDSRVCLT-13

[bert-e]

Hello maeldonn,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[maeldonn]

/approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/1.0

Please check the status of the associated issue CLDSRVCLT-13.

Goodbye maeldonn.

The following options are set: approve