Motivation

We've got a reported in our Community Slack channel about issue with trailing slashes, especially with short key name (single characters). The trailing slashes would be missing:

awslocal s3api put-object --bucket sample-bucket2 --key "u/" --content-type "application/x-directory"
awslocal s3api list-objects-v2 --bucket sample-bucket2
...
       {
           "Key": "u",
           "LastModified": "2025-01-22T11:46:17.000Z",
           "ETag": "\"d41d8cd98f00b204e9800998ecf8427e\"",
           "Size": 0,
           "StorageClass": "STANDARD"
       },
...

I wrote a test for it and I had a hunch it came from our custom logic to parse URI parameters. We had custom logic for S3 because our router strips trailing slashes by default. We would check if the key name is in the path, and then split on the key and check if the leftover characters in the path are all slashes, to keep them.

However, to do so, we would partition the path on the parse Key parameter. Printing the result showed quite quickly what was the issue:

uri_params={'Bucket': 'test-bucket-ec3db341', 'Key': 'u'}
request.path.partition(uri_params["Key"])=('/test-b', 'u', 'cket-ec3db341/u/')

We would split/partition on the bucket name first while using path style. To avoid this, we need to start from the right side. That way, we properly get all the right side slashes.

Changes

• add new tests for single characters with trailing slash
• partition the trailing slashes the path by the Key, but starting from the right