Double slashes in path

[dongxiao1198]

Describe the bug

I got a path like : s3://bucket/xxxxxxxxx//file, and I found that when sending the http request, aws sdk will replace the "//" with "/"(checked the url in sdk debug log).
But actually s3 server side support key like "xxxxxxxxx//file", so why sdk doing this?

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Is there any configurations to change this behavior?

Current Behavior

sdk will replace the "//" with "/"

Reproduction Steps

write a file like : s3://bucket/xxxxxxxxx//file, and you will find the file s3://bucket/xxxxxxxxx/file on server

Possible Solution

No response

Additional Information/Context

No response

AWS CPP SDK version used

1.11.352

Compiler and Version used

llvm18

Operating System and version

centos&macos

[dongxiao1198]

I found this setting:
/**
* When constructing Path segments in a URI preserve path separators instead of collapsing
* slashes. This is useful for aligning with other SDKs and tools on key path for S3 objects
* as currently the C++ SDK sanitizes the path.
*
* TODO: In the next major release, this will become the default to align better with other SDKs.
*/
bool preservePathSeparators = false;

when I set it to 'true', the path issue is resolved, but there is a new issue: when calling the role api like this：
Aws::STS::Model::AssumeRoleRequest request;
request.SetDurationSeconds(ttlSeconds);
if (!externalId.empty()) request.SetExternalId(externalId);
request.SetRoleArn(roleArn);
request.SetRoleSessionName(sessionName);

there is a error：


Sender
SignatureDoesNotMatch
The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.

6de28a5b-15a2-4965-8b72-8032d5c3f9be

it seems like this flag changed the behavior of AWSAuthV4Signer

[pulimsr]

This issue has been fixed in PR #3499. Please upgrade to a newer version of the SDK that includes this fix.

[dongxiao1198]

This issue has been fixed in PR #3499. Please upgrade to a newer version of the SDK that includes this fix.

Thx a lot

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

[dongxiao1198]

@pulimsr Have you test writing file path like :
s3://bucket/test/test_dir/?
it seems this path will ignore the tailing slash...and actually writing file
s3://bucket/test/test_dir