Files
rclone/backend
Nick Craig-Wood f92ccc785e s3: fix listing of directories containing "//" in object keys - fixes #9383
When an object key contained consecutive slashes (e.g.
"2026/1//file"), descending into the empty-named subdirectory failed
with "Entry doesn't belong in directory ... (too short)" and the
object was silently skipped during copy/sync.

The bug was in the listing-prefix slash logic: when the Fs had a
non-empty rootDirectory, the existing HasSuffix check did not append a
delimiter slash if the directory already ended in "/" - which it did
when the dir argument represented an empty-name traversal. The S3
listing prefix was therefore one slash short and returned the same
common-prefix as the parent listing, which the entry validator
rejected.
2026-04-28 15:06:15 +01:00
..
2025-06-12 18:31:01 +01:00
2025-02-28 11:31:14 +00:00
2025-02-28 11:31:14 +00:00
2025-02-28 11:31:14 +00:00
2025-02-28 11:31:14 +00:00
2024-08-12 13:35:44 +01:00
2025-02-28 11:31:14 +00:00
2025-02-28 11:31:14 +00:00
2025-02-28 11:31:14 +00:00
2025-11-13 13:47:40 +00:00