s3: remove Dot from encoding #4704

Before this change the s3 backend used Dot in its encoding. This meant
it was impossible to read and write a file called "." as we were
translating it to its unicode equivalent.

This means that the integration tests weren't testing the ability to
save and load files called "." and ".." at all.

This change removes the encoding which means that files called "."
(which need to be named with the unicode equivalent "." on the
command line) can be used.
This commit is contained in:
Nick Craig-Wood 2020-10-27 17:35:12 +00:00
parent fd2c373af1
commit c1bf3f3999

View file

@ -1190,8 +1190,7 @@ rclone does if you know the bucket exists already.
// - trailing / encoding
// so that AWS keys are always valid file names
Default: encoder.EncodeInvalidUtf8 |
encoder.EncodeSlash |
encoder.EncodeDot,
encoder.EncodeSlash,
}, {
Name: "memory_pool_flush_time",
Default: memoryPoolFlushTime,